
From lars@netapp.com  Wed Feb  8 10:25:01 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 D51D621E8010 for <wgchairs@ietfa.amsl.com>; Wed,  8 Feb 2012 10:25:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.212
X-Spam-Level: 
X-Spam-Status: No, score=-9.212 tagged_above=-999 required=5 tests=[AWL=-0.940, BAYES_00=-2.599, HTML_IMAGE_ONLY_16=1.526, HTML_IMAGE_RATIO_08=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yihuexATbo-R for <wgchairs@ietfa.amsl.com>; Wed,  8 Feb 2012 10:25:01 -0800 (PST)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by ietfa.amsl.com (Postfix) with ESMTP id 1BF5321F85C0 for <wgchairs@ietf.org>; Wed,  8 Feb 2012 10:25:01 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.73,384,1325491200";  d="p7s'?png'150?scan'150,208,217,150";a="623688229"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx2-out.netapp.com with ESMTP; 08 Feb 2012 10:25:00 -0800
Received: from sacrsexc1-prd.hq.netapp.com (sacrsexc1-prd.hq.netapp.com [10.99.115.27]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id q18IP0Nr017617; Wed, 8 Feb 2012 10:25:00 -0800 (PST)
Received: from VMWEXCEHT01-PRD.hq.netapp.com ([10.106.76.239]) by sacrsexc1-prd.hq.netapp.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 8 Feb 2012 10:24:56 -0800
Received: from SACEXCMBX04-PRD.hq.netapp.com ([169.254.6.193]) by vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) with mapi id 14.01.0355.002; Wed, 8 Feb 2012 10:24:28 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: "wgchairs@ietf.org" <wgchairs@ietf.org>, Internet Research Steering Group <irsg@irtf.org>
Subject: IETF/IRTF mailman & S/MIME
Thread-Topic: IETF/IRTF mailman & S/MIME
Thread-Index: AQHM5o70sPG9GG2xGkipdI0RBwRa9w==
Date: Wed, 8 Feb 2012 18:24:55 +0000
Message-ID: <BEB57F99-6093-4D5D-9C23-C98F499B5426@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=_620B25C1-C120-4376-B185-DFB94C3413FC"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-OriginalArrivalTime: 08 Feb 2012 18:24:56.0048 (UTC) FILETIME=[F5341F00:01CCE68E]
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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, 08 Feb 2012 18:25:02 -0000

--Apple-Mail=_620B25C1-C120-4376-B185-DFB94C3413FC
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_0CA9A506-9AA2-40C9-AD91-C7F6BB529693"


--Apple-Mail=_0CA9A506-9AA2-40C9-AD91-C7F6BB529693
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

by default, the IETF/IRTF mailman is configured to add a footer to all =
emails that go through it, e.g.,

> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpm

The way in which this is done breaks S/MIME. This causes emails from =
those of us who use it to be flagged as tampered with:



As a chair, if you want to be nice to us S/MIME users, the easy fix is =
to turn off the generation of that footer in the mailman settings for =
the list. Go to the the "Non-digest options" settings page and clear out =
the "msg_footer" field.

Or click here after replacing LISTNAME with your list name: =
https://www.ietf.org/mailman/admin/LISTNAME/?VARHELP=3Dnondigest/msg_foote=
r

Lars=

--Apple-Mail=_0CA9A506-9AA2-40C9-AD91-C7F6BB529693
Content-Type: multipart/related;
	type="text/html";
	boundary="Apple-Mail=_C598D7FA-B92E-441A-910E-C71F770FF379"


--Apple-Mail=_C598D7FA-B92E-441A-910E-C71F770FF379
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; =
">Hi,<div><br></div><div>by default, the IETF/IRTF mailman is configured =
to add a footer to all emails that go through it, =
e.g.,</div><div><br></div><div><blockquote =
type=3D"cite">_______________________________________________<br>tcpm =
mailing list<br><a =
href=3D"mailto:tcpm@ietf.org">tcpm@ietf.org</a><br>https://www.ietf.org/ma=
ilman/listinfo/tcpm</blockquote><br></div><div>The way in which this is =
done breaks S/MIME. This causes emails from those of us who use it to be =
flagged as tampered with:</div><div><br></div><div><img =
id=3D"5b5ebafa-b3bc-46fb-acfa-c36e77d8f42e" height=3D"167" width=3D"563" =
apple-width=3D"yes" apple-height=3D"yes" =
src=3D"cid:43FFA762-9FF1-422F-94C8-18FF92AFE18E@hq.netapp.com"></div><div>=
<br></div><div>As a chair, if you want to be nice to us S/MIME users, =
the easy fix is to turn off the generation of that footer in the mailman =
settings for the list. Go to the the "Non-digest options" settings page =
and clear out the "msg_footer" field.</div><div><br></div><div>Or click =
here after replacing LISTNAME with your list name:&nbsp;<a =
href=3D"https://www.ietf.org/mailman/admin/LISTNAME/?VARHELP=3Dnondigest/m=
sg_footer">https://www.ietf.org/mailman/admin/LISTNAME/?VARHELP=3Dnondiges=
t/msg_footer</a></div><div><br></div><div>Lars</div></body></html>=

--Apple-Mail=_C598D7FA-B92E-441A-910E-C71F770FF379
Content-Transfer-Encoding: base64
Content-Disposition: inline;
	filename="Screen Shot 2012-02-08 at 10.17.53.png"
Content-Type: image/png;
	x-mac-hide-extension=yes;
	x-unix-mode=0644;
	name="Screen Shot 2012-02-08 at 10.17.53.png"
Content-Id: <43FFA762-9FF1-422F-94C8-18FF92AFE18E@hq.netapp.com>

iVBORw0KGgoAAAANSUhEUgAAAjUAAACnCAIAAABmRjquAAAX8WlDQ1BJQ0MgUHJvZmlsZQAAWIWV
WQk8lFHXv888sxljGYPs+74vWbLve/a9whj7MjR2lbJESbRIQhEiEaVCoiJLi1IqWiSyREkkCZXv
IfW+37v8vt9353fv85/znHvuueecu5wZAHiuUiIjw1CsAITToumO5kZC7h6eQrhBgEI+zIABaFOo
UZGG9vY24L+Wb/0AWns+lV+T9d/5/mMh+flHUQGA7BHs6xdFDUfwVQDgJmokPRoAzJo8sbjoyDV8
BMHsdERBBJev4cDfuGkN+/7GPes8zo7GCB4GAE+kUOiBADBNI3ShWGogIoeZCACWjeYXTENYhRCs
Rw2i+AHA44PwyIWHR6zhLARL+f6TnMD/JdP3r0wKJfAv/j2X9YI3CY6KDKMk/D/N8X+X8LCYP2MI
IJUYFepkjTw5EbvFUymmTgjmQnB2kL+lzQa9IjLayHGD3hIcbem8ZiMEPwuKsXDZwJMxoS6GCOZD
8I/QCOs1fsROKC6ar60dgtkQLEaNMvb8LROlnhjk7LbBY+Pnb2KKYCSKUO70CMc//EFRsU5/6ImJ
Qca2f/hDKFZr/mZGcCaFvj4XRAdUvn+Y+dq4IgiuiYy2d94Y6xEtzHZjLqixALqZ4wZe9o9an+/6
WNFBzha/5cOs0UgA/JYJ8wUEm1n+1gFWCqJb/KEbRIatxzTSF3amxziu2UEMwQH+NJcNmXCmH8XE
+rdN4CJgBiiADvyBL6CBn0AI2ABjYLLRCiF0GtJSQQQIQypdiOXPG8wE5gnmHeY5Zhjz8i+38R8+
EAz8kOcfOvWf6E4gEXxCpPqDqD+joXnQemhttA3SGiBVBa2J3vLn3aPpxum/Wv3WNRDpK79BMdrQ
PvaftfcOTqH/Sx/fvz3+XSczMLYudYNDqVppSunHn/7/mDHWFGuCtcCaYaXhA/AVuBtug+/BLXAj
EIJvwU1wD9y6hv9lFMqGVejr87VGRvQHMevfaP9Ro5i/HBtUZhlmNeC4zh+KvAv+O4LrutbB/yYl
Bqm+iKQQ5J313zn+sbQEYl01tBFaF7EzYmM0J5oHyKM3IxY3ROsjPlBDqMb/2mujlQcB67aMXZ9L
KJhAcHi0f3z0WqAbR0Qm0IMDg6KFDJHd0l9OyJJGVZATUlFSVgFre+/vpT3vuL6nQpy9/6AFqgCg
NofEuuQ/aMEnAbiBrCvczn/QJJA1wNwGwL1cagw99jcNvdZgAAGwINHPjewcokAK0VMFqANtYABM
gRWwA87AA3gh1g0C4YjGcWA3SAbp4BA4Ak6AAlAMysB5cBHUg0bQAtpAF3gAHoPn4DUYBuPgI5gF
38AKBEE4iAkiQ9yQICQOyUIqkCakB5lCNpAj5AH5QIEQDYqBdkOp0CHoGFQAnYWqoMvQdagNugc9
gV5CI9AU9AVaRsEoIoodxY+SQCmiNFGGKGuUM2oHKhC1E5WISkNlo/JRpagaVAOqDfUA9Rw1jPqI
WoABzAhzwsKwPKwJG8N2sCccANPhJDgTzoNL4Vq4GYnFp/AwPA0vobFoMloILY940gLtgqaid6KT
0FnoAvR5dAO6A/0UPYKeRf/CMGH4MLIYLYwlxh0TiInDpGPyMBWYa5hOZD2PY75hsVhOrCRWA4l2
D2wIdhc2C3saW4e9jX2CHcUu4HA4bpwsThdnh6PgonHpuFO4GtwtXB9uHPcdz4gXxKvgzfCeeBo+
BZ+Hv4C/ie/Dv8evMLAyiDNoMdgx+DEkMOQwlDM0M/QyjDOsEEgESYIuwZkQQkgm5BNqCZ2EQcI8
IyOjCOMWRgfGYMZ9jPmMlxjvMo4wLhHZiDJEY+J2Ygwxm1hJvE18SZxnYmKSYDJg8mSKZspmqmK6
wzTE9J2ZzKzAbMnsx7yXuZC5gbmPeYaFgUWcxZDFiyWRJY/lCksvyzQrA6sEqzErhTWJtZD1OusA
6wKJTFIm2ZHCSVmkC6R7pEk2HJsEmymbH1saWxnbHbZRMkwWJRuTqeRUcjm5kzzOjmWXZLdkD2E/
xH6R/RH7LAcbx2YOV454jkKOVo5hTphTgtOSM4wzh7Oes59zeRP/JsNN/psObqrd1LdpkYuXy4DL
nyuTq47rOdcytxC3KXco91HuRu43PGgeGR4HnjieMzydPNO87LzavFTeTN563ld8KD4ZPke+XXxl
fD18C/wC/Ob8kfyn+O/wTwtwChgIhAjkCtwUmBIkC+oJBgvmCt4S/CDEIWQoFCaUL9QhNCvMJ2wh
HCN8VviR8IqIpIiLSIpIncgbUYKopmiAaK5ou+ismKDYVrHdYtVir8QZxDXFg8RPineLL0pISrhJ
ZEg0SkxKcklaSiZKVksOSjFJ6UvtlCqVeiaNldaUDpU+Lf1YBiWjJhMkUyjTK4uSVZcNlj0t+0QO
I7dFjiZXKjcgT5Q3lI+Vr5YfUeBUsFFIUWhUmFEUU/RUPKrYrfhLSU0pTKlc6bUym7KVcopys/IX
FRkVqkqhyjNVJlUz1b2qTapzm2U3+28+s/mFGlltq1qGWrvaT3UNdbp6rfqUhpiGj0aRxoAmu6a9
Zpbm3S2YLUZb9m5p2bKkpa4VrVWv9VlbXjtU+4L2pI6kjr9Ouc6oroguRfes7rCekJ6PXonesL6w
PkW/VP+dgaiBn0GFwXtDacMQwxrDGSMlI7rRNaNFYy3jPca3TWATc5NMk0embKYupgWmQ2YiZoFm
1Waz5mrmu8xvW2AsrC2OWgxY8ltSLassZ600rPZYdVgTrZ2sC6zf2cjY0G2at6K2Wm09vnXQVtyW
ZttoB+ws7Y7bvbGXtN9pf8MB62DvUOgw4ajsuNux24ns5O10wembs5FzjvNrFymXGJd2VxbX7a5V
rotuJm7H3IbdFd33uD/w4PEI9mjyxHm6elZ4Lmwz3XZi2/h2te3p2/t3SO6I33HPi8crzKvVm8Wb
4n3FB+Pj5nPB5wfFjlJKWfC19C3ynaUaU09SP/oZ+OX6Tfnr+h/zfx+gG3AsYDJQN/B44FSQflBe
0HSwcXBB8FyIRUhxyGKoXWhl6GqYW1hdOD7cJ/w6jY0WSuuIEIiIj3gSKRuZHjm8U2vniZ2zdGt6
RRQUtSOqKZodueT2xEjF7I8ZidWLLYz9HucadyWeFE+L70mQSTiY8D7RLPHcLvQu6q723cK7k3eP
7DHcczYJSvJNat8rujdt7/g+833nkwnJockPU5RSjqV8TXVLbU7jT9uXNrrffH91OnM6PX0gQzuj
+AD6QPCBRwdVD546+CvTL/P+IaVDeYd+ZFGz7h9WPpx/eDU7IPtRjnrOmSPYI7Qj/Uf1j54/RjqW
eGz0+NbjDblCuZm5X094n7iXtzmv+CThZMzJ4Xyb/KZTYqeOnPpREFTwvNCosK6Ir+hg0eJpv9N9
ZwzO1BbzFx8qXi4JLnlx1vxsQ6lEaV4Ztiy2bKLctbz7nOa5qgqeikMVPytplcPnHc93VGlUVV3g
u5BTjaqOqZ6q2V7z+KLJxaZa+dqzdZx1hy6BSzGXPlz2udxfb13ffkXzSu1V8atF18jXMhughoSG
2cagxuEmj6Yn162utzdrN1+7oXCjskW4pbCVozXnJuFm2s3VW4m3Fm5H3p5uC2wbbfduf33H/c6z
DoeOR53WnXe7zLrudBt237qre7flnta96/c17zc+UH/Q0KPWc+2h2sNrj9QfNfRq9DY93vK4+YnO
k5t9+n1tT02edj2zfPbgue3zJ/0u/S8Gtg8Mv/B7Mfky7OXcq9hXK6/3DWIGM9+wvskb4hsqfSv9
tm5Yfbh1xGSk553Tu9ej1NGPY1FjP8bTJpgm8t4Lvq+aVJlsmTKbevxh24fxj5EfV6bTP5E+Fc1I
zVz9bPC5Z9Z9dnyOPrf6JWuee77y6+av7Qv2C0Pfwr+tLGZ+5/5+fklzqXvZbfn9StwP3I/8n9I/
m39Z/xpcDV9djaTQKetXARipqIAAAL5UInmLBwDkxwAQmH/nRhsFRi4fKOTpCh1E7YQ1kdvPOOYu
thKXg09g8CdsY3QhOjC5MjuyeLL6kILYaOR09k5O0qZtXBXcc7w6fBn8LwWVhJKEn4nKiqWKv5HU
ksqX/ibrLHdVgUMxQWlExUa1Xo1PPV3j8xZnrRYdEd0DejMGjobXjLlM4k1fmmtanLRcsHa2qd46
ake2N3QIdzzp1OY84Upwk3Y38/DypG9L3X5kR6HXWe8Kn/OUSt9KapnfGf8jAXsDaUFewbYhOqGy
YbzhjOHLtKmIF5HdOxvplVF50ftjomOpcY7xhglyiZt2Qbumdw/saUuq2XtyX3JyeIp7qnGawn6e
dEz6XMbggbsHr2aWHMrKOnw4Jzs7J/tI9tHDxw4dP5CbcmJPXvTJsHzfU64FloXaRXKn+c4wnlku
nih5dPZKaX7Z7nLfcxYVCpXslSvn31Xdv3C5uqAm5WJYrUud/iXpy+TLv+onrzy92nStqGFfI7XJ
9LpkM7558kZ3y7nW5Jvbb2ncZr091dbWnn+H1mHcyd051/W4+8rdvHuJ970eGPVIPWR+uPBosLfj
cc2TE31JTwOf2T/X6hcdYBpYfDHysu9V++v6wdI3R4f2vY0Y3jFi9U5tVGiMMPZl/OXErfflkxlT
oR+2flSYJk4PfCqZCf2sMYuZHZir+ZI27/PVcEH8G8u3n4uz3yeX3i2/Wxn9MfHz06+vq6vr/jdF
GcKK8Ay6DZOBdcIp4Dnw7xm6CBWMWcRYJm9mCxYNVn4SI+kXWZHdiyOXs4cL5tbgCeI9y/dGgEfQ
QShbuEeUIGYuvl/inhRe2komW/aZvKBCkOI1ZVjFTvXU5lF1eY04zXYtRm0nnULdEX1pg3DDeqMl
Ez3TVLMW8xcWU5bfrbE2pK0CtpJ2ivaqDuqO6k6qzvIu4q68bizuwP2zx5Dnw23N28/u2Oe1zVvN
h8VnitLhW0Ld5efirxhACBgPvB1UGBwX4hAqF4YLexfeSjsVQY+02SlBB/RXUVeiD8cExhrG8cZ9
jX+UUJmYsmvb7s17iHsmkm7tzd8XleyeopcqmoZPm9n/LL05o+TA/oOhmfaH1LK4s1YPj2Xfzak9
cuxo7LFtx/VzhU6AE2/zbp0syU8+RSkwKhQtQheNn+4+U1V8qIR21r5UtYyj7Hv563M3K0orU877
VhldEKmGq0dr7lwsr02t87tkclmsHl0/dqXz6rlraQ1+jSZNYtex16ebn9+42VLVevxm0q3Q2x5t
5u0ad6Q6eDqZu1Bd37tn7o7fe3O//0Fvz72HPY96e588fvqkv+/F01fPBp8P9Q8PvHsx9nLi1fvX
Hwan38wOzb/9Nrz0DhoVH7MdT5iofP9yivTB9uPR6ZczMp9TZ0e/2MzfWFD9VvdddenGitmPgV/B
G/5XgD6iTsNOaDz6OiYWq46dwzXhkxgsCHyEWcYOYh5TCLMpizDLLxKWjZMsw76Fw5TTdVMI1z7u
EzwXeTv5hviXBdmFlIRtRSJEs8UuivdKzEtxSevLBMpmyV2SH1D4qSSsbKYSpJq5uUbtofq0JnGL
lJaFtp/OXt0ivVr9aoMzhjlGScahJu6mBmYS5gzmkxadlmesoq3NbNhthrdesKXbqdst27c6JDlq
OS44XXIOdRF3eeta4Obszuze7ZHsqeU5v61me+AOwR0DXke8LX0gnxZKou8W30Vqg1+0v4r/XEBd
YHiQTNBkcEWIX6hQ6JuwgnBXGpnWG3Eo0mInZucdenKUXtSP6Osx8bFqsXNxtfGhCZIJo4nFSKRw
7u7bk51ksRfee2dfFhIr4ilzqa1pmftd00XTP2fcOJBx0DFTIPPDoWtZ+w5bZ3Nmj+TUHIk9anSM
5djg8arc2BPGeaS8oZPV+QmnzArYC0aQU3PPaZszPGcmixtK0s46lYqXrpT1l186l1nhV6l/nvf8
t6q+C3XVWTXBF81rJerQdWOX7lwuq0+94nfV6ppWg1KjZJPgda5m9hukFlIr+03eW+K3VdpM2j3u
RHXkdNZ19XUv3RO6v+PByMMDvZsfj/eVPAvs13sh80p+cOtQzvCX0T0T8lPg4/xnwhfDhZzv8z8i
1vz/+zeytYJVB6CcDQmI5wC4RP3G4vrI+dEDgD0TAM5bAGq/AEBtIgAoq+fv+QEhLRYwAjbAA8SA
ItBB8kwPJOPeBXKQbPI6kj9OQTDEi2SJVhAV2gPlQ1eRLPAzihklj9qKikAdRV1FvUD9hEVgSzgS
zofb4I/IWWSEpqGL0PfRSxgpJC/LxLRgPmNFse7YbGwX9hdOA0fHXcR9wEviA/AVyG4lzRDOcJlh
kaBHSCf0MvIw+jNeJmKJFGIrEx/Tbqa3zMbMVSxkliSWT6xerE9J1qQuJJfpItuQn7NT2Oc4Ujm5
OS9vctz0nauE24p7kaeS14OPia+DP0lAS2BJsFloj7CxCFHkhWiFWJy4lYSYJCQ5LNUuXYnsdPFy
/vJOCqaKWkrKyjIqEqrimyXVZNVVNLQ1lbdIa4lri+qI6UrpKeprGVgZbjeKNs4xqTXtM1u2kLB0
tcq0brf5aWtid8x+1FHT6TBy+hm6FbuvelK2de2Q98rzgSgRvm/9HP27Aw2CrocYhvaEb6fNRh6k
S0Tdi9kZJxj/LDF7t10S+963yZdSM/b7ZhgcZMocyCrNjjhicIx0fOzE9ZM5p4IKjU8LnVktGSnt
LK+tyD+//0JMjWet8SXFesGrbA2EJkwztoXpJvdt2XbjDkpX+t36++8ecve6PMl7xtNf+VL19Y0h
reEroyLjGe/ffVCdTpxpmp2ZF1qwWoxaOrVy4+fw+v4BIbcNLCACMuAHUmAzMAZOwB/Eg8OgHLSA
ATAPsUJSkBG0HYqHcqF6xPdfUGSUGsodtRvJ7++iZmEu2AgOh0/BXfA8WhTthE5D8vMpJCt3QHLx
VsxXrDw2EFuGfYvjx23HFeHe4IXwfvgq/CyDJkMyQw+Bi+BPuMIIMzozVhBRxEDiIyZNpnIk601l
XmQJZ3nPSmUdJQWSZtgSyDjyKXZF9rscfkg+WrHJhYvAdYd7L48uzy/edr5MfmcBYYE5wU6hAuFo
EXtRRTE2sW/iwxIPJVuk6qQrZIpli+QK5c8olCvWKjUr31cZUl1QY1GX07DW9NoSo5WjXa1zX3da
n2SgZehvlGvcZbJipmJOs6i2/GStYhO/tdOO236nQ4+TtPMBl2k3B/dmT4ltuTswXvHeM5Qg31E/
qv9YYEjQbEhyGHt4dYRJ5Ag9OVospicuJkE08dnuA0n6e5eSm1IT9utnYA90ZaZlGWfDOd1HM4/b
niDnvcwvLggokj+9UNx6NqPM8ZxgxfT5GxcO1djWkuveXK66EnfNopG3aa75QUvFzf23/dstOxS7
OO9C96YfvHr4oLf1yeWn9Ofy/e9flLxyGyS8aXxLHWF4d2HMYnzoPW1y+UPKNPxp38zKbOTc6Lzz
19vfZBfzlsBy4MrDn2q/Cjf8jwYMgAR4gSRQB2bI2g8HqaAQNIA+MIv4Xg6yhAKhDKgK6oFmURwo
HZQf6jCqCTUGk2ADZMWfhZ+icWgddBT6AnoUw4+s9lxMH5YN64Q9gX2JE8QF4Opwy3gzfC5+jEGd
4SDDW4IaIZswxWjKWEZkJO4hfmEKYZpg9mOeZIlgWWHNIomSbrH5khnJzewRHLIcH5GVnczlyq3E
w8wzyzvA185fL1AhWCxUKHxapEy0VqxF/J7EgOSUNCTDJ6st5y1/QOGa4oQyn4qb6snNr9XFNCI1
b2qRtIN1OvXE9A8azBv5Gveb2pn1WNhZ9ltTbeZtaXbjDt6OQ87eLhNuEe6/PI9sl9zR5u1DQftW
+7kFYANvBEeGSoaN0EqQu7lk1FzMzbicBOounT2cSQv7XqTcTKtKzzuQmOmSpZJNzvl+dOh494n6
kyWnjhSmnI4tDjvrX+ZzzrvSq4pS7XRRuY7l0qf6nqsXGjKafJu1Wlhah2/VtsXf0e0EXbfu7rqv
9uDTw9JejyfMfQefPngO9WsMhL0oedn3GgzKv3EeinubN1w70vbu4Wj/2PPxJxMd7+sni6b2fPD+
qIbcGN98qpyhf1b//H32+lz0F4UvU/NFX+0WUAuXvu1YJCxe/b5jCbt0cdlx+fvK6R/6P0Z+pv4S
/dW+6rPm/6gAVZX14wMiGgGAGVpdnZcAAHcMgJ9HV1dXSldXf5YhycYgALfDfv/vsn7WsAJQ1LiG
uozT9v3r/x//A3CLxfJ2dcc+AAAACXBIWXMAAAsTAAALEwEAmpwYAAAgAElEQVR4nOydeXwURfr/
P9XTc2ZmcpGEJBwJAQxHAhJZELkCqLCCYVdZVEQFVsATWHbl8Cd+Ad0IXgmiQjxglagYdAmH4EoI
BBQQAiThiEBIgBzknMnMZM7urt8fPbknIQkRcbffr4gz1dVPPfV0Tz1dVU9XEWraCQkJCQkJidsM
5rdWQEJCQkJCwgOSf5KQkJCQuB2R/JOEhISExO2I5J8kJCQkJG5HbqF/ovytK0tCQkJC4nfOrfBP
lFLOUOnI+F4QhFtQnISEhITEfwG3wj/xvOD8+ZCsS6C94BKl9BaUKCEhISHxe6eT/ROl1HX1kuBw
NExxXrkkDwllo+fyWUdd9kaHOEMlV1EqOS0JCQkJiSawnSuO43jnmdM4msH0iJD3i5bpfVx2B3fy
iOqheAHQ3DXeduYkGzOcEOK8cpnLzZIRTggbqPTtIpPJOlcTCQmJ/02uXisrKq4sq6g2GCxWm0Oj
Vvr6agO7eIeG+PfoHth2OWXlxitXy0quG2qs9l9P2/9WvDSq4K6+PXsEBgb4dFgI6dz1I2w2h/XA
Xu+7xsFhdhz7ger9OBnrNeBumd+doDyIwlWwy2msogW/KLt3l/W7nzu1vaZrX+/evVlW8k8SEhI3
RWFRRe6FwioT261HZHBIhH9AiE7nazYbKsuLS4rzCq/m+um5yL7duoV2uaGosnJj1pniwJBB3cOi
/LqE3ALl/8uoqii+VpBTVpw1aGBIh11UJ/efADhZJVd6me01Xj3lD3zlKaXLSnS9hJpSACBEFjxM
4dgvmzifKPyo0+osrRR6KDtdBwkJif81zuVe/eWSIbTnkOGxI7S6+gZR7+2v9/YP7x1lMRvP5fx0
/NQpk9naP7JH69LyLpf4Bw0cdNf9v7LW/7X4dQnx6xJy8hifd/ns7eKfCCFQqvmqUpnfFR4gcl/I
/ajxWsMcspAhtMZIzVUAeHM146VjGNK5akhISPxPcS736i95lgGD7+/b766W8mh1Pn8Y8ccLvoFn
s/YDV1t3UUUlVeMGD/4VNP3fIixi8P49hzp8eif7J4YhxEsrXCsWaspbzGRx/58KLhcPuUJJyK33
T3ze6dxqfc8hvbRNDhgu550xae4eHNz5XcvOxVKyY8/ZKqc84u6YUc1qISHxv0NhUcW5XyqiY/7Y
inOqQ8yTnfmdXqdpZaDPbLbe7LAeZzh55Iz3wLsjfG/3tsQDnaS8X5cQs9na4dM7J35PcDptV6+Y
jh+xfL9TXXxJPuAOwVbZ0h91GNhQreA0UqfZO3a4a882Y/oPNWeynZXlNw7k48rXPf366u8K6xLs
l3+c+eg3ee2ev3TuHr00ZkdR8wP53yeMHv2Tub3ybgH2wtWPvr3tgg0AuJJFIXPj5qRuX//W2wdK
f2vNbg22HSvfXp5aeOOMEv9jnMu92j08pqFzWrVq1RNPPDFq1KgJEybMmTPnq6++avjyZd9+d3UP
jzmXe7UVmUL7gorN+9ctIm4Grd2RBwC2C7NGj/7mwq/Rlph3rJ43c56bRctXb9y2v7gTYjjMO5bP
XL4tF+hM5dtpyUbcrH8SBKH66OGypHXWg98xZZdVfqyiWwBvNPDWqpb+SIBe5qhQRIQIThNnsekj
QxTUxOVmmrd/VZq03llZ2ZqXspv2bz2afqU+SN1lq9qyO7OCa7fmylGIVXp4NJArdRjg1cZnhvKz
JzemZN8iZ8Y50ncfqHQBgPmXrAQgMWPt9iM7t8+OuDXl/+aU7D2wO99x43xthc/5bt8XP7Xc0Zf4
PXD1WpnBLO8fNYJvwK5du9Rq9aRJkyIiInJyct55553XX3+9YYb+USMMZvnVa2WtSBYEgW8bF75e
PH5Bwow3th448O//m5G953wpz/M8w4QBCqaNMtpH0f6kLRdqQkJC/NQ0LX7F/GnjQ9VzTxtbPsFx
ffuHCfvya24gdteWXXlmnu805W9yTYab7XgKAnWG93fm5WuDlMRXL7h4arFAaNHBMDpvpYbAUCXj
XMo7+toyj1OWITqN3FfHnc939YhyKjXy9ukrd//XEWQAOI4HK+uYIa4f2zZ/IYZOiR6i6qAG7UAb
sb822FItBxA1rLf61y/19kE978jOeZ0pkP/pkcT5axIeGxHQmVIlbi1XC8tDu9+h8dI3bAp37drl
7+9PKSWErF+/Pjk5effu3S+99BLDuJ/INV760O53XC282ErEOaW0bc2r5VDyRxjz/od/+5MKGDHC
+Tc7JwgCBFoNUFYpCALHcSzbiaN8lFKM+cvi5U8PBLDqzTX/ef2pySs/eiLhscyX7/F8hlCy4tlF
s07OGdOtlRp5/TXT+VegXnkq3KSDqTN4B0+/mZMBMAxRqlW2ISNL86ocxVW8xSk4eMEltPSnjOgF
YykA2MzGrCzBJfA2jjM5TNmXy/U9Ed5XLu/wVbRtW7B8UXL23g/fJvopRP/CuoPiozF/6NOPiX4K
0U8h+uXrDpbUn+Eo+mLlcrnfVLn+hbX7SjyINBasflQ88YWNP1U1OWi/sC96YQ6QExM4ZdDT+8wA
4DyU/FltWW9vO13d5JTclI/Jo98U134t/2knufvjXLvngnJTPh63dN+h1K+IfsqghF9gL1h09wub
z9rsl3+Muet9IGfuvVMGPb0vM+Vj8sBnubW9e8PxvYP0H+dYGhYrWubkjoTXRSPsuFydk+rWc3lK
Xl22/R++LyZOTTgpdgrtJWeXP/qCmDgzuUDMl3dw7zh3HadsPiuON5ave3q5u+KPfnasxL3WIleR
V1uv19d++Nm4Oj1bNWwL5dq2LVg+L8WtQ/FP+0QdBj398bxHl89MyObqa9qmeyAn+aP5AJYkDNJP
WZRS6D43xT1+mJf68aAFB82izKXL53368+alLxD9C8csng0l8VtRct3QNaRXk8d2vV7vcrk4jnO5
XOL0dnh4OKW0YZ6uIb1KrhtakSwIQtu6UEQTABw8eeq6Q/wulxO3GoAh9z9vPqTQaDSKe18+Upvh
+oltTyrcLN6cUcPz1ee+GKJ4Mk3MUH1i8RDF4i+yeJ7neUfa6oee3JjVtF8CwGav/aYevzThlYHI
WZmUVcPzPF94ZPO9ovR7Xz5R6eAdF1/+w5Ac4G9PjFAonjlRzfOO/HVPurMoHnr5SKGoWPW2Z+59
xl0uD0DgBZ7nawozXn5oiJj3yc1NNWkF0YA3c3Fv3j8xXl7KwK4B3N0Tqq4ZeauVCpz4R7RaotXW
faUCJw8JYZ3VoBSA6Xo1bzCJ6fbr5UZ1oCp6iL+fTqFgOxwuYSnLSXjm5Um7Avakvb7mgYIFU9KK
AcBpMGlT0j4s+uXDDbNyFkxxD+go9Uhf8caMqrsz0t5InI4lf577hTi1U0/58h4vrNA+d/7yv9IS
IudPfHV/RaPDqh4DEkcBiNr07RubFg7RASc/fHP0Mymrvkoo+uXD5MX2aaMfbyIzbFAYdm/edlz0
HpYvFydhzJDeKs8FuczV6R8kjp5ZlPztG1um9wD4rLMFJhfPBvZdvWYsELZo9RtJzw24Y1AYDqVs
3C9Wy/b1/72fPb1Pn8YBE5aynIRnXo07G5mRtnLhgJy4wY9HzyxPTXtjwyzEz9meYweAkx++M35J
UcqRTwsylppWvPr31HKA/ylpafzusKNnt1zKeOP5oV0AgCv8vynvY9XKosufZu58PSZIAQD2GvQe
d/T0pwUZS+N2pyzbXiAacEWvhSt2T9xz4tNLaWN/WpKSfuhaNXdjw3ouF6i8lHO0ggdgvrAvdGIi
Fv/90i+frh+LpN05W364Ym7nPRA2euxcIPrZuKS0t2aP9Bfl769wjx9aKy9n/2xyW+9KTtLC1bNs
96XtXdhL5dFQEr8ZBqPFzz9YaIGqqqrvvvtOLpcvW7asySE//2CD0dKKZLH/1AYUY2auAz4Z00P3
+r8OVznr0qkXsPqxh48MSz7ww6bJB998ZWu2IAjW81/1GPFY0d83nbx06cevX3tv7oS49Sc1wX3C
8GXKoQJBEIp+/Pa9M3jv0wNVgiBYz7+/emdEZECTIiltol7QlLmTAXONU7Ce/6rXmLlRmw4UXPr5
NfrmiOmbTILP1NfWDQRmz33twIHZPRWCYK2mEY8eyMnN/TF58s43X/kmW5RScfHgsXJnbQli/8n5
0wcT3tw58EBuQc6PP8y7K6RtNqnT86bWBuqE+AiZTKbTqbuEBgr9B9mulVGOUo4SuUp752Dt4EGQ
KcQUEJm6ezBsZgCOapu5yKBgCOWoUGM3VVpldw7r4q9XqRQ3E8vnAPDAc2W7n5g4NPrByWOB7GsW
AOoHFz7y8NBgP1+fYDWA3MsWAHCYgMUraeKUUUMHvPjewjjg47TihtLMZzPjgWWT++htiBg2OBoF
J/Ib382q4PseGwt4RY8cMGSAH+wF7y45GrvqrVf+GBES3O2xV2fPbSZT1Xdo4gAsSMriAPuFzAVn
kTx7oK3FguzA8IzLix+bMCAquH4oj9UG/HH8AEAXPXLAsMHB2r7DE0ch4f2jBoC7fHL+ISQ+F9Nk
uNFhAmb93fTRQ6OGDpn99HAg7nzZ4geHDnhy7lyg0spBVB7Tx93pJ5P7d+0DJO3KMgNOG4CC89es
oYMHDOurBQCOA5B+Nv+6TT1kTHRUFxkAaMNeXDJhWA9vv959RwxoZMDEjNkT+wZEDL3nqyPPATXy
thjWY7kAAH8AwLnv9gMTP3h5TERwwKgZT2x6AIC73932e0DXvc/do+Dfs/ewoXfUmde/kRbyRtZL
nDJuREQA59lQEr8VFotNo9HXPa03xOl0rly50mw2/9///V9ERETDQzzPazR6i8XWiuQ2+ydBHzOr
JGvXc6Px2vx7Q72n78o1iekWYPaHR79c8GDM8MkPjEYVFQRByNq3CZj93qsP9wkKip60YP/q0Rn/
+CSX6Tt9Oj798rBTEI7seAsAMnaeMQmmE6m7MP1Pg/2btvsAGmtnqS4AIHPLnzxxSKBV0A59dDYy
tp216qPH/CEMiPzDPTEx0XpGEDT95i+ZEdPN37vXncMG1ouigF/t57oSnDYAZ85fqe4aPTymj76N
NnELvDn/1DlDojIZo+Qc8uwTuj4BnM1CKdXePYypvALA664hpu93U57X3PUHYi4DALvzes5FLcsI
gowQAhkb0NWrOvtnVa+4Ng5W6hu80cu5XABc4hcTYh+KFCcTXA474CUHANv+T5PHL0wFwqIHAA0m
q2IDvVspRRxpjJ+5MN6dELZI03SRC5fDDgBidAbHm4H06roJfP+7H0BSRr75mQhd/Rneca/ELXjk
qyPvDseXb2HA3El9FfILLRVUg1GjB3uKgLWJFXZHhWgfXjRtwZ+T0komdE/5Cpjx8GAP4eaxg3rW
qlGDUd1CVQDgqpu943gzgK2Jvbe6M0UDgGzC0vdWXXlh1sS5sxCWuHP5i2OCoQpbk7agaHxizNbN
GDXt6MePDAtWwFiw9h9vL9lagAFhOIs4twwWCOsrdrBQb/c2GNZTufU4S6/nYNS4MPfN23jflnbc
A7yj+en1eHm2nmdDSfxmqFSK6upKhdJLaDaU9PXXX586deqZZ56566677PZG8W0MwzgdNSqVAi3j
crmcTmcbW1h56PCV31Y8dfRfiyYvnh6z9Mj1t/twLiMwYkBXh8MB1FgF+HAuh6O6+HIGRk7zd7hX
KWU1QUBJRQ2586H5+Mv+U3l3fPEpNmV8f2z0/emZudW7Xsf8r3sSh6NRYJCDEyBwrkapsu6A0eqo
Lr9cAWRMHrQLANAfGAqHw8FbjQBnrXY4CAAYz723bP7KlHPo3x/nMMktqoFYh0sAOJfD4VDfvShj
6eXRz9w/6Bn0/+e//zV3VHhbDAKAEPLb958AOKpNpf/e5heicBqqeWuNYLOWH0yH0w7OKXcatSPH
yPz8NF39wTlB6dXTF1S8S3A6BJuVt9bw5mrIOLW5sPSHfc3vsKaogsaNQuqF+nmd0pPZQHT3ugbZ
0bS5MZzeN35h6qYjX1LTe98+P7bRMWVdsyhDY7cHwGW1AUjM+JqadlLTTmp676kBTeMRXO5bTPxX
pgNiA+vateqs3Yge1l3X+JSeo2PjUPD2a8mvvo1lq+/xbb0gD1MzHggZOXouMO2v78x9vWDu52M8
v7XR0DLNxbIyHRC9+PVaHXZmfTRBB7A+Ya98udN0+cPE6QULpnx60g4AIUMn7DdtL8pYGnsoZXji
aYDf8eoLS7YOOl+2kx55L3kUTKJhXRxQcKHQKZaQdfis2Oi3xbAey61FEdQ1Cod+KXA/FlQe2e0u
zENNAbR6D1Q2iQd03xJ80bWj8PNkvRYMJfFb4eerM1Rdh7g4QGP27NkD4L777mvSsIg5DVXX/Xw7
+dKFD3/y3femAXmmujuWaxJbrAoIGonDZ+uGtDlHCaBVs+gaff9IpDz//Lg9WDqqf8zIJ/HGS4v+
sgH//MuQFkpr0LswZn64fA8m/SlCqwoI8gOePF4hklFR8XZ0bfOodMdocHtXj16ZMvpIYUVFRsbG
kTB7imSuL8an/98/ryjIPfLPaeeW/2lF9i1cjLAT/JPLaru2daufN++yc7yLF3gq8FSoNFzLvABK
YTMr1TLvsePFsIiS7DyZxQqBurPxVOCpo8Yl18hoXnbZT0dv5KK0A0eH4YNX1+4rtHO84fLZjR8d
xaxeLYXguABbtQGAo9pcfvns2mcOADVGMw9x/mlh8rbj5XZ79Y7EpFSEzZ8U1vBc3cDhy4AFoz/d
e7bKbLHknf0lp8LZRH73/hHA0dzcKrPFBlXYrJfD0pckfHG63G6pPpScmgDMuSe0WQ0iXlwclvpB
SjomPjHWr40F3QBV2OxVw3HoaDaGzxsffOP8niQsWjM8++2XV6fmGSy28muFh34q5GDbn7zv0OUq
uY9P325hgEoDwF6yLeVkXoXTLyx0OACwAG+xAkC1oTr34M4Zh5CedcUA6AYOWggsGL96bfK+5Y9O
Gb7wgFhUG+rrqdwG9L93HLC338zPNid/M87vmSQgdnTPllqalu8BmS4E2SvST1bY7BwA3lGF9CO5
uddKtq1cOOltQN92Q0n8ZgQF+pSW5HscejGbzQBUKg/BtQzDlJbkBwV2fOnSBtgP/StpZ+bFCqPF
UnFu13cpQIS+5YDeiDF/AjZs+PKo0W4vzP7m+eWHsfCx/iqgS9SfJuHcYYz8530+wOAHFuLcYWD+
vf09K1lVlncxPz8//+LRvf+a2vv+FIz8On6GDzBg4kzgX0/+vy/zKywW4/Xso5kVnHusZd/hU0a7
HeBqrABgMlZcPJQ07zAOZ583tqiv5dCXXx7Nv876BPQO7Q9ob2XQ8M3Hlwtlx352lFaUlHGsnJWr
WLmaZVnCAs4KY9HJi6ExfWGuYGzVoNRUcN1RVK6SM5RzP41SCqed4xy8y8EJTkE4ekzbu5dXUFAr
s1DjFqzYULxq/p+fWSJ+HzUje+UfmldDrlQBkLMIiRm3bFTK/Ilz5wOrEp6KXbh5/B0bLlXNdpiA
Afhg/OxpAIDEvZ9ODJYBkCtr5yDYgH9efU/9zAuT7t4rJmw48nVU49G2gJjhywYkzxj9JDC3yjRl
3JLXku1rZoyeLR5d89WHLw71MNQ24tGH8fZbcQkTI9nWCqrXpBY9oJTL4B4iazQANWz6pOgVR7F4
ypAbLyXh1ahnUCtnyDN/S8On42cuXCF+n77ANGJ01c+J055BbXWWRKoAu+OHOa+KRsOAiWnPDQQU
k55bEL01cfgdqRgQl/jy2AWvvzU2vFvWwoh3r74X/sY329enhk5fmjb5/PhnLrvaZFiZh3IboBsw
oShNvvKd799djznfvjH9k6Vb9R5eWbvRPfDcvXOfw9b3Y3qlrkn78qWh2gdembHgkff7bQWmP7Xh
5cz5GZ7N58lQ3aQu1G9Ft5Aux07l9o8aycpVTUaTdu7cSQhpMrIHgBDidFivXckddmdQZ6jAFR5d
/sLiuq/Tvj6+sg8LcNDVd1nq8Yl+8sgW092PT97wAgCMXLgxd+ko8ciIqU9iz7/m3NsXQNfoMSOR
gFcnh3tqpBU6nEuYdXeC++uTSze+O/+hcC0AqPo8dOZ75/z7XxgqFoBp+wtjumj7vrh00l+W/6n3
8v7fF2SMf+a9/ikv3D9wA/rP/+fSacvfmPdgWJ+MF3o1LKJWedZ44oVZL7gTX93ySZ9b8C5NLTe7
fjnH8Qajpazc6LxeSg0VqKhQ1lR6K3kZywBwcIIyNCD4zj4AHAZz4Y85Grb+MYcCDitvIFr4+FE/
fyYgUB8YEBTo4+WlumGUhLmiyuwC5IqQLm1Z2oc3G21yrVbFgrNYzFD4ahWc3QmVgoXTYHSyWq2u
ZU9tt1hsnEzno24hC28w2liVWqeS1ea32TherdWq2un9b1RQaxiO7/Qbn5Ry+puHe7U2pN4GJWwG
O9+wOpzdZrY3rY7dYrNx8PVp8CzF2QwWd4rBaBHzc3aw7ruZ37F0atzBp8qOPBRQL6S1+nostxbe
DplbsD1vZuBCc8J722eHtVoxD/dAbX1RpwNnt5ntjevVEs0MJfGbwHH87u+P+wXFRA8Z12RCfuLE
iQD27t3bMD8hhGGY7JP7q0ozH7h/aEs7J3zy2X8eeSq+7fNPdovRYrFzrKpLF582/X45u9FiB6v1
0f5Kqx9xRqOFZVVabb0/sVuMdqh8xBTOYrTAx0cLwGg0qrQ+rbRXnN1isXOt52kOIUShUHy1edmc
J+7rWB1u1jQyGaPXaZQKuSPAx24Pt1odtgu5plNHvbuoAcgJsV0pK5WxQXd0u/bTeRUhAl9/salA
qyqs8kce1nqpVSq5SqlQKuVKZZvetdV18WvPE6tM5+N2Y6xW6yt+cE+NKnx9btCgN7rCnoT7+jTy
kSqtumNPGDcqqBWqPxqfhFHP3X+TzgmASu3bWAm2WQo81pFV+9aOQ9QaxPJB4KMLRo1dNjr02vbk
LWex7KvRAY2EtFZfj+W6sVwaFvL38FnTYkKc215PzcbwjAfDWq0VPN4DQNP6tlZoE9qeU+LXhGVl
AyJ7HD992tcvqHvYgNZjxkTndK3gbOGV00MH92h9Wx9xtaI2+ieV1kfVrlUwWZWPz696A7E+Pk0H
BlXaBkWy2rrjzXM2ldXozLYiGrDdpzUs92ZOFjVQKuUKBeslKHlecDhcRb8IcpZQ3j2NpGBQfeGa
If+6BgIIaONzCccH+Wm9/bxZVsYw5Obr8z8Kx0d/vjQjatBtNsqkffjI6/pjV66V1/Sd/lzGH0eO
6ttJ69hqe2z6dunhM9erqxVzPlwZFzekp7RA7v8wYT2DDEZLzun9ALqHDaC1pKenAxCD3GoXxyPX
Cs7mnN7fO8w7rGdrg3satdJYdV2j9bv5ILT/TcSW3Fh1XaPu+A5Knbw/ocPhuvzvXaqC86yapRQ2
q1MQoNUpBApxDw1BEExGh8ZLrlCyAAylNcF/ndMlvLvkliQkJDqM0+k6nZ2fd6U6tMegyAHDVWpt
E6dCCLHbLLlnjxZdzYro6T04OlyhaG2o5uDhHJW+/4BB48WVFCQX1S7E9lwmk53NSrObzo0ZGdUx
OZ089EkpdRhNKtDqSmuNjdLuPYhKTYsvaXUKClCKajNvvePOmrxL8gqDVqckgMNgomFU8k8SEhId
RqGQD44O1+uv/3Lx5Pf5Z7r1uKNrSC9fv64ajd5qNRmqrl8vvlx49Re9l/POqNBeYV1bd04AwnoE
5Zw/cxbo1mOg3qcdu8JLiJiMZYVXz5SXnInq16GIYgCd7p8EQXCZzCVGgYkcoIzsp/L1Fji++utC
pcMllzMmg90xcIjvXUNcgwfZiwqrcs6x1VddFrMg0JtbRVBCQuJ/HYVC3rtXSI9uAflXSkuuXzx1
9LixusZmc6rVCh9vr8AAnyFR/uE9gxQKeevTTiKhIf6CIBRcPZvxy2GrrRNXzf9fQaNWdg3yHXBH
UGhI0zjkttPJ43s2m6Pw5BmHbxetl0qv0yiVcofDVXTyjGPvbm9vVZlTHvzUzMAgX0ppjdVRXV0j
1Jj1SkVQ37C23DESEhISN4TjeI6rW/CIMgxhGEYmY1hW1q52huN4l4vjOF5oeUMGiZZgGMKyMrmc
vZm2vZP7T3I5GxTVjxAoFHK5XEYIUShY/wF9C7KzjYVXdX8c79/FW6NREkLUaqVep3a5fOVymbS/
u4SERGfRXj/0a8uR6DCd7J9kMkarVTUMw2NZmbfeK+De8VUHf+wyoK9GoxTf9GZZmUzGqNUQ92jp
XDUkJCQkJH7vdPL4nkd4nrdY7Fabw1uvUauVkjeSkJCQkLghv9Kry42QyWRarUqjUcpkjOScJCQk
JCTawq3wTwBkMplMGsiVkJCQkGgzUli3hISEhMTtiOSfJCQkJCRuR9j3k3b91jpISEhISEg0RVr6
UEJCQkLidkQa35OQkJCQuB2R/JOEhISExO2I5J8kJCQkJG5HJP8kISEhIXE7IvknCQkJCYnbEck/
SUhISEjcjkj+SUJCQkLidkTyTxISEhIStyOSf5KQkJCQuB2R/JOEhISExO2I5J8kJCQkJG5HJP8k
ISEhIXE7IvknCQkJCYnbEck/SUhISEjcjkj+SUJCQkLidkTyTxISEhIStyOSf5KQkJCQuB2R/JOE
hISExO2I5J8kJCQkJG5H2FtUjvPShvjkUgXgrEsKmvHS/N7qW1K6/eRMdcyWuE2m7U/pOl1s47QN
mVXzhvh2YiHgyo/ty6zx7TN6WMStuloSEhI3jcM69W9VkxYGz+sjExNyd13v95PC9E8/nK/Qr0fV
+10athT2fIP6LXvmm8FDNB0pzWa1nDr+I+dyMAQApaAACAihhBIAIIQQUEopwxBCiCBAAAillIIy
AAUD9zkApVSUShqVUZta+42K/xJCxM8CKCggUApKQRRq7V1/GKnWeHWkPgBunX8SHZMTWl9fOQCg
xqWR3bKyATMAk+NXEYvo2LhwPQDAlG9SyjvdpNeXTd0+DtUAACAASURBVJqUHp1oy3pR8k8SEr8j
TICDq//qcglwAIA6VJv2FJo8K7MAQF0dKshuq/np4J7+d/QGIQChoKKvAQgViIyIgDCUUojuhIKh
lFJKCQUFJSAUlDIMqfUwhIBSuH0XgAZeq+Hn+g/uExlQSikFAaXkwA87xkyYovHSdqhat9A/KQD4
jlz44vg6t+QsPrbho1P6XmHywlOVYY/Mnxhuzj/29bf7Cy1OQNt/bNyfx/Tmi499vuOU3L8rW5l3
xYDeI+6PYi/tzjgPr8CRU/4yLFwH8NdOn7hQzfUdMry7rkWXpwOgb5JmP7lt3d9XJ6cDcdHjZr+0
/MGoAHvejqcXp3QfN1J9/IMLI7d8Pq/PsS/eXLZmRXo2Yh9f+Oyi5Q8PCWgqNm7Rf7Y/1cSOV/Zv
XLDog3yEz1k09XradnXcG688HOkxMW//xsWLPkjNRtzjDy9e849RIapGOox4c+SFD9IBZC9YsK5v
4osTVTd5GSQkJG4hSra+CyKXuz9z1c6dZzB0qEoHXDleNWuzNV3FLgzlAUZ8fDfkm5d+VJ1UjdgI
deJf/aL0xJPsek6fONL/jr5i/4aCgoCAoaBir4nW9oMoZUAAkDqXAwBih4sQ0XWBEEKZBj2w+qx1
/ST3VwDE3Vmr73oBFGAII0AgBP0je584emj0+EkdMt4t9E8AUFNwODNTxXEApwwccAcMpYbS0sxS
ANpuPF967J3P9gLQBgU5S0vPHUg2YfZjPQyFpaUoLYVCAafz3IFvzgEKBZyGwr2f7e396jR/WDNT
92YBVUHR3SPbMXpnOPRmzLQVQOzcuaFHkxLitlRk2z4Ps5ZsSd2C1C0AYoe6zCeThs9YEf34sjUP
Vy5ZkZC+xXrJtbHpKFvq9vh1JqXdDsCBbk/87bGgS1+EjZ8PIDoWC2bNAhA3dIU910Oi4di63uMX
ALGPP44tW1akbik8b9sY2lCHwZayrHyxnIv5Fhcg+ScJid8LemBrutH/GuN0QSHH+UweSgBwWZwJ
J8iKWTDkVIZttj0+Qn+0Pz/34xr3aVWWsW9V+9+lyx7LfvmRIXplZdnbXQJaKQZw2GsoAghhQHnC
EIAAhEB0J3XuSXRUhAKUEAhCnedxJ/Iup8PhdDgEKqjUGrlSxbJygRfg7nJBdEJuF0UIdfeZAIaC
UgjiGCGp9W2EEoDC6bR22IC31j85Cw/sKnR/7u//0l0AAG2fGU/9KdxHffWHfQDCJ8x+4p7ufGVm
wvpdhT9lVvdQAdD2f2jxtIFnUt7+5pylf9yCaYOtn6z8qBAl5Tb4qzWDJo5VGbjeXds3amtT9Fuz
bFngpDlxERWrjm7JzjZb67rWscsytyyLDtSd/+RdAP6armOmPpwSOMTp38fTfFnqigWptZ+j73vm
MdPBrwE8vinz86eG5O1Y3jsuHsBFD4mOPesXAFi156NlE/TjEThrS9J/zr0xS95IB3ZBnwvy6C1x
G75792HJOUlI/I7QAalZ1spf3L2fbDsQCABgCQAWuHjegUDtphl6Fjj8vKBf7wCQc9CcDWXRLO8Q
oM8LXPxr5iMl9MHg1rpQDABxSA0EAgghtR0aCojzTYQQQokAgAEjUEEAET0ICDiXq/Ta1TOnTpRd
uybwLo1OK1epdN4+/QbHBIZ0l7FySikBT8EAonDUOjXA3X9yJ9f1rwgBoYSC3KDr1yq31j8pwh96
JNYLHHie1YXCWgDAd8Ddvf3VgLOszADAL6gLAJnOWw7AmVfqGABArlMB8NJ5ARadVglownxRaBC1
l4UPGxPetvIbDAUjsFd347nVS+Lj61LktR/ipj86JEQHoN+UGXHzt6QmLRieBACPr0qZ9HAzobFr
Ln3ztJ4TZbO+Ovt3ufkARsb0BxAa3hMA4Mj3kMiLAlZM6r2iVpi9mQ4wu92mTeo8SUj8rigCEhcG
v1gbH5Hz7+Loww2PC5cvC9H9FO5WuH4kkACO0OcK6/IVGAUE32i+nrpDFQBAoCDuTg9DxHE40WMR
d+cHhEDgQRjAZbNezDqZdybHZKi0m6sZnufsFhehjnLliaryvgPvDB8QrdB4CQJDaJPy3H0ldwer
ziMSQqk4oQUCwpCOR4nfWv/kFdg3vLui9ptNHLjixGZa4e/nhXwnxzV0IsE60Wk0SOMAgG84i8jz
TqcTCrXihgEXDWrL7fvn8PhUrErJ/sdU/6T7QhekN8jnqHMJYYv3pM5WaJ1n9m35JH7LimlDHzC9
OKTxKKLeO9TXt6Hn6BYeDmTn5pciqqfNKgZlKD0lwmwGgA1Hix7rry67eOGK0RnSXYfrjXSodZvK
WxPqKCEh0ZlwrR10Atk17la/LrLK5RKgUpet9VM5qJzjfjrjiup7w7bNPaZHRe8gRjyIKYAYsEAI
QyihlAoQwycoJQznchkKr8pMFVHdApmQQGtNDVx2uZyl4CFjrBytKcorkpPgvgMUGm/wXN0UlOgL
iRhxAdTPUtX2lyhqowMhtN9qbm71+098y4eCevcCkLV1066DB7/YkGIAFP2jg2+soO2HhPi1a+P3
XLLdIGPq/JHjRAaRQfNzq8VU4/Gv1y9IB6Cr70DVcnHL9NGT4hL2Xe8VO2lEdDSALt7NMqXOHzZu
XJ3geZtzut85AkBC3IPzFs3zG75AzOUpUTNm6uMAPli/JT09dXHM8PHjR580NbudXTADSN3+1f7c
Vm91CQmJ3xfMPSPkOGHcls/D4fzXVqs4UdS9jxx2+w+XeZ0Gx/dWjE82Vd5YFCVE7LcIlIqDa4RS
0TEQhpFBnDeilABU7EQRhnAOV0WxylQZqlF1VauD1MowX++evn5d1BpfpcqXlQep1V0VLFN+vfJi
rtNkYGQsIUSMuSAMISAAQ4iMYWpjK0ThhKJ+Cswd3d4xfvuI5drOLXSRk2aMrEo+nJ954AAARbdh
s/88EFcLG+YBwMoAd6fC3RNTewEWd3rrZKfX9ZLCo97dgE3zV0wbDcQ9Hhe9JXVLdsEHfURNlO5M
0bOSFu4dnhA/IyYeAOKWpUyK8DDG1kAs9CZXwKiXzqfi2VeWJCUgLhap6QDgMTHyqXUp18zTViyJ
2wIAq1LPPxahMuc00gG6ruPikJqaOmv8iDga2amvVklISPyK6AFlwyZWTlD3u1YBQM/R/sknSqe9
VQIgursMIJAh4E7/PSNKJyVcnwEA2PR818gbNm7iC0cEDEMEt2cACAUD0YuIIeMgIEQABWEYh9Vm
Ly0kVaWMoYrheIaFXKXkIHAcCAXlBMrxHO8QAFbhECArMFazAUER/QbKGEYATygIU9d5IqKLghgU
URfTVxvf12EDNooXvB3gbUajlYdM4+/z6w9o2Q3lZk4XEND6vI6hvJwDoPIN0LXJnRcf+mLLkULv
XhOefHhIwbbl/abFx645uuXuvOaJ+18aBsBuNpjtHKsL8G1ZD7vdDpZVsb/984SEhETnYqhycSwT
oG/khewmroqDzptt+a2Zeg79sCMiPIyQBp7B3XsBIUzt6J8Y30AZwlRVlBeey+mhlsFkpA6nUsn6
BPmovLQ1BpPFWG01WTiHned4nuOcLicnY2Rab6rV/fzLheCoIbHjJnLUBaHWB1KhrlDxhSqx9Lph
wLzLBeM8zNu3iduuvZOpffxv2UyLyvcGrgkA4BvQemxnU/wCnEuWLAEw350Q/exD/f1c55snurXQ
+apuFBivUkmxERIS/534+jWbNQBUejaknXJq4yPc4XQNI+fEz0QAiMxorv5pz87B3YJJDXU5BAKG
sAoXx9sNBt7Bu1ycQCkvgBeoAIEHx3HUVWNmGVn/0G47UlO9vH2HDb2bFzgKSqnQ5O2oun8BUAqG
YQjp+EoMt51/+i9AFfmUqSgm/T8/FZgcUIbc95epkb4s4DFRQkJConMg9aF6bv9Eat+6rfNVlKFn
jx/zgaBlWJfdAdaLkctdnMNYYaECD4FyLhfHCRwvCKAcz7vA81SgLjtfU6319ovq2SP1yy2Rd/TT
emndYXsCgPoljlDrqCilABEESm4iwlxqIn8VdCFRDz4V1ZZECQkJiZuHNAicI/XhfHWegxBAIMRs
MlhKiqKDuzrtdhmjBKsmDONyuqhAZJBRQaCCu+sjCAIvUAgMBB6EF5wOu9kU0S34zOX8nzIO3v/A
ZCoIoAwRX81FfVAfRZ2jgkB5SluJirsB0vrlEhISEr93SIM/gFB3MB2pW4RI7O2QoitX1QxklFBC
BJkchBE4joCykMkICAFDZBB4BhQCQ4iMAUMIQ0Ep73I5baB8RLfg00d/NhirAYZSgRJaGxsoLlRR
F6/HUFo3+9VBJP8kISEh8V+CeyHY2sA3t38CQCCACgKtKiv1UrCUdzFETgCGUpZQViaTsTKGIQLP
8RxPKSGEYRkZAxAQGSNjCEMIIVQQOK6Lj95Ycb342lWGIQLQcNEjsWhRESq+aSUw9CYCzDvJPzlt
lZWllZVG542zSkjcXtjN9t/2xbLfXAGJ/xpq/UTt20hiEB0hAhUoFRx2G2ezeilUgsAwjExGGJmM
IUQmUMJxsNU4HHYnFcBzlOcpx/NiTDpDWZZRKGRyGWEoT729vLrovUpLitxrJgEAI74IVTuo6J70
YhgCIhDS8RDxTvBP+T+mrIxfu379hvXrE+NXvr33TGlLOW35aStXrtyQlt84ce/KlSvf3nWpHUXy
xtzMzNO5xW0d17TnzCSNGDRz9aFi+41PrMWcs5EQQsi4YwbDyUMnDZ3TnJg3DiKEkKnrTjY7ZNg4
lRCyqO6NXPPJtYSsNTTOZM/dTMjUk+ZOUcaTfp4K7Uw4tzFvqiDuZq6IYfO8QWq9+p1jtYXflLTO
UEBCoiPUTj7Vrt7a8KtABTGZ4zilTCaXsYRVMgxLiIyC8CA2h2A22+02jnNRl5O3OxwOF2fjOBvP
2Sh1AJw4VkhYQoiCZX202iuXL3Mu8XdC6wYSazVhGrium+Jm4yP44oOf7TsHhW//qL5qW1HmucJj
32zQBSy7J0jhKbsLgLPxDicyTUA3X1+9r9JT/pYw7N61y6KI6b8spG2hiy4zsDDl6PN3ertcgLX4
s1njR0/yNmW92OYFzx3AqgLTP0LV5+SjYzJttDOC73RzMk194kcuauYouSuH5qcCSNiRuTxyWAAA
dfiDaWkeN4wxdWzDmLbgsdBOJT9mdEymjUbfVEFuIR25IlzhZ0nZq9KKXhpW997zTUjrAB4UkJDo
APUhCfUvxRJQAkoFKlAKSggReF5FWLkMMpZ1ujiDpcpkMpWWlsmAQJ23SkFACEuJ0+lwCnZLjaPM
YCwxGllWptUquvj4BPr6qzRqXibr4qOvsFmt1hqNVtfw7dvaWIyGI36/6fxTxbUiAL5RU6ZNnjh5
2pwZw7oBCrOVdxYf2/D2upRjxQCcxcc+eXtdyo/XxFMMZ/d/9sm6+Pj4T7YfMwMyVqn38lKrZACK
T+9dFx+/cmX8ug0pZyrdg4XG/GOfrIuPj49/e91nB8+Ugi/dm7zTAsCZ+fmuTCf4a6ePpR388Zq5
td6UCQi/Y1BERGRkZGTkkHGL1ixE9tkiOwAYcvfOG0cIIePmrctxPznb969btHpHXmMZ3n7qovj7
YgDEDFuUY8aV/RvHEfeJuQbY87bNm7d24+qZhBAybtGhK3YA9rxtM+et+2LjIkLIoJlr9x/bsWgc
IYTM23iIA1hWF+Dt31zbzK0JeHxN4lws+fSgqBBXdWHnjxfEFZzc5Q6a+Y933wX0DV+d8KgDgNwd
60RVB01dfqyYAwCufMfaeeJjzqLNh+yeUtyFclfWzRy3du8VUVTx/rXj5m02eLZbPR6ONpHP5a2u
Nebpq+7atW4uDxVpICTHfAOVrhza7D535tocAweYt/1jQTqwYtGzO/LsAJpIa8v1vaHlm6tkz9s2
c9HGbZsXETL5zQX1CjRTr2HOqUey2mkZtzHXfrFxOSGEkKnbct1dtCb1auEnIPH7QlzZSEBtgET9
+B51R0dQnvJUYBUKgTBVpuqsczkHDh/c9f1/vj+QcfDnY6fOnb9WVGoy1VisZmtNdWVZWWHx9etl
5ZZqS2mZsey6oay49GpxUY3dDkq0ao2Pj7fbE7kX+qt/ObeuL+XuQt3E+kY365/0gX4ADJmfrfvk
i7QfM2V3PvTqq8smhqt5h6HUYrhabgXAWw2FFsNVQ+32tZbC/LIap9NZmLU3aXuu01BwrrDwlxKr
OXfXR6nHDE5FUJDCUHrum/WfX3OCLz2W+NneQoNT4aWwGPIPfPPp6Uqnudy9UYqxys7Dmpm69/CB
fUeLWttlRA9UG0s5u9lsNhvKc79NTkDc3aEqoHz/2H6TLsamZJ/PGH5xQfTYd8oBwHV1f0J6QXVT
KWzg1JcSoxGduPoRn7zNYePn99mQdj47NTRpQb/1h1zWyqSkJfMvjDx/KXMNEkaHLcvj4LJWbkla
MGNPcEZGSvSWJeOHx6mf2JOWsipp/ugtuXaIPcomcHmfLklfNvfpWbPXIOmDTDMAuKpzE1YUcIDh
2Lqw8fND16QeXT9+f1J2k1M96sDlfdEvbsGg5IyCS5lzdPHDn91iB8oz3o1bUron+1J2WmLCrNGr
Dhmap7gLZUP7dklfsjbdDADm/7y2JL1bD1/PdqvF09Gm8o8o6owZ5HTXrnVzeahIgyvSzdKaSubc
zWGjZ/XZkFZw6ejDRUui/eKLobtzylQgOnH14kGBbMeub+uW92gHl7VyS8L8abPyE5P/NnaqW4He
xuRm6jXM+WJX2k7LuI25ZMZWddrRjDVxqdOmf24GzDlN69XCT0DidwWFIAjU7SIoT3lO4HleoEKd
56IAWCJjZSzPC9XVNQqVLrxHRFSf3tE9Q7qolHaTparSIJOzcqXcwXHVxmrKO9UsG6jXR4V3HdA3
tGu3roxSYXLaKYVcoZQr5IIgoN4l1XvEuiSBCrXbIXaQmx3FUIffM7F/wd5zpYbCi4cLLx7eByjC
Zzw/IxRA3dLbsgafAXQb+9KcMchPW/vZYUvWybJBfgDkcJ08kAmg/+RH/zxYc+CjxMOlhVlXzdyl
YwCCRj4xf3x47q5PtmaWVdZ0mbbwkQ2vfVbqO+yFJ+5RgG/L/k86YMXosBUNUtYcjdMBOd+uy8aq
olceDgH6bEqJD5t25MrfHuype2o7fcqTmKgJsf7YPvK+YeXr5iJ201vzxumAdzISNQdqHHAAc89v
mhfJInJrWnLg+N3Zq2bJAUQf/fylYTp4JcZu2f/XVU9NZLnQOKwwWT3vmGHI/CYJcZlDfXWYEIcl
X6VfGfZgT8hVEDeMObYdccmbXnqQBQ5nmvQx2xuf7UGHZ8OHpKYejX1wmNpuGBgVi2STDai8eg3Q
Aep+454tyh5WqUdletMUmMRC2XtmJiLh3dOGp0bh9LvpSP5oRM63j3iym/t28mjVvk1L1EaFuo3p
c/EY6u/Fls3loSL1V6TwX1NbUencjncRl/z+vHEs8Mo3Gdv8Rv8nd+FTo2NjsX3kH0fV5mr39W2w
mL2Ho7HHPdghFgCi06q2j/MFuABRAfM7zzdX76EGOc05F9tpGdGe0RnfvDLKFyNWb1gSveei+UXs
ebdJvU58u6EVu0n82mzfvv3kyZMM02JXQRCEefPmhYaGtiKE5wVBoACVMQyFQN0bBxJCKV8bMQEQ
XuBdHOelUOq8fVRKB+XVGsYlcxgt5upqq0Xt521xcbzDaTBWWyErMZhLrperNDo/zjuQdwXoBKXO
W2BlZpvNJWdBiNPpEKeZKBHEXlrDoAyIr2EJN7M8bCe8n6sbNm3+XTZjcVHh5Uvns06dMzjzUw/m
PzugxRN8Q3uoAYT2CsLhUpQYHX4A6tZgP7fro3O73Dk5AHIFgLBeXQFETp7z6mQAgM09lOcAFG3b
/8kMrNpz/vlh/hwHl+ny+j8PX7J+z4vDHhM9Vyip91wFlTb0bHkqhHMBcLnMp/dmx06PEfMFjHpx
4yiYcy4gekioaFGdT7i7Bg5gRl8dAMiB6HGRLADOZWq5gENfJQPZMeray/rp3lUPzqs9ar98PD16
3Fvuyyb3NGnXTAeWlZekL9PH1S5iGzudBSIfemnV9uhJ0VsAxM5NfOu1mKhmKajVUjfkgYVYsOdU
eaTz22ysujdCdX1f63bzcPTB5vLdxmyofWvm8liROiHy1i6leL2i3HZT+4QDZVbOfa4N9XNf7b6+
rVne890lB+DvwzYoztaCeg1zdsAycABzBvsC7m66CTAfb1avnI3J7fsJSHQqDMP06NFDo9GQRisD
ud+rpZRWVlaSGy3BwFNBoJQQRgCB4N4zl4AKhAhwb6dBCDWbzS6ecynldmI1VZZmnz2XU1hWaqrW
MpS3u1xeei8vw9hBfW3WihOXrhhNjtIazuyyl5Wbe/npIrXyiB6OgGAIXlTO6DmbjXe5BEYglBAw
ILU9J4LaBWIpYQjt+N4awM2P713atW7lypXJ2Y7uvQeOmTht/rQYoOk+FZyj0Ui9yy4O9PFOoH6H
J8DmBIBh059/6aW/PT1jelzcQzFdNLzNCcBc4wBQenrvZ5+lZBbb4A6KcDfPPO+02Zytx/KZAO/A
UF/fgICAgJCIYY8+G4vsChvgchQhOrHM5TKZbLaqgrQ9GY9G3/iXKZfLg/sg/Yp7IMRwctvajYcc
ALLrhwRNQK37V4n/c6HB/oMtYc5MSMhelpJxPjs7O/v80ZRlSJ3/Y3F9O+gEsqtratXwJKGZDrnf
LJ6f0CejoMxFadGehah0ADBXyR/7yOYylWVnpPRJWjBrU3bzlAZCIx5ZExu/adOmDQlxm6YF3Mhu
Ho+2JL9ZLVo0l8eK1AlpVSV5cB+klxlr9bPmA4GaFh/O2nl9W7R8m++uNqrXEct4KKhxvSwd+glI
dBYqlUqj0SiVSqVSqVKp6j6oVCq1Wq3X6/39/W+8/GbtqJog0Po/SgSBUgqhtkfDuZxanmNtNc5q
44kTpyqqDEqV2lvjFaTW+mu8vL3U4V0DfbVewT6+gVq1r5fcXyPv76McH+QzxM9LywpFRdeNFeWc
3aykrvKKMs7JyQhLSe3S5fW7INatEktJg+5UB7hZ/9QlrAeA/L0bPtm+N21vyoaUTABevu6hNkPm
d9vTdiVtzWp4iiVr62fbd33xaYoBQPgdtTs8KQcMCAJw6sCh7OyftyVvTU395rKV79ItGMC5b75K
O7h3a+qx/PxznEwBHk4AhrOHTl/j277/U4OnXZcD4sr33e+MRfYnP5w36HQ4/vms8ZPergQA+7HN
qzfuzfMgwwUgPfei+a4/LUT8oh25Bs6c+2bMtCVXoIQSWBK/LRcw7123Kh2P39e/3b/zvO8/Tcfc
OVNHRUZFRUVFDpv6xFxgw3/O1x5X3TNtLlY8vy3XAPuVf70+H9A3FuBBB5cDgH+P0ACu+NjKSQnw
hx0491m/3hOSytQBUaPGj3kc8JTSkJiHnsWWJUtSo198IBIt2s2Nx6Me5LuN2db5Do8VqRPSqkqq
QQ8sxIrnd+QaAPOO+LnZWBgb6enqdPz6ejjaikqN5x1bU68t8ZmeLeOhcqrm9erd6qW8vaF7N5Vt
y2/2aOqwznyukNT/lWw83pLDbhHzxSry3PUcB8znK8hzFe0I/+f5k6eshjav6XPfffc99thjDz30
0J8b06tXr6CgIG9v77vuusvPz691IQJA4e6sUAoKQkEEcW/bugXFGZncy5uzOwRzNeuoGdSv1/jh
g0f29IsN1EeF+owaEjYozL9HcFeHS1AAkd2CQ/01g3oF9wv2jgxU9/RVRPfrER3ZXcPyrOBSUCFA
o4GtBhQyAQJDKKh7vfSG22lQQMDNhJnf7Piez8ApT1S7vtp3rjDrmLgdcbeYuJn3hCjgO6HP2X0X
DVmHMxXNisrPygQAbZ8npsXg+l4xsfv4GROqNu07l7V3LwD0nzh7TIgCIZMnXyzZda708IFSAP0n
Pz0sSAb49vJFpsFwODXzD4Pvb8P+T3J9Yw26DoxF9vz0K08+OOofe9ZkTooOdG+1klkWyQJwnf5s
xQdTH5g3sZEUDoDae3g0ZkRPOGo6kLIsK66fHwBEL8z8x90oPAcgflo/ccf4xLSiSBXMAKJrlWig
T2gTi7gxH/ogKXpVRkTdETZy+qro8Z/9ZIxxy+n54GvJcydM6+cHIPrxOI/bKjbRwT5hdiziwuTx
ABYum4v4BRPWjcyckxa3YnyoXNwp8fG0gv4x8qYpMB2uU56NGLMmFktClwwNAIAAz3Zz4/Eo16xE
qItEY+4/MqeuoFbM1cdTRbKerbsix1pRqeeDK5IX7ndfL8SmZK/o2cz6QLuvb+uWhyc7mAFAr2l8
1Tyq1zRnOy1zOLb+FACAXi5HyMQVTeoV4Du0FbvdthjKHadOmiadcCYO93DUDMx90Pel/jIXR8/8
VD1tc3muOeDdce16iQWAYOWhDtWmPdWulx8cMR9XZb6j8e34st24cOFCZWWlTqdTqVR33HHHDfNT
EAoIoESgIGJsuXtTKBBG/B8RBG+HgyhUrODqFhQU3i20psbopXBagzQuJ085Wc/AcCXLCg4zJwh6
nb4fw9t5XqVSE1bBsoxKwShULAhxcqAC7eXllbflS9282brwCMrzYkh5g//cI4wCoWA6PgPVSfs/
8U6j0cwDCp2/rsGLTzazGUpN843XeafNbOV0PjoZYDyzPfGbLN+YGS9O7g3AaTNbHbxM49NQjtNs
NDt5mcbHR10vyul0QiZTyG7iLqjFbiiv4qBreYMnc846/eOwZb2oAgDObodKxQIwG8rtUAX46gCY
T67Tz1KasubYiw2sX2ubOTUkZ924x+1vZb00pF0KG8qLOVYnlttIz5Z04MzlZXaVX4BOBc5s5tQ6
FQvAXnyl1CXXBIXUbTPSPKU1Wrebp6PN5dcbs014rki9kNZVMpcXV1nhFxrS6k5eHbm+rRy94d3V
TvVa0tqjZVooqEG92qvk7QG/eWXJrDIASHw+ptzOjAAAIABJREFU+MV+jRsBh3Xc36qmLgx+sY87
/Vhy8fCfZJfWBYVeNT7yb3z+Nx8dYM93f5Zfq16Q4hriy80/wcFbkfFCl1HBjPlilT7BnvlmSP9K
07J9WDVLrwOuHK+atdmaDsRGqD/4q3+kHrkZlc9utaUD0YHKpGe7DPNzrn6lfEU1oFJkrw7sVmpe
+lF1UjViI9SJf/WL0reppTaZTDt27AgPD3c6nffcc49C4fFd0kbs2/3vsJ49xFWIKMTJK0IFQSCQ
EUJBqFxGC4vzv93mH95dRaHR6i2WmhpTBQMHJ0AQZCqtjpVrvGQEnKWkrMhgqqZOm4+PVuull8mU
DCNzOmxWh1WQs2Bgh5JVanOSvx0x7+mI6X9xOB0E7r15qdh9IxRwT4TlXS6Infindl5fN520vpFM
4ePv7+/fyDkBUOt0zZ0TAJlC7eOjkwGw5X7yTRaAuu6PQq3z8fFpIkeh8/H392/onAAoFIpOcU4A
VL4BIQGt/jJdQPYCNZl30gyArWtPdb4BDX7kdmRXc2ADQtronMxfzBsUvSC9bUM4jfANCGnunFrT
gdUFhAToVOLHupZLFdKzZ89Grqh5Smu0bjdPR5vLZ9vhnNBSReqFtK6SLiCkZ88btv4du74tHr3x
3dU+9VrS2qNlWiioUb3ap+TtgeypV7vRd/xiW8nSIHhl0B9UAF/hgMvOp+bx4pG6zy47n5Rnn1+q
OL/Ubw2co1+ryGswOueyOBNOuDjAfNEQttnaZ4LP+YX60Dxbv29quGvGflttgx70LVjqN0fpGP6B
0S5jp05WR4Mkxnl1s1rGvlV9sY8u++++wyts0Ssr2ziQvXv3br1eb7fbu3fv3hbnBLidg/h/SkEp
3DNQAqU8FQQKwlRdzL+aeZYH5QXKO3jCqLp0CQoK6KpVaVw1NSXXrtlrrJQQKpOrVWoFy1SbLZfO
Xyq7Xu50OCgVZEQmZ5UuDhwPCJQyjN5bX2M0CcTdYSNiFEb9u1A3s3Gum9/6flQEjBw2zKLr9od7
bhiC91ui7vNwZuZIQBPe8t6J6u4TUvagPXsrqscu2pQ5Dxr/PjevYUd1kGgrrdtWsvztjPgAKIe7
wat9qqn7hwLy8//wi5Qh8u9C8ivG3Rf4WfVj7ETMdvFnK7y93vqTVge881eX5rRg91alTpfHjvZS
O/iB3RmcFGyQRQ3T+Cc7Rg7zKvyuJBvKolneIUCfF7j418xHSuiDwTfoQuXk5Njt9tDQUJ7ne/Xq
1a5quhczAigVBEGMnCMCoQKIUoDLxSnUaobIOOriBN5Lo7eby0tLrhUVFhmMpp4Rvby8NJxArCab
3cmxKkW37t2KCwquXy/niVyn0SpZIrCEEIYDKwiEkSEgvLuXvw8FJQS1a5fX+6S6gblWQudvyG/t
n2T+wyZOvHG23xpWFzJkyA12s2QDhjzcvqqwIZE3EtpO2q+DRFtp3baS5W9rOIpmwxSNZgBV8lBx
LMaLaeFJmT9+lsYOde90HXCn/8Y7AaujJLtav7U2eOL/t3fucVGdd/7/POcyV2ZgQEBAA94aNXFM
JFlsUk3AbFe3qbitblI12ZA06LqpmvTX+DO/aBGzpZpahZ+/LJJtsCb4qkHbYGxldwUimhRixuiQ
CokXJAoKCAMzONdzzvP7Y2aQy3DxkkjM8/4nk3POc57nGZLznfNcvu9wInTXJUMEATwJ/3ax+xbn
OxTEDTbkoyhKVVVVUlKSz+e75557hv9kD+6O9adnVaiiBFZJEFBQAirLcuTYOHLfVAoKwrk9HkfX
lSuXLjac+cLW1RU9OsY4Kq6546rT4bA1X6C8ohCqEQiv1jc2Nzbb3ePG3hWu0xCRyKJAtRoCBZLk
U/FhcbGQofTagktAKQhHCKhCQRCMlDfC7Y5PDAaD8VVw7dmm/NdBF6AeH1hWTP3je44OBZpgAHBf
e4YOsDeRxI1CRWtg4M9W2/lmnfAPon15LV/5asx344SWj1oS9l0bzxJ5+HwKNNqWzZEaDxUl6aPP
fNO+M8R8hNVq1ev1YWFhkiSNHj16+H2lwTxC1J8tIjANBEpAQXgKmSriKJMxPqZL8UGiTqfUYetq
vNDYZr9KVapRcfEXLjQf+bRGUPMRahCOdHTa1RyNiwrTG41NVzrONFwcGxOj1vIqo16lkRUolCqC
VsMbjEQJ2KYCK8r9OZYIqOLPb3RTY3zM/8RgMO40jMDfPnfV1btqaq/uLLi86Cw2/TQiGv5JKXdJ
rSTZr7600wN1QFYEuHPK3YBcurezAsL3xwcCSY9XLu6BmSqc7NxfL0tO9+vbHWtawfkAcHfFCFLr
1Q1FXqjhBiADUOq+lMZOEuF2/8852aDDsdIrc4rsQy7ct1qtcXFxkiQNni2iP5QSRfFvflIUhQZW
0flnhgLmQEoEFSdooChumbZddba2t3U4XeCEMQljRsXEhkdFjZ84RVSFtTlczR2dooY3mvROBRIR
RsdEe2VvW5fdQyFRWfa5QUEIr9EaOFErc/4IFNwExQXeoAJ139z+J/b+xPjm4ra1OiQIpuivKds4
Y4RBBnqKG4CCgx0FBwEAGj5/yahl94sADFOM+WNdGdsvZwCp4b2K5Oy7krMPAHKfiZ2s9i/uJzp/
nNIAQPxDUcWfNaf/5hIAaFSWJ3WTOuXUQ/aklRcBrJ4u4qTrsXedJ3/Mz9RgybbmqtfjDj7UPG/b
5cDC/RdGTx709amlpYXjuIiIiLa2tvj46xv496eJIP6JIEJk2j2yR7juMMXznFrFeXmfz33V5boq
ewStilMJGlOUl/CCyTBGpabEZe9QKMer4OM4SQaRRQG8og0P63I5jcSgIrLk8wocB0UWdHp1ZDiV
FYAoikL8XkSlTzS6qWUSt2h9+fDxnsnPKbpmiFKFjZv26D89njzg9gK5o+7EWbc+btrkYao0QuE+
/pQ2+Z1eh1Kr7OUp/Wr1ryO/Hu/GLcBWV759a17Facxc8OwLmfPjB1g852448vqrWyoa7Qkzn/g/
v3huskkAIDVVr1+TU+VA6oKf/+KZWT2KSqUbf9G1KHthcJtnyOK96Vtk4JsPVMRdvbvg8EX/3lAP
Yh5d2atU6LODdb/fH251YdXrz6QIQGv1zidmZnTn88kvK1yWFrkjzbi8An3Itdh7ZMljMKitXYaG
N+kCkyaO2jbjfxL7FpO7VRaMwuCqH4ddcoNEG4NPI1lubacao2BQQ3LKkprX8ACo2wONmgBw26V2
CYZwwTDU8+vo0aMOhyMuLq6zs/ORRx65ri4dOvDH8eOSKCWKokhKIKkQJeA4jqOEcAAP3iu5Kv/q
utrW0dXV2NwKFe+1X+10uuPGJobrDSCU+qTOy41Ohx0QqeyRFTfUok+Rr7S3+yRFw+GuxBi9XsNz
vFobpha1xoi4xB+lc0SlcIHR0aDlPbgjmFJK6dlz59Pm/ei6utPNbRvfM8XGxsaa4O2qtxzYvtsy
8G5r258PHCj50/Fhb8cOjQPILCyzWi1+qiy53wm51soHQB0ybdBXhNS0P3LKHMuYBS+/vODUqvSE
J3eH3PkvNZWmJM3eq5v36qurx1YtnxL5b2clwF33bwkzc5D28vIFFRmzUzaW+wfWbU1ny3fnzFu/
rckpDVa8B/2LDHTzwYqg/b+XrCq95IHH4/G4PJ4+E9Ihzg7ZfQewuqjqzJna2trasqLsbRkz15c2
wV3z/MyMhPyyFrvd3n6+JNu4fE5Seav2h29Yrdba2qoiM7C2uPJMrdVqtS6cxIIToyfEFCl0BycA
AIVbkUCio4cITgAMRuFacALA89HRgkENAILOH5wAEE1g5BAaoxAfOXRwAnDp0qXIyEifzxcVFcK5
Mzg0GAy6J6IAkGs7dQkoqFpFJoxza3SgPC9JWlEQeeLzumtP1f7N+rczNZ+fPlZz+XRTS8Ply+e+
bDx74fKXza0Nl5sbGtuudHR1dRnCRFElUgXUR0FJ+D333fXDx4mooRzttvUClOMIxwX9hBSgN2Up
vE3jIqaU5cvnqgBvsyU//4Dt9If1ruSJWu+ZD/9SUlnbBZhMCSn/MD/lLk8P1VPcU48nXzlRuvfg
pzYvTLET0xal3xulAuQLJz75olP6zoyZYwf+r8AOzJs5e1rvnfG2utL/vWJeQQVSM3Nzf71imkmA
qIZ1T/aLR3O2vYPU1WWF2WmJBvfZvc9vb0ufXrcoo/6jT/55UwHe3rHYALjrdj+5NfC5bn/eivRV
FYA5fW3BG9kp8UKPUl/8e4ara8Gbv5o/AUBD6caMP00o2bHY/9R0tV0CMt9Y90w88HDlBePsY43S
4gn9/iyNHxVZkd2+Y5kJSLu/8s+Rsw/V/sb50YoCbGp5e2U0kFLVEjnzNesv0mZoHCUrJmaUDF18
wrTuB3eIIjW/D3lzd3ne2g+TXlg3P6Z/EbgvVyD9ja3rJvc+Gijy/c7+Zx1Ddd8OjJs2fcIEDYDJ
k9cW/uf6rdYL6xNqS4CSH6VFGwAY5q/bkm0xtLe54idPiwcg+cYBo+++b0LIDEYMRm+0sbriJbd5
b4AkSR6PR6vV2u3261oZ4YcSDoSj/nR7gRStxO95ByGUgIBQSnV3T6BqsfHwUY1BJwgqYtByzZf1
an14WDjn9ugjI3miOJ1X7R2dsiSqVJyg5tVhnCR5O7o8RoNeFHnqpVTgeYMxzny/yhAm+ST/uvJr
4iclsBWLUsoRKDc3vnfb3p/8+bBUsdPuMQGwnWl0OT4rKTp0ssurGhNjutpcX7rrD/WuXqqnzlCC
KAzb/3T88KHq6uojR44cOXKkpsExsPamIsf5vSpr5SbjtjlJ6wMOp24Nj3KlpOBKYH+fM/B5QPtO
oNTPp91VkbPuzzYAcJRuXl8RNfpa4lJdFFCwIW//8erS9S+sR+bDCaF+M0Q++GJZ5SJ/KdsXn1qB
xCgtAKTG+MfDTFMfSUXFsdMOwPDMe5S6LKnDKR4gRJEBbt5txgpRRGq+WIGSKWnTCSFpyzbXtAa+
J3+RkGeH7L4RcHe0Q3K73e6m4+9urcAPHhirmTJzKZAeM/2VzTvLq2uabInr3nu7e1gykNXbxzx7
jGEhROoWPqQb5p70rwin06nX6xVF8Xq9BsN1/67iQfwOd5kQhfSKCH5zLgHhCEclRR8fS6KjOKJV
QNQazZiE2Ol3J02ZHJ80JTEyIUalFnQazmjS6kwaMVzUxxi1Br1KFHU6NacSQXiOEKLRRn7nXl1E
uEQVQgIva93+p56KDUoVSuVuN8UNcNvmlYMVB8btJEheIX76JJ/B/Ojfxdn/VLCn3uv18GN7qJ4e
/Gt+DvoJosZO1A3T/1SwfF5B8F9Tcy256pBuHg+w+vyOZYlAyttVRcaZ3Q6noIbns2uNF4MdiRzQ
vuMv5a4rxIaMT1tXpgkn3qhA4RsPdjdMk3DvamDbqnR/21KfGxvy/xND4oy0RACO6t05M5fkILPo
4XjX+wcrUhf8JvDfsigagU5n6IdyqOKD/+kdNaFvbhrAjAUArrY6AJkLNi59teudF5eYYzrO018l
IiDTchw/FOLsUN03AGtmJ6zp/vf0TX98KB5C/JuNVQ++vn3Vmgx/vjtzZuGhHc9ED9olBmPEIsty
TEwMpVSv1+t0gz3KQqIoCg2MpPkH+LpfPCgBIdTv0yU8JUStjZ18t/1Ck8vj5AWOqrSSJLtdbodL
unT5SntLs8fl4Hgq8DDoNSpFApUhCiqB40RBlmWeF9ThkXH3TKOEI4rCUb9uyr8sI7hAwy8n9O/B
ujmB7m2LT93PUV+gHULE6CjnlcqT+948GjwlAPB2q54CH/oKoobtf9pkaX95hqn7SM2OAdw85nGB
XMGi2MPx063huUb3NNUA9p1rpTSTv78W2GNpmqb6oxVre2bOrilYsQ2rLS2vz4gW6va/MiU988hT
J2dda2aPLpwtXTFx3jtAdrFl7cIZAjA22VwRdG0AsAPmsQP+8upffFAM13XzQJkZL7W3/6vJZAAw
a39YQVJ6ac3aZcFRxJBnH6oYovsOYG2J9cUHjE4fAF1CYrQASI5Wh3b6yq1vr9xa6GhtPPbnHXMy
Ml79+1k7Fk4YolsMxojEZDI9/PDDN1yckuAq78CCOUp6SG0J8a+RgMJRTqamxDGGxAT3mbMKFKjU
HkXhJZ9AlHC9SgrTOWWJUrdOJxg0giB7eVFQRFGlIoJaJRCeCFp1WLjaaFCC+6sUQhBIWxGcAwMN
CqsIITxuwlB4m8b3fPBPQzZbDlTbAIy55y7Vif17Ttu8Ux97eu2rLySHBa/soXoKKYjCsP1PfX6Y
D+jmsXbP0IshHD8A4A7s72u97M8PPQz7TvzC3NSC/N8VFm5LzV3YM3N2fX0FMlNnRAsAJv/jT1Jh
PXXREaIDtiPpE+dZVxc1+ui6YHSJiInC+r/6N6+7z1srkGoaKIFaqOKDcx03D9JU/ZeyL4KNjzSZ
gSijOPjZIbtvB0aPS4qOT0xMTExMjPa3oLbwsZjI11sBQDBEJ6Y9k12YiqpzV4bRLQbjDoQowexG
BAhEJs6fToIQLvCcJxwIx3FUVGlGjR/nH6/jRbWXF6gghuv1SQkx90+f+ncPmO+79+5xY0ZHhBtE
tZoKPERO1GhEtUrQqDmVqvnSxROfnBAEngusy0Bgoov6R/vINZcuwU0KNm5TfOqq/r95eXl5W/IP
nAIw5tG0sSpZCqz2uvrF0f+ydAFQgUcP1dOVyaEEUbgO/1MvBnDzqIE16/fWSHCU562qQOYPgq42
37V/rCk53irZql+ak4MoNQa173SvYDOnr0DJ+jXvYEV6L+fBd6ano+Ct/XWtkuSofmd7BdIfmmSA
u2HHKxtLz15by1bz7pYKpG58NsVeW1NTU3P8eE2rG5MeeRpYs720Ae6Ggv+dgdQnvjPAG07I4oMz
wM0HNmMBbSe2LZq54kiTQ3K37s15wYql9yZououEPBu6+33oN5M05QfrgPXPb97f6pbcbltN6RsZ
FVj43etLVsZg3DEoCCSMAEC61+/1wx+mKDhdWLhKqyWiSHhRVOsgCqJWrdfrI4zG8HB9hMkQHq43
6rUaURREgdNpJJGnhPdQQqjitNt3vbWrs72D4zh/VYRSf1SiNLhakFJKafeivhvu120b3+uy+X+a
qyY9umjxI+MA3P1wSume6lOH9p2CKdakarY1NzS7Jo7toXr6ZShBFFzD8D/BCKjFXp0N6Sjy/3Tf
tsi8DQDMhZZ9E3oLewwzFuYvXZWRHJMBpAbXBgxo3+kh7xESH9mUijXIfSSxVzMmP5mbW5aUPiWw
Em5T2flpGsDd9kbO+iULX5gbfOvr6ARQkW6e2F0w12JfOeMZS/5fk+clrQeAzKr2ZT0GxsSeWxcH
KN4nEvQqopkc8uZ9zFi9ikxbnJt90Dw7wa9MTC2ybOol08oIdTZk93vQ/w8HQJiw0FqcbV6UXhKc
mMrMLVs9q3v6SewjbWQw7mwoKOUIQDkQ2i8yIZigjxCAcLJMz9d/6Z8ycksSB0J4Xks5xStD8kg+
l9frVnyyLFPKcVDxksgrFJCpAkkEBBX30ceffHjkr4/P/4GsUKLI17Y79QhFhBBFAcDdzPje174/
d3C8jg6nrIuI6JNTvqfqKaQg6oYJrb2RHK02t8YQsBX0Q7K12qAx9RrvGtq+0/QKSWgrPhNyjsQv
/jHGxgfVDO69C7Tn1ttfHsbGUkdrU7vTZ0xI/CqSKNzAzR22VrcLmpgBDEyhzvbr/vBw25qa7T5R
jIyMH+AvxWB8Kzj4/ntJSXcFowMJjK4R/1YkdG9I4gBO5G1tHUV5bySPiXXJPrfPK8kyBTWpw1SA
5L7qcXb5PE7J5+KhiBqVrBa9BBSUV6ggKWFqrlNS1rx98B///h/WZ68PjzRSSaJB7VNg2V7wnckv
+DhbXz9n3sIb69cIywujMvQNTf7DPSQoKq1Bdeu2KmhM0SESiQiG6OhBAoNgiu63UkwwRMcbgh/7
PpnddXufnLKoBJm1C0JP4F8rHChw+lxy8b8OL+tB37K3lBu4ucEUbQi1vmOQszfYBY0pPnHgmhiM
bw8BBROHwFwQCOECS72DynUKKlEBPv503bmj1R/fH/+PsiRJsuyTfB6v5LS7VYTIHpfk9SiSTCnl
Bai8MlUoxxORgEoyT6ms4hW3T8ORk7V1n31WlzhpnNGg16tVHA8qA4H8sBTwryonlNz44nKMuPh0
hyIYx87LLVyb/uPhmrM1015eN+2rbRODwbhToAollAA0+OIU3IREABCFcorC+SSZcmqVIFR9fOz0
5YsOr0ckHLyS5PX4JJ/slTpcbipLVKGEEA5UIJAVqlZAIStUEQCFUMVHOju6OIKWK1e+/LKRqtSS
1xMZFRURoY8IC9NrVYSQgFceFNRv3vjm+p++HQjxKctWptzuVjAYjDsWSikJLuumCGyHIuAAwesj
hKgUQnhBDdnTePGCw+W51HZlQlyCCOKlhMgyRxWR532K7E82IQiCKBIOVPFKvACeA+EoCPW5PZfb
Oyk4p9PZdqUtbtx4t8vX0nKlo6NDUZTIqMi4GFOYVsPzvP+Njguu8LsxvmXxSbLVWOuN48xfyVwN
g8Fg3A4U/6uKfxIIFOAILygKp1DCQa0QniOEQlFk5WqXw+XsEkEuXbo0MWEMx/EqIioCkTkvR7yE
UkWWCCDyEKgsEPBEURHCEwICRZZ9bvdlexchhHCc3e7gRZEQnuMIVRSX09ciXfG6XREREXq9RqdV
q0WBUOVmDFDfKv+TVL4+0pz8tkvLghODwbiTIAogU8jgOVELXsdxekHQc5yKQJAVKJQAhBM0XkV2
OLuMOk3bleauq128SiAKBE5Qa3RqrU4XpteH6TUakeepIHIiIQJHCOEoR0Cp5PM5PHKr3anTaHVq
rdvjU4k8JxCFEplSjVqgks/jdrvcrqtdzra2jg57l0eSQb6B+SNuA+6Gz1ybau0vT2ZrvRgMxh2E
QgkgCKJaFNWE4ySfolAoVAFBwKcLTuQFlYpXJIXnteHGcI5ILc3N8WPuEtRqRZIkUI4XCcfxCk8J
FHAEClUkv1qK46jskSXKtXZ5HG6qD4vwunyEU3Ecp1ABko+IhFLZK0lGXuBAZVlSFM7t9rrcHrtz
qL2WAzMy45OrLG/zUVvfoylLXp478SaW7mliRjlLpxgv1fq2DnedwqA4anYYzUetrre7t+y463Zr
pyzpcUlqYVXhMymJoUr3RrId/2v9uO/O+HrGHW+8nUEcxzcbk9FOXxaCX0LS6b7fBoPB+HoQRJ1O
H8HzoqJAkryKIlFKFIXz+CRZ8YHwWp2WJxzPUWOYenRcVEdreGx8RHPLRaNplF5vECQfkaksS5RQ
+DyS4uZEgeOpoPAclQmRCaEK4Zw+b1N7J9GFGU2jpM6rMXExBp3OLjq9Hh+lxOOWKAXh/e9LlOdB
oPC8IPluXI40Qsf3NBGmMJMpLLiqPMxkClOFaYdSswyO1PBfSwoqgG37La1DXz1cGp09JEc+nwMw
F1vOnD9z5kyttSjbmDEzo7pfoA1FffLs5PqvK+P2TbQzgHbc/LKy+cFF4d1fQq9vg8FgfD2oVBqO
ExWFer0+SQYFkSWff82EKKrCw42coOIFdZdLOn7qgt3Dq/W6iLgEXqBXmi9KiiSoBJVKVKs1giCC
41RarSCKPMcTjgfPE0GgvOgjYovd2ynxEaMTDBER+nDTvfdP1+vUKpUgyYrPp3i8EsfxHMcHEsIq
iiLL5Bvq1xgU7cNPr/z5ypU/ezIFAMJSfrZy5c/X/vyRsVpHffXvtuRs2LBhw4YtxYfPyAAgXzhR
XXb4wwuOIaK0Zc8bWLopNxNr3jrsDwTus3ufWrZ5945XCCGELNhbF3hCN5TvWEAImb5gc97GZcvy
GiQAsNWVLksjhJC0ZXk1tmuRpJ/McNzd5gmJEyZMmDxt8dP/DFTYXBKAuv15aYQQQqYveKW6SQrU
/uKOvTtfJOTv/zUtGUByyos1DjQc2Rm48qnN/orcZ/c+tSxv944X/QfLq/e/mEYIIct2HAkICfu1
zV23e8Gy3f50GD0/D9nOAWrv+y1J7V+8/+EX3RmlxN4f+t+EwWB8dQgCTxVFkRWqyAAhnEgp9Xnd
lCqCKAq8wBF4ZaW07MNd7350oUX2gVJ9+Pi7J/lcHQ5HJyGE54kocFq1SqfX6gxhOp1WrVbzvMDx
POFFhVN3uOQrTqqLHjsqbqw2LNw4Kq72zGWPRLRajSCKhBCfJBOO4zgOIBw4Ap4Szu2TtPrwG+7X
yIxPAboDjj/fqtxc/dtdpRe7vGGxsSp0nfqgaOfhC8P0P0E6+9aairWZz2c8uwkFb1gcgF/RVLBm
yR5tWVXlpvSSRU+87QAcNTuT5iw35B+0bF2wZtX6goLyyy4MLIvqT33FX8qPlJeXl+5+MWMJUnOT
44WhBFGrf7Im1wxz7sYnIxp2Js3OmJRfdv5M1cLGNebInKZAO1ctORhXWVlsfmfNnJnp2qcPlhVn
Fyyf/U6dO2Tbut1U6P158HY66gaqve+35Ous27b+fMjIE/ImDAbjq+PBB+8/Vfs3Svw6dwVEUIjg
9XopFLVarVBZ4PkvL7ZedXgjosJMkREqran2/OWoCVMi4yKdjmafz8ULRBQ4QhQSSPOqgCqcwHOC
inIq+1Vfc4dT0Zuix0+NiIzTGmNF3ajyo9bK6s80Wq1WrTYY9BER4QooJYRSRVIUynGyTM+dO/9o
atoN92tkzj/1xd/KLz/9FMC4x559+uGxcptl2/YDFz+ydDzyw+H4n2yWfQVItzxoMuCxdKz5Q0VD
ynz/dIu5ct+6WSY8tDF/jfngacdKHNyKzOLCZXMFoL2qJXJmqQjU/DGkLCok1lXrXjQDgNVqBVB/
wSaZhhJEQaqJwnvf+35KU14m0ov+37I0AVi3r3Jv5Oz/rlv9YwAwV739cooB+tzUd8p/mv3MXEFK
SMd6u9NVczhU27rdVOjhqRqqnb79WweWI+3VAAAV8ElEQVSqvc+3NEnUhLonAJwKdZNnmMqWwfjK
0Ot1c+bMqv74xFWHXQHPCWqf2+1ydoUZjFcdDgWK46qv9uwVR1c74bo8EqHE8EX9eetdCXfFjW36
9NOrX9LIUaM5TpAlRZK8VJYgewgoIRwl1OFwtdocdrccMXGyh+PcXqm5vcvjUVRa8ZNPTujU0KkI
4ShAOjtsiuIROY7jeFEl6vSGf/rxE2HXr1vs5psRnwAA3pYWG4DI2FEAeEO4CMB79rKLnzy0/0k6
8ociwJqsDa50fKs0e/4ywAM8d58/7ykA2AHHsSKr+bnx/u9F0HW/mQ4giwpBqqW6fIZ/jYDt+LLI
5P/17rPli3WDC6Ig+QD4fI4TpdbUJ6YFzmojxgEtTgmiB1jiz00uAua0yQKClthhtC10M0O088kn
Bqy9z7c0CAN0gcFgfJXodNrUR797u1txixnR43u9UUVF6gFIUs+HXZxRNQz/k8OybZt1bXFlrdVq
tdZWFa9FyfIPm0I+NLWJabB2Bmf5fZ7gPweQRQ2Oaep3U9HW6RyGIAoARFGMm4SKlo5g7c56IEbn
f9QH8s36APRerjlw2/p6qoZqp2fg2ofPIF1gMBiM6+CbEZ/8z9nYieMBnNxTeODw4d35xTZANdUc
zw/tfzr7X29VIPO5BbMmT5s2bdrklAVPZwL5/13b/0ofhCkPZ2J95t6aVndr9f9KXgUYfQPKovxF
+tBWd6ymrqbm+PHqvXmrMiqw8IHxQwuifAAq6k47pv9gNda/sL/OBjj252RasTp1qJGx0G0L5aka
qp1Thll7/zV6vmsfNDfQBQaDwejPCP9hKwKAPuD/MUyet+R77UVH6y0ffABANSbl2R/dOwz/k+PI
GwXm7MoJ3X0VJj+RbZ6z66OOZPR+sTCKIhIX/ubgphXzzDEAUs2Adeoo7SCyqGuGJwCiqAasS2Z3
39S8qcT6Ulq0lDiUIEobPtOMJebHquwfFK0uT5/iV8ynFlvXJwIOXGtnz9oSAEAI2TaE8lQN2U4B
6wevvftbQq+D3V+CUScicX6ImzAYDMb1MsL8T8NAdnV0OGXwuqiIW6fZ6EFrTen/1Mf8aP4MDdB6
5JWY2aPtdGVgvCykLGqYDC2IktxuaDQCgj6kyIT44VcUqm2hPFXD4AZq/4puwmAwvs188+LTV43t
+ObI5DXpa/P/ObFuyfJtmUXWHYuZ6oLBYDC+blh8CkFTTfn7Bz+su+R68EfLFs9io1MMBoNxG2Dx
icFgMBgjkW/G+j0Gg8FgfNtg8YnBYDAYI5GRu7hK9rqcHgmC2qBVDX31bUOytba4fICojYm+QTmG
2+EW+q/mYzAYjG83I/L9SW47vDv/tZzNv/3tb3+7OWfLrrK2GxeIAAAk2/Ejx291Hm2pZv9mQsTI
mKUrVqyYFxMpkrSdRxr85xzHNxOyeUBhxbX22HYum641an97XXILBoPB+BYwAtdHuMryNx9tBhA2
bmpcx6nTNgBhyat+/njEDd9SOk7EZIuLzrhl6jz3/he16eXZ1kO/mGJwtTiE+GhDU03pGvO8UQfP
b52bKNnqKj/F7LQBPIjd7RFq0kRzalnjurT4W9UyBoPBuDMYce9P3gsfH20GEPvEqp8/vWjxyrXP
jgHQZam64ALQUV/9u7ycnJycLXm7Dn/WDGBo/5N0duP3e9iVynf41URpy/LqbHCf3bts2eYdG58i
hJC0F480uDEM31LrkdfTt2W3n1xntLwuaiPXvPQUISRhu/eNlpJt8/bYeuuR+sqZrrXn3367alUF
sP7FFfvPXsupF9rAFDBFLTjuCK2nYjAYjDsNOsL48tB/ZGVl/eZPtd1HPHbbFZvNKVHpclVWVlZW
VtZvcn+TlZWVlfWrT22UUvufsrKysrLerbUPcEu79WCuGebckqovPy0EkJlfVmstWQogu9JuzQeA
pfm1ZyybUgGsPuOjgYPpmyori5cCANYWHiwrzgZQWOuilB5cbV5baafUmgrkWuyU+vLNWFrcSKk1
PXVTO6V2yyYgt51S2lJmBlKzi621lWtTAfOmlh7tsfx3LmDOLak8b/cF2lobaOH5M1XZqQCyG2mw
PUjPLSo792khgKX5By1lhf6DVQP1m8FgML7JjLj4dO7gf2RlZeW+fzrUqdysrKz/OHSOUlr7/n9m
Zf3q0DknpdK5qg8OHjx02iYNeFOfNRWpFhe1bDIjtdD/PG+pzM3MPthqzQUya/3RoaXMDORa7HZr
PmD2P/ctualIL/JRSn3WdCDX0k6pPd+MbIuL1uYDaxsppfRMJnCwndLzRcCmdkrt1lwg106pNT/d
H2Mopa7zxQBKzvu62xP44LvW0qpN5kB1lNL2SjNQWBtoT1k7pZRaNpmRWey/oL1qE5BqYfGJwWDc
iXwDVo05mps6vLIhdixEFYCk8aMBTH78uV8+Hrhg3JD+p152pWR/Mr3oWSt3zIKj5guYZyQEEtBG
jAMACRjctyRGmdECQKsGLlx2uC9sm1iApS+46jbPX7K06IzJn1M1QCg5U6y/PfAn/va5gECC74H8
TwiaogbSUzEYDMadxoibf0q4OwmAzXI4oMvw1hflv/nWW299bpNllxeA46oHQPOJ0l27ii1NLmAY
/icA3XalhoCZ3XZ87+YdRzwArJ3d19iB4Jr7AX1LgOahJavXZ/zenfhkyerGZKN2O/JzVzeaE6Zc
WlFZuHhCz0sHEUeJIbyBQ8qTQuupGAwG485jxMUn1biZyWEALhZtzit+rzhvy65mAKbvmWP5UWPi
AJza94eyw6V7Sqrr609JvAoY2v/UbVd64J9WI+fF/XU2yVH3evKiNQ1QQw2sydlbBzhK87IrsPT7
U4eWFcXPfSU3arn2qd9PzymnlL69btnKreWN1oPOPX+s7R3MBpYzVdSdbr12ndSw85WNpWcxiDzJ
B2AAPRWDwWDceYzA8b2Ix3/2PN76vaXZduqkDYBqTPK/LJ6jBbT3Pf746UsHTjUf/aAZwNTHn0+J
5QEM5X/qZVcqXnsyoCYyr7b84ru4eApAzqIpOQCA3LLGyZohfEsAgOiV5e1JmzOStMuRmp5utJeU
VADphZVbpnQvYTcDCC2O6m7PhJbCwMVS266c9XMXvjA3lDypp2gqpJ6KwWAw7jxG4P6nAK6ONrtH
EtTGPp4nr6PD4ZV5XUSEdpCI1J8ediVbqxuaaJMBgON4njFDbT/5nLvJJkRGm65zg5TksDW2tEPQ
6oyDFQ4pZ+puT38GkScNoqdiMBiMO4kR+P4UQBsRFfLFQGWIiLqR+wmaYPgwmKJ7PNDdsLolCNHx
0TdyU4Mp0WAa8jKNKbrf/ttr7emPITp+oJAj+KxL0nvpqVhwYjAYdyQj9/3p60FqPf6eBY/PvXWZ
Jb56mJ6KwWB8G/i2xycGg8FgjExG3Po9BoPBYDDw7YxPn3/+eW1t7e1uBYPBYDAG40bH97yuNocd
UBuiIkaynakn1dXVer1+0qRJ//Iv/6Ioyq5du06fPu10OlNSUnpc5ba1OiQIphuVOd0cksONb7QK
SnI7oOm/6pDBYDCumxt5f6r/sHhDzubt2/O3b8/N2bClNJBH/Fbiqi/dsGHDlgNnIHfUWSwn6ppu
0gAFQBCEadOmRUZG7tmzp7i4ODIy0mw2iz2yOLRW70wj2siYmJiYSJGk7ShvwJAmpxvCXbfTn4m8
D6Uvik/94Qzcx9NIWnW/szdR3/GnSF8231rjVNBodeYPT4kbj9zKOzMYjG8r1/1LV246vOvQKahM
U6d9R+tqtJy6WL0v3xC99uHYW/kexatNY0wmo0kN2P584ECXKnnq2vjr2u7UE4/H43A4SktLATid
Tv/BuLg4l8v1/vvvJyYmGgwGlfL58zMzEvLLWhY/qJHaK7avSp+TNKmFzh43v6wMt3YNtwAA9j55
H9x1O+dtW3rGNxnS8VtaGwA4gMzCsheSI3z+Wn2I+s6t7VN98uxki4vOWLoxXTTvXuxaPOEbtCKS
wWCMRK77/enKhUYApmk/XPT43McXPbckZQygcjhlAE0nSvNycjZsyMnLL/6szeu/vr+xydtUnb8l
r7i6yf/5d1vyij+84G2qzs/L332gtDg/J7+0HrwgqlQi11Fa9H4XAK/l7QMflu3Oz8vfXdcBAG0n
DuTl5b1X3TS0/wlob2+fPXv2q6++2n0kMTHx2LFjzz77bFZW1qxZs9ra2tynLSXAoh+lRRsMBlPi
/HVbstOXtrc5epqc+ouX3Gf3PrVs8+4drxBCCFmwty7wUtLX+RQsnkYImf7UL7ZuBYy90+/Zfr8i
Iz3/5QkD/2Co258X8EIteKW6qZ8Xyta6f/My/7vRizuP9EkZaAdmzJw9bdqMACkzEk1CyB4NdLB/
j3rU/vf/mhY0bLmm/bowfUnWASalYjAYN8l1xydjTCQAm2VX3u92l31o4e//8S9/uXbuOK2j7sCb
JdU2ryo2VmVrPrVv+9sXvJCbq3N3lV60eVV6VZet/oN9b53ogOyxNXfZvmx1ApCdtotdti9tHtlj
a7Y1n7ZUn2r2XpVk2dFa39x8tsXhaL3qr7ejHQbxqq359MefNwNyncVis9lM8aMAp6Wk9OgHh6oa
nQO1OS4uLjc3F8CMGTPi4uJUKtW77757/vz5LVu2ANiyZUtcXJxmysylQHrM9Fc27yyvrmmyJa57
7+2Fkw2+zrpt689LgKNmZ9Kc5Yb8g5atC9asWl9QUH7ZBZ+z7Z2CNUv2aMuqKjellyx64m0HgNby
R6fMO51abK2tnHl6lfnR37YCtuq8pDnLEzaVVG2fU15g7dtER/2eCix4bNJAXZDO7p6Svmp6UeX5
M5bnDDkzV7zjBnzOtne2LV+UUZ9btFL7ydb0Nc0HrWesZbnbMmZnH+k1fGcEjh7+S3V19ZEANbYB
ehTyYMge9ah99U/W5Jphzt345BgtkpLn4Z2SM32T6jIYDMb1cd3je9pxD8+der70VLPt4umjF08f
PQSoxi15YVHjBxYAUx//yY/u033wZu7R5osnv3RIZ6oBxH7v6eVzxtUd+N0eS0ubLZDFNfD2wPf4
DCBs0pJn/mlchNb75RkAIh+zaPWT+a/tajal/Ozph3HBffDU0frPzsspct1FQDX93rEqgJ8+91GN
TZo4WjdIsxVFAfDcc8899NBD1dXV48ePf+CBB9xud/cpCJPfbKx68PXtq9Zk+HPxmTMLD+14RiNq
/F/T6YNbkVlcuGyuALRXtUTOLA0221y5b90sEx7amL/GfPC0Y6X4xzwrshvXLYwHJhUW5yQt+mvD
S2Oq30N6UeHL8wXgqMVuTH6vV/ukq21INScMPCYWOaOkpCp1forWbbt3WiqK7K7AH89c1v5emgl1
OwsBA6Cdkrai0ZrSZuxV2gC8szz9nWsH0i329xCqRyG7WROqR6k9aodUE4X3vvf9FJMAjJlqxp5O
H8BG+BgMxk1wA+sjDCmLlr/68qpnl/z40ZSpJhXgrS85fM5/7tSBN197LfdoMwBIQF9j0y/Xzhk3
WDZT0z3fnRil5XtONAW9GR5ANfbeSQAufl77We1FwHT/9CgA4MelPDJ37pyJEQPOTzU0NPzsZz8D
sHbtWp1O99Of/vTJJ59saGjwn33ppZcaGhokR6tDO33l1rcp9dlbzpcVrrUWZLy692zwHo5jRVbz
Pf3FSx7guftMQCC/uF8R5Xc+EUKINmkRgPNttnPHKgIeKQCiuk8LHfWfWoO3CIkgiJcq1hoJEbWR
c9ZUIEod/GXh90Jh8o9fzk5/Z545QSTi0u3VPl2v6SVHwKzYzXszDCF7NFA3+/fI1bP2oGELAKDV
j0NF9elbu6aEwWB867ju+HTmQN6GDRuKrJ6xE+99ZO6i5YuSAYiAywsAKU+88PLLLz2/5In09B8n
j9INZGzqRvL0HgaS+s0hBYKO/4ke+3fJJqB+376jgCrl/rv854b0P40dO/aTTz759a9/bbfb09PT
lyxZUlZW5j/12muvHTt2bOzYsbWFj8VEvt4KAIIhOjHtmezCVFSduxK8x3WIl0I6n7yAtTMwVtnf
/CTqjEDvZOm9r6nb9/Pl2yZVnm/xUdp4cDXa+jbA0S4uftPls7dYK4snFazKKOw1hGgHIPb5ZRCy
R6G7OYjFqlcvgm22IzVl0tBpCRkMBmMQrjs+jUq6C0B9af7v3istKy3OL7YA0JtM99wTC+DTD45Y
rR/vLdpTUrLvnFMewNgEADbLX94rO1Cw5+QQ9cnwArD97ciJCzIwbkZy4HjYtKmx/tg1tP+J4zij
0bho0SIA9fX1e/bsAaBWqwH85Cc/MRqNHMdN+cE6YP3zm/e3uiW321ZT+kZGBRZ+d3zwHsMVL/lC
O580Dy/KxPoX9tbZ4G74/b8vB3oNwGmSzKmoqGvsjtYV1o+OHz9+vLr6eHV1dU2Dw+cBEHVXQrTU
VL1h3jZEXZMm+ptxateUiY8VtGijp82a88jSvq0yAn/76IOa48erq6v996xrcoXqUehuhrZY9ai9
p9HKfd5aMdBfgsFgMIbNdc8/Rdz7w6c7fX84dOriyeqLAIAxyelPPRyvwpLH2gsPnTpZWgoAU+c+
+0i8CvEhjU2PPDbpb4dO204etah6t0J1rTli4LjWNN4Ei812tMTyd/eNNcTfkxx2yNKF2Aemd/+A
H9r/BADo7Ow8fPhwSkpK9/7cjz/+2G4PSNuFCQutxdnmReklawLXZ+aWrZ4VjZqAyWlA8ZK5ZyVG
URzA+TT/taLMxxZNiQRgXpoOGHq+LUEzboEZx063L54QDyAByJiT3H0yNdfylx88m4r0JDEHwOq1
mchZ9Vje946motsLlfxcWfr6OQniKgDA0rLzU3s2ywAULJ9X0ONIaq6lfGWIHoXsZsge9bRSXTNa
2U+O/uIkMHc8S6vOYDBujhvNHyF7OzocMqAyRBl6bHzyuhxOj8zrInodDGVscjkcUOu0qmFtavJ6
veB5Fc/L3uaD+fkWm+rxVWuTI26k4QA+//xzRVGmTJkS4pzb1tRs94liZGS8off0/vWKl0I5n2Br
bZIEg1891YfW8ldi5mhb6LoBPR+So7XFrYmMNmggORyStn+iCXdTQ7NP1MXGRw9naULIHrkH7mbI
HvVsn9sNjca2kcS4Klt+NetGfCUMBoNxDfoNwlP7q6ysrKysrP88Kn3tlbdbNgFIX5tflL8aQGaR
9ZbXkGvG6rLGW33bgesL1aOb7GZL2WpgU/vQFzIYDMYQfKP8GnJb9f8cs4mm+2el3NJsFcPlqxYv
Sa01lRei0mb0cxl+ZYTs0c10s7XmyIWoB2fEs6XlDAbjZvlGxScGg8FgfGv4Nvo1GAwGgzHyYfGJ
wWAwGCMRFp8YDAaDMRJh8YnBYDAYIxEWnxgMBoMxEmHxicFgMBgjERafGAwGgzESYfGJwWAwGCMR
Fp8YDAaDMRJh8YnBYDAYIxEWnxgMBoMxEmHxicFgMBgjERafGAwGgzESYfGJwWAwGCMRFp8YDAaD
MRL5/9p97pP/91LzAAAAAElFTkSuQmCC

--Apple-Mail=_C598D7FA-B92E-441A-910E-C71F770FF379--

--Apple-Mail=_0CA9A506-9AA2-40C9-AD91-C7F6BB529693--

--Apple-Mail=_620B25C1-C120-4376-B185-DFB94C3413FC
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
hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEyMDIwODE4MjQ1N1owIwYJKoZIhvcNAQkEMRYEFPeH
jCNidA7k8UvPAVZWxQnHLzcZMIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQGEwJVUzEX
MBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
OzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhIChj
KTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlTaWduIENs
YXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEFcfSRTG0jNknqb9LV9GuFkwggEF
BgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJ
bmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1
c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29u
YSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vi
c2NyaWJlciBDQSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMA0GCSqGSIb3DQEBAQUABIIBABzdHMxq
y+nnCUbkgWLhsLgRdmbgIecJiKn2MWFUOrJkMVDGX33z1d0eOd70VRLkwpLUrenkWnRIgWWzabvs
luzgZUEkOwa/zvlgKXl1kUl3pCWHpqctW1Fqq2V6qMJTPQ+JT1zXVloi0DkY3a8VGd6YAvmCetzw
MymOFfwX2GrG1RoN2eqxmiXRTajziJoNlwXXivhWXNMtypGml7jGQKXnW5L68sMZVidYwzhGYPli
ul7ltSHyvPcXvGPokm6DytQz/O1xJfypPu5UjepPx0NCQaMI6TFVZytWDBUt71dRWY2RLswQ9nQG
cq+eVKKa7gEtbL4NesRqY4zH0q4+1xMAAAAAAAA=

--Apple-Mail=_620B25C1-C120-4376-B185-DFB94C3413FC--

From dcrocker@bbiw.net  Wed Feb  8 10:37:49 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 4C0B421F8534; Wed,  8 Feb 2012 10:37:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.2
X-Spam-Level: 
X-Spam-Status: No, score=-6.2 tagged_above=-999 required=5 tests=[AWL=-0.400,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E1YB8n0-hzE7; Wed,  8 Feb 2012 10:37:48 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id A75BD21F852C; Wed,  8 Feb 2012 10:37:48 -0800 (PST)
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 q18IbhX4001194 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 Feb 2012 10:37:48 -0800
Message-ID: <4F32C0F2.5060607@bbiw.net>
Date: Wed, 08 Feb 2012 10:37:38 -0800
From: Dave CROCKER <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0) Gecko/20120129 Thunderbird/10.0
MIME-Version: 1.0
To: "Eggert, Lars" <lars@netapp.com>
Subject: Re: IETF/IRTF mailman & S/MIME
References: <BEB57F99-6093-4D5D-9C23-C98F499B5426@netapp.com>
In-Reply-To: <BEB57F99-6093-4D5D-9C23-C98F499B5426@netapp.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]); Wed, 08 Feb 2012 10:37:48 -0800 (PST)
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, 08 Feb 2012 18:37:49 -0000

On 2/8/2012 10:24 AM, Eggert, Lars wrote:
> As a chair, if you want to be nice to us S/MIME users, the easy fix is to turn
> off the generation of that footer in the mailman settings for the list. Go to
> the the "Non-digest options" settings page and clear out the "msg_footer" field.


That might be a good idea, if the footer contained nothing useful.  In fact 
there is discussion about adding to it with even more useful stuff...

The underlying problem is that a mailing list is creating a new message.  S/MIME 
is residue of the original message that it is based on.

The right solution is to remove the remnants of s/mime, when it's functionality 
no long applies.  Or to not include s/mime when it isn't needed.

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From lars@netapp.com  Wed Feb  8 10:43:26 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 3B90A21F85D3 for <wgchairs@ietfa.amsl.com>; Wed,  8 Feb 2012 10:43:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.954
X-Spam-Level: 
X-Spam-Status: No, score=-9.954 tagged_above=-999 required=5 tests=[AWL=-0.154, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5l6LU+9vYzyY for <wgchairs@ietfa.amsl.com>; Wed,  8 Feb 2012 10:43:25 -0800 (PST)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by ietfa.amsl.com (Postfix) with ESMTP id 8F12221F85D1 for <wgchairs@ietf.org>; Wed,  8 Feb 2012 10:43:25 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.73,385,1325491200";  d="p7s'?scan'208";a="623694371"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx2-out.netapp.com with ESMTP; 08 Feb 2012 10:43:08 -0800
Received: from sacrsexc2-prd.hq.netapp.com (sacrsexc2-prd.hq.netapp.com [10.99.115.28]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id q18Ih8qR010768; Wed, 8 Feb 2012 10:43:08 -0800 (PST)
Received: from VMWEXCEHT02-PRD.hq.netapp.com ([10.106.76.240]) by sacrsexc2-prd.hq.netapp.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 8 Feb 2012 10:43:04 -0800
Received: from SACEXCMBX04-PRD.hq.netapp.com ([169.254.6.193]) by vmwexceht02-prd.hq.netapp.com ([10.106.76.240]) with mapi id 14.01.0355.002; Wed, 8 Feb 2012 10:42:58 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: Dave CROCKER <dcrocker@bbiw.net>
Subject: Re: IETF/IRTF mailman & S/MIME
Thread-Topic: IETF/IRTF mailman & S/MIME
Thread-Index: AQHM5o70sPG9GG2xGkipdI0RBwRa95Yz2nUAgAABfoA=
Date: Wed, 8 Feb 2012 18:42:57 +0000
Message-ID: <3DEC0B0F-7B0B-48B2-8F41-EEBC9D45C34B@netapp.com>
References: <BEB57F99-6093-4D5D-9C23-C98F499B5426@netapp.com> <4F32C0F2.5060607@bbiw.net>
In-Reply-To: <4F32C0F2.5060607@bbiw.net>
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=_1AA30AA3-D87E-4149-B7A2-2F615661698E"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-OriginalArrivalTime: 08 Feb 2012 18:43:04.0120 (UTC) FILETIME=[7DBEBB80:01CCE691]
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, 08 Feb 2012 18:43:26 -0000

--Apple-Mail=_1AA30AA3-D87E-4149-B7A2-2F615661698E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

On Feb 8, 2012, at 10:37, Dave CROCKER wrote:
> That might be a good idea, if the footer contained nothing useful.

At the moment, it doesn't contain anything that the mail headers added =
by mailman wouldn't include.

>  In fact there is discussion about adding to it with even more useful =
stuff...

Is there? Could you elaborate a bit?

Thanks,
Lars=

--Apple-Mail=_1AA30AA3-D87E-4149-B7A2-2F615661698E
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
hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEyMDIwODE4NDI2MFowIwYJKoZIhvcNAQkEMRYEFG5J
43LK2Bxs04rCi5FDSTteBKymMIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQGEwJVUzEX
MBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
OzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhIChj
KTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlTaWduIENs
YXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEFcfSRTG0jNknqb9LV9GuFkwggEF
BgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJ
bmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1
c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29u
YSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vi
c2NyaWJlciBDQSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMA0GCSqGSIb3DQEBAQUABIIBAAkvkIjy
IOINSW5pLxVlTfTmfUahDmhwZ2kBg5ZX7lXhghsC/w7vmXKoQ4Urhs7Pp/IxgWHv8Usrc1lsStfl
YlnReEcgpwYXwh4X2CcuniWSH7/fT17WJ6DVqFOxjG4H+wWoSH0mSz6B9HUcGk34JMsZTi61M1TS
3yuzUTZfj6nXV8bZDb1B2fB+uGtIcwEF2BMgPKVSmUN1pbxz+pYNhRqNHl3ZfvgghUvMCaj3Kakx
Gpk6YwnVwVdTuWcz9agXWFUJ8TJJz7ft7GEKrottGQObP5Gari9St2ApMDO5eGHLtGHAcr+Rx4Nb
QJ1qchqMcd89CNPRHsl4x5B3t6zOlXkAAAAAAAA=

--Apple-Mail=_1AA30AA3-D87E-4149-B7A2-2F615661698E--

From johnl@iecc.com  Wed Feb  8 10:47:29 2012
Return-Path: <johnl@iecc.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3FD621F8577 for <wgchairs@ietfa.amsl.com>; Wed,  8 Feb 2012 10:47:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.969
X-Spam-Level: 
X-Spam-Status: No, score=-101.969 tagged_above=-999 required=5 tests=[AWL=-0.168, BAYES_00=-2.599, NO_RELAYS=-0.001, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xi-gCBCSIEec for <wgchairs@ietfa.amsl.com>; Wed,  8 Feb 2012 10:47:29 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 9938F21F855B for <wgchairs@ietf.org>; Wed,  8 Feb 2012 10:47:23 -0800 (PST)
Received: (qmail 87795 invoked from network); 8 Feb 2012 18:47:17 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=156f2.4f32c335.k1202; bh=h1vqNGM+vwTFyZWJkqlSYd35OyUlCyABdkd5D/bPDKs=; b=Dtbh5TWdHFb5Oaapa/v7UriSw6Aj8RsdezkTL+7KPwWg4zxPHO1D1MuDAInnmSt23QCbgom7uAhr44HcmrkaU5JntgGpFVWO2qnnbigIpNmomNnWOluFpcAXKTKYQ68+g2IbuSJ8ACKXODMY9/LqVG8yejt8601we70w2n69/2A=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1) with (DHE-RSA-AES256-SHA encrypted) SMTP; 8 Feb 2012 18:46:55 -0000
Date: 8 Feb 2012 13:47:14 -0500
Message-ID: <alpine.BSF.2.00.1202081345580.90136@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: "Dave CROCKER" <dcrocker@bbiw.net>
Subject: Re: [irsg] IETF/IRTF mailman & S/MIME
In-Reply-To: <4F32C0F2.5060607@bbiw.net>
References: <BEB57F99-6093-4D5D-9C23-C98F499B5426@netapp.com> <4F32C0F2.5060607@bbiw.net>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: MULTIPART/signed; protocol="application/pkcs7-signature"; micalg=sha1; BOUNDARY="3825401791-1223119679-1328726837=:90136"
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, 08 Feb 2012 18:47:29 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--3825401791-1223119679-1328726837=:90136
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

There is some way to tell Mailmain to wrap the message in a 
multipart/something and make the footer a separate part, so S/MIME 
clients* can still validate the signature.

Dunno what it is, since I don't run Mailman, but I've been on lists that 
do that.

Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. http://jl.ly

* - well, the competent ones, which in my experience is about half of them
--3825401791-1223119679-1328726837=:90136
Content-Type: APPLICATION/pkcs7-signature; name=smime.p7s
Content-Transfer-Encoding: BASE64
Content-Description: S/MIME Cryptographic Signature
Content-Disposition: attachment; filename=smime.p7s

MIIIBAYJKoZIhvcNAQcCoIIH9TCCB/ECAQExCzAJBgUrDgMCGgUAMAsGCSqG
SIb3DQEHAaCCBSEwggUdMIIEBaADAgECAhA6FNbJAwKAhJZfX7nJAmyNMA0G
CSqGSIb3DQEBBQUAMIGTMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRl
ciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01P
RE8gQ0EgTGltaXRlZDE5MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50
aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBMB4XDTExMDgyNzAwMDAwMFoX
DTEyMDgyNjIzNTk1OVowHzEdMBsGCSqGSIb3DQEJARYOam9obmxAaWVjYy5j
b20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDA6Dyrmw/qos6y
ph5EuKy+/sruC3xCbd9rG9KLMiWu3VorEHRy4PVa09tJFHh8KoHorPRKTzjN
5o05fvxPBGoKysLZs1Whp81PDPWWZXo86Ft94VnpjwzUjKCmM3VcXv8Yw9Lv
+4GzZpR8oWeG6hCttcZBE6oZJGgAIrf3avJNqth6JmjL87FrlaK+xB7AARmV
s86WhzIpXrCo/nXml3ZB7gqbkAr4QO8EoqcSe5h0V8ZjLdww+R1Zw0m3TZeP
u5wrz2646FozcIRxetkcVMi82zykm0fwUdyXPnXKPbYrTUEhcxK+fIfsz+g5
l8L6AodwaAqCzXNKETKojxQzqLn1AgMBAAGjggHeMIIB2jAfBgNVHSMEGDAW
gBR6E04AdFvGeGNkJ8Ev4qBbvHnFezAdBgNVHQ4EFgQUtfl1JgM4E8mY80kK
F4i5k88rmywwDgYDVR0PAQH/BAQDAgWgMAwGA1UdEwEB/wQCMAAwIAYDVR0l
BBkwFwYIKwYBBQUHAwQGCysGAQQBsjEBAwUCMBEGCWCGSAGG+EIBAQQEAwIF
IDBGBgNVHSAEPzA9MDsGDCsGAQQBsjEBAgEBATArMCkGCCsGAQUFBwIBFh1o
dHRwczovL3NlY3VyZS5jb21vZG8ubmV0L0NQUzBXBgNVHR8EUDBOMEygSqBI
hkZodHRwOi8vY3JsLmNvbW9kb2NhLmNvbS9DT01PRE9DbGllbnRBdXRoZW50
aWNhdGlvbmFuZFNlY3VyZUVtYWlsQ0EuY3JsMIGIBggrBgEFBQcBAQR8MHow
UgYIKwYBBQUHMAKGRmh0dHA6Ly9jcnQuY29tb2RvY2EuY29tL0NPTU9ET0Ns
aWVudEF1dGhlbnRpY2F0aW9uYW5kU2VjdXJlRW1haWxDQS5jcnQwJAYIKwYB
BQUHMAGGGGh0dHA6Ly9vY3NwLmNvbW9kb2NhLmNvbTAZBgNVHREEEjAQgQ5q
b2hubEBpZWNjLmNvbTANBgkqhkiG9w0BAQUFAAOCAQEAHspD+qV1moo6KgyJ
RHPCTMObHh5Gr1HcP6pTkivyCofyziYMHasjZbReynNHmhVLjepe5U25dY+a
P9u9/WwhJQKYLwITI4LWlAMyKMEmOH4fdwYsOPDVfUyHue/iJhY8v6g3svrX
dwyFbJfKZisMU4FswPR+Lm3YHJdQwnPxR9FSCyjbXs40Aq77J4eiXLtFWSsD
9nxISabgon/cmS2wyoWeV8dCrGMhkWM+KuE+hLfjJKCU9KoKy6LrouhWlqXW
ZNgQXFT+OH931U1ry22bzzvoNt/pwAYJ5QNJTVGOaqCRMaZW4rq7xnpPH6Ml
AgfO1+bEN3OWcQB7RqxlT1iL4zGCAqswggKnAgEBMIGoMIGTMQswCQYDVQQG
EwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdT
YWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDE5MDcGA1UEAxMw
Q09NT0RPIENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWls
IENBAhA6FNbJAwKAhJZfX7nJAmyNMAkGBSsOAwIaBQCggdgwGAYJKoZIhvcN
AQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTIwMjA4MTg0NzE0
WjAjBgkqhkiG9w0BCQQxFgQUctDTL1Giz0xTTp/1kGl6irJxt3gweQYJKoZI
hvcNAQkPMWwwajALBglghkgBZQMEASowCwYJYIZIAWUDBAEWMAsGCWCGSAFl
AwQBAjAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwIC
AUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcNAQEBBQAEggEA
hUylF/Y1gbk01zZn/xB2VIa058TxkUyO8uZz9SeAEUzSilbQOcYRRVs+vthk
Zg8E9RMGqpWG18Ko7LfhdH4K8bMEGEC7AwMsr+xE52LvSri7fBy/0zf4wKca
Z2CXC2kW1zCU1DOZMnebVZdOdz7x/PZ7nMHmAr0lNvvuJBNy6bVzLPkyLFn9
7K1XTAehHWsDrqilkniefruyXpzRiOScnrJLUN3+FOuH5k9Ysq5kDM+cZtEK
yPncP+VLj2ZGmqtu0dBIHS4KoPUFRf2ULAxBP/PzRINMd3OfyBeieddhe7U8
n+nSVQUrXCemyFbEVTbX3LFxlADp85umgv5FJkqJ0g==

--3825401791-1223119679-1328726837=:90136--

From dcrocker@bbiw.net  Wed Feb  8 10:53:01 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 5887A21F8551; Wed,  8 Feb 2012 10:53:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6
X-Spam-Level: 
X-Spam-Status: No, score=-6 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bqb1H2HAKOcc; Wed,  8 Feb 2012 10:53:00 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 8BABB21F85F6; Wed,  8 Feb 2012 10:52:58 -0800 (PST)
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 q18IqqF2002089 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 Feb 2012 10:52:58 -0800
Message-ID: <4F32C480.7030904@bbiw.net>
Date: Wed, 08 Feb 2012 10:52:48 -0800
From: Dave CROCKER <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0) Gecko/20120129 Thunderbird/10.0
MIME-Version: 1.0
To: "Eggert, Lars" <lars@netapp.com>
Subject: Re: IETF/IRTF mailman & S/MIME
References: <BEB57F99-6093-4D5D-9C23-C98F499B5426@netapp.com> <4F32C0F2.5060607@bbiw.net> <3DEC0B0F-7B0B-48B2-8F41-EEBC9D45C34B@netapp.com>
In-Reply-To: <3DEC0B0F-7B0B-48B2-8F41-EEBC9D45C34B@netapp.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]); Wed, 08 Feb 2012 10:52:58 -0800 (PST)
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, 08 Feb 2012 18:53:01 -0000

On 2/8/2012 10:42 AM, Eggert, Lars wrote:
> On Feb 8, 2012, at 10:37, Dave CROCKER wrote:
>> That might be a good idea, if the footer contained nothing useful.
>
> At the moment, it doesn't contain anything that the mail headers added by mailman wouldn't include.

There is a debate about whether invisible header fields are a sufficient 
alternative to text visible in the footer.  I of course wish it were, but the 
reality of current mail client software creates a problem.

Worse is that adding something meant to be a formal notice requires assurance 
that the user is likely to see it.


>>   In fact there is discussion about adding to it with even more useful stuff...

A pointer to NOTE WELL, or somesuch.

I should emphasize that it's an idea, not a plan.  To my knowledge, the idea has 
no formal status and is not listed on anyone's agenda.

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From leifj@sunet.se  Wed Feb  8 11:03:54 2012
Return-Path: <leifj@sunet.se>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2805D21F85A8 for <wgchairs@ietfa.amsl.com>; Wed,  8 Feb 2012 11:03:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.8
X-Spam-Level: 
X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8Wcb5obTGNsf for <wgchairs@ietfa.amsl.com>; Wed,  8 Feb 2012 11:03:53 -0800 (PST)
Received: from backup-server.nordu.net (backup-server.nordu.net [IPv6:2001:948:4:1::66]) by ietfa.amsl.com (Postfix) with ESMTP id 3D32821F8587 for <wgchairs@ietf.org>; Wed,  8 Feb 2012 11:03:53 -0800 (PST)
Received: from [10.0.0.11] (ua-83-227-179-169.cust.bredbandsbolaget.se [83.227.179.169]) (authenticated bits=0) by backup-server.nordu.net (8.14.3/8.14.3) with ESMTP id q18J3mBk013052 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <wgchairs@ietf.org>; Wed, 8 Feb 2012 20:03:51 +0100 (CET)
Message-ID: <4F32C714.6030402@sunet.se>
Date: Wed, 08 Feb 2012 20:03:48 +0100
From: Leif Johansson <leifj@sunet.se>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:9.0) Gecko/20111229 Thunderbird/9.0
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: [irsg] IETF/IRTF mailman & S/MIME
References: <BEB57F99-6093-4D5D-9C23-C98F499B5426@netapp.com> <4F32C0F2.5060607@bbiw.net> <alpine.BSF.2.00.1202081345580.90136@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1202081345580.90136@joyce.lan>
X-Enigmail-Version: 1.3.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: Wed, 08 Feb 2012 19:03:54 -0000

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

On 02/08/2012 07:47 PM, John R. Levine wrote:
> There is some way to tell Mailmain to wrap the message in a 
> multipart/something and make the footer a separate part, so S/MIME 
> clients* can still validate the signature.

multipart/footer? argh.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk8yxxQACgkQ8Jx8FtbMZne2BQCgwmmcbwF98lfqnUyNlqED5fW2
q+gAn1XYw27V1CKumPPIXOVBkp/zs7sN
=+UAz
-----END PGP SIGNATURE-----

From johnl@iecc.com  Wed Feb  8 11:27:12 2012
Return-Path: <johnl@iecc.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F360821F859F for <wgchairs@ietfa.amsl.com>; Wed,  8 Feb 2012 11:27:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.953
X-Spam-Level: 
X-Spam-Status: No, score=-101.953 tagged_above=-999 required=5 tests=[AWL=-0.152, BAYES_00=-2.599, NO_RELAYS=-0.001, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2EbFh3GTIYUn for <wgchairs@ietfa.amsl.com>; Wed,  8 Feb 2012 11:27:11 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 5707B21F8591 for <wgchairs@ietf.org>; Wed,  8 Feb 2012 11:27:04 -0800 (PST)
Received: (qmail 22529 invoked from network); 8 Feb 2012 19:27:01 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=57fe.4f32cc85.k1202; bh=ealmT0VbMLE3PxhXuqRjQFBN3wvzRNjez94ryzJpN64=; b=N/QbSLv+bB3t3Nw/z52+RQHPwrohYhguQypIkniAVMgi8zHN7MFo1U4kNokl5noaNdmTAKd//26BcfVaqvWQ8RqwDMhVZzfdy5BwRxVc7wADoCs3+XnIwrgIvMXwje12XMf+dH3LYfxqjm+Bfugya9avL193V0N5HWjqkLbwjdY=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1) with (DHE-RSA-AES256-SHA encrypted) SMTP; 8 Feb 2012 19:26:39 -0000
Date: 8 Feb 2012 14:27:00 -0500
Message-ID: <alpine.BSF.2.00.1202081426260.92269@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: "Dave CROCKER" <dcrocker@bbiw.net>
Subject: Re: [irsg] IETF/IRTF mailman & S/MIME
In-Reply-To: <alpine.BSF.2.00.1202081345580.90136@joyce.lan>
References: <BEB57F99-6093-4D5D-9C23-C98F499B5426@netapp.com> <4F32C0F2.5060607@bbiw.net> <alpine.BSF.2.00.1202081345580.90136@joyce.lan>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: MULTIPART/signed; protocol="application/pkcs7-signature"; micalg=sha1; BOUNDARY="3825401791-854658842-1328729221=:92269"
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, 08 Feb 2012 19:27:12 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--3825401791-854658842-1328729221=:92269
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

I see that the MAAWG lists add footers in a way that preserves S/MIME 
signatures.  If you want, I can ask how they're set up.

Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. http://jl.ly
--3825401791-854658842-1328729221=:92269
Content-Type: APPLICATION/pkcs7-signature; name=smime.p7s
Content-Transfer-Encoding: BASE64
Content-Description: S/MIME Cryptographic Signature
Content-Disposition: attachment; filename=smime.p7s

MIIIBAYJKoZIhvcNAQcCoIIH9TCCB/ECAQExCzAJBgUrDgMCGgUAMAsGCSqG
SIb3DQEHAaCCBSEwggUdMIIEBaADAgECAhA6FNbJAwKAhJZfX7nJAmyNMA0G
CSqGSIb3DQEBBQUAMIGTMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRl
ciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01P
RE8gQ0EgTGltaXRlZDE5MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50
aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBMB4XDTExMDgyNzAwMDAwMFoX
DTEyMDgyNjIzNTk1OVowHzEdMBsGCSqGSIb3DQEJARYOam9obmxAaWVjYy5j
b20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDA6Dyrmw/qos6y
ph5EuKy+/sruC3xCbd9rG9KLMiWu3VorEHRy4PVa09tJFHh8KoHorPRKTzjN
5o05fvxPBGoKysLZs1Whp81PDPWWZXo86Ft94VnpjwzUjKCmM3VcXv8Yw9Lv
+4GzZpR8oWeG6hCttcZBE6oZJGgAIrf3avJNqth6JmjL87FrlaK+xB7AARmV
s86WhzIpXrCo/nXml3ZB7gqbkAr4QO8EoqcSe5h0V8ZjLdww+R1Zw0m3TZeP
u5wrz2646FozcIRxetkcVMi82zykm0fwUdyXPnXKPbYrTUEhcxK+fIfsz+g5
l8L6AodwaAqCzXNKETKojxQzqLn1AgMBAAGjggHeMIIB2jAfBgNVHSMEGDAW
gBR6E04AdFvGeGNkJ8Ev4qBbvHnFezAdBgNVHQ4EFgQUtfl1JgM4E8mY80kK
F4i5k88rmywwDgYDVR0PAQH/BAQDAgWgMAwGA1UdEwEB/wQCMAAwIAYDVR0l
BBkwFwYIKwYBBQUHAwQGCysGAQQBsjEBAwUCMBEGCWCGSAGG+EIBAQQEAwIF
IDBGBgNVHSAEPzA9MDsGDCsGAQQBsjEBAgEBATArMCkGCCsGAQUFBwIBFh1o
dHRwczovL3NlY3VyZS5jb21vZG8ubmV0L0NQUzBXBgNVHR8EUDBOMEygSqBI
hkZodHRwOi8vY3JsLmNvbW9kb2NhLmNvbS9DT01PRE9DbGllbnRBdXRoZW50
aWNhdGlvbmFuZFNlY3VyZUVtYWlsQ0EuY3JsMIGIBggrBgEFBQcBAQR8MHow
UgYIKwYBBQUHMAKGRmh0dHA6Ly9jcnQuY29tb2RvY2EuY29tL0NPTU9ET0Ns
aWVudEF1dGhlbnRpY2F0aW9uYW5kU2VjdXJlRW1haWxDQS5jcnQwJAYIKwYB
BQUHMAGGGGh0dHA6Ly9vY3NwLmNvbW9kb2NhLmNvbTAZBgNVHREEEjAQgQ5q
b2hubEBpZWNjLmNvbTANBgkqhkiG9w0BAQUFAAOCAQEAHspD+qV1moo6KgyJ
RHPCTMObHh5Gr1HcP6pTkivyCofyziYMHasjZbReynNHmhVLjepe5U25dY+a
P9u9/WwhJQKYLwITI4LWlAMyKMEmOH4fdwYsOPDVfUyHue/iJhY8v6g3svrX
dwyFbJfKZisMU4FswPR+Lm3YHJdQwnPxR9FSCyjbXs40Aq77J4eiXLtFWSsD
9nxISabgon/cmS2wyoWeV8dCrGMhkWM+KuE+hLfjJKCU9KoKy6LrouhWlqXW
ZNgQXFT+OH931U1ry22bzzvoNt/pwAYJ5QNJTVGOaqCRMaZW4rq7xnpPH6Ml
AgfO1+bEN3OWcQB7RqxlT1iL4zGCAqswggKnAgEBMIGoMIGTMQswCQYDVQQG
EwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdT
YWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDE5MDcGA1UEAxMw
Q09NT0RPIENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWls
IENBAhA6FNbJAwKAhJZfX7nJAmyNMAkGBSsOAwIaBQCggdgwGAYJKoZIhvcN
AQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTIwMjA4MTkyNzAw
WjAjBgkqhkiG9w0BCQQxFgQUqPcbppEIspXlXHC35nPMONjY590weQYJKoZI
hvcNAQkPMWwwajALBglghkgBZQMEASowCwYJYIZIAWUDBAEWMAsGCWCGSAFl
AwQBAjAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwIC
AUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcNAQEBBQAEggEA
ljKDyx270gU3Ao8azfskc14ZTyLKpC9jjA6H4WSdzNIY9iIh3yrBmMbMOxxU
VlpGnAfkceaQhv/aoSarYcoPIQxavaNBibT84YV2GjbJqHjGVLzNnlc3n8Gv
SmyH1oYjGB9TVqprPmKPxy51swGSU6r5UD99u23Heec3idv2ULobxDwgRZDH
wav2vLO7uvd/kk6CNkg8m6Z7oz/viYXnT3pF6AYwNegpmaAaC9K3rD/KkItl
ApZxmMRTn67QVKpbwMq45NdX7wbqlLqibLOXpXtBZmB+RoofuQgT4UY4lv8A
a6xdv9GurDG/yoo/ezrbHv+xc1HB/0NaQ/77syx4OQ==

--3825401791-854658842-1328729221=:92269--

From keith.drage@alcatel-lucent.com  Wed Feb  8 18:25:54 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 1340821F8616; Wed,  8 Feb 2012 18:25:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.05
X-Spam-Level: 
X-Spam-Status: No, score=-107.05 tagged_above=-999 required=5 tests=[AWL=-1.599, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xb94aBzgpDH3; Wed,  8 Feb 2012 18:25:53 -0800 (PST)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [62.23.212.56]) by ietfa.amsl.com (Postfix) with ESMTP id 1777421F8615; Wed,  8 Feb 2012 18:25:52 -0800 (PST)
Received: from FRMRSSXCHHUB01.dc-m.alcatel-lucent.com (FRMRSSXCHHUB01.dc-m.alcatel-lucent.com [135.120.45.61]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q192PXQJ016579 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 9 Feb 2012 03:25:40 +0100
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.46]) by FRMRSSXCHHUB01.dc-m.alcatel-lucent.com ([135.120.45.61]) with mapi; Thu, 9 Feb 2012 03:25:37 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Dave CROCKER <dcrocker@bbiw.net>, "Eggert, Lars" <lars@netapp.com>
Date: Thu, 9 Feb 2012 03:25:35 +0100
Subject: RE: IETF/IRTF mailman & S/MIME
Thread-Topic: IETF/IRTF mailman & S/MIME
Thread-Index: AczmkuUW+qrR6sjGS5GM7jyxHRMWWwAPxluw
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE2249EB6E1@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <BEB57F99-6093-4D5D-9C23-C98F499B5426@netapp.com> <4F32C0F2.5060607@bbiw.net> <3DEC0B0F-7B0B-48B2-8F41-EEBC9D45C34B@netapp.com> <4F32C480.7030904@bbiw.net>
In-Reply-To: <4F32C480.7030904@bbiw.net>
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.83
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: Thu, 09 Feb 2012 02:25:54 -0000

Both SIP and SIPPING in the past have used the footer to add information on=
 the scope of various mailing lists to use, if the vague hope that it helps=
 people not repost to the inappropriate list.

Keith

> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
> Behalf Of Dave CROCKER
> Sent: 08 February 2012 18:53
> To: Eggert, Lars
> Cc: wgchairs@ietf.org; Internet Research Steering Group
> Subject: Re: IETF/IRTF mailman & S/MIME
>=20
>=20
>=20
> On 2/8/2012 10:42 AM, Eggert, Lars wrote:
> > On Feb 8, 2012, at 10:37, Dave CROCKER wrote:
> >> That might be a good idea, if the footer contained nothing useful.
> >
> > At the moment, it doesn't contain anything that the mail headers added
> by mailman wouldn't include.
>=20
> There is a debate about whether invisible header fields are a sufficient
> alternative to text visible in the footer.  I of course wish it were, but
> the
> reality of current mail client software creates a problem.
>=20
> Worse is that adding something meant to be a formal notice requires
> assurance
> that the user is likely to see it.
>=20
>=20
> >>   In fact there is discussion about adding to it with even more useful
> stuff...
>=20
> A pointer to NOTE WELL, or somesuch.
>=20
> I should emphasize that it's an idea, not a plan.  To my knowledge, the
> idea has
> no formal status and is not listed on anyone's agenda.
>=20
> d/
>=20
> --
>=20
>    Dave Crocker
>    Brandenburg InternetWorking
>    bbiw.net

From spromano@unina.it  Thu Feb  9 09:48:45 2012
Return-Path: <spromano@unina.it>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0165421E8021 for <wgchairs@ietfa.amsl.com>; Thu,  9 Feb 2012 09:48:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.305
X-Spam-Level: 
X-Spam-Status: No, score=-98.305 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ns641lpPbwti for <wgchairs@ietfa.amsl.com>; Thu,  9 Feb 2012 09:48:44 -0800 (PST)
Received: from smtp1.unina.it (smtp1.unina.it [192.132.34.61]) by ietfa.amsl.com (Postfix) with ESMTP id 1174F21E8014 for <wgchairs@ietf.org>; Thu,  9 Feb 2012 09:48:43 -0800 (PST)
Received: from [192.168.1.188] (host115-137-dynamic.3-87-r.retail.telecomitalia.it [87.3.137.115]) (authenticated bits=0) by smtp1.unina.it (8.14.4/8.14.4) with ESMTP id q19HmdIH027313 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 9 Feb 2012 18:48:40 +0100
Message-ID: <4F3406F0.6020904@unina.it>
Date: Thu, 09 Feb 2012 18:48:32 +0100
From: Simon Pietro Romano <spromano@unina.it>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: "wgchairs@ietf.org" <wgchairs@ietf.org>
Subject: Meetecho support @ IETF 83
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailman-Approved-At: Thu, 09 Feb 2012 10:25:01 -0800
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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, 09 Feb 2012 17:48:45 -0000

Dear chairs,

as usual, the Meetecho team will be supporting the upcoming IETF meeting 
in Paris. Please, don't hesitate to contact us (team@meetecho.com)  if 
you would like to use Meetecho in your WG or BOF session in France. We 
will try and accommodate all requests, on a FCFS basis.

Cheers,

Simon

P.S. Those of you who want to have an idea of what we did last time in 
Taipei, can have a look at the recordings available at the site below:

http://ietf82.conf.meetecho.com/

-- 
                             _\\|//_
                             ( O-O )
    ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
                     Simon Pietro Romano
               Universita' di Napoli Federico II
                  Computer Science Department
         Phone: +39 081 7683823 -- Fax: +39 081 7684219
                 e-mail: spromano@unina.it
           http://www.comics.unina.it/simonpietro.romano

     <<Molti mi dicono che lo scoraggiamento è l'alibi degli
    idioti. Ci rifletto un istante; e mi scoraggio>>. Magritte.
                          oooO
    ~~~~~~~~~~~~~~~~~~~~~~(   )~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
                           \ (    (   )
                            \_)    ) /
                                  (_/



From dcrocker@bbiw.net  Thu Feb  9 10:43:52 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 3B49A21E8033 for <wgchairs@ietfa.amsl.com>; Thu,  9 Feb 2012 10:43:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.333
X-Spam-Level: 
X-Spam-Status: No, score=-6.333 tagged_above=-999 required=5 tests=[AWL=0.266,  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 X42QLMt-lZnv for <wgchairs@ietfa.amsl.com>; Thu,  9 Feb 2012 10:43:51 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 735AD21E802B for <wgchairs@ietf.org>; Thu,  9 Feb 2012 10:43:51 -0800 (PST)
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 q19IhjC3025429 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Feb 2012 10:43:50 -0800
Message-ID: <4F3413DC.2070905@bbiw.net>
Date: Thu, 09 Feb 2012 10:43:40 -0800
From: Dave CROCKER <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0) Gecko/20120129 Thunderbird/10.0
MIME-Version: 1.0
To: Simon Pietro Romano <spromano@unina.it>
Subject: Re: Meetecho support @ IETF 83
References: <4F3406F0.6020904@unina.it>
In-Reply-To: <4F3406F0.6020904@unina.it>
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]); Thu, 09 Feb 2012 10:43:50 -0800 (PST)
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, 09 Feb 2012 18:43:52 -0000

yes, please.  The "repute" working group will have a number of critical 
participants who will be remote.  ours is a pretty small working group.


thanks!

d/


On 2/9/2012 9:48 AM, Simon Pietro Romano wrote:
> Dear chairs,
>
> as usual, the Meetecho team will be supporting the upcoming IETF meeting in
> Paris. Please, don't hesitate to contact us (team@meetecho.com) if you would
> like to use Meetecho in your WG or BOF session in France. We will try and
> accommodate all requests, on a FCFS basis.
>
> Cheers,
>
> Simon
>
> P.S. Those of you who want to have an idea of what we did last time in Taipei,
> can have a look at the recordings available at the site below:
>
> http://ietf82.conf.meetecho.com/
>

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From housley@vigilsec.com  Thu Feb  9 18:01:15 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 85E0611E8081 for <wgchairs@ietfa.amsl.com>; Thu,  9 Feb 2012 18:01:15 -0800 (PST)
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 coqCMdZ+9V8c for <wgchairs@ietfa.amsl.com>; Thu,  9 Feb 2012 18:01:14 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 75F5311E8076 for <wgchairs@ietf.org>; Thu,  9 Feb 2012 18:01:14 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id A81A8F24105 for <wgchairs@ietf.org>; Thu,  9 Feb 2012 21:01:28 -0500 (EST)
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 qKNPdlTrhZpx for <wgchairs@ietf.org>; Thu,  9 Feb 2012 21:01:06 -0500 (EST)
Received: from v234.vpn.iad.rg.net (v234.vpn.iad.rg.net [198.180.150.234]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 6DCF4F2409A for <wgchairs@ietf.org>; Thu,  9 Feb 2012 21:01:25 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: DRAFT Revision to the WG Document Writeup (about IPR)
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <201110271852.p9RIqcOO025921@mtv-core-3.cisco.com>
Date: Thu, 9 Feb 2012 21:01:08 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com>
References: <AE35FF1F-47D2-4AB3-B074-6CCBA5B6AC25@vigilsec.com> <201110271852.p9RIqcOO025921@mtv-core-3.cisco.com>
To: IETF WG Chairs <wgchairs@ietf.org>
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: Fri, 10 Feb 2012 02:01:15 -0000

It has taken me a very long time to incorporate all of the comments into =
a revised draft of the WG Document Writeup.  Here is the revision.  =
Please review and comment.

Russ

=3D =3D =3D =3D =3D =3D =3D =3D =3D=20

Document Writeup

As required by RFC 4858, this is the current template for the Document
Shepherd Write-Up.

Changes are expected over time. This DRAFT version is dated
9 February 2012.

  (1) Briefly describe the review of this document that was
      performed by the Document Shepherd.  If this version of the
      document is not ready for publication, please explain why the
      document is being forwarded to the IESG.

  (2) Has the document had adequate review both from WG participants?=20
      Does the Document Shepherd have any concerns about the depth or
      breadth of the reviews that have been performed? =20

  (3) Do portions of the document need review from a particular or
      from broader perspective, e.g., security, operational complexity,
      AAA, DNS, DHCP, XML, or internationalization? If so, describe the
      review that took place.

  (4) Describe any specific concerns or issues that the Document
      Shepherd has with this document that the Responsible Area
      Director and/or the IESG should be aware of? For example,
      perhaps he or she is uncomfortable with certain parts of the
      document, or has concerns whether there really is a need for it.
      In any event, if the WG has discussed those issues and has
      indicated that it still wishes to advance the document, detail
      those concerns here.

  (5) Has an IPR disclosure been filed that references this document?
      If so, summarize any WG discussion and conclusion regarding the
      IPR disclosures.

  (6) How solid is the WG consensus behind this document? Does it=20
      represent the strong concurrence of a few individuals, with=20
      others being silent, or does the WG as a whole understand and=20
      agree with it?  =20

  (7) Has anyone threatened an appeal or otherwise indicated extreme=20
      discontent? If so, please summarise the areas of conflict in=20
      separate email messages to the Responsible Area Director. (It=20
      should be in a separate email because this questionnaire is=20
      publicly available.)=20

  (8) Identify any ID nits the Document Shepherd has found in this
      document. (See the Internet-Drafts Checklist and
      http://www.ietf.org/tools/idnits/). Boilerplate checks are not
      enough; this check needs to be thorough.

  (9) Describe how the document meets any required formal review
      criteria, such as the MIB Doctor, media type, and URI type
      reviews.

 (10) Have all references within this been document been identified
      as either normative and informative? Are there normative
      references to documents that are not ready for advancement or
      are otherwise in an unclear state? If such normative references
      exist, what is the plan for their completion? Are there normative
      references that are downward references (see [RFC3967])? If so,
      list these downward references to support the Area Director in
      the Last Call procedure.=20

 (11) List other RFCs that this document obsoletes, and indicate whether=20=

      the to-be-obsolete RFCs are listed in both the title page header
      as well as in the Abstract and Introduction. Which if these RFCs,
      if any, are to be moved to Historic? Is this change of status
      explicitly stated in the document Introduction.

 (12) List other RFCs that this document updates, and indicate whether
      they appear in both the title page header as well as in the
      Abstract and Introduction.

 (13) Describe the Document Shepherd's review of the IANA considerations
      section, especially with regard to its consistency with the body
      of the document. Confirm that all protocol extensions that the
      document makes are associated with the appropriate reservations
      in IANA registries. Confirm that any referenced IANA registries
      have been clearly identified. Confirm that newly created IANA
      registries include a detailed specification of the initial
      contents for the registry, that allocations procedures for
      future registrations are defined, and a reasonable name for the
      new registry has been suggested (see [RFC5226]). List any IANA=20
      Experts that the IESG will need to appoint during IESG Evaluation
      for any new registries that require Expert Review for future
      allocations.

 (14) Describe reviews and automated checks performed by the Document
      Shepherd to validate sections of the document written in a formal
      language, such as XML code, BNF rules, MIB definitions, etc.

 (14) The IESG approval announcement includes a Document Announcement
      Write-Up. Please provide such a Document Announcement Write-Up.
      Recent examples can be found in the "Action" announcements for
      approved documents. The approval announcement contains the
      following sections:

      Technical Summary

        Relevant content can frequently be found in the abstract=20
        and/or introduction of the document. If not, this may be=20
        an indication that there are deficiencies in the abstract=20
        or introduction.

      Working Group Summary

        Was there anything in WG process that is worth noting? For=20
        example, was there controversy about particular points or=20
        were there decisions where the consensus was particularly=20
        rough?

      Document Quality

        Are there existing implementations of the protocol? Have a=20
        significant number of vendors indicated their plan to=20
        implement the specification? Are there any reviewers that=20
        merit special mention as having done a thorough review,=20
        e.g., one that resulted in important changes or a=20
        conclusion that the document had no substantive issues? If=20
        there was a MIB Doctor, Media Type or other expert review,=20
        what was its course (briefly)? In the case of a Media Type=20
        review, on what date was the request posted?

      Personnel

        Who is the Document Shepherd? Who is the Responsible Area
        Director.


From Tina.Tsou.Zouting@huawei.com  Thu Feb  9 18:04:22 2012
Return-Path: <Tina.Tsou.Zouting@huawei.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88C5511E8087 for <wgchairs@ietfa.amsl.com>; Thu,  9 Feb 2012 18:04:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.462
X-Spam-Level: 
X-Spam-Status: No, score=-6.462 tagged_above=-999 required=5 tests=[AWL=0.137,  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 mvRTNQ09LUtB for <wgchairs@ietfa.amsl.com>; Thu,  9 Feb 2012 18:04:21 -0800 (PST)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id 9F56411E8075 for <wgchairs@ietf.org>; Thu,  9 Feb 2012 18:04:20 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LZ500IMYN2WO1@szxga04-in.huawei.com> for wgchairs@ietf.org; Fri, 10 Feb 2012 10:04:08 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LZ50014CN2WPR@szxga04-in.huawei.com> for wgchairs@ietf.org; Fri, 10 Feb 2012 10:04:08 +0800 (CST)
Received: from szxeml212-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AGZ92839; Fri, 10 Feb 2012 10:04:07 +0800
Received: from SZXEML405-HUB.china.huawei.com (10.82.67.60) by szxeml212-edg.china.huawei.com (172.24.2.181) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 10 Feb 2012 10:03:34 +0800
Received: from SZXEML526-MBS.china.huawei.com ([169.254.7.225]) by szxeml405-hub.china.huawei.com ([::1]) with mapi id 14.01.0323.003; Fri, 10 Feb 2012 10:04:33 +0800
Date: Fri, 10 Feb 2012 02:03:42 +0000
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
Subject: RE: DRAFT Revision to the WG Document Writeup (about IPR)
In-reply-to: <FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com>
X-Originating-IP: [10.212.244.142]
To: Russ Housley <housley@vigilsec.com>, IETF WG Chairs <wgchairs@ietf.org>
Message-id: <C0E0A32284495243BDE0AC8A066631A80C29F461@szxeml526-mbs.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-language: en-US
Content-transfer-encoding: 7BIT
Accept-Language: en-US, zh-CN
Thread-topic: DRAFT Revision to the WG Document Writeup (about IPR)
Thread-index: AQHM55fnDSg47CTq/Ues6oT0ectJU5Y1YNpw
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: <AE35FF1F-47D2-4AB3-B074-6CCBA5B6AC25@vigilsec.com> <201110271852.p9RIqcOO025921@mtv-core-3.cisco.com> <FCDC373F-94B5-4039-9624-1B68DC807019@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: Fri, 10 Feb 2012 02:04:22 -0000

Tina


> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
> Behalf Of Russ Housley
> Sent: Thursday, February 09, 2012 6:01 PM
> To: IETF WG Chairs
> Subject: Re: DRAFT Revision to the WG Document Writeup (about IPR)
> 
> It has taken me a very long time to incorporate all of the comments into a
> revised draft of the WG Document Writeup.  Here is the revision.  Please
> review and comment.
> 
> Russ
> 
> = = = = = = = = =
> 
> Document Writeup
> 
> As required by RFC 4858, this is the current template for the Document
> Shepherd Write-Up.
> 
> Changes are expected over time. This DRAFT version is dated
> 9 February 2012.
> 
>   (1) Briefly describe the review of this document that was
>       performed by the Document Shepherd.  If this version of the
>       document is not ready for publication, please explain why the
>       document is being forwarded to the IESG.
> 
>   (2) Has the document had adequate review both from WG participants?
>       Does the Document Shepherd have any concerns about the depth or
>       breadth of the reviews that have been performed?
Both from WG participants and what?
> 
>   (3) Do portions of the document need review from a particular or
>       from broader perspective, e.g., security, operational complexity,
>       AAA, DNS, DHCP, XML, or internationalization? If so, describe the
>       review that took place.
> 
>   (4) Describe any specific concerns or issues that the Document
>       Shepherd has with this document that the Responsible Area
>       Director and/or the IESG should be aware of? For example,
>       perhaps he or she is uncomfortable with certain parts of the
>       document, or has concerns whether there really is a need for it.
>       In any event, if the WG has discussed those issues and has
>       indicated that it still wishes to advance the document, detail
>       those concerns here.
> 
>   (5) Has an IPR disclosure been filed that references this document?
>       If so, summarize any WG discussion and conclusion regarding the
>       IPR disclosures.
> 
>   (6) How solid is the WG consensus behind this document? Does it
>       represent the strong concurrence of a few individuals, with
>       others being silent, or does the WG as a whole understand and
>       agree with it?
> 
>   (7) Has anyone threatened an appeal or otherwise indicated extreme
>       discontent? If so, please summarise the areas of conflict in
>       separate email messages to the Responsible Area Director. (It
>       should be in a separate email because this questionnaire is
>       publicly available.)
> 
>   (8) Identify any ID nits the Document Shepherd has found in this
>       document. (See the Internet-Drafts Checklist and
>       http://www.ietf.org/tools/idnits/). Boilerplate checks are not
>       enough; this check needs to be thorough.
> 
>   (9) Describe how the document meets any required formal review
>       criteria, such as the MIB Doctor, media type, and URI type
>       reviews.
> 
>  (10) Have all references within this been document been identified
>       as either normative and informative? Are there normative
>       references to documents that are not ready for advancement or
>       are otherwise in an unclear state? If such normative references
>       exist, what is the plan for their completion? Are there normative
>       references that are downward references (see [RFC3967])? If so,
>       list these downward references to support the Area Director in
>       the Last Call procedure.
> 
>  (11) List other RFCs that this document obsoletes, and indicate whether
>       the to-be-obsolete RFCs are listed in both the title page header
>       as well as in the Abstract and Introduction. Which if these RFCs,
>       if any, are to be moved to Historic? Is this change of status
>       explicitly stated in the document Introduction.
> 
>  (12) List other RFCs that this document updates, and indicate whether
>       they appear in both the title page header as well as in the
>       Abstract and Introduction.
> 
>  (13) Describe the Document Shepherd's review of the IANA considerations
>       section, especially with regard to its consistency with the body
>       of the document. Confirm that all protocol extensions that the
>       document makes are associated with the appropriate reservations
>       in IANA registries. Confirm that any referenced IANA registries
>       have been clearly identified. Confirm that newly created IANA
>       registries include a detailed specification of the initial
>       contents for the registry, that allocations procedures for
>       future registrations are defined, and a reasonable name for the
>       new registry has been suggested (see [RFC5226]). List any IANA
>       Experts that the IESG will need to appoint during IESG Evaluation
>       for any new registries that require Expert Review for future
>       allocations.
> 
>  (14) Describe reviews and automated checks performed by the Document
>       Shepherd to validate sections of the document written in a formal
>       language, such as XML code, BNF rules, MIB definitions, etc.
> 
>  (14) The IESG approval announcement includes a Document Announcement
>       Write-Up. Please provide such a Document Announcement Write-Up.
>       Recent examples can be found in the "Action" announcements for
>       approved documents. The approval announcement contains the
>       following sections:
> 
>       Technical Summary
> 
>         Relevant content can frequently be found in the abstract
>         and/or introduction of the document. If not, this may be
>         an indication that there are deficiencies in the abstract
>         or introduction.
> 
>       Working Group Summary
> 
>         Was there anything in WG process that is worth noting? For
>         example, was there controversy about particular points or
>         were there decisions where the consensus was particularly
>         rough?
> 
>       Document Quality
> 
>         Are there existing implementations of the protocol? Have a
>         significant number of vendors indicated their plan to
>         implement the specification? Are there any reviewers that
>         merit special mention as having done a thorough review,
>         e.g., one that resulted in important changes or a
>         conclusion that the document had no substantive issues? If
>         there was a MIB Doctor, Media Type or other expert review,
>         what was its course (briefly)? In the case of a Media Type
>         review, on what date was the request posted?
> 
>       Personnel
> 
>         Who is the Document Shepherd? Who is the Responsible Area
>         Director.


From housley@vigilsec.com  Thu Feb  9 18:07:15 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 C6A9421E805F for <wgchairs@ietfa.amsl.com>; Thu,  9 Feb 2012 18:07:15 -0800 (PST)
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 5G+7nSPJ8slo for <wgchairs@ietfa.amsl.com>; Thu,  9 Feb 2012 18:07:15 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 4FEB821E803B for <wgchairs@ietf.org>; Thu,  9 Feb 2012 18:07:15 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 9D2DEF24105; Thu,  9 Feb 2012 21:07:33 -0500 (EST)
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 KGOCxlc8hcUJ; Thu,  9 Feb 2012 21:07:08 -0500 (EST)
Received: from v234.vpn.iad.rg.net (v234.vpn.iad.rg.net [198.180.150.234]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 5728AF240F9; Thu,  9 Feb 2012 21:07:32 -0500 (EST)
Subject: Re: DRAFT Revision to the WG Document Writeup (about IPR)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <C0E0A32284495243BDE0AC8A066631A80C29F461@szxeml526-mbs.china.huawei.com>
Date: Thu, 9 Feb 2012 21:07:12 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <0B75AC91-0614-4B05-BD9A-40CEA2B7676C@vigilsec.com>
References: <AE35FF1F-47D2-4AB3-B074-6CCBA5B6AC25@vigilsec.com> <201110271852.p9RIqcOO025921@mtv-core-3.cisco.com> <FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com> <C0E0A32284495243BDE0AC8A066631A80C29F461@szxeml526-mbs.china.huawei.com>
To: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2012 02:07:15 -0000

Tina:

>>  (2) Has the document had adequate review both from WG participants?
>>      Does the Document Shepherd have any concerns about the depth or
>>      breadth of the reviews that have been performed?
> Both from WG participants and what?

Editing remnant.  Please ignore "both"

Russ

From msk@cloudmark.com  Thu Feb  9 21:02:05 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 918C721E8015 for <wgchairs@ietfa.amsl.com>; Thu,  9 Feb 2012 21:02:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.596
X-Spam-Level: 
X-Spam-Status: No, score=-102.596 tagged_above=-999 required=5 tests=[AWL=0.003, 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 hSWOWG2UStDj for <wgchairs@ietfa.amsl.com>; Thu,  9 Feb 2012 21:02:05 -0800 (PST)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.25]) by ietfa.amsl.com (Postfix) with ESMTP id 2D02D21E8010 for <wgchairs@ietf.org>; Thu,  9 Feb 2012 21:02:05 -0800 (PST)
Received: from spite.corp.cloudmark.com (172.22.10.72) by exch-htcas901.corp.cloudmark.com (172.22.10.73) with Microsoft SMTP Server (TLS) id 14.1.355.2; Thu, 9 Feb 2012 21:02:04 -0800
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by spite.corp.cloudmark.com ([172.22.10.72]) with mapi; Thu, 9 Feb 2012 21:02:04 -0800
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: IETF WG Chairs <wgchairs@ietf.org>
Date: Thu, 9 Feb 2012 21:02:12 -0800
Subject: RE: DRAFT Revision to the WG Document Writeup (about IPR)
Thread-Topic: DRAFT Revision to the WG Document Writeup (about IPR)
Thread-Index: Acznl+FoWGXLMyXRTa6VRNQh5Tu7vgAGOScQ
Message-ID: <F5833273385BB34F99288B3648C4F06F19C9A7DCE1@EXCH-C2.corp.cloudmark.com>
References: <AE35FF1F-47D2-4AB3-B074-6CCBA5B6AC25@vigilsec.com> <201110271852.p9RIqcOO025921@mtv-core-3.cisco.com> <FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com>
In-Reply-To: <FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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, 10 Feb 2012 05:02:05 -0000

> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On Beh=
alf Of Russ Housley
> Sent: Thursday, February 09, 2012 6:01 PM
> To: IETF WG Chairs
> Subject: Re: DRAFT Revision to the WG Document Writeup (about IPR)

Another editing remnant:

>  (10) Have all references within this been document been identified [...]

s/this been/this/

>  (11) List other RFCs that this document obsoletes, and indicate whether
>       the to-be-obsolete RFCs are listed in both the title page header
>       as well as in the Abstract and Introduction. Which if these RFCs,
>       if any, are to be moved to Historic? Is this change of status
>       explicitly stated in the document Introduction.

s/./?/

>  (12) List other RFCs that this document updates, and indicate whether
>       they appear in both the title page header as well as in the
>       Abstract and Introduction.

There was some recent chatter about whether or not it's appropriate to list=
 these things in both places as well as the title page header.  Was there c=
onsensus?  If so, should these two be updated?

-MSK

From housley@vigilsec.com  Thu Feb  9 22:04:10 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 4822A21F8577 for <wgchairs@ietfa.amsl.com>; Thu,  9 Feb 2012 22:04:10 -0800 (PST)
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 HL-XUZnAg6W7 for <wgchairs@ietfa.amsl.com>; Thu,  9 Feb 2012 22:04:09 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id C04C021F8571 for <wgchairs@ietf.org>; Thu,  9 Feb 2012 22:04:09 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id C4D62F24035; Fri, 10 Feb 2012 01:05:05 -0500 (EST)
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 Wp7DioTl1K2M; Fri, 10 Feb 2012 01:04:08 -0500 (EST)
Received: from [10.71.30.172] (wsip-184-191-191-52.sd.sd.cox.net [184.191.191.52]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id DD55B9A4732; Fri, 10 Feb 2012 01:05:04 -0500 (EST)
Subject: Re: DRAFT Revision to the WG Document Writeup (about IPR)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F19C9A7DCE1@EXCH-C2.corp.cloudmark.com>
Date: Fri, 10 Feb 2012 01:04:07 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <93A55A3A-381D-4A70-BDC7-9F9F6CF4193D@vigilsec.com>
References: <AE35FF1F-47D2-4AB3-B074-6CCBA5B6AC25@vigilsec.com> <201110271852.p9RIqcOO025921@mtv-core-3.cisco.com> <FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com> <F5833273385BB34F99288B3648C4F06F19C9A7DCE1@EXCH-C2.corp.cloudmark.com>
To: Murray S. Kucherawy <msk@cloudmark.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2012 06:04:10 -0000

Murray:

Thanks for the editorial changes.

>> (12) List other RFCs that this document updates, and indicate whether
>>      they appear in both the title page header as well as in the
>>      Abstract and Introduction.
>=20
> There was some recent chatter about whether or not it's appropriate to =
list these things in both places as well as the title page header.  Was =
there consensus?  If so, should these two be updated?

This remains consistent with the outcome I believe.  It is certainly =
consistent with IDnits.

Russ=

From david.black@emc.com  Fri Feb 10 07:02:22 2012
Return-Path: <david.black@emc.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8807621F86B8 for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 07:02:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.424
X-Spam-Level: 
X-Spam-Status: No, score=-109.424 tagged_above=-999 required=5 tests=[AWL=1.175, 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 UrBic1zAc4h6 for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 07:02:21 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 68A7321F86B3 for <wgchairs@ietf.org>; Fri, 10 Feb 2012 07:02:21 -0800 (PST)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q1AF273D011027 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 10 Feb 2012 10:02:17 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.226]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Fri, 10 Feb 2012 10:01:16 -0500
Received: from mxhub18.corp.emc.com (mxhub18.corp.emc.com [10.254.93.47]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q1AF1FnZ016518; Fri, 10 Feb 2012 10:01:16 -0500
Received: from mx14a.corp.emc.com ([169.254.1.94]) by mxhub18.corp.emc.com ([10.254.93.47]) with mapi; Fri, 10 Feb 2012 10:01:15 -0500
From: <david.black@emc.com>
To: <housley@vigilsec.com>, <wgchairs@ietf.org>
Date: Fri, 10 Feb 2012 10:01:13 -0500
Subject: RE: DRAFT Revision to the WG Document Writeup (about IPR)
Thread-Topic: DRAFT Revision to the WG Document Writeup (about IPR)
Thread-Index: Acznl/WWC98PloARSrK4QlNrAfGBGAAaggfg
Message-ID: <7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CA9E@MX14A.corp.emc.com>
References: <AE35FF1F-47D2-4AB3-B074-6CCBA5B6AC25@vigilsec.com> <201110271852.p9RIqcOO025921@mtv-core-3.cisco.com> <FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com>
In-Reply-To: <FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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, 10 Feb 2012 15:02:22 -0000

Russ,

I have a similar question to Murray's:

>  (11) List other RFCs that this document obsoletes, and indicate whether
>       the to-be-obsolete RFCs are listed in both the title page header
>       as well as in the Abstract and Introduction. Which if these RFCs,
>       if any, are to be moved to Historic? Is this change of status
>       explicitly stated in the document Introduction.
>=20
>  (12) List other RFCs that this document updates, and indicate whether
>       they appear in both the title page header as well as in the
>       Abstract and Introduction.

For both of these items, is the "and" in "Abstract and Introduction" intend=
ed
to be AND, OR, or XOR ?

I had a recent encounter w/idnits where it recommended that this info be
in the Abstract, but the authors chose the Introduction.

In (13), this sentence could be misread as requiring the writeup to nominat=
e
the IANA Experts:

>       List any IANA
>       Experts that the IESG will need to appoint during IESG Evaluation
>       for any new registries that require Expert Review for future
>       allocations.

Assuming that this was not intended, here's an attempt at a rewrite:

        List any new registries that require Expert Review for future
        allocations.  Is there any guidance that the IESG would find useful
        in appointing the IANA Experts for these new registries?  If so,
        provide it here, keeping in mind that this questionnaire is publicl=
y
        available.
=09
The "keeping in mind" is intended to provide a hint along the lines of "if
you nominate IANA Experts here, make sure you've asked them first" ;-).

Thanks,
--David


> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On Beh=
alf Of Russ Housley
> Sent: Thursday, February 09, 2012 9:01 PM
> To: IETF WG Chairs
> Subject: Re: DRAFT Revision to the WG Document Writeup (about IPR)
>=20
> It has taken me a very long time to incorporate all of the comments into =
a revised draft of the WG
> Document Writeup.  Here is the revision.  Please review and comment.
>=20
> Russ
>=20
> =3D =3D =3D =3D =3D =3D =3D =3D =3D
>=20
> Document Writeup
>=20
> As required by RFC 4858, this is the current template for the Document
> Shepherd Write-Up.
>=20
> Changes are expected over time. This DRAFT version is dated
> 9 February 2012.
>=20
>   (1) Briefly describe the review of this document that was
>       performed by the Document Shepherd.  If this version of the
>       document is not ready for publication, please explain why the
>       document is being forwarded to the IESG.
>=20
>   (2) Has the document had adequate review both from WG participants?
>       Does the Document Shepherd have any concerns about the depth or
>       breadth of the reviews that have been performed?
>=20
>   (3) Do portions of the document need review from a particular or
>       from broader perspective, e.g., security, operational complexity,
>       AAA, DNS, DHCP, XML, or internationalization? If so, describe the
>       review that took place.
>=20
>   (4) Describe any specific concerns or issues that the Document
>       Shepherd has with this document that the Responsible Area
>       Director and/or the IESG should be aware of? For example,
>       perhaps he or she is uncomfortable with certain parts of the
>       document, or has concerns whether there really is a need for it.
>       In any event, if the WG has discussed those issues and has
>       indicated that it still wishes to advance the document, detail
>       those concerns here.
>=20
>   (5) Has an IPR disclosure been filed that references this document?
>       If so, summarize any WG discussion and conclusion regarding the
>       IPR disclosures.
>=20
>   (6) How solid is the WG consensus behind this document? Does it
>       represent the strong concurrence of a few individuals, with
>       others being silent, or does the WG as a whole understand and
>       agree with it?
>=20
>   (7) Has anyone threatened an appeal or otherwise indicated extreme
>       discontent? If so, please summarise the areas of conflict in
>       separate email messages to the Responsible Area Director. (It
>       should be in a separate email because this questionnaire is
>       publicly available.)
>=20
>   (8) Identify any ID nits the Document Shepherd has found in this
>       document. (See the Internet-Drafts Checklist and
>       http://www.ietf.org/tools/idnits/). Boilerplate checks are not
>       enough; this check needs to be thorough.
>=20
>   (9) Describe how the document meets any required formal review
>       criteria, such as the MIB Doctor, media type, and URI type
>       reviews.
>=20
>  (10) Have all references within this been document been identified
>       as either normative and informative? Are there normative
>       references to documents that are not ready for advancement or
>       are otherwise in an unclear state? If such normative references
>       exist, what is the plan for their completion? Are there normative
>       references that are downward references (see [RFC3967])? If so,
>       list these downward references to support the Area Director in
>       the Last Call procedure.
>=20
>  (11) List other RFCs that this document obsoletes, and indicate whether
>       the to-be-obsolete RFCs are listed in both the title page header
>       as well as in the Abstract and Introduction. Which if these RFCs,
>       if any, are to be moved to Historic? Is this change of status
>       explicitly stated in the document Introduction.
>=20
>  (12) List other RFCs that this document updates, and indicate whether
>       they appear in both the title page header as well as in the
>       Abstract and Introduction.
>=20
>  (13) Describe the Document Shepherd's review of the IANA considerations
>       section, especially with regard to its consistency with the body
>       of the document. Confirm that all protocol extensions that the
>       document makes are associated with the appropriate reservations
>       in IANA registries. Confirm that any referenced IANA registries
>       have been clearly identified. Confirm that newly created IANA
>       registries include a detailed specification of the initial
>       contents for the registry, that allocations procedures for
>       future registrations are defined, and a reasonable name for the
>       new registry has been suggested (see [RFC5226]). List any IANA
>       Experts that the IESG will need to appoint during IESG Evaluation
>       for any new registries that require Expert Review for future
>       allocations.
>=20
>  (14) Describe reviews and automated checks performed by the Document
>       Shepherd to validate sections of the document written in a formal
>       language, such as XML code, BNF rules, MIB definitions, etc.
>=20
>  (14) The IESG approval announcement includes a Document Announcement
>       Write-Up. Please provide such a Document Announcement Write-Up.
>       Recent examples can be found in the "Action" announcements for
>       approved documents. The approval announcement contains the
>       following sections:
>=20
>       Technical Summary
>=20
>         Relevant content can frequently be found in the abstract
>         and/or introduction of the document. If not, this may be
>         an indication that there are deficiencies in the abstract
>         or introduction.
>=20
>       Working Group Summary
>=20
>         Was there anything in WG process that is worth noting? For
>         example, was there controversy about particular points or
>         were there decisions where the consensus was particularly
>         rough?
>=20
>       Document Quality
>=20
>         Are there existing implementations of the protocol? Have a
>         significant number of vendors indicated their plan to
>         implement the specification? Are there any reviewers that
>         merit special mention as having done a thorough review,
>         e.g., one that resulted in important changes or a
>         conclusion that the document had no substantive issues? If
>         there was a MIB Doctor, Media Type or other expert review,
>         what was its course (briefly)? In the case of a Media Type
>         review, on what date was the request posted?
>=20
>       Personnel
>=20
>         Who is the Document Shepherd? Who is the Responsible Area
>         Director.
>=20


From housley@vigilsec.com  Fri Feb 10 07:21:21 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 62B4D21F869D for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 07:21:21 -0800 (PST)
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 0QtETlw6O9V7 for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 07:21:20 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 5751521F8699 for <wgchairs@ietf.org>; Fri, 10 Feb 2012 07:21:20 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 5DAE2F24112; Fri, 10 Feb 2012 10:21:25 -0500 (EST)
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 tsIl3JhJEkQL; Fri, 10 Feb 2012 10:21:14 -0500 (EST)
Received: from [10.242.25.99] (mb70f36d0.tmodns.net [208.54.15.183]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id B73E3F24111; Fri, 10 Feb 2012 10:21:23 -0500 (EST)
Subject: Re: DRAFT Revision to the WG Document Writeup (about IPR)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <EDEC7EF5CF8C23A7A81ECB27@PST.JCK.COM>
Date: Fri, 10 Feb 2012 10:21:14 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <9D8F4BB8-883A-44A2-9F15-AFFD381A8E75@vigilsec.com>
References: <AE35FF1F-47D2-4AB3-B074-6CCBA5B6AC25@vigilsec.com> <201110271852.p9RIqcOO025921@mtv-core-3.cisco.com> <FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com> <F5833273385BB34F99288B3648C4F06F19C9A7DCE1@EXCH-C2.corp.cloudmark.com> <93A55A3A-381D-4A70-BDC7-9F9F6CF4193D@vigilsec.com> <EDEC7EF5CF8C23A7A81ECB27@PST.JCK.COM>
To: John C Klensin <john@jck.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2012 15:21:21 -0000

John:

How about:

 (12) List other RFCs that this document updates, and indicate whether
      they appear in both the title page header as well as in the
      Abstract and Introduction. If the updated RFCs are not listed
      in the Abstract and Introduction, explain why, and point to part
      of the document that describes the nature of the updates. If this
      information is not in the document, explain why  the WG considers
      it unnecessary.

I will put the discussion of "IESG Considerations" into the I-D on the =
agenda of a future meeting.

WG chair are the people that are most impacted by an update to this =
writeup template, so this seems like the best place to start the review =
process.  RFC 4858 does not expect a heavy-weight process to make =
changes to this template, so I had not thought much about further =
review.

Russ


On Feb 10, 2012, at 9:09 AM, John C Klensin wrote:

>=20
>=20
> --On Friday, February 10, 2012 01:04 -0500 Russ Housley
> <housley@vigilsec.com> wrote:
>=20
>>>> (12) List other RFCs that this document updates, and
>>>> indicate whether they appear in both the title page header
>>>>     as well as in the Abstract and Introduction.
>>>=20
>>> There was some recent chatter about whether or not it's
>>> appropriate to list these things in both places as well as
>>> the title page header.  Was there consensus?  If so, should
>>> these two be updated?
>>=20
>> This remains consistent with the outcome I believe.  It is
>> certainly consistent with IDnits.
>=20
> Russ, I think it is consistent with the outcome in the sense
> that it says "and indicate" rather than some variation on "make
> sure it is there".  But I think the the fuzziness might, itself,
> be confusing.  I also think that the other side of the
> discussion was actually to get some useful information in there.
> Usually "this updates RFC NNNN" is not really useful
> information, at least in the same sense that "this updates RFC
> NNNN, changing A, B, and C because..." might be.  Although
> others might disagree, I don't think one wants to go into detail
> here.  But would some phrasing like the following better address
> the issue (and what the IESG is trying to find out):
>=20
> 	If this document updates other RFCs, are they listed in
> 	the title page header and, if not, why not?  What other
> 	provisions have been made to identify the relationship
> 	(e.g., listing in the Abstract and/or Introduction)?
> 	Are the nature of the changes identified and explained
> 	and, if not, why does the WG consider that unnecesary?
>=20
> I think that can be tuned, but I think it would be useful to
> both get a little more information and to at least slightly
> reduce the guessing game around "if I 'indicate' that the
> information isn't in both the Abstract and Introduction, what
> happens then".   My understanding was that the IESG was inclined
> to move toward a "do it or explain why not (or at least that you
> thought about it and decided not to, rather that forgetting).
> If that is the case, then the text in the draft doesn't reflect
> it very well.
>=20
> Three additional thoughts:
>=20
> (1) I remain troubled by statements about consistency with
> IDnits.  IDNit is not a consensus document or algorithm.   If a
> statement or requirement is to be justified on the basis of
> consistency with something else, can we please confine the
> targets to things that have achieved community consensus.
>=20
> (2) The other idea that came up in that set of conversations was
> the possibility of allowing (or encouraging or requiring) more
> material with the same treatment as the IANA Considerations
> section, i.e., required in the I-D and for LC and other reviews,
> but with instructions to the RFC Editor to remove them before
> publication.  At least some of the people who are most strongly
> opposed to simple "This updates RFC xxxx" statements in
> abstracts would have no problem with a second paragraph of the
> abstract, or a special status paragraph, containing whatever
> information of that sort which the IESG thinks would be helpful
> if it were removed from there on publication.   Has the IESG
> discussed that option?
>=20
> (3) May I presume that a version of this draft will be exposed
> on the IETF list for comment before being made "official"?  It
> seems to me that there are a lot of people with experience as
> ADs, WG Chairs, and/or document shepherds, as well as people who
> might take on some of those roles soon, who don't happen to be
> on the WG Chairs list today.
>=20
> best,
>   john
>=20


From housley@vigilsec.com  Fri Feb 10 07:28:55 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 733DE21F872D for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 07:28:55 -0800 (PST)
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 TNfttGPzJhJy for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 07:28:54 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 1E39D21F8725 for <wgchairs@ietf.org>; Fri, 10 Feb 2012 07:28:50 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 49E3BF24111; Fri, 10 Feb 2012 10:29:00 -0500 (EST)
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 0IYFgQ4XZDMS; Fri, 10 Feb 2012 10:28:46 -0500 (EST)
Received: from [10.242.25.99] (mb70f36d0.tmodns.net [208.54.15.183]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 4B83BF2410D; Fri, 10 Feb 2012 10:28:59 -0500 (EST)
Subject: Re: DRAFT Revision to the WG Document Writeup (about IPR)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CA9E@MX14A.corp.emc.com>
Date: Fri, 10 Feb 2012 10:28:46 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <23B2E96E-08CE-40D1-8038-89A7A672E9F5@vigilsec.com>
References: <AE35FF1F-47D2-4AB3-B074-6CCBA5B6AC25@vigilsec.com> <201110271852.p9RIqcOO025921@mtv-core-3.cisco.com> <FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CA9E@MX14A.corp.emc.com>
To: <david.black@emc.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, 10 Feb 2012 15:28:55 -0000

David:

> I have a similar question to Murray's:
>=20
>> (11) List other RFCs that this document obsoletes, and indicate =
whether
>>      the to-be-obsolete RFCs are listed in both the title page header
>>      as well as in the Abstract and Introduction. Which if these =
RFCs,
>>      if any, are to be moved to Historic? Is this change of status
>>      explicitly stated in the document Introduction.
>>=20
>> (12) List other RFCs that this document updates, and indicate whether
>>      they appear in both the title page header as well as in the
>>      Abstract and Introduction.
>=20
> For both of these items, is the "and" in "Abstract and Introduction" =
intended
> to be AND, OR, or XOR ?

AND

> I had a recent encounter w/idnits where it recommended that this info =
be
> in the Abstract, but the authors chose the Introduction.

Summaries are made of the RFC repository that include the Abstract.  So, =
we are looking for "this document updated RFC XXXX" in the Abstract, and =
a description of the nature of the update in the Introduction.

> In (13), this sentence could be misread as requiring the writeup to =
nominate
> the IANA Experts:
>=20
>>      List any IANA
>>      Experts that the IESG will need to appoint during IESG =
Evaluation
>>      for any new registries that require Expert Review for future
>>      allocations.
>=20
> Assuming that this was not intended, here's an attempt at a rewrite:
>=20
>        List any new registries that require Expert Review for future
>        allocations.  Is there any guidance that the IESG would find =
useful
>        in appointing the IANA Experts for these new registries?  If =
so,
>        provide it here, keeping in mind that this questionnaire is =
publicly
>        available.
> =09
> The "keeping in mind" is intended to provide a hint along the lines of =
"if
> you nominate IANA Experts here, make sure you've asked them first" =
;-).

How about:

 (13) Describe the Document Shepherd's review of the IANA considerations
      section, especially with regard to its consistency with the body
      of the document. Confirm that all protocol extensions that the
      document makes are associated with the appropriate reservations
      in IANA registries. Confirm that any referenced IANA registries
      have been clearly identified. Confirm that newly created IANA
      registries include a detailed specification of the initial
      contents for the registry, that allocations procedures for
      future registrations are defined, and a reasonable name for the
      new registry has been suggested (see [RFC5226]). List any new
      registries that require Expert Review for future allocations.
      Provide any public guidance that the IESG would find useful in
      selecting the IANA Experts for these new registries.

Russ


From david.black@emc.com  Fri Feb 10 07:51:36 2012
Return-Path: <david.black@emc.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C71321F8604 for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 07:51:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.436
X-Spam-Level: 
X-Spam-Status: No, score=-109.436 tagged_above=-999 required=5 tests=[AWL=1.163, 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 erC2YUHHbQV8 for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 07:51:35 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id DA80321F85FB for <wgchairs@ietf.org>; Fri, 10 Feb 2012 07:51:34 -0800 (PST)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q1AFpLfO012422 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 10 Feb 2012 10:51:33 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.145]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Fri, 10 Feb 2012 10:51:11 -0500
Received: from mxhub02.corp.emc.com (mxhub02.corp.emc.com [10.254.141.104]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q1AFofdN005260; Fri, 10 Feb 2012 10:50:42 -0500
Received: from mx14a.corp.emc.com ([169.254.1.94]) by mxhub02.corp.emc.com ([10.254.141.104]) with mapi; Fri, 10 Feb 2012 10:51:09 -0500
From: <david.black@emc.com>
To: <housley@vigilsec.com>
Date: Fri, 10 Feb 2012 10:51:08 -0500
Subject: RE: DRAFT Revision to the WG Document Writeup (about IPR)
Thread-Topic: DRAFT Revision to the WG Document Writeup (about IPR)
Thread-Index: AczoCLvrHC/KwuKRTbODIYEKt8K1vAAAlauw
Message-ID: <7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CAE1@MX14A.corp.emc.com>
References: <AE35FF1F-47D2-4AB3-B074-6CCBA5B6AC25@vigilsec.com> <201110271852.p9RIqcOO025921@mtv-core-3.cisco.com> <FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CA9E@MX14A.corp.emc.com> <23B2E96E-08CE-40D1-8038-89A7A672E9F5@vigilsec.com>
In-Reply-To: <23B2E96E-08CE-40D1-8038-89A7A672E9F5@vigilsec.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: 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, 10 Feb 2012 15:51:36 -0000

Russ,

> > For both of these items, is the "and" in "Abstract and Introduction"
> > intended to be AND, OR, or XOR ?
>=20
> AND

Suggested edit for clarity in items 11 and 12:

OLD
	both the title page header as well as in the Abstract
	and Introduction
NEW
	all three of a) the title page header, b) the Abstract
	and c) the Introduction.
END

Your revised text for (13) looks fine to me.

Thanks,
--David

> -----Original Message-----
> From: Russ Housley [mailto:housley@vigilsec.com]
> Sent: Friday, February 10, 2012 10:29 AM
> To: Black, David
> Cc: wgchairs@ietf.org
> Subject: Re: DRAFT Revision to the WG Document Writeup (about IPR)
>=20
>=20
> David:
>=20
> > I have a similar question to Murray's:
> >
> >> (11) List other RFCs that this document obsoletes, and indicate whethe=
r
> >>      the to-be-obsolete RFCs are listed in both the title page header
> >>      as well as in the Abstract and Introduction. Which if these RFCs,
> >>      if any, are to be moved to Historic? Is this change of status
> >>      explicitly stated in the document Introduction.
> >>
> >> (12) List other RFCs that this document updates, and indicate whether
> >>      they appear in both the title page header as well as in the
> >>      Abstract and Introduction.
> >
> > For both of these items, is the "and" in "Abstract and Introduction" in=
tended
> > to be AND, OR, or XOR ?
>=20
> AND
>=20
> > I had a recent encounter w/idnits where it recommended that this info b=
e
> > in the Abstract, but the authors chose the Introduction.
>=20
> Summaries are made of the RFC repository that include the Abstract.  So, =
we are looking for "this
> document updated RFC XXXX" in the Abstract, and a description of the natu=
re of the update in the
> Introduction.
>=20
> > In (13), this sentence could be misread as requiring the writeup to nom=
inate
> > the IANA Experts:
> >
> >>      List any IANA
> >>      Experts that the IESG will need to appoint during IESG Evaluation
> >>      for any new registries that require Expert Review for future
> >>      allocations.
> >
> > Assuming that this was not intended, here's an attempt at a rewrite:
> >
> >        List any new registries that require Expert Review for future
> >        allocations.  Is there any guidance that the IESG would find use=
ful
> >        in appointing the IANA Experts for these new registries?  If so,
> >        provide it here, keeping in mind that this questionnaire is publ=
icly
> >        available.
> >
> > The "keeping in mind" is intended to provide a hint along the lines of =
"if
> > you nominate IANA Experts here, make sure you've asked them first" ;-).
>=20
> How about:
>=20
>  (13) Describe the Document Shepherd's review of the IANA considerations
>       section, especially with regard to its consistency with the body
>       of the document. Confirm that all protocol extensions that the
>       document makes are associated with the appropriate reservations
>       in IANA registries. Confirm that any referenced IANA registries
>       have been clearly identified. Confirm that newly created IANA
>       registries include a detailed specification of the initial
>       contents for the registry, that allocations procedures for
>       future registrations are defined, and a reasonable name for the
>       new registry has been suggested (see [RFC5226]). List any new
>       registries that require Expert Review for future allocations.
>       Provide any public guidance that the IESG would find useful in
>       selecting the IANA Experts for these new registries.
>=20
> Russ
>=20


From john@jck.com  Fri Feb 10 06:09:30 2012
Return-Path: <john@jck.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE66D21F871A for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 06:09:30 -0800 (PST)
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 YNEu7gcT4e9A for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 06:09:30 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 0E40A21F871B for <wgchairs@ietf.org>; Fri, 10 Feb 2012 06:09:30 -0800 (PST)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john@jck.com>) id 1Rvr6V-0002qv-3Y; Fri, 10 Feb 2012 09:05:35 -0500
Date: Fri, 10 Feb 2012 09:09:22 -0500
From: John C Klensin <john@jck.com>
To: Russ Housley <housley@vigilsec.com>, "Murray S. Kucherawy" <msk@cloudmark.com>
Subject: Re: DRAFT Revision to the WG Document Writeup (about IPR)
Message-ID: <EDEC7EF5CF8C23A7A81ECB27@PST.JCK.COM>
In-Reply-To: <93A55A3A-381D-4A70-BDC7-9F9F6CF4193D@vigilsec.com>
References: <AE35FF1F-47D2-4AB3-B074-6CCBA5B6AC25@vigilsec.com> <201110271852.p9RIqcOO025921@mtv-core-3.cisco.com> <FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com> <F5833273385BB34F99288B3648C4F06F19C9A7DCE1@EXCH-C2.corp.cloudmark.com> <93A55A3A-381D-4A70-BDC7-9F9F6CF4193D@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
X-Mailman-Approved-At: Fri, 10 Feb 2012 08:24:53 -0800
Cc: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2012 14:09:31 -0000

--On Friday, February 10, 2012 01:04 -0500 Russ Housley
<housley@vigilsec.com> wrote:

>>> (12) List other RFCs that this document updates, and
>>> indicate whether they appear in both the title page header
>>>      as well as in the Abstract and Introduction.
>> 
>> There was some recent chatter about whether or not it's
>> appropriate to list these things in both places as well as
>> the title page header.  Was there consensus?  If so, should
>> these two be updated?
> 
> This remains consistent with the outcome I believe.  It is
> certainly consistent with IDnits.

Russ, I think it is consistent with the outcome in the sense
that it says "and indicate" rather than some variation on "make
sure it is there".  But I think the the fuzziness might, itself,
be confusing.  I also think that the other side of the
discussion was actually to get some useful information in there.
Usually "this updates RFC NNNN" is not really useful
information, at least in the same sense that "this updates RFC
NNNN, changing A, B, and C because..." might be.  Although
others might disagree, I don't think one wants to go into detail
here.  But would some phrasing like the following better address
the issue (and what the IESG is trying to find out):

	If this document updates other RFCs, are they listed in
	the title page header and, if not, why not?  What other
	provisions have been made to identify the relationship
	(e.g., listing in the Abstract and/or Introduction)?
	Are the nature of the changes identified and explained
	and, if not, why does the WG consider that unnecesary?

I think that can be tuned, but I think it would be useful to
both get a little more information and to at least slightly
reduce the guessing game around "if I 'indicate' that the
information isn't in both the Abstract and Introduction, what
happens then".   My understanding was that the IESG was inclined
to move toward a "do it or explain why not (or at least that you
thought about it and decided not to, rather that forgetting).
If that is the case, then the text in the draft doesn't reflect
it very well.

Three additional thoughts:

(1) I remain troubled by statements about consistency with
IDnits.  IDNit is not a consensus document or algorithm.   If a
statement or requirement is to be justified on the basis of
consistency with something else, can we please confine the
targets to things that have achieved community consensus.

(2) The other idea that came up in that set of conversations was
the possibility of allowing (or encouraging or requiring) more
material with the same treatment as the IANA Considerations
section, i.e., required in the I-D and for LC and other reviews,
but with instructions to the RFC Editor to remove them before
publication.  At least some of the people who are most strongly
opposed to simple "This updates RFC xxxx" statements in
abstracts would have no problem with a second paragraph of the
abstract, or a special status paragraph, containing whatever
information of that sort which the IESG thinks would be helpful
if it were removed from there on publication.   Has the IESG
discussed that option?

(3) May I presume that a version of this draft will be exposed
on the IETF list for comment before being made "official"?  It
seems to me that there are a lot of people with experience as
ADs, WG Chairs, and/or document shepherds, as well as people who
might take on some of those roles soon, who don't happen to be
on the WG Chairs list today.

best,
   john


From paul.hoffman@vpnc.org  Fri Feb 10 08:51:39 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 781CA21F86DA for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 08:51:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.562
X-Spam-Level: 
X-Spam-Status: No, score=-102.562 tagged_above=-999 required=5 tests=[AWL=0.037, 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 GGjQfX6fcRLz for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 08:51:38 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 92FEB21F86FF for <wgchairs@ietf.org>; Fri, 10 Feb 2012 08:51:37 -0800 (PST)
Received: from [10.20.30.100] (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 q1AGpaIX049514 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 10 Feb 2012 09:51:37 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: DRAFT Revision to the WG Document Writeup (about IPR)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com>
Date: Fri, 10 Feb 2012 08:51:36 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <40962D04-5D33-45E8-A3F5-403DE5178A8A@vpnc.org>
References: <AE35FF1F-47D2-4AB3-B074-6CCBA5B6AC25@vigilsec.com> <201110271852.p9RIqcOO025921@mtv-core-3.cisco.com> <FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.1257)
Cc: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2012 16:51:39 -0000

Formatting nit, but one that bites me every time: the indenting makes =
copy-and-paste followed by adding answers hard.

Proposed change:

Current:

 (1) Briefly describe the review of this document that was
     performed by the Document Shepherd.  If this version of the
     document is not ready for publication, please explain why the
     document is being forwarded to the IESG.


Proposed:

(1) Briefly describe the review of this document that was
performed by the Document Shepherd.  If this version of the
document is not ready for publication, please explain why the
document is being forwarded to the IESG.

This is particularly important for section 14 (well, the second 14: you =
have two :-) )

--Paul Hoffman


From lberger@labn.net  Fri Feb 10 09:05:52 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 3EDF721F860D for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 09:05:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.767
X-Spam-Level: 
X-Spam-Status: No, score=-98.767 tagged_above=-999 required=5 tests=[AWL=1.394, BAYES_00=-2.599, 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 mN6zcaFdIAVk for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 09:05:51 -0800 (PST)
Received: from oproxy1-pub.bluehost.com (oproxy1.bluehost.com [IPv6:2605:dc00:100:2::a1]) by ietfa.amsl.com (Postfix) with SMTP id 9411921F8605 for <wgchairs@ietf.org>; Fri, 10 Feb 2012 09:05:51 -0800 (PST)
Received: (qmail 13320 invoked by uid 0); 10 Feb 2012 17:05:50 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by oproxy1.bluehost.com with SMTP; 10 Feb 2012 17:05:50 -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:Subject:To:MIME-Version:From:Date:Message-ID; bh=TWg1OpBARWiePiLJG2+uxiCDos4OpORbreg640HL7nk=;  b=jcbvClAqX5vzDLxvgN0fSwX5hBO2cFHhaz2nfSxP3ifoOJNThLhX/rFnBkg6mlEMUHERjJ3FIvnhBBWSrEFJhSajwsKcvNlZvUZApsB/jY37ptuSdo3ttSTb80dF4fiw;
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 1Rvtuv-0005hN-S9 for wgchairs@ietf.org; Fri, 10 Feb 2012 10:05:49 -0700
Message-ID: <4F354E6A.3000507@labn.net>
Date: Fri, 10 Feb 2012 12:05:46 -0500
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: IETF WG Chairs <wgchairs@ietf.org>
Subject: On encouraging compliance with IPR disclosure rules
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}
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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, 10 Feb 2012 17:05:52 -0000

Hello,

Our AD suggested that other chairs may be interested to our (CCAMP WG
Chairs) response to being one of the groups hit with a recent very late
IPR disclosure. We've sent two messages to the WG:

1) A general reminder of IPR disclosure requirements and process:
   http://www.ietf.org/mail-archive/web/ccamp/current/msg13082.html

2) An announcement of a WG process change, where a statement on
compliance with IETF IPR rules is required by all authors and
contributors listed in a draft before the draft is moved to the next
step in WG process:
  http://www.ietf.org/mail-archive/web/ccamp/current/msg13083.html

I personally think it would be worthwhile for such messages/policies to
be available in a standard form (perhaps from the IESG?) for use by any
WG, as well be supported in the datatracker I-D workflow.

Lou


From john-ietf@jck.com  Fri Feb 10 09:14:40 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 DA5B921F86A3 for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 09:14:40 -0800 (PST)
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 sLX+uZnDLJhz for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 09:14:40 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id E600C21F8668 for <wgchairs@ietf.org>; Fri, 10 Feb 2012 09:14:39 -0800 (PST)
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 1Rvtzi-00038L-CS; Fri, 10 Feb 2012 12:10:46 -0500
Date: Fri, 10 Feb 2012 12:14:33 -0500
From: John C Klensin <john-ietf@jck.com>
To: Russ Housley <housley@vigilsec.com>
Subject: Re: DRAFT Revision to the WG Document Writeup (about IPR)
Message-ID: <5C49D65A0D7484FBF56485F8@PST.JCK.COM>
In-Reply-To: <9D8F4BB8-883A-44A2-9F15-AFFD381A8E75@vigilsec.com>
References: <AE35FF1F-47D2-4AB3-B074-6CCBA5B6AC25@vigilsec.com> <201110271852.p9RIqcOO025921@mtv-core-3.cisco.com> <FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com> <F5833273385BB34F99288B3648C4F06F19C9A7DCE1@EXCH-C2.corp.cloudmark.com> <93A55A3A-381D-4A70-BDC7-9F9F6CF4193D@vigilsec.com> <EDEC7EF5CF8C23A7A81ECB27@PST.JCK.COM> <9D8F4BB8-883A-44A2-9F15-AFFD381A8E75@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: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2012 17:14:41 -0000

--On Friday, February 10, 2012 10:21 -0500 Russ Housley
<housley@vigilsec.com> wrote:

> John:
> 
> How about:
> 
>  (12) List other RFCs that this document updates, and indicate
> whether they appear in both the title page header as
> well as in the Abstract and Introduction. If the updated
> RFCs are not listed in the Abstract and Introduction,
> explain why, and point to part of the document that
> describes the nature of the updates. If this information
> is not in the document, explain why  the WG considers it
> unnecessary.

You should consider whether you want to ask for a pointer to the
explanation of the changes or an indication or why it is
unnecessary in all cases -- the above asks for that only if
there is no listing in the Abstract and Introduction.   But the
above is more than close enough to solve the problem I was
concerned about.  Thanks.

> I will put the discussion of "IESG Considerations" into the
> I-D on the agenda of a future meeting.

Thanks.  Wfm.  Just didn't want that possibility to get lost.

> WG chair are the people that are most impacted by an update to
> this writeup template, so this seems like the best place to
> start the review process.  RFC 4858 does not expect a
> heavy-weight process to make changes to this template, so I
> had not thought much about further review.

I think that sorting this out on the WG Chair list is absolutely
a reasonable thing to do.  Certainly, of all the lists we have,
it has the highest density of people who are likely to be
concerned enough about document submission issues to review a
draft carefully.  But there are folks in the community would
might be able to make useful contributions to this if they knew
about it; giving them that opportunity seems like a good idea.
Equally important, I think we have all noticed that things that
are designed as guidance (including IDnits, RFC 4859, etc.)
sometimes gradually slide into being normative requirements as,
e.g., ADs with insufficient organizational memory hold documents
up on review because those documents do not "conform" to that
guidance.

Because nasty surprises that show up after a WG thinks it is
finished are, at best, not helpful, I think the more that can be
done to expose the contents of (the nearly-finished form of) a
document like this to the community and get community sign-off,
the better off we all are.

YMMD.

     john

From john-ietf@jck.com  Fri Feb 10 09:29:23 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 CBA1A21F863B for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 09:29:23 -0800 (PST)
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 t2D5pIcG2+bO for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 09:29:23 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 162CA21F8625 for <wgchairs@ietf.org>; Fri, 10 Feb 2012 09:29:23 -0800 (PST)
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 1RvuDx-00039z-JD; Fri, 10 Feb 2012 12:25:29 -0500
Date: Fri, 10 Feb 2012 12:29:16 -0500
From: John C Klensin <john-ietf@jck.com>
To: Lou Berger <lberger@labn.net>, IETF WG Chairs <wgchairs@ietf.org>
Subject: Re: On encouraging compliance with IPR disclosure rules
Message-ID: <6E0F3EF65AE17D32372FDACE@PST.JCK.COM>
In-Reply-To: <4F354E6A.3000507@labn.net>
References: <4F354E6A.3000507@labn.net>
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: Fri, 10 Feb 2012 17:29:24 -0000

--On Friday, February 10, 2012 12:05 -0500 Lou Berger
<lberger@labn.net> wrote:

> Hello,
> 
> Our AD suggested that other chairs may be interested to our
> (CCAMP WG Chairs) response to being one of the groups hit with
> a recent very late IPR disclosure. We've sent two messages to
> the WG:
> 
> 1) A general reminder of IPR disclosure requirements and
> process:
> http://www.ietf.org/mail-archive/web/ccamp/current/msg13082.ht
> ml
> 
> 2) An announcement of a WG process change, where a statement on
> compliance with IETF IPR rules is required by all authors and
> contributors listed in a draft before the draft is moved to
> the next step in WG process:
> 
> http://www.ietf.org/mail-archive/web/ccamp/current/msg13083.ht
> ml
> 
> I personally think it would be worthwhile for such
> messages/policies to be available in a standard form (perhaps
> from the IESG?) for use by any WG, as well be supported in the
> datatracker I-D workflow.

Lou,

FWIW, I think these are very useful steps.   As discussed in
another context (I don't think on this list), I think there is a
third piece of the puzzle that would be helpful.  That would be
an explicit agreement with newly-appointed document editors and
with authors of documents that are made part of WG work programs
that they are bound by the IPR rules, that, as authors/editors,
they have special obligations to the WG to be alert to things
they ought to disclose and doing those disclosures promptly, and
(I hope this can be put more politely) if they are caught in
failure to disclose or making very late disclosures, they will
be removed as authors.

The difficulty with your two pieces without the third is that an
author could get up to the point that the WG is ready to advance
the document, get your sign-off request note, plead surprise,
and disclose at that time.   Obviously, that would be a better
time to get the disclosure than after Last Call (or later), but
it would imply that the WG needs to stop whatever it is doing on
a document it thought was just about finished and go back and
discuss whether a different path would have been chosen if the
IPR had been disclosed earlier.  At best, that would be
unpleasant to manage.

best,
   john


From john-ietf@jck.com  Fri Feb 10 09:41:51 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 7AA1F21F873C for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 09:41:51 -0800 (PST)
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 DcrYjfssH3wL for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 09:41:50 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id CEF7721F8739 for <wgchairs@ietf.org>; Fri, 10 Feb 2012 09:41:50 -0800 (PST)
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 1RvuPz-0003Ax-Q7; Fri, 10 Feb 2012 12:37:55 -0500
Date: Fri, 10 Feb 2012 12:41:42 -0500
From: John C Klensin <john-ietf@jck.com>
To: Russ Housley <housley@vigilsec.com>, david.black@emc.com
Subject: Re: DRAFT Revision to the WG Document Writeup (about IPR)
Message-ID: <712AA03F6F7D0C79D6138203@PST.JCK.COM>
In-Reply-To: <23B2E96E-08CE-40D1-8038-89A7A672E9F5@vigilsec.com>
References: <AE35FF1F-47D2-4AB3-B074-6CCBA5B6AC25@vigilsec.com> <201110271852.p9RIqcOO025921@mtv-core-3.cisco.com> <FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CA9E@MX14A.corp.emc.com> <23B2E96E-08CE-40D1-8038-89A7A672E9F5@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: 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, 10 Feb 2012 17:41:51 -0000

--On Friday, February 10, 2012 10:28 -0500 Russ Housley
<housley@vigilsec.com> wrote:

>...
>> I had a recent encounter w/idnits where it recommended that
>> this info be in the Abstract, but the authors chose the
>> Introduction.
> 
> Summaries are made of the RFC repository that include the
> Abstract.  So, we are looking for "this document updated RFC
> XXXX" in the Abstract, and a description of the nature of the
> update in the Introduction.

Hmm.  I didn't understand until now that those summaries of
published RFCs were part of the motivation for wanting that
sentence in the Abstract.    Given the number of RFCs that have
been published before this suggestion was made that don't
include an "updates" sentence in the Abstract, wouldn't it be a
lot more effective to recommend that those compiling such
summaries use the 
"updates" header or, even better, the RFC Index to capture that
information.

Since it hasn't been said on  this list, I'm strongly in favor
of putting "updates" information in the abstract if it is
critical to the reason the document was written.  But then, I'd
expect to see "This updates RFC NNNN by changing ... to ... and
...", which really might be useful abstract material.

For the more common case, someone who is looking for a RFC or
trying to understand what is covers is a lot more interested in
current specifications and that information rather than the
back-thread.    As others have pointed out, a forward thread is
actually a lot more important, but that information cannot be
obtained from abstracts (or any other part of a published
document).

best,
    john


From fandreas@cisco.com  Fri Feb 10 09:45:05 2012
Return-Path: <fandreas@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B094121F873C for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 09:45:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.999
X-Spam-Level: 
X-Spam-Status: No, score=-7.999 tagged_above=-999 required=5 tests=[AWL=2.600,  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 v6Jtzx43PatQ for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 09:45:04 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 24DB421F873E for <wgchairs@ietf.org>; Fri, 10 Feb 2012 09:45:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fandreas@cisco.com; l=1428; q=dns/txt; s=iport; t=1328895903; x=1330105503; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=fm8ZzVCkRwNqYBs/upGbaad8pe5Tod+Gl0Fx/0Ynmw8=; b=MSpb2NGw4dobVgugvOyrquDMIIVkKO1owvByvue4+KXtU+FaNALNfi3f bZp/uOYpYmPuhRFnErmMaZe7Pbzmw04EShuQE8vemjacJtXbOUf31z904 j9vU1C0IcGvGxfDpAVBPK0u6nO8GrrV3x3BYGov3L5gP3hdYGePzsqJRp k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAHhXNU+tJXG+/2dsb2JhbABEr1yBB4FyAQEBBBIBJUABEAsOCgkWDwkDAgECAUUGDQEHAQEFGYdjmkkBnl6LPQYiBAUGBAcBBQQDBAQHDgYBAwIUARiECg0PE4NDBIhJjGeTAg
X-IronPort-AV: E=Sophos;i="4.73,397,1325462400"; d="scan'208";a="57995128"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-1.cisco.com with ESMTP; 10 Feb 2012 17:45:02 +0000
Received: from rtp-fandreas-87113.cisco.com (rtp-fandreas-87113.cisco.com [10.117.7.94]) by rcdn-core2-3.cisco.com (8.14.3/8.14.3) with ESMTP id q1AHj2bh019705;  Fri, 10 Feb 2012 17:45:02 GMT
Message-ID: <4F35579E.5000009@cisco.com>
Date: Fri, 10 Feb 2012 12:45:02 -0500
From: Flemming Andreasen <fandreas@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.16) Gecko/20101125 Thunderbird/3.0.11
MIME-Version: 1.0
To: Lou Berger <lberger@labn.net>
Subject: Re: On encouraging compliance with IPR disclosure rules
References: <4F354E6A.3000507@labn.net>
In-Reply-To: <4F354E6A.3000507@labn.net>
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: Fri, 10 Feb 2012 17:45:05 -0000

Thanks for sharing this. The MMUSIC group finds itself in a somewhat 
similar situation in that we recently adopted two Huawei authored drafts 
as WG items. The drafts have been presented in a couple of meetings 
previously without any IPR disclosures, however this week we received 
IPR disclosures on both drafts from Huawei. Having a common approach on 
how to deal with this and hopefully avoid a repeat in the future in any 
group would be useful.

Thanks

-- Flemming



On 2/10/12 12:05 PM, Lou Berger wrote:
> Hello,
>
> Our AD suggested that other chairs may be interested to our (CCAMP WG
> Chairs) response to being one of the groups hit with a recent very late
> IPR disclosure. We've sent two messages to the WG:
>
> 1) A general reminder of IPR disclosure requirements and process:
>     http://www.ietf.org/mail-archive/web/ccamp/current/msg13082.html
>
> 2) An announcement of a WG process change, where a statement on
> compliance with IETF IPR rules is required by all authors and
> contributors listed in a draft before the draft is moved to the next
> step in WG process:
>    http://www.ietf.org/mail-archive/web/ccamp/current/msg13083.html
>
> I personally think it would be worthwhile for such messages/policies to
> be available in a standard form (perhaps from the IESG?) for use by any
> WG, as well be supported in the datatracker I-D workflow.
>
> Lou
>
>
>    

From touch@isi.edu  Fri Feb 10 09:47:06 2012
Return-Path: <touch@isi.edu>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 685DA21F8779 for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 09:47:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.981
X-Spam-Level: 
X-Spam-Status: No, score=-102.981 tagged_above=-999 required=5 tests=[AWL=-0.382, 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 ID64BfQeuIP3 for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 09:47:05 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 8400521F86BA for <wgchairs@ietf.org>; Fri, 10 Feb 2012 09:47:05 -0800 (PST)
Received: from [128.9.160.252] (pen.isi.edu [128.9.160.252]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id q1AHkhYD009857 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 10 Feb 2012 09:46:44 -0800 (PST)
Message-ID: <4F355803.2090103@isi.edu>
Date: Fri, 10 Feb 2012 09:46:43 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: On encouraging compliance with IPR disclosure rules
References: <4F354E6A.3000507@labn.net> <6E0F3EF65AE17D32372FDACE@PST.JCK.COM>
In-Reply-To: <6E0F3EF65AE17D32372FDACE@PST.JCK.COM>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2012 17:47:06 -0000

John,

On 2/10/2012 9:29 AM, John C Klensin wrote:
...
> Lou,
>
> FWIW, I think these are very useful steps.   As discussed in
> another context (I don't think on this list), I think there is a
> third piece of the puzzle that would be helpful.  That would be
> an explicit agreement with newly-appointed document editors and
> with authors of documents that are made part of WG work programs
> that they are bound by the IPR rules, that, as authors/editors,
> they have special obligations to the WG to be alert to things
> they ought to disclose and doing those disclosures promptly, and
> (I hope this can be put more politely) if they are caught in
> failure to disclose or making very late disclosures, they will
> be removed as authors.

"Authorship" is determined by many factors, the primary of which should 
be *who wrote what*. I've seen too many WGs 'trade' authorship for 
various things, which is ridiculous and offensive IMO.

Trading it as a threat against IPR disclosure isn't realistic at all...

> The difficulty with your two pieces without the third is that an
> author could get up to the point that the WG is ready to advance
> the document, get your sign-off request note, plead surprise,
> and disclose at that time.

It can easily be impossible to prove the difference between someone who 
lied vs. someone who legitimately didn't know until that time.

IPR disclosure is certainly a tricky issue, and we all hope people do 
the right thing, but short of mind-reading this isn't enforceable 
anyway. Threatening with removing someone as the author of work they 
wrote is both inappropriate and ineffective.

Joe

From lberger@labn.net  Fri Feb 10 09:48: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 A730F21F8794 for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 09:48:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.821
X-Spam-Level: 
X-Spam-Status: No, score=-98.821 tagged_above=-999 required=5 tests=[AWL=1.340, BAYES_00=-2.599, 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 Y34VvX9zl3+n for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 09:48:53 -0800 (PST)
Received: from oproxy1-pub.bluehost.com (oproxy1.bluehost.com [IPv6:2605:dc00:100:2::a1]) by ietfa.amsl.com (Postfix) with SMTP id C54F321F87A0 for <wgchairs@ietf.org>; Fri, 10 Feb 2012 09:48:52 -0800 (PST)
Received: (qmail 28054 invoked by uid 0); 10 Feb 2012 17:48:52 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by oproxy1.bluehost.com with SMTP; 10 Feb 2012 17:48: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=kC+q5mQRloyqpnXFAznA9oeuQoUwo+hQHP+1WeEzfU8=;  b=AU7ieytxBOW/p00yOHBYLvHtV7z4eLwtnXpVz5Jzx2Zf6S2ngx3Bw14rl7tIwRNprT5Mgw9BHhtWnzb0BXg5JBhPxHrVSjv2uKC1qQ2YHqh0F5/ViyqmP+5dhQcuqmPn;
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 1RvuaZ-0005zq-SO; Fri, 10 Feb 2012 10:48:52 -0700
Message-ID: <4F355880.4040607@labn.net>
Date: Fri, 10 Feb 2012 12:48:48 -0500
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 C Klensin <john-ietf@jck.com>
Subject: Re: On encouraging compliance with IPR disclosure rules
References: <4F354E6A.3000507@labn.net> <6E0F3EF65AE17D32372FDACE@PST.JCK.COM>
In-Reply-To: <6E0F3EF65AE17D32372FDACE@PST.JCK.COM>
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: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2012 17:48:54 -0000

John,
	I strongly agree, and think we need an ietf-wide policy that says
something along the lines of what you say:
> (I hope this can be put more politely) if they are caught in
> failure to disclose or making very late disclosures, they will
> be removed as authors.

In particular, I think contributors need to clearly understand the
implications of not following the the IPR disclosure rules.

When I've (privately) proposed similar language in the past the typical
response has been along the lines of that fixed rules are too simplistic
for the complicated real world of the IETF.  I don't agree; I think
there are some clear cases, and for these I think a formal
"consequences" rule is useful & justified.

I'd be happy to support and contribute to a draft on this topic, even
though it's likely to be a contentious discussion.

Lou

On 2/10/2012 12:29 PM, John C Klensin wrote:
> 
> 
> --On Friday, February 10, 2012 12:05 -0500 Lou Berger
> <lberger@labn.net> wrote:
> 
>> Hello,
>>
>> Our AD suggested that other chairs may be interested to our
>> (CCAMP WG Chairs) response to being one of the groups hit with
>> a recent very late IPR disclosure. We've sent two messages to
>> the WG:
>>
>> 1) A general reminder of IPR disclosure requirements and
>> process:
>> http://www.ietf.org/mail-archive/web/ccamp/current/msg13082.ht
>> ml
>>
>> 2) An announcement of a WG process change, where a statement on
>> compliance with IETF IPR rules is required by all authors and
>> contributors listed in a draft before the draft is moved to
>> the next step in WG process:
>>
>> http://www.ietf.org/mail-archive/web/ccamp/current/msg13083.ht
>> ml
>>
>> I personally think it would be worthwhile for such
>> messages/policies to be available in a standard form (perhaps
>> from the IESG?) for use by any WG, as well be supported in the
>> datatracker I-D workflow.
> 
> Lou,
> 
> FWIW, I think these are very useful steps.   As discussed in
> another context (I don't think on this list), I think there is a
> third piece of the puzzle that would be helpful.  That would be
> an explicit agreement with newly-appointed document editors and
> with authors of documents that are made part of WG work programs
> that they are bound by the IPR rules, that, as authors/editors,
> they have special obligations to the WG to be alert to things
> they ought to disclose and doing those disclosures promptly, and
> (I hope this can be put more politely) if they are caught in
> failure to disclose or making very late disclosures, they will
> be removed as authors.
> 
> The difficulty with your two pieces without the third is that an
> author could get up to the point that the WG is ready to advance
> the document, get your sign-off request note, plead surprise,
> and disclose at that time.   Obviously, that would be a better
> time to get the disclosure than after Last Call (or later), but
> it would imply that the WG needs to stop whatever it is doing on
> a document it thought was just about finished and go back and
> discuss whether a different path would have been chosen if the
> IPR had been disclosed earlier.  At best, that would be
> unpleasant to manage.
> 
> best,
>    john
> 
> 
> 
> 
> 

From pkyzivat@alum.mit.edu  Fri Feb 10 09:48:59 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 95F5121F87AA for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 09:48:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.605
X-Spam-Level: 
X-Spam-Status: No, score=-2.605 tagged_above=-999 required=5 tests=[AWL=-0.006, 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 BBxsEjc927YG for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 09:48:59 -0800 (PST)
Received: from QMTA11.westchester.pa.mail.comcast.net (qmta11.westchester.pa.mail.comcast.net [76.96.59.211]) by ietfa.amsl.com (Postfix) with ESMTP id 889F221F87A9 for <wgchairs@ietf.org>; Fri, 10 Feb 2012 09:48:58 -0800 (PST)
Received: from omta22.westchester.pa.mail.comcast.net ([76.96.62.73]) by QMTA11.westchester.pa.mail.comcast.net with comcast id YDfA1i0021ap0As5BHoz2C; Fri, 10 Feb 2012 17:48:59 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([24.62.229.5]) by omta22.westchester.pa.mail.comcast.net with comcast id YHoy1i01L07duvL3iHoyih; Fri, 10 Feb 2012 17:48:58 +0000
Message-ID: <4F355889.6070409@alum.mit.edu>
Date: Fri, 10 Feb 2012 12:48:57 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: On encouraging compliance with IPR disclosure rules
References: <4F354E6A.3000507@labn.net> <6E0F3EF65AE17D32372FDACE@PST.JCK.COM>
In-Reply-To: <6E0F3EF65AE17D32372FDACE@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: Fri, 10 Feb 2012 17:48:59 -0000

On 2/10/12 12:29 PM, John C Klensin wrote:

> FWIW, I think these are very useful steps.   As discussed in
> another context (I don't think on this list), I think there is a
> third piece of the puzzle that would be helpful.  That would be
> an explicit agreement with newly-appointed document editors and
> with authors of documents that are made part of WG work programs
> that they are bound by the IPR rules, that, as authors/editors,
> they have special obligations to the WG to be alert to things
> they ought to disclose and doing those disclosures promptly, and
> (I hope this can be put more politely) if they are caught in
> failure to disclose or making very late disclosures, they will
> be removed as authors.

While I agree with the philosophy expressed here, I wonder about the 
mechanics:

Surely we can remove someone as editor. But removing as author isn't so 
easy. (That discussion has been going on independently.) If this person 
has written most of the words in the doc, then it is pretty hard to 
remove them as an author of the document. (Unless of course the doc is 
also rewritten - presumably to avoid the IPR.)

Perhaps we could make past history of IPR disclosure problems a 
criterion in choosing editors of new documents, and of accepting new 
documents as WG drafts. But that does smack of blacklisting.

	Thanks,
	Paul

From adrian@olddog.co.uk  Fri Feb 10 09:59: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 D2AE921F879C for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 09:59:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.587
X-Spam-Level: 
X-Spam-Status: No, score=-2.587 tagged_above=-999 required=5 tests=[AWL=0.012,  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 PjoTp2KvwQgR for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 09:59:19 -0800 (PST)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id 5C89021F8797 for <wgchairs@ietf.org>; Fri, 10 Feb 2012 09:59:17 -0800 (PST)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id q1AHxFsb007239 for <wgchairs@ietf.org>; Fri, 10 Feb 2012 17:59:16 GMT
Received: from 950129200 (cust.static.46-14-88-124.swisscomdata.ch [46.14.88.124]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id q1AHxC84007203 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <wgchairs@ietf.org>; Fri, 10 Feb 2012 17:59:14 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'IETF WG Chairs'" <wgchairs@ietf.org>
Subject: More on encouraging compliance with IPR disclosure rules
Date: Fri, 10 Feb 2012 17:59:12 -0000
Message-ID: <019d01cce81d$b3c3a1e0$1b4ae5a0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Content-language: en-gb
Thread-Index: AczoHYGEU+Rl6sKYTNeCmS9eegaPxw==
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, 10 Feb 2012 17:59:21 -0000

WG chairs,

At the risk of hijacking a good thread, can I draw your attention to
draft-farrresnickel-ipr-sanctions and draft-polk-ipr-disclosure (soon to be
reposted).

The former is seeing discussion on the main ietf discussion list (ietf@ietf.org)
and I suggest that your views would be valuable there.

Thanks,
Adrian


From john-ietf@jck.com  Fri Feb 10 11:01:07 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 2DFCB21F8816 for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 11:01:07 -0800 (PST)
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=[AWL=1.000, BAYES_00=-2.599, GB_I_LETTER=-2, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KT7MJ7wdRNYw for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 11:01:06 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 2B2FA21F8815 for <wgchairs@ietf.org>; Fri, 10 Feb 2012 11:01:06 -0800 (PST)
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 1Rvveg-0003HC-LK; Fri, 10 Feb 2012 13:57:10 -0500
Date: Fri, 10 Feb 2012 14:00:57 -0500
From: John C Klensin <john-ietf@jck.com>
To: Joe Touch <touch@isi.edu>
Subject: Re: On encouraging compliance with IPR disclosure rules
Message-ID: <5B6C268752C8008FAFCDCDF5@PST.JCK.COM>
In-Reply-To: <4F355803.2090103@isi.edu>
References: <4F354E6A.3000507@labn.net> <6E0F3EF65AE17D32372FDACE@PST.JCK.COM> <4F355803.2090103@isi.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
Cc: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2012 19:01:07 -0000

--On Friday, February 10, 2012 09:46 -0800 Joe Touch
<touch@isi.edu> wrote:

> John,
>...
> "Authorship" is determined by many factors, the primary of
> which should be *who wrote what*. I've seen too many WGs
> 'trade' authorship for various things, which is ridiculous and
> offensive IMO.

Concur.
 
> Trading it as a threat against IPR disclosure isn't realistic
> at all...

Wasn't suggesting "trading" (or any of a number of odious
practices).   But the idea that someone can accept a position of
trust and responsibility with a WG (author, editor, chair, ...),
ignore IPR (or other important) requirements, plead ignorance,
and then continue in those roles really offends me.  Worse, it
is a threat to a the consensual model by which the IETF
functions -- a model that assumes we are working together in
good faith and mutual trust to get things done.  

Maybe that formal agreement with an author/editor should not
discuss sanctions but should merely require that person to stand
up in front of the WG and say "in front of all of you, I am
asserting that I understand the IPR policies and intend to
comply with them" because the really important thing is that
someone should not be able to wait until the 11th hour (or a few
hours past that) and then plead that they were ignorant earlier.


FWIW, from my point of view, an author's ignoring the IPR rules
is exactly the same sort of breach of trust with the WG that the
author's refusing to follow WG consensus decisions about what
should be in the document would be.   As a WG Chair, or even a
WG participant, I want and need to have that person out of that
role, independent of (and superceding) whatever other agreements
might have been made.

>> The difficulty with your two pieces without the third is that
>> an author could get up to the point that the WG is ready to
>> advance the document, get your sign-off request note, plead
>> surprise, and disclose at that time.
> 
> It can easily be impossible to prove the difference between
> someone who lied vs. someone who legitimately didn't know
> until that time.

True.  And not interesting.  I think we have a problem if WG
participants/ contributors can legitimately claim that they
didn't know the rules.  But, in the case of any author/editor
(or a WG Chair), I believe we are obligated to do everything
reasonable to make sure that the individual is informed, has
acknowledged being informed, and so that the claim cannot be
"legitimately" made.   And, once we have done that, we just need
to reject any "didn't know" or "was ignorant of the rules"
claims at illegitimate.  

That doesn't require making a judgment that someone was lying
rather than being stupid, careless, deliberately oblivious, or a
variety of other things (including being ordered to do so by a
malevolent company).   I don't think we need to go there and I
don't want to.    

Personally, as a WG chair, I would just want the individual out
as author or editor for breach of trust with the WG and the
IETF.  My reasons are less some idea about punishment than they
are about not wanting a person whom the WG can't trust to learn
and be responsive to the rules in a critical-path role during
any of Last Call, AUTH48, Errata processing, or preparation of
follow-on documents.

You may reasonably disagree, but I'd be interested in hearing
how you would propose to deal with breaches of the trust
relationship between the WG and an author/editor.  I don't find
"be nice, sympathize with the circumstances, and hope there will
never be another problem" particularly satisfying.  Perhaps I'm
in the minority.

> IPR disclosure is certainly a tricky issue, and we all hope
> people do the right thing, but short of mind-reading this
> isn't enforceable anyway. Threatening with removing someone as
> the author of work they wrote is both inappropriate and
> ineffective.

Again, not suggesting mind-reading.  I'm just suggesting that,
for people who are appointed and formally trusted to serve the
WG, we need to be sure they understand the rules when they take
on that responsibility and agree to follow them.  If we do that,
then anything out of line with the rules is a breach of trust
issue, not a question of what was in someone's mind.   I'm
perfectly ok with claims that breaches of trust are
unintentional.  They just don't change the required outcome for
me.   I can't imagine the IETF going for an "oath of office" for
authors/editors, WG Chairs, or others and am not proposing that,
but this is the sort of situation for which oaths of office were
created -- making certain that the expectations are agreed to
and that there is no doubt about what those expectations are..



--On Friday, February 10, 2012 12:48 -0500 Lou Berger
<lberger@labn.net> wrote:

>...
> In particular, I think contributors need to clearly understand
> the implications of not following the the IPR disclosure rules.

Up to a point, certainly.  But, per my response to Joe above, I
think the implications are much more that not following the
rules is a series breach of community trust and that the
community has the right and obligation to protect itself from
repetitions, than it is about punishment for bad deeds.

> When I've (privately) proposed similar language in the past
> the typical response has been along the lines of that fixed
> rules are too simplistic for the complicated real world of the
> IETF.  I don't agree; I think there are some clear cases, and
> for these I think a formal "consequences" rule is useful &
> justified.

As someone who has argued for a long time for maximum
flexibility, I agree about the fixed rules, but...   Perhaps,
given Joe's comments, my original proposal was better stated.
It wasn't "you will be fired" but "if you get yourself into that
situation, it will be considered as an implicit resignation".
That would give the WG Chair(s), presumably in consultation with
relevant ADs and maybe the WG, the flexibility to not accept the
resignation if conditions made that wise.  But we would have no
disputes over whether the WG Chair had the "right" to "fire"
someone over a disclosure problem either.

But I believe all of us have the necessary discretionary
authority to do that already (just as you had the necessary
discretionary authority to send out those two notes).  WG Chairs
have a lot of authority over who gets to be a document author or
editor.  While it is unusual, I've told people who have written
documents that become WG drafts that they don't get to hold the
pen for the WG because they are too committed to one position,
and I imagine that others have too.   So, from now on, I'm not
accepting anyone as a new author or editor for a WG document
without getting very explicit agreement that they understand the
IPR policy and intend to follow both its letter and its spirit.
I'd be delighted if the IESG and/or IETF Trust supplied me with
a standard template for getting that agreement and signoff, but
I don't think I need one.

    john





From touch@isi.edu  Fri Feb 10 11:13:43 2012
Return-Path: <touch@isi.edu>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3F2C21F87D2 for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 11:13:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.972
X-Spam-Level: 
X-Spam-Status: No, score=-102.972 tagged_above=-999 required=5 tests=[AWL=-0.373, 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 F+MUNJ3t0HST for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 11:13:40 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id C83B121F87CC for <wgchairs@ietf.org>; Fri, 10 Feb 2012 11:13:40 -0800 (PST)
Received: from [128.9.160.252] (pen.isi.edu [128.9.160.252]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id q1AJDR4t023968 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 10 Feb 2012 11:13:27 -0800 (PST)
Message-ID: <4F356C57.308@isi.edu>
Date: Fri, 10 Feb 2012 11:13:27 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: On encouraging compliance with IPR disclosure rules
References: <4F354E6A.3000507@labn.net> <6E0F3EF65AE17D32372FDACE@PST.JCK.COM> <4F355803.2090103@isi.edu> <5B6C268752C8008FAFCDCDF5@PST.JCK.COM>
In-Reply-To: <5B6C268752C8008FAFCDCDF5@PST.JCK.COM>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2012 19:13:43 -0000

Hi, John,

On 2/10/2012 11:00 AM, John C Klensin wrote:
> --On Friday, February 10, 2012 09:46 -0800 Joe Touch
> <touch@isi.edu>  wrote:
>
>> John,
>> ...
>> "Authorship" is determined by many factors, the primary of
>> which should be *who wrote what*. I've seen too many WGs
>> 'trade' authorship for various things, which is ridiculous and
>> offensive IMO.
>
> Concur.
>
>> Trading it as a threat against IPR disclosure isn't realistic
>> at all...
>
> Wasn't suggesting "trading" (or any of a number of odious
> practices).   But the idea that someone can accept a position of
> trust and responsibility with a WG (author, editor, chair, ...),
> ignore IPR (or other important) requirements, plead ignorance,
> and then continue in those roles really offends me.  Worse, it
> is a threat to a the consensual model by which the IETF
> functions -- a model that assumes we are working together in
> good faith and mutual trust to get things done.

Authorship is a matter of fact (granted, arguable fact in some cases).

Editors and chairs are positions of trust and responsibility. I agree 
that these can - and should - incur penalties when we have reasonable 
belief that *any* IETF/IRTF process requirements aren't being respected 
- those include IPR, trading authorship for cookies, etc.

> Maybe that formal agreement with an author/editor should not
> discuss sanctions but should merely require that person to stand
> up in front of the WG and say "in front of all of you, I am
> asserting that I understand the IPR policies and intend to
> comply with them" because the really important thing is that
> someone should not be able to wait until the 11th hour (or a few
> hours past that) and then plead that they were ignorant earlier.

They should be please ignorance of the rules. They can *always* plead 
ignorance of the IPR being relevant, or of the IPR itself - that's a 
permanent "escape mechanism" at any point, and I don't see a way around 
it unfortunately.

> FWIW, from my point of view, an author's ignoring the IPR rules
> is exactly the same sort of breach of trust with the WG that the
> author's refusing to follow WG consensus decisions about what
> should be in the document would be.   As a WG Chair, or even a
> WG participant, I want and need to have that person out of that
> role, independent of (and superceding) whatever other agreements
> might have been made.

You can't undo authorship unless you cut text, IMO.

You can and should undo chairship and editorship just fine in these 
cases, I agree.

However, not knowing the rules and not knowing about the IPR are 
equivalent in impact - in both cases the IETF finds out late - sometimes 
too late to do anything (or too late to *want* to do anything).

...
> You may reasonably disagree, but I'd be interested in hearing
> how you would propose to deal with breaches of the trust
> relationship between the WG and an author/editor.  I don't find
> "be nice, sympathize with the circumstances, and hope there will
> never be another problem" particularly satisfying.  Perhaps I'm
> in the minority.

See above - I agree with your suggestion for roles that are under the 
assignment of the IETF. I don't think it's appropriate for roles that 
should *never* (UNDER ANY CIRCIMSTANCES) be under the assignment of the 
IETF - and I put "author" in that bin.

Joe


From john-ietf@jck.com  Fri Feb 10 11:17:33 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 9828F21F853E for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 11:17:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.655
X-Spam-Level: 
X-Spam-Status: No, score=-103.655 tagged_above=-999 required=5 tests=[AWL=0.944, BAYES_00=-2.599, GB_I_LETTER=-2, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mhrq46G6LvfR for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 11:17:33 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id E732721F852D for <wgchairs@ietf.org>; Fri, 10 Feb 2012 11:17:32 -0800 (PST)
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 1Rvvud-0003Ik-VI; Fri, 10 Feb 2012 14:13:39 -0500
Date: Fri, 10 Feb 2012 14:17:27 -0500
From: John C Klensin <john-ietf@jck.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, wgchairs@ietf.org
Subject: Re: On encouraging compliance with IPR disclosure rules
Message-ID: <15F6D9AD40070C97603562A0@PST.JCK.COM>
In-Reply-To: <4F355889.6070409@alum.mit.edu>
References: <4F354E6A.3000507@labn.net> <6E0F3EF65AE17D32372FDACE@PST.JCK.COM> <4F355889.6070409@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: Fri, 10 Feb 2012 19:17:33 -0000

--On Friday, February 10, 2012 12:48 -0500 Paul Kyzivat
<pkyzivat@alum.mit.edu> wrote:

>...
> While I agree with the philosophy expressed here, I wonder
> about the mechanics:

See my previous note, but...

> Surely we can remove someone as editor. But removing as author
> isn't so easy. (That discussion has been going on
> independently.) If this person has written most of the words
> in the doc, then it is pretty hard to remove them as an author
> of the document. (Unless of course the doc is also rewritten -
> presumably to avoid the IPR.)

Nope.  RFC 3978, to which a pointer now appears in every new I-D
authors or editors post, clearly gives that text to the IETF to
do with as it likes, especially as part of the standards
process.  Taking someone who wrote a significant fraction of a
document and moving them to an acknowledgement that says as
little as "Thanks to Joe Furd for contributing very significant
portions of this document to the IETF" and as much more as the
WG believes to be appropriate.  We may have a problem with
patents and disclosure, but we have no problems at all in
copyrights in I-D text that is used by the IETF in creating IETF
documents (there are gray areas with other uses, but not with
that one).

Again, I really don't see a situation in which the WG had every
reason to believe that an author knew the IPR rules and still
didn't disclose something she clearly knew about earlier as
different from one in which the WG says "change section 1.2.3 to
read..." and the author refuses because he doesn't like the
change).

This would get complicated if the author, instead of saying "I
didn't understand or know about the IETF rules" said "I didn't
know about the IPR and couldn't reasonably be expected to know
about it".  Unless we have additional information that makes
those claims implausible, I think we have to accept that
position.  But, e.g., an inventor who is listed on a patent
application and who is also an IETF document author should be in
no position to claim lack of knowledge of either the IETF
policies or of the invention itself.


> Perhaps we could make past history of IPR disclosure problems
> a criterion in choosing editors of new documents, and of
> accepting new documents as WG drafts. But that does smack of
> blacklisting.

I wouldn't describe it that way and I'm not keeping black lists.
But I do believe that WGs, and WG Chairs, do have a
responsibility to ensure an appropriate relationship of trust
between the WG and the author -- trust that includes both "you
will keep the document in line with WG consensus" and "you will
work to make sure you are in compliance with the letter and
spirit of the IPR policy".

And, again, I see this much more in terms of making absolutely
sure that people are informed and cannot deny being informed and
in terms of trust than I do in terms of identifying and
punishing bad behavior.   In that regard, I think Adrian's work
on sanctions is very useful.  But, from my point of view, if we
get there, we have already failed, have a mess to clean up, and
want to deter future forms of bad behavior.   At least right
now, I'd rather concentrate on prevention and encouragement.

    john


From brian.e.carpenter@gmail.com  Fri Feb 10 11:19:12 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 33C7221F87EF for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 11:19:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.501
X-Spam-Level: 
X-Spam-Status: No, score=-103.501 tagged_above=-999 required=5 tests=[AWL=0.098, 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 9T8ZxNAL7qrQ for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 11:19:11 -0800 (PST)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 749F921F87C4 for <wgchairs@ietf.org>; Fri, 10 Feb 2012 11:19:11 -0800 (PST)
Received: by eekc41 with SMTP id c41so1069098eek.31 for <wgchairs@ietf.org>; Fri, 10 Feb 2012 11:19:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=BmtNVgcVr4WdM7/l87WacqejIE5/+2BXa3LJYdyZ5oY=; b=ccEc9EdPik119JZDaasF4OTewuSEWCvzZGQuhxbNKjgY0MzHuRxW00D97qxGUL5Hef dIdce7WdHzxgk9797Cll84OHIdT31n+Z84LMa35IIh2NwtNxXPHm67FSlVstaaFA/sh1 TU4Ad2DE1mF2eVvjvRK74nK8BIwKUfwV1nOhA=
Received: by 10.213.14.143 with SMTP id g15mr540509eba.82.1328901550301; Fri, 10 Feb 2012 11:19:10 -0800 (PST)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id o49sm25362781eeb.7.2012.02.10.11.19.07 (version=SSLv3 cipher=OTHER); Fri, 10 Feb 2012 11:19:09 -0800 (PST)
Message-ID: <4F356DA4.4000309@gmail.com>
Date: Sat, 11 Feb 2012 08:19:00 +1300
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: david.black@emc.com
Subject: Re: [BOFCHAIRS] DRAFT Revision to the WG Document Writeup (about IPR)
References: <AE35FF1F-47D2-4AB3-B074-6CCBA5B6AC25@vigilsec.com>	<201110271852.p9RIqcOO025921@mtv-core-3.cisco.com>	<FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com>	<7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CA9E@MX14A.corp.emc.com>	<23B2E96E-08CE-40D1-8038-89A7A672E9F5@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CAE1@MX14A.corp.emc.com>
In-Reply-To: <7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CAE1@MX14A.corp.emc.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: wgchairs@ietf.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: Fri, 10 Feb 2012 19:19:12 -0000

On 2012-02-11 04:51, david.black@emc.com wrote:
> Russ,
> 
>>> For both of these items, is the "and" in "Abstract and Introduction"
>>> intended to be AND, OR, or XOR ?
>> AND
> 
> Suggested edit for clarity in items 11 and 12:
> 
> OLD
> 	both the title page header as well as in the Abstract
> 	and Introduction
> NEW
> 	all three of a) the title page header, b) the Abstract
> 	and c) the Introduction.
> END

Stated like that, of course, it looks like a purely bureaucratic
and rather pointless requirement. Rather along the lines that John
suggested, the guideline (not rule) should probably be that
the Abstract indicates the scope of the update in very general
terms, and the Introduction describes it more specifically
(e.g. mentions which part of the protocol is modified).

    Brian

From pkyzivat@alum.mit.edu  Fri Feb 10 11:23:07 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 A4A5521F872D for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 11:23:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.593
X-Spam-Level: 
X-Spam-Status: No, score=-3.593 tagged_above=-999 required=5 tests=[AWL=1.006,  BAYES_00=-2.599, GB_I_LETTER=-2]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9zJzanaYDTiW for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 11:23:06 -0800 (PST)
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 616AB21F8710 for <wgchairs@ietf.org>; Fri, 10 Feb 2012 11:23:04 -0800 (PST)
Received: from omta22.westchester.pa.mail.comcast.net ([76.96.62.73]) by qmta08.westchester.pa.mail.comcast.net with comcast id YJ4N1i0051ap0As58KP45t; Fri, 10 Feb 2012 19:23:04 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([24.62.229.5]) by omta22.westchester.pa.mail.comcast.net with comcast id YKP41i00q07duvL3iKP40c; Fri, 10 Feb 2012 19:23:04 +0000
Message-ID: <4F356E97.9030901@alum.mit.edu>
Date: Fri, 10 Feb 2012 14:23:03 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: On encouraging compliance with IPR disclosure rules
References: <4F354E6A.3000507@labn.net> <6E0F3EF65AE17D32372FDACE@PST.JCK.COM> <4F355803.2090103@isi.edu> <5B6C268752C8008FAFCDCDF5@PST.JCK.COM>
In-Reply-To: <5B6C268752C8008FAFCDCDF5@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: Fri, 10 Feb 2012 19:23:07 -0000

John,

I largely agree with all you say below.
The one area that concerns me is when an IPR claim is filed at the last 
minute, and author(s) from the claiming company says "I didn't know 
about that" or "I just found out about that".

In some cases such a comment is clearly ingenuous (e.g. when the 
person's name is on the patent). But in other cases it might be true and 
it might be false but hard to prove. (It seems that in some cases 
companies are intentionally making it difficult for their standards 
participants to know what IPR they hold.)

In such cases, what are you suggesting the WG do?

	Thanks,
	Paul

On 2/10/12 2:00 PM, John C Klensin wrote:
> --On Friday, February 10, 2012 09:46 -0800 Joe Touch
> <touch@isi.edu>  wrote:
>
>> John,
>> ...
>> "Authorship" is determined by many factors, the primary of
>> which should be *who wrote what*. I've seen too many WGs
>> 'trade' authorship for various things, which is ridiculous and
>> offensive IMO.
>
> Concur.
>
>> Trading it as a threat against IPR disclosure isn't realistic
>> at all...
>
> Wasn't suggesting "trading" (or any of a number of odious
> practices).   But the idea that someone can accept a position of
> trust and responsibility with a WG (author, editor, chair, ...),
> ignore IPR (or other important) requirements, plead ignorance,
> and then continue in those roles really offends me.  Worse, it
> is a threat to a the consensual model by which the IETF
> functions -- a model that assumes we are working together in
> good faith and mutual trust to get things done.
>
> Maybe that formal agreement with an author/editor should not
> discuss sanctions but should merely require that person to stand
> up in front of the WG and say "in front of all of you, I am
> asserting that I understand the IPR policies and intend to
> comply with them" because the really important thing is that
> someone should not be able to wait until the 11th hour (or a few
> hours past that) and then plead that they were ignorant earlier.
>
>
> FWIW, from my point of view, an author's ignoring the IPR rules
> is exactly the same sort of breach of trust with the WG that the
> author's refusing to follow WG consensus decisions about what
> should be in the document would be.   As a WG Chair, or even a
> WG participant, I want and need to have that person out of that
> role, independent of (and superceding) whatever other agreements
> might have been made.
>
>>> The difficulty with your two pieces without the third is that
>>> an author could get up to the point that the WG is ready to
>>> advance the document, get your sign-off request note, plead
>>> surprise, and disclose at that time.
>>
>> It can easily be impossible to prove the difference between
>> someone who lied vs. someone who legitimately didn't know
>> until that time.
>
> True.  And not interesting.  I think we have a problem if WG
> participants/ contributors can legitimately claim that they
> didn't know the rules.  But, in the case of any author/editor
> (or a WG Chair), I believe we are obligated to do everything
> reasonable to make sure that the individual is informed, has
> acknowledged being informed, and so that the claim cannot be
> "legitimately" made.   And, once we have done that, we just need
> to reject any "didn't know" or "was ignorant of the rules"
> claims at illegitimate.
>
> That doesn't require making a judgment that someone was lying
> rather than being stupid, careless, deliberately oblivious, or a
> variety of other things (including being ordered to do so by a
> malevolent company).   I don't think we need to go there and I
> don't want to.
>
> Personally, as a WG chair, I would just want the individual out
> as author or editor for breach of trust with the WG and the
> IETF.  My reasons are less some idea about punishment than they
> are about not wanting a person whom the WG can't trust to learn
> and be responsive to the rules in a critical-path role during
> any of Last Call, AUTH48, Errata processing, or preparation of
> follow-on documents.
>
> You may reasonably disagree, but I'd be interested in hearing
> how you would propose to deal with breaches of the trust
> relationship between the WG and an author/editor.  I don't find
> "be nice, sympathize with the circumstances, and hope there will
> never be another problem" particularly satisfying.  Perhaps I'm
> in the minority.
>
>> IPR disclosure is certainly a tricky issue, and we all hope
>> people do the right thing, but short of mind-reading this
>> isn't enforceable anyway. Threatening with removing someone as
>> the author of work they wrote is both inappropriate and
>> ineffective.
>
> Again, not suggesting mind-reading.  I'm just suggesting that,
> for people who are appointed and formally trusted to serve the
> WG, we need to be sure they understand the rules when they take
> on that responsibility and agree to follow them.  If we do that,
> then anything out of line with the rules is a breach of trust
> issue, not a question of what was in someone's mind.   I'm
> perfectly ok with claims that breaches of trust are
> unintentional.  They just don't change the required outcome for
> me.   I can't imagine the IETF going for an "oath of office" for
> authors/editors, WG Chairs, or others and am not proposing that,
> but this is the sort of situation for which oaths of office were
> created -- making certain that the expectations are agreed to
> and that there is no doubt about what those expectations are..
>
>
>
> --On Friday, February 10, 2012 12:48 -0500 Lou Berger
> <lberger@labn.net>  wrote:
>
>> ...
>> In particular, I think contributors need to clearly understand
>> the implications of not following the the IPR disclosure rules.
>
> Up to a point, certainly.  But, per my response to Joe above, I
> think the implications are much more that not following the
> rules is a series breach of community trust and that the
> community has the right and obligation to protect itself from
> repetitions, than it is about punishment for bad deeds.
>
>> When I've (privately) proposed similar language in the past
>> the typical response has been along the lines of that fixed
>> rules are too simplistic for the complicated real world of the
>> IETF.  I don't agree; I think there are some clear cases, and
>> for these I think a formal "consequences" rule is useful&
>> justified.
>
> As someone who has argued for a long time for maximum
> flexibility, I agree about the fixed rules, but...   Perhaps,
> given Joe's comments, my original proposal was better stated.
> It wasn't "you will be fired" but "if you get yourself into that
> situation, it will be considered as an implicit resignation".
> That would give the WG Chair(s), presumably in consultation with
> relevant ADs and maybe the WG, the flexibility to not accept the
> resignation if conditions made that wise.  But we would have no
> disputes over whether the WG Chair had the "right" to "fire"
> someone over a disclosure problem either.
>
> But I believe all of us have the necessary discretionary
> authority to do that already (just as you had the necessary
> discretionary authority to send out those two notes).  WG Chairs
> have a lot of authority over who gets to be a document author or
> editor.  While it is unusual, I've told people who have written
> documents that become WG drafts that they don't get to hold the
> pen for the WG because they are too committed to one position,
> and I imagine that others have too.   So, from now on, I'm not
> accepting anyone as a new author or editor for a WG document
> without getting very explicit agreement that they understand the
> IPR policy and intend to follow both its letter and its spirit.
> I'd be delighted if the IESG and/or IETF Trust supplied me with
> a standard template for getting that agreement and signoff, but
> I don't think I need one.
>
>      john
>
>
>
>
>


From touch@isi.edu  Fri Feb 10 11:23:31 2012
Return-Path: <touch@isi.edu>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E18021F8737 for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 11:23:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.964
X-Spam-Level: 
X-Spam-Status: No, score=-104.964 tagged_above=-999 required=5 tests=[AWL=1.635, 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 KVPgIlbiC-6n for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 11:23:28 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 1269A21F8712 for <wgchairs@ietf.org>; Fri, 10 Feb 2012 11:23:28 -0800 (PST)
Received: from [128.9.160.252] (pen.isi.edu [128.9.160.252]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id q1AJMvSi015625 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 10 Feb 2012 11:22:57 -0800 (PST)
Message-ID: <4F356E91.3060504@isi.edu>
Date: Fri, 10 Feb 2012 11:22:57 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: On encouraging compliance with IPR disclosure rules
References: <4F354E6A.3000507@labn.net> <6E0F3EF65AE17D32372FDACE@PST.JCK.COM> <4F355889.6070409@alum.mit.edu> <15F6D9AD40070C97603562A0@PST.JCK.COM>
In-Reply-To: <15F6D9AD40070C97603562A0@PST.JCK.COM>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
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, 10 Feb 2012 19:23:31 -0000

On 2/10/2012 11:17 AM, John C Klensin wrote:
>
> --On Friday, February 10, 2012 12:48 -0500 Paul Kyzivat
> <pkyzivat@alum.mit.edu>  wrote:
>> Surely we can remove someone as editor. But removing as author
>> isn't so easy. (That discussion has been going on
>> independently.) If this person has written most of the words
>> in the doc, then it is pretty hard to remove them as an author
>> of the document. (Unless of course the doc is also rewritten -
>> presumably to avoid the IPR.)
>
> Nope.  RFC 3978, to which a pointer now appears in every new I-D
> authors or editors post, clearly gives that text to the IETF to
> do with as it likes, especially as part of the standards
> process.  Taking someone who wrote a significant fraction of a
> document and moving them to an acknowledgement that says as
> little as "Thanks to Joe Furd for contributing very significant
> portions of this document to the IETF" and as much more as the
> WG believes to be appropriate.  We may have a problem with
> patents and disclosure, but we have no problems at all in
> copyrights in I-D text that is used by the IETF in creating IETF
> documents (there are gray areas with other uses, but not with
> that one).

Authorship goes beyond copyright.

And it's not true that in all cases the IETF owns the copyright; that 
depends on the clauses of the I-D (e.g., if it's before it's a WG item).

I don't think authorship should be under WG control. Authorship should 
be determined by the extent of the contribution, period. The WG has 
other positions that it more appropriately controls - editorship, wg 
chair, etc.

Further, putting authorship under control of the WG sets up the 
potential for trading authorship for favors - which happens offensively 
often enough as it is.

Regardless of what IETF process says on this matter, meddling with 
authorship is a bad idea, period.

Joe

From lberger@labn.net  Fri Feb 10 11:30:16 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 20A4921F881A for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 11:30:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.871
X-Spam-Level: 
X-Spam-Status: No, score=-99.871 tagged_above=-999 required=5 tests=[AWL=2.290, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, GB_I_LETTER=-2, 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 eD4rV8HlVRK4 for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 11:30:11 -0800 (PST)
Received: from oproxy4-pub.bluehost.com (oproxy4.bluehost.com [IPv6:2605:dc00:100:2::a4]) by ietfa.amsl.com (Postfix) with SMTP id 9860421F86FD for <wgchairs@ietf.org>; Fri, 10 Feb 2012 11:30:11 -0800 (PST)
Received: (qmail 25833 invoked by uid 0); 10 Feb 2012 19:30:11 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by cpoproxy1.bluehost.com with SMTP; 10 Feb 2012 19:30:11 -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=C308WmOw9In5v4D56JMehihDzcXnfHgcUJnIGUeFmFs=;  b=iTFswBQtfFanobRNMHLEObN2em8sdXWJH6wGTNX3Ivm9fc3tQb70xpqP/2PFgHhb5G9cZnRAq4y7tXOPDf4fqZVyvK0cJAHEsXWfbwUzooNCI04nU9/aceO/qChedBQJ;
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 1RvwAc-0001J5-VE; Fri, 10 Feb 2012 12:30:11 -0700
Message-ID: <4F35703F.8010701@labn.net>
Date: Fri, 10 Feb 2012 14:30:07 -0500
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 C Klensin <john-ietf@jck.com>
Subject: Re: On encouraging compliance with IPR disclosure rules
References: <4F354E6A.3000507@labn.net> <6E0F3EF65AE17D32372FDACE@PST.JCK.COM> <4F355803.2090103@isi.edu> <5B6C268752C8008FAFCDCDF5@PST.JCK.COM>
In-Reply-To: <5B6C268752C8008FAFCDCDF5@PST.JCK.COM>
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: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2012 19:30:16 -0000

John,
	It seems this discussion is following much of the same path as some of
my/our private discussions and is largely how we ended up with the two
messages we sent.

I'd like to reiterate that authorship is not the same as being the
editor of a WG document, and not every author is listed on a cover page.
 I'm sensitive to some of the points being made with regard to
authorship.  Bu, as you you said, as Chair we have a lot of authority
over who is editor (and on the first page).  While, I'd prefer to see a
formal statement along the lines of "if you are found to be in violation
of the IETF process (by whatever definition is agreed to) that it will
no longer be reasonable for you to be editor or listed on the 1st page
of a draft", WG chairs already have the authority to implement such a
policy....

WRT to your last comment on a template for "agreement and signoff". What
do you think about the one we're using?  It's the 2nd URL in my earlier
message (which was based on text from our AD).

Lou

On 2/10/2012 2:00 PM, John C Klensin wrote:
> --On Friday, February 10, 2012 09:46 -0800 Joe Touch
> <touch@isi.edu> wrote:
> 
>> John,
>> ...
>> "Authorship" is determined by many factors, the primary of
>> which should be *who wrote what*. I've seen too many WGs
>> 'trade' authorship for various things, which is ridiculous and
>> offensive IMO.
> 
> Concur.
>  
>> Trading it as a threat against IPR disclosure isn't realistic
>> at all...
> 
> Wasn't suggesting "trading" (or any of a number of odious
> practices).   But the idea that someone can accept a position of
> trust and responsibility with a WG (author, editor, chair, ...),
> ignore IPR (or other important) requirements, plead ignorance,
> and then continue in those roles really offends me.  Worse, it
> is a threat to a the consensual model by which the IETF
> functions -- a model that assumes we are working together in
> good faith and mutual trust to get things done.  
> 
> Maybe that formal agreement with an author/editor should not
> discuss sanctions but should merely require that person to stand
> up in front of the WG and say "in front of all of you, I am
> asserting that I understand the IPR policies and intend to
> comply with them" because the really important thing is that
> someone should not be able to wait until the 11th hour (or a few
> hours past that) and then plead that they were ignorant earlier.
> 
> 
> FWIW, from my point of view, an author's ignoring the IPR rules
> is exactly the same sort of breach of trust with the WG that the
> author's refusing to follow WG consensus decisions about what
> should be in the document would be.   As a WG Chair, or even a
> WG participant, I want and need to have that person out of that
> role, independent of (and superceding) whatever other agreements
> might have been made.
> 
>>> The difficulty with your two pieces without the third is that
>>> an author could get up to the point that the WG is ready to
>>> advance the document, get your sign-off request note, plead
>>> surprise, and disclose at that time.
>>
>> It can easily be impossible to prove the difference between
>> someone who lied vs. someone who legitimately didn't know
>> until that time.
> 
> True.  And not interesting.  I think we have a problem if WG
> participants/ contributors can legitimately claim that they
> didn't know the rules.  But, in the case of any author/editor
> (or a WG Chair), I believe we are obligated to do everything
> reasonable to make sure that the individual is informed, has
> acknowledged being informed, and so that the claim cannot be
> "legitimately" made.   And, once we have done that, we just need
> to reject any "didn't know" or "was ignorant of the rules"
> claims at illegitimate.  
> 
> That doesn't require making a judgment that someone was lying
> rather than being stupid, careless, deliberately oblivious, or a
> variety of other things (including being ordered to do so by a
> malevolent company).   I don't think we need to go there and I
> don't want to.    
> 
> Personally, as a WG chair, I would just want the individual out
> as author or editor for breach of trust with the WG and the
> IETF.  My reasons are less some idea about punishment than they
> are about not wanting a person whom the WG can't trust to learn
> and be responsive to the rules in a critical-path role during
> any of Last Call, AUTH48, Errata processing, or preparation of
> follow-on documents.
> 
> You may reasonably disagree, but I'd be interested in hearing
> how you would propose to deal with breaches of the trust
> relationship between the WG and an author/editor.  I don't find
> "be nice, sympathize with the circumstances, and hope there will
> never be another problem" particularly satisfying.  Perhaps I'm
> in the minority.
> 
>> IPR disclosure is certainly a tricky issue, and we all hope
>> people do the right thing, but short of mind-reading this
>> isn't enforceable anyway. Threatening with removing someone as
>> the author of work they wrote is both inappropriate and
>> ineffective.
> 
> Again, not suggesting mind-reading.  I'm just suggesting that,
> for people who are appointed and formally trusted to serve the
> WG, we need to be sure they understand the rules when they take
> on that responsibility and agree to follow them.  If we do that,
> then anything out of line with the rules is a breach of trust
> issue, not a question of what was in someone's mind.   I'm
> perfectly ok with claims that breaches of trust are
> unintentional.  They just don't change the required outcome for
> me.   I can't imagine the IETF going for an "oath of office" for
> authors/editors, WG Chairs, or others and am not proposing that,
> but this is the sort of situation for which oaths of office were
> created -- making certain that the expectations are agreed to
> and that there is no doubt about what those expectations are..
> 
> 
> 
> --On Friday, February 10, 2012 12:48 -0500 Lou Berger
> <lberger@labn.net> wrote:
> 
>> ...
>> In particular, I think contributors need to clearly understand
>> the implications of not following the the IPR disclosure rules.
> 
> Up to a point, certainly.  But, per my response to Joe above, I
> think the implications are much more that not following the
> rules is a series breach of community trust and that the
> community has the right and obligation to protect itself from
> repetitions, than it is about punishment for bad deeds.
> 
>> When I've (privately) proposed similar language in the past
>> the typical response has been along the lines of that fixed
>> rules are too simplistic for the complicated real world of the
>> IETF.  I don't agree; I think there are some clear cases, and
>> for these I think a formal "consequences" rule is useful &
>> justified.
> 
> As someone who has argued for a long time for maximum
> flexibility, I agree about the fixed rules, but...   Perhaps,
> given Joe's comments, my original proposal was better stated.
> It wasn't "you will be fired" but "if you get yourself into that
> situation, it will be considered as an implicit resignation".
> That would give the WG Chair(s), presumably in consultation with
> relevant ADs and maybe the WG, the flexibility to not accept the
> resignation if conditions made that wise.  But we would have no
> disputes over whether the WG Chair had the "right" to "fire"
> someone over a disclosure problem either.
> 
> But I believe all of us have the necessary discretionary
> authority to do that already (just as you had the necessary
> discretionary authority to send out those two notes).  WG Chairs
> have a lot of authority over who gets to be a document author or
> editor.  While it is unusual, I've told people who have written
> documents that become WG drafts that they don't get to hold the
> pen for the WG because they are too committed to one position,
> and I imagine that others have too.   So, from now on, I'm not
> accepting anyone as a new author or editor for a WG document
> without getting very explicit agreement that they understand the
> IPR policy and intend to follow both its letter and its spirit.
> I'd be delighted if the IESG and/or IETF Trust supplied me with
> a standard template for getting that agreement and signoff, but
> I don't think I need one.
> 
>     john
> 
> 
> 
> 
> 
> 
> 
> 

From adrian@olddog.co.uk  Fri Feb 10 11:36:49 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 DE5F321F8800 for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 11:36:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.588
X-Spam-Level: 
X-Spam-Status: No, score=-3.588 tagged_above=-999 required=5 tests=[AWL=1.011,  BAYES_00=-2.599, GB_I_LETTER=-2]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vu3g0Zl-SJvh for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 11:36:46 -0800 (PST)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id 6983D21F880B for <wgchairs@ietf.org>; Fri, 10 Feb 2012 11:36:46 -0800 (PST)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id q1AJahWL006791;  Fri, 10 Feb 2012 19:36:43 GMT
Received: from 950129200 (cust.static.46-14-88-124.swisscomdata.ch [46.14.88.124]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id q1AJaeY7006771 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 10 Feb 2012 19:36:42 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Paul Kyzivat'" <pkyzivat@alum.mit.edu>, <wgchairs@ietf.org>
References: <4F354E6A.3000507@labn.net> <6E0F3EF65AE17D32372FDACE@PST.JCK.COM>	<4F355803.2090103@isi.edu> <5B6C268752C8008FAFCDCDF5@PST.JCK.COM> <4F356E97.9030901@alum.mit.edu>
In-Reply-To: <4F356E97.9030901@alum.mit.edu>
Subject: RE: On encouraging compliance with IPR disclosure rules
Date: Fri, 10 Feb 2012 19:36:41 -0000
Message-ID: <01b401cce82b$515e15e0$f41a41a0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Content-language: en-gb
Thread-Index: AQEzvzBEB/irVKyyg9XGvkhZeBmoTgMFXiSOAjR+2w0B4dMPdgJOIU25lx2H3/A=
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, 10 Feb 2012 19:36:49 -0000

Hi Paul,

You ask a reasonable question.
Please see draft-farrresnickel-ipr-sanctions for a discussion of how this cannot
be a fixed penalty scheme. 
There has to be discretion both in assessing the magnitude of the offence, and
the clarity of the violation.

Kind of business as usual for handling human interactions. "You'll know it when
you see it"

A

> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On Behalf
> Of Paul Kyzivat
> Sent: 10 February 2012 19:23
> To: wgchairs@ietf.org
> Subject: Re: On encouraging compliance with IPR disclosure rules
> 
> John,
> 
> I largely agree with all you say below.
> The one area that concerns me is when an IPR claim is filed at the last
> minute, and author(s) from the claiming company says "I didn't know
> about that" or "I just found out about that".
> 
> In some cases such a comment is clearly ingenuous (e.g. when the
> person's name is on the patent). But in other cases it might be true and
> it might be false but hard to prove. (It seems that in some cases
> companies are intentionally making it difficult for their standards
> participants to know what IPR they hold.)
> 
> In such cases, what are you suggesting the WG do?
> 
> 	Thanks,
> 	Paul
> 
> On 2/10/12 2:00 PM, John C Klensin wrote:
> > --On Friday, February 10, 2012 09:46 -0800 Joe Touch
> > <touch@isi.edu>  wrote:
> >
> >> John,
> >> ...
> >> "Authorship" is determined by many factors, the primary of
> >> which should be *who wrote what*. I've seen too many WGs
> >> 'trade' authorship for various things, which is ridiculous and
> >> offensive IMO.
> >
> > Concur.
> >
> >> Trading it as a threat against IPR disclosure isn't realistic
> >> at all...
> >
> > Wasn't suggesting "trading" (or any of a number of odious
> > practices).   But the idea that someone can accept a position of
> > trust and responsibility with a WG (author, editor, chair, ...),
> > ignore IPR (or other important) requirements, plead ignorance,
> > and then continue in those roles really offends me.  Worse, it
> > is a threat to a the consensual model by which the IETF
> > functions -- a model that assumes we are working together in
> > good faith and mutual trust to get things done.
> >
> > Maybe that formal agreement with an author/editor should not
> > discuss sanctions but should merely require that person to stand
> > up in front of the WG and say "in front of all of you, I am
> > asserting that I understand the IPR policies and intend to
> > comply with them" because the really important thing is that
> > someone should not be able to wait until the 11th hour (or a few
> > hours past that) and then plead that they were ignorant earlier.
> >
> >
> > FWIW, from my point of view, an author's ignoring the IPR rules
> > is exactly the same sort of breach of trust with the WG that the
> > author's refusing to follow WG consensus decisions about what
> > should be in the document would be.   As a WG Chair, or even a
> > WG participant, I want and need to have that person out of that
> > role, independent of (and superceding) whatever other agreements
> > might have been made.
> >
> >>> The difficulty with your two pieces without the third is that
> >>> an author could get up to the point that the WG is ready to
> >>> advance the document, get your sign-off request note, plead
> >>> surprise, and disclose at that time.
> >>
> >> It can easily be impossible to prove the difference between
> >> someone who lied vs. someone who legitimately didn't know
> >> until that time.
> >
> > True.  And not interesting.  I think we have a problem if WG
> > participants/ contributors can legitimately claim that they
> > didn't know the rules.  But, in the case of any author/editor
> > (or a WG Chair), I believe we are obligated to do everything
> > reasonable to make sure that the individual is informed, has
> > acknowledged being informed, and so that the claim cannot be
> > "legitimately" made.   And, once we have done that, we just need
> > to reject any "didn't know" or "was ignorant of the rules"
> > claims at illegitimate.
> >
> > That doesn't require making a judgment that someone was lying
> > rather than being stupid, careless, deliberately oblivious, or a
> > variety of other things (including being ordered to do so by a
> > malevolent company).   I don't think we need to go there and I
> > don't want to.
> >
> > Personally, as a WG chair, I would just want the individual out
> > as author or editor for breach of trust with the WG and the
> > IETF.  My reasons are less some idea about punishment than they
> > are about not wanting a person whom the WG can't trust to learn
> > and be responsive to the rules in a critical-path role during
> > any of Last Call, AUTH48, Errata processing, or preparation of
> > follow-on documents.
> >
> > You may reasonably disagree, but I'd be interested in hearing
> > how you would propose to deal with breaches of the trust
> > relationship between the WG and an author/editor.  I don't find
> > "be nice, sympathize with the circumstances, and hope there will
> > never be another problem" particularly satisfying.  Perhaps I'm
> > in the minority.
> >
> >> IPR disclosure is certainly a tricky issue, and we all hope
> >> people do the right thing, but short of mind-reading this
> >> isn't enforceable anyway. Threatening with removing someone as
> >> the author of work they wrote is both inappropriate and
> >> ineffective.
> >
> > Again, not suggesting mind-reading.  I'm just suggesting that,
> > for people who are appointed and formally trusted to serve the
> > WG, we need to be sure they understand the rules when they take
> > on that responsibility and agree to follow them.  If we do that,
> > then anything out of line with the rules is a breach of trust
> > issue, not a question of what was in someone's mind.   I'm
> > perfectly ok with claims that breaches of trust are
> > unintentional.  They just don't change the required outcome for
> > me.   I can't imagine the IETF going for an "oath of office" for
> > authors/editors, WG Chairs, or others and am not proposing that,
> > but this is the sort of situation for which oaths of office were
> > created -- making certain that the expectations are agreed to
> > and that there is no doubt about what those expectations are..
> >
> >
> >
> > --On Friday, February 10, 2012 12:48 -0500 Lou Berger
> > <lberger@labn.net>  wrote:
> >
> >> ...
> >> In particular, I think contributors need to clearly understand
> >> the implications of not following the the IPR disclosure rules.
> >
> > Up to a point, certainly.  But, per my response to Joe above, I
> > think the implications are much more that not following the
> > rules is a series breach of community trust and that the
> > community has the right and obligation to protect itself from
> > repetitions, than it is about punishment for bad deeds.
> >
> >> When I've (privately) proposed similar language in the past
> >> the typical response has been along the lines of that fixed
> >> rules are too simplistic for the complicated real world of the
> >> IETF.  I don't agree; I think there are some clear cases, and
> >> for these I think a formal "consequences" rule is useful&
> >> justified.
> >
> > As someone who has argued for a long time for maximum
> > flexibility, I agree about the fixed rules, but...   Perhaps,
> > given Joe's comments, my original proposal was better stated.
> > It wasn't "you will be fired" but "if you get yourself into that
> > situation, it will be considered as an implicit resignation".
> > That would give the WG Chair(s), presumably in consultation with
> > relevant ADs and maybe the WG, the flexibility to not accept the
> > resignation if conditions made that wise.  But we would have no
> > disputes over whether the WG Chair had the "right" to "fire"
> > someone over a disclosure problem either.
> >
> > But I believe all of us have the necessary discretionary
> > authority to do that already (just as you had the necessary
> > discretionary authority to send out those two notes).  WG Chairs
> > have a lot of authority over who gets to be a document author or
> > editor.  While it is unusual, I've told people who have written
> > documents that become WG drafts that they don't get to hold the
> > pen for the WG because they are too committed to one position,
> > and I imagine that others have too.   So, from now on, I'm not
> > accepting anyone as a new author or editor for a WG document
> > without getting very explicit agreement that they understand the
> > IPR policy and intend to follow both its letter and its spirit.
> > I'd be delighted if the IESG and/or IETF Trust supplied me with
> > a standard template for getting that agreement and signoff, but
> > I don't think I need one.
> >
> >      john
> >
> >
> >
> >
> >


From touch@isi.edu  Fri Feb 10 11:37:26 2012
Return-Path: <touch@isi.edu>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18C8021F855D for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 11:37:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105
X-Spam-Level: 
X-Spam-Status: No, score=-105 tagged_above=-999 required=5 tests=[AWL=1.599, 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 qfDWoQ0F2idi for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 11:37:25 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 9575121F8552 for <wgchairs@ietf.org>; Fri, 10 Feb 2012 11:37:25 -0800 (PST)
Received: from [128.9.160.252] (pen.isi.edu [128.9.160.252]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id q1AJanQW018070 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 10 Feb 2012 11:36:50 -0800 (PST)
Message-ID: <4F3571D1.2090108@isi.edu>
Date: Fri, 10 Feb 2012 11:36:49 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: Lou Berger <lberger@labn.net>
Subject: Re: On encouraging compliance with IPR disclosure rules
References: <4F354E6A.3000507@labn.net> <6E0F3EF65AE17D32372FDACE@PST.JCK.COM> <4F355803.2090103@isi.edu> <5B6C268752C8008FAFCDCDF5@PST.JCK.COM> <4F35703F.8010701@labn.net>
In-Reply-To: <4F35703F.8010701@labn.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2012 19:37:26 -0000

To be clear about the first page:

On 2/10/2012 11:30 AM, Lou Berger wrote:
...
> I'd like to reiterate that authorship is not the same as being the
> editor of a WG document, and not every author is listed on a cover page.

Authors are the names listed as authors of the RFC, in distributed 
materials managed by the IETF.

Yes, this may or may not be those on the first page of the doc, but in 
practice it is. It's not enough that they're listed as "additional 
contributors" or even acknowledged as explicit authors elsewhere in the doc.

IETF docs have authors of record. These days, those are the names on the 
first page that are not otherwise tagged as "editor".

Again, I don't think the IETF should be meddling with that. That is a 
right that is earned by writing text, not by decree of a WG or WG chair 
- to do so by decree is to give power to the WG to trade authorship for 
favors, and that goes on way too much as it is and needs to be 
discouraged rather than even endorsed.

Joe


From john-ietf@jck.com  Fri Feb 10 11:45:36 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 154A821F8816 for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 11:45:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.699
X-Spam-Level: 
X-Spam-Status: No, score=-102.699 tagged_above=-999 required=5 tests=[AWL=-0.100, 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 tr2z+a4zMirK for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 11:45:35 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 74F2821F8815 for <wgchairs@ietf.org>; Fri, 10 Feb 2012 11:45:35 -0800 (PST)
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 1RvwLk-0003Kg-Eg; Fri, 10 Feb 2012 14:41:40 -0500
Date: Fri, 10 Feb 2012 14:45:27 -0500
From: John C Klensin <john-ietf@jck.com>
To: Lou Berger <lberger@labn.net>
Subject: Re: On encouraging compliance with IPR disclosure rules
Message-ID: <A687C839A9BA222864557D5E@PST.JCK.COM>
In-Reply-To: <4F35703F.8010701@labn.net>
References: <4F354E6A.3000507@labn.net> <6E0F3EF65AE17D32372FDACE@PST.JCK.COM> <4F355803.2090103@isi.edu> <5B6C268752C8008FAFCDCDF5@PST.JCK.COM> <4F35703F.8010701@labn.net>
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>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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, 10 Feb 2012 19:45:36 -0000

--On Friday, February 10, 2012 14:30 -0500 Lou Berger
<lberger@labn.net> wrote:

>...
> WRT to your last comment on a template for "agreement and
> signoff". What do you think about the one we're using?  It's
> the 2nd URL in my earlier message (which was based on text
> from our AD).

I think it is fine and said so earlier.   I also think that, for
the cases I'm much more concerned about, it is too late in the
sense that finding out that there is an IPR problem when the WG
is otherwise ready to advance a document is likely to be
profoundly disruptive.

So I'm still anxious to get some explicit signoff on "I know the
rules and I intend to follow them" and, if it is really
necessary, "my company will cooperate (or not interfere) with my
following them and intends to cooperate with this whole process
in good faith".   If we need the latter, it is probably better
stated as "I don't have any obligations to any individual or
organization whom I have reason to believe would interfere with
my carrying out these obligations to the IETF", which keeps it
individual.  But you get the idea.

   john



From john-ietf@jck.com  Fri Feb 10 11:47:21 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 0E22521F87DD for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 11:47:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.694
X-Spam-Level: 
X-Spam-Status: No, score=-102.694 tagged_above=-999 required=5 tests=[AWL=-0.095, 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 XtPJ-NwAhFVZ for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 11:47:20 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 3E58821F8819 for <wgchairs@ietf.org>; Fri, 10 Feb 2012 11:47:20 -0800 (PST)
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 1RvwNO-0003Kw-Hn; Fri, 10 Feb 2012 14:43:22 -0500
Date: Fri, 10 Feb 2012 14:47:09 -0500
From: John C Klensin <john-ietf@jck.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, wgchairs@ietf.org
Subject: Re: On encouraging compliance with IPR disclosure rules
Message-ID: <017AA8A094A0713EB3E4D32F@PST.JCK.COM>
In-Reply-To: <4F356E97.9030901@alum.mit.edu>
References: <4F354E6A.3000507@labn.net> <6E0F3EF65AE17D32372FDACE@PST.JCK.COM>	<4F355803.2090103@isi.edu> <5B6C268752C8008FAFCDCDF5@PST.JCK.COM> <4F356E97.9030901@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: Fri, 10 Feb 2012 19:47:21 -0000

--On Friday, February 10, 2012 14:23 -0500 Paul Kyzivat
<pkyzivat@alum.mit.edu> wrote:

> John,
> 
> I largely agree with all you say below.
> The one area that concerns me is when an IPR claim is filed at
> the last minute, and author(s) from the claiming company says
> "I didn't know about that" or "I just found out about that".
> 
> In some cases such a comment is clearly ingenuous (e.g. when
> the person's name is on the patent). But in other cases it
> might be true and it might be false but hard to prove. (It
> seems that in some cases companies are intentionally making it
> difficult for their standards participants to know what IPR
> they hold.)
> 
> In such cases, what are you suggesting the WG do?

I'm going to give you and answer that you will probably find
unsatisfying (and I do too, but...):

I'm suggesting that the WG, and its leadership, consider the
circumstances carefully and act with reason and good sense.  

In situations in which it is not possible to determine fault, I
think the benefit of the doubt needs to be given to the IETF
participant - author.  In situations in which it is clear that
the author actually didn't know but that the company was
manipulating the information available to that author, I think a
discussion about removing the company name from the document and
whether that would be helpful in sending a message might be in
order (I've never been completely convinced that putting company
names in the first page header is consistent with our notions of
individual contributors anyway -- maybe they should appear only
as part of author addresses  of an an acknowledgment (e.g.,
"FooCo supported the work of Melvin Author on this document).

And, of course, if particular organizations show a pattern of
hiding IPR from authors/editors so that those people can't
disclose early --a pattern that could be deduced by a lot of
late disclosures of work in the author's area of competence-- it
would be entirely reasonable for WG Chairs or ADs to hesitate
about future author/editor roles for people supported by that
company.   If one calls that a blacklist, it is a blacklist on
the basis of observable patterns that create risks to the IETF
(given the disruptiveness of late disclosures) and does not
require making a judgment about bad behavior.

    john





From presnick@qualcomm.com  Fri Feb 10 11:48:10 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 E570621F8835 for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 11:48:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.565
X-Spam-Level: 
X-Spam-Status: No, score=-106.565 tagged_above=-999 required=5 tests=[AWL=0.034, 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 Xfa-ZOyFA6sH for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 11:48:10 -0800 (PST)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id 20FBF21F8832 for <wgchairs@ietf.org>; Fri, 10 Feb 2012 11:48:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=presnick@qualcomm.com; q=dns/txt; s=qcdkim; t=1328903290; x=1360439290; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: content-transfer-encoding:x-originating-ip; z=Message-ID:=20<4F357478.4090008@qualcomm.com>|Date:=20Fr i,=2010=20Feb=202012=2011:48:08=20-0800|From:=20Pete=20Re snick=20<presnick@qualcomm.com>|User-Agent:=20Mozilla/5.0 =20(Macintosh=3B=20U=3B=20Intel=20Mac=20OS=20X=2010.6=3B =20en-US=3B=20rv:1.9.1.9)=20Gecko/20100630=20Eudora/3.0.4 |MIME-Version:=201.0|To:=20Joe=20Touch=20<touch@isi.edu> |CC:=20John=20C=20Klensin=20<john-ietf@jck.com>,=20<wgcha irs@ietf.org>|Subject:=20Re:=20On=20encouraging=20complia nce=20with=20IPR=20disclosure=20rules|References:=20<4F35 4E6A.3000507@labn.net>=20<6E0F3EF65AE17D32372FDACE@PST.JC K.COM>=09<4F355889.6070409@alum.mit.edu>=09<15F6D9AD40070 C97603562A0@PST.JCK.COM>=20<4F356E91.3060504@isi.edu> |In-Reply-To:=20<4F356E91.3060504@isi.edu>|Content-Type: =20text/plain=3B=20charset=3D"ISO-8859-1"=3B=20format=3Df lowed|Content-Transfer-Encoding:=207bit|X-Originating-IP: =20[172.30.48.1]; bh=vI9E7fRxCCre7CYvdjxSWgiXF+zmghJvNUsbeFGNgFE=; b=WBob/bgpP8uuV8UMzZGjQHqnOCqDx3gDHL2kadrxhn18i82GT/Kk3BpF UmviInZMRHk1yTPek9tdkca7DBvcjUyjydsQry+8Ebjp/vfCG9JAtctj4 /jVyPzosukjpa7kkEqhf8CmfDKexhW5x1Yyi9dypx/cM/Sp1GybAiIBeh A=;
X-IronPort-AV: E=McAfee;i="5400,1158,6616"; a="162237454"
Received: from ironmsg04-r.qualcomm.com ([172.30.46.18]) by wolverine01.qualcomm.com with ESMTP; 10 Feb 2012 11:48:09 -0800
X-IronPort-AV: E=Sophos;i="4.73,396,1325491200"; d="scan'208";a="253360571"
Received: from nasanexhc05.na.qualcomm.com ([172.30.48.2]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/AES128-SHA; 10 Feb 2012 11:48:09 -0800
Received: from android-f1f182bb86f6b3f.wlan.qualcomm.com (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.2) with Microsoft SMTP Server (TLS) id 14.1.339.1; Fri, 10 Feb 2012 11:48:09 -0800
Message-ID: <4F357478.4090008@qualcomm.com>
Date: Fri, 10 Feb 2012 11:48:08 -0800
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: Joe Touch <touch@isi.edu>
Subject: Re: On encouraging compliance with IPR disclosure rules
References: <4F354E6A.3000507@labn.net> <6E0F3EF65AE17D32372FDACE@PST.JCK.COM>	<4F355889.6070409@alum.mit.edu>	<15F6D9AD40070C97603562A0@PST.JCK.COM> <4F356E91.3060504@isi.edu>
In-Reply-To: <4F356E91.3060504@isi.edu>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
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, 10 Feb 2012 19:48:11 -0000

On 2/10/12 11:22 AM, Joe Touch wrote:
> Authorship goes beyond copyright.
>
> And it's not true that in all cases the IETF owns the copyright; that 
> depends on the clauses of the I-D (e.g., if it's before it's a WG item).
>
> I don't think authorship should be under WG control. Authorship should 
> be determined by the extent of the contribution, period. The WG has 
> other positions that it more appropriately controls - editorship, wg 
> chair, etc.
>
> Further, putting authorship under control of the WG sets up the 
> potential for trading authorship for favors - which happens 
> offensively often enough as it is.
>
> Regardless of what IETF process says on this matter, meddling with 
> authorship is a bad idea, period.

Just to be clear: When it comes to WG documents, the names that appear 
at the top of the document are the document editors. They may be 
"authors" in the RFC Editor sense of the word, but they are clearly the 
document editors. They are the people who are responsible to put in the 
document what the WG wants and they are the people that the RFC Editor 
is going to check with in AUTH48. They can, as per 2418, be removed from 
the position of document editor by the chair on behalf of the WG. If 
they have (in the opinion of the chair and the WG) violated process by 
way of not disclosing IPR in a reasonable fashion, thus interfering with 
the progress of the WG, that's perfectly reasonable grounds to remove an 
editor. If a chair removes a document editor, it is perfectly reasonable 
to remove them from the list of people at the top of the document. 
That's true both for both practical reasons (having someone who is not 
the document editor be responsible for AUTH48 is not best) and 
sanctioning reasons (people do consider it an honor to be listed on the 
front page). It is still good form to list the person in the 
acknowledgments section, because they were clearly contributors to the 
document.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102


From touch@isi.edu  Fri Feb 10 11:53:40 2012
Return-Path: <touch@isi.edu>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2134A21F8613 for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 11:53:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.035
X-Spam-Level: 
X-Spam-Status: No, score=-103.035 tagged_above=-999 required=5 tests=[AWL=-0.436, 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 d2hF60ise6sk for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 11:53:39 -0800 (PST)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 4D35021F8603 for <wgchairs@ietf.org>; Fri, 10 Feb 2012 11:53:32 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id q1AJr4qf024024 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 10 Feb 2012 11:53:04 -0800 (PST)
Message-ID: <4F3575A0.9010505@isi.edu>
Date: Fri, 10 Feb 2012 11:53:04 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: Pete Resnick <presnick@qualcomm.com>
Subject: Re: On encouraging compliance with IPR disclosure rules
References: <4F354E6A.3000507@labn.net> <6E0F3EF65AE17D32372FDACE@PST.JCK.COM>	<4F355889.6070409@alum.mit.edu>	<15F6D9AD40070C97603562A0@PST.JCK.COM> <4F356E91.3060504@isi.edu> <4F357478.4090008@qualcomm.com>
In-Reply-To: <4F357478.4090008@qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
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, 10 Feb 2012 19:53:40 -0000

On 2/10/2012 11:48 AM, Pete Resnick wrote:
> On 2/10/12 11:22 AM, Joe Touch wrote:
>> Authorship goes beyond copyright.
>>
>> And it's not true that in all cases the IETF owns the copyright; that
>> depends on the clauses of the I-D (e.g., if it's before it's a WG item).
>>
>> I don't think authorship should be under WG control. Authorship should
>> be determined by the extent of the contribution, period. The WG has
>> other positions that it more appropriately controls - editorship, wg
>> chair, etc.
>>
>> Further, putting authorship under control of the WG sets up the
>> potential for trading authorship for favors - which happens
>> offensively often enough as it is.
>>
>> Regardless of what IETF process says on this matter, meddling with
>> authorship is a bad idea, period.
>
> Just to be clear: When it comes to WG documents, the names that appear
> at the top of the document are the document editors. They may be
> "authors" in the RFC Editor sense of the word, but they are clearly the
> document editors.

That's not universally true; in some WGs, there is a subset of names 
that are indicated as "ed." which are editors. These have been sometimes 
assigned separately, and other times selected from the previous authors.

However, it's incorrect that all such names on the first page of all WG 
docs are editors. They're not listed as such, and they're indicted in 
the suffix as "Authors' addresses", and in other IETF distributed 
material as authors.

Some docs don't have authors listed on the first page, only editors; 
sometimes this is because there are no clear authors, sometimes because 
it violated (ridiculous, IMO) RFC Editor policy (e.g., exceeding 5 
authors), and sometimes for no particular reason.

However, names listed on the first page that aren't clearly indicated as 
editors *are* authors.

Joe

From lberger@labn.net  Fri Feb 10 11:59:06 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 6565721F8818 for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 11:59:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.952
X-Spam-Level: 
X-Spam-Status: No, score=-98.952 tagged_above=-999 required=5 tests=[AWL=1.209, BAYES_00=-2.599, 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 Ms3evuv49QTE for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 11:59:05 -0800 (PST)
Received: from oproxy6-pub.bluehost.com (oproxy6.bluehost.com [IPv6:2605:dc00:100:2::a6]) by ietfa.amsl.com (Postfix) with SMTP id A6B9021F880B for <wgchairs@ietf.org>; Fri, 10 Feb 2012 11:59:05 -0800 (PST)
Received: (qmail 15744 invoked by uid 0); 10 Feb 2012 19:59:05 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by cpoproxy3.bluehost.com with SMTP; 10 Feb 2012 19:59:05 -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=3mk52fWF8Jr/Qvpqo+T3gl6YUggxxWVVcZTetQX8C6s=;  b=nBKJHpaQsNmG8rxb3ZOhOvSce886gijObOyJLZRfbTMdYGmFXJA2MuvBOcagZ8+4SF0eDZETbWCYGf0E4y3NfwTJQcMVA6rjeDjhBlOkZhCxhWy57QjxLhFqv6atJfew;
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 1Rvwcb-000464-6e; Fri, 10 Feb 2012 12:59:05 -0700
Message-ID: <4F357706.80104@labn.net>
Date: Fri, 10 Feb 2012 14:59:02 -0500
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: Joe Touch <touch@isi.edu>
Subject: Re: On encouraging compliance with IPR disclosure rules
References: <4F354E6A.3000507@labn.net> <6E0F3EF65AE17D32372FDACE@PST.JCK.COM> <4F355803.2090103@isi.edu> <5B6C268752C8008FAFCDCDF5@PST.JCK.COM> <4F35703F.8010701@labn.net> <4F3571D1.2090108@isi.edu>
In-Reply-To: <4F3571D1.2090108@isi.edu>
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: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2012 19:59:06 -0000

Joe,
	I wouldn't argue with your view of authorship in an academic context,
but the IETF is academia.  We already have guidelines on Authors,
Contributors, Editors, etc from the RFC Editors, i.e.,
http://www.rfc-editor.org/policy.html.  It seems that some of what you
express is at odds with their position, particularly with respect to
names on the first page.

Lou


On 2/10/2012 2:36 PM, Joe Touch wrote:
> To be clear about the first page:
> 
> On 2/10/2012 11:30 AM, Lou Berger wrote:
> ...
>> I'd like to reiterate that authorship is not the same as being the
>> editor of a WG document, and not every author is listed on a cover page.
> 
> Authors are the names listed as authors of the RFC, in distributed 
> materials managed by the IETF.
> 
> Yes, this may or may not be those on the first page of the doc, but in 
> practice it is. It's not enough that they're listed as "additional 
> contributors" or even acknowledged as explicit authors elsewhere in the doc.
> 
> IETF docs have authors of record. These days, those are the names on the 
> first page that are not otherwise tagged as "editor".
> 
> Again, I don't think the IETF should be meddling with that. That is a 
> right that is earned by writing text, not by decree of a WG or WG chair 
> - to do so by decree is to give power to the WG to trade authorship for 
> favors, and that goes on way too much as it is and needs to be 
> discouraged rather than even endorsed.
> 
> Joe
> 
> 
> 
> 
> 

From touch@isi.edu  Fri Feb 10 12:04:09 2012
Return-Path: <touch@isi.edu>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4FC621F87D1 for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 12:04:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.017
X-Spam-Level: 
X-Spam-Status: No, score=-103.017 tagged_above=-999 required=5 tests=[AWL=-0.418, 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 6DC-hhx742z7 for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 12:04:08 -0800 (PST)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 47A3C21F87B0 for <wgchairs@ietf.org>; Fri, 10 Feb 2012 12:04:08 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id q1AK3sjM027610 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 10 Feb 2012 12:03:54 -0800 (PST)
Message-ID: <4F35782A.4050305@isi.edu>
Date: Fri, 10 Feb 2012 12:03:54 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: Lou Berger <lberger@labn.net>
Subject: Re: On encouraging compliance with IPR disclosure rules
References: <4F354E6A.3000507@labn.net> <6E0F3EF65AE17D32372FDACE@PST.JCK.COM> <4F355803.2090103@isi.edu> <5B6C268752C8008FAFCDCDF5@PST.JCK.COM> <4F35703F.8010701@labn.net> <4F3571D1.2090108@isi.edu> <4F357706.80104@labn.net>
In-Reply-To: <4F357706.80104@labn.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2012 20:04:09 -0000

On 2/10/2012 11:59 AM, Lou Berger wrote:
> Joe,
> 	I wouldn't argue with your view of authorship in an academic context,
> but the IETF is academia.  We already have guidelines on Authors,
> Contributors, Editors, etc from the RFC Editors, i.e.,
> http://www.rfc-editor.org/policy.html.  It seems that some of what you
> express is at odds with their position, particularly with respect to
> names on the first page.

Seems like they agree *exactly* here:
http://www.rfc-editor.org/policy.html#policy.auth

Further down, on author overload, my distinction between author and 
editor - and editor being clearly indicated as such - is verified.

Was there some particular text on that page you thought was relevant in 
contradicting my view?

Joe

> On 2/10/2012 2:36 PM, Joe Touch wrote:
>> To be clear about the first page:
>>
>> On 2/10/2012 11:30 AM, Lou Berger wrote:
>> ...
>>> I'd like to reiterate that authorship is not the same as being the
>>> editor of a WG document, and not every author is listed on a cover page.
>>
>> Authors are the names listed as authors of the RFC, in distributed
>> materials managed by the IETF.
>>
>> Yes, this may or may not be those on the first page of the doc, but in
>> practice it is. It's not enough that they're listed as "additional
>> contributors" or even acknowledged as explicit authors elsewhere in the doc.
>>
>> IETF docs have authors of record. These days, those are the names on the
>> first page that are not otherwise tagged as "editor".
>>
>> Again, I don't think the IETF should be meddling with that. That is a
>> right that is earned by writing text, not by decree of a WG or WG chair
>> - to do so by decree is to give power to the WG to trade authorship for
>> favors, and that goes on way too much as it is and needs to be
>> discouraged rather than even endorsed.
>>
>> Joe
>>
>>
>>
>>
>>

From lberger@labn.net  Fri Feb 10 12:18:15 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 09FFC21F8829 for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 12:18:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.994
X-Spam-Level: 
X-Spam-Status: No, score=-98.994 tagged_above=-999 required=5 tests=[AWL=1.167, BAYES_00=-2.599, 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 a4+pY-bDcRtm for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 12:18:14 -0800 (PST)
Received: from oproxy4-pub.bluehost.com (oproxy4.bluehost.com [IPv6:2605:dc00:100:2::a4]) by ietfa.amsl.com (Postfix) with SMTP id 8275D21F8812 for <wgchairs@ietf.org>; Fri, 10 Feb 2012 12:18:13 -0800 (PST)
Received: (qmail 24414 invoked by uid 0); 10 Feb 2012 20:18:13 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by cpoproxy1.bluehost.com with SMTP; 10 Feb 2012 20:18:13 -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=IhhAuYO1TDGMsatJqfWqTqo7Z8F5Jzuu9LKa9wA1F7k=;  b=Pf6LAmXTu7wrmVHMLvCmPTA36pspQv/BCttwT455a6vlfT82Tip0NgH7ZtYUbr4AajhRUw8roggYeSwXdGFctFl/j9aTC3ZcSkSW9EouFie5cuvuAVg2F+NxdcetPKNw;
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 1Rvwv6-0002N3-Ub; Fri, 10 Feb 2012 13:18:13 -0700
Message-ID: <4F357B81.9060802@labn.net>
Date: Fri, 10 Feb 2012 15:18:09 -0500
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: Joe Touch <touch@isi.edu>
Subject: Re: On encouraging compliance with IPR disclosure rules
References: <4F354E6A.3000507@labn.net> <6E0F3EF65AE17D32372FDACE@PST.JCK.COM> <4F355803.2090103@isi.edu> <5B6C268752C8008FAFCDCDF5@PST.JCK.COM> <4F35703F.8010701@labn.net> <4F3571D1.2090108@isi.edu> <4F357706.80104@labn.net> <4F35782A.4050305@isi.edu>
In-Reply-To: <4F35782A.4050305@isi.edu>
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: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2012 20:18:15 -0000

Joe,
	See below.

On 2/10/2012 3:03 PM, Joe Touch wrote:
>
>
> On 2/10/2012 11:59 AM, Lou Berger wrote:
>> Joe,
>> 	I wouldn't argue with your view of authorship in an academic context,
>> but the IETF is academia.  We already have guidelines on Authors,
>> Contributors, Editors, etc from the RFC Editors, i.e.,
>> http://www.rfc-editor.org/policy.html.  It seems that some of what you
>> express is at odds with their position, particularly with respect to
>> names on the first page.
>
> Seems like they agree *exactly* here:
> http://www.rfc-editor.org/policy.html#policy.auth
>
> Further down, on author overload, my distinction between author and
> editor - and editor being clearly indicated as such - is verified.
>
> Was there some particular text on that page you thought was relevant in
> contradicting my view?

Yes:
> It's not enough that they're listed as "additional
>>> contributors" or even acknowledged as explicit authors elsewhere in
the doc.
>>>

In particular a contributor may include those "who also contributed
significantly to the RFC." While an author is "considered to be equally
responsible for the contents of the document."  Note that the latter
refers to *responsibility* as the key attribute, not volume of text
contributed -- even when significant.

Lou

>
> Joe
>
>> On 2/10/2012 2:36 PM, Joe Touch wrote:
>>> To be clear about the first page:
>>>
>>> On 2/10/2012 11:30 AM, Lou Berger wrote:
>>> ...
>>>> I'd like to reiterate that authorship is not the same as being the
>>>> editor of a WG document, and not every author is listed on a cover
page.
>>>
>>> Authors are the names listed as authors of the RFC, in distributed
>>> materials managed by the IETF.
>>>
>>> Yes, this may or may not be those on the first page of the doc, but in
>>> practice it is. It's not enough that they're listed as "additional
>>> contributors" or even acknowledged as explicit authors elsewhere in
the doc.
>>>
>>> IETF docs have authors of record. These days, those are the names on the
>>> first page that are not otherwise tagged as "editor".
>>>
>>> Again, I don't think the IETF should be meddling with that. That is a
>>> right that is earned by writing text, not by decree of a WG or WG chair
>>> - to do so by decree is to give power to the WG to trade authorship for
>>> favors, and that goes on way too much as it is and needs to be
>>> discouraged rather than even endorsed.
>>>
>>> Joe
>>>
>>>
>>>
>>>
>>>
>
>
>
>

From john-ietf@jck.com  Fri Feb 10 12:20: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 31F7721F88C0 for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 12:20:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.69
X-Spam-Level: 
X-Spam-Status: No, score=-102.69 tagged_above=-999 required=5 tests=[AWL=-0.091, 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 9eqledwfBO19 for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 12:20:36 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id D78E121F88B8 for <wgchairs@ietf.org>; Fri, 10 Feb 2012 12:20:35 -0800 (PST)
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 1Rvwtc-0003O3-P9; Fri, 10 Feb 2012 15:16:40 -0500
Date: Fri, 10 Feb 2012 15:20:28 -0500
From: John C Klensin <john-ietf@jck.com>
To: Joe Touch <touch@isi.edu>
Subject: Re: On encouraging compliance with IPR disclosure rules
Message-ID: <43BA3FC755F2E9553CE41821@PST.JCK.COM>
In-Reply-To: <4F356C57.308@isi.edu>
References: <4F354E6A.3000507@labn.net> <6E0F3EF65AE17D32372FDACE@PST.JCK.COM> <4F355803.2090103@isi.edu> <5B6C268752C8008FAFCDCDF5@PST.JCK.COM> <4F356C57.308@isi.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
Cc: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2012 20:20:37 -0000

Joe,

Please see Pete's note for most of what I would have said.
Basically someone ceases to be an author (in the sense in which
you are using the term) the instant the document becomes a WG
(or, in the case of an individual submission, an IETF) work
product.  Some, including a few generations of IPR WGs would
argue that the cutover occurs even earlier.   

But see below.

--On Friday, February 10, 2012 11:13 -0800 Joe Touch
<touch@isi.edu> wrote:

> Authorship is a matter of fact (granted, arguable fact in some
> cases).

In the general case, I agree with you and have argued several
times in the past that the IETF should take that position
whenever possible.  But that has not been the prevailing
position.  If I write a document and turn it over to the IETF
--especially for standardization-- I am "contributing" _all_ of
the fundamental rights that come with authorship -- copyright,
change control, final authority over what is published, and even
the right to be identified in anything but the acknowledgments.
The document can be altered into something I disagree with and
the most I can do is to insist my name be taken off the front
page.   If I don't like those rules, I have one option, which is
not to contribute documents to the IETF (probably not to
participate in the IETF more generally, but I might be able to
split some hairs).

> Editors and chairs are positions of trust and responsibility.
> I agree that these can - and should - incur penalties when we
> have reasonable belief that *any* IETF/IRTF process
> requirements aren't being respected - those include IPR,
> trading authorship for cookies, etc.

Yes.  But once the documents become WG work products, someone
who might have been an author (in your sense) of an earlier
version becomes an editor for all future ones, with the text
under the control of the WG to the degree to which it decides to
assert itself, regardless of whether the document says "(ed.)"
or not.


>> Maybe that formal agreement with an author/editor should not
>> discuss sanctions but should merely require that person to
>> stand up in front of the WG and say "in front of all of you,
>> I am asserting that I understand the IPR policies and intend
>> to comply with them" because the really important thing is
>> that someone should not be able to wait until the 11th hour
>> (or a few hours past that) and then plead that they were
>> ignorant earlier.
> 
> They should be please ignorance of the rules. They can
> *always* plead ignorance of the IPR being relevant, or of the
> IPR itself - that's a permanent "escape mechanism" at any
> point, and I don't see a way around it unfortunately.

See my earlier response to Paul for this and several related
comments.

>> FWIW, from my point of view, an author's ignoring the IPR
>> rules is exactly the same sort of breach of trust with the WG
>> that the author's refusing to follow WG consensus decisions
>> about what should be in the document would be.   As a WG
>> Chair, or even a WG participant, I want and need to have that
>> person out of that role, independent of (and superceding)
>> whatever other agreements might have been made.
> 
> You can't undo authorship unless you cut text, IMO.

I can in the IETF.  I recommend that you go read 3978 and the
Note Well again.   And, again, "author" on a document that is a
WG work product is s misnomer, a historical accident, or both.

>...
>> You may reasonably disagree, but I'd be interested in hearing
>> how you would propose to deal with breaches of the trust
>> relationship between the WG and an author/editor.  I don't
>> find "be nice, sympathize with the circumstances, and hope
>> there will never be another problem" particularly satisfying.
>> Perhaps I'm in the minority.
> 
> See above - I agree with your suggestion for roles that are
> under the assignment of the IETF. I don't think it's
> appropriate for roles that should *never* (UNDER ANY
> CIRCIMSTANCES) be under the assignment of the IETF - and I put
> "author" in that bin.

And, again, whether I agree with you about that being a useful
design is irrelevant.  The IETF has very clearly decided
otherwise and if I, as an author, don't like it I certainly have
the option of taking my document and going home, as long as I do
it before the document becomes an IETF "Contribution".

     john



From touch@isi.edu  Fri Feb 10 12:51:28 2012
Return-Path: <touch@isi.edu>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5088C21E8018 for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 12:51:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.008
X-Spam-Level: 
X-Spam-Status: No, score=-103.008 tagged_above=-999 required=5 tests=[AWL=-0.409, 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 Bs43B7kui1Z1 for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 12:51:27 -0800 (PST)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 2A0EA21E8012 for <wgchairs@ietf.org>; Fri, 10 Feb 2012 12:51:27 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id q1AKoc6t013383 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 10 Feb 2012 12:50:38 -0800 (PST)
Message-ID: <4F35831E.1000001@isi.edu>
Date: Fri, 10 Feb 2012 12:50:38 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: Lou Berger <lberger@labn.net>
Subject: Re: On encouraging compliance with IPR disclosure rules
References: <4F354E6A.3000507@labn.net> <6E0F3EF65AE17D32372FDACE@PST.JCK.COM> <4F355803.2090103@isi.edu> <5B6C268752C8008FAFCDCDF5@PST.JCK.COM> <4F35703F.8010701@labn.net> <4F3571D1.2090108@isi.edu> <4F357706.80104@labn.net> <4F35782A.4050305@isi.edu> <4F357B81.9060802@labn.net>
In-Reply-To: <4F357B81.9060802@labn.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2012 20:51:28 -0000

Hi, Lou,

On 2/10/2012 12:18 PM, Lou Berger wrote:
> Joe,
> 	See below.
>
> On 2/10/2012 3:03 PM, Joe Touch wrote:
>>
>>
>> On 2/10/2012 11:59 AM, Lou Berger wrote:
>>> Joe,
>>> 	I wouldn't argue with your view of authorship in an academic context,
>>> but the IETF is academia.  We already have guidelines on Authors,
>>> Contributors, Editors, etc from the RFC Editors, i.e.,
>>> http://www.rfc-editor.org/policy.html.  It seems that some of what you
>>> express is at odds with their position, particularly with respect to
>>> names on the first page.
>>
>> Seems like they agree *exactly* here:
>> http://www.rfc-editor.org/policy.html#policy.auth
>>
>> Further down, on author overload, my distinction between author and
>> editor - and editor being clearly indicated as such - is verified.
>>
>> Was there some particular text on that page you thought was relevant in
>> contradicting my view?
>
> Yes:
>> It's not enough that they're listed as "additional
>>>> contributors" or even acknowledged as explicit authors elsewhere in
> the doc.
>>>>
>
> In particular a contributor may include those "who also contributed
> significantly to the RFC." While an author is "considered to be equally
> responsible for the contents of the document."  Note that the latter
> refers to *responsibility* as the key attribute, not volume of text
> contributed -- even when significant.

 From that same area:

When the RFC Editor refers to "contributors", we mean people, other than 
the authors, who also contributed significantly to the RFC. They should 
be listed in a Contributors section of the body of the document.

"responsible for the contents" can be interpreted as both writing and 
editing.

However, later the distinction is made very clear (annotations below are 
mine), since the title "editor" is introduced as a *separate* role:

---
A small set of author names, with affiliations, may appear on the front 
page header. These should be the lead author(s) who are most responsible 
for the actual text. When there are many contributors, the best choice 
will be to list the person or (few) persons who acted as document 
editor(s) (e.g.,"Tom Smith, Editor").

There is no rigid limit on the size of this set, but there is likely to 
be a discussion if the set exceeds five authors, in which case the right 
answer is probably to list one editor.

An RFC may include a Contributors section, listing those contributors 
who deserve significant credit for the document contents. The 
Contributors section is intended to provide a level of recognition 
greater than an acknowledgment and nearly equal to listing on the front
                                    ^^^^^^
page. The choice of either, both, or none of Contributor and 
Acknowledgment sections in a particular RFC depends upon the circumstance.

 >> i.e., not identical

-----

"Responsible" certainly includes many things, and the difference between 
author and contributor up to interpretation - AFAICT, from the above, 
based on the amount of contribution, not the "responsibility" per se.

Joe

>> Joe
>>
>>> On 2/10/2012 2:36 PM, Joe Touch wrote:
>>>> To be clear about the first page:
>>>>
>>>> On 2/10/2012 11:30 AM, Lou Berger wrote:
>>>> ...
>>>>> I'd like to reiterate that authorship is not the same as being the
>>>>> editor of a WG document, and not every author is listed on a cover
> page.
>>>>
>>>> Authors are the names listed as authors of the RFC, in distributed
>>>> materials managed by the IETF.
>>>>
>>>> Yes, this may or may not be those on the first page of the doc, but in
>>>> practice it is. It's not enough that they're listed as "additional
>>>> contributors" or even acknowledged as explicit authors elsewhere in
> the doc.
>>>>
>>>> IETF docs have authors of record. These days, those are the names on the
>>>> first page that are not otherwise tagged as "editor".
>>>>
>>>> Again, I don't think the IETF should be meddling with that. That is a
>>>> right that is earned by writing text, not by decree of a WG or WG chair
>>>> - to do so by decree is to give power to the WG to trade authorship for
>>>> favors, and that goes on way too much as it is and needs to be
>>>> discouraged rather than even endorsed.
>>>>
>>>> Joe
>>>>
>>>>
>>>>
>>>>
>>>>
>>
>>
>>
>>

From touch@isi.edu  Fri Feb 10 12:52:16 2012
Return-Path: <touch@isi.edu>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BDE021E8018 for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 12:52:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103
X-Spam-Level: 
X-Spam-Status: No, score=-103 tagged_above=-999 required=5 tests=[AWL=-0.401,  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 kmQUpXhynbWD for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 12:52:15 -0800 (PST)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 4FC7E21E8017 for <wgchairs@ietf.org>; Fri, 10 Feb 2012 12:52:15 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id q1AKq4qC014167 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 10 Feb 2012 12:52:04 -0800 (PST)
Message-ID: <4F358374.90600@isi.edu>
Date: Fri, 10 Feb 2012 12:52:04 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: On encouraging compliance with IPR disclosure rules
References: <4F354E6A.3000507@labn.net> <6E0F3EF65AE17D32372FDACE@PST.JCK.COM> <4F355803.2090103@isi.edu> <5B6C268752C8008FAFCDCDF5@PST.JCK.COM> <4F356C57.308@isi.edu> <43BA3FC755F2E9553CE41821@PST.JCK.COM>
In-Reply-To: <43BA3FC755F2E9553CE41821@PST.JCK.COM>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2012 20:52:16 -0000

John,

See http://www.rfc-editor.org/policy.html, which distinguishes between 
authors and editors, and indicates the latter as explicitly labeled.

If you can find a place where all authors are replaced by an editor for 
all WG submissions, and that those editors are not indicated explicitly 
as editors, please cite it.

Joe

On 2/10/2012 12:20 PM, John C Klensin wrote:
> Joe,
>
> Please see Pete's note for most of what I would have said.
> Basically someone ceases to be an author (in the sense in which
> you are using the term) the instant the document becomes a WG
> (or, in the case of an individual submission, an IETF) work
> product.  Some, including a few generations of IPR WGs would
> argue that the cutover occurs even earlier.
>
> But see below.
>
> --On Friday, February 10, 2012 11:13 -0800 Joe Touch
> <touch@isi.edu>  wrote:
>
>> Authorship is a matter of fact (granted, arguable fact in some
>> cases).
>
> In the general case, I agree with you and have argued several
> times in the past that the IETF should take that position
> whenever possible.  But that has not been the prevailing
> position.  If I write a document and turn it over to the IETF
> --especially for standardization-- I am "contributing" _all_ of
> the fundamental rights that come with authorship -- copyright,
> change control, final authority over what is published, and even
> the right to be identified in anything but the acknowledgments.
> The document can be altered into something I disagree with and
> the most I can do is to insist my name be taken off the front
> page.   If I don't like those rules, I have one option, which is
> not to contribute documents to the IETF (probably not to
> participate in the IETF more generally, but I might be able to
> split some hairs).
>
>> Editors and chairs are positions of trust and responsibility.
>> I agree that these can - and should - incur penalties when we
>> have reasonable belief that *any* IETF/IRTF process
>> requirements aren't being respected - those include IPR,
>> trading authorship for cookies, etc.
>
> Yes.  But once the documents become WG work products, someone
> who might have been an author (in your sense) of an earlier
> version becomes an editor for all future ones, with the text
> under the control of the WG to the degree to which it decides to
> assert itself, regardless of whether the document says "(ed.)"
> or not.
>
>
>>> Maybe that formal agreement with an author/editor should not
>>> discuss sanctions but should merely require that person to
>>> stand up in front of the WG and say "in front of all of you,
>>> I am asserting that I understand the IPR policies and intend
>>> to comply with them" because the really important thing is
>>> that someone should not be able to wait until the 11th hour
>>> (or a few hours past that) and then plead that they were
>>> ignorant earlier.
>>
>> They should be please ignorance of the rules. They can
>> *always* plead ignorance of the IPR being relevant, or of the
>> IPR itself - that's a permanent "escape mechanism" at any
>> point, and I don't see a way around it unfortunately.
>
> See my earlier response to Paul for this and several related
> comments.
>
>>> FWIW, from my point of view, an author's ignoring the IPR
>>> rules is exactly the same sort of breach of trust with the WG
>>> that the author's refusing to follow WG consensus decisions
>>> about what should be in the document would be.   As a WG
>>> Chair, or even a WG participant, I want and need to have that
>>> person out of that role, independent of (and superceding)
>>> whatever other agreements might have been made.
>>
>> You can't undo authorship unless you cut text, IMO.
>
> I can in the IETF.  I recommend that you go read 3978 and the
> Note Well again.   And, again, "author" on a document that is a
> WG work product is s misnomer, a historical accident, or both.
>
>> ...
>>> You may reasonably disagree, but I'd be interested in hearing
>>> how you would propose to deal with breaches of the trust
>>> relationship between the WG and an author/editor.  I don't
>>> find "be nice, sympathize with the circumstances, and hope
>>> there will never be another problem" particularly satisfying.
>>> Perhaps I'm in the minority.
>>
>> See above - I agree with your suggestion for roles that are
>> under the assignment of the IETF. I don't think it's
>> appropriate for roles that should *never* (UNDER ANY
>> CIRCIMSTANCES) be under the assignment of the IETF - and I put
>> "author" in that bin.
>
> And, again, whether I agree with you about that being a useful
> design is irrelevant.  The IETF has very clearly decided
> otherwise and if I, as an author, don't like it I certainly have
> the option of taking my document and going home, as long as I do
> it before the document becomes an IETF "Contribution".
>
>       john
>

From ietfdbh@comcast.net  Fri Feb 10 13:02:01 2012
Return-Path: <ietfdbh@comcast.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52B4221F8863 for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 13:02:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.289
X-Spam-Level: 
X-Spam-Status: No, score=-103.289 tagged_above=-999 required=5 tests=[AWL=1.310, BAYES_00=-2.599, GB_I_LETTER=-2, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JIdqj62s2hph for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 13:02:00 -0800 (PST)
Received: from qmta09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [76.96.62.96]) by ietfa.amsl.com (Postfix) with ESMTP id 4052021F8861 for <wgchairs@ietf.org>; Fri, 10 Feb 2012 13:02:00 -0800 (PST)
Received: from omta15.westchester.pa.mail.comcast.net ([76.96.62.87]) by qmta09.westchester.pa.mail.comcast.net with comcast id YLa91i0061swQuc59M20JL; Fri, 10 Feb 2012 21:02:00 +0000
Received: from [192.168.1.33] ([71.233.85.150]) by omta15.westchester.pa.mail.comcast.net with comcast id YM1o1i00o3Ecudz3bM1t0v; Fri, 10 Feb 2012 21:02:00 +0000
User-Agent: Microsoft-MacOutlook/14.14.0.111121
Date: Fri, 10 Feb 2012 16:01:45 -0500
Subject: Re: On encouraging compliance with IPR disclosure rules
From: David Harrington <ietfdbh@comcast.net>
To: John C Klensin <john-ietf@jck.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, <wgchairs@ietf.org>
Message-ID: <CB5AEDEB.1117F%ietfdbh@comcast.net>
Thread-Topic: On encouraging compliance with IPR disclosure rules
In-Reply-To: <15F6D9AD40070C97603562A0@PST.JCK.COM>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2012 21:02:01 -0000

Hi John,

I disagree with an assertion you make that the IETF can do anything they
like with a contribution. From RFC3978:

<excerpt>
7.1.  Rights Granted in IETF Contributions

   The IETF/ISOC must obtain the right to publish an IETF Contribution
   as an RFC or an Internet-Draft from the Contributors.

   A primary objective of this policy is to obtain from the document
   authors only the non-exclusive rights that are needed to develop and
   publish IETF Documents and to use the IETF Contributions in the IETF
   Standards Process while leaving all other rights with the authors.

   The non-exclusive rights that the IETF needs are:

   a. the right to publish the document
   b. the right to let the document be freely reproduced in the formats
      that the IETF publishes it in
   c. the right to let third parties translate it into languages other
      than English
   d. except where explicitly excluded (see Section 5.2), the right to
      make derivative works within the IETF process.
   e. the right to let third parties extract some logical parts, for
      example MIB modules

   The authors retain all other rights, but cannot withdraw the above
   rights from the IETF/ISOC.
<end excerpt>

When I helped coordinate transferring the IETF Bridge MIB documents to
IEEE for further work, the IEEE lawyers had to contact the authors to get
permission to do derivative work because the IETF is not grated the right
to grant to another SDO the right to develop derivative works.

I don't think the IETF has the right to remove somebody as author (and
RFC3978 references the Berne agreement, which I suspect but don't know
protects the author. I think we do have the right to remove somebody as WG
editor. So we should be able to remove them frpm the front page, but
someplace in the document we need to acknowledge that they contributed to
the document.

I think lawyers need to decide just where that fine line exists between
removing an editor and removing an author.

This is of course my own personal opinion, and I am not a lawyer, nor do I
speak for the IESG.

--
David Harrington
Director, Transport Area
Internet Engineering Task Force (IETF)
Ietfdbh@comcast.net
+1-603-828-1401





On 2/10/12 2:17 PM, "John C Klensin" <john-ietf@jck.com> wrote:

>
>
>--On Friday, February 10, 2012 12:48 -0500 Paul Kyzivat
><pkyzivat@alum.mit.edu> wrote:
>
>>...
>> While I agree with the philosophy expressed here, I wonder
>> about the mechanics:
>
>See my previous note, but...
>
>> Surely we can remove someone as editor. But removing as author
>> isn't so easy. (That discussion has been going on
>> independently.) If this person has written most of the words
>> in the doc, then it is pretty hard to remove them as an author
>> of the document. (Unless of course the doc is also rewritten -
>> presumably to avoid the IPR.)
>
>Nope.  RFC 3978, to which a pointer now appears in every new I-D
>authors or editors post, clearly gives that text to the IETF to
>do with as it likes, especially as part of the standards
>process.  Taking someone who wrote a significant fraction of a
>document and moving them to an acknowledgement that says as
>little as "Thanks to Joe Furd for contributing very significant
>portions of this document to the IETF" and as much more as the
>WG believes to be appropriate.  We may have a problem with
>patents and disclosure, but we have no problems at all in
>copyrights in I-D text that is used by the IETF in creating IETF
>documents (there are gray areas with other uses, but not with
>that one).
>
>Again, I really don't see a situation in which the WG had every
>reason to believe that an author knew the IPR rules and still
>didn't disclose something she clearly knew about earlier as
>different from one in which the WG says "change section 1.2.3 to
>read..." and the author refuses because he doesn't like the
>change).
>
>This would get complicated if the author, instead of saying "I
>didn't understand or know about the IETF rules" said "I didn't
>know about the IPR and couldn't reasonably be expected to know
>about it".  Unless we have additional information that makes
>those claims implausible, I think we have to accept that
>position.  But, e.g., an inventor who is listed on a patent
>application and who is also an IETF document author should be in
>no position to claim lack of knowledge of either the IETF
>policies or of the invention itself.
>
>
>> Perhaps we could make past history of IPR disclosure problems
>> a criterion in choosing editors of new documents, and of
>> accepting new documents as WG drafts. But that does smack of
>> blacklisting.
>
>I wouldn't describe it that way and I'm not keeping black lists.
>But I do believe that WGs, and WG Chairs, do have a
>responsibility to ensure an appropriate relationship of trust
>between the WG and the author -- trust that includes both "you
>will keep the document in line with WG consensus" and "you will
>work to make sure you are in compliance with the letter and
>spirit of the IPR policy".
>
>And, again, I see this much more in terms of making absolutely
>sure that people are informed and cannot deny being informed and
>in terms of trust than I do in terms of identifying and
>punishing bad behavior.   In that regard, I think Adrian's work
>on sanctions is very useful.  But, from my point of view, if we
>get there, we have already failed, have a mess to clean up, and
>want to deter future forms of bad behavior.   At least right
>now, I'd rather concentrate on prevention and encouragement.
>
>    john
>



From presnick@qualcomm.com  Fri Feb 10 13:13:28 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 50B1C21F873C for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 13:13:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.565
X-Spam-Level: 
X-Spam-Status: No, score=-106.565 tagged_above=-999 required=5 tests=[AWL=0.034, 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 AQKb4nCQkXwY for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 13:13:26 -0800 (PST)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 90B5921F8741 for <wgchairs@ietf.org>; Fri, 10 Feb 2012 13:13:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=presnick@qualcomm.com; q=dns/txt; s=qcdkim; t=1328908406; x=1360444406; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: content-transfer-encoding:x-originating-ip; z=Message-ID:=20<4F35885F.9050708@qualcomm.com>|Date:=20Fr i,=2010=20Feb=202012=2013:13:03=20-0800|From:=20Pete=20Re snick=20<presnick@qualcomm.com>|User-Agent:=20Mozilla/5.0 =20(Macintosh=3B=20U=3B=20Intel=20Mac=20OS=20X=2010.6=3B =20en-US=3B=20rv:1.9.1.9)=20Gecko/20100630=20Eudora/3.0.4 |MIME-Version:=201.0|To:=20Joe=20Touch=20<touch@isi.edu> |CC:=20John=20C=20Klensin=20<john-ietf@jck.com>,=20IETF =20WG=20Chairs=20<wgchairs@ietf.org>|Subject:=20Re:=20On =20encouraging=20compliance=20with=20IPR=20disclosure=20r ules|References:=20<4F354E6A.3000507@labn.net>=20<6E0F3EF 65AE17D32372FDACE@PST.JCK.COM>=09<4F355803.2090103@isi.ed u>=09<5B6C268752C8008FAFCDCDF5@PST.JCK.COM>=20<4F356C57.3 08@isi.edu>=09<43BA3FC755F2E9553CE41821@PST.JCK.COM>=20<4 F358374.90600@isi.edu>|In-Reply-To:=20<4F358374.90600@isi .edu>|Content-Type:=20text/plain=3B=20charset=3D"ISO-8859 -1"=3B=20format=3Dflowed|Content-Transfer-Encoding:=207bi t|X-Originating-IP:=20[172.30.48.1]; bh=6hXusbQh3er4LG0sQCPpOALV8RXaxlLTMMcZ/N/8CmE=; b=qcZjBSR0CgfdTxoxPQmYKICHekb4bFviBsBkfDNCsbXHs6gGC9iqnHkb qqRrnL2uaArwPkJo4rWWzwvIf7vY4Dd9csiu7mjMBqZLIQ389zQYt9N4t Gh1cg6O0i75DS7XYhlb93latf5QPnddZMkSRJ9kTLco4xQ3KXVfi17Pw4 w=;
X-IronPort-AV: E=McAfee;i="5400,1158,6616"; a="159959702"
Received: from ironmsg04-l.qualcomm.com ([172.30.48.19]) by wolverine02.qualcomm.com with ESMTP; 10 Feb 2012 13:13:06 -0800
X-IronPort-AV: E=Sophos;i="4.73,396,1325491200"; d="scan'208";a="169595512"
Received: from nasanexhc05.na.qualcomm.com ([172.30.48.2]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/AES128-SHA; 10 Feb 2012 13:13:06 -0800
Received: from android-f1f182bb86f6b3f.wlan.qualcomm.com (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.2) with Microsoft SMTP Server (TLS) id 14.1.339.1; Fri, 10 Feb 2012 13:13:06 -0800
Message-ID: <4F35885F.9050708@qualcomm.com>
Date: Fri, 10 Feb 2012 13:13:03 -0800
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: Joe Touch <touch@isi.edu>
Subject: Re: On encouraging compliance with IPR disclosure rules
References: <4F354E6A.3000507@labn.net> <6E0F3EF65AE17D32372FDACE@PST.JCK.COM>	<4F355803.2090103@isi.edu>	<5B6C268752C8008FAFCDCDF5@PST.JCK.COM> <4F356C57.308@isi.edu>	<43BA3FC755F2E9553CE41821@PST.JCK.COM> <4F358374.90600@isi.edu>
In-Reply-To: <4F358374.90600@isi.edu>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Cc: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2012 21:13:28 -0000

Joe,

Note the domain name in that URL. That is certainly the distinction that 
the *RFC Editor* makes between authors and contributors, but the RFC 
Editor *does not* define "editor" except in the overload section, where 
the statement is absolutely clear that the names on the first page may 
not be all of the people who actually were authors of the document. 
Additionally, nowhere in that policy is definition of the IETF concept 
of "Document Editor" given; that's defined in RFC 2418.

I stand by my statement that for purposes of working groups, the folks 
listed on the first page, what the RFC Editor calls the "Authors" are in 
fact what the IETF calls "Document Editors" in the context of WG 
documents. Of course, like many IETF procedures, we are not rigid in 
this, and sometimes we put more people in that section than are 
designated WG Document Editors. But I continue to claim that it is well 
within IETF and RFC Editor policy for a WG to put its Document Editors 
into the RFC Editor's Authors section, and for it to be entirely under 
the discretion of the WG to decide who those people are.

pr

On 2/10/12 12:52 PM, Joe Touch wrote:
> John,
>
> See http://www.rfc-editor.org/policy.html, which distinguishes between 
> authors and editors, and indicates the latter as explicitly labeled.
>
> If you can find a place where all authors are replaced by an editor 
> for all WG submissions, and that those editors are not indicated 
> explicitly as editors, please cite it.
>
> Joe
>
> On 2/10/2012 12:20 PM, John C Klensin wrote:
>> Joe,
>>
>> Please see Pete's note for most of what I would have said.
>> Basically someone ceases to be an author (in the sense in which
>> you are using the term) the instant the document becomes a WG
>> (or, in the case of an individual submission, an IETF) work
>> product.  Some, including a few generations of IPR WGs would
>> argue that the cutover occurs even earlier.
>>
>> But see below.
>>
>> --On Friday, February 10, 2012 11:13 -0800 Joe Touch
>> <touch@isi.edu>  wrote:
>>
>>> Authorship is a matter of fact (granted, arguable fact in some
>>> cases).
>>
>> In the general case, I agree with you and have argued several
>> times in the past that the IETF should take that position
>> whenever possible.  But that has not been the prevailing
>> position.  If I write a document and turn it over to the IETF
>> --especially for standardization-- I am "contributing" _all_ of
>> the fundamental rights that come with authorship -- copyright,
>> change control, final authority over what is published, and even
>> the right to be identified in anything but the acknowledgments.
>> The document can be altered into something I disagree with and
>> the most I can do is to insist my name be taken off the front
>> page.   If I don't like those rules, I have one option, which is
>> not to contribute documents to the IETF (probably not to
>> participate in the IETF more generally, but I might be able to
>> split some hairs).
>>
>>> Editors and chairs are positions of trust and responsibility.
>>> I agree that these can - and should - incur penalties when we
>>> have reasonable belief that *any* IETF/IRTF process
>>> requirements aren't being respected - those include IPR,
>>> trading authorship for cookies, etc.
>>
>> Yes.  But once the documents become WG work products, someone
>> who might have been an author (in your sense) of an earlier
>> version becomes an editor for all future ones, with the text
>> under the control of the WG to the degree to which it decides to
>> assert itself, regardless of whether the document says "(ed.)"
>> or not.
>>
>>
>>>> Maybe that formal agreement with an author/editor should not
>>>> discuss sanctions but should merely require that person to
>>>> stand up in front of the WG and say "in front of all of you,
>>>> I am asserting that I understand the IPR policies and intend
>>>> to comply with them" because the really important thing is
>>>> that someone should not be able to wait until the 11th hour
>>>> (or a few hours past that) and then plead that they were
>>>> ignorant earlier.
>>>
>>> They should be please ignorance of the rules. They can
>>> *always* plead ignorance of the IPR being relevant, or of the
>>> IPR itself - that's a permanent "escape mechanism" at any
>>> point, and I don't see a way around it unfortunately.
>>
>> See my earlier response to Paul for this and several related
>> comments.
>>
>>>> FWIW, from my point of view, an author's ignoring the IPR
>>>> rules is exactly the same sort of breach of trust with the WG
>>>> that the author's refusing to follow WG consensus decisions
>>>> about what should be in the document would be.   As a WG
>>>> Chair, or even a WG participant, I want and need to have that
>>>> person out of that role, independent of (and superceding)
>>>> whatever other agreements might have been made.
>>>
>>> You can't undo authorship unless you cut text, IMO.
>>
>> I can in the IETF.  I recommend that you go read 3978 and the
>> Note Well again.   And, again, "author" on a document that is a
>> WG work product is s misnomer, a historical accident, or both.
>>
>>> ...
>>>> You may reasonably disagree, but I'd be interested in hearing
>>>> how you would propose to deal with breaches of the trust
>>>> relationship between the WG and an author/editor.  I don't
>>>> find "be nice, sympathize with the circumstances, and hope
>>>> there will never be another problem" particularly satisfying.
>>>> Perhaps I'm in the minority.
>>>
>>> See above - I agree with your suggestion for roles that are
>>> under the assignment of the IETF. I don't think it's
>>> appropriate for roles that should *never* (UNDER ANY
>>> CIRCIMSTANCES) be under the assignment of the IETF - and I put
>>> "author" in that bin.
>>
>> And, again, whether I agree with you about that being a useful
>> design is irrelevant.  The IETF has very clearly decided
>> otherwise and if I, as an author, don't like it I certainly have
>> the option of taking my document and going home, as long as I do
>> it before the document becomes an IETF "Contribution".
>>
>>       john
>>

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102


From lberger@labn.net  Fri Feb 10 13:15:06 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 7323521F8827 for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 13:15:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.033
X-Spam-Level: 
X-Spam-Status: No, score=-100.033 tagged_above=-999 required=5 tests=[AWL=2.128, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, GB_I_LETTER=-2, 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 Po1xKACfl947 for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 13:15:05 -0800 (PST)
Received: from oproxy6-pub.bluehost.com (oproxy6.bluehost.com [IPv6:2605:dc00:100:2::a6]) by ietfa.amsl.com (Postfix) with SMTP id 7598121F8741 for <wgchairs@ietf.org>; Fri, 10 Feb 2012 13:15:05 -0800 (PST)
Received: (qmail 13845 invoked by uid 0); 10 Feb 2012 21:15:05 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by cpoproxy3.bluehost.com with SMTP; 10 Feb 2012 21:15:05 -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=9XB35x+CFvtONhinDkAapI2saDK2q6cNqoonA/KdtIQ=;  b=k3UGaTGnK8KxaO6OhnO9xaeT9xXlxzdFSYFwsiifM704e4RpfWejj09Z2/sh4940SRgn5ozQFX+gskvgB1JmuqPJPYQ8lm0dW26rirdHTKwhcAhdLO/cnCqRbj60IHuc;
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 1Rvxo8-0005Sx-Tk; Fri, 10 Feb 2012 14:15:05 -0700
Message-ID: <4F3588D5.3090908@labn.net>
Date: Fri, 10 Feb 2012 16:15:01 -0500
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: David Harrington <ietfdbh@comcast.net>
Subject: Re: On encouraging compliance with IPR disclosure rules
References: <CB5AEDEB.1117F%ietfdbh@comcast.net>
In-Reply-To: <CB5AEDEB.1117F%ietfdbh@comcast.net>
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: Fri, 10 Feb 2012 21:15:06 -0000

Dave,
	I really think the following excerpt is the key point that we, as WG
chairs, need to keep in mind:

>From below:
> I think we do have the right to remove somebody as WG
> editor. So we should be able to remove them frpm the front page, but
> someplace in the document we need to acknowledge that they
> contributed to the document.

This is a reasonably sized hammer, already in our tool box and ready to
be used.  I still think it would be useful to have a published policy on
when it will be used, even just for the most egregious cases, to set
community expectations.

Lou

On 2/10/2012 4:01 PM, David Harrington wrote:
> Hi John,
> 
> I disagree with an assertion you make that the IETF can do anything they
> like with a contribution. From RFC3978:
> 
> <excerpt>
> 7.1.  Rights Granted in IETF Contributions
> 
>    The IETF/ISOC must obtain the right to publish an IETF Contribution
>    as an RFC or an Internet-Draft from the Contributors.
> 
>    A primary objective of this policy is to obtain from the document
>    authors only the non-exclusive rights that are needed to develop and
>    publish IETF Documents and to use the IETF Contributions in the IETF
>    Standards Process while leaving all other rights with the authors.
> 
>    The non-exclusive rights that the IETF needs are:
> 
>    a. the right to publish the document
>    b. the right to let the document be freely reproduced in the formats
>       that the IETF publishes it in
>    c. the right to let third parties translate it into languages other
>       than English
>    d. except where explicitly excluded (see Section 5.2), the right to
>       make derivative works within the IETF process.
>    e. the right to let third parties extract some logical parts, for
>       example MIB modules
> 
>    The authors retain all other rights, but cannot withdraw the above
>    rights from the IETF/ISOC.
> <end excerpt>
> 
> When I helped coordinate transferring the IETF Bridge MIB documents to
> IEEE for further work, the IEEE lawyers had to contact the authors to get
> permission to do derivative work because the IETF is not grated the right
> to grant to another SDO the right to develop derivative works.
> 
> I don't think the IETF has the right to remove somebody as author (and
> RFC3978 references the Berne agreement, which I suspect but don't know
> protects the author. I think we do have the right to remove somebody as WG
> editor. So we should be able to remove them frpm the front page, but
> someplace in the document we need to acknowledge that they contributed to
> the document.
> 
> I think lawyers need to decide just where that fine line exists between
> removing an editor and removing an author.
> 
> This is of course my own personal opinion, and I am not a lawyer, nor do I
> speak for the IESG.
> 
> --
> David Harrington
> Director, Transport Area
> Internet Engineering Task Force (IETF)
> Ietfdbh@comcast.net
> +1-603-828-1401
> 
> 
> 
> 
> 
> On 2/10/12 2:17 PM, "John C Klensin" <john-ietf@jck.com> wrote:
> 
>>
>>
>> --On Friday, February 10, 2012 12:48 -0500 Paul Kyzivat
>> <pkyzivat@alum.mit.edu> wrote:
>>
>>> ...
>>> While I agree with the philosophy expressed here, I wonder
>>> about the mechanics:
>>
>> See my previous note, but...
>>
>>> Surely we can remove someone as editor. But removing as author
>>> isn't so easy. (That discussion has been going on
>>> independently.) If this person has written most of the words
>>> in the doc, then it is pretty hard to remove them as an author
>>> of the document. (Unless of course the doc is also rewritten -
>>> presumably to avoid the IPR.)
>>
>> Nope.  RFC 3978, to which a pointer now appears in every new I-D
>> authors or editors post, clearly gives that text to the IETF to
>> do with as it likes, especially as part of the standards
>> process.  Taking someone who wrote a significant fraction of a
>> document and moving them to an acknowledgement that says as
>> little as "Thanks to Joe Furd for contributing very significant
>> portions of this document to the IETF" and as much more as the
>> WG believes to be appropriate.  We may have a problem with
>> patents and disclosure, but we have no problems at all in
>> copyrights in I-D text that is used by the IETF in creating IETF
>> documents (there are gray areas with other uses, but not with
>> that one).
>>
>> Again, I really don't see a situation in which the WG had every
>> reason to believe that an author knew the IPR rules and still
>> didn't disclose something she clearly knew about earlier as
>> different from one in which the WG says "change section 1.2.3 to
>> read..." and the author refuses because he doesn't like the
>> change).
>>
>> This would get complicated if the author, instead of saying "I
>> didn't understand or know about the IETF rules" said "I didn't
>> know about the IPR and couldn't reasonably be expected to know
>> about it".  Unless we have additional information that makes
>> those claims implausible, I think we have to accept that
>> position.  But, e.g., an inventor who is listed on a patent
>> application and who is also an IETF document author should be in
>> no position to claim lack of knowledge of either the IETF
>> policies or of the invention itself.
>>
>>
>>> Perhaps we could make past history of IPR disclosure problems
>>> a criterion in choosing editors of new documents, and of
>>> accepting new documents as WG drafts. But that does smack of
>>> blacklisting.
>>
>> I wouldn't describe it that way and I'm not keeping black lists.
>> But I do believe that WGs, and WG Chairs, do have a
>> responsibility to ensure an appropriate relationship of trust
>> between the WG and the author -- trust that includes both "you
>> will keep the document in line with WG consensus" and "you will
>> work to make sure you are in compliance with the letter and
>> spirit of the IPR policy".
>>
>> And, again, I see this much more in terms of making absolutely
>> sure that people are informed and cannot deny being informed and
>> in terms of trust than I do in terms of identifying and
>> punishing bad behavior.   In that regard, I think Adrian's work
>> on sanctions is very useful.  But, from my point of view, if we
>> get there, we have already failed, have a mess to clean up, and
>> want to deter future forms of bad behavior.   At least right
>> now, I'd rather concentrate on prevention and encouragement.
>>
>>    john
>>
> 
> 
> 
> 
> 
> 

From touch@isi.edu  Fri Feb 10 13:17:05 2012
Return-Path: <touch@isi.edu>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF84021F889B for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 13:17:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.992
X-Spam-Level: 
X-Spam-Status: No, score=-102.992 tagged_above=-999 required=5 tests=[AWL=-0.393, 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 duMhfffOLog7 for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 13:17:04 -0800 (PST)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id B4B0A21F8897 for <wgchairs@ietf.org>; Fri, 10 Feb 2012 13:17:04 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id q1ALH11g022620 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 10 Feb 2012 13:17:01 -0800 (PST)
Message-ID: <4F35894D.4020300@isi.edu>
Date: Fri, 10 Feb 2012 13:17:01 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: Pete Resnick <presnick@qualcomm.com>
Subject: Re: On encouraging compliance with IPR disclosure rules
References: <4F354E6A.3000507@labn.net> <6E0F3EF65AE17D32372FDACE@PST.JCK.COM>	<4F355803.2090103@isi.edu>	<5B6C268752C8008FAFCDCDF5@PST.JCK.COM> <4F356C57.308@isi.edu>	<43BA3FC755F2E9553CE41821@PST.JCK.COM> <4F358374.90600@isi.edu> <4F35885F.9050708@qualcomm.com>
In-Reply-To: <4F35885F.9050708@qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2012 21:17:05 -0000

On 2/10/2012 1:13 PM, Pete Resnick wrote:
> Joe,
>
> Note the domain name in that URL. That is certainly the distinction that
> the *RFC Editor* makes between authors and contributors, but the RFC
> Editor *does not* define "editor" except in the overload section, where
> the statement is absolutely clear that the names on the first page may
> not be all of the people who actually were authors of the document.
> Additionally, nowhere in that policy is definition of the IETF concept
> of "Document Editor" given; that's defined in RFC 2418.
>
> I stand by my statement that for purposes of working groups, the folks
> listed on the first page, what the RFC Editor calls the "Authors" are in
> fact what the IETF calls "Document Editors" in the context of WG
> documents.

Is that documented anywhere?

Is the distinction between "document editor" and how those individuals 
are indicated on the front matter of the RFC defined anywhere?

> Of course, like many IETF procedures, we are not rigid in
> this, and sometimes we put more people in that section than are
> designated WG Document Editors. But I continue to claim that it is well
> within IETF and RFC Editor policy for a WG to put its Document Editors
> into the RFC Editor's Authors section, and for it to be entirely under
> the discretion of the WG to decide who those people are.

I agree, but editors ought to be labeled as such, as per RFC Editor 
policy, as per typical publication policy throughout the publishing 
community.

Authors don't automatically become "just editors" when a doc becomes a 
WG doc.

Joe

> pr
>
> On 2/10/12 12:52 PM, Joe Touch wrote:
>> John,
>>
>> See http://www.rfc-editor.org/policy.html, which distinguishes between
>> authors and editors, and indicates the latter as explicitly labeled.
>>
>> If you can find a place where all authors are replaced by an editor
>> for all WG submissions, and that those editors are not indicated
>> explicitly as editors, please cite it.
>>
>> Joe
>>
>> On 2/10/2012 12:20 PM, John C Klensin wrote:
>>> Joe,
>>>
>>> Please see Pete's note for most of what I would have said.
>>> Basically someone ceases to be an author (in the sense in which
>>> you are using the term) the instant the document becomes a WG
>>> (or, in the case of an individual submission, an IETF) work
>>> product. Some, including a few generations of IPR WGs would
>>> argue that the cutover occurs even earlier.
>>>
>>> But see below.
>>>
>>> --On Friday, February 10, 2012 11:13 -0800 Joe Touch
>>> <touch@isi.edu> wrote:
>>>
>>>> Authorship is a matter of fact (granted, arguable fact in some
>>>> cases).
>>>
>>> In the general case, I agree with you and have argued several
>>> times in the past that the IETF should take that position
>>> whenever possible. But that has not been the prevailing
>>> position. If I write a document and turn it over to the IETF
>>> --especially for standardization-- I am "contributing" _all_ of
>>> the fundamental rights that come with authorship -- copyright,
>>> change control, final authority over what is published, and even
>>> the right to be identified in anything but the acknowledgments.
>>> The document can be altered into something I disagree with and
>>> the most I can do is to insist my name be taken off the front
>>> page. If I don't like those rules, I have one option, which is
>>> not to contribute documents to the IETF (probably not to
>>> participate in the IETF more generally, but I might be able to
>>> split some hairs).
>>>
>>>> Editors and chairs are positions of trust and responsibility.
>>>> I agree that these can - and should - incur penalties when we
>>>> have reasonable belief that *any* IETF/IRTF process
>>>> requirements aren't being respected - those include IPR,
>>>> trading authorship for cookies, etc.
>>>
>>> Yes. But once the documents become WG work products, someone
>>> who might have been an author (in your sense) of an earlier
>>> version becomes an editor for all future ones, with the text
>>> under the control of the WG to the degree to which it decides to
>>> assert itself, regardless of whether the document says "(ed.)"
>>> or not.
>>>
>>>
>>>>> Maybe that formal agreement with an author/editor should not
>>>>> discuss sanctions but should merely require that person to
>>>>> stand up in front of the WG and say "in front of all of you,
>>>>> I am asserting that I understand the IPR policies and intend
>>>>> to comply with them" because the really important thing is
>>>>> that someone should not be able to wait until the 11th hour
>>>>> (or a few hours past that) and then plead that they were
>>>>> ignorant earlier.
>>>>
>>>> They should be please ignorance of the rules. They can
>>>> *always* plead ignorance of the IPR being relevant, or of the
>>>> IPR itself - that's a permanent "escape mechanism" at any
>>>> point, and I don't see a way around it unfortunately.
>>>
>>> See my earlier response to Paul for this and several related
>>> comments.
>>>
>>>>> FWIW, from my point of view, an author's ignoring the IPR
>>>>> rules is exactly the same sort of breach of trust with the WG
>>>>> that the author's refusing to follow WG consensus decisions
>>>>> about what should be in the document would be. As a WG
>>>>> Chair, or even a WG participant, I want and need to have that
>>>>> person out of that role, independent of (and superceding)
>>>>> whatever other agreements might have been made.
>>>>
>>>> You can't undo authorship unless you cut text, IMO.
>>>
>>> I can in the IETF. I recommend that you go read 3978 and the
>>> Note Well again. And, again, "author" on a document that is a
>>> WG work product is s misnomer, a historical accident, or both.
>>>
>>>> ...
>>>>> You may reasonably disagree, but I'd be interested in hearing
>>>>> how you would propose to deal with breaches of the trust
>>>>> relationship between the WG and an author/editor. I don't
>>>>> find "be nice, sympathize with the circumstances, and hope
>>>>> there will never be another problem" particularly satisfying.
>>>>> Perhaps I'm in the minority.
>>>>
>>>> See above - I agree with your suggestion for roles that are
>>>> under the assignment of the IETF. I don't think it's
>>>> appropriate for roles that should *never* (UNDER ANY
>>>> CIRCIMSTANCES) be under the assignment of the IETF - and I put
>>>> "author" in that bin.
>>>
>>> And, again, whether I agree with you about that being a useful
>>> design is irrelevant. The IETF has very clearly decided
>>> otherwise and if I, as an author, don't like it I certainly have
>>> the option of taking my document and going home, as long as I do
>>> it before the document becomes an IETF "Contribution".
>>>
>>> john
>>>
>

From dworley@avaya.com  Fri Feb 10 14:17:04 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 A2E9421F86DC for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 14:17:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.443
X-Spam-Level: 
X-Spam-Status: No, score=-103.443 tagged_above=-999 required=5 tests=[AWL=0.156, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QfYEVTMr9i+6 for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 14:17:03 -0800 (PST)
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 933ED21F854E for <wgchairs@ietf.org>; Fri, 10 Feb 2012 14:17:03 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAJmWNU+HCzI1/2dsb2JhbABEr1iBBYFvAQEBAQIBEihECwIBCA0IIRAyJQEBBBMIGodanHKbY4tDKwULCQYLDwoEGgIGBAQDAYMZSScND4JzYwSISZJjjQY
X-IronPort-AV: E=Sophos;i="4.73,398,1325480400"; d="scan'208";a="329568261"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 10 Feb 2012 17:17:02 -0500
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 10 Feb 2012 17:02:48 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.137]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Fri, 10 Feb 2012 17:17:02 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: IETF WG Chairs <wgchairs@ietf.org>
Date: Fri, 10 Feb 2012 17:12:47 -0500
Subject: RE: On encouraging compliance with IPR disclosure rules
Thread-Topic: On encouraging compliance with IPR disclosure rules
Thread-Index: AczoHEPcdGWQXFNqShWspENl5LaVUAAJNsHL
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B226F573C21@DC-US1MBEX4.global.avaya.com>
References: <4F354E6A.3000507@labn.net> <6E0F3EF65AE17D32372FDACE@PST.JCK.COM>,<4F355880.4040607@labn.net>
In-Reply-To: <4F355880.4040607@labn.net>
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, 10 Feb 2012 22:17:04 -0000

> From: Lou Berger [lberger@labn.net]
>=20
> In particular, I think contributors need to clearly understand the
> implications of not following the the IPR disclosure rules.

This statement led me to ask, "*Are* there any implications of not
following the IPR disclosure rules?"

A later poster's comments stimulate me to suggest:

    The editorship of the draft is to be removed from the author in
    question, and a statement added to the draft saying "The editing of
    this document was removed from [Name] of [Company] due to his/her
    violation of the IPR rules of RFC xxxx."

Dale

From dworley@avaya.com  Fri Feb 10 14:40:49 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 5F53121F8658 for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 14:40:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.45
X-Spam-Level: 
X-Spam-Status: No, score=-103.45 tagged_above=-999 required=5 tests=[AWL=0.149, 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 A9ecpjTRe2El for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 14:40:48 -0800 (PST)
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 6CCA921F8657 for <wgchairs@ietf.org>; Fri, 10 Feb 2012 14:40:46 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAJScNU/GmAcF/2dsb2JhbABDr1yBBYFvAQEBAQIBEihECwIBCA0IIRAyJQIEARIIGodanwiTeotlBBUJBgsPCgQaAgYEBAECAYMZSScND4JzYwSISZJjjQY
X-IronPort-AV: E=Sophos;i="4.73,398,1325480400"; d="scan'208";a="329571755"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 10 Feb 2012 17:40:46 -0500
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by co300216-co-erhwest-out.avaya.com with ESMTP; 10 Feb 2012 17:34:42 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.137]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Fri, 10 Feb 2012 17:40:45 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "afarrel@juniper.net" <afarrel@juniper.net>, 'IETF WG Chairs' <wgchairs@ietf.org>
Date: Fri, 10 Feb 2012 17:39:07 -0500
Subject: RE: On encouraging compliance with IPR disclosure rules
Thread-Topic: On encouraging compliance with IPR disclosure rules
Thread-Index: AQEzvzBEB/irVKyyg9XGvkhZeBmoTgMFXiSOAng2Da4BINCscpc0FndwgAABmtA=
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B226F573C24@DC-US1MBEX4.global.avaya.com>
References: <4F354E6A.3000507@labn.net> <6E0F3EF65AE17D32372FDACE@PST.JCK.COM>,<4F355880.4040607@labn.net> <CD5674C3CD99574EBA7432465FC13C1B226F573C21@DC-US1MBEX4.global.avaya.com>, <020501cce844$214d3570$63e7a050$@juniper.net>
In-Reply-To: <020501cce844$214d3570$63e7a050$@juniper.net>
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, 10 Feb 2012 22:40:49 -0000

> From: Adrian Farrel [afarrel@juniper.net]
>=20
> Dale, at the risk of becoming a bore...
>=20
> Please read draft-farrresnickel-ipr-sanctions

'Twould have been more informative if you'd said, "I've included that
as part of one possible sanction, listed in item 4g of
draft-farrresnickel-ipr-sanctions."

Dale

From johnl@iecc.com  Fri Feb 10 17:42:07 2012
Return-Path: <johnl@iecc.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D79BB21E801A for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 17:42:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.908
X-Spam-Level: 
X-Spam-Status: No, score=-109.908 tagged_above=-999 required=5 tests=[AWL=1.291, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LO42jpkVqcpm for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 17:42:07 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id DEDDD21E801D for <wgchairs@ietf.org>; Fri, 10 Feb 2012 17:42:06 -0800 (PST)
Received: (qmail 29026 invoked from network); 11 Feb 2012 01:42:04 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 11 Feb 2012 01:42:04 -0000
Date: 11 Feb 2012 01:41:42 -0000
Message-ID: <20120211014142.2523.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: wgchairs@ietf.org
Subject: Re: On encouraging compliance with IPR disclosure rules
In-Reply-To: <4F356E91.3060504@isi.edu>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Feb 2012 01:42:08 -0000

>Authorship goes beyond copyright.

In both directions.  Some people think that author credit is very
important, perhaps because their salary depends on how many documents
they publish.  For others of us, it's purely a vanity thing, and in
some circumstances I'd cheerily horse trade author credit, with
minimal concern about whether some third party felt offended.  So I
agree that using it as a club or a bargaining chip is not a good idea.

The IETF, due to its deliberate lack of structure, has a very weak set
of sanctions.  I don't see anything practical beyond name and shame.

R's,
John

From keith.drage@alcatel-lucent.com  Fri Feb 10 17:44:14 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 D3E7421F8518 for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 17:44:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.304
X-Spam-Level: 
X-Spam-Status: No, score=-107.304 tagged_above=-999 required=5 tests=[AWL=-1.055, BAYES_00=-2.599, HELO_EQ_FR=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 FIC6X2aaNY0s for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 17:44:13 -0800 (PST)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [62.23.212.57]) by ietfa.amsl.com (Postfix) with ESMTP id 35EC421F8516 for <wgchairs@ietf.org>; Fri, 10 Feb 2012 17:44:12 -0800 (PST)
Received: from FRMRSSXCHHUB01.dc-m.alcatel-lucent.com (FRMRSSXCHHUB01.dc-m.alcatel-lucent.com [135.120.45.61]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q1B1i8hX019998 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sat, 11 Feb 2012 02:44:09 +0100
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.46]) by FRMRSSXCHHUB01.dc-m.alcatel-lucent.com ([135.120.45.61]) with mapi; Sat, 11 Feb 2012 02:44:08 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Russ Housley <housley@vigilsec.com>, IETF WG Chairs <wgchairs@ietf.org>
Date: Sat, 11 Feb 2012 02:44:03 +0100
Subject: RE: DRAFT Revision to the WG Document Writeup (about IPR)
Thread-Topic: DRAFT Revision to the WG Document Writeup (about IPR)
Thread-Index: Acznl+SP6E2+jiI7QXe41OFIyP8n0gAxk9vA
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE224A6B6CE@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <AE35FF1F-47D2-4AB3-B074-6CCBA5B6AC25@vigilsec.com> <201110271852.p9RIqcOO025921@mtv-core-3.cisco.com> <FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com>
In-Reply-To: <FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.80
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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, 11 Feb 2012 01:44:15 -0000

One thing I have noted recently is a number of documents that have got beyo=
nd publication request (indeed even to IESG ballot) and have then changed s=
tatus (e.g. informational to proposed standard).

I certainly change the style of my review for an informational document and=
 a proposed standard document, and therefore a change at this late stage co=
uld mean the document has not had the best targeted review.

Could I suggest adding something at the publication request stage that trie=
s to identify if it has been verified that the document is submitted as the=
 correct type of document.

Regards

Keith

> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
> Behalf Of Russ Housley
> Sent: 10 February 2012 02:01
> To: IETF WG Chairs
> Subject: Re: DRAFT Revision to the WG Document Writeup (about IPR)
>=20
> It has taken me a very long time to incorporate all of the comments into =
a
> revised draft of the WG Document Writeup.  Here is the revision.  Please
> review and comment.
>=20
> Russ
>=20
> =3D =3D =3D =3D =3D =3D =3D =3D =3D
>=20
> Document Writeup
>=20
> As required by RFC 4858, this is the current template for the Document
> Shepherd Write-Up.
>=20
> Changes are expected over time. This DRAFT version is dated
> 9 February 2012.
>=20
>   (1) Briefly describe the review of this document that was
>       performed by the Document Shepherd.  If this version of the
>       document is not ready for publication, please explain why the
>       document is being forwarded to the IESG.
>=20
>   (2) Has the document had adequate review both from WG participants?
>       Does the Document Shepherd have any concerns about the depth or
>       breadth of the reviews that have been performed?
>=20
>   (3) Do portions of the document need review from a particular or
>       from broader perspective, e.g., security, operational complexity,
>       AAA, DNS, DHCP, XML, or internationalization? If so, describe the
>       review that took place.
>=20
>   (4) Describe any specific concerns or issues that the Document
>       Shepherd has with this document that the Responsible Area
>       Director and/or the IESG should be aware of? For example,
>       perhaps he or she is uncomfortable with certain parts of the
>       document, or has concerns whether there really is a need for it.
>       In any event, if the WG has discussed those issues and has
>       indicated that it still wishes to advance the document, detail
>       those concerns here.
>=20
>   (5) Has an IPR disclosure been filed that references this document?
>       If so, summarize any WG discussion and conclusion regarding the
>       IPR disclosures.
>=20
>   (6) How solid is the WG consensus behind this document? Does it
>       represent the strong concurrence of a few individuals, with
>       others being silent, or does the WG as a whole understand and
>       agree with it?
>=20
>   (7) Has anyone threatened an appeal or otherwise indicated extreme
>       discontent? If so, please summarise the areas of conflict in
>       separate email messages to the Responsible Area Director. (It
>       should be in a separate email because this questionnaire is
>       publicly available.)
>=20
>   (8) Identify any ID nits the Document Shepherd has found in this
>       document. (See the Internet-Drafts Checklist and
>       http://www.ietf.org/tools/idnits/). Boilerplate checks are not
>       enough; this check needs to be thorough.
>=20
>   (9) Describe how the document meets any required formal review
>       criteria, such as the MIB Doctor, media type, and URI type
>       reviews.
>=20
>  (10) Have all references within this been document been identified
>       as either normative and informative? Are there normative
>       references to documents that are not ready for advancement or
>       are otherwise in an unclear state? If such normative references
>       exist, what is the plan for their completion? Are there normative
>       references that are downward references (see [RFC3967])? If so,
>       list these downward references to support the Area Director in
>       the Last Call procedure.
>=20
>  (11) List other RFCs that this document obsoletes, and indicate whether
>       the to-be-obsolete RFCs are listed in both the title page header
>       as well as in the Abstract and Introduction. Which if these RFCs,
>       if any, are to be moved to Historic? Is this change of status
>       explicitly stated in the document Introduction.
>=20
>  (12) List other RFCs that this document updates, and indicate whether
>       they appear in both the title page header as well as in the
>       Abstract and Introduction.
>=20
>  (13) Describe the Document Shepherd's review of the IANA considerations
>       section, especially with regard to its consistency with the body
>       of the document. Confirm that all protocol extensions that the
>       document makes are associated with the appropriate reservations
>       in IANA registries. Confirm that any referenced IANA registries
>       have been clearly identified. Confirm that newly created IANA
>       registries include a detailed specification of the initial
>       contents for the registry, that allocations procedures for
>       future registrations are defined, and a reasonable name for the
>       new registry has been suggested (see [RFC5226]). List any IANA
>       Experts that the IESG will need to appoint during IESG Evaluation
>       for any new registries that require Expert Review for future
>       allocations.
>=20
>  (14) Describe reviews and automated checks performed by the Document
>       Shepherd to validate sections of the document written in a formal
>       language, such as XML code, BNF rules, MIB definitions, etc.
>=20
>  (14) The IESG approval announcement includes a Document Announcement
>       Write-Up. Please provide such a Document Announcement Write-Up.
>       Recent examples can be found in the "Action" announcements for
>       approved documents. The approval announcement contains the
>       following sections:
>=20
>       Technical Summary
>=20
>         Relevant content can frequently be found in the abstract
>         and/or introduction of the document. If not, this may be
>         an indication that there are deficiencies in the abstract
>         or introduction.
>=20
>       Working Group Summary
>=20
>         Was there anything in WG process that is worth noting? For
>         example, was there controversy about particular points or
>         were there decisions where the consensus was particularly
>         rough?
>=20
>       Document Quality
>=20
>         Are there existing implementations of the protocol? Have a
>         significant number of vendors indicated their plan to
>         implement the specification? Are there any reviewers that
>         merit special mention as having done a thorough review,
>         e.g., one that resulted in important changes or a
>         conclusion that the document had no substantive issues? If
>         there was a MIB Doctor, Media Type or other expert review,
>         what was its course (briefly)? In the case of a Media Type
>         review, on what date was the request posted?
>=20
>       Personnel
>=20
>         Who is the Document Shepherd? Who is the Responsible Area
>         Director.


From paul.hoffman@vpnc.org  Fri Feb 10 18:06:18 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 4264021F85C2 for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 18:06:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.564
X-Spam-Level: 
X-Spam-Status: No, score=-102.564 tagged_above=-999 required=5 tests=[AWL=0.035, 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 DxQEuqNW0-9Y for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 18:06:17 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id CE6F021F85C6 for <wgchairs@ietf.org>; Fri, 10 Feb 2012 18:06:17 -0800 (PST)
Received: from [10.20.30.100] (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 q1B26E3k068324 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 10 Feb 2012 19:06:15 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: DRAFT Revision to the WG Document Writeup (about IPR)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE224A6B6CE@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Date: Fri, 10 Feb 2012 18:06:14 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <BF07712E-4102-4F85-9971-599BAC4A470B@vpnc.org>
References: <AE35FF1F-47D2-4AB3-B074-6CCBA5B6AC25@vigilsec.com> <201110271852.p9RIqcOO025921@mtv-core-3.cisco.com> <FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com> <EDC0A1AE77C57744B664A310A0B23AE224A6B6CE@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
X-Mailer: Apple Mail (2.1257)
Cc: IETF WG Chairs <wgchairs@ietf.org>, Russ Housley <housley@vigilsec.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Feb 2012 02:06:18 -0000

On Feb 10, 2012, at 5:44 PM, DRAGE, Keith (Keith) wrote:

> Could I suggest adding something at the publication request stage that =
tries to identify if it has been verified that the document is submitted =
as the correct type of document.


As someone who is "guilty as charged", I give a +1 to this.

--Paul Hoffman


From fred@cisco.com  Sun Feb 12 21:41:41 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 9C08D21F85F8 for <wgchairs@ietfa.amsl.com>; Sun, 12 Feb 2012 21:41:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T-OZgRAqTr08 for <wgchairs@ietfa.amsl.com>; Sun, 12 Feb 2012 21:41:40 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 44C3221F85F7 for <wgchairs@ietf.org>; Sun, 12 Feb 2012 21:41:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=988; q=dns/txt; s=iport; t=1329111696; x=1330321296; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=sdub53Sh5asuse49LytOJkZysR84jn+pPG1QsqNE+Bg=; b=h0+Llq/gPOFWgakd5ysm80KjAoMXIPBSCfGagcUG1R3i7bv0zsWJ3/kb hIklLlR1TPe4ZEr+JbAKTcZ+DhRPoyp1k3Flxgo65I2UK72MXgu1J9clA p1Gl/CfKvz/DkOD6f10GTQ7YdGxlPAWs/LIXbT0vRVvVnEzLAwdjBNt5L w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EACWhOE+Q/khN/2dsb2JhbABDr3eBB4FyAQEBAwESASc/BQsLRlcGNYdammYBnVyLRAomBQULBQIEBwIHBwsEAQUUAQMVgxgFBj0kCwECCgcEgnJjBIhKjGiFWo0o
X-IronPort-AV: E=Sophos;i="4.73,410,1325462400"; d="scan'208";a="65956269"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-2.cisco.com with ESMTP; 13 Feb 2012 05:41:34 +0000
Received: from Freds-Computer.local (rtp-vpn6-274.cisco.com [10.82.249.19]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id q1D5f1kV029650; Mon, 13 Feb 2012 05:41:34 GMT
Received: from [127.0.0.1] by Freds-Computer.local (PGP Universal service); Mon, 13 Feb 2012 00:41:34 -0500
X-PGP-Universal: processed; by Freds-Computer.local on Mon, 13 Feb 2012 00:41:34 -0500
Subject: Re: [BOFCHAIRS] DRAFT Revision to the WG Document Writeup (about IPR)
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <4F356DA4.4000309@gmail.com>
Date: Sun, 12 Feb 2012 22:44:05 -0500
Message-Id: <3CA94B86-5E83-462E-8206-EB6E9E15626A@cisco.com>
References: <AE35FF1F-47D2-4AB3-B074-6CCBA5B6AC25@vigilsec.com>	<201110271852.p9RIqcOO025921@mtv-core-3.cisco.com>	<FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com>	<7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CA9E@MX14A.corp.emc.com>	<23B2E96E-08CE-40D1-8038-89A7A672E9F5@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CAE1@MX14A.corp.emc.com> <4F356DA4.4000309@gmail.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: Working Group Chairs <wgchairs@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2012 05:41:41 -0000

On Feb 10, 2012, at 2:19 PM, Brian E Carpenter wrote:

> Stated like that, of course, it looks like a purely bureaucratic and =
rather pointless requirement.=20

to be honest, a lot of this looks bureaucratic to me. If the draft =
states (as it has the option to via xm2rfc and in any event in the first =
page header) that it updates an RFC, it seems that information could be =
derived from the document without ALSO being included in the abstract. =
The document shepherd's review is available online; why does it ALSO =
need to be described (first question)? Specifically what description is =
called for in addition to what is online?

To my small and inefficient mind, the questions in this document should =
address the questions the IESG asks itself, the shepherd, and the =
authors. Ideally, having answered them, any further questions the IESG =
has should be specific to the document, not general. And they should =
need to be answered once, in one place.=

From gvandeve@cisco.com  Mon Feb 13 02:13:25 2012
Return-Path: <gvandeve@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3576321F8687 for <wgchairs@ietfa.amsl.com>; Mon, 13 Feb 2012 02:13:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.449
X-Spam-Level: 
X-Spam-Status: No, score=-10.449 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 Yrwv+fIqcAT9 for <wgchairs@ietfa.amsl.com>; Mon, 13 Feb 2012 02:13:24 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id D4E8621F867E for <wgchairs@ietf.org>; Mon, 13 Feb 2012 02:13:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=gvandeve@cisco.com; l=1289; q=dns/txt; s=iport; t=1329128003; x=1330337603; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=ugsiZBc8l+VPRla8eU0xW+z761l/lswVZefWvw6vTY8=; b=heran5J/at0hiaTiZDs63yI0DIgKGV8+ngeTYyFUDvmRajqOftw/lsAO wrTSYpDisb0s6qsS3WNcuY6hCbVyyeg0fJ9wpcAAWfkZVMu/la4B3DznE yqfoLL5+oTOLkKZsAYZM0ge+JXeJ59ack3OK4xkoHwcSOrEUeFo2kX36N c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EANDhOE+Q/khR/2dsb2JhbABEsACBB4FyAQEBAwESAR0KPwUHBAIBCBEEAQELBhcBBgFFCQgBAQQBEggah1qdEgGWJItECiYFBQs9ASaEBAsBAgoHBIJyYwSoFw
X-IronPort-AV: E=Sophos;i="4.73,411,1325462400"; d="scan'208";a="65976818"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-2.cisco.com with ESMTP; 13 Feb 2012 10:13:22 +0000
Received: from xbh-ams-201.cisco.com (xbh-ams-201.cisco.com [144.254.75.7]) by ams-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id q1DADMHh012931; Mon, 13 Feb 2012 10:13:22 GMT
Received: from xmb-ams-102.cisco.com ([144.254.74.77]) by xbh-ams-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 13 Feb 2012 11:13:22 +0100
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: [BOFCHAIRS] DRAFT Revision to the WG Document Writeup (about IPR)
Date: Mon, 13 Feb 2012 11:13:21 +0100
Message-ID: <5C99EC8C99D9BB45AC51D20DC2AD2DC506D64C9A@XMB-AMS-102.cisco.com>
In-Reply-To: <3CA94B86-5E83-462E-8206-EB6E9E15626A@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BOFCHAIRS] DRAFT Revision to the WG Document Writeup (about IPR)
Thread-Index: AczqEi4ebfHLjVynTeuzT7Km2uIMagAJeXnw
References: <AE35FF1F-47D2-4AB3-B074-6CCBA5B6AC25@vigilsec.com>	<201110271852.p9RIqcOO025921@mtv-core-3.cisco.com>	<FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com>	<7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CA9E@MX14A.corp.emc.com>	<23B2E96E-08CE-40D1-8038-89A7A672E9F5@vigilsec.com><7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CAE1@MX14A.corp.emc.com><4F356DA4.4000309@gmail.com> <3CA94B86-5E83-462E-8206-EB6E9E15626A@cisco.com>
From: "Gunter Van de Velde (gvandeve)" <gvandeve@cisco.com>
To: "Fred Baker (fred)" <fred@cisco.com>, "Russ Housley" <housley@vigilsec.com>
X-OriginalArrivalTime: 13 Feb 2012 10:13:22.0701 (UTC) FILETIME=[1DDD43D0:01CCEA38]
Cc: Working Group Chairs <wgchairs@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2012 10:13:25 -0000

+1.

G/

-----Original Message-----
From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
Behalf Of Fred Baker (fred)
Sent: maandag 13 februari 2012 4:44
To: Russ Housley
Cc: Working Group Chairs; Brian E Carpenter
Subject: Re: [BOFCHAIRS] DRAFT Revision to the WG Document Writeup
(about IPR)


On Feb 10, 2012, at 2:19 PM, Brian E Carpenter wrote:

> Stated like that, of course, it looks like a purely bureaucratic and
rather pointless requirement.=20

to be honest, a lot of this looks bureaucratic to me. If the draft
states (as it has the option to via xm2rfc and in any event in the first
page header) that it updates an RFC, it seems that information could be
derived from the document without ALSO being included in the abstract.
The document shepherd's review is available online; why does it ALSO
need to be described (first question)? Specifically what description is
called for in addition to what is online?

To my small and inefficient mind, the questions in this document should
address the questions the IESG asks itself, the shepherd, and the
authors. Ideally, having answered them, any further questions the IESG
has should be specific to the document, not general. And they should
need to be answered once, in one place.

From acee.lindem@ericsson.com  Mon Feb 13 03:08:26 2012
Return-Path: <acee.lindem@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 32B8C21F8588 for <wgchairs@ietfa.amsl.com>; Mon, 13 Feb 2012 03:08:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.508
X-Spam-Level: 
X-Spam-Status: No, score=-6.508 tagged_above=-999 required=5 tests=[AWL=0.091,  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 7d6i7YxdnQKX for <wgchairs@ietfa.amsl.com>; Mon, 13 Feb 2012 03:08:25 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 1893B21F85F1 for <wgchairs@ietf.org>; Mon, 13 Feb 2012 03:08:25 -0800 (PST)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q1DB8AOn019206; Mon, 13 Feb 2012 05:08:22 -0600
Received: from EUSAACMS0702.eamcs.ericsson.se ([169.254.1.135]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Mon, 13 Feb 2012 06:08:17 -0500
From: Acee Lindem <acee.lindem@ericsson.com>
To: "Gunter Van de Velde (gvandeve)" <gvandeve@cisco.com>
Date: Mon, 13 Feb 2012 06:08:14 -0500
Subject: Re: [BOFCHAIRS] DRAFT Revision to the WG Document Writeup (about IPR)
Thread-Topic: [BOFCHAIRS] DRAFT Revision to the WG Document Writeup (about IPR)
Thread-Index: AczqP8kkKnXnuEdSQ6GedX++OSQmtQ==
Message-ID: <4581A9D5-774B-4909-87AF-B954FA45C3FA@ericsson.com>
References: <AE35FF1F-47D2-4AB3-B074-6CCBA5B6AC25@vigilsec.com> <201110271852.p9RIqcOO025921@mtv-core-3.cisco.com> <FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CA9E@MX14A.corp.emc.com> <23B2E96E-08CE-40D1-8038-89A7A672E9F5@vigilsec.com><7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CAE1@MX14A.corp.emc.com><4F356DA4.4000309@gmail.com> <3CA94B86-5E83-462E-8206-EB6E9E15626A@cisco.com> <5C99EC8C99D9BB45AC51D20DC2AD2DC506D64C9A@XMB-AMS-102.cisco.com>
In-Reply-To: <5C99EC8C99D9BB45AC51D20DC2AD2DC506D64C9A@XMB-AMS-102.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Working Group Chairs <wgchairs@ietf.org>, Russ Housley <housley@vigilsec.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2012 11:08:26 -0000

+1 - I'm perfectly happy with the current document shepherd template.=20
Acee=20
On Feb 13, 2012, at 5:13 AM, Gunter Van de Velde (gvandeve) wrote:

> +1.
>=20
> G/
>=20
> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
> Behalf Of Fred Baker (fred)
> Sent: maandag 13 februari 2012 4:44
> To: Russ Housley
> Cc: Working Group Chairs; Brian E Carpenter
> Subject: Re: [BOFCHAIRS] DRAFT Revision to the WG Document Writeup
> (about IPR)
>=20
>=20
> On Feb 10, 2012, at 2:19 PM, Brian E Carpenter wrote:
>=20
>> Stated like that, of course, it looks like a purely bureaucratic and
> rather pointless requirement.=20
>=20
> to be honest, a lot of this looks bureaucratic to me. If the draft
> states (as it has the option to via xm2rfc and in any event in the first
> page header) that it updates an RFC, it seems that information could be
> derived from the document without ALSO being included in the abstract.
> The document shepherd's review is available online; why does it ALSO
> need to be described (first question)? Specifically what description is
> called for in addition to what is online?
>=20
> To my small and inefficient mind, the questions in this document should
> address the questions the IESG asks itself, the shepherd, and the
> authors. Ideally, having answered them, any further questions the IESG
> has should be specific to the document, not general. And they should
> need to be answered once, in one place.


From ogud@ogud.com  Mon Feb 13 07:19:49 2012
Return-Path: <ogud@ogud.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8A0021F862A for <wgchairs@ietfa.amsl.com>; Mon, 13 Feb 2012 07:19:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.474
X-Spam-Level: 
X-Spam-Status: No, score=-106.474 tagged_above=-999 required=5 tests=[AWL=0.125, 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 vhxrs-Zk2aCM for <wgchairs@ietfa.amsl.com>; Mon, 13 Feb 2012 07:19:48 -0800 (PST)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by ietfa.amsl.com (Postfix) with ESMTP id 673D221F851B for <wgchairs@ietf.org>; Mon, 13 Feb 2012 07:19:48 -0800 (PST)
Received: from [IPv6:::1] (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.4/8.14.4) with ESMTP id q1DFJkkw010128 for <wgchairs@ietf.org>; Mon, 13 Feb 2012 10:19:46 -0500 (EST) (envelope-from ogud@ogud.com)
Message-ID: <4F392A11.3040608@ogud.com>
Date: Mon, 13 Feb 2012 10:19:45 -0500
From: Olafur Gudmundsson <ogud@ogud.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: DRAFT Revision to the WG Document Writeup (about IPR)
References: <AE35FF1F-47D2-4AB3-B074-6CCBA5B6AC25@vigilsec.com> <201110271852.p9RIqcOO025921@mtv-core-3.cisco.com> <FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com>
In-Reply-To: <FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.72 on 10.20.30.4
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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, 13 Feb 2012 15:19:49 -0000

Russ,

Personally I would like (14) Writeups first and then the other sections 
as background.

	Olafur


On 09/02/2012 21:01, Russ Housley wrote:
> It has taken me a very long time to incorporate all of the comments into a revised draft of the WG Document Writeup.  Here is the revision.  Please review and comment.
>
> Russ
>
> = = = = = = = = =
>
> Document Writeup
>
> As required by RFC 4858, this is the current template for the Document
> Shepherd Write-Up.
>
> Changes are expected over time. This DRAFT version is dated
> 9 February 2012.
>
>    (1) Briefly describe the review of this document that was
>        performed by the Document Shepherd.  If this version of the
>        document is not ready for publication, please explain why the
>        document is being forwarded to the IESG.
>
>    (2) Has the document had adequate review both from WG participants?
>        Does the Document Shepherd have any concerns about the depth or
>        breadth of the reviews that have been performed?
>
>    (3) Do portions of the document need review from a particular or
>        from broader perspective, e.g., security, operational complexity,
>        AAA, DNS, DHCP, XML, or internationalization? If so, describe the
>        review that took place.
>
>    (4) Describe any specific concerns or issues that the Document
>        Shepherd has with this document that the Responsible Area
>        Director and/or the IESG should be aware of? For example,
>        perhaps he or she is uncomfortable with certain parts of the
>        document, or has concerns whether there really is a need for it.
>        In any event, if the WG has discussed those issues and has
>        indicated that it still wishes to advance the document, detail
>        those concerns here.
>
>    (5) Has an IPR disclosure been filed that references this document?
>        If so, summarize any WG discussion and conclusion regarding the
>        IPR disclosures.
>
>    (6) How solid is the WG consensus behind this document? Does it
>        represent the strong concurrence of a few individuals, with
>        others being silent, or does the WG as a whole understand and
>        agree with it?
>
>    (7) Has anyone threatened an appeal or otherwise indicated extreme
>        discontent? If so, please summarise the areas of conflict in
>        separate email messages to the Responsible Area Director. (It
>        should be in a separate email because this questionnaire is
>        publicly available.)
>
>    (8) Identify any ID nits the Document Shepherd has found in this
>        document. (See the Internet-Drafts Checklist and
>        http://www.ietf.org/tools/idnits/). Boilerplate checks are not
>        enough; this check needs to be thorough.
>
>    (9) Describe how the document meets any required formal review
>        criteria, such as the MIB Doctor, media type, and URI type
>        reviews.
>
>   (10) Have all references within this been document been identified
>        as either normative and informative? Are there normative
>        references to documents that are not ready for advancement or
>        are otherwise in an unclear state? If such normative references
>        exist, what is the plan for their completion? Are there normative
>        references that are downward references (see [RFC3967])? If so,
>        list these downward references to support the Area Director in
>        the Last Call procedure.
>
>   (11) List other RFCs that this document obsoletes, and indicate whether
>        the to-be-obsolete RFCs are listed in both the title page header
>        as well as in the Abstract and Introduction. Which if these RFCs,
>        if any, are to be moved to Historic? Is this change of status
>        explicitly stated in the document Introduction.
>
>   (12) List other RFCs that this document updates, and indicate whether
>        they appear in both the title page header as well as in the
>        Abstract and Introduction.
>
>   (13) Describe the Document Shepherd's review of the IANA considerations
>        section, especially with regard to its consistency with the body
>        of the document. Confirm that all protocol extensions that the
>        document makes are associated with the appropriate reservations
>        in IANA registries. Confirm that any referenced IANA registries
>        have been clearly identified. Confirm that newly created IANA
>        registries include a detailed specification of the initial
>        contents for the registry, that allocations procedures for
>        future registrations are defined, and a reasonable name for the
>        new registry has been suggested (see [RFC5226]). List any IANA
>        Experts that the IESG will need to appoint during IESG Evaluation
>        for any new registries that require Expert Review for future
>        allocations.
>
>   (14) Describe reviews and automated checks performed by the Document
>        Shepherd to validate sections of the document written in a formal
>        language, such as XML code, BNF rules, MIB definitions, etc.
>
>   (14) The IESG approval announcement includes a Document Announcement
>        Write-Up. Please provide such a Document Announcement Write-Up.
>        Recent examples can be found in the "Action" announcements for
>        approved documents. The approval announcement contains the
>        following sections:
>
>        Technical Summary
>
>          Relevant content can frequently be found in the abstract
>          and/or introduction of the document. If not, this may be
>          an indication that there are deficiencies in the abstract
>          or introduction.
>
>        Working Group Summary
>
>          Was there anything in WG process that is worth noting? For
>          example, was there controversy about particular points or
>          were there decisions where the consensus was particularly
>          rough?
>
>        Document Quality
>
>          Are there existing implementations of the protocol? Have a
>          significant number of vendors indicated their plan to
>          implement the specification? Are there any reviewers that
>          merit special mention as having done a thorough review,
>          e.g., one that resulted in important changes or a
>          conclusion that the document had no substantive issues? If
>          there was a MIB Doctor, Media Type or other expert review,
>          what was its course (briefly)? In the case of a Media Type
>          review, on what date was the request posted?
>
>        Personnel
>
>          Who is the Document Shepherd? Who is the Responsible Area
>          Director.
>
>
>
>


From afarrel@juniper.net  Fri Feb 10 14:34:24 2012
Return-Path: <afarrel@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 8996521F85E5 for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 14:34:24 -0800 (PST)
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 ohMI0Xz-JiWC for <wgchairs@ietfa.amsl.com>; Fri, 10 Feb 2012 14:34:24 -0800 (PST)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id A993221F85C4 for <wgchairs@ietf.org>; Fri, 10 Feb 2012 14:34:23 -0800 (PST)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id q1AMYJu2028802;  Fri, 10 Feb 2012 22:34:19 GMT
Received: from 950129200 (cust.static.46-14-3-100.swisscomdata.ch [46.14.3.100]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id q1AMYIDc028788 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 10 Feb 2012 22:34:19 GMT
From: "Adrian Farrel" <afarrel@juniper.net>
To: "'Worley, Dale R \(Dale\)'" <dworley@avaya.com>, "'IETF WG Chairs'" <wgchairs@ietf.org>
References: <4F354E6A.3000507@labn.net>	<6E0F3EF65AE17D32372FDACE@PST.JCK.COM>, <4F355880.4040607@labn.net> <CD5674C3CD99574EBA7432465FC13C1B226F573C21@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B226F573C21@DC-US1MBEX4.global.avaya.com>
Subject: RE: On encouraging compliance with IPR disclosure rules
Date: Fri, 10 Feb 2012 22:34:19 -0000
Message-ID: <020501cce844$214d3570$63e7a050$@juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Content-language: en-gb
Thread-Index: AQEzvzBEB/irVKyyg9XGvkhZeBmoTgMFXiSOAng2Da4BINCscpc0Fndw
X-Mailman-Approved-At: Mon, 13 Feb 2012 08:10:03 -0800
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: afarrel@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: Fri, 10 Feb 2012 22:34:24 -0000

Dale, at the risk of becoming a bore...

Please read draft-farrresnickel-ipr-sanctions

Adrian

> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On Behalf
> Of Worley, Dale R (Dale)
> Sent: 10 February 2012 22:13
> To: IETF WG Chairs
> Subject: RE: On encouraging compliance with IPR disclosure rules
> 
> > From: Lou Berger [lberger@labn.net]
> >
> > In particular, I think contributors need to clearly understand the
> > implications of not following the the IPR disclosure rules.
> 
> This statement led me to ask, "*Are* there any implications of not
> following the IPR disclosure rules?"
> 
> A later poster's comments stimulate me to suggest:
> 
>     The editorship of the draft is to be removed from the author in
>     question, and a statement added to the draft saying "The editing of
>     this document was removed from [Name] of [Company] due to his/her
>     violation of the IPR rules of RFC xxxx."
> 
> Dale


From jhutz@cmu.edu  Mon Feb 13 08:46:08 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 0A4F821F873B for <wgchairs@ietfa.amsl.com>; Mon, 13 Feb 2012 08:46:08 -0800 (PST)
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 7ucPd9VoXFky for <wgchairs@ietfa.amsl.com>; Mon, 13 Feb 2012 08:46:07 -0800 (PST)
Received: from smtp01.srv.cs.cmu.edu (SMTP01.SRV.CS.CMU.EDU [128.2.217.196]) by ietfa.amsl.com (Postfix) with ESMTP id 5627321F8739 for <wgchairs@ietf.org>; Mon, 13 Feb 2012 08:46:06 -0800 (PST)
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 q1DGk2rd021307 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 13 Feb 2012 11:46:03 -0500 (EST)
Subject: Re: [BOFCHAIRS] DRAFT Revision to the WG Document Writeup (about IPR)
From: Jeffrey Hutzelman <jhutz@cmu.edu>
To: Fred Baker <fred@cisco.com>
In-Reply-To: <22335_1329111705_q1D5fhsg006616_3CA94B86-5E83-462E-8206-EB6E9E15626A@cisco.com>
References: <AE35FF1F-47D2-4AB3-B074-6CCBA5B6AC25@vigilsec.com> <201110271852.p9RIqcOO025921@mtv-core-3.cisco.com> <FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CA9E@MX14A.corp.emc.com> <23B2E96E-08CE-40D1-8038-89A7A672E9F5@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CAE1@MX14A.corp.emc.com> <4F356DA4.4000309@gmail.com> <22335_1329111705_q1D5fhsg006616_3CA94B86-5E83-462E-8206-EB6E9E15626A@cisco.com>
Content-Type: text/plain; charset="UTF-8"
Date: Mon, 13 Feb 2012 11:45:57 -0500
Message-ID: <1329151557.24918.201.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: Working Group Chairs <wgchairs@ietf.org>, Russ Housley <housley@vigilsec.com>, Brian E Carpenter <brian.e.carpenter@gmail.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: Mon, 13 Feb 2012 16:46:08 -0000

On Sun, 2012-02-12 at 22:44 -0500, Fred Baker wrote:
> On Feb 10, 2012, at 2:19 PM, Brian E Carpenter wrote:
> 
> > Stated like that, of course, it looks like a purely bureaucratic and
>  rather pointless requirement. 
> 
> to be honest, a lot of this looks bureaucratic to me. If the draft
>  states (as it has the option to via xm2rfc and in any event in the
>  first page header) that it updates an RFC, it seems that information
>  could be derived from the document without ALSO being included in the
>  abstract.

Except that the entire _point_ of the abstract is that people can read
it to get an idea of what the document is about when they don't _have_
the document.  An abstract needs to stand _completely_ on its own; the
person reading it doesn't have metadata from XML or our tracker or the
first-page header.

To a lesser extent, this applies to the introduction, too -- the person
reading the introduction to a published RFC (or even an I-D) isn't
reading the XML or the tracker; they're reading the text.  I'd certainly
agree that there's no specific need to duplicate this information in
both the introduction _and_ the header.  However, as long as the
canonical version of our documents is the plain text and not XML, it
needs to be in some standard, machine-readable place so that tools can
find it.  Whether it _also_ needs to be mentioned in the introduction is
IMHO a matter of style and should mostly be left up to the
author/editor, though personally I'll generally encourage doing so.



>  The document shepherd's review is available online; why does
>  it ALSO need to be described (first question)? Specifically what
>  description is called for in addition to what is online?

Hm?  The writeup that is the answer to these questions is available
online.  But the shepherd is also expected to read and review the
document, and there's no standard place to find the results of that,
unless you count reading the mailing list and looking for it, which
won't always be successful, because there is no requirement that the
shepherd post any comments (I usually find something to comment on, but
not always).

In any case, the point of the question is not to obtain information, but
to cause the shepherd to do a review _before_ submitting the writeup, so
he can answer "yes".  The same goes for most of these questions -- in
most cases, there is a common, trivial answer and a less common answer
that requires explanation; the point is to get the shepherd to check on
these things and point out anything unusual.  


-- Jeff


From brian.e.carpenter@gmail.com  Mon Feb 13 12:28:00 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 1F2EB21F870E for <wgchairs@ietfa.amsl.com>; Mon, 13 Feb 2012 12:28:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.402
X-Spam-Level: 
X-Spam-Status: No, score=-103.402 tagged_above=-999 required=5 tests=[AWL=0.197, 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 tPAhFWcWobFL for <wgchairs@ietfa.amsl.com>; Mon, 13 Feb 2012 12:27:59 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6B38721F8656 for <wgchairs@ietf.org>; Mon, 13 Feb 2012 12:27:54 -0800 (PST)
Received: by yhkk25 with SMTP id k25so3031381yhk.31 for <wgchairs@ietf.org>; Mon, 13 Feb 2012 12:27:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Xt70icpAWFkyBJue0YSQl7aCC1DtJn7cJeQS6R5e5x8=; b=sbSL4ybnA8SOs4fvJumyeYa532twVcEeg/ElVOwkehq5sdRN4G0krsiV+scYWP0kLV 8juuZchGFeJdz451qu+A0cSq2OaEQA8yFLIH3CQBEgfR7yTf7QJMGIjJg4wU8AGBlh4V 2hEFTmHN+YPWtXUvoL2YbFgj0mMigKlc37/78=
Received: by 10.50.178.106 with SMTP id cx10mr29792448igc.15.1329164873782; Mon, 13 Feb 2012 12:27:53 -0800 (PST)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz. [130.216.38.124]) by mx.google.com with ESMTPS id va6sm15541322igc.4.2012.02.13.12.27.49 (version=SSLv3 cipher=OTHER); Mon, 13 Feb 2012 12:27:52 -0800 (PST)
Message-ID: <4F397242.905@gmail.com>
Date: Tue, 14 Feb 2012 09:27:46 +1300
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: Jeffrey Hutzelman <jhutz@cmu.edu>
Subject: Re: [BOFCHAIRS] DRAFT Revision to the WG Document Writeup (about IPR)
References: <AE35FF1F-47D2-4AB3-B074-6CCBA5B6AC25@vigilsec.com>	 <201110271852.p9RIqcOO025921@mtv-core-3.cisco.com>	 <FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com>	 <7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CA9E@MX14A.corp.emc.com>	 <23B2E96E-08CE-40D1-8038-89A7A672E9F5@vigilsec.com>	 <7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CAE1@MX14A.corp.emc.com>	 <4F356DA4.4000309@gmail.com>	 <22335_1329111705_q1D5fhsg006616_3CA94B86-5E83-462E-8206-EB6E9E15626A@cisco.com> <1329151557.24918.201.camel@destiny.pc.cs.cmu.edu>
In-Reply-To: <1329151557.24918.201.camel@destiny.pc.cs.cmu.edu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Working Group Chairs <wgchairs@ietf.org>, Russ Housley <housley@vigilsec.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2012 20:28:00 -0000

On 2012-02-14 05:45, Jeffrey Hutzelman wrote:
> On Sun, 2012-02-12 at 22:44 -0500, Fred Baker wrote:
>> On Feb 10, 2012, at 2:19 PM, Brian E Carpenter wrote:
>>
>>> Stated like that, of course, it looks like a purely bureaucratic and
>>  rather pointless requirement. 
>>
>> to be honest, a lot of this looks bureaucratic to me. If the draft
>>  states (as it has the option to via xm2rfc and in any event in the
>>  first page header) that it updates an RFC, it seems that information
>>  could be derived from the document without ALSO being included in the
>>  abstract.
> 
> Except that the entire _point_ of the abstract is that people can read
> it to get an idea of what the document is about when they don't _have_
> the document.  An abstract needs to stand _completely_ on its own; the
> person reading it doesn't have metadata from XML or our tracker or the
> first-page header.

Allow me to invent an example of what I think would be reasonable:

Updates: 791

Abstract

This document updates the IPv4 specification (RFC 791) by abolishing fragmentation.

Introduction

Since [RFC791] introduced the notion of dynamic fragmentation and reassembly
of Internet Protocol packets, it has proved to be operationally complex
and error-prone (for example, see [RFC1435], [RFC2923], [RFC4459]). It also
creates security risks [RFC1858], [RFC3128]. This document therefore
removes the notion of fragmentation from IP version 4 and redefines the
associated header fields as reserved for future use.

   Brian

> 
> To a lesser extent, this applies to the introduction, too -- the person
> reading the introduction to a published RFC (or even an I-D) isn't
> reading the XML or the tracker; they're reading the text.  I'd certainly
> agree that there's no specific need to duplicate this information in
> both the introduction _and_ the header.  However, as long as the
> canonical version of our documents is the plain text and not XML, it
> needs to be in some standard, machine-readable place so that tools can
> find it.  Whether it _also_ needs to be mentioned in the introduction is
> IMHO a matter of style and should mostly be left up to the
> author/editor, though personally I'll generally encourage doing so.
> 
> 
> 
>>  The document shepherd's review is available online; why does
>>  it ALSO need to be described (first question)? Specifically what
>>  description is called for in addition to what is online?
> 
> Hm?  The writeup that is the answer to these questions is available
> online.  But the shepherd is also expected to read and review the
> document, and there's no standard place to find the results of that,
> unless you count reading the mailing list and looking for it, which
> won't always be successful, because there is no requirement that the
> shepherd post any comments (I usually find something to comment on, but
> not always).
> 
> In any case, the point of the question is not to obtain information, but
> to cause the shepherd to do a review _before_ submitting the writeup, so
> he can answer "yes".  The same goes for most of these questions -- in
> most cases, there is a common, trivial answer and a less common answer
> that requires explanation; the point is to get the shepherd to check on
> these things and point out anything unusual.  
> 
> 
> -- Jeff
> 
> 

From jhutz@cmu.edu  Mon Feb 13 14:24:55 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 94FAF21F8672 for <wgchairs@ietfa.amsl.com>; Mon, 13 Feb 2012 14:24:55 -0800 (PST)
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 xcwkxUy0po3l for <wgchairs@ietfa.amsl.com>; Mon, 13 Feb 2012 14:24:54 -0800 (PST)
Received: from smtp02.srv.cs.cmu.edu (SMTP02.SRV.CS.CMU.EDU [128.2.217.197]) by ietfa.amsl.com (Postfix) with ESMTP id 50F9C21F8685 for <wgchairs@ietf.org>; Mon, 13 Feb 2012 14:24:54 -0800 (PST)
Received: from [66.233.146.161] (66-233-146-161.pit.clearwire-wmx.net [66.233.146.161] (may be forged)) (authenticated bits=0) by smtp02.srv.cs.cmu.edu (8.13.6/8.13.6) with ESMTP id q1DMOiMp028326 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 13 Feb 2012 17:24:50 -0500 (EST)
Subject: Re: [BOFCHAIRS] DRAFT Revision to the WG Document Writeup (about IPR)
From: Jeffrey Hutzelman <jhutz@cmu.edu>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <17462_1329164882_q1DKS1es028144_4F397242.905@gmail.com>
References: <AE35FF1F-47D2-4AB3-B074-6CCBA5B6AC25@vigilsec.com> <201110271852.p9RIqcOO025921@mtv-core-3.cisco.com> <FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CA9E@MX14A.corp.emc.com> <23B2E96E-08CE-40D1-8038-89A7A672E9F5@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CAE1@MX14A.corp.emc.com> <4F356DA4.4000309@gmail.com> <22335_1329111705_q1D5fhsg006616_3CA94B86-5E83-462E-8206-EB6E9E15626A@cisco.com> <1329151557.24918.201.camel@destiny.pc.cs.cmu.edu> <17462_1329164882_q1DKS1es028144_4F397242.905@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Date: Mon, 13 Feb 2012 17:24:43 -0500
Message-ID: <1329171883.24918.238.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: Working Group Chairs <wgchairs@ietf.org>, Russ Housley <housley@vigilsec.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: Mon, 13 Feb 2012 22:24:55 -0000

On Tue, 2012-02-14 at 09:27 +1300, Brian E Carpenter wrote:
> On 2012-02-14 05:45, Jeffrey Hutzelman wrote:
> > On Sun, 2012-02-12 at 22:44 -0500, Fred Baker wrote:
> >> On Feb 10, 2012, at 2:19 PM, Brian E Carpenter wrote:
> >>
> >>> Stated like that, of course, it looks like a purely bureaucratic and
> >>  rather pointless requirement. 
> >>
> >> to be honest, a lot of this looks bureaucratic to me. If the draft
> >>  states (as it has the option to via xm2rfc and in any event in the
> >>  first page header) that it updates an RFC, it seems that information
> >>  could be derived from the document without ALSO being included in the
> >>  abstract.
> > 
> > Except that the entire _point_ of the abstract is that people can read
> > it to get an idea of what the document is about when they don't _have_
> > the document.  An abstract needs to stand _completely_ on its own; the
> > person reading it doesn't have metadata from XML or our tracker or the
> > first-page header.
> 
> Allow me to invent an example of what I think would be reasonable:

OK, so we are in agreement.

Though it seems like assembling those references is an awful lot of
effort to go to in order to demonstrate that. :-)


From chair@ietf.org  Tue Feb 14 11:36:58 2012
Return-Path: <chair@ietf.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 554A521E809F; Tue, 14 Feb 2012 11:36:58 -0800 (PST)
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 JAnKJctZGJr0; Tue, 14 Feb 2012 11:36:53 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id DC4B721E801B; Tue, 14 Feb 2012 11:36:53 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id D145912C871; Tue, 14 Feb 2012 11:36:52 -0800 (PST)
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 VG0sxhVFoUCu; Tue, 14 Feb 2012 11:36:52 -0800 (PST)
Received: from [192.168.2.104] (pool-96-241-165-215.washdc.fios.verizon.net [96.241.165.215]) by c8a.amsl.com (Postfix) with ESMTPSA id 79A9912BFFD; Tue, 14 Feb 2012 11:36:52 -0800 (PST)
From: IETF Chair <chair@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Major upgrade to the IETF Datatracker
Date: Tue, 14 Feb 2012 14:36:51 -0500
Message-Id: <E50AF16F-60A4-48AC-9B39-ED8E3560FB24@ietf.org>
To: IETF Announce <ietf-announce@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Cc: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2012 19:36:58 -0000

Shortly, the IETF datatracker will go through a major change, one of the =
two largest since it was first deployed more than 10 years ago.  =
Hopefully no one will notice.

The previous major change was in 2007, when we switched the public =
Datatracker from Perl cgi-bin scripts to a much more modern and safe =
implementation based on the Django web application framework.  Very few =
people noticed that change at the time.

In a few days, we will transition to completely redesigned Datatracker =
database schema.  The new schema will better support today's needs, and =
we believe it will better support future enhancements.  Frankly, we =
outgrew the old schema some time ago.

In order to achieve a nearly unnoticeable change-over, we now invite you =
to try out the new Datatracker, bang on it, kick the tires, and =
generally see if it works as well for you as the old one.

For some additional insight, you may want to read the instructions that =
was given to our testers:
 http://trac.tools.ietf.org/tools/ietfdb/wiki/InstructionsForTesters

Or, you may want to just jump in and see how it works.  Either way, =
please report any bugs, problems, surprises, gremlins, hiccups, flaws, =
and so on that you discover.  Reports will receive prompt attention.  We =
deploy new code upgrades (if any are available) every hour. Please use =
this mail list to report issues:
 iola-conversion-tool@ietf.org

Try out the new Datatracker, and help us make a smooth transition.  The =
new Datatracker is running here:
 https://trackerbeta.ietf.org/

Thank you for your assistance,
  Russ=

From housley@vigilsec.com  Wed Feb 15 10:25:50 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 2623921E8075 for <wgchairs@ietfa.amsl.com>; Wed, 15 Feb 2012 10:25:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.491
X-Spam-Level: 
X-Spam-Status: No, score=-102.491 tagged_above=-999 required=5 tests=[AWL=0.108, 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 2Ct-fSqqrGGW for <wgchairs@ietfa.amsl.com>; Wed, 15 Feb 2012 10:25:49 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id A5E8721E8071 for <wgchairs@ietf.org>; Wed, 15 Feb 2012 10:25:49 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 40F709A473C; Wed, 15 Feb 2012 13:25:56 -0500 (EST)
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 7goeVES5fpw6; Wed, 15 Feb 2012 13:25:44 -0500 (EST)
Received: from [192.168.2.104] (pool-96-241-165-215.washdc.fios.verizon.net [96.241.165.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 3BAA5F24047; Wed, 15 Feb 2012 13:25:55 -0500 (EST)
Subject: Re: DRAFT Revision to the WG Document Writeup (about IPR)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CAE1@MX14A.corp.emc.com>
Date: Wed, 15 Feb 2012 13:25:47 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <7D5B9928-1D93-43DC-A50C-E74BF81E53F3@vigilsec.com>
References: <AE35FF1F-47D2-4AB3-B074-6CCBA5B6AC25@vigilsec.com> <201110271852.p9RIqcOO025921@mtv-core-3.cisco.com> <FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CA9E@MX14A.corp.emc.com> <23B2E96E-08CE-40D1-8038-89A7A672E9F5@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CAE1@MX14A.corp.emc.com>
To: <david.black@emc.com> <david.black@emc.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: Wed, 15 Feb 2012 18:25:50 -0000

The numbers have changed to address another comment.  I hope this =
wording captures your concern.=20

(12) List other RFCs that this document obsoletes, and indicate whether=20=

      the to-be-obsolete RFCs are listed in the title page header, in
      the Abstract, and in the Introduction. Which of these RFCs, if
      any, are to be moved to Historic? Is this change of status
      explicitly stated in the document Introduction?

 (13) List other RFCs that this document updates, and indicate whether
      they appear in the title page header, in the Abstract, and in the
      Introduction. If the updated RFCs are not listed in the Abstract
      and Introduction, explain why, and point to part of the document
      that describes the nature of the updates. If this information is
      not in the document, explain why the WG considers it unnecessary.

Russ


On Feb 10, 2012, at 10:51 AM, <david.black@emc.com> =
<david.black@emc.com> wrote:

> Russ,
>=20
>>> For both of these items, is the "and" in "Abstract and Introduction"
>>> intended to be AND, OR, or XOR ?
>>=20
>> AND
>=20
> Suggested edit for clarity in items 11 and 12:
>=20
> OLD
> 	both the title page header as well as in the Abstract
> 	and Introduction
> NEW
> 	all three of a) the title page header, b) the Abstract
> 	and c) the Introduction.
> END
>=20
> Your revised text for (13) looks fine to me.
>=20
> Thanks,
> --David


From david.black@emc.com  Wed Feb 15 10:41:51 2012
Return-Path: <david.black@emc.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8283721E8071 for <wgchairs@ietfa.amsl.com>; Wed, 15 Feb 2012 10:41:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.502
X-Spam-Level: 
X-Spam-Status: No, score=-109.502 tagged_above=-999 required=5 tests=[AWL=1.097, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bh4NHljP-iat for <wgchairs@ietfa.amsl.com>; Wed, 15 Feb 2012 10:41:51 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id DF7BB21E8027 for <wgchairs@ietf.org>; Wed, 15 Feb 2012 10:41:50 -0800 (PST)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q1FIfnjF007225 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 15 Feb 2012 13:41:49 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.129]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor); Wed, 15 Feb 2012 13:41:24 -0500
Received: from mxhub15.corp.emc.com (mxhub15.corp.emc.com [128.222.70.236]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q1FIfNXe023284; Wed, 15 Feb 2012 13:41:23 -0500
Received: from mxhub37.corp.emc.com (128.222.70.104) by mxhub15.corp.emc.com (128.222.70.236) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 15 Feb 2012 13:41:23 -0500
Received: from mx14a.corp.emc.com ([169.254.1.94]) by mxhub37.corp.emc.com ([128.222.70.104]) with mapi; Wed, 15 Feb 2012 13:41:22 -0500
From: <david.black@emc.com>
To: <housley@vigilsec.com>
Date: Wed, 15 Feb 2012 13:41:21 -0500
Subject: RE: DRAFT Revision to the WG Document Writeup (about IPR)
Thread-Topic: DRAFT Revision to the WG Document Writeup (about IPR)
Thread-Index: AczsEEMSqw8qF8T6RfOFBmmJFSTBIAAASJBA
Message-ID: <7C4DFCE962635144B8FAE8CA11D0BF1E05AD33AA9D@MX14A.corp.emc.com>
References: <AE35FF1F-47D2-4AB3-B074-6CCBA5B6AC25@vigilsec.com> <201110271852.p9RIqcOO025921@mtv-core-3.cisco.com> <FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CA9E@MX14A.corp.emc.com> <23B2E96E-08CE-40D1-8038-89A7A672E9F5@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CAE1@MX14A.corp.emc.com> <7D5B9928-1D93-43DC-A50C-E74BF81E53F3@vigilsec.com>
In-Reply-To: <7D5B9928-1D93-43DC-A50C-E74BF81E53F3@vigilsec.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: 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, 15 Feb 2012 18:41:51 -0000

Looks good, Thanks, --David


> -----Original Message-----
> From: Russ Housley [mailto:housley@vigilsec.com]
> Sent: Wednesday, February 15, 2012 1:26 PM
> To: Black, David
> Cc: wgchairs@ietf.org
> Subject: Re: DRAFT Revision to the WG Document Writeup (about IPR)
>=20
> The numbers have changed to address another comment.  I hope this wording=
 captures your concern.
>=20
> (12) List other RFCs that this document obsoletes, and indicate whether
>       the to-be-obsolete RFCs are listed in the title page header, in
>       the Abstract, and in the Introduction. Which of these RFCs, if
>       any, are to be moved to Historic? Is this change of status
>       explicitly stated in the document Introduction?
>=20
>  (13) List other RFCs that this document updates, and indicate whether
>       they appear in the title page header, in the Abstract, and in the
>       Introduction. If the updated RFCs are not listed in the Abstract
>       and Introduction, explain why, and point to part of the document
>       that describes the nature of the updates. If this information is
>       not in the document, explain why the WG considers it unnecessary.
>=20
> Russ
>=20
>=20
> On Feb 10, 2012, at 10:51 AM, <david.black@emc.com> <david.black@emc.com>=
 wrote:
>=20
> > Russ,
> >
> >>> For both of these items, is the "and" in "Abstract and Introduction"
> >>> intended to be AND, OR, or XOR ?
> >>
> >> AND
> >
> > Suggested edit for clarity in items 11 and 12:
> >
> > OLD
> > 	both the title page header as well as in the Abstract
> > 	and Introduction
> > NEW
> > 	all three of a) the title page header, b) the Abstract
> > 	and c) the Introduction.
> > END
> >
> > Your revised text for (13) looks fine to me.
> >
> > Thanks,
> > --David
>=20


From wwwrun@ietfa.amsl.com  Wed Feb 15 12:35:44 2012
Return-Path: <wwwrun@ietfa.amsl.com>
X-Original-To: wgchairs@ietf.org
Delivered-To: wgchairs@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 30) id 3D16321F8646; Wed, 15 Feb 2012 12:35:44 -0800 (PST)
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Subject: IETF 83 - Meeting Information 
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20120215203544.3D16321F8646@ietfa.amsl.com>
Date: Wed, 15 Feb 2012 12:35:44 -0800 (PST)
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, 15 Feb 2012 20:35:44 -0000

IETF 83 Meeting
Paris, France
March 25-30, 2012
Host: TBD

Meeting venue:  Le Palais des Congres de Paris
http://www.viparis.com/Viparis/exhibition-paris/site/Palais-Congres-Paris-Paris/en/4

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

1.  Registration
2.  Visas & Letters of Invitation
3.  Accommodations
4.  Transportation to Venues
5.  Companion Program

1. Registration
	A. Early-Bird Registration - USD 650.00 Pay by Friday, 16 March 2012 1700 PT (UTC -7) 
	B. After Early-Bird cutoff - USD 800.00
	C. Full-time Student Registrations - USD 150.00 (with proper ID)
	D. One Day Pass Registration - USD 350.00
	E. Registration Cancellation 	
		Cut-off for registration cancellation is Monday, 19 March 2012 at 1700 PT (UTC -7). 
		Cancellations are subject to a 10% (ten percent)cancellation fee if requested by 
		that date and time.
	F. Online Registration and Payment ends Friday, 23 March 2012,1700 local Paris time.
	G. On-site Registration starting Sunday, 25 March 2012 at 1100 local Paris time.

2. Visas & Letters of Invitation: 
	Information on Visiting France, please visit:
	http://www.consulfrance-sanfrancisco.org/spip.php?rubrique201

	After you complete the registration process, you can request an electronic IETF Letter
	of Invitation. You may also request one at a later time by following the link provided
	in the confirmation email. 

	Orange has graciously offered to provide letters of invitation (LOIs) for those who 
	needs visas to enter France. In order to add this functionality, the letter of invitation 
	system will be offline next Tuesday (Monday is a holiday in the United States). We expect
	to start providing IETF and Host LOIs on Wednesday of next week, and will send a notice 
	out as soon as the system is operational. 

3.  Accommodations
	The Hotel Concorde La Fayette (Headquarter Hotel - connected to meeting venue) 
	The Le Meridien Etoile (directly across the street from the meeting venue). 
	**Le Meridien no longer has single queen bed rooms available, only twin bed rooms 
	available. The cutoff date for Le Meridien is February 15, after this date, if you 
	would like to see if there is availability at the IETF group rate, send an email to 
	<Corinne.Vissenberg@lemeridien.com>

	Room rates include one complimentary daily buffet breakfast and complimentary in-room
	high-speed Internet access. All service fees and VAT are included in guest room rates.

	NOTE: Continental Breakfast will NOT be served at the meeting venue.

	Reservations Cut off Date: 
	Le Meridien - 15 February 2012 (only twin rooms available)
	Hotel Concorde - 09 March 2012

****Cancellation Policy at Le Meridien****
	Guest Cancellation:
	- There is no charge if room is cancelled prior to March 2012
	- There is a one night charge for cancellations made between 09-23 March 2012
	- If the room is cancelled from 23 March 2012 or if the guest is a "no-show" then 
	the amount of the entire stay will be charged onto the guest's credit card.

	Early Departure Fee: Early departure will be charged for the duration of the stay 
	as reserved if changes are made after March 23, 2012.

	Guest Substitution: Guest name substitute may be made by contacting Corinne Vissenberg
	 <Corinne.Vissenberg@lemeridien.com>.

****Cancellation Policy at Hotel Concorde***        
	Reservation Deposit and Cancellations:
	- Guaranteed reservations will be held until the night of the arrival date. 
	- Guests will be be charged 1 night's stay and tax at the time the reservation is made. 
	- 15 days prior to scheduled arrival the guest's credit card shall be charged for an 
	additional 2 nights stay and tax which is non-refundable.
	
	Guest Cancellation: 
	- Guest will forfeit the non-refundable deposit paid as of the date of the cancellation.

	Guest Substitution: 
	- Guests may substitute names for reserved rooms without  penalty.

	Early Departure Fee: 
	- In the event of early departure, the guest will be charged for the remainder of their
	stay. Should the room nights be re-sold, the guest will be refunded for the resold room 
	nights.

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

4.  Transportation
	Information on "Transportation" options to get to the Concorde and Le Meridien Hotels 
	can be found on the IETF83 Meeting Page http://www.ietf.org/meeting/83/index.html under 
	"Venue and Area Information" as well as on the IETF83 Wiki, under "Meeting Communication" 
	headings.

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

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

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

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

Only 38 days until the Paris IETF!

From housley@vigilsec.com  Wed Feb 15 12:54:38 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 9D18D21E808D for <wgchairs@ietfa.amsl.com>; Wed, 15 Feb 2012 12:54:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.497
X-Spam-Level: 
X-Spam-Status: No, score=-102.497 tagged_above=-999 required=5 tests=[AWL=0.102, 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 gRjjSY4QL4p5 for <wgchairs@ietfa.amsl.com>; Wed, 15 Feb 2012 12:54:34 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 7FB3621E8086 for <wgchairs@ietf.org>; Wed, 15 Feb 2012 12:54:34 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 06CC6F24121 for <wgchairs@ietf.org>; Wed, 15 Feb 2012 15:54:51 -0500 (EST)
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 7ggBn7IHyf0w for <wgchairs@ietf.org>; Wed, 15 Feb 2012 15:54:15 -0500 (EST)
Received: from [192.168.2.104] (pool-96-241-165-215.washdc.fios.verizon.net [96.241.165.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id E7122F24112 for <wgchairs@ietf.org>; Wed, 15 Feb 2012 15:54:46 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: DRAFT Revision to the WG Document Writeup
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <7C4DFCE962635144B8FAE8CA11D0BF1E05AD33AA9D@MX14A.corp.emc.com>
Date: Wed, 15 Feb 2012 15:54:28 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <365EF4B3-53D2-4AB8-BC8D-F0803F734E15@vigilsec.com>
References: <AE35FF1F-47D2-4AB3-B074-6CCBA5B6AC25@vigilsec.com> <201110271852.p9RIqcOO025921@mtv-core-3.cisco.com> <FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CA9E@MX14A.corp.emc.com> <23B2E96E-08CE-40D1-8038-89A7A672E9F5@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CAE1@MX14A.corp.emc.com> <7D5B9928-1D93-43DC-A50C-E74BF81E53F3@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD33AA9D@MX14A.corp.emc.com>
To: IETF WG Chairs <wgchairs@ietf.org>
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: Wed, 15 Feb 2012 20:54:38 -0000

I believe that I have addresses all comments, including the requests for =
a different style and ordering.

Russ

=3D =3D =3D =3D =3D =3D =3D =3D =3D

Document Writeup

As required by RFC 4858, this is the current template for the Document
Shepherd Write-Up.

Changes are expected over time. This DRAFT version is dated
15 February 2012.

(1) What type of RFC is being requested (BCP, Proposed Standard,
Internet Standard, Informational, Experimental, or Historic)?

(2) The IESG approval announcement includes a Document Announcement
Write-Up. Please provide such a Document Announcement Write-Up. Recent
examples can be found in the "Action" announcements for approved
documents. The approval announcement contains the following sections:

Technical Summary

   Relevant content can frequently be found in the abstract=20
   and/or introduction of the document. If not, this may be=20
   an indication that there are deficiencies in the abstract=20
   or introduction.

Working Group Summary

   Was there anything in WG process that is worth noting? For=20
   example, was there controversy about particular points or=20
   were there decisions where the consensus was particularly=20
   rough?

Document Quality

   Are there existing implementations of the protocol? Have a=20
   significant number of vendors indicated their plan to=20
   implement the specification? Are there any reviewers that=20
   merit special mention as having done a thorough review,=20
   e.g., one that resulted in important changes or a=20
   conclusion that the document had no substantive issues? If=20
   there was a MIB Doctor, Media Type or other expert review,=20
   what was its course (briefly)? In the case of a Media Type=20
   review, on what date was the request posted?

 Personnel

   Who is the Document Shepherd? Who is the Responsible Area
   Director?

(3) Briefly describe the review of this document that was performed by
the Document Shepherd.  If this version of the document is not ready
for publication, please explain why the document is being forwarded to
the IESG.

(4) Has the document had adequate review from WG participants? Does the
document Shepherd have any concerns about the depth or breadth of the
reviews that have been performed? =20

(5) Do portions of the document need review from a particular or from
broader perspective, e.g., security, operational complexity, AAA, DNS,
DHCP, XML, or internationalization? If so, describe the review that
took place.

(6) Describe any specific concerns or issues that the Document Shepherd
has with this document that the Responsible Area Director and/or the
IESG should be aware of? For example, perhaps he or she is uncomfortable
with certain parts of the document, or has concerns whether there really
is a need for it. In any event, if the WG has discussed those issues and
has indicated that it still wishes to advance the document, detail those
concerns here.

(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. If not, explain why.

(8) Has an IPR disclosure been filed that references this document?
If so, summarize any WG discussion and conclusion regarding the IPR
disclosures.

(9) How solid is the WG consensus behind this document? Does it=20
represent the strong concurrence of a few individuals, with others
being silent, or does the WG as a whole understand and agree with it?  =20=


(10) Has anyone threatened an appeal or otherwise indicated extreme=20
discontent? If so, please summarise the areas of conflict in separate
email messages to the Responsible Area Director. (It should be in a
separate email because this questionnaire is publicly available.)=20

(11) Identify any ID nits the Document Shepherd has found in this
document. (See http://www.ietf.org/tools/idnits/ and the Internet-Drafts
Checklist). Boilerplate checks are not enough; this check needs to be
thorough.

(12) Describe how the document meets any required formal review
criteria, such as the MIB Doctor, media type, and URI type reviews.

(13) Have all references within this document been identified as
either normative and informative? Are there normative references to
documents that are not ready for advancement or are otherwise in an
unclear state? If such normative references exist, what is the plan for
their completion? Are there normative references that are downward
references (see RFC 3967)? If so, list these downward references to
support the Area Director in the Last Call procedure.=20

(14) List other RFCs that this document obsoletes, and indicate whether
the to-be-obsolete RFCs are listed in the title page header, in the
Abstract, and in the Introduction. Which of these RFCs, if any, are to
be moved to Historic? Is this change of status explicitly stated in the
Introduction?

(15) List other RFCs that this document updates, and indicate whether
they appear in the title page header, in the Abstract, and in the
Introduction. If the updated RFCs are not listed in the Abstract and
Introduction, explain why, and point to part of the document that
describes the nature of the updates. If this information is not in
the document, explain why the WG considers it unnecessary.

(16) Describe the Document Shepherd's review of the IANA considerations
section, especially with regard to its consistency with the body of the
document. Confirm that all protocol extensions that the document makes
are associated with the appropriate reservations in IANA registries.
Confirm that any referenced IANA registries have been clearly
identified. Confirm that newly created IANA registries include a
detailed specification of the initial contents for the registry, that
allocations procedures for future registrations are defined, and a
reasonable name for the new registry has been suggested (see RFC 5226).
List any new registries that require Expert Review for future
allocations. Provide any public guidance that the IESG would find
useful in selecting the IANA Experts for these new registries.

(17) Describe reviews and automated checks performed by the Document
Shepherd to validate sections of the document written in a formal
language, such as XML code, BNF rules, MIB definitions, etc.


From Basavaraj.Patil@nokia.com  Wed Feb 15 13:30:58 2012
Return-Path: <Basavaraj.Patil@nokia.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E47FF21F85A0 for <wgchairs@ietfa.amsl.com>; Wed, 15 Feb 2012 13:30:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.687
X-Spam-Level: 
X-Spam-Status: No, score=-102.687 tagged_above=-999 required=5 tests=[AWL=-0.088, 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 OAhOFGko+Ywt for <wgchairs@ietfa.amsl.com>; Wed, 15 Feb 2012 13:30:54 -0800 (PST)
Received: from mgw-sa01.nokia.com (smtp.nokia.com [147.243.1.47]) by ietfa.amsl.com (Postfix) with ESMTP id 8C49A21F8581 for <wgchairs@ietf.org>; Wed, 15 Feb 2012 13:30:54 -0800 (PST)
Received: from vaebh105.NOE.Nokia.com (in-mx.nokia.com [10.160.244.31]) by mgw-sa01.nokia.com (Switch-3.4.4/Switch-3.4.4) with ESMTP id q1FLUqoC002182; Wed, 15 Feb 2012 23:30:53 +0200
Received: from smtp.mgd.nokia.com ([65.54.30.24]) by vaebh105.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 15 Feb 2012 23:30:52 +0200
Received: from 008-AM1MPN1-073.mgdnok.nokia.com ([169.254.3.165]) by 008-AM1MMR1-008.mgdnok.nokia.com ([65.54.30.24]) with mapi id 14.01.0355.003; Wed, 15 Feb 2012 22:30:52 +0100
From: <Basavaraj.Patil@nokia.com>
To: <housley@vigilsec.com>, <wgchairs@ietf.org>
Subject: Re: DRAFT Revision to the WG Document Writeup
Thread-Topic: DRAFT Revision to the WG Document Writeup
Thread-Index: AQHM7CQosdAQ5UchMUyvsAblnbaIYpY+BI+A
Date: Wed, 15 Feb 2012 21:30:52 +0000
Message-ID: <CB617FC5.1ADD8%basavaraj.patil@nokia.com>
In-Reply-To: <365EF4B3-53D2-4AB8-BC8D-F0803F734E15@vigilsec.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.14.0.111121
x-originating-ip: [172.19.59.137]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <EA8535D3E63ECB489FD2020FEE4B2B9A@nokia.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 15 Feb 2012 21:30:52.0912 (UTC) FILETIME=[181AB700:01CCEC29]
X-Nokia-AV: Clean
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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, 15 Feb 2012 21:30:59 -0000

Item 3 of the writeup says: "If this version of the document is not ready
for publication, please explain why the document is being forwarded to
the IESG."

Is it really possible that a WG chair would be forwarding a document when
he/she is aware that it is not ready?

-Basavaraj

On 2/15/12 2:54 PM, "ext Russ Housley" <housley@vigilsec.com> wrote:

>I believe that I have addresses all comments, including the requests for
>a different style and ordering.
>
>Russ
>
>=3D =3D =3D =3D =3D =3D =3D =3D =3D
>
>Document Writeup
>
>As required by RFC 4858, this is the current template for the Document
>Shepherd Write-Up.
>
>Changes are expected over time. This DRAFT version is dated
>15 February 2012.
>
>(1) What type of RFC is being requested (BCP, Proposed Standard,
>Internet Standard, Informational, Experimental, or Historic)?
>
>(2) The IESG approval announcement includes a Document Announcement
>Write-Up. Please provide such a Document Announcement Write-Up. Recent
>examples can be found in the "Action" announcements for approved
>documents. The approval announcement contains the following sections:
>
>Technical Summary
>
>   Relevant content can frequently be found in the abstract
>   and/or introduction of the document. If not, this may be
>   an indication that there are deficiencies in the abstract
>   or introduction.
>
>Working Group Summary
>
>   Was there anything in WG process that is worth noting? For
>   example, was there controversy about particular points or
>   were there decisions where the consensus was particularly
>   rough?
>
>Document Quality
>
>   Are there existing implementations of the protocol? Have a
>   significant number of vendors indicated their plan to
>   implement the specification? Are there any reviewers that
>   merit special mention as having done a thorough review,
>   e.g., one that resulted in important changes or a
>   conclusion that the document had no substantive issues? If
>   there was a MIB Doctor, Media Type or other expert review,
>   what was its course (briefly)? In the case of a Media Type
>   review, on what date was the request posted?
>
> Personnel
>
>   Who is the Document Shepherd? Who is the Responsible Area
>   Director?
>
>(3) Briefly describe the review of this document that was performed by
>the Document Shepherd.  If this version of the document is not ready
>for publication, please explain why the document is being forwarded to
>the IESG.
>
>(4) Has the document had adequate review from WG participants? Does the
>document Shepherd have any concerns about the depth or breadth of the
>reviews that have been performed?
>
>(5) Do portions of the document need review from a particular or from
>broader perspective, e.g., security, operational complexity, AAA, DNS,
>DHCP, XML, or internationalization? If so, describe the review that
>took place.
>
>(6) Describe any specific concerns or issues that the Document Shepherd
>has with this document that the Responsible Area Director and/or the
>IESG should be aware of? For example, perhaps he or she is uncomfortable
>with certain parts of the document, or has concerns whether there really
>is a need for it. In any event, if the WG has discussed those issues and
>has indicated that it still wishes to advance the document, detail those
>concerns here.
>
>(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. If not, explain why.
>
>(8) Has an IPR disclosure been filed that references this document?
>If so, summarize any WG discussion and conclusion regarding the IPR
>disclosures.
>
>(9) How solid is the WG consensus behind this document? Does it
>represent the strong concurrence of a few individuals, with others
>being silent, or does the WG as a whole understand and agree with it?
>
>(10) Has anyone threatened an appeal or otherwise indicated extreme
>discontent? If so, please summarise the areas of conflict in separate
>email messages to the Responsible Area Director. (It should be in a
>separate email because this questionnaire is publicly available.)
>
>(11) Identify any ID nits the Document Shepherd has found in this
>document. (See http://www.ietf.org/tools/idnits/ and the Internet-Drafts
>Checklist). Boilerplate checks are not enough; this check needs to be
>thorough.
>
>(12) Describe how the document meets any required formal review
>criteria, such as the MIB Doctor, media type, and URI type reviews.
>
>(13) Have all references within this document been identified as
>either normative and informative? Are there normative references to
>documents that are not ready for advancement or are otherwise in an
>unclear state? If such normative references exist, what is the plan for
>their completion? Are there normative references that are downward
>references (see RFC 3967)? If so, list these downward references to
>support the Area Director in the Last Call procedure.
>
>(14) List other RFCs that this document obsoletes, and indicate whether
>the to-be-obsolete RFCs are listed in the title page header, in the
>Abstract, and in the Introduction. Which of these RFCs, if any, are to
>be moved to Historic? Is this change of status explicitly stated in the
>Introduction?
>
>(15) List other RFCs that this document updates, and indicate whether
>they appear in the title page header, in the Abstract, and in the
>Introduction. If the updated RFCs are not listed in the Abstract and
>Introduction, explain why, and point to part of the document that
>describes the nature of the updates. If this information is not in
>the document, explain why the WG considers it unnecessary.
>
>(16) Describe the Document Shepherd's review of the IANA considerations
>section, especially with regard to its consistency with the body of the
>document. Confirm that all protocol extensions that the document makes
>are associated with the appropriate reservations in IANA registries.
>Confirm that any referenced IANA registries have been clearly
>identified. Confirm that newly created IANA registries include a
>detailed specification of the initial contents for the registry, that
>allocations procedures for future registrations are defined, and a
>reasonable name for the new registry has been suggested (see RFC 5226).
>List any new registries that require Expert Review for future
>allocations. Provide any public guidance that the IESG would find
>useful in selecting the IANA Experts for these new registries.
>
>(17) Describe reviews and automated checks performed by the Document
>Shepherd to validate sections of the document written in a formal
>language, such as XML code, BNF rules, MIB definitions, etc.
>


From fred@cisco.com  Wed Feb 15 14:51:55 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 BB13F21E80CC for <wgchairs@ietfa.amsl.com>; Wed, 15 Feb 2012 14:51:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.531
X-Spam-Level: 
X-Spam-Status: No, score=-108.531 tagged_above=-999 required=5 tests=[AWL=2.068, 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 s9DNvr5y+reY for <wgchairs@ietfa.amsl.com>; Wed, 15 Feb 2012 14:51:51 -0800 (PST)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 1BE7121E80E3 for <wgchairs@ietf.org>; Wed, 15 Feb 2012 14:51:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=7516; q=dns/txt; s=iport; t=1329346311; x=1330555911; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=0AN1xHYaqs+osRZM/S/kbfMSoRyKnStu74PjU3qpsX8=; b=UZ4K/fewMCH7fdtgAWm+xCG94ot9mia/8ZwSGIUymgV4zpdiI0bY+wJF lJ/0kNPZfM65zo9SnMk03P3+evd8el4a8xE/qsw9+HwbAuDmR8LWwFPTj cxyp5WoGzhkkuV6o4KNMfxRIkp7sExnH0jxRgdjSZLCi2DQ9/OYO77oB6 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: As0GALs2PE+rRDoG/2dsb2JhbAA4CoMOrVeBB4FyAQEBAwESAScxDhALGC5XBhMJCw6HXQmbCgGeUYkWglMCBAMCBQ0CBAYFCwUGBgkMAgoCDQEKg08WCAoDBgIFAgEICQIFgkdjBIhNjGmFXY0r
X-IronPort-AV: E=Sophos;i="4.73,425,1325462400"; d="scan'208";a="30730092"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-3.cisco.com with ESMTP; 15 Feb 2012 22:51:50 +0000
Received: from [192.168.31.91] (sjc-vpn3-474.cisco.com [10.21.65.218]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id q1FMpn9R003059; Wed, 15 Feb 2012 22:51:49 GMT
Subject: Re: DRAFT Revision to the WG Document Writeup
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Fred Baker <fred@cisco.com>
In-Reply-To: <CB617FC5.1ADD8%basavaraj.patil@nokia.com>
Date: Wed, 15 Feb 2012 15:51:49 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <5EF2C195-825E-4028-8445-9F556D912F72@cisco.com>
References: <CB617FC5.1ADD8%basavaraj.patil@nokia.com>
To: "<Basavaraj.Patil@nokia.com>" <Basavaraj.Patil@nokia.com>
X-Mailer: Apple Mail (2.1084)
Cc: wgchairs@ietf.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: Wed, 15 Feb 2012 22:51:56 -0000

On Feb 15, 2012, at 2:30 PM, <Basavaraj.Patil@nokia.com> =
<Basavaraj.Patil@nokia.com> wrote:

>=20
> Item 3 of the writeup says: "If this version of the document is not =
ready
> for publication, please explain why the document is being forwarded to
> the IESG."
>=20
> Is it really possible that a WG chair would be forwarding a document =
when
> he/she is aware that it is not ready?

I think the objective is to (a) make the IESG and community review =
easier and (b) give the WG Chair an objective measure of readiness.=20

> -Basavaraj
>=20
> On 2/15/12 2:54 PM, "ext Russ Housley" <housley@vigilsec.com> wrote:
>=20
>> I believe that I have addresses all comments, including the requests =
for
>> a different style and ordering.
>>=20
>> Russ
>>=20
>> =3D =3D =3D =3D =3D =3D =3D =3D =3D
>>=20
>> Document Writeup
>>=20
>> As required by RFC 4858, this is the current template for the =
Document
>> Shepherd Write-Up.
>>=20
>> Changes are expected over time. This DRAFT version is dated
>> 15 February 2012.
>>=20
>> (1) What type of RFC is being requested (BCP, Proposed Standard,
>> Internet Standard, Informational, Experimental, or Historic)?
>>=20
>> (2) The IESG approval announcement includes a Document Announcement
>> Write-Up. Please provide such a Document Announcement Write-Up. =
Recent
>> examples can be found in the "Action" announcements for approved
>> documents. The approval announcement contains the following sections:
>>=20
>> Technical Summary
>>=20
>>  Relevant content can frequently be found in the abstract
>>  and/or introduction of the document. If not, this may be
>>  an indication that there are deficiencies in the abstract
>>  or introduction.
>>=20
>> Working Group Summary
>>=20
>>  Was there anything in WG process that is worth noting? For
>>  example, was there controversy about particular points or
>>  were there decisions where the consensus was particularly
>>  rough?
>>=20
>> Document Quality
>>=20
>>  Are there existing implementations of the protocol? Have a
>>  significant number of vendors indicated their plan to
>>  implement the specification? Are there any reviewers that
>>  merit special mention as having done a thorough review,
>>  e.g., one that resulted in important changes or a
>>  conclusion that the document had no substantive issues? If
>>  there was a MIB Doctor, Media Type or other expert review,
>>  what was its course (briefly)? In the case of a Media Type
>>  review, on what date was the request posted?
>>=20
>> Personnel
>>=20
>>  Who is the Document Shepherd? Who is the Responsible Area
>>  Director?
>>=20
>> (3) Briefly describe the review of this document that was performed =
by
>> the Document Shepherd.  If this version of the document is not ready
>> for publication, please explain why the document is being forwarded =
to
>> the IESG.
>>=20
>> (4) Has the document had adequate review from WG participants? Does =
the
>> document Shepherd have any concerns about the depth or breadth of the
>> reviews that have been performed?
>>=20
>> (5) Do portions of the document need review from a particular or from
>> broader perspective, e.g., security, operational complexity, AAA, =
DNS,
>> DHCP, XML, or internationalization? If so, describe the review that
>> took place.
>>=20
>> (6) Describe any specific concerns or issues that the Document =
Shepherd
>> has with this document that the Responsible Area Director and/or the
>> IESG should be aware of? For example, perhaps he or she is =
uncomfortable
>> with certain parts of the document, or has concerns whether there =
really
>> is a need for it. In any event, if the WG has discussed those issues =
and
>> has indicated that it still wishes to advance the document, detail =
those
>> concerns here.
>>=20
>> (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. If not, explain why.
>>=20
>> (8) Has an IPR disclosure been filed that references this document?
>> If so, summarize any WG discussion and conclusion regarding the IPR
>> disclosures.
>>=20
>> (9) How solid is the WG consensus behind this document? Does it
>> represent the strong concurrence of a few individuals, with others
>> being silent, or does the WG as a whole understand and agree with it?
>>=20
>> (10) Has anyone threatened an appeal or otherwise indicated extreme
>> discontent? If so, please summarise the areas of conflict in separate
>> email messages to the Responsible Area Director. (It should be in a
>> separate email because this questionnaire is publicly available.)
>>=20
>> (11) Identify any ID nits the Document Shepherd has found in this
>> document. (See http://www.ietf.org/tools/idnits/ and the =
Internet-Drafts
>> Checklist). Boilerplate checks are not enough; this check needs to be
>> thorough.
>>=20
>> (12) Describe how the document meets any required formal review
>> criteria, such as the MIB Doctor, media type, and URI type reviews.
>>=20
>> (13) Have all references within this document been identified as
>> either normative and informative? Are there normative references to
>> documents that are not ready for advancement or are otherwise in an
>> unclear state? If such normative references exist, what is the plan =
for
>> their completion? Are there normative references that are downward
>> references (see RFC 3967)? If so, list these downward references to
>> support the Area Director in the Last Call procedure.
>>=20
>> (14) List other RFCs that this document obsoletes, and indicate =
whether
>> the to-be-obsolete RFCs are listed in the title page header, in the
>> Abstract, and in the Introduction. Which of these RFCs, if any, are =
to
>> be moved to Historic? Is this change of status explicitly stated in =
the
>> Introduction?
>>=20
>> (15) List other RFCs that this document updates, and indicate whether
>> they appear in the title page header, in the Abstract, and in the
>> Introduction. If the updated RFCs are not listed in the Abstract and
>> Introduction, explain why, and point to part of the document that
>> describes the nature of the updates. If this information is not in
>> the document, explain why the WG considers it unnecessary.
>>=20
>> (16) Describe the Document Shepherd's review of the IANA =
considerations
>> section, especially with regard to its consistency with the body of =
the
>> document. Confirm that all protocol extensions that the document =
makes
>> are associated with the appropriate reservations in IANA registries.
>> Confirm that any referenced IANA registries have been clearly
>> identified. Confirm that newly created IANA registries include a
>> detailed specification of the initial contents for the registry, that
>> allocations procedures for future registrations are defined, and a
>> reasonable name for the new registry has been suggested (see RFC =
5226).
>> List any new registries that require Expert Review for future
>> allocations. Provide any public guidance that the IESG would find
>> useful in selecting the IANA Experts for these new registries.
>>=20
>> (17) Describe reviews and automated checks performed by the Document
>> Shepherd to validate sections of the document written in a formal
>> language, such as XML code, BNF rules, MIB definitions, etc.
>>=20
>=20


From touch@isi.edu  Wed Feb 15 14:55:50 2012
Return-Path: <touch@isi.edu>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4034C21E8032 for <wgchairs@ietfa.amsl.com>; Wed, 15 Feb 2012 14:55:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.007
X-Spam-Level: 
X-Spam-Status: No, score=-103.007 tagged_above=-999 required=5 tests=[AWL=-0.408, 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 p+a-UgMnKnM7 for <wgchairs@ietfa.amsl.com>; Wed, 15 Feb 2012 14:55:46 -0800 (PST)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 3AEB121E80B9 for <wgchairs@ietf.org>; Wed, 15 Feb 2012 14:55:46 -0800 (PST)
Received: from [128.9.160.252] (pen.isi.edu [128.9.160.252]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id q1FMspUw012606 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 15 Feb 2012 14:54:56 -0800 (PST)
Message-ID: <4F3C37BB.5000401@isi.edu>
Date: Wed, 15 Feb 2012 14:54:51 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
Subject: Re: DRAFT Revision to the WG Document Writeup
References: <CB617FC5.1ADD8%basavaraj.patil@nokia.com> <5EF2C195-825E-4028-8445-9F556D912F72@cisco.com>
In-Reply-To: <5EF2C195-825E-4028-8445-9F556D912F72@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: wgchairs@ietf.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: Wed, 15 Feb 2012 22:55:50 -0000

FWIW, there are cases where the WG chair doesn't think a doc is ready 
but the authors insist otherwise; that's still a legitimate case where 
the WG chair's perspective can be given and the IESG involved to resolve 
the issue.

Joe

On 2/15/2012 2:51 PM, Fred Baker wrote:
>
> On Feb 15, 2012, at 2:30 PM,<Basavaraj.Patil@nokia.com>  <Basavaraj.Patil@nokia.com>  wrote:
>
>>
>> Item 3 of the writeup says: "If this version of the document is not ready
>> for publication, please explain why the document is being forwarded to
>> the IESG."
>>
>> Is it really possible that a WG chair would be forwarding a document when
>> he/she is aware that it is not ready?
>
> I think the objective is to (a) make the IESG and community review easier and (b) give the WG Chair an objective measure of readiness.
>
>> -Basavaraj
>>
>> On 2/15/12 2:54 PM, "ext Russ Housley"<housley@vigilsec.com>  wrote:
>>
>>> I believe that I have addresses all comments, including the requests for
>>> a different style and ordering.
>>>
>>> Russ
>>>
>>> = = = = = = = = =
>>>
>>> Document Writeup
>>>
>>> As required by RFC 4858, this is the current template for the Document
>>> Shepherd Write-Up.
>>>
>>> Changes are expected over time. This DRAFT version is dated
>>> 15 February 2012.
>>>
>>> (1) What type of RFC is being requested (BCP, Proposed Standard,
>>> Internet Standard, Informational, Experimental, or Historic)?
>>>
>>> (2) The IESG approval announcement includes a Document Announcement
>>> Write-Up. Please provide such a Document Announcement Write-Up. Recent
>>> examples can be found in the "Action" announcements for approved
>>> documents. The approval announcement contains the following sections:
>>>
>>> Technical Summary
>>>
>>>   Relevant content can frequently be found in the abstract
>>>   and/or introduction of the document. If not, this may be
>>>   an indication that there are deficiencies in the abstract
>>>   or introduction.
>>>
>>> Working Group Summary
>>>
>>>   Was there anything in WG process that is worth noting? For
>>>   example, was there controversy about particular points or
>>>   were there decisions where the consensus was particularly
>>>   rough?
>>>
>>> Document Quality
>>>
>>>   Are there existing implementations of the protocol? Have a
>>>   significant number of vendors indicated their plan to
>>>   implement the specification? Are there any reviewers that
>>>   merit special mention as having done a thorough review,
>>>   e.g., one that resulted in important changes or a
>>>   conclusion that the document had no substantive issues? If
>>>   there was a MIB Doctor, Media Type or other expert review,
>>>   what was its course (briefly)? In the case of a Media Type
>>>   review, on what date was the request posted?
>>>
>>> Personnel
>>>
>>>   Who is the Document Shepherd? Who is the Responsible Area
>>>   Director?
>>>
>>> (3) Briefly describe the review of this document that was performed by
>>> the Document Shepherd.  If this version of the document is not ready
>>> for publication, please explain why the document is being forwarded to
>>> the IESG.
>>>
>>> (4) Has the document had adequate review from WG participants? Does the
>>> document Shepherd have any concerns about the depth or breadth of the
>>> reviews that have been performed?
>>>
>>> (5) Do portions of the document need review from a particular or from
>>> broader perspective, e.g., security, operational complexity, AAA, DNS,
>>> DHCP, XML, or internationalization? If so, describe the review that
>>> took place.
>>>
>>> (6) Describe any specific concerns or issues that the Document Shepherd
>>> has with this document that the Responsible Area Director and/or the
>>> IESG should be aware of? For example, perhaps he or she is uncomfortable
>>> with certain parts of the document, or has concerns whether there really
>>> is a need for it. In any event, if the WG has discussed those issues and
>>> has indicated that it still wishes to advance the document, detail those
>>> concerns here.
>>>
>>> (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. If not, explain why.
>>>
>>> (8) Has an IPR disclosure been filed that references this document?
>>> If so, summarize any WG discussion and conclusion regarding the IPR
>>> disclosures.
>>>
>>> (9) How solid is the WG consensus behind this document? Does it
>>> represent the strong concurrence of a few individuals, with others
>>> being silent, or does the WG as a whole understand and agree with it?
>>>
>>> (10) Has anyone threatened an appeal or otherwise indicated extreme
>>> discontent? If so, please summarise the areas of conflict in separate
>>> email messages to the Responsible Area Director. (It should be in a
>>> separate email because this questionnaire is publicly available.)
>>>
>>> (11) Identify any ID nits the Document Shepherd has found in this
>>> document. (See http://www.ietf.org/tools/idnits/ and the Internet-Drafts
>>> Checklist). Boilerplate checks are not enough; this check needs to be
>>> thorough.
>>>
>>> (12) Describe how the document meets any required formal review
>>> criteria, such as the MIB Doctor, media type, and URI type reviews.
>>>
>>> (13) Have all references within this document been identified as
>>> either normative and informative? Are there normative references to
>>> documents that are not ready for advancement or are otherwise in an
>>> unclear state? If such normative references exist, what is the plan for
>>> their completion? Are there normative references that are downward
>>> references (see RFC 3967)? If so, list these downward references to
>>> support the Area Director in the Last Call procedure.
>>>
>>> (14) List other RFCs that this document obsoletes, and indicate whether
>>> the to-be-obsolete RFCs are listed in the title page header, in the
>>> Abstract, and in the Introduction. Which of these RFCs, if any, are to
>>> be moved to Historic? Is this change of status explicitly stated in the
>>> Introduction?
>>>
>>> (15) List other RFCs that this document updates, and indicate whether
>>> they appear in the title page header, in the Abstract, and in the
>>> Introduction. If the updated RFCs are not listed in the Abstract and
>>> Introduction, explain why, and point to part of the document that
>>> describes the nature of the updates. If this information is not in
>>> the document, explain why the WG considers it unnecessary.
>>>
>>> (16) Describe the Document Shepherd's review of the IANA considerations
>>> section, especially with regard to its consistency with the body of the
>>> document. Confirm that all protocol extensions that the document makes
>>> are associated with the appropriate reservations in IANA registries.
>>> Confirm that any referenced IANA registries have been clearly
>>> identified. Confirm that newly created IANA registries include a
>>> detailed specification of the initial contents for the registry, that
>>> allocations procedures for future registrations are defined, and a
>>> reasonable name for the new registry has been suggested (see RFC 5226).
>>> List any new registries that require Expert Review for future
>>> allocations. Provide any public guidance that the IESG would find
>>> useful in selecting the IANA Experts for these new registries.
>>>
>>> (17) Describe reviews and automated checks performed by the Document
>>> Shepherd to validate sections of the document written in a formal
>>> language, such as XML code, BNF rules, MIB definitions, etc.
>>>
>>
>

From ogud@ogud.com  Thu Feb 16 07:05:18 2012
Return-Path: <ogud@ogud.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA78421F87BA for <wgchairs@ietfa.amsl.com>; Thu, 16 Feb 2012 07:05:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.503
X-Spam-Level: 
X-Spam-Status: No, score=-106.503 tagged_above=-999 required=5 tests=[AWL=0.096, 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 LK7Rc2s7IhDj for <wgchairs@ietfa.amsl.com>; Thu, 16 Feb 2012 07:05:17 -0800 (PST)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by ietfa.amsl.com (Postfix) with ESMTP id 56CC621F87B9 for <wgchairs@ietf.org>; Thu, 16 Feb 2012 07:05:17 -0800 (PST)
Received: from [IPv6:::1] (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.4/8.14.4) with ESMTP id q1GF5GKB042398 for <wgchairs@ietf.org>; Thu, 16 Feb 2012 10:05:16 -0500 (EST) (envelope-from ogud@ogud.com)
Message-ID: <4F3D1B2A.7050601@ogud.com>
Date: Thu, 16 Feb 2012 10:05:14 -0500
From: Olafur Gudmundsson <ogud@ogud.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: DRAFT Revision to the WG Document Writeup
References: <AE35FF1F-47D2-4AB3-B074-6CCBA5B6AC25@vigilsec.com> <201110271852.p9RIqcOO025921@mtv-core-3.cisco.com> <FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CA9E@MX14A.corp.emc.com> <23B2E96E-08CE-40D1-8038-89A7A672E9F5@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CAE1@MX14A.corp.emc.com> <7D5B9928-1D93-43DC-A50C-E74BF81E53F3@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD33AA9D@MX14A.corp.emc.com> <365EF4B3-53D2-4AB8-BC8D-F0803F734E15@vigilsec.com>
In-Reply-To: <365EF4B3-53D2-4AB8-BC8D-F0803F734E15@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.72 on 10.20.30.4
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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, 16 Feb 2012 15:05:18 -0000

On 15/02/2012 15:54, Russ Housley wrote:
> I believe that I have addresses all comments, including the requests for a different style and ordering.
>

Thanks Russ,
this looks good (much better than current template).
I really like item (1) to be there not having the intended status in the 
writeup lead to errors and problems:

Do you want to tell the DS to check the document header is in compliance 
with the request?
Current:
(1) What type of RFC is being requested (BCP, Proposed Standard,
Internet Standard, Informational, Experimental, or Historic)?

Proposal:
(1) What type of RFC is being requested (BCP, Proposed Standard,
Internet Standard, Informational, Experimental, or Historic)?
Does the header in the draft state this ?

	Olafur

From brian@innovationslab.net  Thu Feb 16 08:46:07 2012
Return-Path: <brian@innovationslab.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 8A83221F8827 for <wgchairs@ietfa.amsl.com>; Thu, 16 Feb 2012 08:46:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.703
X-Spam-Level: 
X-Spam-Status: No, score=-102.703 tagged_above=-999 required=5 tests=[AWL=-0.104, 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 j95YE7Yi4u-9 for <wgchairs@ietfa.amsl.com>; Thu, 16 Feb 2012 08:46:06 -0800 (PST)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id B5FE121F8826 for <wgchairs@ietf.org>; Thu, 16 Feb 2012 08:46:01 -0800 (PST)
Received: from clairseach.fuaim.com (clairseach.fuaim.com [206.197.161.141]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 88B2688216 for <wgchairs@ietf.org>; Thu, 16 Feb 2012 08:46:01 -0800 (PST)
Received: from clemson.local (unknown [128.220.159.20]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 4CF6013680D8 for <wgchairs@ietf.org>; Thu, 16 Feb 2012 08:46:01 -0800 (PST)
Message-ID: <4F3D32CA.9090602@innovationslab.net>
Date: Thu, 16 Feb 2012 11:46:02 -0500
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: DRAFT Revision to the WG Document Writeup
References: <AE35FF1F-47D2-4AB3-B074-6CCBA5B6AC25@vigilsec.com> <201110271852.p9RIqcOO025921@mtv-core-3.cisco.com> <FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CA9E@MX14A.corp.emc.com> <23B2E96E-08CE-40D1-8038-89A7A672E9F5@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CAE1@MX14A.corp.emc.com> <7D5B9928-1D93-43DC-A50C-E74BF81E53F3@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD33AA9D@MX14A.corp.emc.com> <365EF4B3-53D2-4AB8-BC8D-F0803F734E15@vigilsec.com> <4F3D1B2A.7050601@ogud.com>
In-Reply-To: <4F3D1B2A.7050601@ogud.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: Thu, 16 Feb 2012 16:46:07 -0000

Olafur,
      This is a good point for me to inject a comment...

On 2/16/12 10:05 AM, Olafur Gudmundsson wrote:
> On 15/02/2012 15:54, Russ Housley wrote:
>> I believe that I have addresses all comments, including the requests
>> for a different style and ordering.
>>
>
> Thanks Russ,
> this looks good (much better than current template).
> I really like item (1) to be there not having the intended status in the
> writeup lead to errors and problems:
>
> Do you want to tell the DS to check the document header is in compliance
> with the request?
> Current:
> (1) What type of RFC is being requested (BCP, Proposed Standard,
> Internet Standard, Informational, Experimental, or Historic)?
>
> Proposal:
> (1) What type of RFC is being requested (BCP, Proposed Standard,
> Internet Standard, Informational, Experimental, or Historic)?
> Does the header in the draft state this ?

These types of checks can be automated and would be easy to accomplish 
if the DS writeup was an on-line form that the chair must fill out when 
requesting advancement.  Conceptually, the form would look much like the 
draft submission form in use today.

Can we get such a functionality added as a To Do?

Regards,
Brian


From sob@sobco.com  Wed Feb 15 15:28:03 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 17F4021E8085 for <wgchairs@ietfa.amsl.com>; Wed, 15 Feb 2012 15:28:03 -0800 (PST)
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 Z+eA5DfLyImX for <wgchairs@ietfa.amsl.com>; Wed, 15 Feb 2012 15:28:02 -0800 (PST)
Received: from sobco.sobco.com (unknown [136.248.127.164]) by ietfa.amsl.com (Postfix) with ESMTP id 13EC721E8084 for <wgchairs@ietf.org>; Wed, 15 Feb 2012 15:28:01 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id 666D925A7E90; Wed, 15 Feb 2012 18:28:00 -0500 (EST)
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 h9q1lBEn-Wdv; Wed, 15 Feb 2012 18:27:59 -0500 (EST)
Received: from [10.0.1.3] (unknown [173.166.5.69]) by sobco.sobco.com (Postfix) with ESMTPSA id 21A9525A7E85; Wed, 15 Feb 2012 18:27:59 -0500 (EST)
Subject: Re: DRAFT Revision to the WG Document Writeup (about IPR)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=windows-1252
From: "Scott O. Bradner" <sob@sobco.com>
In-Reply-To: <FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com>
Date: Wed, 15 Feb 2012 18:27:52 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <0796D4BA-04C0-4061-ADD4-8BA84865C2F5@sobco.com>
References: <AE35FF1F-47D2-4AB3-B074-6CCBA5B6AC25@vigilsec.com> <201110271852.p9RIqcOO025921@mtv-core-3.cisco.com> <FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.1257)
X-Mailman-Approved-At: Thu, 16 Feb 2012 09:48:49 -0800
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, 15 Feb 2012 23:28:03 -0000

On Feb 9, 2012, at 9:01 PM, Russ Housley wrote:

> It has taken me a very long time to incorporate all of the comments =
into a revised draft of the WG Document Writeup.  Here is the revision.  =
Please review and comment.
>=20
> Russ
>=20
=85

to me, the goal should be having this as a web page to be filled in - =
that puts constraints on how many questions
you can ask at once=20


>=20
>  (2) Has the document had adequate review both from WG participants?=20=

>      Does the Document Shepherd have any concerns about the depth or
>      breadth of the reviews that have been performed? =20

the two sentences above seem redundant

> (10) Have all references within this been document been identified
>      as either normative and informative? Are there normative
>      references to documents that are not ready for advancement or
>      are otherwise in an unclear state? If such normative references
>      exist, what is the plan for their completion? Are there normative
>      references that are downward references (see [RFC3967])? If so,
>      list these downward references to support the Area Director in
>      the Last Call procedure.=20

multiple questions in a question - maybe ask if the references are =
properly segmented=20
and explain any possibly blocking or downward  references - (a series of =
questions within a single=20
one is a pain if each has to be answered - that is one of the big pains =
of the current version and
stands in the way of making this a web page to be filled in

>=20
> (11) List other RFCs that this document obsoletes, and indicate =
whether=20
>      the to-be-obsolete RFCs are listed in both the title page header
>      as well as in the Abstract and Introduction. Which if these RFCs,
>      if any, are to be moved to Historic? Is this change of status
>      explicitly stated in the document Introduction.

> (12) List other RFCs that this document updates, and indicate whether
>      they appear in both the title page header as well as in the
>      Abstract and Introduction.

for 11 & 13 why not  just ask if any changes to the status of existing =
RFCs (e.g. obsoleting, moving to historic, etc.) are
listsed on the title page header, abstract & introduction?

>=20
> (13) Describe the Document Shepherd's review of the IANA =
considerations
>      section, especially with regard to its consistency with the body
>      of the document. Confirm that all protocol extensions that the
>      document makes are associated with the appropriate reservations
>      in IANA registries. Confirm that any referenced IANA registries
>      have been clearly identified. Confirm that newly created IANA
>      registries include a detailed specification of the initial
>      contents for the registry, that allocations procedures for
>      future registrations are defined, and a reasonable name for the
>      new registry has been suggested (see [RFC5226]). List any IANA=20
>      Experts that the IESG will need to appoint during IESG Evaluation
>      for any new registries that require Expert Review for future
>      allocations.

see above - lots of questions in a pile

>=20
> (14) The IESG approval announcement includes a Document Announcement
>      Write-Up. Please provide such a Document Announcement Write-Up.
>      Recent examples can be found in the "Action" announcements for
>      approved documents. The approval announcement contains the
>      following sections:
>=20
>      Technical Summary
>=20
>        Relevant content can frequently be found in the abstract=20
>        and/or introduction of the document. If not, this may be=20
>        an indication that there are deficiencies in the abstract=20
>        or introduction.
>=20
>      Working Group Summary
>=20
>        Was there anything in WG process that is worth noting? For=20
>        example, was there controversy about particular points or=20
>        were there decisions where the consensus was particularly=20
>        rough?
>=20
>      Document Quality
>=20
>        Are there existing implementations of the protocol? Have a=20
>        significant number of vendors indicated their plan to=20
>        implement the specification? Are there any reviewers that=20
>        merit special mention as having done a thorough review,=20
>        e.g., one that resulted in important changes or a=20
>        conclusion that the document had no substantive issues? If=20
>        there was a MIB Doctor, Media Type or other expert review,=20
>        what was its course (briefly)? In the case of a Media Type=20
>        review, on what date was the request posted?
>=20
>      Personnel
>=20
>        Who is the Document Shepherd? Who is the Responsible Area
>        Director.
>=20


From keith.drage@alcatel-lucent.com  Thu Feb 16 15:19:10 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 E1A8021F8803 for <wgchairs@ietfa.amsl.com>; Thu, 16 Feb 2012 15:19:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.216
X-Spam-Level: 
X-Spam-Status: No, score=-107.216 tagged_above=-999 required=5 tests=[AWL=-0.967, BAYES_00=-2.599, HELO_EQ_FR=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 GUdT6FRLDG4H for <wgchairs@ietfa.amsl.com>; Thu, 16 Feb 2012 15:19:07 -0800 (PST)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [62.23.212.57]) by ietfa.amsl.com (Postfix) with ESMTP id 4FE6821F8807 for <wgchairs@ietf.org>; Thu, 16 Feb 2012 15:19:06 -0800 (PST)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q1GNJ3ua010943 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 17 Feb 2012 00:19:04 +0100
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.46]) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com ([135.120.45.63]) with mapi; Fri, 17 Feb 2012 00:19:03 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Russ Housley <housley@vigilsec.com>, IETF WG Chairs <wgchairs@ietf.org>
Date: Fri, 17 Feb 2012 00:19:02 +0100
Subject: RE: DRAFT Revision to the WG Document Writeup
Thread-Topic: DRAFT Revision to the WG Document Writeup
Thread-Index: AczsJAyIarRsSVZfS528q7s84+LQ5gAxcgIA
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE224A6C4A8@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <AE35FF1F-47D2-4AB3-B074-6CCBA5B6AC25@vigilsec.com> <201110271852.p9RIqcOO025921@mtv-core-3.cisco.com> <FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CA9E@MX14A.corp.emc.com> <23B2E96E-08CE-40D1-8038-89A7A672E9F5@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CAE1@MX14A.corp.emc.com> <7D5B9928-1D93-43DC-A50C-E74BF81E53F3@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD33AA9D@MX14A.corp.emc.com> <365EF4B3-53D2-4AB8-BC8D-F0803F734E15@vigilsec.com>
In-Reply-To: <365EF4B3-53D2-4AB8-BC8D-F0803F734E15@vigilsec.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.80
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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, 16 Feb 2012 23:19:11 -0000

Assuming question 1 is the response to my comment, I did expect something a=
 bit more penetrating to ensure the right decision had been made. Perhaps..=
.

> (1) What type of RFC is being requested (BCP, Proposed Standard,
> Internet Standard, Informational, Experimental, or Historic)? Please iden=
tify why you consider this is the correct type of RFC.

Where the answer is not "This is the type of RFC identified when the milest=
one was set".

Typical answers might be:

Proposed standard: It defines a protocol where meeting the normative requir=
ements defines conformance to the protocol.

Informational: It defines new values for the protocol where IANA registrati=
on requires only a informational RFC.

Regards

Keith


> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
> Behalf Of Russ Housley
> Sent: 15 February 2012 20:54
> To: IETF WG Chairs
> Subject: Re: DRAFT Revision to the WG Document Writeup
>=20
> I believe that I have addresses all comments, including the requests for =
a
> different style and ordering.
>=20
> Russ
>=20
> =3D =3D =3D =3D =3D =3D =3D =3D =3D
>=20
> Document Writeup
>=20
> As required by RFC 4858, this is the current template for the Document
> Shepherd Write-Up.
>=20
> Changes are expected over time. This DRAFT version is dated
> 15 February 2012.
>=20
> (1) What type of RFC is being requested (BCP, Proposed Standard,
> Internet Standard, Informational, Experimental, or Historic)?
>=20
> (2) The IESG approval announcement includes a Document Announcement
> Write-Up. Please provide such a Document Announcement Write-Up. Recent
> examples can be found in the "Action" announcements for approved
> documents. The approval announcement contains the following sections:
>=20
> Technical Summary
>=20
>    Relevant content can frequently be found in the abstract
>    and/or introduction of the document. If not, this may be
>    an indication that there are deficiencies in the abstract
>    or introduction.
>=20
> Working Group Summary
>=20
>    Was there anything in WG process that is worth noting? For
>    example, was there controversy about particular points or
>    were there decisions where the consensus was particularly
>    rough?
>=20
> Document Quality
>=20
>    Are there existing implementations of the protocol? Have a
>    significant number of vendors indicated their plan to
>    implement the specification? Are there any reviewers that
>    merit special mention as having done a thorough review,
>    e.g., one that resulted in important changes or a
>    conclusion that the document had no substantive issues? If
>    there was a MIB Doctor, Media Type or other expert review,
>    what was its course (briefly)? In the case of a Media Type
>    review, on what date was the request posted?
>=20
>  Personnel
>=20
>    Who is the Document Shepherd? Who is the Responsible Area
>    Director?
>=20
> (3) Briefly describe the review of this document that was performed by
> the Document Shepherd.  If this version of the document is not ready
> for publication, please explain why the document is being forwarded to
> the IESG.
>=20
> (4) Has the document had adequate review from WG participants? Does the
> document Shepherd have any concerns about the depth or breadth of the
> reviews that have been performed?
>=20
> (5) Do portions of the document need review from a particular or from
> broader perspective, e.g., security, operational complexity, AAA, DNS,
> DHCP, XML, or internationalization? If so, describe the review that
> took place.
>=20
> (6) Describe any specific concerns or issues that the Document Shepherd
> has with this document that the Responsible Area Director and/or the
> IESG should be aware of? For example, perhaps he or she is uncomfortable
> with certain parts of the document, or has concerns whether there really
> is a need for it. In any event, if the WG has discussed those issues and
> has indicated that it still wishes to advance the document, detail those
> concerns here.
>=20
> (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. If not, explain why.
>=20
> (8) Has an IPR disclosure been filed that references this document?
> If so, summarize any WG discussion and conclusion regarding the IPR
> disclosures.
>=20
> (9) How solid is the WG consensus behind this document? Does it
> represent the strong concurrence of a few individuals, with others
> being silent, or does the WG as a whole understand and agree with it?
>=20
> (10) Has anyone threatened an appeal or otherwise indicated extreme
> discontent? If so, please summarise the areas of conflict in separate
> email messages to the Responsible Area Director. (It should be in a
> separate email because this questionnaire is publicly available.)
>=20
> (11) Identify any ID nits the Document Shepherd has found in this
> document. (See http://www.ietf.org/tools/idnits/ and the Internet-Drafts
> Checklist). Boilerplate checks are not enough; this check needs to be
> thorough.
>=20
> (12) Describe how the document meets any required formal review
> criteria, such as the MIB Doctor, media type, and URI type reviews.
>=20
> (13) Have all references within this document been identified as
> either normative and informative? Are there normative references to
> documents that are not ready for advancement or are otherwise in an
> unclear state? If such normative references exist, what is the plan for
> their completion? Are there normative references that are downward
> references (see RFC 3967)? If so, list these downward references to
> support the Area Director in the Last Call procedure.
>=20
> (14) List other RFCs that this document obsoletes, and indicate whether
> the to-be-obsolete RFCs are listed in the title page header, in the
> Abstract, and in the Introduction. Which of these RFCs, if any, are to
> be moved to Historic? Is this change of status explicitly stated in the
> Introduction?
>=20
> (15) List other RFCs that this document updates, and indicate whether
> they appear in the title page header, in the Abstract, and in the
> Introduction. If the updated RFCs are not listed in the Abstract and
> Introduction, explain why, and point to part of the document that
> describes the nature of the updates. If this information is not in
> the document, explain why the WG considers it unnecessary.
>=20
> (16) Describe the Document Shepherd's review of the IANA considerations
> section, especially with regard to its consistency with the body of the
> document. Confirm that all protocol extensions that the document makes
> are associated with the appropriate reservations in IANA registries.
> Confirm that any referenced IANA registries have been clearly
> identified. Confirm that newly created IANA registries include a
> detailed specification of the initial contents for the registry, that
> allocations procedures for future registrations are defined, and a
> reasonable name for the new registry has been suggested (see RFC 5226).
> List any new registries that require Expert Review for future
> allocations. Provide any public guidance that the IESG would find
> useful in selecting the IANA Experts for these new registries.
>=20
> (17) Describe reviews and automated checks performed by the Document
> Shepherd to validate sections of the document written in a formal
> language, such as XML code, BNF rules, MIB definitions, etc.


From chair@ietf.org  Tue Feb 21 08:54:21 2012
Return-Path: <chair@ietf.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E116D21F87E4; Tue, 21 Feb 2012 08:54:21 -0800 (PST)
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 DFWh5Jts01e5; Tue, 21 Feb 2012 08:54:18 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 514E621F8747; Tue, 21 Feb 2012 08:54:18 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 0A6AF12CA16; Tue, 21 Feb 2012 08:54:17 -0800 (PST)
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 nO1YANFuCyJu; Tue, 21 Feb 2012 08:54:16 -0800 (PST)
Received: from [192.168.2.104] (pool-96-241-165-215.washdc.fios.verizon.net [96.241.165.215]) by c8a.amsl.com (Postfix) with ESMTPSA id 8E45912CA10; Tue, 21 Feb 2012 08:54:16 -0800 (PST)
Subject: Re: Major upgrade to the IETF Datatracker
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: IETF Chair <chair@ietf.org>
In-Reply-To: <E50AF16F-60A4-48AC-9B39-ED8E3560FB24@ietf.org>
Date: Tue, 21 Feb 2012 11:54:16 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <D9CA27E5-20A4-47EA-8EF5-74F07AF9B82E@ietf.org>
References: <E50AF16F-60A4-48AC-9B39-ED8E3560FB24@ietf.org>
To: IETF Announce <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1084)
Cc: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2012 16:54:22 -0000

Thank you for testing the new Datatracker.  You have uncovered several =
bugs, and they have all been fixed.

We still want to achieve a nearly unnoticeable change-over, so please =
make sure the Datatracker fully supports the way that you use the =
current Datatracker.  Unless a significant bug is discovered in the next =
few days, we plan to transition to the new database schema this coming =
weekend.

Thanks, again,
Russ


On Feb 14, 2012, at 2:36 PM, IETF Chair wrote:
>=20
> Shortly, the IETF datatracker will go through a major change, one of =
the two largest since it was first deployed more than 10 years ago.  =
Hopefully no one will notice.
>=20
> The previous major change was in 2007, when we switched the public =
Datatracker from Perl cgi-bin scripts to a much more modern and safe =
implementation based on the Django web application framework.  Very few =
people noticed that change at the time.
>=20
> In a few days, we will transition to completely redesigned Datatracker =
database schema.  The new schema will better support today's needs, and =
we believe it will better support future enhancements.  Frankly, we =
outgrew the old schema some time ago.
>=20
> In order to achieve a nearly unnoticeable change-over, we now invite =
you to try out the new Datatracker, bang on it, kick the tires, and =
generally see if it works as well for you as the old one.
>=20
> For some additional insight, you may want to read the instructions =
that was given to our testers:
> http://trac.tools.ietf.org/tools/ietfdb/wiki/InstructionsForTesters
>=20
> Or, you may want to just jump in and see how it works.  Either way, =
please report any bugs, problems, surprises, gremlins, hiccups, flaws, =
and so on that you discover.  Reports will receive prompt attention.  We =
deploy new code upgrades (if any are available) every hour. Please use =
this mail list to report issues:
> iola-conversion-tool@ietf.org
>=20
> Try out the new Datatracker, and help us make a smooth transition.  =
The new Datatracker is running here:
> https://trackerbeta.ietf.org/
>=20
> Thank you for your assistance,
>  Russ


From wwwrun@ietfa.amsl.com  Tue Feb 21 09:12:17 2012
Return-Path: <wwwrun@ietfa.amsl.com>
X-Original-To: wgchairs@ietf.org
Delivered-To: wgchairs@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 30) id 1683021F8889; Tue, 21 Feb 2012 09:12:17 -0800 (PST)
From: IETF Agenda <agenda@ietf.org>
To: Working Group Chairs <wgchairs@ietf.org>
Subject: 83rd IETF - Working Group Chairs Training - Reminder 
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20120221171217.1683021F8889@ietfa.amsl.com>
Date: Tue, 21 Feb 2012 09:12:17 -0800 (PST)
Cc: irsg@irtf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2012 17:12:17 -0000

During the Wednesday lunch slot (11:30am - 1:00pm) at IETF 83rd in Paris, we will be holding a WG chairs' training session on "Introduction to new Data Tracker DB".  Please come to share your ideas on this topic.  This session is open to all current WG chairs, BOF chairs, IRTF chairs, IESG members, and WG Secretaries.  We will include a complementary lunch.

Henrik Levkowetz will lead the discussion.

If you would like to attend this session, please RSVP to agenda@ietf.org
by Wednesday, March 14, 2012. The location will be sent to those who RSVP.


Thanks,
Wanda

From housley@vigilsec.com  Tue Feb 21 09:59:27 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 6ECD521F871D for <wgchairs@ietfa.amsl.com>; Tue, 21 Feb 2012 09:59:27 -0800 (PST)
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.068, 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 Kutp1TkgAzvv for <wgchairs@ietfa.amsl.com>; Tue, 21 Feb 2012 09:59:23 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 6482521F86BD for <wgchairs@ietf.org>; Tue, 21 Feb 2012 09:59:23 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 7466E9A471B for <wgchairs@ietf.org>; Tue, 21 Feb 2012 12:59:49 -0500 (EST)
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 XIEKeyfAO2lY for <wgchairs@ietf.org>; Tue, 21 Feb 2012 12:59:08 -0500 (EST)
Received: from [192.168.2.104] (pool-96-241-165-215.washdc.fios.verizon.net [96.241.165.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 15CD09A470F for <wgchairs@ietf.org>; Tue, 21 Feb 2012 12:59:46 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: DRAFT Revision to the WG Document Writeup
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <4F3D1B2A.7050601@ogud.com>
Date: Tue, 21 Feb 2012 12:59:18 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <2CB36BF2-E230-4D96-95B1-54989609620B@vigilsec.com>
References: <AE35FF1F-47D2-4AB3-B074-6CCBA5B6AC25@vigilsec.com> <201110271852.p9RIqcOO025921@mtv-core-3.cisco.com> <FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CA9E@MX14A.corp.emc.com> <23B2E96E-08CE-40D1-8038-89A7A672E9F5@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CAE1@MX14A.corp.emc.com> <7D5B9928-1D93-43DC-A50C-E74BF81E53F3@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD33AA9D@MX14A.corp.emc.com> <365EF4B3-53D2-4AB8-BC8D-F0803F734E15@vigilsec.com> <4F3D1B2A.7050601@ogud.com>
To: IETF WG Chairs <wgchairs@ietf.org>
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: Tue, 21 Feb 2012 17:59:27 -0000

I have incorporated the last round of comments.  I think we are probably =
ready to start using this and get some experience with it.

Russ

=3D =3D =3D =3D =3D =3D =3D =3D =3D

Document Writeup

As required by RFC 4858, this is the current template for the Document
Shepherd Write-Up.

Changes are expected over time. This DRAFT version is dated
21 February 2012.

(1) What type of RFC is being requested (BCP, Proposed Standard,
Internet Standard, Informational, Experimental, or Historic)?  Why
is the proper type of RFC?  Is this type of RFC indicated in the title
page header?

(2) The IESG approval announcement includes a Document Announcement
Write-Up. Please provide such a Document Announcement Write-Up. Recent
examples can be found in the "Action" announcements for approved
documents. The approval announcement contains the following sections:

Technical Summary

   Relevant content can frequently be found in the abstract=20
   and/or introduction of the document. If not, this may be=20
   an indication that there are deficiencies in the abstract=20
   or introduction.

Working Group Summary

   Was there anything in WG process that is worth noting? For=20
   example, was there controversy about particular points or=20
   were there decisions where the consensus was particularly=20
   rough?

Document Quality

   Are there existing implementations of the protocol? Have a=20
   significant number of vendors indicated their plan to=20
   implement the specification? Are there any reviewers that=20
   merit special mention as having done a thorough review,=20
   e.g., one that resulted in important changes or a=20
   conclusion that the document had no substantive issues? If=20
   there was a MIB Doctor, Media Type or other expert review,=20
   what was its course (briefly)? In the case of a Media Type=20
   review, on what date was the request posted?

 Personnel

   Who is the Document Shepherd? Who is the Responsible Area
   Director?

(3) Briefly describe the review of this document that was performed by
the Document Shepherd.  If this version of the document is not ready
for publication, please explain why the document is being forwarded to
the IESG.

(4) Does the document Shepherd have any concerns about the depth or
breadth of the reviews that have been performed? =20

(5) Do portions of the document need review from a particular or from
broader perspective, e.g., security, operational complexity, AAA, DNS,
DHCP, XML, or internationalization? If so, describe the review that
took place.

(6) Describe any specific concerns or issues that the Document Shepherd
has with this document that the Responsible Area Director and/or the
IESG should be aware of? For example, perhaps he or she is uncomfortable
with certain parts of the document, or has concerns whether there really
is a need for it. In any event, if the WG has discussed those issues and
has indicated that it still wishes to advance the document, detail those
concerns here.

(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. If not, explain why.

(8) Has an IPR disclosure been filed that references this document?
If so, summarize any WG discussion and conclusion regarding the IPR
disclosures.

(9) How solid is the WG consensus behind this document? Does it=20
represent the strong concurrence of a few individuals, with others
being silent, or does the WG as a whole understand and agree with it?  =20=


(10) Has anyone threatened an appeal or otherwise indicated extreme=20
discontent? If so, please summarise the areas of conflict in separate
email messages to the Responsible Area Director. (It should be in a
separate email because this questionnaire is publicly available.)=20

(11) Identify any ID nits the Document Shepherd has found in this
document. (See http://www.ietf.org/tools/idnits/ and the Internet-Drafts
Checklist). Boilerplate checks are not enough; this check needs to be
thorough.

(12) Describe how the document meets any required formal review
criteria, such as the MIB Doctor, media type, and URI type reviews.

(13) Have all references within this document been identified as
either normative and informative?

(14) Are there normative references to documents that are not ready for
advancement or are otherwise in an unclear state? If such normative
references exist, what is the plan for their completion?

(15) Are there downward normative references references (see RFC 3967)?
If so, list these downward references to support the Area Director in =
the
Last Call procedure.=20

(16) Will publication of this document change to the status of any
existing RFCs? Are those RFCs listed on the title page header, listed
in the abstract, and discussed in the introduction? If the RFCs are not
listed in the Abstract and Introduction, explain why, and point to the
part of the document where the relationship of this document to the
other RFCs is discussed. If this information is not in the document,
explain why the WG considers it unnecessary.

(17) Describe the Document Shepherd's review of the IANA considerations
section, especially with regard to its consistency with the body of the
document. Confirm that all protocol extensions that the document makes
are associated with the appropriate reservations in IANA registries.
Confirm that any referenced IANA registries have been clearly
identified. Confirm that newly created IANA registries include a
detailed specification of the initial contents for the registry, that
allocations procedures for future registrations are defined, and a
reasonable name for the new registry has been suggested (see RFC 5226).

(18) List any new IANA registries that require Expert Review for future
allocations. Provide any public guidance that the IESG would find
useful in selecting the IANA Experts for these new registries.

(19) Describe reviews and automated checks performed by the Document
Shepherd to validate sections of the document written in a formal
language, such as XML code, BNF rules, MIB definitions, etc.


From rcallon@juniper.net  Tue Feb 21 12:39:53 2012
Return-Path: <rcallon@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 52AFB21F87A8 for <wgchairs@ietfa.amsl.com>; Tue, 21 Feb 2012 12:39:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.583
X-Spam-Level: 
X-Spam-Status: No, score=-106.583 tagged_above=-999 required=5 tests=[AWL=0.016, 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 8Si0YktlI7xm for <wgchairs@ietfa.amsl.com>; Tue, 21 Feb 2012 12:39:49 -0800 (PST)
Received: from exprod7og113.obsmtp.com (exprod7og113.obsmtp.com [64.18.2.179]) by ietfa.amsl.com (Postfix) with ESMTP id BFACB21F8763 for <wgchairs@ietf.org>; Tue, 21 Feb 2012 12:39:23 -0800 (PST)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob113.postini.com ([64.18.6.12]) with SMTP ID DSNKT0QA+/ZT8pYkcG/lvxsN1nboNCE9b3vH@postini.com; Tue, 21 Feb 2012 12:39:45 PST
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.3.213.0; Tue, 21 Feb 2012 12:38:18 -0800
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; Tue, 21 Feb 2012 15:38:17 -0500
From: Ross Callon <rcallon@juniper.net>
To: Russ Housley <housley@vigilsec.com>
Date: Tue, 21 Feb 2012 15:38:15 -0500
Subject: RE: DRAFT Revision to the WG Document Writeup
Thread-Topic: DRAFT Revision to the WG Document Writeup
Thread-Index: AczwwpB4khsJpVHnQjuFpJuFx1KgSQAFchuw
Message-ID: <DF7F294AF4153D498141CBEFADB17704C70B74ADCA@EMBX01-WF.jnpr.net>
References: <AE35FF1F-47D2-4AB3-B074-6CCBA5B6AC25@vigilsec.com> <201110271852.p9RIqcOO025921@mtv-core-3.cisco.com> <FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CA9E@MX14A.corp.emc.com> <23B2E96E-08CE-40D1-8038-89A7A672E9F5@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CAE1@MX14A.corp.emc.com> <7D5B9928-1D93-43DC-A50C-E74BF81E53F3@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD33AA9D@MX14A.corp.emc.com> <365EF4B3-53D2-4AB8-BC8D-F0803F734E15@vigilsec.com> <4F3D1B2A.7050601@ogud.com> <2CB36BF2-E230-4D96-95B1-54989609620B@vigilsec.com>
In-Reply-To: <2CB36BF2-E230-4D96-95B1-54989609620B@vigilsec.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EXCLAIMER-MD-CONFIG: e4081efb-6d29-443c-8708-750833aec629
Cc: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2012 20:39:53 -0000

Minor nit:=20

	(13) Have all references within this document been identified as
	either normative and informative?

The "and" above should be "or".

Ross

-----Original Message-----
From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On Behal=
f Of Russ Housley
Sent: Tuesday, February 21, 2012 12:59 PM
To: IETF WG Chairs
Subject: Re: DRAFT Revision to the WG Document Writeup

I have incorporated the last round of comments.  I think we are probably re=
ady to start using this and get some experience with it.

Russ

=3D =3D =3D =3D =3D =3D =3D =3D =3D

Document Writeup

As required by RFC 4858, this is the current template for the Document
Shepherd Write-Up.

Changes are expected over time. This DRAFT version is dated
21 February 2012.

(1) What type of RFC is being requested (BCP, Proposed Standard,
Internet Standard, Informational, Experimental, or Historic)?  Why
is the proper type of RFC?  Is this type of RFC indicated in the title
page header?

(2) The IESG approval announcement includes a Document Announcement
Write-Up. Please provide such a Document Announcement Write-Up. Recent
examples can be found in the "Action" announcements for approved
documents. The approval announcement contains the following sections:

Technical Summary

   Relevant content can frequently be found in the abstract=20
   and/or introduction of the document. If not, this may be=20
   an indication that there are deficiencies in the abstract=20
   or introduction.

Working Group Summary

   Was there anything in WG process that is worth noting? For=20
   example, was there controversy about particular points or=20
   were there decisions where the consensus was particularly=20
   rough?

Document Quality

   Are there existing implementations of the protocol? Have a=20
   significant number of vendors indicated their plan to=20
   implement the specification? Are there any reviewers that=20
   merit special mention as having done a thorough review,=20
   e.g., one that resulted in important changes or a=20
   conclusion that the document had no substantive issues? If=20
   there was a MIB Doctor, Media Type or other expert review,=20
   what was its course (briefly)? In the case of a Media Type=20
   review, on what date was the request posted?

 Personnel

   Who is the Document Shepherd? Who is the Responsible Area
   Director?

(3) Briefly describe the review of this document that was performed by
the Document Shepherd.  If this version of the document is not ready
for publication, please explain why the document is being forwarded to
the IESG.

(4) Does the document Shepherd have any concerns about the depth or
breadth of the reviews that have been performed? =20

(5) Do portions of the document need review from a particular or from
broader perspective, e.g., security, operational complexity, AAA, DNS,
DHCP, XML, or internationalization? If so, describe the review that
took place.

(6) Describe any specific concerns or issues that the Document Shepherd
has with this document that the Responsible Area Director and/or the
IESG should be aware of? For example, perhaps he or she is uncomfortable
with certain parts of the document, or has concerns whether there really
is a need for it. In any event, if the WG has discussed those issues and
has indicated that it still wishes to advance the document, detail those
concerns here.

(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. If not, explain why.

(8) Has an IPR disclosure been filed that references this document?
If so, summarize any WG discussion and conclusion regarding the IPR
disclosures.

(9) How solid is the WG consensus behind this document? Does it=20
represent the strong concurrence of a few individuals, with others
being silent, or does the WG as a whole understand and agree with it?  =20

(10) Has anyone threatened an appeal or otherwise indicated extreme=20
discontent? If so, please summarise the areas of conflict in separate
email messages to the Responsible Area Director. (It should be in a
separate email because this questionnaire is publicly available.)=20

(11) Identify any ID nits the Document Shepherd has found in this
document. (See http://www.ietf.org/tools/idnits/ and the Internet-Drafts
Checklist). Boilerplate checks are not enough; this check needs to be
thorough.

(12) Describe how the document meets any required formal review
criteria, such as the MIB Doctor, media type, and URI type reviews.

(13) Have all references within this document been identified as
either normative and informative?

(14) Are there normative references to documents that are not ready for
advancement or are otherwise in an unclear state? If such normative
references exist, what is the plan for their completion?

(15) Are there downward normative references references (see RFC 3967)?
If so, list these downward references to support the Area Director in the
Last Call procedure.=20

(16) Will publication of this document change to the status of any
existing RFCs? Are those RFCs listed on the title page header, listed
in the abstract, and discussed in the introduction? If the RFCs are not
listed in the Abstract and Introduction, explain why, and point to the
part of the document where the relationship of this document to the
other RFCs is discussed. If this information is not in the document,
explain why the WG considers it unnecessary.

(17) Describe the Document Shepherd's review of the IANA considerations
section, especially with regard to its consistency with the body of the
document. Confirm that all protocol extensions that the document makes
are associated with the appropriate reservations in IANA registries.
Confirm that any referenced IANA registries have been clearly
identified. Confirm that newly created IANA registries include a
detailed specification of the initial contents for the registry, that
allocations procedures for future registrations are defined, and a
reasonable name for the new registry has been suggested (see RFC 5226).

(18) List any new IANA registries that require Expert Review for future
allocations. Provide any public guidance that the IESG would find
useful in selecting the IANA Experts for these new registries.

(19) Describe reviews and automated checks performed by the Document
Shepherd to validate sections of the document written in a formal
language, such as XML code, BNF rules, MIB definitions, etc.


From housley@vigilsec.com  Tue Feb 21 12:43:12 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 ECE9011E8098 for <wgchairs@ietfa.amsl.com>; Tue, 21 Feb 2012 12:43:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.532
X-Spam-Level: 
X-Spam-Status: No, score=-102.532 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HO2XzkZCgXh1 for <wgchairs@ietfa.amsl.com>; Tue, 21 Feb 2012 12:43:10 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 8E58F21F87DF for <wgchairs@ietf.org>; Tue, 21 Feb 2012 12:43:07 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 7F096F24135; Tue, 21 Feb 2012 15:43:22 -0500 (EST)
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 5W0iWtmUeSip; Tue, 21 Feb 2012 15:42:55 -0500 (EST)
Received: from [192.168.2.104] (pool-96-241-165-215.washdc.fios.verizon.net [96.241.165.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id DB0E3F24105; Tue, 21 Feb 2012 15:43:17 -0500 (EST)
Subject: Re: DRAFT Revision to the WG Document Writeup
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <DF7F294AF4153D498141CBEFADB17704C70B74ADCA@EMBX01-WF.jnpr.net>
Date: Tue, 21 Feb 2012 15:43:01 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <98C34DDD-D27F-4E34-BE0C-40BC577FE8F2@vigilsec.com>
References: <AE35FF1F-47D2-4AB3-B074-6CCBA5B6AC25@vigilsec.com> <201110271852.p9RIqcOO025921@mtv-core-3.cisco.com> <FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CA9E@MX14A.corp.emc.com> <23B2E96E-08CE-40D1-8038-89A7A672E9F5@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CAE1@MX14A.corp.emc.com> <7D5B9928-1D93-43DC-A50C-E74BF81E53F3@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD33AA9D@MX14A.corp.emc.com> <365EF4B3-53D2-4AB8-BC8D-F0803F734E15@vigilsec.com> <4F3D1B2A.7050601@ogud.com> <2CB36BF2-E230-4D96-95B1-54989609620B@vigilsec.com> <DF7F294AF4153D498141CBEFADB17704C70B74ADCA@EMBX01-WF.jnpr.net>
To: Ross Callon <rcallon@juniper.net>
X-Mailer: Apple Mail (2.1084)
Cc: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2012 20:43:13 -0000

Thanks.  I'll fix it.

Russ


On Feb 21, 2012, at 3:38 PM, Ross Callon wrote:

> Minor nit:=20
>=20
> 	(13) Have all references within this document been identified as
> 	either normative and informative?
>=20
> The "and" above should be "or".
>=20
> Ross
>=20
> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On =
Behalf Of Russ Housley
> Sent: Tuesday, February 21, 2012 12:59 PM
> To: IETF WG Chairs
> Subject: Re: DRAFT Revision to the WG Document Writeup
>=20
> I have incorporated the last round of comments.  I think we are =
probably ready to start using this and get some experience with it.
>=20
> Russ
>=20
> =3D =3D =3D =3D =3D =3D =3D =3D =3D
>=20
> Document Writeup
>=20
> As required by RFC 4858, this is the current template for the Document
> Shepherd Write-Up.
>=20
> Changes are expected over time. This DRAFT version is dated
> 21 February 2012.
>=20
> (1) What type of RFC is being requested (BCP, Proposed Standard,
> Internet Standard, Informational, Experimental, or Historic)?  Why
> is the proper type of RFC?  Is this type of RFC indicated in the title
> page header?
>=20
> (2) The IESG approval announcement includes a Document Announcement
> Write-Up. Please provide such a Document Announcement Write-Up. Recent
> examples can be found in the "Action" announcements for approved
> documents. The approval announcement contains the following sections:
>=20
> Technical Summary
>=20
>   Relevant content can frequently be found in the abstract=20
>   and/or introduction of the document. If not, this may be=20
>   an indication that there are deficiencies in the abstract=20
>   or introduction.
>=20
> Working Group Summary
>=20
>   Was there anything in WG process that is worth noting? For=20
>   example, was there controversy about particular points or=20
>   were there decisions where the consensus was particularly=20
>   rough?
>=20
> Document Quality
>=20
>   Are there existing implementations of the protocol? Have a=20
>   significant number of vendors indicated their plan to=20
>   implement the specification? Are there any reviewers that=20
>   merit special mention as having done a thorough review,=20
>   e.g., one that resulted in important changes or a=20
>   conclusion that the document had no substantive issues? If=20
>   there was a MIB Doctor, Media Type or other expert review,=20
>   what was its course (briefly)? In the case of a Media Type=20
>   review, on what date was the request posted?
>=20
> Personnel
>=20
>   Who is the Document Shepherd? Who is the Responsible Area
>   Director?
>=20
> (3) Briefly describe the review of this document that was performed by
> the Document Shepherd.  If this version of the document is not ready
> for publication, please explain why the document is being forwarded to
> the IESG.
>=20
> (4) Does the document Shepherd have any concerns about the depth or
> breadth of the reviews that have been performed? =20
>=20
> (5) Do portions of the document need review from a particular or from
> broader perspective, e.g., security, operational complexity, AAA, DNS,
> DHCP, XML, or internationalization? If so, describe the review that
> took place.
>=20
> (6) Describe any specific concerns or issues that the Document =
Shepherd
> has with this document that the Responsible Area Director and/or the
> IESG should be aware of? For example, perhaps he or she is =
uncomfortable
> with certain parts of the document, or has concerns whether there =
really
> is a need for it. In any event, if the WG has discussed those issues =
and
> has indicated that it still wishes to advance the document, detail =
those
> concerns here.
>=20
> (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. If not, explain why.
>=20
> (8) Has an IPR disclosure been filed that references this document?
> If so, summarize any WG discussion and conclusion regarding the IPR
> disclosures.
>=20
> (9) How solid is the WG consensus behind this document? Does it=20
> represent the strong concurrence of a few individuals, with others
> being silent, or does the WG as a whole understand and agree with it?  =
=20
>=20
> (10) Has anyone threatened an appeal or otherwise indicated extreme=20
> discontent? If so, please summarise the areas of conflict in separate
> email messages to the Responsible Area Director. (It should be in a
> separate email because this questionnaire is publicly available.)=20
>=20
> (11) Identify any ID nits the Document Shepherd has found in this
> document. (See http://www.ietf.org/tools/idnits/ and the =
Internet-Drafts
> Checklist). Boilerplate checks are not enough; this check needs to be
> thorough.
>=20
> (12) Describe how the document meets any required formal review
> criteria, such as the MIB Doctor, media type, and URI type reviews.
>=20
> (13) Have all references within this document been identified as
> either normative and informative?
>=20
> (14) Are there normative references to documents that are not ready =
for
> advancement or are otherwise in an unclear state? If such normative
> references exist, what is the plan for their completion?
>=20
> (15) Are there downward normative references references (see RFC =
3967)?
> If so, list these downward references to support the Area Director in =
the
> Last Call procedure.=20
>=20
> (16) Will publication of this document change to the status of any
> existing RFCs? Are those RFCs listed on the title page header, listed
> in the abstract, and discussed in the introduction? If the RFCs are =
not
> listed in the Abstract and Introduction, explain why, and point to the
> part of the document where the relationship of this document to the
> other RFCs is discussed. If this information is not in the document,
> explain why the WG considers it unnecessary.
>=20
> (17) Describe the Document Shepherd's review of the IANA =
considerations
> section, especially with regard to its consistency with the body of =
the
> document. Confirm that all protocol extensions that the document makes
> are associated with the appropriate reservations in IANA registries.
> Confirm that any referenced IANA registries have been clearly
> identified. Confirm that newly created IANA registries include a
> detailed specification of the initial contents for the registry, that
> allocations procedures for future registrations are defined, and a
> reasonable name for the new registry has been suggested (see RFC =
5226).
>=20
> (18) List any new IANA registries that require Expert Review for =
future
> allocations. Provide any public guidance that the IESG would find
> useful in selecting the IANA Experts for these new registries.
>=20
> (19) Describe reviews and automated checks performed by the Document
> Shepherd to validate sections of the document written in a formal
> language, such as XML code, BNF rules, MIB definitions, etc.
>=20


From keith.drage@alcatel-lucent.com  Tue Feb 21 19:34:41 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 77CA921E8030 for <wgchairs@ietfa.amsl.com>; Tue, 21 Feb 2012 19:34:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.149
X-Spam-Level: 
X-Spam-Status: No, score=-109.149 tagged_above=-999 required=5 tests=[AWL=1.100, 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 gjVEWZnnhkmy for <wgchairs@ietfa.amsl.com>; Tue, 21 Feb 2012 19:34:40 -0800 (PST)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by ietfa.amsl.com (Postfix) with ESMTP id E4BE621E802D for <wgchairs@ietf.org>; Tue, 21 Feb 2012 19:34:39 -0800 (PST)
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 q1M3Ya5t022971 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 22 Feb 2012 04:34:37 +0100
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.46]) by FRMRSSXCHHUB01.dc-m.alcatel-lucent.com ([135.120.45.61]) with mapi; Wed, 22 Feb 2012 04:34:36 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Russ Housley <housley@vigilsec.com>, IETF WG Chairs <wgchairs@ietf.org>
Date: Wed, 22 Feb 2012 04:34:34 +0100
Subject: RE: DRAFT Revision to the WG Document Writeup
Thread-Topic: DRAFT Revision to the WG Document Writeup
Thread-Index: AczwwrXTSk4NvoDYQFi0JzA0vaX8RQAUBjVw
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE224AE9A62@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <AE35FF1F-47D2-4AB3-B074-6CCBA5B6AC25@vigilsec.com> <201110271852.p9RIqcOO025921@mtv-core-3.cisco.com> <FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CA9E@MX14A.corp.emc.com> <23B2E96E-08CE-40D1-8038-89A7A672E9F5@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CAE1@MX14A.corp.emc.com> <7D5B9928-1D93-43DC-A50C-E74BF81E53F3@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD33AA9D@MX14A.corp.emc.com> <365EF4B3-53D2-4AB8-BC8D-F0803F734E15@vigilsec.com> <4F3D1B2A.7050601@ogud.com> <2CB36BF2-E230-4D96-95B1-54989609620B@vigilsec.com>
In-Reply-To: <2CB36BF2-E230-4D96-95B1-54989609620B@vigilsec.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.13
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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, 22 Feb 2012 03:34:41 -0000

Seem to be missing the word "this".

(1) What type of RFC is being requested (BCP, Proposed Standard, Internet S=
tandard, Informational, Experimental, or Historic)?  Why is this the proper=
 type of RFC?  Is this type of RFC indicated in the title page header?

Regards

Keith

> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
> Behalf Of Russ Housley
> Sent: 21 February 2012 17:59
> To: IETF WG Chairs
> Subject: Re: DRAFT Revision to the WG Document Writeup
>=20
> I have incorporated the last round of comments.  I think we are probably
> ready to start using this and get some experience with it.
>=20
> Russ
>=20
> =3D =3D =3D =3D =3D =3D =3D =3D =3D
>=20
> Document Writeup
>=20
> As required by RFC 4858, this is the current template for the Document
> Shepherd Write-Up.
>=20
> Changes are expected over time. This DRAFT version is dated
> 21 February 2012.
>=20
> (1) What type of RFC is being requested (BCP, Proposed Standard,
> Internet Standard, Informational, Experimental, or Historic)?  Why
> is the proper type of RFC?  Is this type of RFC indicated in the title
> page header?
>=20
> (2) The IESG approval announcement includes a Document Announcement
> Write-Up. Please provide such a Document Announcement Write-Up. Recent
> examples can be found in the "Action" announcements for approved
> documents. The approval announcement contains the following sections:
>=20
> Technical Summary
>=20
>    Relevant content can frequently be found in the abstract
>    and/or introduction of the document. If not, this may be
>    an indication that there are deficiencies in the abstract
>    or introduction.
>=20
> Working Group Summary
>=20
>    Was there anything in WG process that is worth noting? For
>    example, was there controversy about particular points or
>    were there decisions where the consensus was particularly
>    rough?
>=20
> Document Quality
>=20
>    Are there existing implementations of the protocol? Have a
>    significant number of vendors indicated their plan to
>    implement the specification? Are there any reviewers that
>    merit special mention as having done a thorough review,
>    e.g., one that resulted in important changes or a
>    conclusion that the document had no substantive issues? If
>    there was a MIB Doctor, Media Type or other expert review,
>    what was its course (briefly)? In the case of a Media Type
>    review, on what date was the request posted?
>=20
>  Personnel
>=20
>    Who is the Document Shepherd? Who is the Responsible Area
>    Director?
>=20
> (3) Briefly describe the review of this document that was performed by
> the Document Shepherd.  If this version of the document is not ready
> for publication, please explain why the document is being forwarded to
> the IESG.
>=20
> (4) Does the document Shepherd have any concerns about the depth or
> breadth of the reviews that have been performed?
>=20
> (5) Do portions of the document need review from a particular or from
> broader perspective, e.g., security, operational complexity, AAA, DNS,
> DHCP, XML, or internationalization? If so, describe the review that
> took place.
>=20
> (6) Describe any specific concerns or issues that the Document Shepherd
> has with this document that the Responsible Area Director and/or the
> IESG should be aware of? For example, perhaps he or she is uncomfortable
> with certain parts of the document, or has concerns whether there really
> is a need for it. In any event, if the WG has discussed those issues and
> has indicated that it still wishes to advance the document, detail those
> concerns here.
>=20
> (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. If not, explain why.
>=20
> (8) Has an IPR disclosure been filed that references this document?
> If so, summarize any WG discussion and conclusion regarding the IPR
> disclosures.
>=20
> (9) How solid is the WG consensus behind this document? Does it
> represent the strong concurrence of a few individuals, with others
> being silent, or does the WG as a whole understand and agree with it?
>=20
> (10) Has anyone threatened an appeal or otherwise indicated extreme
> discontent? If so, please summarise the areas of conflict in separate
> email messages to the Responsible Area Director. (It should be in a
> separate email because this questionnaire is publicly available.)
>=20
> (11) Identify any ID nits the Document Shepherd has found in this
> document. (See http://www.ietf.org/tools/idnits/ and the Internet-Drafts
> Checklist). Boilerplate checks are not enough; this check needs to be
> thorough.
>=20
> (12) Describe how the document meets any required formal review
> criteria, such as the MIB Doctor, media type, and URI type reviews.
>=20
> (13) Have all references within this document been identified as
> either normative and informative?
>=20
> (14) Are there normative references to documents that are not ready for
> advancement or are otherwise in an unclear state? If such normative
> references exist, what is the plan for their completion?
>=20
> (15) Are there downward normative references references (see RFC 3967)?
> If so, list these downward references to support the Area Director in the
> Last Call procedure.
>=20
> (16) Will publication of this document change to the status of any
> existing RFCs? Are those RFCs listed on the title page header, listed
> in the abstract, and discussed in the introduction? If the RFCs are not
> listed in the Abstract and Introduction, explain why, and point to the
> part of the document where the relationship of this document to the
> other RFCs is discussed. If this information is not in the document,
> explain why the WG considers it unnecessary.
>=20
> (17) Describe the Document Shepherd's review of the IANA considerations
> section, especially with regard to its consistency with the body of the
> document. Confirm that all protocol extensions that the document makes
> are associated with the appropriate reservations in IANA registries.
> Confirm that any referenced IANA registries have been clearly
> identified. Confirm that newly created IANA registries include a
> detailed specification of the initial contents for the registry, that
> allocations procedures for future registrations are defined, and a
> reasonable name for the new registry has been suggested (see RFC 5226).
>=20
> (18) List any new IANA registries that require Expert Review for future
> allocations. Provide any public guidance that the IESG would find
> useful in selecting the IANA Experts for these new registries.
>=20
> (19) Describe reviews and automated checks performed by the Document
> Shepherd to validate sections of the document written in a formal
> language, such as XML code, BNF rules, MIB definitions, etc.


From paul.hoffman@vpnc.org  Thu Feb 23 08:30:08 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 7F23621F8691 for <wgchairs@ietfa.amsl.com>; Thu, 23 Feb 2012 08:30:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.638
X-Spam-Level: 
X-Spam-Status: No, score=-102.638 tagged_above=-999 required=5 tests=[AWL=-0.039, 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 JiRk4j7GOesD for <wgchairs@ietfa.amsl.com>; Thu, 23 Feb 2012 08:30:08 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 156C221F866D for <wgchairs@ietf.org>; Thu, 23 Feb 2012 08:30:08 -0800 (PST)
Received: from [10.20.30.100] (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 q1NGU7Fx026603 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 23 Feb 2012 09:30:07 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: DRAFT Revision to the WG Document Writeup
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <98C34DDD-D27F-4E34-BE0C-40BC577FE8F2@vigilsec.com>
Date: Thu, 23 Feb 2012 08:30:07 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <4B05FC13-AA69-40CB-9BA1-DF3F3710EF3B@vpnc.org>
References: <AE35FF1F-47D2-4AB3-B074-6CCBA5B6AC25@vigilsec.com> <201110271852.p9RIqcOO025921@mtv-core-3.cisco.com> <FCDC373F-94B5-4039-9624-1B68DC807019@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CA9E@MX14A.corp.emc.com> <23B2E96E-08CE-40D1-8038-89A7A672E9F5@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD29CAE1@MX14A.corp.emc.com> <7D5B9928-1D93-43DC-A50C-E74BF81E53F3@vigilsec.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05AD33AA9D@MX14A.corp.emc.com> <365EF4B3-53D2-4AB8-BC8D-F0803F734E15@vigilsec.com> <4F3D1B2A.7050601@ogud.com> <2CB36BF2-E230-4D96-95B1-54989609620B@vigilsec.com> <DF7F294AF4153D498141CBEFADB17704C70B74ADCA@EMBX01-WF.jnpr.net> <98C34DDD-D27F-4E34-BE0C-40BC577FE8F2@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.1257)
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, 23 Feb 2012 16:30:08 -0000

I know you want to close out this version, but another idea just =
occurred to me that would be valuable for the checklist:

If this is a "bis" document, was there any errata filed on the base RFC? =
If so, have all of them been included in this new document?

--Paul Hoffman=

From wwwrun@ietfa.amsl.com  Thu Feb 23 13:30:19 2012
Return-Path: <wwwrun@ietfa.amsl.com>
X-Original-To: wgchairs@ietf.org
Delivered-To: wgchairs@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 30) id 7A48621F87A2; Thu, 23 Feb 2012 13:30:19 -0800 (PST)
From: IETF Agenda <agenda@ietf.org>
To: Working Group Chairs <wgchairs@ietf.org>
Subject: 83rd IETF DRAFT Agenda 
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20120223213019.7A48621F87A2@ietfa.amsl.com>
Date: Thu, 23 Feb 2012 13:30:19 -0800 (PST)
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, 23 Feb 2012 21:30:19 -0000

The DRAFT agenda is ready for viewing.  Please note the cutoff date for
requests to reschedule Working Group and BOF meetings is February 27, 2012
17:00 PT.  The final agenda will be published on March 2, 2012.

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

http://www.ietf.org/meeting/83/index.html


Thanks,
Wanda

Only 30 days until Paris, 83rd IETF!
Online registration for the IETF meeting is at:
http://www.ietf.org/meeting/register.html


From iesg@ietf.org  Fri Feb 24 13:06:19 2012
Return-Path: <iesg@ietf.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7287821F87B1; Fri, 24 Feb 2012 13:06:19 -0800 (PST)
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 3IIBTJv08JGw; Fri, 24 Feb 2012 13:06:13 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 8029521F86F3; Fri, 24 Feb 2012 13:06:08 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 3B3FF12C981; Fri, 24 Feb 2012 13:06:07 -0800 (PST)
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 Z6Ga+PQaUQmP; Fri, 24 Feb 2012 13:06:07 -0800 (PST)
Received: from [192.168.2.104] (pool-96-241-165-215.washdc.fios.verizon.net [96.241.165.215]) by c8a.amsl.com (Postfix) with ESMTPSA id D420A12C8D4; Fri, 24 Feb 2012 13:06:06 -0800 (PST)
From: The IESG <iesg@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Revision to the WG Document Writeup
Date: Fri, 24 Feb 2012 16:06:06 -0500
Message-Id: <3150D4F6-59FC-4D3D-9D69-ABC1D34B6C82@ietf.org>
To: IETF Announce <ietf-announce@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Cc: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2012 21:06:19 -0000

The IESG has adopted an update the WG Document Write-up Template.  The =
write-up is required by RFC 4858.  The new template has been posted at:

  http://www.ietf.org/iesg/template/doc-writeup.html

Please start using this new template immediately for publication =
requests.  New publications requests after 28 March 2012 must use the =
new template.


On behalf of the IESG,
   Russ Housley
   IESG Chair


From cyrus@daboo.name  Fri Feb 24 13:14:02 2012
Return-Path: <cyrus@daboo.name>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8707F21F870B; Fri, 24 Feb 2012 13:14:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.635
X-Spam-Level: 
X-Spam-Status: No, score=-102.635 tagged_above=-999 required=5 tests=[AWL=-0.036, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sIPLmjc7+lE6; Fri, 24 Feb 2012 13:14:02 -0800 (PST)
Received: from daboo.name (daboo.name [173.13.55.49]) by ietfa.amsl.com (Postfix) with ESMTP id 07B6A21F86F9; Fri, 24 Feb 2012 13:14:02 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 634342263DA2; Fri, 24 Feb 2012 16:14:01 -0500 (EST)
X-Virus-Scanned: amavisd-new at daboo.name
Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TkG4pxp0i8if; Fri, 24 Feb 2012 16:14:00 -0500 (EST)
Received: from caldav.corp.apple.com (unknown [17.45.162.46]) by daboo.name (Postfix) with ESMTPSA id B2BB52263D97; Fri, 24 Feb 2012 16:13:58 -0500 (EST)
Date: Fri, 24 Feb 2012 16:13:55 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: The IESG <iesg@ietf.org>, IETF Announce <ietf-announce@ietf.org>
Subject: Re: Revision to the WG Document Writeup
Message-ID: <937A9BB88FE4376C81B94025@caldav.corp.apple.com>
In-Reply-To: <3150D4F6-59FC-4D3D-9D69-ABC1D34B6C82@ietf.org>
References: <3150D4F6-59FC-4D3D-9D69-ABC1D34B6C82@ietf.org>
X-Mailer: Mulberry/4.1.0a3 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size=624
Cc: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2012 21:14:02 -0000

Hi The,

--On February 24, 2012 4:06:06 PM -0500 The IESG <iesg@ietf.org> wrote:

> The IESG has adopted an update the WG Document Write-up Template.  The
> write-up is required by RFC 4858.  The new template has been posted at:
>
>   http://www.ietf.org/iesg/template/doc-writeup.html
>
> Please start using this new template immediately for publication
> requests.  New publications requests after 28 March 2012 must use the new
> template.
>

Minor typo fix suggestion: item (16)

change: Will publication of this document change to the status
to:     Will publication of this document change the status

-- 
Cyrus Daboo


From chair@ietf.org  Fri Feb 24 13:21:16 2012
Return-Path: <chair@ietf.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E918C21F8642; Fri, 24 Feb 2012 13:21:16 -0800 (PST)
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 tf+3fOMqogq4; Fri, 24 Feb 2012 13:21:16 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 632A821F8545; Fri, 24 Feb 2012 13:21:16 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 0775312C94A; Fri, 24 Feb 2012 13:21:15 -0800 (PST)
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 CjsgKqYQe-JN; Fri, 24 Feb 2012 13:21:14 -0800 (PST)
Received: from [192.168.2.104] (pool-96-241-165-215.washdc.fios.verizon.net [96.241.165.215]) by c8a.amsl.com (Postfix) with ESMTPSA id 706D612C931; Fri, 24 Feb 2012 13:21:14 -0800 (PST)
Subject: Re: Major upgrade to the IETF Datatracker
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: IETF Chair <chair@ietf.org>
In-Reply-To: <E50AF16F-60A4-48AC-9B39-ED8E3560FB24@ietf.org>
Date: Fri, 24 Feb 2012 16:21:13 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <3848B9FF-5F07-42A2-B4AE-06A4567CB143@ietf.org>
References: <E50AF16F-60A4-48AC-9B39-ED8E3560FB24@ietf.org>
To: IETF Announce <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1084)
Cc: IETF WG Chairs <wgchairs@ietf.org>, IAOC <iaoc@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2012 21:21:17 -0000

Thanks for all of the testing.  Several bugs were found and fixed.  At =
this time there are no show stopper bugs, so we will convert to the new =
Datatracker database this weekend.  Of course, to be prudent, we will =
run a complete backup before we being the database conversion.

The database conversation is scheduled to begin at 01:00 PST on =
Saturday, 25 February 2012.  After checking for any errors in the =
conversion process, the Datatracker will be pointed at the new database. =
 The database conversion it is expected to finish around 03:00 PST.  =
Expect the Datatracker to be unavailable during this two hour period, =
and please plan accordingly.

Hopefully, this significant Datatracker major change will go unnoticed =
by the whole community.

Thanks again for you help with the testing,
  Russ


On Feb 14, 2012, at 2:36 PM, IETF Chair wrote:
>=20
> Shortly, the IETF datatracker will go through a major change, one of =
the two largest since it was first deployed more than 10 years ago.  =
Hopefully no one will notice.
>=20
> The previous major change was in 2007, when we switched the public =
Datatracker from Perl cgi-bin scripts to a much more modern and safe =
implementation based on the Django web application framework.  Very few =
people noticed that change at the time.
>=20
> In a few days, we will transition to completely redesigned Datatracker =
database schema.  The new schema will better support today's needs, and =
we believe it will better support future enhancements.  Frankly, we =
outgrew the old schema some time ago.
>=20
> In order to achieve a nearly unnoticeable change-over, we now invite =
you to try out the new Datatracker, bang on it, kick the tires, and =
generally see if it works as well for you as the old one.
>=20
> For some additional insight, you may want to read the instructions =
that was given to our testers:
> http://trac.tools.ietf.org/tools/ietfdb/wiki/InstructionsForTesters
>=20
> Or, you may want to just jump in and see how it works.  Either way, =
please report any bugs, problems, surprises, gremlins, hiccups, flaws, =
and so on that you discover.  Reports will receive prompt attention.  We =
deploy new code upgrades (if any are available) every hour. Please use =
this mail list to report issues:
> iola-conversion-tool@ietf.org
>=20
> Try out the new Datatracker, and help us make a smooth transition.  =
The new Datatracker is running here:
> https://trackerbeta.ietf.org/
>=20
> Thank you for your assistance,
>  Russ


From wwwrun@ietfa.amsl.com  Fri Feb 24 13:56:48 2012
Return-Path: <wwwrun@ietfa.amsl.com>
X-Original-To: wgchairs@ietf.org
Delivered-To: wgchairs@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 30) id 9C16821F8555; Fri, 24 Feb 2012 13:56:48 -0800 (PST)
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Subject: IETF83 - Meeting Information 
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20120224215648.9C16821F8555@ietfa.amsl.com>
Date: Fri, 24 Feb 2012 13:56:48 -0800 (PST)
Cc: wgchairs@ietf.org, 83all@ietf.org, irsg@irtf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2012 21:56:48 -0000

IETF 83 Meeting
Paris, France
March 25-30, 2012
Host: TBD

Meeting venue:  Le Palais des Congres de Paris
http://www.viparis.com/Viparis/exhibition-paris/site/Palais-Congres-Paris-Paris/en/4

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

1.  Registration
2.  Visas & Letters of Invitation
3.  Accommodations
4.  IETF83 wiki
5.  Companion Program
6.  T-Shirt Contest - Reminder

1. Registration
	A. Early-Bird Registration - USD 650.00 Pay by Friday, 16 March 2012 1700 PT (UTC -7)
	B. After Early-Bird cutoff - USD 800.00
	C. Full-time Student Registrations - USD 150.00 (with proper ID)
	D. One Day Pass Registration - USD 350.00
	E. Registration Cancellation 	
		Cut-off for registration cancellation is Monday, 19 March 2012 at 1700 PT (UTC -7). 
		Cancellations are subject to a 10% (ten percent)cancellation fee if requested by 
		that date and time.
	F. Online Registration and Payment ends Friday, 23 March 2012,1700 local Paris time.
	G. On-site Registration starting Sunday, 25 March 2012 at 1100 local Paris time.

2. Visas & Letters of Invitation: 
	Information on Visiting France, please visit:
	http://www.consulfrance-sanfrancisco.org/spip.php?rubrique201

	After you complete the registration process, you can request an electronic IETF Letter
	of Invitation. You may also request one at a later time by following the link provided
	in the confirmation email. 

	Orange has graciously offered to provide letters of invitation (LOIs) for those who 
	needs visas to enter France. In order to add this functionality, the letter of invitation 
	system will be offline next Tuesday (Monday is a holiday in the United States). We expect
	to start providing IETF and Host LOIs on Wednesday of next week, and will send a notice 
	out as soon as the system is operational. 

3.  Accommodations
	The Hotel Concorde La Fayette (Headquarter Hotel - connected to meeting venue) 
	- Reservations Cut off Date: 09 March 2012
	The Le Meridien Etoile (directly across the street from the meeting venue)
	 - Le Meridien cutoff date has passed but there may still be rooms available at the IETF
	group rate, if you want to check on availability, please send a message to:
	Corinne Vissenberg <Corinne.Vissenberg@lemeridien.com>

	Room rates include one complimentary daily buffet breakfast and complimentary in-room
	high-speed Internet access. All service fees and VAT are included in guest room rates.

	NOTE: Continental Breakfast will NOT be served at the meeting venue.

4.  IETF83 wiki
	The IETF 83 meeting wiki (Your Wiki) has been created for the attendees of IETF 83 
	meeting to exchange information.

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

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

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

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

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

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

6.  T-Shirt Contest
	A reminder that you have until 1700 PST today, February 24th to vote for your favorite 
	t-shirt submission. You can view all 12 submissions and vote online at
	http://www.ietf.org/meeting/83/t-shirt-design-contest-voting.html. 

	Please note that submission numbers appear above each entry.  The poll can be found at 
	the bottom of the page, following the designs.

	We will announce the winner on Monday and then begin to accept online orders for the 
	community-selected t-shirt. Happy voting!

Only 29 days until the Paris IETF!

From chair@ietf.org  Sat Feb 25 10:21:52 2012
Return-Path: <chair@ietf.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9E8821F85C6; Sat, 25 Feb 2012 10:21:52 -0800 (PST)
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 nooiOkKzI72m; Sat, 25 Feb 2012 10:21:51 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id DCFEB21F85C3; Sat, 25 Feb 2012 10:21:51 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id C467712C8BF; Sat, 25 Feb 2012 10:21:51 -0800 (PST)
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 Q4a5DRSDtbVV; Sat, 25 Feb 2012 10:21:51 -0800 (PST)
Received: from [192.168.2.107] (pool-96-241-165-215.washdc.fios.verizon.net [96.241.165.215]) by c8a.amsl.com (Postfix) with ESMTPSA id 2C64B12C88E; Sat, 25 Feb 2012 10:21:51 -0800 (PST)
Subject: Re: Major upgrade to the IETF Datatracker
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: IETF Chair <chair@ietf.org>
In-Reply-To: <3848B9FF-5F07-42A2-B4AE-06A4567CB143@ietf.org>
Date: Sat, 25 Feb 2012 13:21:50 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <54733A77-6D00-46A9-9F2C-4C571D4E7D67@ietf.org>
References: <E50AF16F-60A4-48AC-9B39-ED8E3560FB24@ietf.org> <3848B9FF-5F07-42A2-B4AE-06A4567CB143@ietf.org>
To: IETF Announce <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1084)
Cc: IETF WG Chairs <wgchairs@ietf.org>, IAOC <iaoc@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Feb 2012 18:21:52 -0000

There were a few surprises during the Datatracker database conversion =
that caused it to take longer than planned, but in the end the =
conversion was successful.

At 07:01 PST the Datatracker was switched to the converted database.  So =
far, everything looks good.  Of course, we are keeping an eye out to =
look for potential problems.

A very heartfelt thank you to Henrik Levkowetz, Ole Laursen, and Ryan =
Cross for their extra efforts during the conversion.

Russ

On Feb 24, 2012, at 4:21 PM, IETF Chair wrote:

> Thanks for all of the testing.  Several bugs were found and fixed.  At =
this time there are no show stopper bugs, so we will convert to the new =
Datatracker database this weekend.  Of course, to be prudent, we will =
run a complete backup before we being the database conversion.
>=20
> The database conversation is scheduled to begin at 01:00 PST on =
Saturday, 25 February 2012.  After checking for any errors in the =
conversion process, the Datatracker will be pointed at the new database. =
 The database conversion it is expected to finish around 03:00 PST.  =
Expect the Datatracker to be unavailable during this two hour period, =
and please plan accordingly.
>=20
> Hopefully, this significant Datatracker major change will go unnoticed =
by the whole community.
>=20
> Thanks again for you help with the testing,
>  Russ
>=20
>=20
> On Feb 14, 2012, at 2:36 PM, IETF Chair wrote:
>>=20
>> Shortly, the IETF datatracker will go through a major change, one of =
the two largest since it was first deployed more than 10 years ago.  =
Hopefully no one will notice.
>>=20
>> The previous major change was in 2007, when we switched the public =
Datatracker from Perl cgi-bin scripts to a much more modern and safe =
implementation based on the Django web application framework.  Very few =
people noticed that change at the time.
>>=20
>> In a few days, we will transition to completely redesigned =
Datatracker database schema.  The new schema will better support today's =
needs, and we believe it will better support future enhancements.  =
Frankly, we outgrew the old schema some time ago.
>>=20
>> In order to achieve a nearly unnoticeable change-over, we now invite =
you to try out the new Datatracker, bang on it, kick the tires, and =
generally see if it works as well for you as the old one.
>>=20
>> For some additional insight, you may want to read the instructions =
that was given to our testers:
>> http://trac.tools.ietf.org/tools/ietfdb/wiki/InstructionsForTesters
>>=20
>> Or, you may want to just jump in and see how it works.  Either way, =
please report any bugs, problems, surprises, gremlins, hiccups, flaws, =
and so on that you discover.  Reports will receive prompt attention.  We =
deploy new code upgrades (if any are available) every hour. Please use =
this mail list to report issues:
>> iola-conversion-tool@ietf.org
>>=20
>> Try out the new Datatracker, and help us make a smooth transition.  =
The new Datatracker is running here:
>> https://trackerbeta.ietf.org/
>>=20
>> Thank you for your assistance,
>> Russ
>=20


From spromano@unina.it  Tue Feb 28 05:40:23 2012
Return-Path: <spromano@unina.it>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6770F21F85BB; Tue, 28 Feb 2012 05:40:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.119
X-Spam-Level: 
X-Spam-Status: No, score=-98.119 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CsJXkKEb1SQX; Tue, 28 Feb 2012 05:40:22 -0800 (PST)
Received: from smtp1.unina.it (smtp1.unina.it [192.132.34.61]) by ietfa.amsl.com (Postfix) with ESMTP id 6113121F8516; Tue, 28 Feb 2012 05:40:22 -0800 (PST)
Received: from [143.225.229.230] ([143.225.229.230]) (authenticated bits=0) by smtp1.unina.it (8.14.4/8.14.4) with ESMTP id q1SDe7LO027098 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 28 Feb 2012 14:40:09 +0100
Message-ID: <4F4CD936.2020402@unina.it>
Date: Tue, 28 Feb 2012 14:40:06 +0100
From: Simon Pietro Romano <spromano@unina.it>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Dave CROCKER <dcrocker@bbiw.net>
Subject: Moderation experiment at IETF83 [Was: Re: Getting Taipei remote participants' input]
References: <47A5416C-33BF-44FB-B01B-D1FE59808AAD@vpnc.org> <CAC4RtVCdULyZ=-gp_tThMhwGYcMt81J32DUG0+NLHjP+26vF2A@mail.gmail.com> <4ECD1254.9010901@bbiw.net> <2247A63F-FF4C-43C4-AE16-6884B44C4A29@brianrosen.net> <4ECD21A1.5020003@bbiw.net> <C8429466-0E82-4C30-B5F0-FBB13E641130@brianrosen.net> <4ECD2B41.5090702@bbiw.net> <4ECD468D.80402@unina.it> <4ECFF5CA.4000903@bbiw.net>
In-Reply-To: <4ECFF5CA.4000903@bbiw.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailman-Approved-At: Tue, 28 Feb 2012 09:12:07 -0800
Cc: IETF WG chairs <wgchairs@ietf.org>, Simon Pietro Romano <spromano@unina.it>, Ray Pelletier <raypelletier@mac.com>, 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: Tue, 28 Feb 2012 13:40:23 -0000

Dear all,

I'm resuming this old thread since I would like to announce a new 
project/experiment we are going to propose at the upcoming IETF in Paris.
I put some documentation on-line, in order to clearly explain what we 
are talking about. You can access it at the following URL:

http://ietf83.conf.meetecho.com/index.php/UMPIRE_Project

I am putting the vmeet mailing list in CC:, because I think the subject 
is of interest to them.

Cheers,

Simon

Il 25/11/2011 21:08, Dave CROCKER ha scritto:
>
>
> On 11/23/2011 11:16 AM, Simon Pietro Romano wrote:
>> Hi Dave,
>>
>>> If you mean aggregating the set of folk at all the mics and taking 
>>> them in the
>>> strict order of their coming to the (single) queue, that doesn't 
>>> work on
>>> average, unless the queue is tiny. The chair can't keep track of who 
>>> arrived
>>> to the queue and when.
>>
>> I personally like Brian's idea, and think the all thing might work 
>> smoothly if
>> you make use of a tool capable to automatically collect and moderate 
>> floor
>> requests, to be put in a (virtual) single queue. What I'm thinking of 
>> is RFIDs
>> triggering BFCP (Binary Floor Control Protocol) requests,
>
>
> An interesting challenge, for Paul's current contract, is to find a 
> way to navigate between what the community wants, versus what is 
> practical.  The fact that we are a group of engineers means that we 
> tend to try to solve the problem, before agreeing on what problem we 
> want to solve...
>
> Suggestions like the above sound appealing.  Unfortunately, they are 
> far beyond current products and making them useful is considerably 
> more difficult than the suggestions imply.  That doesn't mean they 
> should be ignored, but we need to be careful about slipping into the 
> assumption that merely citing a bit of technology means that an issue 
> is resolved.
>
> We had an experiment with RFIDs.  It was awkward, at best.  In 
> addition, it was extremely limited.  Only the person standing right 
> next to the microphone could be identified.  For example, this means 
> that it would not have been useful for identifying when someone 
> /enters/ the queue.  Too far away.
>
> So if folks are going to attempt to define the technical solution, at 
> least please try to indicate how it would work throughout the 
> requirement.
>
> In the case of queue management, we have at least entering the queue, 
> position in the queue, and the chair's control of the queue.  No 
> doubt, there's even more complexity than that.  For example, there's 
> "noise" such as someone walking by the queue but not entering it...
>
> d/

-- 
                             _\\|//_
                             ( O-O )
    ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
                     Simon Pietro Romano
               Universita' di Napoli Federico II
                  Computer Science Department
         Phone: +39 081 7683823 -- Fax: +39 081 7684219
                 e-mail: spromano@unina.it
           http://www.comics.unina.it/simonpietro.romano

     <<Molti mi dicono che lo scoraggiamento è l'alibi degli
    idioti. Ci rifletto un istante; e mi scoraggio>>. Magritte.
                          oooO
    ~~~~~~~~~~~~~~~~~~~~~~(   )~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
                           \ (    (   )
                            \_)    ) /
                                  (_/



From iad@ietf.org  Wed Feb 29 07:43:56 2012
Return-Path: <iad@ietf.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D56C821F871B; Wed, 29 Feb 2012 07:43:56 -0800 (PST)
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 yzKmuuKSizzP; Wed, 29 Feb 2012 07:43:56 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F30121F8718; Wed, 29 Feb 2012 07:43:56 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Administrative Director <iad@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: RFI:  Agenda Tool
X-Test-IDTracker: no
X-IETF-IDTracker: 4.00
Message-ID: <20120229154356.16678.32244.idtracker@ietfa.amsl.com>
Date: Wed, 29 Feb 2012 07:43:56 -0800
Cc: iaoc@ietf.org, wgchairs@ietf.org, tools-development@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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, 29 Feb 2012 15:43:57 -0000

This is a Request for Information (RFI).  The purpose of this RFI is to obt=
ain feedback from the IETF community on the Statement of Work (SOW), identi=
fy potential suppliers and developers for an IETF Meeting Agenda Creation T=
ool, and to seek comments on the (SOW) from such suppliers/developers to in=
form the preparation of a possible RFP. =


The IETF Meeting Agenda Creation Tool will manage all meeting scheduling an=
d space allocation associated with regular IETF meetings. These meetings oc=
cur three times a year, take place over 7 days with between 250 and 300 dis=
tinct sessions each, between 8 and 12 of these sessions taking place concur=
rently.  Currently the scheduling is being done manually by the IETF Secret=
ariat. =


Examples of the IETF Meeting schedule for IETF 82 meeting in Taipei can be =
found here:
	https://datatracker.ietf.org/meeting/82/agenda.html
	https://datatracker.ietf.org/meeting/82/agenda.txt
	http://tools.ietf.org/agenda/82/

The RFI can be found at: http://iaoc.ietf.org/rfpsrfis.html

Expressions of interest from potential bidders and all SOW comments are due=
 by 27 March 2012 and should be submitted to agenda-tool@ietf.org.  See the=
 RFI for more details.

Questions about this RFI can be addressed to agenda-tool@ietf.org by 9 Marc=
h 2012.
All questions and answers will be posted on the website at http://iaoc.ietf=
.org/rfpsrfis.html.
The identity of the question's originator will not be disclosed.

All information submitted in response to this announcement is voluntary and=
 may be used in the development of the RFP.

Ray Pelletier
IETF Administrative Director

From amorris@amsl.com  Wed Feb 29 13:26:32 2012
Return-Path: <amorris@amsl.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9B1221F8659 for <wgchairs@ietfa.amsl.com>; Wed, 29 Feb 2012 13:26:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.917
X-Spam-Level: 
X-Spam-Status: No, score=-1.917 tagged_above=-999 required=5 tests=[AWL=0.682,  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 vpWcdQH6-Wy5 for <wgchairs@ietfa.amsl.com>; Wed, 29 Feb 2012 13:26:32 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 3314B21F8657 for <wgchairs@ietf.org>; Wed, 29 Feb 2012 13:26:32 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 1E7BB12C659 for <wgchairs@ietf.org>; Wed, 29 Feb 2012 13:26:32 -0800 (PST)
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 IhC++ztldPOK for <wgchairs@ietf.org>; Wed, 29 Feb 2012 13:26:32 -0800 (PST)
Received: from [192.168.0.195] (c-76-102-55-37.hsd1.ca.comcast.net [76.102.55.37]) by c8a.amsl.com (Postfix) with ESMTPSA id EB97E12C641 for <wgchairs@ietf.org>; Wed, 29 Feb 2012 13:26:31 -0800 (PST)
From: Alexa Morris <amorris@amsl.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Blue Sheet PDF for Face-to-Face Interim Meetings
Date: Wed, 29 Feb 2012 13:26:06 -0800
Message-Id: <8895C4A0-C577-4660-A4F6-0FB805552AD5@amsl.com>
To: Working Group Chairs <wgchairs@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
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: Wed, 29 Feb 2012 21:26:33 -0000

WG Chairs,=20

It was recently brought to our attention that every time there is a =
face-to-face interim meeting, the WG Chair has to create their own =
meeting blue sheet from memory. So we've created a blank PDF template =
that is now available for download from the WG Chair's  page, under =
Meeting Tools. Here is a direct link to the PDF: =
http://www.ietf.org/wg/documents/interim-meeting-blue-sheet.pdf.

Regards,
Alexa

----------
Alexa Morris / Executive Director / IETF
48377 Fremont Blvd., Suite 117, Fremont, CA  94538
Phone: +1.510.492.4089 / Fax: +1.510.492.4001
Email: amorris@amsl.com

Managed by Association Management Solutions (AMS)
Forum Management, Meeting and Event Planning
www.amsl.com <http://www.amsl.com/>


From housley@vigilsec.com  Wed Feb 29 14:02:07 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 5809321E8070 for <wgchairs@ietfa.amsl.com>; Wed, 29 Feb 2012 14:02:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.55
X-Spam-Level: 
X-Spam-Status: No, score=-102.55 tagged_above=-999 required=5 tests=[AWL=0.049, 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 4hvEfs7uKqJZ for <wgchairs@ietfa.amsl.com>; Wed, 29 Feb 2012 14:02:06 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 770B121F8642 for <wgchairs@ietf.org>; Wed, 29 Feb 2012 14:02:06 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 1AC45F24035; Wed, 29 Feb 2012 17:02:30 -0500 (EST)
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 PBGrCiMx7ZV0; Wed, 29 Feb 2012 17:01:31 -0500 (EST)
Received: from [192.168.2.104] (pool-96-241-165-215.washdc.fios.verizon.net [96.241.165.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id D7C6FF24010; Wed, 29 Feb 2012 17:02:28 -0500 (EST)
Subject: Re: Blue Sheet PDF for Face-to-Face Interim Meetings
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/signed; boundary=Apple-Mail-66-58405912; protocol="application/pkcs7-signature"; micalg=sha1
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <8895C4A0-C577-4660-A4F6-0FB805552AD5@amsl.com>
Date: Wed, 29 Feb 2012 17:02:03 -0500
Message-Id: <B71DFF30-A256-4B85-94E2-9801EA08EAE6@vigilsec.com>
References: <8895C4A0-C577-4660-A4F6-0FB805552AD5@amsl.com>
To: Alexa Morris <amorris@amsl.com>
X-Mailer: Apple Mail (2.1084)
Cc: Working Group Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Feb 2012 22:02:07 -0000

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

Alexa:

I think the Mail List is not important for this sheet, but it is at the =
top of each page.  Can you please change that to WG name.

Russ


On Feb 29, 2012, at 4:26 PM, Alexa Morris wrote:

> WG Chairs,=20
>=20
> It was recently brought to our attention that every time there is a =
face-to-face interim meeting, the WG Chair has to create their own =
meeting blue sheet from memory. So we've created a blank PDF template =
that is now available for download from the WG Chair's  page, under =
Meeting Tools. Here is a direct link to the PDF: =
http://www.ietf.org/wg/documents/interim-meeting-blue-sheet.pdf.
>=20
> Regards,
> Alexa
>=20
> ----------
> Alexa Morris / Executive Director / IETF
> 48377 Fremont Blvd., Suite 117, Fremont, CA  94538
> Phone: +1.510.492.4089 / Fax: +1.510.492.4001
> Email: amorris@amsl.com
>=20
> Managed by Association Management Solutions (AMS)
> Forum Management, Meeting and Event Planning
> www.amsl.com <http://www.amsl.com/>
>=20


--Apple-Mail-66-58405912
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIILsTCCBXcw
ggRfoAMCAQICEQC/HkHRL9TErrj9ADkdlht/MA0GCSqGSIb3DQEBBQUAMIGuMQswCQYDVQQGEwJV
UzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUgVVNF
UlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQGA1UE
AxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsMB4XDTExMDIy
MzAwMDAwMFoXDTEyMDIyMzIzNTk1OVowJTEjMCEGCSqGSIb3DQEJARYUaG91c2xleUB2aWdpbHNl
Yy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCw0MgZJ40HVA6CN9jGwA0pudBn
0OQT8816EBgpVzV5X3DTnf8roF3vTPNTfZyuyuaDcZADMhmuZ7blVxN2lVlaHmY+WTJZkcvkFwGU
FX2X8lAyBc4I1+J7oSpupF2X8nHW6W7/QvYHD6lxMNssB0/ma/z+5QuE+ypnCEJdbeDbGcipdjXl
wXCBYbIRTQmEzec5VuPZAxVtpMehL+dNyG2xc5q9viXm0eYKdlLmegcFpPTa0CwWUpnMhXjAUUl4
1k4GJnyX4INEL7JJnCkhHPJYKbOsoMwtV4/8D8nIJSz7R4VcRQo0Sq+0ENMrwLZai7LIBflq691Q
fONyCvWvjg3fAgMBAAGjggIWMIICEjAfBgNVHSMEGDAWgBSJgmd9xJ0mcABLtFBIfN49rgRufTAd
BgNVHQ4EFgQUaZfWeIVDGMaHXO9NcMRXavC7TLIwDgYDVR0PAQH/BAQDAgWgMAwGA1UdEwEB/wQC
MAAwIAYDVR0lBBkwFwYIKwYBBQUHAwQGCysGAQQBsjEBAwUCMBEGCWCGSAGG+EIBAQQEAwIFIDBG
BgNVHSAEPzA9MDsGDCsGAQQBsjEBAgEBATArMCkGCCsGAQUFBwIBFh1odHRwczovL3NlY3VyZS5j
b21vZG8ubmV0L0NQUzCBpQYDVR0fBIGdMIGaMEygSqBIhkZodHRwOi8vY3JsLmNvbW9kb2NhLmNv
bS9VVE4tVVNFUkZpcnN0LUNsaWVudEF1dGhlbnRpY2F0aW9uYW5kRW1haWwuY3JsMEqgSKBGhkRo
dHRwOi8vY3JsLmNvbW9kby5uZXQvVVROLVVTRVJGaXJzdC1DbGllbnRBdXRoZW50aWNhdGlvbmFu
ZEVtYWlsLmNybDBsBggrBgEFBQcBAQRgMF4wNgYIKwYBBQUHMAKGKmh0dHA6Ly9jcnQuY29tb2Rv
Y2EuY29tL1VUTkFBQUNsaWVudENBLmNydDAkBggrBgEFBQcwAYYYaHR0cDovL29jc3AuY29tb2Rv
Y2EuY29tMB8GA1UdEQQYMBaBFGhvdXNsZXlAdmlnaWxzZWMuY29tMA0GCSqGSIb3DQEBBQUAA4IB
AQAakko5qXz1U0VWMkiuo+bNCY3QEsM55vIqJujM+c3romvLuBVnDk+ZQ/MjyCrrJ8acR3bFCQGn
r+9+rV/cxLcZCxFUDuUhucaSxlu82N3/75fi1JFe/ZByJJW80U/oY6xnmNUX8S5tQ/+tmr/JpysO
h68BU/qKagXUvDlMVHwSrumBzbG84+/SBMYx4ZB4KgtiL0EaqzKiqLMtjQrGLeSe02A0OoIwRoeY
CzGojMjPHjv9GfvBGNUDXDhB+GiiDK+zT9O65KulkuDHB9A14nYQtXihcaAE9bXRPBjDy1zEZ7kf
XolnnBjx/eokmW7aXnfL/h+a3pLwvu2Hf7xqbTmBMIIGMjCCBRqgAwIBAgIRAPlSTAWGMcizpMWm
2QlLHJUwDQYJKoZIhvcNAQEFBQAwga4xCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJVVDEXMBUGA1UE
BxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VSVFJVU1QgTmV0d29yazEhMB8GA1UE
CxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQDEy1VVE4tVVNFUkZpcnN0LUNsaWVu
dCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwwHhcNMTAwMjAzMDAwMDAwWhcNMTEwMjAzMjM1OTU5
WjCB3zE1MDMGA1UECxMsQ29tb2RvIFRydXN0IE5ldHdvcmsgLSBQRVJTT05BIE5PVCBWQUxJREFU
RUQxRjBEBgNVBAsTPVRlcm1zIGFuZCBDb25kaXRpb25zIG9mIHVzZTogaHR0cDovL3d3dy5jb21v
ZG8ubmV0L3JlcG9zaXRvcnkxHzAdBgNVBAsTFihjKTIwMDMgQ29tb2RvIExpbWl0ZWQxGDAWBgNV
BAMTD1J1c3NlbGwgSG91c2xleTEjMCEGCSqGSIb3DQEJARYUaG91c2xleUB2aWdpbHNlYy5jb20w
ggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDkDJiuAzx+GtqFd70PIDnK20dakNcZrKlG
9QYt/vLNZsWpLfuM4kXNB49NncHWjQGjMPHMt/EY6bLeTBng29TudqfCNU2qsrzzNwTNAPMwtBk3
p27PvH/nKFSOtaGz6ccpCaIVXRs1IM5KnbnV1c1n0vOiHB6HF6bzqePLGB/KBq6ROvRkgqJ82tWJ
PUkTpNa/w/i8SY6lmt0NE/OBSv9dFoYUYXpsWhUCxD1ol/t7rR+V1R3Zz4l8uponXP0+3SRD/WIy
yM3faRevacpiaYDtr0+aXf1yIOhm8DGifdyr9tdmv2wevcUfQhLrvpeqVAxsWDrVArfeSf0mfxV0
N7oRAgMBAAGjggIWMIICEjAfBgNVHSMEGDAWgBSJgmd9xJ0mcABLtFBIfN49rgRufTAdBgNVHQ4E
FgQUWHQSO3dEI5rhPq2etL1YBi8MemMwDgYDVR0PAQH/BAQDAgWgMAwGA1UdEwEB/wQCMAAwIAYD
VR0lBBkwFwYIKwYBBQUHAwQGCysGAQQBsjEBAwUCMBEGCWCGSAGG+EIBAQQEAwIFIDBGBgNVHSAE
PzA9MDsGDCsGAQQBsjEBAgEBATArMCkGCCsGAQUFBwIBFh1odHRwczovL3NlY3VyZS5jb21vZG8u
bmV0L0NQUzCBpQYDVR0fBIGdMIGaMEygSqBIhkZodHRwOi8vY3JsLmNvbW9kb2NhLmNvbS9VVE4t
VVNFUkZpcnN0LUNsaWVudEF1dGhlbnRpY2F0aW9uYW5kRW1haWwuY3JsMEqgSKBGhkRodHRwOi8v
Y3JsLmNvbW9kby5uZXQvVVROLVVTRVJGaXJzdC1DbGllbnRBdXRoZW50aWNhdGlvbmFuZEVtYWls
LmNybDBsBggrBgEFBQcBAQRgMF4wNgYIKwYBBQUHMAKGKmh0dHA6Ly9jcnQuY29tb2RvY2EuY29t
L1VUTkFBQUNsaWVudENBLmNydDAkBggrBgEFBQcwAYYYaHR0cDovL29jc3AuY29tb2RvY2EuY29t
MB8GA1UdEQQYMBaBFGhvdXNsZXlAdmlnaWxzZWMuY29tMA0GCSqGSIb3DQEBBQUAA4IBAQAW8//a
ejmI7TFKF7PqD3nKBMMnB84jXWhjhycrnuEA1eEs1bjOvbRNz+mMoJPDPIxnR8ZG0Iv5IJrnQjjq
6R4NV1QoVVg7gS+lNGnGU+wk+PfCFsuNlIj22qaJGLd0RHzA2Oz++LN54XVzV77HROK7jL3kciR4
F40s2fAQRz6gqMydwRbYXL+B0VlbYAkf/D7efkkPJC2nijRWZCqmxTjF/IeJgSJVZiZ8InJ9egvr
XiZ1JCbAqq367wSypv1ByxXVFjHXCHEcPsCuicFKnlOkfDHNwKluVrw1EJf0NYh2iuk3TKC1t8us
XcgsLpJy1XFM+gL4wAAAftz8eeShQTfoMYID/zCCA/sCAQEwgcQwga4xCzAJBgNVBAYTAlVTMQsw
CQYDVQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VSVFJV
U1QgTmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQDEy1V
VE4tVVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwCEQC/HkHRL9TErrj9
ADkdlht/MAkGBSsOAwIaBQCgggIPMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcN
AQkFMQ8XDTEyMDIyOTIyMDIwNFowIwYJKoZIhvcNAQkEMRYEFJdo5QPncRV0UlZ+wgDOYTHU4idQ
MIHVBgkrBgEEAYI3EAQxgccwgcQwga4xCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJVVDEXMBUGA1UE
BxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VSVFJVU1QgTmV0d29yazEhMB8GA1UE
CxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQDEy1VVE4tVVNFUkZpcnN0LUNsaWVu
dCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwCEQD5UkwFhjHIs6TFptkJSxyVMIHXBgsqhkiG9w0B
CRACCzGBx6CBxDCBrjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExh
a2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8v
d3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVUTi1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRp
Y2F0aW9uIGFuZCBFbWFpbAIRAPlSTAWGMcizpMWm2QlLHJUwDQYJKoZIhvcNAQEBBQAEggEAaUbW
2CI6O8jcdKehXkC33b/w9fHTo4zL50YeDX6ZTK2gddpsllHR5HeOSn++MUiTx3/s1gtMMTwk+zLu
3ghIj1AUaBwZ0azNH1TrlZVeNOvx6PLU/ylbaVevPH1K0Rbd+HjlN2skfMJDRRRL0UKqQGnxcku9
9c79AjzC9FlJwVGzH6LU4SNs3RkqMY54jYWlFn+RyLuIGNFszX8wUcCqvF6TdBzqbjJ5y5GFHSWD
QtPn5SfLZUmTAjQtFwJ1k613uejjpczABToqkEigxanqV7zjryxdBkzMOYH1iHc9UCeY3cjZUtEd
1lmQoTBt9Zc1DTVObR2MIvpOjbR6ExVXRAAAAAAAAA==

--Apple-Mail-66-58405912--

From pkyzivat@alum.mit.edu  Wed Feb 29 16:31:21 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 777F221F861A for <wgchairs@ietfa.amsl.com>; Wed, 29 Feb 2012 16:31:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.582
X-Spam-Level: 
X-Spam-Status: No, score=-2.582 tagged_above=-999 required=5 tests=[AWL=0.017,  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 AVvJVjmWMfcF for <wgchairs@ietfa.amsl.com>; Wed, 29 Feb 2012 16:31:21 -0800 (PST)
Received: from qmta01.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [76.96.62.24]) by ietfa.amsl.com (Postfix) with ESMTP id D75E021F853C for <wgchairs@ietf.org>; Wed, 29 Feb 2012 16:31:20 -0800 (PST)
Received: from omta13.westchester.pa.mail.comcast.net ([76.96.62.52]) by qmta01.westchester.pa.mail.comcast.net with comcast id g0Uh1i00317dt5G510XMly; Thu, 01 Mar 2012 00:31:21 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([24.62.229.5]) by omta13.westchester.pa.mail.comcast.net with comcast id g0XL1i00N07duvL3Z0XLK4; Thu, 01 Mar 2012 00:31:21 +0000
Message-ID: <4F4EC356.4060904@alum.mit.edu>
Date: Wed, 29 Feb 2012 19:31:18 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: Blue Sheet PDF for Face-to-Face Interim Meetings
References: <8895C4A0-C577-4660-A4F6-0FB805552AD5@amsl.com>
In-Reply-To: <8895C4A0-C577-4660-A4F6-0FB805552AD5@amsl.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: Thu, 01 Mar 2012 00:31:21 -0000

On 2/29/12 4:26 PM, Alexa Morris wrote:
> WG Chairs,
>
> It was recently brought to our attention that every time there is a face-to-face interim meeting, the WG Chair has to create their own meeting blue sheet from memory. So we've created a blank PDF template that is now available for download from the WG Chair's  page, under Meeting Tools. Here is a direct link to the PDF: http://www.ietf.org/wg/documents/interim-meeting-blue-sheet.pdf.

I think this template is not likely to be of use very often, unless I 
just print a bunch and carry them around all the time. There is slim 
chance I'll remember (and being in a place where I can) print one before 
a particular interim meeting.

So how important is the template? How much of what is on it is 
necessary? Isn't WG name, date, and list of names and emails enough?

	Thanks,
	Paul

From Sandra.Murphy@sparta.com  Wed Feb 29 21:51:16 2012
Return-Path: <Sandra.Murphy@sparta.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2DEF21E8017 for <wgchairs@ietfa.amsl.com>; Wed, 29 Feb 2012 21:51:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.322
X-Spam-Level: 
X-Spam-Status: No, score=-102.322 tagged_above=-999 required=5 tests=[AWL=0.277, 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 hpjPgDZyCxfO for <wgchairs@ietfa.amsl.com>; Wed, 29 Feb 2012 21:51:13 -0800 (PST)
Received: from M4.sparta.com (M4.sparta.com [157.185.61.2]) by ietfa.amsl.com (Postfix) with ESMTP id A525C21E801E for <wgchairs@ietf.org>; Wed, 29 Feb 2012 21:51:06 -0800 (PST)
Received: from Beta5.sparta.com (beta5.sparta.com [157.185.63.21]) by M4.sparta.com (8.14.4/8.14.4) with ESMTP id q215p4Ph000970; Wed, 29 Feb 2012 23:51:04 -0600
Received: from Hermes.columbia.ads.sparta.com ([157.185.80.107]) by Beta5.sparta.com (8.13.8/8.13.8) with ESMTP id q215p4vr014351; Wed, 29 Feb 2012 23:51:04 -0600
Received: from HERMES.columbia.ads.sparta.com ([2002:9db9:506b::9db9:506b]) by Hermes.columbia.ads.sparta.com ([2002:9db9:506b::9db9:506b]) with mapi id 14.01.0355.002; Thu, 1 Mar 2012 00:51:03 -0500
From: "Murphy, Sandra" <Sandra.Murphy@sparta.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "wgchairs@ietf.org" <wgchairs@ietf.org>
Subject: RE: Blue Sheet PDF for Face-to-Face Interim Meetings
Thread-Topic: Blue Sheet PDF for Face-to-Face Interim Meetings
Thread-Index: AQHM9yjR8ztTo+NAq0W/NaN8/euSmJZU6rwAgAAD3Y8=
Date: Thu, 1 Mar 2012 05:51:02 +0000
Message-ID: <24B20D14B2CD29478C8D5D6E9CBB29F60F6AE360@Hermes.columbia.ads.sparta.com>
References: <8895C4A0-C577-4660-A4F6-0FB805552AD5@amsl.com>, <4F4EC356.4060904@alum.mit.edu>
In-Reply-To: <4F4EC356.4060904@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.185.63.118]
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: Thu, 01 Mar 2012 05:51:16 -0000

I can see a couple of things that I did not include in the self-generated v=
ersion I recently composed.  I did not include the chair name, for example.

One quibble.  The template says: "The NOTE WELL statement included in your =
registration packet applies to this meeting."  What registration packet?  I=
s that a mistaken holdover from the typcial IETF meeting format?  If not, a=
re those holding interim meetings supposed to supply a registration packet?=
  Couldn't we just put the NOTE WELL on the blue sheet?

--Sandy

________________________________________
From: wgchairs-bounces@ietf.org [wgchairs-bounces@ietf.org] on behalf of Pa=
ul Kyzivat [pkyzivat@alum.mit.edu]
Sent: Wednesday, February 29, 2012 7:31 PM
To: wgchairs@ietf.org
Subject: Re: Blue Sheet PDF for Face-to-Face Interim Meetings

On 2/29/12 4:26 PM, Alexa Morris wrote:
> WG Chairs,
>
> It was recently brought to our attention that every time there is a face-=
to-face interim meeting, the WG Chair has to create their own meeting blue =
sheet from memory. So we've created a blank PDF template that is now availa=
ble for download from the WG Chair's  page, under Meeting Tools. Here is a =
direct link to the PDF: http://www.ietf.org/wg/documents/interim-meeting-bl=
ue-sheet.pdf.

I think this template is not likely to be of use very often, unless I
just print a bunch and carry them around all the time. There is slim
chance I'll remember (and being in a place where I can) print one before
a particular interim meeting.

So how important is the template? How much of what is on it is
necessary? Isn't WG name, date, and list of names and emails enough?

        Thanks,
        Paul=
