
From duerst@it.aoyama.ac.jp  Sun Apr  1 22:32:59 2012
Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF26E11E80B6 for <wgchairs@ietfa.amsl.com>; Sun,  1 Apr 2012 22:32:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.056
X-Spam-Level: 
X-Spam-Status: No, score=-96.056 tagged_above=-999 required=5 tests=[AWL=-0.158, BAYES_50=0.001, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265,  MIME_8BIT_HEADER=0.3, MISSING_HEADERS=1.292, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id enoKdbePdYTf for <wgchairs@ietfa.amsl.com>; Sun,  1 Apr 2012 22:32:59 -0700 (PDT)
Received: from scintmta02.scbb.aoyama.ac.jp (scintmta02.scbb.aoyama.ac.jp [133.2.253.34]) by ietfa.amsl.com (Postfix) with ESMTP id 0A8FE11E80B2 for <wgchairs@ietf.org>; Sun,  1 Apr 2012 22:32:58 -0700 (PDT)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta02.scbb.aoyama.ac.jp (secret/secret) with SMTP id q325Wpg3020918 for <wgchairs@ietf.org>; Mon, 2 Apr 2012 14:32:51 +0900
Received: from (unknown [133.2.206.133]) by scmse02.scbb.aoyama.ac.jp with smtp id 677d_b8bb_4a53a3fc_7c85_11e1_a8b1_001d096c5782; Mon, 02 Apr 2012 14:32:50 +0900
Received: from [IPv6:::1] ([133.2.210.1]:44516) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S15B1D63> for <wgchairs@ietf.org> from <duerst@it.aoyama.ac.jp>; Mon, 2 Apr 2012 14:32:54 +0900
Message-ID: <4F793A01.5010607@it.aoyama.ac.jp>
Date: Mon, 02 Apr 2012 14:32:49 +0900
From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
Subject: A caution to chairs re. Etherpad
References: <4EBA594C.1060406@levkowetz.com>	<4F69CC24.1020509@labn.net>	<4F6FA690.4080601@levkowetz.com>	<4F76C0F7.1000308@viagenie.ca> <005270DF49C9185F858E16A7@PST.JCK.COM>
In-Reply-To: <005270DF49C9185F858E16A7@PST.JCK.COM>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: wgchairs@ietf.org, vmeet@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, 02 Apr 2012 05:33:00 -0000

Just a little caution for future meetings re. Etherpad.

What happended in the IRI WG meeting was that we had a very busy chair, 
who was looking at Etherpad and saw that somebody had started to type a 
line or two, and thus said "oh, great, I see we have a minute taker" and 
went on.

It turned out that this was me who wanted to help out as much as 
possible, but I was up for talking about the first two documents and so 
wasn't able to actually scribe. I realized the problem a few minutes 
into the meeting, and the chair said he'd reconstruct minutes from the 
audio.

Conclusion: Collaborative minute taking is great, but still make sure 
that there is somebody who is committed and able to take actual minutes.

Regards,   Martin.

From jgs@bgp.nu  Mon Apr  2 03:31:33 2012
Return-Path: <jgs@bgp.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 5424521F8693 for <wgchairs@ietfa.amsl.com>; Mon,  2 Apr 2012 03:31:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.629
X-Spam-Level: 
X-Spam-Status: No, score=-99.629 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, HELO_IS_SMALL6=0.556, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HybdtAjAuxOa for <wgchairs@ietfa.amsl.com>; Mon,  2 Apr 2012 03:31:33 -0700 (PDT)
Received: from bgp.nu (bgp.nu [147.28.0.53]) by ietfa.amsl.com (Postfix) with ESMTP id F1E1221F85CC for <wgchairs@ietf.org>; Mon,  2 Apr 2012 03:31:32 -0700 (PDT)
Received: from sa-nc-cs-85.static.jnpr.net (natint3.juniper.net [66.129.224.36]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by bgp.nu (Postfix) with ESMTP id 1E29766D36F; Mon,  2 Apr 2012 06:31:31 -0400 (EDT)
Subject: Re: Etherpad deployment for this meeting
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=iso-8859-1
From: "John G. Scudder" <jgs@bgp.nu>
In-Reply-To: <4F76C0F7.1000308@viagenie.ca>
Date: Mon, 2 Apr 2012 12:31:29 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <BC5B3623-A908-419D-BC52-3C043ED13487@bgp.nu>
References: <4EBA594C.1060406@levkowetz.com> <4F69CC24.1020509@labn.net> <4F6FA690.4080601@levkowetz.com> <4F76C0F7.1000308@viagenie.ca>
To: Simon Perreault <simon.perreault@viagenie.ca>
X-Mailer: Apple Mail (2.1257)
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: John Scudder <jgs@juniper.net>
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Apr 2012 10:31:33 -0000

On Mar 31, 2012, at 10:31 AM, Simon Perreault wrote:

> I used Etherpad as a minute taker and overall loved it. FYI, I found =
two minor annoyances, don't know if they are already known:
>=20
> - About every 30 minutes (not exactly sure), it "disconnects" and asks =
me to reconnect. The button is above the page cut (I have a small =
netbook) so it took me a while to notice it. When I clicked it I got =
reconnected without data loss.

FWIW this didn't happen to me. I used Etherpad for at least three =
different WGs.

> - The "chat" button at the bottom right is in the way when typing. It =
would be better if it was somewhere else.

I agree. As far as I'm concerned the "somewhere else" could be "gone" =
but maybe others find it useful.

--John=

From smb@cs.columbia.edu  Fri Mar 30 00:20:43 2012
Return-Path: <smb@cs.columbia.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 E3E7C21E8056; Fri, 30 Mar 2012 00:20:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level: 
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[AWL=2.000,  BAYES_00=-2.599, 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 QPMW8Vn7ECJh; Fri, 30 Mar 2012 00:20:43 -0700 (PDT)
Received: from paneer.cc.columbia.edu (paneer.cc.columbia.edu [128.59.29.4]) by ietfa.amsl.com (Postfix) with ESMTP id 03E8121E8015; Fri, 30 Mar 2012 00:20:42 -0700 (PDT)
Received: from ninthray.home (APuteaux-155-1-62-18.w90-2.abo.wanadoo.fr [90.2.21.18]) (user=smb2132 mech=PLAIN bits=0) by paneer.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id q2U7KbwT000904 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 30 Mar 2012 03:20:39 -0400 (EDT)
Subject: Re: [BOFCHAIRS] [vmeet] Remote participation
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Steven Bellovin <smb@cs.columbia.edu>
In-Reply-To: <1332966135.4980.75.camel@minbar.fac.cs.cmu.edu>
Date: Fri, 30 Mar 2012 09:20:37 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <25D805D4-16EA-4E3B-B37E-D67A058E1827@cs.columbia.edu>
References: <4F729503.5080003@gmail.com> <0BBF44E367CFEE54C9AC516D@PST.JCK.COM> <6.2.5.6.2.20120328035236.0c7dc648@elandnews.com> <CAJNg7VLR0LVW3MqKAeC=0O5_UuwAP69f_w1BuG+YnVedudg8qQ@mail.gmail.com> <24143_1332964425_q2SJriGr012797_6.2.5.6.2.20120328103857.0c1fb050@elandnews.com> <1332966135.4980.75.camel@minbar.fac.cs.cmu.edu>
To: Jeffrey Hutzelman <jhutz@cmu.edu>
X-Mailer: Apple Mail (2.1257)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.4
X-Mailman-Approved-At: Mon, 02 Apr 2012 07:14:54 -0700
Cc: SM <sm@resistor.net>, vmeet@ietf.org, wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Mar 2012 07:20:44 -0000

On Mar 28, 2012, at 10:22 PM, Jeffrey Hutzelman wrote:
> 
> 
> While I think we (and society in general) do tend to overuse slides in
> situations where they don't really add anything,

I'll note that folks who are non-native speakers of English are often
helped significantly by having slides projected.  I've certainly
seen many people taking pictures of the screen, back before early
upload was the policy.


		--Steve Bellovin, https://www.cs.columbia.edu/~smb






From sm@resistor.net  Fri Mar 30 11:56:40 2012
Return-Path: <sm@resistor.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 E984821F867C; Fri, 30 Mar 2012 11:56:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.62
X-Spam-Level: 
X-Spam-Status: No, score=-102.62 tagged_above=-999 required=5 tests=[AWL=-0.021, 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 LyZu-ztMkoq2; Fri, 30 Mar 2012 11:56:38 -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 CDF2221F8645; Fri, 30 Mar 2012 11:56:38 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q2UIuNEn018683; Fri, 30 Mar 2012 11:56:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1333133789; i=@resistor.net; bh=fjGMNMHJ7UtgCHqHh1b/TgwLHkYILFRV8GsRuOinPrE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=1ampvMUaBbuRnNBJQImNi6afxSYjxKDdGtUq0DcJ5QtF/gCDs4XF4Q0jlxIHLlCp+ 9BREb6xU+B/ruQ5eqs4Ro68P3np5ric6CA8tPcppt5AyfVMED/xOKh42A98oB/NTdX b5W5DAGFXNUpBK56dlviDBgksPbzZ3v3YYQlWr0k=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1333133789; i=@resistor.net; bh=fjGMNMHJ7UtgCHqHh1b/TgwLHkYILFRV8GsRuOinPrE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=GTJSgEZ0TAuPV/XXyJRbv0mYJ/cNQhNdXwftPQvVU7MXN20za3vdVzBOkXfUhLqCU JnKatMusHVh6BsUiYahUycAcUJqgXK3vOEVPIj7PA7K+zOdFke9G+TG3+lK4K4+1Eu oC2chC5HFz5yb0NGsu5nd33z6CYLN+acwRW245CY=
Message-Id: <6.2.5.6.2.20120330090037.0901d0f0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 30 Mar 2012 11:34:22 -0700
To: John C Klensin <john-ietf@jck.com>
From: SM <sm@resistor.net>
Subject: Re: [vmeet] [BOFCHAIRS]  Remote participation
In-Reply-To: <C74241B313CA00C3A1D03E7F@PST.JCK.COM>
References: <4F729503.5080003@gmail.com> <0BBF44E367CFEE54C9AC516D@PST.JCK.COM> <6.2.5.6.2.20120328035236.0c7dc648@elandnews.com> <CAJNg7VLR0LVW3MqKAeC=0O5_UuwAP69f_w1BuG+YnVedudg8qQ@mail.gmail.com> <24143_1332964425_q2SJriGr012797_6.2.5.6.2.20120328103857.0c1fb050@elandnews.com> <1332966135.4980.75.camel@minbar.fac.cs.cmu.edu> <25D805D4-16EA-4E3B-B37E-D67A058E1827@cs.columbia.edu> <C74241B313CA00C3A1D03E7F@PST.JCK.COM>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Mailman-Approved-At: Mon, 02 Apr 2012 07:14:54 -0700
Cc: wgchairs@ietf.org, vmeet@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Mar 2012 18:56:41 -0000

At 08:48 30-03-2012, John C Klensin wrote:
>(1) Almost any observation that is based on the advantages of
>slides by non-native speakers also applies to real-time minutes,
>transcripts, Jabber sessions, etc.  Done well, any or all of
>them may be easier to understand than a real-time speaker,
>especially one who is speaking too quickly.

If I recall correctly, a very rough estimate of the cost for 
providing real-time transcription of one week of sessions came to 
under $10,000.

Advantages are:

   (a) The discussions are more accessible for non-English (local and
       remote) participants

   (b) Local participants in another session can follow what is going on

   (c) The transcript can be used to produce minutes for the session

   (d) The transcript can be read by people who have not attended the session

   (e) The transcript can be (easily) translated by the reader

   (f) It does not require an additional screen

   (g) A minute-taker is no longer required

   (h) Less pressure to upload slides before the session

   (i) The content of a session is searchable

Disadvantages are:

   (a) It is not always possible for the person transcribing to capture
       the name of the speaker or some technical words

   (b) It's an additional cost

   (c) There can be network connectivity issues

   (d) There may be an indirect negative impact on attendance revenue

   (e) It may be workable for regular meetings only

   (f) The content of a session is searchable

 From the IETF 82 proceedings:

   Technical plenary http://www.ietf.org/proceedings/82/minutes/plenaryt.txt
   AppArea           http://www.ietf.org/proceedings/82/minutes/appsawg.txt
   IntArea           http://www.ietf.org/proceedings/82/minutes/intarea.txt
   OpsArea           http://www.ietf.org/proceedings/82/minutes/opsawg.txt
   RtgArea           http://www.ietf.org/proceedings/82/minutes/rtgwg.txt
   SecArea           http://www.ietf.org/proceedings/82/minutes/saag.txt
   TsvArea           http://www.ietf.org/proceedings/82/minutes/tsvwg.txt

The quality of reporting varies widely.  I suggest reading the 
proceedings for an area you are involved in to get an idea of the 
remote participant experience.  For English as a foreign language, 
pick an area you are not involved in.

Regards,
-sm 


From sm@resistor.net  Fri Mar 30 16:32:08 2012
Return-Path: <sm@resistor.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 DABA521F8646; Fri, 30 Mar 2012 16:32:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.62
X-Spam-Level: 
X-Spam-Status: No, score=-102.62 tagged_above=-999 required=5 tests=[AWL=-0.021, 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 L82E2GssSja1; Fri, 30 Mar 2012 16:32:07 -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 0BAA621F8645; Fri, 30 Mar 2012 16:32:06 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q2UNVnLx003460; Fri, 30 Mar 2012 16:31:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1333150315; i=@resistor.net; bh=LTPLswIR2RAVEAGvoBdKcmGos0t52EdHRWHfHvYg+ck=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=f3+C4BdDRCZtEQvBPjetuZAgcEk4I691Vy5fCLSsisr0RMZ5DxF/11CrvI1CU5fw5 tMRzLbKrbAhe0sgaqL3Z/AhfUgP4cbty0gDO2koWbsC1GBmDngoHcDhwTRkIPL3U5C PnBIQNj65Q+tqRmIIEya7CedV8V5+SKvB/PjLnFM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1333150315; i=@resistor.net; bh=LTPLswIR2RAVEAGvoBdKcmGos0t52EdHRWHfHvYg+ck=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=dZRfSxXVVZkq44O3d8v8OpjPV/cgd5e8f4SyFpcORvoGcVnI/cYp/33bPblt0CJZn CPgoN9Oo3JZMU6Tx0noWIZ8dVwq3hxUpq6Cioz9kGn9sp62JHGQm+Y1rVjSz7ka1eh eMgYW6zibBRUBitRiq1iDC8iLqDS52hjfTVboLXg=
Message-Id: <6.2.5.6.2.20120330151904.0d747920@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 30 Mar 2012 16:18:57 -0700
To: John C Klensin <john-ietf@jck.com>
From: SM <sm@resistor.net>
Subject: Re: [vmeet] [BOFCHAIRS]  Remote participation
In-Reply-To: <A838D9E54AA2FBA66AC29F99@PST.JCK.COM>
References: <4F729503.5080003@gmail.com> <0BBF44E367CFEE54C9AC516D@PST.JCK.COM> <6.2.5.6.2.20120328035236.0c7dc648@elandnews.com> <CAJNg7VLR0LVW3MqKAeC=0O5_UuwAP69f_w1BuG+YnVedudg8qQ@mail.gmail.com> <24143_1332964425_q2SJriGr012797_6.2.5.6.2.20120328103857.0c1fb05 0@elandnews.com> <1332966135.4980.75.camel@minbar.fac.cs.cmu.edu> <25D805D4-16EA-4E3B-B37E-D67A058E1827@cs.columbia.edu> <C74241B313CA00C3A1D03E7F@PST.JCK.COM> <6.2.5.6.2.20120330090037.0901d0f0@elandnews.com> <A838D9E54AA2FBA66AC29F99@PST.JCK.COM>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Mailman-Approved-At: Mon, 02 Apr 2012 07:14:54 -0700
Cc: wgchairs@ietf.org, vmeet@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Mar 2012 23:32:09 -0000

Hi John,
At 15:14 30-03-2012, John C Klensin wrote:
>Just so we understand what we are talking about, that means all
>eight tracks, plus the plenaries?  My recollection of how much

Yes.

>skilled transcribers can do at a time combined with the length
>of our day, is that would mean at least 10 and probably 12-15,
>transcription people.  Is that roughly what the figure you give
>is based on?  And does it include airfare and hotels for those
>people (noting that they would, e.g., outnumber Secretariat
>staff for the duration of a meeting.

No, I meant doing the transcription remotely to avoid the expenses of 
airfare and hotels.  Skilled transcribers are more expensive.  BTW, I 
looked up the figures over a year ago.

>It does if people who are in the room want to see the
>transcript.  Experience at multiple IETF plenaries and several
>other organizations (including ICANN) indicates that they
>usually do.  The other advantage of transcripts is that they can
>be used by folks who don't hear well.  If they are in the room,
>that certainly requires an extra screen, at least unless you
>expect that population to all bring laptops and spend their time
>hunched over them.

The screen may not be as visible from the back of the room.  If 
people in the room want to see the transcript, they bring their 
laptop.  If you can follow the conversation, you don't need the 
transcript.  The service could be optional; it's up to the session 
chair to make the call.

>I don't think so.  For non-native speakers of whatever language
>the speakers are speaking, ability to review slides in advance
>is a big help.

Ok.

>If the speaker doesn't speak English really clearly, or speaks
>it very quickly, or both, the quality of transcription can
>easily fall below the level needed to make the above advantages
>real.  In that case, the problem is not just speaker names and
>technical words

Yes.  If the quality of transcription falls below an acceptable 
level, the question that arise is whether the people in the room have 
understood what they heard.  But let's not go there as we'll end up 
trying to solve a lot of problems.

After reading 
http://www.ietf.org/mail-archive/web/oauth/current/msg08692.html my 
opinion is that having a transcription might help in such cases.

Regards,
-sm 


From sm@resistor.net  Sat Mar 31 03:49:21 2012
Return-Path: <sm@resistor.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 0B10E21F856A; Sat, 31 Mar 2012 03:49:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.62
X-Spam-Level: 
X-Spam-Status: No, score=-102.62 tagged_above=-999 required=5 tests=[AWL=-0.021, 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 K7lczDzxiCaz; Sat, 31 Mar 2012 03:49:19 -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 D344E21F8555; Sat, 31 Mar 2012 03:49:19 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q2VAnCVZ005142; Sat, 31 Mar 2012 03:49:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1333190958; i=@resistor.net; bh=aQfr90mayk4k/2tG+j/j3aG0KoAgZ+l2BMO+sLUIHm4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=1dVRT8KxuGVyXdXs74K59XPzcC2dOkrqyXsJFJ2NP8iLSYaa+ZSLzbYtj6Z/mfCMH f4qPGkA942RXKQpKNVGw+8EPDyv4+s6jaTwX6NIZC7ig61MKk1UTM/DRRQrUH5SSTd zSm/v44fEbeMuskvFwbvQ8kjrETMRRsqUUnC/Pn8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1333190958; i=@resistor.net; bh=aQfr90mayk4k/2tG+j/j3aG0KoAgZ+l2BMO+sLUIHm4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=l7AJ/FlOlTmU46JqbOEloUPRHoa9KENlCYwa6psdX81nuZFCVp+/pNAVUMYVTCpHm 7LH11y7uR2frN4jBBVF7adzKzTTSexsU9/Z9WWaRc2MAQ6Ar3P6zw8diQSjV3jaQFQ AL4TxGxyf/GRf2CkVTCZTzoBUd01DB2sUH5MABLE=
Message-Id: <6.2.5.6.2.20120330234220.0d442ed0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 31 Mar 2012 03:49:07 -0700
To: John C Klensin <john-ietf@jck.com>
From: SM <sm@resistor.net>
Subject: Re: [vmeet] [BOFCHAIRS]  Remote participation
In-Reply-To: <932A5044CE359AECF4537FC7@PST.JCK.COM>
References: <4F729503.5080003@gmail.com> <0BBF44E367CFEE54C9AC516D@PST.JCK.COM> <6.2.5.6.2.20120328035236.0c7dc648@elandnews.com> <CAJNg7VLR0LVW3MqKAeC=0O5_UuwAP69f_w1BuG+YnVedudg8qQ@mail.gmail.com> <24143_1332964425_q2SJriGr012797_6.2.5.6.2.20120328103857.0c1fb05 0@elandnews.com> <1332966135.4980.75.camel@minbar.fac.cs.cmu.edu> <25D805D4-16EA-4E3B-B37E-D67A058E1827@cs.columbia.edu> <C74241B313CA00C3A1D03E7F@PST.JCK.COM> <6.2.5.6.2.20120330090037.0901d0f0@elandnews.com> <A838D9E54AA2FBA66AC29F99@PST.JCK.COM> <6.2.5.6.2.20120330151904.0d747920@elandnews.com> <932A5044CE359AECF4537FC7@PST.JCK.COM>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Mailman-Approved-At: Mon, 02 Apr 2012 07:14:54 -0700
Cc: wgchairs@ietf.org, vmeet@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Mar 2012 10:49:21 -0000

Hi John,
At 19:55 30-03-2012, John C Klensin wrote:
>Interesting idea.  Of course, if the audio fails, we would
>essentially have what used to be called a domino effect: if
>minutes and everything else depended on the transcribers, the
>transcribers were remote, and the audio went out, the WG might
>reasonably adjourn to the nearest location dispensing coffee or
>stronger beverages.

If the audio fails, you have audio recordings to work from.  It's up 
to the session chair to assess the situation and figure out what to 
do.  It is reasonable for the WG to adjourn.  It is also reasonable 
for the AD to shut down the WG if it's not delivering.

>I worry a little about expecting people to read transcripts on
>their laptops for three reasons:
>
>         (i) Trying to keep track of the laptop screen largely
>         prevents looking at the slides which, we would like to
>         hope, actually contain information.  It might interfere
>         with Jabber tracking even more.

Yes.

>
>         (ii) It might discourage getting up and standing in
>         microphone lines, etc., to comment and participate.

The transcription might provide some statistics about mic attendees, 
how much time they spend at the mic, whether the comment actually 
helps to resolve the issue being discussed.

In a session on Friday, overall, the people who stepped to the mic 
line are from North America.  There was only one non-English 
speaker.  Around 83% of the IETF output is from English 
speakers.  That may fall down to around 60% in the near future.  If 
we ignore the presentations, the numbers for standing up in 
microphone lines do not tally with the trend.

Nothing in what I suggest is going to fix that.

>         (iii) For a WG Chair (or equivalent) looking into the
>         audience and seeing who is huddled over their laptops,
>         presumably reading mail and who is paying attention.
>         Having a significant number of people huddled over their
>         laptops reading transcripts fouls up that particular bit
>         of inference because that group is mentally present in
>         the WG, while most of the mail-readers are not.

There is a significant number of tourists in a WG session.  If a 
person is not paying attention, he/she shouldn't be surprised when 
the minutes shows that he/she contributed to some decision.

BTW, I forgot to mention that some of the tourists are a bit more 
than that.  They take notes of what goes on in a session for internal 
reporting.

At 01:19 31-03-2012, Marshall Eubanks wrote:
>but  meeting consensus can have a big influence on mailing list
>consensus.)

Yes.

>The result of what we are doing here will I think inevitably at some
>point change the answer to no. And, after that, you are not having a
>WG meeting, just some sort of seminar.

If we exclude WG adoption of drafts, how many decisions are taken (to 
be confirmed on the list) in a meeting?

  OAUTH     5
  MANET     4
  TLS       3
  KITTEN    2
  DHC       2
  P2PSIP    2
  SIPCORE   2
  XRBLOCK   2
  WEBSEC    1
  ANTITRUST 1
  INSIPID   1
  KERBEROS  1
  ISIS      1
  JOSE      0
  IPSECME   0
  PKIX      0
  MILE      0
  NEA       0
  ABFAB     0
  DANE      0

The metrics used do not paint a true picture of the sessions.

Regards,
-sm


From Ted.Lemon@nominum.com  Mon Apr  2 07:32:48 2012
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 3A1D221F857D; Mon,  2 Apr 2012 07:32:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.74
X-Spam-Level: 
X-Spam-Status: No, score=-104.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, 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 NF0i6qdJbR29; Mon,  2 Apr 2012 07:32:47 -0700 (PDT)
Received: from exprod7og119.obsmtp.com (exprod7og119.obsmtp.com [64.18.2.16]) by ietfa.amsl.com (Postfix) with ESMTP id 372C821F856C; Mon,  2 Apr 2012 07:32:47 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob119.postini.com ([64.18.6.12]) with SMTP ID DSNKT3m4ju3e2hw6RUF/lvP6ThJ8ahKcrmSt@postini.com; Mon, 02 Apr 2012 07:32:47 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 3DF171B80FE; Mon,  2 Apr 2012 07:32:46 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 2E063190064; Mon,  2 Apr 2012 07:32:46 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0247.003; Mon, 2 Apr 2012 07:32:46 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: SM <sm@resistor.net>, John C Klensin <john-ietf@jck.com>
Subject: RE: [vmeet] [BOFCHAIRS]  Remote participation
Thread-Topic: [vmeet] [BOFCHAIRS]  Remote participation
Thread-Index: AQHNDJwyGhLUxvnL90OauzYccLnpHZaDunGngAD5eoCAAuyzDw==
Date: Mon, 2 Apr 2012 14:32:45 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307472D5DF3@mbx-01.win.nominum.com>
References: <4F729503.5080003@gmail.com> <0BBF44E367CFEE54C9AC516D@PST.JCK.COM> <6.2.5.6.2.20120328035236.0c7dc648@elandnews.com> <CAJNg7VLR0LVW3MqKAeC=0O5_UuwAP69f_w1BuG+YnVedudg8qQ@mail.gmail.com> <24143_1332964425_q2SJriGr012797_6.2.5.6.2.20120328103857.0c1fb05 0@elandnews.com> <1332966135.4980.75.camel@minbar.fac.cs.cmu.edu> <25D805D4-16EA-4E3B-B37E-D67A058E1827@cs.columbia.edu> <C74241B313CA00C3A1D03E7F@PST.JCK.COM> <6.2.5.6.2.20120330090037.0901d0f0@elandnews.com> <A838D9E54AA2FBA66AC29F99@PST.JCK.COM> <6.2.5.6.2.20120330151904.0d747920@elandnews.com> <932A5044CE359AECF4537FC7@PST.JCK.COM>, <6.2.5.6.2.20120330234220.0d442ed0@elandnews.com>
In-Reply-To: <6.2.5.6.2.20120330234220.0d442ed0@elandnews.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>, "vmeet@ietf.org" <vmeet@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, 02 Apr 2012 14:32:48 -0000

> If we exclude WG adoption of drafts, how many decisions are taken (to
> be confirmed on the list) in a meeting?
> DHC       2
> The metrics used do not paint a true picture of the sessions.

In the case of DHC at least, the metrics are pretty accurate.   There was b=
arely time in the wg meeting to actually have any meaningful discussion abo=
ut anything, so each presentation wound up being "sales pitch, a few commen=
ts, chair interrupts for time, next steps, next presentation."   It wasn't =
really a good use of f2f meeting time, and I'd like to do it differently at=
 the next IETF, but I don't really know how, because there weren't a lot of=
 presentations that the working group shouldn't have heard, and we got one =
of the nice like 2.5h time slots.

From jhutz@cmu.edu  Mon Apr  2 07:58:52 2012
Return-Path: <jhutz@cmu.edu>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9437221F85E7; Mon,  2 Apr 2012 07:58:52 -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 PPx8j6mQGQwJ; Mon,  2 Apr 2012 07:58:51 -0700 (PDT)
Received: from smtp02.srv.cs.cmu.edu (SMTP02.SRV.CS.CMU.EDU [128.2.217.197]) by ietfa.amsl.com (Postfix) with ESMTP id 2B74D21F8510; Mon,  2 Apr 2012 07:58:51 -0700 (PDT)
Received: from [192.168.202.157] (pool-98-111-232-78.pitbpa.fios.verizon.net [98.111.232.78]) (authenticated bits=0) by smtp02.srv.cs.cmu.edu (8.13.6/8.13.6) with ESMTP id q32Ewm83022227 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 2 Apr 2012 10:58:49 -0400 (EDT)
Subject: RE: [vmeet] [BOFCHAIRS]  Remote participation
From: Jeffrey Hutzelman <jhutz@cmu.edu>
To: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <18155_1333377170_q32EWngq023020_8D23D4052ABE7A4490E77B1A012B6307472D5DF3@mbx-01.win.nominum.com>
References: <4F729503.5080003@gmail.com> <0BBF44E367CFEE54C9AC516D@PST.JCK.COM> <6.2.5.6.2.20120328035236.0c7dc648@elandnews.com> <CAJNg7VLR0LVW3MqKAeC=0O5_UuwAP69f_w1BuG+YnVedudg8qQ@mail.gmail.com> <24143_1332964425_q2SJriGr012797_6.2.5.6.2.20120328103857.0c1fb05 0@elandnews.com> <1332966135.4980.75.camel@minbar.fac.cs.cmu.edu> <25D805D4-16EA-4E3B-B37E-D67A058E1827@cs.columbia.edu> <C74241B313CA00C3A1D03E7F@PST.JCK.COM> <6.2.5.6.2.20120330090037.0901d0f0@elandnews.com> <A838D9E54AA2FBA66AC29F99@PST.JCK.COM> <6.2.5.6.2.20120330151904.0d747920@elandnews.com> <932A5044CE359AECF4537FC7@PST.JCK.COM> , <6.2.5.6.2.20120330234220.0d442ed0@elandnews.com> <18155_1333377170_q32EWngq023020_8D23D4052ABE7A4490E77B1A012B6307472D5DF3@mbx-01.win.nominum.com>
Content-Type: text/plain; charset="UTF-8"
Date: Mon, 02 Apr 2012 10:58:47 -0400
Message-ID: <1333378727.12176.60.camel@destiny.pc.cs.cmu.edu>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.3 
Content-Transfer-Encoding: 7bit
X-Scanned-By: mimedefang-cmuscs on 128.2.217.197
Cc: SM <sm@resistor.net>, "vmeet@ietf.org" <vmeet@ietf.org>, "wgchairs@ietf.org" <wgchairs@ietf.org>, jhutz@cmu.edu
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Apr 2012 14:58:52 -0000

On Mon, 2012-04-02 at 14:32 +0000, Ted Lemon wrote:
> > If we exclude WG adoption of drafts, how many decisions are taken (to
> > be confirmed on the list) in a meeting?
> > DHC       2
> > The metrics used do not paint a true picture of the sessions.
> 
> In the case of DHC at least, the metrics are pretty accurate.   There
>  was barely time in the wg meeting to actually have any meaningful
>  discussion about anything, so each presentation wound up being "sales
>  pitch, a few comments, chair interrupts for time, next steps, next
>  presentation."   It wasn't really a good use of f2f meeting time, and
>  I'd like to do it differently at the next IETF, but I don't really
>  know how, because there weren't a lot of presentations that the
>  working group shouldn't have heard, and we got one of the nice like
>  2.5h time slots.

Maybe you're not being conservative enough about what is a presentation
the working group should hear.  I generally try to avoid "presentations"
at all, reserving meeting time for things that actually require
face-to-face time in order to get work done and move things forward.  I
regularly turn down requests for meeting time to present some new work
or proposed work to the WG that hasn't been discussed on the meeting
list.

We still don't take a lot of decisions in any one meeting, but the ones
we do are often things for which discussion took a fair amount of time.


I don't claim to follow this principle perfectly, but it is something I
try to do, because I hate sitting in a meeting with a full agenda and
not getting work done because someone is droning on about something we
could have learned by reading a draft or having a discussion on the
mailing list.

-- Jeff


From john-ietf@jck.com  Mon Apr  2 08:36:37 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E45D921F84D7; Mon,  2 Apr 2012 08:36:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.74
X-Spam-Level: 
X-Spam-Status: No, score=-100.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oJ-b-5IOdmBW; Mon,  2 Apr 2012 08:36:37 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 3EA4321F8523; Mon,  2 Apr 2012 08:36:37 -0700 (PDT)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SEjE5-000Jnf-Bd; Mon, 02 Apr 2012 11:31:25 -0400
Date: Mon, 02 Apr 2012 11:36:22 -0400
From: John C Klensin <john-ietf@jck.com>
To: Ted Lemon <Ted.Lemon@nominum.com>, SM <sm@resistor.net>
Subject: RE: [vmeet] [BOFCHAIRS]  Remote participation
Message-ID: <007FA6E7E439668061E0A1E2@PST.JCK.COM>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307472D5DF3@mbx-01.win.nominum.com>
References: <4F729503.5080003@gmail.com> <0BBF44E367CFEE54C9AC516D@PST.JCK.COM> <6.2.5.6.2.20120328035236.0c7dc648@elandnews.com> <CAJNg7VLR0LVW3MqKAeC=0O5_UuwAP69f_w1BuG+YnVedudg8qQ@mail.gmail.com> <24143_1332964425_q2SJriGr012797_6.2.5.6.2.20120328103857.0c1fb05	0@elandnews.com> <1332966135.4980.75.camel@minbar.fac.cs.cmu.edu> <25D805D4-16EA-4E3B-B37E-D67A058E1827@cs.columbia.edu> <C74241B313CA00C3A1D03E7F@PST.JCK.COM> <6.2.5.6.2.20120330090037.0901d0f0@elandnews.com> <A838D9E54AA2FBA66AC29F99@PST.JCK.COM> <6.2.5.6.2.20120330151904.0d747920@elandnews.com> <932A5044CE359AECF4537FC7@PST.JCK.COM> ,<6.2.5.6.2.20120330234220.0d442ed0@elandnews.com> <8D23D4052ABE7A4490E77B1A012B6307472D5DF3@mbx-01.win.nominum.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: wgchairs@ietf.org, vmeet@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, 02 Apr 2012 15:36:38 -0000

--On Monday, April 02, 2012 14:32 +0000 Ted Lemon
<Ted.Lemon@nominum.com> wrote:

> In the case of DHC at least, the metrics are pretty accurate.
> There was barely time in the wg meeting to actually have any
> meaningful discussion about anything, so each presentation
> wound up being "sales pitch, a few comments, chair interrupts
> for time, next steps, next presentation."   It wasn't really a
> good use of f2f meeting time, and I'd like to do it
> differently at the next IETF, but I don't really know how,
> because there weren't a lot of presentations that the working
> group shouldn't have heard, and we got one of the nice like
> 2.5h time slots.

Ted,

When the pressure for more and more meeting time is considered
in the light of my experience of the last week, I've started
wondering whether it is time to move toward a fundamental
change.  Suppose that, instead of having presentations at the
IETF meetings, we did the following:

(i) Encourage presentations to be prepared as a sequence of
slides accompanied by either written narrative or audio (or
possibly video) and made available with a cutoff not later that
the cutoff for new I-Ds and ideally earlier.   If people then
started discussing them on the relevant WG mailing lists, that
would strengthen the case for (ii) below.   

Note that recorded audio or video presentations have added
advantages: People who need a little extra time to understand
them could take that time (or back up and replay if needed),
early availability of the slides would be guaranteed, and asking
questions on mailing lists is both open-ended (no need to limit
the microphone line), more useful for anyone who has trouble
understanding English in real time, and more accessible for
anyone who can't easily translate their questions into English
in real time.  Those who hadn't really understood the relevant
I-Ds could view the presentation, read the I-D, and view the
presentation again.  And so on.

(ii) With presentations (all parts of each one, not just the
slides) available weeks before an actual IETF meeting, we would
ask the presenters to demonstrate to WG Chairs that their
subject matter (perhaps with a one or two minute review of
context) would benefit from f2f discussion time.  The strongest
demonstration would obviously be mailing list discussion after
people had looked at the presentation.

Obviously that would help the remote folks as well because
presentations could be studied at leisure and questions queued
up for f2f discussions before the relevant session even started.
Having someone who would be spending time making a presentation
under today's model instead start by responding to a series of
prepared audience questions (from both the on-site and remote
audiences) might also be a much better use of WG time.

There are lots of details associated with that sort of approach
that I haven't even started to think about, but, if it worked, I
think it could dramatically improve our overall productivity,
reverse the trend toward more presentations and work at meetings
in preference to real work on mailing lists, and reduce pressure
on meeting slots (WGs who have nothing to actually discuss cold
be denied f2f session time). WG Chairs would need discretion to
give time to things that they were confident were in the
critical path and there might need to be a fast-track appeal
procedure when presentation time was denied.   

If we could get it into our collective heads that audio or video
presentations with pre-distributed slides might actually be more
effective, it might help in a lot of ways.   Conversely, if
people needed to show that they were going to be in front of the
room to get permission to travel to IETF, it would be, IMO, far
more helpful to all concerned to have that role be "lead
discussion of presentation and I-D" rather than "give
presentation".

best,
   john


From tony@att.com  Mon Apr  2 08:41:56 2012
Return-Path: <tony@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 43FA221F85C0; Mon,  2 Apr 2012 08:41:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.953
X-Spam-Level: 
X-Spam-Status: No, score=-103.953 tagged_above=-999 required=5 tests=[AWL=-2.647, BAYES_00=-2.599, HTML_MESSAGE=0.001, MISSING_HEADERS=1.292, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MlprxmX7+YwU; Mon,  2 Apr 2012 08:41:55 -0700 (PDT)
Received: from nbfkord-smmo05.seg.att.com (nbfkord-smmo05.seg.att.com [209.65.160.92]) by ietfa.amsl.com (Postfix) with ESMTP id 3738521F85C6; Mon,  2 Apr 2012 08:41:55 -0700 (PDT)
Received: from unknown [144.160.20.145] (EHLO mlpd192.enaf.sfdc.sbc.com) by nbfkord-smmo05.seg.att.com(mxl_mta-6.11.0-8) over TLS secured channel with ESMTP id 2c8c97f4.0.291359.00-408.791375.nbfkord-smmo05.seg.att.com (envelope-from <tony@att.com>);  Mon, 02 Apr 2012 15:41:55 +0000 (UTC)
X-MXL-Hash: 4f79c8c35297d863-80f3a5c57ce9e6c86c499db56b91886c216bf08a
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q32Ffslq013444; Mon, 2 Apr 2012 11:41:54 -0400
Received: from sflint01.pst.cso.att.com (sflint01.pst.cso.att.com [144.154.234.228]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q32Ffnkr013385 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 2 Apr 2012 11:41:50 -0400
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by sflint01.pst.cso.att.com (RSA Interceptor); Mon, 2 Apr 2012 11:41:26 -0400
Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id q32FfQbQ024793; Mon, 2 Apr 2012 11:41:26 -0400
Received: from dns.maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id q32FfNxQ024532; Mon, 2 Apr 2012 11:41:23 -0400
Received: from [135.70.232.128] (vpn-135-70-232-128.vpn.east.att.com[135.70.232.128]) by maillennium.att.com (mailgw1) with ESMTP id <20120402153830gw1004ornoe> (Authid: tony); Mon, 2 Apr 2012 15:38:31 +0000
X-Originating-IP: [135.70.232.128]
Message-ID: <4F79C8A1.30102@att.com>
Date: Mon, 02 Apr 2012 11:41:21 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
Subject: Re: [vmeet] Etherpad deployment for this meeting
References: <4EBA594C.1060406@levkowetz.com> <4F69CC24.1020509@labn.net>	<4F6FA690.4080601@levkowetz.com> <4F76C0F7.1000308@viagenie.ca> <005270DF49C9185F858E16A7@PST.JCK.COM>
In-Reply-To: <005270DF49C9185F858E16A7@PST.JCK.COM>
Content-Type: multipart/alternative; boundary="------------080700010209010602010200"
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-RSA-Action: allow
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <tony@att.com>
X-SOURCE-IP: [144.160.20.145]
X-AnalysisOut: [v=1.0 c=1 a=hZ3_VFEmleMA:10 a=vnNYxAp2wzwA:10 a=TYh4pNH1tl]
X-AnalysisOut: [oA:10 a=ofMgfj31e3cA:10 a=BLceEmwcHowA:10 a=ZRNLZ4dFUbCvG8]
X-AnalysisOut: [UMqPvVAA==:17 a=gus07sIQRV9wWdoJIJEA:9 a=E3lFtT4FgegLOiWUn]
X-AnalysisOut: [MkA:7 a=wPNLvfGTeEIA:10 a=9NGZVl_YAAAA:8 a=6ki53Eo8-fCxNiE]
X-AnalysisOut: [0O8sA:9 a=uhCqVVRg4TOrxPz8OKoA:7 a=_W_S_7VecoQA:10]
Cc: wgchairs@ietf.org, vmeet@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, 02 Apr 2012 15:41:56 -0000

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

Even as a local participant, I found the etherpad scrolling issue 
annoying as well.

Another annoying issue is that the current implementation doesn't have 
the horsepower to handle large numbers of people looking at it 
simultaneously.

     Tony Hansen

On 3/31/2012 8:57 AM, John C Klensin wrote:
> Let me add two things from the perspective of the remote
> participant.
>
> 	- I had to manually scroll the window after every lines
> 	that were typed at the meeting.   Attempts to work
> 	around that by having the minute taker insert a "this is
> 	the bottom line" (or equivalent) line and then type
> 	above it didn't help consistently.   Minor annoyance if
> 	one is trying to track only the Etherpad but, if one
> 	needs to also track a Jabber room while paging through a
> 	slide deck, the behavior becomes enough of a problem to
> 	make remote viewing of the Etherpad much less useful.

--------------080700010209010602010200
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">
    <link href="chrome://translator/skin/floatingPanel.css"
      type="text/css" rel="stylesheet">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Even as a local participant, I found the etherpad scrolling issue
    annoying as well.<br>
    <br>
    Another annoying issue is that the current implementation doesn't
    have the horsepower to handle large numbers of people looking at it
    simultaneously.<br>
    <br>
    &nbsp;&nbsp;&nbsp; Tony Hansen<br>
    <br>
    On 3/31/2012 8:57 AM, John C Klensin wrote:
    <blockquote cite="mid:005270DF49C9185F858E16A7@PST.JCK.COM"
      type="cite">
      <pre wrap="">Let me add two things from the perspective of the remote
participant.

	- I had to manually scroll the window after every lines
	that were typed at the meeting.   Attempts to work
	around that by having the minute taker insert a "this is
	the bottom line" (or equivalent) line and then type
	above it didn't help consistently.   Minor annoyance if
	one is trying to track only the Etherpad but, if one
	needs to also track a Jabber room while paging through a
	slide deck, the behavior becomes enough of a problem to
	make remote viewing of the Etherpad much less useful.
</pre>
    </blockquote>
    <div style="bottom: auto; left: 599px; right: auto; top: 71px;
      display: none;" class="translator-theme-default"
      id="translator-floating-panel">
      <div title="Click to translate"
        id="translator-floating-panel-button"></div>
    </div>
  </body>
</html>

--------------080700010209010602010200--

From stephen.farrell@cs.tcd.ie  Mon Apr  2 08:47:05 2012
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C7A521F8581; Mon,  2 Apr 2012 08:47:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9ze4VRsrxWJq; Mon,  2 Apr 2012 08:47:04 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 5F02821F857F; Mon,  2 Apr 2012 08:47:04 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 7DD07171C05; Mon,  2 Apr 2012 16:47:03 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1333381623; bh=VhNqw6zFVol3Ft wLixjYKFg8Mmn0MsV57qbsGUJlZ38=; b=ftPfHNXgh/htY4fxpEnN0IvgotRjqf W3P361d7yJZkp4SOAa8Mvi2Ht0Z2HwISWoK9j4JvkS6Of4J6m5d/7XKrV88yiEiZ 2L1oq7tYsT1fGNfxpu/ApwXOFkAKwSAux76zgAQR2L7t6JHeXi+dUpqL7afkDDBx lRSPGyelnS8CjJvSjb8ly6RmP4yVayrtum6EiNP46Uht3yy9CAMd0V9ZOqAeQgAw Nc20vFzwrowMy/8F26R7Gqeu7/DFpr80O6ELN6SjL7EbMuY+hcNgH1To3R9jSKkG P2kTjDedjMdUkv6lkP7rFMWbBt7OKUUzMWdm53nMx6JlYIPR7OxIx8Hw==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id x2JAgc+menID; Mon,  2 Apr 2012 16:47:03 +0100 (IST)
Received: from [IPv6:2001:770:10:203:a288:b4ff:fe9c:bc5c] (unknown [IPv6:2001:770:10:203:a288:b4ff:fe9c:bc5c]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 25C2D171BFF; Mon,  2 Apr 2012 16:47:02 +0100 (IST)
Message-ID: <4F79C9ED.90102@cs.tcd.ie>
Date: Mon, 02 Apr 2012 16:46:53 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Tony Hansen <tony@att.com>
Subject: Re: [vmeet] Etherpad deployment for this meeting
References: <4EBA594C.1060406@levkowetz.com> <4F69CC24.1020509@labn.net>	<4F6FA690.4080601@levkowetz.com> <4F76C0F7.1000308@viagenie.ca> <005270DF49C9185F858E16A7@PST.JCK.COM> <4F79C8A1.30102@att.com>
In-Reply-To: <4F79C8A1.30102@att.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: wgchairs@ietf.org, vmeet@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, 02 Apr 2012 15:47:05 -0000

I mailed tools-discuss to suggest they setup a readonly version
of the etherpad content on a webpage, same as we have for the
jabber logs. So, its on their list of suggestions received for
nice-to-have things. No idea how easy/hard that might be.

S

On 04/02/2012 04:41 PM, Tony Hansen wrote:
> Even as a local participant, I found the etherpad scrolling issue
> annoying as well.
>
> Another annoying issue is that the current implementation doesn't have
> the horsepower to handle large numbers of people looking at it
> simultaneously.
>
> Tony Hansen
>
> On 3/31/2012 8:57 AM, John C Klensin wrote:
>> Let me add two things from the perspective of the remote
>> participant.
>>
>> - I had to manually scroll the window after every lines
>> that were typed at the meeting. Attempts to work
>> around that by having the minute taker insert a "this is
>> the bottom line" (or equivalent) line and then type
>> above it didn't help consistently. Minor annoyance if
>> one is trying to track only the Etherpad but, if one
>> needs to also track a Jabber room while paging through a
>> slide deck, the behavior becomes enough of a problem to
>> make remote viewing of the Etherpad much less useful.
>

From john-ietf@jck.com  Mon Apr  2 09:16:28 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AB4C21F84CF; Mon,  2 Apr 2012 09:16:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.669
X-Spam-Level: 
X-Spam-Status: No, score=-101.669 tagged_above=-999 required=5 tests=[AWL=0.930, 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 Ark0dmnrtOUL; Mon,  2 Apr 2012 09:16:27 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id A534921F84CD; Mon,  2 Apr 2012 09:16:27 -0700 (PDT)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SEjqm-000Jrv-7s; Mon, 02 Apr 2012 12:11:24 -0400
Date: Mon, 02 Apr 2012 12:16:20 -0400
From: John C Klensin <john-ietf@jck.com>
To: Tony Hansen <tony@att.com>
Subject: Re: [vmeet] Etherpad deployment for this meeting
Message-ID: <E9F6C36F1368001E8122A0E2@PST.JCK.COM>
In-Reply-To: <4F79C8A1.30102@att.com>
References: <4EBA594C.1060406@levkowetz.com> <4F69CC24.1020509@labn.net>	<4F6FA690.4080601@levkowetz.com> <4F76C0F7.1000308@viagenie.ca> <005270DF49C9185F858E16A7@PST.JCK.COM> <4F79C8A1.30102@att.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: wgchairs@ietf.org, vmeet@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, 02 Apr 2012 16:16:28 -0000

--On Monday, April 02, 2012 11:41 -0400 Tony Hansen
<tony@att.com> wrote:

> Even as a local participant, I found the etherpad scrolling
> issue annoying as well.
> 
> Another annoying issue is that the current implementation
> doesn't have the horsepower to handle large numbers of people
> looking at it simultaneously.

That hadn't occurred to me as a cause, but it might explain
several of the problems I was encountering.  It might be that
Etherpad, at least at present, is fine for a handful of people
working on minutes but that we should go back to Jabber to help
in-room and remote folks follow the meeting ... at least until
Etherpad can be improved somewhat and made hugely more robust.

    john




> On 3/31/2012 8:57 AM, John C Klensin wrote:
>> Let me add two things from the perspective of the remote
>> participant.
>> 
>> 	- I had to manually scroll the window after every lines
>> 	that were typed at the meeting.   Attempts to work
>> 	around that by having the minute taker insert a "this is
>> 	the bottom line" (or equivalent) line and then type
>> 	above it didn't help consistently.   Minor annoyance if
>> 	one is trying to track only the Etherpad but, if one
>> 	needs to also track a Jabber room while paging through a
>> 	slide deck, the behavior becomes enough of a problem to
>> 	make remote viewing of the Etherpad much less useful.





From john-ietf@jck.com  Mon Apr  2 09:17:06 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6D6721F851B; Mon,  2 Apr 2012 09:17:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.669
X-Spam-Level: 
X-Spam-Status: No, score=-101.669 tagged_above=-999 required=5 tests=[AWL=0.930, 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 FeVd+1KXXHho; Mon,  2 Apr 2012 09:17:06 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id C217721F8663; Mon,  2 Apr 2012 09:17:05 -0700 (PDT)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SEjrI-000Js3-J5; Mon, 02 Apr 2012 12:11:56 -0400
Date: Mon, 02 Apr 2012 12:16:53 -0400
From: John C Klensin <john-ietf@jck.com>
To: Tony Hansen <tony@att.com>
Subject: Re: [vmeet] Etherpad deployment for this meeting
Message-ID: <70B9742B9FDE9F00880B53EC@PST.JCK.COM>
In-Reply-To: <4F79C8A1.30102@att.com>
References: <4EBA594C.1060406@levkowetz.com> <4F69CC24.1020509@labn.net>	<4F6FA690.4080601@levkowetz.com> <4F76C0F7.1000308@viagenie.ca> <005270DF49C9185F858E16A7@PST.JCK.COM> <4F79C8A1.30102@att.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: wgchairs@ietf.org, vmeet@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, 02 Apr 2012 16:17:06 -0000

--On Monday, April 02, 2012 11:41 -0400 Tony Hansen
<tony@att.com> wrote:

> Even as a local participant, I found the etherpad scrolling
> issue annoying as well.
> 
> Another annoying issue is that the current implementation
> doesn't have the horsepower to handle large numbers of people
> looking at it simultaneously.

That hadn't occurred to me as a cause, but it might explain
several of the problems I was encountering.  It might be that
Etherpad, at least at present, is fine for a handful of people
working on minutes but that we should go back to Jabber to help
in-room and remote folks follow the meeting ... at least until
Etherpad can be improved somewhat and made hugely more robust.

    john




> On 3/31/2012 8:57 AM, John C Klensin wrote:
>> Let me add two things from the perspective of the remote
>> participant.
>> 
>> 	- I had to manually scroll the window after every lines
>> 	that were typed at the meeting.   Attempts to work
>> 	around that by having the minute taker insert a "this is
>> 	the bottom line" (or equivalent) line and then type
>> 	above it didn't help consistently.   Minor annoyance if
>> 	one is trying to track only the Etherpad but, if one
>> 	needs to also track a Jabber room while paging through a
>> 	slide deck, the behavior becomes enough of a problem to
>> 	make remote viewing of the Etherpad much less useful.





From joelja@bogus.com  Mon Apr  2 09:35:05 2012
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 3993521F85E7; Mon,  2 Apr 2012 09:35:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.37
X-Spam-Level: 
X-Spam-Status: No, score=-101.37 tagged_above=-999 required=5 tests=[AWL=1.230, 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 q+8kfyCDhhQJ; Mon,  2 Apr 2012 09:35:04 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id A539521F859E; Mon,  2 Apr 2012 09:35:04 -0700 (PDT)
Received: from Joels-MacBook-Pro.local (20.128.152.78.rev.sfr.net [78.152.128.20]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id q32GZ0bR011298 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Mon, 2 Apr 2012 16:35:02 GMT (envelope-from joelja@bogus.com)
Message-ID: <4F79D52E.70601@bogus.com>
Date: Mon, 02 Apr 2012 18:34:54 +0200
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120313 Thunderbird/11.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: [vmeet] [BOFCHAIRS]  Remote participation
References: <4F729503.5080003@gmail.com> <0BBF44E367CFEE54C9AC516D@PST.JCK.COM> <6.2.5.6.2.20120328035236.0c7dc648@elandnews.com> <CAJNg7VLR0LVW3MqKAeC=0O5_UuwAP69f_w1BuG+YnVedudg8qQ@mail.gmail.com> <24143_1332964425_q2SJriGr012797_6.2.5.6.2.20120328103857.0c1fb05	0@elandnews.com> <1332966135.4980.75.camel@minbar.fac.cs.cmu.edu> <25D805D4-16EA-4E3B-B37E-D67A058E1827@cs.columbia.edu> <C74241B313CA00C3A1D03E7F@PST.JCK.COM> <6.2.5.6.2.20120330090037.0901d0f0@elandnews.com> <A838D9E54AA2FBA66AC29F99@PST.JCK.COM> <6.2.5.6.2.20120330151904.0d747920@elandnews.com> <932A5044CE359AECF4537FC7@PST.JCK.COM> , <6.2.5.6.2.20120330234220.0d442ed0@elandnews.com> <8D23D4052ABE7A4490E77B1A012B6307472D5DF3@mbx-01.win.nominum.com> <007FA6E7E439668061E0A1E2@PST.JCK.COM>
In-Reply-To: <007FA6E7E439668061E0A1E2@PST.JCK.COM>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Mon, 02 Apr 2012 16:35:04 +0000 (UTC)
Cc: SM <sm@resistor.net>, vmeet@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, 02 Apr 2012 16:35:05 -0000

On 4/2/12 17:36 , John C Klensin wrote:
> 
> 
> --On Monday, April 02, 2012 14:32 +0000 Ted Lemon
> <Ted.Lemon@nominum.com> wrote:
> 
>> In the case of DHC at least, the metrics are pretty accurate.
>> There was barely time in the wg meeting to actually have any
>> meaningful discussion about anything, so each presentation
>> wound up being "sales pitch, a few comments, chair interrupts
>> for time, next steps, next presentation."   It wasn't really a
>> good use of f2f meeting time, and I'd like to do it
>> differently at the next IETF, but I don't really know how,
>> because there weren't a lot of presentations that the working
>> group shouldn't have heard, and we got one of the nice like
>> 2.5h time slots.
> 
> Ted,
> 
> When the pressure for more and more meeting time is considered
> in the light of my experience of the last week, I've started
> wondering whether it is time to move toward a fundamental
> change.  Suppose that, instead of having presentations at the
> IETF meetings, we did the following:
> 
> (i) Encourage presentations to be prepared as a sequence of
> slides accompanied by either written narrative or audio (or
> possibly video) and made available with a cutoff not later that
> the cutoff for new I-Ds and ideally earlier.   If people then
> started discussing them on the relevant WG mailing lists, that
> would strengthen the case for (ii) below.   

What we've been encouraged to do, e.g. use the presentation/meeting
cycle for the problems, not the material is fundamentally at odds with
this approach. We're there to have a discussion and the slides are there
to support that. they should not be there to imho to present the
contents of the draft. We had the mailing list and the drafts themselves
to form the framework for the meeting.

> If we could get it into our collective heads that audio or video
> presentations with pre-distributed slides might actually be more
> effective, it might help in a lot of ways. 

As a quite bad amateur ietf video producer, I'm going to go out on a
limb and say that a few hundred hours per meeting of cooked slides and
audio is not going to improve the productivity of the working groups
unless you're measuring that per byte.

> Conversely, if
> people needed to show that they were going to be in front of the
> room to get permission to travel to IETF, it would be, IMO, far
> more helpful to all concerned to have that role be "lead
> discussion of presentation and I-D" rather than "give
> presentation".

it should be today.

> best,
>    john
> 


From john-ietf@jck.com  Mon Apr  2 11:26:56 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D22521F8646; Mon,  2 Apr 2012 11:26:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.134
X-Spam-Level: 
X-Spam-Status: No, score=-102.134 tagged_above=-999 required=5 tests=[AWL=0.465, 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 HeAgebPzicoq; Mon,  2 Apr 2012 11:26:55 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 19D1421F862B; Mon,  2 Apr 2012 11:26:55 -0700 (PDT)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SElsz-000K16-Cj; Mon, 02 Apr 2012 14:21:49 -0400
Date: Mon, 02 Apr 2012 14:26:46 -0400
From: John C Klensin <john-ietf@jck.com>
To: Joel jaeggli <joelja@bogus.com>
Subject: Re: [vmeet] [BOFCHAIRS]  Remote participation
Message-ID: <A5F4819894B59B596920EA2F@PST.JCK.COM>
In-Reply-To: <4F79D52E.70601@bogus.com>
References: <4F729503.5080003@gmail.com> <0BBF44E367CFEE54C9AC516D@PST.JCK.COM> <6.2.5.6.2.20120328035236.0c7dc648@elandnews.com> <CAJNg7VLR0LVW3MqKAeC=0O5_UuwAP69f_w1BuG+YnVedudg8qQ@mail.gmail.com> <24143_1332964425_q2SJriGr012797_6.2.5.6.2.20120328103857.0c1fb05 0@elandnews.com> <1332966135.4980.75.camel@minbar.fac.cs.cmu.edu> <25D805D4-16EA-4E3B-B37E-D67A058E1827@cs.columbia.edu> <C74241B313CA00C3A1D03E7F@PST.JCK.COM> <6.2.5.6.2.20120330090037.0901d0f0@elandnews.com> <A838D9E54AA2FBA66AC29F99@PST.JCK.COM> <6.2.5.6.2.20120330151904.0d747920@elandnews.com> <932A5044CE359AECF4537FC7@PST.JCK.COM> ,<6.2.5.6.2.20120330234220.0d442ed0@elandnews.com> <8D23D4052ABE7A4490E77B1A012B6307472D5DF3@mbx-01.win.nominum.com> <007FA6E7E439668061E0A1E2@PST.JCK.COM> <4F79D52E.70601@bogus.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: SM <sm@resistor.net>, vmeet@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, 02 Apr 2012 18:26:56 -0000

--On Monday, April 02, 2012 18:34 +0200 Joel jaeggli
<joelja@bogus.com> wrote:

>...
>> (i) Encourage presentations to be prepared as a sequence of
>> slides accompanied by either written narrative or audio (or
>> possibly video) and made available with a cutoff not later
>> that the cutoff for new I-Ds and ideally earlier.   If people
>> then started discussing them on the relevant WG mailing
>> lists, that would strengthen the case for (ii) below.   
 
> What we've been encouraged to do, e.g. use the
> presentation/meeting cycle for the problems, not the material
> is fundamentally at odds with this approach. We're there to
> have a discussion and the slides are there to support that.
> they should not be there to imho to present the contents of
> the draft. We had the mailing list and the drafts themselves
> to form the framework for the meeting.

Joel, I apologize if I wasn't clear, but I was suggesting using
those previously-prepared presentations for online access at the
convenience of participants _before the IETF f2f meetings_ and
eliminating them from those meetings entirely.  If that is
"fundamentally at odds" with focusing the face time on problems
rather than presentations, I don't see how.

>> If we could get it into our collective heads that audio or
>> video presentations with pre-distributed slides might
>> actually be more effective, it might help in a lot of ways. 
> 
> As a quite bad amateur ietf video producer, I'm going to go
> out on a limb and say that a few hundred hours per meeting of
> cooked slides and audio is not going to improve the
> productivity of the working groups unless you're measuring
> that per byte.

And, again, I'm suggesting cutting the amount that appears
during the meeting, taking up meeting time, to nearly zero.

>> Conversely, if
>> people needed to show that they were going to be in front of
>> the room to get permission to travel to IETF, it would be,
>> IMO, far more helpful to all concerned to have that role be
>> "lead discussion of presentation and I-D" rather than "give
>> presentation".
> 
> it should be today.

Agreed.  But that isn't happening in presentation-heavy WGs.

   john



From pkyzivat@alum.mit.edu  Mon Apr  2 11:50:57 2012
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 CA17C21F86F2 for <wgchairs@ietfa.amsl.com>; Mon,  2 Apr 2012 11:50:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9m5bfo15IRt3 for <wgchairs@ietfa.amsl.com>; Mon,  2 Apr 2012 11:50:50 -0700 (PDT)
Received: from qmta04.westchester.pa.mail.comcast.net (qmta04.westchester.pa.mail.comcast.net [76.96.62.40]) by ietfa.amsl.com (Postfix) with ESMTP id 4B76621F86EF for <wgchairs@ietf.org>; Mon,  2 Apr 2012 11:50:50 -0700 (PDT)
Received: from omta23.westchester.pa.mail.comcast.net ([76.96.62.74]) by qmta04.westchester.pa.mail.comcast.net with comcast id t3x41i0041c6gX8546qqpg; Mon, 02 Apr 2012 18:50:50 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([24.62.229.5]) by omta23.westchester.pa.mail.comcast.net with comcast id t6qq1i00g07duvL3j6qqSs; Mon, 02 Apr 2012 18:50:50 +0000
Message-ID: <4F79F508.1070201@alum.mit.edu>
Date: Mon, 02 Apr 2012 14:50:48 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: [vmeet] [BOFCHAIRS]  Remote participation
References: <4F729503.5080003@gmail.com> <0BBF44E367CFEE54C9AC516D@PST.JCK.COM> <6.2.5.6.2.20120328035236.0c7dc648@elandnews.com> <CAJNg7VLR0LVW3MqKAeC=0O5_UuwAP69f_w1BuG+YnVedudg8qQ@mail.gmail.com> <24143_1332964425_q2SJriGr012797_6.2.5.6.2.20120328103857.0c1fb05 0@elandnews.com> <1332966135.4980.75.camel@minbar.fac.cs.cmu.edu> <25D805D4-16EA-4E3B-B37E-D67A058E1827@cs.columbia.edu> <C74241B313CA00C3A1D03E7F@PST.JCK.COM> <6.2.5.6.2.20120330090037.0901d0f0@elandnews.com> <A838D9E54AA2FBA66AC29F99@PST.JCK.COM> <6.2.5.6.2.20120330151904.0d747920@elandnews.com> <932A5044CE359AECF4537FC7@PST.JCK.COM> , <6.2.5.6.2.20120330234220.0d442ed0@elandnews.com> <8D23D4052ABE7A4490E77B1A012B6307472D5DF3@mbx-01.win.nominum.com> <007FA6E7E439668061E0A1E2@PST.JCK.COM> <4F79D52E.70601@bogus.com> <A5F4819894B59B596920EA2F@PST.JCK.COM>
In-Reply-To: <A5F4819894B59B596920EA2F@PST.JCK.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, 02 Apr 2012 18:50:57 -0000

On 4/2/12 2:26 PM, John C Klensin wrote:
>
> Joel, I apologize if I wasn't clear, but I was suggesting using
> those previously-prepared presentations for online access at the
> convenience of participants _before the IETF f2f meetings_ and
> eliminating them from those meetings entirely.  If that is
> "fundamentally at odds" with focusing the face time on problems
> rather than presentations, I don't see how.

John,

I don't know about you, but I have enough trouble getting ready for a 
meeting now, reading all the latest draft versions, ramped up email 
traffic, etc.

What I *don't* need during meeting prep is to watch a bunch of videos 
about each draft on the agenda!!! Perhaps the world has decided that 
people are now too illiterate to read and must watch TV instead, but I'm 
trying to avoid that where possible. IMO reading is much more efficient 
for most things.

Certainly there *are* some things where multimodal presentation is 
preferable, and that is what the meetings (regular and interim) are for.

	Thanks,
	Paul

From melinda.shore@gmail.com  Mon Apr  2 11:53:35 2012
Return-Path: <melinda.shore@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 B503F21F8589 for <wgchairs@ietfa.amsl.com>; Mon,  2 Apr 2012 11:53:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kprxn7+3ACMu for <wgchairs@ietfa.amsl.com>; Mon,  2 Apr 2012 11:53:35 -0700 (PDT)
Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by ietfa.amsl.com (Postfix) with ESMTP id 7979221F85A7 for <wgchairs@ietf.org>; Mon,  2 Apr 2012 11:53:34 -0700 (PDT)
Received: by dady13 with SMTP id y13so3617310dad.27 for <wgchairs@ietf.org>; Mon, 02 Apr 2012 11:53:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=TMIFYes0dBc3GlfA/jxvpakEYFDw9bRAnW0WeHZYUZs=; b=zhPiIdtTdG6nBBj+nME6MjX0kz0FFTMgOLKdp0fDv0r04Q53Flrrowo2adsovGv7nf YVc/QcycsJSWFT5rggp+R0/c9moMMQfm0MD18aum6TjY21/2siTs6OjsMYorxOYIqfRM QCO1jsFoAbnqYYA2UKJAwCwO14Co7mDj8QlVGXQMvhyYbSzjeu+JO5PYeMvjy8X4LUuF JOTiwaPXA1bXluVjGeLOMwMQL4blRvHPf0rd9OZ+0ezDPtfrGK2+Waw+gF/xBHbZvHaa oZPjUfOTCmwNGMZLxUYVTiDf4pTwcqf86LmRaFC0X6ZbwuCLm+oBmg/y23Jze4eNcBZ9 osjA==
Received: by 10.68.197.194 with SMTP id iw2mr23114540pbc.26.1333392814357; Mon, 02 Apr 2012 11:53:34 -0700 (PDT)
Received: from polypro.local (66-230-81-245-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.81.245]) by mx.google.com with ESMTPS id e7sm14545013pbs.21.2012.04.02.11.53.32 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 02 Apr 2012 11:53:33 -0700 (PDT)
Message-ID: <4F79F5AA.8080303@gmail.com>
Date: Mon, 02 Apr 2012 10:53:30 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.27) Gecko/20120216 Lightning/1.0b2 Thunderbird/3.1.19
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: [vmeet] [BOFCHAIRS]  Remote participation
References: <4F729503.5080003@gmail.com> <0BBF44E367CFEE54C9AC516D@PST.JCK.COM>	<6.2.5.6.2.20120328035236.0c7dc648@elandnews.com>	<CAJNg7VLR0LVW3MqKAeC=0O5_UuwAP69f_w1BuG+YnVedudg8qQ@mail.gmail.com>	<24143_1332964425_q2SJriGr012797_6.2.5.6.2.20120328103857.0c1fb05	0@elandnews.com>	<1332966135.4980.75.camel@minbar.fac.cs.cmu.edu>	<25D805D4-16EA-4E3B-B37E-D67A058E1827@cs.columbia.edu>	<C74241B313CA00C3A1D03E7F@PST.JCK.COM>	<6.2.5.6.2.20120330090037.0901d0f0@elandnews.com>	<A838D9E54AA2FBA66AC29F99@PST.JCK.COM>	<6.2.5.6.2.20120330151904.0d747920@elandnews.com>	<932A5044CE359AECF4537FC7@PST.JCK.COM> , <6.2.5.6.2.20120330234220.0d442ed0@elandnews.com>	<8D23D4052ABE7A4490E77B1A012B6307472D5DF3@mbx-01.win.nominum.com>	<007FA6E7E439668061E0A1E2@PST.JCK.COM> <4F79D52E.70601@bogus.com>
In-Reply-To: <4F79D52E.70601@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, 02 Apr 2012 18:53:35 -0000

On 4/2/12 8:34 AM, Joel jaeggli wrote:
> What we've been encouraged to do, e.g. use the presentation/meeting
> cycle for the problems, not the material is fundamentally at odds with
> this approach. We're there to have a discussion and the slides are there
> to support that. they should not be there to imho to present the
> contents of the draft. We had the mailing list and the drafts themselves
> to form the framework for the meeting.

Hear, hear.  This strikes me as a problem that can be addressed through
better working group chair training and not through technology.

Melinda

From jgs@bgp.nu  Mon Apr  2 11:53:38 2012
Return-Path: <jgs@bgp.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 BE69521F86F6 for <wgchairs@ietfa.amsl.com>; Mon,  2 Apr 2012 11:53:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.835
X-Spam-Level: 
X-Spam-Status: No, score=-100.835 tagged_above=-999 required=5 tests=[AWL=1.206, BAYES_00=-2.599, HELO_IS_SMALL6=0.556, 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 JpmJcT8kdCPD for <wgchairs@ietfa.amsl.com>; Mon,  2 Apr 2012 11:53:38 -0700 (PDT)
Received: from bgp.nu (bgp.nu [147.28.0.53]) by ietfa.amsl.com (Postfix) with ESMTP id 2D6AA21F867B for <wgchairs@ietf.org>; Mon,  2 Apr 2012 11:53:35 -0700 (PDT)
Received: from sa-nc-cs-85.static.jnpr.net (natint3.juniper.net [66.129.224.36]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by bgp.nu (Postfix) with ESMTP id 44D5766D357; Mon,  2 Apr 2012 14:53:34 -0400 (EDT)
Subject: Re: [vmeet] [BOFCHAIRS]  Remote participation
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: multipart/alternative; boundary="Apple-Mail=_CD2EE6D6-CC6F-4EF0-AE81-34D5C94DE082"
From: "John G. Scudder" <jgs@bgp.nu>
In-Reply-To: <4F79F508.1070201@alum.mit.edu>
Date: Mon, 2 Apr 2012 20:53:29 +0200
Message-Id: <E8441078-22EA-4868-8F48-CDF041D6442B@bgp.nu>
References: <4F729503.5080003@gmail.com> <0BBF44E367CFEE54C9AC516D@PST.JCK.COM> <6.2.5.6.2.20120328035236.0c7dc648@elandnews.com> <CAJNg7VLR0LVW3MqKAeC=0O5_UuwAP69f_w1BuG+YnVedudg8qQ@mail.gmail.com> <24143_1332964425_q2SJriGr012797_6.2.5.6.2.20120328103857.0c1fb05 0@elandnews.com> <1332966135.4980.75.camel@minbar.fac.cs.cmu.edu> <25D805D4-16EA-4E3B-B37E-D67A058E1827@cs.columbia.edu> <C74241B313CA00C3A1D03E7F@PST.JCK.COM> <6.2.5.6.2.20120330090037.0901d0f0@elandnews.com> <A838D9E54AA2FBA66AC29F99@PST.JCK.COM> <6.2.5.6.2.20120330151904.0d747920@elandnews.com> <932A5044CE359AECF4537FC7@PST.JCK.COM> , <6.2.5.6.2.20120330234220.0d442ed0@elandnews.com> <8D23D4052ABE7A4490E77B1A012B6307472D5DF3@mbx-01.win.nominum.com> <007FA6E7E439668061E0A1E2@PST.JCK.COM> <4F79D52E.70601@bogus.com> <A5F4819894B59B596920EA2F@PST.JCK.COM> <4F79F508.1070201@alum.mit.edu>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
X-Mailer: Apple Mail (2.1257)
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: John Scudder <jgs@juniper.net>
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Apr 2012 18:53:39 -0000

--Apple-Mail=_CD2EE6D6-CC6F-4EF0-AE81-34D5C94DE082
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

On Apr 2, 2012, at 8:50 PM, Paul Kyzivat wrote:
> I don't know about you, but I have enough trouble getting ready for a =
meeting now, reading all the latest draft versions, ramped up email =
traffic, etc.
>=20
> What I *don't* need during meeting prep is to watch a bunch of videos =
about each draft on the agenda!!!

+6.02e23.

--John=

--Apple-Mail=_CD2EE6D6-CC6F-4EF0-AE81-34D5C94DE082
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; =
"><div><div>On Apr 2, 2012, at 8:50 PM, Paul Kyzivat =
wrote:</div><blockquote type=3D"cite"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; font-family: Osaka; 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-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"font-family: monospace; ">I don't =
know about you, but I have enough trouble getting ready for a meeting =
now, reading all the latest draft versions, ramped up email traffic, =
etc.<br><br>What I *don't* need during meeting prep is to watch a bunch =
of videos about each draft on the =
agenda!!!</span></span></blockquote></div><br><div>+6.02e23.</div><div><br=
></div><div>--John</div></body></html>=

--Apple-Mail=_CD2EE6D6-CC6F-4EF0-AE81-34D5C94DE082--

From acmorton@att.com  Mon Apr  2 12:17:41 2012
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 4BC4B21F86E1 for <wgchairs@ietfa.amsl.com>; Mon,  2 Apr 2012 12:17:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.796
X-Spam-Level: 
X-Spam-Status: No, score=-103.796 tagged_above=-999 required=5 tests=[AWL=2.000, BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803, 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 E0yZ6CNaYkzy for <wgchairs@ietfa.amsl.com>; Mon,  2 Apr 2012 12:17:40 -0700 (PDT)
Received: from nbfkord-smmo04.seg.att.com (nbfkord-smmo04.seg.att.com [209.65.160.86]) by ietfa.amsl.com (Postfix) with ESMTP id 4B3CF21F86B9 for <wgchairs@ietf.org>; Mon,  2 Apr 2012 12:17:40 -0700 (PDT)
Received: from unknown [144.160.20.145] (EHLO mlpd192.enaf.sfdc.sbc.com) by nbfkord-smmo04.seg.att.com(mxl_mta-6.11.0-8) over TLS secured channel with ESMTP id 35bf97f4.0.394256.00-491.1088169.nbfkord-smmo04.seg.att.com (envelope-from <acmorton@att.com>);  Mon, 02 Apr 2012 19:17:40 +0000 (UTC)
X-MXL-Hash: 4f79fb5418d2f76c-9c56f1da58316df6b27a34204ca439a1ebccffdb
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q32JHcNG015430 for <wgchairs@ietf.org>; Mon, 2 Apr 2012 15:17:39 -0400
Received: from sflint01.pst.cso.att.com (sflint01.pst.cso.att.com [144.154.234.228]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q32JHWwq015392 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <wgchairs@ietf.org>; Mon, 2 Apr 2012 15:17:33 -0400
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by sflint01.pst.cso.att.com (RSA Interceptor) for <wgchairs@ietf.org>; Mon, 2 Apr 2012 15:17:14 -0400
Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id q32JHE18013394 for <wgchairs@ietf.org>; Mon, 2 Apr 2012 15:17:14 -0400
Received: from mailgw1.maillennium.att.com (mailgw1.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id q32JH5gQ011975 for <wgchairs@ietf.org>; Mon, 2 Apr 2012 15:17:05 -0400
Message-Id: <201204021917.q32JH5gQ011975@alpd052.aldc.att.com>
Received: from acmt.att.com (ds135-16-251-225.dhcps.ugn.att.com[135.16.251.225](misconfigured sender)) by maillennium.att.com (mailgw1) with SMTP id <20120402191413gw1004oroqe>; Mon, 2 Apr 2012 19:14:13 +0000
X-Originating-IP: [135.16.251.225]
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 02 Apr 2012 15:18:12 -0400
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, wgchairs@ietf.org
From: Al Morton <acmorton@att.com>
Subject: Re: [vmeet] [BOFCHAIRS]  Remote participation
In-Reply-To: <4F79F508.1070201@alum.mit.edu>
References: <4F729503.5080003@gmail.com> <0BBF44E367CFEE54C9AC516D@PST.JCK.COM> <6.2.5.6.2.20120328035236.0c7dc648@elandnews.com> <CAJNg7VLR0LVW3MqKAeC=0O5_UuwAP69f_w1BuG+YnVedudg8qQ@mail.gmail.com> <24143_1332964425_q2SJriGr012797_6.2.5.6.2.20120328103857.0c1fb05 0@elandnews.com> <1332966135.4980.75.camel@minbar.fac.cs.cmu.edu> <25D805D4-16EA-4E3B-B37E-D67A058E1827@cs.columbia.edu> <C74241B313CA00C3A1D03E7F@PST.JCK.COM> <6.2.5.6.2.20120330090037.0901d0f0@elandnews.com> <A838D9E54AA2FBA66AC29F99@PST.JCK.COM> <6.2.5.6.2.20120330151904.0d747920@elandnews.com> <932A5044CE359AECF4537FC7@PST.JCK.COM> <6.2.5.6.2.20120330234220.0d442ed0@elandnews.com> <8D23D4052ABE7A4490E77B1A012B6307472D5DF3@mbx-01.win.nominum.com> <007FA6E7E439668061E0A1E2@PST.JCK.COM> <4F79D52E.70601@bogus.com> <A5F4819894B59B596920EA2F@PST.JCK.COM> <4F79F508.1070201@alum.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-RSA-Action: allow
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <acmorton@att.com>
X-SOURCE-IP: [144.160.20.145]
X-AnalysisOut: [v=1.0 c=1 a=b3MHB_GQ4iAA:10 a=U07M8ygeJN8A:10 a=ofMgfj31e3]
X-AnalysisOut: [cA:10 a=BLceEmwcHowA:10 a=kj9zAlcOel0A:10 a=ZRNLZ4dFUbCvG8]
X-AnalysisOut: [UMqPvVAA==:17 a=Ln1kA_ZCAYL0tjkYn94A:9 a=CjuIK1q_8ugA:10]
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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, 02 Apr 2012 19:17:41 -0000

At 02:50 PM 4/2/2012, Paul Kyzivat wrote:
>...
>Certainly there *are* some things where multimodal presentation is 
>preferable, and that is what the meetings (regular and interim) are for.
Yes, the meetings are for *interaction*. During what might start-out
as a presentation we have the opportunity to customize the content by
asking questions, and chairs can guide speakers ("you need to skip to
the issues where discussion is required now, because time is short.")

make the meetings work, not more work,
Al


From john-ietf@jck.com  Mon Apr  2 12:37:06 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7B0321F86D6 for <wgchairs@ietfa.amsl.com>; Mon,  2 Apr 2012 12:37:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.289
X-Spam-Level: 
X-Spam-Status: No, score=-102.289 tagged_above=-999 required=5 tests=[AWL=0.310, 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 VhRvTn8LUBZJ for <wgchairs@ietfa.amsl.com>; Mon,  2 Apr 2012 12:37:05 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 1119B21F86D0 for <wgchairs@ietf.org>; Mon,  2 Apr 2012 12:37:05 -0700 (PDT)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SEmyw-000K78-Hr; Mon, 02 Apr 2012 15:32:02 -0400
Date: Mon, 02 Apr 2012 15:36:59 -0400
From: John C Klensin <john-ietf@jck.com>
To: Melinda Shore <melinda.shore@gmail.com>, wgchairs@ietf.org
Subject: Re: [vmeet] [BOFCHAIRS]  Remote participation
Message-ID: <A64AA15734D0ADEFDD8EED1F@PST.JCK.COM>
In-Reply-To: <4F79F5AA.8080303@gmail.com>
References: <4F729503.5080003@gmail.com> <0BBF44E367CFEE54C9AC516D@PST.JCK.COM> <6.2.5.6.2.20120328035236.0c7dc648@elandnews.com> <CAJNg7VLR0LVW3MqKAeC=0O5_UuwAP69f_w1BuG+YnVedudg8qQ@mail.gmail.com> <24143_1332964425_q2SJriGr012797_6.2.5.6.2.20120328103857.0c1fb05	0@elandnews.com> <1332966135.4980.75.camel@minbar.fac.cs.cmu.edu> <25D805D4-16EA-4E3B-B37E-D67A058E1827@cs.columbia.edu> <C74241B313CA00C3A1D03E7F@PST.JCK.COM> <6.2.5.6.2.20120330090037.0901d0f0@elandnews.com> <A838D9E54AA2FBA66AC29F99@PST.JCK.COM> <6.2.5.6.2.20120330151904.0d747920@elandnews.com> <932A5044CE359AECF4537FC7@PST.JCK.COM> ,	<6.2.5.6.2.20120330234220.0d442ed0@elandnews.com> <8D23D4052ABE7A4490E77B1A012B6307472D5DF3@mbx-01.win.nominum.com> <007FA6E7E439668061E0A1E2@PST.JCK.COM>	<4F79D52E.70601@bogus.com> <4F79F5AA.8080303@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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, 02 Apr 2012 19:37:06 -0000

--On Monday, April 02, 2012 10:53 -0800 Melinda Shore
<melinda.shore@gmail.com> wrote:

>...
> Hear, hear.  This strikes me as a problem that can be
> addressed through
> better working group chair training and not through technology.

I agree in principle.  But many WG chairs seem incapable of
controlling meetings and restricting the time allowed in
practice for long, sometimes incomprehensible, presentations
with little information content.   We've been saying "discussion
and interaction, not presentations" long enough and often enough
that I doubt those presentations are due to lack of training in
most cases.  

Now, I think that if WGs that couldn't get discussions focused
were shut down (if necessary over the objections of their
Chair(s)) or if ADs started denying meeting slots at IETF N+1 to
WGs who used the vast majority of time at IETF N for
presentations that did not generate discussion, learning would
set in rather quickly.  But a catalogue of how often either had
been done in, say, the last decade wouldn't be very long .

    john




From john-ietf@jck.com  Mon Apr  2 12:56:04 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABF6321F8723 for <wgchairs@ietfa.amsl.com>; Mon,  2 Apr 2012 12:56:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.367
X-Spam-Level: 
X-Spam-Status: No, score=-102.367 tagged_above=-999 required=5 tests=[AWL=0.232, 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 7PUSo6YAz8xC for <wgchairs@ietfa.amsl.com>; Mon,  2 Apr 2012 12:56:04 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id CA15321F872B for <wgchairs@ietf.org>; Mon,  2 Apr 2012 12:56:03 -0700 (PDT)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SEnHH-000K8J-HY; Mon, 02 Apr 2012 15:50:59 -0400
Date: Mon, 02 Apr 2012 15:55:56 -0400
From: John C Klensin <john-ietf@jck.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, wgchairs@ietf.org
Subject: Re: [vmeet] [BOFCHAIRS]  Remote participation
Message-ID: <2BD9BC086311C7B6FF0C35BE@PST.JCK.COM>
In-Reply-To: <4F79F508.1070201@alum.mit.edu>
References: <4F729503.5080003@gmail.com> <0BBF44E367CFEE54C9AC516D@PST.JCK.COM> <6.2.5.6.2.20120328035236.0c7dc648@elandnews.com> <CAJNg7VLR0LVW3MqKAeC=0O5_UuwAP69f_w1BuG+YnVedudg8qQ@mail.gmail.com> <24143_1332964425_q2SJriGr012797_6.2.5.6.2.20120328103857.0c1fb05	0@elandnews.com> <1332966135.4980.75.camel@minbar.fac.cs.cmu.edu> <25D805D4-16EA-4E3B-B37E-D67A058E1827@cs.columbia.edu> <C74241B313CA00C3A1D03E7F@PST.JCK.COM> <6.2.5.6.2.20120330090037.0901d0f0@elandnews.com> <A838D9E54AA2FBA66AC29F99@PST.JCK.COM> <6.2.5.6.2.20120330151904.0d747920@elandnews.com> <932A5044CE359AECF4537FC7@PST.JCK.COM> ,	<6.2.5.6.2.20120330234220.0d442ed0@elandnews.com> <8D23D4052ABE7A4490E77B1A012B6307472D5DF3@mbx-01.win.nominum.com> <007FA6E7E439668061E0A1E2@PST.JCK.COM> <4F79D52E.70601@bogus.com>	<A5F4819894B59B596920EA2F@PST.JCK.COM> <4F79F508.1070201@alum.mit.edu>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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, 02 Apr 2012 19:56:04 -0000

--On Monday, April 02, 2012 14:50 -0400 Paul Kyzivat
<pkyzivat@alum.mit.edu> wrote:

>...
> I don't know about you, but I have enough trouble getting
> ready for a meeting now, reading all the latest draft
> versions, ramped up email traffic, etc.
> 
> What I *don't* need during meeting prep is to watch a bunch of
> videos about each draft on the agenda!!! Perhaps the world has
> decided that people are now too illiterate to read and must
> watch TV instead, but I'm trying to avoid that where possible.
> IMO reading is much more efficient for most things.

Good answer.  I bet you even know what to do about that, if only
because you took a several year course in drinking from a fire
hose.  I'd assume you read the drafts and complain on the WG
list that you want to know if there is anything in the
presentations that isn't in the draft and, if so, what it is and
why it isn't in the draft(s).   Possibly you also do what a very
significant fraction of the community seems to do when they find
themselves sitting in a WG meeting facing a presentation that
just reprises parts of an I-D that you/they have read, namely go
read email or try to follow another WG in parallel.

I had really hoped it would be clear where I was going, but let
me be very explicit:

(i) I think there are multiple reasons why we keep getting more
and more requests for time at IETF, thereby pushing on evenings,
more of Friday, etc.  I think one of the major reasons among
that lot is that we are wasting a lot of the time that is
allocated... and I believe a presentation that is not directly
linked to, and focused on, discussion that the presenter and WG
leadership expect to be usefully occur during that session.

(ii) I think we should prefer that no new information show up in
presentations.  New organization of material, new summaries to
focus discussion or summaries of prior discussions, definitely.
But anything that could go into an I-D should go into an I-D.
That is just much better for the process as we claim it works.

(iii) If someone needs to prepare and provide a presentation to
justify their presence and existence at IETF, I think we should
arrange for them to do that without taking up meeting time (or
the time of WG participants who actually read drafts).  Videos
available well in advance might serve some of the same purpose
that "Poster Sessions" serve at many scientific meetings... and
that purpose is not to provide information that is critical to
understanding the mainstream presentations or discussions.  If
you, me, or 900 other people don't pay any attention to those
videos, the amount of critical-path information lost is likely
to be insignificant.

> Certainly there *are* some things where multimodal
> presentation is preferable, and that is what the meetings
> (regular and interim) are for.

Yep.

best,
   john



From stephen.farrell@cs.tcd.ie  Mon Apr  2 13:02:52 2012
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5AFD21F8572 for <wgchairs@ietfa.amsl.com>; Mon,  2 Apr 2012 13:02: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=[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 gj5wCYXpbaOd for <wgchairs@ietfa.amsl.com>; Mon,  2 Apr 2012 13:02:51 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id A2B3621F8565 for <wgchairs@ietf.org>; Mon,  2 Apr 2012 13:02:25 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id CC066171C06; Mon,  2 Apr 2012 21:02:23 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1333396943; bh=EkKwOXxpOrdpbf oMBBviiK4PuIja6AhvSJK6n35XNvE=; b=nvoxnQFA4EP80wPyJ/lboITlVPFxu4 WtqsAL6fMC6li8wPm1WDQYzTgsA+SLGOz7HLjHCXHtWFlQ9x1Fkdd/REJtjK0ixJ Zb0vKbdCEkYgc5IsMW/CgjxG+uE4XFJNK9/EiGtfOGkq2JI9FoymN03zOmSb+H8m 96lNcLjY+lOH3lCVA2SsdSi6jhzfAkWFepjQg4ifuT8NbEjWwofHHSQ5FVhlZZ+N 6kU12xqCbUTD6TtYJybNb9n4mx/85wGSetzFJE3qYMG6UD1u8CxwRY5JYZfd3StU 2KPcbR49w471LyBVivZ96Dezd90MtklHmjt56Thh5sJODQ4QZsf4jXew==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id U-BsAULyZ4Hk; Mon,  2 Apr 2012 21:02:23 +0100 (IST)
Received: from [10.87.48.8] (unknown [86.45.62.67]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 3F51B171C05; Mon,  2 Apr 2012 21:02:22 +0100 (IST)
Message-ID: <4F7A05CD.8030304@cs.tcd.ie>
Date: Mon, 02 Apr 2012 21:02:21 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: [vmeet] [BOFCHAIRS]  Remote participation
References: <4F729503.5080003@gmail.com> <0BBF44E367CFEE54C9AC516D@PST.JCK.COM> <6.2.5.6.2.20120328035236.0c7dc648@elandnews.com> <CAJNg7VLR0LVW3MqKAeC=0O5_UuwAP69f_w1BuG+YnVedudg8qQ@mail.gmail.com> <24143_1332964425_q2SJriGr012797_6.2.5.6.2.20120328103857.0c1fb05	0@elandnews.com> <1332966135.4980.75.camel@minbar.fac.cs.cmu.edu> <25D805D4-16EA-4E3B-B37E-D67A058E1827@cs.columbia.edu> <C74241B313CA00C3A1D03E7F@PST.JCK.COM> <6.2.5.6.2.20120330090037.0901d0f0@elandnews.com> <A838D9E54AA2FBA66AC29F99@PST.JCK.COM> <6.2.5.6.2.20120330151904.0d747920@elandnews.com> <932A5044CE359AECF4537FC7@PST.JCK.COM> , <6.2.5.6.2.20120330234220.0d442ed0@elandnews.com> <8D23D4052ABE7A4490E77B1A012B6307472D5DF3@mbx-01.win.nominum.com> <007FA6E7E439668061E0A1E2@PST.JCK.COM>	<4F79D52E.70601@bogus.com> <4F79F5AA.8080303@gmail.com> <A64AA15734D0ADEFDD8EED1F@PST.JCK.COM>
In-Reply-To: <A64AA15734D0ADEFDD8EED1F@PST.JCK.COM>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Apr 2012 20:02:52 -0000

On 04/02/2012 08:36 PM, John C Klensin wrote:
> I agree in principle.  But many WG chairs seem incapable of
> controlling meetings and restricting the time allowed in
> practice for long, sometimes incomprehensible, presentations
> with little information content.   We've been saying "discussion
> and interaction, not presentations" long enough and often enough
> that I doubt those presentations are due to lack of training in
> most cases.

As it happens, I don't recall being at any such WG session
in Paris. Could it be that this is mostly an ex-problem? If
not, then can someone point me at some WGs that did have this
problem at IETF-83? (On-list or off-list, whatever.)

S

From ajs@anvilwalrusden.com  Mon Apr  2 13:07:48 2012
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4835221F871E for <wgchairs@ietfa.amsl.com>; Mon,  2 Apr 2012 13:07:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TjbXTmNTuIUQ for <wgchairs@ietfa.amsl.com>; Mon,  2 Apr 2012 13:07:47 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id B95DD21F871D for <wgchairs@ietf.org>; Mon,  2 Apr 2012 13:07:47 -0700 (PDT)
Received: from mail.yitter.info (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 161C41ECB41D for <wgchairs@ietf.org>; Mon,  2 Apr 2012 20:07:47 +0000 (UTC)
Date: Mon, 2 Apr 2012 16:07:45 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: wgchairs@ietf.org
Subject: Re: [vmeet] [BOFCHAIRS]  Remote participation
Message-ID: <20120402200744.GC22789@mail.yitter.info>
References: <6.2.5.6.2.20120330090037.0901d0f0@elandnews.com> <A838D9E54AA2FBA66AC29F99@PST.JCK.COM> <6.2.5.6.2.20120330151904.0d747920@elandnews.com> <932A5044CE359AECF4537FC7@PST.JCK.COM> <6.2.5.6.2.20120330234220.0d442ed0@elandnews.com> <8D23D4052ABE7A4490E77B1A012B6307472D5DF3@mbx-01.win.nominum.com> <007FA6E7E439668061E0A1E2@PST.JCK.COM> <4F79D52E.70601@bogus.com> <4F79F5AA.8080303@gmail.com> <A64AA15734D0ADEFDD8EED1F@PST.JCK.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <A64AA15734D0ADEFDD8EED1F@PST.JCK.COM>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Apr 2012 20:07:48 -0000

On Mon, Apr 02, 2012 at 03:36:59PM -0400, John C Klensin wrote:

> Chair(s)) or if ADs started denying meeting slots at IETF N+1 to
> WGs who used the vast majority of time at IETF N for

If we're going to make ADs start to micromanage WGs (presumably in the
12 remaining spare minutes in the year they have), why not start with
something simpler?  For instance, "No WG gets more than 2.5 hours per
meeting, period, no exceptions" might focus the mind.  Pick some other
arbitrary time if you like.  The idea is that the scarcity of resource
will make time management more important; and that if the claim is,
"We really need this time anyway because of all the work we took
on," perhaps the response ought to be, "You should have taken less
work.  Reschedule some of it later.  People can't follow what you're
doing."

I have no idea whether this will work, and I am not really a fan of
yet more rules.  But one could make a compelling argument that the
IETF week is a shared resource, and it'd be a mistake to add another
track or stretch into Friday afternoons, since that makes everyone pay
for the management practices of some.  As a side benefit, it might
make remote participation work better too.

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From pkyzivat@alum.mit.edu  Mon Apr  2 13:23:38 2012
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 A337121F86A4 for <wgchairs@ietfa.amsl.com>; Mon,  2 Apr 2012 13:23:35 -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 oqvAo6Zbl1td for <wgchairs@ietfa.amsl.com>; Mon,  2 Apr 2012 13:23:35 -0700 (PDT)
Received: from qmta08.westchester.pa.mail.comcast.net (qmta08.westchester.pa.mail.comcast.net [76.96.62.80]) by ietfa.amsl.com (Postfix) with ESMTP id 9014721F86BA for <wgchairs@ietf.org>; Mon,  2 Apr 2012 13:23:33 -0700 (PDT)
Received: from omta19.westchester.pa.mail.comcast.net ([76.96.62.98]) by qmta08.westchester.pa.mail.comcast.net with comcast id t5Fk1i00527AodY588PaJ6; Mon, 02 Apr 2012 20:23:34 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([24.62.229.5]) by omta19.westchester.pa.mail.comcast.net with comcast id t8PZ1i02607duvL3f8PZlJ; Mon, 02 Apr 2012 20:23:33 +0000
Message-ID: <4F7A0AC4.8010806@alum.mit.edu>
Date: Mon, 02 Apr 2012 16:23:32 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: [vmeet] [BOFCHAIRS]  Remote participation
References: <4F729503.5080003@gmail.com> <0BBF44E367CFEE54C9AC516D@PST.JCK.COM> <6.2.5.6.2.20120328035236.0c7dc648@elandnews.com> <CAJNg7VLR0LVW3MqKAeC=0O5_UuwAP69f_w1BuG+YnVedudg8qQ@mail.gmail.com> <24143_1332964425_q2SJriGr012797_6.2.5.6.2.20120328103857.0c1fb05	0@elandnews.com> <1332966135.4980.75.camel@minbar.fac.cs.cmu.edu> <25D805D4-16EA-4E3B-B37E-D67A058E1827@cs.columbia.edu> <C74241B313CA00C3A1D03E7F@PST.JCK.COM> <6.2.5.6.2.20120330090037.0901d0f0@elandnews.com> <A838D9E54AA2FBA66AC29F99@PST.JCK.COM> <6.2.5.6.2.20120330151904.0d747920@elandnews.com> <932A5044CE359AECF4537FC7@PST.JCK.COM> , <6.2.5.6.2.20120330234220.0d442ed0@elandnews.com> <8D23D4052ABE7A4490E77B1A012B6307472D5DF3@mbx-01.win.nominum.com> <007FA6E7E439668061E0A1E2@PST.JCK.COM> <4F79D52E.70601@bogus.com>	<A5F4819894B59B596920EA2F@PST.JCK.COM> <4F79F508.1070201@alum.mit.edu> <2BD9BC086311C7B6FF0C35BE@PST.JCK.COM>
In-Reply-To: <2BD9BC086311C7B6FF0C35BE@PST.JCK.COM>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Apr 2012 20:23:38 -0000

Frankly, it perhaps doesn't matter if we get the meetings to use the 
meeting time more efficiently. I think the highest value things that 
meetings provide are:

1) provide an artificial, but compelling, periodic deadline for 
progressing drafts, and for others to catch up on the status of those 
drafts.

2) force the primary participants to set aside their day job and 
personal concerns for a week and focus almost exclusively on the ietf tasks

3) all get on a common time zone for a week, and facilitate informal 
"hallway" conversations.

The official agenda, and the resulting proceedings, provide the formal 
justification to employers for the above. As long as they are working 
well enough to accomplish that maybe they are doing well enough.

	Thanks,
	Paul

On 4/2/12 3:55 PM, John C Klensin wrote:
>
>
> --On Monday, April 02, 2012 14:50 -0400 Paul Kyzivat
> <pkyzivat@alum.mit.edu>  wrote:
>
>> ...
>> I don't know about you, but I have enough trouble getting
>> ready for a meeting now, reading all the latest draft
>> versions, ramped up email traffic, etc.
>>
>> What I *don't* need during meeting prep is to watch a bunch of
>> videos about each draft on the agenda!!! Perhaps the world has
>> decided that people are now too illiterate to read and must
>> watch TV instead, but I'm trying to avoid that where possible.
>> IMO reading is much more efficient for most things.
>
> Good answer.  I bet you even know what to do about that, if only
> because you took a several year course in drinking from a fire
> hose.  I'd assume you read the drafts and complain on the WG
> list that you want to know if there is anything in the
> presentations that isn't in the draft and, if so, what it is and
> why it isn't in the draft(s).   Possibly you also do what a very
> significant fraction of the community seems to do when they find
> themselves sitting in a WG meeting facing a presentation that
> just reprises parts of an I-D that you/they have read, namely go
> read email or try to follow another WG in parallel.
>
> I had really hoped it would be clear where I was going, but let
> me be very explicit:
>
> (i) I think there are multiple reasons why we keep getting more
> and more requests for time at IETF, thereby pushing on evenings,
> more of Friday, etc.  I think one of the major reasons among
> that lot is that we are wasting a lot of the time that is
> allocated... and I believe a presentation that is not directly
> linked to, and focused on, discussion that the presenter and WG
> leadership expect to be usefully occur during that session.
>
> (ii) I think we should prefer that no new information show up in
> presentations.  New organization of material, new summaries to
> focus discussion or summaries of prior discussions, definitely.
> But anything that could go into an I-D should go into an I-D.
> That is just much better for the process as we claim it works.
>
> (iii) If someone needs to prepare and provide a presentation to
> justify their presence and existence at IETF, I think we should
> arrange for them to do that without taking up meeting time (or
> the time of WG participants who actually read drafts).  Videos
> available well in advance might serve some of the same purpose
> that "Poster Sessions" serve at many scientific meetings... and
> that purpose is not to provide information that is critical to
> understanding the mainstream presentations or discussions.  If
> you, me, or 900 other people don't pay any attention to those
> videos, the amount of critical-path information lost is likely
> to be insignificant.
>
>> Certainly there *are* some things where multimodal
>> presentation is preferable, and that is what the meetings
>> (regular and interim) are for.
>
> Yep.
>
> best,
>     john
>
>
>


From joelja@gmail.com  Mon Apr  2 12:02:19 2012
Return-Path: <joelja@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 3A04021F84B6; Mon,  2 Apr 2012 12:02:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j5XN-XK+B9RU; Mon,  2 Apr 2012 12:02:18 -0700 (PDT)
Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by ietfa.amsl.com (Postfix) with ESMTP id A0F1E21F8525; Mon,  2 Apr 2012 12:02:18 -0700 (PDT)
Received: by dady13 with SMTP id y13so3629105dad.27 for <multiple recipients>; Mon, 02 Apr 2012 12:02:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=clnqHynTKRZ1Vhiwl6eIjlfJjfC/fSpOQCPOSLjCUYU=; b=fE1OjRejvhHnap1XIndsdKyvVrU7Ch2wLmpVjGUrFL3zz9tqp0JAgjv7W1PuHe55K+ 7qt6FcZ0B4wJ0W/7KhmHMVzEU+Wec8QP2QpDaPNPVnOVmZI9dTARlNbTv0vd0mvnEpBk Cjg86+vsaSSAAnZiP1RECYOj089GEPGOneHFw9oOrSUf8U5BtR7VC1yiFMfC4xD0YNlP a8ux3OOh7mKU8WC6g0dsonn8k0kdUcrXWY4IMwkFhxWE6VXEcDZdqG/ZzRIqenpV2NBq ZVrrdGE9B7EeMPAr1yGkbcuogUYFWI1xIkt68Ab13x339c7oS+UEIJS/YToTUuEe2Qsz tEkg==
Received: by 10.68.132.99 with SMTP id ot3mr22379188pbb.160.1333393338461; Mon, 02 Apr 2012 12:02:18 -0700 (PDT)
Received: from Joels-MacBook-Pro.local (20.128.152.78.rev.sfr.net. [78.152.128.20]) by mx.google.com with ESMTPS id t7sm5220929pbp.15.2012.04.02.12.02.15 (version=SSLv3 cipher=OTHER); Mon, 02 Apr 2012 12:02:17 -0700 (PDT)
Message-ID: <4F79F7B4.2010307@gmail.com>
Date: Mon, 02 Apr 2012 21:02:12 +0200
From: Joel Jaeggli <joelja@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120313 Thunderbird/11.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: [vmeet] [BOFCHAIRS]  Remote participation
References: <4F729503.5080003@gmail.com> <0BBF44E367CFEE54C9AC516D@PST.JCK.COM> <6.2.5.6.2.20120328035236.0c7dc648@elandnews.com> <CAJNg7VLR0LVW3MqKAeC=0O5_UuwAP69f_w1BuG+YnVedudg8qQ@mail.gmail.com> <24143_1332964425_q2SJriGr012797_6.2.5.6.2.20120328103857.0c1fb05 0@elandnews.com> <1332966135.4980.75.camel@minbar.fac.cs.cmu.edu> <25D805D4-16EA-4E3B-B37E-D67A058E1827@cs.columbia.edu> <C74241B313CA00C3A1D03E7F@PST.JCK.COM> <6.2.5.6.2.20120330090037.0901d0f0@elandnews.com> <A838D9E54AA2FBA66AC29F99@PST.JCK.COM> <6.2.5.6.2.20120330151904.0d747920@elandnews.com> <932A5044CE359AECF4537FC7@PST.JCK.COM> , <6.2.5.6.2.20120330234220.0d442ed0@elandnews.com> <8D23D4052ABE7A4490E77B1A012B6307472D5DF3@mbx-01.win.nominum.com> <007FA6E7E439668061E0A1E2@PST.JCK.COM> <4F79D52E.70601@bogus.com> <A5F4819894B59B596920EA2F@PST.JCK.COM>
In-Reply-To: <A5F4819894B59B596920EA2F@PST.JCK.COM>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 02 Apr 2012 14:28:10 -0700
Cc: wgchairs@ietf.org, vmeet@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, 02 Apr 2012 19:02:19 -0000

On 4/2/12 20:26 , John C Klensin wrote:
>>> Conversely, if
>>> people needed to show that they were going to be in front of
>>> the room to get permission to travel to IETF, it would be,
>>> IMO, far more helpful to all concerned to have that role be
>>> "lead discussion of presentation and I-D" rather than "give
>>> presentation".
>>
>> it should be today.
> 
> Agreed.  But that isn't happening in presentation-heavy WGs.

We got 4.5 hours of meeting during 83.  If we can do it but some other
wg's can't then no technological solution is likely needed.

>    john
> 
> 
> _______________________________________________
> NOTE WELL: This list operates according to
> http://mipassoc.org/dkim/ietf-list-rules.html.
> https://www.ietf.org/mailman/listinfo/vmeet


From sm@resistor.net  Mon Apr  2 12:29:09 2012
Return-Path: <sm@resistor.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 4586E21F86BE for <wgchairs@ietfa.amsl.com>; Mon,  2 Apr 2012 12:29:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.52
X-Spam-Level: 
X-Spam-Status: No, score=-101.52 tagged_above=-999 required=5 tests=[AWL=1.080, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1qL5jXQEc+Yt for <wgchairs@ietfa.amsl.com>; Mon,  2 Apr 2012 12:29:07 -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 B33B021F86E4 for <wgchairs@ietf.org>; Mon,  2 Apr 2012 12:29:07 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q32JT0sO003791; Mon, 2 Apr 2012 12:29:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1333394946; i=@resistor.net; bh=ryt9A6U8zc0HSgQlpR5VucRrfeRruN/iyq74nAmu4vE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=nfFzZWBy1jGhammcO9Yf4SuelunenvXnaS8u843gS88OBWxVlV6RlnWGMwDzjuRHT JnzmktxWdAurIGYQKMMqRGQWd70dnDoIDU6L9gA+fg6HFAEB7ppzqMadO5eQFjTjS4 LeV/FfimACnbeISm/VJgcK4TWDRli9/OWO39L2So=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1333394946; i=@resistor.net; bh=ryt9A6U8zc0HSgQlpR5VucRrfeRruN/iyq74nAmu4vE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=OQ+sSJTGyZSoqSZbGEid/bDqws/kRrpqsUKC5vzuPd4hP3Ma7FGCCianlot4kc/4F V56KDKoa5/n1inptG6MMKFiGRZol8NVq4/B22yz8b2ZCmFu/2FRGpxYKl8hAR2rFZk YHLv9YD+ODZMTYnn6PVzaCIMQoCbGhUu1L9EHuLg=
Message-Id: <6.2.5.6.2.20120402094047.0b79b658@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 02 Apr 2012 12:24:29 -0700
To: Ted Lemon <Ted.Lemon@nominum.com>, John C Klensin <john-ietf@jck.com>
From: SM <sm@resistor.net>
Subject: RE: [vmeet] [BOFCHAIRS]  Remote participation
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307472D5DF3@mbx-01.win.nominu m.com>
References: <4F729503.5080003@gmail.com> <0BBF44E367CFEE54C9AC516D@PST.JCK.COM> <6.2.5.6.2.20120328035236.0c7dc648@elandnews.com> <CAJNg7VLR0LVW3MqKAeC=0O5_UuwAP69f_w1BuG+YnVedudg8qQ@mail.gmail.com> <24143_1332964425_q2SJriGr012797_6.2.5.6.2.20120328103857.0c1fb05 0@elandnews.com> <1332966135.4980.75.camel@minbar.fac.cs.cmu.edu> <25D805D4-16EA-4E3B-B37E-D67A058E1827@cs.columbia.edu> <C74241B313CA00C3A1D03E7F@PST.JCK.COM> <6.2.5.6.2.20120330090037.0901d0f0@elandnews.com> <A838D9E54AA2FBA66AC29F99@PST.JCK.COM> <6.2.5.6.2.20120330151904.0d747920@elandnews.com> <932A5044CE359AECF4537FC7@PST.JCK.COM> <6.2.5.6.2.20120330234220.0d442ed0@elandnews.com> <8D23D4052ABE7A4490E77B1A012B6307472D5DF3@mbx-01.win.nominum.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Mailman-Approved-At: Mon, 02 Apr 2012 14:28:10 -0700
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Apr 2012 19:29:09 -0000

Hi Ted,
At 07:32 02-04-2012, Ted Lemon wrote:
>In the case of DHC at least, the metrics are pretty 
>accurate.   There was barely time in the wg meeting to actually have 
>any meaningful discussion about anything, so each presentation wound 
>up being "sales pitch, a few comments, chair interrupts for time, 
>next steps, next presentation."   It wasn't really a good use of f2f 
>meeting time, and I'd like to do it differently at the next IETF, 
>but I don't really know how, because there weren't a lot of 
>presentations that the working group shouldn't have heard, and we 
>got one of the nice like 2.5h time slots.

There are two points in the above:

  (i)  Not enough time to have a meaningful discussion about anything

  (ii) The working group should have heard most of the presentations

One of the alternatives is to have a longer slot.  Another 
alternative is to have a 50/50 rule; the chair keeps half of the time 
for discussions and let presenters make their pitch in the other 
half.  If there are too many presentation proposals, the chair would 
have to figure out which ones to drop, or it could be first X who 
have all their material ready are on the agenda.

Regards,
-sm 


From Ted.Lemon@nominum.com  Tue Apr  3 02:55:15 2012
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 C08C421F86DA; Tue,  3 Apr 2012 02:55:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.669
X-Spam-Level: 
X-Spam-Status: No, score=-105.669 tagged_above=-999 required=5 tests=[AWL=0.929, 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 QHTnx2OLMuMy; Tue,  3 Apr 2012 02:55:15 -0700 (PDT)
Received: from exprod7og120.obsmtp.com (exprod7og120.obsmtp.com [64.18.2.18]) by ietfa.amsl.com (Postfix) with ESMTP id 97BD921F86CB; Tue,  3 Apr 2012 02:55:14 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob120.postini.com ([64.18.6.12]) with SMTP ID DSNKT3rJAhlNxWsneB+xFx9YmE/+ooOjnWXZ@postini.com; Tue, 03 Apr 2012 02:55:14 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 975581B82D1; Tue,  3 Apr 2012 02:55:13 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 84A65190064; Tue,  3 Apr 2012 02:55:13 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0247.003; Tue, 3 Apr 2012 02:55:13 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Joel jaeggli <joelja@bogus.com>, John C Klensin <john-ietf@jck.com>
Subject: RE: [vmeet] [BOFCHAIRS]  Remote participation
Thread-Topic: [vmeet] [BOFCHAIRS]  Remote participation
Thread-Index: AQHNDJwyGhLUxvnL90OauzYccLnpHZaDunGngAD5eoCAAuyzD4AAiDgAgAAQWwCAAKpiQw==
Date: Tue, 3 Apr 2012 09:55:13 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307472D606C@mbx-01.win.nominum.com>
References: <4F729503.5080003@gmail.com> <0BBF44E367CFEE54C9AC516D@PST.JCK.COM> <6.2.5.6.2.20120328035236.0c7dc648@elandnews.com> <CAJNg7VLR0LVW3MqKAeC=0O5_UuwAP69f_w1BuG+YnVedudg8qQ@mail.gmail.com> <24143_1332964425_q2SJriGr012797_6.2.5.6.2.20120328103857.0c1fb05 0@elandnews.com> <1332966135.4980.75.camel@minbar.fac.cs.cmu.edu> <25D805D4-16EA-4E3B-B37E-D67A058E1827@cs.columbia.edu> <C74241B313CA00C3A1D03E7F@PST.JCK.COM> <6.2.5.6.2.20120330090037.0901d0f0@elandnews.com> <A838D9E54AA2FBA66AC29F99@PST.JCK.COM> <6.2.5.6.2.20120330151904.0d747920@elandnews.com> <932A5044CE359AECF4537FC7@PST.JCK.COM> ,<6.2.5.6.2.20120330234220.0d442ed0@elandnews.com> <8D23D4052ABE7A4490E77B1A012B6307472D5DF3@mbx-01.win.nominum.com> <007FA6E7E439668061E0A1E2@PST.JCK.COM>,<4F79D52E.70601@bogus.com>
In-Reply-To: <4F79D52E.70601@bogus.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: SM <sm@resistor.net>, "vmeet@ietf.org" <vmeet@ietf.org>, "wgchairs@ietf.org" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Apr 2012 09:55:15 -0000

It's difficult to set a good balance here.   When you have a bazillion diff=
erent proposals, it's not really shocking that not everybody has read every=
 proposal.   Even if you've read every proposal, it may be difficult to rem=
ember the details of each one if you didn't read them this week.   In that =
context, you'd like a presentation that explains what the proposal is, as a=
 sales pitch to get people to read the document, and as a refresher for peo=
ple who read the document a month ago and read two dozen more documents sin=
ce then.   Then you'd like people who haven't read the documents to read th=
e ones they've decided are worth the time.   Then you'd like to have a disc=
ussion, because you'd have a group of people who were sufficiently up to sp=
eed to *have* a discussion.

But to do this would require more time than any working group has, and hard=
er agenda planning than the IETF can reasonably do.   The wish to keep pres=
entations completely out of working group meetings isn't realistic, but aft=
er this meeting I feel like we (the DHC wg) need to do something differentl=
y.

BTW, I should point out that discussion-only sessions aren't always good.  =
 Sometimes you have people with strong opinions who aren't open to debate o=
n those opinions, and then you get an incredibly time-wasting "discussion" =
at the microphone, in which no forward progress is made.   So a disproporti=
onate amount of working group time can spent "discussing" relatively minor =
proposals while the serious work of the working group doesn't get discussed=
 due to time constraints.

This is a hard problem.

For DHC, I think that in the future presentations have to be very short, li=
ke maybe 1 minute or maybe 2 minutes for a really complex draft.   Essentia=
lly, they need to be just slightly longer than an elevator pitch.   The rem=
ainder of the slot needs to be spent on discussion.   Drafts that are conte=
ntious should be discussed offline, because no actual design discussion is =
going to happen anyway.   The wg chairs need to use their judgment on this-=
-there's a very fine line between a contentious discussion that can actuall=
y produce results, and one that won't.

I'm thinking the presentation on the projector needs to have a timer on it,=
 too.

From lberger@labn.net  Tue Apr  3 04:35:53 2012
Return-Path: <lberger@labn.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 AC0A621F86FF for <wgchairs@ietfa.amsl.com>; Tue,  3 Apr 2012 04:35:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.561
X-Spam-Level: 
X-Spam-Status: No, score=-97.561 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, IP_NOT_FRIENDLY=0.334, 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 vfebeqRMcIEh for <wgchairs@ietfa.amsl.com>; Tue,  3 Apr 2012 04:35:53 -0700 (PDT)
Received: from oproxy8-pub.bluehost.com (oproxy8.bluehost.com [IPv6:2605:dc00:100:2::a8]) by ietfa.amsl.com (Postfix) with SMTP id D863721F86F9 for <wgchairs@ietf.org>; Tue,  3 Apr 2012 04:35:52 -0700 (PDT)
Received: (qmail 17826 invoked by uid 0); 3 Apr 2012 11:35:52 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by oproxy8.bluehost.com with SMTP; 3 Apr 2012 11:35:52 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default;  h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=t8TVRLRVaOEpCI68mKEkZYyC/ScmO9vSNjYtavugPJw=;  b=SM02HWrz2F7I6bbnGszDnK1g582NKVErrzohhdNiCkEIK3ewJFYCvkzwgGVzCjQAnya01W/R3PFI1C42eJKjfuXGadmNp3t7iLM4EQk8GY/cuzmI/Sr3UO0Vfpc9D6AW;
Received: from box313.bluehost.com ([69.89.31.113] helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.76) (envelope-from <lberger@labn.net>) id 1SF21f-0006tL-W9; Tue, 03 Apr 2012 05:35:52 -0600
Message-ID: <4F7AE098.9020705@labn.net>
Date: Tue, 03 Apr 2012 07:35:52 -0400
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: John Scudder <jgs@juniper.net>
Subject: Re: Etherpad deployment for this meeting
References: <4EBA594C.1060406@levkowetz.com> <4F69CC24.1020509@labn.net>	<4F6FA690.4080601@levkowetz.com> <4F76C0F7.1000308@viagenie.ca> <BC5B3623-A908-419D-BC52-3C043ED13487@bgp.nu>
In-Reply-To: <BC5B3623-A908-419D-BC52-3C043ED13487@bgp.nu>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Apr 2012 11:35:53 -0000

On 4/2/2012 6:31 AM, John G. Scudder wrote:
> On Mar 31, 2012, at 10:31 AM, Simon Perreault wrote:
> 
>> I used Etherpad as a minute taker and overall loved it. FYI, I found two minor annoyances, don't know if they are already known:
>>
>> - About every 30 minutes (not exactly sure), it "disconnects" and asks me to reconnect. The button is above the page cut (I have a small netbook) so it took me a while to notice it. When I clicked it I got reconnected without data loss.
> 
> FWIW this didn't happen to me. I used Etherpad for at least three different WGs.
> 

+1.  Great tool.  Truly appreciate having it!


From sm@resistor.net  Tue Apr  3 04:30:33 2012
Return-Path: <sm@resistor.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 112FF21F872B for <wgchairs@ietfa.amsl.com>; Tue,  3 Apr 2012 04:30:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.239
X-Spam-Level: 
X-Spam-Status: No, score=-102.239 tagged_above=-999 required=5 tests=[AWL=0.360, 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 lBHZouljPoZS for <wgchairs@ietfa.amsl.com>; Tue,  3 Apr 2012 04:30:28 -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 7E17C21F868C for <wgchairs@ietf.org>; Tue,  3 Apr 2012 04:30:28 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q33BUKqj005071; Tue, 3 Apr 2012 04:30:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1333452626; i=@resistor.net; bh=5S0SsBn4SQp+JDQJVuWJusNp1eG8Tgnq/a3bwUivtI8=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=eqUjjfZg37ahCKLCoanTJ+PcLwFba9DaDTHHH3txveY2bvxfXT850XPh1EoPbrw05 LYWdYWhT12/Hkn6IonHYDwA2mlqU7uXmTT8NM0pe1bF1i5N5V/iBQGDA+f28F2sRth Pqmc//fjZgun0lzWVP4zKNbKaoR8SRcNLrIZ0qPY=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1333452626; i=@resistor.net; bh=5S0SsBn4SQp+JDQJVuWJusNp1eG8Tgnq/a3bwUivtI8=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=J8qwA4JRHDK4LdpQTPyQeqYPjy9oqVgjYfUFCkMTnZCD4+xSAiQDQhhloSJNj7CiW uPMoVvibCXwJ8NXBfnvnDfJ5juZOlk9aQGcOoi34lNZE0HZgj8EBJpHzltMndR6QpT IMwB65gpO3FKB+IV/nkuF21QaXINqEpa07XJ/tVg=
Message-Id: <6.2.5.6.2.20120403020248.0b7cf0c0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 03 Apr 2012 04:30:00 -0700
To: John C Klensin <john-ietf@jck.com>, Melinda Shore <melinda.shore@gmail.com>, wgchairs@ietf.org
From: SM <sm@resistor.net>
Subject: Re: [vmeet] [BOFCHAIRS]  Remote participation
In-Reply-To: <A64AA15734D0ADEFDD8EED1F@PST.JCK.COM>
References: <4F729503.5080003@gmail.com> <0BBF44E367CFEE54C9AC516D@PST.JCK.COM> <6.2.5.6.2.20120328035236.0c7dc648@elandnews.com> <CAJNg7VLR0LVW3MqKAeC=0O5_UuwAP69f_w1BuG+YnVedudg8qQ@mail.gmail.com> <24143_1332964425_q2SJriGr012797_6.2.5.6.2.20120328103857.0c1fb05	0@elandnews.com> <1332966135.4980.75.camel@minbar.fac.cs.cmu.edu> <25D805D4-16EA-4E3B-B37E-D67A058E1827@cs.columbia.edu> <C74241B313CA00C3A1D03E7F@PST.JCK.COM> <6.2.5.6.2.20120330090037.0901d0f0@elandnews.com> <A838D9E54AA2FBA66AC29F99@PST.JCK.COM> <6.2.5.6.2.20120330151904.0d747920@elandnews.com> <932A5044CE359AECF4537FC7@PST.JCK.COM> <6.2.5.6.2.20120330234220.0d442ed0@elandnews.com> <8D23D4052ABE7A4490E77B1A012B6307472D5DF3@mbx-01.win.nominum.com> <007FA6E7E439668061E0A1E2@PST.JCK.COM> <4F79D52E.70601@bogus.com> <4F79F5AA.8080303@gmail.com> <A64AA15734D0ADEFDD8EED1F@PST.JCK.COM>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Mailman-Approved-At: Tue, 03 Apr 2012 06:04:11 -0700
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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, 03 Apr 2012 11:30:33 -0000

Hi John,
At 12:36 02-04-2012, John C Klensin wrote:
>I agree in principle.  But many WG chairs seem incapable of
>controlling meetings and restricting the time allowed in

Most WG chairs do a decent job controlling the session.

>practice for long, sometimes incomprehensible, presentations
>with little information content.   We've been saying "discussion
>and interaction, not presentations" long enough and often enough

Some people find the presentations worthwhile, others don't.  Some 
people need it to justify the travel.

Sometimes there is a nine-minute presentation followed by one minute 
for discussion.  After the first few minutes, glancing at the list 
archive confirms that it's a sales pitch and that the mailing list 
has been lethargic over the last six months.

Regards,
-sm



From john-ietf@jck.com  Tue Apr  3 07:55:44 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D58A321F8793 for <wgchairs@ietfa.amsl.com>; Tue,  3 Apr 2012 07:55:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.413
X-Spam-Level: 
X-Spam-Status: No, score=-102.413 tagged_above=-999 required=5 tests=[AWL=0.186, 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 Qs3tf0aYw4Ay for <wgchairs@ietfa.amsl.com>; Tue,  3 Apr 2012 07:55:44 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 0A79F21F8790 for <wgchairs@ietf.org>; Tue,  3 Apr 2012 07:55:44 -0700 (PDT)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SF549-000Lho-4E; Tue, 03 Apr 2012 10:50:37 -0400
Date: Tue, 03 Apr 2012 10:55:35 -0400
From: John C Klensin <john-ietf@jck.com>
To: SM <sm@resistor.net>, Melinda Shore <melinda.shore@gmail.com>, wgchairs@ietf.org
Subject: Re: [vmeet] [BOFCHAIRS]  Remote participation
Message-ID: <4C78EAAB9AD999D13349D26A@PST.JCK.COM>
In-Reply-To: <6.2.5.6.2.20120403020248.0b7cf0c0@elandnews.com>
References: <4F729503.5080003@gmail.com> <0BBF44E367CFEE54C9AC516D@PST.JCK.COM> <6.2.5.6.2.20120328035236.0c7dc648@elandnews.com> <CAJNg7VLR0LVW3MqKAeC=0O5_UuwAP69f_w1BuG+YnVedudg8qQ@mail.gmail.com> <24143_1332964425_q2SJriGr012797_6.2.5.6.2.20120328103857.0c1fb05 0@elandnews.com> <1332966135.4980.75.camel@minbar.fac.cs.cmu.edu> <25D805D4-16EA-4E3B-B37E-D67A058E1827@cs.columbia.edu> <C74241B313CA00C3A1D03E7F@PST.JCK.COM> <6.2.5.6.2.20120330090037.0901d0f0@elandnews.com> <A838D9E54AA2FBA66AC29F99@PST.JCK.COM> <6.2.5.6.2.20120330151904.0d747920@elandnews.com> <932A5044CE359AECF4537FC7@PST.JCK.COM> <6.2.5.6.2.20120330234220.0d442ed0@elandnews.com> <8D23D4052ABE7A4490E77B1A012B6307472D5DF3@mbx-01.win.nominum.com> <007FA6E7E439668061E0A1E2@PST.JCK.COM> <4F79D52E.70601@bogus.com> <4F79F5AA.8080303@gmail.com> <A64AA15734D0ADEFDD8EED1F@PST.JCK.COM> <6.2.5.6.2.20120403020248.0b7cf0c0@elandnews.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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, 03 Apr 2012 14:55:44 -0000

--On Tuesday, April 03, 2012 04:30 -0700 SM <sm@resistor.net>
wrote:

> Hi John,
> At 12:36 02-04-2012, John C Klensin wrote:
>> I agree in principle.  But many WG chairs seem incapable of
>> controlling meetings and restricting the time allowed in
> 
> Most WG chairs do a decent job controlling the session.

And some don't.  Let me put this personally -- while we haven't
had an product sales pitches, Joseph and I have had considerable
trouble in EAI controlling the kinds of presentations that take
nine or ten minutes that are completely redundant with what has
already occurred on the mailing list and that produce just about
zero (using your example, a minute or less) of discussion.  I
think that is a waste of meeting time, to the point that we
cancelled the EAI f2f meeting in Paris.  But, justifiably or
not, I'm got the reputation of being rather ruthless about such
things.  I feel as if a larger collection of tools, such as
agreement that it would be reasonable to force such
presentations onto the net with at most one minute, no slide,
summaries a f2f meetings, would help.  

At some level, I don't care as much whether that alternative is
required or merely an expansion of Chair options.  But, if it
were an option, then it would be also possible to push back on
requests for long (or multiple) meeting slots that might be
presentation-heavy.
 
>> practice for long, sometimes incomprehensible, presentations
>> with little information content.   We've been saying
>> "discussion and interaction, not presentations" long enough
>> and often enough
> 
> Some people find the presentations worthwhile, others don't.
> Some people need it to justify the travel.

> Sometimes there is a nine-minute presentation followed by one
> minute for discussion.  After the first few minutes, glancing
> at the list archive confirms that it's a sales pitch and that
> the mailing list has been lethargic over the last six months.

Yes, exactly.

I recognize that I'm pushing, possibly out of nostalgia, for an
IETF that gets most of its work done on mailing lists and for
which we should say to a WG (not always or rigidly, but often)
"if you aren't getting work done on your mailing list, then you
aren't getting work done and maybe you should be closed rather
than getting more meeting slots at IETF".  There will always be
exceptions but, when someone says something like "we had 4.5
hours at IETF and got a lot of work done", my personal reaction
isn't "hmm, I wonder how much more work that WG could do if
given more time" but "I wonder what is wrong that requires that
much meeting time to make progress" with possible answers
including (but not limited to) "not enough happening on the
mailing list between meetings" and "too much work assigned to
that WG and it is trying to do all of it in parallel".  

FWIW, I think that "if we had even more meeting time, we could
get more work done" and its frequent corollary "the amount of
work we can get done is bounded by how much meeting time we get"
tends toward a situation in which WGs or their organizational
equivalents meet for several days or a week with little
expectation of anything getting done between meetings other than
meeting preparation.  Many of us have seen organizations that
work that way, some of them are actually quite effective.
Whether it is desirable for the IETF to go in that direction or
not, I think that, if we are actually going in that direction,
we should be reviewing procedures to see if they are an
appropriate match for it --trying to push back the tide is not
usually very productive.

     john




From br@brianrosen.net  Tue Apr  3 08:04:12 2012
Return-Path: <br@brianrosen.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9A7821F851E for <wgchairs@ietfa.amsl.com>; Tue,  3 Apr 2012 08:04:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.901
X-Spam-Level: 
X-Spam-Status: No, score=-101.901 tagged_above=-999 required=5 tests=[AWL=0.698, 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 C0RKqMufDi-A for <wgchairs@ietfa.amsl.com>; Tue,  3 Apr 2012 08:04:12 -0700 (PDT)
Received: from barmail4.idig.net (barmail4.idig.net [64.34.111.235]) by ietfa.amsl.com (Postfix) with ESMTP id F224221F8518 for <wgchairs@ietf.org>; Tue,  3 Apr 2012 08:04:11 -0700 (PDT)
X-ASG-Debug-ID: 1333465399-04d035034c365850001-JRdzcT
Received: from wwh1.winweblinux.com (wwh1.winweblinux.com [76.74.186.184]) by barmail4.idig.net with ESMTP id TdU7biPBPL84xWBc; Tue, 03 Apr 2012 08:03:19 -0700 (PDT)
X-Barracuda-Envelope-From: br@brianrosen.net
X-Barracuda-Apparent-Source-IP: 76.74.186.184
Received: from [209.173.57.233] (helo=[192.168.130.23]) by wwh1.winweblinux.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <br@brianrosen.net>) id 1SF5GQ-000NaZ-3n; Tue, 03 Apr 2012 08:03:18 -0700
Subject: Re: [vmeet] [BOFCHAIRS]  Remote participation
Mime-Version: 1.0 (Apple Message framework v1257)
X-ASG-Orig-Subj: Re: [vmeet] [BOFCHAIRS]  Remote participation
Content-Type: text/plain; charset=us-ascii
From: Brian Rosen <br@brianrosen.net>
In-Reply-To: <4C78EAAB9AD999D13349D26A@PST.JCK.COM>
Date: Tue, 3 Apr 2012 11:03:14 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <6C518FB2-0A98-40EF-A13B-A77E09882D03@brianrosen.net>
References: <4F729503.5080003@gmail.com> <0BBF44E367CFEE54C9AC516D@PST.JCK.COM> <6.2.5.6.2.20120328035236.0c7dc648@elandnews.com> <CAJNg7VLR0LVW3MqKAeC=0O5_UuwAP69f_w1BuG+YnVedudg8qQ@mail.gmail.com> <24143_1332964425_q2SJriGr012797_6.2.5.6.2.20120328103857.0c1fb05 0@elandnews.com> <1332966135.4980.75.camel@minbar.fac.cs.cmu.edu> <25D805D4-16EA-4E3B-B37E-D67A058E1827@cs.columbia.edu> <C74241B313CA00C3A1D03E7F@PST.JCK.COM> <6.2.5.6.2.20120330090037.0901d0f0@elandnews.com> <A838D9E54AA2FBA66AC29F99@PST.JCK.COM> <6.2.5.6.2.20120330151904.0d747920@elandnews.com> <932A5044CE359AECF4537FC7@PST.JCK.COM> <6.2.5.6.2.20120330234220.0d442ed0@elandnews.com> <8D23D4052ABE7A4490E77B1A012B6307472D5DF3@mbx-01.win.nominum.com> <007FA6E7E439668061E0A1E2@PST.JCK.COM> <4F79D52E.70601@bogus.com> <4F79F5AA.8080303@gmail.com> <A64AA15734D0ADEFDD8EED1F@PST.JCK.COM> <6.2.5.6.2.20120403020248.0b7cf0c0@elandnews.com> <4C78EAAB9AD999D13349D26A@PST.JCK.COM>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1257)
X-Barracuda-Connect: wwh1.winweblinux.com[76.74.186.184]
X-Barracuda-Start-Time: 1333465399
X-Barracuda-URL: http://64.34.111.235:8000/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at idig.net
X-Barracuda-Spam-Score: 0.00
X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=3.5 tests=
X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.2.93075 Rule breakdown below pts rule name              description ---- ---------------------- --------------------------------------------------
Cc: SM <sm@resistor.net>, 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, 03 Apr 2012 15:04:12 -0000

Personally, I prefer dealing with reality, rather than relying on what =
ideally should be.

Ideally, everyone in the room has read the document, followed the mail =
list discussion, and is aware of the open issues.

In reality, we are lucky to have half the room in such a state.

I usually choose to allow a presenter to spend some time summarizing =
where the document is before moving on to the open issues.  If I see =
half the presentation dealing with "level setting", then I'll take =
action, but that's just me.

Brian

On Apr 3, 2012, at 10:55 AM, John C Klensin wrote:

>=20
>=20
> --On Tuesday, April 03, 2012 04:30 -0700 SM <sm@resistor.net>
> wrote:
>=20
>> Hi John,
>> At 12:36 02-04-2012, John C Klensin wrote:
>>> I agree in principle.  But many WG chairs seem incapable of
>>> controlling meetings and restricting the time allowed in
>>=20
>> Most WG chairs do a decent job controlling the session.
>=20
> And some don't.  Let me put this personally -- while we haven't
> had an product sales pitches, Joseph and I have had considerable
> trouble in EAI controlling the kinds of presentations that take
> nine or ten minutes that are completely redundant with what has
> already occurred on the mailing list and that produce just about
> zero (using your example, a minute or less) of discussion.  I
> think that is a waste of meeting time, to the point that we
> cancelled the EAI f2f meeting in Paris.  But, justifiably or
> not, I'm got the reputation of being rather ruthless about such
> things.  I feel as if a larger collection of tools, such as
> agreement that it would be reasonable to force such
> presentations onto the net with at most one minute, no slide,
> summaries a f2f meetings, would help. =20
>=20
> At some level, I don't care as much whether that alternative is
> required or merely an expansion of Chair options.  But, if it
> were an option, then it would be also possible to push back on
> requests for long (or multiple) meeting slots that might be
> presentation-heavy.
>=20
>>> practice for long, sometimes incomprehensible, presentations
>>> with little information content.   We've been saying
>>> "discussion and interaction, not presentations" long enough
>>> and often enough
>>=20
>> Some people find the presentations worthwhile, others don't.
>> Some people need it to justify the travel.
>=20
>> Sometimes there is a nine-minute presentation followed by one
>> minute for discussion.  After the first few minutes, glancing
>> at the list archive confirms that it's a sales pitch and that
>> the mailing list has been lethargic over the last six months.
>=20
> Yes, exactly.
>=20
> I recognize that I'm pushing, possibly out of nostalgia, for an
> IETF that gets most of its work done on mailing lists and for
> which we should say to a WG (not always or rigidly, but often)
> "if you aren't getting work done on your mailing list, then you
> aren't getting work done and maybe you should be closed rather
> than getting more meeting slots at IETF".  There will always be
> exceptions but, when someone says something like "we had 4.5
> hours at IETF and got a lot of work done", my personal reaction
> isn't "hmm, I wonder how much more work that WG could do if
> given more time" but "I wonder what is wrong that requires that
> much meeting time to make progress" with possible answers
> including (but not limited to) "not enough happening on the
> mailing list between meetings" and "too much work assigned to
> that WG and it is trying to do all of it in parallel". =20
>=20
> FWIW, I think that "if we had even more meeting time, we could
> get more work done" and its frequent corollary "the amount of
> work we can get done is bounded by how much meeting time we get"
> tends toward a situation in which WGs or their organizational
> equivalents meet for several days or a week with little
> expectation of anything getting done between meetings other than
> meeting preparation.  Many of us have seen organizations that
> work that way, some of them are actually quite effective.
> Whether it is desirable for the IETF to go in that direction or
> not, I think that, if we are actually going in that direction,
> we should be reviewing procedures to see if they are an
> appropriate match for it --trying to push back the tide is not
> usually very productive.
>=20
>     john
>=20
>=20
>=20


From jhaas@slice.pfrc.org  Tue Apr  3 08:58:28 2012
Return-Path: <jhaas@slice.pfrc.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A1BE11E811F for <wgchairs@ietfa.amsl.com>; Tue,  3 Apr 2012 08:58:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level: 
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VsnYj+5E+vdE for <wgchairs@ietfa.amsl.com>; Tue,  3 Apr 2012 08:58:28 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 0524411E811E for <wgchairs@ietf.org>; Tue,  3 Apr 2012 08:58:28 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id A275817041D; Tue,  3 Apr 2012 11:58:27 -0400 (EDT)
Date: Tue, 3 Apr 2012 11:58:27 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Lou Berger <lberger@labn.net>
Subject: Re: Etherpad deployment for this meeting
Message-ID: <20120403155827.GA7467@slice>
References: <4EBA594C.1060406@levkowetz.com> <4F69CC24.1020509@labn.net> <4F6FA690.4080601@levkowetz.com> <4F76C0F7.1000308@viagenie.ca> <BC5B3623-A908-419D-BC52-3C043ED13487@bgp.nu> <4F7AE098.9020705@labn.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4F7AE098.9020705@labn.net>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: John Scudder <jgs@juniper.net>, 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, 03 Apr 2012 15:58:28 -0000

On Tue, Apr 03, 2012 at 07:35:52AM -0400, Lou Berger wrote:
> +1.  Great tool.  Truly appreciate having it!

+1 also.  It deals with a few things I find problematic about taking meeting
minutes:
- Getting the details right since more than one person can add at the same
  time.
- It doesn't prevent someone who is roped into helping with minutes from
  being able to participate in session discussion.  (Major gripe of mine!)



From wesley.george@twcable.com  Tue Apr  3 13:50:04 2012
Return-Path: <wesley.george@twcable.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6062B11E80FF for <wgchairs@ietfa.amsl.com>; Tue,  3 Apr 2012 13:50:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.763
X-Spam-Level: 
X-Spam-Status: No, score=-0.763 tagged_above=-999 required=5 tests=[AWL=0.700,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JDADHW+IGjDe for <wgchairs@ietfa.amsl.com>; Tue,  3 Apr 2012 13:50:03 -0700 (PDT)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id BF96E11E809D for <wgchairs@ietf.org>; Tue,  3 Apr 2012 13:50:03 -0700 (PDT)
X-SENDER-IP: 10.136.163.13
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.75,364,1330923600"; d="scan'208";a="363083503"
Received: from unknown (HELO PRVPEXHUB04.corp.twcable.com) ([10.136.163.13]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 03 Apr 2012 16:49:45 -0400
Received: from PRVPEXVS03.corp.twcable.com ([10.136.163.27]) by PRVPEXHUB04.corp.twcable.com ([10.136.163.13]) with mapi; Tue, 3 Apr 2012 16:50:02 -0400
From: "George, Wes" <wesley.george@twcable.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, John C Klensin <john-ietf@jck.com>
Date: Tue, 3 Apr 2012 16:50:01 -0400
Subject: RE: [vmeet] [BOFCHAIRS]  Remote participation
Thread-Topic: [vmeet] [BOFCHAIRS]  Remote participation
Thread-Index: Ac0RDodjyq1uU0sxQcSX6NaGTUDd+QAxBkAw
Message-ID: <DCC302FAA9FE5F4BBA4DCAD465693779173D818CB9@PRVPEXVS03.corp.twcable.com>
References: <4F729503.5080003@gmail.com> <0BBF44E367CFEE54C9AC516D@PST.JCK.COM> <6.2.5.6.2.20120328035236.0c7dc648@elandnews.com> <CAJNg7VLR0LVW3MqKAeC=0O5_UuwAP69f_w1BuG+YnVedudg8qQ@mail.gmail.com> <24143_1332964425_q2SJriGr012797_6.2.5.6.2.20120328103857.0c1fb05 0@elandnews.com>	<1332966135.4980.75.camel@minbar.fac.cs.cmu.edu> <25D805D4-16EA-4E3B-B37E-D67A058E1827@cs.columbia.edu> <C74241B313CA00C3A1D03E7F@PST.JCK.COM> <6.2.5.6.2.20120330090037.0901d0f0@elandnews.com> <A838D9E54AA2FBA66AC29F99@PST.JCK.COM> <6.2.5.6.2.20120330151904.0d747920@elandnews.com> <932A5044CE359AECF4537FC7@PST.JCK.COM> , <6.2.5.6.2.20120330234220.0d442ed0@elandnews.com> <8D23D4052ABE7A4490E77B1A012B6307472D5DF3@mbx-01.win.nominum.com> <007FA6E7E439668061E0A1E2@PST.JCK.COM>	<4F79D52E.70601@bogus.com> <A5F4819894B59B596920EA2F@PST.JCK.COM>	<4F79F508.1070201@alum.mit.edu> <2BD9BC086311C7B6FF0C35BE@PST.JCK.COM> <4F7A0AC4.8010806@alum.mit.edu>
In-Reply-To: <4F7A0AC4.8010806@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "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, 03 Apr 2012 20:50:04 -0000

I might add one more...

Promote "WG tourism" and cross-pollination.

With this many WGs, it's simply impossible to be actively involved in every=
 WG list for every piece of the IETF that I think might be applicable to my=
 employer and my skill set. My hope with the meetings is that I have enough=
 "free" timeslots (i.e. not occupied by groups that I'm actively involved i=
n) that I can sit in on a few other groups that I'm not actively involved i=
n and get a sense for what they're doing, maybe provide some ad hoc feedbac=
k. I've had failures, where I go to a WG meeting and can't understand enoug=
h of what's going on to contribute, but I've also had some successes, where=
 I find something else that I can provide feedback on or that I should be m=
ore actively watching. This is probably pretty important in order to attrac=
t new folks to the list so that additional work can get done, and probably =
should be a consideration when we talk about format for presentations and b=
est use of discussion during F2F meetings. I know that means that you spend=
 some time getting those who haven't read the drafts or aren't actively inv=
olved up to speed, but I thought that it was worth mentioning as something =
else that distinguishes the meetings from the list.

Thanks,

Wes George


> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On Beh=
alf
> Of Paul Kyzivat
> Sent: Monday, April 02, 2012 4:24 PM
> To: John C Klensin
> Cc: wgchairs@ietf.org
> Subject: Re: [vmeet] [BOFCHAIRS] Remote participation
>
> Frankly, it perhaps doesn't matter if we get the meetings to use the
> meeting time more efficiently. I think the highest value things that
> meetings provide are:
>
> 1) provide an artificial, but compelling, periodic deadline for
> progressing drafts, and for others to catch up on the status of those
> drafts.
>
> 2) force the primary participants to set aside their day job and
> personal concerns for a week and focus almost exclusively on the ietf tas=
ks
>
> 3) all get on a common time zone for a week, and facilitate informal
> "hallway" conversations.
>
> The official agenda, and the resulting proceedings, provide the formal
> justification to employers for the above. As long as they are working
> well enough to accomplish that maybe they are doing well enough.
>
>       Thanks,
>       Paul

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 sa.morris7@googlemail.com  Tue Apr  3 14:59:36 2012
Return-Path: <sa.morris7@googlemail.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 B467B21F850D for <wgchairs@ietfa.amsl.com>; Tue,  3 Apr 2012 14:59:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jfGwP1tzxP4k for <wgchairs@ietfa.amsl.com>; Tue,  3 Apr 2012 14:59:36 -0700 (PDT)
Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com [209.85.212.170]) by ietfa.amsl.com (Postfix) with ESMTP id ED54821F84FA for <wgchairs@ietf.org>; Tue,  3 Apr 2012 14:59:35 -0700 (PDT)
Received: by wibhr17 with SMTP id hr17so3719949wib.1 for <wgchairs@ietf.org>; Tue, 03 Apr 2012 14:59:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=PGDgWPfG8nIZl8bFUQ+omTBX/zcGFX716JTE3GFINfk=; b=QL1kj22ewzjVPlXDDaZf9UAkwLXd3XCAF1TIOp6RRZca7hQEfaNHu+uooTgBz9iuJH Kg9c0yApPv2bTTMdxTVQXe6HdjJt2K2XYQVDF+/7/2LWku13CCwkzl8o9act1WsLMh6y AXWykhfEJCw0LTyUC+HsgH1u1FaPskCHuxTLmG299OPszROqNphnFvdCoMMGB02vlOUp L/FRv4jp0W5fF71H449M4Pyc3GI3GyN2MvDpGvvpYKWPtXMXLRPQbxgaCelsJDR0CKI6 dstQtgqMKP8CaB2QYY2U2nHA2cvcmRnWpnW3PoNzx6SqSjHAj0ruQf7mrNGoTp3DqTQ8 Tq6g==
Received: by 10.180.95.197 with SMTP id dm5mr10374603wib.20.1333490375180; Tue, 03 Apr 2012 14:59:35 -0700 (PDT)
Received: from stephen-morriss-macbook-pro.local ([217.155.47.50]) by mx.google.com with ESMTPS id fn2sm74757057wib.0.2012.04.03.14.59.33 (version=SSLv3 cipher=OTHER); Tue, 03 Apr 2012 14:59:34 -0700 (PDT)
Message-ID: <4F7B72C5.3020300@googlemail.com>
Date: Tue, 03 Apr 2012 22:59:33 +0100
From: Stephen Morris <sa.morris7@googlemail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: [vmeet] [BOFCHAIRS]  Remote participation
References: <4F729503.5080003@gmail.com> <6.2.5.6.2.20120328035236.0c7dc648@elandnews.com> <CAJNg7VLR0LVW3MqKAeC=0O5_UuwAP69f_w1BuG+YnVedudg8qQ@mail.gmail.com> <24143_1332964425_q2SJriGr012797_6.2.5.6.2.20120328103857.0c1fb05 0@elandnews.com>	<1332966135.4980.75.camel@minbar.fac.cs.cmu.edu> <25D805D4-16EA-4E3B-B37E-D67A058E1827@cs.columbia.edu> <C74241B313CA00C3A1D03E7F@PST.JCK.COM> <6.2.5.6.2.20120330090037.0901d0f0@elandnews.com> <A838D9E54AA2FBA66AC29F99@PST.JCK.COM> <6.2.5.6.2.20120330151904.0d747920@elandnews.com> <932A5044CE359AECF4537FC7@PST.JCK.COM> , <6.2.5.6.2.20120330234220.0d442ed0@elandnews.com> <8D23D4052ABE7A4490E77B1A012B6307472D5DF3@mbx-01.win.nominum.com> <007FA6E7E439668061E0A1E2@PST.JCK.COM>	<4F79D52E.70601@bogus.com> <A5F4819894B59B596920EA2F@PST.JCK.COM>	<4F79F508.1070201@alum.mit.edu> <2BD9BC086311C7B6FF0C35BE@PST.JCK.COM> <4F7A0AC4.8010806@alum.mit.edu> <DCC302FAA9FE5F4BBA4DCAD465693779173D818CB9@PRVPEXVS03.corp.twcable.com>
In-Reply-To: <DCC302FAA9FE5F4BBA4DCAD465693779173D818CB9@PRVPEXVS03.corp.twcable.com>
X-Enigmail-Version: 1.4
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Apr 2012 21:59:36 -0000

On 03/04/2012 21:50, George, Wes wrote:
> I might add one more...
> 
> Promote "WG tourism" and cross-pollination.
> 
> With this many WGs, it's simply impossible to be actively involved 
> in every WG list for every piece of the IETF that I think might be 
> applicable to my employer and my skill set. My hope with the 
> meetings is that I have enough "free" timeslots (i.e. not occupied 
> by groups that I'm actively involved in) that I can sit in on a
> few other groups that I'm not actively involved in and get a sense
> for what they're doing, maybe provide some ad hoc feedback.

+1 to that.

But for that to happen, it does mean that presentations do have to take
account the fact that not everyone has read the draft.  Which in turn
means some "scene setting" in a presentation before getting down to the
open issues.  (In fact, in my WG I sometimes get a bit depressed how few
hands are raised to the question "who here has read the draft?".)

Stephen

From dean.willis@softarmor.com  Tue Apr  3 17:37:57 2012
Return-Path: <dean.willis@softarmor.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 3152411E809D for <wgchairs@ietfa.amsl.com>; Tue,  3 Apr 2012 17:37:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.5
X-Spam-Level: 
X-Spam-Status: No, score=-103.5 tagged_above=-999 required=5 tests=[AWL=0.099,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vvO1jht3Eriv for <wgchairs@ietfa.amsl.com>; Tue,  3 Apr 2012 17:37:55 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 71A5D11E8073 for <wgchairs@ietf.org>; Tue,  3 Apr 2012 17:37:47 -0700 (PDT)
Received: by obbtb4 with SMTP id tb4so439546obb.31 for <wgchairs@ietf.org>; Tue, 03 Apr 2012 17:37:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=softarmor.com; s=google; h=references:in-reply-to:mime-version:content-type:message-id :content-transfer-encoding:cc:from:subject:date:to:x-mailer; bh=+VOc9ggE+d3bydcYfD0pw/ILGUaTUQ/wclHvyoukcz8=; b=HAyCPkRSYeWgZgHyvMIRsTL3W1j1lllsHs2POl4AO/fgjuz0DHzMMDk30+kFw/901S NkQhwl4VAvjt/4zbQ6mwTFoGLcQWITiuF18ZweGlBfOx8/RSMSm9i0zFmA/hJGsL7aeo rkig+ppJyguTdx+8gTi+N2mE9Myztt4aYlkqs=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=references:in-reply-to:mime-version:content-type:message-id :content-transfer-encoding:cc:from:subject:date:to:x-mailer :x-gm-message-state; bh=+VOc9ggE+d3bydcYfD0pw/ILGUaTUQ/wclHvyoukcz8=; b=XPERmED2ddc5hPOcT1jd1Zi7EwdUbu3jCbtjSo0THQel/u5LWIHC/TMvJoFd7BnOZG 8P7vdx85OL7tomd2hDsYT4BW9V4MB0fhsfy9v6Ougbkc1EP2K3qLFNs8kWlp7tZUPTZ/ svHzUUy7dNtD99q2nBKMVpX1UaabD9xSqVbyyAmzT6ryq58fUOjHxQJA9ZLtrpxk1OGO 8AiJWPCLqq847L9WJnkJktyFRb7KLX2mFNQiiVoYckHtBVOxTL0xUE3vaTjNB9//U+mX zaOpCrNvBNRKYijYAlEIWMdw/41kSkm2BvgCEQlwIHWlI1MG7fxK4v/dCogzIQ1aegCX Vn+g==
Received: by 10.60.4.199 with SMTP id m7mr21472144oem.65.1333499867041; Tue, 03 Apr 2012 17:37:47 -0700 (PDT)
Received: from [192.168.2.119] (cpe-66-25-15-110.tx.res.rr.com. [66.25.15.110]) by mx.google.com with ESMTPS id h9sm23340841obr.20.2012.04.03.17.37.45 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 03 Apr 2012 17:37:46 -0700 (PDT)
References: <4F729503.5080003@gmail.com> <0BBF44E367CFEE54C9AC516D@PST.JCK.COM> <6.2.5.6.2.20120328035236.0c7dc648@elandnews.com> <CAJNg7VLR0LVW3MqKAeC=0O5_UuwAP69f_w1BuG+YnVedudg8qQ@mail.gmail.com> <24143_1332964425_q2SJriGr012797_6.2.5.6.2.20120328103857.0c1fb05	0@elandnews.com> <1332966135.4980.75.camel@minbar.fac.cs.cmu.edu> <25D805D4-16EA-4E3B-B37E-D67A058E1827@cs.columbia.edu> <C74241B313CA00C3A1D03E7F@PST.JCK.COM> <6.2.5.6.2.20120330090037.0901d0f0@elandnews.com> <A838D9E54AA2FBA66AC29F99@PST.JCK.COM> <6.2.5.6.2.20120330151904.0d747920@elandnews.com> <932A5044CE359AECF4537FC7@PST.JCK.COM> , <6.2.5.6.2.20120330234220.0d442ed0@elandnews.com> <8D23D4052ABE7A4490E77B1A012B6307472D5DF3@mbx-01.win.nominum.com> <007FA6E7E439668061E0A1E2@PST.JCK.COM> <4F79D52E.70601@bogus.com>	<A5F4819894B59B596920EA2F@PST.JCK.COM> <4F79F508.1070201@alum.mit.edu> <2BD9BC086311C7B6FF0C35BE@PST.JCK.COM> <4F7A0AC4.8010806@alum.mit.edu>
In-Reply-To: <4F7A0AC4.8010806@alum.mit.edu>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
Message-Id: <33E45281-4B54-4498-B82C-1701D804B66B@softarmor.com>
Content-Transfer-Encoding: quoted-printable
From: Dean Willis <dean.willis@softarmor.com>
Subject: Re: [vmeet] [BOFCHAIRS]  Remote participation
Date: Tue, 3 Apr 2012 19:37:44 -0500
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
X-Mailer: Apple Mail (2.1084)
X-Gm-Message-State: ALoCoQnoDXYf5ZKIvhyfpGpYeU4lYOpKV+oqR+8Ws0abyuEwNIzvRFoSg4wQGqUhUkJju5GtONd6
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, 04 Apr 2012 00:37:57 -0000

On Apr 2, 2012, at 3:23 PM, Paul Kyzivat wrote:

> Frankly, it perhaps doesn't matter if we get the meetings to use the =
meeting time more efficiently. I think the highest value things that =
meetings provide are:
>=20
> 1) provide an artificial, but compelling, periodic deadline for =
progressing drafts, and for others to catch up on the status of those =
drafts.
>=20
> 2) force the primary participants to set aside their day job and =
personal concerns for a week and focus almost exclusively on the ietf =
tasks
>=20
> 3) all get on a common time zone for a week, and facilitate informal =
"hallway" conversations.
>=20
> The official agenda, and the resulting proceedings, provide the formal =
justification to employers for the above. As long as they are working =
well enough to accomplish that maybe they are doing well enough.

That's a profoundly astute and brilliant observation. I've run gong-show =
meetings, meetings with nothing but intense focused discussion, and =
meetings where the entire greybearded DNS mafia showed up to pelt me =
with fruit. None has been profoundly more or less effective at achieving =
the desired goal of furthering consensus building on the problems at =
hand, because most of this actually happens outside the meeting room =
(quite often during the meeting when I throw out people having side =
conversations).

And that's why virtual meetings are so hard to get right. Although we =
might could remote the fruit-throwing part as John suggested.

--
Dean


From sm@resistor.net  Tue Apr  3 17:58:33 2012
Return-Path: <sm@resistor.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 0D51921F85E1 for <wgchairs@ietfa.amsl.com>; Tue,  3 Apr 2012 17:58:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.329
X-Spam-Level: 
X-Spam-Status: No, score=-102.329 tagged_above=-999 required=5 tests=[AWL=0.270, 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 vJimDtzbFOwu for <wgchairs@ietfa.amsl.com>; Tue,  3 Apr 2012 17:58:32 -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 7221E21F85DF for <wgchairs@ietf.org>; Tue,  3 Apr 2012 17:58:32 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q340wOgO004825; Tue, 3 Apr 2012 17:58:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1333501110; i=@resistor.net; bh=yrg8iz4Y1I7iJ6QMXztAqLuoQEwryrJ5H8wUOYGLDVc=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=uiSGjVPJ9Op/xuMpdogY2d7KGTrCHeDv/w0+88FRAJR5qpC/4xnOQmXYKrKX4MgbU 0rEeCyEHq6FR4NBjzLdt0P05Pgfqz+L0tTk2ihzr3qmbb4DRnz24eLNjXfzqCiJhTW lp85XnLjVz4SvdnnhMyQ/WskYqEN7g8lgDRiOJZI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1333501110; i=@resistor.net; bh=yrg8iz4Y1I7iJ6QMXztAqLuoQEwryrJ5H8wUOYGLDVc=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=ZDgIwh+/69A1h04v17sDkf1/8P5Su0jD7LpuKTQAemKeF86NOoV7Yzf3zV7Bc5B9m NFLspi/O38HoRgpp0xPDHvzTltiF6ZKgotVrStUFvEyvVFfphRUAxiCQdTxgyW58gz AKDwr43byl64KOKtzuzJFr01YSlzGwUNQA0wdUHQ=
Message-Id: <6.2.5.6.2.20120403140035.0ab6b130@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 03 Apr 2012 16:40:54 -0700
To: John C Klensin <john-ietf@jck.com>, wgchairs@ietf.org
From: SM <sm@resistor.net>
Subject: Re: [vmeet] [BOFCHAIRS]  Remote participation
In-Reply-To: <4C78EAAB9AD999D13349D26A@PST.JCK.COM>
References: <4F729503.5080003@gmail.com> <0BBF44E367CFEE54C9AC516D@PST.JCK.COM> <6.2.5.6.2.20120328035236.0c7dc648@elandnews.com> <CAJNg7VLR0LVW3MqKAeC=0O5_UuwAP69f_w1BuG+YnVedudg8qQ@mail.gmail.com> <24143_1332964425_q2SJriGr012797_6.2.5.6.2.20120328103857.0c1fb05 0@elandnews.com> <1332966135.4980.75.camel@minbar.fac.cs.cmu.edu> <25D805D4-16EA-4E3B-B37E-D67A058E1827@cs.columbia.edu> <C74241B313CA00C3A1D03E7F@PST.JCK.COM> <6.2.5.6.2.20120330090037.0901d0f0@elandnews.com> <A838D9E54AA2FBA66AC29F99@PST.JCK.COM> <6.2.5.6.2.20120330151904.0d747920@elandnews.com> <932A5044CE359AECF4537FC7@PST.JCK.COM> <6.2.5.6.2.20120330234220.0d442ed0@elandnews.com> <8D23D4052ABE7A4490E77B1A012B6307472D5DF3@mbx-01.win.nominum.com> <007FA6E7E439668061E0A1E2@PST.JCK.COM> <4F79D52E.70601@bogus.com> <4F79F5AA.8080303@gmail.com> <A64AA15734D0ADEFDD8EED1F@PST.JCK.COM> <6.2.5.6.2.20120403020248.0b7cf0c0@elandnews.com> <4C78EAAB9AD999D13349D26A@PST.JCK.COM>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Mailman-Approved-At: Wed, 04 Apr 2012 06:12:43 -0700
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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, 04 Apr 2012 00:58:33 -0000

Hi John,
At 07:55 03-04-2012, John C Klensin wrote:
>And some don't.  Let me put this personally -- while we haven't
>had an product sales pitches, Joseph and I have had considerable
>trouble in EAI controlling the kinds of presentations that take
>nine or ten minutes that are completely redundant with what has
>already occurred on the mailing list and that produce just about
>zero (using your example, a minute or less) of discussion.  I

Allowing more time for discussion or a video of the presentation 
won't change much.  From the above, the presenter is either not 
following the mailing list discussions, the presenter does not 
understand the mailing list discussions, or the presenter is using 
that nine minutes for other purposes.  There may also be cultural issues.

Regards,
-sm 


From pkyzivat@alum.mit.edu  Wed Apr  4 07:06:00 2012
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 1814D21F8764 for <wgchairs@ietfa.amsl.com>; Wed,  4 Apr 2012 07:06:00 -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 E2FSfr-t7i-l for <wgchairs@ietfa.amsl.com>; Wed,  4 Apr 2012 07:05:59 -0700 (PDT)
Received: from qmta15.westchester.pa.mail.comcast.net (qmta15.westchester.pa.mail.comcast.net [76.96.59.228]) by ietfa.amsl.com (Postfix) with ESMTP id 47FC721F875A for <wgchairs@ietf.org>; Wed,  4 Apr 2012 07:05:59 -0700 (PDT)
Received: from omta22.westchester.pa.mail.comcast.net ([76.96.62.73]) by qmta15.westchester.pa.mail.comcast.net with comcast id towF1i0041ap0As5Fq5zfW; Wed, 04 Apr 2012 14:05:59 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([24.62.229.5]) by omta22.westchester.pa.mail.comcast.net with comcast id tq5z1i00K07duvL3iq5zzy; Wed, 04 Apr 2012 14:05:59 +0000
Message-ID: <4F7C5545.4010807@alum.mit.edu>
Date: Wed, 04 Apr 2012 10:05:57 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: "George, Wes" <wesley.george@twcable.com>
Subject: Re: [vmeet] [BOFCHAIRS]  Remote participation
References: <4F729503.5080003@gmail.com> <6.2.5.6.2.20120328035236.0c7dc648@elandnews.com> <CAJNg7VLR0LVW3MqKAeC=0O5_UuwAP69f_w1BuG+YnVedudg8qQ@mail.gmail.com> <24143_1332964425_q2SJriGr012797_6.2.5.6.2.20120328103857.0c1fb05 0@elandnews.com>	<1332966135.4980.75.camel@minbar.fac.cs.cmu.edu> <25D805D4-16EA-4E3B-B37E-D67A058E1827@cs.columbia.edu> <C74241B313CA00C3A1D03E7F@PST.JCK.COM> <6.2.5.6.2.20120330090037.0901d0f0@elandnews.com> <A838D9E54AA2FBA66AC29F99@PST.JCK.COM> <6.2.5.6.2.20120330151904.0d747920@elandnews.com> <932A5044CE359AECF4537FC7@PST.JCK.COM> , <6.2.5.6.2.20120330234220.0d442ed0@elandnews.com> <8D23D4052ABE7A4490E77B1A012B6307472D5DF3@mbx-01.win.nominum.com> <007FA6E7E439668061E0A1E2@PST.JCK.COM>	<4F79D52E.70601@bogus.com> <A5F4819894B59B596920EA2F@PST.JCK.COM>	<4F79F508.1070201@alum.mit.edu> <2BD9BC086311C7B6FF0C35BE@PST.JCK.COM> <4F7A0AC4.8010806@alum.mit.edu> <DCC302FAA9FE5F4BBA4DCAD465693779173D818CB9@PRVPEXVS03.corp.twcable.com>
In-Reply-To: <DCC302FAA9FE5F4BBA4DCAD465693779173D818CB9@PRVPEXVS03.corp.twcable.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Apr 2012 14:06:00 -0000

On 4/3/12 4:50 PM, George, Wes wrote:
> I might add one more...
>
> Promote "WG tourism" and cross-pollination.
>
> With this many WGs, it's simply impossible to be actively involved in every WG list for every piece of the IETF that I think might be applicable to my employer and my skill set. My hope with the meetings is that I have enough "free" timeslots (i.e. not occupied by groups that I'm actively involved in) that I can sit in on a few other groups that I'm not actively involved in and get a sense for what they're doing, maybe provide some ad hoc feedback. I've had failures, where I go to a WG meeting and can't understand enough of what's going on to contribute, but I've also had some successes, where I find something else that I can provide feedback on or that I should be more actively watching. This is probably pretty important in order to attract new folks to the list so that additional work can get done, and probably should be a consideration when we talk about format for presentations and best use of discussion during F2F meetings. I know that means that you spend some time ge
 tting tho
se who haven't read the drafts or aren't actively involved up to speed, but I thought that it was worth mentioning as something else that distinguishes the meetings from the list.

I do *try* this. In fact I try it practically every meeting. But I find 
it is rarely helpful. IMO you really must have done your homework prior 
to a WG meeting in order to get any real sense of what is going on.

But perhaps it is possible to get a sense of whether a WG is functioning 
well, and hence worth investigating.

	Thanks,
	Paul

> Thanks,
>
> Wes George
>
>
>> -----Original Message-----
>> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On Behalf
>> Of Paul Kyzivat
>> Sent: Monday, April 02, 2012 4:24 PM
>> To: John C Klensin
>> Cc: wgchairs@ietf.org
>> Subject: Re: [vmeet] [BOFCHAIRS] Remote participation
>>
>> Frankly, it perhaps doesn't matter if we get the meetings to use the
>> meeting time more efficiently. I think the highest value things that
>> meetings provide are:
>>
>> 1) provide an artificial, but compelling, periodic deadline for
>> progressing drafts, and for others to catch up on the status of those
>> drafts.
>>
>> 2) force the primary participants to set aside their day job and
>> personal concerns for a week and focus almost exclusively on the ietf tasks
>>
>> 3) all get on a common time zone for a week, and facilitate informal
>> "hallway" conversations.
>>
>> The official agenda, and the resulting proceedings, provide the formal
>> justification to employers for the above. As long as they are working
>> well enough to accomplish that maybe they are doing well enough.
>>
>>        Thanks,
>>        Paul
>
> This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
>


From d3e3e3@gmail.com  Fri Apr  6 10:16:14 2012
Return-Path: <d3e3e3@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C51A21F861B for <wgchairs@ietfa.amsl.com>; Fri,  6 Apr 2012 10:16:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.312
X-Spam-Level: 
X-Spam-Status: No, score=-104.312 tagged_above=-999 required=5 tests=[AWL=-0.712, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vRWMv92aqD4l for <wgchairs@ietfa.amsl.com>; Fri,  6 Apr 2012 10:16:13 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 51E8121F85ED for <wgchairs@ietf.org>; Fri,  6 Apr 2012 10:16:13 -0700 (PDT)
Received: by lbok13 with SMTP id k13so847367lbo.31 for <wgchairs@ietf.org>; Fri, 06 Apr 2012 10:16:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type :content-transfer-encoding; bh=Qyob821b9+XjKgS5R9A7PwKwy4ssNkxlgHjHhiLgTcU=; b=CWKjCic4OQH8XheHprOVTFCU3LjWgSOYNz60BOlv6uUz311Fj7uPJjQZ/udGFUJcyf r8lRumnAk8uJ/xDLlZqzkzRTTRzrPn5+EuO88xppBXep6LWNOvYoZeYoJZmHcZfy2D9J eRpe+nD2KSqut30mLlW51VpsDZIR+8h9hd8Ml7Kc7bJBR3x89FpdpNREA803DSf9YxZb UwCqLH0iEATQZPJnpbGaQ+ScI7mG1FwHIw1sJA/ykTzNeok4IpRsFVRXWsQYO30KqEsy KHknhlXbSZ6VBoVigqUTZqEtNataK/ziBEOsoF+NJYPGjez3rSJU7XKcLUeWJUudYhxm QhSQ==
Received: by 10.152.113.229 with SMTP id jb5mr9550978lab.45.1333732572159; Fri, 06 Apr 2012 10:16:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.152.21.162 with HTTP; Fri, 6 Apr 2012 10:15:49 -0700 (PDT)
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 6 Apr 2012 13:15:49 -0400
Message-ID: <CAF4+nEGcB1oEH=dYhzJk7YVgzZ+O7dwyBqNdPMPAaCcyjEY-FQ@mail.gmail.com>
Subject: pre-approving -00 drafts
To: Working Group Chairs <wgchairs@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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, 06 Apr 2012 17:16:14 -0000

When I try to go to
https://datatracker.ietf.org/cgi-bin/wg/wg_init_rev_approval.cgi,
which, for example, is linked off the
http://www.ietf.org/wg/chairs-page.html Working Group Chairs' Page, I
seem to just get immediately re-directed to the datatracker. Is there
some new trick?

Thanks,
Donald
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
=A0Donald E. Eastlake 3rd=A0=A0 +1-508-333-2270 (cell)
=A0155 Beaver Street,=A0Milford, MA 01757 USA
=A0d3e3e3@gmail.com

From sm@elandsys.com  Fri Apr  6 10:29:26 2012
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 7BD8121F85D1 for <wgchairs@ietfa.amsl.com>; Fri,  6 Apr 2012 10:29:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.382
X-Spam-Level: 
X-Spam-Status: No, score=-102.382 tagged_above=-999 required=5 tests=[AWL=0.217, 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 IoBHJPIC2Fj8 for <wgchairs@ietfa.amsl.com>; Fri,  6 Apr 2012 10:29:25 -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 1382D21F85CC for <wgchairs@ietf.org>; Fri,  6 Apr 2012 10:29:21 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([41.136.239.246]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q36HT3C0010695 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 6 Apr 2012 10:29:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1333733356; i=@elandsys.com; bh=mtrZOgMisAkDIglj1qzt9HMmg2GQEZgnk5C8zueE72g=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=WVLROTut1aqUw8x13mHz/3T2G5V0AKCl0P8AuLncyAmjU5KIwCrpbca1+1N+4nr6D qlWQD1jTjAPLg584Fauq+kQcWAY7nvJfHuZgC5lumDvah+LyP0Mw9cFICAz4J0WLS0 nKUDMQFzYUHMyZTIdLzXYO8XXs+6AKHrkav3VyMg=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1333733356; i=@elandsys.com; bh=mtrZOgMisAkDIglj1qzt9HMmg2GQEZgnk5C8zueE72g=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=eRYuBICC+DdTd0/Rd0YLDIigxMIa3erIx1zRdGfxbsoDEL5cUEJE0uhQKIa4pKafR swM1LAxoqqwRmM3DuqbNaV0T+VsmG4KmXBm5+CCmimxcovEIyXR5shdRpOHYpddF2p yBphlWC64BI4JdtbnhlJAGD0dJR2HxBWePraEyL4=
Message-Id: <6.2.5.6.2.20120406102126.0a101b58@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 06 Apr 2012 10:25:54 -0700
To: Donald Eastlake <d3e3e3@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: pre-approving -00 drafts
In-Reply-To: <CAF4+nEGcB1oEH=dYhzJk7YVgzZ+O7dwyBqNdPMPAaCcyjEY-FQ@mail.g mail.com>
References: <CAF4+nEGcB1oEH=dYhzJk7YVgzZ+O7dwyBqNdPMPAaCcyjEY-FQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Working Group Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Apr 2012 17:29:26 -0000

Hi Donald,
At 10:15 06-04-2012, Donald Eastlake wrote:
>When I try to go to
>https://datatracker.ietf.org/cgi-bin/wg/wg_init_rev_approval.cgi,

It should be https://datatracker.ietf.org/wg/wg-name/  I was told the 
pre-approval is not working correctly due to a bug in the datatracker.

Regards,
S. Moonesamy 


From msk@cloudmark.com  Fri Apr  6 10:38:34 2012
Return-Path: <msk@cloudmark.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 93E2021F85F8 for <wgchairs@ietfa.amsl.com>; Fri,  6 Apr 2012 10:38:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.518
X-Spam-Level: 
X-Spam-Status: No, score=-102.518 tagged_above=-999 required=5 tests=[AWL=0.081, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AhsLWFLpOqd3 for <wgchairs@ietfa.amsl.com>; Fri,  6 Apr 2012 10:38:34 -0700 (PDT)
Received: from ht2-outbound.cloudmark.com (ht2-outbound.cloudmark.com [72.5.239.26]) by ietfa.amsl.com (Postfix) with ESMTP id 28FE021F8594 for <wgchairs@ietf.org>; Fri,  6 Apr 2012 10:38:34 -0700 (PDT)
Received: from EXCH-MBX901.corp.cloudmark.com ([fe80::addf:849a:f71c:4a82]) by exch-htcas902.corp.cloudmark.com ([fe80::54de:dc60:5f3e:334%10]) with mapi id 14.01.0355.002; Fri, 6 Apr 2012 10:38:33 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: Working Group Chairs <wgchairs@ietf.org>
Subject: RE: pre-approving -00 drafts
Thread-Topic: pre-approving -00 drafts
Thread-Index: AQHNFBj7J36BtCo76UWqNVgTgODkFZaOD2lg
Date: Fri, 6 Apr 2012 17:38:32 +0000
Message-ID: <9452079D1A51524AA5749AD23E0039280CCFFE@exch-mbx901.corp.cloudmark.com>
References: <CAF4+nEGcB1oEH=dYhzJk7YVgzZ+O7dwyBqNdPMPAaCcyjEY-FQ@mail.gmail.com>
In-Reply-To: <CAF4+nEGcB1oEH=dYhzJk7YVgzZ+O7dwyBqNdPMPAaCcyjEY-FQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.20.2.121]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Apr 2012 17:38:34 -0000

> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On Beh=
alf Of Donald Eastlake
> Sent: Friday, April 06, 2012 10:16 AM
> To: Working Group Chairs
> Subject: pre-approving -00 drafts
>=20
> When I try to go to
> https://datatracker.ietf.org/cgi-bin/wg/wg_init_rev_approval.cgi,
> which, for example, is linked off the
> http://www.ietf.org/wg/chairs-page.html Working Group Chairs' Page, I
> seem to just get immediately re-directed to the datatracker. Is there
> some new trick?

After you log in to the datatracker, you should see an "Adopt in WG" link f=
or any document that's not a WG document.  I think that's the new way to do=
 it, via a "Call for Adoption" step.  However, I haven't actually tried it =
to see if, after that, it offers you a way to create -00 working group docu=
ments.

We've discovered that you don't even get the "Adopt in WG" link if an indiv=
idual submission is in "AD is watching" state, so there are possibly multip=
le obstacles here.

The bug has been reported, but we haven't heard anything back yet.

-MSK

From d3e3e3@gmail.com  Fri Apr  6 11:18:22 2012
Return-Path: <d3e3e3@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D70821F8633 for <wgchairs@ietfa.amsl.com>; Fri,  6 Apr 2012 11:18:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.232
X-Spam-Level: 
X-Spam-Status: No, score=-104.232 tagged_above=-999 required=5 tests=[AWL=-0.633, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AvIoadWi-8cQ for <wgchairs@ietfa.amsl.com>; Fri,  6 Apr 2012 11:18:18 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 92E6521F8585 for <wgchairs@ietf.org>; Fri,  6 Apr 2012 11:18:10 -0700 (PDT)
Received: by lbok13 with SMTP id k13so874212lbo.31 for <wgchairs@ietf.org>; Fri, 06 Apr 2012 11:18:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=4jlp1j9tynrzfmIqQ2Ustjw68MLOlOMCdkLyZWL/dHU=; b=nmPPI2iPDN1iF8VKBJ/xlec4bRP/telPGv/YVikYgEu0EILkVQT/up4bCBPOLd5Z70 Npycb9jPjh47p+bcC9SNZpogRGrwdtvwcDpD23t+EoasejrselwCTOBcyZgPt0z3wzMx nSOxbx9DWhvH8dJXtlfrf4emd3YXS84VDK98Ax2osAe7i+WWopiqXIFVXokdCsFsuvDe UW9RxxgkQP3CGyWmOMudWUcvv4s1wsviV9sAOW1gG3dqfeHfNsA81RdAbXopjubdDnII 4oA3joYnWJg1qLmn0j7le+oHypHzSxhER+pipIB0QYPfI7CmPMfOECPw5dDq8TrHUTkR l7hw==
Received: by 10.152.131.66 with SMTP id ok2mr9922797lab.10.1333736289562; Fri, 06 Apr 2012 11:18:09 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.152.21.162 with HTTP; Fri, 6 Apr 2012 11:17:49 -0700 (PDT)
In-Reply-To: <9452079D1A51524AA5749AD23E0039280CCFFE@exch-mbx901.corp.cloudmark.com>
References: <CAF4+nEGcB1oEH=dYhzJk7YVgzZ+O7dwyBqNdPMPAaCcyjEY-FQ@mail.gmail.com> <9452079D1A51524AA5749AD23E0039280CCFFE@exch-mbx901.corp.cloudmark.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 6 Apr 2012 14:17:49 -0400
Message-ID: <CAF4+nEGJij6Nrg2+w1KK7O1Xw5NgdcpMcx-4O0f3CMoBrd-HvQ@mail.gmail.com>
Subject: Re: pre-approving -00 drafts
To: "Murray S. Kucherawy" <msk@cloudmark.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Working Group Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Apr 2012 18:18:22 -0000

Hi Murray,

On Fri, Apr 6, 2012 at 1:38 PM, Murray S. Kucherawy <msk@cloudmark.com> wro=
te:
>> -----Original Message-----
>> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On Be=
half Of Donald Eastlake
>> Sent: Friday, April 06, 2012 10:16 AM
>> To: Working Group Chairs
>> Subject: pre-approving -00 drafts
>>
>> When I try to go to
>> https://datatracker.ietf.org/cgi-bin/wg/wg_init_rev_approval.cgi,
>> which, for example, is linked off the
>> http://www.ietf.org/wg/chairs-page.html Working Group Chairs' Page, I
>> seem to just get immediately re-directed to the datatracker. Is there
>> some new trick?
>
> After you log in to the datatracker, you should see an "Adopt in WG" link=
 for any document that's not a WG document. =A0I think that's the new way t=
o do it, via a "Call for Adoption" step. =A0However, I haven't actually tri=
ed it to see if, after that, it offers you a way to create -00 working grou=
p documents.

Well, if you click on that you then get to choose which of your WGs
you want to move towards adopting it and there is an ominous button
labeled "Call for adoption". Will that automatically post email to the
WG mailing list or something? And, at least through that stage, there
has been no opportunity to specify the file name for the WG draft
which might be different from the individual draft file name. And what
about drafts that start their life as a WG draft because they come out
of extensive discussions and consensus? As far as I know, there isn't
an IETF required process for making a draft a WG draft but one seems
to be assumed here...

I suppose if I get the WG draft version and this hasn't been
straightened out, I'll just ask internet-drafts to post it and note
that it replaces the individual version.

> We've discovered that you don't even get the "Adopt in WG" link if an ind=
ividual submission is in "AD is watching" state, so there are possibly mult=
iple obstacles here.
>
> The bug has been reported, but we haven't heard anything back yet.

Thanks,
Donald
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
=A0Donald E. Eastlake 3rd=A0=A0 +1-508-333-2270 (cell)
=A0155 Beaver Street,=A0Milford, MA 01757 USA
=A0d3e3e3@gmail.com

> -MSK

From msk@cloudmark.com  Fri Apr  6 11:25:55 2012
Return-Path: <msk@cloudmark.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 63D4221F8649 for <wgchairs@ietfa.amsl.com>; Fri,  6 Apr 2012 11:25:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.522
X-Spam-Level: 
X-Spam-Status: No, score=-102.522 tagged_above=-999 required=5 tests=[AWL=0.077, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QJnkS1PV1rky for <wgchairs@ietfa.amsl.com>; Fri,  6 Apr 2012 11:25:54 -0700 (PDT)
Received: from ht2-outbound.cloudmark.com (ht2-outbound.cloudmark.com [72.5.239.26]) by ietfa.amsl.com (Postfix) with ESMTP id CB4E721F8648 for <wgchairs@ietf.org>; Fri,  6 Apr 2012 11:25:54 -0700 (PDT)
Received: from EXCH-MBX901.corp.cloudmark.com ([fe80::addf:849a:f71c:4a82]) by exch-htcas902.corp.cloudmark.com ([fe80::54de:dc60:5f3e:334%10]) with mapi id 14.01.0355.002; Fri, 6 Apr 2012 11:25:54 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: Working Group Chairs <wgchairs@ietf.org>
Subject: RE: pre-approving -00 drafts
Thread-Topic: pre-approving -00 drafts
Thread-Index: AQHNFBj7J36BtCo76UWqNVgTgODkFZaOD2lggACA44D//4wb4A==
Date: Fri, 6 Apr 2012 18:25:54 +0000
Message-ID: <9452079D1A51524AA5749AD23E0039280CD127@exch-mbx901.corp.cloudmark.com>
References: <CAF4+nEGcB1oEH=dYhzJk7YVgzZ+O7dwyBqNdPMPAaCcyjEY-FQ@mail.gmail.com> <9452079D1A51524AA5749AD23E0039280CCFFE@exch-mbx901.corp.cloudmark.com> <CAF4+nEGJij6Nrg2+w1KK7O1Xw5NgdcpMcx-4O0f3CMoBrd-HvQ@mail.gmail.com>
In-Reply-To: <CAF4+nEGJij6Nrg2+w1KK7O1Xw5NgdcpMcx-4O0f3CMoBrd-HvQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.20.2.121]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Apr 2012 18:25:55 -0000

> -----Original Message-----
> From: Donald Eastlake [mailto:d3e3e3@gmail.com]
> Sent: Friday, April 06, 2012 11:18 AM
> To: Murray S. Kucherawy
> Cc: Working Group Chairs
> Subject: Re: pre-approving -00 drafts
>=20
> Well, if you click on that you then get to choose which of your WGs you
> want to move towards adopting it and there is an ominous button labeled
> "Call for adoption". Will that automatically post email to the WG
> mailing list or something? And, at least through that stage, there has
> been no opportunity to specify the file name for the WG draft which
> might be different from the individual draft file name. And what about
> drafts that start their life as a WG draft because they come out of
> extensive discussions and consensus? As far as I know, there isn't an
> IETF required process for making a draft a WG draft but one seems to be
> assumed here...
>=20
> I suppose if I get the WG draft version and this hasn't been
> straightened out, I'll just ask internet-drafts to post it and note
> that it replaces the individual version.

You're about where I am.  I'm tempted to post a dummy draft to use as a gui=
nea pig and walk it through the implicit datatracker process.  I have a wor=
king group about to shut down so the experiment wouldn't be too disruptive =
if I did it over there.

It would be nice if the tools team would explain or document this.  I was h=
oping they'd have talked about it in Paris, but then I didn't actually ask =
for that either.

But it is becoming a pain point that creating -00 documents is either not a=
vailable or not obvious right now.

-MSK


From housley@vigilsec.com  Tue Apr 17 12:00:19 2012
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 354A211E80F6 for <wgchairs@ietfa.amsl.com>; Tue, 17 Apr 2012 12:00:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.501
X-Spam-Level: 
X-Spam-Status: No, score=-102.501 tagged_above=-999 required=5 tests=[AWL=0.098, 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 4e4ZlfQ9sxlm for <wgchairs@ietfa.amsl.com>; Tue, 17 Apr 2012 12:00:16 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 31BC311E80EB for <wgchairs@ietf.org>; Tue, 17 Apr 2012 12:00:16 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id BBED2F2402F; Tue, 17 Apr 2012 15:00:37 -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 BUNeaKTTMCdI; Tue, 17 Apr 2012 15:00:05 -0400 (EDT)
Received: from [192.168.2.101] (pool-96-255-140-31.washdc.fios.verizon.net [96.255.140.31]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id E055BF24028; Tue, 17 Apr 2012 15:00:36 -0400 (EDT)
Subject: Formats for WG and BOF Agendas
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com>
Date: Tue, 17 Apr 2012 15:00:14 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com>
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com> <D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com> <B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com> <66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com>
To: IETF WG Chairs <wgchairs@ietf.org>
X-Mailer: Apple Mail (2.1084)
Cc: Ryan Cross <rcross@amsl.com>, 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: Tue, 17 Apr 2012 19:00:19 -0000

Some WG and BOF chairs have been posting agendas in many different =
formats, including text, html, pdf, ppt, and pptx.  Until recently, only =
.txt and .html files were supported  for session minutes and agendas.  =
In fact the support for the other formats was never announced, but you =
guys found the new capability without any announcement.

Magnus Westerlund has asked that links to meeting agendas and minutes be =
long-term persistent.  He would like a URL that works regardless of the =
format.  I support this request, and the Secretariat tells me that it =
would not difficult to support, especially if text and html are the only =
formats that we accept.  It is possible to make this approach work for =
PDF and PPT files as well, but the Secretariat feels that .txt and .html =
files integrate into the website better than the other formats.  In =
addition, Henrik points out that the use of PDF and PPT files will make =
it harder to provide inline agendas in the Datatracker.

I propose that we to revert to supporting only .txt and .html file types =
for session minutes and agendas.  Then, using Apache's content =
negotiation, the Secretariat can link to them with an extension-less =
URL.  Apache will set the appropriate content-type.  This way the URLs =
will be persistent and consistent across supported file formats.

Does anyone have concerns with the proposed way forward?

Russ


From jgs@bgp.nu  Tue Apr 17 12:42:53 2012
Return-Path: <jgs@bgp.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 A56C721F843A for <wgchairs@ietfa.amsl.com>; Tue, 17 Apr 2012 12:42:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.647
X-Spam-Level: 
X-Spam-Status: No, score=-100.647 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_IS_SMALL6=0.556, 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 ZTUfZ97f9vxE for <wgchairs@ietfa.amsl.com>; Tue, 17 Apr 2012 12:42:53 -0700 (PDT)
Received: from bgp.nu (bgp.nu [147.28.0.53]) by ietfa.amsl.com (Postfix) with ESMTP id 937C421F8437 for <wgchairs@ietf.org>; Tue, 17 Apr 2012 12:42:49 -0700 (PDT)
Received: from [10.27.244.220] (mobile-166-147-098-135.mycingular.net [166.147.98.135]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by bgp.nu (Postfix) with ESMTP id D5EEC66D373; Tue, 17 Apr 2012 15:42:48 -0400 (EDT)
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com> <D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com> <B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com> <66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com> <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com>
In-Reply-To: <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <E455982B-58F6-4127-98A9-E806C87F4100@bgp.nu>
X-Mailer: iPhone Mail (9A405)
From: "John G. Scudder" <jgs@bgp.nu>
Subject: Re: Formats for WG and BOF Agendas
Date: Tue, 17 Apr 2012 15:42:43 -0400
To: Russ Housley <housley@vigilsec.com>
Cc: IETF WG Chairs <wgchairs@ietf.org>, Ryan Cross <rcross@amsl.com>, 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: Tue, 17 Apr 2012 19:42:53 -0000

On Apr 17, 2012, at 3:00 PM, Russ Housley <housley@vigilsec.com> wrote:

> I propose that we to revert to supporting only .txt and .html file types f=
or session minutes and agendas.  Then, using Apache's content negotiation, t=
he Secretariat can link to them with an extension-less URL.  Apache will set=
 the appropriate content-type.  This way the URLs will be persistent and con=
sistent across supported file formats.
>=20
> Does anyone have concerns with the proposed way forward?

Au contraire, sounds like a fine thing.=20

--John=

From kodonog@gmail.com  Tue Apr 17 12:48:17 2012
Return-Path: <kodonog@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 6190321F8474 for <wgchairs@ietfa.amsl.com>; Tue, 17 Apr 2012 12:48:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8av2bG5hCP9Y for <wgchairs@ietfa.amsl.com>; Tue, 17 Apr 2012 12:48:16 -0700 (PDT)
Received: from mail-qa0-f42.google.com (mail-qa0-f42.google.com [209.85.216.42]) by ietfa.amsl.com (Postfix) with ESMTP id C88D021F8458 for <wgchairs@ietf.org>; Tue, 17 Apr 2012 12:48:16 -0700 (PDT)
Received: by qafi31 with SMTP id i31so748332qaf.15 for <wgchairs@ietf.org>; Tue, 17 Apr 2012 12:48:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=PVuNA2HegYvdK8v19cI5GYhHFr+5TONvIHl5fffnNRc=; b=sTrZfh93yscsM9/xUHxvXPq07TLizGR34VQF7+dNIaLWfxMl2wYh+VAZXxyD+vPkRQ O14NzCvPkI2kWLVBBiKxeqLpgMT/ZrzysZxS/LS1otgE6E8+9L9coQKuuyZoefMk6tYd lRIRcNmzQtQmV9Fb5IMFehij74la2yudpIkMfnvDXw5SN3dKBcl6TTDPTwM6hE6Wbisd IF8BWsN2gx4g5df4n+eEfsqkhMmVG6/tOfeFmu1ZFY+c3n2BDSwYij9agbNaWVDevXsy DqoIKTnakHFzsJzmbKQChfKViA8svJU0EENW3pPvkAeKjH4BAypYuML//s6Uj4K3o6rS pU+w==
Received: by 10.229.75.139 with SMTP id y11mr7008536qcj.69.1334692096354; Tue, 17 Apr 2012 12:48:16 -0700 (PDT)
Received: from kodonog-mac.local (d-74-214-48-204.cpe.metrocast.net. [74.214.48.204]) by mx.google.com with ESMTPS id cv8sm41867221qab.12.2012.04.17.12.48.14 (version=SSLv3 cipher=OTHER); Tue, 17 Apr 2012 12:48:15 -0700 (PDT)
Sender: Karen ODonoghue <kodonog@gmail.com>
Message-ID: <4F8DC8FE.4070906@pobox.com>
Date: Tue, 17 Apr 2012 15:48:14 -0400
From: Karen O'Donoghue <kodonog@pobox.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: Formats for WG and BOF Agendas
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com> <D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com> <B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com> <66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com> <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com> <E455982B-58F6-4127-98A9-E806C87F4100@bgp.nu>
In-Reply-To: <E455982B-58F6-4127-98A9-E806C87F4100@bgp.nu>
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
Reply-To: kodonog@pobox.com
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Apr 2012 19:48:17 -0000

Sounds fine to me as well...

Karen

On 4/17/12 3:42 PM, John G. Scudder wrote:
> On Apr 17, 2012, at 3:00 PM, Russ Housley<housley@vigilsec.com>  wrote:
>
>> I propose that we to revert to supporting only .txt and .html file types for session minutes and agendas.  Then, using Apache's content negotiation, the Secretariat can link to them with an extension-less URL.  Apache will set the appropriate content-type.  This way the URLs will be persistent and consistent across supported file formats.
>>
>> Does anyone have concerns with the proposed way forward?
> Au contraire, sounds like a fine thing.
>
> --John


From adam@nostrum.com  Tue Apr 17 12:49:12 2012
Return-Path: <adam@nostrum.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 188F821F8496 for <wgchairs@ietfa.amsl.com>; Tue, 17 Apr 2012 12:49:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.251
X-Spam-Level: 
X-Spam-Status: No, score=-102.251 tagged_above=-999 required=5 tests=[AWL=0.349, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hEoYMfBXRYT6 for <wgchairs@ietfa.amsl.com>; Tue, 17 Apr 2012 12:49:11 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 788FA21F848E for <wgchairs@ietf.org>; Tue, 17 Apr 2012 12:49:11 -0700 (PDT)
Received: from hydra-en0.roach.at (99-152-144-32.lightspeed.dllstx.sbcglobal.net [99.152.144.32]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q3HJn7ID050037 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 17 Apr 2012 14:49:08 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <4F8DC932.1000607@nostrum.com>
Date: Tue, 17 Apr 2012 14:49:06 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: Formats for WG and BOF Agendas
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com> <D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com> <B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com> <66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com> <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com>
In-Reply-To: <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 99.152.144.32 is authenticated by a trusted mechanism)
Cc: IETF WG Chairs <wgchairs@ietf.org>, Ryan Cross <rcross@amsl.com>, 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: Tue, 17 Apr 2012 19:49:12 -0000

On 4/17/12 14:00, Apr 17, Russ Housley wrote:
> I propose that we to revert to supporting only .txt and .html file types for session minutes and agendas.  Then, using Apache's content negotiation, the Secretariat can link to them with an extension-less URL.  Apache will set the appropriate content-type.  This way the URLs will be persistent and consistent across supported file formats.
>
> Does anyone have concerns with the proposed way forward?

Speaking as a chair who works on the tools during code sprints (and 
agenda-related tools in particular), I _strongly_ support the proposal 
to re-impose the restriction that agendas can be text and HTML only.

/a

From john-ietf@jck.com  Tue Apr 17 13:19:26 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07A3011E80C5 for <wgchairs@ietfa.amsl.com>; Tue, 17 Apr 2012 13:19:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.481
X-Spam-Level: 
X-Spam-Status: No, score=-102.481 tagged_above=-999 required=5 tests=[AWL=0.118, 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 TITr3Vn3kyf0 for <wgchairs@ietfa.amsl.com>; Tue, 17 Apr 2012 13:19:25 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 72AA211E80BA for <wgchairs@ietf.org>; Tue, 17 Apr 2012 13:19:25 -0700 (PDT)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SKEmg-000Otq-Hd; Tue, 17 Apr 2012 16:13:54 -0400
Date: Tue, 17 Apr 2012 16:19:16 -0400
From: John C Klensin <john-ietf@jck.com>
To: Russ Housley <housley@vigilsec.com>, IETF WG Chairs <wgchairs@ietf.org>
Subject: Re: Formats for WG and BOF Agendas
Message-ID: <89E33405ACD4F8D85C8BF282@PST.JCK.COM>
In-Reply-To: <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com>
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com> <D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com> <B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com> <66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com> <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: Ryan Cross <rcross@amsl.com>, 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: Tue, 17 Apr 2012 20:19:26 -0000

--On Tuesday, April 17, 2012 15:00 -0400 Russ Housley
<housley@vigilsec.com> wrote:

> Some WG and BOF chairs have been posting agendas in many
> different formats, including text, html, pdf, ppt, and pptx.
> Until recently, only .txt and .html files were supported  for
> session minutes and agendas.  In fact the support for the
> other formats was never announced, but you guys found the new
> capability without any announcement.
> 
> Magnus Westerlund has asked that links to meeting agendas and
> minutes be long-term persistent.  He would like a URL that
> works regardless of the format.  I support this request, and
> the Secretariat tells me that it would not difficult to
> support, especially if text and html are the only formats that
> we accept.  It is possible to make this approach work for PDF
> and PPT files as well, but the Secretariat feels that .txt and
> .html files integrate into the website better than the other
> formats.  In addition, Henrik points out that the use of PDF
> and PPT files will make it harder to provide inline agendas in
> the Datatracker.
> 
> I propose that we to revert to supporting only .txt and .html
> file types for session minutes and agendas.  Then, using
> Apache's content negotiation, the Secretariat can link to them
> with an extension-less URL.  Apache will set the appropriate
> content-type.  This way the URLs will be persistent and
> consistent across supported file formats.

Russ, while I think we can safely do without PPT (or anything
else proprietary), I'm concerned that prohibiting PDF would
accidentally prevent the use of artwork when artwork is
appropriate.  I think that is especially a matter of concern if
this principle and format limitation were in the future to be
expanded to minutes.  Now, perhaps we don't need artwork/ images
in agendas: if everyone else is comfortable with that, then I am
too and have no objection to restricting them to plain text and
simple (one file) HTML.

best,
    john


From kent@bbn.com  Tue Apr 17 13:26:31 2012
Return-Path: <kent@bbn.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 661DF21F844F for <wgchairs@ietfa.amsl.com>; Tue, 17 Apr 2012 13:26:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.579
X-Spam-Level: 
X-Spam-Status: No, score=-106.579 tagged_above=-999 required=5 tests=[AWL=0.020, 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 EhcjAWXmBP78 for <wgchairs@ietfa.amsl.com>; Tue, 17 Apr 2012 13:26:31 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfa.amsl.com (Postfix) with ESMTP id E511021F844D for <wgchairs@ietf.org>; Tue, 17 Apr 2012 13:26:30 -0700 (PDT)
Received: from dhcp89-089-239.bbn.com ([128.89.89.239]:49221) by smtp.bbn.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1SKEyW-000HfD-68; Tue, 17 Apr 2012 16:26:08 -0400
Mime-Version: 1.0
Message-Id: <p0624081acbb37eea9a3b@[128.89.89.239]>
In-Reply-To: <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com>
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com> <D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com> <B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com> <66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com> <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com>
Date: Tue, 17 Apr 2012 16:15:55 -0400
To: Russ Housley <housley@vigilsec.com>
From: Stephen Kent <kent@bbn.com>
Subject: Re: Formats for WG and BOF Agendas
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Cc: IETF WG Chairs <wgchairs@ietf.org>, Ryan Cross <rcross@amsl.com>, 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: Tue, 17 Apr 2012 20:26:31 -0000

At 3:00 PM -0400 4/17/12, Russ Housley wrote:
>...
>
>Does anyone have concerns with the proposed way forward?
>
>Russ

I have no problem with text or HTML agendas.  As for minutes, I used
to always provide HTML, but have found that MS Word produces output
that is hard for me to control, and is somewhat unpredictable. I posted
minutes as PDF this time and found the result was much more predictable.

Steve

From jmpolk@cisco.com  Tue Apr 17 14:22:43 2012
Return-Path: <jmpolk@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A98FC11E80C5 for <wgchairs@ietfa.amsl.com>; Tue, 17 Apr 2012 14:22:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.396
X-Spam-Level: 
X-Spam-Status: No, score=-110.396 tagged_above=-999 required=5 tests=[AWL=0.203, 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 ah5LzRu1PqAB for <wgchairs@ietfa.amsl.com>; Tue, 17 Apr 2012 14:22:39 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id A256611E80B2 for <wgchairs@ietf.org>; Tue, 17 Apr 2012 14:22:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jmpolk@cisco.com; l=723; q=dns/txt; s=iport; t=1334697756; x=1335907356; h=message-id:date:to:from:subject:in-reply-to:references: mime-version; bh=o6NC3fl8OZCN9BNJCxYLLjd4Jdr3z//xnQbThHvK5+E=; b=Hk5nZrBI7PCHgZL+WAAW2dM58BnjVhZtNeMj7aIL8grcpl5r3ovukMSb lKk/dUY5MpNqFUZOOEuE4PPaGaXK1ea//OEhieo/+LOYPNd+CJxHHHzgo cmZwVGEYJo7QdVPrigMyecz9lnvaWdpsTI0ANGl2+FcwBFzk6ONanPyDY o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ak4GAOrdjU+rRDoI/2dsb2JhbABEr0eBdoEHggkBAQEEEgElAk8HBBgeEBk+BxIih2uZfp95kGMEiFybYIFpgwU
X-IronPort-AV: E=Sophos;i="4.75,438,1330905600"; d="scan'208";a="37869997"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-1.cisco.com with ESMTP; 17 Apr 2012 21:22:36 +0000
Received: from jmpolk-wxp01.cisco.com (rcdn-jmpolk-8711.cisco.com [10.99.80.18]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id q3HLMZ4o021505; Tue, 17 Apr 2012 21:22:36 GMT
Message-Id: <201204172122.q3HLMZ4o021505@mtv-core-3.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 17 Apr 2012 16:22:35 -0500
To: kodonog@pobox.com, wgchairs@ietf.org
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: Formats for WG and BOF Agendas
In-Reply-To: <4F8DC8FE.4070906@pobox.com>
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com> <D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com> <B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com> <66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com> <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com> <E455982B-58F6-4127-98A9-E806C87F4100@bgp.nu> <4F8DC8FE.4070906@pobox.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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, 17 Apr 2012 21:22:44 -0000

good idea

At 02:48 PM 4/17/2012, Karen O'Donoghue wrote:
>Sounds fine to me as well...
>
>Karen
>
>On 4/17/12 3:42 PM, John G. Scudder wrote:
>>On Apr 17, 2012, at 3:00 PM, Russ Housley<housley@vigilsec.com>  wrote:
>>
>>>I propose that we to revert to supporting only .txt and .html file 
>>>types for session minutes and agendas.  Then, using Apache's 
>>>content negotiation, the Secretariat can link to them with an 
>>>extension-less URL.  Apache will set the appropriate 
>>>content-type.  This way the URLs will be persistent and consistent 
>>>across supported file formats.
>>>
>>>Does anyone have concerns with the proposed way forward?
>>Au contraire, sounds like a fine thing.
>>
>>--John


From glenzorn@gmail.com  Tue Apr 17 18:55:55 2012
Return-Path: <glenzorn@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 2412D11E80E5 for <wgchairs@ietfa.amsl.com>; Tue, 17 Apr 2012 18:55:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pbbA0kElSRwE for <wgchairs@ietfa.amsl.com>; Tue, 17 Apr 2012 18:55:54 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 93E0B11E80E3 for <wgchairs@ietf.org>; Tue, 17 Apr 2012 18:55:54 -0700 (PDT)
Received: by obbwd20 with SMTP id wd20so5177024obb.31 for <wgchairs@ietf.org>; Tue, 17 Apr 2012 18:55:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=E04CAAvWvryqeWn7Em25oo+9AkPrdhS84AlRk1VfCgA=; b=fFST1y/Is1EoRPXq9zbXUuQ/B5qYZCovHnGu4RFyOY1ReNPUBXs2QfLnTeLaKcI/p5 b+KFLWVP+e8VnFR7iu5rcJq79lzeG+OayJT9c0s41YmreuYGChElAJAhTRlIgFF3sih4 9eC4cdkdyb2tcaQzdgyk7DFL8Gjg2ivFHzKrxXsSTXMbMVTFKJRdl1+YPoRCblBG3hGn W7gfj12T6V4tXpZmK86KJKd2djwc51Vl0uWA4lrsmGixEQbuHimhRAnjbfmykLlGDM+K IuUyWrxubeuQ2R2Qh7JuMoqZ1NQA1qAs+kbTHH9BDL/Nps3mip9jfEnlw5adEho0PfG4 xWUA==
Received: by 10.182.122.4 with SMTP id lo4mr541332obb.24.1334714150596; Tue, 17 Apr 2012 18:55:50 -0700 (PDT)
Received: from [192.168.1.98] (ppp-171-96-15-147.revip8.asianet.co.th. [171.96.15.147]) by mx.google.com with ESMTPS id h5sm25276019oba.17.2012.04.17.18.55.46 (version=SSLv3 cipher=OTHER); Tue, 17 Apr 2012 18:55:49 -0700 (PDT)
Message-ID: <4F8E1F20.8040207@gmail.com>
Date: Wed, 18 Apr 2012 08:55:44 +0700
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120318 Thunderbird/11.0
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: Formats for WG and BOF Agendas
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com> <D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com> <B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com> <66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com> <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com>
In-Reply-To: <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF WG Chairs <wgchairs@ietf.org>, Ryan Cross <rcross@amsl.com>, 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, 18 Apr 2012 01:55:55 -0000

On 04/18/2012 02:00 AM, Russ Housley wrote:
> Some WG and BOF chairs have been posting agendas in many different formats, including text, html, pdf, ppt, and pptx.  Until recently, only .txt and .html files were supported  for session minutes and agendas.  In fact the support for the other formats was never announced, but you guys found the new capability without any announcement.
>
> Magnus Westerlund has asked that links to meeting agendas and minutes be long-term persistent.  He would like a URL that works regardless of the format.  I support this request, and the Secretariat tells me that it would not difficult to support, especially if text and html are the only formats that we accept.  It is possible to make this approach work for PDF and PPT files as well, but the Secretariat feels that .txt and .html files integrate into the website better than the other formats.  In addition, Henrik points out that the use of PDF and PPT files will make it harder to provide inline agendas in the Datatracker.
>
> I propose that we to revert to supporting only .txt and .html file types for session minutes and agendas.  Then, using Apache's content negotiation, the Secretariat can link to them with an extension-less URL.  Apache will set the appropriate content-type.  This way the URLs will be persistent and consistent across supported file formats.
>
> Does anyone have concerns with the proposed way forward?

Seems perfectly reasonable to me (less is more!).

>
> Russ
>


From yaakov_s@rad.com  Tue Apr 17 22:03:49 2012
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 5073D21F85A4 for <wgchairs@ietfa.amsl.com>; Tue, 17 Apr 2012 22:03:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.587
X-Spam-Level: 
X-Spam-Status: No, score=-102.587 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, 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 DiM489Cpok3G for <wgchairs@ietfa.amsl.com>; Tue, 17 Apr 2012 22:03:47 -0700 (PDT)
Received: from rad.co.il (mailrelay02.rad.co.il [62.0.23.237]) by ietfa.amsl.com (Postfix) with ESMTP id D991521F8592 for <wgchairs@ietf.org>; Tue, 17 Apr 2012 22:03:45 -0700 (PDT)
Received: from Internal Mail-Server by MailRelay02 (envelope-from yaakov?s@rad.com) with AES128-SHA encrypted SMTP; 18 Apr 2012 07:50:09 +0300
Received: from EXRAD5.ad.rad.co.il ([192.114.24.28]) by EXRAD5.ad.rad.co.il ([192.114.24.28]) with mapi id 14.01.0323.003; Wed, 18 Apr 2012 08:03:43 +0300
From: Yaakov Stein <yaakov_s@rad.com>
To: Russ Housley <housley@vigilsec.com>, IETF WG Chairs <wgchairs@ietf.org>
Subject: RE: Formats for WG and BOF Agendas
Thread-Topic: Formats for WG and BOF Agendas
Thread-Index: AQHNHMx3ZRwCxvaQWEueKCwmFhNlepagBiIg
Date: Wed, 18 Apr 2012 05:03:42 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC904373362@EXRAD5.ad.rad.co.il>
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com> <D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com> <B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com> <66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com> <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com>
In-Reply-To: <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.17.140.53]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Commtouch-Refid: str=0001.0A020201.4F8E4B30.0017,ss=1,fgs=0
Cc: Ryan Cross <rcross@amsl.com>, 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, 18 Apr 2012 05:03:49 -0000

I can easily go along with plain text for agendas.
In general, topics for discussion should be describable in plain text.

However, minutes may need diagrams, equations, international characters, et=
c.

Minutes should only be required to conform to the same format as RFCs.
For the time being this means pure text
(and thus the tools will work and the content will be as persistent as RFCs=
 are).
However, if we do eventually decide on some new format for RFCs
then minutes would immediately be able to enjoy the new capabilities.

Y(J)S

-----Original Message-----
From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On Behal=
f Of Russ Housley
Sent: Tuesday, April 17, 2012 22:00
To: IETF WG Chairs
Cc: Ryan Cross; Henrik Levkowetz
Subject: Formats for WG and BOF Agendas

Some WG and BOF chairs have been posting agendas in many different formats,=
 including text, html, pdf, ppt, and pptx.  Until recently, only .txt and .=
html files were supported  for session minutes and agendas.  In fact the su=
pport for the other formats was never announced, but you guys found the new=
 capability without any announcement.

Magnus Westerlund has asked that links to meeting agendas and minutes be lo=
ng-term persistent.  He would like a URL that works regardless of the forma=
t.  I support this request, and the Secretariat tells me that it would not =
difficult to support, especially if text and html are the only formats that=
 we accept.  It is possible to make this approach work for PDF and PPT file=
s as well, but the Secretariat feels that .txt and .html files integrate in=
to the website better than the other formats.  In addition, Henrik points o=
ut that the use of PDF and PPT files will make it harder to provide inline =
agendas in the Datatracker.

I propose that we to revert to supporting only .txt and .html file types fo=
r session minutes and agendas.  Then, using Apache's content negotiation, t=
he Secretariat can link to them with an extension-less URL.  Apache will se=
t the appropriate content-type.  This way the URLs will be persistent and c=
onsistent across supported file formats.

Does anyone have concerns with the proposed way forward?

Russ


From melinda.shore@gmail.com  Tue Apr 17 22:08:03 2012
Return-Path: <melinda.shore@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 212F721F85D8 for <wgchairs@ietfa.amsl.com>; Tue, 17 Apr 2012 22:08:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zNjV7TGmG7Qn for <wgchairs@ietfa.amsl.com>; Tue, 17 Apr 2012 22:08:02 -0700 (PDT)
Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by ietfa.amsl.com (Postfix) with ESMTP id 9797E21F85D7 for <wgchairs@ietf.org>; Tue, 17 Apr 2012 22:08:02 -0700 (PDT)
Received: by dady13 with SMTP id y13so12848219dad.27 for <wgchairs@ietf.org>; Tue, 17 Apr 2012 22:08:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=3e8yEg9Wheq2vzOKnk6E1A67fDUhVLdjG4Yc6YOBHuI=; b=njf1dEcs6XX+62xyqHVLoq36OsfZ1Mh0WsmGufKMtSUOHt5v0dam07JuIARyYzVkaF XN4Hr3XNAHo6ZBLXIb0Rfz0laMN0vNorRZhQsMBsiwa5f3tEd1HQf67kEkwTO11QeTxy Spjj2jrfJjPALsjbUkFTKv/D4LM41TyfewgQtxSQgR++NI+bK81QwZWsMz9+hEMc6hhf 4NPkOZHMKScQ3APVLhbZzVEpyRIR0feQcxL9T3chRJQtGB0T7CqIu8ykHBM1LJy728Zc Wlawf7i1FOZVqRwyfLnEi1L7jHNtbzTEcztm7PNsff7bkizPMx9IH97Q5g3+ZLAjMlgc gpkA==
Received: by 10.68.134.8 with SMTP id pg8mr3079153pbb.152.1334725682299; Tue, 17 Apr 2012 22:08:02 -0700 (PDT)
Received: from polypro.local (66-230-81-245-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.81.245]) by mx.google.com with ESMTPS id nt3sm22694016pbc.14.2012.04.17.22.08.00 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 17 Apr 2012 22:08:01 -0700 (PDT)
Message-ID: <4F8E4C2F.4080000@gmail.com>
Date: Tue, 17 Apr 2012 21:07:59 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: Formats for WG and BOF Agendas
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com> <D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com> <B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com> <66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com> <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com> <07F7D7DED63154409F13298786A2ADC904373362@EXRAD5.ad.rad.co.il>
In-Reply-To: <07F7D7DED63154409F13298786A2ADC904373362@EXRAD5.ad.rad.co.il>
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: Wed, 18 Apr 2012 05:08:03 -0000

On 4/17/12 9:03 PM, Yaakov Stein wrote:
> Minutes should only be required to conform to the same format as RFCs.
> For the time being this means pure text
> (and thus the tools will work and the content will be as persistent as RFCs are).
> However, if we do eventually decide on some new format for RFCs
> then minutes would immediately be able to enjoy the new capabilities.

This is outside the scope of the question (to which my answer is
"Yay!"), but I have to say that as a matter of general principle,
anything that makes it slower and/or more work to get minutes out
is not a good thing.

Melinda


From salvatore.loreto@ericsson.com  Tue Apr 17 22:55:39 2012
Return-Path: <salvatore.loreto@ericsson.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7535521F85FD for <wgchairs@ietfa.amsl.com>; Tue, 17 Apr 2012 22:55:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.661
X-Spam-Level: 
X-Spam-Status: No, score=-106.661 tagged_above=-999 required=5 tests=[AWL=-0.412, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6PSoSnk35gDc for <wgchairs@ietfa.amsl.com>; Tue, 17 Apr 2012 22:55:39 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id B700D21F84EA for <wgchairs@ietf.org>; Tue, 17 Apr 2012 22:55:38 -0700 (PDT)
X-AuditID: c1b4fb25-b7b18ae000000dce-4d-4f8e5758f89b
Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 18.C0.03534.8575E8F4; Wed, 18 Apr 2012 07:55:37 +0200 (CEST)
Received: from mail.lmf.ericsson.se (153.88.115.8) by esessmw0191.eemea.ericsson.se (153.88.115.85) with Microsoft SMTP Server id 8.3.213.0; Wed, 18 Apr 2012 07:55:36 +0200
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3])	by mail.lmf.ericsson.se (Postfix) with ESMTP id 8CC6B2325	for <wgchairs@ietf.org>; Wed, 18 Apr 2012 08:55:36 +0300 (EEST)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 920F552606	for <wgchairs@ietf.org>; Wed, 18 Apr 2012 08:55:36 +0300 (EEST)
Received: from n106.nomadiclab.com (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 4C9445238E	for <wgchairs@ietf.org>; Wed, 18 Apr 2012 08:55:36 +0300 (EEST)
Message-ID: <4F8E5757.2070307@ericsson.com>
Date: Wed, 18 Apr 2012 08:55:35 +0300
From: Salvatore Loreto <salvatore.loreto@ericsson.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: Formats for WG and BOF Agendas
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com> <D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com> <B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com> <66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com> <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com>
In-Reply-To: <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Brightmail-Tracker: AAAAAA==
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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, 18 Apr 2012 05:55:39 -0000

On 4/17/12 10:00 PM, Russ Housley wrote:
> Some WG and BOF chairs have been posting agendas in many different formats, including text, html, pdf, ppt, and pptx.  Until recently, only .txt and .html files were supported  for session minutes and agendas.  In fact the support for the other formats was never announced, but you guys found the new capability without any announcement.
>
> Magnus Westerlund has asked that links to meeting agendas and minutes be long-term persistent.  He would like a URL that works regardless of the format.  I support this request, and the Secretariat tells me that it would not difficult to support, especially if text and html are the only formats that we accept.  It is possible to make this approach work for PDF and PPT files as well, but the Secretariat feels that .txt and .html files integrate into the website better than the other formats.  In addition, Henrik points out that the use of PDF and PPT files will make it harder to provide inline agendas in the Datatracker.
>
> I propose that we to revert to supporting only .txt and .html file types for session minutes and agendas.  Then, using Apache's content negotiation, the Secretariat can link to them with an extension-less URL.  Apache will set the appropriate content-type.  This way the URLs will be persistent and consistent across supported file formats.
>
> Does anyone have concerns with the proposed way forward?
>
> Russ
>
I support the proposal

/Sal


From lars@netapp.com  Wed Apr 18 01:49:48 2012
Return-Path: <lars@netapp.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A4E921F85C6 for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 01:49:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.774
X-Spam-Level: 
X-Spam-Status: No, score=-10.774 tagged_above=-999 required=5 tests=[AWL=-0.175, 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 7-7B5K2sGYAN for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 01:49:48 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by ietfa.amsl.com (Postfix) with ESMTP id 0724B21F8539 for <wgchairs@ietf.org>; Wed, 18 Apr 2012 01:49:48 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.75,441,1330934400";  d="p7s'?scan'208";a="641716767"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx2-out.netapp.com with ESMTP; 18 Apr 2012 01:49:32 -0700
Received: from vmwexceht04-prd.hq.netapp.com (vmwexceht04-prd.hq.netapp.com [10.106.77.34]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id q3I8nWoS004504; Wed, 18 Apr 2012 01:49:32 -0700 (PDT)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.117]) by vmwexceht04-prd.hq.netapp.com ([10.106.77.34]) with mapi id 14.02.0247.003; Wed, 18 Apr 2012 01:49:32 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: "wgchairs@ietf.org" <wgchairs@ietf.org>, Internet Research Steering Group <irsg@irtf.org>
Subject: latest missing replaced-by information
Thread-Topic: latest missing replaced-by information
Thread-Index: AQHNHUArfc1edZEOVEayFUwcFf7CfQ==
Date: Wed, 18 Apr 2012 08:49:31 +0000
Message-ID: <E9354164-6546-42A9-BAC4-BE6660855AE9@netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: multipart/signed; boundary="Apple-Mail=_807F4516-3BB2-4959-A490-29CC282BDECA"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Apr 2012 08:49:48 -0000

--Apple-Mail=_807F4516-3BB2-4959-A490-29CC282BDECA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

here's yet another installment in the series of reports on potentially =
missing "replaced-by" relationships in the IETF datatracker.

*** NEW *** Also includes IRTF documents now.

WG and RG chairs are encouraged to check whether these are accurate for =
their groups, and if so, send a ticket to the secretariat instructing =
them to "record in the database that draft X replaced draft Y".

As always, double-check before reporting to the secretariat. Also, see =
list of possible inconsistencies at the end of the report.

(Note that the IPR disclosure search tool uses these replaced-by =
relationships, so keeping them up-to-date is actually useful and not =
just WG hygiene.)

Lars


-----------------------------------------------------------------
APP Area
-----------------------------------------------------------------
CORE Working Group, APP Area
   draft-rahman-core-groupcomm POTENTIALLY REPLACED BY =
draft-ietf-core-groupcomm

EAI Working Group, APP Area
   draft-duerst-eai-mailto POTENTIALLY REPLACED BY draft-ietf-eai-mailto
   draft-yao-eai-rfc5336bis POTENTIALLY REPLACED BY =
draft-ietf-eai-rfc5336bis

PAWS Working Group, APP Area
   draft-probasco-paws-problem-stmt-usecases-rqmts POTENTIALLY REPLACED =
BY draft-ietf-paws-problem-stmt-usecases-rqmts

VCARDDAV Working Group, APP Area
   draft-cauchie-vcarddav-oma-cab-extensions POTENTIALLY REPLACED BY =
draft-ietf-vcarddav-oma-cab-extensions

-----------------------------------------------------------------
CONCLUDED Area
-----------------------------------------------------------------
ATOMPUB Working Group, CONCLUDED Area
   draft-snell-atompub-autodiscovery POTENTIALLY REPLACED BY =
draft-ietf-atompub-autodiscovery

HTTP Working Group, CONCLUDED Area
   draft-wallis-http-digest-auth-a3a8 POTENTIALLY REPLACED BY =
draft-ietf-http-digest-auth-a3a8

IDNABIS Working Group, CONCLUDED Area
   draft-faltstrom-idnabis-tables POTENTIALLY REPLACED BY =
draft-ietf-idnabis-tables

IMAP Working Group, CONCLUDED Area
   draft-crispin-imap-compat POTENTIALLY REPLACED BY =
draft-ietf-imap-compat

TFTPEXTS Working Group, CONCLUDED Area
   draft-malkin-tftpexts-blksize-opt POTENTIALLY REPLACED BY =
draft-ietf-tftpexts-blksize-opt
   draft-malkin-tftpexts-option-ext POTENTIALLY REPLACED BY =
draft-ietf-tftpexts-option-ext
   draft-malkin-tftpexts-options POTENTIALLY REPLACED BY =
draft-ietf-tftpexts-options

XMPP Working Group, CONCLUDED Area
   draft-barnes-xmpp-dna POTENTIALLY REPLACED BY draft-ietf-xmpp-dna
   draft-miller-xmpp-e2e POTENTIALLY REPLACED BY draft-ietf-xmpp-e2e
   draft-saintandre-xmpp-6122bis POTENTIALLY REPLACED BY =
draft-ietf-xmpp-6122bis

MIPSHOP Working Group, CONCLUDED Area
   draft-xia-mipshop-fmip-ptp POTENTIALLY REPLACED BY =
draft-ietf-mipshop-fmip-ptp

NETLMM Working Group, CONCLUDED Area
   draft-cui-netlmm-mip-interactions POTENTIALLY REPLACED BY =
draft-ietf-netlmm-mip-interactions
   draft-glenn-netlmm-pmipv6-mib POTENTIALLY REPLACED BY =
draft-ietf-netlmm-pmipv6-mib
   draft-korhonen-netlmm-lma-discovery POTENTIALLY REPLACED BY =
draft-ietf-netlmm-lma-discovery
   draft-xia-netlmm-lma-discovery POTENTIALLY REPLACED BY =
draft-ietf-netlmm-lma-discovery

SEND Working Group, CONCLUDED Area
   draft-arkko-send-cga POTENTIALLY REPLACED BY draft-ietf-send-cga
   draft-arkko-send-ndopt POTENTIALLY REPLACED BY draft-ietf-send-ndopt

SHIM6 Working Group, CONCLUDED Area
   draft-garcia-shim6-applicability POTENTIALLY REPLACED BY =
draft-ietf-shim6-applicability

CAPWAP Working Group, CONCLUDED Area
   draft-yangshi-capwap-802dot11-mib POTENTIALLY REPLACED BY =
draft-ietf-capwap-802dot11-mib
   draft-yangshi-capwap-base-mib POTENTIALLY REPLACED BY =
draft-ietf-capwap-base-mib

RMONMIB Working Group, CONCLUDED Area
   draft-bierman-rmonmib-hc-alarm-mib POTENTIALLY REPLACED BY =
draft-ietf-rmonmib-hc-alarm-mib

MEGACO Working Group, CONCLUDED Area
   draft-blatherwick-megaco-ipphone POTENTIALLY REPLACED BY =
draft-ietf-megaco-ipphone

SIGTRAN Working Group, CONCLUDED Area
   draft-anil-sigtran-dua POTENTIALLY REPLACED BY draft-ietf-sigtran-dua

SIP Working Group, CONCLUDED Area
   draft-arkko-sip-sec-agree POTENTIALLY REPLACED BY =
draft-ietf-sip-sec-agree
   draft-biggs-sip-replaces POTENTIALLY REPLACED BY =
draft-ietf-sip-replaces
   draft-pashalidis-sip-saml POTENTIALLY REPLACED BY draft-ietf-sip-saml

SIPPING Working Group, CONCLUDED Area
   draft-drage-sipping-service-identification POTENTIALLY REPLACED BY =
draft-ietf-sipping-service-identification
   draft-elwell-sipping-update-pai POTENTIALLY REPLACED BY =
draft-ietf-sipping-update-pai
   draft-hilt-sipping-overload-design POTENTIALLY REPLACED BY =
draft-ietf-sipping-overload-design
   draft-petrie-sipping-profile-datasets POTENTIALLY REPLACED BY =
draft-ietf-sipping-profile-datasets
   draft-rosenberg-sipping-service-identification POTENTIALLY REPLACED =
BY draft-ietf-sipping-service-identification
   draft-zhang-sipping-overlap POTENTIALLY REPLACED BY =
draft-ietf-sipping-overlap

SPEERMINT Working Group, CONCLUDED Area
   draft-meyer-speermint-reqs-and-terminology POTENTIALLY REPLACED BY =
draft-ietf-speermint-reqs-and-terminology
   draft-niccolini-speermint-voipthreats POTENTIALLY REPLACED BY =
draft-ietf-speermint-voipthreats

XCON Working Group, CONCLUDED Area
   draft-barnes-xcon-ccmp POTENTIALLY REPLACED BY draft-ietf-xcon-ccmp
   draft-barnes-xcon-examples POTENTIALLY REPLACED BY =
draft-ietf-xcon-examples

DKIM Working Group, CONCLUDED Area
   draft-lindsey-dkim-mailinglists POTENTIALLY REPLACED BY =
draft-ietf-dkim-mailinglists

SACRED Working Group, CONCLUDED Area
   draft-arsenault-sacred-reqs POTENTIALLY REPLACED BY =
draft-ietf-sacred-reqs

SASL Working Group, CONCLUDED Area
   draft-zeilenga-sasl-crammd5 POTENTIALLY REPLACED BY =
draft-ietf-sasl-crammd5
   draft-zeilenga-sasl-rfc2222bis POTENTIALLY REPLACED BY =
draft-ietf-sasl-rfc2222bis

SMIME Working Group, CONCLUDED Area
   draft-dusse-smime-cert POTENTIALLY REPLACED BY draft-ietf-smime-cert
   draft-dusse-smime-msg POTENTIALLY REPLACED BY draft-ietf-smime-msg

DIFFSERV Working Group, CONCLUDED Area
   draft-baker-diffserv-mib POTENTIALLY REPLACED BY =
draft-ietf-diffserv-mib
   draft-black-diffserv-tunnels POTENTIALLY REPLACED BY =
draft-ietf-diffserv-tunnels

RSVP Working Group, CONCLUDED Area
   draft-berger-rsvp-refresh-reduct POTENTIALLY REPLACED BY =
draft-ietf-rsvp-refresh-reduct

-----------------------------------------------------------------
INT Area
-----------------------------------------------------------------
6MAN Working Group, INT Area
   draft-carpenter-6man-uri-zoneid POTENTIALLY REPLACED BY =
draft-ietf-6man-uri-zoneid
   draft-costa-6man-dad-proxy POTENTIALLY REPLACED BY =
draft-ietf-6man-dad-proxy
   draft-fujisaki-6man-addr-select-opt POTENTIALLY REPLACED BY =
draft-ietf-6man-addr-select-opt
   draft-george-6man-3627-historic POTENTIALLY REPLACED BY =
draft-ietf-6man-3627-historic
   draft-gont-6man-ipv6-atomic-fragments POTENTIALLY REPLACED BY =
draft-ietf-6man-ipv6-atomic-fragments
   draft-hsingh-6man-enhanced-dad POTENTIALLY REPLACED BY =
draft-ietf-6man-enhanced-dad
   draft-joshi-6man-neighbor-inform POTENTIALLY REPLACED BY =
draft-ietf-6man-neighbor-inform
   draft-lynn-6man-6lobac POTENTIALLY REPLACED BY draft-ietf-6man-6lobac
   draft-nordmark-6man-impatient-nud POTENTIALLY REPLACED BY =
draft-ietf-6man-impatient-nud

ANCP Working Group, INT Area
   draft-lefaucheur-ancp-mc-extensions POTENTIALLY REPLACED BY =
draft-ietf-ancp-mc-extensions

CSI Working Group, INT Area
   draft-jiang-csi-dhcpv6-cga-ps POTENTIALLY REPLACED BY =
draft-ietf-csi-dhcpv6-cga-ps
   draft-rgaglian-csi-send-name-type-registry POTENTIALLY REPLACED BY =
draft-ietf-csi-send-name-type-registry

DHC Working Group, INT Area
   draft-jiang-dhc-cga-config-dhcpv6 POTENTIALLY REPLACED BY =
draft-ietf-dhc-cga-config-dhcpv6
   draft-jjmb-dhc-dhcpv6-redundancy-consider POTENTIALLY REPLACED BY =
draft-ietf-dhc-dhcpv6-redundancy-consider
   draft-miles-dhc-dhcpv6-ldra POTENTIALLY REPLACED BY =
draft-ietf-dhc-dhcpv6-ldra
   draft-mrugalski-dhc-dhcpv6-failover-requirements POTENTIALLY REPLACED =
BY draft-ietf-dhc-dhcpv6-failover-requirements
   draft-xia-dhc-host-gen-id POTENTIALLY REPLACED BY =
draft-ietf-dhc-host-gen-id

DNSEXT Working Group, INT Area
   draft-wang-dnsext-newzone-notify POTENTIALLY REPLACED BY =
draft-ietf-dnsext-newzone-notify

HIP Working Group, INT Area
   draft-camarillo-hip-via POTENTIALLY REPLACED BY draft-ietf-hip-via
   draft-henderson-hip-rfc5206-bis POTENTIALLY REPLACED BY =
draft-ietf-hip-rfc5206-bis
   draft-jokela-hip-rfc5202-bis POTENTIALLY REPLACED BY =
draft-ietf-hip-rfc5202-bis
   draft-keranen-hip-native-nat-traversal POTENTIALLY REPLACED BY =
draft-ietf-hip-native-nat-traversal
   draft-keranen-hip-over-hip POTENTIALLY REPLACED BY =
draft-ietf-hip-over-hip
   draft-keranen-hip-reload-instance POTENTIALLY REPLACED BY =
draft-ietf-hip-reload-instance
   draft-moskowitz-hip-rfc4423-bis POTENTIALLY REPLACED BY =
draft-ietf-hip-rfc4423-bis
   draft-moskowitz-hip-rfc5201-bis POTENTIALLY REPLACED BY =
draft-ietf-hip-rfc5201-bis
   draft-nikander-hip-hiccups POTENTIALLY REPLACED BY =
draft-ietf-hip-hiccups

INTAREA Working Group, INT Area
   draft-boucadair-intarea-nat-reveal-analysis POTENTIALLY REPLACED BY =
draft-ietf-intarea-nat-reveal-analysis

LISP Working Group, INT Area
   draft-jakab-lisp-deployment POTENTIALLY REPLACED BY =
draft-ietf-lisp-deployment
   draft-maino-lisp-sec POTENTIALLY REPLACED BY draft-ietf-lisp-sec
   draft-meyer-lisp-eid-block POTENTIALLY REPLACED BY =
draft-ietf-lisp-eid-block

MIF Working Group, INT Area
   draft-liu-mif-api-extension POTENTIALLY REPLACED BY =
draft-ietf-mif-api-extension

MULTIMOB Working Group, INT Area
   draft-schmidt-multimob-pmipv6-source POTENTIALLY REPLACED BY =
draft-ietf-multimob-pmipv6-source
   draft-wu-multimob-igmp-mld-tuning POTENTIALLY REPLACED BY =
draft-ietf-multimob-igmp-mld-tuning
   draft-zuniga-multimob-pmipv6-ropt POTENTIALLY REPLACED BY =
draft-ietf-multimob-pmipv6-ropt

NETEXT Working Group, INT Area
   draft-bernardos-netext-pmipv6-flowmob POTENTIALLY REPLACED BY =
draft-ietf-netext-pmipv6-flowmob
   draft-korhonen-netext-redirect POTENTIALLY REPLACED BY =
draft-ietf-netext-redirect
   draft-krishnan-netext-pmip-lr POTENTIALLY REPLACED BY =
draft-ietf-netext-pmip-lr
   draft-melia-netext-logical-interface-support POTENTIALLY REPLACED BY =
draft-ietf-netext-logical-interface-support
   draft-zhou-netext-pd-pmip POTENTIALLY REPLACED BY =
draft-ietf-netext-pd-pmip

PCP Working Group, INT Area
   draft-bpw-pcp-dhcp POTENTIALLY REPLACED BY draft-ietf-pcp-dhcp
   draft-bpw-pcp-upnp-igd-interworking POTENTIALLY REPLACED BY =
draft-ietf-pcp-upnp-igd-interworking

SAVI Working Group, INT Area
   draft-bi-savi-mix POTENTIALLY REPLACED BY draft-ietf-savi-mix

SOFTWIRE Working Group, INT Area
   draft-guo-softwire-6rd-radius-attrib POTENTIALLY REPLACED BY =
draft-ietf-softwire-6rd-radius-attrib
   draft-ieft-softwire-dslite-deployment POTENTIALLY REPLACED BY =
draft-ietf-softwire-dslite-deployment
   draft-lee-softwire-dslite-deployment POTENTIALLY REPLACED BY =
draft-ietf-softwire-dslite-deployment
   draft-maglione-softwire-dslite-radius-ext POTENTIALLY REPLACED BY =
draft-ietf-softwire-dslite-radius-ext
   draft-qin-softwire-multicast-prefix-option POTENTIALLY REPLACED BY =
draft-ietf-softwire-multicast-prefix-option
   draft-xu-softwire-mesh-multicast POTENTIALLY REPLACED BY =
draft-ietf-softwire-mesh-multicast

TICTOC Working Group, INT Area
   draft-davari-tictoc-1588overmpls POTENTIALLY REPLACED BY =
draft-ietf-tictoc-1588overmpls
   draft-mizrahi-tictoc-security-requirements POTENTIALLY REPLACED BY =
draft-ietf-tictoc-security-requirements
   draft-vinay-tictoc-ptp-mib POTENTIALLY REPLACED BY =
draft-ietf-tictoc-ptp-mib

TRILL Working Group, INT Area
   draft-tissa-trill-cmt POTENTIALLY REPLACED BY draft-ietf-trill-cmt

-----------------------------------------------------------------
IRTF Area
-----------------------------------------------------------------
DTNRG Working Group, IRTF Area
   draft-lindgren-dtnrg-prophet POTENTIALLY REPLACED BY =
draft-irtf-dtnrg-prophet
   draft-symington-dtnrg-bundle-metadata-block POTENTIALLY REPLACED BY =
draft-irtf-dtnrg-bundle-metadata-block
   draft-symington-dtnrg-bundle-retrans-block POTENTIALLY REPLACED BY =
draft-irtf-dtnrg-bundle-retrans-block

HIPRG Working Group, IRTF Area
   draft-ahrenholz-hiprg-dht POTENTIALLY REPLACED BY =
draft-irtf-hiprg-dht

MOBOPTS Working Group, IRTF Area
   draft-koki-mobopts-l2-abstractions POTENTIALLY REPLACED BY =
draft-irtf-mobopts-l2-abstractions
   draft-ohba-mobopts-mpa-framework POTENTIALLY REPLACED BY =
draft-irtf-mobopts-mpa-framework
   draft-schmidt-mobopts-mmcastv6-ps POTENTIALLY REPLACED BY =
draft-irtf-mobopts-mmcastv6-ps
   draft-weniger-mobopts-mip6-cnlocpriv POTENTIALLY REPLACED BY =
draft-irtf-mobopts-mip6-cnlocpriv

P2PRG Working Group, IRTF Area
   draft-gurbani-p2prg-simulation-survey POTENTIALLY REPLACED BY =
draft-irtf-p2prg-simulation-survey

-----------------------------------------------------------------
IRTF-CONCLUDED Area
-----------------------------------------------------------------
-----------------------------------------------------------------
OPS Area
-----------------------------------------------------------------
ARMD Working Group, OPS Area
   draft-dunbar-armd-problem-statement POTENTIALLY REPLACED BY =
draft-ietf-armd-problem-statement

BMWG Working Group, OPS Area
   draft-janovak-bmwg-ipflow-meth POTENTIALLY REPLACED BY =
draft-ietf-bmwg-ipflow-meth
   draft-morton-bmwg-imix-genome POTENTIALLY REPLACED BY =
draft-ietf-bmwg-imix-genome

DIME Working Group, OPS Area
   draft-zorn-dime-rfc4005bis POTENTIALLY REPLACED BY =
draft-ietf-dime-rfc4005bis

EMAN Working Group, OPS Area
   draft-tychon-eman-applicability-statement POTENTIALLY REPLACED BY =
draft-ietf-eman-applicability-statement

GROW Working Group, OPS Area
   draft-dimitri-grow-rss POTENTIALLY REPLACED BY draft-ietf-grow-rss
   draft-manderson-grow-geomrt POTENTIALLY REPLACED BY =
draft-ietf-grow-geomrt

IPFIX Working Group, OPS Area
   draft-boschi-ipfix-anon POTENTIALLY REPLACED BY draft-ietf-ipfix-anon
   draft-boschi-ipfix-exporting-type POTENTIALLY REPLACED BY =
draft-ietf-ipfix-exporting-type
   draft-claise-ipfix-export-per-sctp-stream POTENTIALLY REPLACED BY =
draft-ietf-ipfix-export-per-sctp-stream
   draft-claise-ipfix-protocol-rfc5101bis POTENTIALLY REPLACED BY =
draft-ietf-ipfix-protocol-rfc5101bis
   draft-dkcm-ipfix-rfc5815bis POTENTIALLY REPLACED BY =
draft-ietf-ipfix-rfc5815bis
   draft-gupta-ipfix-reliability-template-ext POTENTIALLY REPLACED BY =
draft-ietf-ipfix-reliability-template-ext
   draft-trammell-ipfix-file POTENTIALLY REPLACED BY =
draft-ietf-ipfix-file

MBONED Working Group, OPS Area
   draft-asaeda-mboned-mtrace-v2 POTENTIALLY REPLACED BY =
draft-ietf-mboned-mtrace-v2
   draft-asaeda-mboned-session-announcement-req POTENTIALLY REPLACED BY =
draft-ietf-mboned-session-announcement-req
   draft-bipi-mboned-ip-multicast-pm-requirement POTENTIALLY REPLACED BY =
draft-ietf-mboned-ip-multicast-pm-requirement
   draft-venaas-mboned-mcaddrdoc POTENTIALLY REPLACED BY =
draft-ietf-mboned-mcaddrdoc
   draft-venaas-mboned-ssmping POTENTIALLY REPLACED BY =
draft-ietf-mboned-ssmping

NETCONF Working Group, OPS Area
   draft-bierman-netconf-access-control POTENTIALLY REPLACED BY =
draft-ietf-netconf-access-control
   draft-bierman-netconf-with-defaults POTENTIALLY REPLACED BY =
draft-ietf-netconf-with-defaults
   draft-chisholm-netconf-monitoring POTENTIALLY REPLACED BY =
draft-ietf-netconf-monitoring

NETMOD Working Group, OPS Area
   draft-bierman-netmod-system-mgmt POTENTIALLY REPLACED BY =
draft-ietf-netmod-system-mgmt
   draft-bjorklund-netmod-interfaces-cfg POTENTIALLY REPLACED BY =
draft-ietf-netmod-interfaces-cfg
   draft-bjorklund-netmod-ip-cfg POTENTIALLY REPLACED BY =
draft-ietf-netmod-ip-cfg
   draft-lhotka-netmod-routing-cfg POTENTIALLY REPLACED BY =
draft-ietf-netmod-routing-cfg
   draft-schoenw-netmod-smi-yang POTENTIALLY REPLACED BY =
draft-ietf-netmod-smi-yang

OPSAWG Working Group, OPS Area
   draft-mizrahi-opsawg-oam-overview POTENTIALLY REPLACED BY =
draft-ietf-opsawg-oam-overview

OPSEC Working Group, OPS Area
   draft-gont-opsec-icmp-filtering POTENTIALLY REPLACED BY =
draft-ietf-opsec-icmp-filtering
   draft-gont-opsec-ip-security POTENTIALLY REPLACED BY =
draft-ietf-opsec-ip-security

RADEXT Working Group, OPS Area
   draft-dekok-radext-dtls POTENTIALLY REPLACED BY =
draft-ietf-radext-dtls
   draft-dekok-radext-radius-extensions POTENTIALLY REPLACED BY =
draft-ietf-radext-radius-extensions
   draft-dekok-radext-tcp-transport POTENTIALLY REPLACED BY =
draft-ietf-radext-tcp-transport
   draft-lourdelet-radext-ipv6-access POTENTIALLY REPLACED BY =
draft-ietf-radext-ipv6-access
   draft-nelson-radext-crypto-agility-requirements POTENTIALLY REPLACED =
BY draft-ietf-radext-crypto-agility-requirements
   draft-tiwari-radext-tunnel-type POTENTIALLY REPLACED BY =
draft-ietf-radext-tunnel-type

V6OPS Working Group, OPS Area
   draft-hilliard-v6ops-ipv6-discard-prefix POTENTIALLY REPLACED BY =
draft-ietf-v6ops-ipv6-discard-prefix
   draft-rgaglian-v6ops-v6inixp POTENTIALLY REPLACED BY =
draft-ietf-v6ops-v6inixp
   draft-vandevelde-v6ops-ra-guard POTENTIALLY REPLACED BY =
draft-ietf-v6ops-ra-guard
   draft-wbeebee-v6ops-ipv6-cpe-router-bis POTENTIALLY REPLACED BY =
draft-ietf-v6ops-ipv6-cpe-router-bis

-----------------------------------------------------------------
RAI Area
-----------------------------------------------------------------
ATOCA Working Group, RAI Area
   draft-rosen-atoca-cap POTENTIALLY REPLACED BY draft-ietf-atoca-cap

BLISS Working Group, RAI Area
   draft-elwell-bliss-ach-analysis POTENTIALLY REPLACED BY =
draft-ietf-bliss-ach-analysis
   draft-poetzl-bliss-call-completion POTENTIALLY REPLACED BY =
draft-ietf-bliss-call-completion
   draft-procter-bliss-call-park-extension POTENTIALLY REPLACED BY =
draft-ietf-bliss-call-park-extension
   draft-rosenberg-bliss-problem-statement POTENTIALLY REPLACED BY =
draft-ietf-bliss-problem-statement

CLUE Working Group, RAI Area
   draft-romanow-clue-framework POTENTIALLY REPLACED BY =
draft-ietf-clue-framework
   draft-romanow-clue-telepresence-requirements POTENTIALLY REPLACED BY =
draft-ietf-clue-telepresence-requirements
   draft-romanow-clue-telepresence-use-cases POTENTIALLY REPLACED BY =
draft-ietf-clue-telepresence-use-cases

CODEC Working Group, RAI Area
   draft-valin-codec-guidelines POTENTIALLY REPLACED BY =
draft-ietf-codec-guidelines
   draft-valin-codec-results POTENTIALLY REPLACED BY =
draft-ietf-codec-results

DRINKS Working Group, RAI Area
   draft-channabasappa-drinks-usecases-requirements POTENTIALLY REPLACED =
BY draft-ietf-drinks-usecases-requirements

GEOPRIV Working Group, RAI Area
   draft-barnes-geopriv-policy-uri POTENTIALLY REPLACED BY =
draft-ietf-geopriv-policy-uri
   draft-mayrhofer-geopriv-geo-uri POTENTIALLY REPLACED BY =
draft-ietf-geopriv-geo-uri
   draft-winterbottom-geopriv-local-civic POTENTIALLY REPLACED BY =
draft-ietf-geopriv-local-civic

MMUSIC Working Group, RAI Area
   draft-garcia-mmusic-sdp-miscellaneous-caps POTENTIALLY REPLACED BY =
draft-ietf-mmusic-sdp-miscellaneous-caps
   draft-greevenbosch-mmusic-parallax-attribute POTENTIALLY REPLACED BY =
draft-ietf-mmusic-parallax-attribute
   draft-greevenbosch-mmusic-signal-3d-format POTENTIALLY REPLACED BY =
draft-ietf-mmusic-signal-3d-format
   draft-holmberg-mmusic-sdp-bundle-negotiation POTENTIALLY REPLACED BY =
draft-ietf-mmusic-sdp-bundle-negotiation
   draft-loreto-mmusic-sctp-sdp POTENTIALLY REPLACED BY =
draft-ietf-mmusic-sctp-sdp
   draft-polk-mmusic-traffic-class-for-sdp POTENTIALLY REPLACED BY =
draft-ietf-mmusic-traffic-class-for-sdp

P2PSIP Working Group, RAI Area
   draft-bryan-p2psip-reload POTENTIALLY REPLACED BY =
draft-ietf-p2psip-reload
   draft-zong-p2psip-drr POTENTIALLY REPLACED BY draft-ietf-p2psip-drr
   draft-zong-p2psip-rpr POTENTIALLY REPLACED BY draft-ietf-p2psip-rpr

PAYLOAD Working Group, RAI Area
   draft-westin-payload-vp8 POTENTIALLY REPLACED BY =
draft-ietf-payload-vp8

RTCWEB Working Group, RAI Area
   draft-uberti-rtcweb-jsep POTENTIALLY REPLACED BY =
draft-ietf-rtcweb-jsep

SIPCORE Working Group, RAI Area
   draft-holmberg-sipcore-proxy-feature POTENTIALLY REPLACED BY =
draft-ietf-sipcore-proxy-feature

SOC Working Group, RAI Area
   draft-noel-soc-overload-rate-control POTENTIALLY REPLACED BY =
draft-ietf-soc-overload-rate-control
   draft-shen-soc-load-control-event-package POTENTIALLY REPLACED BY =
draft-ietf-soc-load-control-event-package

XMPP Working Group, RAI Area
   draft-barnes-xmpp-dna POTENTIALLY REPLACED BY draft-ietf-xmpp-dna
   draft-miller-xmpp-e2e POTENTIALLY REPLACED BY draft-ietf-xmpp-e2e
   draft-saintandre-xmpp-6122bis POTENTIALLY REPLACED BY =
draft-ietf-xmpp-6122bis

XRBLOCK Working Group, RAI Area
   draft-clark-xrblock-rtcp-xr-qoe POTENTIALLY REPLACED BY =
draft-ietf-xrblock-rtcp-xr-qoe

-----------------------------------------------------------------
RTG Area
-----------------------------------------------------------------
BFD Working Group, RTG Area
   draft-bhatia-bfd-hmac-sha POTENTIALLY REPLACED BY =
draft-ietf-bfd-hmac-sha

CCAMP Working Group, RTG Area
   draft-bccg-ccamp-otn-g709-info-model POTENTIALLY REPLACED BY =
draft-ietf-ccamp-otn-g709-info-model
   draft-berger-ccamp-assoc-info POTENTIALLY REPLACED BY =
draft-ietf-ccamp-assoc-info
   draft-bernstein-ccamp-wson-signaling POTENTIALLY REPLACED BY =
draft-ietf-ccamp-wson-signaling

FORCES Working Group, RTG Area
   draft-hadi-forces-sctptml POTENTIALLY REPLACED BY =
draft-ietf-forces-sctptml
   draft-haleplidis-forces-implementation-experience POTENTIALLY =
REPLACED BY draft-ietf-forces-implementation-experience

IDR Working Group, RTG Area
   draft-decraene-idr-reserved-extended-communities POTENTIALLY REPLACED =
BY draft-ietf-idr-reserved-extended-communities
   draft-keyupate-idr-bgp-gr-notification POTENTIALLY REPLACED BY =
draft-ietf-idr-bgp-gr-notification
   draft-keyur-idr-enhanced-gr POTENTIALLY REPLACED BY =
draft-ietf-idr-enhanced-gr
   draft-raszuk-idr-flow-spec-v6 POTENTIALLY REPLACED BY =
draft-ietf-idr-flow-spec-v6
   draft-wkumari-idr-as0 POTENTIALLY REPLACED BY draft-ietf-idr-as0

ISIS Working Group, RTG Area
   draft-chopps-isis-bfd-tlv POTENTIALLY REPLACED BY =
draft-ietf-isis-bfd-tlv
   draft-ginsberg-isis-genapp POTENTIALLY REPLACED BY =
draft-ietf-isis-genapp
   draft-previdi-isis-mi POTENTIALLY REPLACED BY draft-ietf-isis-mi
   draft-shen-isis-oper-enhance POTENTIALLY REPLACED BY =
draft-ietf-isis-oper-enhance

L2VPN Working Group, RTG Area
   draft-delord-l2vpn-ldp-vpls-broadcast-exten POTENTIALLY REPLACED BY =
draft-ietf-l2vpn-ldp-vpls-broadcast-exten
   draft-henderickx-l2vpn-vpls-multihoming POTENTIALLY REPLACED BY =
draft-ietf-l2vpn-vpls-multihoming
   draft-key-l2vpn-etree-frwk POTENTIALLY REPLACED BY =
draft-ietf-l2vpn-etree-frwk
   draft-kompella-l2vpn-vpls-multihoming POTENTIALLY REPLACED BY =
draft-ietf-l2vpn-vpls-multihoming
   draft-pdutta-l2vpn-vpls-ldp-mac-opt POTENTIALLY REPLACED BY =
draft-ietf-l2vpn-vpls-ldp-mac-opt
   draft-pkwok-l2vpn-vpls-macflush-ld POTENTIALLY REPLACED BY =
draft-ietf-l2vpn-vpls-macflush-ld
   draft-sajassi-l2vpn-pbb-evpn POTENTIALLY REPLACED BY =
draft-ietf-l2vpn-pbb-evpn
   draft-sajassi-l2vpn-vpls-pbb-interop POTENTIALLY REPLACED BY =
draft-ietf-l2vpn-vpls-pbb-interop

L3VPN Working Group, RTG Area
   draft-rekhter-l3vpn-virtual-hub POTENTIALLY REPLACED BY =
draft-ietf-l3vpn-virtual-hub

MANET Working Group, RTG Area
   draft-herberg-manet-nhdp-sec POTENTIALLY REPLACED BY =
draft-ietf-manet-nhdp-sec
   draft-herberg-manet-nhdp-sec-threats POTENTIALLY REPLACED BY =
draft-ietf-manet-nhdp-sec-threats

MPLS Working Group, RTG Area
   draft-frost-mpls-tp-loss-delay-profile POTENTIALLY REPLACED BY =
draft-ietf-mpls-tp-loss-delay-profile
   draft-koike-mpls-tp-temporal-hitless-psm POTENTIALLY REPLACED BY =
draft-ietf-mpls-tp-temporal-hitless-psm
   draft-liu-mpls-tp-ring-protection POTENTIALLY REPLACED BY =
draft-ietf-mpls-tp-ring-protection
   draft-raggarwa-mpls-seamless-mcast POTENTIALLY REPLACED BY =
draft-ietf-mpls-seamless-mcast

OSPF Working Group, RTG Area
   draft-acee-ospf-multi-instance POTENTIALLY REPLACED BY =
draft-ietf-ospf-multi-instance
   draft-acee-ospf-transport-instance POTENTIALLY REPLACED BY =
draft-ietf-ospf-transport-instance
   draft-cheng-ospf-ipv4-embedded-ipv6-routing POTENTIALLY REPLACED BY =
draft-ietf-ospf-ipv4-embedded-ipv6-routing
   draft-nguyen-ospf-lls POTENTIALLY REPLACED BY draft-ietf-ospf-lls
   draft-nsheth-ospf-hybrid-bcast-and-p2mp POTENTIALLY REPLACED BY =
draft-ietf-ospf-hybrid-bcast-and-p2mp
   draft-ogier-ospf-dbex-opt POTENTIALLY REPLACED BY =
draft-ietf-ospf-dbex-opt
   draft-retana-ospf-rfc3137bis POTENTIALLY REPLACED BY =
draft-ietf-ospf-rfc3137bis
   draft-venkata-ospf-dynamic-hostname POTENTIALLY REPLACED BY =
draft-ietf-ospf-dynamic-hostname

PCE Working Group, RTG Area
   draft-tang-pce-stateful-pce POTENTIALLY REPLACED BY =
draft-ietf-pce-stateful-pce
   draft-zhao-pce-pcep-inter-domain-p2mp-procedures POTENTIALLY REPLACED =
BY draft-ietf-pce-pcep-inter-domain-p2mp-procedures

PIM Working Group, RTG Area
   draft-hou-pim-drlb POTENTIALLY REPLACED BY draft-ietf-pim-drlb

PWE3 Working Group, RTG Area
   draft-bryant-pwe3-packet-pw POTENTIALLY REPLACED BY =
draft-ietf-pwe3-packet-pw
   draft-delregno-pwe3-pw-vccv-impl-survey-results POTENTIALLY REPLACED =
BY draft-ietf-pwe3-pw-vccv-impl-survey-results
   draft-jin-pwe3-cbit-negotiation POTENTIALLY REPLACED BY =
draft-ietf-pwe3-cbit-negotiation
   draft-raza-pwe3-pw-typed-wc-fec POTENTIALLY REPLACED BY =
draft-ietf-pwe3-pw-typed-wc-fec

ROLL Working Group, RTG Area
   draft-dt-roll-p2p-rpl POTENTIALLY REPLACED BY draft-ietf-roll-p2p-rpl
   draft-gnawali-roll-minrank-hysteresis-of POTENTIALLY REPLACED BY =
draft-ietf-roll-minrank-hysteresis-of
   draft-goyal-roll-p2p-measurement POTENTIALLY REPLACED BY =
draft-ietf-roll-p2p-measurement
   draft-levis-roll-trickle POTENTIALLY REPLACED BY =
draft-ietf-roll-trickle
   draft-popa-roll-applicability-ami POTENTIALLY REPLACED BY =
draft-ietf-roll-applicability-ami
   draft-tsao-roll-security-framework POTENTIALLY REPLACED BY =
draft-ietf-roll-security-framework

RTGWG Working Group, RTG Area
   draft-atlas-rtgwg-mrt-frr-architecture POTENTIALLY REPLACED BY =
draft-ietf-rtgwg-mrt-frr-architecture

-----------------------------------------------------------------
SEC Area
-----------------------------------------------------------------
ABFAB Working Group, SEC Area
   draft-lear-abfab-arch POTENTIALLY REPLACED BY draft-ietf-abfab-arch

HOKEY Working Group, SEC Area
   draft-wu-hokey-rfc5296bis POTENTIALLY REPLACED BY =
draft-ietf-hokey-rfc5296bis

MILE Working Group, SEC Area
   draft-moriarty-mile-grc-exchange POTENTIALLY REPLACED BY =
draft-ietf-mile-grc-exchange

NEA Working Group, SEC Area
   draft-hanna-nea-pt-eap POTENTIALLY REPLACED BY draft-ietf-nea-pt-eap
   draft-sangster-nea-pt-tls POTENTIALLY REPLACED BY =
draft-ietf-nea-pt-tls

OAUTH Working Group, SEC Area
   draft-mortimore-oauth-assertions POTENTIALLY REPLACED BY =
draft-ietf-oauth-assertions

PKIX Working Group, SEC Area
   draft-cooper-pkix-rfc2560bis POTENTIALLY REPLACED BY =
draft-ietf-pkix-rfc2560bis
   draft-cooper-pkix-rfc5280-clarifications POTENTIALLY REPLACED BY =
draft-ietf-pkix-rfc5280-clarifications
   draft-santesson-pkix-certimage POTENTIALLY REPLACED BY =
draft-ietf-pkix-certimage

TLS Working Group, SEC Area
   draft-kanno-tls-camellia POTENTIALLY REPLACED BY =
draft-ietf-tls-camellia
   draft-rescorla-tls-suiteb POTENTIALLY REPLACED BY =
draft-ietf-tls-suiteb
   draft-seggelmann-tls-dtls-heartbeat POTENTIALLY REPLACED BY =
draft-ietf-tls-dtls-heartbeat

-----------------------------------------------------------------
TSV Area
-----------------------------------------------------------------
ALTO Working Group, TSV Area
   draft-song-alto-server-discovery POTENTIALLY REPLACED BY =
draft-ietf-alto-server-discovery
   draft-stiemerling-alto-deployments POTENTIALLY REPLACED BY =
draft-ietf-alto-deployments

BEHAVE Working Group, TSV Area
   draft-liu-behave-ftp64 POTENTIALLY REPLACED BY =
draft-ietf-behave-ftp64
   draft-penno-behave-64-analysis POTENTIALLY REPLACED BY =
draft-ietf-behave-64-analysis

CDNI Working Group, TSV Area
   draft-watson-cdni-use-cases POTENTIALLY REPLACED BY =
draft-ietf-cdni-use-cases

CONEX Working Group, TSV Area
   draft-krishnan-conex-destopt POTENTIALLY REPLACED BY =
draft-ietf-conex-destopt
   draft-kuehlewind-conex-tcp-modifications POTENTIALLY REPLACED BY =
draft-ietf-conex-tcp-modifications
   draft-mathis-conex-abstract-mech POTENTIALLY REPLACED BY =
draft-ietf-conex-abstract-mech
   draft-moncaster-conex-concepts-uses POTENTIALLY REPLACED BY =
draft-ietf-conex-concepts-uses

DECADE Working Group, TSV Area
   draft-alimi-decade-arch POTENTIALLY REPLACED BY =
draft-ietf-decade-arch
   draft-chen-decade-integration-example POTENTIALLY REPLACED BY =
draft-ietf-decade-integration-example
   draft-huang-decade-integration-example POTENTIALLY REPLACED BY =
draft-ietf-decade-integration-example

FECFRAME Working Group, TSV Area
   draft-roca-fecframe-ldpc POTENTIALLY REPLACED BY =
draft-ietf-fecframe-ldpc
   draft-roca-fecframe-simple-rs POTENTIALLY REPLACED BY =
draft-ietf-fecframe-simple-rs

IPPM Working Group, TSV Area
   draft-baillargeon-ippm-twamp-value-added-octets POTENTIALLY REPLACED =
BY draft-ietf-ippm-twamp-value-added-octets
   draft-geib-ippm-metrictest POTENTIALLY REPLACED BY =
draft-ietf-ippm-metrictest
   draft-morton-ippm-rt-loss POTENTIALLY REPLACED BY =
draft-ietf-ippm-rt-loss
   draft-morton-ippm-testplan-rfc2679 POTENTIALLY REPLACED BY =
draft-ietf-ippm-testplan-rfc2679

NFSV4 Working Group, TSV Area
   draft-alexrn-nfsv4-ipv6 POTENTIALLY REPLACED BY draft-ietf-nfsv4-ipv6
   draft-dnoveck-nfsv4-migration-issues POTENTIALLY REPLACED BY =
draft-ietf-nfsv4-migration-issues
   draft-eisler-nfsv4-minorversion-2-requirements POTENTIALLY REPLACED =
BY draft-ietf-nfsv4-minorversion-2-requirements
   draft-faibish-nfsv4-pnfs-access-permissions-check POTENTIALLY =
REPLACED BY draft-ietf-nfsv4-pnfs-access-permissions-check
   draft-faibish-nfsv4-pnfs-block-disk-protection POTENTIALLY REPLACED =
BY draft-ietf-nfsv4-pnfs-block-disk-protection
   draft-haynes-nfsv4-minorversion2 POTENTIALLY REPLACED BY =
draft-ietf-nfsv4-minorversion2
   draft-haynes-nfsv4-minorversion2-dot-x POTENTIALLY REPLACED BY =
draft-ietf-nfsv4-minorversion2-dot-x
   draft-quigley-nfsv4-labreqs POTENTIALLY REPLACED BY =
draft-ietf-nfsv4-labreqs

PCN Working Group, TSV Area
   draft-karagiannis-pcn-signaling-requirements POTENTIALLY REPLACED BY =
draft-ietf-pcn-signaling-requirements

PPSP Working Group, TSV Area
   draft-gu-ppsp-peer-protocol POTENTIALLY REPLACED BY =
draft-ietf-ppsp-peer-protocol
   draft-gu-ppsp-survey POTENTIALLY REPLACED BY draft-ietf-ppsp-survey

TCPM Working Group, TSV Area
   draft-blanton-tcpm-3517bis POTENTIALLY REPLACED BY =
draft-ietf-tcpm-3517bis
   draft-cheng-tcpm-fastopen POTENTIALLY REPLACED BY =
draft-ietf-tcpm-fastopen
   draft-gont-tcpm-rfc1948bis POTENTIALLY REPLACED BY =
draft-ietf-tcpm-rfc1948bis
   draft-henderson-tcpm-rfc3782-bis POTENTIALLY REPLACED BY =
draft-ietf-tcpm-rfc3782-bis
   draft-hkchu-tcpm-initcwnd POTENTIALLY REPLACED BY =
draft-ietf-tcpm-initcwnd
   draft-mathis-tcpm-proportional-rate-reduction POTENTIALLY REPLACED BY =
draft-ietf-tcpm-proportional-rate-reduction
   draft-touch-tcpm-experimental-options POTENTIALLY REPLACED BY =
draft-ietf-tcpm-experimental-options

TSVWG Working Group, TSV Area
   draft-gont-tsvwg-source-quench POTENTIALLY REPLACED BY =
draft-ietf-tsvwg-source-quench
   draft-polk-tsvwg-intserv-multiple-tspec POTENTIALLY REPLACED BY =
draft-ietf-tsvwg-intserv-multiple-tspec

-----------------------------------------------------------------
Potential Inconsistencies
-----------------------------------------------------------------
draft-ietf-6lowpan-nd may replace one or more of 2 individual IDs - =
check this
draft-ietf-armd-problem-statement may replace one or more of 2 =
individual IDs - check this
draft-ietf-avt-rtp-gsm-hr may replace one or more of 3 individual IDs - =
check this
draft-ietf-avt-rtp-svc may replace one or more of 2 individual IDs - =
check this
draft-ietf-bmwg-ipflow-meth may replace one or more of 2 individual IDs =
- check this
draft-ietf-cdni-use-cases may replace one or more of 2 individual IDs - =
check this
draft-ietf-decade-integration-example may replace one or more of 2 =
individual IDs - check this
draft-ietf-decade-survey may replace one or more of 2 individual IDs - =
check this
draft-ietf-dhc-dhcpv4-bulk-leasequery may replace one or more of 2 =
individual IDs - check this
draft-ietf-forces-tmlsp may replace one or more of 2 individual IDs - =
check this
draft-ietf-ipfix-biflow may replace one or more of 2 individual IDs - =
check this
draft-ietf-l2tpext-tdm may replace one or more of 2 individual IDs - =
check this
draft-ietf-l2vpn-vpls-multihoming may replace one or more of 2 =
individual IDs - check this
draft-ietf-mpls-tp-fault may replace one or more of 2 individual IDs - =
check this
draft-ietf-mpls-tp-ring-protection may replace one or more of 2 =
individual IDs - check this
draft-ietf-netconf-monitoring may replace one or more of 2 individual =
IDs - check this
draft-ietf-netlmm-lma-discovery may replace one or more of 2 individual =
IDs - check this
draft-ietf-netlmm-mip-interactions may replace one or more of 2 =
individual IDs - check this
draft-ietf-pce-stateful-pce may replace one or more of 2 individual IDs =
- check this
draft-ietf-sip-saml may replace one or more of 2 individual IDs - check =
this
draft-ietf-sipping-service-identification may replace one or more of 2 =
individual IDs - check this
draft-ietf-softwire-dslite-deployment may replace one or more of 2 =
individual IDs - check this
draft-ietf-trill-rbridge-arch may replace one or more of 2 individual =
IDs - check this


--Apple-Mail=_807F4516-3BB2-4959-A490-29CC282BDECA
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMQDCCBUow
ggQyoAMCAQICEFcfSRTG0jNknqb9LV9GuFkwDQYJKoZIhvcNAQEFBQAwgd0xCzAJBgNVBAYTAlVT
MRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEg
KGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24g
Q2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMzAeFw0xMTEyMTAwMDAwMDBaFw0x
MjEyMDkyMzU5NTlaMIIBDTEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9S
UEEgSW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMpOTgxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZh
bGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJRCBDbGFzcyAxIC0gTmV0c2NhcGUgRnVsbCBTZXJ2
aWNlMRQwEgYDVQQDFAtMYXJzIEVnZ2VydDEeMBwGCSqGSIb3DQEJARYPbGFyc0BuZXRhcHAuY29t
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAokrhJTcXt6J/VEpZOicLoguBlYTjXP9v
Ze4HuuhXnURUS8YouAfgaqA0zYbt5yd6fh4PBMdAaEWr5yJyHuFykXlrCumjUWSpLuqTS2A+pt4q
cZaAQk9iLDN/UVd3SpkUuvWbxXlqzG7/BSqa3VNObBzCmyh+V7aXxri+30CT//DSsNRC4VFy6sn6
dMgSaFenXLwe/FBwY0qTMfICT1PrrX6Sw1S8OfH9rykLlZXbmfkFExxQngp1DJH9xMHeODHGbCv/
ty5gdxMOrLe+vENxFEcy1YQWBZd1kNL4UObugF8A/jE/s+Oa3H1VFH8ghqZTdqGDysVxmtKHuNFx
6jIBSQIDAQABo4HSMIHPMAkGA1UdEwQCMAAwRAYDVR0gBD0wOzA5BgtghkgBhvhFAQcXATAqMCgG
CCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhMAsGA1UdDwQEAwIFoDAdBgNV
HSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwUAYDVR0fBEkwRzBFoEOgQYY/aHR0cDovL2luZGMx
ZGlnaXRhbGlkLWczLWNybC52ZXJpc2lnbi5jb20vSW5kQzFEaWdpdGFsSUQtRzMuY3JsMA0GCSqG
SIb3DQEBBQUAA4IBAQBA7q6tR92qpd7xo7VBsrOfGCWzoxIVfTc7t0RhB/Oz/+c3lnhYnNScIuKN
JmyZvznmVxqB9BJ72+NkvmdB/hnILSBTRawL2tyLo9PkBtN0nRt4gS6wjpWnD8G83hlJLE7r25jk
7HkRev61dTIXsANFpJKF02C4XSoDfEzNV6MpuEvHvcgHCqMrlwWwfKc7+NoDnE8PBuRzwSXvlD5L
mswCY2iiOsd7ImNO4OzTCxETvKTDu92+FTIbRJJpYjVNv1UF7e3w9Kq65BkZJErUH19beUeQl0Wh
2BJQE6/15rQyCnP0iJ/Nmx2/kI6M0PWunEsI6FMs0MbosreaWGHlQmomMIIG7jCCBdagAwIBAgIQ
cRVmBUrkkSFN6bxE+azT3DANBgkqhkiG9w0BAQUFADCByjELMAkGA1UEBhMCVVMxFzAVBgNVBAoT
DlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTowOAYDVQQL
EzEoYykgMTk5OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MUUwQwYD
VQQDEzxWZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9y
aXR5IC0gRzMwHhcNMDkwNTAxMDAwMDAwWhcNMTkwNDMwMjM1OTU5WjCB3TELMAkGA1UEBhMCVVMx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3Jr
MTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAo
YykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBD
bGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBDQSAtIEczMIIBIjANBgkqhkiG9w0BAQEFAAOC
AQ8AMIIBCgKCAQEA7cRH3yooHXwGa7vXITLJbBOP6bGNQU4099oL42r6ZYggCxET6ZvgSU6Lb9UB
0F8NR5GKWkx0Pj/GkQm7TDSejW6hglFi92l2WJYHr54UGAdPWr2f0jGyVBlzRmoZQhHsEnMhjfXc
MM3l2VYKMcU2bSkUl70t2olHGYjYSwQ967Y8Zx50ABMN0Ibak2f4MwOuGjxraXj2wCyO4YM/d/mZ
//6fUlrCtIcK2GypR8FUKWVDPkrAlh/Brfd3r2yxBF6+wbaULZeQLSfSux7pg2qE9sSyriMGZSal
J1grByK0b6ZiSBp38tVQJ5op05b7KPW6JHZi44xZ6/tu1ULEvkHH9QIDAQABo4ICuTCCArUwNAYI
KwYBBQUHAQEEKDAmMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC52ZXJpc2lnbi5jb20wEgYDVR0T
AQH/BAgwBgEB/wIBADBwBgNVHSAEaTBnMGUGC2CGSAGG+EUBBxcBMFYwKAYIKwYBBQUHAgEWHGh0
dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9jcHMwKgYIKwYBBQUHAgIwHhocaHR0cHM6Ly93d3cudmVy
aXNpZ24uY29tL3JwYTA0BgNVHR8ELTArMCmgJ6AlhiNodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9w
Y2ExLWczLmNybDAOBgNVHQ8BAf8EBAMCAQYwbgYIKwYBBQUHAQwEYjBgoV6gXDBaMFgwVhYJaW1h
Z2UvZ2lmMCEwHzAHBgUrDgMCGgQUS2u5KJYGDLvQUjibKaxLB4shBRgwJhYkaHR0cDovL2xvZ28u
dmVyaXNpZ24uY29tL3ZzbG9nbzEuZ2lmMC4GA1UdEQQnMCWkIzAhMR8wHQYDVQQDExZQcml2YXRl
TGFiZWw0LTIwNDgtMTE4MB0GA1UdDgQWBBR5R2EIQf04BKJL57XM9UP2SSsR+DCB8QYDVR0jBIHp
MIHmoYHQpIHNMIHKMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNV
BAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4BgNVBAsTMShjKSAxOTk5IFZlcmlTaWduLCBJ
bmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxRTBDBgNVBAMTPFZlcmlTaWduIENsYXNzIDEg
UHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgLSBHM4IRAItbdVaEVIULAM+v
OEjOsaQwDQYJKoZIhvcNAQEFBQADggEBADlNz0GZgbWpBbVSOOk5hIls5DSoWufYbAlMJBq6WaSH
O3Mh8ZOBz79oY1pn/jWFK6HDXaNKwjoZ3TDWzE3v8dKBl8pUWkO/N4t6jhmND0OojPKvYLMVirOV
nDzgnrMnmKQ1chfl/Cpdh9OKDcLRRSr4wPSsKpM61a4ScAjr+zvid+zoK2Q1ds262uDRyxTWcVib
vtU+fbbZ6CTFJGZMXZEfdrMXPn8NxiGJL7M3uKH/XLJtSd5lUkL7DojS7Uodv0vj+Mxy+kgOZY5J
yNb4mZg7t5Q+MXEGh/psWVMu198r7V9jAKwV7QO4VRaMxmgD5yKocwuxvKDaUljdCg5/wYIxggSL
MIIEhwIBATCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0
cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFs
aWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBD
QSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMAkGBSsOAwIaBQCgggJtMBgGCSqGSIb3DQEJAzELBgkq
hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEyMDQxODA4NDkzMVowIwYJKoZIhvcNAQkEMRYEFDTB
/AsqQVSXQllokDikWat2wVgBMIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQGEwJVUzEX
MBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
OzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhIChj
KTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlTaWduIENs
YXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEFcfSRTG0jNknqb9LV9GuFkwggEF
BgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJ
bmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1
c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29u
YSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vi
c2NyaWJlciBDQSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMA0GCSqGSIb3DQEBAQUABIIBAAwqsW9J
+oG30x4DXlJM+JQoUjb3DtGqDLuG/ydBgFzgNfgCd6QpHZt6rNWMZftCqiJCVwuXc8inhnyjFqVn
2QXkTzDFj6Ail3+FlUklWLEWAu83MbSoRO1VaxLX00o6VT9NXNwprqqS+DUB9XW+Ey8PQydddgQ3
feWnfoTfeOY82bjm1eVZBEcd8ipPyrDcJCKtBX6RWwtnA+OviDj2/lWdTZ+5QotCF2RlP7rRoOjh
EX+ps3lsJaBLpeRGKAGx8vWCDE+jd2ueLEifoI9h3yLsbFiSBoLNuSz7qUXDFYDfH62Xi9rphuBY
e/hltjUy8oFIgkGGGeh69rUWmqEg0p8AAAAAAAA=

--Apple-Mail=_807F4516-3BB2-4959-A490-29CC282BDECA--

From denghui02@hotmail.com  Wed Apr 18 01:54:17 2012
Return-Path: <denghui02@hotmail.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 0B83321F8623 for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 01:54:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.698
X-Spam-Level: 
X-Spam-Status: No, score=-99.698 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, MANGLED_WORKNG=2.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 oZn-054u5Hug for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 01:54:13 -0700 (PDT)
Received: from col0-omc1-s8.col0.hotmail.com (col0-omc1-s8.col0.hotmail.com [65.55.34.18]) by ietfa.amsl.com (Postfix) with ESMTP id BA07621F861D for <wgchairs@ietf.org>; Wed, 18 Apr 2012 01:54:12 -0700 (PDT)
Received: from COL118-W55 ([65.55.34.9]) by col0-omc1-s8.col0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 18 Apr 2012 01:54:12 -0700
Message-ID: <COL118-W55777ADB1F1049DEEEB2A9B13C0@phx.gbl>
Content-Type: multipart/alternative; boundary="_f81acde2-b07d-42d6-8e4b-7f437544ad99_"
X-Originating-IP: [221.130.253.135]
From: Hui Deng <denghui02@hotmail.com>
To: <lars@netapp.com>, <wgchairs@ietf.org>, <irsg@irtf.org>
Subject: RE: latest missing replaced-by information
Date: Wed, 18 Apr 2012 16:54:12 +0800
Importance: Normal
In-Reply-To: <E9354164-6546-42A9-BAC4-BE6660855AE9@netapp.com>
References: <E9354164-6546-42A9-BAC4-BE6660855AE9@netapp.com>
MIME-Version: 1.0
X-OriginalArrivalTime: 18 Apr 2012 08:54:12.0176 (UTC) FILETIME=[D32E6D00:01CD1D40]
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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, 18 Apr 2012 08:54:17 -0000

--_f81acde2-b07d-42d6-8e4b-7f437544ad99_
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: 8bit


excuse me for naive question, how to send a ticket to the secretariat ?
 
Best,
 
-Hui
 

> From: lars@netapp.com
> To: wgchairs@ietf.org; irsg@irtf.org
> Subject: latest missing replaced-by information
> Date: Wed, 18 Apr 2012 08:49:31 +0000
> 
> Hi,
> 
> here's yet another installment in the series of reports on potentially missing "replaced-by" relationships in the IETF datatracker.
> 
> *** NEW *** Also includes IRTF documents now.
> 
> WG and RG chairs are encouraged to check whether these are accurate for their groups, and if so, send a ticket to the secretariat instructing them to "record in the database that draft X replaced draft Y".
> 
> As always, double-check before reporting to the secretariat. Also, see list of possible inconsistencies at the end of the report.
> 
> (Note that the IPR disclosure search tool uses these replaced-by relationships, so keeping them up-to-date is actually useful and not just WG hygiene.)
> 
> Lars
> 
> 
> -----------------------------------------------------------------
> APP Area
> -----------------------------------------------------------------
> CORE Working Group, APP Area
> draft-rahman-core-groupcomm POTENTIALLY REPLACED BY draft-ietf-core-groupcomm
> 
> EAI Working Group, APP Area
> draft-duerst-eai-mailto POTENTIALLY REPLACED BY draft-ietf-eai-mailto
> draft-yao-eai-rfc5336bis POTENTIALLY REPLACED BY draft-ietf-eai-rfc5336bis
> 
> PAWS Working Group, APP Area
> draft-probasco-paws-problem-stmt-usecases-rqmts POTENTIALLY REPLACED BY draft-ietf-paws-problem-stmt-usecases-rqmts
> 
> VCARDDAV Working Group, APP Area
> draft-cauchie-vcarddav-oma-cab-extensions POTENTIALLY REPLACED BY draft-ietf-vcarddav-oma-cab-extensions
> 
> -----------------------------------------------------------------
> CONCLUDED Area
> -----------------------------------------------------------------
> ATOMPUB Working Group, CONCLUDED Area
> draft-snell-atompub-autodiscovery POTENTIALLY REPLACED BY draft-ietf-atompub-autodiscovery
> 
> HTTP Working Group, CONCLUDED Area
> draft-wallis-http-digest-auth-a3a8 POTENTIALLY REPLACED BY draft-ietf-http-digest-auth-a3a8
> 
> IDNABIS Working Group, CONCLUDED Area
> draft-faltstrom-idnabis-tables POTENTIALLY REPLACED BY draft-ietf-idnabis-tables
> 
> IMAP Working Group, CONCLUDED Area
> draft-crispin-imap-compat POTENTIALLY REPLACED BY draft-ietf-imap-compat
> 
> TFTPEXTS Working Group, CONCLUDED Area
> draft-malkin-tftpexts-blksize-opt POTENTIALLY REPLACED BY draft-ietf-tftpexts-blksize-opt
> draft-malkin-tftpexts-option-ext POTENTIALLY REPLACED BY draft-ietf-tftpexts-option-ext
> draft-malkin-tftpexts-options POTENTIALLY REPLACED BY draft-ietf-tftpexts-options
> 
> XMPP Working Group, CONCLUDED Area
> draft-barnes-xmpp-dna POTENTIALLY REPLACED BY draft-ietf-xmpp-dna
> draft-miller-xmpp-e2e POTENTIALLY REPLACED BY draft-ietf-xmpp-e2e
> draft-saintandre-xmpp-6122bis POTENTIALLY REPLACED BY draft-ietf-xmpp-6122bis
> 
> MIPSHOP Working Group, CONCLUDED Area
> draft-xia-mipshop-fmip-ptp POTENTIALLY REPLACED BY draft-ietf-mipshop-fmip-ptp
> 
> NETLMM Working Group, CONCLUDED Area
> draft-cui-netlmm-mip-interactions POTENTIALLY REPLACED BY draft-ietf-netlmm-mip-interactions
> draft-glenn-netlmm-pmipv6-mib POTENTIALLY REPLACED BY draft-ietf-netlmm-pmipv6-mib
> draft-korhonen-netlmm-lma-discovery POTENTIALLY REPLACED BY draft-ietf-netlmm-lma-discovery
> draft-xia-netlmm-lma-discovery POTENTIALLY REPLACED BY draft-ietf-netlmm-lma-discovery
> 
> SEND Working Group, CONCLUDED Area
> draft-arkko-send-cga POTENTIALLY REPLACED BY draft-ietf-send-cga
> draft-arkko-send-ndopt POTENTIALLY REPLACED BY draft-ietf-send-ndopt
> 
> SHIM6 Working Group, CONCLUDED Area
> draft-garcia-shim6-applicability POTENTIALLY REPLACED BY draft-ietf-shim6-applicability
> 
> CAPWAP Working Group, CONCLUDED Area
> draft-yangshi-capwap-802dot11-mib POTENTIALLY REPLACED BY draft-ietf-capwap-802dot11-mib
> draft-yangshi-capwap-base-mib POTENTIALLY REPLACED BY draft-ietf-capwap-base-mib
> 
> RMONMIB Working Group, CONCLUDED Area
> draft-bierman-rmonmib-hc-alarm-mib POTENTIALLY REPLACED BY draft-ietf-rmonmib-hc-alarm-mib
> 
> MEGACO Working Group, CONCLUDED Area
> draft-blatherwick-megaco-ipphone POTENTIALLY REPLACED BY draft-ietf-megaco-ipphone
> 
> SIGTRAN Working Group, CONCLUDED Area
> draft-anil-sigtran-dua POTENTIALLY REPLACED BY draft-ietf-sigtran-dua
> 
> SIP Working Group, CONCLUDED Area
> draft-arkko-sip-sec-agree POTENTIALLY REPLACED BY draft-ietf-sip-sec-agree
> draft-biggs-sip-replaces POTENTIALLY REPLACED BY draft-ietf-sip-replaces
> draft-pashalidis-sip-saml POTENTIALLY REPLACED BY draft-ietf-sip-saml
> 
> SIPPING Working Group, CONCLUDED Area
> draft-drage-sipping-service-identification POTENTIALLY REPLACED BY draft-ietf-sipping-service-identification
> draft-elwell-sipping-update-pai POTENTIALLY REPLACED BY draft-ietf-sipping-update-pai
> draft-hilt-sipping-overload-design POTENTIALLY REPLACED BY draft-ietf-sipping-overload-design
> draft-petrie-sipping-profile-datasets POTENTIALLY REPLACED BY draft-ietf-sipping-profile-datasets
> draft-rosenberg-sipping-service-identification POTENTIALLY REPLACED BY draft-ietf-sipping-service-identification
> draft-zhang-sipping-overlap POTENTIALLY REPLACED BY draft-ietf-sipping-overlap
> 
> SPEERMINT Working Group, CONCLUDED Area
> draft-meyer-speermint-reqs-and-terminology POTENTIALLY REPLACED BY draft-ietf-speermint-reqs-and-terminology
> draft-niccolini-speermint-voipthreats POTENTIALLY REPLACED BY draft-ietf-speermint-voipthreats
> 
> XCON Working Group, CONCLUDED Area
> draft-barnes-xcon-ccmp POTENTIALLY REPLACED BY draft-ietf-xcon-ccmp
> draft-barnes-xcon-examples POTENTIALLY REPLACED BY draft-ietf-xcon-examples
> 
> DKIM Working Group, CONCLUDED Area
> draft-lindsey-dkim-mailinglists POTENTIALLY REPLACED BY draft-ietf-dkim-mailinglists
> 
> SACRED Working Group, CONCLUDED Area
> draft-arsenault-sacred-reqs POTENTIALLY REPLACED BY draft-ietf-sacred-reqs
> 
> SASL Working Group, CONCLUDED Area
> draft-zeilenga-sasl-crammd5 POTENTIALLY REPLACED BY draft-ietf-sasl-crammd5
> draft-zeilenga-sasl-rfc2222bis POTENTIALLY REPLACED BY draft-ietf-sasl-rfc2222bis
> 
> SMIME Working Group, CONCLUDED Area
> draft-dusse-smime-cert POTENTIALLY REPLACED BY draft-ietf-smime-cert
> draft-dusse-smime-msg POTENTIALLY REPLACED BY draft-ietf-smime-msg
> 
> DIFFSERV Working Group, CONCLUDED Area
> draft-baker-diffserv-mib POTENTIALLY REPLACED BY draft-ietf-diffserv-mib
> draft-black-diffserv-tunnels POTENTIALLY REPLACED BY draft-ietf-diffserv-tunnels
> 
> RSVP Working Group, CONCLUDED Area
> draft-berger-rsvp-refresh-reduct POTENTIALLY REPLACED BY draft-ietf-rsvp-refresh-reduct
> 
> -----------------------------------------------------------------
> INT Area
> -----------------------------------------------------------------
> 6MAN Working Group, INT Area
> draft-carpenter-6man-uri-zoneid POTENTIALLY REPLACED BY draft-ietf-6man-uri-zoneid
> draft-costa-6man-dad-proxy POTENTIALLY REPLACED BY draft-ietf-6man-dad-proxy
> draft-fujisaki-6man-addr-select-opt POTENTIALLY REPLACED BY draft-ietf-6man-addr-select-opt
> draft-george-6man-3627-historic POTENTIALLY REPLACED BY draft-ietf-6man-3627-historic
> draft-gont-6man-ipv6-atomic-fragments POTENTIALLY REPLACED BY draft-ietf-6man-ipv6-atomic-fragments
> draft-hsingh-6man-enhanced-dad POTENTIALLY REPLACED BY draft-ietf-6man-enhanced-dad
> draft-joshi-6man-neighbor-inform POTENTIALLY REPLACED BY draft-ietf-6man-neighbor-inform
> draft-lynn-6man-6lobac POTENTIALLY REPLACED BY draft-ietf-6man-6lobac
> draft-nordmark-6man-impatient-nud POTENTIALLY REPLACED BY draft-ietf-6man-impatient-nud
> 
> ANCP Working Group, INT Area
> draft-lefaucheur-ancp-mc-extensions POTENTIALLY REPLACED BY draft-ietf-ancp-mc-extensions
> 
> CSI Working Group, INT Area
> draft-jiang-csi-dhcpv6-cga-ps POTENTIALLY REPLACED BY draft-ietf-csi-dhcpv6-cga-ps
> draft-rgaglian-csi-send-name-type-registry POTENTIALLY REPLACED BY draft-ietf-csi-send-name-type-registry
> 
> DHC Working Group, INT Area
> draft-jiang-dhc-cga-config-dhcpv6 POTENTIALLY REPLACED BY draft-ietf-dhc-cga-config-dhcpv6
> draft-jjmb-dhc-dhcpv6-redundancy-consider POTENTIALLY REPLACED BY draft-ietf-dhc-dhcpv6-redundancy-consider
> draft-miles-dhc-dhcpv6-ldra POTENTIALLY REPLACED BY draft-ietf-dhc-dhcpv6-ldra
> draft-mrugalski-dhc-dhcpv6-failover-requirements POTENTIALLY REPLACED BY draft-ietf-dhc-dhcpv6-failover-requirements
> draft-xia-dhc-host-gen-id POTENTIALLY REPLACED BY draft-ietf-dhc-host-gen-id
> 
> DNSEXT Working Group, INT Area
> draft-wang-dnsext-newzone-notify POTENTIALLY REPLACED BY draft-ietf-dnsext-newzone-notify
> 
> HIP Working Group, INT Area
> draft-camarillo-hip-via POTENTIALLY REPLACED BY draft-ietf-hip-via
> draft-henderson-hip-rfc5206-bis POTENTIALLY REPLACED BY draft-ietf-hip-rfc5206-bis
> draft-jokela-hip-rfc5202-bis POTENTIALLY REPLACED BY draft-ietf-hip-rfc5202-bis
> draft-keranen-hip-native-nat-traversal POTENTIALLY REPLACED BY draft-ietf-hip-native-nat-traversal
> draft-keranen-hip-over-hip POTENTIALLY REPLACED BY draft-ietf-hip-over-hip
> draft-keranen-hip-reload-instance POTENTIALLY REPLACED BY draft-ietf-hip-reload-instance
> draft-moskowitz-hip-rfc4423-bis POTENTIALLY REPLACED BY draft-ietf-hip-rfc4423-bis
> draft-moskowitz-hip-rfc5201-bis POTENTIALLY REPLACED BY draft-ietf-hip-rfc5201-bis
> draft-nikander-hip-hiccups POTENTIALLY REPLACED BY draft-ietf-hip-hiccups
> 
> INTAREA Working Group, INT Area
> draft-boucadair-intarea-nat-reveal-analysis POTENTIALLY REPLACED BY draft-ietf-intarea-nat-reveal-analysis
> 
> LISP Working Group, INT Area
> draft-jakab-lisp-deployment POTENTIALLY REPLACED BY draft-ietf-lisp-deployment
> draft-maino-lisp-sec POTENTIALLY REPLACED BY draft-ietf-lisp-sec
> draft-meyer-lisp-eid-block POTENTIALLY REPLACED BY draft-ietf-lisp-eid-block
> 
> MIF Working Group, INT Area
> draft-liu-mif-api-extension POTENTIALLY REPLACED BY draft-ietf-mif-api-extension
> 
> MULTIMOB Working Group, INT Area
> draft-schmidt-multimob-pmipv6-source POTENTIALLY REPLACED BY draft-ietf-multimob-pmipv6-source
> draft-wu-multimob-igmp-mld-tuning POTENTIALLY REPLACED BY draft-ietf-multimob-igmp-mld-tuning
> draft-zuniga-multimob-pmipv6-ropt POTENTIALLY REPLACED BY draft-ietf-multimob-pmipv6-ropt
> 
> NETEXT Working Group, INT Area
> draft-bernardos-netext-pmipv6-flowmob POTENTIALLY REPLACED BY draft-ietf-netext-pmipv6-flowmob
> draft-korhonen-netext-redirect POTENTIALLY REPLACED BY draft-ietf-netext-redirect
> draft-krishnan-netext-pmip-lr POTENTIALLY REPLACED BY draft-ietf-netext-pmip-lr
> draft-melia-netext-logical-interface-support POTENTIALLY REPLACED BY draft-ietf-netext-logical-interface-support
> draft-zhou-netext-pd-pmip POTENTIALLY REPLACED BY draft-ietf-netext-pd-pmip
> 
> PCP Working Group, INT Area
> draft-bpw-pcp-dhcp POTENTIALLY REPLACED BY draft-ietf-pcp-dhcp
> draft-bpw-pcp-upnp-igd-interworking POTENTIALLY REPLACED BY draft-ietf-pcp-upnp-igd-interworking
> 
> SAVI Working Group, INT Area
> draft-bi-savi-mix POTENTIALLY REPLACED BY draft-ietf-savi-mix
> 
> SOFTWIRE Working Group, INT Area
> draft-guo-softwire-6rd-radius-attrib POTENTIALLY REPLACED BY draft-ietf-softwire-6rd-radius-attrib
> draft-ieft-softwire-dslite-deployment POTENTIALLY REPLACED BY draft-ietf-softwire-dslite-deployment
> draft-lee-softwire-dslite-deployment POTENTIALLY REPLACED BY draft-ietf-softwire-dslite-deployment
> draft-maglione-softwire-dslite-radius-ext POTENTIALLY REPLACED BY draft-ietf-softwire-dslite-radius-ext
> draft-qin-softwire-multicast-prefix-option POTENTIALLY REPLACED BY draft-ietf-softwire-multicast-prefix-option
> draft-xu-softwire-mesh-multicast POTENTIALLY REPLACED BY draft-ietf-softwire-mesh-multicast
> 
> TICTOC Working Group, INT Area
> draft-davari-tictoc-1588overmpls POTENTIALLY REPLACED BY draft-ietf-tictoc-1588overmpls
> draft-mizrahi-tictoc-security-requirements POTENTIALLY REPLACED BY draft-ietf-tictoc-security-requirements
> draft-vinay-tictoc-ptp-mib POTENTIALLY REPLACED BY draft-ietf-tictoc-ptp-mib
> 
> TRILL Working Group, INT Area
> draft-tissa-trill-cmt POTENTIALLY REPLACED BY draft-ietf-trill-cmt
> 
> -----------------------------------------------------------------
> IRTF Area
> -----------------------------------------------------------------
> DTNRG Working Group, IRTF Area
> draft-lindgren-dtnrg-prophet POTENTIALLY REPLACED BY draft-irtf-dtnrg-prophet
> draft-symington-dtnrg-bundle-metadata-block POTENTIALLY REPLACED BY draft-irtf-dtnrg-bundle-metadata-block
> draft-symington-dtnrg-bundle-retrans-block POTENTIALLY REPLACED BY draft-irtf-dtnrg-bundle-retrans-block
> 
> HIPRG Working Group, IRTF Area
> draft-ahrenholz-hiprg-dht POTENTIALLY REPLACED BY draft-irtf-hiprg-dht
> 
> MOBOPTS Working Group, IRTF Area
> draft-koki-mobopts-l2-abstractions POTENTIALLY REPLACED BY draft-irtf-mobopts-l2-abstractions
> draft-ohba-mobopts-mpa-framework POTENTIALLY REPLACED BY draft-irtf-mobopts-mpa-framework
> draft-schmidt-mobopts-mmcastv6-ps POTENTIALLY REPLACED BY draft-irtf-mobopts-mmcastv6-ps
> draft-weniger-mobopts-mip6-cnlocpriv POTENTIALLY REPLACED BY draft-irtf-mobopts-mip6-cnlocpriv
> 
> P2PRG Working Group, IRTF Area
> draft-gurbani-p2prg-simulation-survey POTENTIALLY REPLACED BY draft-irtf-p2prg-simulation-survey
> 
> -----------------------------------------------------------------
> IRTF-CONCLUDED Area
> -----------------------------------------------------------------
> -----------------------------------------------------------------
> OPS Area
> -----------------------------------------------------------------
> ARMD Working Group, OPS Area
> draft-dunbar-armd-problem-statement POTENTIALLY REPLACED BY draft-ietf-armd-problem-statement
> 
> BMWG Working Group, OPS Area
> draft-janovak-bmwg-ipflow-meth POTENTIALLY REPLACED BY draft-ietf-bmwg-ipflow-meth
> draft-morton-bmwg-imix-genome POTENTIALLY REPLACED BY draft-ietf-bmwg-imix-genome
> 
> DIME Working Group, OPS Area
> draft-zorn-dime-rfc4005bis POTENTIALLY REPLACED BY draft-ietf-dime-rfc4005bis
> 
> EMAN Working Group, OPS Area
> draft-tychon-eman-applicability-statement POTENTIALLY REPLACED BY draft-ietf-eman-applicability-statement
> 
> GROW Working Group, OPS Area
> draft-dimitri-grow-rss POTENTIALLY REPLACED BY draft-ietf-grow-rss
> draft-manderson-grow-geomrt POTENTIALLY REPLACED BY draft-ietf-grow-geomrt
> 
> IPFIX Working Group, OPS Area
> draft-boschi-ipfix-anon POTENTIALLY REPLACED BY draft-ietf-ipfix-anon
> draft-boschi-ipfix-exporting-type POTENTIALLY REPLACED BY draft-ietf-ipfix-exporting-type
> draft-claise-ipfix-export-per-sctp-stream POTENTIALLY REPLACED BY draft-ietf-ipfix-export-per-sctp-stream
> draft-claise-ipfix-protocol-rfc5101bis POTENTIALLY REPLACED BY draft-ietf-ipfix-protocol-rfc5101bis
> draft-dkcm-ipfix-rfc5815bis POTENTIALLY REPLACED BY draft-ietf-ipfix-rfc5815bis
> draft-gupta-ipfix-reliability-template-ext POTENTIALLY REPLACED BY draft-ietf-ipfix-reliability-template-ext
> draft-trammell-ipfix-file POTENTIALLY REPLACED BY draft-ietf-ipfix-file
> 
> MBONED Working Group, OPS Area
> draft-asaeda-mboned-mtrace-v2 POTENTIALLY REPLACED BY draft-ietf-mboned-mtrace-v2
> draft-asaeda-mboned-session-announcement-req POTENTIALLY REPLACED BY draft-ietf-mboned-session-announcement-req
> draft-bipi-mboned-ip-multicast-pm-requirement POTENTIALLY REPLACED BY draft-ietf-mboned-ip-multicast-pm-requirement
> draft-venaas-mboned-mcaddrdoc POTENTIALLY REPLACED BY draft-ietf-mboned-mcaddrdoc
> draft-venaas-mboned-ssmping POTENTIALLY REPLACED BY draft-ietf-mboned-ssmping
> 
> NETCONF Working Group, OPS Area
> draft-bierman-netconf-access-control POTENTIALLY REPLACED BY draft-ietf-netconf-access-control
> draft-bierman-netconf-with-defaults POTENTIALLY REPLACED BY draft-ietf-netconf-with-defaults
> draft-chisholm-netconf-monitoring POTENTIALLY REPLACED BY draft-ietf-netconf-monitoring
> 
> NETMOD Working Group, OPS Area
> draft-bierman-netmod-system-mgmt POTENTIALLY REPLACED BY draft-ietf-netmod-system-mgmt
> draft-bjorklund-netmod-interfaces-cfg POTENTIALLY REPLACED BY draft-ietf-netmod-interfaces-cfg
> draft-bjorklund-netmod-ip-cfg POTENTIALLY REPLACED BY draft-ietf-netmod-ip-cfg
> draft-lhotka-netmod-routing-cfg POTENTIALLY REPLACED BY draft-ietf-netmod-routing-cfg
> draft-schoenw-netmod-smi-yang POTENTIALLY REPLACED BY draft-ietf-netmod-smi-yang
> 
> OPSAWG Working Group, OPS Area
> draft-mizrahi-opsawg-oam-overview POTENTIALLY REPLACED BY draft-ietf-opsawg-oam-overview
> 
> OPSEC Working Group, OPS Area
> draft-gont-opsec-icmp-filtering POTENTIALLY REPLACED BY draft-ietf-opsec-icmp-filtering
> draft-gont-opsec-ip-security POTENTIALLY REPLACED BY draft-ietf-opsec-ip-security
> 
> RADEXT Working Group, OPS Area
> draft-dekok-radext-dtls POTENTIALLY REPLACED BY draft-ietf-radext-dtls
> draft-dekok-radext-radius-extensions POTENTIALLY REPLACED BY draft-ietf-radext-radius-extensions
> draft-dekok-radext-tcp-transport POTENTIALLY REPLACED BY draft-ietf-radext-tcp-transport
> draft-lourdelet-radext-ipv6-access POTENTIALLY REPLACED BY draft-ietf-radext-ipv6-access
> draft-nelson-radext-crypto-agility-requirements POTENTIALLY REPLACED BY draft-ietf-radext-crypto-agility-requirements
> draft-tiwari-radext-tunnel-type POTENTIALLY REPLACED BY draft-ietf-radext-tunnel-type
> 
> V6OPS Working Group, OPS Area
> draft-hilliard-v6ops-ipv6-discard-prefix POTENTIALLY REPLACED BY draft-ietf-v6ops-ipv6-discard-prefix
> draft-rgaglian-v6ops-v6inixp POTENTIALLY REPLACED BY draft-ietf-v6ops-v6inixp
> draft-vandevelde-v6ops-ra-guard POTENTIALLY REPLACED BY draft-ietf-v6ops-ra-guard
> draft-wbeebee-v6ops-ipv6-cpe-router-bis POTENTIALLY REPLACED BY draft-ietf-v6ops-ipv6-cpe-router-bis
> 
> -----------------------------------------------------------------
> RAI Area
> -----------------------------------------------------------------
> ATOCA Working Group, RAI Area
> draft-rosen-atoca-cap POTENTIALLY REPLACED BY draft-ietf-atoca-cap
> 
> BLISS Working Group, RAI Area
> draft-elwell-bliss-ach-analysis POTENTIALLY REPLACED BY draft-ietf-bliss-ach-analysis
> draft-poetzl-bliss-call-completion POTENTIALLY REPLACED BY draft-ietf-bliss-call-completion
> draft-procter-bliss-call-park-extension POTENTIALLY REPLACED BY draft-ietf-bliss-call-park-extension
> draft-rosenberg-bliss-problem-statement POTENTIALLY REPLACED BY draft-ietf-bliss-problem-statement
> 
> CLUE Working Group, RAI Area
> draft-romanow-clue-framework POTENTIALLY REPLACED BY draft-ietf-clue-framework
> draft-romanow-clue-telepresence-requirements POTENTIALLY REPLACED BY draft-ietf-clue-telepresence-requirements
> draft-romanow-clue-telepresence-use-cases POTENTIALLY REPLACED BY draft-ietf-clue-telepresence-use-cases
> 
> CODEC Working Group, RAI Area
> draft-valin-codec-guidelines POTENTIALLY REPLACED BY draft-ietf-codec-guidelines
> draft-valin-codec-results POTENTIALLY REPLACED BY draft-ietf-codec-results
> 
> DRINKS Working Group, RAI Area
> draft-channabasappa-drinks-usecases-requirements POTENTIALLY REPLACED BY draft-ietf-drinks-usecases-requirements
> 
> GEOPRIV Working Group, RAI Area
> draft-barnes-geopriv-policy-uri POTENTIALLY REPLACED BY draft-ietf-geopriv-policy-uri
> draft-mayrhofer-geopriv-geo-uri POTENTIALLY REPLACED BY draft-ietf-geopriv-geo-uri
> draft-winterbottom-geopriv-local-civic POTENTIALLY REPLACED BY draft-ietf-geopriv-local-civic
> 
> MMUSIC Working Group, RAI Area
> draft-garcia-mmusic-sdp-miscellaneous-caps POTENTIALLY REPLACED BY draft-ietf-mmusic-sdp-miscellaneous-caps
> draft-greevenbosch-mmusic-parallax-attribute POTENTIALLY REPLACED BY draft-ietf-mmusic-parallax-attribute
> draft-greevenbosch-mmusic-signal-3d-format POTENTIALLY REPLACED BY draft-ietf-mmusic-signal-3d-format
> draft-holmberg-mmusic-sdp-bundle-negotiation POTENTIALLY REPLACED BY draft-ietf-mmusic-sdp-bundle-negotiation
> draft-loreto-mmusic-sctp-sdp POTENTIALLY REPLACED BY draft-ietf-mmusic-sctp-sdp
> draft-polk-mmusic-traffic-class-for-sdp POTENTIALLY REPLACED BY draft-ietf-mmusic-traffic-class-for-sdp
> 
> P2PSIP Working Group, RAI Area
> draft-bryan-p2psip-reload POTENTIALLY REPLACED BY draft-ietf-p2psip-reload
> draft-zong-p2psip-drr POTENTIALLY REPLACED BY draft-ietf-p2psip-drr
> draft-zong-p2psip-rpr POTENTIALLY REPLACED BY draft-ietf-p2psip-rpr
> 
> PAYLOAD Working Group, RAI Area
> draft-westin-payload-vp8 POTENTIALLY REPLACED BY draft-ietf-payload-vp8
> 
> RTCWEB Working Group, RAI Area
> draft-uberti-rtcweb-jsep POTENTIALLY REPLACED BY draft-ietf-rtcweb-jsep
> 
> SIPCORE Working Group, RAI Area
> draft-holmberg-sipcore-proxy-feature POTENTIALLY REPLACED BY draft-ietf-sipcore-proxy-feature
> 
> SOC Working Group, RAI Area
> draft-noel-soc-overload-rate-control POTENTIALLY REPLACED BY draft-ietf-soc-overload-rate-control
> draft-shen-soc-load-control-event-package POTENTIALLY REPLACED BY draft-ietf-soc-load-control-event-package
> 
> XMPP Working Group, RAI Area
> draft-barnes-xmpp-dna POTENTIALLY REPLACED BY draft-ietf-xmpp-dna
> draft-miller-xmpp-e2e POTENTIALLY REPLACED BY draft-ietf-xmpp-e2e
> draft-saintandre-xmpp-6122bis POTENTIALLY REPLACED BY draft-ietf-xmpp-6122bis
> 
> XRBLOCK Working Group, RAI Area
> draft-clark-xrblock-rtcp-xr-qoe POTENTIALLY REPLACED BY draft-ietf-xrblock-rtcp-xr-qoe
> 
> -----------------------------------------------------------------
> RTG Area
> -----------------------------------------------------------------
> BFD Working Group, RTG Area
> draft-bhatia-bfd-hmac-sha POTENTIALLY REPLACED BY draft-ietf-bfd-hmac-sha
> 
> CCAMP Working Group, RTG Area
> draft-bccg-ccamp-otn-g709-info-model POTENTIALLY REPLACED BY draft-ietf-ccamp-otn-g709-info-model
> draft-berger-ccamp-assoc-info POTENTIALLY REPLACED BY draft-ietf-ccamp-assoc-info
> draft-bernstein-ccamp-wson-signaling POTENTIALLY REPLACED BY draft-ietf-ccamp-wson-signaling
> 
> FORCES Working Group, RTG Area
> draft-hadi-forces-sctptml POTENTIALLY REPLACED BY draft-ietf-forces-sctptml
> draft-haleplidis-forces-implementation-experience POTENTIALLY REPLACED BY draft-ietf-forces-implementation-experience
> 
> IDR Working Group, RTG Area
> draft-decraene-idr-reserved-extended-communities POTENTIALLY REPLACED BY draft-ietf-idr-reserved-extended-communities
> draft-keyupate-idr-bgp-gr-notification POTENTIALLY REPLACED BY draft-ietf-idr-bgp-gr-notification
> draft-keyur-idr-enhanced-gr POTENTIALLY REPLACED BY draft-ietf-idr-enhanced-gr
> draft-raszuk-idr-flow-spec-v6 POTENTIALLY REPLACED BY draft-ietf-idr-flow-spec-v6
> draft-wkumari-idr-as0 POTENTIALLY REPLACED BY draft-ietf-idr-as0
> 
> ISIS Working Group, RTG Area
> draft-chopps-isis-bfd-tlv POTENTIALLY REPLACED BY draft-ietf-isis-bfd-tlv
> draft-ginsberg-isis-genapp POTENTIALLY REPLACED BY draft-ietf-isis-genapp
> draft-previdi-isis-mi POTENTIALLY REPLACED BY draft-ietf-isis-mi
> draft-shen-isis-oper-enhance POTENTIALLY REPLACED BY draft-ietf-isis-oper-enhance
> 
> L2VPN Working Group, RTG Area
> draft-delord-l2vpn-ldp-vpls-broadcast-exten POTENTIALLY REPLACED BY draft-ietf-l2vpn-ldp-vpls-broadcast-exten
> draft-henderickx-l2vpn-vpls-multihoming POTENTIALLY REPLACED BY draft-ietf-l2vpn-vpls-multihoming
> draft-key-l2vpn-etree-frwk POTENTIALLY REPLACED BY draft-ietf-l2vpn-etree-frwk
> draft-kompella-l2vpn-vpls-multihoming POTENTIALLY REPLACED BY draft-ietf-l2vpn-vpls-multihoming
> draft-pdutta-l2vpn-vpls-ldp-mac-opt POTENTIALLY REPLACED BY draft-ietf-l2vpn-vpls-ldp-mac-opt
> draft-pkwok-l2vpn-vpls-macflush-ld POTENTIALLY REPLACED BY draft-ietf-l2vpn-vpls-macflush-ld
> draft-sajassi-l2vpn-pbb-evpn POTENTIALLY REPLACED BY draft-ietf-l2vpn-pbb-evpn
> draft-sajassi-l2vpn-vpls-pbb-interop POTENTIALLY REPLACED BY draft-ietf-l2vpn-vpls-pbb-interop
> 
> L3VPN Working Group, RTG Area
> draft-rekhter-l3vpn-virtual-hub POTENTIALLY REPLACED BY draft-ietf-l3vpn-virtual-hub
> 
> MANET Working Group, RTG Area
> draft-herberg-manet-nhdp-sec POTENTIALLY REPLACED BY draft-ietf-manet-nhdp-sec
> draft-herberg-manet-nhdp-sec-threats POTENTIALLY REPLACED BY draft-ietf-manet-nhdp-sec-threats
> 
> MPLS Working Group, RTG Area
> draft-frost-mpls-tp-loss-delay-profile POTENTIALLY REPLACED BY draft-ietf-mpls-tp-loss-delay-profile
> draft-koike-mpls-tp-temporal-hitless-psm POTENTIALLY REPLACED BY draft-ietf-mpls-tp-temporal-hitless-psm
> draft-liu-mpls-tp-ring-protection POTENTIALLY REPLACED BY draft-ietf-mpls-tp-ring-protection
> draft-raggarwa-mpls-seamless-mcast POTENTIALLY REPLACED BY draft-ietf-mpls-seamless-mcast
> 
> OSPF Working Group, RTG Area
> draft-acee-ospf-multi-instance POTENTIALLY REPLACED BY draft-ietf-ospf-multi-instance
> draft-acee-ospf-transport-instance POTENTIALLY REPLACED BY draft-ietf-ospf-transport-instance
> draft-cheng-ospf-ipv4-embedded-ipv6-routing POTENTIALLY REPLACED BY draft-ietf-ospf-ipv4-embedded-ipv6-routing
> draft-nguyen-ospf-lls POTENTIALLY REPLACED BY draft-ietf-ospf-lls
> draft-nsheth-ospf-hybrid-bcast-and-p2mp POTENTIALLY REPLACED BY draft-ietf-ospf-hybrid-bcast-and-p2mp
> draft-ogier-ospf-dbex-opt POTENTIALLY REPLACED BY draft-ietf-ospf-dbex-opt
> draft-retana-ospf-rfc3137bis POTENTIALLY REPLACED BY draft-ietf-ospf-rfc3137bis
> draft-venkata-ospf-dynamic-hostname POTENTIALLY REPLACED BY draft-ietf-ospf-dynamic-hostname
> 
> PCE Working Group, RTG Area
> draft-tang-pce-stateful-pce POTENTIALLY REPLACED BY draft-ietf-pce-stateful-pce
> draft-zhao-pce-pcep-inter-domain-p2mp-procedures POTENTIALLY REPLACED BY draft-ietf-pce-pcep-inter-domain-p2mp-procedures
> 
> PIM Working Group, RTG Area
> draft-hou-pim-drlb POTENTIALLY REPLACED BY draft-ietf-pim-drlb
> 
> PWE3 Working Group, RTG Area
> draft-bryant-pwe3-packet-pw POTENTIALLY REPLACED BY draft-ietf-pwe3-packet-pw
> draft-delregno-pwe3-pw-vccv-impl-survey-results POTENTIALLY REPLACED BY draft-ietf-pwe3-pw-vccv-impl-survey-results
> draft-jin-pwe3-cbit-negotiation POTENTIALLY REPLACED BY draft-ietf-pwe3-cbit-negotiation
> draft-raza-pwe3-pw-typed-wc-fec POTENTIALLY REPLACED BY draft-ietf-pwe3-pw-typed-wc-fec
> 
> ROLL Working Group, RTG Area
> draft-dt-roll-p2p-rpl POTENTIALLY REPLACED BY draft-ietf-roll-p2p-rpl
> draft-gnawali-roll-minrank-hysteresis-of POTENTIALLY REPLACED BY draft-ietf-roll-minrank-hysteresis-of
> draft-goyal-roll-p2p-measurement POTENTIALLY REPLACED BY draft-ietf-roll-p2p-measurement
> draft-levis-roll-trickle POTENTIALLY REPLACED BY draft-ietf-roll-trickle
> draft-popa-roll-applicability-ami POTENTIALLY REPLACED BY draft-ietf-roll-applicability-ami
> draft-tsao-roll-security-framework POTENTIALLY REPLACED BY draft-ietf-roll-security-framework
> 
> RTGWG Working Group, RTG Area
> draft-atlas-rtgwg-mrt-frr-architecture POTENTIALLY REPLACED BY draft-ietf-rtgwg-mrt-frr-architecture
> 
> -----------------------------------------------------------------
> SEC Area
> -----------------------------------------------------------------
> ABFAB Working Group, SEC Area
> draft-lear-abfab-arch POTENTIALLY REPLACED BY draft-ietf-abfab-arch
> 
> HOKEY Working Group, SEC Area
> draft-wu-hokey-rfc5296bis POTENTIALLY REPLACED BY draft-ietf-hokey-rfc5296bis
> 
> MILE Working Group, SEC Area
> draft-moriarty-mile-grc-exchange POTENTIALLY REPLACED BY draft-ietf-mile-grc-exchange
> 
> NEA Working Group, SEC Area
> draft-hanna-nea-pt-eap POTENTIALLY REPLACED BY draft-ietf-nea-pt-eap
> draft-sangster-nea-pt-tls POTENTIALLY REPLACED BY draft-ietf-nea-pt-tls
> 
> OAUTH Working Group, SEC Area
> draft-mortimore-oauth-assertions POTENTIALLY REPLACED BY draft-ietf-oauth-assertions
> 
> PKIX Working Group, SEC Area
> draft-cooper-pkix-rfc2560bis POTENTIALLY REPLACED BY draft-ietf-pkix-rfc2560bis
> draft-cooper-pkix-rfc5280-clarifications POTENTIALLY REPLACED BY draft-ietf-pkix-rfc5280-clarifications
> draft-santesson-pkix-certimage POTENTIALLY REPLACED BY draft-ietf-pkix-certimage
> 
> TLS Working Group, SEC Area
> draft-kanno-tls-camellia POTENTIALLY REPLACED BY draft-ietf-tls-camellia
> draft-rescorla-tls-suiteb POTENTIALLY REPLACED BY draft-ietf-tls-suiteb
> draft-seggelmann-tls-dtls-heartbeat POTENTIALLY REPLACED BY draft-ietf-tls-dtls-heartbeat
> 
> -----------------------------------------------------------------
> TSV Area
> -----------------------------------------------------------------
> ALTO Working Group, TSV Area
> draft-song-alto-server-discovery POTENTIALLY REPLACED BY draft-ietf-alto-server-discovery
> draft-stiemerling-alto-deployments POTENTIALLY REPLACED BY draft-ietf-alto-deployments
> 
> BEHAVE Working Group, TSV Area
> draft-liu-behave-ftp64 POTENTIALLY REPLACED BY draft-ietf-behave-ftp64
> draft-penno-behave-64-analysis POTENTIALLY REPLACED BY draft-ietf-behave-64-analysis
> 
> CDNI Working Group, TSV Area
> draft-watson-cdni-use-cases POTENTIALLY REPLACED BY draft-ietf-cdni-use-cases
> 
> CONEX Working Group, TSV Area
> draft-krishnan-conex-destopt POTENTIALLY REPLACED BY draft-ietf-conex-destopt
> draft-kuehlewind-conex-tcp-modifications POTENTIALLY REPLACED BY draft-ietf-conex-tcp-modifications
> draft-mathis-conex-abstract-mech POTENTIALLY REPLACED BY draft-ietf-conex-abstract-mech
> draft-moncaster-conex-concepts-uses POTENTIALLY REPLACED BY draft-ietf-conex-concepts-uses
> 
> DECADE Working Group, TSV Area
> draft-alimi-decade-arch POTENTIALLY REPLACED BY draft-ietf-decade-arch
> draft-chen-decade-integration-example POTENTIALLY REPLACED BY draft-ietf-decade-integration-example
> draft-huang-decade-integration-example POTENTIALLY REPLACED BY draft-ietf-decade-integration-example
> 
> FECFRAME Working Group, TSV Area
> draft-roca-fecframe-ldpc POTENTIALLY REPLACED BY draft-ietf-fecframe-ldpc
> draft-roca-fecframe-simple-rs POTENTIALLY REPLACED BY draft-ietf-fecframe-simple-rs
> 
> IPPM Working Group, TSV Area
> draft-baillargeon-ippm-twamp-value-added-octets POTENTIALLY REPLACED BY draft-ietf-ippm-twamp-value-added-octets
> draft-geib-ippm-metrictest POTENTIALLY REPLACED BY draft-ietf-ippm-metrictest
> draft-morton-ippm-rt-loss POTENTIALLY REPLACED BY draft-ietf-ippm-rt-loss
> draft-morton-ippm-testplan-rfc2679 POTENTIALLY REPLACED BY draft-ietf-ippm-testplan-rfc2679
> 
> NFSV4 Working Group, TSV Area
> draft-alexrn-nfsv4-ipv6 POTENTIALLY REPLACED BY draft-ietf-nfsv4-ipv6
> draft-dnoveck-nfsv4-migration-issues POTENTIALLY REPLACED BY draft-ietf-nfsv4-migration-issues
> draft-eisler-nfsv4-minorversion-2-requirements POTENTIALLY REPLACED BY draft-ietf-nfsv4-minorversion-2-requirements
> draft-faibish-nfsv4-pnfs-access-permissions-check POTENTIALLY REPLACED BY draft-ietf-nfsv4-pnfs-access-permissions-check
> draft-faibish-nfsv4-pnfs-block-disk-protection POTENTIALLY REPLACED BY draft-ietf-nfsv4-pnfs-block-disk-protection
> draft-haynes-nfsv4-minorversion2 POTENTIALLY REPLACED BY draft-ietf-nfsv4-minorversion2
> draft-haynes-nfsv4-minorversion2-dot-x POTENTIALLY REPLACED BY draft-ietf-nfsv4-minorversion2-dot-x
> draft-quigley-nfsv4-labreqs POTENTIALLY REPLACED BY draft-ietf-nfsv4-labreqs
> 
> PCN Working Group, TSV Area
> draft-karagiannis-pcn-signaling-requirements POTENTIALLY REPLACED BY draft-ietf-pcn-signaling-requirements
> 
> PPSP Working Group, TSV Area
> draft-gu-ppsp-peer-protocol POTENTIALLY REPLACED BY draft-ietf-ppsp-peer-protocol
> draft-gu-ppsp-survey POTENTIALLY REPLACED BY draft-ietf-ppsp-survey
> 
> TCPM Working Group, TSV Area
> draft-blanton-tcpm-3517bis POTENTIALLY REPLACED BY draft-ietf-tcpm-3517bis
> draft-cheng-tcpm-fastopen POTENTIALLY REPLACED BY draft-ietf-tcpm-fastopen
> draft-gont-tcpm-rfc1948bis POTENTIALLY REPLACED BY draft-ietf-tcpm-rfc1948bis
> draft-henderson-tcpm-rfc3782-bis POTENTIALLY REPLACED BY draft-ietf-tcpm-rfc3782-bis
> draft-hkchu-tcpm-initcwnd POTENTIALLY REPLACED BY draft-ietf-tcpm-initcwnd
> draft-mathis-tcpm-proportional-rate-reduction POTENTIALLY REPLACED BY draft-ietf-tcpm-proportional-rate-reduction
> draft-touch-tcpm-experimental-options POTENTIALLY REPLACED BY draft-ietf-tcpm-experimental-options
> 
> TSVWG Working Group, TSV Area
> draft-gont-tsvwg-source-quench POTENTIALLY REPLACED BY draft-ietf-tsvwg-source-quench
> draft-polk-tsvwg-intserv-multiple-tspec POTENTIALLY REPLACED BY draft-ietf-tsvwg-intserv-multiple-tspec
> 
> -----------------------------------------------------------------
> Potential Inconsistencies
> -----------------------------------------------------------------
> draft-ietf-6lowpan-nd may replace one or more of 2 individual IDs - check this
> draft-ietf-armd-problem-statement may replace one or more of 2 individual IDs - check this
> draft-ietf-avt-rtp-gsm-hr may replace one or more of 3 individual IDs - check this
> draft-ietf-avt-rtp-svc may replace one or more of 2 individual IDs - check this
> draft-ietf-bmwg-ipflow-meth may replace one or more of 2 individual IDs - check this
> draft-ietf-cdni-use-cases may replace one or more of 2 individual IDs - check this
> draft-ietf-decade-integration-example may replace one or more of 2 individual IDs - check this
> draft-ietf-decade-survey may replace one or more of 2 individual IDs - check this
> draft-ietf-dhc-dhcpv4-bulk-leasequery may replace one or more of 2 individual IDs - check this
> draft-ietf-forces-tmlsp may replace one or more of 2 individual IDs - check this
> draft-ietf-ipfix-biflow may replace one or more of 2 individual IDs - check this
> draft-ietf-l2tpext-tdm may replace one or more of 2 individual IDs - check this
> draft-ietf-l2vpn-vpls-multihoming may replace one or more of 2 individual IDs - check this
> draft-ietf-mpls-tp-fault may replace one or more of 2 individual IDs - check this
> draft-ietf-mpls-tp-ring-protection may replace one or more of 2 individual IDs - check this
> draft-ietf-netconf-monitoring may replace one or more of 2 individual IDs - check this
> draft-ietf-netlmm-lma-discovery may replace one or more of 2 individual IDs - check this
> draft-ietf-netlmm-mip-interactions may replace one or more of 2 individual IDs - check this
> draft-ietf-pce-stateful-pce may replace one or more of 2 individual IDs - check this
> draft-ietf-sip-saml may replace one or more of 2 individual IDs - check this
> draft-ietf-sipping-service-identification may replace one or more of 2 individual IDs - check this
> draft-ietf-softwire-dslite-deployment may replace one or more of 2 individual IDs - check this
> draft-ietf-trill-rbridge-arch may replace one or more of 2 individual IDs - check this
> 
 		 	   		  
--_f81acde2-b07d-42d6-8e4b-7f437544ad99_
Content-Type: text/html; charset="gb2312"
Content-Transfer-Encoding: 8bit

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
excuse me for naive question, how to send a ticket to the secretariat&nbsp;?<BR>
&nbsp;<BR>
Best,<BR>
&nbsp;<BR>
-Hui<BR>&nbsp;<BR>
<DIV>
<DIV id=SkyDrivePlaceholder></DIV>&gt; From: lars@netapp.com<BR>&gt; To: wgchairs@ietf.org; irsg@irtf.org<BR>&gt; Subject: latest missing replaced-by information<BR>&gt; Date: Wed, 18 Apr 2012 08:49:31 +0000<BR>&gt; <BR>&gt; Hi,<BR>&gt; <BR>&gt; here's yet another installment in the series of reports on potentially missing "replaced-by" relationships in the IETF datatracker.<BR>&gt; <BR>&gt; *** NEW *** Also includes IRTF documents now.<BR>&gt; <BR>&gt; WG and RG chairs are encouraged to check whether these are accurate for their groups, and if so, send a ticket to the secretariat instructing them to "record in the database that draft X replaced draft Y".<BR>&gt; <BR>&gt; As always, double-check before reporting to the secretariat. Also, see list of possible inconsistencies at the end of the report.<BR>&gt; <BR>&gt; (Note that the IPR disclosure search tool uses these replaced-by relationships, so keeping them up-to-date is actually useful and not just WG hygiene.)<BR>&gt; <B
 R>&gt; Lars<BR>&gt; <BR>&gt; <BR>&gt; -----------------------------------------------------------------<BR>&gt; APP Area<BR>&gt; -----------------------------------------------------------------<BR>&gt; CORE Working Group, APP Area<BR>&gt; draft-rahman-core-groupcomm POTENTIALLY REPLACED BY draft-ietf-core-groupcomm<BR>&gt; <BR>&gt; EAI Working Group, APP Area<BR>&gt; draft-duerst-eai-mailto POTENTIALLY REPLACED BY draft-ietf-eai-mailto<BR>&gt; draft-yao-eai-rfc5336bis POTENTIALLY REPLACED BY draft-ietf-eai-rfc5336bis<BR>&gt; <BR>&gt; PAWS Working Group, APP Area<BR>&gt; draft-probasco-paws-problem-stmt-usecases-rqmts POTENTIALLY REPLACED BY draft-ietf-paws-problem-stmt-usecases-rqmts<BR>&gt; <BR>&gt; VCARDDAV Working Group, APP Area<BR>&gt; draft-cauchie-vcarddav-oma-cab-extensions POTENTIALLY REPLACED BY draft-ietf-vcarddav-oma-cab-extensions<BR>&gt; <BR>&gt; -----------------------------------------------------------------<BR>&gt; CONCLUDED Area<BR>&gt; ------------------
 -----------------------------------------------<BR>&gt; ATOMPUB Working Group, CONCLUDED Area<BR>&gt; draft-snell-atompub-autodiscovery POTENTIALLY REPLACED BY draft-ietf-atompub-autodiscovery<BR>&gt; <BR>&gt; HTTP Working Group, CONCLUDED Area<BR>&gt; draft-wallis-http-digest-auth-a3a8 POTENTIALLY REPLACED BY draft-ietf-http-digest-auth-a3a8<BR>&gt; <BR>&gt; IDNABIS Working Group, CONCLUDED Area<BR>&gt; draft-faltstrom-idnabis-tables POTENTIALLY REPLACED BY draft-ietf-idnabis-tables<BR>&gt; <BR>&gt; IMAP Working Group, CONCLUDED Area<BR>&gt; draft-crispin-imap-compat POTENTIALLY REPLACED BY draft-ietf-imap-compat<BR>&gt; <BR>&gt; TFTPEXTS Working Group, CONCLUDED Area<BR>&gt; draft-malkin-tftpexts-blksize-opt POTENTIALLY REPLACED BY draft-ietf-tftpexts-blksize-opt<BR>&gt; draft-malkin-tftpexts-option-ext POTENTIALLY REPLACED BY draft-ietf-tftpexts-option-ext<BR>&gt; draft-malkin-tftpexts-options POTENTIALLY REPLACED BY draft-ietf-tftpexts-options<BR>&gt; <BR>&gt; XMPP Worki
 ng Group, CONCLUDED Area<BR>&gt; draft-barnes-xmpp-dna POTENTIALLY REPLACED BY draft-ietf-xmpp-dna<BR>&gt; draft-miller-xmpp-e2e POTENTIALLY REPLACED BY draft-ietf-xmpp-e2e<BR>&gt; draft-saintandre-xmpp-6122bis POTENTIALLY REPLACED BY draft-ietf-xmpp-6122bis<BR>&gt; <BR>&gt; MIPSHOP Working Group, CONCLUDED Area<BR>&gt; draft-xia-mipshop-fmip-ptp POTENTIALLY REPLACED BY draft-ietf-mipshop-fmip-ptp<BR>&gt; <BR>&gt; NETLMM Working Group, CONCLUDED Area<BR>&gt; draft-cui-netlmm-mip-interactions POTENTIALLY REPLACED BY draft-ietf-netlmm-mip-interactions<BR>&gt; draft-glenn-netlmm-pmipv6-mib POTENTIALLY REPLACED BY draft-ietf-netlmm-pmipv6-mib<BR>&gt; draft-korhonen-netlmm-lma-discovery POTENTIALLY REPLACED BY draft-ietf-netlmm-lma-discovery<BR>&gt; draft-xia-netlmm-lma-discovery POTENTIALLY REPLACED BY draft-ietf-netlmm-lma-discovery<BR>&gt; <BR>&gt; SEND Working Group, CONCLUDED Area<BR>&gt; draft-arkko-send-cga POTENTIALLY REPLACED BY draft-ietf-send-cga<BR>&gt; draft-arkko-se
 nd-ndopt POTENTIALLY REPLACED BY draft-ietf-send-ndopt<BR>&gt; <BR>&gt; SHIM6 Working Group, CONCLUDED Area<BR>&gt; draft-garcia-shim6-applicability POTENTIALLY REPLACED BY draft-ietf-shim6-applicability<BR>&gt; <BR>&gt; CAPWAP Working Group, CONCLUDED Area<BR>&gt; draft-yangshi-capwap-802dot11-mib POTENTIALLY REPLACED BY draft-ietf-capwap-802dot11-mib<BR>&gt; draft-yangshi-capwap-base-mib POTENTIALLY REPLACED BY draft-ietf-capwap-base-mib<BR>&gt; <BR>&gt; RMONMIB Working Group, CONCLUDED Area<BR>&gt; draft-bierman-rmonmib-hc-alarm-mib POTENTIALLY REPLACED BY draft-ietf-rmonmib-hc-alarm-mib<BR>&gt; <BR>&gt; MEGACO Working Group, CONCLUDED Area<BR>&gt; draft-blatherwick-megaco-ipphone POTENTIALLY REPLACED BY draft-ietf-megaco-ipphone<BR>&gt; <BR>&gt; SIGTRAN Working Group, CONCLUDED Area<BR>&gt; draft-anil-sigtran-dua POTENTIALLY REPLACED BY draft-ietf-sigtran-dua<BR>&gt; <BR>&gt; SIP Working Group, CONCLUDED Area<BR>&gt; draft-arkko-sip-sec-agree POTENTIALLY REPLACED BY draf
 t-ietf-sip-sec-agree<BR>&gt; draft-biggs-sip-replaces POTENTIALLY REPLACED BY draft-ietf-sip-replaces<BR>&gt; draft-pashalidis-sip-saml POTENTIALLY REPLACED BY draft-ietf-sip-saml<BR>&gt; <BR>&gt; SIPPING Working Group, CONCLUDED Area<BR>&gt; draft-drage-sipping-service-identification POTENTIALLY REPLACED BY draft-ietf-sipping-service-identification<BR>&gt; draft-elwell-sipping-update-pai POTENTIALLY REPLACED BY draft-ietf-sipping-update-pai<BR>&gt; draft-hilt-sipping-overload-design POTENTIALLY REPLACED BY draft-ietf-sipping-overload-design<BR>&gt; draft-petrie-sipping-profile-datasets POTENTIALLY REPLACED BY draft-ietf-sipping-profile-datasets<BR>&gt; draft-rosenberg-sipping-service-identification POTENTIALLY REPLACED BY draft-ietf-sipping-service-identification<BR>&gt; draft-zhang-sipping-overlap POTENTIALLY REPLACED BY draft-ietf-sipping-overlap<BR>&gt; <BR>&gt; SPEERMINT Working Group, CONCLUDED Area<BR>&gt; draft-meyer-speermint-reqs-and-terminology POTENTIALLY REPLACE
 D BY draft-ietf-speermint-reqs-and-terminology<BR>&gt; draft-niccolini-speermint-voipthreats POTENTIALLY REPLACED BY draft-ietf-speermint-voipthreats<BR>&gt; <BR>&gt; XCON Working Group, CONCLUDED Area<BR>&gt; draft-barnes-xcon-ccmp POTENTIALLY REPLACED BY draft-ietf-xcon-ccmp<BR>&gt; draft-barnes-xcon-examples POTENTIALLY REPLACED BY draft-ietf-xcon-examples<BR>&gt; <BR>&gt; DKIM Working Group, CONCLUDED Area<BR>&gt; draft-lindsey-dkim-mailinglists POTENTIALLY REPLACED BY draft-ietf-dkim-mailinglists<BR>&gt; <BR>&gt; SACRED Working Group, CONCLUDED Area<BR>&gt; draft-arsenault-sacred-reqs POTENTIALLY REPLACED BY draft-ietf-sacred-reqs<BR>&gt; <BR>&gt; SASL Working Group, CONCLUDED Area<BR>&gt; draft-zeilenga-sasl-crammd5 POTENTIALLY REPLACED BY draft-ietf-sasl-crammd5<BR>&gt; draft-zeilenga-sasl-rfc2222bis POTENTIALLY REPLACED BY draft-ietf-sasl-rfc2222bis<BR>&gt; <BR>&gt; SMIME Working Group, CONCLUDED Area<BR>&gt; draft-dusse-smime-cert POTENTIALLY REPLACED BY draft-ietf-
 smime-cert<BR>&gt; draft-dusse-smime-msg POTENTIALLY REPLACED BY draft-ietf-smime-msg<BR>&gt; <BR>&gt; DIFFSERV Working Group, CONCLUDED Area<BR>&gt; draft-baker-diffserv-mib POTENTIALLY REPLACED BY draft-ietf-diffserv-mib<BR>&gt; draft-black-diffserv-tunnels POTENTIALLY REPLACED BY draft-ietf-diffserv-tunnels<BR>&gt; <BR>&gt; RSVP Working Group, CONCLUDED Area<BR>&gt; draft-berger-rsvp-refresh-reduct POTENTIALLY REPLACED BY draft-ietf-rsvp-refresh-reduct<BR>&gt; <BR>&gt; -----------------------------------------------------------------<BR>&gt; INT Area<BR>&gt; -----------------------------------------------------------------<BR>&gt; 6MAN Working Group, INT Area<BR>&gt; draft-carpenter-6man-uri-zoneid POTENTIALLY REPLACED BY draft-ietf-6man-uri-zoneid<BR>&gt; draft-costa-6man-dad-proxy POTENTIALLY REPLACED BY draft-ietf-6man-dad-proxy<BR>&gt; draft-fujisaki-6man-addr-select-opt POTENTIALLY REPLACED BY draft-ietf-6man-addr-select-opt<BR>&gt; draft-george-6man-3627-historic PO
 TENTIALLY REPLACED BY draft-ietf-6man-3627-historic<BR>&gt; draft-gont-6man-ipv6-atomic-fragments POTENTIALLY REPLACED BY draft-ietf-6man-ipv6-atomic-fragments<BR>&gt; draft-hsingh-6man-enhanced-dad POTENTIALLY REPLACED BY draft-ietf-6man-enhanced-dad<BR>&gt; draft-joshi-6man-neighbor-inform POTENTIALLY REPLACED BY draft-ietf-6man-neighbor-inform<BR>&gt; draft-lynn-6man-6lobac POTENTIALLY REPLACED BY draft-ietf-6man-6lobac<BR>&gt; draft-nordmark-6man-impatient-nud POTENTIALLY REPLACED BY draft-ietf-6man-impatient-nud<BR>&gt; <BR>&gt; ANCP Working Group, INT Area<BR>&gt; draft-lefaucheur-ancp-mc-extensions POTENTIALLY REPLACED BY draft-ietf-ancp-mc-extensions<BR>&gt; <BR>&gt; CSI Working Group, INT Area<BR>&gt; draft-jiang-csi-dhcpv6-cga-ps POTENTIALLY REPLACED BY draft-ietf-csi-dhcpv6-cga-ps<BR>&gt; draft-rgaglian-csi-send-name-type-registry POTENTIALLY REPLACED BY draft-ietf-csi-send-name-type-registry<BR>&gt; <BR>&gt; DHC Working Group, INT Area<BR>&gt; draft-jiang-dhc-cga
 -config-dhcpv6 POTENTIALLY REPLACED BY draft-ietf-dhc-cga-config-dhcpv6<BR>&gt; draft-jjmb-dhc-dhcpv6-redundancy-consider POTENTIALLY REPLACED BY draft-ietf-dhc-dhcpv6-redundancy-consider<BR>&gt; draft-miles-dhc-dhcpv6-ldra POTENTIALLY REPLACED BY draft-ietf-dhc-dhcpv6-ldra<BR>&gt; draft-mrugalski-dhc-dhcpv6-failover-requirements POTENTIALLY REPLACED BY draft-ietf-dhc-dhcpv6-failover-requirements<BR>&gt; draft-xia-dhc-host-gen-id POTENTIALLY REPLACED BY draft-ietf-dhc-host-gen-id<BR>&gt; <BR>&gt; DNSEXT Working Group, INT Area<BR>&gt; draft-wang-dnsext-newzone-notify POTENTIALLY REPLACED BY draft-ietf-dnsext-newzone-notify<BR>&gt; <BR>&gt; HIP Working Group, INT Area<BR>&gt; draft-camarillo-hip-via POTENTIALLY REPLACED BY draft-ietf-hip-via<BR>&gt; draft-henderson-hip-rfc5206-bis POTENTIALLY REPLACED BY draft-ietf-hip-rfc5206-bis<BR>&gt; draft-jokela-hip-rfc5202-bis POTENTIALLY REPLACED BY draft-ietf-hip-rfc5202-bis<BR>&gt; draft-keranen-hip-native-nat-traversal POTENTIALLY 
 REPLACED BY draft-ietf-hip-native-nat-traversal<BR>&gt; draft-keranen-hip-over-hip POTENTIALLY REPLACED BY draft-ietf-hip-over-hip<BR>&gt; draft-keranen-hip-reload-instance POTENTIALLY REPLACED BY draft-ietf-hip-reload-instance<BR>&gt; draft-moskowitz-hip-rfc4423-bis POTENTIALLY REPLACED BY draft-ietf-hip-rfc4423-bis<BR>&gt; draft-moskowitz-hip-rfc5201-bis POTENTIALLY REPLACED BY draft-ietf-hip-rfc5201-bis<BR>&gt; draft-nikander-hip-hiccups POTENTIALLY REPLACED BY draft-ietf-hip-hiccups<BR>&gt; <BR>&gt; INTAREA Working Group, INT Area<BR>&gt; draft-boucadair-intarea-nat-reveal-analysis POTENTIALLY REPLACED BY draft-ietf-intarea-nat-reveal-analysis<BR>&gt; <BR>&gt; LISP Working Group, INT Area<BR>&gt; draft-jakab-lisp-deployment POTENTIALLY REPLACED BY draft-ietf-lisp-deployment<BR>&gt; draft-maino-lisp-sec POTENTIALLY REPLACED BY draft-ietf-lisp-sec<BR>&gt; draft-meyer-lisp-eid-block POTENTIALLY REPLACED BY draft-ietf-lisp-eid-block<BR>&gt; <BR>&gt; MIF Working Group, INT Ar
 ea<BR>&gt; draft-liu-mif-api-extension POTENTIALLY REPLACED BY draft-ietf-mif-api-extension<BR>&gt; <BR>&gt; MULTIMOB Working Group, INT Area<BR>&gt; draft-schmidt-multimob-pmipv6-source POTENTIALLY REPLACED BY draft-ietf-multimob-pmipv6-source<BR>&gt; draft-wu-multimob-igmp-mld-tuning POTENTIALLY REPLACED BY draft-ietf-multimob-igmp-mld-tuning<BR>&gt; draft-zuniga-multimob-pmipv6-ropt POTENTIALLY REPLACED BY draft-ietf-multimob-pmipv6-ropt<BR>&gt; <BR>&gt; NETEXT Working Group, INT Area<BR>&gt; draft-bernardos-netext-pmipv6-flowmob POTENTIALLY REPLACED BY draft-ietf-netext-pmipv6-flowmob<BR>&gt; draft-korhonen-netext-redirect POTENTIALLY REPLACED BY draft-ietf-netext-redirect<BR>&gt; draft-krishnan-netext-pmip-lr POTENTIALLY REPLACED BY draft-ietf-netext-pmip-lr<BR>&gt; draft-melia-netext-logical-interface-support POTENTIALLY REPLACED BY draft-ietf-netext-logical-interface-support<BR>&gt; draft-zhou-netext-pd-pmip POTENTIALLY REPLACED BY draft-ietf-netext-pd-pmip<BR>&gt; <B
 R>&gt; PCP Working Group, INT Area<BR>&gt; draft-bpw-pcp-dhcp POTENTIALLY REPLACED BY draft-ietf-pcp-dhcp<BR>&gt; draft-bpw-pcp-upnp-igd-interworking POTENTIALLY REPLACED BY draft-ietf-pcp-upnp-igd-interworking<BR>&gt; <BR>&gt; SAVI Working Group, INT Area<BR>&gt; draft-bi-savi-mix POTENTIALLY REPLACED BY draft-ietf-savi-mix<BR>&gt; <BR>&gt; SOFTWIRE Working Group, INT Area<BR>&gt; draft-guo-softwire-6rd-radius-attrib POTENTIALLY REPLACED BY draft-ietf-softwire-6rd-radius-attrib<BR>&gt; draft-ieft-softwire-dslite-deployment POTENTIALLY REPLACED BY draft-ietf-softwire-dslite-deployment<BR>&gt; draft-lee-softwire-dslite-deployment POTENTIALLY REPLACED BY draft-ietf-softwire-dslite-deployment<BR>&gt; draft-maglione-softwire-dslite-radius-ext POTENTIALLY REPLACED BY draft-ietf-softwire-dslite-radius-ext<BR>&gt; draft-qin-softwire-multicast-prefix-option POTENTIALLY REPLACED BY draft-ietf-softwire-multicast-prefix-option<BR>&gt; draft-xu-softwire-mesh-multicast POTENTIALLY REPLAC
 ED BY draft-ietf-softwire-mesh-multicast<BR>&gt; <BR>&gt; TICTOC Working Group, INT Area<BR>&gt; draft-davari-tictoc-1588overmpls POTENTIALLY REPLACED BY draft-ietf-tictoc-1588overmpls<BR>&gt; draft-mizrahi-tictoc-security-requirements POTENTIALLY REPLACED BY draft-ietf-tictoc-security-requirements<BR>&gt; draft-vinay-tictoc-ptp-mib POTENTIALLY REPLACED BY draft-ietf-tictoc-ptp-mib<BR>&gt; <BR>&gt; TRILL Working Group, INT Area<BR>&gt; draft-tissa-trill-cmt POTENTIALLY REPLACED BY draft-ietf-trill-cmt<BR>&gt; <BR>&gt; -----------------------------------------------------------------<BR>&gt; IRTF Area<BR>&gt; -----------------------------------------------------------------<BR>&gt; DTNRG Working Group, IRTF Area<BR>&gt; draft-lindgren-dtnrg-prophet POTENTIALLY REPLACED BY draft-irtf-dtnrg-prophet<BR>&gt; draft-symington-dtnrg-bundle-metadata-block POTENTIALLY REPLACED BY draft-irtf-dtnrg-bundle-metadata-block<BR>&gt; draft-symington-dtnrg-bundle-retrans-block POTENTIALLY REPL
 ACED BY draft-irtf-dtnrg-bundle-retrans-block<BR>&gt; <BR>&gt; HIPRG Working Group, IRTF Area<BR>&gt; draft-ahrenholz-hiprg-dht POTENTIALLY REPLACED BY draft-irtf-hiprg-dht<BR>&gt; <BR>&gt; MOBOPTS Working Group, IRTF Area<BR>&gt; draft-koki-mobopts-l2-abstractions POTENTIALLY REPLACED BY draft-irtf-mobopts-l2-abstractions<BR>&gt; draft-ohba-mobopts-mpa-framework POTENTIALLY REPLACED BY draft-irtf-mobopts-mpa-framework<BR>&gt; draft-schmidt-mobopts-mmcastv6-ps POTENTIALLY REPLACED BY draft-irtf-mobopts-mmcastv6-ps<BR>&gt; draft-weniger-mobopts-mip6-cnlocpriv POTENTIALLY REPLACED BY draft-irtf-mobopts-mip6-cnlocpriv<BR>&gt; <BR>&gt; P2PRG Working Group, IRTF Area<BR>&gt; draft-gurbani-p2prg-simulation-survey POTENTIALLY REPLACED BY draft-irtf-p2prg-simulation-survey<BR>&gt; <BR>&gt; -----------------------------------------------------------------<BR>&gt; IRTF-CONCLUDED Area<BR>&gt; -----------------------------------------------------------------<BR>&gt; --------------------
 ---------------------------------------------<BR>&gt; OPS Area<BR>&gt; -----------------------------------------------------------------<BR>&gt; ARMD Working Group, OPS Area<BR>&gt; draft-dunbar-armd-problem-statement POTENTIALLY REPLACED BY draft-ietf-armd-problem-statement<BR>&gt; <BR>&gt; BMWG Working Group, OPS Area<BR>&gt; draft-janovak-bmwg-ipflow-meth POTENTIALLY REPLACED BY draft-ietf-bmwg-ipflow-meth<BR>&gt; draft-morton-bmwg-imix-genome POTENTIALLY REPLACED BY draft-ietf-bmwg-imix-genome<BR>&gt; <BR>&gt; DIME Working Group, OPS Area<BR>&gt; draft-zorn-dime-rfc4005bis POTENTIALLY REPLACED BY draft-ietf-dime-rfc4005bis<BR>&gt; <BR>&gt; EMAN Working Group, OPS Area<BR>&gt; draft-tychon-eman-applicability-statement POTENTIALLY REPLACED BY draft-ietf-eman-applicability-statement<BR>&gt; <BR>&gt; GROW Working Group, OPS Area<BR>&gt; draft-dimitri-grow-rss POTENTIALLY REPLACED BY draft-ietf-grow-rss<BR>&gt; draft-manderson-grow-geomrt POTENTIALLY REPLACED BY draft-ietf-gr
 ow-geomrt<BR>&gt; <BR>&gt; IPFIX Working Group, OPS Area<BR>&gt; draft-boschi-ipfix-anon POTENTIALLY REPLACED BY draft-ietf-ipfix-anon<BR>&gt; draft-boschi-ipfix-exporting-type POTENTIALLY REPLACED BY draft-ietf-ipfix-exporting-type<BR>&gt; draft-claise-ipfix-export-per-sctp-stream POTENTIALLY REPLACED BY draft-ietf-ipfix-export-per-sctp-stream<BR>&gt; draft-claise-ipfix-protocol-rfc5101bis POTENTIALLY REPLACED BY draft-ietf-ipfix-protocol-rfc5101bis<BR>&gt; draft-dkcm-ipfix-rfc5815bis POTENTIALLY REPLACED BY draft-ietf-ipfix-rfc5815bis<BR>&gt; draft-gupta-ipfix-reliability-template-ext POTENTIALLY REPLACED BY draft-ietf-ipfix-reliability-template-ext<BR>&gt; draft-trammell-ipfix-file POTENTIALLY REPLACED BY draft-ietf-ipfix-file<BR>&gt; <BR>&gt; MBONED Working Group, OPS Area<BR>&gt; draft-asaeda-mboned-mtrace-v2 POTENTIALLY REPLACED BY draft-ietf-mboned-mtrace-v2<BR>&gt; draft-asaeda-mboned-session-announcement-req POTENTIALLY REPLACED BY draft-ietf-mboned-session-announce
 ment-req<BR>&gt; draft-bipi-mboned-ip-multicast-pm-requirement POTENTIALLY REPLACED BY draft-ietf-mboned-ip-multicast-pm-requirement<BR>&gt; draft-venaas-mboned-mcaddrdoc POTENTIALLY REPLACED BY draft-ietf-mboned-mcaddrdoc<BR>&gt; draft-venaas-mboned-ssmping POTENTIALLY REPLACED BY draft-ietf-mboned-ssmping<BR>&gt; <BR>&gt; NETCONF Working Group, OPS Area<BR>&gt; draft-bierman-netconf-access-control POTENTIALLY REPLACED BY draft-ietf-netconf-access-control<BR>&gt; draft-bierman-netconf-with-defaults POTENTIALLY REPLACED BY draft-ietf-netconf-with-defaults<BR>&gt; draft-chisholm-netconf-monitoring POTENTIALLY REPLACED BY draft-ietf-netconf-monitoring<BR>&gt; <BR>&gt; NETMOD Working Group, OPS Area<BR>&gt; draft-bierman-netmod-system-mgmt POTENTIALLY REPLACED BY draft-ietf-netmod-system-mgmt<BR>&gt; draft-bjorklund-netmod-interfaces-cfg POTENTIALLY REPLACED BY draft-ietf-netmod-interfaces-cfg<BR>&gt; draft-bjorklund-netmod-ip-cfg POTENTIALLY REPLACED BY draft-ietf-netmod-ip-cf
 g<BR>&gt; draft-lhotka-netmod-routing-cfg POTENTIALLY REPLACED BY draft-ietf-netmod-routing-cfg<BR>&gt; draft-schoenw-netmod-smi-yang POTENTIALLY REPLACED BY draft-ietf-netmod-smi-yang<BR>&gt; <BR>&gt; OPSAWG Working Group, OPS Area<BR>&gt; draft-mizrahi-opsawg-oam-overview POTENTIALLY REPLACED BY draft-ietf-opsawg-oam-overview<BR>&gt; <BR>&gt; OPSEC Working Group, OPS Area<BR>&gt; draft-gont-opsec-icmp-filtering POTENTIALLY REPLACED BY draft-ietf-opsec-icmp-filtering<BR>&gt; draft-gont-opsec-ip-security POTENTIALLY REPLACED BY draft-ietf-opsec-ip-security<BR>&gt; <BR>&gt; RADEXT Working Group, OPS Area<BR>&gt; draft-dekok-radext-dtls POTENTIALLY REPLACED BY draft-ietf-radext-dtls<BR>&gt; draft-dekok-radext-radius-extensions POTENTIALLY REPLACED BY draft-ietf-radext-radius-extensions<BR>&gt; draft-dekok-radext-tcp-transport POTENTIALLY REPLACED BY draft-ietf-radext-tcp-transport<BR>&gt; draft-lourdelet-radext-ipv6-access POTENTIALLY REPLACED BY draft-ietf-radext-ipv6-access<
 BR>&gt; draft-nelson-radext-crypto-agility-requirements POTENTIALLY REPLACED BY draft-ietf-radext-crypto-agility-requirements<BR>&gt; draft-tiwari-radext-tunnel-type POTENTIALLY REPLACED BY draft-ietf-radext-tunnel-type<BR>&gt; <BR>&gt; V6OPS Working Group, OPS Area<BR>&gt; draft-hilliard-v6ops-ipv6-discard-prefix POTENTIALLY REPLACED BY draft-ietf-v6ops-ipv6-discard-prefix<BR>&gt; draft-rgaglian-v6ops-v6inixp POTENTIALLY REPLACED BY draft-ietf-v6ops-v6inixp<BR>&gt; draft-vandevelde-v6ops-ra-guard POTENTIALLY REPLACED BY draft-ietf-v6ops-ra-guard<BR>&gt; draft-wbeebee-v6ops-ipv6-cpe-router-bis POTENTIALLY REPLACED BY draft-ietf-v6ops-ipv6-cpe-router-bis<BR>&gt; <BR>&gt; -----------------------------------------------------------------<BR>&gt; RAI Area<BR>&gt; -----------------------------------------------------------------<BR>&gt; ATOCA Working Group, RAI Area<BR>&gt; draft-rosen-atoca-cap POTENTIALLY REPLACED BY draft-ietf-atoca-cap<BR>&gt; <BR>&gt; BLISS Working Group, RA
 I Area<BR>&gt; draft-elwell-bliss-ach-analysis POTENTIALLY REPLACED BY draft-ietf-bliss-ach-analysis<BR>&gt; draft-poetzl-bliss-call-completion POTENTIALLY REPLACED BY draft-ietf-bliss-call-completion<BR>&gt; draft-procter-bliss-call-park-extension POTENTIALLY REPLACED BY draft-ietf-bliss-call-park-extension<BR>&gt; draft-rosenberg-bliss-problem-statement POTENTIALLY REPLACED BY draft-ietf-bliss-problem-statement<BR>&gt; <BR>&gt; CLUE Working Group, RAI Area<BR>&gt; draft-romanow-clue-framework POTENTIALLY REPLACED BY draft-ietf-clue-framework<BR>&gt; draft-romanow-clue-telepresence-requirements POTENTIALLY REPLACED BY draft-ietf-clue-telepresence-requirements<BR>&gt; draft-romanow-clue-telepresence-use-cases POTENTIALLY REPLACED BY draft-ietf-clue-telepresence-use-cases<BR>&gt; <BR>&gt; CODEC Working Group, RAI Area<BR>&gt; draft-valin-codec-guidelines POTENTIALLY REPLACED BY draft-ietf-codec-guidelines<BR>&gt; draft-valin-codec-results POTENTIALLY REPLACED BY draft-ietf-co
 dec-results<BR>&gt; <BR>&gt; DRINKS Working Group, RAI Area<BR>&gt; draft-channabasappa-drinks-usecases-requirements POTENTIALLY REPLACED BY draft-ietf-drinks-usecases-requirements<BR>&gt; <BR>&gt; GEOPRIV Working Group, RAI Area<BR>&gt; draft-barnes-geopriv-policy-uri POTENTIALLY REPLACED BY draft-ietf-geopriv-policy-uri<BR>&gt; draft-mayrhofer-geopriv-geo-uri POTENTIALLY REPLACED BY draft-ietf-geopriv-geo-uri<BR>&gt; draft-winterbottom-geopriv-local-civic POTENTIALLY REPLACED BY draft-ietf-geopriv-local-civic<BR>&gt; <BR>&gt; MMUSIC Working Group, RAI Area<BR>&gt; draft-garcia-mmusic-sdp-miscellaneous-caps POTENTIALLY REPLACED BY draft-ietf-mmusic-sdp-miscellaneous-caps<BR>&gt; draft-greevenbosch-mmusic-parallax-attribute POTENTIALLY REPLACED BY draft-ietf-mmusic-parallax-attribute<BR>&gt; draft-greevenbosch-mmusic-signal-3d-format POTENTIALLY REPLACED BY draft-ietf-mmusic-signal-3d-format<BR>&gt; draft-holmberg-mmusic-sdp-bundle-negotiation POTENTIALLY REPLACED BY draft-i
 etf-mmusic-sdp-bundle-negotiation<BR>&gt; draft-loreto-mmusic-sctp-sdp POTENTIALLY REPLACED BY draft-ietf-mmusic-sctp-sdp<BR>&gt; draft-polk-mmusic-traffic-class-for-sdp POTENTIALLY REPLACED BY draft-ietf-mmusic-traffic-class-for-sdp<BR>&gt; <BR>&gt; P2PSIP Working Group, RAI Area<BR>&gt; draft-bryan-p2psip-reload POTENTIALLY REPLACED BY draft-ietf-p2psip-reload<BR>&gt; draft-zong-p2psip-drr POTENTIALLY REPLACED BY draft-ietf-p2psip-drr<BR>&gt; draft-zong-p2psip-rpr POTENTIALLY REPLACED BY draft-ietf-p2psip-rpr<BR>&gt; <BR>&gt; PAYLOAD Working Group, RAI Area<BR>&gt; draft-westin-payload-vp8 POTENTIALLY REPLACED BY draft-ietf-payload-vp8<BR>&gt; <BR>&gt; RTCWEB Working Group, RAI Area<BR>&gt; draft-uberti-rtcweb-jsep POTENTIALLY REPLACED BY draft-ietf-rtcweb-jsep<BR>&gt; <BR>&gt; SIPCORE Working Group, RAI Area<BR>&gt; draft-holmberg-sipcore-proxy-feature POTENTIALLY REPLACED BY draft-ietf-sipcore-proxy-feature<BR>&gt; <BR>&gt; SOC Working Group, RAI Area<BR>&gt; draft-noel-
 soc-overload-rate-control POTENTIALLY REPLACED BY draft-ietf-soc-overload-rate-control<BR>&gt; draft-shen-soc-load-control-event-package POTENTIALLY REPLACED BY draft-ietf-soc-load-control-event-package<BR>&gt; <BR>&gt; XMPP Working Group, RAI Area<BR>&gt; draft-barnes-xmpp-dna POTENTIALLY REPLACED BY draft-ietf-xmpp-dna<BR>&gt; draft-miller-xmpp-e2e POTENTIALLY REPLACED BY draft-ietf-xmpp-e2e<BR>&gt; draft-saintandre-xmpp-6122bis POTENTIALLY REPLACED BY draft-ietf-xmpp-6122bis<BR>&gt; <BR>&gt; XRBLOCK Working Group, RAI Area<BR>&gt; draft-clark-xrblock-rtcp-xr-qoe POTENTIALLY REPLACED BY draft-ietf-xrblock-rtcp-xr-qoe<BR>&gt; <BR>&gt; -----------------------------------------------------------------<BR>&gt; RTG Area<BR>&gt; -----------------------------------------------------------------<BR>&gt; BFD Working Group, RTG Area<BR>&gt; draft-bhatia-bfd-hmac-sha POTENTIALLY REPLACED BY draft-ietf-bfd-hmac-sha<BR>&gt; <BR>&gt; CCAMP Working Group, RTG Area<BR>&gt; draft-bccg-ccam
 p-otn-g709-info-model POTENTIALLY REPLACED BY draft-ietf-ccamp-otn-g709-info-model<BR>&gt; draft-berger-ccamp-assoc-info POTENTIALLY REPLACED BY draft-ietf-ccamp-assoc-info<BR>&gt; draft-bernstein-ccamp-wson-signaling POTENTIALLY REPLACED BY draft-ietf-ccamp-wson-signaling<BR>&gt; <BR>&gt; FORCES Working Group, RTG Area<BR>&gt; draft-hadi-forces-sctptml POTENTIALLY REPLACED BY draft-ietf-forces-sctptml<BR>&gt; draft-haleplidis-forces-implementation-experience POTENTIALLY REPLACED BY draft-ietf-forces-implementation-experience<BR>&gt; <BR>&gt; IDR Working Group, RTG Area<BR>&gt; draft-decraene-idr-reserved-extended-communities POTENTIALLY REPLACED BY draft-ietf-idr-reserved-extended-communities<BR>&gt; draft-keyupate-idr-bgp-gr-notification POTENTIALLY REPLACED BY draft-ietf-idr-bgp-gr-notification<BR>&gt; draft-keyur-idr-enhanced-gr POTENTIALLY REPLACED BY draft-ietf-idr-enhanced-gr<BR>&gt; draft-raszuk-idr-flow-spec-v6 POTENTIALLY REPLACED BY draft-ietf-idr-flow-spec-v6<BR>
 &gt; draft-wkumari-idr-as0 POTENTIALLY REPLACED BY draft-ietf-idr-as0<BR>&gt; <BR>&gt; ISIS Working Group, RTG Area<BR>&gt; draft-chopps-isis-bfd-tlv POTENTIALLY REPLACED BY draft-ietf-isis-bfd-tlv<BR>&gt; draft-ginsberg-isis-genapp POTENTIALLY REPLACED BY draft-ietf-isis-genapp<BR>&gt; draft-previdi-isis-mi POTENTIALLY REPLACED BY draft-ietf-isis-mi<BR>&gt; draft-shen-isis-oper-enhance POTENTIALLY REPLACED BY draft-ietf-isis-oper-enhance<BR>&gt; <BR>&gt; L2VPN Working Group, RTG Area<BR>&gt; draft-delord-l2vpn-ldp-vpls-broadcast-exten POTENTIALLY REPLACED BY draft-ietf-l2vpn-ldp-vpls-broadcast-exten<BR>&gt; draft-henderickx-l2vpn-vpls-multihoming POTENTIALLY REPLACED BY draft-ietf-l2vpn-vpls-multihoming<BR>&gt; draft-key-l2vpn-etree-frwk POTENTIALLY REPLACED BY draft-ietf-l2vpn-etree-frwk<BR>&gt; draft-kompella-l2vpn-vpls-multihoming POTENTIALLY REPLACED BY draft-ietf-l2vpn-vpls-multihoming<BR>&gt; draft-pdutta-l2vpn-vpls-ldp-mac-opt POTENTIALLY REPLACED BY draft-ietf-l2vpn
 -vpls-ldp-mac-opt<BR>&gt; draft-pkwok-l2vpn-vpls-macflush-ld POTENTIALLY REPLACED BY draft-ietf-l2vpn-vpls-macflush-ld<BR>&gt; draft-sajassi-l2vpn-pbb-evpn POTENTIALLY REPLACED BY draft-ietf-l2vpn-pbb-evpn<BR>&gt; draft-sajassi-l2vpn-vpls-pbb-interop POTENTIALLY REPLACED BY draft-ietf-l2vpn-vpls-pbb-interop<BR>&gt; <BR>&gt; L3VPN Working Group, RTG Area<BR>&gt; draft-rekhter-l3vpn-virtual-hub POTENTIALLY REPLACED BY draft-ietf-l3vpn-virtual-hub<BR>&gt; <BR>&gt; MANET Working Group, RTG Area<BR>&gt; draft-herberg-manet-nhdp-sec POTENTIALLY REPLACED BY draft-ietf-manet-nhdp-sec<BR>&gt; draft-herberg-manet-nhdp-sec-threats POTENTIALLY REPLACED BY draft-ietf-manet-nhdp-sec-threats<BR>&gt; <BR>&gt; MPLS Working Group, RTG Area<BR>&gt; draft-frost-mpls-tp-loss-delay-profile POTENTIALLY REPLACED BY draft-ietf-mpls-tp-loss-delay-profile<BR>&gt; draft-koike-mpls-tp-temporal-hitless-psm POTENTIALLY REPLACED BY draft-ietf-mpls-tp-temporal-hitless-psm<BR>&gt; draft-liu-mpls-tp-ring-prot
 ection POTENTIALLY REPLACED BY draft-ietf-mpls-tp-ring-protection<BR>&gt; draft-raggarwa-mpls-seamless-mcast POTENTIALLY REPLACED BY draft-ietf-mpls-seamless-mcast<BR>&gt; <BR>&gt; OSPF Working Group, RTG Area<BR>&gt; draft-acee-ospf-multi-instance POTENTIALLY REPLACED BY draft-ietf-ospf-multi-instance<BR>&gt; draft-acee-ospf-transport-instance POTENTIALLY REPLACED BY draft-ietf-ospf-transport-instance<BR>&gt; draft-cheng-ospf-ipv4-embedded-ipv6-routing POTENTIALLY REPLACED BY draft-ietf-ospf-ipv4-embedded-ipv6-routing<BR>&gt; draft-nguyen-ospf-lls POTENTIALLY REPLACED BY draft-ietf-ospf-lls<BR>&gt; draft-nsheth-ospf-hybrid-bcast-and-p2mp POTENTIALLY REPLACED BY draft-ietf-ospf-hybrid-bcast-and-p2mp<BR>&gt; draft-ogier-ospf-dbex-opt POTENTIALLY REPLACED BY draft-ietf-ospf-dbex-opt<BR>&gt; draft-retana-ospf-rfc3137bis POTENTIALLY REPLACED BY draft-ietf-ospf-rfc3137bis<BR>&gt; draft-venkata-ospf-dynamic-hostname POTENTIALLY REPLACED BY draft-ietf-ospf-dynamic-hostname<BR>&gt; 
 <BR>&gt; PCE Working Group, RTG Area<BR>&gt; draft-tang-pce-stateful-pce POTENTIALLY REPLACED BY draft-ietf-pce-stateful-pce<BR>&gt; draft-zhao-pce-pcep-inter-domain-p2mp-procedures POTENTIALLY REPLACED BY draft-ietf-pce-pcep-inter-domain-p2mp-procedures<BR>&gt; <BR>&gt; PIM Working Group, RTG Area<BR>&gt; draft-hou-pim-drlb POTENTIALLY REPLACED BY draft-ietf-pim-drlb<BR>&gt; <BR>&gt; PWE3 Working Group, RTG Area<BR>&gt; draft-bryant-pwe3-packet-pw POTENTIALLY REPLACED BY draft-ietf-pwe3-packet-pw<BR>&gt; draft-delregno-pwe3-pw-vccv-impl-survey-results POTENTIALLY REPLACED BY draft-ietf-pwe3-pw-vccv-impl-survey-results<BR>&gt; draft-jin-pwe3-cbit-negotiation POTENTIALLY REPLACED BY draft-ietf-pwe3-cbit-negotiation<BR>&gt; draft-raza-pwe3-pw-typed-wc-fec POTENTIALLY REPLACED BY draft-ietf-pwe3-pw-typed-wc-fec<BR>&gt; <BR>&gt; ROLL Working Group, RTG Area<BR>&gt; draft-dt-roll-p2p-rpl POTENTIALLY REPLACED BY draft-ietf-roll-p2p-rpl<BR>&gt; draft-gnawali-roll-minrank-hysteresis
 -of POTENTIALLY REPLACED BY draft-ietf-roll-minrank-hysteresis-of<BR>&gt; draft-goyal-roll-p2p-measurement POTENTIALLY REPLACED BY draft-ietf-roll-p2p-measurement<BR>&gt; draft-levis-roll-trickle POTENTIALLY REPLACED BY draft-ietf-roll-trickle<BR>&gt; draft-popa-roll-applicability-ami POTENTIALLY REPLACED BY draft-ietf-roll-applicability-ami<BR>&gt; draft-tsao-roll-security-framework POTENTIALLY REPLACED BY draft-ietf-roll-security-framework<BR>&gt; <BR>&gt; RTGWG Working Group, RTG Area<BR>&gt; draft-atlas-rtgwg-mrt-frr-architecture POTENTIALLY REPLACED BY draft-ietf-rtgwg-mrt-frr-architecture<BR>&gt; <BR>&gt; -----------------------------------------------------------------<BR>&gt; SEC Area<BR>&gt; -----------------------------------------------------------------<BR>&gt; ABFAB Working Group, SEC Area<BR>&gt; draft-lear-abfab-arch POTENTIALLY REPLACED BY draft-ietf-abfab-arch<BR>&gt; <BR>&gt; HOKEY Working Group, SEC Area<BR>&gt; draft-wu-hokey-rfc5296bis POTENTIALLY REPLAC
 ED BY draft-ietf-hokey-rfc5296bis<BR>&gt; <BR>&gt; MILE Working Group, SEC Area<BR>&gt; draft-moriarty-mile-grc-exchange POTENTIALLY REPLACED BY draft-ietf-mile-grc-exchange<BR>&gt; <BR>&gt; NEA Working Group, SEC Area<BR>&gt; draft-hanna-nea-pt-eap POTENTIALLY REPLACED BY draft-ietf-nea-pt-eap<BR>&gt; draft-sangster-nea-pt-tls POTENTIALLY REPLACED BY draft-ietf-nea-pt-tls<BR>&gt; <BR>&gt; OAUTH Working Group, SEC Area<BR>&gt; draft-mortimore-oauth-assertions POTENTIALLY REPLACED BY draft-ietf-oauth-assertions<BR>&gt; <BR>&gt; PKIX Working Group, SEC Area<BR>&gt; draft-cooper-pkix-rfc2560bis POTENTIALLY REPLACED BY draft-ietf-pkix-rfc2560bis<BR>&gt; draft-cooper-pkix-rfc5280-clarifications POTENTIALLY REPLACED BY draft-ietf-pkix-rfc5280-clarifications<BR>&gt; draft-santesson-pkix-certimage POTENTIALLY REPLACED BY draft-ietf-pkix-certimage<BR>&gt; <BR>&gt; TLS Working Group, SEC Area<BR>&gt; draft-kanno-tls-camellia POTENTIALLY REPLACED BY draft-ietf-tls-camellia<BR>&gt; draf
 t-rescorla-tls-suiteb POTENTIALLY REPLACED BY draft-ietf-tls-suiteb<BR>&gt; draft-seggelmann-tls-dtls-heartbeat POTENTIALLY REPLACED BY draft-ietf-tls-dtls-heartbeat<BR>&gt; <BR>&gt; -----------------------------------------------------------------<BR>&gt; TSV Area<BR>&gt; -----------------------------------------------------------------<BR>&gt; ALTO Working Group, TSV Area<BR>&gt; draft-song-alto-server-discovery POTENTIALLY REPLACED BY draft-ietf-alto-server-discovery<BR>&gt; draft-stiemerling-alto-deployments POTENTIALLY REPLACED BY draft-ietf-alto-deployments<BR>&gt; <BR>&gt; BEHAVE Working Group, TSV Area<BR>&gt; draft-liu-behave-ftp64 POTENTIALLY REPLACED BY draft-ietf-behave-ftp64<BR>&gt; draft-penno-behave-64-analysis POTENTIALLY REPLACED BY draft-ietf-behave-64-analysis<BR>&gt; <BR>&gt; CDNI Working Group, TSV Area<BR>&gt; draft-watson-cdni-use-cases POTENTIALLY REPLACED BY draft-ietf-cdni-use-cases<BR>&gt; <BR>&gt; CONEX Working Group, TSV Area<BR>&gt; draft-krishn
 an-conex-destopt POTENTIALLY REPLACED BY draft-ietf-conex-destopt<BR>&gt; draft-kuehlewind-conex-tcp-modifications POTENTIALLY REPLACED BY draft-ietf-conex-tcp-modifications<BR>&gt; draft-mathis-conex-abstract-mech POTENTIALLY REPLACED BY draft-ietf-conex-abstract-mech<BR>&gt; draft-moncaster-conex-concepts-uses POTENTIALLY REPLACED BY draft-ietf-conex-concepts-uses<BR>&gt; <BR>&gt; DECADE Working Group, TSV Area<BR>&gt; draft-alimi-decade-arch POTENTIALLY REPLACED BY draft-ietf-decade-arch<BR>&gt; draft-chen-decade-integration-example POTENTIALLY REPLACED BY draft-ietf-decade-integration-example<BR>&gt; draft-huang-decade-integration-example POTENTIALLY REPLACED BY draft-ietf-decade-integration-example<BR>&gt; <BR>&gt; FECFRAME Working Group, TSV Area<BR>&gt; draft-roca-fecframe-ldpc POTENTIALLY REPLACED BY draft-ietf-fecframe-ldpc<BR>&gt; draft-roca-fecframe-simple-rs POTENTIALLY REPLACED BY draft-ietf-fecframe-simple-rs<BR>&gt; <BR>&gt; IPPM Working Group, TSV Area<BR>&gt
 ; draft-baillargeon-ippm-twamp-value-added-octets POTENTIALLY REPLACED BY draft-ietf-ippm-twamp-value-added-octets<BR>&gt; draft-geib-ippm-metrictest POTENTIALLY REPLACED BY draft-ietf-ippm-metrictest<BR>&gt; draft-morton-ippm-rt-loss POTENTIALLY REPLACED BY draft-ietf-ippm-rt-loss<BR>&gt; draft-morton-ippm-testplan-rfc2679 POTENTIALLY REPLACED BY draft-ietf-ippm-testplan-rfc2679<BR>&gt; <BR>&gt; NFSV4 Working Group, TSV Area<BR>&gt; draft-alexrn-nfsv4-ipv6 POTENTIALLY REPLACED BY draft-ietf-nfsv4-ipv6<BR>&gt; draft-dnoveck-nfsv4-migration-issues POTENTIALLY REPLACED BY draft-ietf-nfsv4-migration-issues<BR>&gt; draft-eisler-nfsv4-minorversion-2-requirements POTENTIALLY REPLACED BY draft-ietf-nfsv4-minorversion-2-requirements<BR>&gt; draft-faibish-nfsv4-pnfs-access-permissions-check POTENTIALLY REPLACED BY draft-ietf-nfsv4-pnfs-access-permissions-check<BR>&gt; draft-faibish-nfsv4-pnfs-block-disk-protection POTENTIALLY REPLACED BY draft-ietf-nfsv4-pnfs-block-disk-protection<BR
 >&gt; draft-haynes-nfsv4-minorversion2 POTENTIALLY REPLACED BY draft-ietf-nfsv4-minorversion2<BR>&gt; draft-haynes-nfsv4-minorversion2-dot-x POTENTIALLY REPLACED BY draft-ietf-nfsv4-minorversion2-dot-x<BR>&gt; draft-quigley-nfsv4-labreqs POTENTIALLY REPLACED BY draft-ietf-nfsv4-labreqs<BR>&gt; <BR>&gt; PCN Working Group, TSV Area<BR>&gt; draft-karagiannis-pcn-signaling-requirements POTENTIALLY REPLACED BY draft-ietf-pcn-signaling-requirements<BR>&gt; <BR>&gt; PPSP Working Group, TSV Area<BR>&gt; draft-gu-ppsp-peer-protocol POTENTIALLY REPLACED BY draft-ietf-ppsp-peer-protocol<BR>&gt; draft-gu-ppsp-survey POTENTIALLY REPLACED BY draft-ietf-ppsp-survey<BR>&gt; <BR>&gt; TCPM Working Group, TSV Area<BR>&gt; draft-blanton-tcpm-3517bis POTENTIALLY REPLACED BY draft-ietf-tcpm-3517bis<BR>&gt; draft-cheng-tcpm-fastopen POTENTIALLY REPLACED BY draft-ietf-tcpm-fastopen<BR>&gt; draft-gont-tcpm-rfc1948bis POTENTIALLY REPLACED BY draft-ietf-tcpm-rfc1948bis<BR>&gt; draft-henderson-tcpm-rfc
 3782-bis POTENTIALLY REPLACED BY draft-ietf-tcpm-rfc3782-bis<BR>&gt; draft-hkchu-tcpm-initcwnd POTENTIALLY REPLACED BY draft-ietf-tcpm-initcwnd<BR>&gt; draft-mathis-tcpm-proportional-rate-reduction POTENTIALLY REPLACED BY draft-ietf-tcpm-proportional-rate-reduction<BR>&gt; draft-touch-tcpm-experimental-options POTENTIALLY REPLACED BY draft-ietf-tcpm-experimental-options<BR>&gt; <BR>&gt; TSVWG Working Group, TSV Area<BR>&gt; draft-gont-tsvwg-source-quench POTENTIALLY REPLACED BY draft-ietf-tsvwg-source-quench<BR>&gt; draft-polk-tsvwg-intserv-multiple-tspec POTENTIALLY REPLACED BY draft-ietf-tsvwg-intserv-multiple-tspec<BR>&gt; <BR>&gt; -----------------------------------------------------------------<BR>&gt; Potential Inconsistencies<BR>&gt; -----------------------------------------------------------------<BR>&gt; draft-ietf-6lowpan-nd may replace one or more of 2 individual IDs - check this<BR>&gt; draft-ietf-armd-problem-statement may replace one or more of 2 individual IDs
  - check this<BR>&gt; draft-ietf-avt-rtp-gsm-hr may replace one or more of 3 individual IDs - check this<BR>&gt; draft-ietf-avt-rtp-svc may replace one or more of 2 individual IDs - check this<BR>&gt; draft-ietf-bmwg-ipflow-meth may replace one or more of 2 individual IDs - check this<BR>&gt; draft-ietf-cdni-use-cases may replace one or more of 2 individual IDs - check this<BR>&gt; draft-ietf-decade-integration-example may replace one or more of 2 individual IDs - check this<BR>&gt; draft-ietf-decade-survey may replace one or more of 2 individual IDs - check this<BR>&gt; draft-ietf-dhc-dhcpv4-bulk-leasequery may replace one or more of 2 individual IDs - check this<BR>&gt; draft-ietf-forces-tmlsp may replace one or more of 2 individual IDs - check this<BR>&gt; draft-ietf-ipfix-biflow may replace one or more of 2 individual IDs - check this<BR>&gt; draft-ietf-l2tpext-tdm may replace one or more of 2 individual IDs - check this<BR>&gt; draft-ietf-l2vpn-vpls-multihoming may repl
 ace one or more of 2 individual IDs - check this<BR>&gt; draft-ietf-mpls-tp-fault may replace one or more of 2 individual IDs - check this<BR>&gt; draft-ietf-mpls-tp-ring-protection may replace one or more of 2 individual IDs - check this<BR>&gt; draft-ietf-netconf-monitoring may replace one or more of 2 individual IDs - check this<BR>&gt; draft-ietf-netlmm-lma-discovery may replace one or more of 2 individual IDs - check this<BR>&gt; draft-ietf-netlmm-mip-interactions may replace one or more of 2 individual IDs - check this<BR>&gt; draft-ietf-pce-stateful-pce may replace one or more of 2 individual IDs - check this<BR>&gt; draft-ietf-sip-saml may replace one or more of 2 individual IDs - check this<BR>&gt; draft-ietf-sipping-service-identification may replace one or more of 2 individual IDs - check this<BR>&gt; draft-ietf-softwire-dslite-deployment may replace one or more of 2 individual IDs - check this<BR>&gt; draft-ietf-trill-rbridge-arch may replace one or more of 2 ind
 ividual IDs - check this<BR>&gt; <BR></DIV> 		 	   		  </div></body>
</html>
--_f81acde2-b07d-42d6-8e4b-7f437544ad99_--

From lars@netapp.com  Wed Apr 18 01:57:12 2012
Return-Path: <lars@netapp.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C002C21F855F for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 01:57:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.767
X-Spam-Level: 
X-Spam-Status: No, score=-10.767 tagged_above=-999 required=5 tests=[AWL=-0.168, 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 mP+7LKU+BDIA for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 01:57:12 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by ietfa.amsl.com (Postfix) with ESMTP id 3DCFB21F8550 for <wgchairs@ietf.org>; Wed, 18 Apr 2012 01:57:12 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.75,441,1330934400";  d="p7s'?scan'208";a="641717586"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx2-out.netapp.com with ESMTP; 18 Apr 2012 01:57:12 -0700
Received: from vmwexceht05-prd.hq.netapp.com (vmwexceht05-prd.hq.netapp.com [10.106.77.35]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id q3I8vB29000902; Wed, 18 Apr 2012 01:57:12 -0700 (PDT)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.117]) by vmwexceht05-prd.hq.netapp.com ([10.106.77.35]) with mapi id 14.02.0247.003; Wed, 18 Apr 2012 01:57:00 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: Hui Deng <denghui02@hotmail.com>
Subject: Re: latest missing replaced-by information
Thread-Topic: latest missing replaced-by information
Thread-Index: AQHNHUArfc1edZEOVEayFUwcFf7CfZagvH4AgAAA1YA=
Date: Wed, 18 Apr 2012 08:57:10 +0000
Message-ID: <A9940A1E-DC57-4593-8F6A-F85EA976C822@netapp.com>
References: <E9354164-6546-42A9-BAC4-BE6660855AE9@netapp.com> <COL118-W55777ADB1F1049DEEEB2A9B13C0@phx.gbl>
In-Reply-To: <COL118-W55777ADB1F1049DEEEB2A9B13C0@phx.gbl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: multipart/signed; boundary="Apple-Mail=_A376EC22-6C67-466E-BDE4-9BA971C1619B"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Cc: "<wgchairs@ietf.org>" <wgchairs@ietf.org>, "<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: Wed, 18 Apr 2012 08:57:12 -0000

--Apple-Mail=_A376EC22-6C67-466E-BDE4-9BA971C1619B
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=GB2312

On Apr 18, 2012, at 10:54, Hui Deng wrote:
> excuse me for naive question, how to send a ticket to the secretariat ?

Email ietf-action@ietf.org.

(I should add this to the email boilerplate.)

Lars
--Apple-Mail=_A376EC22-6C67-466E-BDE4-9BA971C1619B
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMQDCCBUow
ggQyoAMCAQICEFcfSRTG0jNknqb9LV9GuFkwDQYJKoZIhvcNAQEFBQAwgd0xCzAJBgNVBAYTAlVT
MRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEg
KGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24g
Q2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMzAeFw0xMTEyMTAwMDAwMDBaFw0x
MjEyMDkyMzU5NTlaMIIBDTEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9S
UEEgSW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMpOTgxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZh
bGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJRCBDbGFzcyAxIC0gTmV0c2NhcGUgRnVsbCBTZXJ2
aWNlMRQwEgYDVQQDFAtMYXJzIEVnZ2VydDEeMBwGCSqGSIb3DQEJARYPbGFyc0BuZXRhcHAuY29t
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAokrhJTcXt6J/VEpZOicLoguBlYTjXP9v
Ze4HuuhXnURUS8YouAfgaqA0zYbt5yd6fh4PBMdAaEWr5yJyHuFykXlrCumjUWSpLuqTS2A+pt4q
cZaAQk9iLDN/UVd3SpkUuvWbxXlqzG7/BSqa3VNObBzCmyh+V7aXxri+30CT//DSsNRC4VFy6sn6
dMgSaFenXLwe/FBwY0qTMfICT1PrrX6Sw1S8OfH9rykLlZXbmfkFExxQngp1DJH9xMHeODHGbCv/
ty5gdxMOrLe+vENxFEcy1YQWBZd1kNL4UObugF8A/jE/s+Oa3H1VFH8ghqZTdqGDysVxmtKHuNFx
6jIBSQIDAQABo4HSMIHPMAkGA1UdEwQCMAAwRAYDVR0gBD0wOzA5BgtghkgBhvhFAQcXATAqMCgG
CCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhMAsGA1UdDwQEAwIFoDAdBgNV
HSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwUAYDVR0fBEkwRzBFoEOgQYY/aHR0cDovL2luZGMx
ZGlnaXRhbGlkLWczLWNybC52ZXJpc2lnbi5jb20vSW5kQzFEaWdpdGFsSUQtRzMuY3JsMA0GCSqG
SIb3DQEBBQUAA4IBAQBA7q6tR92qpd7xo7VBsrOfGCWzoxIVfTc7t0RhB/Oz/+c3lnhYnNScIuKN
JmyZvznmVxqB9BJ72+NkvmdB/hnILSBTRawL2tyLo9PkBtN0nRt4gS6wjpWnD8G83hlJLE7r25jk
7HkRev61dTIXsANFpJKF02C4XSoDfEzNV6MpuEvHvcgHCqMrlwWwfKc7+NoDnE8PBuRzwSXvlD5L
mswCY2iiOsd7ImNO4OzTCxETvKTDu92+FTIbRJJpYjVNv1UF7e3w9Kq65BkZJErUH19beUeQl0Wh
2BJQE6/15rQyCnP0iJ/Nmx2/kI6M0PWunEsI6FMs0MbosreaWGHlQmomMIIG7jCCBdagAwIBAgIQ
cRVmBUrkkSFN6bxE+azT3DANBgkqhkiG9w0BAQUFADCByjELMAkGA1UEBhMCVVMxFzAVBgNVBAoT
DlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTowOAYDVQQL
EzEoYykgMTk5OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MUUwQwYD
VQQDEzxWZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9y
aXR5IC0gRzMwHhcNMDkwNTAxMDAwMDAwWhcNMTkwNDMwMjM1OTU5WjCB3TELMAkGA1UEBhMCVVMx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3Jr
MTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAo
YykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBD
bGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBDQSAtIEczMIIBIjANBgkqhkiG9w0BAQEFAAOC
AQ8AMIIBCgKCAQEA7cRH3yooHXwGa7vXITLJbBOP6bGNQU4099oL42r6ZYggCxET6ZvgSU6Lb9UB
0F8NR5GKWkx0Pj/GkQm7TDSejW6hglFi92l2WJYHr54UGAdPWr2f0jGyVBlzRmoZQhHsEnMhjfXc
MM3l2VYKMcU2bSkUl70t2olHGYjYSwQ967Y8Zx50ABMN0Ibak2f4MwOuGjxraXj2wCyO4YM/d/mZ
//6fUlrCtIcK2GypR8FUKWVDPkrAlh/Brfd3r2yxBF6+wbaULZeQLSfSux7pg2qE9sSyriMGZSal
J1grByK0b6ZiSBp38tVQJ5op05b7KPW6JHZi44xZ6/tu1ULEvkHH9QIDAQABo4ICuTCCArUwNAYI
KwYBBQUHAQEEKDAmMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC52ZXJpc2lnbi5jb20wEgYDVR0T
AQH/BAgwBgEB/wIBADBwBgNVHSAEaTBnMGUGC2CGSAGG+EUBBxcBMFYwKAYIKwYBBQUHAgEWHGh0
dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9jcHMwKgYIKwYBBQUHAgIwHhocaHR0cHM6Ly93d3cudmVy
aXNpZ24uY29tL3JwYTA0BgNVHR8ELTArMCmgJ6AlhiNodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9w
Y2ExLWczLmNybDAOBgNVHQ8BAf8EBAMCAQYwbgYIKwYBBQUHAQwEYjBgoV6gXDBaMFgwVhYJaW1h
Z2UvZ2lmMCEwHzAHBgUrDgMCGgQUS2u5KJYGDLvQUjibKaxLB4shBRgwJhYkaHR0cDovL2xvZ28u
dmVyaXNpZ24uY29tL3ZzbG9nbzEuZ2lmMC4GA1UdEQQnMCWkIzAhMR8wHQYDVQQDExZQcml2YXRl
TGFiZWw0LTIwNDgtMTE4MB0GA1UdDgQWBBR5R2EIQf04BKJL57XM9UP2SSsR+DCB8QYDVR0jBIHp
MIHmoYHQpIHNMIHKMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNV
BAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4BgNVBAsTMShjKSAxOTk5IFZlcmlTaWduLCBJ
bmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxRTBDBgNVBAMTPFZlcmlTaWduIENsYXNzIDEg
UHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgLSBHM4IRAItbdVaEVIULAM+v
OEjOsaQwDQYJKoZIhvcNAQEFBQADggEBADlNz0GZgbWpBbVSOOk5hIls5DSoWufYbAlMJBq6WaSH
O3Mh8ZOBz79oY1pn/jWFK6HDXaNKwjoZ3TDWzE3v8dKBl8pUWkO/N4t6jhmND0OojPKvYLMVirOV
nDzgnrMnmKQ1chfl/Cpdh9OKDcLRRSr4wPSsKpM61a4ScAjr+zvid+zoK2Q1ds262uDRyxTWcVib
vtU+fbbZ6CTFJGZMXZEfdrMXPn8NxiGJL7M3uKH/XLJtSd5lUkL7DojS7Uodv0vj+Mxy+kgOZY5J
yNb4mZg7t5Q+MXEGh/psWVMu198r7V9jAKwV7QO4VRaMxmgD5yKocwuxvKDaUljdCg5/wYIxggSL
MIIEhwIBATCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0
cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFs
aWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBD
QSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMAkGBSsOAwIaBQCgggJtMBgGCSqGSIb3DQEJAzELBgkq
hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEyMDQxODA4NTcxMVowIwYJKoZIhvcNAQkEMRYEFIxR
Y4i9T+lYrbondn81v2Ppl+6HMIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQGEwJVUzEX
MBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
OzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhIChj
KTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlTaWduIENs
YXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEFcfSRTG0jNknqb9LV9GuFkwggEF
BgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJ
bmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1
c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29u
YSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vi
c2NyaWJlciBDQSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMA0GCSqGSIb3DQEBAQUABIIBAFvSEkvY
DWQavtwzreN4Xmzz2dj4m6AoBcyWE93LeqwyMkLwcnGmLqID9Pg/2Va92C0xmj8uQOQ5/ZJ/aeiX
nuxf57/y28uZBuePoNhAR9tKx9af4D8VgG7lZQTDXnhWzy6XrEP6hwAuAdCpb/iGKYX927dJkNE/
DpcFAhWjgUwleixZ7/5p8+Q2D2e0fIy/iQ8US9CENnFRaYjQUZTEwjHLlG8lUyItxABO0MlEZx2F
OtV4+E4rRbSlRuMxn3ITPZH+QOdKqAeQcPejTp2W1QaGuV0I51IkxSylyEbfAq4tcbH9+6W8Afpp
78CujtXVVQxpg4pW2zD+OkBOM62dIhMAAAAAAAA=

--Apple-Mail=_A376EC22-6C67-466E-BDE4-9BA971C1619B--

From duerst@it.aoyama.ac.jp  Wed Apr 18 02:24:41 2012
Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43F6D21F85B7 for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 02:24:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.265
X-Spam-Level: 
X-Spam-Status: No, score=-99.265 tagged_above=-999 required=5 tests=[AWL=0.525, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265,  MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qh240PA2wh2Q for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 02:24:37 -0700 (PDT)
Received: from scintmta01.scbb.aoyama.ac.jp (scintmta01.scbb.aoyama.ac.jp [133.2.253.33]) by ietfa.amsl.com (Postfix) with ESMTP id 3CE1921F85B8 for <wgchairs@ietf.org>; Wed, 18 Apr 2012 02:24:36 -0700 (PDT)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta01.scbb.aoyama.ac.jp (secret/secret) with SMTP id q3I9OPeg021779 for <wgchairs@ietf.org>; Wed, 18 Apr 2012 18:24:25 +0900
Received: from (unknown [133.2.206.133]) by scmse02.scbb.aoyama.ac.jp with smtp id 572c_cc19_4a070636_8938_11e1_873f_001d096c5782; Wed, 18 Apr 2012 18:24:24 +0900
Received: from [IPv6:::1] ([133.2.210.1]:44864) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S15B93C0> for <wgchairs@ietf.org> from <duerst@it.aoyama.ac.jp>; Wed, 18 Apr 2012 18:24:29 +0900
Message-ID: <4F8E8846.60209@it.aoyama.ac.jp>
Date: Wed, 18 Apr 2012 18:24:22 +0900
From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: "Eggert, Lars" <lars@netapp.com>
Subject: Re: latest missing replaced-by information
References: <E9354164-6546-42A9-BAC4-BE6660855AE9@netapp.com>
In-Reply-To: <E9354164-6546-42A9-BAC4-BE6660855AE9@netapp.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>, Internet Research Steering Group <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: Wed, 18 Apr 2012 09:24:41 -0000

Hello Lars,

On 2012/04/18 17:49, Eggert, Lars wrote:
> Hi,
>
> here's yet another installment in the series of reports on potentially missing "replaced-by" relationships in the IETF datatracker.

> (Note that the IPR disclosure search tool uses these replaced-by relationships, so keeping them up-to-date is actually useful and not just WG hygiene.)
>
> Lars

> -----------------------------------------------------------------
> APP Area
> -----------------------------------------------------------------

> EAI Working Group, APP Area
>     draft-duerst-eai-mailto POTENTIALLY REPLACED BY draft-ietf-eai-mailto

No. Your tool got it right that there's a relationship, but 
draft-ietf-eai-mailto was an attempt at doing some work in an earlier 
incarnation of the EAI WG (-00: February 18, 2008; -01: March 9, 2009).

On the other hand, draft-duerst-eai-mailto is newer (-00: March 7, 2011; 
-01: September 7, 2011; -02: March 12, 2012; -03: March 26, 2012). So 
your tool could eliminate the above proposal by looking at the 
publication dates.

draft-duerst-eai-mailto is an 'individual' draft currently waiting for 
the WG to complete some higher priority work first (work on mailto: is 
in the charter of the EAI WG). It is possible that in the future, 
draft-duerst-eai-mailto will be replaced by (-02 of) 
draft-ietf-eai-mailto, but the choice of name for that future WG draft 
would be up to the chairs. (Your advice on whether that's a good idea 
would be appreciated; see also next paragraph.)

I would have to dig up the details, but I think it currently would be 
more appropriate to say draft-ietf-eai-mailto (POTENTIALLY) REPLACED BY 
draft-duerst-eai-mailto. Is such a thing possible? Is that 
necessary/helpful?

>     draft-yao-eai-rfc5336bis POTENTIALLY REPLACED BY draft-ietf-eai-rfc5336bis

Yes indeed. Tools 
(http://tools.ietf.org/html/draft-ietf-eai-rfc5336bis-16) has this 
right, so I wonder why it's "POTENTIALLY" here.

Regards,   Martin.

From loa@pi.nu  Wed Apr 18 05:58:40 2012
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 2C93721F8592 for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 05:58:40 -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 fmi1uUJa4E-q for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 05:58:39 -0700 (PDT)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by ietfa.amsl.com (Postfix) with ESMTP id 9445421F84D1 for <wgchairs@ietf.org>; Wed, 18 Apr 2012 05:58:39 -0700 (PDT)
Received: from [192.168.1.64] (81-236-221-144-no93.tbcn.telia.com [81.236.221.144]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by mail.pi.nu (Postfix) with ESMTPSA id 5900C2A8002; Wed, 18 Apr 2012 14:58:38 +0200 (CEST)
Message-ID: <4F8EBA7E.9050603@pi.nu>
Date: Wed, 18 Apr 2012 14:58:38 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: wgchairs@ietf.org, Henrik Levkowetz <henrik@levkowetz.com>
Subject: Warning on document dates ...
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: Wed, 18 Apr 2012 12:58:40 -0000

Folks,

when I run the nit-tool I always get a warning like this:

   -- The document date (April 11, 2012) is 7 days in the past.  Is this
      intentional?

I tried to figure why this warning is there, but can't come up with a
good explanation. If the warning were for "7days in the future" I could
understand. If it is off by a year, one will get specific warning on
that,

Is the "xx days in the past" useful for anything?

/Loa

-- 


Loa Andersson                         email: loa.andersson@ericsson.com
Sr Strategy and Standards Manager            loa@pi.nu
Ericsson Inc                          phone: +46 10 717 52 13
                                              +46 767 72 92 13

From warren@kumari.net  Wed Apr 18 06:01:31 2012
Return-Path: <warren@kumari.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AD6921F859B for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 06:01:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mQIlggs7Us1T for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 06:01:30 -0700 (PDT)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by ietfa.amsl.com (Postfix) with ESMTP id 842DF21F8594 for <wgchairs@ietf.org>; Wed, 18 Apr 2012 06:01:30 -0700 (PDT)
Received: from dhcp-27-180.ripemtg.ripe.net (dhcp-27-180.ripemtg.ripe.net [193.0.27.180]) by vimes.kumari.net (Postfix) with ESMTPSA id 7F4771B40372; Wed, 18 Apr 2012 09:01:29 -0400 (EDT)
Subject: Re: Warning on document dates ...
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=windows-1252
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <4F8EBA7E.9050603@pi.nu>
Date: Wed, 18 Apr 2012 15:01:27 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <5CF9F389-64D4-4C32-9867-ABAE4F3FE51F@kumari.net>
References: <4F8EBA7E.9050603@pi.nu>
To: Loa Andersson <loa@pi.nu>
X-Mailer: Apple Mail (2.1257)
Cc: 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, 18 Apr 2012 13:01:31 -0000

On Apr 18, 2012, at 2:58 PM, Loa Andersson wrote:

> Folks,
>=20
> when I run the nit-tool I always get a warning like this:
>=20
>  -- The document date (April 11, 2012) is 7 days in the past.  Is this
>     intentional?
>=20
> I tried to figure why this warning is there, but can't come up with a
> good explanation.
> If the warning were for "7days in the future" I could
> understand. If it is off by a year, one will get specific warning on
> that,
>=20
> Is the "xx days in the past" useful for anything?

Sure - it's useful for me=85

I've often accidentally tried to upload a document that I've just edited =
and forgotten to bump the date field (or, sometimes edited a document =
and then tried to upload the old version!).

I think that this is useful for dummies like me...


W
>=20
> /Loa
>=20
> --=20
>=20
>=20
> Loa Andersson                         email: =
loa.andersson@ericsson.com
> Sr Strategy and Standards Manager            loa@pi.nu
> Ericsson Inc                          phone: +46 10 717 52 13
>                                             +46 767 72 92 13
>=20


From loa@pi.nu  Wed Apr 18 06:12:40 2012
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 BB2BA21F8569 for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 06:12:40 -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 wEuvqwpiuxdq for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 06:12:40 -0700 (PDT)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by ietfa.amsl.com (Postfix) with ESMTP id 2D3C421F8568 for <wgchairs@ietf.org>; Wed, 18 Apr 2012 06:12:39 -0700 (PDT)
Received: from [192.168.1.64] (81-236-221-144-no93.tbcn.telia.com [81.236.221.144]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by mail.pi.nu (Postfix) with ESMTPSA id C2E682A8002; Wed, 18 Apr 2012 15:12:38 +0200 (CEST)
Message-ID: <4F8EBDC6.3060404@pi.nu>
Date: Wed, 18 Apr 2012 15:12:38 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Warren Kumari <warren@kumari.net>
Subject: Re: Warning on document dates ...
References: <4F8EBA7E.9050603@pi.nu> <5CF9F389-64D4-4C32-9867-ABAE4F3FE51F@kumari.net>
In-Reply-To: <5CF9F389-64D4-4C32-9867-ABAE4F3FE51F@kumari.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Cc: 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, 18 Apr 2012 13:12:40 -0000

Warren,

maybe - but that is when u are about to upload a document, but
you get the same warning if you look at a document that is in the
repository and has been there for 2 months (60 days in the past)
even if the date was correctly set when the doc was uploaded.

/Loa

On 2012-04-18 15:01, Warren Kumari wrote:
>
> On Apr 18, 2012, at 2:58 PM, Loa Andersson wrote:
>
>> Folks,
>>
>> when I run the nit-tool I always get a warning like this:
>>
>>   -- The document date (April 11, 2012) is 7 days in the past.  Is this
>>      intentional?
>>
>> I tried to figure why this warning is there, but can't come up with a
>> good explanation.
>> If the warning were for "7days in the future" I could
>> understand. If it is off by a year, one will get specific warning on
>> that,
>>
>> Is the "xx days in the past" useful for anything?
>
> Sure - it's useful for me…
>
> I've often accidentally tried to upload a document that I've just edited and forgotten to bump the date field (or, sometimes edited a document and then tried to upload the old version!).
>
> I think that this is useful for dummies like me...
>
>
> W
>>
>> /Loa
>>
>> --
>>
>>
>> Loa Andersson                         email: loa.andersson@ericsson.com
>> Sr Strategy and Standards Manager            loa@pi.nu
>> Ericsson Inc                          phone: +46 10 717 52 13
>>                                              +46 767 72 92 13
>>
>

-- 


Loa Andersson                         email: loa.andersson@ericsson.com
Sr Strategy and Standards Manager            loa@pi.nu
Ericsson Inc                          phone: +46 10 717 52 13
                                              +46 767 72 92 13

From warren@kumari.net  Wed Apr 18 06:15:33 2012
Return-Path: <warren@kumari.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76E0F21F85A8 for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 06:15:33 -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 UVZEYEccdACW for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 06:15:33 -0700 (PDT)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by ietfa.amsl.com (Postfix) with ESMTP id E286C21F85A5 for <wgchairs@ietf.org>; Wed, 18 Apr 2012 06:15:32 -0700 (PDT)
Received: from dhcp-27-180.ripemtg.ripe.net (dhcp-27-180.ripemtg.ripe.net [193.0.27.180]) by vimes.kumari.net (Postfix) with ESMTPSA id 05F7A1B4030F; Wed, 18 Apr 2012 09:15:31 -0400 (EDT)
Subject: Re: Warning on document dates ...
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=windows-1252
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <4F8EBDC6.3060404@pi.nu>
Date: Wed, 18 Apr 2012 15:15:29 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <71D3F45D-385B-4B74-B927-30F6D64B8995@kumari.net>
References: <4F8EBA7E.9050603@pi.nu> <5CF9F389-64D4-4C32-9867-ABAE4F3FE51F@kumari.net> <4F8EBDC6.3060404@pi.nu>
To: Loa Andersson <loa@pi.nu>
X-Mailer: Apple Mail (2.1257)
Cc: 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, 18 Apr 2012 13:15:33 -0000

On Apr 18, 2012, at 3:12 PM, Loa Andersson wrote:

> Warren,
>=20
> maybe - but that is when u are about to upload a document, but
> you get the same warning if you look at a document that is in the
> repository and has been there for 2 months (60 days in the past)
> even if the date was correctly set when the doc was uploaded.

Oh. Well, that's just stupid then :-)

Guessing that's just a special case that hasn't been handled, cannot see =
any useful use -- other than maybe used by the expiration checker ;-)

W



>=20
> /Loa
>=20
> On 2012-04-18 15:01, Warren Kumari wrote:
>>=20
>> On Apr 18, 2012, at 2:58 PM, Loa Andersson wrote:
>>=20
>>> Folks,
>>>=20
>>> when I run the nit-tool I always get a warning like this:
>>>=20
>>>  -- The document date (April 11, 2012) is 7 days in the past.  Is =
this
>>>     intentional?
>>>=20
>>> I tried to figure why this warning is there, but can't come up with =
a
>>> good explanation.
>>> If the warning were for "7days in the future" I could
>>> understand. If it is off by a year, one will get specific warning on
>>> that,
>>>=20
>>> Is the "xx days in the past" useful for anything?
>>=20
>> Sure - it's useful for me=85
>>=20
>> I've often accidentally tried to upload a document that I've just =
edited and forgotten to bump the date field (or, sometimes edited a =
document and then tried to upload the old version!).
>>=20
>> I think that this is useful for dummies like me...
>>=20
>>=20
>> W
>>>=20
>>> /Loa
>>>=20
>>> --
>>>=20
>>>=20
>>> Loa Andersson                         email: =
loa.andersson@ericsson.com
>>> Sr Strategy and Standards Manager            loa@pi.nu
>>> Ericsson Inc                          phone: +46 10 717 52 13
>>>                                             +46 767 72 92 13
>>>=20
>>=20
>=20
> --=20
>=20
>=20
> Loa Andersson                         email: =
loa.andersson@ericsson.com
> Sr Strategy and Standards Manager            loa@pi.nu
> Ericsson Inc                          phone: +46 10 717 52 13
>                                             +46 767 72 92 13
>=20


From dworley@avaya.com  Wed Apr 18 06:26:37 2012
Return-Path: <dworley@avaya.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D93B21F84FA for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 06:26:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.731
X-Spam-Level: 
X-Spam-Status: No, score=-102.731 tagged_above=-999 required=5 tests=[AWL=-0.132, 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 So69uNol2Hbj for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 06:26:36 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id AF39121F846F for <wgchairs@ietf.org>; Wed, 18 Apr 2012 06:26:36 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAIzAjk+HCzI1/2dsb2JhbABEsT2BB4IJAQEBAQIBEig/BQsCAQgNCCEQMiUBAQQBDQUIGodoBZ0FnTaQBWMEnASKJYMD
X-IronPort-AV: E=Sophos;i="4.75,442,1330923600";  d="scan'208";a="4953736"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 18 Apr 2012 09:26:34 -0400
Received: from unknown (HELO DC-US1HCEX4.global.avaya.com) ([135.11.52.35]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 18 Apr 2012 09:10:03 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.202]) by DC-US1HCEX4.global.avaya.com ([135.11.52.35]) with mapi; Wed, 18 Apr 2012 09:26:35 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Loa Andersson <loa@pi.nu>, Warren Kumari <warren@kumari.net>
Date: Wed, 18 Apr 2012 09:25:12 -0400
Subject: RE: Warning on document dates ...
Thread-Topic: Warning on document dates ...
Thread-Index: Ac0dZQIHmWBxhBgPTZ24t+wFxjMtEAAAa1uk
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22726A0A4C@DC-US1MBEX4.global.avaya.com>
References: <4F8EBA7E.9050603@pi.nu> <5CF9F389-64D4-4C32-9867-ABAE4F3FE51F@kumari.net>, <4F8EBDC6.3060404@pi.nu>
In-Reply-To: <4F8EBDC6.3060404@pi.nu>
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: "wgchairs@ietf.org" <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, 18 Apr 2012 13:26:37 -0000

> From: Loa Andersson [loa@pi.nu]
>=20
> but you get the same warning if you look at a document that is in the
> repository and has been there for 2 months (60 days in the past) even
> if the date was correctly set when the doc was uploaded.

I expect that is so that there doesn't have to be a way to operate the
checker in two different modes, one when a document is being uploaded,
and one for other times.

Dale

From martin.vigoureux@alcatel-lucent.com  Wed Apr 18 06:33:09 2012
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 61D4721F84F0; Wed, 18 Apr 2012 06:33:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.649
X-Spam-Level: 
X-Spam-Status: No, score=-109.649 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BFAKe1ld35dq; Wed, 18 Apr 2012 06:33:07 -0700 (PDT)
Received: from smail6.alcatel.fr (smail6.alcatel.fr [64.208.49.42]) by ietfa.amsl.com (Postfix) with ESMTP id C3F9721F84D6; Wed, 18 Apr 2012 06:33:06 -0700 (PDT)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail6.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q3IDX292018240 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 18 Apr 2012 15:33:05 +0200
Received: from [172.27.205.177] (135.120.57.7) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (135.120.45.63) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 18 Apr 2012 15:32:52 +0200
Message-ID: <4F8EC284.3020301@alcatel-lucent.com>
Date: Wed, 18 Apr 2012 15:32:52 +0200
From: Martin Vigoureux <martin.vigoureux@alcatel-lucent.com>
Organization: Alcatel-Lucent
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.2.28) Gecko/20120306 Thunderbird/3.1.20
MIME-Version: 1.0
To: "Eggert, Lars" <lars@netapp.com>
Subject: Re: latest missing replaced-by information
References: <E9354164-6546-42A9-BAC4-BE6660855AE9@netapp.com>
In-Reply-To: <E9354164-6546-42A9-BAC4-BE6660855AE9@netapp.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.84
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>, Internet Research Steering Group <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: Wed, 18 Apr 2012 13:33:09 -0000

Lars,

thanks.
As a side question, I was wondering if managing the "replaced by" status 
shouldn't be under the full responsibility of the chairs, i.e., a 
functionality of the datatracker rather than the chairs needing to send 
an e-mail to the secretariat for each (batch of) changes.
What do you think? and that question also goes to the chairs.

-m

Le 18/04/2012 10:49, Eggert, Lars a écrit :
> Hi,
>
> here's yet another installment in the series of reports on potentially missing "replaced-by" relationships in the IETF datatracker.
>
> *** NEW *** Also includes IRTF documents now.
>
> WG and RG chairs are encouraged to check whether these are accurate for their groups, and if so, send a ticket to the secretariat instructing them to "record in the database that draft X replaced draft Y".
>
> As always, double-check before reporting to the secretariat. Also, see list of possible inconsistencies at the end of the report.
>
> (Note that the IPR disclosure search tool uses these replaced-by relationships, so keeping them up-to-date is actually useful and not just WG hygiene.)
>
> Lars
>
>
> -----------------------------------------------------------------
> APP Area
> -----------------------------------------------------------------
> CORE Working Group, APP Area
>     draft-rahman-core-groupcomm POTENTIALLY REPLACED BY draft-ietf-core-groupcomm
>
> EAI Working Group, APP Area
>     draft-duerst-eai-mailto POTENTIALLY REPLACED BY draft-ietf-eai-mailto
>     draft-yao-eai-rfc5336bis POTENTIALLY REPLACED BY draft-ietf-eai-rfc5336bis
>
> PAWS Working Group, APP Area
>     draft-probasco-paws-problem-stmt-usecases-rqmts POTENTIALLY REPLACED BY draft-ietf-paws-problem-stmt-usecases-rqmts
>
> VCARDDAV Working Group, APP Area
>     draft-cauchie-vcarddav-oma-cab-extensions POTENTIALLY REPLACED BY draft-ietf-vcarddav-oma-cab-extensions
>
> -----------------------------------------------------------------
> CONCLUDED Area
> -----------------------------------------------------------------
> ATOMPUB Working Group, CONCLUDED Area
>     draft-snell-atompub-autodiscovery POTENTIALLY REPLACED BY draft-ietf-atompub-autodiscovery
>
> HTTP Working Group, CONCLUDED Area
>     draft-wallis-http-digest-auth-a3a8 POTENTIALLY REPLACED BY draft-ietf-http-digest-auth-a3a8
>
> IDNABIS Working Group, CONCLUDED Area
>     draft-faltstrom-idnabis-tables POTENTIALLY REPLACED BY draft-ietf-idnabis-tables
>
> IMAP Working Group, CONCLUDED Area
>     draft-crispin-imap-compat POTENTIALLY REPLACED BY draft-ietf-imap-compat
>
> TFTPEXTS Working Group, CONCLUDED Area
>     draft-malkin-tftpexts-blksize-opt POTENTIALLY REPLACED BY draft-ietf-tftpexts-blksize-opt
>     draft-malkin-tftpexts-option-ext POTENTIALLY REPLACED BY draft-ietf-tftpexts-option-ext
>     draft-malkin-tftpexts-options POTENTIALLY REPLACED BY draft-ietf-tftpexts-options
>
> XMPP Working Group, CONCLUDED Area
>     draft-barnes-xmpp-dna POTENTIALLY REPLACED BY draft-ietf-xmpp-dna
>     draft-miller-xmpp-e2e POTENTIALLY REPLACED BY draft-ietf-xmpp-e2e
>     draft-saintandre-xmpp-6122bis POTENTIALLY REPLACED BY draft-ietf-xmpp-6122bis
>
> MIPSHOP Working Group, CONCLUDED Area
>     draft-xia-mipshop-fmip-ptp POTENTIALLY REPLACED BY draft-ietf-mipshop-fmip-ptp
>
> NETLMM Working Group, CONCLUDED Area
>     draft-cui-netlmm-mip-interactions POTENTIALLY REPLACED BY draft-ietf-netlmm-mip-interactions
>     draft-glenn-netlmm-pmipv6-mib POTENTIALLY REPLACED BY draft-ietf-netlmm-pmipv6-mib
>     draft-korhonen-netlmm-lma-discovery POTENTIALLY REPLACED BY draft-ietf-netlmm-lma-discovery
>     draft-xia-netlmm-lma-discovery POTENTIALLY REPLACED BY draft-ietf-netlmm-lma-discovery
>
> SEND Working Group, CONCLUDED Area
>     draft-arkko-send-cga POTENTIALLY REPLACED BY draft-ietf-send-cga
>     draft-arkko-send-ndopt POTENTIALLY REPLACED BY draft-ietf-send-ndopt
>
> SHIM6 Working Group, CONCLUDED Area
>     draft-garcia-shim6-applicability POTENTIALLY REPLACED BY draft-ietf-shim6-applicability
>
> CAPWAP Working Group, CONCLUDED Area
>     draft-yangshi-capwap-802dot11-mib POTENTIALLY REPLACED BY draft-ietf-capwap-802dot11-mib
>     draft-yangshi-capwap-base-mib POTENTIALLY REPLACED BY draft-ietf-capwap-base-mib
>
> RMONMIB Working Group, CONCLUDED Area
>     draft-bierman-rmonmib-hc-alarm-mib POTENTIALLY REPLACED BY draft-ietf-rmonmib-hc-alarm-mib
>
> MEGACO Working Group, CONCLUDED Area
>     draft-blatherwick-megaco-ipphone POTENTIALLY REPLACED BY draft-ietf-megaco-ipphone
>
> SIGTRAN Working Group, CONCLUDED Area
>     draft-anil-sigtran-dua POTENTIALLY REPLACED BY draft-ietf-sigtran-dua
>
> SIP Working Group, CONCLUDED Area
>     draft-arkko-sip-sec-agree POTENTIALLY REPLACED BY draft-ietf-sip-sec-agree
>     draft-biggs-sip-replaces POTENTIALLY REPLACED BY draft-ietf-sip-replaces
>     draft-pashalidis-sip-saml POTENTIALLY REPLACED BY draft-ietf-sip-saml
>
> SIPPING Working Group, CONCLUDED Area
>     draft-drage-sipping-service-identification POTENTIALLY REPLACED BY draft-ietf-sipping-service-identification
>     draft-elwell-sipping-update-pai POTENTIALLY REPLACED BY draft-ietf-sipping-update-pai
>     draft-hilt-sipping-overload-design POTENTIALLY REPLACED BY draft-ietf-sipping-overload-design
>     draft-petrie-sipping-profile-datasets POTENTIALLY REPLACED BY draft-ietf-sipping-profile-datasets
>     draft-rosenberg-sipping-service-identification POTENTIALLY REPLACED BY draft-ietf-sipping-service-identification
>     draft-zhang-sipping-overlap POTENTIALLY REPLACED BY draft-ietf-sipping-overlap
>
> SPEERMINT Working Group, CONCLUDED Area
>     draft-meyer-speermint-reqs-and-terminology POTENTIALLY REPLACED BY draft-ietf-speermint-reqs-and-terminology
>     draft-niccolini-speermint-voipthreats POTENTIALLY REPLACED BY draft-ietf-speermint-voipthreats
>
> XCON Working Group, CONCLUDED Area
>     draft-barnes-xcon-ccmp POTENTIALLY REPLACED BY draft-ietf-xcon-ccmp
>     draft-barnes-xcon-examples POTENTIALLY REPLACED BY draft-ietf-xcon-examples
>
> DKIM Working Group, CONCLUDED Area
>     draft-lindsey-dkim-mailinglists POTENTIALLY REPLACED BY draft-ietf-dkim-mailinglists
>
> SACRED Working Group, CONCLUDED Area
>     draft-arsenault-sacred-reqs POTENTIALLY REPLACED BY draft-ietf-sacred-reqs
>
> SASL Working Group, CONCLUDED Area
>     draft-zeilenga-sasl-crammd5 POTENTIALLY REPLACED BY draft-ietf-sasl-crammd5
>     draft-zeilenga-sasl-rfc2222bis POTENTIALLY REPLACED BY draft-ietf-sasl-rfc2222bis
>
> SMIME Working Group, CONCLUDED Area
>     draft-dusse-smime-cert POTENTIALLY REPLACED BY draft-ietf-smime-cert
>     draft-dusse-smime-msg POTENTIALLY REPLACED BY draft-ietf-smime-msg
>
> DIFFSERV Working Group, CONCLUDED Area
>     draft-baker-diffserv-mib POTENTIALLY REPLACED BY draft-ietf-diffserv-mib
>     draft-black-diffserv-tunnels POTENTIALLY REPLACED BY draft-ietf-diffserv-tunnels
>
> RSVP Working Group, CONCLUDED Area
>     draft-berger-rsvp-refresh-reduct POTENTIALLY REPLACED BY draft-ietf-rsvp-refresh-reduct
>
> -----------------------------------------------------------------
> INT Area
> -----------------------------------------------------------------
> 6MAN Working Group, INT Area
>     draft-carpenter-6man-uri-zoneid POTENTIALLY REPLACED BY draft-ietf-6man-uri-zoneid
>     draft-costa-6man-dad-proxy POTENTIALLY REPLACED BY draft-ietf-6man-dad-proxy
>     draft-fujisaki-6man-addr-select-opt POTENTIALLY REPLACED BY draft-ietf-6man-addr-select-opt
>     draft-george-6man-3627-historic POTENTIALLY REPLACED BY draft-ietf-6man-3627-historic
>     draft-gont-6man-ipv6-atomic-fragments POTENTIALLY REPLACED BY draft-ietf-6man-ipv6-atomic-fragments
>     draft-hsingh-6man-enhanced-dad POTENTIALLY REPLACED BY draft-ietf-6man-enhanced-dad
>     draft-joshi-6man-neighbor-inform POTENTIALLY REPLACED BY draft-ietf-6man-neighbor-inform
>     draft-lynn-6man-6lobac POTENTIALLY REPLACED BY draft-ietf-6man-6lobac
>     draft-nordmark-6man-impatient-nud POTENTIALLY REPLACED BY draft-ietf-6man-impatient-nud
>
> ANCP Working Group, INT Area
>     draft-lefaucheur-ancp-mc-extensions POTENTIALLY REPLACED BY draft-ietf-ancp-mc-extensions
>
> CSI Working Group, INT Area
>     draft-jiang-csi-dhcpv6-cga-ps POTENTIALLY REPLACED BY draft-ietf-csi-dhcpv6-cga-ps
>     draft-rgaglian-csi-send-name-type-registry POTENTIALLY REPLACED BY draft-ietf-csi-send-name-type-registry
>
> DHC Working Group, INT Area
>     draft-jiang-dhc-cga-config-dhcpv6 POTENTIALLY REPLACED BY draft-ietf-dhc-cga-config-dhcpv6
>     draft-jjmb-dhc-dhcpv6-redundancy-consider POTENTIALLY REPLACED BY draft-ietf-dhc-dhcpv6-redundancy-consider
>     draft-miles-dhc-dhcpv6-ldra POTENTIALLY REPLACED BY draft-ietf-dhc-dhcpv6-ldra
>     draft-mrugalski-dhc-dhcpv6-failover-requirements POTENTIALLY REPLACED BY draft-ietf-dhc-dhcpv6-failover-requirements
>     draft-xia-dhc-host-gen-id POTENTIALLY REPLACED BY draft-ietf-dhc-host-gen-id
>
> DNSEXT Working Group, INT Area
>     draft-wang-dnsext-newzone-notify POTENTIALLY REPLACED BY draft-ietf-dnsext-newzone-notify
>
> HIP Working Group, INT Area
>     draft-camarillo-hip-via POTENTIALLY REPLACED BY draft-ietf-hip-via
>     draft-henderson-hip-rfc5206-bis POTENTIALLY REPLACED BY draft-ietf-hip-rfc5206-bis
>     draft-jokela-hip-rfc5202-bis POTENTIALLY REPLACED BY draft-ietf-hip-rfc5202-bis
>     draft-keranen-hip-native-nat-traversal POTENTIALLY REPLACED BY draft-ietf-hip-native-nat-traversal
>     draft-keranen-hip-over-hip POTENTIALLY REPLACED BY draft-ietf-hip-over-hip
>     draft-keranen-hip-reload-instance POTENTIALLY REPLACED BY draft-ietf-hip-reload-instance
>     draft-moskowitz-hip-rfc4423-bis POTENTIALLY REPLACED BY draft-ietf-hip-rfc4423-bis
>     draft-moskowitz-hip-rfc5201-bis POTENTIALLY REPLACED BY draft-ietf-hip-rfc5201-bis
>     draft-nikander-hip-hiccups POTENTIALLY REPLACED BY draft-ietf-hip-hiccups
>
> INTAREA Working Group, INT Area
>     draft-boucadair-intarea-nat-reveal-analysis POTENTIALLY REPLACED BY draft-ietf-intarea-nat-reveal-analysis
>
> LISP Working Group, INT Area
>     draft-jakab-lisp-deployment POTENTIALLY REPLACED BY draft-ietf-lisp-deployment
>     draft-maino-lisp-sec POTENTIALLY REPLACED BY draft-ietf-lisp-sec
>     draft-meyer-lisp-eid-block POTENTIALLY REPLACED BY draft-ietf-lisp-eid-block
>
> MIF Working Group, INT Area
>     draft-liu-mif-api-extension POTENTIALLY REPLACED BY draft-ietf-mif-api-extension
>
> MULTIMOB Working Group, INT Area
>     draft-schmidt-multimob-pmipv6-source POTENTIALLY REPLACED BY draft-ietf-multimob-pmipv6-source
>     draft-wu-multimob-igmp-mld-tuning POTENTIALLY REPLACED BY draft-ietf-multimob-igmp-mld-tuning
>     draft-zuniga-multimob-pmipv6-ropt POTENTIALLY REPLACED BY draft-ietf-multimob-pmipv6-ropt
>
> NETEXT Working Group, INT Area
>     draft-bernardos-netext-pmipv6-flowmob POTENTIALLY REPLACED BY draft-ietf-netext-pmipv6-flowmob
>     draft-korhonen-netext-redirect POTENTIALLY REPLACED BY draft-ietf-netext-redirect
>     draft-krishnan-netext-pmip-lr POTENTIALLY REPLACED BY draft-ietf-netext-pmip-lr
>     draft-melia-netext-logical-interface-support POTENTIALLY REPLACED BY draft-ietf-netext-logical-interface-support
>     draft-zhou-netext-pd-pmip POTENTIALLY REPLACED BY draft-ietf-netext-pd-pmip
>
> PCP Working Group, INT Area
>     draft-bpw-pcp-dhcp POTENTIALLY REPLACED BY draft-ietf-pcp-dhcp
>     draft-bpw-pcp-upnp-igd-interworking POTENTIALLY REPLACED BY draft-ietf-pcp-upnp-igd-interworking
>
> SAVI Working Group, INT Area
>     draft-bi-savi-mix POTENTIALLY REPLACED BY draft-ietf-savi-mix
>
> SOFTWIRE Working Group, INT Area
>     draft-guo-softwire-6rd-radius-attrib POTENTIALLY REPLACED BY draft-ietf-softwire-6rd-radius-attrib
>     draft-ieft-softwire-dslite-deployment POTENTIALLY REPLACED BY draft-ietf-softwire-dslite-deployment
>     draft-lee-softwire-dslite-deployment POTENTIALLY REPLACED BY draft-ietf-softwire-dslite-deployment
>     draft-maglione-softwire-dslite-radius-ext POTENTIALLY REPLACED BY draft-ietf-softwire-dslite-radius-ext
>     draft-qin-softwire-multicast-prefix-option POTENTIALLY REPLACED BY draft-ietf-softwire-multicast-prefix-option
>     draft-xu-softwire-mesh-multicast POTENTIALLY REPLACED BY draft-ietf-softwire-mesh-multicast
>
> TICTOC Working Group, INT Area
>     draft-davari-tictoc-1588overmpls POTENTIALLY REPLACED BY draft-ietf-tictoc-1588overmpls
>     draft-mizrahi-tictoc-security-requirements POTENTIALLY REPLACED BY draft-ietf-tictoc-security-requirements
>     draft-vinay-tictoc-ptp-mib POTENTIALLY REPLACED BY draft-ietf-tictoc-ptp-mib
>
> TRILL Working Group, INT Area
>     draft-tissa-trill-cmt POTENTIALLY REPLACED BY draft-ietf-trill-cmt
>
> -----------------------------------------------------------------
> IRTF Area
> -----------------------------------------------------------------
> DTNRG Working Group, IRTF Area
>     draft-lindgren-dtnrg-prophet POTENTIALLY REPLACED BY draft-irtf-dtnrg-prophet
>     draft-symington-dtnrg-bundle-metadata-block POTENTIALLY REPLACED BY draft-irtf-dtnrg-bundle-metadata-block
>     draft-symington-dtnrg-bundle-retrans-block POTENTIALLY REPLACED BY draft-irtf-dtnrg-bundle-retrans-block
>
> HIPRG Working Group, IRTF Area
>     draft-ahrenholz-hiprg-dht POTENTIALLY REPLACED BY draft-irtf-hiprg-dht
>
> MOBOPTS Working Group, IRTF Area
>     draft-koki-mobopts-l2-abstractions POTENTIALLY REPLACED BY draft-irtf-mobopts-l2-abstractions
>     draft-ohba-mobopts-mpa-framework POTENTIALLY REPLACED BY draft-irtf-mobopts-mpa-framework
>     draft-schmidt-mobopts-mmcastv6-ps POTENTIALLY REPLACED BY draft-irtf-mobopts-mmcastv6-ps
>     draft-weniger-mobopts-mip6-cnlocpriv POTENTIALLY REPLACED BY draft-irtf-mobopts-mip6-cnlocpriv
>
> P2PRG Working Group, IRTF Area
>     draft-gurbani-p2prg-simulation-survey POTENTIALLY REPLACED BY draft-irtf-p2prg-simulation-survey
>
> -----------------------------------------------------------------
> IRTF-CONCLUDED Area
> -----------------------------------------------------------------
> -----------------------------------------------------------------
> OPS Area
> -----------------------------------------------------------------
> ARMD Working Group, OPS Area
>     draft-dunbar-armd-problem-statement POTENTIALLY REPLACED BY draft-ietf-armd-problem-statement
>
> BMWG Working Group, OPS Area
>     draft-janovak-bmwg-ipflow-meth POTENTIALLY REPLACED BY draft-ietf-bmwg-ipflow-meth
>     draft-morton-bmwg-imix-genome POTENTIALLY REPLACED BY draft-ietf-bmwg-imix-genome
>
> DIME Working Group, OPS Area
>     draft-zorn-dime-rfc4005bis POTENTIALLY REPLACED BY draft-ietf-dime-rfc4005bis
>
> EMAN Working Group, OPS Area
>     draft-tychon-eman-applicability-statement POTENTIALLY REPLACED BY draft-ietf-eman-applicability-statement
>
> GROW Working Group, OPS Area
>     draft-dimitri-grow-rss POTENTIALLY REPLACED BY draft-ietf-grow-rss
>     draft-manderson-grow-geomrt POTENTIALLY REPLACED BY draft-ietf-grow-geomrt
>
> IPFIX Working Group, OPS Area
>     draft-boschi-ipfix-anon POTENTIALLY REPLACED BY draft-ietf-ipfix-anon
>     draft-boschi-ipfix-exporting-type POTENTIALLY REPLACED BY draft-ietf-ipfix-exporting-type
>     draft-claise-ipfix-export-per-sctp-stream POTENTIALLY REPLACED BY draft-ietf-ipfix-export-per-sctp-stream
>     draft-claise-ipfix-protocol-rfc5101bis POTENTIALLY REPLACED BY draft-ietf-ipfix-protocol-rfc5101bis
>     draft-dkcm-ipfix-rfc5815bis POTENTIALLY REPLACED BY draft-ietf-ipfix-rfc5815bis
>     draft-gupta-ipfix-reliability-template-ext POTENTIALLY REPLACED BY draft-ietf-ipfix-reliability-template-ext
>     draft-trammell-ipfix-file POTENTIALLY REPLACED BY draft-ietf-ipfix-file
>
> MBONED Working Group, OPS Area
>     draft-asaeda-mboned-mtrace-v2 POTENTIALLY REPLACED BY draft-ietf-mboned-mtrace-v2
>     draft-asaeda-mboned-session-announcement-req POTENTIALLY REPLACED BY draft-ietf-mboned-session-announcement-req
>     draft-bipi-mboned-ip-multicast-pm-requirement POTENTIALLY REPLACED BY draft-ietf-mboned-ip-multicast-pm-requirement
>     draft-venaas-mboned-mcaddrdoc POTENTIALLY REPLACED BY draft-ietf-mboned-mcaddrdoc
>     draft-venaas-mboned-ssmping POTENTIALLY REPLACED BY draft-ietf-mboned-ssmping
>
> NETCONF Working Group, OPS Area
>     draft-bierman-netconf-access-control POTENTIALLY REPLACED BY draft-ietf-netconf-access-control
>     draft-bierman-netconf-with-defaults POTENTIALLY REPLACED BY draft-ietf-netconf-with-defaults
>     draft-chisholm-netconf-monitoring POTENTIALLY REPLACED BY draft-ietf-netconf-monitoring
>
> NETMOD Working Group, OPS Area
>     draft-bierman-netmod-system-mgmt POTENTIALLY REPLACED BY draft-ietf-netmod-system-mgmt
>     draft-bjorklund-netmod-interfaces-cfg POTENTIALLY REPLACED BY draft-ietf-netmod-interfaces-cfg
>     draft-bjorklund-netmod-ip-cfg POTENTIALLY REPLACED BY draft-ietf-netmod-ip-cfg
>     draft-lhotka-netmod-routing-cfg POTENTIALLY REPLACED BY draft-ietf-netmod-routing-cfg
>     draft-schoenw-netmod-smi-yang POTENTIALLY REPLACED BY draft-ietf-netmod-smi-yang
>
> OPSAWG Working Group, OPS Area
>     draft-mizrahi-opsawg-oam-overview POTENTIALLY REPLACED BY draft-ietf-opsawg-oam-overview
>
> OPSEC Working Group, OPS Area
>     draft-gont-opsec-icmp-filtering POTENTIALLY REPLACED BY draft-ietf-opsec-icmp-filtering
>     draft-gont-opsec-ip-security POTENTIALLY REPLACED BY draft-ietf-opsec-ip-security
>
> RADEXT Working Group, OPS Area
>     draft-dekok-radext-dtls POTENTIALLY REPLACED BY draft-ietf-radext-dtls
>     draft-dekok-radext-radius-extensions POTENTIALLY REPLACED BY draft-ietf-radext-radius-extensions
>     draft-dekok-radext-tcp-transport POTENTIALLY REPLACED BY draft-ietf-radext-tcp-transport
>     draft-lourdelet-radext-ipv6-access POTENTIALLY REPLACED BY draft-ietf-radext-ipv6-access
>     draft-nelson-radext-crypto-agility-requirements POTENTIALLY REPLACED BY draft-ietf-radext-crypto-agility-requirements
>     draft-tiwari-radext-tunnel-type POTENTIALLY REPLACED BY draft-ietf-radext-tunnel-type
>
> V6OPS Working Group, OPS Area
>     draft-hilliard-v6ops-ipv6-discard-prefix POTENTIALLY REPLACED BY draft-ietf-v6ops-ipv6-discard-prefix
>     draft-rgaglian-v6ops-v6inixp POTENTIALLY REPLACED BY draft-ietf-v6ops-v6inixp
>     draft-vandevelde-v6ops-ra-guard POTENTIALLY REPLACED BY draft-ietf-v6ops-ra-guard
>     draft-wbeebee-v6ops-ipv6-cpe-router-bis POTENTIALLY REPLACED BY draft-ietf-v6ops-ipv6-cpe-router-bis
>
> -----------------------------------------------------------------
> RAI Area
> -----------------------------------------------------------------
> ATOCA Working Group, RAI Area
>     draft-rosen-atoca-cap POTENTIALLY REPLACED BY draft-ietf-atoca-cap
>
> BLISS Working Group, RAI Area
>     draft-elwell-bliss-ach-analysis POTENTIALLY REPLACED BY draft-ietf-bliss-ach-analysis
>     draft-poetzl-bliss-call-completion POTENTIALLY REPLACED BY draft-ietf-bliss-call-completion
>     draft-procter-bliss-call-park-extension POTENTIALLY REPLACED BY draft-ietf-bliss-call-park-extension
>     draft-rosenberg-bliss-problem-statement POTENTIALLY REPLACED BY draft-ietf-bliss-problem-statement
>
> CLUE Working Group, RAI Area
>     draft-romanow-clue-framework POTENTIALLY REPLACED BY draft-ietf-clue-framework
>     draft-romanow-clue-telepresence-requirements POTENTIALLY REPLACED BY draft-ietf-clue-telepresence-requirements
>     draft-romanow-clue-telepresence-use-cases POTENTIALLY REPLACED BY draft-ietf-clue-telepresence-use-cases
>
> CODEC Working Group, RAI Area
>     draft-valin-codec-guidelines POTENTIALLY REPLACED BY draft-ietf-codec-guidelines
>     draft-valin-codec-results POTENTIALLY REPLACED BY draft-ietf-codec-results
>
> DRINKS Working Group, RAI Area
>     draft-channabasappa-drinks-usecases-requirements POTENTIALLY REPLACED BY draft-ietf-drinks-usecases-requirements
>
> GEOPRIV Working Group, RAI Area
>     draft-barnes-geopriv-policy-uri POTENTIALLY REPLACED BY draft-ietf-geopriv-policy-uri
>     draft-mayrhofer-geopriv-geo-uri POTENTIALLY REPLACED BY draft-ietf-geopriv-geo-uri
>     draft-winterbottom-geopriv-local-civic POTENTIALLY REPLACED BY draft-ietf-geopriv-local-civic
>
> MMUSIC Working Group, RAI Area
>     draft-garcia-mmusic-sdp-miscellaneous-caps POTENTIALLY REPLACED BY draft-ietf-mmusic-sdp-miscellaneous-caps
>     draft-greevenbosch-mmusic-parallax-attribute POTENTIALLY REPLACED BY draft-ietf-mmusic-parallax-attribute
>     draft-greevenbosch-mmusic-signal-3d-format POTENTIALLY REPLACED BY draft-ietf-mmusic-signal-3d-format
>     draft-holmberg-mmusic-sdp-bundle-negotiation POTENTIALLY REPLACED BY draft-ietf-mmusic-sdp-bundle-negotiation
>     draft-loreto-mmusic-sctp-sdp POTENTIALLY REPLACED BY draft-ietf-mmusic-sctp-sdp
>     draft-polk-mmusic-traffic-class-for-sdp POTENTIALLY REPLACED BY draft-ietf-mmusic-traffic-class-for-sdp
>
> P2PSIP Working Group, RAI Area
>     draft-bryan-p2psip-reload POTENTIALLY REPLACED BY draft-ietf-p2psip-reload
>     draft-zong-p2psip-drr POTENTIALLY REPLACED BY draft-ietf-p2psip-drr
>     draft-zong-p2psip-rpr POTENTIALLY REPLACED BY draft-ietf-p2psip-rpr
>
> PAYLOAD Working Group, RAI Area
>     draft-westin-payload-vp8 POTENTIALLY REPLACED BY draft-ietf-payload-vp8
>
> RTCWEB Working Group, RAI Area
>     draft-uberti-rtcweb-jsep POTENTIALLY REPLACED BY draft-ietf-rtcweb-jsep
>
> SIPCORE Working Group, RAI Area
>     draft-holmberg-sipcore-proxy-feature POTENTIALLY REPLACED BY draft-ietf-sipcore-proxy-feature
>
> SOC Working Group, RAI Area
>     draft-noel-soc-overload-rate-control POTENTIALLY REPLACED BY draft-ietf-soc-overload-rate-control
>     draft-shen-soc-load-control-event-package POTENTIALLY REPLACED BY draft-ietf-soc-load-control-event-package
>
> XMPP Working Group, RAI Area
>     draft-barnes-xmpp-dna POTENTIALLY REPLACED BY draft-ietf-xmpp-dna
>     draft-miller-xmpp-e2e POTENTIALLY REPLACED BY draft-ietf-xmpp-e2e
>     draft-saintandre-xmpp-6122bis POTENTIALLY REPLACED BY draft-ietf-xmpp-6122bis
>
> XRBLOCK Working Group, RAI Area
>     draft-clark-xrblock-rtcp-xr-qoe POTENTIALLY REPLACED BY draft-ietf-xrblock-rtcp-xr-qoe
>
> -----------------------------------------------------------------
> RTG Area
> -----------------------------------------------------------------
> BFD Working Group, RTG Area
>     draft-bhatia-bfd-hmac-sha POTENTIALLY REPLACED BY draft-ietf-bfd-hmac-sha
>
> CCAMP Working Group, RTG Area
>     draft-bccg-ccamp-otn-g709-info-model POTENTIALLY REPLACED BY draft-ietf-ccamp-otn-g709-info-model
>     draft-berger-ccamp-assoc-info POTENTIALLY REPLACED BY draft-ietf-ccamp-assoc-info
>     draft-bernstein-ccamp-wson-signaling POTENTIALLY REPLACED BY draft-ietf-ccamp-wson-signaling
>
> FORCES Working Group, RTG Area
>     draft-hadi-forces-sctptml POTENTIALLY REPLACED BY draft-ietf-forces-sctptml
>     draft-haleplidis-forces-implementation-experience POTENTIALLY REPLACED BY draft-ietf-forces-implementation-experience
>
> IDR Working Group, RTG Area
>     draft-decraene-idr-reserved-extended-communities POTENTIALLY REPLACED BY draft-ietf-idr-reserved-extended-communities
>     draft-keyupate-idr-bgp-gr-notification POTENTIALLY REPLACED BY draft-ietf-idr-bgp-gr-notification
>     draft-keyur-idr-enhanced-gr POTENTIALLY REPLACED BY draft-ietf-idr-enhanced-gr
>     draft-raszuk-idr-flow-spec-v6 POTENTIALLY REPLACED BY draft-ietf-idr-flow-spec-v6
>     draft-wkumari-idr-as0 POTENTIALLY REPLACED BY draft-ietf-idr-as0
>
> ISIS Working Group, RTG Area
>     draft-chopps-isis-bfd-tlv POTENTIALLY REPLACED BY draft-ietf-isis-bfd-tlv
>     draft-ginsberg-isis-genapp POTENTIALLY REPLACED BY draft-ietf-isis-genapp
>     draft-previdi-isis-mi POTENTIALLY REPLACED BY draft-ietf-isis-mi
>     draft-shen-isis-oper-enhance POTENTIALLY REPLACED BY draft-ietf-isis-oper-enhance
>
> L2VPN Working Group, RTG Area
>     draft-delord-l2vpn-ldp-vpls-broadcast-exten POTENTIALLY REPLACED BY draft-ietf-l2vpn-ldp-vpls-broadcast-exten
>     draft-henderickx-l2vpn-vpls-multihoming POTENTIALLY REPLACED BY draft-ietf-l2vpn-vpls-multihoming
>     draft-key-l2vpn-etree-frwk POTENTIALLY REPLACED BY draft-ietf-l2vpn-etree-frwk
>     draft-kompella-l2vpn-vpls-multihoming POTENTIALLY REPLACED BY draft-ietf-l2vpn-vpls-multihoming
>     draft-pdutta-l2vpn-vpls-ldp-mac-opt POTENTIALLY REPLACED BY draft-ietf-l2vpn-vpls-ldp-mac-opt
>     draft-pkwok-l2vpn-vpls-macflush-ld POTENTIALLY REPLACED BY draft-ietf-l2vpn-vpls-macflush-ld
>     draft-sajassi-l2vpn-pbb-evpn POTENTIALLY REPLACED BY draft-ietf-l2vpn-pbb-evpn
>     draft-sajassi-l2vpn-vpls-pbb-interop POTENTIALLY REPLACED BY draft-ietf-l2vpn-vpls-pbb-interop
>
> L3VPN Working Group, RTG Area
>     draft-rekhter-l3vpn-virtual-hub POTENTIALLY REPLACED BY draft-ietf-l3vpn-virtual-hub
>
> MANET Working Group, RTG Area
>     draft-herberg-manet-nhdp-sec POTENTIALLY REPLACED BY draft-ietf-manet-nhdp-sec
>     draft-herberg-manet-nhdp-sec-threats POTENTIALLY REPLACED BY draft-ietf-manet-nhdp-sec-threats
>
> MPLS Working Group, RTG Area
>     draft-frost-mpls-tp-loss-delay-profile POTENTIALLY REPLACED BY draft-ietf-mpls-tp-loss-delay-profile
>     draft-koike-mpls-tp-temporal-hitless-psm POTENTIALLY REPLACED BY draft-ietf-mpls-tp-temporal-hitless-psm
>     draft-liu-mpls-tp-ring-protection POTENTIALLY REPLACED BY draft-ietf-mpls-tp-ring-protection
>     draft-raggarwa-mpls-seamless-mcast POTENTIALLY REPLACED BY draft-ietf-mpls-seamless-mcast
>
> OSPF Working Group, RTG Area
>     draft-acee-ospf-multi-instance POTENTIALLY REPLACED BY draft-ietf-ospf-multi-instance
>     draft-acee-ospf-transport-instance POTENTIALLY REPLACED BY draft-ietf-ospf-transport-instance
>     draft-cheng-ospf-ipv4-embedded-ipv6-routing POTENTIALLY REPLACED BY draft-ietf-ospf-ipv4-embedded-ipv6-routing
>     draft-nguyen-ospf-lls POTENTIALLY REPLACED BY draft-ietf-ospf-lls
>     draft-nsheth-ospf-hybrid-bcast-and-p2mp POTENTIALLY REPLACED BY draft-ietf-ospf-hybrid-bcast-and-p2mp
>     draft-ogier-ospf-dbex-opt POTENTIALLY REPLACED BY draft-ietf-ospf-dbex-opt
>     draft-retana-ospf-rfc3137bis POTENTIALLY REPLACED BY draft-ietf-ospf-rfc3137bis
>     draft-venkata-ospf-dynamic-hostname POTENTIALLY REPLACED BY draft-ietf-ospf-dynamic-hostname
>
> PCE Working Group, RTG Area
>     draft-tang-pce-stateful-pce POTENTIALLY REPLACED BY draft-ietf-pce-stateful-pce
>     draft-zhao-pce-pcep-inter-domain-p2mp-procedures POTENTIALLY REPLACED BY draft-ietf-pce-pcep-inter-domain-p2mp-procedures
>
> PIM Working Group, RTG Area
>     draft-hou-pim-drlb POTENTIALLY REPLACED BY draft-ietf-pim-drlb
>
> PWE3 Working Group, RTG Area
>     draft-bryant-pwe3-packet-pw POTENTIALLY REPLACED BY draft-ietf-pwe3-packet-pw
>     draft-delregno-pwe3-pw-vccv-impl-survey-results POTENTIALLY REPLACED BY draft-ietf-pwe3-pw-vccv-impl-survey-results
>     draft-jin-pwe3-cbit-negotiation POTENTIALLY REPLACED BY draft-ietf-pwe3-cbit-negotiation
>     draft-raza-pwe3-pw-typed-wc-fec POTENTIALLY REPLACED BY draft-ietf-pwe3-pw-typed-wc-fec
>
> ROLL Working Group, RTG Area
>     draft-dt-roll-p2p-rpl POTENTIALLY REPLACED BY draft-ietf-roll-p2p-rpl
>     draft-gnawali-roll-minrank-hysteresis-of POTENTIALLY REPLACED BY draft-ietf-roll-minrank-hysteresis-of
>     draft-goyal-roll-p2p-measurement POTENTIALLY REPLACED BY draft-ietf-roll-p2p-measurement
>     draft-levis-roll-trickle POTENTIALLY REPLACED BY draft-ietf-roll-trickle
>     draft-popa-roll-applicability-ami POTENTIALLY REPLACED BY draft-ietf-roll-applicability-ami
>     draft-tsao-roll-security-framework POTENTIALLY REPLACED BY draft-ietf-roll-security-framework
>
> RTGWG Working Group, RTG Area
>     draft-atlas-rtgwg-mrt-frr-architecture POTENTIALLY REPLACED BY draft-ietf-rtgwg-mrt-frr-architecture
>
> -----------------------------------------------------------------
> SEC Area
> -----------------------------------------------------------------
> ABFAB Working Group, SEC Area
>     draft-lear-abfab-arch POTENTIALLY REPLACED BY draft-ietf-abfab-arch
>
> HOKEY Working Group, SEC Area
>     draft-wu-hokey-rfc5296bis POTENTIALLY REPLACED BY draft-ietf-hokey-rfc5296bis
>
> MILE Working Group, SEC Area
>     draft-moriarty-mile-grc-exchange POTENTIALLY REPLACED BY draft-ietf-mile-grc-exchange
>
> NEA Working Group, SEC Area
>     draft-hanna-nea-pt-eap POTENTIALLY REPLACED BY draft-ietf-nea-pt-eap
>     draft-sangster-nea-pt-tls POTENTIALLY REPLACED BY draft-ietf-nea-pt-tls
>
> OAUTH Working Group, SEC Area
>     draft-mortimore-oauth-assertions POTENTIALLY REPLACED BY draft-ietf-oauth-assertions
>
> PKIX Working Group, SEC Area
>     draft-cooper-pkix-rfc2560bis POTENTIALLY REPLACED BY draft-ietf-pkix-rfc2560bis
>     draft-cooper-pkix-rfc5280-clarifications POTENTIALLY REPLACED BY draft-ietf-pkix-rfc5280-clarifications
>     draft-santesson-pkix-certimage POTENTIALLY REPLACED BY draft-ietf-pkix-certimage
>
> TLS Working Group, SEC Area
>     draft-kanno-tls-camellia POTENTIALLY REPLACED BY draft-ietf-tls-camellia
>     draft-rescorla-tls-suiteb POTENTIALLY REPLACED BY draft-ietf-tls-suiteb
>     draft-seggelmann-tls-dtls-heartbeat POTENTIALLY REPLACED BY draft-ietf-tls-dtls-heartbeat
>
> -----------------------------------------------------------------
> TSV Area
> -----------------------------------------------------------------
> ALTO Working Group, TSV Area
>     draft-song-alto-server-discovery POTENTIALLY REPLACED BY draft-ietf-alto-server-discovery
>     draft-stiemerling-alto-deployments POTENTIALLY REPLACED BY draft-ietf-alto-deployments
>
> BEHAVE Working Group, TSV Area
>     draft-liu-behave-ftp64 POTENTIALLY REPLACED BY draft-ietf-behave-ftp64
>     draft-penno-behave-64-analysis POTENTIALLY REPLACED BY draft-ietf-behave-64-analysis
>
> CDNI Working Group, TSV Area
>     draft-watson-cdni-use-cases POTENTIALLY REPLACED BY draft-ietf-cdni-use-cases
>
> CONEX Working Group, TSV Area
>     draft-krishnan-conex-destopt POTENTIALLY REPLACED BY draft-ietf-conex-destopt
>     draft-kuehlewind-conex-tcp-modifications POTENTIALLY REPLACED BY draft-ietf-conex-tcp-modifications
>     draft-mathis-conex-abstract-mech POTENTIALLY REPLACED BY draft-ietf-conex-abstract-mech
>     draft-moncaster-conex-concepts-uses POTENTIALLY REPLACED BY draft-ietf-conex-concepts-uses
>
> DECADE Working Group, TSV Area
>     draft-alimi-decade-arch POTENTIALLY REPLACED BY draft-ietf-decade-arch
>     draft-chen-decade-integration-example POTENTIALLY REPLACED BY draft-ietf-decade-integration-example
>     draft-huang-decade-integration-example POTENTIALLY REPLACED BY draft-ietf-decade-integration-example
>
> FECFRAME Working Group, TSV Area
>     draft-roca-fecframe-ldpc POTENTIALLY REPLACED BY draft-ietf-fecframe-ldpc
>     draft-roca-fecframe-simple-rs POTENTIALLY REPLACED BY draft-ietf-fecframe-simple-rs
>
> IPPM Working Group, TSV Area
>     draft-baillargeon-ippm-twamp-value-added-octets POTENTIALLY REPLACED BY draft-ietf-ippm-twamp-value-added-octets
>     draft-geib-ippm-metrictest POTENTIALLY REPLACED BY draft-ietf-ippm-metrictest
>     draft-morton-ippm-rt-loss POTENTIALLY REPLACED BY draft-ietf-ippm-rt-loss
>     draft-morton-ippm-testplan-rfc2679 POTENTIALLY REPLACED BY draft-ietf-ippm-testplan-rfc2679
>
> NFSV4 Working Group, TSV Area
>     draft-alexrn-nfsv4-ipv6 POTENTIALLY REPLACED BY draft-ietf-nfsv4-ipv6
>     draft-dnoveck-nfsv4-migration-issues POTENTIALLY REPLACED BY draft-ietf-nfsv4-migration-issues
>     draft-eisler-nfsv4-minorversion-2-requirements POTENTIALLY REPLACED BY draft-ietf-nfsv4-minorversion-2-requirements
>     draft-faibish-nfsv4-pnfs-access-permissions-check POTENTIALLY REPLACED BY draft-ietf-nfsv4-pnfs-access-permissions-check
>     draft-faibish-nfsv4-pnfs-block-disk-protection POTENTIALLY REPLACED BY draft-ietf-nfsv4-pnfs-block-disk-protection
>     draft-haynes-nfsv4-minorversion2 POTENTIALLY REPLACED BY draft-ietf-nfsv4-minorversion2
>     draft-haynes-nfsv4-minorversion2-dot-x POTENTIALLY REPLACED BY draft-ietf-nfsv4-minorversion2-dot-x
>     draft-quigley-nfsv4-labreqs POTENTIALLY REPLACED BY draft-ietf-nfsv4-labreqs
>
> PCN Working Group, TSV Area
>     draft-karagiannis-pcn-signaling-requirements POTENTIALLY REPLACED BY draft-ietf-pcn-signaling-requirements
>
> PPSP Working Group, TSV Area
>     draft-gu-ppsp-peer-protocol POTENTIALLY REPLACED BY draft-ietf-ppsp-peer-protocol
>     draft-gu-ppsp-survey POTENTIALLY REPLACED BY draft-ietf-ppsp-survey
>
> TCPM Working Group, TSV Area
>     draft-blanton-tcpm-3517bis POTENTIALLY REPLACED BY draft-ietf-tcpm-3517bis
>     draft-cheng-tcpm-fastopen POTENTIALLY REPLACED BY draft-ietf-tcpm-fastopen
>     draft-gont-tcpm-rfc1948bis POTENTIALLY REPLACED BY draft-ietf-tcpm-rfc1948bis
>     draft-henderson-tcpm-rfc3782-bis POTENTIALLY REPLACED BY draft-ietf-tcpm-rfc3782-bis
>     draft-hkchu-tcpm-initcwnd POTENTIALLY REPLACED BY draft-ietf-tcpm-initcwnd
>     draft-mathis-tcpm-proportional-rate-reduction POTENTIALLY REPLACED BY draft-ietf-tcpm-proportional-rate-reduction
>     draft-touch-tcpm-experimental-options POTENTIALLY REPLACED BY draft-ietf-tcpm-experimental-options
>
> TSVWG Working Group, TSV Area
>     draft-gont-tsvwg-source-quench POTENTIALLY REPLACED BY draft-ietf-tsvwg-source-quench
>     draft-polk-tsvwg-intserv-multiple-tspec POTENTIALLY REPLACED BY draft-ietf-tsvwg-intserv-multiple-tspec
>
> -----------------------------------------------------------------
> Potential Inconsistencies
> -----------------------------------------------------------------
> draft-ietf-6lowpan-nd may replace one or more of 2 individual IDs - check this
> draft-ietf-armd-problem-statement may replace one or more of 2 individual IDs - check this
> draft-ietf-avt-rtp-gsm-hr may replace one or more of 3 individual IDs - check this
> draft-ietf-avt-rtp-svc may replace one or more of 2 individual IDs - check this
> draft-ietf-bmwg-ipflow-meth may replace one or more of 2 individual IDs - check this
> draft-ietf-cdni-use-cases may replace one or more of 2 individual IDs - check this
> draft-ietf-decade-integration-example may replace one or more of 2 individual IDs - check this
> draft-ietf-decade-survey may replace one or more of 2 individual IDs - check this
> draft-ietf-dhc-dhcpv4-bulk-leasequery may replace one or more of 2 individual IDs - check this
> draft-ietf-forces-tmlsp may replace one or more of 2 individual IDs - check this
> draft-ietf-ipfix-biflow may replace one or more of 2 individual IDs - check this
> draft-ietf-l2tpext-tdm may replace one or more of 2 individual IDs - check this
> draft-ietf-l2vpn-vpls-multihoming may replace one or more of 2 individual IDs - check this
> draft-ietf-mpls-tp-fault may replace one or more of 2 individual IDs - check this
> draft-ietf-mpls-tp-ring-protection may replace one or more of 2 individual IDs - check this
> draft-ietf-netconf-monitoring may replace one or more of 2 individual IDs - check this
> draft-ietf-netlmm-lma-discovery may replace one or more of 2 individual IDs - check this
> draft-ietf-netlmm-mip-interactions may replace one or more of 2 individual IDs - check this
> draft-ietf-pce-stateful-pce may replace one or more of 2 individual IDs - check this
> draft-ietf-sip-saml may replace one or more of 2 individual IDs - check this
> draft-ietf-sipping-service-identification may replace one or more of 2 individual IDs - check this
> draft-ietf-softwire-dslite-deployment may replace one or more of 2 individual IDs - check this
> draft-ietf-trill-rbridge-arch may replace one or more of 2 individual IDs - check this
>

From lars@netapp.com  Wed Apr 18 06:39:31 2012
Return-Path: <lars@netapp.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7328621F85B5 for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 06:39:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.749
X-Spam-Level: 
X-Spam-Status: No, score=-10.749 tagged_above=-999 required=5 tests=[AWL=-0.150, 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 rrOU-+GgVhpo for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 06:39:30 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by ietfa.amsl.com (Postfix) with ESMTP id 95EED21F85AD for <wgchairs@ietf.org>; Wed, 18 Apr 2012 06:39:27 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.75,441,1330934400";  d="p7s'?scan'208";a="641764085"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx2-out.netapp.com with ESMTP; 18 Apr 2012 06:39:12 -0700
Received: from vmwexceht03-prd.hq.netapp.com (vmwexceht03-prd.hq.netapp.com [10.106.76.241]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id q3IDdClK026194; Wed, 18 Apr 2012 06:39:12 -0700 (PDT)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.117]) by vmwexceht03-prd.hq.netapp.com ([10.106.76.241]) with mapi id 14.02.0247.003; Wed, 18 Apr 2012 06:39:11 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: Martin Vigoureux <martin.vigoureux@alcatel-lucent.com>
Subject: Re: latest missing replaced-by information
Thread-Topic: latest missing replaced-by information
Thread-Index: AQHNHUArfc1edZEOVEayFUwcFf7CfZahCloAgAABxQA=
Date: Wed, 18 Apr 2012 13:39:11 +0000
Message-ID: <5EB4938E-5550-48CD-91D1-77080C2584C4@netapp.com>
References: <E9354164-6546-42A9-BAC4-BE6660855AE9@netapp.com> <4F8EC284.3020301@alcatel-lucent.com>
In-Reply-To: <4F8EC284.3020301@alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: multipart/signed; boundary="Apple-Mail=_00EB1066-4024-4F8A-9E27-AC1F54395A64"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>, Internet Research Steering Group <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: Wed, 18 Apr 2012 13:39:31 -0000

--Apple-Mail=_00EB1066-4024-4F8A-9E27-AC1F54395A64
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Hi,

On Apr 18, 2012, at 15:32, Martin Vigoureux wrote:
> As a side question, I was wondering if managing the "replaced by" =
status shouldn't be under the full responsibility of the chairs, i.e., a =
functionality of the datatracker rather than the chairs needing to send =
an e-mail to the secretariat for each (batch of) changes.
> What do you think? and that question also goes to the chairs.

well, it *is* under the control of the chairs (and ADs), except only via =
tickets to the secretariat.

I agree that the datatracker should allow you to indicate replaced-by =
relationships, and ideally it would even nudge you occasionally about =
it. (Then I could stop sending these emails...)

Lars=

--Apple-Mail=_00EB1066-4024-4F8A-9E27-AC1F54395A64
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMQDCCBUow
ggQyoAMCAQICEFcfSRTG0jNknqb9LV9GuFkwDQYJKoZIhvcNAQEFBQAwgd0xCzAJBgNVBAYTAlVT
MRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEg
KGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24g
Q2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMzAeFw0xMTEyMTAwMDAwMDBaFw0x
MjEyMDkyMzU5NTlaMIIBDTEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9S
UEEgSW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMpOTgxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZh
bGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJRCBDbGFzcyAxIC0gTmV0c2NhcGUgRnVsbCBTZXJ2
aWNlMRQwEgYDVQQDFAtMYXJzIEVnZ2VydDEeMBwGCSqGSIb3DQEJARYPbGFyc0BuZXRhcHAuY29t
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAokrhJTcXt6J/VEpZOicLoguBlYTjXP9v
Ze4HuuhXnURUS8YouAfgaqA0zYbt5yd6fh4PBMdAaEWr5yJyHuFykXlrCumjUWSpLuqTS2A+pt4q
cZaAQk9iLDN/UVd3SpkUuvWbxXlqzG7/BSqa3VNObBzCmyh+V7aXxri+30CT//DSsNRC4VFy6sn6
dMgSaFenXLwe/FBwY0qTMfICT1PrrX6Sw1S8OfH9rykLlZXbmfkFExxQngp1DJH9xMHeODHGbCv/
ty5gdxMOrLe+vENxFEcy1YQWBZd1kNL4UObugF8A/jE/s+Oa3H1VFH8ghqZTdqGDysVxmtKHuNFx
6jIBSQIDAQABo4HSMIHPMAkGA1UdEwQCMAAwRAYDVR0gBD0wOzA5BgtghkgBhvhFAQcXATAqMCgG
CCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhMAsGA1UdDwQEAwIFoDAdBgNV
HSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwUAYDVR0fBEkwRzBFoEOgQYY/aHR0cDovL2luZGMx
ZGlnaXRhbGlkLWczLWNybC52ZXJpc2lnbi5jb20vSW5kQzFEaWdpdGFsSUQtRzMuY3JsMA0GCSqG
SIb3DQEBBQUAA4IBAQBA7q6tR92qpd7xo7VBsrOfGCWzoxIVfTc7t0RhB/Oz/+c3lnhYnNScIuKN
JmyZvznmVxqB9BJ72+NkvmdB/hnILSBTRawL2tyLo9PkBtN0nRt4gS6wjpWnD8G83hlJLE7r25jk
7HkRev61dTIXsANFpJKF02C4XSoDfEzNV6MpuEvHvcgHCqMrlwWwfKc7+NoDnE8PBuRzwSXvlD5L
mswCY2iiOsd7ImNO4OzTCxETvKTDu92+FTIbRJJpYjVNv1UF7e3w9Kq65BkZJErUH19beUeQl0Wh
2BJQE6/15rQyCnP0iJ/Nmx2/kI6M0PWunEsI6FMs0MbosreaWGHlQmomMIIG7jCCBdagAwIBAgIQ
cRVmBUrkkSFN6bxE+azT3DANBgkqhkiG9w0BAQUFADCByjELMAkGA1UEBhMCVVMxFzAVBgNVBAoT
DlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTowOAYDVQQL
EzEoYykgMTk5OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MUUwQwYD
VQQDEzxWZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9y
aXR5IC0gRzMwHhcNMDkwNTAxMDAwMDAwWhcNMTkwNDMwMjM1OTU5WjCB3TELMAkGA1UEBhMCVVMx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3Jr
MTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAo
YykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBD
bGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBDQSAtIEczMIIBIjANBgkqhkiG9w0BAQEFAAOC
AQ8AMIIBCgKCAQEA7cRH3yooHXwGa7vXITLJbBOP6bGNQU4099oL42r6ZYggCxET6ZvgSU6Lb9UB
0F8NR5GKWkx0Pj/GkQm7TDSejW6hglFi92l2WJYHr54UGAdPWr2f0jGyVBlzRmoZQhHsEnMhjfXc
MM3l2VYKMcU2bSkUl70t2olHGYjYSwQ967Y8Zx50ABMN0Ibak2f4MwOuGjxraXj2wCyO4YM/d/mZ
//6fUlrCtIcK2GypR8FUKWVDPkrAlh/Brfd3r2yxBF6+wbaULZeQLSfSux7pg2qE9sSyriMGZSal
J1grByK0b6ZiSBp38tVQJ5op05b7KPW6JHZi44xZ6/tu1ULEvkHH9QIDAQABo4ICuTCCArUwNAYI
KwYBBQUHAQEEKDAmMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC52ZXJpc2lnbi5jb20wEgYDVR0T
AQH/BAgwBgEB/wIBADBwBgNVHSAEaTBnMGUGC2CGSAGG+EUBBxcBMFYwKAYIKwYBBQUHAgEWHGh0
dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9jcHMwKgYIKwYBBQUHAgIwHhocaHR0cHM6Ly93d3cudmVy
aXNpZ24uY29tL3JwYTA0BgNVHR8ELTArMCmgJ6AlhiNodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9w
Y2ExLWczLmNybDAOBgNVHQ8BAf8EBAMCAQYwbgYIKwYBBQUHAQwEYjBgoV6gXDBaMFgwVhYJaW1h
Z2UvZ2lmMCEwHzAHBgUrDgMCGgQUS2u5KJYGDLvQUjibKaxLB4shBRgwJhYkaHR0cDovL2xvZ28u
dmVyaXNpZ24uY29tL3ZzbG9nbzEuZ2lmMC4GA1UdEQQnMCWkIzAhMR8wHQYDVQQDExZQcml2YXRl
TGFiZWw0LTIwNDgtMTE4MB0GA1UdDgQWBBR5R2EIQf04BKJL57XM9UP2SSsR+DCB8QYDVR0jBIHp
MIHmoYHQpIHNMIHKMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNV
BAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4BgNVBAsTMShjKSAxOTk5IFZlcmlTaWduLCBJ
bmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxRTBDBgNVBAMTPFZlcmlTaWduIENsYXNzIDEg
UHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgLSBHM4IRAItbdVaEVIULAM+v
OEjOsaQwDQYJKoZIhvcNAQEFBQADggEBADlNz0GZgbWpBbVSOOk5hIls5DSoWufYbAlMJBq6WaSH
O3Mh8ZOBz79oY1pn/jWFK6HDXaNKwjoZ3TDWzE3v8dKBl8pUWkO/N4t6jhmND0OojPKvYLMVirOV
nDzgnrMnmKQ1chfl/Cpdh9OKDcLRRSr4wPSsKpM61a4ScAjr+zvid+zoK2Q1ds262uDRyxTWcVib
vtU+fbbZ6CTFJGZMXZEfdrMXPn8NxiGJL7M3uKH/XLJtSd5lUkL7DojS7Uodv0vj+Mxy+kgOZY5J
yNb4mZg7t5Q+MXEGh/psWVMu198r7V9jAKwV7QO4VRaMxmgD5yKocwuxvKDaUljdCg5/wYIxggSL
MIIEhwIBATCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0
cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFs
aWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBD
QSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMAkGBSsOAwIaBQCgggJtMBgGCSqGSIb3DQEJAzELBgkq
hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEyMDQxODEzMzkxMlowIwYJKoZIhvcNAQkEMRYEFPGj
6nk08SeQXH/0imCUbpOuuIyQMIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQGEwJVUzEX
MBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
OzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhIChj
KTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlTaWduIENs
YXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEFcfSRTG0jNknqb9LV9GuFkwggEF
BgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJ
bmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1
c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29u
YSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vi
c2NyaWJlciBDQSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMA0GCSqGSIb3DQEBAQUABIIBABdEyL5l
Ji1HDmonDpZu+QXd4XbWLqHcUm/XeJj7eBCuBYeRzvO9iPd5Ym/BSP7+DBOxVerKqlhNOcoqNPR7
u2dcTMyG80vjC7+3pZthLfyI7JtjVN9+W3mABywrwCeKPw2MRYT07YOHd1cHZJ+4ToZ4H29XVt4f
OQFBuBXHPbxBxZfXZLnkwQG+YaN2807O0eg8QhEvsIJO9ZB/Tq1q8lizI0ga/Xk5G+NgBFzH8hn7
BSgpLOZ+8p9rMDtV4vtCRZVF99ci/i2+bUXNGvgx4iSTB/QQTquaKaWuC5vYZOohpFpArLW3B3zL
SaQW45kqy2EqAR1TUhzRtsRGhhy0MeAAAAAAAAA=

--Apple-Mail=_00EB1066-4024-4F8A-9E27-AC1F54395A64--

From amalis@gmail.com  Wed Apr 18 06:39:58 2012
Return-Path: <amalis@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 AAE4221F85B4 for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 06:39:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.223
X-Spam-Level: 
X-Spam-Status: No, score=-103.223 tagged_above=-999 required=5 tests=[AWL=-0.225, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y-HmLrPH5++x for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 06:39:54 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 42DDF21F85A8 for <wgchairs@ietf.org>; Wed, 18 Apr 2012 06:39:54 -0700 (PDT)
Received: by yenm5 with SMTP id m5so4168715yen.31 for <wgchairs@ietf.org>; Wed, 18 Apr 2012 06:39:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=8xjpf7SRXwUP/nrBKsxerAac2QnEnLU4sEA78aJtngk=; b=cx0m61I+dJXM16dzLIABqjk258lUDrTxS+kP9jSsWb/lSVCMNmIDIkbeKGHWuRI7S1 OqFc398a228zppHXKj3zPtytNdsn0Kt0Y2zwv/0sVP+x49JO6BZB6lNdyH1wR/obFh2Y 1fECDTi3GdoEe1sLnkPmoOZVBN6ajsoamOVGHWw9z3vMB9tK3WBYX5BGhoNqRBLajAWc w/FdWcH/9Kf/geEMMAJiW87GBOim7T8UFnGLW/x0zHicUqtYgsGS+P+EqFsBG2+FF1kq uPYFQp8mxx6o5t6Lc6nsB1LvRANGJbaxWRNcAJoyADlxiQLZI7Uoai/gOIJ4pwJLxd5W 9E9w==
Received: by 10.236.109.197 with SMTP id s45mr2228310yhg.64.1334756393639; Wed, 18 Apr 2012 06:39:53 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.236.67.41 with HTTP; Wed, 18 Apr 2012 06:39:32 -0700 (PDT)
In-Reply-To: <4F8EC284.3020301@alcatel-lucent.com>
References: <E9354164-6546-42A9-BAC4-BE6660855AE9@netapp.com> <4F8EC284.3020301@alcatel-lucent.com>
From: "Andrew G. Malis" <amalis@gmail.com>
Date: Wed, 18 Apr 2012 09:39:32 -0400
Message-ID: <CAK+d4xs1XxOhCVgW27GTNkPv37kW4+UMZ48OCH6szLhQERX3EA@mail.gmail.com>
Subject: Re: latest missing replaced-by information
To: Martin Vigoureux <martin.vigoureux@alcatel-lucent.com>
Content-Type: multipart/alternative; boundary=20cf303ea802b45d9804bdf430ed
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>, Internet Research Steering Group <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: Wed, 18 Apr 2012 13:39:58 -0000

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

+1

On Wed, Apr 18, 2012 at 9:32 AM, Martin Vigoureux <
martin.vigoureux@alcatel-lucent.com> wrote:

> Lars,
>
> thanks.
> As a side question, I was wondering if managing the "replaced by" status
> shouldn't be under the full responsibility of the chairs, i.e., a
> functionality of the datatracker rather than the chairs needing to send a=
n
> e-mail to the secretariat for each (batch of) changes.
> What do you think? and that question also goes to the chairs.
>
> -m
>
> Le 18/04/2012 10:49, Eggert, Lars a =E9crit :
>
>  Hi,
>>
>> here's yet another installment in the series of reports on potentially
>> missing "replaced-by" relationships in the IETF datatracker.
>>
>> *** NEW *** Also includes IRTF documents now.
>>
>> WG and RG chairs are encouraged to check whether these are accurate for
>> their groups, and if so, send a ticket to the secretariat instructing th=
em
>> to "record in the database that draft X replaced draft Y".
>>
>> As always, double-check before reporting to the secretariat. Also, see
>> list of possible inconsistencies at the end of the report.
>>
>> (Note that the IPR disclosure search tool uses these replaced-by
>> relationships, so keeping them up-to-date is actually useful and not jus=
t
>> WG hygiene.)
>>
>> Lars
>>
>>
>> ------------------------------**------------------------------**-----
>> APP Area
>> ------------------------------**------------------------------**-----
>> CORE Working Group, APP Area
>>    draft-rahman-core-groupcomm POTENTIALLY REPLACED BY
>> draft-ietf-core-groupcomm
>>
>> EAI Working Group, APP Area
>>    draft-duerst-eai-mailto POTENTIALLY REPLACED BY draft-ietf-eai-mailto
>>    draft-yao-eai-rfc5336bis POTENTIALLY REPLACED BY
>> draft-ietf-eai-rfc5336bis
>>
>> PAWS Working Group, APP Area
>>    draft-probasco-paws-problem-**stmt-usecases-rqmts POTENTIALLY
>> REPLACED BY draft-ietf-paws-problem-stmt-**usecases-rqmts
>>
>> VCARDDAV Working Group, APP Area
>>    draft-cauchie-vcarddav-oma-**cab-extensions POTENTIALLY REPLACED BY
>> draft-ietf-vcarddav-oma-cab-**extensions
>>
>> ------------------------------**------------------------------**-----
>> CONCLUDED Area
>> ------------------------------**------------------------------**-----
>> ATOMPUB Working Group, CONCLUDED Area
>>    draft-snell-atompub-**autodiscovery POTENTIALLY REPLACED BY
>> draft-ietf-atompub-**autodiscovery
>>
>> HTTP Working Group, CONCLUDED Area
>>    draft-wallis-http-digest-auth-**a3a8 POTENTIALLY REPLACED BY
>> draft-ietf-http-digest-auth-**a3a8
>>
>> IDNABIS Working Group, CONCLUDED Area
>>    draft-faltstrom-idnabis-tables POTENTIALLY REPLACED BY
>> draft-ietf-idnabis-tables
>>
>> IMAP Working Group, CONCLUDED Area
>>    draft-crispin-imap-compat POTENTIALLY REPLACED BY
>> draft-ietf-imap-compat
>>
>> TFTPEXTS Working Group, CONCLUDED Area
>>    draft-malkin-tftpexts-blksize-**opt POTENTIALLY REPLACED BY
>> draft-ietf-tftpexts-blksize-**opt
>>    draft-malkin-tftpexts-option-**ext POTENTIALLY REPLACED BY
>> draft-ietf-tftpexts-option-ext
>>    draft-malkin-tftpexts-options POTENTIALLY REPLACED BY
>> draft-ietf-tftpexts-options
>>
>> XMPP Working Group, CONCLUDED Area
>>    draft-barnes-xmpp-dna POTENTIALLY REPLACED BY draft-ietf-xmpp-dna
>>    draft-miller-xmpp-e2e POTENTIALLY REPLACED BY draft-ietf-xmpp-e2e
>>    draft-saintandre-xmpp-6122bis POTENTIALLY REPLACED BY
>> draft-ietf-xmpp-6122bis
>>
>> MIPSHOP Working Group, CONCLUDED Area
>>    draft-xia-mipshop-fmip-ptp POTENTIALLY REPLACED BY
>> draft-ietf-mipshop-fmip-ptp
>>
>> NETLMM Working Group, CONCLUDED Area
>>    draft-cui-netlmm-mip-**interactions POTENTIALLY REPLACED BY
>> draft-ietf-netlmm-mip-**interactions
>>    draft-glenn-netlmm-pmipv6-mib POTENTIALLY REPLACED BY
>> draft-ietf-netlmm-pmipv6-mib
>>    draft-korhonen-netlmm-lma-**discovery POTENTIALLY REPLACED BY
>> draft-ietf-netlmm-lma-**discovery
>>    draft-xia-netlmm-lma-discovery POTENTIALLY REPLACED BY
>> draft-ietf-netlmm-lma-**discovery
>>
>> SEND Working Group, CONCLUDED Area
>>    draft-arkko-send-cga POTENTIALLY REPLACED BY draft-ietf-send-cga
>>    draft-arkko-send-ndopt POTENTIALLY REPLACED BY draft-ietf-send-ndopt
>>
>> SHIM6 Working Group, CONCLUDED Area
>>    draft-garcia-shim6-**applicability POTENTIALLY REPLACED BY
>> draft-ietf-shim6-applicability
>>
>> CAPWAP Working Group, CONCLUDED Area
>>    draft-yangshi-capwap-802dot11-**mib POTENTIALLY REPLACED BY
>> draft-ietf-capwap-802dot11-mib
>>    draft-yangshi-capwap-base-mib POTENTIALLY REPLACED BY
>> draft-ietf-capwap-base-mib
>>
>> RMONMIB Working Group, CONCLUDED Area
>>    draft-bierman-rmonmib-hc-**alarm-mib POTENTIALLY REPLACED BY
>> draft-ietf-rmonmib-hc-alarm-**mib
>>
>> MEGACO Working Group, CONCLUDED Area
>>    draft-blatherwick-megaco-**ipphone POTENTIALLY REPLACED BY
>> draft-ietf-megaco-ipphone
>>
>> SIGTRAN Working Group, CONCLUDED Area
>>    draft-anil-sigtran-dua POTENTIALLY REPLACED BY draft-ietf-sigtran-dua
>>
>> SIP Working Group, CONCLUDED Area
>>    draft-arkko-sip-sec-agree POTENTIALLY REPLACED BY
>> draft-ietf-sip-sec-agree
>>    draft-biggs-sip-replaces POTENTIALLY REPLACED BY
>> draft-ietf-sip-replaces
>>    draft-pashalidis-sip-saml POTENTIALLY REPLACED BY draft-ietf-sip-saml
>>
>> SIPPING Working Group, CONCLUDED Area
>>    draft-drage-sipping-service-**identification POTENTIALLY REPLACED BY
>> draft-ietf-sipping-service-**identification
>>    draft-elwell-sipping-update-**pai POTENTIALLY REPLACED BY
>> draft-ietf-sipping-update-pai
>>    draft-hilt-sipping-overload-**design POTENTIALLY REPLACED BY
>> draft-ietf-sipping-overload-**design
>>    draft-petrie-sipping-profile-**datasets POTENTIALLY REPLACED BY
>> draft-ietf-sipping-profile-**datasets
>>    draft-rosenberg-sipping-**service-identification POTENTIALLY REPLACED
>> BY draft-ietf-sipping-service-**identification
>>    draft-zhang-sipping-overlap POTENTIALLY REPLACED BY
>> draft-ietf-sipping-overlap
>>
>> SPEERMINT Working Group, CONCLUDED Area
>>    draft-meyer-speermint-reqs-**and-terminology POTENTIALLY REPLACED BY
>> draft-ietf-speermint-reqs-and-**terminology
>>    draft-niccolini-speermint-**voipthreats POTENTIALLY REPLACED BY
>> draft-ietf-speermint-**voipthreats
>>
>> XCON Working Group, CONCLUDED Area
>>    draft-barnes-xcon-ccmp POTENTIALLY REPLACED BY draft-ietf-xcon-ccmp
>>    draft-barnes-xcon-examples POTENTIALLY REPLACED BY
>> draft-ietf-xcon-examples
>>
>> DKIM Working Group, CONCLUDED Area
>>    draft-lindsey-dkim-**mailinglists POTENTIALLY REPLACED BY
>> draft-ietf-dkim-mailinglists
>>
>> SACRED Working Group, CONCLUDED Area
>>    draft-arsenault-sacred-reqs POTENTIALLY REPLACED BY
>> draft-ietf-sacred-reqs
>>
>> SASL Working Group, CONCLUDED Area
>>    draft-zeilenga-sasl-crammd5 POTENTIALLY REPLACED BY
>> draft-ietf-sasl-crammd5
>>    draft-zeilenga-sasl-rfc2222bis POTENTIALLY REPLACED BY
>> draft-ietf-sasl-rfc2222bis
>>
>> SMIME Working Group, CONCLUDED Area
>>    draft-dusse-smime-cert POTENTIALLY REPLACED BY draft-ietf-smime-cert
>>    draft-dusse-smime-msg POTENTIALLY REPLACED BY draft-ietf-smime-msg
>>
>> DIFFSERV Working Group, CONCLUDED Area
>>    draft-baker-diffserv-mib POTENTIALLY REPLACED BY
>> draft-ietf-diffserv-mib
>>    draft-black-diffserv-tunnels POTENTIALLY REPLACED BY
>> draft-ietf-diffserv-tunnels
>>
>> RSVP Working Group, CONCLUDED Area
>>    draft-berger-rsvp-refresh-**reduct POTENTIALLY REPLACED BY
>> draft-ietf-rsvp-refresh-reduct
>>
>> ------------------------------**------------------------------**-----
>> INT Area
>> ------------------------------**------------------------------**-----
>> 6MAN Working Group, INT Area
>>    draft-carpenter-6man-uri-**zoneid POTENTIALLY REPLACED BY
>> draft-ietf-6man-uri-zoneid
>>    draft-costa-6man-dad-proxy POTENTIALLY REPLACED BY
>> draft-ietf-6man-dad-proxy
>>    draft-fujisaki-6man-addr-**select-opt POTENTIALLY REPLACED BY
>> draft-ietf-6man-addr-select-**opt
>>    draft-george-6man-3627-**historic POTENTIALLY REPLACED BY
>> draft-ietf-6man-3627-historic
>>    draft-gont-6man-ipv6-atomic-**fragments POTENTIALLY REPLACED BY
>> draft-ietf-6man-ipv6-atomic-**fragments
>>    draft-hsingh-6man-enhanced-dad POTENTIALLY REPLACED BY
>> draft-ietf-6man-enhanced-dad
>>    draft-joshi-6man-neighbor-**inform POTENTIALLY REPLACED BY
>> draft-ietf-6man-neighbor-**inform
>>    draft-lynn-6man-6lobac POTENTIALLY REPLACED BY draft-ietf-6man-6lobac
>>    draft-nordmark-6man-impatient-**nud POTENTIALLY REPLACED BY
>> draft-ietf-6man-impatient-nud
>>
>> ANCP Working Group, INT Area
>>    draft-lefaucheur-ancp-mc-**extensions POTENTIALLY REPLACED BY
>> draft-ietf-ancp-mc-extensions
>>
>> CSI Working Group, INT Area
>>    draft-jiang-csi-dhcpv6-cga-ps POTENTIALLY REPLACED BY
>> draft-ietf-csi-dhcpv6-cga-ps
>>    draft-rgaglian-csi-send-name-**type-registry POTENTIALLY REPLACED BY
>> draft-ietf-csi-send-name-type-**registry
>>
>> DHC Working Group, INT Area
>>    draft-jiang-dhc-cga-config-**dhcpv6 POTENTIALLY REPLACED BY
>> draft-ietf-dhc-cga-config-**dhcpv6
>>    draft-jjmb-dhc-dhcpv6-**redundancy-consider POTENTIALLY REPLACED BY
>> draft-ietf-dhc-dhcpv6-**redundancy-consider
>>    draft-miles-dhc-dhcpv6-ldra POTENTIALLY REPLACED BY
>> draft-ietf-dhc-dhcpv6-ldra
>>    draft-mrugalski-dhc-dhcpv6-**failover-requirements POTENTIALLY
>> REPLACED BY draft-ietf-dhc-dhcpv6-**failover-requirements
>>    draft-xia-dhc-host-gen-id POTENTIALLY REPLACED BY
>> draft-ietf-dhc-host-gen-id
>>
>> DNSEXT Working Group, INT Area
>>    draft-wang-dnsext-newzone-**notify POTENTIALLY REPLACED BY
>> draft-ietf-dnsext-newzone-**notify
>>
>> HIP Working Group, INT Area
>>    draft-camarillo-hip-via POTENTIALLY REPLACED BY draft-ietf-hip-via
>>    draft-henderson-hip-rfc5206-**bis POTENTIALLY REPLACED BY
>> draft-ietf-hip-rfc5206-bis
>>    draft-jokela-hip-rfc5202-bis POTENTIALLY REPLACED BY
>> draft-ietf-hip-rfc5202-bis
>>    draft-keranen-hip-native-nat-**traversal POTENTIALLY REPLACED BY
>> draft-ietf-hip-native-nat-**traversal
>>    draft-keranen-hip-over-hip POTENTIALLY REPLACED BY
>> draft-ietf-hip-over-hip
>>    draft-keranen-hip-reload-**instance POTENTIALLY REPLACED BY
>> draft-ietf-hip-reload-instance
>>    draft-moskowitz-hip-rfc4423-**bis POTENTIALLY REPLACED BY
>> draft-ietf-hip-rfc4423-bis
>>    draft-moskowitz-hip-rfc5201-**bis POTENTIALLY REPLACED BY
>> draft-ietf-hip-rfc5201-bis
>>    draft-nikander-hip-hiccups POTENTIALLY REPLACED BY
>> draft-ietf-hip-hiccups
>>
>> INTAREA Working Group, INT Area
>>    draft-boucadair-intarea-nat-**reveal-analysis POTENTIALLY REPLACED BY
>> draft-ietf-intarea-nat-reveal-**analysis
>>
>> LISP Working Group, INT Area
>>    draft-jakab-lisp-deployment POTENTIALLY REPLACED BY
>> draft-ietf-lisp-deployment
>>    draft-maino-lisp-sec POTENTIALLY REPLACED BY draft-ietf-lisp-sec
>>    draft-meyer-lisp-eid-block POTENTIALLY REPLACED BY
>> draft-ietf-lisp-eid-block
>>
>> MIF Working Group, INT Area
>>    draft-liu-mif-api-extension POTENTIALLY REPLACED BY
>> draft-ietf-mif-api-extension
>>
>> MULTIMOB Working Group, INT Area
>>    draft-schmidt-multimob-pmipv6-**source POTENTIALLY REPLACED BY
>> draft-ietf-multimob-pmipv6-**source
>>    draft-wu-multimob-igmp-mld-**tuning POTENTIALLY REPLACED BY
>> draft-ietf-multimob-igmp-mld-**tuning
>>    draft-zuniga-multimob-pmipv6-**ropt POTENTIALLY REPLACED BY
>> draft-ietf-multimob-pmipv6-**ropt
>>
>> NETEXT Working Group, INT Area
>>    draft-bernardos-netext-pmipv6-**flowmob POTENTIALLY REPLACED BY
>> draft-ietf-netext-pmipv6-**flowmob
>>    draft-korhonen-netext-redirect POTENTIALLY REPLACED BY
>> draft-ietf-netext-redirect
>>    draft-krishnan-netext-pmip-lr POTENTIALLY REPLACED BY
>> draft-ietf-netext-pmip-lr
>>    draft-melia-netext-logical-**interface-support POTENTIALLY REPLACED
>> BY draft-ietf-netext-logical-**interface-support
>>    draft-zhou-netext-pd-pmip POTENTIALLY REPLACED BY
>> draft-ietf-netext-pd-pmip
>>
>> PCP Working Group, INT Area
>>    draft-bpw-pcp-dhcp POTENTIALLY REPLACED BY draft-ietf-pcp-dhcp
>>    draft-bpw-pcp-upnp-igd-**interworking POTENTIALLY REPLACED BY
>> draft-ietf-pcp-upnp-igd-**interworking
>>
>> SAVI Working Group, INT Area
>>    draft-bi-savi-mix POTENTIALLY REPLACED BY draft-ietf-savi-mix
>>
>> SOFTWIRE Working Group, INT Area
>>    draft-guo-softwire-6rd-radius-**attrib POTENTIALLY REPLACED BY
>> draft-ietf-softwire-6rd-**radius-attrib
>>    draft-ieft-softwire-dslite-**deployment POTENTIALLY REPLACED BY
>> draft-ietf-softwire-dslite-**deployment
>>    draft-lee-softwire-dslite-**deployment POTENTIALLY REPLACED BY
>> draft-ietf-softwire-dslite-**deployment
>>    draft-maglione-softwire-**dslite-radius-ext POTENTIALLY REPLACED BY
>> draft-ietf-softwire-dslite-**radius-ext
>>    draft-qin-softwire-multicast-**prefix-option POTENTIALLY REPLACED BY
>> draft-ietf-softwire-multicast-**prefix-option
>>    draft-xu-softwire-mesh-**multicast POTENTIALLY REPLACED BY
>> draft-ietf-softwire-mesh-**multicast
>>
>> TICTOC Working Group, INT Area
>>    draft-davari-tictoc-**1588overmpls POTENTIALLY REPLACED BY
>> draft-ietf-tictoc-1588overmpls
>>    draft-mizrahi-tictoc-security-**requirements POTENTIALLY REPLACED BY
>> draft-ietf-tictoc-security-**requirements
>>    draft-vinay-tictoc-ptp-mib POTENTIALLY REPLACED BY
>> draft-ietf-tictoc-ptp-mib
>>
>> TRILL Working Group, INT Area
>>    draft-tissa-trill-cmt POTENTIALLY REPLACED BY draft-ietf-trill-cmt
>>
>> ------------------------------**------------------------------**-----
>> IRTF Area
>> ------------------------------**------------------------------**-----
>> DTNRG Working Group, IRTF Area
>>    draft-lindgren-dtnrg-prophet POTENTIALLY REPLACED BY
>> draft-irtf-dtnrg-prophet
>>    draft-symington-dtnrg-bundle-**metadata-block POTENTIALLY REPLACED BY
>> draft-irtf-dtnrg-bundle-**metadata-block
>>    draft-symington-dtnrg-bundle-**retrans-block POTENTIALLY REPLACED BY
>> draft-irtf-dtnrg-bundle-**retrans-block
>>
>> HIPRG Working Group, IRTF Area
>>    draft-ahrenholz-hiprg-dht POTENTIALLY REPLACED BY draft-irtf-hiprg-dh=
t
>>
>> MOBOPTS Working Group, IRTF Area
>>    draft-koki-mobopts-l2-**abstractions POTENTIALLY REPLACED BY
>> draft-irtf-mobopts-l2-**abstractions
>>    draft-ohba-mobopts-mpa-**framework POTENTIALLY REPLACED BY
>> draft-irtf-mobopts-mpa-**framework
>>    draft-schmidt-mobopts-**mmcastv6-ps POTENTIALLY REPLACED BY
>> draft-irtf-mobopts-mmcastv6-ps
>>    draft-weniger-mobopts-mip6-**cnlocpriv POTENTIALLY REPLACED BY
>> draft-irtf-mobopts-mip6-**cnlocpriv
>>
>> P2PRG Working Group, IRTF Area
>>    draft-gurbani-p2prg-**simulation-survey POTENTIALLY REPLACED BY
>> draft-irtf-p2prg-simulation-**survey
>>
>> ------------------------------**------------------------------**-----
>> IRTF-CONCLUDED Area
>> ------------------------------**------------------------------**-----
>> ------------------------------**------------------------------**-----
>> OPS Area
>> ------------------------------**------------------------------**-----
>> ARMD Working Group, OPS Area
>>    draft-dunbar-armd-problem-**statement POTENTIALLY REPLACED BY
>> draft-ietf-armd-problem-**statement
>>
>> BMWG Working Group, OPS Area
>>    draft-janovak-bmwg-ipflow-meth POTENTIALLY REPLACED BY
>> draft-ietf-bmwg-ipflow-meth
>>    draft-morton-bmwg-imix-genome POTENTIALLY REPLACED BY
>> draft-ietf-bmwg-imix-genome
>>
>> DIME Working Group, OPS Area
>>    draft-zorn-dime-rfc4005bis POTENTIALLY REPLACED BY
>> draft-ietf-dime-rfc4005bis
>>
>> EMAN Working Group, OPS Area
>>    draft-tychon-eman-**applicability-statement POTENTIALLY REPLACED BY
>> draft-ietf-eman-applicability-**statement
>>
>> GROW Working Group, OPS Area
>>    draft-dimitri-grow-rss POTENTIALLY REPLACED BY draft-ietf-grow-rss
>>    draft-manderson-grow-geomrt POTENTIALLY REPLACED BY
>> draft-ietf-grow-geomrt
>>
>> IPFIX Working Group, OPS Area
>>    draft-boschi-ipfix-anon POTENTIALLY REPLACED BY draft-ietf-ipfix-anon
>>    draft-boschi-ipfix-exporting-**type POTENTIALLY REPLACED BY
>> draft-ietf-ipfix-exporting-**type
>>    draft-claise-ipfix-export-per-**sctp-stream POTENTIALLY REPLACED BY
>> draft-ietf-ipfix-export-per-**sctp-stream
>>    draft-claise-ipfix-protocol-**rfc5101bis POTENTIALLY REPLACED BY
>> draft-ietf-ipfix-protocol-**rfc5101bis
>>    draft-dkcm-ipfix-rfc5815bis POTENTIALLY REPLACED BY
>> draft-ietf-ipfix-rfc5815bis
>>    draft-gupta-ipfix-reliability-**template-ext POTENTIALLY REPLACED BY
>> draft-ietf-ipfix-reliability-**template-ext
>>    draft-trammell-ipfix-file POTENTIALLY REPLACED BY draft-ietf-ipfix-fi=
le
>>
>> MBONED Working Group, OPS Area
>>    draft-asaeda-mboned-mtrace-v2 POTENTIALLY REPLACED BY
>> draft-ietf-mboned-mtrace-v2
>>    draft-asaeda-mboned-session-**announcement-req POTENTIALLY REPLACED
>> BY draft-ietf-mboned-session-**announcement-req
>>    draft-bipi-mboned-ip-**multicast-pm-requirement POTENTIALLY REPLACED
>> BY draft-ietf-mboned-ip-**multicast-pm-requirement
>>    draft-venaas-mboned-mcaddrdoc POTENTIALLY REPLACED BY
>> draft-ietf-mboned-mcaddrdoc
>>    draft-venaas-mboned-ssmping POTENTIALLY REPLACED BY
>> draft-ietf-mboned-ssmping
>>
>> NETCONF Working Group, OPS Area
>>    draft-bierman-netconf-access-**control POTENTIALLY REPLACED BY
>> draft-ietf-netconf-access-**control
>>    draft-bierman-netconf-with-**defaults POTENTIALLY REPLACED BY
>> draft-ietf-netconf-with-**defaults
>>    draft-chisholm-netconf-**monitoring POTENTIALLY REPLACED BY
>> draft-ietf-netconf-monitoring
>>
>> NETMOD Working Group, OPS Area
>>    draft-bierman-netmod-system-**mgmt POTENTIALLY REPLACED BY
>> draft-ietf-netmod-system-mgmt
>>    draft-bjorklund-netmod-**interfaces-cfg POTENTIALLY REPLACED BY
>> draft-ietf-netmod-interfaces-**cfg
>>    draft-bjorklund-netmod-ip-cfg POTENTIALLY REPLACED BY
>> draft-ietf-netmod-ip-cfg
>>    draft-lhotka-netmod-routing-**cfg POTENTIALLY REPLACED BY
>> draft-ietf-netmod-routing-cfg
>>    draft-schoenw-netmod-smi-yang POTENTIALLY REPLACED BY
>> draft-ietf-netmod-smi-yang
>>
>> OPSAWG Working Group, OPS Area
>>    draft-mizrahi-opsawg-oam-**overview POTENTIALLY REPLACED BY
>> draft-ietf-opsawg-oam-overview
>>
>> OPSEC Working Group, OPS Area
>>    draft-gont-opsec-icmp-**filtering POTENTIALLY REPLACED BY
>> draft-ietf-opsec-icmp-**filtering
>>    draft-gont-opsec-ip-security POTENTIALLY REPLACED BY
>> draft-ietf-opsec-ip-security
>>
>> RADEXT Working Group, OPS Area
>>    draft-dekok-radext-dtls POTENTIALLY REPLACED BY draft-ietf-radext-dtl=
s
>>    draft-dekok-radext-radius-**extensions POTENTIALLY REPLACED BY
>> draft-ietf-radext-radius-**extensions
>>    draft-dekok-radext-tcp-**transport POTENTIALLY REPLACED BY
>> draft-ietf-radext-tcp-**transport
>>    draft-lourdelet-radext-ipv6-**access POTENTIALLY REPLACED BY
>> draft-ietf-radext-ipv6-access
>>    draft-nelson-radext-crypto-**agility-requirements POTENTIALLY
>> REPLACED BY draft-ietf-radext-crypto-**agility-requirements
>>    draft-tiwari-radext-tunnel-**type POTENTIALLY REPLACED BY
>> draft-ietf-radext-tunnel-type
>>
>> V6OPS Working Group, OPS Area
>>    draft-hilliard-v6ops-ipv6-**discard-prefix POTENTIALLY REPLACED BY
>> draft-ietf-v6ops-ipv6-discard-**prefix
>>    draft-rgaglian-v6ops-v6inixp POTENTIALLY REPLACED BY
>> draft-ietf-v6ops-v6inixp
>>    draft-vandevelde-v6ops-ra-**guard POTENTIALLY REPLACED BY
>> draft-ietf-v6ops-ra-guard
>>    draft-wbeebee-v6ops-ipv6-cpe-**router-bis POTENTIALLY REPLACED BY
>> draft-ietf-v6ops-ipv6-cpe-**router-bis
>>
>> ------------------------------**------------------------------**-----
>> RAI Area
>> ------------------------------**------------------------------**-----
>> ATOCA Working Group, RAI Area
>>    draft-rosen-atoca-cap POTENTIALLY REPLACED BY draft-ietf-atoca-cap
>>
>> BLISS Working Group, RAI Area
>>    draft-elwell-bliss-ach-**analysis POTENTIALLY REPLACED BY
>> draft-ietf-bliss-ach-analysis
>>    draft-poetzl-bliss-call-**completion POTENTIALLY REPLACED BY
>> draft-ietf-bliss-call-**completion
>>    draft-procter-bliss-call-park-**extension POTENTIALLY REPLACED BY
>> draft-ietf-bliss-call-park-**extension
>>    draft-rosenberg-bliss-problem-**statement POTENTIALLY REPLACED BY
>> draft-ietf-bliss-problem-**statement
>>
>> CLUE Working Group, RAI Area
>>    draft-romanow-clue-framework POTENTIALLY REPLACED BY
>> draft-ietf-clue-framework
>>    draft-romanow-clue-**telepresence-requirements POTENTIALLY REPLACED
>> BY draft-ietf-clue-telepresence-**requirements
>>    draft-romanow-clue-**telepresence-use-cases POTENTIALLY REPLACED BY
>> draft-ietf-clue-telepresence-**use-cases
>>
>> CODEC Working Group, RAI Area
>>    draft-valin-codec-guidelines POTENTIALLY REPLACED BY
>> draft-ietf-codec-guidelines
>>    draft-valin-codec-results POTENTIALLY REPLACED BY
>> draft-ietf-codec-results
>>
>> DRINKS Working Group, RAI Area
>>    draft-channabasappa-drinks-**usecases-requirements POTENTIALLY
>> REPLACED BY draft-ietf-drinks-usecases-**requirements
>>
>> GEOPRIV Working Group, RAI Area
>>    draft-barnes-geopriv-policy-**uri POTENTIALLY REPLACED BY
>> draft-ietf-geopriv-policy-uri
>>    draft-mayrhofer-geopriv-geo-**uri POTENTIALLY REPLACED BY
>> draft-ietf-geopriv-geo-uri
>>    draft-winterbottom-geopriv-**local-civic POTENTIALLY REPLACED BY
>> draft-ietf-geopriv-local-civic
>>
>> MMUSIC Working Group, RAI Area
>>    draft-garcia-mmusic-sdp-**miscellaneous-caps POTENTIALLY REPLACED BY
>> draft-ietf-mmusic-sdp-**miscellaneous-caps
>>    draft-greevenbosch-mmusic-**parallax-attribute POTENTIALLY REPLACED
>> BY draft-ietf-mmusic-parallax-**attribute
>>    draft-greevenbosch-mmusic-**signal-3d-format POTENTIALLY REPLACED BY
>> draft-ietf-mmusic-signal-3d-**format
>>    draft-holmberg-mmusic-sdp-**bundle-negotiation POTENTIALLY REPLACED
>> BY draft-ietf-mmusic-sdp-bundle-**negotiation
>>    draft-loreto-mmusic-sctp-sdp POTENTIALLY REPLACED BY
>> draft-ietf-mmusic-sctp-sdp
>>    draft-polk-mmusic-traffic-**class-for-sdp POTENTIALLY REPLACED BY
>> draft-ietf-mmusic-traffic-**class-for-sdp
>>
>> P2PSIP Working Group, RAI Area
>>    draft-bryan-p2psip-reload POTENTIALLY REPLACED BY
>> draft-ietf-p2psip-reload
>>    draft-zong-p2psip-drr POTENTIALLY REPLACED BY draft-ietf-p2psip-drr
>>    draft-zong-p2psip-rpr POTENTIALLY REPLACED BY draft-ietf-p2psip-rpr
>>
>> PAYLOAD Working Group, RAI Area
>>    draft-westin-payload-vp8 POTENTIALLY REPLACED BY draft-ietf-payload-v=
p8
>>
>> RTCWEB Working Group, RAI Area
>>    draft-uberti-rtcweb-jsep POTENTIALLY REPLACED BY draft-ietf-rtcweb-js=
ep
>>
>> SIPCORE Working Group, RAI Area
>>    draft-holmberg-sipcore-proxy-**feature POTENTIALLY REPLACED BY
>> draft-ietf-sipcore-proxy-**feature
>>
>> SOC Working Group, RAI Area
>>    draft-noel-soc-overload-rate-**control POTENTIALLY REPLACED BY
>> draft-ietf-soc-overload-rate-**control
>>    draft-shen-soc-load-control-**event-package POTENTIALLY REPLACED BY
>> draft-ietf-soc-load-control-**event-package
>>
>> XMPP Working Group, RAI Area
>>    draft-barnes-xmpp-dna POTENTIALLY REPLACED BY draft-ietf-xmpp-dna
>>    draft-miller-xmpp-e2e POTENTIALLY REPLACED BY draft-ietf-xmpp-e2e
>>    draft-saintandre-xmpp-6122bis POTENTIALLY REPLACED BY
>> draft-ietf-xmpp-6122bis
>>
>> XRBLOCK Working Group, RAI Area
>>    draft-clark-xrblock-rtcp-xr-**qoe POTENTIALLY REPLACED BY
>> draft-ietf-xrblock-rtcp-xr-qoe
>>
>> ------------------------------**------------------------------**-----
>> RTG Area
>> ------------------------------**------------------------------**-----
>> BFD Working Group, RTG Area
>>    draft-bhatia-bfd-hmac-sha POTENTIALLY REPLACED BY
>> draft-ietf-bfd-hmac-sha
>>
>> CCAMP Working Group, RTG Area
>>    draft-bccg-ccamp-otn-g709-**info-model POTENTIALLY REPLACED BY
>> draft-ietf-ccamp-otn-g709-**info-model
>>    draft-berger-ccamp-assoc-info POTENTIALLY REPLACED BY
>> draft-ietf-ccamp-assoc-info
>>    draft-bernstein-ccamp-wson-**signaling POTENTIALLY REPLACED BY
>> draft-ietf-ccamp-wson-**signaling
>>
>> FORCES Working Group, RTG Area
>>    draft-hadi-forces-sctptml POTENTIALLY REPLACED BY
>> draft-ietf-forces-sctptml
>>    draft-haleplidis-forces-**implementation-experience POTENTIALLY
>> REPLACED BY draft-ietf-forces-**implementation-experience
>>
>> IDR Working Group, RTG Area
>>    draft-decraene-idr-reserved-**extended-communities POTENTIALLY
>> REPLACED BY draft-ietf-idr-reserved-**extended-communities
>>    draft-keyupate-idr-bgp-gr-**notification POTENTIALLY REPLACED BY
>> draft-ietf-idr-bgp-gr-**notification
>>    draft-keyur-idr-enhanced-gr POTENTIALLY REPLACED BY
>> draft-ietf-idr-enhanced-gr
>>    draft-raszuk-idr-flow-spec-v6 POTENTIALLY REPLACED BY
>> draft-ietf-idr-flow-spec-v6
>>    draft-wkumari-idr-as0 POTENTIALLY REPLACED BY draft-ietf-idr-as0
>>
>> ISIS Working Group, RTG Area
>>    draft-chopps-isis-bfd-tlv POTENTIALLY REPLACED BY
>> draft-ietf-isis-bfd-tlv
>>    draft-ginsberg-isis-genapp POTENTIALLY REPLACED BY
>> draft-ietf-isis-genapp
>>    draft-previdi-isis-mi POTENTIALLY REPLACED BY draft-ietf-isis-mi
>>    draft-shen-isis-oper-enhance POTENTIALLY REPLACED BY
>> draft-ietf-isis-oper-enhance
>>
>> L2VPN Working Group, RTG Area
>>    draft-delord-l2vpn-ldp-vpls-**broadcast-exten POTENTIALLY REPLACED BY
>> draft-ietf-l2vpn-ldp-vpls-**broadcast-exten
>>    draft-henderickx-l2vpn-vpls-**multihoming POTENTIALLY REPLACED BY
>> draft-ietf-l2vpn-vpls-**multihoming
>>    draft-key-l2vpn-etree-frwk POTENTIALLY REPLACED BY
>> draft-ietf-l2vpn-etree-frwk
>>    draft-kompella-l2vpn-vpls-**multihoming POTENTIALLY REPLACED BY
>> draft-ietf-l2vpn-vpls-**multihoming
>>    draft-pdutta-l2vpn-vpls-ldp-**mac-opt POTENTIALLY REPLACED BY
>> draft-ietf-l2vpn-vpls-ldp-mac-**opt
>>    draft-pkwok-l2vpn-vpls-**macflush-ld POTENTIALLY REPLACED BY
>> draft-ietf-l2vpn-vpls-**macflush-ld
>>    draft-sajassi-l2vpn-pbb-evpn POTENTIALLY REPLACED BY
>> draft-ietf-l2vpn-pbb-evpn
>>    draft-sajassi-l2vpn-vpls-pbb-**interop POTENTIALLY REPLACED BY
>> draft-ietf-l2vpn-vpls-pbb-**interop
>>
>> L3VPN Working Group, RTG Area
>>    draft-rekhter-l3vpn-virtual-**hub POTENTIALLY REPLACED BY
>> draft-ietf-l3vpn-virtual-hub
>>
>> MANET Working Group, RTG Area
>>    draft-herberg-manet-nhdp-sec POTENTIALLY REPLACED BY
>> draft-ietf-manet-nhdp-sec
>>    draft-herberg-manet-nhdp-sec-**threats POTENTIALLY REPLACED BY
>> draft-ietf-manet-nhdp-sec-**threats
>>
>> MPLS Working Group, RTG Area
>>    draft-frost-mpls-tp-loss-**delay-profile POTENTIALLY REPLACED BY
>> draft-ietf-mpls-tp-loss-delay-**profile
>>    draft-koike-mpls-tp-temporal-**hitless-psm POTENTIALLY REPLACED BY
>> draft-ietf-mpls-tp-temporal-**hitless-psm
>>    draft-liu-mpls-tp-ring-**protection POTENTIALLY REPLACED BY
>> draft-ietf-mpls-tp-ring-**protection
>>    draft-raggarwa-mpls-seamless-**mcast POTENTIALLY REPLACED BY
>> draft-ietf-mpls-seamless-mcast
>>
>> OSPF Working Group, RTG Area
>>    draft-acee-ospf-multi-instance POTENTIALLY REPLACED BY
>> draft-ietf-ospf-multi-instance
>>    draft-acee-ospf-transport-**instance POTENTIALLY REPLACED BY
>> draft-ietf-ospf-transport-**instance
>>    draft-cheng-ospf-ipv4-**embedded-ipv6-routing POTENTIALLY REPLACED BY
>> draft-ietf-ospf-ipv4-embedded-**ipv6-routing
>>    draft-nguyen-ospf-lls POTENTIALLY REPLACED BY draft-ietf-ospf-lls
>>    draft-nsheth-ospf-hybrid-**bcast-and-p2mp POTENTIALLY REPLACED BY
>> draft-ietf-ospf-hybrid-bcast-**and-p2mp
>>    draft-ogier-ospf-dbex-opt POTENTIALLY REPLACED BY
>> draft-ietf-ospf-dbex-opt
>>    draft-retana-ospf-rfc3137bis POTENTIALLY REPLACED BY
>> draft-ietf-ospf-rfc3137bis
>>    draft-venkata-ospf-dynamic-**hostname POTENTIALLY REPLACED BY
>> draft-ietf-ospf-dynamic-**hostname
>>
>> PCE Working Group, RTG Area
>>    draft-tang-pce-stateful-pce POTENTIALLY REPLACED BY
>> draft-ietf-pce-stateful-pce
>>    draft-zhao-pce-pcep-inter-**domain-p2mp-procedures POTENTIALLY
>> REPLACED BY draft-ietf-pce-pcep-inter-**domain-p2mp-procedures
>>
>> PIM Working Group, RTG Area
>>    draft-hou-pim-drlb POTENTIALLY REPLACED BY draft-ietf-pim-drlb
>>
>> PWE3 Working Group, RTG Area
>>    draft-bryant-pwe3-packet-pw POTENTIALLY REPLACED BY
>> draft-ietf-pwe3-packet-pw
>>    draft-delregno-pwe3-pw-vccv-**impl-survey-results POTENTIALLY
>> REPLACED BY draft-ietf-pwe3-pw-vccv-impl-**survey-results
>>    draft-jin-pwe3-cbit-**negotiation POTENTIALLY REPLACED BY
>> draft-ietf-pwe3-cbit-**negotiation
>>    draft-raza-pwe3-pw-typed-wc-**fec POTENTIALLY REPLACED BY
>> draft-ietf-pwe3-pw-typed-wc-**fec
>>
>> ROLL Working Group, RTG Area
>>    draft-dt-roll-p2p-rpl POTENTIALLY REPLACED BY draft-ietf-roll-p2p-rpl
>>    draft-gnawali-roll-minrank-**hysteresis-of POTENTIALLY REPLACED BY
>> draft-ietf-roll-minrank-**hysteresis-of
>>    draft-goyal-roll-p2p-**measurement POTENTIALLY REPLACED BY
>> draft-ietf-roll-p2p-**measurement
>>    draft-levis-roll-trickle POTENTIALLY REPLACED BY
>> draft-ietf-roll-trickle
>>    draft-popa-roll-applicability-**ami POTENTIALLY REPLACED BY
>> draft-ietf-roll-applicability-**ami
>>    draft-tsao-roll-security-**framework POTENTIALLY REPLACED BY
>> draft-ietf-roll-security-**framework
>>
>> RTGWG Working Group, RTG Area
>>    draft-atlas-rtgwg-mrt-frr-**architecture POTENTIALLY REPLACED BY
>> draft-ietf-rtgwg-mrt-frr-**architecture
>>
>> ------------------------------**------------------------------**-----
>> SEC Area
>> ------------------------------**------------------------------**-----
>> ABFAB Working Group, SEC Area
>>    draft-lear-abfab-arch POTENTIALLY REPLACED BY draft-ietf-abfab-arch
>>
>> HOKEY Working Group, SEC Area
>>    draft-wu-hokey-rfc5296bis POTENTIALLY REPLACED BY
>> draft-ietf-hokey-rfc5296bis
>>
>> MILE Working Group, SEC Area
>>    draft-moriarty-mile-grc-**exchange POTENTIALLY REPLACED BY
>> draft-ietf-mile-grc-exchange
>>
>> NEA Working Group, SEC Area
>>    draft-hanna-nea-pt-eap POTENTIALLY REPLACED BY draft-ietf-nea-pt-eap
>>    draft-sangster-nea-pt-tls POTENTIALLY REPLACED BY draft-ietf-nea-pt-t=
ls
>>
>> OAUTH Working Group, SEC Area
>>    draft-mortimore-oauth-**assertions POTENTIALLY REPLACED BY
>> draft-ietf-oauth-assertions
>>
>> PKIX Working Group, SEC Area
>>    draft-cooper-pkix-rfc2560bis POTENTIALLY REPLACED BY
>> draft-ietf-pkix-rfc2560bis
>>    draft-cooper-pkix-rfc5280-**clarifications POTENTIALLY REPLACED BY
>> draft-ietf-pkix-rfc5280-**clarifications
>>    draft-santesson-pkix-certimage POTENTIALLY REPLACED BY
>> draft-ietf-pkix-certimage
>>
>> TLS Working Group, SEC Area
>>    draft-kanno-tls-camellia POTENTIALLY REPLACED BY
>> draft-ietf-tls-camellia
>>    draft-rescorla-tls-suiteb POTENTIALLY REPLACED BY draft-ietf-tls-suit=
eb
>>    draft-seggelmann-tls-dtls-**heartbeat POTENTIALLY REPLACED BY
>> draft-ietf-tls-dtls-heartbeat
>>
>> ------------------------------**------------------------------**-----
>> TSV Area
>> ------------------------------**------------------------------**-----
>> ALTO Working Group, TSV Area
>>    draft-song-alto-server-**discovery POTENTIALLY REPLACED BY
>> draft-ietf-alto-server-**discovery
>>    draft-stiemerling-alto-**deployments POTENTIALLY REPLACED BY
>> draft-ietf-alto-deployments
>>
>> BEHAVE Working Group, TSV Area
>>    draft-liu-behave-ftp64 POTENTIALLY REPLACED BY draft-ietf-behave-ftp6=
4
>>    draft-penno-behave-64-analysis POTENTIALLY REPLACED BY
>> draft-ietf-behave-64-analysis
>>
>> CDNI Working Group, TSV Area
>>    draft-watson-cdni-use-cases POTENTIALLY REPLACED BY
>> draft-ietf-cdni-use-cases
>>
>> CONEX Working Group, TSV Area
>>    draft-krishnan-conex-destopt POTENTIALLY REPLACED BY
>> draft-ietf-conex-destopt
>>    draft-kuehlewind-conex-tcp-**modifications POTENTIALLY REPLACED BY
>> draft-ietf-conex-tcp-**modifications
>>    draft-mathis-conex-abstract-**mech POTENTIALLY REPLACED BY
>> draft-ietf-conex-abstract-mech
>>    draft-moncaster-conex-**concepts-uses POTENTIALLY REPLACED BY
>> draft-ietf-conex-concepts-uses
>>
>> DECADE Working Group, TSV Area
>>    draft-alimi-decade-arch POTENTIALLY REPLACED BY draft-ietf-decade-arc=
h
>>    draft-chen-decade-integration-**example POTENTIALLY REPLACED BY
>> draft-ietf-decade-integration-**example
>>    draft-huang-decade-**integration-example POTENTIALLY REPLACED BY
>> draft-ietf-decade-integration-**example
>>
>> FECFRAME Working Group, TSV Area
>>    draft-roca-fecframe-ldpc POTENTIALLY REPLACED BY
>> draft-ietf-fecframe-ldpc
>>    draft-roca-fecframe-simple-rs POTENTIALLY REPLACED BY
>> draft-ietf-fecframe-simple-rs
>>
>> IPPM Working Group, TSV Area
>>    draft-baillargeon-ippm-twamp-**value-added-octets POTENTIALLY
>> REPLACED BY draft-ietf-ippm-twamp-value-**added-octets
>>    draft-geib-ippm-metrictest POTENTIALLY REPLACED BY
>> draft-ietf-ippm-metrictest
>>    draft-morton-ippm-rt-loss POTENTIALLY REPLACED BY
>> draft-ietf-ippm-rt-loss
>>    draft-morton-ippm-testplan-**rfc2679 POTENTIALLY REPLACED BY
>> draft-ietf-ippm-testplan-**rfc2679
>>
>> NFSV4 Working Group, TSV Area
>>    draft-alexrn-nfsv4-ipv6 POTENTIALLY REPLACED BY draft-ietf-nfsv4-ipv6
>>    draft-dnoveck-nfsv4-migration-**issues POTENTIALLY REPLACED BY
>> draft-ietf-nfsv4-migration-**issues
>>    draft-eisler-nfsv4-**minorversion-2-requirements POTENTIALLY REPLACED
>> BY draft-ietf-nfsv4-minorversion-**2-requirements
>>    draft-faibish-nfsv4-pnfs-**access-permissions-check POTENTIALLY
>> REPLACED BY draft-ietf-nfsv4-pnfs-access-**permissions-check
>>    draft-faibish-nfsv4-pnfs-**block-disk-protection POTENTIALLY REPLACED
>> BY draft-ietf-nfsv4-pnfs-block-**disk-protection
>>    draft-haynes-nfsv4-**minorversion2 POTENTIALLY REPLACED BY
>> draft-ietf-nfsv4-minorversion2
>>    draft-haynes-nfsv4-**minorversion2-dot-x POTENTIALLY REPLACED BY
>> draft-ietf-nfsv4-**minorversion2-dot-x
>>    draft-quigley-nfsv4-labreqs POTENTIALLY REPLACED BY
>> draft-ietf-nfsv4-labreqs
>>
>> PCN Working Group, TSV Area
>>    draft-karagiannis-pcn-**signaling-requirements POTENTIALLY REPLACED
>> BY draft-ietf-pcn-signaling-**requirements
>>
>> PPSP Working Group, TSV Area
>>    draft-gu-ppsp-peer-protocol POTENTIALLY REPLACED BY
>> draft-ietf-ppsp-peer-protocol
>>    draft-gu-ppsp-survey POTENTIALLY REPLACED BY draft-ietf-ppsp-survey
>>
>> TCPM Working Group, TSV Area
>>    draft-blanton-tcpm-3517bis POTENTIALLY REPLACED BY
>> draft-ietf-tcpm-3517bis
>>    draft-cheng-tcpm-fastopen POTENTIALLY REPLACED BY
>> draft-ietf-tcpm-fastopen
>>    draft-gont-tcpm-rfc1948bis POTENTIALLY REPLACED BY
>> draft-ietf-tcpm-rfc1948bis
>>    draft-henderson-tcpm-rfc3782-**bis POTENTIALLY REPLACED BY
>> draft-ietf-tcpm-rfc3782-bis
>>    draft-hkchu-tcpm-initcwnd POTENTIALLY REPLACED BY
>> draft-ietf-tcpm-initcwnd
>>    draft-mathis-tcpm-**proportional-rate-reduction POTENTIALLY REPLACED
>> BY draft-ietf-tcpm-proportional-**rate-reduction
>>    draft-touch-tcpm-experimental-**options POTENTIALLY REPLACED BY
>> draft-ietf-tcpm-experimental-**options
>>
>> TSVWG Working Group, TSV Area
>>    draft-gont-tsvwg-source-quench POTENTIALLY REPLACED BY
>> draft-ietf-tsvwg-source-quench
>>    draft-polk-tsvwg-intserv-**multiple-tspec POTENTIALLY REPLACED BY
>> draft-ietf-tsvwg-intserv-**multiple-tspec
>>
>> ------------------------------**------------------------------**-----
>> Potential Inconsistencies
>> ------------------------------**------------------------------**-----
>> draft-ietf-6lowpan-nd may replace one or more of 2 individual IDs - chec=
k
>> this
>> draft-ietf-armd-problem-**statement may replace one or more of 2
>> individual IDs - check this
>> draft-ietf-avt-rtp-gsm-hr may replace one or more of 3 individual IDs -
>> check this
>> draft-ietf-avt-rtp-svc may replace one or more of 2 individual IDs -
>> check this
>> draft-ietf-bmwg-ipflow-meth may replace one or more of 2 individual IDs =
-
>> check this
>> draft-ietf-cdni-use-cases may replace one or more of 2 individual IDs -
>> check this
>> draft-ietf-decade-integration-**example may replace one or more of 2
>> individual IDs - check this
>> draft-ietf-decade-survey may replace one or more of 2 individual IDs -
>> check this
>> draft-ietf-dhc-dhcpv4-bulk-**leasequery may replace one or more of 2
>> individual IDs - check this
>> draft-ietf-forces-tmlsp may replace one or more of 2 individual IDs -
>> check this
>> draft-ietf-ipfix-biflow may replace one or more of 2 individual IDs -
>> check this
>> draft-ietf-l2tpext-tdm may replace one or more of 2 individual IDs -
>> check this
>> draft-ietf-l2vpn-vpls-**multihoming may replace one or more of 2
>> individual IDs - check this
>> draft-ietf-mpls-tp-fault may replace one or more of 2 individual IDs -
>> check this
>> draft-ietf-mpls-tp-ring-**protection may replace one or more of 2
>> individual IDs - check this
>> draft-ietf-netconf-monitoring may replace one or more of 2 individual ID=
s
>> - check this
>> draft-ietf-netlmm-lma-**discovery may replace one or more of 2
>> individual IDs - check this
>> draft-ietf-netlmm-mip-**interactions may replace one or more of 2
>> individual IDs - check this
>> draft-ietf-pce-stateful-pce may replace one or more of 2 individual IDs =
-
>> check this
>> draft-ietf-sip-saml may replace one or more of 2 individual IDs - check
>> this
>> draft-ietf-sipping-service-**identification may replace one or more of 2
>> individual IDs - check this
>> draft-ietf-softwire-dslite-**deployment may replace one or more of 2
>> individual IDs - check this
>> draft-ietf-trill-rbridge-arch may replace one or more of 2 individual ID=
s
>> - check this
>>
>>

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

+1<br><br><div class=3D"gmail_quote">On Wed, Apr 18, 2012 at 9:32 AM, Marti=
n Vigoureux <span dir=3D"ltr">&lt;<a href=3D"mailto:martin.vigoureux@alcate=
l-lucent.com">martin.vigoureux@alcatel-lucent.com</a>&gt;</span> wrote:<br>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">

Lars,<br>
<br>
thanks.<br>
As a side question, I was wondering if managing the &quot;replaced by&quot;=
 status shouldn&#39;t be under the full responsibility of the chairs, i.e.,=
 a functionality of the datatracker rather than the chairs needing to send =
an e-mail to the secretariat for each (batch of) changes.<br>


What do you think? and that question also goes to the chairs.<br>
<br>
-m<br>
<br>
Le 18/04/2012 10:49, Eggert, Lars a =E9crit :<div class=3D"HOEnZb"><div cla=
ss=3D"h5"><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Hi,<br>
<br>
here&#39;s yet another installment in the series of reports on potentially =
missing &quot;replaced-by&quot; relationships in the IETF datatracker.<br>
<br>
*** NEW *** Also includes IRTF documents now.<br>
<br>
WG and RG chairs are encouraged to check whether these are accurate for the=
ir groups, and if so, send a ticket to the secretariat instructing them to =
&quot;record in the database that draft X replaced draft Y&quot;.<br>
<br>
As always, double-check before reporting to the secretariat. Also, see list=
 of possible inconsistencies at the end of the report.<br>
<br>
(Note that the IPR disclosure search tool uses these replaced-by relationsh=
ips, so keeping them up-to-date is actually useful and not just WG hygiene.=
)<br>
<br>
Lars<br>
<br>
<br>
------------------------------<u></u>------------------------------<u></u>-=
----<br>
APP Area<br>
------------------------------<u></u>------------------------------<u></u>-=
----<br>
CORE Working Group, APP Area<br>
 =A0 =A0draft-rahman-core-groupcomm POTENTIALLY REPLACED BY draft-ietf-core=
-groupcomm<br>
<br>
EAI Working Group, APP Area<br>
 =A0 =A0draft-duerst-eai-mailto POTENTIALLY REPLACED BY draft-ietf-eai-mail=
to<br>
 =A0 =A0draft-yao-eai-rfc5336bis POTENTIALLY REPLACED BY draft-ietf-eai-rfc=
5336bis<br>
<br>
PAWS Working Group, APP Area<br>
 =A0 =A0draft-probasco-paws-problem-<u></u>stmt-usecases-rqmts POTENTIALLY =
REPLACED BY draft-ietf-paws-problem-stmt-<u></u>usecases-rqmts<br>
<br>
VCARDDAV Working Group, APP Area<br>
 =A0 =A0draft-cauchie-vcarddav-oma-<u></u>cab-extensions POTENTIALLY REPLAC=
ED BY draft-ietf-vcarddav-oma-cab-<u></u>extensions<br>
<br>
------------------------------<u></u>------------------------------<u></u>-=
----<br>
CONCLUDED Area<br>
------------------------------<u></u>------------------------------<u></u>-=
----<br>
ATOMPUB Working Group, CONCLUDED Area<br>
 =A0 =A0draft-snell-atompub-<u></u>autodiscovery POTENTIALLY REPLACED BY dr=
aft-ietf-atompub-<u></u>autodiscovery<br>
<br>
HTTP Working Group, CONCLUDED Area<br>
 =A0 =A0draft-wallis-http-digest-auth-<u></u>a3a8 POTENTIALLY REPLACED BY d=
raft-ietf-http-digest-auth-<u></u>a3a8<br>
<br>
IDNABIS Working Group, CONCLUDED Area<br>
 =A0 =A0draft-faltstrom-idnabis-tables POTENTIALLY REPLACED BY draft-ietf-i=
dnabis-tables<br>
<br>
IMAP Working Group, CONCLUDED Area<br>
 =A0 =A0draft-crispin-imap-compat POTENTIALLY REPLACED BY draft-ietf-imap-c=
ompat<br>
<br>
TFTPEXTS Working Group, CONCLUDED Area<br>
 =A0 =A0draft-malkin-tftpexts-blksize-<u></u>opt POTENTIALLY REPLACED BY dr=
aft-ietf-tftpexts-blksize-<u></u>opt<br>
 =A0 =A0draft-malkin-tftpexts-option-<u></u>ext POTENTIALLY REPLACED BY dra=
ft-ietf-tftpexts-option-ext<br>
 =A0 =A0draft-malkin-tftpexts-options POTENTIALLY REPLACED BY draft-ietf-tf=
tpexts-options<br>
<br>
XMPP Working Group, CONCLUDED Area<br>
 =A0 =A0draft-barnes-xmpp-dna POTENTIALLY REPLACED BY draft-ietf-xmpp-dna<b=
r>
 =A0 =A0draft-miller-xmpp-e2e POTENTIALLY REPLACED BY draft-ietf-xmpp-e2e<b=
r>
 =A0 =A0draft-saintandre-xmpp-6122bis POTENTIALLY REPLACED BY draft-ietf-xm=
pp-6122bis<br>
<br>
MIPSHOP Working Group, CONCLUDED Area<br>
 =A0 =A0draft-xia-mipshop-fmip-ptp POTENTIALLY REPLACED BY draft-ietf-mipsh=
op-fmip-ptp<br>
<br>
NETLMM Working Group, CONCLUDED Area<br>
 =A0 =A0draft-cui-netlmm-mip-<u></u>interactions POTENTIALLY REPLACED BY dr=
aft-ietf-netlmm-mip-<u></u>interactions<br>
 =A0 =A0draft-glenn-netlmm-pmipv6-mib POTENTIALLY REPLACED BY draft-ietf-ne=
tlmm-pmipv6-mib<br>
 =A0 =A0draft-korhonen-netlmm-lma-<u></u>discovery POTENTIALLY REPLACED BY =
draft-ietf-netlmm-lma-<u></u>discovery<br>
 =A0 =A0draft-xia-netlmm-lma-discovery POTENTIALLY REPLACED BY draft-ietf-n=
etlmm-lma-<u></u>discovery<br>
<br>
SEND Working Group, CONCLUDED Area<br>
 =A0 =A0draft-arkko-send-cga POTENTIALLY REPLACED BY draft-ietf-send-cga<br=
>
 =A0 =A0draft-arkko-send-ndopt POTENTIALLY REPLACED BY draft-ietf-send-ndop=
t<br>
<br>
SHIM6 Working Group, CONCLUDED Area<br>
 =A0 =A0draft-garcia-shim6-<u></u>applicability POTENTIALLY REPLACED BY dra=
ft-ietf-shim6-applicability<br>
<br>
CAPWAP Working Group, CONCLUDED Area<br>
 =A0 =A0draft-yangshi-capwap-802dot11-<u></u>mib POTENTIALLY REPLACED BY dr=
aft-ietf-capwap-802dot11-mib<br>
 =A0 =A0draft-yangshi-capwap-base-mib POTENTIALLY REPLACED BY draft-ietf-ca=
pwap-base-mib<br>
<br>
RMONMIB Working Group, CONCLUDED Area<br>
 =A0 =A0draft-bierman-rmonmib-hc-<u></u>alarm-mib POTENTIALLY REPLACED BY d=
raft-ietf-rmonmib-hc-alarm-<u></u>mib<br>
<br>
MEGACO Working Group, CONCLUDED Area<br>
 =A0 =A0draft-blatherwick-megaco-<u></u>ipphone POTENTIALLY REPLACED BY dra=
ft-ietf-megaco-ipphone<br>
<br>
SIGTRAN Working Group, CONCLUDED Area<br>
 =A0 =A0draft-anil-sigtran-dua POTENTIALLY REPLACED BY draft-ietf-sigtran-d=
ua<br>
<br>
SIP Working Group, CONCLUDED Area<br>
 =A0 =A0draft-arkko-sip-sec-agree POTENTIALLY REPLACED BY draft-ietf-sip-se=
c-agree<br>
 =A0 =A0draft-biggs-sip-replaces POTENTIALLY REPLACED BY draft-ietf-sip-rep=
laces<br>
 =A0 =A0draft-pashalidis-sip-saml POTENTIALLY REPLACED BY draft-ietf-sip-sa=
ml<br>
<br>
SIPPING Working Group, CONCLUDED Area<br>
 =A0 =A0draft-drage-sipping-service-<u></u>identification POTENTIALLY REPLA=
CED BY draft-ietf-sipping-service-<u></u>identification<br>
 =A0 =A0draft-elwell-sipping-update-<u></u>pai POTENTIALLY REPLACED BY draf=
t-ietf-sipping-update-pai<br>
 =A0 =A0draft-hilt-sipping-overload-<u></u>design POTENTIALLY REPLACED BY d=
raft-ietf-sipping-overload-<u></u>design<br>
 =A0 =A0draft-petrie-sipping-profile-<u></u>datasets POTENTIALLY REPLACED B=
Y draft-ietf-sipping-profile-<u></u>datasets<br>
 =A0 =A0draft-rosenberg-sipping-<u></u>service-identification POTENTIALLY R=
EPLACED BY draft-ietf-sipping-service-<u></u>identification<br>
 =A0 =A0draft-zhang-sipping-overlap POTENTIALLY REPLACED BY draft-ietf-sipp=
ing-overlap<br>
<br>
SPEERMINT Working Group, CONCLUDED Area<br>
 =A0 =A0draft-meyer-speermint-reqs-<u></u>and-terminology POTENTIALLY REPLA=
CED BY draft-ietf-speermint-reqs-and-<u></u>terminology<br>
 =A0 =A0draft-niccolini-speermint-<u></u>voipthreats POTENTIALLY REPLACED B=
Y draft-ietf-speermint-<u></u>voipthreats<br>
<br>
XCON Working Group, CONCLUDED Area<br>
 =A0 =A0draft-barnes-xcon-ccmp POTENTIALLY REPLACED BY draft-ietf-xcon-ccmp=
<br>
 =A0 =A0draft-barnes-xcon-examples POTENTIALLY REPLACED BY draft-ietf-xcon-=
examples<br>
<br>
DKIM Working Group, CONCLUDED Area<br>
 =A0 =A0draft-lindsey-dkim-<u></u>mailinglists POTENTIALLY REPLACED BY draf=
t-ietf-dkim-mailinglists<br>
<br>
SACRED Working Group, CONCLUDED Area<br>
 =A0 =A0draft-arsenault-sacred-reqs POTENTIALLY REPLACED BY draft-ietf-sacr=
ed-reqs<br>
<br>
SASL Working Group, CONCLUDED Area<br>
 =A0 =A0draft-zeilenga-sasl-crammd5 POTENTIALLY REPLACED BY draft-ietf-sasl=
-crammd5<br>
 =A0 =A0draft-zeilenga-sasl-rfc2222bis POTENTIALLY REPLACED BY draft-ietf-s=
asl-rfc2222bis<br>
<br>
SMIME Working Group, CONCLUDED Area<br>
 =A0 =A0draft-dusse-smime-cert POTENTIALLY REPLACED BY draft-ietf-smime-cer=
t<br>
 =A0 =A0draft-dusse-smime-msg POTENTIALLY REPLACED BY draft-ietf-smime-msg<=
br>
<br>
DIFFSERV Working Group, CONCLUDED Area<br>
 =A0 =A0draft-baker-diffserv-mib POTENTIALLY REPLACED BY draft-ietf-diffser=
v-mib<br>
 =A0 =A0draft-black-diffserv-tunnels POTENTIALLY REPLACED BY draft-ietf-dif=
fserv-tunnels<br>
<br>
RSVP Working Group, CONCLUDED Area<br>
 =A0 =A0draft-berger-rsvp-refresh-<u></u>reduct POTENTIALLY REPLACED BY dra=
ft-ietf-rsvp-refresh-reduct<br>
<br>
------------------------------<u></u>------------------------------<u></u>-=
----<br>
INT Area<br>
------------------------------<u></u>------------------------------<u></u>-=
----<br>
6MAN Working Group, INT Area<br>
 =A0 =A0draft-carpenter-6man-uri-<u></u>zoneid POTENTIALLY REPLACED BY draf=
t-ietf-6man-uri-zoneid<br>
 =A0 =A0draft-costa-6man-dad-proxy POTENTIALLY REPLACED BY draft-ietf-6man-=
dad-proxy<br>
 =A0 =A0draft-fujisaki-6man-addr-<u></u>select-opt POTENTIALLY REPLACED BY =
draft-ietf-6man-addr-select-<u></u>opt<br>
 =A0 =A0draft-george-6man-3627-<u></u>historic POTENTIALLY REPLACED BY draf=
t-ietf-6man-3627-historic<br>
 =A0 =A0draft-gont-6man-ipv6-atomic-<u></u>fragments POTENTIALLY REPLACED B=
Y draft-ietf-6man-ipv6-atomic-<u></u>fragments<br>
 =A0 =A0draft-hsingh-6man-enhanced-dad POTENTIALLY REPLACED BY draft-ietf-6=
man-enhanced-dad<br>
 =A0 =A0draft-joshi-6man-neighbor-<u></u>inform POTENTIALLY REPLACED BY dra=
ft-ietf-6man-neighbor-<u></u>inform<br>
 =A0 =A0draft-lynn-6man-6lobac POTENTIALLY REPLACED BY draft-ietf-6man-6lob=
ac<br>
 =A0 =A0draft-nordmark-6man-impatient-<u></u>nud POTENTIALLY REPLACED BY dr=
aft-ietf-6man-impatient-nud<br>
<br>
ANCP Working Group, INT Area<br>
 =A0 =A0draft-lefaucheur-ancp-mc-<u></u>extensions POTENTIALLY REPLACED BY =
draft-ietf-ancp-mc-extensions<br>
<br>
CSI Working Group, INT Area<br>
 =A0 =A0draft-jiang-csi-dhcpv6-cga-ps POTENTIALLY REPLACED BY draft-ietf-cs=
i-dhcpv6-cga-ps<br>
 =A0 =A0draft-rgaglian-csi-send-name-<u></u>type-registry POTENTIALLY REPLA=
CED BY draft-ietf-csi-send-name-type-<u></u>registry<br>
<br>
DHC Working Group, INT Area<br>
 =A0 =A0draft-jiang-dhc-cga-config-<u></u>dhcpv6 POTENTIALLY REPLACED BY dr=
aft-ietf-dhc-cga-config-<u></u>dhcpv6<br>
 =A0 =A0draft-jjmb-dhc-dhcpv6-<u></u>redundancy-consider POTENTIALLY REPLAC=
ED BY draft-ietf-dhc-dhcpv6-<u></u>redundancy-consider<br>
 =A0 =A0draft-miles-dhc-dhcpv6-ldra POTENTIALLY REPLACED BY draft-ietf-dhc-=
dhcpv6-ldra<br>
 =A0 =A0draft-mrugalski-dhc-dhcpv6-<u></u>failover-requirements POTENTIALLY=
 REPLACED BY draft-ietf-dhc-dhcpv6-<u></u>failover-requirements<br>
 =A0 =A0draft-xia-dhc-host-gen-id POTENTIALLY REPLACED BY draft-ietf-dhc-ho=
st-gen-id<br>
<br>
DNSEXT Working Group, INT Area<br>
 =A0 =A0draft-wang-dnsext-newzone-<u></u>notify POTENTIALLY REPLACED BY dra=
ft-ietf-dnsext-newzone-<u></u>notify<br>
<br>
HIP Working Group, INT Area<br>
 =A0 =A0draft-camarillo-hip-via POTENTIALLY REPLACED BY draft-ietf-hip-via<=
br>
 =A0 =A0draft-henderson-hip-rfc5206-<u></u>bis POTENTIALLY REPLACED BY draf=
t-ietf-hip-rfc5206-bis<br>
 =A0 =A0draft-jokela-hip-rfc5202-bis POTENTIALLY REPLACED BY draft-ietf-hip=
-rfc5202-bis<br>
 =A0 =A0draft-keranen-hip-native-nat-<u></u>traversal POTENTIALLY REPLACED =
BY draft-ietf-hip-native-nat-<u></u>traversal<br>
 =A0 =A0draft-keranen-hip-over-hip POTENTIALLY REPLACED BY draft-ietf-hip-o=
ver-hip<br>
 =A0 =A0draft-keranen-hip-reload-<u></u>instance POTENTIALLY REPLACED BY dr=
aft-ietf-hip-reload-instance<br>
 =A0 =A0draft-moskowitz-hip-rfc4423-<u></u>bis POTENTIALLY REPLACED BY draf=
t-ietf-hip-rfc4423-bis<br>
 =A0 =A0draft-moskowitz-hip-rfc5201-<u></u>bis POTENTIALLY REPLACED BY draf=
t-ietf-hip-rfc5201-bis<br>
 =A0 =A0draft-nikander-hip-hiccups POTENTIALLY REPLACED BY draft-ietf-hip-h=
iccups<br>
<br>
INTAREA Working Group, INT Area<br>
 =A0 =A0draft-boucadair-intarea-nat-<u></u>reveal-analysis POTENTIALLY REPL=
ACED BY draft-ietf-intarea-nat-reveal-<u></u>analysis<br>
<br>
LISP Working Group, INT Area<br>
 =A0 =A0draft-jakab-lisp-deployment POTENTIALLY REPLACED BY draft-ietf-lisp=
-deployment<br>
 =A0 =A0draft-maino-lisp-sec POTENTIALLY REPLACED BY draft-ietf-lisp-sec<br=
>
 =A0 =A0draft-meyer-lisp-eid-block POTENTIALLY REPLACED BY draft-ietf-lisp-=
eid-block<br>
<br>
MIF Working Group, INT Area<br>
 =A0 =A0draft-liu-mif-api-extension POTENTIALLY REPLACED BY draft-ietf-mif-=
api-extension<br>
<br>
MULTIMOB Working Group, INT Area<br>
 =A0 =A0draft-schmidt-multimob-pmipv6-<u></u>source POTENTIALLY REPLACED BY=
 draft-ietf-multimob-pmipv6-<u></u>source<br>
 =A0 =A0draft-wu-multimob-igmp-mld-<u></u>tuning POTENTIALLY REPLACED BY dr=
aft-ietf-multimob-igmp-mld-<u></u>tuning<br>
 =A0 =A0draft-zuniga-multimob-pmipv6-<u></u>ropt POTENTIALLY REPLACED BY dr=
aft-ietf-multimob-pmipv6-<u></u>ropt<br>
<br>
NETEXT Working Group, INT Area<br>
 =A0 =A0draft-bernardos-netext-pmipv6-<u></u>flowmob POTENTIALLY REPLACED B=
Y draft-ietf-netext-pmipv6-<u></u>flowmob<br>
 =A0 =A0draft-korhonen-netext-redirect POTENTIALLY REPLACED BY draft-ietf-n=
etext-redirect<br>
 =A0 =A0draft-krishnan-netext-pmip-lr POTENTIALLY REPLACED BY draft-ietf-ne=
text-pmip-lr<br>
 =A0 =A0draft-melia-netext-logical-<u></u>interface-support POTENTIALLY REP=
LACED BY draft-ietf-netext-logical-<u></u>interface-support<br>
 =A0 =A0draft-zhou-netext-pd-pmip POTENTIALLY REPLACED BY draft-ietf-netext=
-pd-pmip<br>
<br>
PCP Working Group, INT Area<br>
 =A0 =A0draft-bpw-pcp-dhcp POTENTIALLY REPLACED BY draft-ietf-pcp-dhcp<br>
 =A0 =A0draft-bpw-pcp-upnp-igd-<u></u>interworking POTENTIALLY REPLACED BY =
draft-ietf-pcp-upnp-igd-<u></u>interworking<br>
<br>
SAVI Working Group, INT Area<br>
 =A0 =A0draft-bi-savi-mix POTENTIALLY REPLACED BY draft-ietf-savi-mix<br>
<br>
SOFTWIRE Working Group, INT Area<br>
 =A0 =A0draft-guo-softwire-6rd-radius-<u></u>attrib POTENTIALLY REPLACED BY=
 draft-ietf-softwire-6rd-<u></u>radius-attrib<br>
 =A0 =A0draft-ieft-softwire-dslite-<u></u>deployment POTENTIALLY REPLACED B=
Y draft-ietf-softwire-dslite-<u></u>deployment<br>
 =A0 =A0draft-lee-softwire-dslite-<u></u>deployment POTENTIALLY REPLACED BY=
 draft-ietf-softwire-dslite-<u></u>deployment<br>
 =A0 =A0draft-maglione-softwire-<u></u>dslite-radius-ext POTENTIALLY REPLAC=
ED BY draft-ietf-softwire-dslite-<u></u>radius-ext<br>
 =A0 =A0draft-qin-softwire-multicast-<u></u>prefix-option POTENTIALLY REPLA=
CED BY draft-ietf-softwire-multicast-<u></u>prefix-option<br>
 =A0 =A0draft-xu-softwire-mesh-<u></u>multicast POTENTIALLY REPLACED BY dra=
ft-ietf-softwire-mesh-<u></u>multicast<br>
<br>
TICTOC Working Group, INT Area<br>
 =A0 =A0draft-davari-tictoc-<u></u>1588overmpls POTENTIALLY REPLACED BY dra=
ft-ietf-tictoc-1588overmpls<br>
 =A0 =A0draft-mizrahi-tictoc-security-<u></u>requirements POTENTIALLY REPLA=
CED BY draft-ietf-tictoc-security-<u></u>requirements<br>
 =A0 =A0draft-vinay-tictoc-ptp-mib POTENTIALLY REPLACED BY draft-ietf-ticto=
c-ptp-mib<br>
<br>
TRILL Working Group, INT Area<br>
 =A0 =A0draft-tissa-trill-cmt POTENTIALLY REPLACED BY draft-ietf-trill-cmt<=
br>
<br>
------------------------------<u></u>------------------------------<u></u>-=
----<br>
IRTF Area<br>
------------------------------<u></u>------------------------------<u></u>-=
----<br>
DTNRG Working Group, IRTF Area<br>
 =A0 =A0draft-lindgren-dtnrg-prophet POTENTIALLY REPLACED BY draft-irtf-dtn=
rg-prophet<br>
 =A0 =A0draft-symington-dtnrg-bundle-<u></u>metadata-block POTENTIALLY REPL=
ACED BY draft-irtf-dtnrg-bundle-<u></u>metadata-block<br>
 =A0 =A0draft-symington-dtnrg-bundle-<u></u>retrans-block POTENTIALLY REPLA=
CED BY draft-irtf-dtnrg-bundle-<u></u>retrans-block<br>
<br>
HIPRG Working Group, IRTF Area<br>
 =A0 =A0draft-ahrenholz-hiprg-dht POTENTIALLY REPLACED BY draft-irtf-hiprg-=
dht<br>
<br>
MOBOPTS Working Group, IRTF Area<br>
 =A0 =A0draft-koki-mobopts-l2-<u></u>abstractions POTENTIALLY REPLACED BY d=
raft-irtf-mobopts-l2-<u></u>abstractions<br>
 =A0 =A0draft-ohba-mobopts-mpa-<u></u>framework POTENTIALLY REPLACED BY dra=
ft-irtf-mobopts-mpa-<u></u>framework<br>
 =A0 =A0draft-schmidt-mobopts-<u></u>mmcastv6-ps POTENTIALLY REPLACED BY dr=
aft-irtf-mobopts-mmcastv6-ps<br>
 =A0 =A0draft-weniger-mobopts-mip6-<u></u>cnlocpriv POTENTIALLY REPLACED BY=
 draft-irtf-mobopts-mip6-<u></u>cnlocpriv<br>
<br>
P2PRG Working Group, IRTF Area<br>
 =A0 =A0draft-gurbani-p2prg-<u></u>simulation-survey POTENTIALLY REPLACED B=
Y draft-irtf-p2prg-simulation-<u></u>survey<br>
<br>
------------------------------<u></u>------------------------------<u></u>-=
----<br>
IRTF-CONCLUDED Area<br>
------------------------------<u></u>------------------------------<u></u>-=
----<br>
------------------------------<u></u>------------------------------<u></u>-=
----<br>
OPS Area<br>
------------------------------<u></u>------------------------------<u></u>-=
----<br>
ARMD Working Group, OPS Area<br>
 =A0 =A0draft-dunbar-armd-problem-<u></u>statement POTENTIALLY REPLACED BY =
draft-ietf-armd-problem-<u></u>statement<br>
<br>
BMWG Working Group, OPS Area<br>
 =A0 =A0draft-janovak-bmwg-ipflow-meth POTENTIALLY REPLACED BY draft-ietf-b=
mwg-ipflow-meth<br>
 =A0 =A0draft-morton-bmwg-imix-genome POTENTIALLY REPLACED BY draft-ietf-bm=
wg-imix-genome<br>
<br>
DIME Working Group, OPS Area<br>
 =A0 =A0draft-zorn-dime-rfc4005bis POTENTIALLY REPLACED BY draft-ietf-dime-=
rfc4005bis<br>
<br>
EMAN Working Group, OPS Area<br>
 =A0 =A0draft-tychon-eman-<u></u>applicability-statement POTENTIALLY REPLAC=
ED BY draft-ietf-eman-applicability-<u></u>statement<br>
<br>
GROW Working Group, OPS Area<br>
 =A0 =A0draft-dimitri-grow-rss POTENTIALLY REPLACED BY draft-ietf-grow-rss<=
br>
 =A0 =A0draft-manderson-grow-geomrt POTENTIALLY REPLACED BY draft-ietf-grow=
-geomrt<br>
<br>
IPFIX Working Group, OPS Area<br>
 =A0 =A0draft-boschi-ipfix-anon POTENTIALLY REPLACED BY draft-ietf-ipfix-an=
on<br>
 =A0 =A0draft-boschi-ipfix-exporting-<u></u>type POTENTIALLY REPLACED BY dr=
aft-ietf-ipfix-exporting-<u></u>type<br>
 =A0 =A0draft-claise-ipfix-export-per-<u></u>sctp-stream POTENTIALLY REPLAC=
ED BY draft-ietf-ipfix-export-per-<u></u>sctp-stream<br>
 =A0 =A0draft-claise-ipfix-protocol-<u></u>rfc5101bis POTENTIALLY REPLACED =
BY draft-ietf-ipfix-protocol-<u></u>rfc5101bis<br>
 =A0 =A0draft-dkcm-ipfix-rfc5815bis POTENTIALLY REPLACED BY draft-ietf-ipfi=
x-rfc5815bis<br>
 =A0 =A0draft-gupta-ipfix-reliability-<u></u>template-ext POTENTIALLY REPLA=
CED BY draft-ietf-ipfix-reliability-<u></u>template-ext<br>
 =A0 =A0draft-trammell-ipfix-file POTENTIALLY REPLACED BY draft-ietf-ipfix-=
file<br>
<br>
MBONED Working Group, OPS Area<br>
 =A0 =A0draft-asaeda-mboned-mtrace-v2 POTENTIALLY REPLACED BY draft-ietf-mb=
oned-mtrace-v2<br>
 =A0 =A0draft-asaeda-mboned-session-<u></u>announcement-req POTENTIALLY REP=
LACED BY draft-ietf-mboned-session-<u></u>announcement-req<br>
 =A0 =A0draft-bipi-mboned-ip-<u></u>multicast-pm-requirement POTENTIALLY RE=
PLACED BY draft-ietf-mboned-ip-<u></u>multicast-pm-requirement<br>
 =A0 =A0draft-venaas-mboned-mcaddrdoc POTENTIALLY REPLACED BY draft-ietf-mb=
oned-mcaddrdoc<br>
 =A0 =A0draft-venaas-mboned-ssmping POTENTIALLY REPLACED BY draft-ietf-mbon=
ed-ssmping<br>
<br>
NETCONF Working Group, OPS Area<br>
 =A0 =A0draft-bierman-netconf-access-<u></u>control POTENTIALLY REPLACED BY=
 draft-ietf-netconf-access-<u></u>control<br>
 =A0 =A0draft-bierman-netconf-with-<u></u>defaults POTENTIALLY REPLACED BY =
draft-ietf-netconf-with-<u></u>defaults<br>
 =A0 =A0draft-chisholm-netconf-<u></u>monitoring POTENTIALLY REPLACED BY dr=
aft-ietf-netconf-monitoring<br>
<br>
NETMOD Working Group, OPS Area<br>
 =A0 =A0draft-bierman-netmod-system-<u></u>mgmt POTENTIALLY REPLACED BY dra=
ft-ietf-netmod-system-mgmt<br>
 =A0 =A0draft-bjorklund-netmod-<u></u>interfaces-cfg POTENTIALLY REPLACED B=
Y draft-ietf-netmod-interfaces-<u></u>cfg<br>
 =A0 =A0draft-bjorklund-netmod-ip-cfg POTENTIALLY REPLACED BY draft-ietf-ne=
tmod-ip-cfg<br>
 =A0 =A0draft-lhotka-netmod-routing-<u></u>cfg POTENTIALLY REPLACED BY draf=
t-ietf-netmod-routing-cfg<br>
 =A0 =A0draft-schoenw-netmod-smi-yang POTENTIALLY REPLACED BY draft-ietf-ne=
tmod-smi-yang<br>
<br>
OPSAWG Working Group, OPS Area<br>
 =A0 =A0draft-mizrahi-opsawg-oam-<u></u>overview POTENTIALLY REPLACED BY dr=
aft-ietf-opsawg-oam-overview<br>
<br>
OPSEC Working Group, OPS Area<br>
 =A0 =A0draft-gont-opsec-icmp-<u></u>filtering POTENTIALLY REPLACED BY draf=
t-ietf-opsec-icmp-<u></u>filtering<br>
 =A0 =A0draft-gont-opsec-ip-security POTENTIALLY REPLACED BY draft-ietf-ops=
ec-ip-security<br>
<br>
RADEXT Working Group, OPS Area<br>
 =A0 =A0draft-dekok-radext-dtls POTENTIALLY REPLACED BY draft-ietf-radext-d=
tls<br>
 =A0 =A0draft-dekok-radext-radius-<u></u>extensions POTENTIALLY REPLACED BY=
 draft-ietf-radext-radius-<u></u>extensions<br>
 =A0 =A0draft-dekok-radext-tcp-<u></u>transport POTENTIALLY REPLACED BY dra=
ft-ietf-radext-tcp-<u></u>transport<br>
 =A0 =A0draft-lourdelet-radext-ipv6-<u></u>access POTENTIALLY REPLACED BY d=
raft-ietf-radext-ipv6-access<br>
 =A0 =A0draft-nelson-radext-crypto-<u></u>agility-requirements POTENTIALLY =
REPLACED BY draft-ietf-radext-crypto-<u></u>agility-requirements<br>
 =A0 =A0draft-tiwari-radext-tunnel-<u></u>type POTENTIALLY REPLACED BY draf=
t-ietf-radext-tunnel-type<br>
<br>
V6OPS Working Group, OPS Area<br>
 =A0 =A0draft-hilliard-v6ops-ipv6-<u></u>discard-prefix POTENTIALLY REPLACE=
D BY draft-ietf-v6ops-ipv6-discard-<u></u>prefix<br>
 =A0 =A0draft-rgaglian-v6ops-v6inixp POTENTIALLY REPLACED BY draft-ietf-v6o=
ps-v6inixp<br>
 =A0 =A0draft-vandevelde-v6ops-ra-<u></u>guard POTENTIALLY REPLACED BY draf=
t-ietf-v6ops-ra-guard<br>
 =A0 =A0draft-wbeebee-v6ops-ipv6-cpe-<u></u>router-bis POTENTIALLY REPLACED=
 BY draft-ietf-v6ops-ipv6-cpe-<u></u>router-bis<br>
<br>
------------------------------<u></u>------------------------------<u></u>-=
----<br>
RAI Area<br>
------------------------------<u></u>------------------------------<u></u>-=
----<br>
ATOCA Working Group, RAI Area<br>
 =A0 =A0draft-rosen-atoca-cap POTENTIALLY REPLACED BY draft-ietf-atoca-cap<=
br>
<br>
BLISS Working Group, RAI Area<br>
 =A0 =A0draft-elwell-bliss-ach-<u></u>analysis POTENTIALLY REPLACED BY draf=
t-ietf-bliss-ach-analysis<br>
 =A0 =A0draft-poetzl-bliss-call-<u></u>completion POTENTIALLY REPLACED BY d=
raft-ietf-bliss-call-<u></u>completion<br>
 =A0 =A0draft-procter-bliss-call-park-<u></u>extension POTENTIALLY REPLACED=
 BY draft-ietf-bliss-call-park-<u></u>extension<br>
 =A0 =A0draft-rosenberg-bliss-problem-<u></u>statement POTENTIALLY REPLACED=
 BY draft-ietf-bliss-problem-<u></u>statement<br>
<br>
CLUE Working Group, RAI Area<br>
 =A0 =A0draft-romanow-clue-framework POTENTIALLY REPLACED BY draft-ietf-clu=
e-framework<br>
 =A0 =A0draft-romanow-clue-<u></u>telepresence-requirements POTENTIALLY REP=
LACED BY draft-ietf-clue-telepresence-<u></u>requirements<br>
 =A0 =A0draft-romanow-clue-<u></u>telepresence-use-cases POTENTIALLY REPLAC=
ED BY draft-ietf-clue-telepresence-<u></u>use-cases<br>
<br>
CODEC Working Group, RAI Area<br>
 =A0 =A0draft-valin-codec-guidelines POTENTIALLY REPLACED BY draft-ietf-cod=
ec-guidelines<br>
 =A0 =A0draft-valin-codec-results POTENTIALLY REPLACED BY draft-ietf-codec-=
results<br>
<br>
DRINKS Working Group, RAI Area<br>
 =A0 =A0draft-channabasappa-drinks-<u></u>usecases-requirements POTENTIALLY=
 REPLACED BY draft-ietf-drinks-usecases-<u></u>requirements<br>
<br>
GEOPRIV Working Group, RAI Area<br>
 =A0 =A0draft-barnes-geopriv-policy-<u></u>uri POTENTIALLY REPLACED BY draf=
t-ietf-geopriv-policy-uri<br>
 =A0 =A0draft-mayrhofer-geopriv-geo-<u></u>uri POTENTIALLY REPLACED BY draf=
t-ietf-geopriv-geo-uri<br>
 =A0 =A0draft-winterbottom-geopriv-<u></u>local-civic POTENTIALLY REPLACED =
BY draft-ietf-geopriv-local-civic<br>
<br>
MMUSIC Working Group, RAI Area<br>
 =A0 =A0draft-garcia-mmusic-sdp-<u></u>miscellaneous-caps POTENTIALLY REPLA=
CED BY draft-ietf-mmusic-sdp-<u></u>miscellaneous-caps<br>
 =A0 =A0draft-greevenbosch-mmusic-<u></u>parallax-attribute POTENTIALLY REP=
LACED BY draft-ietf-mmusic-parallax-<u></u>attribute<br>
 =A0 =A0draft-greevenbosch-mmusic-<u></u>signal-3d-format POTENTIALLY REPLA=
CED BY draft-ietf-mmusic-signal-3d-<u></u>format<br>
 =A0 =A0draft-holmberg-mmusic-sdp-<u></u>bundle-negotiation POTENTIALLY REP=
LACED BY draft-ietf-mmusic-sdp-bundle-<u></u>negotiation<br>
 =A0 =A0draft-loreto-mmusic-sctp-sdp POTENTIALLY REPLACED BY draft-ietf-mmu=
sic-sctp-sdp<br>
 =A0 =A0draft-polk-mmusic-traffic-<u></u>class-for-sdp POTENTIALLY REPLACED=
 BY draft-ietf-mmusic-traffic-<u></u>class-for-sdp<br>
<br>
P2PSIP Working Group, RAI Area<br>
 =A0 =A0draft-bryan-p2psip-reload POTENTIALLY REPLACED BY draft-ietf-p2psip=
-reload<br>
 =A0 =A0draft-zong-p2psip-drr POTENTIALLY REPLACED BY draft-ietf-p2psip-drr=
<br>
 =A0 =A0draft-zong-p2psip-rpr POTENTIALLY REPLACED BY draft-ietf-p2psip-rpr=
<br>
<br>
PAYLOAD Working Group, RAI Area<br>
 =A0 =A0draft-westin-payload-vp8 POTENTIALLY REPLACED BY draft-ietf-payload=
-vp8<br>
<br>
RTCWEB Working Group, RAI Area<br>
 =A0 =A0draft-uberti-rtcweb-jsep POTENTIALLY REPLACED BY draft-ietf-rtcweb-=
jsep<br>
<br>
SIPCORE Working Group, RAI Area<br>
 =A0 =A0draft-holmberg-sipcore-proxy-<u></u>feature POTENTIALLY REPLACED BY=
 draft-ietf-sipcore-proxy-<u></u>feature<br>
<br>
SOC Working Group, RAI Area<br>
 =A0 =A0draft-noel-soc-overload-rate-<u></u>control POTENTIALLY REPLACED BY=
 draft-ietf-soc-overload-rate-<u></u>control<br>
 =A0 =A0draft-shen-soc-load-control-<u></u>event-package POTENTIALLY REPLAC=
ED BY draft-ietf-soc-load-control-<u></u>event-package<br>
<br>
XMPP Working Group, RAI Area<br>
 =A0 =A0draft-barnes-xmpp-dna POTENTIALLY REPLACED BY draft-ietf-xmpp-dna<b=
r>
 =A0 =A0draft-miller-xmpp-e2e POTENTIALLY REPLACED BY draft-ietf-xmpp-e2e<b=
r>
 =A0 =A0draft-saintandre-xmpp-6122bis POTENTIALLY REPLACED BY draft-ietf-xm=
pp-6122bis<br>
<br>
XRBLOCK Working Group, RAI Area<br>
 =A0 =A0draft-clark-xrblock-rtcp-xr-<u></u>qoe POTENTIALLY REPLACED BY draf=
t-ietf-xrblock-rtcp-xr-qoe<br>
<br>
------------------------------<u></u>------------------------------<u></u>-=
----<br>
RTG Area<br>
------------------------------<u></u>------------------------------<u></u>-=
----<br>
BFD Working Group, RTG Area<br>
 =A0 =A0draft-bhatia-bfd-hmac-sha POTENTIALLY REPLACED BY draft-ietf-bfd-hm=
ac-sha<br>
<br>
CCAMP Working Group, RTG Area<br>
 =A0 =A0draft-bccg-ccamp-otn-g709-<u></u>info-model POTENTIALLY REPLACED BY=
 draft-ietf-ccamp-otn-g709-<u></u>info-model<br>
 =A0 =A0draft-berger-ccamp-assoc-info POTENTIALLY REPLACED BY draft-ietf-cc=
amp-assoc-info<br>
 =A0 =A0draft-bernstein-ccamp-wson-<u></u>signaling POTENTIALLY REPLACED BY=
 draft-ietf-ccamp-wson-<u></u>signaling<br>
<br>
FORCES Working Group, RTG Area<br>
 =A0 =A0draft-hadi-forces-sctptml POTENTIALLY REPLACED BY draft-ietf-forces=
-sctptml<br>
 =A0 =A0draft-haleplidis-forces-<u></u>implementation-experience POTENTIALL=
Y REPLACED BY draft-ietf-forces-<u></u>implementation-experience<br>
<br>
IDR Working Group, RTG Area<br>
 =A0 =A0draft-decraene-idr-reserved-<u></u>extended-communities POTENTIALLY=
 REPLACED BY draft-ietf-idr-reserved-<u></u>extended-communities<br>
 =A0 =A0draft-keyupate-idr-bgp-gr-<u></u>notification POTENTIALLY REPLACED =
BY draft-ietf-idr-bgp-gr-<u></u>notification<br>
 =A0 =A0draft-keyur-idr-enhanced-gr POTENTIALLY REPLACED BY draft-ietf-idr-=
enhanced-gr<br>
 =A0 =A0draft-raszuk-idr-flow-spec-v6 POTENTIALLY REPLACED BY draft-ietf-id=
r-flow-spec-v6<br>
 =A0 =A0draft-wkumari-idr-as0 POTENTIALLY REPLACED BY draft-ietf-idr-as0<br=
>
<br>
ISIS Working Group, RTG Area<br>
 =A0 =A0draft-chopps-isis-bfd-tlv POTENTIALLY REPLACED BY draft-ietf-isis-b=
fd-tlv<br>
 =A0 =A0draft-ginsberg-isis-genapp POTENTIALLY REPLACED BY draft-ietf-isis-=
genapp<br>
 =A0 =A0draft-previdi-isis-mi POTENTIALLY REPLACED BY draft-ietf-isis-mi<br=
>
 =A0 =A0draft-shen-isis-oper-enhance POTENTIALLY REPLACED BY draft-ietf-isi=
s-oper-enhance<br>
<br>
L2VPN Working Group, RTG Area<br>
 =A0 =A0draft-delord-l2vpn-ldp-vpls-<u></u>broadcast-exten POTENTIALLY REPL=
ACED BY draft-ietf-l2vpn-ldp-vpls-<u></u>broadcast-exten<br>
 =A0 =A0draft-henderickx-l2vpn-vpls-<u></u>multihoming POTENTIALLY REPLACED=
 BY draft-ietf-l2vpn-vpls-<u></u>multihoming<br>
 =A0 =A0draft-key-l2vpn-etree-frwk POTENTIALLY REPLACED BY draft-ietf-l2vpn=
-etree-frwk<br>
 =A0 =A0draft-kompella-l2vpn-vpls-<u></u>multihoming POTENTIALLY REPLACED B=
Y draft-ietf-l2vpn-vpls-<u></u>multihoming<br>
 =A0 =A0draft-pdutta-l2vpn-vpls-ldp-<u></u>mac-opt POTENTIALLY REPLACED BY =
draft-ietf-l2vpn-vpls-ldp-mac-<u></u>opt<br>
 =A0 =A0draft-pkwok-l2vpn-vpls-<u></u>macflush-ld POTENTIALLY REPLACED BY d=
raft-ietf-l2vpn-vpls-<u></u>macflush-ld<br>
 =A0 =A0draft-sajassi-l2vpn-pbb-evpn POTENTIALLY REPLACED BY draft-ietf-l2v=
pn-pbb-evpn<br>
 =A0 =A0draft-sajassi-l2vpn-vpls-pbb-<u></u>interop POTENTIALLY REPLACED BY=
 draft-ietf-l2vpn-vpls-pbb-<u></u>interop<br>
<br>
L3VPN Working Group, RTG Area<br>
 =A0 =A0draft-rekhter-l3vpn-virtual-<u></u>hub POTENTIALLY REPLACED BY draf=
t-ietf-l3vpn-virtual-hub<br>
<br>
MANET Working Group, RTG Area<br>
 =A0 =A0draft-herberg-manet-nhdp-sec POTENTIALLY REPLACED BY draft-ietf-man=
et-nhdp-sec<br>
 =A0 =A0draft-herberg-manet-nhdp-sec-<u></u>threats POTENTIALLY REPLACED BY=
 draft-ietf-manet-nhdp-sec-<u></u>threats<br>
<br>
MPLS Working Group, RTG Area<br>
 =A0 =A0draft-frost-mpls-tp-loss-<u></u>delay-profile POTENTIALLY REPLACED =
BY draft-ietf-mpls-tp-loss-delay-<u></u>profile<br>
 =A0 =A0draft-koike-mpls-tp-temporal-<u></u>hitless-psm POTENTIALLY REPLACE=
D BY draft-ietf-mpls-tp-temporal-<u></u>hitless-psm<br>
 =A0 =A0draft-liu-mpls-tp-ring-<u></u>protection POTENTIALLY REPLACED BY dr=
aft-ietf-mpls-tp-ring-<u></u>protection<br>
 =A0 =A0draft-raggarwa-mpls-seamless-<u></u>mcast POTENTIALLY REPLACED BY d=
raft-ietf-mpls-seamless-mcast<br>
<br>
OSPF Working Group, RTG Area<br>
 =A0 =A0draft-acee-ospf-multi-instance POTENTIALLY REPLACED BY draft-ietf-o=
spf-multi-instance<br>
 =A0 =A0draft-acee-ospf-transport-<u></u>instance POTENTIALLY REPLACED BY d=
raft-ietf-ospf-transport-<u></u>instance<br>
 =A0 =A0draft-cheng-ospf-ipv4-<u></u>embedded-ipv6-routing POTENTIALLY REPL=
ACED BY draft-ietf-ospf-ipv4-embedded-<u></u>ipv6-routing<br>
 =A0 =A0draft-nguyen-ospf-lls POTENTIALLY REPLACED BY draft-ietf-ospf-lls<b=
r>
 =A0 =A0draft-nsheth-ospf-hybrid-<u></u>bcast-and-p2mp POTENTIALLY REPLACED=
 BY draft-ietf-ospf-hybrid-bcast-<u></u>and-p2mp<br>
 =A0 =A0draft-ogier-ospf-dbex-opt POTENTIALLY REPLACED BY draft-ietf-ospf-d=
bex-opt<br>
 =A0 =A0draft-retana-ospf-rfc3137bis POTENTIALLY REPLACED BY draft-ietf-osp=
f-rfc3137bis<br>
 =A0 =A0draft-venkata-ospf-dynamic-<u></u>hostname POTENTIALLY REPLACED BY =
draft-ietf-ospf-dynamic-<u></u>hostname<br>
<br>
PCE Working Group, RTG Area<br>
 =A0 =A0draft-tang-pce-stateful-pce POTENTIALLY REPLACED BY draft-ietf-pce-=
stateful-pce<br>
 =A0 =A0draft-zhao-pce-pcep-inter-<u></u>domain-p2mp-procedures POTENTIALLY=
 REPLACED BY draft-ietf-pce-pcep-inter-<u></u>domain-p2mp-procedures<br>
<br>
PIM Working Group, RTG Area<br>
 =A0 =A0draft-hou-pim-drlb POTENTIALLY REPLACED BY draft-ietf-pim-drlb<br>
<br>
PWE3 Working Group, RTG Area<br>
 =A0 =A0draft-bryant-pwe3-packet-pw POTENTIALLY REPLACED BY draft-ietf-pwe3=
-packet-pw<br>
 =A0 =A0draft-delregno-pwe3-pw-vccv-<u></u>impl-survey-results POTENTIALLY =
REPLACED BY draft-ietf-pwe3-pw-vccv-impl-<u></u>survey-results<br>
 =A0 =A0draft-jin-pwe3-cbit-<u></u>negotiation POTENTIALLY REPLACED BY draf=
t-ietf-pwe3-cbit-<u></u>negotiation<br>
 =A0 =A0draft-raza-pwe3-pw-typed-wc-<u></u>fec POTENTIALLY REPLACED BY draf=
t-ietf-pwe3-pw-typed-wc-<u></u>fec<br>
<br>
ROLL Working Group, RTG Area<br>
 =A0 =A0draft-dt-roll-p2p-rpl POTENTIALLY REPLACED BY draft-ietf-roll-p2p-r=
pl<br>
 =A0 =A0draft-gnawali-roll-minrank-<u></u>hysteresis-of POTENTIALLY REPLACE=
D BY draft-ietf-roll-minrank-<u></u>hysteresis-of<br>
 =A0 =A0draft-goyal-roll-p2p-<u></u>measurement POTENTIALLY REPLACED BY dra=
ft-ietf-roll-p2p-<u></u>measurement<br>
 =A0 =A0draft-levis-roll-trickle POTENTIALLY REPLACED BY draft-ietf-roll-tr=
ickle<br>
 =A0 =A0draft-popa-roll-applicability-<u></u>ami POTENTIALLY REPLACED BY dr=
aft-ietf-roll-applicability-<u></u>ami<br>
 =A0 =A0draft-tsao-roll-security-<u></u>framework POTENTIALLY REPLACED BY d=
raft-ietf-roll-security-<u></u>framework<br>
<br>
RTGWG Working Group, RTG Area<br>
 =A0 =A0draft-atlas-rtgwg-mrt-frr-<u></u>architecture POTENTIALLY REPLACED =
BY draft-ietf-rtgwg-mrt-frr-<u></u>architecture<br>
<br>
------------------------------<u></u>------------------------------<u></u>-=
----<br>
SEC Area<br>
------------------------------<u></u>------------------------------<u></u>-=
----<br>
ABFAB Working Group, SEC Area<br>
 =A0 =A0draft-lear-abfab-arch POTENTIALLY REPLACED BY draft-ietf-abfab-arch=
<br>
<br>
HOKEY Working Group, SEC Area<br>
 =A0 =A0draft-wu-hokey-rfc5296bis POTENTIALLY REPLACED BY draft-ietf-hokey-=
rfc5296bis<br>
<br>
MILE Working Group, SEC Area<br>
 =A0 =A0draft-moriarty-mile-grc-<u></u>exchange POTENTIALLY REPLACED BY dra=
ft-ietf-mile-grc-exchange<br>
<br>
NEA Working Group, SEC Area<br>
 =A0 =A0draft-hanna-nea-pt-eap POTENTIALLY REPLACED BY draft-ietf-nea-pt-ea=
p<br>
 =A0 =A0draft-sangster-nea-pt-tls POTENTIALLY REPLACED BY draft-ietf-nea-pt=
-tls<br>
<br>
OAUTH Working Group, SEC Area<br>
 =A0 =A0draft-mortimore-oauth-<u></u>assertions POTENTIALLY REPLACED BY dra=
ft-ietf-oauth-assertions<br>
<br>
PKIX Working Group, SEC Area<br>
 =A0 =A0draft-cooper-pkix-rfc2560bis POTENTIALLY REPLACED BY draft-ietf-pki=
x-rfc2560bis<br>
 =A0 =A0draft-cooper-pkix-rfc5280-<u></u>clarifications POTENTIALLY REPLACE=
D BY draft-ietf-pkix-rfc5280-<u></u>clarifications<br>
 =A0 =A0draft-santesson-pkix-certimage POTENTIALLY REPLACED BY draft-ietf-p=
kix-certimage<br>
<br>
TLS Working Group, SEC Area<br>
 =A0 =A0draft-kanno-tls-camellia POTENTIALLY REPLACED BY draft-ietf-tls-cam=
ellia<br>
 =A0 =A0draft-rescorla-tls-suiteb POTENTIALLY REPLACED BY draft-ietf-tls-su=
iteb<br>
 =A0 =A0draft-seggelmann-tls-dtls-<u></u>heartbeat POTENTIALLY REPLACED BY =
draft-ietf-tls-dtls-heartbeat<br>
<br>
------------------------------<u></u>------------------------------<u></u>-=
----<br>
TSV Area<br>
------------------------------<u></u>------------------------------<u></u>-=
----<br>
ALTO Working Group, TSV Area<br>
 =A0 =A0draft-song-alto-server-<u></u>discovery POTENTIALLY REPLACED BY dra=
ft-ietf-alto-server-<u></u>discovery<br>
 =A0 =A0draft-stiemerling-alto-<u></u>deployments POTENTIALLY REPLACED BY d=
raft-ietf-alto-deployments<br>
<br>
BEHAVE Working Group, TSV Area<br>
 =A0 =A0draft-liu-behave-ftp64 POTENTIALLY REPLACED BY draft-ietf-behave-ft=
p64<br>
 =A0 =A0draft-penno-behave-64-analysis POTENTIALLY REPLACED BY draft-ietf-b=
ehave-64-analysis<br>
<br>
CDNI Working Group, TSV Area<br>
 =A0 =A0draft-watson-cdni-use-cases POTENTIALLY REPLACED BY draft-ietf-cdni=
-use-cases<br>
<br>
CONEX Working Group, TSV Area<br>
 =A0 =A0draft-krishnan-conex-destopt POTENTIALLY REPLACED BY draft-ietf-con=
ex-destopt<br>
 =A0 =A0draft-kuehlewind-conex-tcp-<u></u>modifications POTENTIALLY REPLACE=
D BY draft-ietf-conex-tcp-<u></u>modifications<br>
 =A0 =A0draft-mathis-conex-abstract-<u></u>mech POTENTIALLY REPLACED BY dra=
ft-ietf-conex-abstract-mech<br>
 =A0 =A0draft-moncaster-conex-<u></u>concepts-uses POTENTIALLY REPLACED BY =
draft-ietf-conex-concepts-uses<br>
<br>
DECADE Working Group, TSV Area<br>
 =A0 =A0draft-alimi-decade-arch POTENTIALLY REPLACED BY draft-ietf-decade-a=
rch<br>
 =A0 =A0draft-chen-decade-integration-<u></u>example POTENTIALLY REPLACED B=
Y draft-ietf-decade-integration-<u></u>example<br>
 =A0 =A0draft-huang-decade-<u></u>integration-example POTENTIALLY REPLACED =
BY draft-ietf-decade-integration-<u></u>example<br>
<br>
FECFRAME Working Group, TSV Area<br>
 =A0 =A0draft-roca-fecframe-ldpc POTENTIALLY REPLACED BY draft-ietf-fecfram=
e-ldpc<br>
 =A0 =A0draft-roca-fecframe-simple-rs POTENTIALLY REPLACED BY draft-ietf-fe=
cframe-simple-rs<br>
<br>
IPPM Working Group, TSV Area<br>
 =A0 =A0draft-baillargeon-ippm-twamp-<u></u>value-added-octets POTENTIALLY =
REPLACED BY draft-ietf-ippm-twamp-value-<u></u>added-octets<br>
 =A0 =A0draft-geib-ippm-metrictest POTENTIALLY REPLACED BY draft-ietf-ippm-=
metrictest<br>
 =A0 =A0draft-morton-ippm-rt-loss POTENTIALLY REPLACED BY draft-ietf-ippm-r=
t-loss<br>
 =A0 =A0draft-morton-ippm-testplan-<u></u>rfc2679 POTENTIALLY REPLACED BY d=
raft-ietf-ippm-testplan-<u></u>rfc2679<br>
<br>
NFSV4 Working Group, TSV Area<br>
 =A0 =A0draft-alexrn-nfsv4-ipv6 POTENTIALLY REPLACED BY draft-ietf-nfsv4-ip=
v6<br>
 =A0 =A0draft-dnoveck-nfsv4-migration-<u></u>issues POTENTIALLY REPLACED BY=
 draft-ietf-nfsv4-migration-<u></u>issues<br>
 =A0 =A0draft-eisler-nfsv4-<u></u>minorversion-2-requirements POTENTIALLY R=
EPLACED BY draft-ietf-nfsv4-minorversion-<u></u>2-requirements<br>
 =A0 =A0draft-faibish-nfsv4-pnfs-<u></u>access-permissions-check POTENTIALL=
Y REPLACED BY draft-ietf-nfsv4-pnfs-access-<u></u>permissions-check<br>
 =A0 =A0draft-faibish-nfsv4-pnfs-<u></u>block-disk-protection POTENTIALLY R=
EPLACED BY draft-ietf-nfsv4-pnfs-block-<u></u>disk-protection<br>
 =A0 =A0draft-haynes-nfsv4-<u></u>minorversion2 POTENTIALLY REPLACED BY dra=
ft-ietf-nfsv4-minorversion2<br>
 =A0 =A0draft-haynes-nfsv4-<u></u>minorversion2-dot-x POTENTIALLY REPLACED =
BY draft-ietf-nfsv4-<u></u>minorversion2-dot-x<br>
 =A0 =A0draft-quigley-nfsv4-labreqs POTENTIALLY REPLACED BY draft-ietf-nfsv=
4-labreqs<br>
<br>
PCN Working Group, TSV Area<br>
 =A0 =A0draft-karagiannis-pcn-<u></u>signaling-requirements POTENTIALLY REP=
LACED BY draft-ietf-pcn-signaling-<u></u>requirements<br>
<br>
PPSP Working Group, TSV Area<br>
 =A0 =A0draft-gu-ppsp-peer-protocol POTENTIALLY REPLACED BY draft-ietf-ppsp=
-peer-protocol<br>
 =A0 =A0draft-gu-ppsp-survey POTENTIALLY REPLACED BY draft-ietf-ppsp-survey=
<br>
<br>
TCPM Working Group, TSV Area<br>
 =A0 =A0draft-blanton-tcpm-3517bis POTENTIALLY REPLACED BY draft-ietf-tcpm-=
3517bis<br>
 =A0 =A0draft-cheng-tcpm-fastopen POTENTIALLY REPLACED BY draft-ietf-tcpm-f=
astopen<br>
 =A0 =A0draft-gont-tcpm-rfc1948bis POTENTIALLY REPLACED BY draft-ietf-tcpm-=
rfc1948bis<br>
 =A0 =A0draft-henderson-tcpm-rfc3782-<u></u>bis POTENTIALLY REPLACED BY dra=
ft-ietf-tcpm-rfc3782-bis<br>
 =A0 =A0draft-hkchu-tcpm-initcwnd POTENTIALLY REPLACED BY draft-ietf-tcpm-i=
nitcwnd<br>
 =A0 =A0draft-mathis-tcpm-<u></u>proportional-rate-reduction POTENTIALLY RE=
PLACED BY draft-ietf-tcpm-proportional-<u></u>rate-reduction<br>
 =A0 =A0draft-touch-tcpm-experimental-<u></u>options POTENTIALLY REPLACED B=
Y draft-ietf-tcpm-experimental-<u></u>options<br>
<br>
TSVWG Working Group, TSV Area<br>
 =A0 =A0draft-gont-tsvwg-source-quench POTENTIALLY REPLACED BY draft-ietf-t=
svwg-source-quench<br>
 =A0 =A0draft-polk-tsvwg-intserv-<u></u>multiple-tspec POTENTIALLY REPLACED=
 BY draft-ietf-tsvwg-intserv-<u></u>multiple-tspec<br>
<br>
------------------------------<u></u>------------------------------<u></u>-=
----<br>
Potential Inconsistencies<br>
------------------------------<u></u>------------------------------<u></u>-=
----<br>
draft-ietf-6lowpan-nd may replace one or more of 2 individual IDs - check t=
his<br>
draft-ietf-armd-problem-<u></u>statement may replace one or more of 2 indiv=
idual IDs - check this<br>
draft-ietf-avt-rtp-gsm-hr may replace one or more of 3 individual IDs - che=
ck this<br>
draft-ietf-avt-rtp-svc may replace one or more of 2 individual IDs - check =
this<br>
draft-ietf-bmwg-ipflow-meth may replace one or more of 2 individual IDs - c=
heck this<br>
draft-ietf-cdni-use-cases may replace one or more of 2 individual IDs - che=
ck this<br>
draft-ietf-decade-integration-<u></u>example may replace one or more of 2 i=
ndividual IDs - check this<br>
draft-ietf-decade-survey may replace one or more of 2 individual IDs - chec=
k this<br>
draft-ietf-dhc-dhcpv4-bulk-<u></u>leasequery may replace one or more of 2 i=
ndividual IDs - check this<br>
draft-ietf-forces-tmlsp may replace one or more of 2 individual IDs - check=
 this<br>
draft-ietf-ipfix-biflow may replace one or more of 2 individual IDs - check=
 this<br>
draft-ietf-l2tpext-tdm may replace one or more of 2 individual IDs - check =
this<br>
draft-ietf-l2vpn-vpls-<u></u>multihoming may replace one or more of 2 indiv=
idual IDs - check this<br>
draft-ietf-mpls-tp-fault may replace one or more of 2 individual IDs - chec=
k this<br>
draft-ietf-mpls-tp-ring-<u></u>protection may replace one or more of 2 indi=
vidual IDs - check this<br>
draft-ietf-netconf-monitoring may replace one or more of 2 individual IDs -=
 check this<br>
draft-ietf-netlmm-lma-<u></u>discovery may replace one or more of 2 individ=
ual IDs - check this<br>
draft-ietf-netlmm-mip-<u></u>interactions may replace one or more of 2 indi=
vidual IDs - check this<br>
draft-ietf-pce-stateful-pce may replace one or more of 2 individual IDs - c=
heck this<br>
draft-ietf-sip-saml may replace one or more of 2 individual IDs - check thi=
s<br>
draft-ietf-sipping-service-<u></u>identification may replace one or more of=
 2 individual IDs - check this<br>
draft-ietf-softwire-dslite-<u></u>deployment may replace one or more of 2 i=
ndividual IDs - check this<br>
draft-ietf-trill-rbridge-arch may replace one or more of 2 individual IDs -=
 check this<br>
<br>
</blockquote>
</div></div></blockquote></div><br>

--20cf303ea802b45d9804bdf430ed--

From trammell@tik.ee.ethz.ch  Wed Apr 18 06:42:16 2012
Return-Path: <trammell@tik.ee.ethz.ch>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 024C321F8541 for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 06:42:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J9Sz2KwRaL2Q for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 06:42:15 -0700 (PDT)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id 616A321F8531 for <wgchairs@ietf.org>; Wed, 18 Apr 2012 06:42:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id AC76ED9304; Wed, 18 Apr 2012 15:42:14 +0200 (MEST)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id DEF5DZXG0fB8; Wed, 18 Apr 2012 15:42:14 +0200 (MEST)
Received: from public-docking-etx-r-059.ethz.ch (public-docking-etx-r-059.ethz.ch [195.176.113.59]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: briant) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id 68C96D930B; Wed, 18 Apr 2012 15:42:14 +0200 (MEST)
Subject: Re: latest missing replaced-by information
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=iso-8859-1
From: Brian Trammell <trammell@tik.ee.ethz.ch>
In-Reply-To: <5EB4938E-5550-48CD-91D1-77080C2584C4@netapp.com>
Date: Wed, 18 Apr 2012 15:42:14 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <12E8767B-2A14-4363-A6C6-904D8F3CCADB@tik.ee.ethz.ch>
References: <E9354164-6546-42A9-BAC4-BE6660855AE9@netapp.com> <4F8EC284.3020301@alcatel-lucent.com> <5EB4938E-5550-48CD-91D1-77080C2584C4@netapp.com>
To: "Eggert, Lars" <lars@netapp.com>
X-Mailer: Apple Mail (2.1257)
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>, Internet Research Steering Group <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: Wed, 18 Apr 2012 13:42:16 -0000

+1; it's odd that this has to go through the ticketing system.

Cheers,

Brian

On Apr 18, 2012, at 3:39 PM, Eggert, Lars wrote:

> Hi,
>=20
> On Apr 18, 2012, at 15:32, Martin Vigoureux wrote:
>> As a side question, I was wondering if managing the "replaced by" =
status shouldn't be under the full responsibility of the chairs, i.e., a =
functionality of the datatracker rather than the chairs needing to send =
an e-mail to the secretariat for each (batch of) changes.
>> What do you think? and that question also goes to the chairs.
>=20
> well, it *is* under the control of the chairs (and ADs), except only =
via tickets to the secretariat.
>=20
> I agree that the datatracker should allow you to indicate replaced-by =
relationships, and ideally it would even nudge you occasionally about =
it. (Then I could stop sending these emails...)
>=20
> Lars


From henrik@levkowetz.com  Wed Apr 18 06:53:39 2012
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 A64DE21F8576 for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 06:53:39 -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=[AWL=0.001,  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 cBCFkrU2b+M9 for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 06:53:37 -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 B615B21F8548 for <wgchairs@ietf.org>; Wed, 18 Apr 2012 06:53:37 -0700 (PDT)
Received: from [2a01:3f0:1:0:21e:c2ff:fe13:7e3e] (port=60205 helo=brunello.netnod.se) by grenache.tools.ietf.org with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.77) (envelope-from <henrik@levkowetz.com>) id 1SKVK3-0000vt-UP; Wed, 18 Apr 2012 15:53:32 +0200
Message-ID: <4F8EC757.7090908@levkowetz.com>
Date: Wed, 18 Apr 2012 15:53:27 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.3) Gecko/20120306 Thunderbird/10.0.3
MIME-Version: 1.0
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
References: <4F8EBA7E.9050603@pi.nu> <5CF9F389-64D4-4C32-9867-ABAE4F3FE51F@kumari.net>, <4F8EBDC6.3060404@pi.nu> <CD5674C3CD99574EBA7432465FC13C1B22726A0A4C@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B22726A0A4C@DC-US1MBEX4.global.avaya.com>
X-Enigmail-Version: 1.4
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 2a01:3f0:1:0:21e:c2ff:fe13:7e3e
X-SA-Exim-Rcpt-To: dworley@avaya.com, loa@pi.nu, warren@kumari.net, wgchairs@ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
Subject: Re: Warning on document dates ...
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: "wgchairs@ietf.org" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Apr 2012 13:53:39 -0000

On 2012-04-18 15:25 Worley, Dale R (Dale) said:
>> From: Loa Andersson [loa@pi.nu]
>>
>> but you get the same warning if you look at a document that is in the
>> repository and has been there for 2 months (60 days in the past) even
>> if the date was correctly set when the doc was uploaded.
> 
> I expect that is so that there doesn't have to be a way to operate the
> checker in two different modes, one when a document is being uploaded,
> and one for other times.

Bingo! :-)


Best regards,

	Henrik


From adam@nostrum.com  Wed Apr 18 07:03:53 2012
Return-Path: <adam@nostrum.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE68321F854F for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 07:03:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.496
X-Spam-Level: 
X-Spam-Status: No, score=-102.496 tagged_above=-999 required=5 tests=[AWL=0.104, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UEeLeTUwWig4 for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 07:03:53 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 7483121F84BF for <wgchairs@ietf.org>; Wed, 18 Apr 2012 07:03:53 -0700 (PDT)
Received: from dn3-228.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q3IE3m8n031984 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 18 Apr 2012 09:03:48 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <4F8EC9C4.2080303@nostrum.com>
Date: Wed, 18 Apr 2012 09:03:48 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Warren Kumari <warren@kumari.net>
Subject: Re: Warning on document dates ...
References: <4F8EBA7E.9050603@pi.nu> <5CF9F389-64D4-4C32-9867-ABAE4F3FE51F@kumari.net>
In-Reply-To: <5CF9F389-64D4-4C32-9867-ABAE4F3FE51F@kumari.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: 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, 18 Apr 2012 14:03:54 -0000

On 4/18/12 8:01 AM, Warren Kumari wrote:
> I've often accidentally tried to upload a document that I've just edited and forgotten to bump the date field

By the way, with the latest set of tools, all the parameters in the date 
field are optional, and default to this year/this month/today. So you 
can avoid this problem in particular by simply adding an element like 
"<date/>", and the xml2rfc tools will take care of figuring out today's 
date for you.

/a

From A.Hoenes@TR-Sys.de  Wed Apr 18 07:20:10 2012
Return-Path: <A.Hoenes@TR-Sys.de>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A307621F858D for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 07:20:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.043
X-Spam-Level: 
X-Spam-Status: No, score=-98.043 tagged_above=-999 required=5 tests=[AWL=0.706, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5WPDV0qGSU5y for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 07:20:09 -0700 (PDT)
Received: from TR-Sys.de (gateway.tr-sys.de [213.178.172.147]) by ietfa.amsl.com (Postfix) with ESMTP id 77ACC21F85BB for <wgchairs@ietf.org>; Wed, 18 Apr 2012 07:20:08 -0700 (PDT)
Received: from ZEUS.TR-Sys.de by w. with ESMTP ($Revision: 1.37.109.26 $/16.3.2) id AA097228732; Wed, 18 Apr 2012 16:18:52 +0200
Received: (from ah@localhost) by z.TR-Sys.de (8.9.3 (PHNE_25183)/8.7.3) id QAA27098; Wed, 18 Apr 2012 16:18:51 +0200 (MESZ)
From: Alfred =?hp-roman8?B?SM5uZXM=?= <ah@TR-Sys.de>
Message-Id: <201204181418.QAA27098@TR-Sys.de>
Subject: Re: latest missing replaced-by information
To: wgchairs@ietf.org
Date: Wed, 18 Apr 2012 16:18:51 +0200 (MESZ)
In-Reply-To: <12E8767B-2A14-4363-A6C6-904D8F3CCADB@tik.ee.ethz.ch> from Brian Trammell at Apr "18, " 2012 "03:42:14" pm
X-Mailer: ELM [$Revision: 1.17.214.3 $]
Mime-Version: 1.0
Content-Type: text/plain; charset=hp-roman8
Content-Transfer-Encoding: 8bit
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Apr 2012 14:20:10 -0000

RFC 6175 (WG Datatracker requirements) in Section 6.2 talks about...

|  This will facilitate the Datatracker's ability to correctly
|  capture "Replaces" information for WG drafts and "Replaced by"
|  information for the individual submission I-Ds that are replaced
|  by WG drafts.

This is written in the context of pre-approval of WG drafts
before submission (which so far seems not to be implemented
in the Datatracker WG Chair user interface), but in the
discussion on the draft for RFC 6175, IIRC it was clear that
during approval of a WG -00 draft, a Chair needs to be able to
supply the "Replaces" metadata -- or correct the preliminary
guesses made by the system.  Somehow, this seems to have been
lost during operation on the many change requests on the draft,
but IMHO this requirement is implied in RFC 6175.
It also has been discussed in the draft stage of RFC 6175 that
the I-D upload tool should allow an I-D submitter to supply
"replaces" metadata, without leading to manual processing
of the submission by the Secretariat (as is the case for all
metadata changes intended by the submitter); in the case of a
WG draft adoption( WG -00 draft), the WG Chair UI then should
allow to edit these metadata (if needed) before accepting the
submission.

I haven't a useful example at hands currently to exercise the
procedure, but from a more detailed reading of RFC 6175, it looks
like the desired functionality is seen in RFC 6175 part of WG Chair
operation on the *individual* I-Ds being adopted, not on the
'draft-ietf-' ones.

So could please someone with a pending draft adoption check whether
they can enter the "replaced by" information for the individual I-D?


Kind regards,
  Alfred HÎnes.

-- 

+------------------------+--------------------------------------------+
| TR-Sys Alfred Hoenes   |  Alfred Hoenes   Dipl.-Math., Dipl.-Phys.  |
| Gerlinger Strasse 12   |  Phone: (+49)7156/9635-0, Fax: -18         |
| D-71254  Ditzingen     |  E-Mail:  ah@TR-Sys.de                     |
+------------------------+--------------------------------------------+


From jmh@joelhalpern.com  Wed Apr 18 09:05:24 2012
Return-Path: <jmh@joelhalpern.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 4A98721E8011 for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 09:05:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.079
X-Spam-Level: 
X-Spam-Status: No, score=-102.079 tagged_above=-999 required=5 tests=[AWL=0.186, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id comh-MM9dI5b for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 09:05:23 -0700 (PDT)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 76C7821E800F for <wgchairs@ietf.org>; Wed, 18 Apr 2012 09:05:23 -0700 (PDT)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by morbo.tigertech.net (Postfix) with ESMTP id 2C3C1557FC5 for <wgchairs@ietf.org>; Wed, 18 Apr 2012 09:05:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id A48431BC9825; Wed, 18 Apr 2012 09:05:22 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [172.17.114.244] (207.47.24.2.static.nextweb.net [207.47.24.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 0AB561BC9821; Wed, 18 Apr 2012 09:05:22 -0700 (PDT)
Message-ID: <4F8EE648.8080200@joelhalpern.com>
Date: Wed, 18 Apr 2012 12:05:28 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Yaakov Stein <yaakov_s@rad.com>
Subject: Re: Formats for WG and BOF Agendas
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com> <D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com> <B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com> <66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com> <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com> <07F7D7DED63154409F13298786A2ADC904373362@EXRAD5.ad.rad.co.il>
In-Reply-To: <07F7D7DED63154409F13298786A2ADC904373362@EXRAD5.ad.rad.co.il>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Apr 2012 16:05:24 -0000

Pardon my lack of imagination, but why would minutes need diagrams?
Minutes are descriptions of what was discussed / resolved.  They are not 
intended to capture the details of the issues at the level that requires 
diagrams.

It seems to me a stretch even to need equations in minutes, although I 
suppose that is [possible.  My guess is that a crude approximation of 
the equation would suffice for minuting purposes in almost all cases.

Getting people's names right is a more meaningful issue.

Yours,
Joel

On 4/18/2012 1:03 AM, Yaakov Stein wrote:
> However, minutes may need diagrams, equations, international characters, etc.

From ajs@anvilwalrusden.com  Wed Apr 18 09:10:39 2012
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84C8D21F85E3 for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 09:10:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.749
X-Spam-Level: 
X-Spam-Status: No, score=-2.749 tagged_above=-999 required=5 tests=[AWL=-0.150, 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 CmmnTeQWSbMO for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 09:10:39 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id 1885121F8533 for <wgchairs@ietf.org>; Wed, 18 Apr 2012 09:10:39 -0700 (PDT)
Received: from mail.yitter.info (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id E96E91ECB41D for <wgchairs@ietf.org>; Wed, 18 Apr 2012 16:10:28 +0000 (UTC)
Date: Wed, 18 Apr 2012 12:10:27 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: wgchairs@ietf.org
Subject: Re: Formats for WG and BOF Agendas
Message-ID: <20120418161021.GJ94829@mail.yitter.info>
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com> <D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com> <B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com> <66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com> <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com> <07F7D7DED63154409F13298786A2ADC904373362@EXRAD5.ad.rad.co.il> <4F8EE648.8080200@joelhalpern.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4F8EE648.8080200@joelhalpern.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Apr 2012 16:10:39 -0000

On Wed, Apr 18, 2012 at 12:05:28PM -0400, Joel M. Halpern wrote:

> It seems to me a stretch even to need equations in minutes

Oh, I dunno.  A lot of WG discussions are probably most easily
summarized with something like

    A & ~A

I note, however, that you can still do that using ASCII.  So maybe we
don't need other formal logic symbols.

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From yaakov_s@rad.com  Wed Apr 18 09:16:41 2012
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 4808711E8093 for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 09:16:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.511
X-Spam-Level: 
X-Spam-Status: No, score=-102.511 tagged_above=-999 required=5 tests=[AWL=0.087, 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 znvYFqNyJgyJ for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 09:16:40 -0700 (PDT)
Received: from rad.co.il (mailrelay01.rad.co.il [62.0.23.252]) by ietfa.amsl.com (Postfix) with ESMTP id 7545711E8088 for <wgchairs@ietf.org>; Wed, 18 Apr 2012 09:16:31 -0700 (PDT)
Received: from Internal Mail-Server by MailRelay01 (envelope-from yaakov?s@rad.com) with AES128-SHA encrypted SMTP; 18 Apr 2012 19:01:09 +0300
Received: from EXRAD5.ad.rad.co.il ([192.114.24.28]) by EXRAD5.ad.rad.co.il ([192.114.24.28]) with mapi id 14.01.0323.003; Wed, 18 Apr 2012 19:16:28 +0300
From: Yaakov Stein <yaakov_s@rad.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Subject: RE: Formats for WG and BOF Agendas
Thread-Topic: Formats for WG and BOF Agendas
Thread-Index: AQHNHMx3ZRwCxvaQWEueKCwmFhNlepagBiIggACIHwCAADKBQA==
Date: Wed, 18 Apr 2012 16:16:27 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC904373A3B@EXRAD5.ad.rad.co.il>
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com> <D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com> <B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com> <66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com> <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com> <07F7D7DED63154409F13298786A2ADC904373362@EXRAD5.ad.rad.co.il> <4F8EE648.8080200@joelhalpern.com>
In-Reply-To: <4F8EE648.8080200@joelhalpern.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.17.140.53]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Commtouch-Refid: str=0001.0A020208.4F8EE8DC.016B,ss=1,fgs=0
Cc: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Apr 2012 16:16:41 -0000

For example, we want to capture in the minutes that it was decided that
the protocol should work this way <diagram> rather than the other proposal =
<diagram>.

Of course if Mr. <string of non-Latin characters> proposed that
the first parameter in <equation> should be determined by <equation>,
we would also need more than plain text.


Y(J)S




-----Original Message-----
From: Joel M. Halpern [mailto:jmh@joelhalpern.com]=20
Sent: Wednesday, April 18, 2012 19:05
To: Yaakov Stein
Cc: IETF WG Chairs
Subject: Re: Formats for WG and BOF Agendas

Pardon my lack of imagination, but why would minutes need diagrams?
Minutes are descriptions of what was discussed / resolved.  They are not=20
intended to capture the details of the issues at the level that requires=20
diagrams.

It seems to me a stretch even to need equations in minutes, although I=20
suppose that is [possible.  My guess is that a crude approximation of=20
the equation would suffice for minuting purposes in almost all cases.

Getting people's names right is a more meaningful issue.

Yours,
Joel

On 4/18/2012 1:03 AM, Yaakov Stein wrote:
> However, minutes may need diagrams, equations, international characters, =
etc.

From jmh@joelhalpern.com  Wed Apr 18 09:23:16 2012
Return-Path: <jmh@joelhalpern.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 6410421F8581 for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 09:23:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.116
X-Spam-Level: 
X-Spam-Status: No, score=-102.116 tagged_above=-999 required=5 tests=[AWL=0.149, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n-0j-8tdnXN2 for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 09:23:16 -0700 (PDT)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 0532F21F858D for <wgchairs@ietf.org>; Wed, 18 Apr 2012 09:23:15 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by morbo.tigertech.net (Postfix) with ESMTP id 398AA55812E for <wgchairs@ietf.org>; Wed, 18 Apr 2012 09:23:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 769D11C5975; Wed, 18 Apr 2012 09:23:14 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [172.17.114.244] (207.47.24.2.static.nextweb.net [207.47.24.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 519B41C0932; Wed, 18 Apr 2012 09:23:08 -0700 (PDT)
Message-ID: <4F8EEA6A.5020109@joelhalpern.com>
Date: Wed, 18 Apr 2012 12:23:06 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Yaakov Stein <yaakov_s@rad.com>
Subject: Re: Formats for WG and BOF Agendas
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com> <D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com> <B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com> <66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com> <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com> <07F7D7DED63154409F13298786A2ADC904373362@EXRAD5.ad.rad.co.il> <4F8EE648.8080200@joelhalpern.com> <07F7D7DED63154409F13298786A2ADC904373A3B@EXRAD5.ad.rad.co.il>
In-Reply-To: <07F7D7DED63154409F13298786A2ADC904373A3B@EXRAD5.ad.rad.co.il>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Apr 2012 16:23:16 -0000

Frankly, if I am taking minutes, I would much prefer to capture
The working group selected the diagram on slide 4 as a better 
description than the one on slide 5, rather than trying to figure out 
how the heck I was going to write the figure.

--  Yes, we have lost the ability to do diagrams and much of any other 
development work on the fly in working group sessions.  That is not the 
minutes problem.

Similarly for the equation, I would not want to try to recreate the 
equation in the minutes.  In both cases, if you are cutting and pasting 
from elsewhere, it is more than sufficient to put a reference to the 
"where" in the minutes.  The minutes are not themselves a working document.

I do think we should try to capture names properly, and that can be done 
by after-the-fact repairs.

Yours,
Joel

On 4/18/2012 12:16 PM, Yaakov Stein wrote:
> For example, we want to capture in the minutes that it was decided that
> the protocol should work this way<diagram>  rather than the other proposal<diagram>.
>
> Of course if Mr.<string of non-Latin characters>  proposed that
> the first parameter in<equation>  should be determined by<equation>,
> we would also need more than plain text.
>
>
> Y(J)S
>
>
>
>
> -----Original Message-----
> From: Joel M. Halpern [mailto:jmh@joelhalpern.com]
> Sent: Wednesday, April 18, 2012 19:05
> To: Yaakov Stein
> Cc: IETF WG Chairs
> Subject: Re: Formats for WG and BOF Agendas
>
> Pardon my lack of imagination, but why would minutes need diagrams?
> Minutes are descriptions of what was discussed / resolved.  They are not
> intended to capture the details of the issues at the level that requires
> diagrams.
>
> It seems to me a stretch even to need equations in minutes, although I
> suppose that is [possible.  My guess is that a crude approximation of
> the equation would suffice for minuting purposes in almost all cases.
>
> Getting people's names right is a more meaningful issue.
>
> Yours,
> Joel
>
> On 4/18/2012 1:03 AM, Yaakov Stein wrote:
>> However, minutes may need diagrams, equations, international characters, etc.
>

From yaakov_s@rad.com  Wed Apr 18 09:26:16 2012
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 32E3921F858D for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 09:26:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.519
X-Spam-Level: 
X-Spam-Status: No, score=-102.519 tagged_above=-999 required=5 tests=[AWL=0.079, 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 vlHoxwBWOzJs for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 09:26:15 -0700 (PDT)
Received: from rad.co.il (mailrelay01-q.rad.co.il [80.74.100.150]) by ietfa.amsl.com (Postfix) with ESMTP id 1533621F8581 for <wgchairs@ietf.org>; Wed, 18 Apr 2012 09:26:13 -0700 (PDT)
Received: from Internal Mail-Server by MailRelay01 (envelope-from yaakov?s@rad.com) with AES128-SHA encrypted SMTP; 18 Apr 2012 19:10: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.01.0323.003; Wed, 18 Apr 2012 19:26:11 +0300
From: Yaakov Stein <yaakov_s@rad.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Subject: RE: Formats for WG and BOF Agendas
Thread-Topic: Formats for WG and BOF Agendas
Thread-Index: AQHNHMx3ZRwCxvaQWEueKCwmFhNlepagBiIggACIHwCAADKBQP//0mwAgAAyeCA=
Date: Wed, 18 Apr 2012 16:26:10 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC904373A79@EXRAD5.ad.rad.co.il>
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com> <D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com> <B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com> <66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com> <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com> <07F7D7DED63154409F13298786A2ADC904373362@EXRAD5.ad.rad.co.il> <4F8EE648.8080200@joelhalpern.com> <07F7D7DED63154409F13298786A2ADC904373A3B@EXRAD5.ad.rad.co.il> <4F8EEA6A.5020109@joelhalpern.com>
In-Reply-To: <4F8EEA6A.5020109@joelhalpern.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.17.140.53]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Commtouch-Refid: str=0001.0A020208.4F8EEB24.003F,ss=1,fgs=0
Cc: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Apr 2012 16:26:16 -0000

I completely agree that what you suggest is easier to do,
assuming that everyone us using fancy slides.
But what happens when we use the good old fashioned method of drawing up so=
mething on a whiteboard ?
(yes, I know it is heretical to actually work on something in a WG session)

Y(J)S

-----Original Message-----
From: Joel M. Halpern [mailto:jmh@joelhalpern.com]=20
Sent: Wednesday, April 18, 2012 19:23
To: Yaakov Stein
Cc: IETF WG Chairs
Subject: Re: Formats for WG and BOF Agendas

Frankly, if I am taking minutes, I would much prefer to capture
The working group selected the diagram on slide 4 as a better=20
description than the one on slide 5, rather than trying to figure out=20
how the heck I was going to write the figure.

--  Yes, we have lost the ability to do diagrams and much of any other=20
development work on the fly in working group sessions.  That is not the=20
minutes problem.

Similarly for the equation, I would not want to try to recreate the=20
equation in the minutes.  In both cases, if you are cutting and pasting=20
from elsewhere, it is more than sufficient to put a reference to the=20
"where" in the minutes.  The minutes are not themselves a working document.

I do think we should try to capture names properly, and that can be done=20
by after-the-fact repairs.

Yours,
Joel

On 4/18/2012 12:16 PM, Yaakov Stein wrote:
> For example, we want to capture in the minutes that it was decided that
> the protocol should work this way<diagram>  rather than the other proposa=
l<diagram>.
>
> Of course if Mr.<string of non-Latin characters>  proposed that
> the first parameter in<equation>  should be determined by<equation>,
> we would also need more than plain text.
>
>
> Y(J)S
>
>
>
>
> -----Original Message-----
> From: Joel M. Halpern [mailto:jmh@joelhalpern.com]
> Sent: Wednesday, April 18, 2012 19:05
> To: Yaakov Stein
> Cc: IETF WG Chairs
> Subject: Re: Formats for WG and BOF Agendas
>
> Pardon my lack of imagination, but why would minutes need diagrams?
> Minutes are descriptions of what was discussed / resolved.  They are not
> intended to capture the details of the issues at the level that requires
> diagrams.
>
> It seems to me a stretch even to need equations in minutes, although I
> suppose that is [possible.  My guess is that a crude approximation of
> the equation would suffice for minuting purposes in almost all cases.
>
> Getting people's names right is a more meaningful issue.
>
> Yours,
> Joel
>
> On 4/18/2012 1:03 AM, Yaakov Stein wrote:
>> However, minutes may need diagrams, equations, international characters,=
 etc.
>

From jmh@joelhalpern.com  Wed Apr 18 09:30:18 2012
Return-Path: <jmh@joelhalpern.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 D679C21F8575 for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 09:30:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.141
X-Spam-Level: 
X-Spam-Status: No, score=-102.141 tagged_above=-999 required=5 tests=[AWL=0.124, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DSvYu2Me3sZ3 for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 09:30:18 -0700 (PDT)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 0852621F8570 for <wgchairs@ietf.org>; Wed, 18 Apr 2012 09:30:18 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by morbo.tigertech.net (Postfix) with ESMTP id E386055804E for <wgchairs@ietf.org>; Wed, 18 Apr 2012 09:30:17 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id C1BB61C0748; Wed, 18 Apr 2012 09:30:17 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [172.17.114.244] (207.47.24.2.static.nextweb.net [207.47.24.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 8B9F51C04E0; Wed, 18 Apr 2012 09:30:17 -0700 (PDT)
Message-ID: <4F8EEC21.8080007@joelhalpern.com>
Date: Wed, 18 Apr 2012 12:30:25 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Yaakov Stein <yaakov_s@rad.com>
Subject: Re: Formats for WG and BOF Agendas
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com> <D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com> <B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com> <66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com> <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com> <07F7D7DED63154409F13298786A2ADC904373362@EXRAD5.ad.rad.co.il> <4F8EE648.8080200@joelhalpern.com> <07F7D7DED63154409F13298786A2ADC904373A3B@EXRAD5.ad.rad.co.il> <4F8EEA6A.5020109@joelhalpern.com> <07F7D7DED63154409F13298786A2ADC904373A79@EXRAD5.ad.rad.co.il>
In-Reply-To: <07F7D7DED63154409F13298786A2ADC904373A79@EXRAD5.ad.rad.co.il>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Apr 2012 16:30:18 -0000

I don't think the minutes are the place to capture the drawing, if you 
can actually succeed in working that way.  I can think of several ways 
to deal with it, depending upon other choices.  But not the minutes. 
The simple reason is that youa re going to need to capture the diagram 
somewhere else so that the working group can actually work with it.

Yours,
Joel

On 4/18/2012 12:26 PM, Yaakov Stein wrote:
> I completely agree that what you suggest is easier to do,
> assuming that everyone us using fancy slides.
> But what happens when we use the good old fashioned method of drawing up something on a whiteboard ?
> (yes, I know it is heretical to actually work on something in a WG session)
>
> Y(J)S
>
> -----Original Message-----
> From: Joel M. Halpern [mailto:jmh@joelhalpern.com]
> Sent: Wednesday, April 18, 2012 19:23
> To: Yaakov Stein
> Cc: IETF WG Chairs
> Subject: Re: Formats for WG and BOF Agendas
>
> Frankly, if I am taking minutes, I would much prefer to capture
> The working group selected the diagram on slide 4 as a better
> description than the one on slide 5, rather than trying to figure out
> how the heck I was going to write the figure.
>
> --  Yes, we have lost the ability to do diagrams and much of any other
> development work on the fly in working group sessions.  That is not the
> minutes problem.
>
> Similarly for the equation, I would not want to try to recreate the
> equation in the minutes.  In both cases, if you are cutting and pasting
> from elsewhere, it is more than sufficient to put a reference to the
> "where" in the minutes.  The minutes are not themselves a working document.
>
> I do think we should try to capture names properly, and that can be done
> by after-the-fact repairs.
>
> Yours,
> Joel
>
> On 4/18/2012 12:16 PM, Yaakov Stein wrote:
>> For example, we want to capture in the minutes that it was decided that
>> the protocol should work this way<diagram>   rather than the other proposal<diagram>.
>>
>> Of course if Mr.<string of non-Latin characters>   proposed that
>> the first parameter in<equation>   should be determined by<equation>,
>> we would also need more than plain text.
>>
>>
>> Y(J)S
>>
>>
>>
>>
>> -----Original Message-----
>> From: Joel M. Halpern [mailto:jmh@joelhalpern.com]
>> Sent: Wednesday, April 18, 2012 19:05
>> To: Yaakov Stein
>> Cc: IETF WG Chairs
>> Subject: Re: Formats for WG and BOF Agendas
>>
>> Pardon my lack of imagination, but why would minutes need diagrams?
>> Minutes are descriptions of what was discussed / resolved.  They are not
>> intended to capture the details of the issues at the level that requires
>> diagrams.
>>
>> It seems to me a stretch even to need equations in minutes, although I
>> suppose that is [possible.  My guess is that a crude approximation of
>> the equation would suffice for minuting purposes in almost all cases.
>>
>> Getting people's names right is a more meaningful issue.
>>
>> Yours,
>> Joel
>>
>> On 4/18/2012 1:03 AM, Yaakov Stein wrote:
>>> However, minutes may need diagrams, equations, international characters, etc.
>>
>

From fred@cisco.com  Wed Apr 18 10:45:22 2012
Return-Path: <fred@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF16D21F84C9 for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 10:45:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.662
X-Spam-Level: 
X-Spam-Status: No, score=-110.662 tagged_above=-999 required=5 tests=[AWL=-0.064, 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 xrE+64NxdZgM for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 10:45:10 -0700 (PDT)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 62A5521F84D3 for <wgchairs@ietf.org>; Wed, 18 Apr 2012 10:45:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=6695; q=dns/txt; s=iport; t=1334771110; x=1335980710; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to; bh=WIfhZkfj6U0oMDIh/70JB7ju6BN43X+wLg4SKP0f+fM=; b=HwkNii3wnVu2Hdpsx1TXvVKk1ECee+3+6b1KLl6SXKuJXWIbrrnyBiDn ECFAao2jpqhbIdZRIcj79AM1MQc2Qu3vaXJdFZMleTILhT3Rj0NaVE4tm A+YAu6o3vEI7ZhCK241+M03nynE4NhR+5kgnJ9Z++lNW6jL4tfnQGpZLz 4=;
X-Files: agenda.html : 4357
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnoGAED9jk+rRDoI/2dsb2JhbABEqDgBhxaBcoEHggkBAQEEDgQBGjgCEhALGC5XBicOh2wMmnGgHY9SYwSIXIYShwGBEYRiiF6BaYMH
X-IronPort-AV: E=Sophos;i="4.75,442,1330905600";  d="html'217?scan'217,208,217";a="41034654"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-4.cisco.com with ESMTP; 18 Apr 2012 17:45:09 +0000
Received: from stealth-10-32-244-218.cisco.com (stealth-10-32-244-218.cisco.com [10.32.244.218]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id q3IHj8C7007463; Wed, 18 Apr 2012 17:45:08 GMT
Received: from [127.0.0.1] by stealth-10-32-244-218.cisco.com (PGP Universal service); Wed, 18 Apr 2012 10:45:09 -0700
X-PGP-Universal: processed; by stealth-10-32-244-218.cisco.com on Wed, 18 Apr 2012 10:45:09 -0700
Subject: Re: Formats for WG and BOF Agendas
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <89E33405ACD4F8D85C8BF282@PST.JCK.COM>
Date: Wed, 18 Apr 2012 10:44:48 -0700
Message-Id: <6FD06427-9205-4E5F-8692-1B2ADF77B287@cisco.com>
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com> <D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com> <B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com> <66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com> <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com> <89E33405ACD4F8D85C8BF282@PST.JCK.COM>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1084)
Content-Type: multipart/mixed; boundary=Apple-Mail-53--18396566
Cc: IETF WG Chairs <wgchairs@ietf.org>, Ryan Cross <rcross@amsl.com>, Russ Housley <housley@vigilsec.com>, 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, 18 Apr 2012 17:45:22 -0000

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


On Apr 17, 2012, at 1:19 PM, John C Klensin wrote:
> Russ, while I think we can safely do without PPT (or anything
> else proprietary), I'm concerned that prohibiting PDF would
> accidentally prevent the use of artwork when artwork is
> appropriate.  I think that is especially a matter of concern if
> this principle and format limitation were in the future to be
> expanded to minutes.  Now, perhaps we don't need artwork/ images
> in agendas: if everyone else is comfortable with that, then I am
> too and have no objection to restricting them to plain text and
> simple (one file) HTML.

I personally think that HTML is preferred, as it is not proprietary (PDF =
actually is, although it is commonly used and doesn't change too much) =
and allows me to put in links. I'd be hard pressed to say why images =
were needed in an agenda. The agendas I post, such as the attached, are =
the simplest possible HTML that I can think of. Yes, it's =
program-generated, from 1id-index.txt and the names of the Internet =
Drafts that will be discussed, and then edited with an HTML editor such =
as SeaMonkey.=20

I could see something a little more complex for minutes. We basically =
want a header for each discussion and then commentary on it, capturing =
important discussions, actions taken, and outcomes. I could imagine a =
lot of things, but one that would make sense to be were we to support it =
with a tool would be to start from an agenda like this and add links =
from each agenda item to slides used if any, a recording of the =
discussion, and a text summary. I would want PDF for the slides, =
mp4-or-whatever for the audio stream, and something not a lot more =
complicated than a text file for the minutes of that discussion. There =
are no doubt other ways to handle that as well, but that's one I might =
suggest.

To Russ's question, I have no problem with the proposal.


--Apple-Mail-53--18396566
Content-Disposition: attachment;
	filename=agenda.html
Content-Type: text/html;
	name="agenda.html"
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta http-equiv="content-type" content="text/html;
      charset=ISO-8859-1">
    <title>IPv6 Operations - IETF 83</title>
    <style type="text/css">
.indented
   {
   padding-left: 50pt;
   padding-right: 50pt;
   }
  </style>
  </head>
  <body>
    <h2> IPv6 Operations - IETF 83 </h2>
    <h3>Monday March 26, 9:00 </h3>
    <div class="indented">
      <dl>
        <dt><b>Agenda bashing</b></dt>
        <dd>&nbsp;</dd>
        <!-- Agenda item 1 -->
	<dt><a href="http://tools.ietf.org/html/draft-hazeyama-widecamp-ipv6-only-experience">
            <b>Experiences from IPv6-Only Networks with Transition
              Technologies in the WIDE Camp Spring 2012</b></a></dt>
        <dd> 12-Mar-12 ,
          &lt;draft-hazeyama-widecamp-ipv6-only-experience&gt;</dd>
        <!-- Agenda item 2 -->
	<dt><a href="http://tools.ietf.org/html/draft-donley-behave-deterministic-cgn">
            <b>Deterministic Address Mapping to Reduce Logging in
              Carrier Grade NAT Deployments</b></a></dt>
        <dd> 18-Jan-12 , &lt;draft-donley-behave-deterministic-cgn&gt;</dd>
        <!-- Agenda item 3 -->
	<dt><a href="http://tools.ietf.org/html/draft-chen-v6ops-nat64-experience">
            <b>NAT64 Operational Experiences</b></a></dt>
        <dd> 12-Mar-12 , &lt;draft-chen-v6ops-nat64-experience&gt;</dd>
        <!-- Agenda item 4 -->
	<dt><a href="http://tools.ietf.org/html/draft-ietf-v6ops-464xlat">
            <b>464XLAT: Combination of Stateful and Stateless
              Translation</b></a></dt>
        <dd> 12-Mar-12 , &lt;draft-ietf-v6ops-464xlat&gt;</dd>
        <dd>&nbsp;</dd>
        <!-- Agenda item 5 -->
        <dt><a href="http://tools.ietf.org/html/draft-ietf-v6ops-ivi-icmp-address">
            <b>Stateless Source Address Mapping for ICMPv6 Packets</b></a></dt>
        <dd> 24-Feb-12 , &lt;draft-ietf-v6ops-ivi-icmp-address&gt;</dd>
        <!-- Agenda item 10 -->
	<dt><a href="http://tools.ietf.org/html/draft-carpenter-v6ops-icp-guidance">
            <b>IPv6 Guidance for Internet Content and Application
              Service Providers</b></a></dt>
        <dd> 22-Feb-12 , &lt;draft-carpenter-v6ops-icp-guidance&gt;</dd>
        <!-- Agenda item 11 -->
	<dt><a href="http://tools.ietf.org/html/draft-carpenter-v6ops-label-balance">
            <b>Using the IPv6 Flow Label for Server Load Balancing</b></a></dt>
        <dd> 6-Mar-12 , &lt;draft-carpenter-v6ops-label-balance&gt;</dd>
      </dl>
    </div>
    <h3>Thursday March 29, 15:20 </h3>
    <div class="indented">
      <dl>
        <!-- Agenda item 6 -->
	<dt><a href="http://tools.ietf.org/html/draft-townsley-troan-ipv6-ce-transitioning">
            <b>Basic Requirements for Customer Edge Routers -
              multihoming and transition</b></a></dt>
        <dd> 16-Dec-11 ,
          &lt;draft-townsley-troan-ipv6-ce-transitioning&gt;</dd>
        <!-- Agenda item 7 -->
	<dt><a href="http://tools.ietf.org/html/draft-ietf-v6ops-6204bis">
            <b>Basic Requirements for IPv6 Customer Edge Routers</b></a></dt>
        <dd> 8-Mar-12 , &lt;draft-ietf-v6ops-6204bis&gt;</dd>
	<dd>&nbsp; </dd>
        <!-- Agenda item 8 -->
	<dt><a href="http://tools.ietf.org/html/draft-ietf-v6ops-ra-guard-implementation">
            <b>Implementation Advice for IPv6 Router Advertisement Guard
              (RA-Guard)</b></a></dt>
        <dd> 8-Mar-12 , &lt;draft-ietf-v6ops-ra-guard-implementation&gt;</dd>
        <!-- Agenda item 9 -->
	<dt><a href="http://tools.ietf.org/html/draft-ietf-v6ops-wireline-incremental-ipv6">
            <b>Wireline Incremental IPv6</b></a></dt>
        <dd> 1-Feb-12 ,
          &lt;draft-ietf-v6ops-wireline-incremental-ipv6&gt;</dd>
        <!-- Agenda item 12 -->
	<dt><a href="http://tools.ietf.org/html/draft-gundavelli-v6ops-community-wifi-svcs">
            <b>Service Provider Wi-Fi Services Over Residential
              Architectures</b></a></dt>
        <dd> 11-Mar-12 ,
          &lt;draft-gundavelli-v6ops-community-wifi-svcs&gt;</dd>
        <!-- Agenda item 13 -->
	<dt><a href="http://tools.ietf.org/html/draft-behringer-lla-only">
            <b>Using Only Link-Local Address in Network Core</b></a></dt>
        <dd> 5-Mar-12 , &lt;draft-behringer-lla-only&gt;</dd>
      </dl>
    </div>
  </body>
</html>

--Apple-Mail-53--18396566--

From adam@nostrum.com  Wed Apr 18 10:51:03 2012
Return-Path: <adam@nostrum.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA27B21F8555 for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 10:51:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.509
X-Spam-Level: 
X-Spam-Status: No, score=-102.509 tagged_above=-999 required=5 tests=[AWL=0.091, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IaGD0ikVzR7X for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 10:50:59 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id DEF6F21F8550 for <wgchairs@ietf.org>; Wed, 18 Apr 2012 10:50:58 -0700 (PDT)
Received: from dn3-228.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q3IHos6A071251 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 18 Apr 2012 12:50:55 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <4F8EFEFE.60302@nostrum.com>
Date: Wed, 18 Apr 2012 12:50:54 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
Subject: Re: Formats for WG and BOF Agendas
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com> <D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com> <B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com> <66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com> <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com> <89E33405ACD4F8D85C8BF282@PST.JCK.COM> <6FD06427-9205-4E5F-8692-1B2ADF77B287@cisco.com>
In-Reply-To: <6FD06427-9205-4E5F-8692-1B2ADF77B287@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: IETF WG Chairs <wgchairs@ietf.org>, Ryan Cross <rcross@amsl.com>, Russ Housley <housley@vigilsec.com>, 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, 18 Apr 2012 17:51:03 -0000

On 4/18/12 12:44 PM, Fred Baker wrote:
> I could see something a little more complex for minutes. We basically want a header for each discussion and then commentary on it, capturing important discussions, actions taken, and outcomes. I could imagine a lot of things, but one that would make sense to be were we to support it with a tool would be to start from an agenda like this and add links from each agenda item to slides used if any, a recording of the discussion, and a text summary. I would want PDF for the slides, mp4-or-whatever for the audio stream, and something not a lot more complicated than a text file for the minutes of that discussion.

Something like this?

http://www.ietf.org/proceedings/75/minutes/sipcore.html

It's not too hard to assemble something like that by hand, and HTML is 
very much up to the task. I'm not sure we really need anything more than 
the allowance of HTML as a minuting format.

/a

From fred@cisco.com  Wed Apr 18 10:53:10 2012
Return-Path: <fred@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E57421F84D2 for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 10:53:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.357
X-Spam-Level: 
X-Spam-Status: No, score=-110.357 tagged_above=-999 required=5 tests=[AWL=-0.358, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5BH6-3aYGDiB for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 10:53:06 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 6E43011E8083 for <wgchairs@ietf.org>; Wed, 18 Apr 2012 10:53:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=971; q=dns/txt; s=iport; t=1334771586; x=1335981186; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=8mNA/merCVbGKDhhzo6XzL8bm2T2//3BylE0zomfzHg=; b=BTlhphhGEkQtnKYeEk0FbO11Zt60IZHTXDK0lQWId2za5kNXUVPLnlnz R7Urul27YdbIAZA1xxedAId5aiu4q0bUHlZe9NxWjdw+JbbdsS3fFI76V coBqn9H+pDiQNSwAsrQuFB7ZsfAZORV0/j14F7PvrqQjsYuOiSZx8s2aJ w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvMFAHX+jk+rRDoJ/2dsb2JhbABEr0+BcoEHggkBAQEDARIBJz8FCwtGVwY1h2gEmwGgHY9SYwSIXI0ThXOIXoFpgwc
X-IronPort-AV: E=Sophos;i="4.75,442,1330905600"; d="scan'208";a="41127500"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-2.cisco.com with ESMTP; 18 Apr 2012 17:53:06 +0000
Received: from stealth-10-32-244-218.cisco.com (stealth-10-32-244-218.cisco.com [10.32.244.218]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id q3IHr5fW007103; Wed, 18 Apr 2012 17:53:05 GMT
Received: from [127.0.0.1] by stealth-10-32-244-218.cisco.com (PGP Universal service); Wed, 18 Apr 2012 10:53:05 -0700
X-PGP-Universal: processed; by stealth-10-32-244-218.cisco.com on Wed, 18 Apr 2012 10:53:05 -0700
Subject: Re: Formats for WG and BOF Agendas
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <07F7D7DED63154409F13298786A2ADC904373A79@EXRAD5.ad.rad.co.il>
Date: Wed, 18 Apr 2012 10:52:39 -0700
Message-Id: <C2548CC2-4AA9-4DA6-8F30-F5CEAB5A372B@cisco.com>
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com> <D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com> <B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com> <66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com> <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com> <07F7D7DED63154409F13298786A2ADC904373362@EXRAD5.ad.rad.co.il> <4F8EE648.8080200@joelhalpern.com> <07F7D7DED63154409F13298786A2ADC904373A3B@EXRAD5.ad.rad.co.il> <4F8EEA6A.5020109@joelhalpern.com> <07F7D7DED63154409F13298786A2ADC904373A79@EXRAD5.ad.rad.co.il>
To: Yaakov Stein <yaakov_s@rad.com>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Apr 2012 17:53:10 -0000

On Apr 18, 2012, at 9:26 AM, Yaakov Stein wrote:

> But what happens when we use the good old fashioned method of drawing =
up something on a whiteboard ?

I'm very much in favor of white boards. However, if we were to try to =
include them in minutes, I think the right way to do that would either =
be to use a whiteboard that can print-to-pdf its contents, or take a =
photo of it. I have used both.=20

That said, v6ops is probably a worst case, but many WGs I work in have =
the problem of "OK, we have 30 minutes to discuss <> and come to a =
resolution". In a ten person design team, it's useful to have a white =
board or whatever in the room to work through issues. With 100 people in =
the room, that can quickly become unmanageable, and can't be seen by all =
of the participants - especially remote ones. =46rom my perspective, the =
value of slides is that they are thought through in advance and don't =
have to be sketched on the fly.=

From fred@cisco.com  Wed Apr 18 11:11:37 2012
Return-Path: <fred@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B5EA21F8531 for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 11:11:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.63
X-Spam-Level: 
X-Spam-Status: No, score=-110.63 tagged_above=-999 required=5 tests=[AWL=-0.031, 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 EmLk3nSe3z8P for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 11:11:33 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id B447B21F855A for <wgchairs@ietf.org>; Wed, 18 Apr 2012 11:11:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=1052; q=dns/txt; s=iport; t=1334772690; x=1335982290; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=9A96jB1JdB0rB/uVpFEZnD2OqkhKR/CiQ4GeZ6QpMdE=; b=gSu65E5wBONIVPOkzCxd4o8AIvDeVvC5IKbFDKep/q5y4tU8vh+tLBMd xJAOss58EsudHO/wrmVjremVi6DlXg8V9GwJVpGG0A87901OHP7iFOOHI dFsDdB/6ky4x1Oi01yknJndJiOtzk81/J6ffqeSMhjZkBeRRvqY/slXYm 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvMFACsDj0+rRDoI/2dsb2JhbABEr0+BcoEHggkBAQEDARIBJz8FCwsYLlcGHBmHaAQMmnqgH49SYwSIXI0ThXOIXoFpgwc
X-IronPort-AV: E=Sophos;i="4.75,442,1330905600"; d="scan'208";a="41130717"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-2.cisco.com with ESMTP; 18 Apr 2012 18:11:30 +0000
Received: from stealth-10-32-244-218.cisco.com (stealth-10-32-244-218.cisco.com [10.32.244.218]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id q3IIAsaF026460; Wed, 18 Apr 2012 18:11:29 GMT
Received: from [127.0.0.1] by stealth-10-32-244-218.cisco.com (PGP Universal service); Wed, 18 Apr 2012 11:11:30 -0700
X-PGP-Universal: processed; by stealth-10-32-244-218.cisco.com on Wed, 18 Apr 2012 11:11:30 -0700
Subject: Re: Formats for WG and BOF Agendas
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <4F8EFEFE.60302@nostrum.com>
Date: Wed, 18 Apr 2012 11:10:08 -0700
Message-Id: <94E45014-1604-4341-A93E-BC9E47D3077D@cisco.com>
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com> <D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com> <B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com> <66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com> <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com> <89E33405ACD4F8D85C8BF282@PST.JCK.COM> <6FD06427-9205-4E5F-8692-1B2ADF77B287@cisco.com> <4F8EFEFE.60302@nostrum.com>
To: Adam Roach <adam@nostrum.com>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: IETF WG Chairs <wgchairs@ietf.org>, Ryan Cross <rcross@amsl.com>, Russ Housley <housley@vigilsec.com>, 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, 18 Apr 2012 18:11:37 -0000

On Apr 18, 2012, at 10:50 AM, Adam Roach wrote:

> On 4/18/12 12:44 PM, Fred Baker wrote:
>> I could see something a little more complex for minutes. We basically =
want a header for each discussion and then commentary on it, capturing =
important discussions, actions taken, and outcomes. I could imagine a =
lot of things, but one that would make sense to be were we to support it =
with a tool would be to start from an agenda like this and add links =
from each agenda item to slides used if any, a recording of the =
discussion, and a text summary. I would want PDF for the slides, =
mp4-or-whatever for the audio stream, and something not a lot more =
complicated than a text file for the minutes of that discussion.
>=20
> Something like this?
>=20
> http://www.ietf.org/proceedings/75/minutes/sipcore.html
>=20
> It's not too hard to assemble something like that by hand, and HTML is =
very much up to the task. I'm not sure we really need anything more than =
the allowance of HTML as a minuting format.

Pretty much.=

From vkg@bell-labs.com  Wed Apr 18 11:49:56 2012
Return-Path: <vkg@bell-labs.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B143E21F8531 for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 11:49:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.488
X-Spam-Level: 
X-Spam-Status: No, score=-107.488 tagged_above=-999 required=5 tests=[AWL=-0.889, 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 YwalvIUHBmjj for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 11:49:52 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 41E1621F8533 for <wgchairs@ietf.org>; Wed, 18 Apr 2012 11:49:52 -0700 (PDT)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id q3IInpBj013137 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <wgchairs@ietf.org>; Wed, 18 Apr 2012 13:49:51 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q3IInodI012311 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <wgchairs@ietf.org>; Wed, 18 Apr 2012 13:49:51 -0500
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.238.235]) by umail.lucent.com (8.13.8/TPES) with ESMTP id q3IInoJ1016752 for <wgchairs@ietf.org>; Wed, 18 Apr 2012 13:49:50 -0500 (CDT)
Message-ID: <4F8F0DFB.30007@bell-labs.com>
Date: Wed, 18 Apr 2012 13:54:51 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120329 Thunderbird/11.0.1
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: Formats for WG and BOF Agendas
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com> <D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com> <B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com> <66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com> <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com> <89E33405ACD4F8D85C8BF282@PST.JCK.COM> <6FD06427-9205-4E5F-8692-1B2ADF77B287@cisco.com>
In-Reply-To: <6FD06427-9205-4E5F-8692-1B2ADF77B287@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.9
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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, 18 Apr 2012 18:49:56 -0000

On 04/18/2012 12:44 PM, Fred Baker wrote:
> I could imagine a lot of things, but one that would make sense to be
> were we to support it with a tool would be to start from an agenda
> like this and add links from each agenda item to slides used if any,
> a recording of the discussion, and a text summary. I would want PDF
> for the slides, mp4-or-whatever for the audio stream, and something
> not a lot more complicated than a text file for the minutes of that
> discussion.

Fred: I have been providing exactly what you write above ---
including PDF slides and individual MP3 recordings corresponding
to each agenda item discussed during the WG meeting --- for the working
groups I chair and participate in for quite a while now.  See [1,2] for
examples.

This seem to work out well.  The minutes file has links to the
drafts, slides, and individual MP3 recording corresponding to
each WG agenda slot.  People can only download the MP3 for
a session they are interested in following instead of downloading
a large 75-400M file corresponding to the recording of the
entire session and seeking for the correct place in the recording
to find the relevant discussion of interest.

I have also worked with the folks at Meetecho to have them
split their streams into individual chunks corresponding to each
WG agenda discussion.  However, at least for now, I am still
splicing the raw MP3 audio file since (a) Meetecho does not cover
all IETF WGs, and (b) HTML5 support (for Meetecho) is not ubiquitous
across all platforms yet.  When Meetecho is available, I usually
provide both the Meetecho URLs as well as URLs to the spliced
audio; see [3] for an example.

[1] http://www.ietf.org/proceedings/83/minutes/minutes-83-alto.html
[2] http://www.ietf.org/proceedings/78/minutes/sipcore.html
[3] http://www.ietf.org/proceedings/83/minutes/minutes-83-i2aex.html

Thanks,

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

From msk@cloudmark.com  Wed Apr 18 12:17:40 2012
Return-Path: <msk@cloudmark.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 A621721F84EA for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 12:17:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.558
X-Spam-Level: 
X-Spam-Status: No, score=-102.558 tagged_above=-999 required=5 tests=[AWL=0.041, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PPyNbDVN5FRo for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 12:17:36 -0700 (PDT)
Received: from mail.cloudmark.com (cmgw1.cloudmark.com [208.83.136.25]) by ietfa.amsl.com (Postfix) with ESMTP id B267921F84D6 for <wgchairs@ietf.org>; Wed, 18 Apr 2012 12:17:36 -0700 (PDT)
Received: from ht1-outbound.cloudmark.com ([72.5.239.25]) by mail.cloudmark.com with bizsmtp id zXHr1i0010ZaKgw01XHrce; Wed, 18 Apr 2012 12:17:54 -0700
X-CMAE-Match: 0
X-CMAE-Score: 0.00
X-CMAE-Analysis: v=2.0 cv=fNu7LOme c=1 sm=1 a=LdFkGDrDWH2mcjCZERnC4w==:17 a=LvckAehuu68A:10 a=3KWvjgOOO3IA:10 a=zutiEJmiVI4A:10 a=kj9zAlcOel0A:10 a=xqWC_Br6kY4A:10 a=48vgC7mUAAAA:8 a=vQ_JypNCdMeKaK9ldioA:9 a=CjuIK1q_8ugA:10 a=lZB815dzVvQA:10 a=LdFkGDrDWH2mcjCZERnC4w==:117
Received: from EXCH-MBX901.corp.cloudmark.com ([fe80::addf:849a:f71c:4a82]) by exch-htcas901.corp.cloudmark.com ([fe80::2524:76b6:a865:539c%10]) with mapi id 14.01.0355.002; Wed, 18 Apr 2012 12:17:32 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: Brian Trammell <trammell@tik.ee.ethz.ch>, "Eggert, Lars" <lars@netapp.com>
Subject: RE: latest missing replaced-by information
Thread-Topic: latest missing replaced-by information
Thread-Index: AQHNHUArfc1edZEOVEayFUwcFf7CfZahCloAgAABxQCAAADZAP//54vw
Date: Wed, 18 Apr 2012 19:17:32 +0000
Message-ID: <9452079D1A51524AA5749AD23E0039280F855A@exch-mbx901.corp.cloudmark.com>
References: <E9354164-6546-42A9-BAC4-BE6660855AE9@netapp.com> <4F8EC284.3020301@alcatel-lucent.com> <5EB4938E-5550-48CD-91D1-77080C2584C4@netapp.com> <12E8767B-2A14-4363-A6C6-904D8F3CCADB@tik.ee.ethz.ch>
In-Reply-To: <12E8767B-2A14-4363-A6C6-904D8F3CCADB@tik.ee.ethz.ch>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.20.2.121]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudmark.com; s=default; t=1334776674; bh=/eu2ygLNhTvGqWrZXTcvNwGdcbyLJa7qOdKiBZKZsIw=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=J4V85qEfMpYtj+CQ5eKmz6o8x8MWcUVdLOw/SKZpkejkCTiPTSRWHfCrZxnStcjwu bmozlPkimo5dP6/YSNuoye2hNpriYgJsSgxjgJIJKhGkLb9EuZ5WZVndgcLNsbJ/sj CJCXYzLKlUEhiRzGgOEZFVbjOwPbrdFSCu+JT8js=
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Apr 2012 19:17:40 -0000

> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On Beh=
alf Of Brian Trammell
> Sent: Wednesday, April 18, 2012 6:42 AM
> To: Eggert, Lars
> Cc: wgchairs@ietf.org; Internet Research Steering Group
> Subject: Re: latest missing replaced-by information
>=20
> +1; it's odd that this has to go through the ticketing system.

+1 for me too.

And this new "Adopt in WG" datatracker feature is neat, but it also has a c=
ouple of issues:

1) If an AD has tagged something 'AD is watching' while it's still outside =
the WG, it can no longer be adopted into a WG via the datatracker.

2) You can do a call for adoption, and then label it an adopted document on=
ce it is.  But you can't move the document past that; the process of creati=
ng a WG-named -00 version is still a separate one.  It seems like this woul=
d be the perfect place to connect the two and add the "replaced-by" recordi=
ng step right there in the middle, which means the secretariat doesn't have=
 to do it anymore.

-MSK

From sm@elandsys.com  Wed Apr 18 12:19:20 2012
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 D3B4B11E8085 for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 12:19:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.566
X-Spam-Level: 
X-Spam-Status: No, score=-102.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fo7RNl6PM3N4 for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 12:19:14 -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 90D7D11E8080 for <wgchairs@ietf.org>; Wed, 18 Apr 2012 12:19:14 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([41.136.232.248]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q3IJIkBO027666 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 18 Apr 2012 12:19:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1334776746; i=@elandsys.com; bh=Hm5wQ98S+aRoLUHr9l5j61IapQ5IpkdVsDcL9Sperb4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=1iX0DjE7cfD3Rg5oGopHV/XUeFmE7HoMd3jWPb2SHAY+7ph1K/bEZkgYvvInrbSKy PYnQ+CfkDgHeJBDCsrHbzvoKhMu19/4lzCBKRrK4JyyKlcrk6EZLdqxfFYrLXiuwfn agXLgrL3aRWca4A5WfEJRjZMichry3go0EddTiNM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1334776746; i=@elandsys.com; bh=Hm5wQ98S+aRoLUHr9l5j61IapQ5IpkdVsDcL9Sperb4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=l8cHZ1xDKqzt6SMI/K1hc4vwjxP7ORjfM7eKBDiTU0djVe7dEX2TuHeAoVOW03N6w 8LAdAP7X5gDHYU6QRaD5tRTy4Riibh73E0Lm72mp3kKqOBzKV8QUw8H8OiWsREcztv 1LgHdW8CSLwi2/IDzZHyllupUvZOW3z5iJtNLBI0=
Message-Id: <6.2.5.6.2.20120418120507.08d284d8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 18 Apr 2012 12:17:38 -0700
To: "Vijay K. Gurbani" <vkg@bell-labs.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Formats for WG and BOF Agendas
In-Reply-To: <4F8F0DFB.30007@bell-labs.com>
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com> <D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com> <B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com> <66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com> <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com> <89E33405ACD4F8D85C8BF282@PST.JCK.COM> <6FD06427-9205-4E5F-8692-1B2ADF77B287@cisco.com> <4F8F0DFB.30007@bell-labs.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, 18 Apr 2012 19:19:20 -0000

Hi Vijay,
At 11:54 18-04-2012, Vijay K. Gurbani wrote:
>This seem to work out well.  The minutes file has links to the
>drafts, slides, and individual MP3 recording corresponding to
>each WG agenda slot.  People can only download the MP3 for
>a session they are interested in following instead of downloading
>a large 75-400M file corresponding to the recording of the
>entire session and seeking for the correct place in the recording
>to find the relevant discussion of interest.

It's an impressive piece of work.  I am curious to see (off-list) the 
raw notes taken by
Sreekanth and Markus Isomaki.  Did you use some form of 
timecoding?  How long did you take to get this work done?

Regards,
S. Moonesamy 


From vkg@bell-labs.com  Wed Apr 18 13:01:47 2012
Return-Path: <vkg@bell-labs.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5097211E8094 for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 13:01:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.399
X-Spam-Level: 
X-Spam-Status: No, score=-107.399 tagged_above=-999 required=5 tests=[AWL=-0.800, 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 hiaFulwhz+F4 for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 13:01:43 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id E762A11E809D for <wgchairs@ietf.org>; Wed, 18 Apr 2012 13:01:42 -0700 (PDT)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id q3IK1RAO002984 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 18 Apr 2012 15:01:27 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q3IK1QaK030229 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 18 Apr 2012 15:01:27 -0500
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.238.235]) by umail.lucent.com (8.13.8/TPES) with ESMTP id q3IK1P0u009444; Wed, 18 Apr 2012 15:01:26 -0500 (CDT)
Message-ID: <4F8F1EC3.4020703@bell-labs.com>
Date: Wed, 18 Apr 2012 15:06:27 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120329 Thunderbird/11.0.1
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Formats for WG and BOF Agendas
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com> <D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com> <B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com> <66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com> <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com> <89E33405ACD4F8D85C8BF282@PST.JCK.COM> <6FD06427-9205-4E5F-8692-1B2ADF77B287@cisco.com> <4F8F0DFB.30007@bell-labs.com> <6.2.5.6.2.20120418120507.08d284d8@elandnews.com>
In-Reply-To: <6.2.5.6.2.20120418120507.08d284d8@elandnews.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Apr 2012 20:01:47 -0000

On 04/18/2012 02:17 PM, S Moonesamy wrote:
> It's an impressive piece of work. I am curious to see (off-list) the
>  raw notes taken by Sreekanth and Markus Isomaki.

SM: Absolutely.  I will send these to you in private email.

> Did you use some form of timecoding?

Unfortunately, no.  It would be good if automatic markers could be
placed in the media stream, but right now that is not the case.
Most of this, right now, is manual work (more below).

I have had chats with the IETF Secretariat on automating this, but
I understand that this is a work in progress.  I have automated
some aspects of the generating the per-agenda-item MP3 file, and
I have shared the Perl scripts I wrote, and the open-source tools
I use to split/join the MP3 file etc. with the Secretariat already.

> How long did you take to get this work done?

Well, since I have been doing this for a while, it takes me < 1/2 hour
or so --- with my semi-automated tools --- to finish this.  For the WGs
that I participate in and the WGs I chair, I usually annotate start and
stop times during the WG session and these allow me to recreate easily
when a discussion started and when it ended.

For a neophyte WG chair who has never done this before, the worst case
time involvement would be equal to the time spent on hearing the large
raw MP3 audio file (usually, 1-2.5 hours) and annotating the start and
stop times of each discussion item.  Once these times are annotated, my
simple Perl script will take them as input and chop the large MP3 file
into its constituents.

Thanks,

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

From john-ietf@jck.com  Wed Apr 18 14:02:43 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D431521F848F for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 14:02:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ls0LByAABrxE for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 14:02:43 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id E469321F847F for <wgchairs@ietf.org>; Wed, 18 Apr 2012 14:02:42 -0700 (PDT)
Received: from localhost ([::1] helo=JcK-HP8200) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SKbwh-0000hj-9g; Wed, 18 Apr 2012 16:57:47 -0400
Date: Wed, 18 Apr 2012 17:02:35 -0400
From: John C Klensin <john-ietf@jck.com>
To: Fred Baker <fred@cisco.com>
Subject: Re: Formats for WG and BOF Agendas
Message-ID: <F275560B749B4A0C6D3550F2@JcK-HP8200.jck.com>
In-Reply-To: <6FD06427-9205-4E5F-8692-1B2ADF77B287@cisco.com>
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com> <D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com> <B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com> <66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com> <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com> <89E33405ACD4F8D85C8BF282@PST.JCK.COM> <6FD06427-9205-4E5F-8692-1B2ADF77B287@cisco.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF WG Chairs <wgchairs@ietf.org>, Ryan Cross <rcross@amsl.com>, Russ Housley <housley@vigilsec.com>, 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, 18 Apr 2012 21:02:44 -0000

--On Wednesday, April 18, 2012 10:44 -0700 Fred Baker
<fred@cisco.com> wrote:

> 
> On Apr 17, 2012, at 1:19 PM, John C Klensin wrote:
>> Russ, while I think we can safely do without PPT (or anything
>> else proprietary), I'm concerned that prohibiting PDF would
>> accidentally prevent the use of artwork when artwork is
>> appropriate.  I think that is especially a matter of concern
>> if this principle and format limitation were in the future to
>> be expanded to minutes.  Now, perhaps we don't need artwork/
>> images in agendas: if everyone else is comfortable with that,
>> then I am too and have no objection to restricting them to
>> plain text and simple (one file) HTML.
> 
> I personally think that HTML is preferred, as it is not
> proprietary (PDF actually is, although it is commonly used and
> doesn't change too much) and allows me to put in links. I'd be
> hard pressed to say why images were needed in an agenda. The
> agendas I post, such as the attached, are the simplest
> possible HTML that I can think of. Yes, it's
> program-generated, from 1id-index.txt and the names of the
> Internet Drafts that will be discussed, and then edited with
> an HTML editor such as SeaMonkey. 

Fred,

PDF was once, but is no longer.  As I understand it, the spec
was released to ISO some years ago along with full change
control. That makes it about as proprietary as, say, ASCII
(which also had its origins in a spec/proposal from one
company).  Like HMTL, Standard PDF is afflicted with a great
many proprietary extensions.  One of the thing that worries me
about HTML is that we are unlikely to be able and inclined to
impose and enforce conformance rules that keep files that are
"best viewed with version 1.2.3 of the FooBar browser" out of
our archives.  From the PDF side, a narrow "no extensions or
callouts allowed" definition is part of what PDF/A is all about.

HTML has one big advantage over PDF, which is that it is
plausible to assemble a relatively simple HTML file by hand,
while PDF essentially has to be compiled from some other format.
It also has one disadvantage, which is accessibility from a wide
variety of current and older tools as the standard evolves.
While absolute archival stability is the other important design
goal for PDF/A, I can only imagine what would occur if a simple,
HTML 3 or 4, rendering engine were suddenly confronted with an
input file that used many of the advanced features of HTML 5.  

If our goals for agendas include making them accessible to as
large a fraction of the community as possible, even those of us
who sometimes (or often) use older equipment and software, then
neither "PDF" nor "HTML" is a sufficient specification: for
either, we would need to specify a profile and be serious about
it, with "single file" being just the beginning.  In fairness,
that is also true of plain ASCII text because it is good to
specify line lengths and line-ending conventions and, e.g., "no
non-spacing control characters".  But that seems a little less
complex to me.

>...

 best,
    john


From jhutz@cmu.edu  Wed Apr 18 23:58:14 2012
Return-Path: <jhutz@cmu.edu>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E877521F84B4 for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 23:58:14 -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 ktOwd0vlqsnI for <wgchairs@ietfa.amsl.com>; Wed, 18 Apr 2012 23:58:14 -0700 (PDT)
Received: from smtp03.srv.cs.cmu.edu (SMTP03.SRV.CS.CMU.EDU [128.2.217.198]) by ietfa.amsl.com (Postfix) with ESMTP id 3178121F8499 for <wgchairs@ietf.org>; Wed, 18 Apr 2012 23:58:14 -0700 (PDT)
Received: from [192.168.202.157] (pool-98-111-232-78.pitbpa.fios.verizon.net [98.111.232.78]) (authenticated bits=0) by smtp03.srv.cs.cmu.edu (8.13.6/8.13.6) with ESMTP id q3J6w7LU015113 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 19 Apr 2012 02:58:08 -0400 (EDT)
Subject: Re: Formats for WG and BOF Agendas
From: Jeffrey Hutzelman <jhutz@cmu.edu>
To: John C Klensin <john-ietf@jck.com>
In-Reply-To: <6711_1334782966_q3IL2irQ020972_F275560B749B4A0C6D3550F2@JcK-HP8200.jck.com>
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com> <D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com> <B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com> <66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com> <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com> <89E33405ACD4F8D85C8BF282@PST.JCK.COM> <6FD06427-9205-4E5F-8692-1B2ADF77B287@cisco.com> <6711_1334782966_q3IL2irQ020972_F275560B749B4A0C6D3550F2@JcK-HP8200.jck.com>
Content-Type: text/plain; charset="UTF-8"
Date: Thu, 19 Apr 2012 02:58:06 -0400
Message-ID: <1334818686.21993.40.camel@destiny.pc.cs.cmu.edu>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.3 
Content-Transfer-Encoding: 7bit
X-Scanned-By: mimedefang-cmuscs on 128.2.217.198
Cc: IETF WG Chairs <wgchairs@ietf.org>, Russ Housley <housley@vigilsec.com>, Ryan Cross <rcross@amsl.com>, Henrik Levkowetz <henrik@levkowetz.com>, jhutz@cmu.edu
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Apr 2012 06:58:15 -0000

On Wed, 2012-04-18 at 17:02 -0400, John C Klensin wrote:
> 
> --On Wednesday, April 18, 2012 10:44 -0700 Fred Baker
> <fred@cisco.com> wrote:
> 
> > 
> > On Apr 17, 2012, at 1:19 PM, John C Klensin wrote:
> >> Russ, while I think we can safely do without PPT (or anything
> >> else proprietary), I'm concerned that prohibiting PDF would
> >> accidentally prevent the use of artwork when artwork is
> >> appropriate.  I think that is especially a matter of concern
> >> if this principle and format limitation were in the future to
> >> be expanded to minutes.  Now, perhaps we don't need artwork/
> >> images in agendas: if everyone else is comfortable with that,
> >> then I am too and have no objection to restricting them to
> >> plain text and simple (one file) HTML.
> > 
> > I personally think that HTML is preferred, as it is not
> > proprietary (PDF actually is, although it is commonly used and
> > doesn't change too much) and allows me to put in links. I'd be
> > hard pressed to say why images were needed in an agenda. The
> > agendas I post, such as the attached, are the simplest
> > possible HTML that I can think of. Yes, it's
> > program-generated, from 1id-index.txt and the names of the
> > Internet Drafts that will be discussed, and then edited with
> > an HTML editor such as SeaMonkey. 
> 
> Fred,
> 
> PDF was once, but is no longer.  As I understand it, the spec
> was released to ISO some years ago along with full change
> control. That makes it about as proprietary as, say, ASCII
> (which also had its origins in a spec/proposal from one
> company).  Like HMTL, Standard PDF is afflicted with a great
> many proprietary extensions.  One of the thing that worries me
> about HTML is that we are unlikely to be able and inclined to
> impose and enforce conformance rules that keep files that are
> "best viewed with version 1.2.3 of the FooBar browser" out of
> our archives.  From the PDF side, a narrow "no extensions or
> callouts allowed" definition is part of what PDF/A is all about.
> 
> HTML has one big advantage over PDF, which is that it is
> plausible to assemble a relatively simple HTML file by hand,
> while PDF essentially has to be compiled from some other format.
> It also has one disadvantage, which is accessibility from a wide
> variety of current and older tools as the standard evolves.
> While absolute archival stability is the other important design
> goal for PDF/A, I can only imagine what would occur if a simple,
> HTML 3 or 4, rendering engine were suddenly confronted with an
> input file that used many of the advanced features of HTML 5.  
> 
> If our goals for agendas include making them accessible to as
> large a fraction of the community as possible, even those of us
> who sometimes (or often) use older equipment and software, then
> neither "PDF" nor "HTML" is a sufficient specification: for
> either, we would need to specify a profile and be serious about
> it, with "single file" being just the beginning.  In fairness,
> that is also true of plain ASCII text because it is good to
> specify line lengths and line-ending conventions and, e.g., "no
> non-spacing control characters".  But that seems a little less
> complex to me.


It seems to me we are overthinking this.

For _agendas_ plain text should certainly be more than enough.  For
minutes (which, as I understand it, were not actually at issue in Russ's
original post), plain text should _still_ be enough.  It's enough for
the vast majority of our actual standards documents; it certainly ought
to be enough for minutes, which are simply a record of what happened
during a meeting(*).

Note that I didn't say plain _ASCII_.  It is certainly appropriate to
use, say, UTF-8, particularly since plenty of people's names cannot be
correctly spelled without it.  But that doesn't have to mean also
allowing all (or some) sorts of markup.

That said, the situation for some time has been that both plain text and
HTML were accepted for both agendas and minutes, and recently the tools
have started accepting things like PDF and (ugh) PowerPoint.  It
certainly seems reasonably to me to restore the previous constraint,
which after all was not lifted deliberately.




(*) Minutes are not a transcript of the meeting, or a recording of the
meeting.  They do not need to contain the content of everything that was
discussed, proposed, or adopted in the meeting.  That is what we have
internet-drafts, mailing messages, and even slides for.

Minutes should record the topics of discussion, points or issues raised
(and by whom) and how they were resolved, decisions and actions taken or
promised, and the like.

-- Jeff


From warren@kumari.net  Thu Apr 19 00:22:14 2012
Return-Path: <warren@kumari.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DED8521F84EB for <wgchairs@ietfa.amsl.com>; Thu, 19 Apr 2012 00:22:14 -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 1TqRuQ8XONsc for <wgchairs@ietfa.amsl.com>; Thu, 19 Apr 2012 00:22:13 -0700 (PDT)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by ietfa.amsl.com (Postfix) with ESMTP id DD3EC21F84E6 for <wgchairs@ietf.org>; Thu, 19 Apr 2012 00:22:12 -0700 (PDT)
Received: from [5.5.8.6] (vpn.snozzages.com [204.194.22.7]) by vimes.kumari.net (Postfix) with ESMTPSA id 844E41B40333; Thu, 19 Apr 2012 03:22:10 -0400 (EDT)
Subject: Re: Warning on document dates ...
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=windows-1252
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <4F8EC9C4.2080303@nostrum.com>
Date: Thu, 19 Apr 2012 09:22:08 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <92525B6C-FCBF-4B45-8EF9-1FE729328DEC@kumari.net>
References: <4F8EBA7E.9050603@pi.nu> <5CF9F389-64D4-4C32-9867-ABAE4F3FE51F@kumari.net> <4F8EC9C4.2080303@nostrum.com>
To: Adam Roach <adam@nostrum.com>
X-Mailer: Apple Mail (2.1257)
Cc: 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: Thu, 19 Apr 2012 07:22:15 -0000

On Apr 18, 2012, at 4:03 PM, Adam Roach wrote:

> On 4/18/12 8:01 AM, Warren Kumari wrote:
>> I've often accidentally tried to upload a document that I've just =
edited and forgotten to bump the date field
>=20
> By the way, with the latest set of tools, all the parameters in the =
date field are optional, and default to this year/this month/today. So =
you can avoid this problem in particular by simply adding an element =
like "<date/>", and the xml2rfc tools will take care of figuring out =
today's date for you.

Whoa=85. cool.

Didn't know this, that is awesome!

W


>=20
> /a
>=20


From yaakov_s@rad.com  Thu Apr 19 01:26:09 2012
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 2A76E21F85A4 for <wgchairs@ietfa.amsl.com>; Thu, 19 Apr 2012 01:26:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.526
X-Spam-Level: 
X-Spam-Status: No, score=-102.526 tagged_above=-999 required=5 tests=[AWL=0.072, 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 e9omS3DznNXQ for <wgchairs@ietfa.amsl.com>; Thu, 19 Apr 2012 01:26:08 -0700 (PDT)
Received: from rad.co.il (mailrelay02-q.rad.co.il [94.188.133.159]) by ietfa.amsl.com (Postfix) with ESMTP id E3F8C21F85A3 for <wgchairs@ietf.org>; Thu, 19 Apr 2012 01:26:05 -0700 (PDT)
Received: from Internal Mail-Server by MailRelay02 (envelope-from yaakov?s@rad.com) with AES128-SHA encrypted SMTP; 19 Apr 2012 11:12:11 +0300
Received: from EXRAD5.ad.rad.co.il ([192.114.24.28]) by EXRAD5.ad.rad.co.il ([192.114.24.28]) with mapi id 14.01.0323.003; Thu, 19 Apr 2012 11:26:02 +0300
From: Yaakov Stein <yaakov_s@rad.com>
To: Jeffrey Hutzelman <jhutz@cmu.edu>
Subject: RE: Formats for WG and BOF Agendas
Thread-Topic: Formats for WG and BOF Agendas
Thread-Index: AQHNHfnFZRwCxvaQWEueKCwmFhNlepahzwSA
Date: Thu, 19 Apr 2012 08:26:00 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC904373FC8@EXRAD5.ad.rad.co.il>
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com> <D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com> <B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com> <66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com> <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com> <89E33405ACD4F8D85C8BF282@PST.JCK.COM> <6FD06427-9205-4E5F-8692-1B2ADF77B287@cisco.com> <6711_1334782966_q3IL2irQ020972_F275560B749B4A0C6D3550F2@JcK-HP8200.jck.com> <1334818686.21993.40.camel@destiny.pc.cs.cmu.edu>
In-Reply-To: <1334818686.21993.40.camel@destiny.pc.cs.cmu.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.17.140.53]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Commtouch-Refid: str=0001.0A090206.4F8FCC1B.0034,ss=1,fgs=0
Cc: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Apr 2012 08:26:09 -0000

PiBNaW51dGVzIHNob3VsZCByZWNvcmQgdGhlIHRvcGljcyBvZiBkaXNjdXNzaW9uLCBwb2ludHMg
b3IgaXNzdWVzIHJhaXNlZA0KPiAoYW5kIGJ5IHdob20pIGFuZCBob3cgdGhleSB3ZXJlIHJlc29s
dmVkLCBkZWNpc2lvbnMgYW5kIGFjdGlvbnMgdGFrZW4gb3INCj4gcHJvbWlzZWQsIGFuZCB0aGUg
bGlrZS4NCg0KUHJlY2lzZWx5LiAgSG93ZXZlciwgaWYgeW91IGNvdWxkIGRlc2NyaWJlIGhvdyBh
biBpc3N1ZSB3YXMgcmVzb2x2ZWQgaW4gcGxhaW4gdGV4dCwNCnRoZW4gcGxhaW4gdGV4dCB3b3Vs
ZCBiZSBzdWZmaWNpZW50IGZvciBSRkNzIGFzIHdlbGwuDQpBbmQgYSBsb3Qgb2YgdXMgYmVsaWV2
ZSB0aGF0IGl0IGlzIG5vdCAoYXQgbGVhc3Qgbm90IEFMV0FZUykuDQoNClkoSilTDQo=

From loa@pi.nu  Thu Apr 19 01:28:13 2012
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 607F821F8557 for <wgchairs@ietfa.amsl.com>; Thu, 19 Apr 2012 01:28:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 Tg6qSPIed8Pk for <wgchairs@ietfa.amsl.com>; Thu, 19 Apr 2012 01:28:12 -0700 (PDT)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by ietfa.amsl.com (Postfix) with ESMTP id 9EA9921F842A for <wgchairs@ietf.org>; Thu, 19 Apr 2012 01:28:12 -0700 (PDT)
Received: from [192.168.1.64] (81-236-221-144-no93.tbcn.telia.com [81.236.221.144]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by mail.pi.nu (Postfix) with ESMTPSA id D7D682A8002; Thu, 19 Apr 2012 10:28:10 +0200 (CEST)
Message-ID: <4F8FCC96.2050002@pi.nu>
Date: Thu, 19 Apr 2012 10:28:06 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Henrik Levkowetz <henrik@levkowetz.com>
Subject: Re: Warning on document dates ...
References: <4F8EBA7E.9050603@pi.nu> <5CF9F389-64D4-4C32-9867-ABAE4F3FE51F@kumari.net>, <4F8EBDC6.3060404@pi.nu> <CD5674C3CD99574EBA7432465FC13C1B22726A0A4C@DC-US1MBEX4.global.avaya.com> <4F8EC757.7090908@levkowetz.com>
In-Reply-To: <4F8EC757.7090908@levkowetz.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Apr 2012 08:28:13 -0000

Henrik,

I guess "Bingo!" menas that the date check is meant to be used
when new documents are checked in, and if I use the nits tool
on documents already in the repository I can just drop that
info.?

/Loa

On 2012-04-18 15:53, Henrik Levkowetz wrote:
>
> On 2012-04-18 15:25 Worley, Dale R (Dale) said:
>>> From: Loa Andersson [loa@pi.nu]
>>>
>>> but you get the same warning if you look at a document that is in the
>>> repository and has been there for 2 months (60 days in the past) even
>>> if the date was correctly set when the doc was uploaded.
>>
>> I expect that is so that there doesn't have to be a way to operate the
>> checker in two different modes, one when a document is being uploaded,
>> and one for other times.
>
> Bingo! :-)
>
>
> Best regards,
>
> 	Henrik
>

-- 


Loa Andersson                         email: loa.andersson@ericsson.com
Sr Strategy and Standards Manager            loa@pi.nu
Ericsson Inc                          phone: +46 10 717 52 13
                                              +46 767 72 92 13

From ynir@checkpoint.com  Thu Apr 19 02:22:18 2012
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 8B52121F8471 for <wgchairs@ietfa.amsl.com>; Thu, 19 Apr 2012 02:22:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.546
X-Spam-Level: 
X-Spam-Status: No, score=-10.546 tagged_above=-999 required=5 tests=[AWL=0.053, 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 fk2jWxx+DxzM for <wgchairs@ietfa.amsl.com>; Thu, 19 Apr 2012 02:22:17 -0700 (PDT)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 7EAD721F846F for <wgchairs@ietf.org>; Thu, 19 Apr 2012 02:22:17 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id q3J9M8vE008804;  Thu, 19 Apr 2012 12:22:09 +0300
X-CheckPoint: {4F8FE610-2-1B221DC2-5FFFF}
Received: from il-ex03.ad.checkpoint.com (194.29.34.71) by il-ex01.ad.checkpoint.com (194.29.34.26) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 19 Apr 2012 12:22:09 +0300
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex03.ad.checkpoint.com ([194.29.34.71]) with mapi; Thu, 19 Apr 2012 12:22:07 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Jeffrey Hutzelman <jhutz@cmu.edu>
Date: Thu, 19 Apr 2012 12:22:07 +0300
Subject: Re: Formats for WG and BOF Agendas
Thread-Topic: Formats for WG and BOF Agendas
Thread-Index: Ac0eDeLmVNdLCvkjTGGokgaYyYZCXw==
Message-ID: <591C4B50-2DC1-45BB-9EE2-1A92644879D6@checkpoint.com>
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com> <D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com> <B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com> <66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com> <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com> <89E33405ACD4F8D85C8BF282@PST.JCK.COM> <6FD06427-9205-4E5F-8692-1B2ADF77B287@cisco.com> <6711_1334782966_q3IL2irQ020972_F275560B749B4A0C6D3550F2@JcK-HP8200.jck.com> <1334818686.21993.40.camel@destiny.pc.cs.cmu.edu>
In-Reply-To: <1334818686.21993.40.camel@destiny.pc.cs.cmu.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
x-cpdlp: 11f40c79bf0f5265972bcea0fcd3b0b44aa7e46906
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-KSE-AntiSpam-Interceptor-Info: protection disabled
Cc: IETF WG Chairs <wgchairs@ietf.org>, Russ Housley <housley@vigilsec.com>, 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, 19 Apr 2012 09:22:18 -0000

SGkgSmVmZnJleQ0KDQpPbiBBcHIgMTksIDIwMTIsIGF0IDk6NTggQU0sIEplZmZyZXkgSHV0emVs
bWFuIHdyb3RlOg0KDQo+IEl0IHNlZW1zIHRvIG1lIHdlIGFyZSBvdmVydGhpbmtpbmcgdGhpcy4N
Cj4gDQo+IEZvciBfYWdlbmRhc18gcGxhaW4gdGV4dCBzaG91bGQgY2VydGFpbmx5IGJlIG1vcmUg
dGhhbiBlbm91Z2guICBGb3INCj4gbWludXRlcyAod2hpY2gsIGFzIEkgdW5kZXJzdGFuZCBpdCwg
d2VyZSBub3QgYWN0dWFsbHkgYXQgaXNzdWUgaW4gUnVzcydzDQo+IG9yaWdpbmFsIHBvc3QpLCBw
bGFpbiB0ZXh0IHNob3VsZCBfc3RpbGxfIGJlIGVub3VnaC4gIEl0J3MgZW5vdWdoIGZvcg0KPiB0
aGUgdmFzdCBtYWpvcml0eSBvZiBvdXIgYWN0dWFsIHN0YW5kYXJkcyBkb2N1bWVudHM7IGl0IGNl
cnRhaW5seSBvdWdodA0KPiB0byBiZSBlbm91Z2ggZm9yIG1pbnV0ZXMsIHdoaWNoIGFyZSBzaW1w
bHkgYSByZWNvcmQgb2Ygd2hhdCBoYXBwZW5lZA0KPiBkdXJpbmcgYSBtZWV0aW5nKCopLg0KPiAN
Cj4gTm90ZSB0aGF0IEkgZGlkbid0IHNheSBwbGFpbiBfQVNDSUlfLiAgSXQgaXMgY2VydGFpbmx5
IGFwcHJvcHJpYXRlIHRvDQo+IHVzZSwgc2F5LCBVVEYtOCwgcGFydGljdWxhcmx5IHNpbmNlIHBs
ZW50eSBvZiBwZW9wbGUncyBuYW1lcyBjYW5ub3QgYmUNCj4gY29ycmVjdGx5IHNwZWxsZWQgd2l0
aG91dCBpdC4gIEJ1dCB0aGF0IGRvZXNuJ3QgaGF2ZSB0byBtZWFuIGFsc28NCj4gYWxsb3dpbmcg
YWxsIChvciBzb21lKSBzb3J0cyBvZiBtYXJrdXAuDQoNCkkgaGF2ZSBubyBvYmplY3Rpb24gdG8g
VVRGLTggaW5zdGVhZCBvZiBBU0NJSSwgYnV0IEkgZGlzYWdyZWUgd2l0aCB0aGUgc3RhdGVtZW50
IHRoYXQgcGxlbnR5IG9mIHBlb3BsZSdzIG5hbWVzIGNhbm5vdCBiZSBzcGVsbGVkIHdpdGhvdXQg
aXQuDQoNClN1cmUsIEkgd291bGQgYmUgdGhyaWxsZWQgaWYgYSBtZW50aW9uIG9mIG15IG5hbWUg
dXNlcyB0aGUgY29ycmVjdCBjaGFyYWN0ZXJzLCBidXQgaGVyZSdzIGEgYml0IGZyb20gdGhlIElQ
c2VjTUUgbWludXRlcyBmcm9tIFBhcmlzLCB3aGljaCBJIG1vZGlmaWVkIHRvIHN1cHBvcnQgVVRG
LTg6DQoNCgkjIDIxOSBTdGFyIHRvcG9sb2d5IGFzIGFuIGFkbWluIGNob2ljZQ0KCQlQZW9wbGUg
ZG9uJ3QgbmVlZCB0byB1c2UgdGhpcyBpZiB0aGV5IGRvbid0IHdhbnQgdG8NCgkJU2F5IHRoaXMg
aW4gdGhlIHNlY3VyaXR5IGNvbnNpZGVyYXRpb25zDQoJCdeZ15XXkNeRINeg15nXqDoNCgkJCUhh
cyB0byBiZSBhIHJlcXVpcmVtZW50IHRoYXQgYW55IHNvbHV0aW9uIGNhbiBpbXBsZW1lbnQgZGlm
ZmVyZW50IHBvbGljaWVzDQoJCdeZ16jXldefINep16TXqDoNCgkJCUFncmVlcyB3aXRoINeZ15XX
kNeRLCBtYXliZSBiZWNvbWVzIGEgdXNlIGNhc2UNCgkJCVRha2UgdGhpcyB0byB0aGUgbGlzdA0K
DQpJcyB0aGlzIHJlYWRhYmxlIHRvIHlvdT8gIFdvdWxkIGEgYnVuY2ggb2YgQ3lyaWxsaWMsIEdy
ZWVrLCBDaGluZXNlIG9yIEFyYWJpYyBjaGFyYWN0ZXJzIGJlIGFueSBiZXR0ZXI/ICBUaGUgYWdl
bmRhcyBhbmQgbWludXRlcyBhcmUgaW4gRW5nbGlzaCwgc28gd2UncmUgYW55d2F5IGdvaW5nIHRv
IHJlbmRlciB0aGUgbmFtZXMgaW4gRW5nbGlzaC4gU3VyZSwgc29tZWJvZHkgZnJvbSBmcmFuY2Ug
bmFtZWQgRnJhbsOnb2lzIG1heSBwcmVmZXIgdGhhdCBoaXMgbmFtZSBub3QgYmUgc3BlbGxlZCBG
cmFuY29pcywgYnV0IHRoYXQncyBqdXN0IGJlY2F1c2UgdGhlIEVuZ2xpc2ggcmVuZGl0aW9uIGxv
b2tzIHNvIGNsb3NlIHRvIHRoZSBGcmVuY2gsIG5vdCBiZWNhdXNlIEZyZW5jaCBwZW9wbGUgbmVl
ZCB0aGVpciBuYW1lcyByZW5kZXJlZCBwcm9wZXJseSBtb3JlIHRoYW4gQ2hpbmVzZSBwZW9wbGUu
DQoNCkkgaGF2ZSBubyBwcmVmZXJlbmNlIGZvciBBU0NJSSBhcyBvcHBvc2VkIHRvIFVURi04Lg0K
DQpZb2F2DQoNCg==

From henrik@levkowetz.com  Thu Apr 19 02:36:10 2012
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 67A8B21F84EE for <wgchairs@ietfa.amsl.com>; Thu, 19 Apr 2012 02:36:10 -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=[AWL=0.000,  BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bHvzaIwPNVm5 for <wgchairs@ietfa.amsl.com>; Thu, 19 Apr 2012 02:36:09 -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 C1F3021F84CD for <wgchairs@ietf.org>; Thu, 19 Apr 2012 02:36:09 -0700 (PDT)
Received: from [2a01:3f0:1:0:21e:c2ff:fe13:7e3e] (port=49231 helo=brunello.netnod.se) by grenache.tools.ietf.org with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.77) (envelope-from <henrik@levkowetz.com>) id 1SKnmV-0000mG-RM; Thu, 19 Apr 2012 11:36:08 +0200
Message-ID: <4F8FDC81.6080406@levkowetz.com>
Date: Thu, 19 Apr 2012 11:36:01 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.3) Gecko/20120306 Thunderbird/10.0.3
MIME-Version: 1.0
To: Loa Andersson <loa@pi.nu>
References: <4F8EBA7E.9050603@pi.nu> <5CF9F389-64D4-4C32-9867-ABAE4F3FE51F@kumari.net>, <4F8EBDC6.3060404@pi.nu> <CD5674C3CD99574EBA7432465FC13C1B22726A0A4C@DC-US1MBEX4.global.avaya.com> <4F8EC757.7090908@levkowetz.com> <4F8FCC96.2050002@pi.nu>
In-Reply-To: <4F8FCC96.2050002@pi.nu>
X-Enigmail-Version: 1.4
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 2a01:3f0:1:0:21e:c2ff:fe13:7e3e
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: Warning on document dates ...
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: "wgchairs@ietf.org" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Apr 2012 09:36:10 -0000

Hi Loa,

On 2012-04-19 10:28 Loa Andersson said:
> Henrik,
> 
> I guess "Bingo!" menas that the date check is meant to be used
> when new documents are checked in, and if I use the nits tool
> on documents already in the repository I can just drop that
> info.?

Yes.  The observation that idnits makes is clearly correct, but also
clearly not relevant in that case.


Best regards,

	Henrik

> /Loa
> 
> On 2012-04-18 15:53, Henrik Levkowetz wrote:
>>
>> On 2012-04-18 15:25 Worley, Dale R (Dale) said:
>>>> From: Loa Andersson [loa@pi.nu]
>>>>
>>>> but you get the same warning if you look at a document that is in the
>>>> repository and has been there for 2 months (60 days in the past) even
>>>> if the date was correctly set when the doc was uploaded.
>>>
>>> I expect that is so that there doesn't have to be a way to operate the
>>> checker in two different modes, one when a document is being uploaded,
>>> and one for other times.
>>
>> Bingo! :-)
>>
>>
>> Best regards,
>>
>> 	Henrik
>>
> 

From adrian@olddog.co.uk  Thu Apr 19 04:20:20 2012
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 8F15E21F85EA for <wgchairs@ietfa.amsl.com>; Thu, 19 Apr 2012 04:20:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.855
X-Spam-Level: 
X-Spam-Status: No, score=-1.855 tagged_above=-999 required=5 tests=[AWL=0.745,  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 YpWtx+A1tXZA for <wgchairs@ietfa.amsl.com>; Thu, 19 Apr 2012 04:20:19 -0700 (PDT)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id 6353821F85C5 for <wgchairs@ietf.org>; Thu, 19 Apr 2012 04:20:19 -0700 (PDT)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id q3JBKCpN022254;  Thu, 19 Apr 2012 12:20:12 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id q3JBKApo022189 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 19 Apr 2012 12:20:11 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Russ Housley'" <housley@vigilsec.com>, "'IETF WG Chairs'" <wgchairs@ietf.org>
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com>	<D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com>	<B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com>	<66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com> <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com>
In-Reply-To: <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com>
Subject: RE: Formats for WG and BOF Agendas
Date: Thu, 19 Apr 2012 12:20:15 +0100
Message-ID: <0e3201cd1e1e$66184090$3248c1b0$@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: AQIz34898AChCwJRktwawtQJxykupwGmPNxzAe7YkV8Ckvo8QwCgoy+rlZ42umA=
Content-Language: en-gb
Cc: 'Ryan Cross' <rcross@amsl.com>, 'Henrik Levkowetz' <henrik@levkowetz.com>
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, 19 Apr 2012 11:20:20 -0000

I have read this thread and strongly support agendas being limited to text or
html. I encourage chairs to use html so that links to I-Ds and slides can be
embedded to make the meeting easier to participate in.

I also support minutes being limited to text or html. I hear the claim that
diagrams or equations may need to be captured in minutes, but I have not
experienced this need in my time at the IETF and I suspect that:
- it is rare
- it can usually be handled by ASCII-art
- it is not a big deal for the exceptional case to be handled through
   the submission of in I-D with a PDF variant

Thanks,
Adrian

> -----Original Message-----
> From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of Russ
> Housley
> Sent: 17 April 2012 20:00
> To: IETF WG Chairs
> Cc: Ryan Cross; Henrik Levkowetz
> Subject: Formats for WG and BOF Agendas
> 
> Some WG and BOF chairs have been posting agendas in many different formats,
> including text, html, pdf, ppt, and pptx.  Until recently, only .txt and .html
files
> were supported  for session minutes and agendas.  In fact the support for the
> other formats was never announced, but you guys found the new capability
> without any announcement.
> 
> Magnus Westerlund has asked that links to meeting agendas and minutes be
> long-term persistent.  He would like a URL that works regardless of the
format.  I
> support this request, and the Secretariat tells me that it would not difficult
to
> support, especially if text and html are the only formats that we accept.  It
is
> possible to make this approach work for PDF and PPT files as well, but the
> Secretariat feels that .txt and .html files integrate into the website better
than
> the other formats.  In addition, Henrik points out that the use of PDF and PPT
files
> will make it harder to provide inline agendas in the Datatracker.
> 
> I propose that we to revert to supporting only .txt and .html file types for
session
> minutes and agendas.  Then, using Apache's content negotiation, the
Secretariat
> can link to them with an extension-less URL.  Apache will set the appropriate
> content-type.  This way the URLs will be persistent and consistent across
> supported file formats.
> 
> Does anyone have concerns with the proposed way forward?
> 
> Russ


From john-ietf@jck.com  Thu Apr 19 05:44:02 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DA0421F85C3 for <wgchairs@ietfa.amsl.com>; Thu, 19 Apr 2012 05:44:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jjclOr4eYy1O for <wgchairs@ietfa.amsl.com>; Thu, 19 Apr 2012 05:43:58 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 3D18B21F85C4 for <wgchairs@ietf.org>; Thu, 19 Apr 2012 05:43:58 -0700 (PDT)
Received: from localhost ([::1] helo=JcK-HP8200) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SKqdS-0002BI-Ug; Thu, 19 Apr 2012 08:38:55 -0400
Date: Thu, 19 Apr 2012 08:43:44 -0400
From: John C Klensin <john-ietf@jck.com>
To: adrian@olddog.co.uk, 'Russ Housley' <housley@vigilsec.com>, 'IETF WG Chairs' <wgchairs@ietf.org>
Subject: RE: Formats for WG and BOF Agendas
Message-ID: <01D86B13EFF01AE45550B050@JcK-HP8200.jck.com>
In-Reply-To: <0e3201cd1e1e$66184090$3248c1b0$@olddog.co.uk>
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com> <D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com> <B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com> <66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com> <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com> <0e3201cd1e1e$66184090$3248c1b0$@olddog.co.uk>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: 'Ryan Cross' <rcross@amsl.com>, '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, 19 Apr 2012 12:44:02 -0000

--On Thursday, April 19, 2012 12:20 +0100 Adrian Farrel
<adrian@olddog.co.uk> wrote:

> I have read this thread and strongly support agendas being
> limited to text or html. I encourage chairs to use html so
> that links to I-Ds and slides can be embedded to make the
> meeting easier to participate in.

Just an observation about the "so links can be embedded" reason
for permitting HTML...  I have never had any trouble putting
URIs into text files, nor with using those links once they are
inserted.  As a trivial example, http://www.ietf.org/ goes
perfectly well into this text/plain message.  

I'm not opposed to html if we impose a fairly simple profile on
its use.  Certainly it has advantages over plain text including
flexible formatting.  I just don't want to force readers into
use of browsers to read agendas nor to exaggerate the advantages.

    john


From jhutz@cmu.edu  Thu Apr 19 07:03:27 2012
Return-Path: <jhutz@cmu.edu>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C2F321F85F7 for <wgchairs@ietfa.amsl.com>; Thu, 19 Apr 2012 07:03:27 -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 Lxi2mdOoi-hk for <wgchairs@ietfa.amsl.com>; Thu, 19 Apr 2012 07:03:26 -0700 (PDT)
Received: from smtp01.srv.cs.cmu.edu (SMTP01.SRV.CS.CMU.EDU [128.2.217.196]) by ietfa.amsl.com (Postfix) with ESMTP id 5997221F85A3 for <wgchairs@ietf.org>; Thu, 19 Apr 2012 07:03:26 -0700 (PDT)
Received: from [192.168.202.157] (pool-98-111-232-78.pitbpa.fios.verizon.net [98.111.232.78]) (authenticated bits=0) by smtp01.srv.cs.cmu.edu (8.13.6/8.13.6) with ESMTP id q3JE3K9K013401 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 19 Apr 2012 10:03:21 -0400 (EDT)
Subject: RE: Formats for WG and BOF Agendas
From: Jeffrey Hutzelman <jhutz@cmu.edu>
To: Yaakov Stein <yaakov_s@rad.com>
In-Reply-To: <07F7D7DED63154409F13298786A2ADC904373FC8@EXRAD5.ad.rad.co.il>
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com> <D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com> <B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com> <66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com> <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com> <89E33405ACD4F8D85C8BF282@PST.JCK.COM> <6FD06427-9205-4E5F-8692-1B2ADF77B287@cisco.com> <6711_1334782966_q3IL2irQ020972_F275560B749B4A0C6D3550F2@JcK-HP8200.jck.com> <1334818686.21993.40.camel@destiny.pc.cs.cmu.edu> <07F7D7DED63154409F13298786A2ADC904373FC8@EXRAD5.ad.rad.co.il>
Content-Type: text/plain; charset="UTF-8"
Date: Thu, 19 Apr 2012 10:03:18 -0400
Message-ID: <1334844198.21993.46.camel@destiny.pc.cs.cmu.edu>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.3 
Content-Transfer-Encoding: 7bit
X-Scanned-By: mimedefang-cmuscs on 128.2.217.196
Cc: IETF WG Chairs <wgchairs@ietf.org>, jhutz@cmu.edu
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Apr 2012 14:03:27 -0000

On Thu, 2012-04-19 at 08:26 +0000, Yaakov Stein wrote:
> > Minutes should record the topics of discussion, points or issues raised
> > (and by whom) and how they were resolved, decisions and actions taken or
> > promised, and the like.
> 
> Precisely.  However, if you could describe how an issue was resolved in plain text,
> then plain text would be sufficient for RFCs as well.

Not necessarily.  Minutes should record that a resolution was reached,
and which one, but should _not_ contain a detailed description of the
resolution.  Save that for the internet-draft and resulting RFC.

If _that_ requires more than plain text, so be it.  I'll argue against
relying too heavily on non-textual information in RFCs and especially in
protocol specifications, but I won't argue for prohibiting it.

-- Jeff


From pkyzivat@alum.mit.edu  Thu Apr 19 07:08:37 2012
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 9E06421F860F for <wgchairs@ietfa.amsl.com>; Thu, 19 Apr 2012 07:08:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.532
X-Spam-Level: 
X-Spam-Status: No, score=-2.532 tagged_above=-999 required=5 tests=[AWL=0.067,  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 pFk2tsUw-BEV for <wgchairs@ietfa.amsl.com>; Thu, 19 Apr 2012 07:08:37 -0700 (PDT)
Received: from qmta13.westchester.pa.mail.comcast.net (qmta13.westchester.pa.mail.comcast.net [76.96.59.243]) by ietfa.amsl.com (Postfix) with ESMTP id 8AA2621F8604 for <wgchairs@ietf.org>; Thu, 19 Apr 2012 07:08:36 -0700 (PDT)
Received: from omta19.westchester.pa.mail.comcast.net ([76.96.62.98]) by qmta13.westchester.pa.mail.comcast.net with comcast id zp2u1i00427AodY5Dq8cti; Thu, 19 Apr 2012 14:08:36 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([24.62.229.5]) by omta19.westchester.pa.mail.comcast.net with comcast id zq8d1i00G07duvL3fq8dZB; Thu, 19 Apr 2012 14:08:37 +0000
Message-ID: <4F901C62.4030007@alum.mit.edu>
Date: Thu, 19 Apr 2012 10:08:34 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: Formats for WG and BOF Minutes
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com> <D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com> <B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com> <66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com> <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com> <89E33405ACD4F8D85C8BF282@PST.JCK.COM> <6FD06427-9205-4E5F-8692-1B2ADF77B287@cisco.com> <6711_1334782966_q3IL2irQ020972_F275560B749B4A0C6D3550F2@JcK-HP8200.jck.com> <1334818686.21993.40.camel@destiny.pc.cs.cmu.edu>
In-Reply-To: <1334818686.21993.40.camel@destiny.pc.cs.cmu.edu>
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: Thu, 19 Apr 2012 14:08:37 -0000

Changing the subject to match the content

On 4/19/12 2:58 AM, Jeffrey Hutzelman wrote:

> It seems to me we are overthinking this.
>
> For _agendas_ plain text should certainly be more than enough.  For
> minutes (which, as I understand it, were not actually at issue in Russ's
> original post), plain text should _still_ be enough.  It's enough for
> the vast majority of our actual standards documents; it certainly ought
> to be enough for minutes, which are simply a record of what happened
> during a meeting(*).
>
> Note that I didn't say plain _ASCII_.  It is certainly appropriate to
> use, say, UTF-8, particularly since plenty of people's names cannot be
> correctly spelled without it.  But that doesn't have to mean also
> allowing all (or some) sorts of markup.

My concern is that we minimize the hassle of both taking raw notes and 
assembling them into minutes.

In the groups I chair, and those I frequent and take notes for, we have 
not put any particular or strong requirements on the tools and formats 
that notes takers use. Some do it in text in the body of a mail message. 
Some use html in the body of an email. Some use other tools, including 
Word. Its easier to get note takers if they can use the tools they are 
comfortable with, and the notes are probably better that way too.

At ietf meetings I personally use MSWord to take my own notes. I prep in 
advance of the meeting, deriving a template doc from the agendas for the 
sessions I plan to attend. That makes it easier to keep up with live 
discussion. I find Word preferable here because its easier for me to 
delineate things, make lists, etc. When I am designated note taker for a 
session I take notes in the same way, but with more care than otherwise. 
Then after the meeting I tidy it up a bit to be readable by someone 
other than me, snip out the notes for the session and send them in - 
usually converted to text.

When assembling minutes for a session I chair, I have been assembling 
the raw notes from note takers, into a Word document, reformat and tweak 
as necessary, and then exporting that as an html document. I have been 
using Word because its fairly easy to import whatever notes I get into 
it and its fairly easy to reformat. I do however appreciate that there 
are a lot of options in going from Word to html that can affect how good 
the html is. And I may not be doing that optimally.

It would be more work to take that stuff and reformat it into raw text.

The above is not as easy as I might hope, but it isn't a large job. I'd 
appreciate something that was easier, but not rules that make it harder.

	Thanks,
	Paul

From randy_presuhn@mindspring.com  Thu Apr 19 08:34:58 2012
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 5885F21F86AB for <wgchairs@ietfa.amsl.com>; Thu, 19 Apr 2012 08:34:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.123
X-Spam-Level: 
X-Spam-Status: No, score=-100.123 tagged_above=-999 required=5 tests=[AWL=0.062, BAYES_40=-0.185, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h5Wts2oOBQYZ for <wgchairs@ietfa.amsl.com>; Thu, 19 Apr 2012 08:34:53 -0700 (PDT)
Received: from elasmtp-mealy.atl.sa.earthlink.net (elasmtp-mealy.atl.sa.earthlink.net [209.86.89.69]) by ietfa.amsl.com (Postfix) with ESMTP id 85DEE21F869E for <wgchairs@ietf.org>; Thu, 19 Apr 2012 08:34:53 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=JIFxIP7G/Ul2dGBGTsNFYwgo4SF6JQ3PamKlrmpO7I+PS4ArioL76K93sU0tUcJe; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [99.187.237.246] (helo=oemcomputer) by elasmtp-mealy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1SKtNd-0008DL-Gr for wgchairs@ietf.org; Thu, 19 Apr 2012 11:34:45 -0400
Message-ID: <001c01cd1e42$1ec1bae0$6b01a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "IETF WG Chairs" <wgchairs@ietf.org>
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com><D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com><B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com><66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com><EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com><89E33405ACD4F8D85C8BF282@PST.JCK.COM><6FD06427-9205-4E5F-8692-1B2ADF77B287@cisco.com><6711_1334782966_q3IL2irQ020972_F275560B749B4A0C6D3550F2@JcK-HP8200.jck.com><1334818686.21993.40.camel@destiny.pc.cs.cmu.edu> <07F7D7DED63154409F13298786A2ADC904373FC8@EXRAD5.ad.rad.co.il>
Subject: Re: Formats for WG and BOF Agendas
Date: Thu, 19 Apr 2012 08:35:57 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d8882951211ce6890f880ab74c18979e2383b2226df9ca9eeaae350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.187.237.246
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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, 19 Apr 2012 15:34:58 -0000

Hi -

> From: "Yaakov Stein" <yaakov_s@rad.com>
> To: "Jeffrey Hutzelman" <jhutz@cmu.edu>
> Cc: "IETF WG Chairs" <wgchairs@ietf.org>
> Sent: Thursday, April 19, 2012 1:26 AM
> Subject: RE: Formats for WG and BOF Agendas
>
> > Minutes should record the topics of discussion, points or issues raised
> > (and by whom) and how they were resolved, decisions and actions taken or
> > promised, and the like.
> 
> Precisely.  However, if you could describe how an issue was resolved in plain text,
> then plain text would be sufficient for RFCs as well.
> And a lot of us believe that it is not (at least not ALWAYS).

To me it seems that if the resolution cannot be described in plain text,
it's not adequately understood, and should be recorded as an action item
for the person or design team claiming to understand the resolution to post
that understanding to the WG mailing list.

Randy


From adrian@olddog.co.uk  Thu Apr 19 13:31:17 2012
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 D83C911E80A3; Thu, 19 Apr 2012 13:31:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.351
X-Spam-Level: 
X-Spam-Status: No, score=-2.351 tagged_above=-999 required=5 tests=[AWL=0.248,  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 byglG3TIFGEL; Thu, 19 Apr 2012 13:31:17 -0700 (PDT)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id 0690C11E808D; Thu, 19 Apr 2012 13:31:16 -0700 (PDT)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id q3JKVFo5008539;  Thu, 19 Apr 2012 21:31:15 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id q3JKVA9d008506 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 19 Apr 2012 21:31:12 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ietf@ietf.org>, <wgchairs@ietf.org>
Subject: Proposed IESG Statement on the Conclusion of Experiments
Date: Thu, 19 Apr 2012 21:31:14 +0100
Message-ID: <0f6601cd1e6b$5ff2e420$1fd8ac60$@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: Ac0ea1trQ6bEEENVRsKUUaoiCTZbyg==
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, 19 Apr 2012 20:31:18 -0000

All,

The IESG has been discussing how to tidy up after Experimental RFCs.

We have developed the following draft IESG statement. This does not 
represent a change in process, and continues to value Experimental RFCs
as an important part of the IETF process. It does, however, seek to 
encourage documentation of the conclusion of experiments.

We are aware that there may be other discussion points around 
Experimental RFCs, and we would like to discuss these, but we also
believe that there is merit in making small, incremental improvements.

The IESG would welcome your thoughts on this draft before they approve
the final text on April 26th.

Thanks,
Adrian

=============

IESG Statement on Conclusion of IETF Experiments


Experiments are an established and valuable part of the IETF process.
A number of core Internet protocols were first published as Experimental
RFCs while the community gathered experience and carefully investigated
the consequences of deploying new mechanisms within the Internet.

In the case where an experiment leads on to the development of a      
Standards Track RFC documenting a protocol, the new RFC obsoletes the 
old Experimental RFC and there is a clear conclusion to the experiment.

However, many experiments do not lead to the development of Standards
Track RFCs. Instead, the work may be abandoned through lack of interest
or because important lessons have been learned.

It is currently hard to distinguish between an experiment that is still
being investigated, and an old experiment that has ceased to be of
interest to the community. In both cases an Experimental RFC exists in
the repository and newcomers might easily be misled into thinking that
it would be helpful to conduct more research into an abandoned
experiment.

In view of this, the original proponents of experiments (that is, 
authors of Experimental RFCs, and Working Groups that requested the
publication of Experimental RFCs) are strongly encouraged to document
the termination of experiments that do not result in subsequent
Standards Track work by publishing an Informational RFC that:

- very briefly describes the results of the experiment

- obsoletes the Experimental RFC

- if appropriate, deprecate any IANA code points allocated for the 
  experiment

- may request that the Experimental RFC is moved to Historic status.

If there is no energy in the community for the producing such an
Informational RFC, if the authors have moved on to other things, or if
the Working Group has been closed down, Area Directors should author or
seek volunteers to author such an Informational RFC.


From lear@cisco.com  Thu Apr 19 13:39:01 2012
Return-Path: <lear@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DB9D11E80A3; Thu, 19 Apr 2012 13:39:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.247
X-Spam-Level: 
X-Spam-Status: No, score=-110.247 tagged_above=-999 required=5 tests=[AWL=0.352, 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 Ohy2cqrMCWAY; Thu, 19 Apr 2012 13:39:00 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 0F95C21F862F; Thu, 19 Apr 2012 13:38:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=lear@cisco.com; l=3406; q=dns/txt; s=iport; t=1334867940; x=1336077540; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=rA0KWKx4s22YJ16Wm5hWr4WbhskzJ6yiK04aSpcWO6A=; b=MKS/pkdhuE5GDNw92XcqDjX7/Rg6yowbjv8ZuNVxVyYkt9qhANUot41+ xvbMc7onmYGOv9xtNe4kXL8rRyB3b033Q8TPDU9SFpDKuc2NegkCknBlT RW2QzcuFdjUhdxR8tAGyrdAKzkPTYQ7+SZXIPyH3p9PzFyHg3oKznezm1 Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFALx3kE+Q/khN/2dsb2JhbABDhWarYYEHggkBAQEEEgEQVQEQCxgCAgUWCwICCQMCAQIBRRMBBwEBEA6HbZsLjRCTB4EvjiCBGASVb45SgWmCaQ
X-IronPort-AV: E=Sophos;i="4.75,447,1330905600"; d="scan'208";a="135699781"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-1.cisco.com with ESMTP; 19 Apr 2012 20:38:38 +0000
Received: from ams3-vpn-dhcp4371.cisco.com (ams3-vpn-dhcp4371.cisco.com [10.61.81.18]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id q3JKcclE018457; Thu, 19 Apr 2012 20:38:38 GMT
Message-ID: <4F9077CE.4050400@cisco.com>
Date: Thu, 19 Apr 2012 22:38:38 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: adrian@olddog.co.uk
Subject: Re: Proposed IESG Statement on the Conclusion of Experiments
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk>
In-Reply-To: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk>
X-Enigmail-Version: 1.4
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: wgchairs@ietf.org, ietf@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Apr 2012 20:39:01 -0000

Hi Adrian,

I do not support such a view, and it is not supported in a plain reading
of RFC 2026.  What's more, it's not how researchers work.  Researchers
naturally move on.  If we are looking to further push researchers away
from the IRTF, this is a good way to do it.

Whether or not an experiment is active is also not how research works. 
Sometimes work is taken up after years of gaps.  ILNP is a good example
of this.  Had 8+8 been published in a timely fashion as an experimental
RFC, we would have had obsoleted it, only to then unobsolete it?

Eliot

On 4/19/12 10:31 PM, Adrian Farrel wrote:
> All,
>
> The IESG has been discussing how to tidy up after Experimental RFCs.
>
> We have developed the following draft IESG statement. This does not 
> represent a change in process, and continues to value Experimental RFCs
> as an important part of the IETF process. It does, however, seek to 
> encourage documentation of the conclusion of experiments.
>
> We are aware that there may be other discussion points around 
> Experimental RFCs, and we would like to discuss these, but we also
> believe that there is merit in making small, incremental improvements.
>
> The IESG would welcome your thoughts on this draft before they approve
> the final text on April 26th.
>
> Thanks,
> Adrian
>
> =============
>
> IESG Statement on Conclusion of IETF Experiments
>
>
> Experiments are an established and valuable part of the IETF process.
> A number of core Internet protocols were first published as Experimental
> RFCs while the community gathered experience and carefully investigated
> the consequences of deploying new mechanisms within the Internet.
>
> In the case where an experiment leads on to the development of a      
> Standards Track RFC documenting a protocol, the new RFC obsoletes the 
> old Experimental RFC and there is a clear conclusion to the experiment.
>
> However, many experiments do not lead to the development of Standards
> Track RFCs. Instead, the work may be abandoned through lack of interest
> or because important lessons have been learned.
>
> It is currently hard to distinguish between an experiment that is still
> being investigated, and an old experiment that has ceased to be of
> interest to the community. In both cases an Experimental RFC exists in
> the repository and newcomers might easily be misled into thinking that
> it would be helpful to conduct more research into an abandoned
> experiment.
>
> In view of this, the original proponents of experiments (that is, 
> authors of Experimental RFCs, and Working Groups that requested the
> publication of Experimental RFCs) are strongly encouraged to document
> the termination of experiments that do not result in subsequent
> Standards Track work by publishing an Informational RFC that:
>
> - very briefly describes the results of the experiment
>
> - obsoletes the Experimental RFC
>
> - if appropriate, deprecate any IANA code points allocated for the 
>   experiment
>
> - may request that the Experimental RFC is moved to Historic status.
>
> If there is no energy in the community for the producing such an
> Informational RFC, if the authors have moved on to other things, or if
> the Working Group has been closed down, Area Directors should author or
> seek volunteers to author such an Informational RFC.
>
>

From sob@sobco.com  Thu Apr 19 13:48:17 2012
Return-Path: <sob@sobco.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 11BE311E80BD; Thu, 19 Apr 2012 13:48:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E0BSVFZeObog; Thu, 19 Apr 2012 13:48:16 -0700 (PDT)
Received: from sobco.sobco.com (unknown [136.248.127.164]) by ietfa.amsl.com (Postfix) with ESMTP id 4D9A411E80BB; Thu, 19 Apr 2012 13:48:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id 3A1F52B32EE6; Thu, 19 Apr 2012 16:48:15 -0400 (EDT)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZVu8OKSLDyCA; Thu, 19 Apr 2012 16:48:13 -0400 (EDT)
Received: from [10.0.1.11] (unknown [173.166.5.69]) by sobco.sobco.com (Postfix) with ESMTPSA id C38142B32ED8; Thu, 19 Apr 2012 16:48:13 -0400 (EDT)
Subject: Re: Proposed IESG Statement on the Conclusion of Experiments
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Scott O Bradner <sob@sobco.com>
In-Reply-To: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk>
Date: Thu, 19 Apr 2012 16:48:27 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <248A261F-D83D-4F97-8F5D-A9A0BCD2EC0D@sobco.com>
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk>
To: <adrian@olddog.co.uk>
X-Mailer: Apple Mail (2.1257)
X-Mailman-Approved-At: Thu, 19 Apr 2012 13:58:00 -0700
Cc: wgchairs@ietf.org, ietf@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Apr 2012 20:48:17 -0000

encouraging a report is fine

retracting the code points seems to add more confusion than it is worth =
unless the
code space is very tight

and I see no reason to obsolete the experimental rfc or move it to =
historic status unless the report is
that some bad thing happens when you try it out - updating the old rfc =
is fine

and I agree with Elliot about the nature of research - it is very common =
to not
reach a conclusion that something is bad (as in bad for the net) - and =
that is the
only case where I think that an experiment should be flagged as a don't =
go there situation

Scott


On Apr 19, 2012, at 4:31 PM, Adrian Farrel wrote:

> All,
>=20
> The IESG has been discussing how to tidy up after Experimental RFCs.
>=20
> We have developed the following draft IESG statement. This does not=20
> represent a change in process, and continues to value Experimental =
RFCs
> as an important part of the IETF process. It does, however, seek to=20
> encourage documentation of the conclusion of experiments.
>=20
> We are aware that there may be other discussion points around=20
> Experimental RFCs, and we would like to discuss these, but we also
> believe that there is merit in making small, incremental improvements.
>=20
> The IESG would welcome your thoughts on this draft before they approve
> the final text on April 26th.
>=20
> Thanks,
> Adrian
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> IESG Statement on Conclusion of IETF Experiments
>=20
>=20
> Experiments are an established and valuable part of the IETF process.
> A number of core Internet protocols were first published as =
Experimental
> RFCs while the community gathered experience and carefully =
investigated
> the consequences of deploying new mechanisms within the Internet.
>=20
> In the case where an experiment leads on to the development of a     =20=

> Standards Track RFC documenting a protocol, the new RFC obsoletes the=20=

> old Experimental RFC and there is a clear conclusion to the =
experiment.
>=20
> However, many experiments do not lead to the development of Standards
> Track RFCs. Instead, the work may be abandoned through lack of =
interest
> or because important lessons have been learned.
>=20
> It is currently hard to distinguish between an experiment that is =
still
> being investigated, and an old experiment that has ceased to be of
> interest to the community. In both cases an Experimental RFC exists in
> the repository and newcomers might easily be misled into thinking that
> it would be helpful to conduct more research into an abandoned
> experiment.
>=20
> In view of this, the original proponents of experiments (that is,=20
> authors of Experimental RFCs, and Working Groups that requested the
> publication of Experimental RFCs) are strongly encouraged to document
> the termination of experiments that do not result in subsequent
> Standards Track work by publishing an Informational RFC that:
>=20
> - very briefly describes the results of the experiment
>=20
> - obsoletes the Experimental RFC
>=20
> - if appropriate, deprecate any IANA code points allocated for the=20
>  experiment
>=20
> - may request that the Experimental RFC is moved to Historic status.
>=20
> If there is no energy in the community for the producing such an
> Informational RFC, if the authors have moved on to other things, or if
> the Working Group has been closed down, Area Directors should author =
or
> seek volunteers to author such an Informational RFC.
>=20


From dcrocker@bbiw.net  Thu Apr 19 13:59:58 2012
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 3D35A11E8089; Thu, 19 Apr 2012 13:59:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.932
X-Spam-Level: 
X-Spam-Status: No, score=-5.932 tagged_above=-999 required=5 tests=[AWL=-0.334, 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 A8jyNnR9WaCa; Thu, 19 Apr 2012 13:59:57 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 478D321F85FC; Thu, 19 Apr 2012 13:59:57 -0700 (PDT)
Received: from com.flipdogsolutions (adsl-67-127-58-62.dsl.pltn13.pacbell.net [67.127.58.62]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q3JKxqxl016041 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 19 Apr 2012 13:59:56 -0700
Date: Thu, 19 Apr 2012 14:00:06 -0700 (PDT)
From: Dave Crocker <dcrocker@bbiw.net>
To: Scott O Bradner <sob@sobco.com>, adrian@olddog.co.uk
Message-ID: <f8e77298-bbd5-4ad8-80df-a3c367f67d95.maildroid@localhost>
In-Reply-To: <248A261F-D83D-4F97-8F5D-A9A0BCD2EC0D@sobco.com>
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk> <248A261F-D83D-4F97-8F5D-A9A0BCD2EC0D@sobco.com>
Subject: Re: Proposed IESG Statement on the Conclusion of Experiments
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_0_1091463096.1334869207313"
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.67]); Thu, 19 Apr 2012 13:59:57 -0700 (PDT)
Cc: wgchairs@ietf.org, ietf@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Apr 2012 20:59:58 -0000

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

+1


/d

--
Dave Crocker
bbiw.net

via mobile



-----Original Message-----
From: Scott O Bradner <sob@sobco.com>
To: adrian@olddog.co.uk
Cc: wgchairs@ietf.org, ietf@ietf.org
Sent: Thu, 19 Apr 2012 1:48 PM
Subject: Re: Proposed IESG Statement on the Conclusion of Experiments

encouraging a report is fine

retracting the code points seems to add more confusion than it is worth unless the
code space is very tight

and I see no reason to obsolete the experimental rfc or move it to historic status unless the report is
that some bad thing happens when you try it out - updating the old rfc is fine

and I agree with Elliot about the nature of research - it is very common to not
reach a conclusion that something is bad (as in bad for the net) - and that is the
only case where I think that an experiment should be flagged as a don't go there situation

Scott


On Apr 19, 2012, at 4:31 PM, Adrian Farrel wrote:

> All,
> 
> The IESG has been discussing how to tidy up after Experimental RFCs.
> 
> We have developed the following draft IESG statement. This does not 
> represent a change in process, and continues to value Experimental RFCs
> as an important part of the IETF process. It does, however, seek to 
> encourage documentation of the conclusion of experiments.
> 
> We are aware that there may be other discussion points around 
> Experimental RFCs, and we would like to discuss these, but we also
> believe that there is merit in making small, incremental improvements.
> 
> The IESG would welcome your thoughts on this draft before they approve
> the final text on April 26th.
> 
> Thanks,
> Adrian
> 
> =============
> 
> IESG Statement on Conclusion of IETF Experiments
> 
> 
> Experiments are an established and valuable part of the IETF process.
> A number of core Internet protocols were first published as Experimental
> RFCs while the community gathered experience and carefully investigated
> the consequences of deploying new mechanisms within the Internet.
> 
> In the case where an experiment leads on to the development of a      
> Standards Track RFC documenting a protocol, the new RFC obsoletes the 
> old Experimental RFC and there is a clear conclusion to the experiment.
> 
> However, many experiments do not lead to the development of Standards
> Track RFCs. Instead, the work may be abandoned through lack of interest
> or because important lessons have been learned.
> 
> It is currently hard to distinguish between an experiment that is still
> being investigated, and an old experiment that has ceased to be of
> interest to the community. In both cases an Experimental RFC exists in
> the repository and newcomers might easily be misled into thinking that
> it would be helpful to conduct more research into an abandoned
> experiment.
> 
> In view of this, the original proponents of experiments (that is, 
> authors of Experimental RFCs, and Working Groups that requested the
> publication of Experimental RFCs) are strongly encouraged to document
> the termination of experiments that do not result in subsequent
> Standards Track work by publishing an Informational RFC that:
> 
> - very briefly describes the results of the experiment
> 
> - obsoletes the Experimental RFC
> 
> - if appropriate, deprecate any IANA code points allocated for the 
>  experiment
> 
> - may request that the Experimental RFC is moved to Historic status.
> 
> If there is no energy in the community for the producing such an
> Informational RFC, if the authors have moved on to other things, or if
> the Working Group has been closed down, Area Directors should author or
> seek volunteers to author such an Informational RFC.
> 


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

<div><p>+1<br/><br/><font color ="#888888"><p><br>
<font color ="#888888">/d</font></p>
<p><font color ="#888888">--</font><br>
<font color ="#888888">Dave Crocker</font><br>
<font color ="#888888"><a href="http://bbiw.net">bbiw.net</a></font></p>
<p><font color ="#888888">via mobile</font></p>
</font></p>
<br/><br/>-----Original Message-----<br/>From: Scott O Bradner &lt;sob@sobco.com&gt;<br/>To: adrian@olddog.co.uk<br/>Cc: wgchairs@ietf.org, ietf@ietf.org<br/>Sent: Thu, 19 Apr 2012 1:48 PM<br/>Subject: Re: Proposed IESG Statement on the Conclusion of Experiments<br/><br/></div><p>encouraging a report is fine&#13;<br>
&#13;<br>
retracting the code points seems to add more confusion than it is worth unless the&#13;<br>
code space is very tight&#13;<br>
&#13;<br>
and I see no reason to obsolete the experimental rfc or move it to historic status unless the report is&#13;<br>
that some bad thing happens when you try it out - updating the old rfc is fine&#13;<br>
&#13;<br>
and I agree with Elliot about the nature of research - it is very common to not&#13;<br>
reach a conclusion that something is bad (as in bad for the net) - and that is the&#13;<br>
only case where I think that an experiment should be flagged as a don't go there situation&#13;<br>
&#13;<br>
Scott&#13;<br>
&#13;<br>
&#13;<br>
On Apr 19, 2012, at 4:31 PM, Adrian Farrel wrote:&#13;<br>
&#13;<br>
&gt; All,&#13;<br>
&gt; &#13;<br>
&gt; The IESG has been discussing how to tidy up after Experimental RFCs.&#13;<br>
&gt; &#13;<br>
&gt; We have developed the following draft IESG statement. This does not &#13;<br>
&gt; represent a change in process, and continues to value Experimental RFCs&#13;<br>
&gt; as an important part of the IETF process. It does, however, seek to &#13;<br>
&gt; encourage documentation of the conclusion of experiments.&#13;<br>
&gt; &#13;<br>
&gt; We are aware that there may be other discussion points around &#13;<br>
&gt; Experimental RFCs, and we would like to discuss these, but we also&#13;<br>
&gt; believe that there is merit in making small, incremental improvements.&#13;<br>
&gt; &#13;<br>
&gt; The IESG would welcome your thoughts on this draft before they approve&#13;<br>
&gt; the final text on April 26th.&#13;<br>
&gt; &#13;<br>
&gt; Thanks,&#13;<br>
&gt; Adrian&#13;<br>
&gt; &#13;<br>
&gt; =============&#13;<br>
&gt; &#13;<br>
&gt; IESG Statement on Conclusion of IETF Experiments&#13;<br>
&gt; &#13;<br>
&gt; &#13;<br>
&gt; Experiments are an established and valuable part of the IETF process.&#13;<br>
&gt; A number of core Internet protocols were first published as Experimental&#13;<br>
&gt; RFCs while the community gathered experience and carefully investigated&#13;<br>
&gt; the consequences of deploying new mechanisms within the Internet.&#13;<br>
&gt; &#13;<br>
&gt; In the case where an experiment leads on to the development of a&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#13;<br>
&gt; Standards Track RFC documenting a protocol, the new RFC obsoletes the &#13;<br>
&gt; old Experimental RFC and there is a clear conclusion to the experiment.&#13;<br>
&gt; &#13;<br>
&gt; However, many experiments do not lead to the development of Standards&#13;<br>
&gt; Track RFCs. Instead, the work may be abandoned through lack of interest&#13;<br>
&gt; or because important lessons have been learned.&#13;<br>
&gt; &#13;<br>
&gt; It is currently hard to distinguish between an experiment that is still&#13;<br>
&gt; being investigated, and an old experiment that has ceased to be of&#13;<br>
&gt; interest to the community. In both cases an Experimental RFC exists in&#13;<br>
&gt; the repository and newcomers might easily be misled into thinking that&#13;<br>
&gt; it would be helpful to conduct more research into an abandoned&#13;<br>
&gt; experiment.&#13;<br>
&gt; &#13;<br>
&gt; In view of this, the original proponents of experiments (that is, &#13;<br>
&gt; authors of Experimental RFCs, and Working Groups that requested the&#13;<br>
&gt; publication of Experimental RFCs) are strongly encouraged to document&#13;<br>
&gt; the termination of experiments that do not result in subsequent&#13;<br>
&gt; Standards Track work by publishing an Informational RFC that:&#13;<br>
&gt; &#13;<br>
&gt; - very briefly describes the results of the experiment&#13;<br>
&gt; &#13;<br>
&gt; - obsoletes the Experimental RFC&#13;<br>
&gt; &#13;<br>
&gt; - if appropriate, deprecate any IANA code points allocated for the &#13;<br>
&gt;&nbsp; experiment&#13;<br>
&gt; &#13;<br>
&gt; - may request that the Experimental RFC is moved to Historic status.&#13;<br>
&gt; &#13;<br>
&gt; If there is no energy in the community for the producing such an&#13;<br>
&gt; Informational RFC, if the authors have moved on to other things, or if&#13;<br>
&gt; the Working Group has been closed down, Area Directors should author or&#13;<br>
&gt; seek volunteers to author such an Informational RFC.&#13;<br>
&gt; &#13;<br>
&#13;<br>
</p>

------=_Part_0_1091463096.1334869207313--

From ynir@checkpoint.com  Thu Apr 19 14:17:55 2012
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 0B24811E8073; Thu, 19 Apr 2012 14:17:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.548
X-Spam-Level: 
X-Spam-Status: No, score=-10.548 tagged_above=-999 required=5 tests=[AWL=0.051, 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 I9IIJRi8M1yT; Thu, 19 Apr 2012 14:17:54 -0700 (PDT)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 9051B11E80C0; Thu, 19 Apr 2012 14:17:53 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id q3JLHoNp016726;  Fri, 20 Apr 2012 00:17:50 +0300
X-CheckPoint: {4F908DC6-0-1B221DC2-5FFFF}
Received: from il-ex03.ad.checkpoint.com (194.29.34.71) by il-ex01.ad.checkpoint.com (194.29.34.26) with Microsoft SMTP Server (TLS) id 8.3.213.0; Fri, 20 Apr 2012 00:17:50 +0300
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex03.ad.checkpoint.com ([194.29.34.71]) with mapi; Fri, 20 Apr 2012 00:17:48 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>
Date: Fri, 20 Apr 2012 00:17:46 +0300
Subject: Re: Proposed IESG Statement on the Conclusion of Experiments
Thread-Topic: Proposed IESG Statement on the Conclusion of Experiments
Thread-Index: Ac0ecd5Y+BNIjNA1RQuA2My0QlZ8yQ==
Message-ID: <40D324FA-D3BA-47FA-AC32-E1326D6A375A@checkpoint.com>
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk>
In-Reply-To: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
x-cpdlp: 11a6178a1efeab7b8e9de27c04a9e7601a9893511f
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-KSE-AntiSpam-Interceptor-Info: protection disabled
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Apr 2012 21:17:55 -0000

RFC 2026 says this about Experimental RFCs:

   The "Experimental" designation typically denotes a specification that
   is part of some research or development effort.

However, I do not believe that this is still typical. Authors come up with =
ideas that they think are useful. If when the documents are ready for publi=
cation it is still not clear whether there are enough implementers convince=
d by the use case (some definition of running code), they are encouraged to=
 publish them as experimental rather than proposed standard.

I am the author of two Experimental RFCs. In both cases I was going for sta=
ndards track, and in both cased an AD was the document shepherd and he told=
 me to go for Experimental.=20

The first of these (4478) has three independent, interoperable implementati=
ons in shipping code, although I don't know if it's used much. I am not awa=
re of any implementations of the other one (6023), although there may be so=
me. When I asked an AD about promoting 4478 to standards track (seeing as w=
e have all this running code) his response was "why bother?" (these are thr=
ee different ADs in this story...)

Neither of these can really be called an "experiment" except in the sense o=
f "let's see if the Internet needs this specification". They may be used mo=
re later than they are now, but they're in no way stopping. I don't see why=
 we should waste precious cycles on maintaining old Experimental RFCs. Eith=
er they're in use or they're not, and a search engine can usually reveal th=
is.

It may be a good idea to have former authors or ADs or volunteers write a p=
aragraph that can be displayed on, say, the tools page for the RFC, along t=
he lines of "In seven years, this RFC has seen three independent implementa=
tions, but it is not in wide use", or "the protocol in this RFC is used eve=
rywhere on the web, and this could be progressed to PS if we had the energy=
."

I don't think we should waste our energy by creating an RFC for each of tho=
se experimental RFCs.

Yoav

On Apr 19, 2012, at 11:31 PM, Adrian Farrel wrote:

> All,
>=20
> The IESG has been discussing how to tidy up after Experimental RFCs.
>=20
> We have developed the following draft IESG statement. This does not=20
> represent a change in process, and continues to value Experimental RFCs
> as an important part of the IETF process. It does, however, seek to=20
> encourage documentation of the conclusion of experiments.
>=20
> We are aware that there may be other discussion points around=20
> Experimental RFCs, and we would like to discuss these, but we also
> believe that there is merit in making small, incremental improvements.
>=20
> The IESG would welcome your thoughts on this draft before they approve
> the final text on April 26th.
>=20
> Thanks,
> Adrian
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> IESG Statement on Conclusion of IETF Experiments
>=20
>=20
> Experiments are an established and valuable part of the IETF process.
> A number of core Internet protocols were first published as Experimental
> RFCs while the community gathered experience and carefully investigated
> the consequences of deploying new mechanisms within the Internet.
>=20
> In the case where an experiment leads on to the development of a     =20
> Standards Track RFC documenting a protocol, the new RFC obsoletes the=20
> old Experimental RFC and there is a clear conclusion to the experiment.
>=20
> However, many experiments do not lead to the development of Standards
> Track RFCs. Instead, the work may be abandoned through lack of interest
> or because important lessons have been learned.
>=20
> It is currently hard to distinguish between an experiment that is still
> being investigated, and an old experiment that has ceased to be of
> interest to the community. In both cases an Experimental RFC exists in
> the repository and newcomers might easily be misled into thinking that
> it would be helpful to conduct more research into an abandoned
> experiment.
>=20
> In view of this, the original proponents of experiments (that is,=20
> authors of Experimental RFCs, and Working Groups that requested the
> publication of Experimental RFCs) are strongly encouraged to document
> the termination of experiments that do not result in subsequent
> Standards Track work by publishing an Informational RFC that:
>=20
> - very briefly describes the results of the experiment
>=20
> - obsoletes the Experimental RFC
>=20
> - if appropriate, deprecate any IANA code points allocated for the=20
>  experiment
>=20
> - may request that the Experimental RFC is moved to Historic status.
>=20
> If there is no energy in the community for the producing such an
> Informational RFC, if the authors have moved on to other things, or if
> the Working Group has been closed down, Area Directors should author or
> seek volunteers to author such an Informational RFC.
>=20
>=20
> Scanned by Check Point Total Security Gateway.


From drc@virtualized.org  Thu Apr 19 14:17:48 2012
Return-Path: <drc@virtualized.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 46AC321E8012; Thu, 19 Apr 2012 14:17:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.556
X-Spam-Level: 
X-Spam-Status: No, score=-2.556 tagged_above=-999 required=5 tests=[AWL=0.043,  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 SsNBxfOHzynl; Thu, 19 Apr 2012 14:17:47 -0700 (PDT)
Received: from trantor.virtualized.org (trantor.virtualized.org [199.48.134.42]) by ietfa.amsl.com (Postfix) with ESMTP id 9437521E8015; Thu, 19 Apr 2012 14:17:47 -0700 (PDT)
Received: from [192.168.2.168] (unknown [173.245.57.22]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: drc) by trantor.virtualized.org (Postfix) with ESMTPSA id 57B8E1705A; Thu, 19 Apr 2012 21:17:46 +0000 (UTC)
Subject: Re: Proposed IESG Statement on the Conclusion of Experiments
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: David Conrad <drc@virtualized.org>
In-Reply-To: <f8e77298-bbd5-4ad8-80df-a3c367f67d95.maildroid@localhost>
Date: Thu, 19 Apr 2012 14:17:44 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <E0BDBD64-D3D4-4248-9EB2-BDD1F1CE39BF@virtualized.org>
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk> <248A261F-D83D-4F97-8F5D-A9A0BCD2EC0D@sobco.com> <f8e77298-bbd5-4ad8-80df-a3c367f67d95.maildroid@localhost>
To: IETF discussion list <ietf@ietf.org>
X-Mailer: Apple Mail (2.1257)
X-Mailman-Approved-At: Thu, 19 Apr 2012 14:28:06 -0700
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Apr 2012 21:17:48 -0000

Hi,

"Scott O Bradner <sob@sobco.com>" wrote:
> encouraging a report is fine=20

Agreed.

> retracting the code points seems to add more confusion than it is =
worth unless the code space is very tight

Disagree.  =46rom my experience at IANA, trying to figure out who to =
contact to remove a code point gets harder the longer the code points =
are not being used.  Unless the code space is unlimited, I'd argue that =
you want to deallocate as soon as an experiment is over.  I'd even go so =
far as to say that the original proposal for experimental code points =
should have explicit revocation dates (which can, of course, be =
refreshed similarly to IDs).

> and I see no reason to obsolete the experimental rfc or move it to =
historic status unless the report is that some bad thing happens when =
you try it out - updating the old rfc is fine

Having been involved with RFC 6563, I think in general it is quite =
useful to signal "hey, you really don't want to implement this".  If =
this can be done by updating the old RFC, that's fine.

> and I agree with Elliot about the nature of research - it is very =
common to not reach a conclusion that something is bad (as in bad for =
the net) - and that is the only case where I think that an experiment =
should be flagged as a don't go there situation

Agreed, with the proviso that limited resources (whether they are scarce =
or not) should be reclaimed.

Regards,
-drc


From cabo@tzi.org  Thu Apr 19 15:20:08 2012
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 15AA421F8495; Thu, 19 Apr 2012 15:20:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.323
X-Spam-Level: 
X-Spam-Status: No, score=-106.323 tagged_above=-999 required=5 tests=[AWL=-0.074, 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 oSON94qEEpO3; Thu, 19 Apr 2012 15:20:07 -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 36B3921F84A0; Thu, 19 Apr 2012 15:20:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id q3JMJvUh005027; Fri, 20 Apr 2012 00:19:57 +0200 (CEST)
Received: from [192.168.217.105] (p54899A0A.dip.t-dialin.net [84.137.154.10]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 9EABDD0F; Fri, 20 Apr 2012 00:19:57 +0200 (CEST)
Subject: Re: Proposed IESG Statement on the Conclusion of Experiments
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <E0BDBD64-D3D4-4248-9EB2-BDD1F1CE39BF@virtualized.org>
Date: Fri, 20 Apr 2012 00:19:57 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <0D5008B2-6645-4EAA-9698-0CD59C9584F5@tzi.org>
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk> <248A261F-D83D-4F97-8F5D-A9A0BCD2EC0D@sobco.com> <f8e77298-bbd5-4ad8-80df-a3c367f67d95.maildroid@localhost> <E0BDBD64-D3D4-4248-9EB2-BDD1F1CE39BF@virtualized.org>
To: David Conrad <drc@virtualized.org>
X-Mailer: Apple Mail (2.1257)
Cc: wgchairs@ietf.org, IETF discussion list <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Apr 2012 22:20:08 -0000

On Apr 19, 2012, at 23:17, David Conrad wrote:

> RFC 6563

But that's the point.  RFC 6563 is about documenting a failed =
experiment.
That's where the proposed approach actually helps.
(Retracting the A6 code point, maybe not so much :-)

Many other experimental RFCs neither fail nor succeed.

Between November 2004 and November 2009, I could not have said whether =
RFC 3940 "failed" or "succeeded".  It just was there, and people played =
with it.  It didn't take over the world, and it didn't destroy the =
Internet either.

When would the IESG have cut in under the new policy?

(RFC3940 finally was superseded by standards-track RFC 5740 in November =
2009.)

Now imagine an over-eager AD somewhere in these 5 years, wanting to =
clean up their backyard.

Gr=FC=DFe, Carsten


From rbonica@juniper.net  Thu Apr 19 15:28:11 2012
Return-Path: <rbonica@juniper.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 CBCFC11E809C; Thu, 19 Apr 2012 15:28:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.541
X-Spam-Level: 
X-Spam-Status: No, score=-106.541 tagged_above=-999 required=5 tests=[AWL=0.058, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rFrx4oJ7mpp4; Thu, 19 Apr 2012 15:28:11 -0700 (PDT)
Received: from exprod7og106.obsmtp.com (exprod7og106.obsmtp.com [64.18.2.165]) by ietfa.amsl.com (Postfix) with ESMTP id 0A5E711E8083; Thu, 19 Apr 2012 15:28:10 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob106.postini.com ([64.18.6.12]) with SMTP ID DSNKT5CRcd/YsWx00ynW2qshnIVcBuYd3cma@postini.com; Thu, 19 Apr 2012 15:28:11 PDT
Received: from P-CLDFE01-HQ.jnpr.net (172.24.192.59) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 19 Apr 2012 15:27:47 -0700
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by p-cldfe01-hq.jnpr.net (172.24.192.59) with Microsoft SMTP Server (TLS) id 14.1.355.2; Thu, 19 Apr 2012 15:27:47 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Thu, 19 Apr 2012 18:27:46 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: Scott O Bradner <sob@sobco.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>
Date: Thu, 19 Apr 2012 18:27:45 -0400
Subject: RE: Proposed IESG Statement on the Conclusion of Experiments
Thread-Topic: Proposed IESG Statement on the Conclusion of Experiments
Thread-Index: Ac0ebcEUCm1otab1RxKD9/xJUxUiYAADBVpg
Message-ID: <13205C286662DE4387D9AF3AC30EF456D76A76098B@EMBX01-WF.jnpr.net>
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk> <248A261F-D83D-4F97-8F5D-A9A0BCD2EC0D@sobco.com>
In-Reply-To: <248A261F-D83D-4F97-8F5D-A9A0BCD2EC0D@sobco.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: "wgchairs@ietf.org" <wgchairs@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Apr 2012 22:28:11 -0000

Hi Scott,

Comments inline.....

> -----Original Message-----
> From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of
> Scott O Bradner
> Sent: Thursday, April 19, 2012 4:48 PM
> To: adrian@olddog.co.uk
> Cc: wgchairs@ietf.org; ietf@ietf.org; iesg@ietf.org
> Subject: Re: Proposed IESG Statement on the Conclusion of Experiments
>=20
> encouraging a report is fine
>=20
> retracting the code points seems to add more confusion than it is worth
> unless the code space is very tight


We are talking about deprecating, not reusing the code point. There is curr=
ently a draft in the works that deprecates a few ICMPv4 code points. This d=
raft illustrates the benefits of deprecation. Namely,

- operators have a smaller decision to make when deciding whether to filter=
 the deprecated ICMP message
- if anybody is still writing ICMPv4 software, they don't have to fiddle wi=
th the deprecated messages

Conversely, do you see any benefit in not deprecating ICMPv4 message #31. (=
RFC 1475 reserves this code for IPv7.)

>=20
> and I see no reason to obsolete the experimental rfc or move it to
> historic status unless the report is that some bad thing happens when
> you try it out - updating the old rfc is fine
>

I think that this is a case-by-case judgment call. In some cases (e.g., RFC=
 1475), the experiment is clearly over. IMO, allowing RFC 1475 to retain EX=
PERIMENTAL status detracts from the credibility of current experiments that=
 share the label.

                                                   Ron
=20


From ajs@anvilwalrusden.com  Thu Apr 19 19:40:43 2012
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 736CB21F8534; Thu, 19 Apr 2012 19:40:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.691
X-Spam-Level: 
X-Spam-Status: No, score=-2.691 tagged_above=-999 required=5 tests=[AWL=-0.092, 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 Ov9lFeEz62ft; Thu, 19 Apr 2012 19:40:43 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id DBD5721F8531; Thu, 19 Apr 2012 19:40:42 -0700 (PDT)
Received: from mail.yitter.info (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 32D6E1ECB41D; Fri, 20 Apr 2012 02:40:42 +0000 (UTC)
Date: Thu, 19 Apr 2012 22:40:40 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: Proposed IESG Statement on the Conclusion of Experiments
Message-ID: <20120420024035.GL94829@mail.yitter.info>
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk> <40D324FA-D3BA-47FA-AC32-E1326D6A375A@checkpoint.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <40D324FA-D3BA-47FA-AC32-E1326D6A375A@checkpoint.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>, "ietf@ietf.org" <ietf@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, 20 Apr 2012 02:40:43 -0000

On Fri, Apr 20, 2012 at 12:17:46AM +0300, Yoav Nir wrote:

>    The "Experimental" designation typically denotes a specification that
>    is part of some research or development effort.
> 
> However, I do not believe that this is still typical. Authors come up with ideas that they think are useful. If when the documents are ready for publication it is still not clear whether there are enough implementers convinced by the use case (some definition of running code), they are encouraged to publish them as experimental rather than proposed standard.
> 

Yes, and surely what we want is that we continue to mislabel as many
RFCs as possible in this way.  We want to make our own contribution to
the gradual reduction of all words to mean everything else, so that we
can all communicate exclusively by mumbling, "Whatever."  Now that the
AP Stylebook has given up on "hopefully" and Oxford is playing with
the comma, anything goes.
 
> Neither of these can really be called an "experiment" except in the
> sense of "let's see if the Internet needs this specification". 

Yes, and that's a stupid meaning of the term in this case, because
quite frankly all the rest of the RFCs are also experiments in this
sense (and many of them have delivered the clarion answer, "Don't need
it at all!"  When was the last time you used BEEP?)

I don't know what I think about the proposal overall, but I will say
that one thing definitely in its favour is that it would discourage
those who think that "Experimental" is the Standards Track Consolation
Prize Track.  I'd be wholeheartedly in its favour, except that the old
"2 year review" standards track process didn't work, so we ditched
it.  I don't see how recycling the approach with Experimental
documents is any more likely to succeed.

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From bob.hinden@gmail.com  Thu Apr 19 21:47:41 2012
Return-Path: <bob.hinden@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 F0C5921F8596 for <wgchairs@ietfa.amsl.com>; Thu, 19 Apr 2012 21:47:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.545
X-Spam-Level: 
X-Spam-Status: No, score=-103.545 tagged_above=-999 required=5 tests=[AWL=0.054, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lzP1WVo36qRX for <wgchairs@ietfa.amsl.com>; Thu, 19 Apr 2012 21:47:39 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id D29F721F8639 for <wgchairs@ietf.org>; Thu, 19 Apr 2012 21:47:37 -0700 (PDT)
Received: by obbwd20 with SMTP id wd20so8793206obb.31 for <wgchairs@ietf.org>; Thu, 19 Apr 2012 21:47:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=qdOJSqrUEkxDA/IFyPAHuhbxn6POwbAB7NaApf3egXE=; b=pqLoOIRnduL2gFXz1mq1u04qkBxbCOmAQUzs7sZNpZQjNlHtjDbr9lijU6+B0xn41z Xz6ff3Xt2OqBNDspmP342ChJvEaDwm5cjTi9mWVNXoEMHih15V5zQhgLg46s0Z+SHtc1 gSmaFiZ3CNOHygj9RFSqtpr/QlTY1i30MpMvmHyZUerlbDRlCU8g61IxVPD1x2R/0yje I2+MZ4YmEy16zydlY4JDV8CnRNp8hv2JpCA1Q5rgbpzL5P0fuAs928EA1RFahkrlk2Ud Y2zLU/tIV65cRj0RKKgo5l8KN083LDsrC7QoxdCbQTSsn9seiUzQFYsA4hRhJ71iPnpt eQmw==
Received: by 10.182.40.70 with SMTP id v6mr6688875obk.39.1334897256800; Thu, 19 Apr 2012 21:47:36 -0700 (PDT)
Received: from [10.0.0.27] (c-69-181-250-158.hsd1.ca.comcast.net. [69.181.250.158]) by mx.google.com with ESMTPS id k7sm4454234oei.0.2012.04.19.21.47.35 (version=SSLv3 cipher=OTHER); Thu, 19 Apr 2012 21:47:36 -0700 (PDT)
Subject: Re: Formats for WG and BOF Agendas
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <4F8DC8FE.4070906@pobox.com>
Date: Thu, 19 Apr 2012 21:47:34 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <2A21E913-7FE4-49A1-A253-1764A4BAD372@gmail.com>
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com> <D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com> <B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com> <66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com> <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com> <E455982B-58F6-4127-98A9-E806C87F4100@bgp.nu> <4F8DC8FE.4070906@pobox.com>
To: kodonog@pobox.com
X-Mailer: Apple Mail (2.1084)
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, 20 Apr 2012 04:47:41 -0000

On Apr 17, 2012, at 12:48 PM, Karen O'Donoghue wrote:

> Sounds fine to me as well...

+1

Bob

>=20
> Karen
>=20
> On 4/17/12 3:42 PM, John G. Scudder wrote:
>> On Apr 17, 2012, at 3:00 PM, Russ Housley<housley@vigilsec.com>  =
wrote:
>>=20
>>> I propose that we to revert to supporting only .txt and .html file =
types for session minutes and agendas.  Then, using Apache's content =
negotiation, the Secretariat can link to them with an extension-less =
URL.  Apache will set the appropriate content-type.  This way the URLs =
will be persistent and consistent across supported file formats.
>>>=20
>>> Does anyone have concerns with the proposed way forward?
>> Au contraire, sounds like a fine thing.
>>=20
>> --John
>=20


From brian.e.carpenter@gmail.com  Fri Apr 20 00:19:58 2012
Return-Path: <brian.e.carpenter@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 4D81021E8034; Fri, 20 Apr 2012 00:19:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.57
X-Spam-Level: 
X-Spam-Status: No, score=-101.57 tagged_above=-999 required=5 tests=[AWL=0.121, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UDbTTSlgM-58; Fri, 20 Apr 2012 00:19:57 -0700 (PDT)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 01E8D21E8032; Fri, 20 Apr 2012 00:19:56 -0700 (PDT)
Received: by wgbdr13 with SMTP id dr13so6339638wgb.13 for <multiple recipients>; Fri, 20 Apr 2012 00:19:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=YWAd3xj3eJd/8L2ot3d2wViG7C09g03oXqHRHCxb2RY=; b=Oh7CXJf4rKuc9/xjFSCAiIWWfxO28O/a3hEp0sVAy/UyqKHs2XSsIkmTT5yJTjgem0 zyLzLkWHUvxRFHTG1WQGMavNy/5ubcMVdY4OZRzyibG/ZlNN5bB5+dVFXBMzDtdEO9aI /QEKtkIfI5gN/jCh7v9sebJWVSDIDVPHpHs+DrrUCw8P2/St5br6VqqHYiD2pJVjN3Sz TPNUnvxnrBOovw/G2HheKAsA3nTnd+HrViQbyJrP4jL9TArsSeKNcKIoFIpupl3xCp7D 88eUcjaftDPeo79uVBKXVHHekoWjQz6v7CFQA6qqwnAcIgCgxt3jUEyjZ5MRiQqlaScn XXVQ==
Received: by 10.180.92.130 with SMTP id cm2mr12379395wib.4.1334906396202; Fri, 20 Apr 2012 00:19:56 -0700 (PDT)
Received: from [192.168.1.64] (host-2-102-216-233.as13285.net. [2.102.216.233]) by mx.google.com with ESMTPS id l5sm3521117wia.11.2012.04.20.00.19.54 (version=SSLv3 cipher=OTHER); Fri, 20 Apr 2012 00:19:55 -0700 (PDT)
Message-ID: <4F910E19.5080303@gmail.com>
Date: Fri, 20 Apr 2012 08:19:53 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Ronald Bonica <rbonica@juniper.net>
Subject: Re: Proposed IESG Statement on the Conclusion of Experiments
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk>	<248A261F-D83D-4F97-8F5D-A9A0BCD2EC0D@sobco.com> <13205C286662DE4387D9AF3AC30EF456D76A76098B@EMBX01-WF.jnpr.net>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D76A76098B@EMBX01-WF.jnpr.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "ietf@ietf.org" <ietf@ietf.org>, Scott O Bradner <sob@sobco.com>, "wgchairs@ietf.org" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Apr 2012 07:19:58 -0000

On 2012-04-19 23:27, Ronald Bonica wrote:
...
> I think that this is a case-by-case judgment call. In some cases (e.g., RFC 1475), the experiment is clearly over. IMO, allowing RFC 1475 to retain EXPERIMENTAL status detracts from the credibility of current experiments that share the label.

I agree that it is case by case, so I don't really see the value in the
IESG statement. If it's appropriate to write an experiment-terminating
RFC, do so; if it's inappropriate, don't bother. That doesn't need
any new legislation.

    Brian

From lars@netapp.com  Fri Apr 20 00:31:37 2012
Return-Path: <lars@netapp.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15C0F21F8527; Fri, 20 Apr 2012 00:31:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.736
X-Spam-Level: 
X-Spam-Status: No, score=-10.736 tagged_above=-999 required=5 tests=[AWL=-0.137, 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 KLUaAPYTVchJ; Fri, 20 Apr 2012 00:31:36 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by ietfa.amsl.com (Postfix) with ESMTP id 695D121F8512; Fri, 20 Apr 2012 00:31:36 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.75,451,1330934400";  d="p7s'?scan'208";a="642223800"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx2-out.netapp.com with ESMTP; 20 Apr 2012 00:31:21 -0700
Received: from vmwexceht01-prd.hq.netapp.com (vmwexceht01-prd.hq.netapp.com [10.106.76.239]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id q3K7VLWF002036; Fri, 20 Apr 2012 00:31:21 -0700 (PDT)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.117]) by vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) with mapi id 14.02.0247.003; Fri, 20 Apr 2012 00:31:20 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: "<adrian@olddog.co.uk>" <adrian@olddog.co.uk>
Subject: Re: Proposed IESG Statement on the Conclusion of Experiments
Thread-Topic: Proposed IESG Statement on the Conclusion of Experiments
Thread-Index: Ac0ea1trQ6bEEENVRsKUUaoiCTZbygAluXqA
Date: Fri, 20 Apr 2012 07:31:20 +0000
Message-ID: <759FD9FB-D281-4D78-AA10-1F1AFA2B1FCB@netapp.com>
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk>
In-Reply-To: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: multipart/signed; boundary="Apple-Mail=_8A998C11-DC91-4EE7-94F5-61AA9461A923"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Cc: "<wgchairs@ietf.org>" <wgchairs@ietf.org>, "<ietf@ietf.org>" <ietf@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, 20 Apr 2012 07:31:37 -0000

--Apple-Mail=_8A998C11-DC91-4EE7-94F5-61AA9461A923
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

On Apr 19, 2012, at 22:31, Adrian Farrel wrote:
> The IESG has been discussing how to tidy up after Experimental RFCs.
>=20
> We have developed the following draft IESG statement. This does not=20
> represent a change in process, and continues to value Experimental =
RFCs
> as an important part of the IETF process. It does, however, seek to=20
> encourage documentation of the conclusion of experiments.

any IESG statement would only cover Experimental RFCs on the IETF =
Stream, right?

Lars=

--Apple-Mail=_8A998C11-DC91-4EE7-94F5-61AA9461A923
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMQDCCBUow
ggQyoAMCAQICEFcfSRTG0jNknqb9LV9GuFkwDQYJKoZIhvcNAQEFBQAwgd0xCzAJBgNVBAYTAlVT
MRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEg
KGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24g
Q2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMzAeFw0xMTEyMTAwMDAwMDBaFw0x
MjEyMDkyMzU5NTlaMIIBDTEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9S
UEEgSW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMpOTgxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZh
bGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJRCBDbGFzcyAxIC0gTmV0c2NhcGUgRnVsbCBTZXJ2
aWNlMRQwEgYDVQQDFAtMYXJzIEVnZ2VydDEeMBwGCSqGSIb3DQEJARYPbGFyc0BuZXRhcHAuY29t
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAokrhJTcXt6J/VEpZOicLoguBlYTjXP9v
Ze4HuuhXnURUS8YouAfgaqA0zYbt5yd6fh4PBMdAaEWr5yJyHuFykXlrCumjUWSpLuqTS2A+pt4q
cZaAQk9iLDN/UVd3SpkUuvWbxXlqzG7/BSqa3VNObBzCmyh+V7aXxri+30CT//DSsNRC4VFy6sn6
dMgSaFenXLwe/FBwY0qTMfICT1PrrX6Sw1S8OfH9rykLlZXbmfkFExxQngp1DJH9xMHeODHGbCv/
ty5gdxMOrLe+vENxFEcy1YQWBZd1kNL4UObugF8A/jE/s+Oa3H1VFH8ghqZTdqGDysVxmtKHuNFx
6jIBSQIDAQABo4HSMIHPMAkGA1UdEwQCMAAwRAYDVR0gBD0wOzA5BgtghkgBhvhFAQcXATAqMCgG
CCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhMAsGA1UdDwQEAwIFoDAdBgNV
HSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwUAYDVR0fBEkwRzBFoEOgQYY/aHR0cDovL2luZGMx
ZGlnaXRhbGlkLWczLWNybC52ZXJpc2lnbi5jb20vSW5kQzFEaWdpdGFsSUQtRzMuY3JsMA0GCSqG
SIb3DQEBBQUAA4IBAQBA7q6tR92qpd7xo7VBsrOfGCWzoxIVfTc7t0RhB/Oz/+c3lnhYnNScIuKN
JmyZvznmVxqB9BJ72+NkvmdB/hnILSBTRawL2tyLo9PkBtN0nRt4gS6wjpWnD8G83hlJLE7r25jk
7HkRev61dTIXsANFpJKF02C4XSoDfEzNV6MpuEvHvcgHCqMrlwWwfKc7+NoDnE8PBuRzwSXvlD5L
mswCY2iiOsd7ImNO4OzTCxETvKTDu92+FTIbRJJpYjVNv1UF7e3w9Kq65BkZJErUH19beUeQl0Wh
2BJQE6/15rQyCnP0iJ/Nmx2/kI6M0PWunEsI6FMs0MbosreaWGHlQmomMIIG7jCCBdagAwIBAgIQ
cRVmBUrkkSFN6bxE+azT3DANBgkqhkiG9w0BAQUFADCByjELMAkGA1UEBhMCVVMxFzAVBgNVBAoT
DlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTowOAYDVQQL
EzEoYykgMTk5OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MUUwQwYD
VQQDEzxWZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9y
aXR5IC0gRzMwHhcNMDkwNTAxMDAwMDAwWhcNMTkwNDMwMjM1OTU5WjCB3TELMAkGA1UEBhMCVVMx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3Jr
MTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAo
YykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBD
bGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBDQSAtIEczMIIBIjANBgkqhkiG9w0BAQEFAAOC
AQ8AMIIBCgKCAQEA7cRH3yooHXwGa7vXITLJbBOP6bGNQU4099oL42r6ZYggCxET6ZvgSU6Lb9UB
0F8NR5GKWkx0Pj/GkQm7TDSejW6hglFi92l2WJYHr54UGAdPWr2f0jGyVBlzRmoZQhHsEnMhjfXc
MM3l2VYKMcU2bSkUl70t2olHGYjYSwQ967Y8Zx50ABMN0Ibak2f4MwOuGjxraXj2wCyO4YM/d/mZ
//6fUlrCtIcK2GypR8FUKWVDPkrAlh/Brfd3r2yxBF6+wbaULZeQLSfSux7pg2qE9sSyriMGZSal
J1grByK0b6ZiSBp38tVQJ5op05b7KPW6JHZi44xZ6/tu1ULEvkHH9QIDAQABo4ICuTCCArUwNAYI
KwYBBQUHAQEEKDAmMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC52ZXJpc2lnbi5jb20wEgYDVR0T
AQH/BAgwBgEB/wIBADBwBgNVHSAEaTBnMGUGC2CGSAGG+EUBBxcBMFYwKAYIKwYBBQUHAgEWHGh0
dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9jcHMwKgYIKwYBBQUHAgIwHhocaHR0cHM6Ly93d3cudmVy
aXNpZ24uY29tL3JwYTA0BgNVHR8ELTArMCmgJ6AlhiNodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9w
Y2ExLWczLmNybDAOBgNVHQ8BAf8EBAMCAQYwbgYIKwYBBQUHAQwEYjBgoV6gXDBaMFgwVhYJaW1h
Z2UvZ2lmMCEwHzAHBgUrDgMCGgQUS2u5KJYGDLvQUjibKaxLB4shBRgwJhYkaHR0cDovL2xvZ28u
dmVyaXNpZ24uY29tL3ZzbG9nbzEuZ2lmMC4GA1UdEQQnMCWkIzAhMR8wHQYDVQQDExZQcml2YXRl
TGFiZWw0LTIwNDgtMTE4MB0GA1UdDgQWBBR5R2EIQf04BKJL57XM9UP2SSsR+DCB8QYDVR0jBIHp
MIHmoYHQpIHNMIHKMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNV
BAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4BgNVBAsTMShjKSAxOTk5IFZlcmlTaWduLCBJ
bmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxRTBDBgNVBAMTPFZlcmlTaWduIENsYXNzIDEg
UHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgLSBHM4IRAItbdVaEVIULAM+v
OEjOsaQwDQYJKoZIhvcNAQEFBQADggEBADlNz0GZgbWpBbVSOOk5hIls5DSoWufYbAlMJBq6WaSH
O3Mh8ZOBz79oY1pn/jWFK6HDXaNKwjoZ3TDWzE3v8dKBl8pUWkO/N4t6jhmND0OojPKvYLMVirOV
nDzgnrMnmKQ1chfl/Cpdh9OKDcLRRSr4wPSsKpM61a4ScAjr+zvid+zoK2Q1ds262uDRyxTWcVib
vtU+fbbZ6CTFJGZMXZEfdrMXPn8NxiGJL7M3uKH/XLJtSd5lUkL7DojS7Uodv0vj+Mxy+kgOZY5J
yNb4mZg7t5Q+MXEGh/psWVMu198r7V9jAKwV7QO4VRaMxmgD5yKocwuxvKDaUljdCg5/wYIxggSL
MIIEhwIBATCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0
cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFs
aWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBD
QSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMAkGBSsOAwIaBQCgggJtMBgGCSqGSIb3DQEJAzELBgkq
hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEyMDQyMDA3MzEyMVowIwYJKoZIhvcNAQkEMRYEFGcf
5fu0Cf0b9pH2PuL+IqYm0yATMIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQGEwJVUzEX
MBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
OzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhIChj
KTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlTaWduIENs
YXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEFcfSRTG0jNknqb9LV9GuFkwggEF
BgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJ
bmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1
c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29u
YSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vi
c2NyaWJlciBDQSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMA0GCSqGSIb3DQEBAQUABIIBABKBhNml
kAVBxBsi7hEzx6TxQa85nnM2BcsGgBYKayQwb36t/2RMNKdDSvuv2pfGDezlfJWDwBS1q5DSaepb
gTnrmN+e45feEji+4+Y9KSMRkviUXZw4Y/8hDxiII0BME1v3S3TBDERAHKa5DW5Zs+XVg2mTdzoN
htv2WNdjmtju2Qe2dsix4Fhc1s3r3KX/NytGFiVfNg12oec9KCZbi/sUTEs3oY/8en2YAwTyD9JQ
X2bUTNX4VcCl/ujayxRlr/llfkTGYZs9xL8xSOYF9lyYSFVTiamchY10XAno2H7Egfx1HOunRJ5m
duItUMSlrNVP/gKtQUWz1CySKhuPuiQAAAAAAAA=

--Apple-Mail=_8A998C11-DC91-4EE7-94F5-61AA9461A923--

From lars@netapp.com  Fri Apr 20 01:24:14 2012
Return-Path: <lars@netapp.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA15A21F86F9; Fri, 20 Apr 2012 01:24:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.733
X-Spam-Level: 
X-Spam-Status: No, score=-10.733 tagged_above=-999 required=5 tests=[AWL=-0.134, 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 lU8tDPdIgpqY; Fri, 20 Apr 2012 01:24:12 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by ietfa.amsl.com (Postfix) with ESMTP id DB90321F86F7; Fri, 20 Apr 2012 01:24:11 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.75,451,1330934400";  d="p7s'?scan'208";a="642230204"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx2-out.netapp.com with ESMTP; 20 Apr 2012 01:24:11 -0700
Received: from vmwexceht01-prd.hq.netapp.com (vmwexceht01-prd.hq.netapp.com [10.106.76.239]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id q3K8OB8N008977; Fri, 20 Apr 2012 01:24:11 -0700 (PDT)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.117]) by vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) with mapi id 14.02.0247.003; Fri, 20 Apr 2012 01:24:10 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: Eliot Lear <lear@cisco.com>
Subject: Re: Proposed IESG Statement on the Conclusion of Experiments
Thread-Topic: Proposed IESG Statement on the Conclusion of Experiments
Thread-Index: Ac0ea1trQ6bEEENVRsKUUaoiCTZbygAO7bwAABikHIA=
Date: Fri, 20 Apr 2012 08:24:09 +0000
Message-ID: <25CD1A39-FEB2-405B-9F71-014BEE05D656@netapp.com>
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk> <4F9077CE.4050400@cisco.com>
In-Reply-To: <4F9077CE.4050400@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: multipart/signed; boundary="Apple-Mail=_582EACBC-BF2B-4792-839C-8AE0DA9EDBB1"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Cc: Adrian Farrel <adrian@olddog.co.uk>, Internet Research Steering Group <irsg@irtf.org>, "ietf@ietf.org" <ietf@ietf.org>, "wgchairs@ietf.org" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Apr 2012 08:24:14 -0000

--Apple-Mail=_582EACBC-BF2B-4792-839C-8AE0DA9EDBB1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

On Apr 19, 2012, at 22:38, Eliot Lear wrote:
> I do not support such a view, and it is not supported in a plain =
reading
> of RFC 2026.  What's more, it's not how researchers work.  Researchers
> naturally move on.  If we are looking to further push researchers away
> from the IRTF, this is a good way to do it.
>=20
> Whether or not an experiment is active is also not how research works.=20=

> Sometimes work is taken up after years of gaps.  ILNP is a good =
example
> of this.  Had 8+8 been published in a timely fashion as an =
experimental
> RFC, we would have had obsoleted it, only to then unobsolete it?

I agree with Eliot. I think the IESG is interpreting things into 2026 =
that aren't there. Not all Experimental RFCs describe what - with my =
research hat on - I would call a scientific experiment. Actually, I =
can't come up with single one that does.

Experimental RFCs specify protocols and protocol extensions *for =
experimentation*, just as Standards Track RFCs specify protocols and =
protocol extensions for widespread implementation and deployment. But =
they do *not* (usually) describe the actual experiments that are to be =
performed, and I know of no one that would go so far as discuss a =
timeline for any such experiments. The assumption that an Experimental =
RFC always describes an actual scientific experiment is simply wrong, =
and since this assumption underlies the proposed IESG statement, it =
renders it ineffectual at best and actually harmful at worst.

Experimental RFCs get published for all kinds of reasons. On the IETF =
side, this may range from actual proposals for protocol evolution for =
the community to play with, to things that failed to get Standards Track =
consensus but that a WG didn't feel like abandoning outright, and some =
WGs use them as a pre-PS step. The proposed IESG statement completely =
misses that reality.

And obviously, Experimental RFCs exist on other Streams. In terms of =
whether any IESG statement would even apply to IRTF and Independent =
Stream RFCs, that is not at all clear to me. In any event, it would have =
been good to CC the IRSG, since they are not included on the wgchairs =
list. If the IESG believes that their statement would extend to RFCs on =
other Streams, they should REALLY have engaged us much earlier, rather =
than with a six-day deadline for comments.

> On 4/19/12 10:31 PM, Adrian Farrel wrote:
>> We have developed the following draft IESG statement. This does not=20=

>> represent a change in process,

Actually, this *does* represent a change in process. It implies that any =
Experimental RFC must only describe an actual scientific experiment, so =
that later on it can be judged whether that experiment has succeeded or =
failed, and the outcome recorded. This is a much more limited view of =
what Experimental RFCs are than I believe 2026 states.

It also requires the proponents of an Experimental RFC to also sign up =
for writing another future document describing the "results." (Which per =
above, I believe doesn't make sense for the cast majority of =
Experimental RFCs, because they do not describe scientific experiments.)

>> and continues to value Experimental RFCs
>> as an important part of the IETF process. It does, however, seek to=20=

>> encourage documentation of the conclusion of experiments.
>>=20
>> We are aware that there may be other discussion points around=20
>> Experimental RFCs, and we would like to discuss these, but we also
>> believe that there is merit in making small, incremental =
improvements.
>>=20
>> The IESG would welcome your thoughts on this draft before they =
approve
>> the final text on April 26th.

This is simply much too soon.

>> IESG Statement on Conclusion of IETF Experiments
>>=20
>>=20
>> Experiments are an established and valuable part of the IETF process.

Actually, I would claim they are not. Experimental *RFCs* are, and IETF =
participants (and others) may perform experiments with IETF protocols =
and proposed extensions (whether they are described in IDs, or RFCs of =
whatever status), but the IETF itself does not do experiments.

>> A number of core Internet protocols were first published as =
Experimental
>> RFCs while the community gathered experience and carefully =
investigated
>> the consequences of deploying new mechanisms within the Internet.
>>=20
>> In the case where an experiment leads on to the development of a     =20=

>> Standards Track RFC documenting a protocol, the new RFC obsoletes the=20=

>> old Experimental RFC and there is a clear conclusion to the =
experiment.

It's not so simple. Consider for example TCP F-RTO. The Experimental RFC =
is 4138. It defines F-RTO for both TCP and SCTP. TCP F-RTO was moved to =
PS in 5682, but 4138 was not obsoleted, because the SCTP F-RTO is still =
considered an experiment.

4128 was published in 2005. 5682 was published in 2009. So clearly SCTP =
F-RTO has failed the "experiment"? Not really. With RTCWEB strongly =
considering SCTP as a transport framework for the data channel, it's =
actually very likely that SCTP F-RTO will move to PS in a few years too. =
So if we had declared the experiment closed, would we have done good or =
harm?

>> However, many experiments do not lead to the development of Standards
>> Track RFCs. Instead, the work may be abandoned through lack of =
interest
>> or because important lessons have been learned.

Or, nobody feels a great need to do the work to republish an =
Experimental RFC as PS, although it is widely implemented. Again, 4138 =
was Experimental for four years, although all major stacks implemented =
and enabled it by default. Why took it so long? Because the community =
had other things to work on and the original document was fine.

>> It is currently hard to distinguish between an experiment that is =
still
>> being investigated, and an old experiment that has ceased to be of
>> interest to the community.

Very true. That is why it is very hard to come up with any generic rules =
here, as this IESG statement is attempting to do. (And never mind that =
many Experimental RFCs don't actually describe experiments.)

>> In both cases an Experimental RFC exists in
>> the repository and newcomers might easily be misled into thinking =
that
>> it would be helpful to conduct more research into an abandoned
>> experiment.

An abandoned experiment is not a failed experiment. Old ideas aren't =
necessarily bad ideas, and many IETF technologies that lie dormant for a =
long time all of a sudden gain traction. (Example: SCTP in RTCWEB.)

>> In view of this, the original proponents of experiments (that is,=20
>> authors of Experimental RFCs, and Working Groups that requested the
>> publication of Experimental RFCs) are strongly encouraged to document
>> the termination of experiments that do not result in subsequent
>> Standards Track work by publishing an Informational RFC that:
>>=20
>> - very briefly describes the results of the experiment
>>=20
>> - obsoletes the Experimental RFC
>>=20
>> - if appropriate, deprecate any IANA code points allocated for the=20
>>  experiment
>>=20
>> - may request that the Experimental RFC is moved to Historic status.

So is the intent here RFC database and IANA registry housekeeping? In =
that case, focusing on Experimental RFCs is simply misguided. There are =
many more standards-track RFCs that have "failed" and would also need to =
be obsoleted and have their codepoints reclaimed.=20

And unlike for Experimental RFCs, we actually do have 2026 text that =
talks about standards-track maturity, etc.=20

>> If there is no energy in the community for the producing such an
>> Informational RFC, if the authors have moved on to other things, or =
if
>> the Working Group has been closed down, Area Directors should author =
or
>> seek volunteers to author such an Informational RFC.

If I am counting things correctly, almost 1500 Experimental RFCs have =
been published so far, many by working groups that no longer exist. =
That's a lot of RFCs to write by volunteers (ADs really should have =
better things to do...) for little gain.

Lars



--Apple-Mail=_582EACBC-BF2B-4792-839C-8AE0DA9EDBB1
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMQDCCBUow
ggQyoAMCAQICEFcfSRTG0jNknqb9LV9GuFkwDQYJKoZIhvcNAQEFBQAwgd0xCzAJBgNVBAYTAlVT
MRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEg
KGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24g
Q2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMzAeFw0xMTEyMTAwMDAwMDBaFw0x
MjEyMDkyMzU5NTlaMIIBDTEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9S
UEEgSW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMpOTgxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZh
bGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJRCBDbGFzcyAxIC0gTmV0c2NhcGUgRnVsbCBTZXJ2
aWNlMRQwEgYDVQQDFAtMYXJzIEVnZ2VydDEeMBwGCSqGSIb3DQEJARYPbGFyc0BuZXRhcHAuY29t
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAokrhJTcXt6J/VEpZOicLoguBlYTjXP9v
Ze4HuuhXnURUS8YouAfgaqA0zYbt5yd6fh4PBMdAaEWr5yJyHuFykXlrCumjUWSpLuqTS2A+pt4q
cZaAQk9iLDN/UVd3SpkUuvWbxXlqzG7/BSqa3VNObBzCmyh+V7aXxri+30CT//DSsNRC4VFy6sn6
dMgSaFenXLwe/FBwY0qTMfICT1PrrX6Sw1S8OfH9rykLlZXbmfkFExxQngp1DJH9xMHeODHGbCv/
ty5gdxMOrLe+vENxFEcy1YQWBZd1kNL4UObugF8A/jE/s+Oa3H1VFH8ghqZTdqGDysVxmtKHuNFx
6jIBSQIDAQABo4HSMIHPMAkGA1UdEwQCMAAwRAYDVR0gBD0wOzA5BgtghkgBhvhFAQcXATAqMCgG
CCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhMAsGA1UdDwQEAwIFoDAdBgNV
HSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwUAYDVR0fBEkwRzBFoEOgQYY/aHR0cDovL2luZGMx
ZGlnaXRhbGlkLWczLWNybC52ZXJpc2lnbi5jb20vSW5kQzFEaWdpdGFsSUQtRzMuY3JsMA0GCSqG
SIb3DQEBBQUAA4IBAQBA7q6tR92qpd7xo7VBsrOfGCWzoxIVfTc7t0RhB/Oz/+c3lnhYnNScIuKN
JmyZvznmVxqB9BJ72+NkvmdB/hnILSBTRawL2tyLo9PkBtN0nRt4gS6wjpWnD8G83hlJLE7r25jk
7HkRev61dTIXsANFpJKF02C4XSoDfEzNV6MpuEvHvcgHCqMrlwWwfKc7+NoDnE8PBuRzwSXvlD5L
mswCY2iiOsd7ImNO4OzTCxETvKTDu92+FTIbRJJpYjVNv1UF7e3w9Kq65BkZJErUH19beUeQl0Wh
2BJQE6/15rQyCnP0iJ/Nmx2/kI6M0PWunEsI6FMs0MbosreaWGHlQmomMIIG7jCCBdagAwIBAgIQ
cRVmBUrkkSFN6bxE+azT3DANBgkqhkiG9w0BAQUFADCByjELMAkGA1UEBhMCVVMxFzAVBgNVBAoT
DlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTowOAYDVQQL
EzEoYykgMTk5OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MUUwQwYD
VQQDEzxWZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9y
aXR5IC0gRzMwHhcNMDkwNTAxMDAwMDAwWhcNMTkwNDMwMjM1OTU5WjCB3TELMAkGA1UEBhMCVVMx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3Jr
MTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAo
YykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBD
bGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBDQSAtIEczMIIBIjANBgkqhkiG9w0BAQEFAAOC
AQ8AMIIBCgKCAQEA7cRH3yooHXwGa7vXITLJbBOP6bGNQU4099oL42r6ZYggCxET6ZvgSU6Lb9UB
0F8NR5GKWkx0Pj/GkQm7TDSejW6hglFi92l2WJYHr54UGAdPWr2f0jGyVBlzRmoZQhHsEnMhjfXc
MM3l2VYKMcU2bSkUl70t2olHGYjYSwQ967Y8Zx50ABMN0Ibak2f4MwOuGjxraXj2wCyO4YM/d/mZ
//6fUlrCtIcK2GypR8FUKWVDPkrAlh/Brfd3r2yxBF6+wbaULZeQLSfSux7pg2qE9sSyriMGZSal
J1grByK0b6ZiSBp38tVQJ5op05b7KPW6JHZi44xZ6/tu1ULEvkHH9QIDAQABo4ICuTCCArUwNAYI
KwYBBQUHAQEEKDAmMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC52ZXJpc2lnbi5jb20wEgYDVR0T
AQH/BAgwBgEB/wIBADBwBgNVHSAEaTBnMGUGC2CGSAGG+EUBBxcBMFYwKAYIKwYBBQUHAgEWHGh0
dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9jcHMwKgYIKwYBBQUHAgIwHhocaHR0cHM6Ly93d3cudmVy
aXNpZ24uY29tL3JwYTA0BgNVHR8ELTArMCmgJ6AlhiNodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9w
Y2ExLWczLmNybDAOBgNVHQ8BAf8EBAMCAQYwbgYIKwYBBQUHAQwEYjBgoV6gXDBaMFgwVhYJaW1h
Z2UvZ2lmMCEwHzAHBgUrDgMCGgQUS2u5KJYGDLvQUjibKaxLB4shBRgwJhYkaHR0cDovL2xvZ28u
dmVyaXNpZ24uY29tL3ZzbG9nbzEuZ2lmMC4GA1UdEQQnMCWkIzAhMR8wHQYDVQQDExZQcml2YXRl
TGFiZWw0LTIwNDgtMTE4MB0GA1UdDgQWBBR5R2EIQf04BKJL57XM9UP2SSsR+DCB8QYDVR0jBIHp
MIHmoYHQpIHNMIHKMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNV
BAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4BgNVBAsTMShjKSAxOTk5IFZlcmlTaWduLCBJ
bmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxRTBDBgNVBAMTPFZlcmlTaWduIENsYXNzIDEg
UHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgLSBHM4IRAItbdVaEVIULAM+v
OEjOsaQwDQYJKoZIhvcNAQEFBQADggEBADlNz0GZgbWpBbVSOOk5hIls5DSoWufYbAlMJBq6WaSH
O3Mh8ZOBz79oY1pn/jWFK6HDXaNKwjoZ3TDWzE3v8dKBl8pUWkO/N4t6jhmND0OojPKvYLMVirOV
nDzgnrMnmKQ1chfl/Cpdh9OKDcLRRSr4wPSsKpM61a4ScAjr+zvid+zoK2Q1ds262uDRyxTWcVib
vtU+fbbZ6CTFJGZMXZEfdrMXPn8NxiGJL7M3uKH/XLJtSd5lUkL7DojS7Uodv0vj+Mxy+kgOZY5J
yNb4mZg7t5Q+MXEGh/psWVMu198r7V9jAKwV7QO4VRaMxmgD5yKocwuxvKDaUljdCg5/wYIxggSL
MIIEhwIBATCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0
cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFs
aWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBD
QSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMAkGBSsOAwIaBQCgggJtMBgGCSqGSIb3DQEJAzELBgkq
hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEyMDQyMDA4MjQxMlowIwYJKoZIhvcNAQkEMRYEFBQb
8UpK/sLFbX0g9Ttdwo1zG38mMIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQGEwJVUzEX
MBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
OzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhIChj
KTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlTaWduIENs
YXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEFcfSRTG0jNknqb9LV9GuFkwggEF
BgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJ
bmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1
c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29u
YSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vi
c2NyaWJlciBDQSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMA0GCSqGSIb3DQEBAQUABIIBAJSH5Bqu
r0e5cuxbBsOZRMQHCJTWwy5m65zGgtwd0PnjB1GjXoPIYjmX4wolHDjGInse3IBosy8hPsvl1p0v
0xyiA0HyDjxWlXaSVM1/nSUKil02dyyvUP+f6FfuDVCGE+Kq3SBpK3DkfhT3uaTycBRrGUzyJQdu
dD5HQXu0QKpfahSjojdJdEE9DhBG4pUUFwm2pksas8kezzZeYnLEseFSfKey3Uv6lw2bv3YRHqgf
qkBxHbK3W7av/3zPOxkLcsyvegOHavB/TXsVk3LemO+WHL3VwEA5KCAf/RVB9pqlP/+5GF/BwGlI
qfZgCn1MwgU/DujJbuqN0lCuiOSoV8gAAAAAAAA=

--Apple-Mail=_582EACBC-BF2B-4792-839C-8AE0DA9EDBB1--

From adrian@olddog.co.uk  Fri Apr 20 01:24:15 2012
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 4A00C21F86F7; Fri, 20 Apr 2012 01:24:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.413
X-Spam-Level: 
X-Spam-Status: No, score=-2.413 tagged_above=-999 required=5 tests=[AWL=0.186,  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 Ip1YoqZKksoM; Fri, 20 Apr 2012 01:24:14 -0700 (PDT)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id 1CAAF21F86F8; Fri, 20 Apr 2012 01:24:13 -0700 (PDT)
Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id q3K8OCDM002228;  Fri, 20 Apr 2012 09:24:12 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id q3K8OAD2002174 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 20 Apr 2012 09:24:11 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Eggert, Lars'" <lars@netapp.com>
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk> <759FD9FB-D281-4D78-AA10-1F1AFA2B1FCB@netapp.com>
In-Reply-To: <759FD9FB-D281-4D78-AA10-1F1AFA2B1FCB@netapp.com>
Subject: RE: Proposed IESG Statement on the Conclusion of Experiments
Date: Fri, 20 Apr 2012 09:24:15 +0100
Message-ID: <111c01cd1ece$fa283e10$ee78ba30$@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: AQGnz2jfWO+T6KQHYDN/WAeucdikQAEyHuqlluRhNsA=
Content-Language: en-gb
Cc: wgchairs@ietf.org, ietf@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Apr 2012 08:24:15 -0000

Hi Lars,

I was just typing a similar response to Eliot and Scott.

Clearly the IESG does not have authority over the IRTF stream.

I had thought this context ant the limitation to the IETF stream was clear in
the initial blurb ("Experiments are an established and valuable part of the IETF
process.") but obviously I was wrong :-)

We will add clarification of this point to the statement.

Thanks,
Adrian

> -----Original Message-----
> From: Eggert, Lars [mailto:lars@netapp.com]
> Sent: 20 April 2012 08:31
> To: <adrian@olddog.co.uk> 
> Cc: <ietf@ietf.org>; <wgchairs@ietf.org>; <iesg@ietf.org>
> Subject: Re: Proposed IESG Statement on the Conclusion of Experiments
> 
> Hi,
> 
> On Apr 19, 2012, at 22:31, Adrian Farrel wrote:
> > The IESG has been discussing how to tidy up after Experimental RFCs.
> >
> > We have developed the following draft IESG statement. This does not
> > represent a change in process, and continues to value Experimental RFCs
> > as an important part of the IETF process. It does, however, seek to
> > encourage documentation of the conclusion of experiments.
> 
> any IESG statement would only cover Experimental RFCs on the IETF Stream,
> right?
> 
> Lars


From adrian@olddog.co.uk  Fri Apr 20 02:03:46 2012
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 52A6921F876E; Fri, 20 Apr 2012 02:03:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level: 
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[AWL=0.149,  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 3fW44c4-N1Yi; Fri, 20 Apr 2012 02:03:45 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id 6370521F8730; Fri, 20 Apr 2012 02:03:45 -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 q3K93hw7018999;  Fri, 20 Apr 2012 10:03:43 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id q3K93fhA018959 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 20 Apr 2012 10:03:42 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Brian E Carpenter'" <brian.e.carpenter@gmail.com>
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk>	<248A261F-D83D-4F97-8F5D-A9A0BCD2EC0D@sobco.com> <13205C286662DE4387D9AF3AC30EF456D76A76098B@EMBX01-WF.jnpr.net> <4F910E19.5080303@gmail.com>
In-Reply-To: <4F910E19.5080303@gmail.com>
Subject: RE: Proposed IESG Statement on the Conclusion of Experiments
Date: Fri, 20 Apr 2012 10:03:46 +0100
Message-ID: <114101cd1ed4$7f2ae4f0$7d80aed0$@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: AQGnz2jfWO+T6KQHYDN/WAeucdikQAHavnLcAkyzZzwCryxeK5a3U4vg
Content-Language: en-gb
Cc: wgchairs@ietf.org, ietf@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Apr 2012 09:03:46 -0000

Hi,=20

I sort of agree that no new legislation is needed, and I don't read the =
statement as legislation.

But it is clear that, with the exception of promotion of Experimental =
RFCs onto the Standards Track, this function has not been happening. It =
makes sense (I think) to set expectations.

Adrian

> -----Original Message-----
> From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]
> Sent: 20 April 2012 08:20
> To: Ronald Bonica
> Cc: Scott O Bradner; adrian@olddog.co.uk; wgchairs@ietf.org; =
ietf@ietf.org;
> iesg@ietf.org
> Subject: Re: Proposed IESG Statement on the Conclusion of Experiments
>=20
> On 2012-04-19 23:27, Ronald Bonica wrote:
> ...
> > I think that this is a case-by-case judgment call. In some cases =
(e.g., RFC 1475),
> the experiment is clearly over. IMO, allowing RFC 1475 to retain =
EXPERIMENTAL
> status detracts from the credibility of current experiments that share =
the label.
>=20
> I agree that it is case by case, so I don't really see the value in =
the
> IESG statement. If it's appropriate to write an experiment-terminating
> RFC, do so; if it's inappropriate, don't bother. That doesn't need
> any new legislation.
>=20
>     Brian


From msk@cloudmark.com  Fri Apr 20 06:38:35 2012
Return-Path: <msk@cloudmark.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 8177F21F8779 for <wgchairs@ietfa.amsl.com>; Fri, 20 Apr 2012 06:38:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.657
X-Spam-Level: 
X-Spam-Status: No, score=-102.657 tagged_above=-999 required=5 tests=[AWL=-0.058, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bD0Fe4lL5HjP for <wgchairs@ietfa.amsl.com>; Fri, 20 Apr 2012 06:38:35 -0700 (PDT)
Received: from mail.cloudmark.com (cmgw1.cloudmark.com [208.83.136.25]) by ietfa.amsl.com (Postfix) with ESMTP id 642B221F8778 for <wgchairs@ietf.org>; Fri, 20 Apr 2012 06:38:35 -0700 (PDT)
Received: from ht1-outbound.cloudmark.com ([72.5.239.25]) by mail.cloudmark.com with bizsmtp id 0Dco1j0010ZaKgw01Dco6e; Fri, 20 Apr 2012 06:36:54 -0700
X-CMAE-Match: 0
X-CMAE-Score: 0.00
X-CMAE-Analysis: v=2.0 cv=RaES+iRv c=1 sm=1 a=LdFkGDrDWH2mcjCZERnC4w==:17 a=ldJM1g7oyCcA:10 a=vWDRnAXyDpsA:10 a=zutiEJmiVI4A:10 a=kj9zAlcOel0A:10 a=xqWC_Br6kY4A:10 a=6KNn6gTf59IYLXjdy6EA:9 a=MDLUDmMw_pDml9PFJQAA:7 a=CjuIK1q_8ugA:10 a=LdFkGDrDWH2mcjCZERnC4w==:117
Received: from EXCH-MBX901.corp.cloudmark.com ([fe80::addf:849a:f71c:4a82]) by exch-htcas901.corp.cloudmark.com ([fe80::2524:76b6:a865:539c%10]) with mapi id 14.01.0355.002; Fri, 20 Apr 2012 06:36:48 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "ietf@ietf.org" <ietf@ietf.org>, "wgchairs@ietf.org" <wgchairs@ietf.org>
Subject: RE: Proposed IESG Statement on the Conclusion of Experiments
Thread-Topic: Proposed IESG Statement on the Conclusion of Experiments
Thread-Index: Ac0ea1trQ6bEEENVRsKUUaoiCTZbygAjpwXw
Date: Fri, 20 Apr 2012 13:36:48 +0000
Message-ID: <9452079D1A51524AA5749AD23E0039280FBFC3@exch-mbx901.corp.cloudmark.com>
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk>
In-Reply-To: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [67.160.203.60]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudmark.com; s=default; t=1334929014; bh=yvZ9jp9nonTXMjsDjcK/qjUf6J9IPKE6uHsXZARUf9c=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=ng3YceZlJRM136rcmRvpFJJLlbzBoElqh9SlIOxh5n2pUKOnsYbhSgKvpWtcguVpn CMYnSjlvynRc6eTbCLTMrFv0+QCuiSoDGz6T7U7+irpt2PUfqoENZSPx5iFED4nQyA Dfvo/Zb0Be7q3O+r8y8P88+bBBJ8AgbKvHlQCD70=
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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, 20 Apr 2012 13:38:35 -0000

What about the idea of requiring new Experimental documents to include text=
 that indicates when the experiment is to be considered completed absent ne=
w work on it?  Essentially, the document declares a date by which the exper=
iment is considered concluded, and code points automatically deprecated, an=
d the document itself goes to Historic status, unless some other document a=
ction updates the deadline or moves the work to the Standards Track.

Keeping track of such dates to trigger these actions by default becomes a n=
ew burden for the Secretariat, I imagine.  I don't know what that cost woul=
d be compared to the "cost" of experiments currently languishing in this un=
resolved state.

To Eliot's point, work that is resumed much later could always restore docu=
ment and code point status and declare new drop-dead dates when it becomes =
interesting again.

-MSK


From ned.freed@mrochek.com  Fri Apr 20 00:35:30 2012
Return-Path: <ned.freed@mrochek.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 ED9B421F8551; Fri, 20 Apr 2012 00:35:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.483
X-Spam-Level: 
X-Spam-Status: No, score=-2.483 tagged_above=-999 required=5 tests=[AWL=0.116,  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 Y9p1x+Vnmo4e; Fri, 20 Apr 2012 00:35:29 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 484FF21F8557; Fri, 20 Apr 2012 00:35:29 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OEITGQD5CW006HAP@mauve.mrochek.com>; Fri, 20 Apr 2012 00:35:25 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OEGM6GSINK00ZGHB@mauve.mrochek.com>; Fri, 20 Apr 2012 00:35:22 -0700 (PDT)
Message-id: <01OEITGOW2LW00ZGHB@mauve.mrochek.com>
Date: Fri, 20 Apr 2012 00:33:08 -0700 (PDT)
From: Ned Freed <ned.freed@mrochek.com>
Subject: Re: Proposed IESG Statement on the Conclusion of Experiments
In-reply-to: "Your message dated Fri, 20 Apr 2012 08:19:53 +0100" <4F910E19.5080303@gmail.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk> <248A261F-D83D-4F97-8F5D-A9A0BCD2EC0D@sobco.com> <13205C286662DE4387D9AF3AC30EF456D76A76098B@EMBX01-WF.jnpr.net> <4F910E19.5080303@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1334907353; bh=16AkawqDtnXM2gvX6Q+rs9+HiBH24zQhoyX2HrtdcKk=; h=Cc:Message-id:Date:From:Subject:In-reply-to:MIME-version: Content-type:References:To; b=ZgSxEQmGwbxmyC2Ud6nTRJo3tQBtz3MG6QRfZwRT3H8R4t8JCRM9yktE4m+bgQb+/ Z49B01xWhrYL6Cj/kqSasBE3bNyQngHTSj4smHe3zhNoeXbrVcv/JP20yUK2msHifo cFfp9rgBBg99Byxd2IwQnPZMlJPoc8kdc3Z0ma1w=
X-Mailman-Approved-At: Fri, 20 Apr 2012 07:02:18 -0700
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, Scott O Bradner <sob@sobco.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Apr 2012 07:35:30 -0000

> On 2012-04-19 23:27, Ronald Bonica wrote:
> ...
> > I think that this is a case-by-case judgment call. In some cases (e.g., RFC 1475), the experiment is clearly over. IMO, allowing RFC 1475 to retain EXPERIMENTAL status detracts from the credibility of current experiments that share the label.

> I agree that it is case by case, so I don't really see the value in the
> IESG statement. If it's appropriate to write an experiment-terminating
> RFC, do so; if it's inappropriate, don't bother. That doesn't need
> any new legislation.

While I agree 100% that this needs to be handled on a case-by-case basis, I
also think that it's an issue that always needs to be addressed when an
experiment ends. So some sort of statement saying that the handling of any
allocations associated with the experiment must be resolved when the experiment
ends might be appropriate. Or not - this could just be something to add to some
checklist somewhere. (We do have checklists for this sort of thing, right?)

				Ned

From robert@raszuk.net  Fri Apr 20 00:49:13 2012
Return-Path: <robert@raszuk.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 98E1521F8707 for <wgchairs@ietfa.amsl.com>; Fri, 20 Apr 2012 00:49:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.923
X-Spam-Level: 
X-Spam-Status: No, score=-1.923 tagged_above=-999 required=5 tests=[AWL=0.057,  BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XbE9X9TtPbIu for <wgchairs@ietfa.amsl.com>; Fri, 20 Apr 2012 00:49:13 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id 3641621F85D3 for <wgchairs@ietf.org>; Fri, 20 Apr 2012 00:49:13 -0700 (PDT)
Received: (qmail 6977 invoked by uid 399); 20 Apr 2012 07:42:31 -0000
Received: from unknown (HELO ?10.0.1.3?) (pbs:robert@raszuk.net@216.31.254.135) by mail1310.opentransfer.com with ESMTPM; 20 Apr 2012 07:42:31 -0000
X-Originating-IP: 216.31.254.135
Message-ID: <4F911367.2060405@raszuk.net>
Date: Fri, 20 Apr 2012 09:42:31 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Proposed IESG Statement on the Conclusion of Experiments
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk>	<248A261F-D83D-4F97-8F5D-A9A0BCD2EC0D@sobco.com> <13205C286662DE4387D9AF3AC30EF456D76A76098B@EMBX01-WF.jnpr.net> <4F910E19.5080303@gmail.com>
In-Reply-To: <4F910E19.5080303@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Fri, 20 Apr 2012 07:02:18 -0700
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, Scott O Bradner <sob@sobco.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Apr 2012 07:49:13 -0000

Hi Brian,

My personal observation is that some folks are just too afraid about 
success of some 12 experimental RFCs to be published soon and are 
already actively seeking a formal way to kill them in the not too 
distant future.

If the goal here is really about clean-up of dead experiments - I would 
highly recommend to add a clear definition to the mentioned IESG 
Statement (if at all needed) that this is applicable only to those 
experiments which are no longer being actively tested in any way.

If anyone on the respective list would state that he is still testing 
given experimental RFC for as long as it takes I am against moving such 
RFC to historic status. If no one would care to respond within min 4-6 
weeks period I see no reason to block corresponding allocations.

Best regards,
R.


> On 2012-04-19 23:27, Ronald Bonica wrote: ...
>> I think that this is a case-by-case judgment call. In some cases
>> (e.g., RFC 1475), the experiment is clearly over. IMO, allowing RFC
>> 1475 to retain EXPERIMENTAL status detracts from the credibility of
>> current experiments that share the label.
>
> I agree that it is case by case, so I don't really see the value in
> the IESG statement. If it's appropriate to write an
> experiment-terminating RFC, do so; if it's inappropriate, don't
> bother. That doesn't need any new legislation.
>
> Brian

From john@jlc.net  Fri Apr 20 04:38:58 2012
Return-Path: <john@jlc.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 4CFF521F8745; Fri, 20 Apr 2012 04:38:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.003
X-Spam-Level: 
X-Spam-Status: No, score=-106.003 tagged_above=-999 required=5 tests=[AWL=0.596, 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 szoYvvQy8LBd; Fri, 20 Apr 2012 04:38:57 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 6A3F921F8746; Fri, 20 Apr 2012 04:38:57 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id AD68033C20; Fri, 20 Apr 2012 07:38:56 -0400 (EDT)
Date: Fri, 20 Apr 2012 07:38:56 -0400
From: John Leslie <john@jlc.net>
To: Adrian Farrel <adrian@olddog.co.uk>
Subject: Re: Proposed IESG Statement on the Conclusion of Experiments
Message-ID: <20120420113856.GM99904@verdi>
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk> <759FD9FB-D281-4D78-AA10-1F1AFA2B1FCB@netapp.com> <111c01cd1ece$fa283e10$ee78ba30$@olddog.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <111c01cd1ece$fa283e10$ee78ba30$@olddog.co.uk>
User-Agent: Mutt/1.4.1i
X-Mailman-Approved-At: Fri, 20 Apr 2012 07:02:18 -0700
Cc: wgchairs@ietf.org, ietf@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, 20 Apr 2012 11:38:58 -0000

Adrian Farrel <adrian@olddog.co.uk> wrote:
> [Lars Eggert wrote:]
>> On Apr 19, 2012, at 22:31, Adrian Farrel wrote:
>> 
>>> The IESG has been discussing how to tidy up after Experimental RFCs.

   The IESG (IMHO) feels it has a responsibility to manage Experiments
it starts. This is evidenced by the care they take to craft a path by
which Experimental RFCs can be backed out. "Tidy up after" may not quite
capture their intent here. They want results of experiments to be
documented, and they want experiments they start to conclude.

>>> We have developed the following draft IESG statement. This does not
>>> represent a change in process, and continues to value Experimental RFCs
>>> as an important part of the IETF process. It does, however, seek to
>>> encourage documentation of the conclusion of experiments.

   This statement captures the IESG intent better, though it omits to
state "experiments the IESG is responsible for".

>> any IESG statement would only cover Experimental RFCs on the IETF Stream,
>> right?
> 
> Clearly the IESG does not have authority over the IRTF stream.

   Hopefully this clarification remedies that omission.

====

   I don't really have an opinion on how the IESG should manage
IETF-stream experiments.

   Suggestions on how to manage IESG-stream experiments would be helpful
here. I would hope that opinions on how IRTF-stream experiments should
be managed will find a different thread, ideally in a different list.

--
John Leslie <john@jlc.net>

From stbryant@cisco.com  Fri Apr 20 08:12:49 2012
Return-Path: <stbryant@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 0383621F879C; Fri, 20 Apr 2012 08:12:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.546
X-Spam-Level: 
X-Spam-Status: No, score=-110.546 tagged_above=-999 required=5 tests=[AWL=0.053, 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 8Pk1d76Jys1e; Fri, 20 Apr 2012 08:12:46 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 66EB321F87A4; Fri, 20 Apr 2012 08:12:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=750; q=dns/txt; s=iport; t=1334934765; x=1336144365; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=8uXHUEYHCVKIUhahv5N4xZOm4HQ7d6DvuW8bYAzdmUs=; b=kXIpVNE9LL7+qo+1dK64MyffdkOVkHB0/Xd4pkx7HuCQE3aU569kadyb OppcCOB8Hh1wz27WpK3RKCiGS0iOnEv2RogDSLd3AzLZOd2/ZYefQRIGN DhQreqH7mLLZLJkoAT/PkCET4golia3pm7/K/HkyNcERs/2yC8zkWdxEU M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhkFAGJ7kU+Q/khN/2dsb2JhbABDriODFYEHggkBAQEEEgECI0ABEAsYCRYPCQMCAQIBRQYNAQcBAR6HbZppgz8QnGaQZwSVeY5UgQJngmg
X-IronPort-AV: E=Sophos;i="4.75,453,1330905600"; d="scan'208";a="135788512"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-1.cisco.com with ESMTP; 20 Apr 2012 15:12:34 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id q3KFCYhk032401; Fri, 20 Apr 2012 15:12:34 GMT
Received: from stbryant-mac2.local (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id q3KFCXLo002996; Fri, 20 Apr 2012 16:12:34 +0100 (BST)
Message-ID: <4F917CE1.5090403@cisco.com>
Date: Fri, 20 Apr 2012 16:12:33 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: "Murray S. Kucherawy" <msk@cloudmark.com>
Subject: Re: Proposed IESG Statement on the Conclusion of Experiments
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk> <9452079D1A51524AA5749AD23E0039280FBFC3@exch-mbx901.corp.cloudmark.com>
In-Reply-To: <9452079D1A51524AA5749AD23E0039280FBFC3@exch-mbx901.corp.cloudmark.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "ietf@ietf.org" <ietf@ietf.org>, "wgchairs@ietf.org" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Apr 2012 15:12:49 -0000

On 20/04/2012 14:36, Murray S. Kucherawy wrote:
> What about the idea of requiring new Experimental documents to include text that indicates when the experiment is to be considered completed absent new work on it?  Essentially, the document declares a date by which the experiment is considered concluded, and code points automatically deprecated, and the document itself goes to Historic status, unless some other document action updates the deadline or moves the work to the Standards Track.
If you factor in the historic success rate that engineers typically have 
in predicting s/w development schedules, I would expect that the overrun 
rate on predicted end exp dates would be  close to 100%, even after 
several extensions.

- Stewart

From brian.e.carpenter@gmail.com  Fri Apr 20 08:23:53 2012
Return-Path: <brian.e.carpenter@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 8F48021F8782; Fri, 20 Apr 2012 08:23:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.583
X-Spam-Level: 
X-Spam-Status: No, score=-101.583 tagged_above=-999 required=5 tests=[AWL=0.108, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QJz7sV93Yp5b; Fri, 20 Apr 2012 08:23:53 -0700 (PDT)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3092921F872A; Fri, 20 Apr 2012 08:23:52 -0700 (PDT)
Received: by eeke51 with SMTP id e51so2673421eek.31 for <multiple recipients>; Fri, 20 Apr 2012 08:23:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=G+2IGb9efUWyq8PqrcL0s99+xo6K+/9eQGnK+OPARD8=; b=ovHHETeQOH+Q/EcL1Vhi5HAHVuOCKNO/1CPJ6FRXsrcImh0MLGHOLF6vt4hEhxRFnV HVL5faKfaj1auMhEsyY1c+PDOe2bAxdL18eMysqv82YhuxVe+gFnmI0XFIrRqnCtTFLb Oup2qoS4JQqQk0LtHLXVkpKDPIS4qmWptN720bGLJl8SsHIKj50qYC8e1oiDVVvjaOhC rM8dU5NM39W8UobBm5j2tVIYS6SMvfHR9/DgoX8tQ7ZSrxo+/ya/yi/q6ewwLi6olhpT avNCSEbJVcmwMSk4TVp9tfN3VsnVyuzDNKfpaFI9ESJIgNZWVMGiS10KGy0gTykmXMwd /PmQ==
Received: by 10.14.94.195 with SMTP id n43mr1174163eef.57.1334935431352; Fri, 20 Apr 2012 08:23:51 -0700 (PDT)
Received: from [192.168.1.64] (host-2-102-216-233.as13285.net. [2.102.216.233]) by mx.google.com with ESMTPS id q45sm27727200eem.7.2012.04.20.08.23.49 (version=SSLv3 cipher=OTHER); Fri, 20 Apr 2012 08:23:50 -0700 (PDT)
Message-ID: <4F917F84.5040702@gmail.com>
Date: Fri, 20 Apr 2012 16:23:48 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: stbryant@cisco.com
Subject: Re: Proposed IESG Statement on the Conclusion of Experiments
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk>	<9452079D1A51524AA5749AD23E0039280FBFC3@exch-mbx901.corp.cloudmark.com> <4F917CE1.5090403@cisco.com>
In-Reply-To: <4F917CE1.5090403@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "ietf@ietf.org" <ietf@ietf.org>, "wgchairs@ietf.org" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Apr 2012 15:23:53 -0000

On 2012-04-20 16:12, Stewart Bryant wrote:
> On 20/04/2012 14:36, Murray S. Kucherawy wrote:
>> What about the idea of requiring new Experimental documents to include
>> text that indicates when the experiment is to be considered completed
>> absent new work on it?  Essentially, the document declares a date by
>> which the experiment is considered concluded, and code points
>> automatically deprecated, and the document itself goes to Historic
>> status, unless some other document action updates the deadline or
>> moves the work to the Standards Track.
> If you factor in the historic success rate that engineers typically have
> in predicting s/w development schedules, I would expect that the overrun
> rate on predicted end exp dates would be  close to 100%, even after
> several extensions.

Exactly. This whole discussion seems to be about over-engineering a
small corner of the IETF process that isn't a particular source
of practical problems anyway, afaik.

So, the standard question: what's the problem that needs solving here?

   Brian

From jhutz@cmu.edu  Fri Apr 20 09:07:42 2012
Return-Path: <jhutz@cmu.edu>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7462421F8744 for <wgchairs@ietfa.amsl.com>; Fri, 20 Apr 2012 09:07:42 -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 8t4q3RBJHdIV for <wgchairs@ietfa.amsl.com>; Fri, 20 Apr 2012 09:07:41 -0700 (PDT)
Received: from smtp02.srv.cs.cmu.edu (SMTP02.SRV.CS.CMU.EDU [128.2.217.197]) by ietfa.amsl.com (Postfix) with ESMTP id 8004521F85AD for <wgchairs@ietf.org>; Fri, 20 Apr 2012 09:07:41 -0700 (PDT)
Received: from [192.168.202.157] (pool-98-111-232-78.pitbpa.fios.verizon.net [98.111.232.78]) (authenticated bits=0) by smtp02.srv.cs.cmu.edu (8.13.6/8.13.6) with ESMTP id q3KG7apr002109 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 20 Apr 2012 12:07:37 -0400 (EDT)
Subject: RE: Formats for WG and BOF Agendas
From: Jeffrey Hutzelman <jhutz@cmu.edu>
To: John C Klensin <john-ietf@jck.com>
In-Reply-To: <14875_1334839446_q3JCi4gt024517_01D86B13EFF01AE45550B050@JcK-HP8200.jck.com>
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com> <D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com> <B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com> <66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com> <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com> <0e3201cd1e1e$66184090$3248c1b0$@olddog.co.uk> <14875_1334839446_q3JCi4gt024517_01D86B13EFF01AE45550B050@JcK-HP8200.jck.com>
Content-Type: text/plain; charset="UTF-8"
Date: Fri, 20 Apr 2012 12:07:36 -0400
Message-ID: <1334938056.21993.94.camel@destiny.pc.cs.cmu.edu>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.3 
Content-Transfer-Encoding: 7bit
X-Scanned-By: mimedefang-cmuscs on 128.2.217.197
Cc: 'IETF WG Chairs' <wgchairs@ietf.org>, 'Russ Housley' <housley@vigilsec.com>, adrian@olddog.co.uk, 'Ryan Cross' <rcross@amsl.com>, 'Henrik Levkowetz' <henrik@levkowetz.com>, jhutz@cmu.edu
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Apr 2012 16:07:42 -0000

On Thu, 2012-04-19 at 08:43 -0400, John C Klensin wrote:

> Just an observation about the "so links can be embedded" reason
> for permitting HTML...  I have never had any trouble putting
> URIs into text files, nor with using those links once they are
> inserted.  As a trivial example, http://www.ietf.org/ goes
> perfectly well into this text/plain message.

... and when I click on it, the IETF web site pops up.




From dhc@dcrocker.net  Fri Apr 20 09:16:05 2012
Return-Path: <dhc@dcrocker.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 8D06B21F855F; Fri, 20 Apr 2012 09:16:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.099
X-Spam-Level: 
X-Spam-Status: No, score=-4.099 tagged_above=-999 required=5 tests=[AWL=-1.500, 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 0Sth0+3QNauT; Fri, 20 Apr 2012 09:16:04 -0700 (PDT)
Received: from sbh11.songbird.com (sbh11.songbird.com [72.52.113.11]) by ietfa.amsl.com (Postfix) with ESMTP id 86B4E21F8555; Fri, 20 Apr 2012 09:16:04 -0700 (PDT)
Received: from [192.168.1.11] (adsl-67-127-58-62.dsl.pltn13.pacbell.net [67.127.58.62]) (authenticated bits=0) by sbh11.songbird.com (8.13.8/8.13.8) with ESMTP id q3KGFoCY025858 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 20 Apr 2012 09:16:01 -0700
Message-ID: <4F918BB0.3080505@dcrocker.net>
Date: Fri, 20 Apr 2012 09:15:44 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Proposed IESG Statement on the Conclusion of Experiments
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk> <9452079D1A51524AA5749AD23E0039280FBFC3@exch-mbx901.corp.cloudmark.com>
In-Reply-To: <9452079D1A51524AA5749AD23E0039280FBFC3@exch-mbx901.corp.cloudmark.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh11.songbird.com [72.52.113.11]); Fri, 20 Apr 2012 09:16:04 -0700 (PDT)
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Apr 2012 16:16:05 -0000

On 4/20/2012 6:36 AM, Murray S. Kucherawy wrote:
> What about the idea of requiring new Experimental documents to
> include text that indicates when the experiment is to be considered
> completed absent new work on it?  Essentially, the document declares
> a date by which the experiment is considered concluded,
...
> To Eliot's point, work that is resumed much later could always
> restore document and code point status and declare new drop-dead
> dates when it becomes interesting again.


As Brian notes, "dates" are probably unlikely to be useful while also 
imposing additional administrative tracking overhead.

On the other hand, objective performance/achievement criteria --
statements that describe what experiential information is being sought
-- would be useful to encourage.

d/

-- 


-- 
  Dave Crocker
  bbiw.net

From housley@vigilsec.com  Fri Apr 20 09:55:23 2012
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 B388D21F85A4 for <wgchairs@ietfa.amsl.com>; Fri, 20 Apr 2012 09:55:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.268
X-Spam-Level: 
X-Spam-Status: No, score=-102.268 tagged_above=-999 required=5 tests=[AWL=0.331, 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 qCOfAcRa9T88 for <wgchairs@ietfa.amsl.com>; Fri, 20 Apr 2012 09:55:23 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 0518821F8555 for <wgchairs@ietf.org>; Fri, 20 Apr 2012 09:55:23 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 57692F2403F; Fri, 20 Apr 2012 12:55:42 -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 XtJ7MIvqCWN5; Fri, 20 Apr 2012 12:55:14 -0400 (EDT)
Received: from [192.168.2.100] (pool-96-255-140-3.washdc.fios.verizon.net [96.255.140.3]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id B132AF2403C; Fri, 20 Apr 2012 12:55:41 -0400 (EDT)
Subject: Re: Formats for WG and BOF Agendas
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <1334938056.21993.94.camel@destiny.pc.cs.cmu.edu>
Date: Fri, 20 Apr 2012 12:55:20 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <C153B9DD-4A3A-4FCE-B29A-C4857E7CFC78@vigilsec.com>
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com> <D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com> <B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com> <66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com> <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com> <0e3201cd1e1e$66184090$3248c1b0$@olddog.co.uk> <14875_1334839446_q3JCi4gt024517_01D86B13EFF01AE45550B050@JcK-HP8200.jck.com> <1334938056.21993.94.camel@destiny.pc.cs.cmu.edu>
To: IETF WG Chairs <wgchairs@ietf.org>
X-Mailer: Apple Mail (2.1084)
Cc: Ryan Cross <rcross@amsl.com>, 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: Fri, 20 Apr 2012 16:55:23 -0000

This is the consensus that I am hearing:

(1) The format independent URLs are desirable.  Let's make that happen.

(2) Agendas should be limited to text and html.

(3) Minutes should be limited to text, html, and pdf.

Russ


From marc.blanchet@viagenie.ca  Fri Apr 20 12:06:05 2012
Return-Path: <marc.blanchet@viagenie.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 1F39A21F85AC; Fri, 20 Apr 2012 12:06:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.569
X-Spam-Level: 
X-Spam-Status: No, score=-102.569 tagged_above=-999 required=5 tests=[AWL=0.030, 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 lhBd0BX7nTn5; Fri, 20 Apr 2012 12:06:04 -0700 (PDT)
Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by ietfa.amsl.com (Postfix) with ESMTP id 61BFF21F8565; Fri, 20 Apr 2012 12:06:04 -0700 (PDT)
Received: from h99.viagenie.ca (h99.viagenie.ca [206.123.31.99]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 40C77415D0; Fri, 20 Apr 2012 15:06:03 -0400 (EDT)
Subject: Re: Proposed IESG Statement on the Conclusion of Experiments
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=iso-8859-1
From: Marc Blanchet <marc.blanchet@viagenie.ca>
In-Reply-To: <248A261F-D83D-4F97-8F5D-A9A0BCD2EC0D@sobco.com>
Date: Fri, 20 Apr 2012 15:06:02 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <ADA64B45-D455-4696-8E28-B4793EE2F9BC@viagenie.ca>
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk> <248A261F-D83D-4F97-8F5D-A9A0BCD2EC0D@sobco.com>
To: Scott O Bradner <sob@sobco.com>
X-Mailer: Apple Mail (2.1257)
Cc: adrian@olddog.co.uk, 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: Fri, 20 Apr 2012 19:06:05 -0000

I agree with everything Scott wrote. I don't see a good reason for =
removing code points from a registry, unless very exceptional cases =
(range is almost full need more space), which could be processed as =
one-off, not as a regular process.

Marc.

Le 2012-04-19 =E0 16:48, Scott O Bradner a =E9crit :

> encouraging a report is fine
>=20
> retracting the code points seems to add more confusion than it is =
worth unless the
> code space is very tight
>=20
> and I see no reason to obsolete the experimental rfc or move it to =
historic status unless the report is
> that some bad thing happens when you try it out - updating the old rfc =
is fine
>=20
> and I agree with Elliot about the nature of research - it is very =
common to not
> reach a conclusion that something is bad (as in bad for the net) - and =
that is the
> only case where I think that an experiment should be flagged as a =
don't go there situation
>=20
> Scott
>=20
>=20
> On Apr 19, 2012, at 4:31 PM, Adrian Farrel wrote:
>=20
>> All,
>>=20
>> The IESG has been discussing how to tidy up after Experimental RFCs.
>>=20
>> We have developed the following draft IESG statement. This does not=20=

>> represent a change in process, and continues to value Experimental =
RFCs
>> as an important part of the IETF process. It does, however, seek to=20=

>> encourage documentation of the conclusion of experiments.
>>=20
>> We are aware that there may be other discussion points around=20
>> Experimental RFCs, and we would like to discuss these, but we also
>> believe that there is merit in making small, incremental =
improvements.
>>=20
>> The IESG would welcome your thoughts on this draft before they =
approve
>> the final text on April 26th.
>>=20
>> Thanks,
>> Adrian
>>=20
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>=20
>> IESG Statement on Conclusion of IETF Experiments
>>=20
>>=20
>> Experiments are an established and valuable part of the IETF process.
>> A number of core Internet protocols were first published as =
Experimental
>> RFCs while the community gathered experience and carefully =
investigated
>> the consequences of deploying new mechanisms within the Internet.
>>=20
>> In the case where an experiment leads on to the development of a     =20=

>> Standards Track RFC documenting a protocol, the new RFC obsoletes the=20=

>> old Experimental RFC and there is a clear conclusion to the =
experiment.
>>=20
>> However, many experiments do not lead to the development of Standards
>> Track RFCs. Instead, the work may be abandoned through lack of =
interest
>> or because important lessons have been learned.
>>=20
>> It is currently hard to distinguish between an experiment that is =
still
>> being investigated, and an old experiment that has ceased to be of
>> interest to the community. In both cases an Experimental RFC exists =
in
>> the repository and newcomers might easily be misled into thinking =
that
>> it would be helpful to conduct more research into an abandoned
>> experiment.
>>=20
>> In view of this, the original proponents of experiments (that is,=20
>> authors of Experimental RFCs, and Working Groups that requested the
>> publication of Experimental RFCs) are strongly encouraged to document
>> the termination of experiments that do not result in subsequent
>> Standards Track work by publishing an Informational RFC that:
>>=20
>> - very briefly describes the results of the experiment
>>=20
>> - obsoletes the Experimental RFC
>>=20
>> - if appropriate, deprecate any IANA code points allocated for the=20
>> experiment
>>=20
>> - may request that the Experimental RFC is moved to Historic status.
>>=20
>> If there is no energy in the community for the producing such an
>> Informational RFC, if the authors have moved on to other things, or =
if
>> the Working Group has been closed down, Area Directors should author =
or
>> seek volunteers to author such an Informational RFC.
>>=20


From melinda.shore@gmail.com  Fri Apr 20 12:27:30 2012
Return-Path: <melinda.shore@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 8467721F85B9; Fri, 20 Apr 2012 12:27:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UtIvbYjqKv27; Fri, 20 Apr 2012 12:27:30 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1022B21F85B8; Fri, 20 Apr 2012 12:27:30 -0700 (PDT)
Received: by pbbrp16 with SMTP id rp16so1449953pbb.31 for <multiple recipients>; Fri, 20 Apr 2012 12:27:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=V+RcxPnn1uh1SQfHHXZEwDK0j/S4jIssfgmuw5LouwE=; b=dJeXybFxhmYRlVgG/60xPE69jN8XZtydrH67QCDAQh2watV8a34M5bri6bCDa5uQr/ VNSdGqx7BKBI70dgScESTDSFt48Wsxk9/Tv34r1Q23LXiLfaWnxBhpY3+Py54qQZxvms PAmmCgLoc9C5mxczcUNy16XSNbaxpCtffcxEyhQf0Rc+HyMDFZ8CP+COiXNja6eV1ISe leWoz7CcjmZGEq2AHnF0wQRxnUmuIgUXF1RaWiyn0IdILYqU26gNb17Lmyw9N4ZZLig2 ckLBHe0ndIPiUb7fgbxekiJQy8WhC3e3nF6ZF6pWhoZdUo+jNj6TFNtyNnxHq92Pc+xr M7ow==
Received: by 10.68.191.164 with SMTP id gz4mr1203173pbc.133.1334950049900; Fri, 20 Apr 2012 12:27:29 -0700 (PDT)
Received: from polypro.local (66-230-81-245-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.81.245]) by mx.google.com with ESMTPS id w10sm6132024pbk.30.2012.04.20.12.27.27 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 20 Apr 2012 12:27:29 -0700 (PDT)
Message-ID: <4F91B89D.2060706@gmail.com>
Date: Fri, 20 Apr 2012 11:27:25 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Proposed IESG Statement on the Conclusion of Experiments
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk>	<9452079D1A51524AA5749AD23E0039280FBFC3@exch-mbx901.corp.cloudmark.com> <4F917CE1.5090403@cisco.com> <4F917F84.5040702@gmail.com>
In-Reply-To: <4F917F84.5040702@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "ietf@ietf.org" <ietf@ietf.org>, "wgchairs@ietf.org" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Apr 2012 19:27:30 -0000

On 4/20/12 7:23 AM, Brian E Carpenter wrote:
> Exactly. This whole discussion seems to be about over-engineering a
> small corner of the IETF process that isn't a particular source
> of practical problems anyway, afaik.

Reading the back-and-forth on this I think at this point I feel pretty
strongly that I don't support the proposal.  If someone wants to take
it upon themselves to badger authors of drafts that might be published
as experimental protocols, fine, but even while (heaven knows) I'm a
fan of "process" stuff this really seems overly legalistic and not a
solution for anything that's clearly a problem.

So, no.

Melinda

From ynir@checkpoint.com  Fri Apr 20 13:49:23 2012
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 D88BC21F85D8; Fri, 20 Apr 2012 13:49:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.55
X-Spam-Level: 
X-Spam-Status: No, score=-10.55 tagged_above=-999 required=5 tests=[AWL=0.049,  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 UsjaJsat2BJl; Fri, 20 Apr 2012 13:49:23 -0700 (PDT)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 8FE1B21F85D5; Fri, 20 Apr 2012 13:49:22 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id q3KKnGFW016573;  Fri, 20 Apr 2012 23:49:16 +0300
X-CheckPoint: {4F91D886-0-1B221DC2-5FFFF}
Received: from il-ex03.ad.checkpoint.com (194.29.34.71) by il-ex01.ad.checkpoint.com (194.29.34.26) with Microsoft SMTP Server (TLS) id 8.3.213.0; Fri, 20 Apr 2012 23:49:17 +0300
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex03.ad.checkpoint.com ([194.29.34.71]) with mapi; Fri, 20 Apr 2012 23:49:15 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Date: Fri, 20 Apr 2012 23:49:13 +0300
Subject: Re: Proposed IESG Statement on the Conclusion of Experiments
Thread-Topic: Proposed IESG Statement on the Conclusion of Experiments
Thread-Index: Ac0fNwvObo4TTwRCScSogL1KohHhaA==
Message-ID: <667942B0-31E6-4012-9949-D68ED380011C@checkpoint.com>
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk> <40D324FA-D3BA-47FA-AC32-E1326D6A375A@checkpoint.com> <20120420024035.GL94829@mail.yitter.info>
In-Reply-To: <20120420024035.GL94829@mail.yitter.info>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
x-cpdlp: 11dc94408f929c47a7ea6d9267cd5525bac1b449a8
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-KSE-AntiSpam-Interceptor-Info: protection disabled
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>, "ietf@ietf.org" <ietf@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, 20 Apr 2012 20:49:24 -0000

On Apr 20, 2012, at 5:40 AM, Andrew Sullivan wrote:

> On Fri, Apr 20, 2012 at 12:17:46AM +0300, Yoav Nir wrote:
>=20
>>   The "Experimental" designation typically denotes a specification that
>>   is part of some research or development effort.
>>=20
>> However, I do not believe that this is still typical. Authors come up wi=
th ideas that they think are useful. If when the documents are ready for pu=
blication it is still not clear whether there are enough implementers convi=
nced by the use case (some definition of running code), they are encouraged=
 to publish them as experimental rather than proposed standard.
>>=20
>=20
> Yes, and surely what we want is that we continue to mislabel as many
> RFCs as possible in this way. =20

No, I don't believe they are mislabeled, they just don't fit the statement =
in RFC 2026, and they're not scientific experiments. It gives fair warning =
to would-be implementers regarding the maturity of the specification. Other=
 implementations may not have implemented this RFC (if it's an extension), =
or they may solve the same problem with some other mechanism. Or they may e=
ven have implemented the same RFC, but we're not sure yet that it's unambig=
uous enough and error-free enough to produce interoperable implementations.

> We want to make our own contribution to
> the gradual reduction of all words to mean everything else, so that we
> can all communicate exclusively by mumbling, "Whatever."  Now that the
> AP Stylebook has given up on "hopefully" and Oxford is playing with
> the comma, anything goes.
>=20
>> Neither of these can really be called an "experiment" except in the
>> sense of "let's see if the Internet needs this specification".=20
>=20
> Yes, and that's a stupid meaning of the term in this case, because
> quite frankly all the rest of the RFCs are also experiments in this
> sense (and many of them have delivered the clarion answer, "Don't need
> it at all!"  When was the last time you used BEEP?)
>=20
> I don't know what I think about the proposal overall, but I will say
> that one thing definitely in its favour is that it would discourage
> those who think that "Experimental" is the Standards Track Consolation
> Prize Track.  I'd be wholeheartedly in its favour, except that the old
> "2 year review" standards track process didn't work, so we ditched
> it.  I don't see how recycling the approach with Experimental
> documents is any more likely to succeed.

True. Perhaps if successful standards were advanced form Proposed to someth=
ing else, there would be less pushback against publishing ideas with little=
 running code as PS. Surely your little idea with no running code can't be =
in the same category as TLS, right?


From rbonica@juniper.net  Fri Apr 20 14:01:20 2012
Return-Path: <rbonica@juniper.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 11EBE21F85E6; Fri, 20 Apr 2012 14:01:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.545
X-Spam-Level: 
X-Spam-Status: No, score=-106.545 tagged_above=-999 required=5 tests=[AWL=0.054, 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 gzwWdl2t1RJO; Fri, 20 Apr 2012 14:01:19 -0700 (PDT)
Received: from exprod7og113.obsmtp.com (exprod7og113.obsmtp.com [64.18.2.179]) by ietfa.amsl.com (Postfix) with ESMTP id 12C6F21F85DD; Fri, 20 Apr 2012 14:01:17 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob113.postini.com ([64.18.6.12]) with SMTP ID DSNKT5HOnUVIBRSqe23B+2QPM+vf/ibFGl2V@postini.com; Fri, 20 Apr 2012 14:01:19 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.3.213.0; Fri, 20 Apr 2012 13:56:56 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Fri, 20 Apr 2012 16:56:56 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "ietf@ietf.org" <ietf@ietf.org>, "wgchairs@ietf.org" <wgchairs@ietf.org>
Date: Fri, 20 Apr 2012 16:56:54 -0400
Subject: RE: Proposed IESG Statement on the Conclusion of Experiments
Thread-Topic: Proposed IESG Statement on the Conclusion of Experiments
Thread-Index: Ac0ea1trQ6bEEENVRsKUUaoiCTZbygAxt2ag
Message-ID: <13205C286662DE4387D9AF3AC30EF456D76A81D0EF@EMBX01-WF.jnpr.net>
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk>
In-Reply-To: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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, 20 Apr 2012 21:01:20 -0000

Folks,

I would like to clarify a few points regarding this statement. Specifically=
,=20

- It applies only to documents that were published on the IETF stream.
- It does not apply to documents that were published on the IAB, IRTF or In=
dependent streams.
- Reuse of deprecated code points is not a goal of this exercise.
- It does not recommend any change in IETF process.

Today, experiments can be concluded through either of the following actions=
:

- Obsoleting the EXPERIMENTAL RFC with a Standards Track document
- Publishing an INFORMATIONAL RFC that terminates the experiment and possib=
ly moves the EXPERIMENTAL RFC to HISTORIC

Today, both of these actions require community consensus. Today, both of th=
ese actions can be undertaken by anyone. If this IESG statement is publishe=
d, none of that changes.

                                             Ron



> -----Original Message-----
> From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of
> Adrian Farrel
> Sent: Thursday, April 19, 2012 4:31 PM
> To: ietf@ietf.org; wgchairs@ietf.org
> Cc: iesg@ietf.org
> Subject: Proposed IESG Statement on the Conclusion of Experiments
>=20
> All,
>=20
> The IESG has been discussing how to tidy up after Experimental RFCs.
>=20
> We have developed the following draft IESG statement. This does not
> represent a change in process, and continues to value Experimental RFCs
> as an important part of the IETF process. It does, however, seek to
> encourage documentation of the conclusion of experiments.
>=20
> We are aware that there may be other discussion points around
> Experimental RFCs, and we would like to discuss these, but we also
> believe that there is merit in making small, incremental improvements.
>=20
> The IESG would welcome your thoughts on this draft before they approve
> the final text on April 26th.
>=20
> Thanks,
> Adrian
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> IESG Statement on Conclusion of IETF Experiments
>=20
>=20
> Experiments are an established and valuable part of the IETF process.
> A number of core Internet protocols were first published as
> Experimental RFCs while the community gathered experience and carefully
> investigated the consequences of deploying new mechanisms within the
> Internet.
>=20
> In the case where an experiment leads on to the development of a
> Standards Track RFC documenting a protocol, the new RFC obsoletes the
> old Experimental RFC and there is a clear conclusion to the experiment.
>=20
> However, many experiments do not lead to the development of Standards
> Track RFCs. Instead, the work may be abandoned through lack of interest
> or because important lessons have been learned.
>=20
> It is currently hard to distinguish between an experiment that is still
> being investigated, and an old experiment that has ceased to be of
> interest to the community. In both cases an Experimental RFC exists in
> the repository and newcomers might easily be misled into thinking that
> it would be helpful to conduct more research into an abandoned
> experiment.
>=20
> In view of this, the original proponents of experiments (that is,
> authors of Experimental RFCs, and Working Groups that requested the
> publication of Experimental RFCs) are strongly encouraged to document
> the termination of experiments that do not result in subsequent
> Standards Track work by publishing an Informational RFC that:
>=20
> - very briefly describes the results of the experiment
>=20
> - obsoletes the Experimental RFC
>=20
> - if appropriate, deprecate any IANA code points allocated for the
>   experiment
>=20
> - may request that the Experimental RFC is moved to Historic status.
>=20
> If there is no energy in the community for the producing such an
> Informational RFC, if the authors have moved on to other things, or if
> the Working Group has been closed down, Area Directors should author or
> seek volunteers to author such an Informational RFC.


From randy_presuhn@mindspring.com  Fri Apr 20 16:04:20 2012
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 37C9D11E808A; Fri, 20 Apr 2012 16:04:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.592
X-Spam-Level: 
X-Spam-Status: No, score=-100.592 tagged_above=-999 required=5 tests=[AWL=0.518, BAYES_05=-1.11, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BDA+DNtA2JC5; Fri, 20 Apr 2012 16:04:19 -0700 (PDT)
Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) by ietfa.amsl.com (Postfix) with ESMTP id B162111E8088; Fri, 20 Apr 2012 16:04:19 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=bNqDBzQPGWBg3bvQpBYiH5asLkC+cs578t1PQc1WuAGECl+oj5JZvfJEB8VoOLKh; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [99.187.237.246] (helo=oemcomputer) by elasmtp-banded.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1SLMsE-0001Ce-Rc; Fri, 20 Apr 2012 19:04:19 -0400
Message-ID: <003f01cd1f4a$17e2e880$6b01a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <ietf@ietf.org>, <wgchairs@ietf.org>
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk> <13205C286662DE4387D9AF3AC30EF456D76A81D0EF@EMBX01-WF.jnpr.net>
Subject: Re: Proposed IESG Statement on the Conclusion of Experiments
Date: Fri, 20 Apr 2012 16:05:33 -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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d8882951211ce6890f88b735bcb8d6dcd9f233496107cdb131b4350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.187.237.246
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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, 20 Apr 2012 23:04:20 -0000

Hi -

> From: "Ronald Bonica" <rbonica@juniper.net>
> To: <adrian@olddog.co.uk>; <ietf@ietf.org>; <wgchairs@ietf.org>
> Sent: Friday, April 20, 2012 1:56 PM
> Subject: RE: Proposed IESG Statement on the Conclusion of Experiments
....
> If this IESG statement is published, none of that changes.

It might be helpful to say what *would* change upon publication
of this statement, and why the IESG believes it is important to make
that change, because we're obviously not unerstanding the
proposal in the same way.

Randy


From keith.drage@alcatel-lucent.com  Fri Apr 20 17:28:59 2012
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 86C4111E8095; Fri, 20 Apr 2012 17:28:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.017
X-Spam-Level: 
X-Spam-Status: No, score=-110.017 tagged_above=-999 required=5 tests=[AWL=0.232, BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 qecd4Z90t0CC; Fri, 20 Apr 2012 17:28:59 -0700 (PDT)
Received: from smail6.alcatel.fr (smail6.alcatel.fr [64.208.49.42]) by ietfa.amsl.com (Postfix) with ESMTP id BDC1211E8093; Fri, 20 Apr 2012 17:28:57 -0700 (PDT)
Received: from FRMRSSXCHHUB01.dc-m.alcatel-lucent.com (FRMRSSXCHHUB01.dc-m.alcatel-lucent.com [135.120.45.61]) by smail6.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q3L0Ssme009691 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sat, 21 Apr 2012 02:28:55 +0200
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.44]) by FRMRSSXCHHUB01.dc-m.alcatel-lucent.com ([135.120.45.61]) with mapi; Sat, 21 Apr 2012 02:28:54 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Date: Sat, 21 Apr 2012 02:28:52 +0200
Subject: RE: Proposed IESG Statement on the Conclusion of Experiments
Thread-Topic: Proposed IESG Statement on the Conclusion of Experiments
Thread-Index: Ac0fCZ+OBVdJauAtSByEWhZuSONfqAAS3Gsw
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE2260C3063@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk> <9452079D1A51524AA5749AD23E0039280FBFC3@exch-mbx901.corp.cloudmark.com> <4F917CE1.5090403@cisco.com> <4F917F84.5040702@gmail.com>
In-Reply-To: <4F917F84.5040702@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.84
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Apr 2012 00:28:59 -0000

Maybe I am the worst person to respond here but I agree with Brian.

I've always had a problem with the large number of different document types=
.

My overall view is that essentially market forces decide how a document is =
taken and implemented, and the IETF process has never had enough responsive=
ness to follow that in a timely fashion that has any real meaning. This app=
lies to proposed standard --> draft standard --> standard, and it will not =
be different here.

Changing something from experimental to proposed standard in a process that=
 will probably take 12 months will be unlikely change the number of people =
implementing and deploying an RFC.

Regards

Keith

> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
> Behalf Of Brian E Carpenter
> Sent: 20 April 2012 16:24
> To: stbryant@cisco.com
> Cc: adrian@olddog.co.uk; ietf@ietf.org; wgchairs@ietf.org
> Subject: Re: Proposed IESG Statement on the Conclusion of Experiments
>=20
> On 2012-04-20 16:12, Stewart Bryant wrote:
> > On 20/04/2012 14:36, Murray S. Kucherawy wrote:
> >> What about the idea of requiring new Experimental documents to include
> >> text that indicates when the experiment is to be considered completed
> >> absent new work on it?  Essentially, the document declares a date by
> >> which the experiment is considered concluded, and code points
> >> automatically deprecated, and the document itself goes to Historic
> >> status, unless some other document action updates the deadline or
> >> moves the work to the Standards Track.
> > If you factor in the historic success rate that engineers typically hav=
e
> > in predicting s/w development schedules, I would expect that the overru=
n
> > rate on predicted end exp dates would be  close to 100%, even after
> > several extensions.
>=20
> Exactly. This whole discussion seems to be about over-engineering a
> small corner of the IETF process that isn't a particular source
> of practical problems anyway, afaik.
>=20
> So, the standard question: what's the problem that needs solving here?
>=20
>    Brian

From melinda.shore@gmail.com  Fri Apr 20 17:37:33 2012
Return-Path: <melinda.shore@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 EB24921E8036; Fri, 20 Apr 2012 17:37:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sq6rVfwrDNu3; Fri, 20 Apr 2012 17:37:33 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 695F421E8011; Fri, 20 Apr 2012 17:37:33 -0700 (PDT)
Received: by pbbrp16 with SMTP id rp16so1664188pbb.31 for <multiple recipients>; Fri, 20 Apr 2012 17:37:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=wP59V/fYSRz7O45y5p1D6m6HRcSIMsvMJS0Gf/fwwAA=; b=eQUFRtd8tmRzlOKx6vHE+RW49Oqiek1ngLk6ZPRldMQQEGq1D8ZnAeRjDANwl4RaoT WtavUhYIk39Y6P8e1MDphLxGvDqQWACO2hx9XgZ4gJSfh4kFNYDPmcV5gPx58MGOjDy4 /HlUBl6ncDhPwJGw0kh8Lx2vIHKqQyc7MIbfSATrHylbIx9s1Z4PDKyVQrR7MlvAX0w5 8CeCP2ArbOn1sKu1JguvvYA4/2RHzQ3pdviXLyYoGVolWyg9sCRSpzWufoBfI0V6UNFp uPRI81Bi7B8SUGk3EgX35SsX049p7qIjsRH3V9gVT9LgsfXmZrg6GQNHaQ2jBD6Lcc0v U2XQ==
Received: by 10.68.216.225 with SMTP id ot1mr16687021pbc.46.1334968653143; Fri, 20 Apr 2012 17:37:33 -0700 (PDT)
Received: from polypro.local (66-230-81-245-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.81.245]) by mx.google.com with ESMTPS id vm4sm422065pbc.47.2012.04.20.17.37.31 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 20 Apr 2012 17:37:32 -0700 (PDT)
Message-ID: <4F92014A.4040707@gmail.com>
Date: Fri, 20 Apr 2012 16:37:30 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
Subject: Re: Proposed IESG Statement on the Conclusion of Experiments
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk> <9452079D1A51524AA5749AD23E0039280FBFC3@exch-mbx901.corp.cloudmark.com> <4F917CE1.5090403@cisco.com> <4F917F84.5040702@gmail.com> <EDC0A1AE77C57744B664A310A0B23AE2260C3063@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE2260C3063@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Apr 2012 00:37:34 -0000

On 4/20/12 4:28 PM, DRAGE, Keith (Keith) wrote:
> Changing something from experimental to proposed standard in a
> process that will probably take 12 months will be unlikely change the
> number of people implementing and deploying an RFC.

I'm going to take the liberty of mentioning that I spoke with Ron
earlier today about this.  Basically what he's asking is that there
be no process changes, and, I think, no policy changes, just
that IESG members should be mindful about how to phase experimental
stuff out when it's flopped.

Personally, I think he's correct about both cruft and mindfulness
and suspect that probably nearly everybody agrees with what he's
saying, anyway, but unfortunately it was presented in a form that
made it look like More Process.

Melinda

From aaron@serendipity.cx  Fri Apr 20 18:01:26 2012
Return-Path: <aaron@serendipity.cx>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1E2421E8041; Fri, 20 Apr 2012 18:01:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.643
X-Spam-Level: 
X-Spam-Status: No, score=-101.643 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bliAK9M02ZlH; Fri, 20 Apr 2012 18:01:26 -0700 (PDT)
Received: from slice.serendipity.cx (slice.serendipity.cx [67.23.2.90]) by ietfa.amsl.com (Postfix) with ESMTP id 2C14F21E8011; Fri, 20 Apr 2012 18:01:26 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by slice.serendipity.cx (Postfix) with ESMTPSA id BF46D32797; Fri, 20 Apr 2012 18:00:53 -0700 (PDT)
Received: by vcbfo1 with SMTP id fo1so3508862vcb.31 for <multiple recipients>; Fri, 20 Apr 2012 18:01:02 -0700 (PDT)
Received: by 10.52.72.227 with SMTP id g3mr2614086vdv.21.1334970062422; Fri, 20 Apr 2012 18:01:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.34.70 with HTTP; Fri, 20 Apr 2012 18:00:41 -0700 (PDT)
In-Reply-To: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk>
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk>
From: Aaron Stone <aaron@serendipity.cx>
Date: Fri, 20 Apr 2012 18:00:41 -0700
Message-ID: <CAEdAYKWvyMhGnbsXxh0MCfXoa5H9nf_wcD-WUxsm14KfE73b6A@mail.gmail.com>
Subject: Re: Proposed IESG Statement on the Conclusion of Experiments
To: adrian@olddog.co.uk
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: wgchairs@ietf.org, ietf@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Apr 2012 01:01:26 -0000

On Thu, Apr 19, 2012 at 1:31 PM, Adrian Farrel <adrian@olddog.co.uk> wrote:
> All,
>
> The IESG has been discussing how to tidy up after Experimental RFCs.
>
> We have developed the following draft IESG statement. This does not
> represent a change in process, and continues to value Experimental RFCs
> as an important part of the IETF process. It does, however, seek to
> encourage documentation of the conclusion of experiments.
>
> We are aware that there may be other discussion points around
> Experimental RFCs, and we would like to discuss these, but we also
> believe that there is merit in making small, incremental improvements.
>
> The IESG would welcome your thoughts on this draft before they approve
> the final text on April 26th.
>
> Thanks,
> Adrian
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> IESG Statement on Conclusion of IETF Experiments
>
>
> Experiments are an established and valuable part of the IETF process.
> A number of core Internet protocols were first published as Experimental
> RFCs while the community gathered experience and carefully investigated
> the consequences of deploying new mechanisms within the Internet.
>
> In the case where an experiment leads on to the development of a
> Standards Track RFC documenting a protocol, the new RFC obsoletes the
> old Experimental RFC and there is a clear conclusion to the experiment.
>
> However, many experiments do not lead to the development of Standards
> Track RFCs. Instead, the work may be abandoned through lack of interest
> or because important lessons have been learned.
>
> It is currently hard to distinguish between an experiment that is still
> being investigated, and an old experiment that has ceased to be of
> interest to the community. In both cases an Experimental RFC exists in
> the repository and newcomers might easily be misled into thinking that
> it would be helpful to conduct more research into an abandoned
> experiment.

If no concluding document has been written, then why wouldn't it be
useful to conduct further research?

It sounds like the main issue is negative results that aren't getting
published. We should encourage people to publish them. If they don't,
then of course someone may come along and revisit the experiment.
How's that any different if the experiment is moved to historical or
not? Old ideas that came before their time are often revisited to
useful outcomes.

If the result of this discussion is the statement below that
officially encourages publishing results, positive or negative, great.
If it's added process or any kind of automatic document expiration,
not great.

Cheers,
Aaron

> In view of this, the original proponents of experiments (that is,
> authors of Experimental RFCs, and Working Groups that requested the
> publication of Experimental RFCs) are strongly encouraged to document
> the termination of experiments that do not result in subsequent
> Standards Track work by publishing an Informational RFC that:
>
> - very briefly describes the results of the experiment
>
> - obsoletes the Experimental RFC
>
> - if appropriate, deprecate any IANA code points allocated for the
> =A0experiment
>
> - may request that the Experimental RFC is moved to Historic status.
>
> If there is no energy in the community for the producing such an
> Informational RFC, if the authors have moved on to other things, or if
> the Working Group has been closed down, Area Directors should author or
> seek volunteers to author such an Informational RFC.
>

From rbonica@juniper.net  Sat Apr 21 07:44:18 2012
Return-Path: <rbonica@juniper.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 6518A21F8589; Sat, 21 Apr 2012 07:44:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.547
X-Spam-Level: 
X-Spam-Status: No, score=-106.547 tagged_above=-999 required=5 tests=[AWL=0.052, 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 4KI7AhdV2wPd; Sat, 21 Apr 2012 07:44:14 -0700 (PDT)
Received: from exprod7og101.obsmtp.com (exprod7og101.obsmtp.com [64.18.2.155]) by ietfa.amsl.com (Postfix) with ESMTP id 7290821F858A; Sat, 21 Apr 2012 07:44:13 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob101.postini.com ([64.18.6.12]) with SMTP ID DSNKT5LHvCSUN+dvXvRYN0X9RPW2i/Xc4cKB@postini.com; Sat, 21 Apr 2012 07:44:14 PDT
Received: from P-CLDFE02-HQ.jnpr.net (172.24.192.60) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.3.213.0; Sat, 21 Apr 2012 07:44:11 -0700
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by p-cldfe02-hq.jnpr.net (172.24.192.60) with Microsoft SMTP Server (TLS) id 14.1.355.2; Sat, 21 Apr 2012 07:44:11 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Sat, 21 Apr 2012 10:44:11 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: Randy Presuhn <randy_presuhn@mindspring.com>, "ietf@ietf.org" <ietf@ietf.org>, "wgchairs@ietf.org" <wgchairs@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Date: Sat, 21 Apr 2012 10:44:09 -0400
Subject: RE: Proposed IESG Statement on the Conclusion of Experiments
Thread-Topic: Proposed IESG Statement on the Conclusion of Experiments
Thread-Index: Ac0fSfdsH3kMnl7MTXmK52DdObUSCgAeAvZA
Message-ID: <13205C286662DE4387D9AF3AC30EF456D76A81D2B5@EMBX01-WF.jnpr.net>
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk> <13205C286662DE4387D9AF3AC30EF456D76A81D0EF@EMBX01-WF.jnpr.net> <003f01cd1f4a$17e2e880$6b01a8c0@oemcomputer>
In-Reply-To: <003f01cd1f4a$17e2e880$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-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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, 21 Apr 2012 14:44:18 -0000

Hi Randy,

Both you and Brian have rightly noted that the proposed IESG statement chan=
ges neither process nor policy. It is intended to direct the community's at=
tention to a problem that is small today, but promises to grow with time.

Please review the list of experimental RFCs at the following URL:

- http://www.rfc-editor.org/categories/rfc-experimental.html

I am willing to bet that you laughed at least once while scanning this list=
. I got a chuckle from RFC 1475, the IPv7 experiment. But seriously, I iden=
tified nearly a dozen RFCs that fell into one of the following categories:

- should have been obsolete by subsequent Standards Track documents, but we=
ren't
- are more than 10 years old and have not gained traction, generally becaus=
e an alternative approach has gained traction and become widely deployed (e=
.g., RFC 1393 - Traceroute Using an IP Option).

The proposed IESG statement encourages community members to terminate their=
 own experiments when they have clearly ended. In many cases, the experimen=
ter moves on before the experiment is terminated. In that case, the cleanup=
 chore is left to others.

The proposed IESG statement *does not* seek to expedite the termination of =
any experiment. Its only goal is to identify experiments that clearly have =
terminated.

IMO, it is important that we label terminated experiments as such. Otherwis=
e, in years to come, it will become even more difficult to distinguish betw=
een active experiments that deserve community attention and old cruft that =
can safely be ignored.

                                                Ron



> -----Original Message-----
> From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of
> Randy Presuhn
> Sent: Friday, April 20, 2012 7:06 PM
> To: ietf@ietf.org; wgchairs@ietf.org
> Subject: Re: Proposed IESG Statement on the Conclusion of Experiments
>=20
> Hi -
>=20
> > From: "Ronald Bonica" <rbonica@juniper.net>
> > To: <adrian@olddog.co.uk>; <ietf@ietf.org>; <wgchairs@ietf.org>
> > Sent: Friday, April 20, 2012 1:56 PM
> > Subject: RE: Proposed IESG Statement on the Conclusion of Experiments
> ....
> > If this IESG statement is published, none of that changes.
>=20
> It might be helpful to say what *would* change upon publication of this
> statement, and why the IESG believes it is important to make that
> change, because we're obviously not unerstanding the proposal in the
> same way.
>=20
> Randy


From randy_presuhn@mindspring.com  Sat Apr 21 08:41:16 2012
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 B281C21F8607; Sat, 21 Apr 2012 08:41:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.493
X-Spam-Level: 
X-Spam-Status: No, score=-100.493 tagged_above=-999 required=5 tests=[AWL=0.247, BAYES_20=-0.74, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5iH9Hjp2U756; Sat, 21 Apr 2012 08:41:16 -0700 (PDT)
Received: from elasmtp-mealy.atl.sa.earthlink.net (elasmtp-mealy.atl.sa.earthlink.net [209.86.89.69]) by ietfa.amsl.com (Postfix) with ESMTP id 1362221F8573; Sat, 21 Apr 2012 08:41:16 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=T/FI8PnMEBymtaZ6DwhCDRFB+Kc+/a2bZbe/DOxpDUgjI1SzsZM9/inrUtiD7kN2; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [99.187.237.246] (helo=oemcomputer) by elasmtp-mealy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1SLcQz-0002tZ-PB; Sat, 21 Apr 2012 11:41:14 -0400
Message-ID: <001a01cd1fd5$5c9cfde0$6b01a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <ietf@ietf.org>, <wgchairs@ietf.org>
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk><13205C286662DE4387D9AF3AC30EF456D76A81D0EF@EMBX01-WF.jnpr.net> <003f01cd1f4a$17e2e880$6b01a8c0@oemcomputer> <13205C286662DE4387D9AF3AC30EF456D76A81D2B5@EMBX01-WF.jnpr.net>
Subject: Re: Proposed IESG Statement on the Conclusion of Experiments
Date: Sat, 21 Apr 2012 08:42:28 -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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d8882951211ce6890f88659c72e6c0044b7933cc95ee5b2e8024350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.187.237.246
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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, 21 Apr 2012 15:41:16 -0000

Hi -

> From: "Ronald Bonica" <rbonica@juniper.net>
> To: "Randy Presuhn" <randy_presuhn@mindspring.com>; <ietf@ietf.org>; <wgchairs@ietf.org>; "Brian E Carpenter"
<brian.e.carpenter@gmail.com>
> Sent: Saturday, April 21, 2012 7:44 AM
> Subject: RE: Proposed IESG Statement on the Conclusion of Experiments
...
> The proposed IESG statement encourages community members to terminate
> their own experiments when they have clearly ended. In many cases, the
> experimenter moves on before the experiment is terminated. In that case,
> the cleanup chore is left to others.

I think there are some  fundamental problems in this framing of the question.
The use of the phrase "their own" and "clearly" are the ones that concern me.
The problems with "clearly" are obvious, particularly for protocols that have
a long legacy of "just working", regardless of their theoretical shortcomings.
"Their own" assumes a level of "ownership" and, more importantly, *control*
which is rarely true, and in some cases the "owners" may actually have a
conflict of interest leading them to favor premature termination.

> The proposed IESG statement *does not* seek to expedite the termination
> of any experiment. Its only goal is to identify experiments that clearly have terminated.

I do not see any way in which this improves the criteria or process for determining
"clearly", or even the subtler problem of "terminated."  Sometimes the result of
the experiment may be "we don't want to standardize this", but also "in the
aftermath of the experiment, there are a lot of implementations of this, and
insufficient motivation for those who have deployed it to move to something else."

Randy



From joelja@bogus.com  Sat Apr 21 10:01:39 2012
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 3149421F8616; Sat, 21 Apr 2012 10:01:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 f9ISZI0hX6cm; Sat, 21 Apr 2012 10:01:38 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id BF6B121F8610; Sat, 21 Apr 2012 10:01:38 -0700 (PDT)
Received: from Joels-MacBook-Pro.local (adsl-99-191-195-38.dsl.pltn13.sbcglobal.net [99.191.195.38]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id q3LH1a5O008262 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Sat, 21 Apr 2012 17:01:37 GMT (envelope-from joelja@bogus.com)
Message-ID: <4F92E7E9.2030405@bogus.com>
Date: Sat, 21 Apr 2012 10:01:29 -0700
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Scott O Bradner <sob@sobco.com>
Subject: Re: Proposed IESG Statement on the Conclusion of Experiments
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk> <248A261F-D83D-4F97-8F5D-A9A0BCD2EC0D@sobco.com>
In-Reply-To: <248A261F-D83D-4F97-8F5D-A9A0BCD2EC0D@sobco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Sat, 21 Apr 2012 17:01:38 +0000 (UTC)
Cc: adrian@olddog.co.uk, 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: Sat, 21 Apr 2012 17:01:39 -0000

On 4/19/12 13:48 , Scott O Bradner wrote:
> encouraging a report is fine
> 
> retracting the code points seems to add more confusion than it is worth unless the
> code space is very tight
> 

unless retracting  involves marking it do not use, I too do no see value
in doing that.

From yaakov_s@rad.com  Sun Apr 22 02:51:15 2012
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 B95C121F85D2 for <wgchairs@ietfa.amsl.com>; Sun, 22 Apr 2012 02:51:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.531
X-Spam-Level: 
X-Spam-Status: No, score=-102.531 tagged_above=-999 required=5 tests=[AWL=0.067, 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 duDFa3vdjC2k for <wgchairs@ietfa.amsl.com>; Sun, 22 Apr 2012 02:51:15 -0700 (PDT)
Received: from rad.co.il (mailrelay02.rad.co.il [62.0.23.237]) by ietfa.amsl.com (Postfix) with ESMTP id 9429921F85CF for <wgchairs@ietf.org>; Sun, 22 Apr 2012 02:51:13 -0700 (PDT)
Received: from Internal Mail-Server by MailRelay02 (envelope-from yaakov?s@rad.com) with AES128-SHA encrypted SMTP; 22 Apr 2012 12:36:34 +0300
Received: from EXRAD5.ad.rad.co.il ([192.114.24.28]) by EXRAD5.ad.rad.co.il ([192.114.24.28]) with mapi id 14.01.0323.003; Sun, 22 Apr 2012 12:51:10 +0300
From: Yaakov Stein <yaakov_s@rad.com>
To: Randy Presuhn <randy_presuhn@mindspring.com>, IETF WG Chairs <wgchairs@ietf.org>
Subject: RE: Formats for WG and BOF Agendas
Thread-Topic: Formats for WG and BOF Agendas
Thread-Index: AQHNHkIdZRwCxvaQWEueKCwmFhNlepammwuQ
Date: Sun, 22 Apr 2012 09:51:09 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC904374D69@EXRAD5.ad.rad.co.il>
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com><D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com><B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com><66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com><EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com><89E33405ACD4F8D85C8BF282@PST.JCK.COM><6FD06427-9205-4E5F-8692-1B2ADF77B287@cisco.com><6711_1334782966_q3IL2irQ020972_F275560B749B4A0C6D3550F2@JcK-HP8200.jck.com><1334818686.21993.40.camel@destiny.pc.cs.cmu.edu> <07F7D7DED63154409F13298786A2ADC904373FC8@EXRAD5.ad.rad.co.il> <001c01cd1e42$1ec1bae0$6b01a8c0@oemcomputer>
In-Reply-To: <001c01cd1e42$1ec1bae0$6b01a8c0@oemcomputer>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.17.140.53]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Commtouch-Refid: str=0001.0A020205.4F93D48F.005D,ss=1,fgs=0
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Apr 2012 09:51:15 -0000

PiBUbyBtZSBpdCBzZWVtcyB0aGF0IGlmIHRoZSByZXNvbHV0aW9uIGNhbm5vdCBiZSBkZXNjcmli
ZWQgaW4gcGxhaW4gdGV4dCwNCj4gaXQncyBub3QgYWRlcXVhdGVseSB1bmRlcnN0b29kLCBhbmQg
c2hvdWxkIGJlIHJlY29yZGVkIGFzIGFuIGFjdGlvbiBpdGVtDQo+IGZvciB0aGUgcGVyc29uIG9y
IGRlc2lnbiB0ZWFtIGNsYWltaW5nIHRvIHVuZGVyc3RhbmQgdGhlIHJlc29sdXRpb24gdG8gcG9z
dA0KPiB0aGF0IHVuZGVyc3RhbmRpbmcgdG8gdGhlIFdHIG1haWxpbmcgbGlzdC4NCg0KLi4uIGFu
ZCBhc3N1bWluZyB0aGF0IHNvbWVvbmUgY2FuIHBvc3QgdG8gdGhlIGxpc3QgaW4gYW55IGZvcm1h
dCwgdGhhdCBzb2x2ZXMgdGhlIHByb2JsZW0hDQpCdXQgYXQgdGhlIHByaWNlIG9mIG1ha2luZyB0
aGUgbWludXRlcyBtZWFuaW5nbGVzcyB3aXRob3V0IHJlYWRpbmcgYWxsIG9mIHRoZXNlIGVtYWls
cw0KaW4gZm9ybWF0cyB0aGF0IHdpbGwgbm90IHBlcnNpc3QuDQoNCkkgYWxzbyBkb24ndCBhZ3Jl
ZSB3aXRoIHlvdXIgc3RhdGVtZW50IHRoYXQgYSBzdGF0ZW1lbnQgdGhhdCBjYW4ndCBiZSBjYXB0
dXJlZA0KaW4gcGxhaW4gdGV4dCBpcyBub3QgYWRlcXVhdGVseSB1bmRlcnN0b29kLiANCkZyb20g
YSB0aGVvcmV0aWNhbCBzdGFuZHBvaW50LCBub3RoaW5nIGluIG5hdHVyYWwgaHVtYW4gbGFuZ3Vh
Z2UgY2FuIGJlIGNvbXBsZXRlbHkgdW5kZXJzdG9vZC4gDQpNb3JlIGltcG9ydGFudGx5IGZyb20g
YSBwcmFjdGljYWwgc3RhbmRwb2ludCBJIGhhdmUgc2VlbiBtaW51dGVzIHRoYXQgc2F5IA0KIm9w
dGlvbiAzIHdhcyBjb25zaWRlcmVkIHRoZSBiZXN0IGJ5IHRoZSBncm91cCINCm9ubHkgdG8gZGlz
Y292ZXIgYSB5ZWFyIGxhdGVyIHRoYXQgc29tZSB0aG91Z2h0IHRoaXMgbWVhbnQgb3B0aW9uIDNB
IGFuZCBvdGhlcnMgM0IuIA0KDQpZKEopUw0KDQo=

From dromasca@avaya.com  Sun Apr 22 04:08:53 2012
Return-Path: <dromasca@avaya.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31FC421F8639; Sun, 22 Apr 2012 04:08:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.399
X-Spam-Level: 
X-Spam-Status: No, score=-103.399 tagged_above=-999 required=5 tests=[AWL=0.200, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 64jnMOOUFsHK; Sun, 22 Apr 2012 04:08:50 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id CDE6321F85F2; Sun, 22 Apr 2012 04:08:49 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EANblk0+HCzI1/2dsb2JhbABEsUCBB4IJAQEBAQMSHgo/DAQCAQgNBAQBAQsGDAsBBgFFCQgBAQQBEggMDodtnUGcHpBQYwScEIoogms
X-IronPort-AV: E=Sophos;i="4.75,462,1330923600"; d="scan'208";a="343661616"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 22 Apr 2012 07:08:29 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.13]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 22 Apr 2012 06:52:06 -0400
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Proposed IESG Statement on the Conclusion of Experiments
Date: Sun, 22 Apr 2012 13:08:46 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0407810532@307622ANEX5.global.avaya.com>
In-Reply-To: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Proposed IESG Statement on the Conclusion of Experiments
Thread-Index: Ac0ea1trQ6bEEENVRsKUUaoiCTZbygCDCGdQ
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <adrian@olddog.co.uk>, <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: Sun, 22 Apr 2012 11:08:53 -0000

Hi,

Part of the problems with Experimental RFCs which were prompted up also
in this discussion derive from the fact that many of the RFCs labeled as
Experimental do not describe in clear terms the goals of the experiment
that is being proposed. It is hard for somebody to describe the results
of the experiment (even very briefly) if the goals were not specified.
If the IESG decides to go ahead with this statement I suggest that a
strong recommendation is added for documents that aim Experimental as
their Proposed Status to include clear and explicit text about the goals
of the experiment and wherever relevant conditions, restrictions, and
timeframe.=20

Regards,

Dan
=20



> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
Of
> Adrian Farrel
> Sent: Thursday, April 19, 2012 11:31 PM
> To: ietf@ietf.org; wgchairs@ietf.org
> Cc: iesg@ietf.org
> Subject: Proposed IESG Statement on the Conclusion of Experiments
>=20
> All,
>=20
> The IESG has been discussing how to tidy up after Experimental RFCs.
>=20
> We have developed the following draft IESG statement. This does not
> represent a change in process, and continues to value Experimental
RFCs
> as an important part of the IETF process. It does, however, seek to
> encourage documentation of the conclusion of experiments.
>=20
> We are aware that there may be other discussion points around
> Experimental RFCs, and we would like to discuss these, but we also
> believe that there is merit in making small, incremental improvements.
>=20
> The IESG would welcome your thoughts on this draft before they approve
> the final text on April 26th.
>=20
> Thanks,
> Adrian
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> IESG Statement on Conclusion of IETF Experiments
>=20
>=20
> Experiments are an established and valuable part of the IETF process.
> A number of core Internet protocols were first published as
> Experimental
> RFCs while the community gathered experience and carefully
investigated
> the consequences of deploying new mechanisms within the Internet.
>=20
> In the case where an experiment leads on to the development of a
> Standards Track RFC documenting a protocol, the new RFC obsoletes the
> old Experimental RFC and there is a clear conclusion to the
experiment.
>=20
> However, many experiments do not lead to the development of Standards
> Track RFCs. Instead, the work may be abandoned through lack of
interest
> or because important lessons have been learned.
>=20
> It is currently hard to distinguish between an experiment that is
still
> being investigated, and an old experiment that has ceased to be of
> interest to the community. In both cases an Experimental RFC exists in
> the repository and newcomers might easily be misled into thinking that
> it would be helpful to conduct more research into an abandoned
> experiment.
>=20
> In view of this, the original proponents of experiments (that is,
> authors of Experimental RFCs, and Working Groups that requested the
> publication of Experimental RFCs) are strongly encouraged to document
> the termination of experiments that do not result in subsequent
> Standards Track work by publishing an Informational RFC that:
>=20
> - very briefly describes the results of the experiment
>=20
> - obsoletes the Experimental RFC
>=20
> - if appropriate, deprecate any IANA code points allocated for the
>   experiment
>=20
> - may request that the Experimental RFC is moved to Historic status.
>=20
> If there is no energy in the community for the producing such an
> Informational RFC, if the authors have moved on to other things, or if
> the Working Group has been closed down, Area Directors should author
or
> seek volunteers to author such an Informational RFC.


From cabo@tzi.org  Sun Apr 22 05:17:43 2012
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 5722021F84B5; Sun, 22 Apr 2012 05:17:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.163
X-Spam-Level: 
X-Spam-Status: No, score=-105.163 tagged_above=-999 required=5 tests=[AWL=-1.214, BAYES_00=-2.599, HELO_EQ_DE=0.35, MANGLED_MEN=2.3, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g69It47E9uWy; Sun, 22 Apr 2012 05:17:42 -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 DA8E421F84B3; Sun, 22 Apr 2012 05:17:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id q3MCHXrR027761; Sun, 22 Apr 2012 14:17:34 +0200 (CEST)
Received: from [192.168.217.105] (p5489B676.dip.t-dialin.net [84.137.182.118]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 7D1183C2; Sun, 22 Apr 2012 14:17:33 +0200 (CEST)
Subject: Re: Proposed IESG Statement on the Conclusion of Experiments
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=utf-8
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A0407810532@307622ANEX5.global.avaya.com>
Date: Sun, 22 Apr 2012 14:17:32 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <A3641334-1936-4F85-B41F-57EE0E95128E@tzi.org>
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk> <EDC652A26FB23C4EB6384A4584434A0407810532@307622ANEX5.global.avaya.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
X-Mailer: Apple Mail (2.1257)
Cc: adrian@olddog.co.uk, 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: Sun, 22 Apr 2012 12:17:43 -0000

On Apr 22, 2012, at 13:08, Romascanu, Dan (Dan) wrote:

> Part of the problems with Experimental RFCs which were prompted up =
also
> in this discussion derive from the fact that many of the RFCs labeled =
as
> Experimental do not describe in clear terms the goals of the =
experiment
> that is being proposed.=20

I never knew that was an objective for an experimental RFC.

(But I have only been contributing to the IETF for 19 years.)

The way that I understood *experimental* RFCs all this time was that =
they provide interoperability specifications that are *experimental*, =
i.e., we need further *experience* to validate them (e.g., we don't =
fully understand yet whether they work as well as we think).

The design of formal *experiments* around these specifications never was =
a subject, and I would be surprised to do these anywhere in the IETF =
(maybe in the IRTF, but even that is a long shot for most of these).  =
More importantly, the *experience* needed for validation may not come =
out of *experiments* at all.

Please read these two sentences from RFC 2026 again and tell me what I =
have missed these 19 years.

   The "Experimental" designation typically denotes a specification that
   is part of some research or development effort.  Such a specification
   is published for the general information of the Internet technical
   community and as an archival record of the work, subject only to
   editorial considerations and to verification that there has been
   adequate coordination with the standards process (see below). =20

I wouldn't mind if an experimental RFC were more vocal about what kind =
of experience is missing, motivating *why* it is still experimental.  As =
was already said in this thread, "experimental" status is often =
threatened as a cop-out out of a standardization process that some party =
does not want to complete.  Curbing *that* would be worth some effort.

Gr=C3=BC=C3=9Fe, Carsten

PS.: Since I'm not a native speaker, I just looked up again what =
experimental means.  Yes, experiments may be involved (in submeaning 2), =
but that's not the main semantics of this word.  Deriving the *need* for =
an "experiment" from this word strikes me as confused.

experimental |=C9=AAk=CB=88=CB=8Csp=C9=9Br=C9=99=CB=88=CB=8Cm=C9=9Bn(t)l|
adjective
(of a new invention or product) based on untested ideas or techniques =
and not yet established or finalized: an experimental drug.
=E2=80=A2 (of a work of art or an artistic technique) involving a =
radically new and innovative style: experimental music.
=E2=80=A2 of or relating to scientific experiments: experimental =
results.
=E2=80=A2 archaic based on experience as opposed to authority or =
conjecture: an experimental knowledge of God.


From fred@cisco.com  Sun Apr 22 06:45:03 2012
Return-Path: <fred@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B0C421F84E7; Sun, 22 Apr 2012 06:45:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.264
X-Spam-Level: 
X-Spam-Status: No, score=-110.264 tagged_above=-999 required=5 tests=[AWL=0.335, 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 IuRdQXt5wq0Q; Sun, 22 Apr 2012 06:45:02 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 1433E21F84CE; Sun, 22 Apr 2012 06:45:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=463; q=dns/txt; s=iport; t=1335102302; x=1336311902; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=fgh/YFjHqAthxQ1zOE1I9M4vd8A7kaITz/SFeZjBhiI=; b=CQn+a37QbW2AimT7uk3WUyHDgMZJNBn1tSaaxIdFeSwmWnuPp/5bniTT U5t/oWpi9PO/fbkYdJwNO820YovIsmaQwrnFnLDJjs0O6OluYhBblveKL rxiwuWawb1BpkybyxqNY6TOQSS6KibIJynC3FE8X4e/gwK7fJJeSULJ0Q A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAE0KlE+Q/khL/2dsb2JhbABEsUCBB4IJAQEBAwESASc/BQsLDjhXBjWHaAWaVZ8ZkFBjBJV6hXSIYYFpgms
X-IronPort-AV: E=Sophos;i="4.75,462,1330905600"; d="scan'208";a="135873282"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 22 Apr 2012 13:45:00 +0000
Received: from Freds-Computer.local (ams3-vpn-dhcp4278.cisco.com [10.61.80.181]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id q3MDj0MT013954; Sun, 22 Apr 2012 13:45:00 GMT
Received: from [127.0.0.1] by Freds-Computer.local (PGP Universal service); Sun, 22 Apr 2012 15:45:00 +0200
X-PGP-Universal: processed; by Freds-Computer.local on Sun, 22 Apr 2012 15:45:00 +0200
Subject: Re: Proposed IESG Statement on the Conclusion of Experiments
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <E0BDBD64-D3D4-4248-9EB2-BDD1F1CE39BF@virtualized.org>
Date: Sun, 22 Apr 2012 15:44:26 +0200
Message-Id: <DF8FBB49-E4FC-492F-BF2C-81629F3F1C46@cisco.com>
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk> <248A261F-D83D-4F97-8F5D-A9A0BCD2EC0D@sobco.com> <f8e77298-bbd5-4ad8-80df-a3c367f67d95.maildroid@localhost> <E0BDBD64-D3D4-4248-9EB2-BDD1F1CE39BF@virtualized.org>
To: David Conrad <drc@virtualized.org>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: wgchairs@ietf.org, IETF discussion list <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Apr 2012 13:45:03 -0000

On Apr 19, 2012, at 11:17 PM, David Conrad wrote:

> I'd argue that you want to deallocate as soon as an experiment is =
over.

But the point is that experiments don't necessarily become "over". Some =
of them in effect become standards, and it would probably be good if =
there were an easy way to reclassify the experimental RFC as a Proposed =
Standard. Saying that "nobody" is using a given code point or RFC of any =
category is very difficult.=

From jgs@bgp.nu  Sun Apr 22 06:54:30 2012
Return-Path: <jgs@bgp.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 1ADFB21F85A4; Sun, 22 Apr 2012 06:54:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.043
X-Spam-Level: 
X-Spam-Status: No, score=-102.043 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_IS_SMALL6=0.556, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id monwCuFCLvih; Sun, 22 Apr 2012 06:54:29 -0700 (PDT)
Received: from bgp.nu (bgp.nu [147.28.0.53]) by ietfa.amsl.com (Postfix) with ESMTP id A45A921F859F; Sun, 22 Apr 2012 06:54:29 -0700 (PDT)
Received: from [192.168.42.13] (75-151-14-9-Michigan.hfc.comcastbusiness.net [75.151.14.9]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by bgp.nu (Postfix) with ESMTP id D5B8566D357; Sun, 22 Apr 2012 09:54:28 -0400 (EDT)
Subject: Re: Proposed IESG Statement on the Conclusion of Experiments
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: "John G. Scudder" <jgs@bgp.nu>
In-Reply-To: <DF8FBB49-E4FC-492F-BF2C-81629F3F1C46@cisco.com>
Date: Sun, 22 Apr 2012 07:54:28 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <6D8983DD-54EB-446C-9512-7145C52BF236@bgp.nu>
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk> <248A261F-D83D-4F97-8F5D-A9A0BCD2EC0D@sobco.com> <f8e77298-bbd5-4ad8-80df-a3c367f67d95.maildroid@localhost> <E0BDBD64-D3D4-4248-9EB2-BDD1F1CE39BF@virtualized.org> <DF8FBB49-E4FC-492F-BF2C-81629F3F1C46@cisco.com>
To: Fred Baker <fred@cisco.com>
X-Mailer: Apple Mail (2.1257)
Cc: wgchairs@ietf.org, David Conrad <drc@virtualized.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Apr 2012 13:54:30 -0000

On Apr 22, 2012, at 7:44 AM, Fred Baker wrote:

> Saying that "nobody" is using a given code point or RFC of any =
category is very difficult.

True enough, although since you didn't give context I'm not sure who =
you're making that point to, or why. The proposal Adrian originally sent =
talks about optionally deprecating code points, which while generally =
related to your comment, isn't the same.

--John=

From keith.drage@alcatel-lucent.com  Sun Apr 22 16:12:44 2012
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 20C0421F85B6; Sun, 22 Apr 2012 16:12:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.063
X-Spam-Level: 
X-Spam-Status: No, score=-110.063 tagged_above=-999 required=5 tests=[AWL=0.186, BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 CNPbXe3eC+oM; Sun, 22 Apr 2012 16:12:43 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by ietfa.amsl.com (Postfix) with ESMTP id 65AD621F853E; Sun, 22 Apr 2012 16:12:42 -0700 (PDT)
Received: from FRMRSSXCHHUB01.dc-m.alcatel-lucent.com (FRMRSSXCHHUB01.dc-m.alcatel-lucent.com [135.120.45.61]) by smail5.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q3MNCeL2001176 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 23 Apr 2012 01:12:40 +0200
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.44]) by FRMRSSXCHHUB01.dc-m.alcatel-lucent.com ([135.120.45.61]) with mapi; Mon, 23 Apr 2012 01:12:40 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Melinda Shore <melinda.shore@gmail.com>
Date: Mon, 23 Apr 2012 01:12:38 +0200
Subject: RE: Proposed IESG Statement on the Conclusion of Experiments
Thread-Topic: Proposed IESG Statement on the Conclusion of Experiments
Thread-Index: Ac0fVv2cMVvrlQYMTgmY88/z+MpgKABhiKgQ
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE22614022A@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk> <9452079D1A51524AA5749AD23E0039280FBFC3@exch-mbx901.corp.cloudmark.com> <4F917CE1.5090403@cisco.com> <4F917F84.5040702@gmail.com> <EDC0A1AE77C57744B664A310A0B23AE2260C3063@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <4F92014A.4040707@gmail.com>
In-Reply-To: <4F92014A.4040707@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.13
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Apr 2012 23:12:44 -0000

I wasn't discussing the point about whether there should be a process chang=
e or not. Rather, I don't think any process, existing or new, of changing t=
he document type can be done in less than 12 months, and I don't think that=
 such change in status will match any market needs for extra identification=
 of active RFCs worthy of implementation.

Therefore essentially in many respects this discussion will achieve nothing=
.

Regards

Keith

> -----Original Message-----
> From: Melinda Shore [mailto:melinda.shore@gmail.com]
> Sent: 21 April 2012 01:38
> To: DRAGE, Keith (Keith)
> Cc: Brian E Carpenter; wgchairs@ietf.org; ietf@ietf.org
> Subject: Re: Proposed IESG Statement on the Conclusion of Experiments
>=20
> On 4/20/12 4:28 PM, DRAGE, Keith (Keith) wrote:
> > Changing something from experimental to proposed standard in a
> > process that will probably take 12 months will be unlikely change the
> > number of people implementing and deploying an RFC.
>=20
> I'm going to take the liberty of mentioning that I spoke with Ron
> earlier today about this.  Basically what he's asking is that there
> be no process changes, and, I think, no policy changes, just
> that IESG members should be mindful about how to phase experimental
> stuff out when it's flopped.
>=20
> Personally, I think he's correct about both cruft and mindfulness
> and suspect that probably nearly everybody agrees with what he's
> saying, anyway, but unfortunately it was presented in a form that
> made it look like More Process.
>=20
> Melinda

From peter@denic.de  Mon Apr 23 00:26:37 2012
Return-Path: <peter@denic.de>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15D0B21F857D for <wgchairs@ietfa.amsl.com>; Mon, 23 Apr 2012 00:26:37 -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 Eco7jKxtPZp1 for <wgchairs@ietfa.amsl.com>; Mon, 23 Apr 2012 00:26:36 -0700 (PDT)
Received: from office.denic.de (office.denic.de [IPv6:2a02:568:122:16:1::4]) by ietfa.amsl.com (Postfix) with ESMTP id 7AE1D21F856C for <wgchairs@ietf.org>; Mon, 23 Apr 2012 00:26:36 -0700 (PDT)
Received: from x27.adm.denic.de ([10.122.64.128]) by office.denic.de with esmtp  id 1SMDfP-0007pr-3p; Mon, 23 Apr 2012 09:26:35 +0200
Received: from localhost by x27.adm.denic.de with local  id 1SMDfO-00069d-Vw; Mon, 23 Apr 2012 09:26:35 +0200
Date: Mon, 23 Apr 2012 09:26:34 +0200
From: Peter Koch <pk@ISOC.DE>
To: IETF WG Chairs <wgchairs@ietf.org>
Subject: Re: Formats for WG and BOF Agendas
Message-ID: <20120423072634.GO8966@x27.adm.denic.de>
Mail-Followup-To: IETF WG Chairs <wgchairs@ietf.org>
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com> <D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com> <B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com> <66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com> <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com> <0e3201cd1e1e$66184090$3248c1b0$@olddog.co.uk> <14875_1334839446_q3JCi4gt024517_01D86B13EFF01AE45550B050@JcK-HP8200.jck.com> <1334938056.21993.94.camel@destiny.pc.cs.cmu.edu> <C153B9DD-4A3A-4FCE-B29A-C4857E7CFC78@vigilsec.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <C153B9DD-4A3A-4FCE-B29A-C4857E7CFC78@vigilsec.com>
User-Agent: Mutt/1.4.2.3i
Sender: Peter Koch <peter@denic.de>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Apr 2012 07:26:37 -0000

On Fri, Apr 20, 2012 at 12:55:20PM -0400, Russ Housley wrote:

> (3) Minutes should be limited to text, html, and pdf.

I'd support this without the PDF option.

On a related issue, we increasingly see the agendas and minutes only
posted to the materials site, which means there is no copy available
in the mail archives. Maybe that ought to change back.

-Peter

From dromasca@avaya.com  Mon Apr 23 03:29:17 2012
Return-Path: <dromasca@avaya.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADAED21F86A2; Mon, 23 Apr 2012 03:29:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.275
X-Spam-Level: 
X-Spam-Status: No, score=-102.275 tagged_above=-999 required=5 tests=[AWL=-0.976, BAYES_00=-2.599, MANGLED_MEN=2.3, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CHou+kZUEhiP; Mon, 23 Apr 2012 03:29:17 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 4FD3B21F8652; Mon, 23 Apr 2012 03:29:15 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhgFAJIulU+HCzI1/2dsb2JhbABEhRNVqlqBAoEHggkBAQEBAgEMBhENBEUFBwQCAQYCDQEDBAEBAQICBgYMCwECAgIBAUQJCAEBBBMIDA6HaAWdEYoekkqBL4lDhSk1YwScEIoogmuBUgIX
X-IronPort-AV: E=Sophos;i="4.75,466,1330923600"; d="scan'208";a="303122533"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 23 Apr 2012 06:28:37 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.13]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 23 Apr 2012 06:11:54 -0400
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Subject: RE: Proposed IESG Statement on the Conclusion of Experiments
Date: Mon, 23 Apr 2012 12:28:35 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0407810736@307622ANEX5.global.avaya.com>
In-Reply-To: <A3641334-1936-4F85-B41F-57EE0E95128E@tzi.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Proposed IESG Statement on the Conclusion of Experiments
Thread-Index: Ac0ggeu89nV48lXCRVOKfb3T+gXbZgAt1UjQ
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk> <EDC652A26FB23C4EB6384A4584434A0407810532@307622ANEX5.global.avaya.com> <A3641334-1936-4F85-B41F-57EE0E95128E@tzi.org>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Carsten Bormann" <cabo@tzi.org>
Cc: adrian@olddog.co.uk, 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, 23 Apr 2012 10:29:17 -0000

SGkgQ2Fyc3RlbiwNCg0KV2UgYXJlIGRpc2N1c3NpbmcgYSBwcm9wb3NhbCBmb3IgYW4gSUVTRyBz
dGF0ZW1lbnQgdGhhdCBpbmNsdWRlcyB0aGUgZm9sbG93aW5nOiANCg0KPiBJbiB2aWV3IG9mIHRo
aXMsIHRoZSBvcmlnaW5hbCBwcm9wb25lbnRzIG9mIGV4cGVyaW1lbnRzICh0aGF0IGlzLCBhdXRo
b3JzIG9mIEV4cGVyaW1lbnRhbCBSRkNzLCBhbmQgV29ya2luZyBHcm91cHMgdGhhdCByZXF1ZXN0
ZWQgdGhlIHB1YmxpY2F0aW9uIG9mIEV4cGVyaW1lbnRhbCBSRkNzKSBhcmUgc3Ryb25nbHkgZW5j
b3VyYWdlZCB0byBkb2N1bWVudCB0aGUgdGVybWluYXRpb24gb2YgZXhwZXJpbWVudHMgdGhhdCBk
byBub3QgcmVzdWx0IGluIHN1YnNlcXVlbnQgU3RhbmRhcmRzIFRyYWNrIHdvcmsgYnkgcHVibGlz
aGluZyBhbiBJbmZvcm1hdGlvbmFsIFJGQyB0aGF0Og0KDQotIHZlcnkgYnJpZWZseSBkZXNjcmli
ZXMgdGhlIHJlc3VsdHMgb2YgdGhlIGV4cGVyaW1lbnQNCg0KU28gdGhlICdleHBlcmltZW50cycg
c2VlbSB0byBiZSBjb25zaWRlcmVkIGJ5IHRoZSBJRVNHIGFzIHJlbGF0ZWQgdG8gRXhwZXJpbWVu
dGFsIFJGQ3MuIA0KDQpNeSBwb2ludCBpcyB0aGF0IGlmIHdlIGRpc2N1c3MgYWJvdXQgJ3Jlc3Vs
dHMgb2YgdGhlIGV4cGVyaW1lbnQnIGFuZCB0aGUgSUVTRyBwbGFucyB0byBzdHJvbmdseSBlbmNv
dXJhZ2UgYXV0aG9ycyBvZiBFeHBlcmltZW50YWwgUkZDcyB0byBicmllZmx5IGRlc2NyaWJlIHRo
ZSByZXN1bHRzLCB0aGV5IHNob3VsZCBhbHNvIHJlY29tbWVuZCB0byBpbmNsdWRlIGluIHRoZSBS
RkNzIGluIGFuIGV4cGxpY2l0IG1hbm5lciB0aGUgZ29hbHMgd2hpY2ggdGhlIHJlc3VsdHMgb2Yg
dGhlIGV4cGVyaW1lbnRzIGFyZSB0byBiZSBtZWFzdXJlZCBhZ2FpbnN0LiANCg0KQWxzbywgaWYg
eW91IGFyZSBxdW90aW5nIFJGQyAyMDI2IHlvdSBtdXN0IGhhdmUgYWxzbyBlbmNvdW50ZXJlZCB0
aGUgZm9sbG93aW5nIHBhcmFncmFwaCBpbiBzZWN0aW9uIDMuMzogDQoNCj4gKGQpICBMaW1pdGVk
IFVzZTogIFRoZSBUUyBpcyBjb25zaWRlcmVkIHRvIGJlIGFwcHJvcHJpYXRlIGZvciB1c2UNCiAg
ICAgIG9ubHkgaW4gbGltaXRlZCBvciB1bmlxdWUgY2lyY3Vtc3RhbmNlcy4gIEZvciBleGFtcGxl
LCB0aGUgdXNhZ2UNCiAgICAgIG9mIGEgcHJvdG9jb2wgd2l0aCB0aGUgIkV4cGVyaW1lbnRhbCIg
ZGVzaWduYXRpb24gc2hvdWxkIGdlbmVyYWxseQ0KICAgICAgYmUgbGltaXRlZCB0byB0aG9zZSBh
Y3RpdmVseSBpbnZvbHZlZCB3aXRoIHRoZSBleHBlcmltZW50Lg0KDQpTbyB0aGUgdGVybSAnZXhw
ZXJpbWVudCcgYWxyZWFkeSBhcHBlYXJzIGluIDIwMjYuIA0KDQpSZWdhcmRzLA0KDQpEYW4NCiAg
IA0KDQoNCg0KDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogQ2Fyc3Rl
biBCb3JtYW5uIFttYWlsdG86Y2Fib0B0emkub3JnXQ0KPiBTZW50OiBTdW5kYXksIEFwcmlsIDIy
LCAyMDEyIDM6MTggUE0NCj4gVG86IFJvbWFzY2FudSwgRGFuIChEYW4pDQo+IENjOiBhZHJpYW5A
b2xkZG9nLmNvLnVrOyBpZXRmQGlldGYub3JnOyB3Z2NoYWlyc0BpZXRmLm9yZw0KPiBTdWJqZWN0
OiBSZTogUHJvcG9zZWQgSUVTRyBTdGF0ZW1lbnQgb24gdGhlIENvbmNsdXNpb24gb2YgRXhwZXJp
bWVudHMNCj4gDQo+IE9uIEFwciAyMiwgMjAxMiwgYXQgMTM6MDgsIFJvbWFzY2FudSwgRGFuIChE
YW4pIHdyb3RlOg0KPiANCj4gPiBQYXJ0IG9mIHRoZSBwcm9ibGVtcyB3aXRoIEV4cGVyaW1lbnRh
bCBSRkNzIHdoaWNoIHdlcmUgcHJvbXB0ZWQgdXANCj4gYWxzbw0KPiA+IGluIHRoaXMgZGlzY3Vz
c2lvbiBkZXJpdmUgZnJvbSB0aGUgZmFjdCB0aGF0IG1hbnkgb2YgdGhlIFJGQ3MgbGFiZWxlZA0K
PiBhcw0KPiA+IEV4cGVyaW1lbnRhbCBkbyBub3QgZGVzY3JpYmUgaW4gY2xlYXIgdGVybXMgdGhl
IGdvYWxzIG9mIHRoZQ0KPiBleHBlcmltZW50DQo+ID4gdGhhdCBpcyBiZWluZyBwcm9wb3NlZC4N
Cj4gDQo+IEkgbmV2ZXIga25ldyB0aGF0IHdhcyBhbiBvYmplY3RpdmUgZm9yIGFuIGV4cGVyaW1l
bnRhbCBSRkMuDQo+IA0KPiAoQnV0IEkgaGF2ZSBvbmx5IGJlZW4gY29udHJpYnV0aW5nIHRvIHRo
ZSBJRVRGIGZvciAxOSB5ZWFycy4pDQo+IA0KPiBUaGUgd2F5IHRoYXQgSSB1bmRlcnN0b29kICpl
eHBlcmltZW50YWwqIFJGQ3MgYWxsIHRoaXMgdGltZSB3YXMgdGhhdA0KPiB0aGV5IHByb3ZpZGUg
aW50ZXJvcGVyYWJpbGl0eSBzcGVjaWZpY2F0aW9ucyB0aGF0IGFyZSAqZXhwZXJpbWVudGFsKiwN
Cj4gaS5lLiwgd2UgbmVlZCBmdXJ0aGVyICpleHBlcmllbmNlKiB0byB2YWxpZGF0ZSB0aGVtIChl
LmcuLCB3ZSBkb24ndA0KPiBmdWxseSB1bmRlcnN0YW5kIHlldCB3aGV0aGVyIHRoZXkgd29yayBh
cyB3ZWxsIGFzIHdlIHRoaW5rKS4NCj4gDQo+IFRoZSBkZXNpZ24gb2YgZm9ybWFsICpleHBlcmlt
ZW50cyogYXJvdW5kIHRoZXNlIHNwZWNpZmljYXRpb25zIG5ldmVyDQo+IHdhcyBhIHN1YmplY3Qs
IGFuZCBJIHdvdWxkIGJlIHN1cnByaXNlZCB0byBkbyB0aGVzZSBhbnl3aGVyZSBpbiB0aGUNCj4g
SUVURiAobWF5YmUgaW4gdGhlIElSVEYsIGJ1dCBldmVuIHRoYXQgaXMgYSBsb25nIHNob3QgZm9y
IG1vc3Qgb2YNCj4gdGhlc2UpLiAgTW9yZSBpbXBvcnRhbnRseSwgdGhlICpleHBlcmllbmNlKiBu
ZWVkZWQgZm9yIHZhbGlkYXRpb24gbWF5DQo+IG5vdCBjb21lIG91dCBvZiAqZXhwZXJpbWVudHMq
IGF0IGFsbC4NCj4gDQo+IFBsZWFzZSByZWFkIHRoZXNlIHR3byBzZW50ZW5jZXMgZnJvbSBSRkMg
MjAyNiBhZ2FpbiBhbmQgdGVsbCBtZSB3aGF0IEkNCj4gaGF2ZSBtaXNzZWQgdGhlc2UgMTkgeWVh
cnMuDQo+IA0KPiAgICBUaGUgIkV4cGVyaW1lbnRhbCIgZGVzaWduYXRpb24gdHlwaWNhbGx5IGRl
bm90ZXMgYSBzcGVjaWZpY2F0aW9uDQo+IHRoYXQNCj4gICAgaXMgcGFydCBvZiBzb21lIHJlc2Vh
cmNoIG9yIGRldmVsb3BtZW50IGVmZm9ydC4gIFN1Y2ggYQ0KPiBzcGVjaWZpY2F0aW9uDQo+ICAg
IGlzIHB1Ymxpc2hlZCBmb3IgdGhlIGdlbmVyYWwgaW5mb3JtYXRpb24gb2YgdGhlIEludGVybmV0
IHRlY2huaWNhbA0KPiAgICBjb21tdW5pdHkgYW5kIGFzIGFuIGFyY2hpdmFsIHJlY29yZCBvZiB0
aGUgd29yaywgc3ViamVjdCBvbmx5IHRvDQo+ICAgIGVkaXRvcmlhbCBjb25zaWRlcmF0aW9ucyBh
bmQgdG8gdmVyaWZpY2F0aW9uIHRoYXQgdGhlcmUgaGFzIGJlZW4NCj4gICAgYWRlcXVhdGUgY29v
cmRpbmF0aW9uIHdpdGggdGhlIHN0YW5kYXJkcyBwcm9jZXNzIChzZWUgYmVsb3cpLg0KPiANCj4g
SSB3b3VsZG4ndCBtaW5kIGlmIGFuIGV4cGVyaW1lbnRhbCBSRkMgd2VyZSBtb3JlIHZvY2FsIGFi
b3V0IHdoYXQga2luZA0KPiBvZiBleHBlcmllbmNlIGlzIG1pc3NpbmcsIG1vdGl2YXRpbmcgKndo
eSogaXQgaXMgc3RpbGwgZXhwZXJpbWVudGFsLg0KPiBBcyB3YXMgYWxyZWFkeSBzYWlkIGluIHRo
aXMgdGhyZWFkLCAiZXhwZXJpbWVudGFsIiBzdGF0dXMgaXMgb2Z0ZW4NCj4gdGhyZWF0ZW5lZCBh
cyBhIGNvcC1vdXQgb3V0IG9mIGEgc3RhbmRhcmRpemF0aW9uIHByb2Nlc3MgdGhhdCBzb21lDQo+
IHBhcnR5IGRvZXMgbm90IHdhbnQgdG8gY29tcGxldGUuICBDdXJiaW5nICp0aGF0KiB3b3VsZCBi
ZSB3b3J0aCBzb21lDQo+IGVmZm9ydC4NCj4gDQo+IEdyw7zDn2UsIENhcnN0ZW4NCj4gDQo+IFBT
LjogU2luY2UgSSdtIG5vdCBhIG5hdGl2ZSBzcGVha2VyLCBJIGp1c3QgbG9va2VkIHVwIGFnYWlu
IHdoYXQNCj4gZXhwZXJpbWVudGFsIG1lYW5zLiAgWWVzLCBleHBlcmltZW50cyBtYXkgYmUgaW52
b2x2ZWQgKGluIHN1Ym1lYW5pbmcNCj4gMiksIGJ1dCB0aGF0J3Mgbm90IHRoZSBtYWluIHNlbWFu
dGljcyBvZiB0aGlzIHdvcmQuICBEZXJpdmluZyB0aGUNCj4gKm5lZWQqIGZvciBhbiAiZXhwZXJp
bWVudCIgZnJvbSB0aGlzIHdvcmQgc3RyaWtlcyBtZSBhcyBjb25mdXNlZC4NCj4gDQo+IGV4cGVy
aW1lbnRhbCB8yapry4jLjHNwyZtyyZnLiMuMbcmbbih0KWx8DQo+IGFkamVjdGl2ZQ0KPiAob2Yg
YSBuZXcgaW52ZW50aW9uIG9yIHByb2R1Y3QpIGJhc2VkIG9uIHVudGVzdGVkIGlkZWFzIG9yIHRl
Y2huaXF1ZXMNCj4gYW5kIG5vdCB5ZXQgZXN0YWJsaXNoZWQgb3IgZmluYWxpemVkOiBhbiBleHBl
cmltZW50YWwgZHJ1Zy4NCj4g4oCiIChvZiBhIHdvcmsgb2YgYXJ0IG9yIGFuIGFydGlzdGljIHRl
Y2huaXF1ZSkgaW52b2x2aW5nIGEgcmFkaWNhbGx5IG5ldw0KPiBhbmQgaW5ub3ZhdGl2ZSBzdHls
ZTogZXhwZXJpbWVudGFsIG11c2ljLg0KPiDigKIgb2Ygb3IgcmVsYXRpbmcgdG8gc2NpZW50aWZp
YyBleHBlcmltZW50czogZXhwZXJpbWVudGFsIHJlc3VsdHMuDQo+IOKAoiBhcmNoYWljIGJhc2Vk
IG9uIGV4cGVyaWVuY2UgYXMgb3Bwb3NlZCB0byBhdXRob3JpdHkgb3IgY29uamVjdHVyZTogYW4N
Cj4gZXhwZXJpbWVudGFsIGtub3dsZWRnZSBvZiBHb2QuDQoNCg==

From cabo@tzi.org  Mon Apr 23 05:28:01 2012
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 062F021F85FF; Mon, 23 Apr 2012 05:28:01 -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 hTebdajf4FYS; Mon, 23 Apr 2012 05:28:00 -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 33E6821F85D9; Mon, 23 Apr 2012 05:27:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id q3NCRnBF017779; Mon, 23 Apr 2012 14:27:49 +0200 (CEST)
Received: from [192.168.217.105] (p5B3E6405.dip.t-dialin.net [91.62.100.5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id E2E42861; Mon, 23 Apr 2012 14:27:48 +0200 (CEST)
Subject: Re: Proposed IESG Statement on the Conclusion of Experiments
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A0407810736@307622ANEX5.global.avaya.com>
Date: Mon, 23 Apr 2012 14:27:47 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <A6334480-AD4C-4529-AA6A-39091A41DB80@tzi.org>
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk> <EDC652A26FB23C4EB6384A4584434A0407810532@307622ANEX5.global.avaya.com> <A3641334-1936-4F85-B41F-57EE0E95128E@tzi.org> <EDC652A26FB23C4EB6384A4584434A0407810736@307622ANEX5.global.avaya.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
X-Mailer: Apple Mail (2.1257)
Cc: adrian@olddog.co.uk, 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, 23 Apr 2012 12:28:01 -0000

> My point is that if we discuss about 'results of the experiment' and =
the IESG plans to strongly encourage authors of Experimental RFCs to =
briefly describe the results, they should also recommend to include in =
the RFCs in an explicit manner the goals which the results of the =
experiments are to be measured against.=20

This makes sense if you believe the Experimental RFCs are actually (with =
respect to time, with respect to the people involved) coupled to any =
experiments.
Otherwise it's just another layer of red tape, another hoop to jump =
through.

>      be limited to those actively involved with the experiment.
>=20
> So the term 'experiment' already appears in 2026.=20

Yes (but note that this is about the "limited use" designation, not =
about "experimental").  I've wondered about this, too, a long time ago =
when I started to learn about the IETF and RFC 1310.  More than once =
this has been explained to me as a euphemism for "stuff should be used =
only by people that know the stuff, know what they are doing and know =
what will break and how to fix this".  But of course I didn't record =
those hallway conversations and don't remember who said that at the =
time.

Honestly, I would have no idea what I would have written into RFC =
3940/3941, except for "it is believed we haven't had enough deployment =
experience to make this a PS, so please join us in the experiment of =
deploying this for the applications where it is needed." =20

If that sentence is fine with the new procedure, I don't have a problem.

Of course, it would be easy to describe the result of the "experiment": =
3940/3941 were upgraded to PS 5 and 4 years later, with some fixes =
learned from the wider use that the Experimental status (and more time) =
brought with it.  But, again, I'm not sure what we'd have written if =
people had wanted us to write up "the experiment" before going to PS.  =
Maybe a list of fixes (section 10 of RFC 5740)?

I understand there may be grander things going on (like attempting to =
change the way we use addresses in the Internet) that do justify jumping =
through those hoops.  But as a general rule, this procedure makes me =
unhappy.  How about "The IESG may ask for..."?

Gr=FC=DFe, Carsten


From dcrocker@bbiw.net  Mon Apr 23 07:27:23 2012
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 0C41E21F86A1 for <wgchairs@ietfa.amsl.com>; Mon, 23 Apr 2012 07:27:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.932
X-Spam-Level: 
X-Spam-Status: No, score=-3.932 tagged_above=-999 required=5 tests=[AWL=-2.334, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_BACKHAIR_27=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 0tF7uh+mk9l1 for <wgchairs@ietfa.amsl.com>; Mon, 23 Apr 2012 07:27:22 -0700 (PDT)
Received: from sbh11.songbird.com (sbh11.songbird.com [72.52.113.11]) by ietfa.amsl.com (Postfix) with ESMTP id 31F2421F869A for <wgchairs@ietf.org>; Mon, 23 Apr 2012 07:27:21 -0700 (PDT)
Received: from com.flipdogsolutions (adsl-67-127-58-62.dsl.pltn13.pacbell.net [67.127.58.62]) (authenticated bits=0) by sbh11.songbird.com (8.13.8/8.13.8) with ESMTP id q3NERGUL004694 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Mon, 23 Apr 2012 07:27:21 -0700
Date: Mon, 23 Apr 2012 07:27:46 -0700 (PDT)
From: Dave Crocker <dcrocker@bbiw.net>
To: Peter Koch <pk@ISOC.DE>, IETF WG Chairs <wgchairs@ietf.org>
Message-ID: <08c6a495-1aac-4e82-b37d-e16509dbb8d9.maildroid@localhost>
In-Reply-To: <20120423072634.GO8966@x27.adm.denic.de>
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com> <D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com> <B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com> <66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com> <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com> <0e3201cd1e1e$66184090$3248c1b0$@olddog.co.uk> <14875_1334839446_q3JCi4gt024517_01D86B13EFF01AE45550B050@JcK-HP8200.jck.com> <1334938056.21993.94.camel@destiny.pc.cs.cmu.edu> <C153B9DD-4A3A-4FCE-B29A-C4857E7CFC78@vigilsec.com> <20120423072634.GO8966@x27.adm.denic.de>
Subject: Re: Formats for WG and BOF Agendas
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_2_1107914336.1335191266695"
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh11.songbird.com [72.52.113.11]); Mon, 23 Apr 2012 07:27:21 -0700 (PDT)
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Apr 2012 14:27:23 -0000

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

when posted to the site, minutes should be auto-posted to the wg mailing list (and not just a link)?  

That sounds reasonable to me.


/d

--

Dave Crocker
bbiw.net



-----Original Message-----
From: Peter Koch <pk@ISOC.DE>
To: IETF WG Chairs <wgchairs@ietf.org>
Sent: Mon, 23 Apr 2012 12:26 AM
Subject: Re: Formats for WG and BOF Agendas

On Fri, Apr 20, 2012 at 12:55:20PM -0400, Russ Housley wrote:

> (3) Minutes should be limited to text, html, and pdf.

I'd support this without the PDF option.

On a related issue, we increasingly see the agendas and minutes only
posted to the materials site, which means there is no copy available
in the mail archives. Maybe that ought to change back.

-Peter

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

<div><p>when posted to the site, minutes should be auto-posted to the wg mailing list (and not just a link)?&nbsp; <br/><br/><u>That</u> sounds reasonable to me.<br/><br/><font color ="#888888"><p><br>
<font color ="#888888">/d</font></p>
<p><font color ="#888888">--</font></p>
<p><font color ="#888888">Dave Crocker</font><br>
<font color ="#888888"><a href="http://bbiw.net">bbiw.net</a></font></p>
</font></p>
<br/><br/>-----Original Message-----<br/>From: Peter Koch &lt;pk@ISOC.DE&gt;<br/>To: IETF WG Chairs &lt;wgchairs@ietf.org&gt;<br/>Sent: Mon, 23 Apr 2012 12:26 AM<br/>Subject: Re: Formats for WG and BOF Agendas<br/><br/></div><p>On Fri, Apr 20, 2012 at 12:55:20PM -0400, Russ Housley wrote:&#13;<br>
&#13;<br>
&gt; (3) Minutes should be limited to text, html, and pdf.&#13;<br>
&#13;<br>
I'd support this without the PDF option.&#13;<br>
&#13;<br>
On a related issue, we increasingly see the agendas and minutes only&#13;<br>
posted to the materials site, which means there is no copy available&#13;<br>
in the mail archives. Maybe that ought to change back.&#13;<br>
&#13;<br>
-Peter&#13;<br>
</p>

------=_Part_2_1107914336.1335191266695--

From housley@vigilsec.com  Mon Apr 23 07:32:34 2012
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 9FBC221F8666 for <wgchairs@ietfa.amsl.com>; Mon, 23 Apr 2012 07:32:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.349
X-Spam-Level: 
X-Spam-Status: No, score=-102.349 tagged_above=-999 required=5 tests=[AWL=-0.251, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BAD_LINEBREAK=0.5, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rAQfyTMnWfsE for <wgchairs@ietfa.amsl.com>; Mon, 23 Apr 2012 07:32:34 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id D8B1021F86BE for <wgchairs@ietf.org>; Mon, 23 Apr 2012 07:32:33 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id ADB1DF2404B for <wgchairs@ietf.org>; Mon, 23 Apr 2012 10:32:43 -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 TDgZFT5VHJaa for <wgchairs@ietf.org>; Mon, 23 Apr 2012 10:32:27 -0400 (EDT)
Received: from [172.16.2.61] (unknown [195.70.5.235]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 9A249F24035 for <wgchairs@ietf.org>; Mon, 23 Apr 2012 10:32:40 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-133-402062867
Subject: Re: Formats for WG and BOF Agendas
Date: Mon, 23 Apr 2012 10:32:28 -0400
In-Reply-To: <08c6a495-1aac-4e82-b37d-e16509dbb8d9.maildroid@localhost>
To: IETF WG Chairs <wgchairs@ietf.org>
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com> <D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com> <B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com> <66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com> <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com> <0e3201cd1e1e$66184090$3248c1b0$@olddog.co.uk> <14875_1334839446_q3JCi4gt024517_01D86B13EFF01AE45550B050@JcK-HP8200.jck.com> <1334938056.21993.94.camel@destiny.pc.cs.cmu.edu> <C153B9DD-4A3A-4FCE-B29A-C4857E7CFC78@vigilsec.com> <20120423072634.GO8966@x27.adm.denic.de> <08c6a495-1aac-4e82-b37d-e16509dbb8d9.maildroid@localhost>
Message-Id: <26CD4A90-9D91-4CAB-A6A6-95FFFFDF26BC@vigilsec.com>
X-Mailer: Apple Mail (2.1084)
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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, 23 Apr 2012 14:32:34 -0000

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

Not me.  Many times a WG chair posts them and then asks for comments.  =
Some chairs post edits as the comments come in.  That could lead to many =
postings, but the practice does reduce the number of times you get the =
same comment.

Russ


On Apr 23, 2012, at 10:27 AM, Dave Crocker wrote:

> when posted to the site, minutes should be auto-posted to the wg =
mailing list (and not just a link)? =20
>=20
> That sounds reasonable to me.
>=20
>=20
>=20
> /d
>=20
> --
>=20
> Dave Crocker
> bbiw.net
>=20
>=20
>=20
>=20
> -----Original Message-----
> From: Peter Koch <pk@ISOC.DE>
> To: IETF WG Chairs <wgchairs@ietf.org>
> Sent: Mon, 23 Apr 2012 12:26 AM
> Subject: Re: Formats for WG and BOF Agendas
>=20
> On Fri, Apr 20, 2012 at 12:55:20PM -0400, Russ Housley wrote:=0D
>=20
> > (3) Minutes should be limited to text, html, and pdf.=0D
>=20
> I'd support this without the PDF option.=0D
>=20
> On a related issue, we increasingly see the agendas and minutes only=0D=

> posted to the materials site, which means there is no copy available=0D=

> in the mail archives. Maybe that ought to change back.=0D
>=20
> -Peter=0D


--Apple-Mail-133-402062867
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Not =
me. &nbsp;Many times a WG chair posts them and then asks for comments. =
&nbsp;Some chairs post edits as the comments come in. &nbsp;That could =
lead to many postings, but the practice does reduce the number of times =
you get the same =
comment.<div><br></div><div>Russ</div><div><br></div><div><br><div><div>On=
 Apr 23, 2012, at 10:27 AM, Dave Crocker wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div><p>when=
 posted to the site, minutes should be auto-posted to the wg mailing =
list (and not just a link)?&nbsp; <br><br><u>That</u> sounds reasonable =
to me.<br><br><font color=3D"#888888"></font></p><p><font =
color=3D"#888888"><br>
<font color=3D"#888888">/d</font></font></p><font =
color=3D"#888888"><p><font color=3D"#888888">--</font></p><p><font =
color=3D"#888888">Dave Crocker</font><br>
<font color=3D"#888888"><a =
href=3D"http://bbiw.net/">bbiw.net</a></font></p>
</font><div><br class=3D"webkit-block-placeholder"></div>
<br><br>-----Original Message-----<br>From: Peter Koch &lt;<a =
href=3D"mailto:pk@ISOC.DE">pk@ISOC.DE</a>&gt;<br>To: IETF WG Chairs =
&lt;<a =
href=3D"mailto:wgchairs@ietf.org">wgchairs@ietf.org</a>&gt;<br>Sent: =
Mon, 23 Apr 2012 12:26 AM<br>Subject: Re: Formats for WG and BOF =
Agendas<br><br></div><p>On Fri, Apr 20, 2012 at 12:55:20PM -0400, Russ =
Housley wrote:=0D<br>
=0D<br>
&gt; (3) Minutes should be limited to text, html, and pdf.=0D<br>
=0D<br>
I'd support this without the PDF option.=0D<br>
=0D<br>
On a related issue, we increasingly see the agendas and minutes only=0D=
<br>
posted to the materials site, which means there is no copy available=0D=
<br>
in the mail archives. Maybe that ought to change back.=0D<br>
=0D<br>
-Peter=0D<br>
</p>
</blockquote></div><br></div></body></html>=

--Apple-Mail-133-402062867--

From julien.meuric@orange.com  Mon Apr 23 07:57:32 2012
Return-Path: <julien.meuric@orange.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95EE921F86C1 for <wgchairs@ietfa.amsl.com>; Mon, 23 Apr 2012 07:57:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 8-z8ZOhXX6rj for <wgchairs@ietfa.amsl.com>; Mon, 23 Apr 2012 07:57:29 -0700 (PDT)
Received: from p-mail2.rd.francetelecom.com (p-mail2.rd.francetelecom.com [195.101.245.16]) by ietfa.amsl.com (Postfix) with ESMTP id 672C421F86B5 for <wgchairs@ietf.org>; Mon, 23 Apr 2012 07:57:29 -0700 (PDT)
Received: from p-mail2.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id C4DAEE30251 for <wgchairs@ietf.org>; Mon, 23 Apr 2012 17:09:28 +0200 (CEST)
Received: from ftrdsmtp2.rd.francetelecom.fr (unknown [10.192.128.47]) by p-mail2.rd.francetelecom.com (Postfix) with ESMTP id BFA5CE301B1 for <wgchairs@ietf.org>; Mon, 23 Apr 2012 17:09:28 +0200 (CEST)
Received: from ftrdmel10.rd.francetelecom.fr ([10.192.128.44]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 23 Apr 2012 16:57:28 +0200
Received: from [10.193.71.152] ([10.193.71.152]) by ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 23 Apr 2012 16:57:28 +0200
Message-ID: <4F956DD7.2060509@orange.com>
Date: Mon, 23 Apr 2012 16:57:27 +0200
From: Julien Meuric <julien.meuric@orange.com>
Organization: France Telecom
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120410 Thunderbird/11.0.1
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: Formats for WG and BOF Agendas
References: <6E99F6CF-2DC5-41D4-A605-382B644F5403@amsl.com> <D8828209-9C65-4D4B-84BE-D60EBFEFBA6E@amsl.com> <B668E7D6-59DA-4867-AB8A-B1A0EE5AAEF1@amsl.com> <66087E95-69F6-4B11-902E-D7EDC05FAF1B@vigilsec.com> <EF92865E-E2B4-4DBA-8AB4-1E616A195D32@vigilsec.com> <0e3201cd1e1e$66184090$3248c1b0$@olddog.co.uk> <14875_1334839446_q3JCi4gt024517_01D86B13EFF01AE45550B050@JcK-HP8200.jck.com> <1334938056.21993.94.camel@destiny.pc.cs.cmu.edu> <C153B9DD-4A3A-4FCE-B29A-C4857E7CFC78@vigilsec.com> <20120423072634.GO8966@x27.adm.denic.de> <08c6a495-1aac-4e82-b37d-e16509dbb8d9.maildroid@localhost> <26CD4A90-9D91-4CAB-A6A6-95FFFFDF26BC@vigilsec.com>
In-Reply-To: <26CD4A90-9D91-4CAB-A6A6-95FFFFDF26BC@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 23 Apr 2012 14:57:28.0625 (UTC) FILETIME=[66F15A10:01CD2161]
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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, 23 Apr 2012 14:57:32 -0000

Hi.

I agree. My experience with auto-mailing linked to document versioning 
will keep me away from that idea. If associated to auto-posting, I will 
tend to edit comments only on a local file which will be uploaded much 
later... (or sometimes even forgotten).

Anyway, an option (a button) allowing the chair/secretary to easily 
request an auto-generated announce could be a useful feature.

Julien


Le 23/04/2012 16:32, Russ Housley a écrit :
> Not me.  Many times a WG chair posts them and then asks for comments. 
>  Some chairs post edits as the comments come in.  That could lead to 
> many postings, but the practice does reduce the number of times you 
> get the same comment.
>
> Russ
>
>
> On Apr 23, 2012, at 10:27 AM, Dave Crocker wrote:
>
>> when posted to the site, minutes should be auto-posted to the wg 
>> mailing list (and not just a link)?
>>
>> _That_ sounds reasonable to me.
>>
>>
>> /d
>>
>> --
>>
>> Dave Crocker
>> bbiw.net <http://bbiw.net/>
>>
>>
>>
>>
>> -----Original Message-----
>> From: Peter Koch <pk@ISOC.DE <mailto:pk@ISOC.DE>>
>> To: IETF WG Chairs <wgchairs@ietf.org <mailto:wgchairs@ietf.org>>
>> Sent: Mon, 23 Apr 2012 12:26 AM
>> Subject: Re: Formats for WG and BOF Agendas
>>
>> On Fri, Apr 20, 2012 at 12:55:20PM -0400, Russ Housley wrote:
>>
>> > (3) Minutes should be limited to text, html, and pdf.
>>
>> I'd support this without the PDF option.
>>
>> On a related issue, we increasingly see the agendas and minutes only
>> posted to the materials site, which means there is no copy available
>> in the mail archives. Maybe that ought to change back.
>>
>> -Peter
>>
>

From magnus.westerlund@ericsson.com  Mon Apr 23 23:48:02 2012
Return-Path: <magnus.westerlund@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 E963521E804C for <wgchairs@ietfa.amsl.com>; Mon, 23 Apr 2012 23:48:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.137
X-Spam-Level: 
X-Spam-Status: No, score=-106.137 tagged_above=-999 required=5 tests=[AWL=0.112, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m+6ych8pyeVx for <wgchairs@ietfa.amsl.com>; Mon, 23 Apr 2012 23:48:02 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 42A5711E80AB for <wgchairs@ietf.org>; Mon, 23 Apr 2012 23:48:02 -0700 (PDT)
X-AuditID: c1b4fb2d-b7b76ae0000063d8-b0-4f964ca1eaf7
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 0C.C9.25560.1AC469F4; Tue, 24 Apr 2012 08:48:01 +0200 (CEST)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0256.eemea.ericsson.se (153.88.115.97) with Microsoft SMTP Server id 8.3.213.0; Tue, 24 Apr 2012 08:48:01 +0200
Message-ID: <4F964C92.3020804@ericsson.com>
Date: Tue, 24 Apr 2012 08:47:46 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: "Murray S. Kucherawy" <msk@cloudmark.com>
Subject: Re: latest missing replaced-by information
References: <E9354164-6546-42A9-BAC4-BE6660855AE9@netapp.com> <4F8EC284.3020301@alcatel-lucent.com> <5EB4938E-5550-48CD-91D1-77080C2584C4@netapp.com> <12E8767B-2A14-4363-A6C6-904D8F3CCADB@tik.ee.ethz.ch> <9452079D1A51524AA5749AD23E0039280F855A@exch-mbx901.corp.cloudmark.com>
In-Reply-To: <9452079D1A51524AA5749AD23E0039280F855A@exch-mbx901.corp.cloudmark.com>
X-Enigmail-Version: 1.4
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
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, 24 Apr 2012 06:48:03 -0000

On 2012-04-18 21:17, Murray S. Kucherawy wrote:
> 
> 1) If an AD has tagged something 'AD is watching' while it's still
> outside the WG, it can no longer be adopted into a WG via the
> datatracker.

If I understand this correctly, I think it is a bug in the WG tracker.
You should report it to ietf-actions.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From hallam@gmail.com  Wed Apr 25 07:27:15 2012
Return-Path: <hallam@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 E9DAA21F86D3; Wed, 25 Apr 2012 07:27:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.569
X-Spam-Level: 
X-Spam-Status: No, score=-3.569 tagged_above=-999 required=5 tests=[AWL=0.030,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QR0B2cu8B2cf; Wed, 25 Apr 2012 07:27:11 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 12CC321F86E1; Wed, 25 Apr 2012 07:27:10 -0700 (PDT)
Received: by yhkk25 with SMTP id k25so162694yhk.31 for <multiple recipients>; Wed, 25 Apr 2012 07:27:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=+5ZUDn1VIPSQrP5tr4Je1lFm9yOjkx2Vl40UBnwDJqk=; b=YR6kWgfLReJWGnbDfHGHCzf6yqcdpROjKLqoZ9mrbOcWCo50Ss+jag1tSpJq+/KwnY EVDlTYLjzHQPOpoI69US+dpGgOB7BF2MPhD93AJpzP7jvR9d0WhYdgKoqSaZTluSfXjp 6kFPSAD2C7JbGnPDKMjRQxwQouYH7uYYem1r3zgir2aTRwX7kMz18iYVcxNCrikH6Co3 SWxF7ROqmqTJLsq27IQcpXT7J883O5ROjx/7teWrdQiZtt7XZTdodmEznB5gkI9lbp5N bsp+fQFnFBZOeEHXwCezjmJrGs2Nd3jfaTF6exvKfsJ7jeiSx6Bce4DQDP6zByhc5ivE ruiw==
MIME-Version: 1.0
Received: by 10.60.27.7 with SMTP id p7mr3730975oeg.56.1335364029617; Wed, 25 Apr 2012 07:27:09 -0700 (PDT)
Received: by 10.182.41.165 with HTTP; Wed, 25 Apr 2012 07:27:09 -0700 (PDT)
In-Reply-To: <E0BDBD64-D3D4-4248-9EB2-BDD1F1CE39BF@virtualized.org>
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk> <248A261F-D83D-4F97-8F5D-A9A0BCD2EC0D@sobco.com> <f8e77298-bbd5-4ad8-80df-a3c367f67d95.maildroid@localhost> <E0BDBD64-D3D4-4248-9EB2-BDD1F1CE39BF@virtualized.org>
Date: Wed, 25 Apr 2012 10:27:09 -0400
Message-ID: <CAMm+LwjWV3eoeYgpbE92kZ7vBHHX3BqoXv95yfU-0ZNm3SqN4Q@mail.gmail.com>
Subject: Re: Proposed IESG Statement on the Conclusion of Experiments
From: Phillip Hallam-Baker <hallam@gmail.com>
To: David Conrad <drc@virtualized.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: wgchairs@ietf.org, IETF discussion list <ietf@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, 25 Apr 2012 14:27:15 -0000

I see no value in deallocating code point spaces and a huge amount of
potential harm.

Except at the very lowest levels of the protocol stack (IP and BGP)
there is really no technical need for a namespace that is limited. We
do have some protocols that will come to a crisis some day but there
are plenty of ways that the code space for DNS, TLS etc can be
expanded if we ever need to.


The Internet is driven by innovation and experiment. There are
certainly people who think that the role of this organization is to
protect the Internet from the meddling of people who might not get it
but they are wrong.

Even more wrong is the idea that IANA can actually act as suggested.
IANA only exists by mutual consent. I am happy to register a code
point if there is a reasonable procedure to do so. But if the idea is
to force me to kiss someone's ring then I'll pick a number and ship
the code and let other folk work out the problems later.

This already happens on a significant scale in the wild. SRV code
points being a prime example. There are far more unofficial code
points than recognized ones. Some of them are in standards I wrote at
W3C and OASIS. It would be best if IANA tracked these but I think it
rather unlikely anyone is going to accidentally overwrite the SAML or
the XKMS SRV code points.

It has happened with other registries too. Back in the day there was
an attempt to stop the storage manufacturers using ethernet IDs on
their drives. So the drive manufacturers simply declared a block of
space (Cxxxxxx) as theirs and the IEEE has since been forced to accept
this as a fait accompli. It has happened in UPC codes as well, when
the Europeans decided that the US authority was charging them
ridiculous fees they just extended the code by an octet and set
themselves up as a meta-registry.


The only role of IANA is to help people avoid treading on each other
by accident. If it starts issuing code points that have been 'lightly
used', the value of IANA is degraded. I certainly don't want my
protocol to have to deal with issues that are caused by someone's
'experiment' that has not completely shut down. The only value of
going to IANA rather than choosing one myself is to avoid
contamination with earlier efforts.

The only area where I can see the benefits of re-allocation
outweighing the risks is in IP port assignments but even there I think
the real solution has to be to simply ditch the whole notion of port
numbers and use SRV type approaches for new protocols.


IANA is not a control point for the Internet. A fact that people need
to keep in mind when the ITU attempts to grab control in Dubai later
on this year.

Weakness is strength: The registries are not the control points people
imagine because they only have authority as long as people consent.


On Thu, Apr 19, 2012 at 5:17 PM, David Conrad <drc@virtualized.org> wrote:
> Hi,
>
> "Scott O Bradner <sob@sobco.com>" wrote:
>> encouraging a report is fine
>
> Agreed.
>
>> retracting the code points seems to add more confusion than it is worth =
unless the code space is very tight
>
> Disagree. =A0From my experience at IANA, trying to figure out who to cont=
act to remove a code point gets harder the longer the code points are not b=
eing used. =A0Unless the code space is unlimited, I'd argue that you want t=
o deallocate as soon as an experiment is over. =A0I'd even go so far as to =
say that the original proposal for experimental code points should have exp=
licit revocation dates (which can, of course, be refreshed similarly to IDs=
).
>
>> and I see no reason to obsolete the experimental rfc or move it to histo=
ric status unless the report is that some bad thing happens when you try it=
 out - updating the old rfc is fine
>
> Having been involved with RFC 6563, I think in general it is quite useful=
 to signal "hey, you really don't want to implement this". =A0If this can b=
e done by updating the old RFC, that's fine.
>
>> and I agree with Elliot about the nature of research - it is very common=
 to not reach a conclusion that something is bad (as in bad for the net) - =
and that is the only case where I think that an experiment should be flagge=
d as a don't go there situation
>
> Agreed, with the proviso that limited resources (whether they are scarce =
or not) should be reclaimed.
>
> Regards,
> -drc
>



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

From hallam@gmail.com  Wed Apr 25 11:24:36 2012
Return-Path: <hallam@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 CED2221F88A8; Wed, 25 Apr 2012 11:24:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.571
X-Spam-Level: 
X-Spam-Status: No, score=-3.571 tagged_above=-999 required=5 tests=[AWL=0.028,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XZbmNBSTlI3F; Wed, 25 Apr 2012 11:24:35 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id C4A1221F88AB; Wed, 25 Apr 2012 11:24:34 -0700 (PDT)
Received: by ghbg16 with SMTP id g16so436518ghb.31 for <multiple recipients>; Wed, 25 Apr 2012 11:24:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=K9QBYkcB+b9X2nbhePaqFq6EmXbmworNybVUraxwmOc=; b=jq/L5eomXH4KfCN6rYxN+EBGQHoiTcyh0lChBF7kbCVckWl6SRk3YY/jwGr+t4m/nU yWpiA9SQxL8wuRtVDkYgbA55I9j1zlyhB1oizLH2TNNpir8yOihc/Hb7/H0dxV2ytlg/ F3GATaLqehiTzNNdvkJ406oUMYsC2XEFhFi+UmmOEuyitmHhMA1Ml0hzGf31jtioAVNO Lrx39IyrBHq6ovSkgPqQsxVbDIjVy/weIGTmQ1NVQq8oSGJt0MyogILxe+XRroiT+bM0 f19P234NWUFpBaqT5F4FxEdpS0F9Z0cbTd0CU/mhata2aqWyi9bQJ/U+jPPgwx8N2Gh1 l7Bg==
MIME-Version: 1.0
Received: by 10.60.27.7 with SMTP id p7mr272825oeg.56.1335378274240; Wed, 25 Apr 2012 11:24:34 -0700 (PDT)
Received: by 10.182.41.165 with HTTP; Wed, 25 Apr 2012 11:24:34 -0700 (PDT)
In-Reply-To: <01OEQEU68N2Y0006TF@mauve.mrochek.com>
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk> <248A261F-D83D-4F97-8F5D-A9A0BCD2EC0D@sobco.com> <f8e77298-bbd5-4ad8-80df-a3c367f67d95.maildroid@localhost> <E0BDBD64-D3D4-4248-9EB2-BDD1F1CE39BF@virtualized.org> <CAMm+LwjWV3eoeYgpbE92kZ7vBHHX3BqoXv95yfU-0ZNm3SqN4Q@mail.gmail.com> <01OEQEU68N2Y0006TF@mauve.mrochek.com>
Date: Wed, 25 Apr 2012 14:24:34 -0400
Message-ID: <CAMm+LwhGCZJSosYCVGfT1BrbK46LWuyp_kA3OUWseYE60+3n5w@mail.gmail.com>
Subject: Re: Proposed IESG Statement on the Conclusion of Experiments
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Ned Freed <ned.freed@mrochek.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: wgchairs@ietf.org, David Conrad <drc@virtualized.org>, IETF discussion list <ietf@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, 25 Apr 2012 18:24:36 -0000

+1

Deprecating a code point is very different from deallocating it which
implies that it is going to be given out again in the future. Last
thing I want is a used code point.

I agree that avoiding multiple allocations is also a function of IANA,
but this is also something that argues for not being overly strict. If
it is too hard to get an allocation then there will be multiple
unofficial versions. Eventually there may be an attempt to pick one of
them as 'official'.

On Wed, Apr 25, 2012 at 1:46 PM, Ned Freed <ned.freed@mrochek.com> wrote:
>> I see no value in deallocating code point spaces and a huge amount of
>> potential harm.
>
> It depends on the size of the space. I completely agree that if the space=
 is
> large - and that's almost always the case - then deallocating is going to=
 be
> somewhere between silly and very damaging.
>
> Deprecacting the use of a code point, OTOH, may make sense even if the sp=
ace is
> large.
>
> The takeaway here, I think, is that if you're going to "conclude" experim=
ents,
> you need to examine these allocations and do something sensible with them=
,
> where "sensible" is rarely going to mean "deallocate".
>
>> Except at the very lowest levels of the protocol stack (IP and BGP)
>> there is really no technical need for a namespace that is limited. We
>> do have some protocols that will come to a crisis some day but there
>> are plenty of ways that the code space for DNS, TLS etc can be
>> expanded if we ever need to.
>
> There may not be any technical need, but there are a number of legacy des=
igns
> that were done ... poorly.
>
>> The Internet is driven by innovation and experiment. There are
>> certainly people who think that the role of this organization is to
>> protect the Internet from the meddling of people who might not get it
>> but they are wrong.
>
> +1
>
>> Even more wrong is the idea that IANA can actually act as suggested.
>> IANA only exists by mutual consent. I am happy to register a code
>> point if there is a reasonable procedure to do so. But if the idea is
>> to force me to kiss someone's ring then I'll pick a number and ship
>> the code and let other folk work out the problems later.
>
>> This already happens on a significant scale in the wild. SRV code
>> points being a prime example. There are far more unofficial code
>> points than recognized ones. Some of them are in standards I wrote at
>> W3C and OASIS. It would be best if IANA tracked these but I think it
>> rather unlikely anyone is going to accidentally overwrite the SAML or
>> the XKMS SRV code points.
>
> Media types are an excellent example of this. The original registration
> procedures were too restrictive so people simply picked names to use. We =
fixed
> that for "vendor" assignments (fill in a web form) and the registrations
> starting rolling in. (We're now trying to do the same for "standard"
> assignments.) But of course we now have a legacy of unassigned material
> to deal with.
>
>> It has happened with other registries too. Back in the day there was
>> an attempt to stop the storage manufacturers using ethernet IDs on
>> their drives. So the drive manufacturers simply declared a block of
>> space (Cxxxxxx) as theirs and the IEEE has since been forced to accept
>> this as a fait accompli. It has happened in UPC codes as well, when
>> the Europeans decided that the US authority was charging them
>> ridiculous fees they just extended the code by an octet and set
>> themselves up as a meta-registry.
>
>> The only role of IANA is to help people avoid treading on each other
>> by accident. If it starts issuing code points that have been 'lightly
>> used', the value of IANA is degraded. I certainly don't want my
>> protocol to have to deal with issues that are caused by someone's
>> 'experiment' that has not completely shut down. The only value of
>> going to IANA rather than choosing one myself is to avoid
>> contamination with earlier efforts.
>
> No, not quite. The other important role is (hopefully) to keep people fro=
m
> having multiple allocations for the same thing.
>
>> The only area where I can see the benefits of re-allocation
>> outweighing the risks is in IP port assignments but even there I think
>> the real solution has to be to simply ditch the whole notion of port
>> numbers and use SRV type approaches for new protocols.
>
> +1
>
>> IANA is not a control point for the Internet. A fact that people need
>> to keep in mind when the ITU attempts to grab control in Dubai later
>> on this year.
>
>> Weakness is strength: The registries are not the control points people
>> imagine because they only have authority as long as people consent.
>
> Good point.
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Ned



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

From hallam@gmail.com  Wed Apr 25 11:26:51 2012
Return-Path: <hallam@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 B3DA721F887D; Wed, 25 Apr 2012 11:26:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.572
X-Spam-Level: 
X-Spam-Status: No, score=-3.572 tagged_above=-999 required=5 tests=[AWL=0.027,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3aRQIWNPVmDf; Wed, 25 Apr 2012 11:26:51 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2294721F8882; Wed, 25 Apr 2012 11:26:51 -0700 (PDT)
Received: by obbwd20 with SMTP id wd20so447105obb.31 for <multiple recipients>; Wed, 25 Apr 2012 11:26:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+CF74BzGcsYvsGiyYRsYprLtqkpXpmOLgFuiluEjztg=; b=uViGYVuRKAEBgZePuIdBHZJUi7R8R5eYt33CrnlmkMhnjbdrHDsf33XvGdFJAfEOPf UKAM8EdsqkTaJ1mEM1VxwhGSYSA5ILFo5gaDWu8Ms6CQrEukSaWp3tZFeNZdBBoaKfCG WMZzxM0ETrr3k8Wpupld4rxMlrrQiFRUt+UCI7R8xPDQdsgRFxETXW9jsjpLr5fK1TKD k1RJph6fk0euwq+Y+QCYStP3Uxk94y87bsasno/ZNIx8nO+6s0YBadYTR+QksMEcy2HD uOPQ3cFxv8tQY3k4w8XqKeyZJBXQAqZCTdiEWelCGoz37J2t9kjCStzJXU3MfNB2vFI1 zn8g==
MIME-Version: 1.0
Received: by 10.182.31.47 with SMTP id x15mr4551857obh.76.1335378410778; Wed, 25 Apr 2012 11:26:50 -0700 (PDT)
Received: by 10.182.41.165 with HTTP; Wed, 25 Apr 2012 11:26:50 -0700 (PDT)
In-Reply-To: <107555D1-057F-4D8B-944D-4A7A84F2A3D3@virtualized.org>
References: <0f6601cd1e6b$5ff2e420$1fd8ac60$@olddog.co.uk> <248A261F-D83D-4F97-8F5D-A9A0BCD2EC0D@sobco.com> <f8e77298-bbd5-4ad8-80df-a3c367f67d95.maildroid@localhost> <E0BDBD64-D3D4-4248-9EB2-BDD1F1CE39BF@virtualized.org> <CAMm+LwjWV3eoeYgpbE92kZ7vBHHX3BqoXv95yfU-0ZNm3SqN4Q@mail.gmail.com> <107555D1-057F-4D8B-944D-4A7A84F2A3D3@virtualized.org>
Date: Wed, 25 Apr 2012 14:26:50 -0400
Message-ID: <CAMm+LwhA1u20BT6ak9k04DWgKDmrNp7ic07QdBYGQCGQ2e+Jsw@mail.gmail.com>
Subject: Re: Proposed IESG Statement on the Conclusion of Experiments
From: Phillip Hallam-Baker <hallam@gmail.com>
To: David Conrad <drc@virtualized.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: wgchairs@ietf.org, IETF discussion list <ietf@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, 25 Apr 2012 18:26:51 -0000

Not arguable in the fashion that you do. You seem to want to signal
disagreement without needing to actually argue a contrary case.

Cutting pieces out of someone's argument to make it look stupid is
itself a stupid trick.


On Wed, Apr 25, 2012 at 12:55 PM, David Conrad <drc@virtualized.org> wrote:
> On Apr 25, 2012, at 7:27 AM, Phillip Hallam-Baker wrote:
>> Except at the very lowest levels of the protocol stack (IP and BGP)
>> there is really no technical need for a namespace that is limited.
>
> Arguable, but irrelevant since the reality is that historically many (most?) protocols defined by the IETF to date used fixed length fields implying limitations in the number of identifiers in those namespaces.
>
>> We
>> do have some protocols that will come to a crisis some day but there
>> are plenty of ways that the code space for DNS, TLS etc can be
>> expanded if we ever need to.
>
> Unfortunately, experience has demonstrated that most implementations of protocols do not handle potential expansion.
>
>> Even more wrong is the idea that IANA can actually act as suggested.
>
> You seem to have an odd idea of what is being suggested. However, experience has shown arguing with you is a waste of time so I'll let others engage if they care.
>
>> Weakness is strength
>
>
> And we've always been at war with Eastasia.
>
> Regards,
> -drc
>



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

From glen@amsl.com  Thu Apr 26 10:40:53 2012
Return-Path: <glen@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 5B0FC21F84DA; Thu, 26 Apr 2012 10:40:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.334
X-Spam-Level: 
X-Spam-Status: No, score=-102.334 tagged_above=-999 required=5 tests=[AWL=0.266, 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 X4-dfgrVcZWu; Thu, 26 Apr 2012 10:40:52 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id EDAB021F8484; Thu, 26 Apr 2012 10:40:52 -0700 (PDT)
Received: by c8a.amsl.com (Postfix, from userid 1000) id BCDED12CA93; Thu, 26 Apr 2012 10:40:52 -0700 (PDT)
Date: Thu, 26 Apr 2012 10:40:52 -0700
From: Glen <glen@amsl.com>
To: iab@ietf.org, iesg@ietf.org, iaoc@ietf.org, wgchairs@ietf.org, rfc-editor@rfc-editor.org
Subject: Overnight slowdown report
Message-ID: <20120426174052.GB738@amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: rpelletier@isoc.org, pelletier@isoc.org, 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: Thu, 26 Apr 2012 17:40:53 -0000

Good morning -

Last night at about 10:50PM Pacific time, traffic out of the AMS primary data
center in Fremont became extremely slow.  During that time, web pages for
all sites may have been served slowly, or become stalled.  Our engineers
came online and performed circuit and server checks, and before any cause 
could be positively identified, normal speeds had been restored.  The total
slowdown period was 39 minutes.

During the testing we did determine that all of our servers were up and 
functioning properly; in addition, our circuit path from our center to
AT&T was also up and functioning properly.  (We were able to connect remotely
through our backup circuits without issue.)  We therefore suspect that 
something upstream was occurring, and have opened an inquiry with AT&T to 
see if the cause can be determined.

No machines were compromised, no email or data was lost, and no damage 
occurred.  As always, any questions, please feel free to let me know.

Thank you,
Glen

Glen Barney
IT Director
AMS

From sm@elandsys.com  Thu Apr 26 10:58:36 2012
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 966C121E808D; Thu, 26 Apr 2012 10:58:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.568
X-Spam-Level: 
X-Spam-Status: No, score=-102.568 tagged_above=-999 required=5 tests=[AWL=0.031, 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 O2t4Bwjkw7CW; Thu, 26 Apr 2012 10:58:34 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D5BA21E80C8; Thu, 26 Apr 2012 10:58:29 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([41.136.238.158]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q3QHw9LR002013 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 26 Apr 2012 10:58:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1335463104; i=@elandsys.com; bh=xzLJNiD7owktDZTlB6enKDMLOwxF+6RPDpFNbloqook=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=pA/SYdQuElOY0RmtohIF/eWIfakQCZtU4ze0Ys4iChFdEmaB7W8mtUN6KABH2Qnzu 2vBW/32TcfSrKOSz9aiHo4/AOs33oXY/BvgRC/bd4IZgVYuXrVLXImxWGTQwveqh16 R50Lvt+yKEIQtFzwPQKuOg/tKBVQLHr6A5R2FBk8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1335463104; i=@elandsys.com; bh=xzLJNiD7owktDZTlB6enKDMLOwxF+6RPDpFNbloqook=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=fnS7o/tefLtq9M7WCfAv5LyaUvCjHiTIypN7dIza20vjdwGUMR5+WLYh6OZkLF7h1 EQzgTT4RubkXdiokXyz/JfzAmjUzsi/WhTps6nPkbWb38CSxp6zuGyd5ur7j6ZOJBD lAwMzrmV7ZRvs5GQIP8Rd4Z2wvJ7pVmEjKmwp3TI=
Message-Id: <6.2.5.6.2.20120426104416.0a52a000@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 26 Apr 2012 10:56:37 -0700
To: Glen <glen@amsl.com>, iab@ietf.org, iesg@ietf.org, iaoc@ietf.org, rfc-editor@rfc-editor.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Overnight slowdown report
In-Reply-To: <20120426174052.GB738@amsl.com>
References: <20120426174052.GB738@amsl.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: Thu, 26 Apr 2012 17:58:36 -0000

Hi Glen,
At 10:40 26-04-2012, Glen wrote:
>Last night at about 10:50PM Pacific time, traffic out of the AMS primary data
>center in Fremont became extremely slow.  During that time, web pages for
>all sites may have been served slowly, or become stalled.  Our engineers
>came online and performed circuit and server checks, and before any cause
>could be positively identified, normal speeds had been restored.  The total
>slowdown period was 39 minutes.

I was going to send an email about that.  The ietf.org and 
rfc-editor.org network was not reachable during that time.  The last 
reachable hop was cr81.sj2ca.ip.att.net (12.122.1.118).

As the known point of contact were unreachable, I gave up on sending 
a notification.

BTW, there is a similar issue right now.

Regards,
S. Moonesamy 


From glen@amsl.com  Thu Apr 26 12:02:03 2012
Return-Path: <glen@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 5D24D21E80B0; Thu, 26 Apr 2012 12:02:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.368
X-Spam-Level: 
X-Spam-Status: No, score=-102.368 tagged_above=-999 required=5 tests=[AWL=0.232, 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 mlxGA5uKPJ1P; Thu, 26 Apr 2012 12:02:03 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 05E0921E80DF; Thu, 26 Apr 2012 12:02:03 -0700 (PDT)
Received: by c8a.amsl.com (Postfix, from userid 1000) id 4970012C875; Thu, 26 Apr 2012 12:02:03 -0700 (PDT)
Date: Thu, 26 Apr 2012 12:02:03 -0700
From: Glen <glen@amsl.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Overnight slowdown report
Message-ID: <20120426190203.GC24083@amsl.com>
References: <20120426174052.GB738@amsl.com> <6.2.5.6.2.20120426104416.0a52a000@elandnews.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6.2.5.6.2.20120426104416.0a52a000@elandnews.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: iaoc@ietf.org, iab@ietf.org, wgchairs@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Apr 2012 19:02:03 -0000

On Thu, Apr 26, 2012 at 10:56:37AM -0700, S Moonesamy wrote:
> BTW, there is a similar issue right now.

We are not experiencing any issues at the moment, nor have we all morning.

If you are having issues, you are welcome and encouraged to open a ticket
by emailing ietf-action@ietf.org and the duty staff will assist you.

Thanks,
Glen



From wlo@amsl.com  Thu Apr 26 13:47:52 2012
Return-Path: <wlo@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 A55CD11E80AD for <wgchairs@ietfa.amsl.com>; Thu, 26 Apr 2012 13:47:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[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 9pCrHDcyu45z for <wgchairs@ietfa.amsl.com>; Thu, 26 Apr 2012 13:47:52 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 0DA3111E80A3 for <wgchairs@ietf.org>; Thu, 26 Apr 2012 13:47:52 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 9B76F12CA4A; Thu, 26 Apr 2012 13:47:51 -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 pE41fxigoD6F; Thu, 26 Apr 2012 13:47:51 -0700 (PDT)
Received: from [12.22.58.170] (unknown [12.22.58.170]) by c8a.amsl.com (Postfix) with ESMTPSA id 79F5412BCA7; Thu, 26 Apr 2012 13:47:51 -0700 (PDT)
From: Wanda Lo <wlo@amsl.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-4-683785848
Subject: Request For IETF 83 WG and BOF Sessions Agenda, Minutes, and Presentations
Date: Thu, 26 Apr 2012 13:47:51 -0700
Message-Id: <E8D3B386-9DBB-49F5-A7A0-5CEBE5271808@amsl.com>
To: WG Chairs <wgchairs@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Cc: irsg@irtf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Apr 2012 20:47:52 -0000

--Apple-Mail-4-683785848
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 83 and we are =
still missing meeting minutes from various sessions. The cutoff for =
submissions is tomorrow Friday, April 27th, and correction submissions =
cutoff is May 16, 2012.  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 =
wlo@amsl.com for manual posting.

Groups I still need minutes from are:

Application Area
-appsawg/apparea
-core
-httpbis
-scim (bof)
-spfbis
-urnbis
-websec
-weirds

Internet Area
-ancp
-dnsext
-pcp
-trill

Operations and Management
-6renum
-armd
-grow
-opsarea/opsawg
-radext

Real-time Applications and Infrastructure Area
-avtext

Routing Area
-nvo3

Security
-jose
-kitten
-saag
-tls

Transport Area
-conex
-pcn
-rmt

IRTF
-mobopts


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


If you have any questions, please let me know.=20
=20
Thanks,
Wanda






=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D
Wanda Lo / Project Manager
Internet Engineering Task Force (IETF)
48377 Fremont Blvd., Ste. 117=20
Fremont, California 94538 / USA=20
T: +1.510.492.4082
F: +1.510.492.4001=20
www.ietf.org
=20
--
Managed by Association Management Solutions (AMS)
Forum Management, Meeting and Event Planning
www.amsl.com





--Apple-Mail-4-683785848
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-family: Courier; "><span style=3D"font-family: =
Arial, sans-serif; "><font class=3D"Apple-style-span">Dear WG Chairs and =
BOF Chairs,<o:p></o:p></font></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; =
font-family: Courier; "><span style=3D"font-family: Arial, sans-serif; =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; "><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 83 and we are still missing meeting =
minutes from various sessions. The cutoff for submissions is =
tomorrow&nbsp;</span><font class=3D"Apple-style-span" =
face=3D"Arial"><b>Friday, April 27th</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 May 16</span><font =
class=3D"Apple-style-span" face=3D"Arial">, 2012</font><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; color: blue; =
text-decoration: underline; ">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; color: blue; text-decoration: underline; =
">proceedings@ietf.org</a><font class=3D"Apple-style-span" =
style=3D"font-family: Arial, sans-serif; ">&nbsp;or&nbsp;</font><a =
href=3D"mailto:wlo@amsl.com" style=3D"font-family: Arial, sans-serif; =
color: blue; text-decoration: underline; ">wlo@amsl.com</a><font =
class=3D"Apple-style-span" style=3D"font-family: Arial, sans-serif; =
">&nbsp;for manual posting.<o:p></o:p></font></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-family: Courier; "><span style=3D"font-family: =
Arial, sans-serif; "><o:p><br></o:p></span></div><div style=3D"margin-top:=
 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; =
"><span class=3D"Apple-style-span" style=3D"font-family: Helvetica; =
">Groups I still need minutes from are:</span><div style=3D"font-family: =
Helvetica; "><br></div><div><b>Application Area</b></div><div =
style=3D"font-family: Helvetica; ">-appsawg/apparea</div><div =
style=3D"font-family: Helvetica; ">-core</div><div style=3D"font-family: =
Helvetica; ">-httpbis</div><div style=3D"font-family: Helvetica; ">-scim =
(bof)</div><div style=3D"font-family: Helvetica; ">-spfbis</div><div =
style=3D"font-family: Helvetica; ">-urnbis</div><div style=3D"font-family:=
 Helvetica; ">-websec</div><div style=3D"font-family: Helvetica; =
">-weirds</div><div style=3D"font-family: Helvetica; =
"><br></div><div><b>Internet Area</b></div><div style=3D"font-family: =
Helvetica; ">-ancp</div><div style=3D"font-family: Helvetica; =
">-dnsext</div><div style=3D"font-family: Helvetica; ">-pcp</div><div =
style=3D"font-family: Helvetica; ">-trill</div><div style=3D"font-family: =
Helvetica; "><br></div><div><b>Operations and Management</b></div><div =
style=3D"font-family: Helvetica; ">-6renum</div><div style=3D"font-family:=
 Helvetica; ">-armd</div><div style=3D"font-family: Helvetica; =
">-grow</div><div style=3D"font-family: Helvetica; =
">-opsarea/opsawg</div><div style=3D"font-family: Helvetica; =
">-radext</div><div style=3D"font-family: Helvetica; =
"><br></div><div><b>Real-time Applications and Infrastructure =
Area</b></div><div style=3D"font-family: Helvetica; ">-avtext</div><div =
style=3D"font-family: Helvetica; "><br></div><div><b>Routing =
Area</b></div><div style=3D"font-family: Helvetica; ">-nvo3</div><div =
style=3D"font-family: Helvetica; =
"><br></div><div><b>Security</b></div><div style=3D"font-family: =
Helvetica; ">-jose</div><div style=3D"font-family: Helvetica; =
">-kitten</div><div style=3D"font-family: Helvetica; ">-saag</div><div =
style=3D"font-family: Helvetica; ">-tls</div><div style=3D"font-family: =
Helvetica; "><br></div><div><b>Transport Area</b></div><div =
style=3D"font-family: Helvetica; ">-conex</div><div style=3D"font-family: =
Helvetica; ">-pcn</div><div style=3D"font-family: Helvetica; =
">-rmt</div><div style=3D"font-family: Helvetica; =
"><br></div><div><b>IRTF</b></div><div style=3D"font-family: Helvetica; =
">-mobopts</div><div style=3D"font-family: Helvetica; "><br></div><div =
style=3D"font-family: Helvetica; "><br></div><div><a =
href=3D"https://datatracker.ietf.org/meeting/83/materials.html">https://da=
tatracker.ietf.org/meeting/83/materials.html</a></div><div><br></div><div>=
<br></div>If you have any questions, please let me know.<font =
class=3D"Apple-style-span" face=3D"Arial, =
sans-serif">&nbsp;</font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; =
font-family: Courier; "><span style=3D"font-family: Arial, sans-serif; =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; =
font-family: Courier; "><span style=3D"font-family: Arial, sans-serif; =
">Thanks,<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; =
font-family: Courier; "><span style=3D"font-family: Arial, sans-serif; =
">Wanda</span></div><div><span style=3D"font-family: Arial, sans-serif; =
"><br></span></div><div>
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: Helvetica; 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-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: Helvetica; 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-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; 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-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: =
normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: =
0px; -webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; =
font-size: 12pt; font-family: 'Times New Roman'; "><font size=3D"2" =
face=3D"Arial"><span style=3D"font-size: 10pt; font-family: Arial; "><br =
class=3D"Apple-interchange-newline"><br></span></font></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; =
font-family: Arial; "><br></span></font></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; =
font-size: 12pt; font-family: 'Times New Roman'; "><font size=3D"2" =
face=3D"Arial"><span style=3D"font-size: 10pt; font-family: Arial; =
"><br></span></font></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; =
font-family: 'Times New Roman'; "><font size=3D"2" face=3D"Arial"><span =
style=3D"font-size: 10pt; font-family: Arial; =
"><br></span></font></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; =
font-family: 'Times New Roman'; "><font size=3D"2" face=3D"Arial"><span =
style=3D"font-size: 10pt; font-family: Arial; =
">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D</span></font><o:p></o:p></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman'; "><font size=3D"2" =
face=3D"Arial"><span style=3D"font-size: 10pt; font-family: Arial; =
">Wanda Lo / Project Manager</span></font><o:p></o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; =
font-family: Arial; ">Internet Engineering Task Force =
(IETF)</span></font><o:p></o:p></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman'; "><st1:address =
w:st=3D"on"><st1:street w:st=3D"on"><font size=3D"2" face=3D"Arial"><span =
style=3D"font-size: 10pt; font-family: Arial; ">48377 Fremont Blvd., =
Ste. 117</span></font></st1:street><font size=3D"2" face=3D"Arial"><span =
style=3D"font-size: 10pt; font-family: Arial; ">&nbsp;<br><st1:city =
w:st=3D"on">Fremont</st1:city>,&nbsp;<st1:state =
w:st=3D"on">California</st1:state>&nbsp;<st1:postalcode =
w:st=3D"on">94538</st1:postalcode></span></font></st1:address><font =
size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; font-family: =
Arial; ">&nbsp;/&nbsp;<st1:country-region w:st=3D"on"><st1:place =
w:st=3D"on">USA</st1:place></st1:country-region>&nbsp;<br>T: =
+1.510.492.4082<br>F: +1.510.492.4001&nbsp;<br><u><font =
color=3D"blue"><span =
title=3D"blocked::blocked::http://www.ipsphereforum.org/ =
blocked::http://www.ipsphereforum.org/"><span style=3D"color: blue; "><a =
href=3D"http://www.ietf.org/" style=3D"color: blue; text-decoration: =
underline; =
">www.ietf.org</a></span></span></font></u></span></font><o:p></o:p></div>=
<div style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: =
0.0001pt; margin-left: 0in; font-size: 12pt; font-family: 'Times New =
Roman'; "><font size=3D"3" face=3D"Times New Roman"><span =
style=3D"font-size: 12pt; ">&nbsp;<o:p></o:p></span></font></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman'; =
"><i><font size=3D"1" face=3D"Verdana"><span style=3D"font-size: 7.5pt; =
font-family: Verdana; font-style: italic; "><span =
title=3D"blocked::blocked::http://www.ipsphereforum.org/ =
blocked::http://www.ipsphereforum.org/">--</span></span></font></i><i><fon=
t size=3D"1" face=3D"Arial"><span style=3D"font-size: 7.5pt; =
font-family: Arial; font-style: italic; =
"><o:p></o:p></span></font></i></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman'; "><font size=3D"1" =
face=3D"Arial"><span style=3D"font-size: 7.5pt; font-family: Arial; =
">Managed by Association Management Solutions =
(AMS)<o:p></o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman'; "><font size=3D"1" =
face=3D"Arial"><span style=3D"font-size: 7.5pt; font-family: Arial; =
">Forum Management, Meeting and Event =
Planning<o:p></o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman'; "><font size=3D"1" =
face=3D"Verdana"><span style=3D"font-size: 7.5pt; font-family: Verdana; =
"><a href=3D"http://www.amsl.com/" style=3D"color: blue; =
text-decoration: underline; "><font color=3D"purple" face=3D"Arial"><span =
style=3D"font-family: Arial; color: purple; =
">www.amsl.com</span></font></a></span></font></div></div></div><div><br><=
/div></div></span><br class=3D"Apple-interchange-newline"></span><br =
class=3D"Apple-interchange-newline"></div></span></div></span></span>
</div>
<br></body></html>=

--Apple-Mail-4-683785848--

From presnick@qualcomm.com  Mon Apr 30 09:12:32 2012
Return-Path: <presnick@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 9255221F8716 for <wgchairs@ietfa.amsl.com>; Mon, 30 Apr 2012 09:12:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.554
X-Spam-Level: 
X-Spam-Status: No, score=-106.554 tagged_above=-999 required=5 tests=[AWL=0.044, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pnMJC5LDL6BE for <wgchairs@ietfa.amsl.com>; Mon, 30 Apr 2012 09:12:30 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 91E9221F8630 for <wgchairs@ietf.org>; Mon, 30 Apr 2012 09:12:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=presnick@qualcomm.com; q=dns/txt; s=qcdkim; t=1335802350; x=1367338350; h=message-id:date:from:user-agent:mime-version:to:subject: content-type:x-originating-ip; bh=Pm+YwXjJ7H4ekFv5uwBB6D0Qj43myuQ7UbaEMlZ9Kig=; b=QlhwAS4WZGGP81ymI3x9Ngwvjy8E1QtU7SolBghNYMVdEfi9BZVrm8uE 3Y6QC2XHwjhVay6lqfoiaRMTkB2LNit8IBknxQvI2Xfq3ueDTm2uU179c QMnpLJBUDHKE11S0dfwJix1xJTqWVHImUiRGNLhwFQToqe1GvDeSsMuep Q=;
X-IronPort-AV: E=McAfee;i="5400,1158,6696"; a="183954675"
Received: from ironmsg02-l.qualcomm.com ([172.30.48.16]) by wolverine02.qualcomm.com with ESMTP; 30 Apr 2012 09:12:30 -0700
X-IronPort-AV: E=Sophos;i="4.75,504,1330934400";  d="scan'208,217";a="120660617"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by ironmsg02-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 30 Apr 2012 09:12:29 -0700
Received: from Macintosh-4.local (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.2.283.3; Mon, 30 Apr 2012 09:12:28 -0700
Message-ID: <4F9EB9E0.9010104@qualcomm.com>
Date: Mon, 30 Apr 2012 09:12:16 -0700
From: Pete Resnick <presnick@qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: 'WG Chairs' <wgchairs@ietf.org>
Subject: Fwd: IPR disclosure question
Content-Type: multipart/alternative; boundary="------------090400020108080505060602"
X-Originating-IP: [172.30.39.5]
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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, 30 Apr 2012 16:12:32 -0000

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

Hi all,

I think we made this clear in the run-up to the new shepherding 
template, but I just got a question about it from a participant, so I 
thought I'd forward my answer to all of you just in case:

-------- Original Message --------
Date: 	Mon, 30 Apr 2012 09:04:50 -0700
From: 	Pete Resnick <presnick@qualcomm.com>


[The person asked]

> [...] how to reply to a Chair when non-necessary IPR exists. I was 
> asked again how to answer the question of "Do you have any IPR?" when 
> you have an IPR which will not be necessarily infringed [...]

You can find the list of questions that a document shepherd (sometimes 
the chair, but sometimes a person assigned by the chair) is supposed to 
answer for the IESG: 
<http://www.ietf.org/iesg/template/doc-writeup.html> In there, it says:

"(7) Has each author confirmed that any and all appropriate IPR
disclosures required for full conformance with the provisions of BCP 78
and BCP 79 have already been filed."

When it says "any and all appropriate IPR disclosures required for full 
conformance with the provisions of BCP 78 and 79", according to BCP 79 
that means any IPR that "Covers or may ultimately Cover" the document, 
where "Covers" is defined as:

       ...a valid claim of a patent or a
       patent application in any jurisdiction or a protected claim, or
       any other Intellectual Property Right, would necessarily be
       infringed by the exercise of a right (e.g., making, using,
       selling, importing, distribution, copying, etc.) with respect to
       an Implementing Technology.

So I think you are only required to declare IPR that would necessarily 
be infringed by the implementation of the document.

If a chair or document shepherd asks the question in an imprecise way, 
the participant should mention the above discussion to the chair and 
perhaps the AD, but simply answering, "I have disclosed all appropriate 
IPR as per BCP 78 and 79" is good enough. I agree that trying to answer 
the question "Do you have any IPR related to this document?" is 
problematic and we should remind chairs and shepherds that all we are 
asking for is disclosures that need to be made under BCP 78 and 79.

I hope that helps.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html; charset=ISO-8859-1"
 http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi all,<br>
<br>
I think we made this clear in the run-up to the new shepherding
template, but I just got a question about it from a participant, so I
thought I'd forward my answer to all of you just in case:<br>
<br>
-------- Original Message --------
<table class="moz-email-headers-table" border="0" cellpadding="0"
 cellspacing="0">
  <tbody>
    <tr>
      <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date: </th>
      <td>Mon, 30 Apr 2012 09:04:50 -0700</td>
    </tr>
    <tr>
      <th align="RIGHT" nowrap="nowrap" valign="BASELINE">From: </th>
      <td>Pete Resnick <a class="moz-txt-link-rfc2396E" href="mailto:presnick@qualcomm.com">&lt;presnick@qualcomm.com&gt;</a></td>
    </tr>
  </tbody>
</table>
<br>
[The person asked]<br>
<br>
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
<span
 style="font-size: 12pt; font-family: Consolas; color: rgb(31, 73, 125);">
<blockquote type="cite"><span
 style="font-size: 12pt; font-family: Consolas; color: rgb(31, 73, 125);">[...]
how to reply to a Chair when non-necessary IPR exists. I was asked
again how to answer the question
of &#8220;Do you have any IPR?&#8221; when you have an IPR which will not be
necessarily infringed [...]</span></blockquote>
</span>
<blockquote
 cite="mid:45A6AB3BE14CA04FAAE8CCDE6CAB6BB120F2A40A@szxeml521-mbs.china.huawei.com"
 type="cite">
  <div class="WordSection1"> </div>
</blockquote>
<br>
You can find the list of questions that a document shepherd (sometimes
the chair, but sometimes a person assigned by the chair) is supposed to
answer for the IESG:
<a moz-do-not-send="true" class="moz-txt-link-rfc2396E"
 href="http://www.ietf.org/iesg/template/doc-writeup.html">&lt;http://www.ietf.org/iesg/template/doc-writeup.html&gt;</a>
In there, it
says:<br>
<br>
"(7) Has each author confirmed that any and all appropriate IPR<br>
disclosures required for full conformance with the provisions of BCP 78<br>
and BCP 79 have already been filed."<br>
<br>
When it says "any and all appropriate IPR disclosures required for full
conformance with the provisions of BCP 78 and 79", according to BCP 79
that means any IPR that "Covers or may ultimately Cover" the document,
where "Covers" is defined as:<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ...a valid claim of a patent or a<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; patent application in any jurisdiction or a protected claim, or<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; any other Intellectual Property Right, would necessarily be<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; infringed by the exercise of a right (e.g., making, using,<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; selling, importing, distribution, copying, etc.) with respect to<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; an Implementing Technology.<br>
<br>
So I think you are only required to declare IPR that would necessarily
be infringed by the implementation of the document.<br>
<br>
If a chair or document shepherd asks the question in an imprecise way,
the participant should mention the above discussion to the chair and
perhaps the AD, but simply answering, "I have disclosed all appropriate
IPR as per BCP 78 and 79" is good enough. I agree that trying to answer
the question "Do you have any IPR related to this document?" is
problematic and we should remind chairs and shepherds that all we are
asking for is disclosures that need to be made under BCP 78 and 79.<br>
<br>
I hope that helps.<br>
<br>
pr<br>
<pre class="moz-signature" cols="72">-- 
Pete Resnick <a moz-do-not-send="true" class="moz-txt-link-rfc2396E"
 href="http://www.qualcomm.com/%7Epresnick/">&lt;http://www.qualcomm.com/~presnick/&gt;</a>
Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102</pre>
</body>
</html>

--------------090400020108080505060602--

From dcrocker@bbiw.net  Mon Apr 30 09:23:05 2012
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 0F2C821F8777 for <wgchairs@ietfa.amsl.com>; Mon, 30 Apr 2012 09:23:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.332
X-Spam-Level: 
X-Spam-Status: No, score=-6.332 tagged_above=-999 required=5 tests=[AWL=0.267,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FXpPuShuIrIo for <wgchairs@ietfa.amsl.com>; Mon, 30 Apr 2012 09:23:04 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 3D69321F8786 for <wgchairs@ietf.org>; Mon, 30 Apr 2012 09:23:02 -0700 (PDT)
Received: from [192.168.1.11] (adsl-67-127-58-62.dsl.pltn13.pacbell.net [67.127.58.62]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q3UGMwNs011238 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <wgchairs@ietf.org>; Mon, 30 Apr 2012 09:22:59 -0700
Message-ID: <4F9EBC62.2010600@bbiw.net>
Date: Mon, 30 Apr 2012 09:22:58 -0700
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120420 Thunderbird/12.0
MIME-Version: 1.0
To: "'WG Chairs'" <wgchairs@ietf.org>
Subject: Re: Fwd: IPR disclosure question
References: <4F9EB9E0.9010104@qualcomm.com>
In-Reply-To: <4F9EB9E0.9010104@qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Mon, 30 Apr 2012 09:22:59 -0700 (PDT)
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Apr 2012 16:23:05 -0000

On 4/30/2012 9:12 AM, Pete Resnick wrote:
> When it says "any and all appropriate IPR disclosures required for full
> conformance with the provisions of BCP 78 and 79", according to BCP 79
> that means any IPR that "Covers or may ultimately Cover" the document,
> where "Covers" is defined as:
...
>        ...with respect to
>        an Implementing Technology.
>
> So I think you are only required to declare IPR that would necessarily
> be infringed by the implementation of the document.


There is an unfortunate ambiguity or potentially larger scope in the 
wording "implementation".  It has two different technical meanings. One 
is for development and the other is for operations.

One is the instantiation of the technology, such as by software 
programming.  The other is deployment of the technology, as in 
operational use.  They really are distinct meanings in our profession.

Indeed it is possible to have a patent that is not infringed on by the 
creation of the software, but is instead infringed on by the /use/ of 
the software.

We should clarify exactly what scope the IPR declaration requirements 
cover and we should modify the existing language to avoid the potential 
for misunderstanding.

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From stpeter@stpeter.im  Mon Apr 30 09:26:35 2012
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 AA66721F871A for <wgchairs@ietfa.amsl.com>; Mon, 30 Apr 2012 09:26:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V2oNQMZXPDV8 for <wgchairs@ietfa.amsl.com>; Mon, 30 Apr 2012 09:26:33 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id A732F21F8690 for <wgchairs@ietf.org>; Mon, 30 Apr 2012 09:26:33 -0700 (PDT)
Received: from [107.16.139.250] (unknown [209.116.57.2]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 4B99140058; Mon, 30 Apr 2012 10:41:25 -0600 (MDT)
Message-ID: <4F9EBD39.5010605@stpeter.im>
Date: Mon, 30 Apr 2012 09:26:33 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Dave Crocker <dcrocker@bbiw.net>
Subject: Re: Fwd: IPR disclosure question
References: <4F9EB9E0.9010104@qualcomm.com> <4F9EBC62.2010600@bbiw.net>
In-Reply-To: <4F9EBC62.2010600@bbiw.net>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=UTF-8
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, 30 Apr 2012 16:26:35 -0000

On 4/30/12 9:22 AM, Dave Crocker wrote:
> 
> 
> On 4/30/2012 9:12 AM, Pete Resnick wrote:
>> When it says "any and all appropriate IPR disclosures required for full
>> conformance with the provisions of BCP 78 and 79", according to BCP 79
>> that means any IPR that "Covers or may ultimately Cover" the document,
>> where "Covers" is defined as:
> ...
>>        ...with respect to
>>        an Implementing Technology.
>>
>> So I think you are only required to declare IPR that would necessarily
>> be infringed by the implementation of the document.
> 
> 
> There is an unfortunate ambiguity or potentially larger scope in the
> wording "implementation".  It has two different technical meanings. One
> is for development and the other is for operations.
> 
> One is the instantiation of the technology, such as by software
> programming.  The other is deployment of the technology, as in
> operational use.  They really are distinct meanings in our profession.

FWIW, I always use "implementation" for the first and "deployment" for
the second...

Peter

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



From dcrocker@bbiw.net  Mon Apr 30 09:33:04 2012
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 587F421F873C for <wgchairs@ietfa.amsl.com>; Mon, 30 Apr 2012 09:33:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.349
X-Spam-Level: 
X-Spam-Status: No, score=-6.349 tagged_above=-999 required=5 tests=[AWL=0.250,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N88kZPjM4upN for <wgchairs@ietfa.amsl.com>; Mon, 30 Apr 2012 09:33:04 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id E90E821F8714 for <wgchairs@ietf.org>; Mon, 30 Apr 2012 09:33:03 -0700 (PDT)
Received: from [192.168.1.11] (adsl-67-127-58-62.dsl.pltn13.pacbell.net [67.127.58.62]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q3UGX3q1011482 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 30 Apr 2012 09:33:03 -0700
Message-ID: <4F9EBEBE.4030604@bbiw.net>
Date: Mon, 30 Apr 2012 09:33:02 -0700
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120420 Thunderbird/12.0
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: Fwd: IPR disclosure question
References: <4F9EB9E0.9010104@qualcomm.com> <4F9EBC62.2010600@bbiw.net> <4F9EBD39.5010605@stpeter.im>
In-Reply-To: <4F9EBD39.5010605@stpeter.im>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Mon, 30 Apr 2012 09:33:03 -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: Mon, 30 Apr 2012 16:33:04 -0000

On 4/30/2012 9:26 AM, Peter Saint-Andre wrote:
>> One is the instantiation of the technology, such as by software
>> programming.  The other is deployment of the technology, as in
>> operational use.  They really are distinct meanings in our profession.
>
> FWIW, I always use "implementation" for the first and "deployment" for
> the second...


Me too, but neither of us is primarily an operations person.   In the 
world of operations, implementation is used to mean deployment...

At this point, I try to say "develop" and "deploy" since they seem to be 
unambiguous both to the development and the operations community.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From jmh@joelhalpern.com  Mon Apr 30 09:41:20 2012
Return-Path: <jmh@joelhalpern.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 D7F1421F8789 for <wgchairs@ietfa.amsl.com>; Mon, 30 Apr 2012 09:41:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.357
X-Spam-Level: 
X-Spam-Status: No, score=-102.357 tagged_above=-999 required=5 tests=[AWL=-0.092, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bl+HFzAkORof for <wgchairs@ietfa.amsl.com>; Mon, 30 Apr 2012 09:41:20 -0700 (PDT)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 6697321F8782 for <wgchairs@ietf.org>; Mon, 30 Apr 2012 09:41:20 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by morbo.tigertech.net (Postfix) with ESMTP id EA7445580F0 for <wgchairs@ietf.org>; Mon, 30 Apr 2012 09:41:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 9538E1C08BD; Mon, 30 Apr 2012 09:41:11 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [10.10.10.100] (pool-71-161-51-182.clppva.btas.verizon.net [71.161.51.182]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id B65051C075B; Mon, 30 Apr 2012 09:41:10 -0700 (PDT)
Message-ID: <4F9EC0DF.3050405@joelhalpern.com>
Date: Mon, 30 Apr 2012 12:42:07 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20120420 Thunderbird/12.0
MIME-Version: 1.0
To: Dave Crocker <dcrocker@bbiw.net>
Subject: Re: Fwd: IPR disclosure question
References: <4F9EB9E0.9010104@qualcomm.com> <4F9EBC62.2010600@bbiw.net> <4F9EBD39.5010605@stpeter.im> <4F9EBEBE.4030604@bbiw.net>
In-Reply-To: <4F9EBEBE.4030604@bbiw.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 'WG Chairs' <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Apr 2012 16:41:21 -0000

I would also note that "necessary" is fuzzy.
I have seen lawyers argue that the other sides patent is "necessary" 
precisely so they could then say "and not disclosed, you violated the 
rules..."

Yours,
Joel

On 4/30/2012 12:33 PM, Dave Crocker wrote:
>
>
> On 4/30/2012 9:26 AM, Peter Saint-Andre wrote:
>>> One is the instantiation of the technology, such as by software
>>> programming. The other is deployment of the technology, as in
>>> operational use. They really are distinct meanings in our profession.
>>
>> FWIW, I always use "implementation" for the first and "deployment" for
>> the second...
>
>
> Me too, but neither of us is primarily an operations person. In the
> world of operations, implementation is used to mean deployment...
>
> At this point, I try to say "develop" and "deploy" since they seem to be
> unambiguous both to the development and the operations community.
>
> d/
>

From barryleiba.mailing.lists@gmail.com  Mon Apr 30 09:50:58 2012
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 2405F21F84B9 for <wgchairs@ietfa.amsl.com>; Mon, 30 Apr 2012 09:50:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.965
X-Spam-Level: 
X-Spam-Status: No, score=-102.965 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zcc0m2K8yZFK for <wgchairs@ietfa.amsl.com>; Mon, 30 Apr 2012 09:50:57 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id ECA4321F846B for <wgchairs@ietf.org>; Mon, 30 Apr 2012 09:50:56 -0700 (PDT)
Received: by eaaq11 with SMTP id q11so758132eaa.31 for <wgchairs@ietf.org>; Mon, 30 Apr 2012 09:50:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=8Cb8PFqqq59AxRpQbEkGCbfXK2jnNZGph3u68lwAmZI=; b=lnwr9LvAk3Q42IDEVQBM4PE90gX3lAtCfCs1KBxw+VZsEfXPYfSlpG9/Ql0B1t1sEN lu00c+Bbr8HA3ioIWmycb7N1+i8Wj2HGW6CiiF8siG8bw+74r4orTI7EIYUvwMZWI+0F FoVoaNOBivdvUWkDzldlUWyLC1DI4OVdArPUpwY2coiXJeZclScAi/kHYJ6ctUGF4gIy DpFHT1Vcxunk5F4R65b+1/xK473wzVADnTiTiQ3LJmuE6HepOCVo/imoQfsuYb6i3HMX HLZpeTkXG03C6Fau4G/Md9C/bXVU+4pZzb3lW0pwmf423gsMMMy/YcDRQMLhSlu6VvSV 0crQ==
MIME-Version: 1.0
Received: by 10.213.2.198 with SMTP id 6mr1538616ebk.161.1335804656004; Mon, 30 Apr 2012 09:50:56 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.14.225.2 with HTTP; Mon, 30 Apr 2012 09:50:55 -0700 (PDT)
In-Reply-To: <4F9EC0DF.3050405@joelhalpern.com>
References: <4F9EB9E0.9010104@qualcomm.com> <4F9EBC62.2010600@bbiw.net> <4F9EBD39.5010605@stpeter.im> <4F9EBEBE.4030604@bbiw.net> <4F9EC0DF.3050405@joelhalpern.com>
Date: Mon, 30 Apr 2012 12:50:55 -0400
X-Google-Sender-Auth: HQtf4gUEOWGKF2QThfWyLDkR9ZM
Message-ID: <CAC4RtVCRNtq2WZ9YsHNj9thWN4f=Gj7Kon28KVe9uk35nUk8cg@mail.gmail.com>
Subject: Re: Fwd: IPR disclosure question
From: Barry Leiba <barryleiba@computer.org>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Apr 2012 16:50:58 -0000

> I would also note that "necessary" is fuzzy.

The IETF counsel can obviously speak for himself, but the outcome of
my conversations with him have led me to understand that the phrase
requires disclosure only when the document in question cannot be
implemented without infringing.

Thus, if a patent is about doing X, and the document provides the
option of doing X or Y, the "necessarily" condition is NOT met.

Barry

From dthaler@microsoft.com  Mon Apr 30 09:55:09 2012
Return-Path: <dthaler@microsoft.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 3027621F87BE for <wgchairs@ietfa.amsl.com>; Mon, 30 Apr 2012 09:55:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.323
X-Spam-Level: 
X-Spam-Status: No, score=-105.323 tagged_above=-999 required=5 tests=[AWL=1.276, 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 FJHNG1say4cm for <wgchairs@ietfa.amsl.com>; Mon, 30 Apr 2012 09:55:08 -0700 (PDT)
Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe002.messaging.microsoft.com [65.55.88.12]) by ietfa.amsl.com (Postfix) with ESMTP id 1826421F87B2 for <wgchairs@ietf.org>; Mon, 30 Apr 2012 09:55:07 -0700 (PDT)
Received: from mail72-tx2-R.bigfish.com (10.9.14.249) by TX2EHSOBE009.bigfish.com (10.9.40.29) with Microsoft SMTP Server id 14.1.225.23; Mon, 30 Apr 2012 16:55:02 +0000
Received: from mail72-tx2 (localhost [127.0.0.1])	by mail72-tx2-R.bigfish.com (Postfix) with ESMTP id 978E31E035D; Mon, 30 Apr 2012 16:55:01 +0000 (UTC)
X-SpamScore: -33
X-BigFish: VS-33(zf7Iz9371I542M1432Nzz1202hzz1033IL8275dhz2fh2a8h668h839h944hd25h)
X-Forefront-Antispam-Report: CIP:131.107.125.8; KIP:(null); UIP:(null); IPV:NLI; H:TK5EX14HUBC104.redmond.corp.microsoft.com; RD:none; EFVD:NLI
Received-SPF: pass (mail72-tx2: domain of microsoft.com designates 131.107.125.8 as permitted sender) client-ip=131.107.125.8; envelope-from=dthaler@microsoft.com; helo=TK5EX14HUBC104.redmond.corp.microsoft.com ; icrosoft.com ; 
Received: from mail72-tx2 (localhost.localdomain [127.0.0.1]) by mail72-tx2 (MessageSwitch) id 133580489274214_4830; Mon, 30 Apr 2012 16:54:52 +0000 (UTC)
Received: from TX2EHSMHS021.bigfish.com (unknown [10.9.14.242])	by mail72-tx2.bigfish.com (Postfix) with ESMTP id 0A66D20066F; Mon, 30 Apr 2012 16:54:52 +0000 (UTC)
Received: from TK5EX14HUBC104.redmond.corp.microsoft.com (131.107.125.8) by TX2EHSMHS021.bigfish.com (10.9.99.121) with Microsoft SMTP Server (TLS) id 14.1.225.23; Mon, 30 Apr 2012 16:54:51 +0000
Received: from TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) by TK5EX14HUBC104.redmond.corp.microsoft.com (157.54.80.25) with Microsoft SMTP Server (TLS) id 14.2.298.5; Mon, 30 Apr 2012 16:54:44 +0000
Received: from TK5EX14MBXW605.wingroup.windeploy.ntdev.microsoft.com ([169.254.5.160]) by TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.68]) with mapi id 14.02.0298.005; Mon, 30 Apr 2012 09:54:43 -0700
From: Dave Thaler <dthaler@microsoft.com>
To: Barry Leiba <barryleiba@computer.org>, "Joel M. Halpern" <jmh@joelhalpern.com>
Subject: RE: Fwd: IPR disclosure question
Thread-Topic: Fwd: IPR disclosure question
Thread-Index: AQHNJuwRM0+ujyFGAUipIePcQuCN4Za0AoIAgAABAYCAAAHPAIAAAoqAgAACdoD//4s2gA==
Date: Mon, 30 Apr 2012 16:54:42 +0000
Message-ID: <9B57C850BB53634CACEC56EF4853FF653B5A060F@TK5EX14MBXW605.wingroup.windeploy.ntdev.microsoft.com>
References: <4F9EB9E0.9010104@qualcomm.com> <4F9EBC62.2010600@bbiw.net> <4F9EBD39.5010605@stpeter.im> <4F9EBEBE.4030604@bbiw.net> <4F9EC0DF.3050405@joelhalpern.com> <CAC4RtVCRNtq2WZ9YsHNj9thWN4f=Gj7Kon28KVe9uk35nUk8cg@mail.gmail.com>
In-Reply-To: <CAC4RtVCRNtq2WZ9YsHNj9thWN4f=Gj7Kon28KVe9uk35nUk8cg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.41]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
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, 30 Apr 2012 16:55:09 -0000

> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
> Behalf Of Barry Leiba
> Sent: Monday, April 30, 2012 9:51 AM
> To: Joel M. Halpern
> Cc: WG Chairs
> Subject: Re: Fwd: IPR disclosure question
>=20
> > I would also note that "necessary" is fuzzy.
>=20
> The IETF counsel can obviously speak for himself, but the outcome of my
> conversations with him have led me to understand that the phrase requires
> disclosure only when the document in question cannot be implemented
> without infringing.
>=20
> Thus, if a patent is about doing X, and the document provides the option =
of
> doing X or Y, the "necessarily" condition is NOT met.
>=20
> Barry

"Cannot be implemented" is not boolean.   There are often many SHOULDs
and MAYs that are not mandatory-to-implement, but for which some patent
may be relevant.

-Dave


From jmh@joelhalpern.com  Mon Apr 30 10:00:07 2012
Return-Path: <jmh@joelhalpern.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 3C3A121F87E2 for <wgchairs@ietfa.amsl.com>; Mon, 30 Apr 2012 10:00:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.353
X-Spam-Level: 
X-Spam-Status: No, score=-102.353 tagged_above=-999 required=5 tests=[AWL=-0.088, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mnNV+ECdtmHu for <wgchairs@ietfa.amsl.com>; Mon, 30 Apr 2012 10:00:06 -0700 (PDT)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id CF65621F87E0 for <wgchairs@ietf.org>; Mon, 30 Apr 2012 10:00:06 -0700 (PDT)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by morbo.tigertech.net (Postfix) with ESMTP id C5163557F3C for <wgchairs@ietf.org>; Mon, 30 Apr 2012 10:00:06 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id F132D1E01CB; Mon, 30 Apr 2012 10:00:05 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [10.10.10.100] (pool-71-161-51-182.clppva.btas.verizon.net [71.161.51.182]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 20B281E01C8; Mon, 30 Apr 2012 10:00:04 -0700 (PDT)
Message-ID: <4F9EC519.1050304@joelhalpern.com>
Date: Mon, 30 Apr 2012 13:00:09 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20120420 Thunderbird/12.0
MIME-Version: 1.0
To: Dave Thaler <dthaler@microsoft.com>
Subject: Re: Fwd: IPR disclosure question
References: <4F9EB9E0.9010104@qualcomm.com> <4F9EBC62.2010600@bbiw.net> <4F9EBD39.5010605@stpeter.im> <4F9EBEBE.4030604@bbiw.net> <4F9EC0DF.3050405@joelhalpern.com> <CAC4RtVCRNtq2WZ9YsHNj9thWN4f=Gj7Kon28KVe9uk35nUk8cg@mail.gmail.com> <9B57C850BB53634CACEC56EF4853FF653B5A060F@TK5EX14MBXW605.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <9B57C850BB53634CACEC56EF4853FF653B5A060F@TK5EX14MBXW605.wingroup.windeploy.ntdev.microsoft.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: WG Chairs <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: Mon, 30 Apr 2012 17:00:07 -0000

There are some clear cases, but if you have not watched the lawyers play 
these games you would be amazed how muddied they can make it.  I think 
that in terms of "rules" things are written right.  It is just that 
folks trying to decide whether to disclose should be aware that reality 
is often much messier than theory.
Just my personal take, from working with these folks in past lives.

Yours,
Joel

On 4/30/2012 12:54 PM, Dave Thaler wrote:
>> -----Original Message-----
>> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
>> Behalf Of Barry Leiba
>> Sent: Monday, April 30, 2012 9:51 AM
>> To: Joel M. Halpern
>> Cc: WG Chairs
>> Subject: Re: Fwd: IPR disclosure question
>>
>>> I would also note that "necessary" is fuzzy.
>>
>> The IETF counsel can obviously speak for himself, but the outcome of my
>> conversations with him have led me to understand that the phrase requires
>> disclosure only when the document in question cannot be implemented
>> without infringing.
>>
>> Thus, if a patent is about doing X, and the document provides the option of
>> doing X or Y, the "necessarily" condition is NOT met.
>>
>> Barry
>
> "Cannot be implemented" is not boolean.   There are often many SHOULDs
> and MAYs that are not mandatory-to-implement, but for which some patent
> may be relevant.
>
> -Dave
>
>

From paul.hoffman@vpnc.org  Mon Apr 30 10:35:50 2012
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B24F821F8855 for <wgchairs@ietfa.amsl.com>; Mon, 30 Apr 2012 10:35:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.539
X-Spam-Level: 
X-Spam-Status: No, score=-102.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QoY01QpY8QVV for <wgchairs@ietfa.amsl.com>; Mon, 30 Apr 2012 10:35:50 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 43CD921F8848 for <wgchairs@ietf.org>; Mon, 30 Apr 2012 10:35:50 -0700 (PDT)
Received: from [10.20.30.102] (50-0-66-4.dsl.dynamic.fusionbroadband.com [50.0.66.4]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.3) with ESMTP id q3UHZn02013140 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <wgchairs@ietf.org>; Mon, 30 Apr 2012 10:35:49 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1257)
Subject: Re: IPR disclosure question
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <4F9EC0DF.3050405@joelhalpern.com>
Date: Mon, 30 Apr 2012 10:35:49 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <F3DCE00D-9E68-4ACD-ABF5-ABABF1361FDC@vpnc.org>
References: <4F9EB9E0.9010104@qualcomm.com> <4F9EBC62.2010600@bbiw.net> <4F9EBD39.5010605@stpeter.im> <4F9EBEBE.4030604@bbiw.net> <4F9EC0DF.3050405@joelhalpern.com>
To: WG Chairs <wgchairs@ietf.org>
X-Mailer: Apple Mail (2.1257)
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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, 30 Apr 2012 17:35:50 -0000

On Apr 30, 2012, at 9:42 AM, Joel M. Halpern wrote:

> I would also note that "necessary" is fuzzy.

+l/Like

Having said that, it's the best we can do and the WG chair can in good =
faith say "I guessed as best I can".

--Paul Hoffman


From presnick@qualcomm.com  Mon Apr 30 10:48:07 2012
Return-Path: <presnick@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 D3C0F21F8879 for <wgchairs@ietfa.amsl.com>; Mon, 30 Apr 2012 10:48:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.555
X-Spam-Level: 
X-Spam-Status: No, score=-106.555 tagged_above=-999 required=5 tests=[AWL=0.044, 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 4T0yWRVC+uS0 for <wgchairs@ietfa.amsl.com>; Mon, 30 Apr 2012 10:48:07 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id 4C9C821F888C for <wgchairs@ietf.org>; Mon, 30 Apr 2012 10:48:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=presnick@qualcomm.com; q=dns/txt; s=qcdkim; t=1335808085; x=1367344085; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: content-transfer-encoding:x-originating-ip; bh=q9O0WGDDJNH687LeDmBYV5Ej1s3YeUxiywizlnDcX20=; b=bK8QmV2k5GNEoyAT/xSfF31SLKmwnHGLnCvLdKa2YNw/CAPm0d7WCC03 t2T49JReRhflnZgFGHul5V/+/GMdzxy6V0DacON+Nznvr+B5lBq4O6ajD 00ruduLwOUhPILp+bwSDrJCckr8lcSbI2+Ej7s1YJDyqvqbpmbMsnvR5H c=;
X-IronPort-AV: E=McAfee;i="5400,1158,6697"; a="186252009"
Received: from ironmsg02-l.qualcomm.com ([172.30.48.16]) by wolverine01.qualcomm.com with ESMTP; 30 Apr 2012 10:48:04 -0700
X-IronPort-AV: E=Sophos;i="4.75,504,1330934400"; d="scan'208";a="120662513"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by ironmsg02-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 30 Apr 2012 10:48:04 -0700
Received: from Macintosh-4.local (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.2.283.3; Mon, 30 Apr 2012 10:48:04 -0700
Message-ID: <4F9ED050.9000403@qualcomm.com>
Date: Mon, 30 Apr 2012 10:48:00 -0700
From: Pete Resnick <presnick@qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: IPR disclosure question
References: <4F9EB9E0.9010104@qualcomm.com> <4F9EBC62.2010600@bbiw.net>	<4F9EBD39.5010605@stpeter.im> <4F9EBEBE.4030604@bbiw.net>	<4F9EC0DF.3050405@joelhalpern.com> <F3DCE00D-9E68-4ACD-ABF5-ABABF1361FDC@vpnc.org>
In-Reply-To: <F3DCE00D-9E68-4ACD-ABF5-ABABF1361FDC@vpnc.org>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
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, 30 Apr 2012 17:48:08 -0000

On 4/30/12 10:35 AM, Paul Hoffman wrote:
> On Apr 30, 2012, at 9:42 AM, Joel M. Halpern wrote:
>
>    
>> I would also note that "necessary" is fuzzy.
>>      
> +l/Like
>
> Having said that, it's the best we can do and the WG chair can in good faith say "I guessed as best I can".
>    

Just to be clear, the chair does not have to do any guessing here, in 
that the chair never has to do any of the calculation of whether 
something is "necessarily infringing". That's up to the person who has 
or knows about the IPR. And though it's annoying to us IETFers if that 
person doesn't disclose because they guessed wrong, it's the person who 
has the IPR who gets into legal hot water if they guess wrong and don't 
disclose. Chairs only have to ask, "Did you do everything that 3979 says 
you need to do?" Then the chair can in good faith say, "I asked; they 
said 'Yup.'"

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102

