
From adrian@olddog.co.uk  Fri Jan  3 07:19:34 2014
Return-Path: <adrian@olddog.co.uk>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01AD11ADFDF for <wgchairs@ietfa.amsl.com>; Fri,  3 Jan 2014 07:19:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.553
X-Spam-Level: 
X-Spam-Status: No, score=-0.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_BL_SPAMCOP_NET=1.347, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yUkmqBx84L6z for <wgchairs@ietfa.amsl.com>; Fri,  3 Jan 2014 07:19:32 -0800 (PST)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id A922D1ADFD0 for <wgchairs@ietf.org>; Fri,  3 Jan 2014 07:19:31 -0800 (PST)
Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id s03FJNWr021110 for <wgchairs@ietf.org>; Fri, 3 Jan 2014 15:19:23 GMT
Received: from 950129200 (108.26.90.92.rev.sfr.net [92.90.26.108]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id s03FJJ2I021088 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <wgchairs@ietf.org>; Fri, 3 Jan 2014 15:19:22 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <wgchairs@ietf.org>
References: <20140103151454.20579.95323.idtracker@ietfa.amsl.com>
In-Reply-To: <20140103151454.20579.95323.idtracker@ietfa.amsl.com>
Subject: FW: Last Call: <draft-crocker-id-adoption-05.txt> (Creating an IETF Working Group Draft) to Informational RFC
Date: Fri, 3 Jan 2014 15:19:21 -0000
Message-ID: <01c301cf0897$2fd44c80$8f7ce580$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIFTM6SDdVHGdKJzgR8rc9+dAejqpoGlH9Q
Content-Language: en-gb
X-TM-AS-MML: No
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jan 2014 15:19:34 -0000

Hi WG chairs,

I know you were (selectively) interested in this as it was being written.

Be aware of the last call.

Thanks,
Adrian (and probably Dave)

> -----Original Message-----
> From: IETF-Announce [mailto:ietf-announce-bounces@ietf.org] On Behalf Of The
> IESG
> Sent: 03 January 2014 15:15
> To: IETF-Announce
> Subject: Last Call: <draft-crocker-id-adoption-05.txt> (Creating an IETF
Working
> Group Draft) to Informational RFC
> 
> 
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Creating an IETF Working Group Draft'
>   <draft-crocker-id-adoption-05.txt> as Informational RFC
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2014-01-31. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> Abstract
> 
> 
>    The productive output of an IETF working group is documents, as
>    mandated by the working group's charter.  When a working group is
>    ready to develop a particular document, the most common mechanism is
>    for it to "adopt" an existing document as a starting point.  The
>    document that a working group adopts and then develops further is
>    based on initial input at varying levels of maturity.  An initial
>    working group draft might be a document already in wide use, or it
>    might be a blank sheet, wholly created by the working group, or it
>    might represent any level of maturity in between.  This document
>    discusses how a working group typically handles the formal documents
>    that it targets for publication.
> 
> 
> 
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-crocker-id-adoption/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-crocker-id-adoption/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.



From agenda@ietf.org  Mon Jan  6 14:42:04 2014
Return-Path: <agenda@ietf.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF9ED1AE2A2; Mon,  6 Jan 2014 14:42:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.8
X-Spam-Level: 
X-Spam-Status: No, score=0.8 tagged_above=-999 required=5 tests=[BAYES_50=0.8] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8NPH3WKKDT5K; Mon,  6 Jan 2014 14:42:02 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 212461AE29A; Mon,  6 Jan 2014 14:42:02 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Agenda <agenda@ietf.org>
To: Working Group Chairs <wgchairs@ietf.org>
Subject: 89th IETF - Working Group/BOF/IRTF Scheduling - REMINDER
X-Test-IDTracker: no
X-IETF-IDTracker: 4.90.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140106224201.21858.37999.idtracker@ietfa.amsl.com>
Date: Mon, 06 Jan 2014 14:42:01 -0800
Cc: irsg@irtf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: IETF Agenda <agenda@ietf.org>
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jan 2014 22:42:05 -0000

-----------------------------------------------------------------
89th IETF =E2=80=93 London, England
Meeting Dates: March 2 =E2=80=93 7, 2014
-----------------------------------------------------------------
IETF meetings start Monday morning and run through Friday afternoon (13:30).

The milestones and deadlines for scheduling-related activities are as follo=
ws:

NOTE: cutoff dates are subject to change.

=E2=80=A2	2014-01-17 (Friday): Cut-off date for requests to schedule Workin=
g Group meetings at UTC 23:59. To request a Working Group session, use the =
IETF Meeting Session Request Tool.
=E2=80=A2	2014-01-17 (Friday): Cut-off date for BOF proposal requests to Ar=
ea Directors at UTC 23:59. To request a BOF, please see instructions on Req=
uesting a BOF.
=E2=80=A2	2014-01-24 (Friday): Cut-off date for Area Directors to approve B=
OFs at UTC 23:59.
=E2=80=A2	2014-01-31 (Friday): Preliminary agenda published for comment.
=E2=80=A2	2014-02-03 (Monday): Cut-off date for requests to reschedule Work=
ing Group and BOF meetings UTC 23:59.
=E2=80=A2	2014-02-07 (Friday): Final agenda to be published.
=E2=80=A2	2014-02-17 (Monday): Draft Working Group agendas due by UTC 23:59=
, upload using IETF Meeting Materials Management Tool.
=E2=80=A2	2014-02-24 (Monday): Revised Working Group agendas due by UTC 23:=
59, upload using IETF Meeting Materials Management Tool.
=E2=80=A2	2014-03-28 (Friday): Proceedings submission cutoff date by UTC 23=
:59, upload using IETF Meeting Materials Management Tool.
=E2=80=A2	2014-04-18 (Friday): Proceedings submission corrections cutoff da=
te by UTC 23:59, upload using IETF Meeting Materials Management Tool.

Submitting Requests for Working Group and BOF Sessions

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

The URL for the tool is:

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

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

Submitting Session Agendas

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

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

The URL for the tool is:

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

Additional information about this tool is available at:

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

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

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

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

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

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

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

Instructions for using the tool are available at:

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

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

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

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

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

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

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

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


    b. AREA under which Working Group or BOF appears:

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

    d. Expected Attendance:

    e. Special requests:

    f. Number of sessions:

    g. Length of session: =

       - 1 hour =

       - 1 1/2 hours
       - 2 hours =

       - 2 1/2 hours

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

IETF Chair =

Jari Arkko <jari.arkko@piuha.net>

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

Internet Area (int) =

Brian Haberman <brian@innovationslab.net> =

Ted Lemon <ted.lemon@nominum.com>

Operations & Management Area (ops) =

Benoit Claise <bclaise@cisco.com> =

Joel Jaeggli <joelja@bogus.com>

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


Routing Area (rtg) =

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


Security Area (sec) =

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


Transport Area (tsv) =

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

Spencer Dawkins  <spencerdawkins.ietf@gmail.com>
 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
88th IETF Meeting Attendance Numbers

6lo - 52
6man - 143
6tisch - 45
abfab - 20
alto  - 35
appsawg/apparea - 138
aqm - 108
aqm (2nd session) - 45
avtcore - 51
avtext =E2=80=93 59
bfd - 17
bmwg - 19
ccamp - 49
ccamp (2nd session) - 44
cdni - 39
clue - 41
clue (2nd session) - 32
core - 62
core (2nd session) - 50
dhc - 59
dice - 65
dime - 23
dispatch - 55
dmm - 37
dnsop - 125
dnssd - 108
ecrit - 31
eman - 19
forces - 40
geonet (BoF) - 99
geopriv - 41
homenet - 156
httpauth - 43
httpbis - 89
httpbis (2nd session) - 127
i2rs - 223
iccrg (RG) - 68
icnrg (RG) - 43
idr - 90
igovupdate BoF - 220
insipid - 32
intarea (AG) - 98
ipfix - 23
ippm - 48
ipsecme - 27
IRTF Open Meeting - 100
isis - 58
jose - 42
json - 49
karp - 22
kitten - 23
l2vpn - 71
l3vpn - 65
lisp - 56
lmap - 52
lwig - 35
manet - 35
mboned - 25
mif - 41
mmusic - 69
mmusic (2nd session) - 53
mpls - 71
mpls (2nd session) - 72
mptcp - 45
mptcp (2nd session) - 70
ncrg (RG) - 33
netconf - 62
netext - 27
netmod - 69
nfsv4 - 16
nmrg (RG) - 35
nmrg (RG) (2nd session) - 17
ntp (combined with tictoc) - 32
nvo3 - 193
nwcrg (PRG) - 25
oauth - 38
opsawg/opsarea - 68
opsec - 48
ospf - 38
paws - 17
pce - 72
pcp - 30
perpass (BoF) - 313
pim - 24
ppsp - 12
precis - 32
pwe3 - 40
radext - 20
rfcform (BoF) - 52
rmcat - 60
rtcweb - 174
rtcweb (2nd session) - 188
rtgarea (AG) - 101
rtgwg - 118
saag (AG) - 148
sacm - 40
scim - 32
sdnrg (RG) - 259
sidr - 61
siprec - 31
softwire - 52
spring - 158
stir - 82
stir (2nd session) - 79
storm - 21
tcpm - 36
tictoc (combined with ntp) - 32
tls - 111
trill - 33
tsvarea (AG) - 153
tsvwg - 63
tsvwg (2nd session) - 47
v6ops - 135
v6ops (2nd session) - 92
weirds - 55
wpkops - 34
xmpp - 31
xrblock - 24

From fluffy@cisco.com  Wed Jan  8 11:14:02 2014
Return-Path: <fluffy@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 448191AE06D; Wed,  8 Jan 2014 11:14:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.039
X-Spam-Level: 
X-Spam-Status: No, score=-110.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RFRcfGv3_2Oe; Wed,  8 Jan 2014 11:14:00 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) by ietfa.amsl.com (Postfix) with ESMTP id 24A221AE069; Wed,  8 Jan 2014 11:14:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1097; q=dns/txt; s=iport; t=1389208431; x=1390418031; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=9sgbweeMDmf1/2n6Jwf02kIxK65yyUr4bygN13Dq4/Q=; b=R1JTX7Fa2B8ObxKX3SNG1H+9vXaGqqyqoH+T83o1xgIwpHcnHt2ZjoiC 61DfLExUsYSE9QUnkJZ0nsHZmfvgxecyVbaIrwZdCwv2GjJEIfzvd+izr nlZG0gvufP8OEpJxnuuWpsmMSrSxdstqHTIRjxJeG1Bk55xnWFRJmK68A g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ai0FAAyjzVKtJV2Z/2dsb2JhbABZDoJ9OFa5N4EUFnSCJQEBAQMBeQULAgFOMiUCBAENBQmHcwgNxEQXjRWBHFQCBYMkgRMEmBeBMJBlgm4/gio
X-IronPort-AV: E=Sophos;i="4.95,625,1384300800"; d="scan'208";a="11451002"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-3.cisco.com with ESMTP; 08 Jan 2014 19:13:49 +0000
Received: from xhc-rcd-x09.cisco.com (xhc-rcd-x09.cisco.com [173.37.183.83]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s08JDnqt032111 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 8 Jan 2014 19:13:49 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.76]) by xhc-rcd-x09.cisco.com ([173.37.183.83]) with mapi id 14.03.0123.003; Wed, 8 Jan 2014 13:13:49 -0600
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Barry Leiba <barryleiba@computer.org>, IESG IESG <iesg@ietf.org>, "Scott Bradner" <sob@harvard.edu>
Subject: Problem with new Note Well 
Thread-Topic: Problem with new Note Well 
Thread-Index: AQHPDKXCVON+Exaz90mkT0XXpyiWJQ==
Date: Wed, 8 Jan 2014 19:13:48 +0000
Message-ID: <1032B807-2417-449B-ADE3-E06F19729664@cisco.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com>
In-Reply-To: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <F0AE97E8376EE549B076B5ECC3074D0B@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jan 2014 19:14:02 -0000

On Dec 16, 2013, at 12:56 PM, Barry Leiba <barryleiba@computer.org> wrote:

> The IESG has made final edits to the updated Note Well statement, and
> it has been officially updated:
> http://www.ietf.org/about/note-well.html
>=20
> I have just uploaded the final versions of the Note Well meeting
> slides, attached to the bottom of the WG Chairs wiki:
> http://wiki.tools.ietf.org/group/wgchairs/wiki/WikiStart
>=20
> Please use this new version now, and please remember that as you
> prepare slides for the London meeting.
>=20
> Barry


The new note well says=20

	=95 If you are aware that any contribution (something written, said, or di=
scussed in any IETF context) is covered by patents or patent applications, =
you must disclose that fact.

Is that true?  Or is it missing something along the lines of section y of B=
CP 79 such as=20

   or must not contribute to or participate in IETF activities with
   respect to technologies that he or she reasonably and personally
   knows to be Covered by IPR which he or she will not disclose.

Thanks, Cullen




From sob@harvard.edu  Wed Jan  8 11:17:53 2014
Return-Path: <sob@harvard.edu>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77AF01AE3C1; Wed,  8 Jan 2014 11:17:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.138
X-Spam-Level: 
X-Spam-Status: No, score=-3.138 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G5wV2vbdLrvU; Wed,  8 Jan 2014 11:17:51 -0800 (PST)
Received: from ackroyd.harvard.edu (ackroyd.harvard.edu [128.103.208.29]) by ietfa.amsl.com (Postfix) with ESMTP id 3F2BD1AE3A0; Wed,  8 Jan 2014 11:17:51 -0800 (PST)
Received: from ENTWEDGE0000004.university.harvard.edu (entwedge0000004.university.harvard.edu [10.35.202.51]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ackroyd.harvard.edu (Postfix) with ESMTP id 23323E94C2; Wed,  8 Jan 2014 14:17:41 -0500 (EST)
Received: from ENTWHUBT0000001.university.harvard.edu (10.32.8.202) by entwedge0000004.university.harvard.edu (10.35.202.51) with Microsoft SMTP Server (TLS) id 14.3.146.0; Wed, 8 Jan 2014 14:17:22 -0500
Received: from ENTWEXMB0000008.university.harvard.edu ([169.254.1.83]) by ENTWHUBT0000001.university.harvard.edu ([10.32.8.202]) with mapi id 14.03.0146.000; Wed, 8 Jan 2014 14:17:40 -0500
From: "Bradner, Scott" <sob@harvard.edu>
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Subject: Re: Problem with new Note Well 
Thread-Topic: Problem with new Note Well 
Thread-Index: AQHPDKXCVON+Exaz90mkT0XXpyiWJZp7hx4A
Date: Wed, 8 Jan 2014 19:17:40 +0000
Message-ID: <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com>
In-Reply-To: <1032B807-2417-449B-ADE3-E06F19729664@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [128.103.229.199]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <8C4A1FA186219441BF73E62559BE4A32@Exchange.university.harvard.edu>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>, Barry Leiba <barryleiba@computer.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jan 2014 19:17:53 -0000

you are correct - we (Barry, the IESG & me) discussed this before the IESG =
approved this text - they felt that=20
being brief was more important than being fully accurate (or at least that =
is the way I expressed it)

Scott

Scott O Bradner
Senior Technology Consultant

Harvard University Information Technology
Innovation & Architecture
(P) +1 (617) 495 3864
8 Story St, room 5014
Cambridge, MA 02138



On Jan 8, 2014, at 2:13 PM, Cullen Jennings (fluffy) <fluffy@cisco.com> wro=
te:

>=20
>=20
> On Dec 16, 2013, at 12:56 PM, Barry Leiba <barryleiba@computer.org> wrote=
:
>=20
>> The IESG has made final edits to the updated Note Well statement, and
>> it has been officially updated:
>> http://www.ietf.org/about/note-well.html
>>=20
>> I have just uploaded the final versions of the Note Well meeting
>> slides, attached to the bottom of the WG Chairs wiki:
>> http://wiki.tools.ietf.org/group/wgchairs/wiki/WikiStart
>>=20
>> Please use this new version now, and please remember that as you
>> prepare slides for the London meeting.
>>=20
>> Barry
>=20
>=20
> The new note well says=20
>=20
> 	=95 If you are aware that any contribution (something written, said, or =
discussed in any IETF context) is covered by patents or patent applications=
, you must disclose that fact.
>=20
> Is that true?  Or is it missing something along the lines of section y of=
 BCP 79 such as=20
>=20
>   or must not contribute to or participate in IETF activities with
>   respect to technologies that he or she reasonably and personally
>   knows to be Covered by IPR which he or she will not disclose.
>=20
> Thanks, Cullen
>=20
>=20
>=20


From mary.ietf.barnes@gmail.com  Wed Jan  8 12:57:58 2014
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C3111AE5C1 for <wgchairs@ietfa.amsl.com>; Wed,  8 Jan 2014 12:57:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IX1zHIvFmEHu for <wgchairs@ietfa.amsl.com>; Wed,  8 Jan 2014 12:57:56 -0800 (PST)
Received: from mail-wi0-x231.google.com (mail-wi0-x231.google.com [IPv6:2a00:1450:400c:c05::231]) by ietfa.amsl.com (Postfix) with ESMTP id 263411AE1AA for <wgchairs@ietf.org>; Wed,  8 Jan 2014 12:57:55 -0800 (PST)
Received: by mail-wi0-f177.google.com with SMTP id cc10so2643666wib.16 for <wgchairs@ietf.org>; Wed, 08 Jan 2014 12:57:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=5hc2wEBna14TIOtveVjiwf4WtTYoR+d3kJk8Q30Q+Hg=; b=bSvsh58VN31RDMbAUQZhD6Erpiv/uqUWVOv7domq0oMV4NHqx1OEJnMNv/5ltCuugw FDdHT7QVxqxuAKueQt5bVYmqMkn0kp4gaCaj4+jgJuht4fK8duYKRYQqc0sDEcA/INbv U0FE6D0lDgGF8+I6MPwh+PoGJ1iF5VMt6F8xsqre5BcQAnGkCGcdlgFjIiQSJC+3HyIG kpGyjNdWXrd+n/XxZ0fx3Br1zxAn2aZSd0cfJH+/pssBLFbOaPQrb+yvUaij93LXIfjM baXjv1ypJ6Bhrw0/1dX8ThaOpaZWm4IyJUEw4nSlgq8Dje6fmfIG8/SZCH4Qup6H3+um TDQQ==
MIME-Version: 1.0
X-Received: by 10.180.96.226 with SMTP id dv2mr34133wib.36.1389214666389; Wed, 08 Jan 2014 12:57:46 -0800 (PST)
Received: by 10.216.172.9 with HTTP; Wed, 8 Jan 2014 12:57:46 -0800 (PST)
In-Reply-To: <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu>
Date: Wed, 8 Jan 2014 14:57:46 -0600
Message-ID: <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com>
Subject: Re: Problem with new Note Well
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: "Bradner, Scott" <sob@harvard.edu>
Content-Type: multipart/alternative; boundary=f46d044303e6b4ff5f04ef7bbee3
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, "wgchairs@ietf.org" <wgchairs@ietf.org>, Barry Leiba <barryleiba@computer.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jan 2014 20:57:58 -0000

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

Personally, I've never seen significant value in this shorter note well and
while others have been using this new text for the past few meetings, I've
stuck to the old.   Now that this is considered the recommended note well
for chairs to use, I guess I'll use it.  But, I personally think accuracy
should trump brevity.  I think the "must" in that bullet  ought to at least
be a should and that adding an "otherwise, one should not contribute to or
participate in any related IETF activities." would add more value.

Mary.


On Wed, Jan 8, 2014 at 1:17 PM, Bradner, Scott <sob@harvard.edu> wrote:

> you are correct - we (Barry, the IESG & me) discussed this before the IES=
G
> approved this text - they felt that
> being brief was more important than being fully accurate (or at least tha=
t
> is the way I expressed it)
>
> Scott
>
> Scott O Bradner
> Senior Technology Consultant
>
> Harvard University Information Technology
> Innovation & Architecture
> (P) +1 (617) 495 3864
> 8 Story St, room 5014
> Cambridge, MA 02138
>
>
>
> On Jan 8, 2014, at 2:13 PM, Cullen Jennings (fluffy) <fluffy@cisco.com>
> wrote:
>
> >
> >
> > On Dec 16, 2013, at 12:56 PM, Barry Leiba <barryleiba@computer.org>
> wrote:
> >
> >> The IESG has made final edits to the updated Note Well statement, and
> >> it has been officially updated:
> >> http://www.ietf.org/about/note-well.html
> >>
> >> I have just uploaded the final versions of the Note Well meeting
> >> slides, attached to the bottom of the WG Chairs wiki:
> >> http://wiki.tools.ietf.org/group/wgchairs/wiki/WikiStart
> >>
> >> Please use this new version now, and please remember that as you
> >> prepare slides for the London meeting.
> >>
> >> Barry
> >
> >
> > The new note well says
> >
> >       =95 If you are aware that any contribution (something written, sa=
id,
> or discussed in any IETF context) is covered by patents or patent
> applications, you must disclose that fact.
> >
> > Is that true?  Or is it missing something along the lines of section y
> of BCP 79 such as
> >
> >   or must not contribute to or participate in IETF activities with
> >   respect to technologies that he or she reasonably and personally
> >   knows to be Covered by IPR which he or she will not disclose.
> >
> > Thanks, Cullen
> >
> >
> >
>
>

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

<div dir=3D"ltr">Personally, I&#39;ve never seen significant value in this =
shorter note well and while others have been using this new text for the pa=
st few meetings, I&#39;ve stuck to the old. =A0 Now that this is considered=
 the recommended note well for chairs to use, I guess I&#39;ll use it. =A0B=
ut, I personally think accuracy should trump brevity. =A0I think the &quot;=
must&quot; in that bullet =A0ought to at least be a should and that adding =
an &quot;otherwise, one should not contribute to or participate in any rela=
ted IETF activities.&quot; would add more value. =A0=A0<div>
<br></div><div>Mary.<br><div class=3D"gmail_extra"><br><br><div class=3D"gm=
ail_quote">On Wed, Jan 8, 2014 at 1:17 PM, Bradner, Scott <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:sob@harvard.edu" target=3D"_blank">sob@harvard.edu</=
a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">you are correct - we (Barry, the IESG &amp; =
me) discussed this before the IESG approved this text - they felt that<br>
being brief was more important than being fully accurate (or at least that =
is the way I expressed it)<br>
<br>
Scott<br>
<br>
Scott O Bradner<br>
Senior Technology Consultant<br>
<br>
Harvard University Information Technology<br>
Innovation &amp; Architecture<br>
(P) <a href=3D"tel:%2B1%20%28617%29%20495%203864" value=3D"+16174953864">+1=
 (617) 495 3864</a><br>
8 Story St, room 5014<br>
Cambridge, MA 02138<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
<br>
On Jan 8, 2014, at 2:13 PM, Cullen Jennings (fluffy) &lt;<a href=3D"mailto:=
fluffy@cisco.com">fluffy@cisco.com</a>&gt; wrote:<br>
<br>
&gt;<br>
&gt;<br>
&gt; On Dec 16, 2013, at 12:56 PM, Barry Leiba &lt;<a href=3D"mailto:barryl=
eiba@computer.org">barryleiba@computer.org</a>&gt; wrote:<br>
&gt;<br>
&gt;&gt; The IESG has made final edits to the updated Note Well statement, =
and<br>
&gt;&gt; it has been officially updated:<br>
&gt;&gt; <a href=3D"http://www.ietf.org/about/note-well.html" target=3D"_bl=
ank">http://www.ietf.org/about/note-well.html</a><br>
&gt;&gt;<br>
&gt;&gt; I have just uploaded the final versions of the Note Well meeting<b=
r>
&gt;&gt; slides, attached to the bottom of the WG Chairs wiki:<br>
&gt;&gt; <a href=3D"http://wiki.tools.ietf.org/group/wgchairs/wiki/WikiStar=
t" target=3D"_blank">http://wiki.tools.ietf.org/group/wgchairs/wiki/WikiSta=
rt</a><br>
&gt;&gt;<br>
&gt;&gt; Please use this new version now, and please remember that as you<b=
r>
&gt;&gt; prepare slides for the London meeting.<br>
&gt;&gt;<br>
&gt;&gt; Barry<br>
&gt;<br>
&gt;<br>
&gt; The new note well says<br>
&gt;<br>
&gt; =A0 =A0 =A0 =95 If you are aware that any contribution (something writ=
ten, said, or discussed in any IETF context) is covered by patents or paten=
t applications, you must disclose that fact.<br>
&gt;<br>
&gt; Is that true? =A0Or is it missing something along the lines of section=
 y of BCP 79 such as<br>
&gt;<br>
&gt; =A0 or must not contribute to or participate in IETF activities with<b=
r>
&gt; =A0 respect to technologies that he or she reasonably and personally<b=
r>
&gt; =A0 knows to be Covered by IPR which he or she will not disclose.<br>
&gt;<br>
&gt; Thanks, Cullen<br>
&gt;<br>
&gt;<br>
&gt;<br>
<br>
</div></div></blockquote></div><br></div></div></div>

--f46d044303e6b4ff5f04ef7bbee3--

From bclaise@cisco.com  Mon Jan 13 00:10:05 2014
Return-Path: <bclaise@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3BAE1ADFC0 for <wgchairs@ietfa.amsl.com>; Mon, 13 Jan 2014 00:10:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.039
X-Spam-Level: 
X-Spam-Status: No, score=-10.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DS5D05-sGNvd for <wgchairs@ietfa.amsl.com>; Mon, 13 Jan 2014 00:10:03 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id 307171ADF4E for <wgchairs@ietf.org>; Mon, 13 Jan 2014 00:10:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=829; q=dns/txt; s=iport; t=1389600592; x=1390810192; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=tWjNfy9LzPWhiVHDgnZE6iCDe5igOMLCSDB6lNKiAAs=; b=TZP55AZcbIQr+n+7ia9/M+IiXHL7DwR7i5B4SQ1zekTGPePcHgAiZZi6 JkTtwfpEA67oRR7YN2esnA7BvIC8igIDWxwmDImLUN4M6y+GXqf+/u73g dOUxbkXen/xBD1Y+s6DYVwrkE4RDTmNx7MsY70oQsyGjYpEP4z/ntjcFr c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiMFAJGe01KQ/khR/2dsb2JhbABagws4g1S2YAqBCRZ0giYBAQQjFTYKESUCBQ8HBQYCAgkDAgECAUUGDQgBAQWHew2pSoQmlkEXgSmMfBEBVxiCV4FIAQOYF4EwhRWLUIMuO4E1
X-IronPort-AV: E=Sophos;i="4.95,651,1384300800";  d="scan'208";a="3547551"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by aer-iport-1.cisco.com with ESMTP; 13 Jan 2014 08:09:51 +0000
Received: from [10.60.67.85] (ams-bclaise-8914.cisco.com [10.60.67.85]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s0D89pbL032046 for <wgchairs@ietf.org>; Mon, 13 Jan 2014 08:09:51 GMT
Message-ID: <52D39F4F.6030900@cisco.com>
Date: Mon, 13 Jan 2014 09:09:51 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: WG Chairs <wgchairs@ietf.org>
Subject: How to globally change the email address for all IETF mailing lists?
References: <52D00EDE.8020308@cisco.com>
In-Reply-To: <52D00EDE.8020308@cisco.com>
X-Forwarded-Message-Id: <52D00EDE.8020308@cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 08:10:05 -0000

Dear all,

 From time to time, we have the request of someone wanted to change 
her/his contact, so the following might be handy.

You can globally change the email address for all the @ietf.org lists someone is
subscribed to. You should take the following steps:

1) Go tohttps://www.ietf.org/mailman/options/ietf/<email-address>

2) Enter password. (If you do not remember your password, there is
a button here to have the system send you a password reminder.)

2) Under the "Changing your Ietf membership information" section, enter
your new email address in the appropriate fields.

3) Check the "Change globally" box.

4) Hit the "Change My Address and Name" button.

5) You will receive an email at your new address asking you to confirm
the change.


Best regards,

Amy

     

     

   





From michael.scharf@alcatel-lucent.com  Mon Jan 13 00:43:48 2014
Return-Path: <michael.scharf@alcatel-lucent.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D527D1AE070 for <wgchairs@ietfa.amsl.com>; Mon, 13 Jan 2014 00:43:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uRK_jOxRGSAZ for <wgchairs@ietfa.amsl.com>; Mon, 13 Jan 2014 00:43:47 -0800 (PST)
Received: from hoemail2.alcatel.com (hoemail2.alcatel.com [192.160.6.149]) by ietfa.amsl.com (Postfix) with ESMTP id 0E5D21AE062 for <wgchairs@ietf.org>; Mon, 13 Jan 2014 00:43:47 -0800 (PST)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by hoemail2.alcatel.com (8.13.8/IER-o) with ESMTP id s0D8hXF7026559 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 13 Jan 2014 02:43:34 -0600 (CST)
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id s0D8hVpw017730 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 13 Jan 2014 09:43:32 +0100
Received: from FR712WXCHMBA15.zeu.alcatel-lucent.com ([169.254.7.70]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.02.0247.003; Mon, 13 Jan 2014 09:43:31 +0100
From: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
To: Benoit Claise <bclaise@cisco.com>, WG Chairs <wgchairs@ietf.org>
Subject: RE: How to globally change the email address for all IETF mailing lists?
Thread-Topic: How to globally change the email address for all IETF mailing lists?
Thread-Index: AQHPEDbeP2xdAfhyikC5c7Urk1Aw2pqCVlzg
Date: Mon, 13 Jan 2014 08:43:32 +0000
Message-ID: <655C07320163294895BBADA28372AF5D161F8E@FR712WXCHMBA15.zeu.alcatel-lucent.com>
References: <52D00EDE.8020308@cisco.com> <52D39F4F.6030900@cisco.com>
In-Reply-To: <52D39F4F.6030900@cisco.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.40]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 08:43:49 -0000

SXMgdGhpcyB1c2VmdWwgaGludCBtZW50aW9uZWQgc29tZXdoZXJlIG9uIHRoZSBJRVRGIFdlYiBz
aXRlPw0KDQpNaWNoYWVsDQoNCg0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9t
OiBXR0NoYWlycyBbbWFpbHRvOndnY2hhaXJzLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBP
ZiBCZW5vaXQNCj4gQ2xhaXNlDQo+IFNlbnQ6IE1vbmRheSwgSmFudWFyeSAxMywgMjAxNCA5OjEw
IEFNDQo+IFRvOiBXRyBDaGFpcnMNCj4gU3ViamVjdDogSG93IHRvIGdsb2JhbGx5IGNoYW5nZSB0
aGUgZW1haWwgYWRkcmVzcyBmb3IgYWxsIElFVEYgbWFpbGluZw0KPiBsaXN0cz8NCj4gDQo+IERl
YXIgYWxsLA0KPiANCj4gIEZyb20gdGltZSB0byB0aW1lLCB3ZSBoYXZlIHRoZSByZXF1ZXN0IG9m
IHNvbWVvbmUgd2FudGVkIHRvIGNoYW5nZQ0KPiBoZXIvaGlzIGNvbnRhY3QsIHNvIHRoZSBmb2xs
b3dpbmcgbWlnaHQgYmUgaGFuZHkuDQo+IA0KPiBZb3UgY2FuIGdsb2JhbGx5IGNoYW5nZSB0aGUg
ZW1haWwgYWRkcmVzcyBmb3IgYWxsIHRoZSBAaWV0Zi5vcmcgbGlzdHMNCj4gc29tZW9uZSBpcw0K
PiBzdWJzY3JpYmVkIHRvLiBZb3Ugc2hvdWxkIHRha2UgdGhlIGZvbGxvd2luZyBzdGVwczoNCj4g
DQo+IDEpIEdvIHRvaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9vcHRpb25zL2lldGYvPGVt
YWlsLWFkZHJlc3M+DQo+IA0KPiAyKSBFbnRlciBwYXNzd29yZC4gKElmIHlvdSBkbyBub3QgcmVt
ZW1iZXIgeW91ciBwYXNzd29yZCwgdGhlcmUgaXMNCj4gYSBidXR0b24gaGVyZSB0byBoYXZlIHRo
ZSBzeXN0ZW0gc2VuZCB5b3UgYSBwYXNzd29yZCByZW1pbmRlci4pDQo+IA0KPiAyKSBVbmRlciB0
aGUgIkNoYW5naW5nIHlvdXIgSWV0ZiBtZW1iZXJzaGlwIGluZm9ybWF0aW9uIiBzZWN0aW9uLCBl
bnRlcg0KPiB5b3VyIG5ldyBlbWFpbCBhZGRyZXNzIGluIHRoZSBhcHByb3ByaWF0ZSBmaWVsZHMu
DQo+IA0KPiAzKSBDaGVjayB0aGUgIkNoYW5nZSBnbG9iYWxseSIgYm94Lg0KPiANCj4gNCkgSGl0
IHRoZSAiQ2hhbmdlIE15IEFkZHJlc3MgYW5kIE5hbWUiIGJ1dHRvbi4NCj4gDQo+IDUpIFlvdSB3
aWxsIHJlY2VpdmUgYW4gZW1haWwgYXQgeW91ciBuZXcgYWRkcmVzcyBhc2tpbmcgeW91IHRvIGNv
bmZpcm0NCj4gdGhlIGNoYW5nZS4NCj4gDQo+IA0KPiBCZXN0IHJlZ2FyZHMsDQo+IA0KPiBBbXkN
Cj4gDQo+IA0KPiANCj4gDQo+IA0KPiANCj4gDQo+IA0KPiANCg0K

From bclaise@cisco.com  Mon Jan 13 00:51:34 2014
Return-Path: <bclaise@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAEBA1ADF7A for <wgchairs@ietfa.amsl.com>; Mon, 13 Jan 2014 00:51:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.039
X-Spam-Level: 
X-Spam-Status: No, score=-10.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jexy9JPMywGN for <wgchairs@ietfa.amsl.com>; Mon, 13 Jan 2014 00:51:33 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id E04DE1AE058 for <wgchairs@ietf.org>; Mon, 13 Jan 2014 00:51:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1321; q=dns/txt; s=iport; t=1389603082; x=1390812682; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=npNYD1UTlTVGcEnhA/w9ttGeKVeYE/xyfcNoJmm76xo=; b=PlUvmAq1dntdX5TJyFxXRe6DUpB6wYFtzNLiL7D85m8QDQIL3GYtBHum v8w319/uV1GCQxbQWCBdFQUYePYS5j2ymuGlmC6KxBJQBv+Wm1ShN4eeF WJYYgqMZHCBi7KjzC3nZIGIpn2EPNg5Q/GJg0D7ktuMOBz+PlP9xacGwD M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiMFAKmo01KQ/khM/2dsb2JhbABagws4g1S2aoEMFnSCJQEBAQQjFTYKDQQLEQQBAQMCBQ8HBQMDAgIJAwIBAgE0CQgGAQwGAgEBBYd7DalYhCaWPxeBKYx8EQFXBhKCV4FIAQOYF4EwhRWLUIMuO4E1
X-IronPort-AV: E=Sophos;i="4.95,651,1384300800";  d="scan'208";a="2879083"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by aer-iport-2.cisco.com with ESMTP; 13 Jan 2014 08:51:21 +0000
Received: from [10.60.67.85] (ams-bclaise-8914.cisco.com [10.60.67.85]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s0D8pLAX032153; Mon, 13 Jan 2014 08:51:21 GMT
Message-ID: <52D3A909.6070009@cisco.com>
Date: Mon, 13 Jan 2014 09:51:21 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>, WG Chairs <wgchairs@ietf.org>
Subject: Re: How to globally change the email address for all IETF mailing lists?
References: <52D00EDE.8020308@cisco.com> <52D39F4F.6030900@cisco.com> <655C07320163294895BBADA28372AF5D161F8E@FR712WXCHMBA15.zeu.alcatel-lucent.com>
In-Reply-To: <655C07320163294895BBADA28372AF5D161F8E@FR712WXCHMBA15.zeu.alcatel-lucent.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 08:51:35 -0000

Don't think so.
Hence this email.

Regards, Benoit
> Is this useful hint mentioned somewhere on the IETF Web site?
>
> Michael
>
>
>> -----Original Message-----
>> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of Benoit
>> Claise
>> Sent: Monday, January 13, 2014 9:10 AM
>> To: WG Chairs
>> Subject: How to globally change the email address for all IETF mailing
>> lists?
>>
>> Dear all,
>>
>>   From time to time, we have the request of someone wanted to change
>> her/his contact, so the following might be handy.
>>
>> You can globally change the email address for all the @ietf.org lists
>> someone is
>> subscribed to. You should take the following steps:
>>
>> 1) Go tohttps://www.ietf.org/mailman/options/ietf/<email-address>
>>
>> 2) Enter password. (If you do not remember your password, there is
>> a button here to have the system send you a password reminder.)
>>
>> 2) Under the "Changing your Ietf membership information" section, enter
>> your new email address in the appropriate fields.
>>
>> 3) Check the "Change globally" box.
>>
>> 4) Hit the "Change My Address and Name" button.
>>
>> 5) You will receive an email at your new address asking you to confirm
>> the change.
>>
>>
>> Best regards,
>>
>> Amy
>>
>>
>>
>>
>>
>>
>>
>>
>>


From michael.scharf@alcatel-lucent.com  Mon Jan 13 00:56:26 2014
Return-Path: <michael.scharf@alcatel-lucent.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DB4F1AE078 for <wgchairs@ietfa.amsl.com>; Mon, 13 Jan 2014 00:56:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uPwgKMgBfYDY for <wgchairs@ietfa.amsl.com>; Mon, 13 Jan 2014 00:56:24 -0800 (PST)
Received: from hoemail2.alcatel.com (hoemail2.alcatel.com [192.160.6.149]) by ietfa.amsl.com (Postfix) with ESMTP id 803E91ADF7A for <wgchairs@ietf.org>; Mon, 13 Jan 2014 00:56:24 -0800 (PST)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by hoemail2.alcatel.com (8.13.8/IER-o) with ESMTP id s0D8uBvL005164 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 13 Jan 2014 02:56:13 -0600 (CST)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id s0D8uBqN029807 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 13 Jan 2014 09:56:11 +0100
Received: from FR712WXCHMBA15.zeu.alcatel-lucent.com ([169.254.7.70]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.02.0247.003; Mon, 13 Jan 2014 09:56:11 +0100
From: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
To: Benoit Claise <bclaise@cisco.com>, WG Chairs <wgchairs@ietf.org>
Subject: RE: How to globally change the email address for all IETF mailing lists?
Thread-Topic: How to globally change the email address for all IETF mailing lists?
Thread-Index: AQHPEDbeP2xdAfhyikC5c7Urk1Aw2pqCVlzg///xtYCAABFVQA==
Date: Mon, 13 Jan 2014 08:56:10 +0000
Message-ID: <655C07320163294895BBADA28372AF5D162001@FR712WXCHMBA15.zeu.alcatel-lucent.com>
References: <52D00EDE.8020308@cisco.com> <52D39F4F.6030900@cisco.com> <655C07320163294895BBADA28372AF5D161F8E@FR712WXCHMBA15.zeu.alcatel-lucent.com> <52D3A909.6070009@cisco.com>
In-Reply-To: <52D3A909.6070009@cisco.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.40]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 08:56:26 -0000

V2h5IG5vdCBwdWJsaXNoIHRoZSBoaW50IHNvbWV3aGVyZSB3aGVyZSBub24tY2hhaXJzIGNhbiBm
aW5kIGl0LCB0b28/DQoNCk1pY2hhZWwNCg0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0t
DQo+IEZyb206IEJlbm9pdCBDbGFpc2UgW21haWx0bzpiY2xhaXNlQGNpc2NvLmNvbV0NCj4gU2Vu
dDogTW9uZGF5LCBKYW51YXJ5IDEzLCAyMDE0IDk6NTEgQU0NCj4gVG86IFNjaGFyZiwgTWljaGFl
bCAoTWljaGFlbCk7IFdHIENoYWlycw0KPiBTdWJqZWN0OiBSZTogSG93IHRvIGdsb2JhbGx5IGNo
YW5nZSB0aGUgZW1haWwgYWRkcmVzcyBmb3IgYWxsIElFVEYNCj4gbWFpbGluZyBsaXN0cz8NCj4g
DQo+IERvbid0IHRoaW5rIHNvLg0KPiBIZW5jZSB0aGlzIGVtYWlsLg0KPiANCj4gUmVnYXJkcywg
QmVub2l0DQo+ID4gSXMgdGhpcyB1c2VmdWwgaGludCBtZW50aW9uZWQgc29tZXdoZXJlIG9uIHRo
ZSBJRVRGIFdlYiBzaXRlPw0KPiA+DQo+ID4gTWljaGFlbA0KPiA+DQo+ID4NCj4gPj4gLS0tLS1P
cmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gPj4gRnJvbTogV0dDaGFpcnMgW21haWx0bzp3Z2NoYWly
cy1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YNCj4gQmVub2l0DQo+ID4+IENsYWlzZQ0K
PiA+PiBTZW50OiBNb25kYXksIEphbnVhcnkgMTMsIDIwMTQgOToxMCBBTQ0KPiA+PiBUbzogV0cg
Q2hhaXJzDQo+ID4+IFN1YmplY3Q6IEhvdyB0byBnbG9iYWxseSBjaGFuZ2UgdGhlIGVtYWlsIGFk
ZHJlc3MgZm9yIGFsbCBJRVRGDQo+IG1haWxpbmcNCj4gPj4gbGlzdHM/DQo+ID4+DQo+ID4+IERl
YXIgYWxsLA0KPiA+Pg0KPiA+PiAgIEZyb20gdGltZSB0byB0aW1lLCB3ZSBoYXZlIHRoZSByZXF1
ZXN0IG9mIHNvbWVvbmUgd2FudGVkIHRvIGNoYW5nZQ0KPiA+PiBoZXIvaGlzIGNvbnRhY3QsIHNv
IHRoZSBmb2xsb3dpbmcgbWlnaHQgYmUgaGFuZHkuDQo+ID4+DQo+ID4+IFlvdSBjYW4gZ2xvYmFs
bHkgY2hhbmdlIHRoZSBlbWFpbCBhZGRyZXNzIGZvciBhbGwgdGhlIEBpZXRmLm9yZw0KPiBsaXN0
cw0KPiA+PiBzb21lb25lIGlzDQo+ID4+IHN1YnNjcmliZWQgdG8uIFlvdSBzaG91bGQgdGFrZSB0
aGUgZm9sbG93aW5nIHN0ZXBzOg0KPiA+Pg0KPiA+PiAxKSBHbyB0b2h0dHBzOi8vd3d3LmlldGYu
b3JnL21haWxtYW4vb3B0aW9ucy9pZXRmLzxlbWFpbC1hZGRyZXNzPg0KPiA+Pg0KPiA+PiAyKSBF
bnRlciBwYXNzd29yZC4gKElmIHlvdSBkbyBub3QgcmVtZW1iZXIgeW91ciBwYXNzd29yZCwgdGhl
cmUgaXMNCj4gPj4gYSBidXR0b24gaGVyZSB0byBoYXZlIHRoZSBzeXN0ZW0gc2VuZCB5b3UgYSBw
YXNzd29yZCByZW1pbmRlci4pDQo+ID4+DQo+ID4+IDIpIFVuZGVyIHRoZSAiQ2hhbmdpbmcgeW91
ciBJZXRmIG1lbWJlcnNoaXAgaW5mb3JtYXRpb24iIHNlY3Rpb24sDQo+IGVudGVyDQo+ID4+IHlv
dXIgbmV3IGVtYWlsIGFkZHJlc3MgaW4gdGhlIGFwcHJvcHJpYXRlIGZpZWxkcy4NCj4gPj4NCj4g
Pj4gMykgQ2hlY2sgdGhlICJDaGFuZ2UgZ2xvYmFsbHkiIGJveC4NCj4gPj4NCj4gPj4gNCkgSGl0
IHRoZSAiQ2hhbmdlIE15IEFkZHJlc3MgYW5kIE5hbWUiIGJ1dHRvbi4NCj4gPj4NCj4gPj4gNSkg
WW91IHdpbGwgcmVjZWl2ZSBhbiBlbWFpbCBhdCB5b3VyIG5ldyBhZGRyZXNzIGFza2luZyB5b3Ug
dG8NCj4gY29uZmlybQ0KPiA+PiB0aGUgY2hhbmdlLg0KPiA+Pg0KPiA+Pg0KPiA+PiBCZXN0IHJl
Z2FyZHMsDQo+ID4+DQo+ID4+IEFteQ0KPiA+Pg0KPiA+Pg0KPiA+Pg0KPiA+Pg0KPiA+Pg0KPiA+
Pg0KPiA+Pg0KPiA+Pg0KPiA+Pg0KDQo=

From bclaise@cisco.com  Mon Jan 13 02:26:46 2014
Return-Path: <bclaise@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 085C51AE076 for <wgchairs@ietfa.amsl.com>; Mon, 13 Jan 2014 02:26:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.039
X-Spam-Level: 
X-Spam-Status: No, score=-10.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0NlMMZzC4rDV for <wgchairs@ietfa.amsl.com>; Mon, 13 Jan 2014 02:26:44 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id 248D01ADFA9 for <wgchairs@ietf.org>; Mon, 13 Jan 2014 02:26:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2352; q=dns/txt; s=iport; t=1389608793; x=1390818393; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=PoGbqz3S/h5+Zd+0xB/wdH/bDbFl5qvtOgCYGOfPI4A=; b=VFVlZ0ufs6QDJHVVAPS8/rChf2T/yf+PyKfr+YKo0YGmY5yRgUInk7ub hFlPi47ogpvryh8Dj5HWUPRsqbevv/tK8L8vs8rQYRcs7sujKRZDu+0nU At5MkZmzlOG5/TjsMI+PYbgZMge0drpeZGpib0sGnMlRKN2885ahyGgVU w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiMFAOm+01KQ/khM/2dsb2JhbABagws4g1S2bIEPFnSCJQEBAQMBIxU2CgYHBAsRBAEBAwIFDwcFAwMCAgkDAgECATQJCAYBDAYCAQEFh3MIDalwhCaWRheBKYx8EQFXBhKCV4FIAQOYF4EwhRWLUIMuO4EsBwIX
X-IronPort-AV: E=Sophos;i="4.95,652,1384300800";  d="scan'208";a="2884413"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by aer-iport-2.cisco.com with ESMTP; 13 Jan 2014 10:26:31 +0000
Received: from [10.60.67.85] (ams-bclaise-8914.cisco.com [10.60.67.85]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s0DAQVe8025636; Mon, 13 Jan 2014 10:26:31 GMT
Message-ID: <52D3BF57.7070304@cisco.com>
Date: Mon, 13 Jan 2014 11:26:31 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>, WG Chairs <wgchairs@ietf.org>
Subject: Re: How to globally change the email address for all IETF mailing lists?
References: <52D00EDE.8020308@cisco.com> <52D39F4F.6030900@cisco.com> <655C07320163294895BBADA28372AF5D161F8E@FR712WXCHMBA15.zeu.alcatel-lucent.com> <52D3A909.6070009@cisco.com> <655C07320163294895BBADA28372AF5D162001@FR712WXCHMBA15.zeu.alcatel-lucent.com>
In-Reply-To: <655C07320163294895BBADA28372AF5D162001@FR712WXCHMBA15.zeu.alcatel-lucent.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 10:26:46 -0000

> Why not publish the hint somewhere where non-chairs can find it, too?
No problem to publish that, it's a small effort, but what's suitable 
place for this type of hints that are rarely used, independent (i.e. we 
don't have 10 hints on emails)?
Personally, I'm a little skeptical by the approach to document 
everything on the web, in WIKIs for example IF this information is not 
maintained/updated and IF not properly advertised.

Now, why didn't I send this on the IETF-discussion list instead of the 
WG chair list? No good reason.
Maybe IETF-discussion is more appropriate...

Regards, Benoit
>
> Michael
>
>
>> -----Original Message-----
>> From: Benoit Claise [mailto:bclaise@cisco.com]
>> Sent: Monday, January 13, 2014 9:51 AM
>> To: Scharf, Michael (Michael); WG Chairs
>> Subject: Re: How to globally change the email address for all IETF
>> mailing lists?
>>
>> Don't think so.
>> Hence this email.
>>
>> Regards, Benoit
>>> Is this useful hint mentioned somewhere on the IETF Web site?
>>>
>>> Michael
>>>
>>>
>>>> -----Original Message-----
>>>> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of
>> Benoit
>>>> Claise
>>>> Sent: Monday, January 13, 2014 9:10 AM
>>>> To: WG Chairs
>>>> Subject: How to globally change the email address for all IETF
>> mailing
>>>> lists?
>>>>
>>>> Dear all,
>>>>
>>>>    From time to time, we have the request of someone wanted to change
>>>> her/his contact, so the following might be handy.
>>>>
>>>> You can globally change the email address for all the @ietf.org
>> lists
>>>> someone is
>>>> subscribed to. You should take the following steps:
>>>>
>>>> 1) Go tohttps://www.ietf.org/mailman/options/ietf/<email-address>
>>>>
>>>> 2) Enter password. (If you do not remember your password, there is
>>>> a button here to have the system send you a password reminder.)
>>>>
>>>> 2) Under the "Changing your Ietf membership information" section,
>> enter
>>>> your new email address in the appropriate fields.
>>>>
>>>> 3) Check the "Change globally" box.
>>>>
>>>> 4) Hit the "Change My Address and Name" button.
>>>>
>>>> 5) You will receive an email at your new address asking you to
>> confirm
>>>> the change.
>>>>
>>>>
>>>> Best regards,
>>>>
>>>> Amy
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>


From tom.taylor.stds@gmail.com  Mon Jan 13 06:25:59 2014
Return-Path: <tom.taylor.stds@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 055B41ADF38 for <wgchairs@ietfa.amsl.com>; Mon, 13 Jan 2014 06:25:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RBGbXM_vskKV for <wgchairs@ietfa.amsl.com>; Mon, 13 Jan 2014 06:25:57 -0800 (PST)
Received: from mail-ig0-x22d.google.com (mail-ig0-x22d.google.com [IPv6:2607:f8b0:4001:c05::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 229B11ADF23 for <wgchairs@ietf.org>; Mon, 13 Jan 2014 06:25:57 -0800 (PST)
Received: by mail-ig0-f173.google.com with SMTP id c10so2044569igq.0 for <wgchairs@ietf.org>; Mon, 13 Jan 2014 06:25:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=1uYNKnbXSENycjLF9xcQOhFQGdOE0qGfvi3Y+1Hf0hs=; b=JsNkYyPvM9wao1O4IiyFjzVD9U2D0suodSLIQOq7iikeYjn3bUXA+v6vHvMiKdoQZR G35POwMxSyZ0kZoEzcymLHUGlVFy0mmvz2myePTq9D1+vu1VXlL+Qudv6S8BZ5PrY5Rx C7ijd6vsd+cDCbvoBgP7fY1f2CxPfucgUIzxC9i9peAtLgUVqv0vqItJqQ8hnnTv/Vzd FbVVIeZ9p24beIlscQwvm1+vzj77cRBsDLWe1TsLloKo3vRoq0ngYVrbWrR6S9F4wcDt YhZaf9WL57ht4Jv5DPGhsF2mwmAuGOeII5usGH13AM2E2dj+8QsXjHnuuTT/W2expT0M brSA==
X-Received: by 10.43.16.2 with SMTP id pw2mr2409667icb.56.1389623146084; Mon, 13 Jan 2014 06:25:46 -0800 (PST)
Received: from [192.168.1.69] ([64.56.250.4]) by mx.google.com with ESMTPSA id ml2sm18560505igb.10.2014.01.13.06.25.44 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 13 Jan 2014 06:25:45 -0800 (PST)
Message-ID: <52D3F766.9030507@gmail.com>
Date: Mon, 13 Jan 2014 09:25:42 -0500
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: wgchairs@ietf.org, Benoit Claise <bclaise@cisco.com>
Subject: Re: How to globally change the email address for all IETF mailing lists?
References: <52D00EDE.8020308@cisco.com> <52D39F4F.6030900@cisco.com> <655C07320163294895BBADA28372AF5D161F8E@FR712WXCHMBA15.zeu.alcatel-lucent.com> <52D3A909.6070009@cisco.com> <655C07320163294895BBADA28372AF5D162001@FR712WXCHMBA15.zeu.alcatel-lucent.com> <52D3BF57.7070304@cisco.com>
In-Reply-To: <52D3BF57.7070304@cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 14:25:59 -0000

Tuck it into the monthly password reminder E-mail and the initial 
welcoming message.

Tom Taylor

On 13/01/2014 5:26 AM, Benoit Claise wrote:
>
>> Why not publish the hint somewhere where non-chairs can find it, too?
> No problem to publish that, it's a small effort, but what's suitable
> place for this type of hints that are rarely used, independent (i.e. we
> don't have 10 hints on emails)?
> Personally, I'm a little skeptical by the approach to document
> everything on the web, in WIKIs for example IF this information is not
> maintained/updated and IF not properly advertised.
>
> Now, why didn't I send this on the IETF-discussion list instead of the
> WG chair list? No good reason.
> Maybe IETF-discussion is more appropriate...
>
> Regards, Benoit
>>
>> Michael
>>
>>
>>> -----Original Message-----
>>> From: Benoit Claise [mailto:bclaise@cisco.com]
>>> Sent: Monday, January 13, 2014 9:51 AM
>>> To: Scharf, Michael (Michael); WG Chairs
>>> Subject: Re: How to globally change the email address for all IETF
>>> mailing lists?
>>>
>>> Don't think so.
>>> Hence this email.
>>>
>>> Regards, Benoit
>>>> Is this useful hint mentioned somewhere on the IETF Web site?
>>>>
>>>> Michael
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of
>>> Benoit
>>>>> Claise
>>>>> Sent: Monday, January 13, 2014 9:10 AM
>>>>> To: WG Chairs
>>>>> Subject: How to globally change the email address for all IETF
>>> mailing
>>>>> lists?
>>>>>
>>>>> Dear all,
>>>>>
>>>>>    From time to time, we have the request of someone wanted to change
>>>>> her/his contact, so the following might be handy.
>>>>>
>>>>> You can globally change the email address for all the @ietf.org
>>> lists
>>>>> someone is
>>>>> subscribed to. You should take the following steps:
>>>>>
>>>>> 1) Go tohttps://www.ietf.org/mailman/options/ietf/<email-address>
>>>>>
>>>>> 2) Enter password. (If you do not remember your password, there is
>>>>> a button here to have the system send you a password reminder.)
>>>>>
>>>>> 2) Under the "Changing your Ietf membership information" section,
>>> enter
>>>>> your new email address in the appropriate fields.
>>>>>
>>>>> 3) Check the "Change globally" box.
>>>>>
>>>>> 4) Hit the "Change My Address and Name" button.
>>>>>
>>>>> 5) You will receive an email at your new address asking you to
>>> confirm
>>>>> the change.
>>>>>
>>>>>
>>>>> Best regards,
>>>>>
>>>>> Amy
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>
>

From keith.drage@alcatel-lucent.com  Mon Jan 13 07:01:03 2014
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3997D1AE12E for <wgchairs@ietfa.amsl.com>; Mon, 13 Jan 2014 07:01:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MMAblCcJ8W2V for <wgchairs@ietfa.amsl.com>; Mon, 13 Jan 2014 07:01:01 -0800 (PST)
Received: from hoemail1.alcatel.com (hoemail1.alcatel.com [192.160.6.148]) by ietfa.amsl.com (Postfix) with ESMTP id 3DB8D1AE1B0 for <wgchairs@ietf.org>; Mon, 13 Jan 2014 07:01:00 -0800 (PST)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by hoemail1.alcatel.com (8.13.8/IER-o) with ESMTP id s0DF0lQs009614 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 13 Jan 2014 09:00:48 -0600 (CST)
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id s0DF0kKQ008791 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 13 Jan 2014 16:00:46 +0100
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.26]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.02.0247.003; Mon, 13 Jan 2014 16:00:46 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Tom Taylor <tom.taylor.stds@gmail.com>, "wgchairs@ietf.org" <wgchairs@ietf.org>, Benoit Claise <bclaise@cisco.com>
Subject: RE: How to globally change the email address for all IETF mailing lists?
Thread-Topic: How to globally change the email address for all IETF mailing lists?
Thread-Index: AQHPEDbemMNVrX8txEGV3aMfzzTiLZqCReIAgAACL4CAAAFZAIAAGT6AgABC1ACAABhaMA==
Date: Mon, 13 Jan 2014 15:00:45 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B1133C8@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <52D00EDE.8020308@cisco.com> <52D39F4F.6030900@cisco.com> <655C07320163294895BBADA28372AF5D161F8E@FR712WXCHMBA15.zeu.alcatel-lucent.com> <52D3A909.6070009@cisco.com> <655C07320163294895BBADA28372AF5D162001@FR712WXCHMBA15.zeu.alcatel-lucent.com> <52D3BF57.7070304@cisco.com> <52D3F766.9030507@gmail.com>
In-Reply-To: <52D3F766.9030507@gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.41]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 15:01:03 -0000

I don't have a problem with that, but experiences suggests that many people=
 send that message automatically to their junk mail folders; certainly many=
 do not seem to be aware that it exists.

I would note most of it is also at:

http://www.ietf.org/list/

But perhaps that could be made clearer.

Keith

> -----Original Message-----
> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf=20
> Of Tom Taylor
> Sent: 13 January 2014 14:26
> To: wgchairs@ietf.org; Benoit Claise
> Subject: Re: How to globally change the email address for all=20
> IETF mailing lists?
>=20
> Tuck it into the monthly password reminder E-mail and the=20
> initial welcoming message.
>=20
> Tom Taylor
>=20
> On 13/01/2014 5:26 AM, Benoit Claise wrote:
> >
> >> Why not publish the hint somewhere where non-chairs can=20
> find it, too?
> > No problem to publish that, it's a small effort, but what's=20
> suitable=20
> > place for this type of hints that are rarely used,=20
> independent (i.e.=20
> > we don't have 10 hints on emails)?
> > Personally, I'm a little skeptical by the approach to document=20
> > everything on the web, in WIKIs for example IF this=20
> information is not=20
> > maintained/updated and IF not properly advertised.
> >
> > Now, why didn't I send this on the IETF-discussion list=20
> instead of the=20
> > WG chair list? No good reason.
> > Maybe IETF-discussion is more appropriate...
> >
> > Regards, Benoit
> >>
> >> Michael
> >>
> >>
> >>> -----Original Message-----
> >>> From: Benoit Claise [mailto:bclaise@cisco.com]
> >>> Sent: Monday, January 13, 2014 9:51 AM
> >>> To: Scharf, Michael (Michael); WG Chairs
> >>> Subject: Re: How to globally change the email address for=20
> all IETF=20
> >>> mailing lists?
> >>>
> >>> Don't think so.
> >>> Hence this email.
> >>>
> >>> Regards, Benoit
> >>>> Is this useful hint mentioned somewhere on the IETF Web site?
> >>>>
> >>>> Michael
> >>>>
> >>>>
> >>>>> -----Original Message-----
> >>>>> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of
> >>> Benoit
> >>>>> Claise
> >>>>> Sent: Monday, January 13, 2014 9:10 AM
> >>>>> To: WG Chairs
> >>>>> Subject: How to globally change the email address for all IETF
> >>> mailing
> >>>>> lists?
> >>>>>
> >>>>> Dear all,
> >>>>>
> >>>>>    From time to time, we have the request of someone wanted to=20
> >>>>> change her/his contact, so the following might be handy.
> >>>>>
> >>>>> You can globally change the email address for all the @ietf.org
> >>> lists
> >>>>> someone is
> >>>>> subscribed to. You should take the following steps:
> >>>>>
> >>>>> 1) Go=20
> tohttps://www.ietf.org/mailman/options/ietf/<email-address>
> >>>>>
> >>>>> 2) Enter password. (If you do not remember your=20
> password, there is=20
> >>>>> a button here to have the system send you a password reminder.)
> >>>>>
> >>>>> 2) Under the "Changing your Ietf membership=20
> information" section,
> >>> enter
> >>>>> your new email address in the appropriate fields.
> >>>>>
> >>>>> 3) Check the "Change globally" box.
> >>>>>
> >>>>> 4) Hit the "Change My Address and Name" button.
> >>>>>
> >>>>> 5) You will receive an email at your new address asking you to
> >>> confirm
> >>>>> the change.
> >>>>>
> >>>>>
> >>>>> Best regards,
> >>>>>
> >>>>> Amy
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >
> >
> =

From pkyzivat@alum.mit.edu  Mon Jan 13 07:03:34 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 522831AE04F for <wgchairs@ietfa.amsl.com>; Mon, 13 Jan 2014 07:03:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p6Rfot-l7Rsb for <wgchairs@ietfa.amsl.com>; Mon, 13 Jan 2014 07:03:32 -0800 (PST)
Received: from qmta03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:32]) by ietfa.amsl.com (Postfix) with ESMTP id A66411ADFB6 for <wgchairs@ietf.org>; Mon, 13 Jan 2014 07:03:32 -0800 (PST)
Received: from omta14.westchester.pa.mail.comcast.net ([76.96.62.60]) by qmta03.westchester.pa.mail.comcast.net with comcast id DSBT1n0041HzFnQ53T3MJr; Mon, 13 Jan 2014 15:03:21 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta14.westchester.pa.mail.comcast.net with comcast id DT3M1n00Q3ZTu2S3aT3MYR; Mon, 13 Jan 2014 15:03:21 +0000
Message-ID: <52D40039.7080109@alum.mit.edu>
Date: Mon, 13 Jan 2014 10:03:21 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: How to globally change the email address for all IETF mailing lists?
References: <52D00EDE.8020308@cisco.com> <52D39F4F.6030900@cisco.com> <655C07320163294895BBADA28372AF5D161F8E@FR712WXCHMBA15.zeu.alcatel-lucent.com> <52D3A909.6070009@cisco.com> <655C07320163294895BBADA28372AF5D162001@FR712WXCHMBA15.zeu.alcatel-lucent.com> <52D3BF57.7070304@cisco.com>
In-Reply-To: <52D3BF57.7070304@cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1389625401; bh=DGEgMgPOCwYIvzPCKCbBZhCiFCMGtp5RYo3IZPan9cU=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=YXWBHNnaC5zwC4O8DxpyjONxjpRNK1c48J8RBIIoTSq2shlu0tFLM+iNyVSNiZpZz rI3d78JlPWmcHmaecMTOj6xS1QKLjMvmSKKgwpIXIrD1OAuCs5y+d6MMrSukkA82xn yUuDf8vRCFM03ZanZUXc6OR6SpcYh35gf8NDM7nvg8Ws2j3ikwKqT1bGvuuTm47oHP SsikzGM0f799kgNbUSoYXA5V2gp64+BCuEkicOg7/R9Kb/tDNI3NTf84PH9e96qoFu 8WYDc0yPTHeZSNiqDur0EJgVE9TThDO6JKoYlx042HCAHrWZL2DlhG/N4/ixKozezr JRXmqu8hzlucg==
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 15:03:34 -0000

IMO it is sufficient that when you start to change your address one list 
at a time, the form you get has the "Change Globally" box.

I've had to do this in the past and was pleasantly surprised to find 
this. I would not have thought to go searching for info elsewhere on how 
to do this.

	Thanks,
	Paul

On 1/13/14 5:26 AM, Benoit Claise wrote:
>
>> Why not publish the hint somewhere where non-chairs can find it, too?
> No problem to publish that, it's a small effort, but what's suitable
> place for this type of hints that are rarely used, independent (i.e. we
> don't have 10 hints on emails)?
> Personally, I'm a little skeptical by the approach to document
> everything on the web, in WIKIs for example IF this information is not
> maintained/updated and IF not properly advertised.
>
> Now, why didn't I send this on the IETF-discussion list instead of the
> WG chair list? No good reason.
> Maybe IETF-discussion is more appropriate...
>
> Regards, Benoit
>>
>> Michael
>>
>>
>>> -----Original Message-----
>>> From: Benoit Claise [mailto:bclaise@cisco.com]
>>> Sent: Monday, January 13, 2014 9:51 AM
>>> To: Scharf, Michael (Michael); WG Chairs
>>> Subject: Re: How to globally change the email address for all IETF
>>> mailing lists?
>>>
>>> Don't think so.
>>> Hence this email.
>>>
>>> Regards, Benoit
>>>> Is this useful hint mentioned somewhere on the IETF Web site?
>>>>
>>>> Michael
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of
>>> Benoit
>>>>> Claise
>>>>> Sent: Monday, January 13, 2014 9:10 AM
>>>>> To: WG Chairs
>>>>> Subject: How to globally change the email address for all IETF
>>> mailing
>>>>> lists?
>>>>>
>>>>> Dear all,
>>>>>
>>>>>    From time to time, we have the request of someone wanted to change
>>>>> her/his contact, so the following might be handy.
>>>>>
>>>>> You can globally change the email address for all the @ietf.org
>>> lists
>>>>> someone is
>>>>> subscribed to. You should take the following steps:
>>>>>
>>>>> 1) Go tohttps://www.ietf.org/mailman/options/ietf/<email-address>
>>>>>
>>>>> 2) Enter password. (If you do not remember your password, there is
>>>>> a button here to have the system send you a password reminder.)
>>>>>
>>>>> 2) Under the "Changing your Ietf membership information" section,
>>> enter
>>>>> your new email address in the appropriate fields.
>>>>>
>>>>> 3) Check the "Change globally" box.
>>>>>
>>>>> 4) Hit the "Change My Address and Name" button.
>>>>>
>>>>> 5) You will receive an email at your new address asking you to
>>> confirm
>>>>> the change.
>>>>>
>>>>>
>>>>> Best regards,
>>>>>
>>>>> Amy
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>
>


From warren@kumari.net  Mon Jan 13 07:19:32 2014
Return-Path: <warren@kumari.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F2291AE1F8 for <wgchairs@ietfa.amsl.com>; Mon, 13 Jan 2014 07:19:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HRNN7WQ68OUu for <wgchairs@ietfa.amsl.com>; Mon, 13 Jan 2014 07:19:30 -0800 (PST)
Received: from mail-wg0-f42.google.com (mail-wg0-f42.google.com [74.125.82.42]) by ietfa.amsl.com (Postfix) with ESMTP id 1F52D1AE1EE for <wgchairs@ietf.org>; Mon, 13 Jan 2014 07:19:29 -0800 (PST)
Received: by mail-wg0-f42.google.com with SMTP id l18so2880037wgh.1 for <wgchairs@ietf.org>; Mon, 13 Jan 2014 07:19:18 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=PxDpLDwiQo7twDSAc9m1ONZcPGj/Sa8A9KLQWBHw4FE=; b=fFdRL1zrN5Q9rYyHx3zhSR7TF+cE6epa98OU28D0Cd5jqUSV876Rqm8eYxmD0WvyXi UxA1RolkQu1CdQBJRcROAIK4MXTcIsyG6wlNRsA4SVCvWqgoy1XbxxUNXKviz8iphZcs sKwUxbrSTYfuzSWfoASmJRi5cvuTYcpMLFC0ZKktDPvS6DWsb+n5wYzkgEgFfj3fP2a1 IdtEXDDBrU79gSNdq4pejQxtmpoDjN+V5wkrnQ7pGYpOGAEhAL6zdb6S8awGkwRo5DtD zAomTLkXDpaqE0A7+8aisDNMURVMGSkIEhQsXuOM7jnNVsbuL092faPDJ/HrzPK1dSUU Xh2g==
X-Gm-Message-State: ALoCoQkL3vpBiqdsOxcnAdrB5FREjX0rpdAkmALD2z8NiqU+q7fr2SEb/oHhFlfaPItLeENJKp5R
MIME-Version: 1.0
X-Received: by 10.194.80.137 with SMTP id r9mr272469wjx.88.1389626358737; Mon, 13 Jan 2014 07:19:18 -0800 (PST)
Received: by 10.194.54.167 with HTTP; Mon, 13 Jan 2014 07:19:18 -0800 (PST)
X-Originating-IP: [98.244.98.35]
In-Reply-To: <52D3BF57.7070304@cisco.com>
References: <52D00EDE.8020308@cisco.com> <52D39F4F.6030900@cisco.com> <655C07320163294895BBADA28372AF5D161F8E@FR712WXCHMBA15.zeu.alcatel-lucent.com> <52D3A909.6070009@cisco.com> <655C07320163294895BBADA28372AF5D162001@FR712WXCHMBA15.zeu.alcatel-lucent.com> <52D3BF57.7070304@cisco.com>
Date: Mon, 13 Jan 2014 10:19:18 -0500
Message-ID: <CAHw9_iL9WQeoevmivufQmPV6O_yL0MXc20fkcnyBCufu=KwKXg@mail.gmail.com>
Subject: Re: How to globally change the email address for all IETF mailing lists?
From: Warren Kumari <warren@kumari.net>
To: Benoit Claise <bclaise@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 15:19:32 -0000

On Mon, Jan 13, 2014 at 5:26 AM, Benoit Claise <bclaise@cisco.com> wrote:
>
>> Why not publish the hint somewhere where non-chairs can find it, too?
>
> No problem to publish that, it's a small effort, but what's suitable place
> for this type of hints that are rarely used, independent (i.e. we don't have
> 10 hints on emails)?
> Personally, I'm a little skeptical by the approach to document everything on
> the web, in WIKIs for example IF this information is not maintained/updated
> and IF not properly advertised.


Well, it's now on the Chairs wiki as well, for a: those new chairs who
didn't get this mail and b: folk like me who have no memory...
http://wiki.tools.ietf.org/group/wgchairs/wiki/GlobalEmailChange

W

>
> Now, why didn't I send this on the IETF-discussion list instead of the WG
> chair list? No good reason.
> Maybe IETF-discussion is more appropriate...
>
> Regards, Benoit
>
>>
>> Michael
>>
>>
>>> -----Original Message-----
>>> From: Benoit Claise [mailto:bclaise@cisco.com]
>>> Sent: Monday, January 13, 2014 9:51 AM
>>> To: Scharf, Michael (Michael); WG Chairs
>>> Subject: Re: How to globally change the email address for all IETF
>>> mailing lists?
>>>
>>> Don't think so.
>>> Hence this email.
>>>
>>> Regards, Benoit
>>>>
>>>> Is this useful hint mentioned somewhere on the IETF Web site?
>>>>
>>>> Michael
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of
>>>
>>> Benoit
>>>>>
>>>>> Claise
>>>>> Sent: Monday, January 13, 2014 9:10 AM
>>>>> To: WG Chairs
>>>>> Subject: How to globally change the email address for all IETF
>>>
>>> mailing
>>>>>
>>>>> lists?
>>>>>
>>>>> Dear all,
>>>>>
>>>>>    From time to time, we have the request of someone wanted to change
>>>>> her/his contact, so the following might be handy.
>>>>>
>>>>> You can globally change the email address for all the @ietf.org
>>>
>>> lists
>>>>>
>>>>> someone is
>>>>> subscribed to. You should take the following steps:
>>>>>
>>>>> 1) Go tohttps://www.ietf.org/mailman/options/ietf/<email-address>
>>>>>
>>>>> 2) Enter password. (If you do not remember your password, there is
>>>>> a button here to have the system send you a password reminder.)
>>>>>
>>>>> 2) Under the "Changing your Ietf membership information" section,
>>>
>>> enter
>>>>>
>>>>> your new email address in the appropriate fields.
>>>>>
>>>>> 3) Check the "Change globally" box.
>>>>>
>>>>> 4) Hit the "Change My Address and Name" button.
>>>>>
>>>>> 5) You will receive an email at your new address asking you to
>>>
>>> confirm
>>>>>
>>>>> the change.
>>>>>
>>>>>
>>>>> Best regards,
>>>>>
>>>>> Amy
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>

From gvandeve@cisco.com  Mon Jan 13 07:39:05 2014
Return-Path: <gvandeve@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F7E81AE181 for <wgchairs@ietfa.amsl.com>; Mon, 13 Jan 2014 07:39:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.039
X-Spam-Level: 
X-Spam-Status: No, score=-10.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FnWEfDGx8TmS for <wgchairs@ietfa.amsl.com>; Mon, 13 Jan 2014 07:39:03 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) by ietfa.amsl.com (Postfix) with ESMTP id A23361AE15A for <wgchairs@ietf.org>; Mon, 13 Jan 2014 07:39:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3270; q=dns/txt; s=iport; t=1389627533; x=1390837133; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=WevPl51TzH/xkFHSVvw3nS5p8pXol/1mUCk14soGAZY=; b=XuKjY6OrXaK60lm1A5+tLBYJbTAPSwnBmKYDBcxbj9NKn2vTnIzAyYve eJSyY7JjfVsw3hirEvGD3bUhOw0/fH7vPbAvvnQinT+sntB9cFoq2OTvq riQvmGgPP0f/4uJwPHQIVzFHZ/0cUyGkCOuTey0kpj3Zv9Vt0vEgDMvDS M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiMFAFwH1FKtJV2b/2dsb2JhbABagws4VrltgRQWdIIlAQEBAwE6NAsMBAIBCBEEAQEBCg4GBgMHMhQJCAIEAQ0FCAGHcwgNrhqWWheOJRACAR4PIgcGEoMMgRMEmUeQZYMtgWgHOw
X-IronPort-AV: E=Sophos;i="4.95,653,1384300800"; d="scan'208";a="12475342"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-6.cisco.com with ESMTP; 13 Jan 2014 15:38:52 +0000
Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s0DFcqTs023208 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 13 Jan 2014 15:38:52 GMT
Received: from xmb-aln-x12.cisco.com ([169.254.7.104]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.03.0123.003; Mon, 13 Jan 2014 09:38:52 -0600
From: "Gunter Van de Velde (gvandeve)" <gvandeve@cisco.com>
To: Warren Kumari <warren@kumari.net>, "Benoit Claise (bclaise)" <bclaise@cisco.com>
Subject: RE: How to globally change the email address for all IETF mailing lists?
Thread-Topic: How to globally change the email address for all IETF mailing lists?
Thread-Index: AQHPEDcGU9/lLwTiNEuNqt5KLcym8ZqCuzoAgAACMICAAAFYAIAAGT6AgABRzgD//6CqwA==
Date: Mon, 13 Jan 2014 15:38:51 +0000
Message-ID: <67832B1175062E48926BF3CB27C49B240D3A7084@xmb-aln-x12.cisco.com>
References: <52D00EDE.8020308@cisco.com> <52D39F4F.6030900@cisco.com> <655C07320163294895BBADA28372AF5D161F8E@FR712WXCHMBA15.zeu.alcatel-lucent.com> <52D3A909.6070009@cisco.com> <655C07320163294895BBADA28372AF5D162001@FR712WXCHMBA15.zeu.alcatel-lucent.com> <52D3BF57.7070304@cisco.com> <CAHw9_iL9WQeoevmivufQmPV6O_yL0MXc20fkcnyBCufu=KwKXg@mail.gmail.com>
In-Reply-To: <CAHw9_iL9WQeoevmivufQmPV6O_yL0MXc20fkcnyBCufu=KwKXg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.61.213.174]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 15:39:05 -0000

Thanks Warren.

I think if its in the body of the monthly mail also, it is covered pretty w=
ell (even if in many cases it ends up often in the bitbucket)

G/

-----Original Message-----
From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of Warren Kumar=
i
Sent: 13 January 2014 16:19
To: Benoit Claise (bclaise)
Cc: WG Chairs
Subject: Re: How to globally change the email address for all IETF mailing =
lists?

On Mon, Jan 13, 2014 at 5:26 AM, Benoit Claise <bclaise@cisco.com> wrote:
>
>> Why not publish the hint somewhere where non-chairs can find it, too?
>
> No problem to publish that, it's a small effort, but what's suitable=20
> place for this type of hints that are rarely used, independent (i.e.=20
> we don't have
> 10 hints on emails)?
> Personally, I'm a little skeptical by the approach to document=20
> everything on the web, in WIKIs for example IF this information is not=20
> maintained/updated and IF not properly advertised.


Well, it's now on the Chairs wiki as well, for a: those new chairs who didn=
't get this mail and b: folk like me who have no memory...
http://wiki.tools.ietf.org/group/wgchairs/wiki/GlobalEmailChange

W

>
> Now, why didn't I send this on the IETF-discussion list instead of the=20
> WG chair list? No good reason.
> Maybe IETF-discussion is more appropriate...
>
> Regards, Benoit
>
>>
>> Michael
>>
>>
>>> -----Original Message-----
>>> From: Benoit Claise [mailto:bclaise@cisco.com]
>>> Sent: Monday, January 13, 2014 9:51 AM
>>> To: Scharf, Michael (Michael); WG Chairs
>>> Subject: Re: How to globally change the email address for all IETF=20
>>> mailing lists?
>>>
>>> Don't think so.
>>> Hence this email.
>>>
>>> Regards, Benoit
>>>>
>>>> Is this useful hint mentioned somewhere on the IETF Web site?
>>>>
>>>> Michael
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of
>>>
>>> Benoit
>>>>>
>>>>> Claise
>>>>> Sent: Monday, January 13, 2014 9:10 AM
>>>>> To: WG Chairs
>>>>> Subject: How to globally change the email address for all IETF
>>>
>>> mailing
>>>>>
>>>>> lists?
>>>>>
>>>>> Dear all,
>>>>>
>>>>>    From time to time, we have the request of someone wanted to=20
>>>>> change her/his contact, so the following might be handy.
>>>>>
>>>>> You can globally change the email address for all the @ietf.org
>>>
>>> lists
>>>>>
>>>>> someone is
>>>>> subscribed to. You should take the following steps:
>>>>>
>>>>> 1) Go tohttps://www.ietf.org/mailman/options/ietf/<email-address>
>>>>>
>>>>> 2) Enter password. (If you do not remember your password, there is=20
>>>>> a button here to have the system send you a password reminder.)
>>>>>
>>>>> 2) Under the "Changing your Ietf membership information" section,
>>>
>>> enter
>>>>>
>>>>> your new email address in the appropriate fields.
>>>>>
>>>>> 3) Check the "Change globally" box.
>>>>>
>>>>> 4) Hit the "Change My Address and Name" button.
>>>>>
>>>>> 5) You will receive an email at your new address asking you to
>>>
>>> confirm
>>>>>
>>>>> the change.
>>>>>
>>>>>
>>>>> Best regards,
>>>>>
>>>>> Amy
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>

From odonoghue@isoc.org  Mon Jan 13 07:44:25 2014
Return-Path: <odonoghue@isoc.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A29B01ADF53 for <wgchairs@ietfa.amsl.com>; Mon, 13 Jan 2014 07:44:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LjjyZ_Tkx-5o for <wgchairs@ietfa.amsl.com>; Mon, 13 Jan 2014 07:44:23 -0800 (PST)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0203.outbound.protection.outlook.com [207.46.163.203]) by ietfa.amsl.com (Postfix) with ESMTP id AC31C1ADF86 for <wgchairs@ietf.org>; Mon, 13 Jan 2014 07:44:22 -0800 (PST)
Received: from kodonog-mac.local (74.214.48.55) by CO2PR06MB588.namprd06.prod.outlook.com (10.141.229.154) with Microsoft SMTP Server (TLS) id 15.0.851.15; Mon, 13 Jan 2014 15:44:09 +0000
Message-ID: <52D409C9.1010707@isoc.org>
Date: Mon, 13 Jan 2014 10:44:09 -0500
From: Karen O'Donoghue <odonoghue@isoc.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: <wgchairs@ietf.org>
Subject: Re: How to globally change the email address for all IETF mailing lists?
References: <52D00EDE.8020308@cisco.com> <52D39F4F.6030900@cisco.com> <655C07320163294895BBADA28372AF5D161F8E@FR712WXCHMBA15.zeu.alcatel-lucent.com> <52D3A909.6070009@cisco.com> <655C07320163294895BBADA28372AF5D162001@FR712WXCHMBA15.zeu.alcatel-lucent.com> <52D3BF57.7070304@cisco.com> <CAHw9_iL9WQeoevmivufQmPV6O_yL0MXc20fkcnyBCufu=KwKXg@mail.gmail.com> <67832B1175062E48926BF3CB27C49B240D3A7084@xmb-aln-x12.cisco.com>
In-Reply-To: <67832B1175062E48926BF3CB27C49B240D3A7084@xmb-aln-x12.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [74.214.48.55]
X-ClientProxiedBy: BL2PR04CA003.namprd04.prod.outlook.com (10.255.226.23) To CO2PR06MB588.namprd06.prod.outlook.com (10.141.229.154)
X-Forefront-PRVS: 00909363D5
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019001)(13464003)(51704005)(24454002)(377454003)(479174003)(189002)(199002)(74876001)(87976001)(59766001)(77982001)(76796001)(76786001)(59896001)(76482001)(47446002)(15202345003)(56816005)(15975445006)(83072002)(74366001)(83506001)(85852003)(74502001)(81542001)(50466002)(81342001)(31966008)(4396001)(74706001)(90146001)(74662001)(85306002)(69226001)(80022001)(81686001)(23756003)(65956001)(66066001)(65806001)(47976001)(63696002)(47776003)(51856001)(80976001)(83322001)(19580395003)(47736001)(19580405001)(77096001)(80316001)(42186004)(79102001)(53806001)(54356001)(49866001)(50986001)(46102001)(33656001)(54316002)(56776001)(92726001)(81816001)(93136001)(92566001)(551544002)(64126003)(36756003); DIR:OUT; SFP:1102; SCL:1; SRVR:CO2PR06MB588; H:kodonog-mac.local; CLIP:74.214.48.55; FPR:; RD:InfoNoRecords; MX:1; A:1; LANG:en; 
X-OriginatorOrg: isoc.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 15:44:25 -0000

I second the idea of putting it in the reminder email as well. That's 
probably the first place I would think to look if I needed the info. The 
wiki is great (thanks Warren!) as long as it is maintained. Wrong 
information can be more annoying than no information. But, I would think 
this changes *very* rarely...

Karen

On 1/13/14 10:38 AM, Gunter Van de Velde (gvandeve) wrote:
> Thanks Warren.
>
> I think if its in the body of the monthly mail also, it is covered pretty well (even if in many cases it ends up often in the bitbucket)
>
> G/
>
> -----Original Message-----
> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of Warren Kumari
> Sent: 13 January 2014 16:19
> To: Benoit Claise (bclaise)
> Cc: WG Chairs
> Subject: Re: How to globally change the email address for all IETF mailing lists?
>
> On Mon, Jan 13, 2014 at 5:26 AM, Benoit Claise <bclaise@cisco.com> wrote:
>>> Why not publish the hint somewhere where non-chairs can find it, too?
>> No problem to publish that, it's a small effort, but what's suitable
>> place for this type of hints that are rarely used, independent (i.e.
>> we don't have
>> 10 hints on emails)?
>> Personally, I'm a little skeptical by the approach to document
>> everything on the web, in WIKIs for example IF this information is not
>> maintained/updated and IF not properly advertised.
>
> Well, it's now on the Chairs wiki as well, for a: those new chairs who didn't get this mail and b: folk like me who have no memory...
> http://wiki.tools.ietf.org/group/wgchairs/wiki/GlobalEmailChange
>
> W
>
>> Now, why didn't I send this on the IETF-discussion list instead of the
>> WG chair list? No good reason.
>> Maybe IETF-discussion is more appropriate...
>>
>> Regards, Benoit
>>
>>> Michael
>>>
>>>
>>>> -----Original Message-----
>>>> From: Benoit Claise [mailto:bclaise@cisco.com]
>>>> Sent: Monday, January 13, 2014 9:51 AM
>>>> To: Scharf, Michael (Michael); WG Chairs
>>>> Subject: Re: How to globally change the email address for all IETF
>>>> mailing lists?
>>>>
>>>> Don't think so.
>>>> Hence this email.
>>>>
>>>> Regards, Benoit
>>>>> Is this useful hint mentioned somewhere on the IETF Web site?
>>>>>
>>>>> Michael
>>>>>
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of
>>>> Benoit
>>>>>> Claise
>>>>>> Sent: Monday, January 13, 2014 9:10 AM
>>>>>> To: WG Chairs
>>>>>> Subject: How to globally change the email address for all IETF
>>>> mailing
>>>>>> lists?
>>>>>>
>>>>>> Dear all,
>>>>>>
>>>>>>     From time to time, we have the request of someone wanted to
>>>>>> change her/his contact, so the following might be handy.
>>>>>>
>>>>>> You can globally change the email address for all the @ietf.org
>>>> lists
>>>>>> someone is
>>>>>> subscribed to. You should take the following steps:
>>>>>>
>>>>>> 1) Go tohttps://www.ietf.org/mailman/options/ietf/<email-address>
>>>>>>
>>>>>> 2) Enter password. (If you do not remember your password, there is
>>>>>> a button here to have the system send you a password reminder.)
>>>>>>
>>>>>> 2) Under the "Changing your Ietf membership information" section,
>>>> enter
>>>>>> your new email address in the appropriate fields.
>>>>>>
>>>>>> 3) Check the "Change globally" box.
>>>>>>
>>>>>> 4) Hit the "Change My Address and Name" button.
>>>>>>
>>>>>> 5) You will receive an email at your new address asking you to
>>>> confirm
>>>>>> the change.
>>>>>>
>>>>>>
>>>>>> Best regards,
>>>>>>
>>>>>> Amy
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>


From bclaise@cisco.com  Tue Jan 14 00:36:51 2014
Return-Path: <bclaise@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87FBD1ACCE9 for <wgchairs@ietfa.amsl.com>; Tue, 14 Jan 2014 00:36:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.039
X-Spam-Level: 
X-Spam-Status: No, score=-10.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2K7cHE6k-j4P for <wgchairs@ietfa.amsl.com>; Tue, 14 Jan 2014 00:36:49 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id 07FEC1AE222 for <wgchairs@ietf.org>; Tue, 14 Jan 2014 00:36:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4066; q=dns/txt; s=iport; t=1389688598; x=1390898198; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=tUV2HYUt4t4O1uZ9AeUKMm1XiHSc76M89j6XWdZ9X1s=; b=D1dP+SH1yC2eX2cEhWzv8nRwqLfGVc6WnH+lpt8ehwfTN/z5zHR0rDlQ eN+5tDTeuO0v0OExYqsDxQC7Ob2nK/YHlDaTUEvTKi4fbFoLK8Jn7QEGZ VkkmoH0l3dmRhtJyeNcB4iDzg/tBCcMOtEusgQZvJqVgaNIEdT2C4ijfV U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiEFAA721FKQ/khM/2dsb2JhbABagws4uyABCIEPFnSCJQEBAQQ4NgoNBAsRBAEBAQkPBwUDBwkDAgECATQJCAYBDAYCAQEFh3sNrlKWXReOJRACASktBhKEHwEDmB6BMIUVhhiFOIMuO4EsBw
X-IronPort-AV: E=Sophos;i="4.95,657,1384300800";  d="scan'208";a="3597536"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by aer-iport-1.cisco.com with ESMTP; 14 Jan 2014 08:36:36 +0000
Received: from [10.60.67.85] (ams-bclaise-8914.cisco.com [10.60.67.85]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s0E8aaUY028866; Tue, 14 Jan 2014 08:36:36 GMT
Message-ID: <52D4F714.7040808@cisco.com>
Date: Tue, 14 Jan 2014 09:36:36 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "Karen O'Donoghue" <odonoghue@isoc.org>, wgchairs@ietf.org
Subject: Re: How to globally change the email address for all IETF mailing lists?
References: <52D00EDE.8020308@cisco.com> <52D39F4F.6030900@cisco.com> <655C07320163294895BBADA28372AF5D161F8E@FR712WXCHMBA15.zeu.alcatel-lucent.com> <52D3A909.6070009@cisco.com> <655C07320163294895BBADA28372AF5D162001@FR712WXCHMBA15.zeu.alcatel-lucent.com> <52D3BF57.7070304@cisco.com> <CAHw9_iL9WQeoevmivufQmPV6O_yL0MXc20fkcnyBCufu=KwKXg@mail.gmail.com> <67832B1175062E48926BF3CB27C49B240D3A7084@xmb-aln-x12.cisco.com> <52D409C9.1010707@isoc.org>
In-Reply-To: <52D409C9.1010707@isoc.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 08:36:51 -0000

On 13/01/2014 16:44, Karen O'Donoghue wrote:
> I second the idea of putting it in the reminder email as well. 
I opened a case to add "Instructions for changing a subscriber address 
globally can be found at: http://www.ietf.org/list/" in the "ietf.org 
mailing list memberships reminder" email

Regards, Benoit
> That's probably the first place I would think to look if I needed the 
> info. The wiki is great (thanks Warren!) as long as it is maintained. 
> Wrong information can be more annoying than no information. But, I 
> would think this changes *very* rarely...
>
> Karen
>
> On 1/13/14 10:38 AM, Gunter Van de Velde (gvandeve) wrote:
>> Thanks Warren.
>>
>> I think if its in the body of the monthly mail also, it is covered 
>> pretty well (even if in many cases it ends up often in the bitbucket)
>>
>> G/
>>
>> -----Original Message-----
>> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of Warren 
>> Kumari
>> Sent: 13 January 2014 16:19
>> To: Benoit Claise (bclaise)
>> Cc: WG Chairs
>> Subject: Re: How to globally change the email address for all IETF 
>> mailing lists?
>>
>> On Mon, Jan 13, 2014 at 5:26 AM, Benoit Claise <bclaise@cisco.com> 
>> wrote:
>>>> Why not publish the hint somewhere where non-chairs can find it, too?
>>> No problem to publish that, it's a small effort, but what's suitable
>>> place for this type of hints that are rarely used, independent (i.e.
>>> we don't have
>>> 10 hints on emails)?
>>> Personally, I'm a little skeptical by the approach to document
>>> everything on the web, in WIKIs for example IF this information is not
>>> maintained/updated and IF not properly advertised.
>>
>> Well, it's now on the Chairs wiki as well, for a: those new chairs 
>> who didn't get this mail and b: folk like me who have no memory...
>> http://wiki.tools.ietf.org/group/wgchairs/wiki/GlobalEmailChange
>>
>> W
>>
>>> Now, why didn't I send this on the IETF-discussion list instead of the
>>> WG chair list? No good reason.
>>> Maybe IETF-discussion is more appropriate...
>>>
>>> Regards, Benoit
>>>
>>>> Michael
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: Benoit Claise [mailto:bclaise@cisco.com]
>>>>> Sent: Monday, January 13, 2014 9:51 AM
>>>>> To: Scharf, Michael (Michael); WG Chairs
>>>>> Subject: Re: How to globally change the email address for all IETF
>>>>> mailing lists?
>>>>>
>>>>> Don't think so.
>>>>> Hence this email.
>>>>>
>>>>> Regards, Benoit
>>>>>> Is this useful hint mentioned somewhere on the IETF Web site?
>>>>>>
>>>>>> Michael
>>>>>>
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of
>>>>> Benoit
>>>>>>> Claise
>>>>>>> Sent: Monday, January 13, 2014 9:10 AM
>>>>>>> To: WG Chairs
>>>>>>> Subject: How to globally change the email address for all IETF
>>>>> mailing
>>>>>>> lists?
>>>>>>>
>>>>>>> Dear all,
>>>>>>>
>>>>>>>     From time to time, we have the request of someone wanted to
>>>>>>> change her/his contact, so the following might be handy.
>>>>>>>
>>>>>>> You can globally change the email address for all the @ietf.org
>>>>> lists
>>>>>>> someone is
>>>>>>> subscribed to. You should take the following steps:
>>>>>>>
>>>>>>> 1) Go tohttps://www.ietf.org/mailman/options/ietf/<email-address>
>>>>>>>
>>>>>>> 2) Enter password. (If you do not remember your password, there is
>>>>>>> a button here to have the system send you a password reminder.)
>>>>>>>
>>>>>>> 2) Under the "Changing your Ietf membership information" section,
>>>>> enter
>>>>>>> your new email address in the appropriate fields.
>>>>>>>
>>>>>>> 3) Check the "Change globally" box.
>>>>>>>
>>>>>>> 4) Hit the "Change My Address and Name" button.
>>>>>>>
>>>>>>> 5) You will receive an email at your new address asking you to
>>>>> confirm
>>>>>>> the change.
>>>>>>>
>>>>>>>
>>>>>>> Best regards,
>>>>>>>
>>>>>>> Amy
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>
> .
>


From agenda@ietf.org  Tue Jan 14 08:52:21 2014
Return-Path: <agenda@ietf.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 524521AE0D6; Tue, 14 Jan 2014 08:52:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 48WxZG2905GF; Tue, 14 Jan 2014 08:52:18 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E7031AE11C; Tue, 14 Jan 2014 08:52:18 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Agenda <agenda@ietf.org>
To: Working Group Chairs <wgchairs@ietf.org>
Subject: 89th IETF - Working Group/BOF/IRTF Scheduling - Cut-Off Friday
X-Test-IDTracker: no
X-IETF-IDTracker: 4.90.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140114165217.4985.60278.idtracker@ietfa.amsl.com>
Date: Tue, 14 Jan 2014 08:52:17 -0800
Cc: irsg@irtf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: IETF Agenda <agenda@ietf.org>
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 16:52:21 -0000

-----------------------------------------------------------------
89th IETF =E2=80=93 London, England
Meeting Dates: March 2 =E2=80=93 7, 2014
-----------------------------------------------------------------
IETF meetings start Monday morning and run through Friday afternoon (13:30).

The milestones and deadlines for scheduling-related activities are as follo=
ws:

NOTE: cutoff dates are subject to change.

=E2=80=A2	2014-01-17 (Friday): Cut-off date for requests to schedule Workin=
g Group meetings at UTC 23:59. To request a Working Group session, use the =
IETF Meeting Session Request Tool.
=E2=80=A2	2014-01-17 (Friday): Cut-off date for BOF proposal requests to Ar=
ea Directors at UTC 23:59. To request a BOF, please see instructions on Req=
uesting a BOF.
=E2=80=A2	2014-01-24 (Friday): Cut-off date for Area Directors to approve B=
OFs at UTC 23:59.
=E2=80=A2	2014-01-31 (Friday): Preliminary agenda published for comment.
=E2=80=A2	2014-02-03 (Monday): Cut-off date for requests to reschedule Work=
ing Group and BOF meetings UTC 23:59.
=E2=80=A2	2014-02-07 (Friday): Final agenda to be published.
=E2=80=A2	2014-02-17 (Monday): Draft Working Group agendas due by UTC 23:59=
, upload using IETF Meeting Materials Management Tool.
=E2=80=A2	2014-02-24 (Monday): Revised Working Group agendas due by UTC 23:=
59, upload using IETF Meeting Materials Management Tool.
=E2=80=A2	2014-03-28 (Friday): Proceedings submission cutoff date by UTC 23=
:59, upload using IETF Meeting Materials Management Tool.
=E2=80=A2	2014-04-18 (Friday): Proceedings submission corrections cutoff da=
te by UTC 23:59, upload using IETF Meeting Materials Management Tool.

Submitting Requests for Working Group and BOF Sessions

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

The URL for the tool is:

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

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

Submitting Session Agendas

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

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

The URL for the tool is:

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

Additional information about this tool is available at:

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

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

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

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

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

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

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

Instructions for using the tool are available at:

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

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

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

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

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

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

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

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


    b. AREA under which Working Group or BOF appears:

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

    d. Expected Attendance:

    e. Special requests:

    f. Number of sessions:

    g. Length of session: =

       - 1 hour =

       - 1 1/2 hours
       - 2 hours =

       - 2 1/2 hours

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

IETF Chair =

Jari Arkko <jari.arkko@piuha.net>

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

Internet Area (int) =

Brian Haberman <brian@innovationslab.net> =

Ted Lemon <ted.lemon@nominum.com>

Operations & Management Area (ops) =

Benoit Claise <bclaise@cisco.com> =

Joel Jaeggli <joelja@bogus.com>

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


Routing Area (rtg) =

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


Security Area (sec) =

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


Transport Area (tsv) =

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

Spencer Dawkins  <spencerdawkins.ietf@gmail.com>
 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
88th IETF Meeting Attendance Numbers

6lo - 52
6man - 143
6tisch - 45
abfab - 20
alto  - 35
appsawg/apparea - 138
aqm - 108
aqm (2nd session) - 45
avtcore - 51
avtext =E2=80=93 59
bfd - 17
bmwg - 19
ccamp - 49
ccamp (2nd session) - 44
cdni - 39
clue - 41
clue (2nd session) - 32
core - 62
core (2nd session) - 50
dhc - 59
dice - 65
dime - 23
dispatch - 55
dmm - 37
dnsop - 125
dnssd - 108
ecrit - 31
eman - 19
forces - 40
geonet (BoF) - 99
geopriv - 41
homenet - 156
httpauth - 43
httpbis - 89
httpbis (2nd session) - 127
i2rs - 223
iccrg (RG) - 68
icnrg (RG) - 43
idr - 90
igovupdate BoF - 220
insipid - 32
intarea (AG) - 98
ipfix - 23
ippm - 48
ipsecme - 27
IRTF Open Meeting - 100
isis - 58
jose - 42
json - 49
karp - 22
kitten - 23
l2vpn - 71
l3vpn - 65
lisp - 56
lmap - 52
lwig - 35
manet - 35
mboned - 25
mif - 41
mmusic - 69
mmusic (2nd session) - 53
mpls - 71
mpls (2nd session) - 72
mptcp - 45
mptcp (2nd session) - 70
ncrg (RG) - 33
netconf - 62
netext - 27
netmod - 69
nfsv4 - 16
nmrg (RG) - 35
nmrg (RG) (2nd session) - 17
ntp (combined with tictoc) - 32
nvo3 - 193
nwcrg (PRG) - 25
oauth - 38
opsawg/opsarea - 68
opsec - 48
ospf - 38
paws - 17
pce - 72
pcp - 30
perpass (BoF) - 313
pim - 24
ppsp - 12
precis - 32
pwe3 - 40
radext - 20
rfcform (BoF) - 52
rmcat - 60
rtcweb - 174
rtcweb (2nd session) - 188
rtgarea (AG) - 101
rtgwg - 118
saag (AG) - 148
sacm - 40
scim - 32
sdnrg (RG) - 259
sidr - 61
siprec - 31
softwire - 52
spring - 158
stir - 82
stir (2nd session) - 79
storm - 21
tcpm - 36
tictoc (combined with ntp) - 32
tls - 111
trill - 33
tsvarea (AG) - 153
tsvwg - 63
tsvwg (2nd session) - 47
v6ops - 135
v6ops (2nd session) - 92
weirds - 55
wpkops - 34
xmpp - 31
xrblock - 24

From bclaise@cisco.com  Wed Jan 15 05:01:19 2014
Return-Path: <bclaise@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C9D91AE1CF for <wgchairs@ietfa.amsl.com>; Wed, 15 Jan 2014 05:01:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.039
X-Spam-Level: 
X-Spam-Status: No, score=-10.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2Woe5JDEkQCj for <wgchairs@ietfa.amsl.com>; Wed, 15 Jan 2014 05:01:17 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id 1CD541AE04E for <wgchairs@ietf.org>; Wed, 15 Jan 2014 05:01:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4331; q=dns/txt; s=iport; t=1389790865; x=1391000465; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=v0MJV78t5yRAXr64ZcxIdS0691ZhJRW0WrGhimbTJoI=; b=REhT4tMMSa6we/EiM73+inHbEH1ReyXcSlmPCO/Yk5go9WZc8F2j16RI iJqrbq8QE4p4SZpkUJdgK/e2mbJ+U8iiMxYBlPO1/UCQ3iU7pYIdKitZW G+MGYPJVTnUzHQNPDkihgjkYZzUzXK0nFbVKU80B2Z/uVCdDFygWmLPEq c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ai0FAAqG1lKQ/khN/2dsb2JhbABagws4u0oBCIEUFnSCJQEBAQQ4NgoNBAsRBAEBAQkPBwUDBwkDAgECATQJCAYBDAYCAQEFh3sNrEiXTheOJRACASktBhKEHwEDmB6BMIUVhhiFOIMuO4EsBw
X-IronPort-AV: E=Sophos;i="4.95,663,1384300800";  d="scan'208";a="3660520"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by aer-iport-1.cisco.com with ESMTP; 15 Jan 2014 13:01:04 +0000
Received: from [10.60.67.85] (ams-bclaise-8914.cisco.com [10.60.67.85]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s0FD14l9016389; Wed, 15 Jan 2014 13:01:04 GMT
Message-ID: <52D68690.5030403@cisco.com>
Date: Wed, 15 Jan 2014 14:01:04 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "Karen O'Donoghue" <odonoghue@isoc.org>, wgchairs@ietf.org
Subject: Re: How to globally change the email address for all IETF mailing lists?
References: <52D00EDE.8020308@cisco.com> <52D39F4F.6030900@cisco.com> <655C07320163294895BBADA28372AF5D161F8E@FR712WXCHMBA15.zeu.alcatel-lucent.com> <52D3A909.6070009@cisco.com> <655C07320163294895BBADA28372AF5D162001@FR712WXCHMBA15.zeu.alcatel-lucent.com> <52D3BF57.7070304@cisco.com> <CAHw9_iL9WQeoevmivufQmPV6O_yL0MXc20fkcnyBCufu=KwKXg@mail.gmail.com> <67832B1175062E48926BF3CB27C49B240D3A7084@xmb-aln-x12.cisco.com> <52D409C9.1010707@isoc.org> <52D4F714.7040808@cisco.com>
In-Reply-To: <52D4F714.7040808@cisco.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.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 13:01:19 -0000

On 14/01/2014 09:36, Benoit Claise wrote:
> On 13/01/2014 16:44, Karen O'Donoghue wrote:
>> I second the idea of putting it in the reminder email as well. 
> I opened a case to add "Instructions for changing a subscriber address 
> globally can be found at: http://www.ietf.org/list/" in the "ietf.org 
> mailing list memberships reminder" email
Done.
Now, don't automatically throw away those emails :-)

Regards, Benoit
>
> Regards, Benoit
>> That's probably the first place I would think to look if I needed the 
>> info. The wiki is great (thanks Warren!) as long as it is maintained. 
>> Wrong information can be more annoying than no information. But, I 
>> would think this changes *very* rarely...
>>
>> Karen
>>
>> On 1/13/14 10:38 AM, Gunter Van de Velde (gvandeve) wrote:
>>> Thanks Warren.
>>>
>>> I think if its in the body of the monthly mail also, it is covered 
>>> pretty well (even if in many cases it ends up often in the bitbucket)
>>>
>>> G/
>>>
>>> -----Original Message-----
>>> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of 
>>> Warren Kumari
>>> Sent: 13 January 2014 16:19
>>> To: Benoit Claise (bclaise)
>>> Cc: WG Chairs
>>> Subject: Re: How to globally change the email address for all IETF 
>>> mailing lists?
>>>
>>> On Mon, Jan 13, 2014 at 5:26 AM, Benoit Claise <bclaise@cisco.com> 
>>> wrote:
>>>>> Why not publish the hint somewhere where non-chairs can find it, too?
>>>> No problem to publish that, it's a small effort, but what's suitable
>>>> place for this type of hints that are rarely used, independent (i.e.
>>>> we don't have
>>>> 10 hints on emails)?
>>>> Personally, I'm a little skeptical by the approach to document
>>>> everything on the web, in WIKIs for example IF this information is not
>>>> maintained/updated and IF not properly advertised.
>>>
>>> Well, it's now on the Chairs wiki as well, for a: those new chairs 
>>> who didn't get this mail and b: folk like me who have no memory...
>>> http://wiki.tools.ietf.org/group/wgchairs/wiki/GlobalEmailChange
>>>
>>> W
>>>
>>>> Now, why didn't I send this on the IETF-discussion list instead of the
>>>> WG chair list? No good reason.
>>>> Maybe IETF-discussion is more appropriate...
>>>>
>>>> Regards, Benoit
>>>>
>>>>> Michael
>>>>>
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Benoit Claise [mailto:bclaise@cisco.com]
>>>>>> Sent: Monday, January 13, 2014 9:51 AM
>>>>>> To: Scharf, Michael (Michael); WG Chairs
>>>>>> Subject: Re: How to globally change the email address for all IETF
>>>>>> mailing lists?
>>>>>>
>>>>>> Don't think so.
>>>>>> Hence this email.
>>>>>>
>>>>>> Regards, Benoit
>>>>>>> Is this useful hint mentioned somewhere on the IETF Web site?
>>>>>>>
>>>>>>> Michael
>>>>>>>
>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of
>>>>>> Benoit
>>>>>>>> Claise
>>>>>>>> Sent: Monday, January 13, 2014 9:10 AM
>>>>>>>> To: WG Chairs
>>>>>>>> Subject: How to globally change the email address for all IETF
>>>>>> mailing
>>>>>>>> lists?
>>>>>>>>
>>>>>>>> Dear all,
>>>>>>>>
>>>>>>>>     From time to time, we have the request of someone wanted to
>>>>>>>> change her/his contact, so the following might be handy.
>>>>>>>>
>>>>>>>> You can globally change the email address for all the @ietf.org
>>>>>> lists
>>>>>>>> someone is
>>>>>>>> subscribed to. You should take the following steps:
>>>>>>>>
>>>>>>>> 1) Go tohttps://www.ietf.org/mailman/options/ietf/<email-address>
>>>>>>>>
>>>>>>>> 2) Enter password. (If you do not remember your password, there is
>>>>>>>> a button here to have the system send you a password reminder.)
>>>>>>>>
>>>>>>>> 2) Under the "Changing your Ietf membership information" section,
>>>>>> enter
>>>>>>>> your new email address in the appropriate fields.
>>>>>>>>
>>>>>>>> 3) Check the "Change globally" box.
>>>>>>>>
>>>>>>>> 4) Hit the "Change My Address and Name" button.
>>>>>>>>
>>>>>>>> 5) You will receive an email at your new address asking you to
>>>>>> confirm
>>>>>>>> the change.
>>>>>>>>
>>>>>>>>
>>>>>>>> Best regards,
>>>>>>>>
>>>>>>>> Amy
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>
>> .
>>
>
> .
>


From chair@ietf.org  Thu Jan 16 11:21:34 2014
Return-Path: <chair@ietf.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAC681AC499; Thu, 16 Jan 2014 11:21:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lFGZJr0NoRpf; Thu, 16 Jan 2014 11:21:33 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:15]) by ietfa.amsl.com (Postfix) with ESMTP id 8D5F41A1F66; Thu, 16 Jan 2014 11:21:33 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id F29ACA60E7; Thu, 16 Jan 2014 11:19:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c9a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BMfrS_JrZ4TO; Thu, 16 Jan 2014 11:19:05 -0800 (PST)
Received: from [10.30.0.138] (unknown [83.150.71.93]) by c9a.amsl.com (Postfix) with ESMTPSA id 1010CA60BA; Thu, 16 Jan 2014 11:19:04 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Subject: REMINDER: BOF deadline coming up
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: IETF Chair <chair@ietf.org>
Date: Thu, 16 Jan 2014 21:21:17 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <F48FB135-DC1E-47B6-A399-64905DA730EA@ietf.org>
To: "ietf-announce@ietf.org" <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1510)
Cc: Working Group Chairs <wgchairs@ietf.org>, "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: "ietf@ietf.org Discussion" <ietf@ietf.org>
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2014 19:21:34 -0000

The IETF-89 deadline for new work proposals (BOF sessions) is coming up =
fast. The deadline is tomorrow, Friday, January 17th. See:

http://www.ietf.org/meeting/important-dates-2014.html#IETF89

Jari


From ietf-secretariat@ietf.org  Thu Jan 16 11:52:57 2014
Return-Path: <ietf-secretariat@ietf.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F0271AC829; Thu, 16 Jan 2014 11:52:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.198
X-Spam-Level: 
X-Spam-Status: No, score=-3.198 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FUZZY_CPILL=0.001, GB_I_INVITATION=-2, GB_I_LETTER=-2, LOTS_OF_MONEY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WqYTXkU1hW5z; Thu, 16 Jan 2014 11:52:32 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 223781AC499; Thu, 16 Jan 2014 11:52:32 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: IETF 89 London Hotel Almost Filled!
X-Test-IDTracker: no
X-IETF-IDTracker: 4.90.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140116195231.2994.71112.idtracker@ietfa.amsl.com>
Date: Thu, 16 Jan 2014 11:52:31 -0800
Cc: wgchairs@ietf.org, recentattendees@ietf.org, irsg@irtf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: agenda@ietf.org
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2014 19:52:57 -0000

89th IETF Meeting
London, England
March 2-7, 2014
Host: ICANN

Meeting venue:  Hilton London Metropole: http://www.hiltonlondonmet.com/
Hotel Reservations: http://www.hilton.com/en/hi/groups/personalized/L/LONME=
TW-GINTA-20140226/index.jhtml
Register online at: http://www.ietf.org/meetings/89/

1.  Registration
2.  Visas & Letters of Invitation
3.  Accommodations - IETF block is almost fully booked.
4.  Bits-N-Bites
5.  Companion Program

1. Registration
A. Early-Bird Registration - USD 650.00 Pay by Friday, 21 February 2014 UTC=
 23:59
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,
          24 February 2014 at UTC 23:59.
          Cancellations are subject to a 10% (ten percent)
          cancellation fee if requested by that date and time.
F. Online Registration and Payment ends Friday, 28 February 2014, 1700 loca=
l London time.
G. On-site Registration starting Sunday, 2 March 2014 at 1100 local London =
time.

2. Visas & Letters of Invitation:
Information on Visiting the UK, please visit:
http://www.ukba.homeoffice.gov.uk/visas-immigration/do-you-need-a-visa/ and
http://www.ukba.homeoffice.gov.uk/visas-immigration/

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

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

3.  Accommodations
PLEASE NOTE: The IETF block at the Hilton is filling up quickly!

The IETF is holding a block of guest rooms at the Hilton London Metropole, =
the meeting venue.
Room Rates include in room high-speed Internet access, English breakfast an=
d taxes (which are subject to change).

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

4.  Bits-N-Bites
Technology & Networking Social
IETF 89 Meeting - London, UK
Hilton London Metropole
Date: 6 March 2014
Time: 19:00-21:00

Bits-N-Bites is focused on Internet standards, technology and related subje=
cts. Nearly 1,200 engineers, computer scientists and academicians, who are =
in the forefront of developing standards for the continuing expansion and r=
obustness of the Internet from more than 40 countries and leading corporati=
ons worldwide, will meet at IETF 89 in London.
Exhibitors, product vendors, and service providers will be able to share in=
formation and showcase products and services to IETF community in a social =
setting with hors d'oeuvres and cocktails.

Each exhibitor table will include:
   =E2=80=A2 Electricity
   =E2=80=A2	Access to the IETF wireless network.
   =E2=80=A2	A table (minimum 6=E2=80=99) or space for alternate display fo=
r companies that already have an exhibition display/booth they might like t=
o use.

Additional Benefits
   =E2=80=A2	Two (2) complimentary full conference registrations to the IET=
F Meeting
   =E2=80=A2	Signage at the event
   =E2=80=A2	Sponsor Logo on the IETF meeting website, with link to Sponsor=
 website (or page of your own design)
   =E2=80=A2	Logo and recognition in the IETF Program
   =E2=80=A2	Acknowledgement at the Plenary and in the Proceedings of the M=
eeting.

Contribution: $10,000

If your organization is interested in face-to-face time with hundreds of IE=
TF participants, please contact Drew Dvorshak <dvorshak@isoc.org> or Emma F=
rost <frost@isoc.org> to sponsor a table.

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

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

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

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

Only 45 days until the London IETF!

From Ted.Lemon@nominum.com  Thu Jan 16 19:04:08 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 026841ADDCA for <wgchairs@ietfa.amsl.com>; Thu, 16 Jan 2014 19:04:08 -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=[BAYES_00=-1.9, GB_I_INVITATION=-2, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Oa7G0rjoDEhd for <wgchairs@ietfa.amsl.com>; Thu, 16 Jan 2014 19:04:06 -0800 (PST)
Received: from exprod7og103.obsmtp.com (exprod7og103.obsmtp.com [64.18.2.159]) by ietfa.amsl.com (Postfix) with ESMTP id 2EE5D1AC4AB for <wgchairs@ietf.org>; Thu, 16 Jan 2014 19:04:06 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob103.postini.com ([64.18.6.12]) with SMTP ID DSNKUtidmQSHfvlG9uJdTWnYpcuZQN36sZzw@postini.com; Thu, 16 Jan 2014 19:03:54 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id B66AD1B82B9 for <wgchairs@ietf.org>; Thu, 16 Jan 2014 19:03:53 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 89D7D19005C; Thu, 16 Jan 2014 19:03:53 -0800 (PST)
Received: from divertimento.ddns.nominum.com (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 16 Jan 2014 19:03:53 -0800
From: Ted Lemon <ted.lemon@nominum.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Subject: Document language editing session in London
Date: Thu, 16 Jan 2014 19:03:52 -0800
Message-ID: <D6557C43-1445-4660-804D-BD17ED9DD486@nominum.com>
To: "wgchairs@ietf.org Chairs" <wgchairs@ietf.org>
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Cc: "Heather Flanagan \(RFC Series Editor\)" <rse@rfc-editor.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jan 2014 03:04:08 -0000

Dear WG Chairs:

The IESG has decided to repeat the experiment that we tried in Berlin at =
the upcoming London IETF meeting.   We would like to invite ten document =
authors to a language editing session in London on the Saturday prior to =
the IETF meeting.   The goal of this editing session will be for two =
area directors, me and Joel Jaeggli, to each sit with a group of five =
document editors and work on each editors' document for 30 minutes in a =
group setting.   Benoit Claise has also offered to help if there are any =
French-speaking authors who would like to participate.

The plan for this work is to do two things: first, to review the =
documents, and secondly, for the participants to have the opportunity to =
work with Joel or with me to improve the quality of their documents.   =
The goal is specifically for non-native english speakers who have =
documents that the working group considers important, but which are felt =
to need help with english language editing.   It is important that the =
authors _want_ to get help=97that they recognize that they could use =
help and that they are comfortable getting that help in a small group =
setting.

What the meeting will look like is that there will be one or two tables =
in a meeting room; I will be at one table with five authors and a =
representative from the RFC Editor.   Joel will be at a separate table, =
with the same arrangement.   If there aren't enough authors, we may do a =
single table, as we did in Berlin.

Each of us will have briefly reviewed the five documents prior to the =
meeting, and we expect that the authors will be familiar with each =
others' documents as well.   For thirty minutes per document, we will =
sit with the author and go over the document, offering comments and =
suggestions and getting feedback from the author.   The other authors =
will follow this. Then we will move on to the next author.   Joel will =
be doing the same thing at the other table.   The RFC Editor will be =
observing and offering advice on request, or if they can't resist, but =
the main goal is to take advantage of the technical editorial expertise =
of the two ADs for this experiment.   At the end of the editing session, =
we will have a half hour session where we talk about what went well, if =
anything, and what went wrong, if anything, and how we might do it =
better next time.

Neither Joel nor I are experts on teaching english to non-native =
speakers, so we do not claim any specific knowledge other than that we =
both have a keen interest in improving the quality of IETF documents, a =
fair amount of experience in at least trying to do so, and a desire to =
help our colleagues to accomplish their goals.

Our desired outcome from this meeting is twofold: first, to help the =
specific authors who attend; secondly, to learn how to help authors in =
general: what frustrations they have in writing documents for IETF, what =
stumbling blocks they trip over, and how we can help them.

What we are asking working group chairs to do is think about whether =
there are documents in their working group that could use this sort of =
help.   If you believe there are, please contact the authors of those =
documents and ask them in a non-pushy way whether they would like to =
participate in this experiment.   Please let us know if any of your =
authors are interested in this.   If you have more than one document =
that you'd like worked on, please tell us which one is most important to =
you.   We will have to do a triage process unless the response to this =
call for participants is tiny, so it's likely that we will only take the =
document you think is more important.   If we get a really good =
response, we won't be able to take documents from every working group =
that responds; please don't take this as a criticism if your document =
isn't chosen.

If you think this is a good idea and want to take advantage of it, =
please contact your authors as soon as possible, so that they can make =
travel plans that allow them to get to the venue on Saturday rather than =
on Sunday.   Please bear in mind that the document selection process =
will take time, and set your authors' expectations appropriately.

We will arrange for authors who wish to attend and who are selected to =
receive invitations, so that they can justify the early arrival to their =
management if necessary.

Thanks!


From mcr@sandelman.ca  Fri Jan 17 08:21:31 2014
Return-Path: <mcr@sandelman.ca>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4EDE1AE123 for <wgchairs@ietfa.amsl.com>; Fri, 17 Jan 2014 08:21:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.009
X-Spam-Level: *
X-Spam-Status: No, score=1.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, RDNS_NONE=0.793, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MjkMYmhMU2QX for <wgchairs@ietfa.amsl.com>; Fri, 17 Jan 2014 08:21:30 -0800 (PST)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id 7FE5A1AE11E for <wgchairs@ietf.org>; Fri, 17 Jan 2014 08:21:30 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 779B720036; Fri, 17 Jan 2014 12:37:10 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id C7F9764647; Fri, 17 Jan 2014 11:21:17 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id B813A63AAE; Fri, 17 Jan 2014 11:21:17 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: Ted Lemon <ted.lemon@nominum.com>
Subject: Re: Document language editing session in London
In-Reply-To: <D6557C43-1445-4660-804D-BD17ED9DD486@nominum.com>
References: <D6557C43-1445-4660-804D-BD17ED9DD486@nominum.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
Date: Fri, 17 Jan 2014 11:21:17 -0500
Message-ID: <3129.1389975677@sandelman.ca>
Sender: mcr@sandelman.ca
X-Mailman-Approved-At: Fri, 17 Jan 2014 08:23:03 -0800
Cc: "wgchairs@ietf.org Chairs" <wgchairs@ietf.org>, "Heather Flanagan \(RFC Series Editor\)" <rse@rfc-editor.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jan 2014 16:21:32 -0000

Ted Lemon <ted.lemon@nominum.com> wrote:
    > The IESG has decided to repeat the experiment that we tried in Berlin
    > at the upcoming London IETF meeting.   We would like to invite ten
    > document authors to a language editing session in London on the
    > Saturday prior to the IETF meeting.   The goal of this editing session
    > will be for two area directors, me and Joel Jaeggli, to each sit with a
    > group of five document editors and work on each editors' document for
    > 30 minutes in a group setting.   Benoit Claise has also offered to help
    > if there are any French-speaking authors who would like to
    > participate.

So, it's aimed at non-english document editors.
WG chairs should consider where to apply this careful --- laser precision here.

(In my WG, I think that we have most of the non-english first language
speakers have self-selected themselves out of being document editors; we do
have lots of individual submissions, and I think that some of the barrier to
adoption is language.
Mind: we have quite a few french-as-first-language contributors, but one
hardly notices that until you talk to them)

    > What we are asking working group chairs to do is think about whether
    > there are documents in their working group that could use this sort of
    > help.   If you believe there are, please contact the authors of those
    > documents and ask them in a non-pushy way whether they would like to
    > participate in this experiment.   Please let us know if any of your
    > authors are interested in this.   If you have more than one document
    > that you'd like worked on, please tell us which one is most important
    > to you.   We will have to do a triage process unless the response to
    > this call for participants is tiny, so it's likely that we will only
    > take the document you think is more important.   If we get a really
    > good response, we won't be able to take documents from every working
    > group that responds; please don't take this as a criticism if your
    > document isn't chosen.

Thank you for this.
I hope that it will be repeated several times.

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


From mcr@sandelman.ca  Fri Jan 17 08:28:36 2014
Return-Path: <mcr@sandelman.ca>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 156731AE11E for <wgchairs@ietfa.amsl.com>; Fri, 17 Jan 2014 08:28:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.019
X-Spam-Level: *
X-Spam-Status: No, score=1.019 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, RDNS_NONE=0.793, SPF_SOFTFAIL=0.665, T_TVD_MIME_NO_HEADERS=0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zmcfvYaR6_Sb for <wgchairs@ietfa.amsl.com>; Fri, 17 Jan 2014 08:28:34 -0800 (PST)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id 8F37C1AE114 for <wgchairs@ietf.org>; Fri, 17 Jan 2014 08:28:34 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id B47D320036; Fri, 17 Jan 2014 12:44:14 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 0F0DB64647; Fri, 17 Jan 2014 11:28:16 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id ED8D263AAE; Fri, 17 Jan 2014 11:28:16 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Ted Lemon <ted.lemon@nominum.com>
Subject: Re: Document language editing session in London
In-Reply-To: <D6557C43-1445-4660-804D-BD17ED9DD486@nominum.com>
References: <D6557C43-1445-4660-804D-BD17ED9DD486@nominum.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Fri, 17 Jan 2014 11:28:16 -0500
Message-ID: <5096.1389976096@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: "wgchairs@ietf.org Chairs" <wgchairs@ietf.org>, "Heather Flanagan \(RFC Series Editor\)" <rse@rfc-editor.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jan 2014 16:28:36 -0000

--=-=-=


Ted Lemon <ted.lemon@nominum.com> wrote:
    > The IESG has decided to repeat the experiment that we tried in Berlin
    > at the upcoming London IETF meeting.   We would like to invite ten
    > document authors to a language editing session in London on the
    > Saturday prior to the IETF meeting.   The goal of this editing session
    > will be for two area directors, me and Joel Jaeggli, to each sit with a
    > group of five document editors and work on each editors' document for
    > 30 minutes in a group setting.   Benoit Claise has also offered to help
    > if there are any French-speaking authors who would like to
    > participate.

So, it's aimed at non-english document editors.
WG chairs should consider where to apply this careful --- laser precision here.

(In my WG, I think that we have most of the non-english first language
speakers have self-selected themselves out of being document editors; we do
have lots of individual submissions, and I think that some of the barrier to
adoption is language.
Mind: we have quite a few french-as-first-language contributors, but one
hardly notices that until you talk to them)

    > What we are asking working group chairs to do is think about whether
    > there are documents in their working group that could use this sort of
    > help.   If you believe there are, please contact the authors of those
    > documents and ask them in a non-pushy way whether they would like to
    > participate in this experiment.   Please let us know if any of your
    > authors are interested in this.   If you have more than one document
    > that you'd like worked on, please tell us which one is most important
    > to you.   We will have to do a triage process unless the response to
    > this call for participants is tiny, so it's likely that we will only
    > take the document you think is more important.   If we get a really
    > good response, we won't be able to take documents from every working
    > group that responds; please don't take this as a criticism if your
    > document isn't chosen.

Thank you for this.
I hope that it will be repeated several times.

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


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




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

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

iQCVAwUBUtlaGoqHRg3pndX9AQJcTAQAmFvmNHpskZvUfpiOwfaqyR4NIfNtBeNl
gqFzkF/8j+wDOO+a9mzo7occ4GOOrmZFairDClzu387M3tFrQdQcpNcOPcIooM7F
zS2QHSaztyhI3khjE473jZHdWR24R0S4OdZWj5TxwE8t0ncQpn7cBpIQ3fAn1073
EDMSAlp6COM=
=Sm/r
-----END PGP SIGNATURE-----
--=-=-=--

From narten@us.ibm.com  Fri Jan 17 08:49:18 2014
Return-Path: <narten@us.ibm.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC8F11AE152 for <wgchairs@ietfa.amsl.com>; Fri, 17 Jan 2014 08:49:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.439
X-Spam-Level: 
X-Spam-Status: No, score=-7.439 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WbWWQNhebGlR for <wgchairs@ietfa.amsl.com>; Fri, 17 Jan 2014 08:49:17 -0800 (PST)
Received: from e7.ny.us.ibm.com (e7.ny.us.ibm.com [32.97.182.137]) by ietfa.amsl.com (Postfix) with ESMTP id 5CB4F1AE11E for <wgchairs@ietf.org>; Fri, 17 Jan 2014 08:49:17 -0800 (PST)
Received: from /spool/local by e7.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <wgchairs@ietf.org> from <narten@us.ibm.com>; Fri, 17 Jan 2014 11:49:04 -0500
Received: from d01dlp01.pok.ibm.com (9.56.250.166) by e7.ny.us.ibm.com (192.168.1.107) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 17 Jan 2014 11:49:03 -0500
Received: from b01cxnp22036.gho.pok.ibm.com (b01cxnp22036.gho.pok.ibm.com [9.57.198.26]) by d01dlp01.pok.ibm.com (Postfix) with ESMTP id 3DFCC38C8054 for <wgchairs@ietf.org>; Fri, 17 Jan 2014 11:49:03 -0500 (EST)
Received: from d01av05.pok.ibm.com (d01av05.pok.ibm.com [9.56.224.195]) by b01cxnp22036.gho.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id s0HGn3Cd16253076 for <wgchairs@ietf.org>; Fri, 17 Jan 2014 16:49:03 GMT
Received: from d01av05.pok.ibm.com (localhost [127.0.0.1]) by d01av05.pok.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id s0HGn2dx010998 for <wgchairs@ietf.org>; Fri, 17 Jan 2014 11:49:02 -0500
Received: from cichlid.raleigh.ibm.com ([9.57.74.132]) by d01av05.pok.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id s0HGn2lG010967 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 17 Jan 2014 11:49:02 -0500
Received: from cichlid.raleigh.ibm.com.us.ibm.com (localhost [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id s0HGn1OX002032; Fri, 17 Jan 2014 11:49:01 -0500
Date: Fri, 17 Jan 2014 11:49:01 -0500
Message-ID: <m37g9ytuyq.wl%narten@us.ibm.com>
From: Thomas Narten <narten@us.ibm.com>
To: Ted Lemon <ted.lemon@nominum.com>
Subject: Re: [BOFChairs] Document language editing session in London
In-Reply-To: <D6557C43-1445-4660-804D-BD17ED9DD486@nominum.com>
References: <D6557C43-1445-4660-804D-BD17ED9DD486@nominum.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.8 EasyPG/1.0.0 Emacs/23.1 (x86_64-redhat-linux-gnu) MULE/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-TM-AS-MML: disable
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 14011716-5806-0000-0000-000023E520E9
Cc: "wgchairs@ietf.org Chairs" <wgchairs@ietf.org>, "Heather Flanagan \(RFC Series Editor\)" <rse@rfc-editor.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jan 2014 16:49:18 -0000

> The IESG has decided to repeat the experiment that we tried in
> Berlin

Is there a report or summary of the what was learned from that
experiment?

While I have to support the goals of this effort, it surprises me that
ADs are doing the leg work here.

With all due respect, aren't ADs chronically overloaded and short on
cycles to do more important things? I'd be suprised if only ADs can
take on this particular task, and if other volunteers can't be found,
that might say something about how important the community feels this
issue is.

Improving writing skills of non-native english speakers is a generic
problem, hardly  specific to the IETF.

Thomas


From zongning@huawei.com  Fri Jan 17 18:58:56 2014
Return-Path: <zongning@huawei.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBD6D1A1F63 for <wgchairs@ietfa.amsl.com>; Fri, 17 Jan 2014 18:58:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.739
X-Spam-Level: 
X-Spam-Status: No, score=-106.739 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_INVITATION=-2, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pC3OxHOe8b2Q for <wgchairs@ietfa.amsl.com>; Fri, 17 Jan 2014 18:58:55 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id BF8D11ACCEA for <wgchairs@ietf.org>; Fri, 17 Jan 2014 18:58:54 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BCP64013; Sat, 18 Jan 2014 02:58:41 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sat, 18 Jan 2014 02:57:39 +0000
Received: from nkgeml407-hub.china.huawei.com (10.98.56.38) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sat, 18 Jan 2014 02:58:40 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.56]) by nkgeml407-hub.china.huawei.com ([10.98.56.38]) with mapi id 14.03.0158.001; Sat, 18 Jan 2014 10:58:32 +0800
From: Zongning <zongning@huawei.com>
To: Ted Lemon <ted.lemon@nominum.com>, "wgchairs@ietf.org Chairs" <wgchairs@ietf.org>
Subject: RE: Document language editing session in London
Thread-Topic: Document language editing session in London
Thread-Index: AQHPEzDJ4/+IJpAC1EiAoRNPZC9QtZqJyFxg
Date: Sat, 18 Jan 2014 02:58:31 +0000
Message-ID: <B0D29E0424F2DE47A0B36779EC66677925867D07@nkgeml501-mbs.china.huawei.com>
References: <D6557C43-1445-4660-804D-BD17ED9DD486@nominum.com>
In-Reply-To: <D6557C43-1445-4660-804D-BD17ED9DD486@nominum.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.138.41.28]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "Heather Flanagan \(RFC Series Editor\)" <rse@rfc-editor.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Jan 2014 02:58:56 -0000

Dear Ted, and all,

As a non-native English speaker, I agree that this is a good practice to im=
prove the quality of IETF I-Ds.

I also share the opinion of Thomas that more volunteers should be called to=
 help the whole community. Probably the similar practice could be conducted=
 in a more "distributed" way, e.g., in WG level, led by WG co-chairs.

Anyway, I will plan to submit I-D to this session in London, learn somethin=
g important, then talk to my group, especially as a non-native English WG c=
o-chair. :-)

Thanks.

-Ning

> -----Original Message-----
> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of Ted Lemon
> Sent: Friday, January 17, 2014 11:04 AM
> To: wgchairs@ietf.org Chairs
> Cc: Heather Flanagan (RFC Series Editor)
> Subject: Document language editing session in London
>=20
> Dear WG Chairs:
>=20
> The IESG has decided to repeat the experiment that we tried in Berlin at =
the
> upcoming London IETF meeting.   We would like to invite ten document
> authors to a language editing session in London on the Saturday prior to =
the
> IETF meeting.   The goal of this editing session will be for two area dir=
ectors,
> me and Joel Jaeggli, to each sit with a group of five document editors an=
d work
> on each editors' document for 30 minutes in a group setting.   Benoit Cla=
ise
> has also offered to help if there are any French-speaking authors who wou=
ld like
> to participate.
>=20
> The plan for this work is to do two things: first, to review the document=
s, and
> secondly, for the participants to have the opportunity to work with Joel =
or with
> me to improve the quality of their documents.   The goal is specifically =
for
> non-native english speakers who have documents that the working group
> considers important, but which are felt to need help with english languag=
e
> editing.   It is important that the authors _want_ to get help-that they
> recognize that they could use help and that they are comfortable getting =
that
> help in a small group setting.
>=20
> What the meeting will look like is that there will be one or two tables i=
n a
> meeting room; I will be at one table with five authors and a representati=
ve
> from the RFC Editor.   Joel will be at a separate table, with the same
> arrangement.   If there aren't enough authors, we may do a single table, =
as
> we did in Berlin.
>=20
> Each of us will have briefly reviewed the five documents prior to the mee=
ting,
> and we expect that the authors will be familiar with each others' documen=
ts as
> well.   For thirty minutes per document, we will sit with the author and =
go
> over the document, offering comments and suggestions and getting feedback
> from the author.   The other authors will follow this. Then we will move =
on to
> the next author.   Joel will be doing the same thing at the other table. =
  The
> RFC Editor will be observing and offering advice on request, or if they c=
an't
> resist, but the main goal is to take advantage of the technical editorial
> expertise of the two ADs for this experiment.   At the end of the editing
> session, we will have a half hour session where we talk about what went w=
ell, if
> anything, and what went wrong, if anything, and how we might do it better
> next time.
>=20
> Neither Joel nor I are experts on teaching english to non-native speakers=
, so we
> do not claim any specific knowledge other than that we both have a keen
> interest in improving the quality of IETF documents, a fair amount of exp=
erience
> in at least trying to do so, and a desire to help our colleagues to accom=
plish
> their goals.
>=20
> Our desired outcome from this meeting is twofold: first, to help the spec=
ific
> authors who attend; secondly, to learn how to help authors in general: wh=
at
> frustrations they have in writing documents for IETF, what stumbling bloc=
ks
> they trip over, and how we can help them.
>=20
> What we are asking working group chairs to do is think about whether ther=
e
> are documents in their working group that could use this sort of help.   =
If you
> believe there are, please contact the authors of those documents and ask =
them
> in a non-pushy way whether they would like to participate in this experim=
ent.
> Please let us know if any of your authors are interested in this.   If yo=
u have
> more than one document that you'd like worked on, please tell us which on=
e is
> most important to you.   We will have to do a triage process unless the
> response to this call for participants is tiny, so it's likely that we wi=
ll only take
> the document you think is more important.   If we get a really good respo=
nse,
> we won't be able to take documents from every working group that responds=
;
> please don't take this as a criticism if your document isn't chosen.
>=20
> If you think this is a good idea and want to take advantage of it, please=
 contact
> your authors as soon as possible, so that they can make travel plans that=
 allow
> them to get to the venue on Saturday rather than on Sunday.   Please bear=
 in
> mind that the document selection process will take time, and set your aut=
hors'
> expectations appropriately.
>=20
> We will arrange for authors who wish to attend and who are selected to re=
ceive
> invitations, so that they can justify the early arrival to their manageme=
nt if
> necessary.
>=20
> Thanks!


From bill@wjcerveny.com  Sun Jan 19 15:38:09 2014
Return-Path: <bill@wjcerveny.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD9451A0003 for <wgchairs@ietfa.amsl.com>; Sun, 19 Jan 2014 15:38:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, GB_I_INVITATION=-2, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vcTRFxMKZhT7 for <wgchairs@ietfa.amsl.com>; Sun, 19 Jan 2014 15:38:06 -0800 (PST)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id 659271A0002 for <wgchairs@ietf.org>; Sun, 19 Jan 2014 15:38:06 -0800 (PST)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 7632D20617 for <wgchairs@ietf.org>; Sun, 19 Jan 2014 18:38:05 -0500 (EST)
Received: from frontend1 ([10.202.2.160]) by compute3.internal (MEProxy); Sun, 19 Jan 2014 18:38:05 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id :references:to; s=smtpout; bh=2R1HWqiXeyYoPAz0oCNhbE3bIx8=; b=bT 7pP0DeJERCJH8yC3sUME9fVtlzWeeFYaz7n0WVfe9moeWwBArEVh1GXQcspaIhBy KkxdTM1IvyGTuN9NIZgfauVoxuafGQDrfF1d/aZOepZlL3GGg1+Ed8GvXtNJuVBG rtgGOq6X8h91csCMGrIkCBRpZB9HN7MeY7SPzTBd0=
X-Sasl-enc: 1GoP5o95slhQ5eC8/B7037xLHvGAmQbnADPxG7Xgh8Ky 1390174685
Received: from [192.168.1.110] (unknown [24.231.177.41]) by mail.messagingengine.com (Postfix) with ESMTPA id 9CE8CC00E87; Sun, 19 Jan 2014 18:38:04 -0500 (EST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Document language editing session in London
From: Bill Cerveny <bill@wjcerveny.com>
In-Reply-To: <B0D29E0424F2DE47A0B36779EC66677925867D07@nkgeml501-mbs.china.huawei.com>
Date: Sun, 19 Jan 2014 18:38:03 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <9ADCA470-8200-4C9E-A728-FD69D155A569@wjcerveny.com>
References: <D6557C43-1445-4660-804D-BD17ED9DD486@nominum.com> <B0D29E0424F2DE47A0B36779EC66677925867D07@nkgeml501-mbs.china.huawei.com>
To: Zongning <zongning@huawei.com>
X-Mailer: Apple Mail (2.1827)
Cc: "wgchairs@ietf.org Chairs" <wgchairs@ietf.org>, "Heather Flanagan \(RFC Series Editor\)" <rse@rfc-editor.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 19 Jan 2014 23:38:09 -0000

[My first rant as a WG chair. I first wrote the rant, then took out =
maybe 2/3rds of what I wrote :-) ]

Having documents cleaned up grammatically as early as possible is very =
important and will result in better technical discussions, better =
(final) documents and a faster document turnaround from submission to =
publication.

Last year my daughter, a recent college graduate in English, told me she =
aspired to be a technical writer, at which time I told her, =93Gee, =
how=92d you like to get experience reviewing technical documents?=94 I =
recruited her to review WG documents primarily from a grammatical, =
non-technical perspective. She was successful at providing constructive =
grammatical feedback to WG draft authors.

Having worked with my daughter in in helping her get up to speed in =
reviewing IETF documents, it seems there are challenges a volunteer =
reviewer faces:
1) There doesn=92t appear to be a clear, concise web page new volunteer =
reviewers can use as a starting point.
2) How does one determine which documents are fair game for document =
review?  In theory, any document submitted to the IETF should be open =
for grammatical review the moment it is submitted, but given limited =
resources, from a WG perspective, we encourage reviewing WG documents =
first.
3) How should a reviewer submit proposed changes? There isn=92t a =
consistent IETF recommendation for how to submit review comments/changes =
(such as format and/or tools) and it seems a consistent recommendation =
would be useful.
4) There isn=92t any mechanism for encouraging (or even rewarding) =
reviewers who may not be intimately interested in the technical aspects =
of the documents. I sent my daughter an IETF88 T-shirt, but other than a =
thanks from the authors and/or the WG chairs, there isn=92t much that is =
done to encourage or reward the reviewers.

At the risk of sounding non-IETFish here (we=92re mostly all =
=93volunteers=94), in a perfect world, it would make sense for authors =
to pay a document reviewer to review a document before it is even =
submitted to the IETF. The time involved with reviewing documents for =
grammatical correctness can be non-trivial. Certainly, there is an =
implied financial cost for the time that a volunteer reviewer spends to =
review a document. If the author is serious about submitting a concise =
technical document and having a concise technical document published, it =
would behoove the author to ensure that the document is grammatically =
correct before it is submitted to engineers for technical scrutiny. In =
this perfect world, there might be some sort of central list of people =
willing to review documents, although at a larger organization, it =
should be possible for the author to ask someone at the organization to =
review the document.

Bill Cerveny

On Jan 17, 2014, at 9:58 PM, Zongning <zongning@huawei.com> wrote:

> Dear Ted, and all,
>=20
> As a non-native English speaker, I agree that this is a good practice =
to improve the quality of IETF I-Ds.
>=20
> I also share the opinion of Thomas that more volunteers should be =
called to help the whole community. Probably the similar practice could =
be conducted in a more "distributed" way, e.g., in WG level, led by WG =
co-chairs.
>=20
> Anyway, I will plan to submit I-D to this session in London, learn =
something important, then talk to my group, especially as a non-native =
English WG co-chair. :-)
>=20
> Thanks.
>=20
> -Ning
>=20
>> -----Original Message-----
>> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of Ted =
Lemon
>> Sent: Friday, January 17, 2014 11:04 AM
>> To: wgchairs@ietf.org Chairs
>> Cc: Heather Flanagan (RFC Series Editor)
>> Subject: Document language editing session in London
>>=20
>> Dear WG Chairs:
>>=20
>> The IESG has decided to repeat the experiment that we tried in Berlin =
at the
>> upcoming London IETF meeting.   We would like to invite ten document
>> authors to a language editing session in London on the Saturday prior =
to the
>> IETF meeting.   The goal of this editing session will be for two area =
directors,
>> me and Joel Jaeggli, to each sit with a group of five document =
editors and work
>> on each editors' document for 30 minutes in a group setting.   Benoit =
Claise
>> has also offered to help if there are any French-speaking authors who =
would like
>> to participate.
>>=20
>> The plan for this work is to do two things: first, to review the =
documents, and
>> secondly, for the participants to have the opportunity to work with =
Joel or with
>> me to improve the quality of their documents.   The goal is =
specifically for
>> non-native english speakers who have documents that the working group
>> considers important, but which are felt to need help with english =
language
>> editing.   It is important that the authors _want_ to get help-that =
they
>> recognize that they could use help and that they are comfortable =
getting that
>> help in a small group setting.
>>=20
>> What the meeting will look like is that there will be one or two =
tables in a
>> meeting room; I will be at one table with five authors and a =
representative
>> from the RFC Editor.   Joel will be at a separate table, with the =
same
>> arrangement.   If there aren't enough authors, we may do a single =
table, as
>> we did in Berlin.
>>=20
>> Each of us will have briefly reviewed the five documents prior to the =
meeting,
>> and we expect that the authors will be familiar with each others' =
documents as
>> well.   For thirty minutes per document, we will sit with the author =
and go
>> over the document, offering comments and suggestions and getting =
feedback
>> from the author.   The other authors will follow this. Then we will =
move on to
>> the next author.   Joel will be doing the same thing at the other =
table.   The
>> RFC Editor will be observing and offering advice on request, or if =
they can't
>> resist, but the main goal is to take advantage of the technical =
editorial
>> expertise of the two ADs for this experiment.   At the end of the =
editing
>> session, we will have a half hour session where we talk about what =
went well, if
>> anything, and what went wrong, if anything, and how we might do it =
better
>> next time.
>>=20
>> Neither Joel nor I are experts on teaching english to non-native =
speakers, so we
>> do not claim any specific knowledge other than that we both have a =
keen
>> interest in improving the quality of IETF documents, a fair amount of =
experience
>> in at least trying to do so, and a desire to help our colleagues to =
accomplish
>> their goals.
>>=20
>> Our desired outcome from this meeting is twofold: first, to help the =
specific
>> authors who attend; secondly, to learn how to help authors in =
general: what
>> frustrations they have in writing documents for IETF, what stumbling =
blocks
>> they trip over, and how we can help them.
>>=20
>> What we are asking working group chairs to do is think about whether =
there
>> are documents in their working group that could use this sort of =
help.   If you
>> believe there are, please contact the authors of those documents and =
ask them
>> in a non-pushy way whether they would like to participate in this =
experiment.
>> Please let us know if any of your authors are interested in this.   =
If you have
>> more than one document that you'd like worked on, please tell us =
which one is
>> most important to you.   We will have to do a triage process unless =
the
>> response to this call for participants is tiny, so it's likely that =
we will only take
>> the document you think is more important.   If we get a really good =
response,
>> we won't be able to take documents from every working group that =
responds;
>> please don't take this as a criticism if your document isn't chosen.
>>=20
>> If you think this is a good idea and want to take advantage of it, =
please contact
>> your authors as soon as possible, so that they can make travel plans =
that allow
>> them to get to the venue on Saturday rather than on Sunday.   Please =
bear in
>> mind that the document selection process will take time, and set your =
authors'
>> expectations appropriately.
>>=20
>> We will arrange for authors who wish to attend and who are selected =
to receive
>> invitations, so that they can justify the early arrival to their =
management if
>> necessary.
>>=20
>> Thanks!
>=20


From mcr@sandelman.ca  Sun Jan 19 15:53:54 2014
Return-Path: <mcr@sandelman.ca>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47C8F1A0005 for <wgchairs@ietfa.amsl.com>; Sun, 19 Jan 2014 15:53:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.697
X-Spam-Level: ***
X-Spam-Status: No, score=3.697 tagged_above=-999 required=5 tests=[FH_RELAY_NODNS=1.451, RDNS_NONE=1.274, SPF_SOFTFAIL=0.972] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qDTYeFt8lsf8 for <wgchairs@ietfa.amsl.com>; Sun, 19 Jan 2014 15:53:52 -0800 (PST)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id CF7951A0004 for <wgchairs@ietf.org>; Sun, 19 Jan 2014 15:53:52 -0800 (PST)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id 4AB202003D for <wgchairs@ietf.org>; Sun, 19 Jan 2014 20:09:52 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 896D664647; Sun, 19 Jan 2014 18:53:51 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 709FA63B88 for <wgchairs@ietf.org>; Sun, 19 Jan 2014 18:53:51 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "wgchairs\@ietf.org Chairs" <wgchairs@ietf.org>
Subject: Re: Document language editing session in London
In-Reply-To: <9ADCA470-8200-4C9E-A728-FD69D155A569@wjcerveny.com>
References: <D6557C43-1445-4660-804D-BD17ED9DD486@nominum.com> <B0D29E0424F2DE47A0B36779EC66677925867D07@nkgeml501-mbs.china.huawei.com> <9ADCA470-8200-4C9E-A728-FD69D155A569@wjcerveny.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Sun, 19 Jan 2014 18:53:51 -0500
Message-ID: <13255.1390175631@sandelman.ca>
Sender: mcr@sandelman.ca
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 19 Jan 2014 23:53:54 -0000

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


Bill Cerveny <bill@wjcerveny.com> wrote:
    > 2) How does one determine which documents are fair game for document
    > review?  In theory, any document submitted to the IETF should be open
    > for grammatical review the moment it is submitted, but given limited
    > resources, from a WG perspective, we encourage reviewing WG documents
    > first.

I think that this is partially just a matter of some interesting views (whi=
ch
might already exist) on the datatracker... I think that the better question
is, how early is it worth while?   My opinion is that the first review is
somewhere around WG adoption stage, and I'd like to say *before*, but I thi=
nk
that this costs too much.

    > 4) There isn=E2=80=99t any mechanism for encouraging (or even rewardi=
ng)
    > reviewers who may not be intimately interested in the technical aspec=
ts
    > of the documents. I sent my daughter an IETF88 T-shirt, but other than
    > a thanks from the authors and/or the WG chairs, there isn=E2=80=99t m=
uch that
    > is done to encourage or reward the reviewers.

I just want to leave this part here.
We have some significant incentive issues to work out.

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




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

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

iQCVAwUBUtxljYqHRg3pndX9AQI6owQA6P/PPpL2PshxF/xBtogYOb/H5XwFHaic
z3mHZ0kHi+qYOKOWlCyGuFV4kxJxXAORsT89qioKmRlDtCETi461bQURwWVDK61a
ZJY1zba6+XkxCYLHZFUENh0eP8oLjIJXFi4aQkIId1WtdDFy4fQkwPzC3BltQI0f
x7dg6h/88PI=
=KflT
-----END PGP SIGNATURE-----
--=-=-=--

From Ted.Lemon@nominum.com  Sun Jan 19 16:05:10 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36C4C1A000B for <wgchairs@ietfa.amsl.com>; Sun, 19 Jan 2014 16:05:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2kUpG90oOTpv for <wgchairs@ietfa.amsl.com>; Sun, 19 Jan 2014 16:05:09 -0800 (PST)
Received: from exprod7og124.obsmtp.com (exprod7og124.obsmtp.com [64.18.2.26]) by ietfa.amsl.com (Postfix) with ESMTP id F055C1A000A for <wgchairs@ietf.org>; Sun, 19 Jan 2014 16:05:08 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob124.postini.com ([64.18.6.12]) with SMTP ID DSNKUtxoNIckqqswbTgOFupM24i8PDGdZcV3@postini.com; Sun, 19 Jan 2014 16:05:09 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 6F1241B8229 for <wgchairs@ietf.org>; Sun, 19 Jan 2014 16:05:08 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 4A8B519005C; Sun, 19 Jan 2014 16:05:08 -0800 (PST)
Received: from [10.0.1.12] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sun, 19 Jan 2014 16:05:07 -0800
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Document language editing session in London
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <9ADCA470-8200-4C9E-A728-FD69D155A569@wjcerveny.com>
Date: Sun, 19 Jan 2014 19:05:07 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <A7401A7C-2514-44A9-BDA9-CD01C7CA047B@nominum.com>
References: <D6557C43-1445-4660-804D-BD17ED9DD486@nominum.com> <B0D29E0424F2DE47A0B36779EC66677925867D07@nkgeml501-mbs.china.huawei.com> <9ADCA470-8200-4C9E-A728-FD69D155A569@wjcerveny.com>
To: Bill Cerveny <bill@wjcerveny.com>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Cc: "wgchairs@ietf.org Chairs" <wgchairs@ietf.org>, "Heather Flanagan \(RFC Series Editor\)" <rse@rfc-editor.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2014 00:05:10 -0000

Just to clarify, the point of the language editing session is not to =
help non-native speakers to express themselves better in english through =
the process of reviewing and editing their documents, not to correct =
trivial grammatical errors.   The point of having a technical reviewer =
do this work is that we are more likely to understand what is intended, =
and therefore be able to suggest better ways of expressing it.

You are absolutely right that the other sort of work is also useful, and =
might well be able to be accomplished by reviewers who are interested in =
honing their tech writing chops.   It is worth noting that the RFC =
Editor function at the IETF is staffed by people who are in fact already =
quite good at that.   But as you say, doing the editing earlier in the =
process is definitely helpful, and the RFC editor can't help very much =
with that.

To answer Michael's question, it is helpful to do these edits early in =
the process because it can make the document easier to review.   To =
answer your question, it is _always_ in scope to review an internet =
draft.   However, it's up to the authors to read your review and update =
the draft, and there is no guarantee that they will do so, so it can't =
hurt to ask.

Any document that's in a call for adoption or working group last call =
would be a good document to do this work on.   Also, any document that =
covers a topic you find interesting.   There's never a guarantee that =
your work will be useful when you review a document, because documents =
don't always survive working group last call or IETF last call.   So you =
have to be willing to risk a little to contribute to the process of =
improving documents.


From bill@wjcerveny.com  Sun Jan 19 17:00:25 2014
Return-Path: <bill@wjcerveny.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CD311A0010 for <wgchairs@ietfa.amsl.com>; Sun, 19 Jan 2014 17:00:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.7
X-Spam-Level: 
X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 222kPW6h5rNC for <wgchairs@ietfa.amsl.com>; Sun, 19 Jan 2014 17:00:23 -0800 (PST)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id 3FF441A0016 for <wgchairs@ietf.org>; Sun, 19 Jan 2014 17:00:22 -0800 (PST)
Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 72BEB208CD; Sun, 19 Jan 2014 20:00:22 -0500 (EST)
Received: from frontend2 ([10.202.2.161]) by compute2.internal (MEProxy); Sun, 19 Jan 2014 20:00:22 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id :references:to; s=smtpout; bh=nm225Azo7G9MiSl7RMnEUPUDbfI=; b=EU UELQdKW+4L46VR0wnjnqDr3met4NK8DhV2OWoz5rXWbc1OIhB+6ap2XfA7lICTwG wqbVtCvsiDKMW/6r49eYL/dUDfsgUHRFt7kaMEcUW43ofLMHQfThxxzKSlpWE0J5 sQhVBA69pf4KbXP5roCD1eIU/lEwW8vW5icpH/BYU=
X-Sasl-enc: XxNwXmCryBD74rPAvbaOCGpU7gAbXPosOVpLkF2QMp9y 1390179622
Received: from [192.168.1.110] (unknown [24.231.177.41]) by mail.messagingengine.com (Postfix) with ESMTPA id A2381680256; Sun, 19 Jan 2014 20:00:21 -0500 (EST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Document language editing session in London
From: Bill Cerveny <bill@wjcerveny.com>
In-Reply-To: <A7401A7C-2514-44A9-BDA9-CD01C7CA047B@nominum.com>
Date: Sun, 19 Jan 2014 20:00:19 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <F28E9CD4-6D7F-4465-993D-8FBFCD231A21@wjcerveny.com>
References: <D6557C43-1445-4660-804D-BD17ED9DD486@nominum.com> <B0D29E0424F2DE47A0B36779EC66677925867D07@nkgeml501-mbs.china.huawei.com> <9ADCA470-8200-4C9E-A728-FD69D155A569@wjcerveny.com> <A7401A7C-2514-44A9-BDA9-CD01C7CA047B@nominum.com>
To: Ted Lemon <ted.lemon@nominum.com>
X-Mailer: Apple Mail (2.1827)
Cc: "wgchairs@ietf.org Chairs" <wgchairs@ietf.org>, "Heather Flanagan \(RFC Series Editor\)" <rse@rfc-editor.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2014 01:00:25 -0000

Ted,

Thanks for the clarifications.There was a sentence in your initial =
e-mail about ADs offering "technical editoral expertise".  I'm curious =
myself; it would seem any technical author would find this advice =
useful, as ADs must see/review an insane number of documents. It would =
be interesting to have ADs (or even previous ADs) offer their technical =
perspective on what they look for in documents and what common problems =
that they see in documents they review.

Thanks,

Bill

On Jan 19, 2014, at 7:05 PM, Ted Lemon <ted.lemon@nominum.com> wrote:

> Just to clarify, the point of the language editing session is not to =
help non-native speakers to express themselves better in english through =
the process of reviewing and editing their documents, not to correct =
trivial grammatical errors.   The point of having a technical reviewer =
do this work is that we are more likely to understand what is intended, =
and therefore be able to suggest better ways of expressing it.

>=20
> You are absolutely right that the other sort of work is also useful, =
and might well be able to be accomplished by reviewers who are =
interested in honing their tech writing chops.   It is worth noting that =
the RFC Editor function at the IETF is staffed by people who are in fact =
already quite good at that.   But as you say, doing the editing earlier =
in the process is definitely helpful, and the RFC editor can't help very =
much with that.
>=20
> To answer Michael's question, it is helpful to do these edits early in =
the process because it can make the document easier to review.   To =
answer your question, it is _always_ in scope to review an internet =
draft.   However, it's up to the authors to read your review and update =
the draft, and there is no guarantee that they will do so, so it can't =
hurt to ask.
>=20
> Any document that's in a call for adoption or working group last call =
would be a good document to do this work on.   Also, any document that =
covers a topic you find interesting.   There's never a guarantee that =
your work will be useful when you review a document, because documents =
don't always survive working group last call or IETF last call.   So you =
have to be willing to risk a little to contribute to the process of =
improving documents.
>=20



From prvs=609711ff24=sandra.murphy@parsons.com  Mon Jan 20 07:20:36 2014
Return-Path: <prvs=609711ff24=sandra.murphy@parsons.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F4321A01AF for <wgchairs@ietfa.amsl.com>; Mon, 20 Jan 2014 07:20:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.436
X-Spam-Level: 
X-Spam-Status: No, score=-2.436 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zZ6KgiBkNnJ8 for <wgchairs@ietfa.amsl.com>; Mon, 20 Jan 2014 07:20:35 -0800 (PST)
Received: from txdal11mx03.parsons.com (txdal11mx03.parsons.com [206.219.199.111]) by ietfa.amsl.com (Postfix) with ESMTP id 1BBE51A019F for <wgchairs@ietf.org>; Mon, 20 Jan 2014 07:20:35 -0800 (PST)
Received: from pps.filterd (txdal11mx03 [127.0.0.1]) by txdal11mx03.parsons.com (8.14.5/8.14.5) with SMTP id s0KFJwZE011581; Mon, 20 Jan 2014 09:20:25 -0600
Received: from m4.sparta.com (m4.sparta.com [157.185.61.2]) by txdal11mx03.parsons.com with ESMTP id 1hh5f186xv-1 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Mon, 20 Jan 2014 09:20:25 -0600
Received: from Beta5.sparta.com ([10.62.8.21]) by M4.sparta.com (8.14.4/8.14.4) with ESMTP id s0KFKOKb018509; Mon, 20 Jan 2014 09:20:24 -0600
Received: from tanis.huntsville.ads.sparta.com ([10.62.8.118]) by Beta5.sparta.com (8.13.8/8.13.8) with ESMTP id s0KFKNYJ005095; Mon, 20 Jan 2014 09:20:23 -0600
Received: from HSV-MB002.huntsville.ads.sparta.com ([fe80::2521:a783:a30c:d057]) by tanis.huntsville.ads.sparta.com ([::1]) with mapi id 14.02.0342.003; Mon, 20 Jan 2014 09:20:23 -0600
From: "Murphy, Sandra" <Sandra.Murphy@parsons.com>
To: Ted Lemon <ted.lemon@nominum.com>, Bill Cerveny <bill@wjcerveny.com>
Subject: RE: Document language editing session in London
Thread-Topic: Document language editing session in London
Thread-Index: AQHPEzDoSHJmoxVby0SYn2E1UxTaXpqKMImAgALsqICAAAePgIAAmmzj
Date: Mon, 20 Jan 2014 15:20:22 +0000
Message-ID: <24B20D14B2CD29478C8D5D6E9CBB29F678F1F89D@HSV-MB002.huntsville.ads.sparta.com>
References: <D6557C43-1445-4660-804D-BD17ED9DD486@nominum.com> <B0D29E0424F2DE47A0B36779EC66677925867D07@nkgeml501-mbs.china.huawei.com> <9ADCA470-8200-4C9E-A728-FD69D155A569@wjcerveny.com>, <A7401A7C-2514-44A9-BDA9-CD01C7CA047B@nominum.com>
In-Reply-To: <A7401A7C-2514-44A9-BDA9-CD01C7CA047B@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.185.61.33]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.11.87, 1.0.14, 0.0.0000 definitions=2014-01-20_01:2014-01-20,2014-01-20,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 kscore.is_bulkscore=0 kscore.compositescore=0 circleOfTrustscore=0 compositescore=0.0395041412045292 urlsuspect_oldscore=0.0395041412045292 suspectscore=0 recipient_domain_to_sender_totalscore=1469 phishscore=0 bulkscore=0 kscore.is_spamscore=0 recipient_to_sender_totalscore=0 recipient_domain_to_sender_domain_totalscore=7945 rbsscore=0.0395041412045292 spamscore=0 recipient_to_sender_domain_totalscore=0 urlsuspectscore=0.3 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1305240000 definitions=main-1401200083
Cc: "wgchairs@ietf.org Chairs" <wgchairs@ietf.org>, "Heather Flanagan \(RFC Series Editor\)" <rse@rfc-editor.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2014 15:20:36 -0000

Speaking of editing:=0A=
=0A=
>Just to clarify, the point of the language editing session is not to help =
non-native speakers to express themselves >better in english through the pr=
ocess of reviewing and editing their documents, not to correct trivial gram=
matical >errors.=0A=
=0A=
This is unclear.  I'm guessing that one of those "not"s is not supposed to =
be "not".  :-)=0A=
=0A=
--Sandy=0A=
=0A=
________________________________________=0A=
From: WGChairs [wgchairs-bounces@ietf.org] on behalf of Ted Lemon [ted.lemo=
n@nominum.com]=0A=
Sent: Sunday, January 19, 2014 7:05 PM=0A=
To: Bill Cerveny=0A=
Cc: wgchairs@ietf.org Chairs; Heather Flanagan (RFC Series Editor)=0A=
Subject: Re: Document language editing session in London=0A=
=0A=
Just to clarify, the point of the language editing session is not to help n=
on-native speakers to express themselves better in english through the proc=
ess of reviewing and editing their documents, not to correct trivial gramma=
tical errors.   The point of having a technical reviewer do this work is th=
at we are more likely to understand what is intended, and therefore be able=
 to suggest better ways of expressing it.=0A=
=0A=
You are absolutely right that the other sort of work is also useful, and mi=
ght well be able to be accomplished by reviewers who are interested in honi=
ng their tech writing chops.   It is worth noting that the RFC Editor funct=
ion at the IETF is staffed by people who are in fact already quite good at =
that.   But as you say, doing the editing earlier in the process is definit=
ely helpful, and the RFC editor can't help very much with that.=0A=
=0A=
To answer Michael's question, it is helpful to do these edits early in the =
process because it can make the document easier to review.   To answer your=
 question, it is _always_ in scope to review an internet draft.   However, =
it's up to the authors to read your review and update the draft, and there =
is no guarantee that they will do so, so it can't hurt to ask.=0A=
=0A=
Any document that's in a call for adoption or working group last call would=
 be a good document to do this work on.   Also, any document that covers a =
topic you find interesting.   There's never a guarantee that your work will=
 be useful when you review a document, because documents don't always survi=
ve working group last call or IETF last call.   So you have to be willing t=
o risk a little to contribute to the process of improving documents.=0A=
=0A=

From pkyzivat@alum.mit.edu  Mon Jan 20 07:26:22 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB3661A01B4 for <wgchairs@ietfa.amsl.com>; Mon, 20 Jan 2014 07:26:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.235
X-Spam-Level: 
X-Spam-Status: No, score=-3.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, GB_I_INVITATION=-2, SPF_SOFTFAIL=0.665] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7y7U67JfrMgz for <wgchairs@ietfa.amsl.com>; Mon, 20 Jan 2014 07:26:20 -0800 (PST)
Received: from qmta14.westchester.pa.mail.comcast.net (qmta14.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:212]) by ietfa.amsl.com (Postfix) with ESMTP id B431C1A01B5 for <wgchairs@ietf.org>; Mon, 20 Jan 2014 07:26:19 -0800 (PST)
Received: from omta09.westchester.pa.mail.comcast.net ([76.96.62.20]) by qmta14.westchester.pa.mail.comcast.net with comcast id GFHE1n0030SCNGk5EFSK55; Mon, 20 Jan 2014 15:26:19 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta09.westchester.pa.mail.comcast.net with comcast id GFSK1n00i3ZTu2S3VFSKje; Mon, 20 Jan 2014 15:26:19 +0000
Message-ID: <52DD401B.7000106@alum.mit.edu>
Date: Mon, 20 Jan 2014 10:26:19 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: Document language editing session in London
References: <D6557C43-1445-4660-804D-BD17ED9DD486@nominum.com> <B0D29E0424F2DE47A0B36779EC66677925867D07@nkgeml501-mbs.china.huawei.com> <9ADCA470-8200-4C9E-A728-FD69D155A569@wjcerveny.com>
In-Reply-To: <9ADCA470-8200-4C9E-A728-FD69D155A569@wjcerveny.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1390231579; bh=siCmHYAC9nLnuc5SKpSXhXjpdElpHV3l6xLnQQPv80c=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=UJVMvWgFaJbUc7LMuGbRY38I4IaaJzUZi+pPZcMekM41wJNQ/z8EZhxm60tOtpBkv zLP26p8vWNoWHJqBw4xCOAwGnd0eWLeJJVjQHbxveMYjxzvKoPnr8Cnf9+U9CYWPm7 BpRgjmRTmpfLA6llk3h+N/69ghBbDupJ8LLLpseHwlOgLUTqmLFebWkDpsTIFjSVer 0bXJ0E0cGroRfsB51Ad+QrSilKwvghTZkwi5/gHYR/tD/guHOGoDZ/D5qQz01PoJzv atRdYdcHEFlmxdBAlqkmH53nQj1m7L+/mSzRQDKE1JpBa2LSIZ8IrS4r+vAsyjwuiv 4Jlk/VglIZcGg==
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2014 15:26:22 -0000

I have a very different view of this from Bill.

IMO, especially early in the process, what is important is to discuss 
the *concepts* in a draft, not the language usage. This is true whether 
the author is just a grammatically inept native English speaker/writer, 
or if the author doesn't have English as his native language.

I find that documents written by many non-native English writers have 
usage that is "unusual" for natives, but in general it is still 
perfectly understandable. I find it easier to just "let it be" until the 
document is quite mature and the discussion of basics is over and it is 
time for polishing.

Discussing language style and grammar in the midst of technical 
discussions is very distracting.

	Thanks,
	Paul

On 1/19/14 6:38 PM, Bill Cerveny wrote:
> [My first rant as a WG chair. I first wrote the rant, then took out maybe 2/3rds of what I wrote :-) ]
>
> Having documents cleaned up grammatically as early as possible is very important and will result in better technical discussions, better (final) documents and a faster document turnaround from submission to publication.
>
> Last year my daughter, a recent college graduate in English, told me she aspired to be a technical writer, at which time I told her, “Gee, how’d you like to get experience reviewing technical documents?” I recruited her to review WG documents primarily from a grammatical, non-technical perspective. She was successful at providing constructive grammatical feedback to WG draft authors.
>
> Having worked with my daughter in in helping her get up to speed in reviewing IETF documents, it seems there are challenges a volunteer reviewer faces:
> 1) There doesn’t appear to be a clear, concise web page new volunteer reviewers can use as a starting point.
> 2) How does one determine which documents are fair game for document review?  In theory, any document submitted to the IETF should be open for grammatical review the moment it is submitted, but given limited resources, from a WG perspective, we encourage reviewing WG documents first.
> 3) How should a reviewer submit proposed changes? There isn’t a consistent IETF recommendation for how to submit review comments/changes (such as format and/or tools) and it seems a consistent recommendation would be useful.
> 4) There isn’t any mechanism for encouraging (or even rewarding) reviewers who may not be intimately interested in the technical aspects of the documents. I sent my daughter an IETF88 T-shirt, but other than a thanks from the authors and/or the WG chairs, there isn’t much that is done to encourage or reward the reviewers.
>
> At the risk of sounding non-IETFish here (we’re mostly all “volunteers”), in a perfect world, it would make sense for authors to pay a document reviewer to review a document before it is even submitted to the IETF. The time involved with reviewing documents for grammatical correctness can be non-trivial. Certainly, there is an implied financial cost for the time that a volunteer reviewer spends to review a document. If the author is serious about submitting a concise technical document and having a concise technical document published, it would behoove the author to ensure that the document is grammatically correct before it is submitted to engineers for technical scrutiny. In this perfect world, there might be some sort of central list of people willing to review documents, although at a larger organization, it should be possible for the author to ask someone at the organization to review the document.
>
> Bill Cerveny
>
> On Jan 17, 2014, at 9:58 PM, Zongning <zongning@huawei.com> wrote:
>
>> Dear Ted, and all,
>>
>> As a non-native English speaker, I agree that this is a good practice to improve the quality of IETF I-Ds.
>>
>> I also share the opinion of Thomas that more volunteers should be called to help the whole community. Probably the similar practice could be conducted in a more "distributed" way, e.g., in WG level, led by WG co-chairs.
>>
>> Anyway, I will plan to submit I-D to this session in London, learn something important, then talk to my group, especially as a non-native English WG co-chair. :-)
>>
>> Thanks.
>>
>> -Ning
>>
>>> -----Original Message-----
>>> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of Ted Lemon
>>> Sent: Friday, January 17, 2014 11:04 AM
>>> To: wgchairs@ietf.org Chairs
>>> Cc: Heather Flanagan (RFC Series Editor)
>>> Subject: Document language editing session in London
>>>
>>> Dear WG Chairs:
>>>
>>> The IESG has decided to repeat the experiment that we tried in Berlin at the
>>> upcoming London IETF meeting.   We would like to invite ten document
>>> authors to a language editing session in London on the Saturday prior to the
>>> IETF meeting.   The goal of this editing session will be for two area directors,
>>> me and Joel Jaeggli, to each sit with a group of five document editors and work
>>> on each editors' document for 30 minutes in a group setting.   Benoit Claise
>>> has also offered to help if there are any French-speaking authors who would like
>>> to participate.
>>>
>>> The plan for this work is to do two things: first, to review the documents, and
>>> secondly, for the participants to have the opportunity to work with Joel or with
>>> me to improve the quality of their documents.   The goal is specifically for
>>> non-native english speakers who have documents that the working group
>>> considers important, but which are felt to need help with english language
>>> editing.   It is important that the authors _want_ to get help-that they
>>> recognize that they could use help and that they are comfortable getting that
>>> help in a small group setting.
>>>
>>> What the meeting will look like is that there will be one or two tables in a
>>> meeting room; I will be at one table with five authors and a representative
>>> from the RFC Editor.   Joel will be at a separate table, with the same
>>> arrangement.   If there aren't enough authors, we may do a single table, as
>>> we did in Berlin.
>>>
>>> Each of us will have briefly reviewed the five documents prior to the meeting,
>>> and we expect that the authors will be familiar with each others' documents as
>>> well.   For thirty minutes per document, we will sit with the author and go
>>> over the document, offering comments and suggestions and getting feedback
>>> from the author.   The other authors will follow this. Then we will move on to
>>> the next author.   Joel will be doing the same thing at the other table.   The
>>> RFC Editor will be observing and offering advice on request, or if they can't
>>> resist, but the main goal is to take advantage of the technical editorial
>>> expertise of the two ADs for this experiment.   At the end of the editing
>>> session, we will have a half hour session where we talk about what went well, if
>>> anything, and what went wrong, if anything, and how we might do it better
>>> next time.
>>>
>>> Neither Joel nor I are experts on teaching english to non-native speakers, so we
>>> do not claim any specific knowledge other than that we both have a keen
>>> interest in improving the quality of IETF documents, a fair amount of experience
>>> in at least trying to do so, and a desire to help our colleagues to accomplish
>>> their goals.
>>>
>>> Our desired outcome from this meeting is twofold: first, to help the specific
>>> authors who attend; secondly, to learn how to help authors in general: what
>>> frustrations they have in writing documents for IETF, what stumbling blocks
>>> they trip over, and how we can help them.
>>>
>>> What we are asking working group chairs to do is think about whether there
>>> are documents in their working group that could use this sort of help.   If you
>>> believe there are, please contact the authors of those documents and ask them
>>> in a non-pushy way whether they would like to participate in this experiment.
>>> Please let us know if any of your authors are interested in this.   If you have
>>> more than one document that you'd like worked on, please tell us which one is
>>> most important to you.   We will have to do a triage process unless the
>>> response to this call for participants is tiny, so it's likely that we will only take
>>> the document you think is more important.   If we get a really good response,
>>> we won't be able to take documents from every working group that responds;
>>> please don't take this as a criticism if your document isn't chosen.
>>>
>>> If you think this is a good idea and want to take advantage of it, please contact
>>> your authors as soon as possible, so that they can make travel plans that allow
>>> them to get to the venue on Saturday rather than on Sunday.   Please bear in
>>> mind that the document selection process will take time, and set your authors'
>>> expectations appropriately.
>>>
>>> We will arrange for authors who wish to attend and who are selected to receive
>>> invitations, so that they can justify the early arrival to their management if
>>> necessary.
>>>
>>> Thanks!
>>
>
>


From Ted.Lemon@nominum.com  Mon Jan 20 10:49:05 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A9351A022F for <wgchairs@ietfa.amsl.com>; Mon, 20 Jan 2014 10:49:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pa6Qf8TRkF5f for <wgchairs@ietfa.amsl.com>; Mon, 20 Jan 2014 10:49:04 -0800 (PST)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by ietfa.amsl.com (Postfix) with ESMTP id D64D41A0240 for <wgchairs@ietf.org>; Mon, 20 Jan 2014 10:48:54 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP ID DSNKUt1vl7C5WM5sdP6l6OUAsARejDQI7s/R@postini.com; Mon, 20 Jan 2014 10:48:55 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id E27691B82DF for <wgchairs@ietf.org>; Mon, 20 Jan 2014 10:48:54 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 24FF519005C; Mon, 20 Jan 2014 10:48:54 -0800 (PST)
Received: from [10.0.10.40] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 20 Jan 2014 10:48:53 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Document language editing session in London
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <24B20D14B2CD29478C8D5D6E9CBB29F678F1F89D@HSV-MB002.huntsville.ads.sparta.com>
Date: Mon, 20 Jan 2014 13:48:51 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <52EE4FDE-C72C-45B1-82DC-67B1AF535587@nominum.com>
References: <D6557C43-1445-4660-804D-BD17ED9DD486@nominum.com> <B0D29E0424F2DE47A0B36779EC66677925867D07@nkgeml501-mbs.china.huawei.com> <9ADCA470-8200-4C9E-A728-FD69D155A569@wjcerveny.com>, <A7401A7C-2514-44A9-BDA9-CD01C7CA047B@nominum.com> <24B20D14B2CD29478C8D5D6E9CBB29F678F1F89D@HSV-MB002.huntsville.ads.sparta.com>
To: "Murphy, Sandra" <Sandra.Murphy@parsons.com>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Cc: "wgchairs@ietf.org Chairs" <wgchairs@ietf.org>, "Heather Flanagan \(RFC Series Editor\)" <rse@rfc-editor.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2014 18:49:05 -0000

On Jan 20, 2014, at 10:20 AM, Murphy, Sandra <Sandra.Murphy@parsons.com> =
wrote:
> This is unclear.  I'm guessing that one of those "not"s is not =
supposed to be "not".  :-)

Oops.   You are correct.   :)


From Ted.Lemon@nominum.com  Mon Jan 20 10:55:59 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 942031A022F for <wgchairs@ietfa.amsl.com>; Mon, 20 Jan 2014 10:55:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LJBdrPk6_4jK for <wgchairs@ietfa.amsl.com>; Mon, 20 Jan 2014 10:55:58 -0800 (PST)
Received: from exprod7og126.obsmtp.com (exprod7og126.obsmtp.com [64.18.2.206]) by ietfa.amsl.com (Postfix) with ESMTP id 47BAF1A0224 for <wgchairs@ietf.org>; Mon, 20 Jan 2014 10:55:58 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob126.postini.com ([64.18.6.12]) with SMTP ID DSNKUt1xPmMcK2ehFLq9B9sJPi4LVSj+g7R+@postini.com; Mon, 20 Jan 2014 10:55:58 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 5E6A81B82C9 for <wgchairs@ietf.org>; Mon, 20 Jan 2014 10:55:58 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 56FE919005C; Mon, 20 Jan 2014 10:55:58 -0800 (PST)
Received: from [10.0.10.40] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 20 Jan 2014 10:55:52 -0800
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Document language editing session in London
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <F28E9CD4-6D7F-4465-993D-8FBFCD231A21@wjcerveny.com>
Date: Mon, 20 Jan 2014 13:55:46 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <D13573CF-4D30-4391-B8D1-988A4DB2D9DB@nominum.com>
References: <D6557C43-1445-4660-804D-BD17ED9DD486@nominum.com> <B0D29E0424F2DE47A0B36779EC66677925867D07@nkgeml501-mbs.china.huawei.com> <9ADCA470-8200-4C9E-A728-FD69D155A569@wjcerveny.com> <A7401A7C-2514-44A9-BDA9-CD01C7CA047B@nominum.com> <F28E9CD4-6D7F-4465-993D-8FBFCD231A21@wjcerveny.com>
To: Bill Cerveny <bill@wjcerveny.com>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Cc: "wgchairs@ietf.org Chairs" <wgchairs@ietf.org>, "Heather Flanagan \(RFC Series Editor\)" <rse@rfc-editor.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2014 18:55:59 -0000

On Jan 19, 2014, at 8:00 PM, Bill Cerveny <bill@wjcerveny.com> wrote:
> It would be interesting to have ADs (or even previous ADs) offer their =
technical perspective on what they look for in documents and what common =
problems that they see in documents they review.

Different ADs look for different things.   We're supposed to consider =
process as well as content, and there's plenty of process to consider.   =
We also have debates about how to look at content, not only with each =
other but with document authors.   I can say for my part that I don't =
always find myself winning these debates=97sometimes my reaction to what =
the authors did misses the author's intentions, and once that's clear my =
objection becomes clearly invalid.

The best ways to become exposed to these discussions are, in no =
particular order, to be a document shepherd, to be a working group =
chair, and to be a document author.


From keith.drage@alcatel-lucent.com  Mon Jan 20 18:25:59 2014
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9ACFB1A000E for <wgchairs@ietfa.amsl.com>; Mon, 20 Jan 2014 18:25:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.9
X-Spam-Level: 
X-Spam-Status: No, score=-8.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_INVITATION=-2, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Van2Fvi2FAW for <wgchairs@ietfa.amsl.com>; Mon, 20 Jan 2014 18:25:56 -0800 (PST)
Received: from hoemail2.alcatel.com (hoemail2.alcatel.com [192.160.6.149]) by ietfa.amsl.com (Postfix) with ESMTP id F1C021A000C for <wgchairs@ietf.org>; Mon, 20 Jan 2014 18:25:55 -0800 (PST)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by hoemail2.alcatel.com (8.13.8/IER-o) with ESMTP id s0L2Pr4l012611 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 20 Jan 2014 20:25:54 -0600 (CST)
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id s0L2Ppuf018895 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 21 Jan 2014 03:25:52 +0100
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.26]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.02.0247.003; Tue, 21 Jan 2014 03:25:51 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "wgchairs@ietf.org" <wgchairs@ietf.org>
Subject: RE: Document language editing session in London
Thread-Topic: Document language editing session in London
Thread-Index: AQHPFfP3SHJmoxVby0SYn2E1UxTaXpqOaMVw
Date: Tue, 21 Jan 2014 02:25:51 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B11E9C3@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <D6557C43-1445-4660-804D-BD17ED9DD486@nominum.com> <B0D29E0424F2DE47A0B36779EC66677925867D07@nkgeml501-mbs.china.huawei.com> <9ADCA470-8200-4C9E-A728-FD69D155A569@wjcerveny.com> <52DD401B.7000106@alum.mit.edu>
In-Reply-To: <52DD401B.7000106@alum.mit.edu>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.41]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 02:25:59 -0000

Conversely, at the stage of IESG approval the Ads should not be worrying wi=
th this at all.

Given that the document is meant to be complete technically before WGLC, at=
 that point we should be able yo ascertain that:
-	the document is clearly written
-	that all requirements are clear
The WGLC will obviously polish this, but it is really the responsibility of=
 the WG chair to ensure this.

Keith=20

> -----Original Message-----
> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf=20
> Of Paul Kyzivat
> Sent: 20 January 2014 15:26
> To: wgchairs@ietf.org
> Subject: Re: Document language editing session in London
>=20
> I have a very different view of this from Bill.
>=20
> IMO, especially early in the process, what is important is to=20
> discuss the *concepts* in a draft, not the language usage.=20
> This is true whether the author is just a grammatically inept=20
> native English speaker/writer, or if the author doesn't have=20
> English as his native language.
>=20
> I find that documents written by many non-native English=20
> writers have usage that is "unusual" for natives, but in=20
> general it is still perfectly understandable. I find it=20
> easier to just "let it be" until the document is quite mature=20
> and the discussion of basics is over and it is time for polishing.
>=20
> Discussing language style and grammar in the midst of=20
> technical discussions is very distracting.
>=20
> 	Thanks,
> 	Paul
>=20
> On 1/19/14 6:38 PM, Bill Cerveny wrote:
> > [My first rant as a WG chair. I first wrote the rant, then took out=20
> > maybe 2/3rds of what I wrote :-) ]
> >
> > Having documents cleaned up grammatically as early as=20
> possible is very important and will result in better=20
> technical discussions, better (final) documents and a faster=20
> document turnaround from submission to publication.
> >
> > Last year my daughter, a recent college graduate in=20
> English, told me she aspired to be a technical writer, at=20
> which time I told her, "Gee, how'd you like to get experience=20
> reviewing technical documents?" I recruited her to review WG=20
> documents primarily from a grammatical, non-technical=20
> perspective. She was successful at providing constructive=20
> grammatical feedback to WG draft authors.
> >
> > Having worked with my daughter in in helping her get up to=20
> speed in reviewing IETF documents, it seems there are=20
> challenges a volunteer reviewer faces:
> > 1) There doesn't appear to be a clear, concise web page new=20
> volunteer reviewers can use as a starting point.
> > 2) How does one determine which documents are fair game for=20
> document review?  In theory, any document submitted to the=20
> IETF should be open for grammatical review the moment it is=20
> submitted, but given limited resources, from a WG=20
> perspective, we encourage reviewing WG documents first.
> > 3) How should a reviewer submit proposed changes? There=20
> isn't a consistent IETF recommendation for how to submit=20
> review comments/changes (such as format and/or tools) and it=20
> seems a consistent recommendation would be useful.
> > 4) There isn't any mechanism for encouraging (or even=20
> rewarding) reviewers who may not be intimately interested in=20
> the technical aspects of the documents. I sent my daughter an=20
> IETF88 T-shirt, but other than a thanks from the authors=20
> and/or the WG chairs, there isn't much that is done to=20
> encourage or reward the reviewers.
> >
> > At the risk of sounding non-IETFish here (we're mostly all=20
> "volunteers"), in a perfect world, it would make sense for=20
> authors to pay a document reviewer to review a document=20
> before it is even submitted to the IETF. The time involved=20
> with reviewing documents for grammatical correctness can be=20
> non-trivial. Certainly, there is an implied financial cost=20
> for the time that a volunteer reviewer spends to review a=20
> document. If the author is serious about submitting a concise=20
> technical document and having a concise technical document=20
> published, it would behoove the author to ensure that the=20
> document is grammatically correct before it is submitted to=20
> engineers for technical scrutiny. In this perfect world,=20
> there might be some sort of central list of people willing to=20
> review documents, although at a larger organization, it=20
> should be possible for the author to ask someone at the=20
> organization to review the document.
> >
> > Bill Cerveny
> >
> > On Jan 17, 2014, at 9:58 PM, Zongning <zongning@huawei.com> wrote:
> >
> >> Dear Ted, and all,
> >>
> >> As a non-native English speaker, I agree that this is a=20
> good practice to improve the quality of IETF I-Ds.
> >>
> >> I also share the opinion of Thomas that more volunteers=20
> should be called to help the whole community. Probably the=20
> similar practice could be conducted in a more "distributed"=20
> way, e.g., in WG level, led by WG co-chairs.
> >>
> >> Anyway, I will plan to submit I-D to this session in London, learn=20
> >> something important, then talk to my group, especially as a=20
> >> non-native English WG co-chair. :-)
> >>
> >> Thanks.
> >>
> >> -Ning
> >>
> >>> -----Original Message-----
> >>> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On=20
> Behalf Of Ted=20
> >>> Lemon
> >>> Sent: Friday, January 17, 2014 11:04 AM
> >>> To: wgchairs@ietf.org Chairs
> >>> Cc: Heather Flanagan (RFC Series Editor)
> >>> Subject: Document language editing session in London
> >>>
> >>> Dear WG Chairs:
> >>>
> >>> The IESG has decided to repeat the experiment that we=20
> tried in Berlin at the
> >>> upcoming London IETF meeting.   We would like to invite=20
> ten document
> >>> authors to a language editing session in London on the=20
> Saturday prior to the
> >>> IETF meeting.   The goal of this editing session will be=20
> for two area directors,
> >>> me and Joel Jaeggli, to each sit with a group of five=20
> document editors and work
> >>> on each editors' document for 30 minutes in a group=20
> setting.   Benoit Claise
> >>> has also offered to help if there are any French-speaking authors=20
> >>> who would like to participate.
> >>>
> >>> The plan for this work is to do two things: first, to review the=20
> >>> documents, and secondly, for the participants to have the=20
> opportunity to work with Joel or with
> >>> me to improve the quality of their documents.   The goal=20
> is specifically for
> >>> non-native english speakers who have documents that the working=20
> >>> group considers important, but which are felt to need=20
> help with english language
> >>> editing.   It is important that the authors _want_ to get=20
> help-that they
> >>> recognize that they could use help and that they are comfortable=20
> >>> getting that help in a small group setting.
> >>>
> >>> What the meeting will look like is that there will be one or two=20
> >>> tables in a meeting room; I will be at one table with=20
> five authors and a representative
> >>> from the RFC Editor.   Joel will be at a separate table,=20
> with the same
> >>> arrangement.   If there aren't enough authors, we may do=20
> a single table, as
> >>> we did in Berlin.
> >>>
> >>> Each of us will have briefly reviewed the five documents prior to=20
> >>> the meeting, and we expect that the authors will be=20
> familiar with each others' documents as
> >>> well.   For thirty minutes per document, we will sit with=20
> the author and go
> >>> over the document, offering comments and suggestions and=20
> getting feedback
> >>> from the author.   The other authors will follow this.=20
> Then we will move on to
> >>> the next author.   Joel will be doing the same thing at=20
> the other table.   The
> >>> RFC Editor will be observing and offering advice on=20
> request, or if=20
> >>> they can't resist, but the main goal is to take advantage=20
> of the technical editorial
> >>> expertise of the two ADs for this experiment.   At the=20
> end of the editing
> >>> session, we will have a half hour session where we talk=20
> about what=20
> >>> went well, if anything, and what went wrong, if anything,=20
> and how we=20
> >>> might do it better next time.
> >>>
> >>> Neither Joel nor I are experts on teaching english to non-native=20
> >>> speakers, so we do not claim any specific knowledge other=20
> than that=20
> >>> we both have a keen interest in improving the quality of IETF=20
> >>> documents, a fair amount of experience in at least trying=20
> to do so,=20
> >>> and a desire to help our colleagues to accomplish their goals.
> >>>
> >>> Our desired outcome from this meeting is twofold: first,=20
> to help the=20
> >>> specific authors who attend; secondly, to learn how to=20
> help authors=20
> >>> in general: what frustrations they have in writing documents for=20
> >>> IETF, what stumbling blocks they trip over, and how we=20
> can help them.
> >>>
> >>> What we are asking working group chairs to do is think=20
> about whether there
> >>> are documents in their working group that could use this=20
> sort of help.   If you
> >>> believe there are, please contact the authors of those=20
> documents and=20
> >>> ask them in a non-pushy way whether they would like to=20
> participate in this experiment.
> >>> Please let us know if any of your authors are interested=20
> in this.   If you have
> >>> more than one document that you'd like worked on, please=20
> tell us which one is
> >>> most important to you.   We will have to do a triage=20
> process unless the
> >>> response to this call for participants is tiny, so it's=20
> likely that we will only take
> >>> the document you think is more important.   If we get a=20
> really good response,
> >>> we won't be able to take documents from every working group that=20
> >>> responds; please don't take this as a criticism if your=20
> document isn't chosen.
> >>>
> >>> If you think this is a good idea and want to take=20
> advantage of it,=20
> >>> please contact your authors as soon as possible, so that=20
> they can make travel plans that allow
> >>> them to get to the venue on Saturday rather than on=20
> Sunday.   Please bear in
> >>> mind that the document selection process will take time,=20
> and set your authors'
> >>> expectations appropriately.
> >>>
> >>> We will arrange for authors who wish to attend and who=20
> are selected=20
> >>> to receive invitations, so that they can justify the=20
> early arrival=20
> >>> to their management if necessary.
> >>>
> >>> Thanks!
> >>
> >
> >
>=20
> =

From Ted.Lemon@nominum.com  Mon Jan 20 19:15:17 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9CB71A0024 for <wgchairs@ietfa.amsl.com>; Mon, 20 Jan 2014 19:15:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KeRdmzRWFkCA for <wgchairs@ietfa.amsl.com>; Mon, 20 Jan 2014 19:15:16 -0800 (PST)
Received: from exprod7og127.obsmtp.com (exprod7og127.obsmtp.com [64.18.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id DB5251A000F for <wgchairs@ietf.org>; Mon, 20 Jan 2014 19:15:15 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob127.postini.com ([64.18.6.12]) with SMTP ID DSNKUt3mQ62abmmaocNzxqPpeHDRq1uBSoPW@postini.com; Mon, 20 Jan 2014 19:15:16 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 1388D1B82E2 for <wgchairs@ietf.org>; Mon, 20 Jan 2014 19:15:15 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id DBD7919005C; Mon, 20 Jan 2014 19:15:14 -0800 (PST)
Received: from [10.0.10.40] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 20 Jan 2014 19:15:14 -0800
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Document language editing session in London
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <52DD401B.7000106@alum.mit.edu>
Date: Mon, 20 Jan 2014 22:15:10 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <AE9402B1-12C6-41DB-BB71-C0E643F01A8E@nominum.com>
References: <D6557C43-1445-4660-804D-BD17ED9DD486@nominum.com> <B0D29E0424F2DE47A0B36779EC66677925867D07@nkgeml501-mbs.china.huawei.com> <9ADCA470-8200-4C9E-A728-FD69D155A569@wjcerveny.com> <52DD401B.7000106@alum.mit.edu>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Cc: "wgchairs@ietf.org Chairs" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 03:15:18 -0000

On Jan 20, 2014, at 10:26 AM, Paul Kyzivat <pkyzivat@alum.mit.edu> =
wrote:
> I find that documents written by many non-native English writers have =
usage that is "unusual" for natives, but in general it is still =
perfectly understandable. I find it easier to just "let it be" until the =
document is quite mature and the discussion of basics is over and it is =
time for polishing.

You are probably much smarter than me.   For whatever reason, I find a =
lot of documents difficult to follow, even after IETF last call.  Hence =
the motivation to try to help improve them.


From pthubert@cisco.com  Mon Jan 20 22:43:20 2014
Return-Path: <pthubert@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 045831A029C for <wgchairs@ietfa.amsl.com>; Mon, 20 Jan 2014 22:43:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.036
X-Spam-Level: 
X-Spam-Status: No, score=-12.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, GB_I_INVITATION=-2, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aKNbd28iRclr for <wgchairs@ietfa.amsl.com>; Mon, 20 Jan 2014 22:43:17 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) by ietfa.amsl.com (Postfix) with ESMTP id F2E991A029B for <wgchairs@ietf.org>; Mon, 20 Jan 2014 22:43:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11377; q=dns/txt; s=iport; t=1390286597; x=1391496197; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=U68mhqhsmb7TsyA1TCleJ74J+DXNI23ITUlTKg2IBVE=; b=BxthbaSsrjqUndDNxwEwC7wm/eVyQk8S8LzGjf2ulI+RxJ0y8zpztrvn 83/qdVAaBmzofaj1EpuppTm6KrAPzDnPEPlz3hiNZNiX3eWOpCNIp/d9p 4ZDEYMsOap0cBbvNsu7IxgjdUhS78FytNNtLjqPgMIUcSTq2THVS0ukiO k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag4FAMQW3lKtJXG//2dsb2JhbABTBg6CfYEOu12BDRZ0giUBAQEEHR0xCREEAgEIEQQBAQEKFAkHMhQJCAIEARIIDIdxxAYXjicEERI4BoMegRQEk3qWQIJuP4FoQg
X-IronPort-AV: E=Sophos;i="4.95,695,1384300800"; d="scan'208";a="14275319"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by alln-iport-6.cisco.com with ESMTP; 21 Jan 2014 06:43:06 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id s0L6h6Yg012824 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 21 Jan 2014 06:43:06 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.207]) by xhc-rcd-x14.cisco.com ([173.37.183.88]) with mapi id 14.03.0123.003; Tue, 21 Jan 2014 00:43:05 -0600
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, "wgchairs@ietf.org" <wgchairs@ietf.org>
Subject: RE: Document language editing session in London
Thread-Topic: Document language editing session in London
Thread-Index: AQHPEzDHgXTubRI/uUmbfruOsivErpqKMIqAgALsp4CAAQjxgIAAuEaA///hEkA=
Date: Tue, 21 Jan 2014 06:43:02 +0000
Deferred-Delivery: Tue, 21 Jan 2014 06:42:00 +0000
Message-ID: <E045AECD98228444A58C61C200AE1BD8416A2C00@xmb-rcd-x01.cisco.com>
References: <D6557C43-1445-4660-804D-BD17ED9DD486@nominum.com> <B0D29E0424F2DE47A0B36779EC66677925867D07@nkgeml501-mbs.china.huawei.com> <9ADCA470-8200-4C9E-A728-FD69D155A569@wjcerveny.com> <52DD401B.7000106@alum.mit.edu> <949EF20990823C4C85C18D59AA11AD8B11E9C3@FR712WXCHMBA11.zeu.alcatel-lucent.com>
In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B11E9C3@FR712WXCHMBA11.zeu.alcatel-lucent.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.61.77.102]
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.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 06:43:20 -0000

As a non-Native chair, Keith, I'm unclear how I can accomplish that.=20
Maybe the WG could have a more official position for a secretary who would =
have to be fluent in English?
Would that be a slippery slope?

Cheers,

Pascal

> -----Original Message-----
> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of DRAGE,
> Keith (Keith)
> Sent: mardi 21 janvier 2014 03:26
> To: Paul Kyzivat; wgchairs@ietf.org
> Subject: RE: Document language editing session in London
>=20
> Conversely, at the stage of IESG approval the Ads should not be worrying =
with
> this at all.
>=20
> Given that the document is meant to be complete technically before WGLC, =
at
> that point we should be able yo ascertain that:
> -	the document is clearly written
> -	that all requirements are clear
> The WGLC will obviously polish this, but it is really the responsibility =
of the WG
> chair to ensure this.
>=20
> Keith
>=20
> > -----Original Message-----
> > From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of Paul
> > Kyzivat
> > Sent: 20 January 2014 15:26
> > To: wgchairs@ietf.org
> > Subject: Re: Document language editing session in London
> >
> > I have a very different view of this from Bill.
> >
> > IMO, especially early in the process, what is important is to discuss
> > the *concepts* in a draft, not the language usage.
> > This is true whether the author is just a grammatically inept native
> > English speaker/writer, or if the author doesn't have English as his
> > native language.
> >
> > I find that documents written by many non-native English writers have
> > usage that is "unusual" for natives, but in general it is still
> > perfectly understandable. I find it easier to just "let it be" until
> > the document is quite mature and the discussion of basics is over and
> > it is time for polishing.
> >
> > Discussing language style and grammar in the midst of technical
> > discussions is very distracting.
> >
> > 	Thanks,
> > 	Paul
> >
> > On 1/19/14 6:38 PM, Bill Cerveny wrote:
> > > [My first rant as a WG chair. I first wrote the rant, then took out
> > > maybe 2/3rds of what I wrote :-) ]
> > >
> > > Having documents cleaned up grammatically as early as
> > possible is very important and will result in better technical
> > discussions, better (final) documents and a faster document turnaround
> > from submission to publication.
> > >
> > > Last year my daughter, a recent college graduate in
> > English, told me she aspired to be a technical writer, at which time I
> > told her, "Gee, how'd you like to get experience reviewing technical
> > documents?" I recruited her to review WG documents primarily from a
> > grammatical, non-technical perspective. She was successful at
> > providing constructive grammatical feedback to WG draft authors.
> > >
> > > Having worked with my daughter in in helping her get up to
> > speed in reviewing IETF documents, it seems there are challenges a
> > volunteer reviewer faces:
> > > 1) There doesn't appear to be a clear, concise web page new
> > volunteer reviewers can use as a starting point.
> > > 2) How does one determine which documents are fair game for
> > document review?  In theory, any document submitted to the IETF should
> > be open for grammatical review the moment it is submitted, but given
> > limited resources, from a WG perspective, we encourage reviewing WG
> > documents first.
> > > 3) How should a reviewer submit proposed changes? There
> > isn't a consistent IETF recommendation for how to submit review
> > comments/changes (such as format and/or tools) and it seems a
> > consistent recommendation would be useful.
> > > 4) There isn't any mechanism for encouraging (or even
> > rewarding) reviewers who may not be intimately interested in the
> > technical aspects of the documents. I sent my daughter an
> > IETF88 T-shirt, but other than a thanks from the authors and/or the WG
> > chairs, there isn't much that is done to encourage or reward the
> > reviewers.
> > >
> > > At the risk of sounding non-IETFish here (we're mostly all
> > "volunteers"), in a perfect world, it would make sense for authors to
> > pay a document reviewer to review a document before it is even
> > submitted to the IETF. The time involved with reviewing documents for
> > grammatical correctness can be non-trivial. Certainly, there is an
> > implied financial cost for the time that a volunteer reviewer spends
> > to review a document. If the author is serious about submitting a
> > concise technical document and having a concise technical document
> > published, it would behoove the author to ensure that the document is
> > grammatically correct before it is submitted to engineers for
> > technical scrutiny. In this perfect world, there might be some sort of
> > central list of people willing to review documents, although at a
> > larger organization, it should be possible for the author to ask
> > someone at the organization to review the document.
> > >
> > > Bill Cerveny
> > >
> > > On Jan 17, 2014, at 9:58 PM, Zongning <zongning@huawei.com> wrote:
> > >
> > >> Dear Ted, and all,
> > >>
> > >> As a non-native English speaker, I agree that this is a
> > good practice to improve the quality of IETF I-Ds.
> > >>
> > >> I also share the opinion of Thomas that more volunteers
> > should be called to help the whole community. Probably the similar
> > practice could be conducted in a more "distributed"
> > way, e.g., in WG level, led by WG co-chairs.
> > >>
> > >> Anyway, I will plan to submit I-D to this session in London, learn
> > >> something important, then talk to my group, especially as a
> > >> non-native English WG co-chair. :-)
> > >>
> > >> Thanks.
> > >>
> > >> -Ning
> > >>
> > >>> -----Original Message-----
> > >>> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On
> > Behalf Of Ted
> > >>> Lemon
> > >>> Sent: Friday, January 17, 2014 11:04 AM
> > >>> To: wgchairs@ietf.org Chairs
> > >>> Cc: Heather Flanagan (RFC Series Editor)
> > >>> Subject: Document language editing session in London
> > >>>
> > >>> Dear WG Chairs:
> > >>>
> > >>> The IESG has decided to repeat the experiment that we
> > tried in Berlin at the
> > >>> upcoming London IETF meeting.   We would like to invite
> > ten document
> > >>> authors to a language editing session in London on the
> > Saturday prior to the
> > >>> IETF meeting.   The goal of this editing session will be
> > for two area directors,
> > >>> me and Joel Jaeggli, to each sit with a group of five
> > document editors and work
> > >>> on each editors' document for 30 minutes in a group
> > setting.   Benoit Claise
> > >>> has also offered to help if there are any French-speaking authors
> > >>> who would like to participate.
> > >>>
> > >>> The plan for this work is to do two things: first, to review the
> > >>> documents, and secondly, for the participants to have the
> > opportunity to work with Joel or with
> > >>> me to improve the quality of their documents.   The goal
> > is specifically for
> > >>> non-native english speakers who have documents that the working
> > >>> group considers important, but which are felt to need
> > help with english language
> > >>> editing.   It is important that the authors _want_ to get
> > help-that they
> > >>> recognize that they could use help and that they are comfortable
> > >>> getting that help in a small group setting.
> > >>>
> > >>> What the meeting will look like is that there will be one or two
> > >>> tables in a meeting room; I will be at one table with
> > five authors and a representative
> > >>> from the RFC Editor.   Joel will be at a separate table,
> > with the same
> > >>> arrangement.   If there aren't enough authors, we may do
> > a single table, as
> > >>> we did in Berlin.
> > >>>
> > >>> Each of us will have briefly reviewed the five documents prior to
> > >>> the meeting, and we expect that the authors will be
> > familiar with each others' documents as
> > >>> well.   For thirty minutes per document, we will sit with
> > the author and go
> > >>> over the document, offering comments and suggestions and
> > getting feedback
> > >>> from the author.   The other authors will follow this.
> > Then we will move on to
> > >>> the next author.   Joel will be doing the same thing at
> > the other table.   The
> > >>> RFC Editor will be observing and offering advice on
> > request, or if
> > >>> they can't resist, but the main goal is to take advantage
> > of the technical editorial
> > >>> expertise of the two ADs for this experiment.   At the
> > end of the editing
> > >>> session, we will have a half hour session where we talk
> > about what
> > >>> went well, if anything, and what went wrong, if anything,
> > and how we
> > >>> might do it better next time.
> > >>>
> > >>> Neither Joel nor I are experts on teaching english to non-native
> > >>> speakers, so we do not claim any specific knowledge other
> > than that
> > >>> we both have a keen interest in improving the quality of IETF
> > >>> documents, a fair amount of experience in at least trying
> > to do so,
> > >>> and a desire to help our colleagues to accomplish their goals.
> > >>>
> > >>> Our desired outcome from this meeting is twofold: first,
> > to help the
> > >>> specific authors who attend; secondly, to learn how to
> > help authors
> > >>> in general: what frustrations they have in writing documents for
> > >>> IETF, what stumbling blocks they trip over, and how we
> > can help them.
> > >>>
> > >>> What we are asking working group chairs to do is think
> > about whether there
> > >>> are documents in their working group that could use this
> > sort of help.   If you
> > >>> believe there are, please contact the authors of those
> > documents and
> > >>> ask them in a non-pushy way whether they would like to
> > participate in this experiment.
> > >>> Please let us know if any of your authors are interested
> > in this.   If you have
> > >>> more than one document that you'd like worked on, please
> > tell us which one is
> > >>> most important to you.   We will have to do a triage
> > process unless the
> > >>> response to this call for participants is tiny, so it's
> > likely that we will only take
> > >>> the document you think is more important.   If we get a
> > really good response,
> > >>> we won't be able to take documents from every working group that
> > >>> responds; please don't take this as a criticism if your
> > document isn't chosen.
> > >>>
> > >>> If you think this is a good idea and want to take
> > advantage of it,
> > >>> please contact your authors as soon as possible, so that
> > they can make travel plans that allow
> > >>> them to get to the venue on Saturday rather than on
> > Sunday.   Please bear in
> > >>> mind that the document selection process will take time,
> > and set your authors'
> > >>> expectations appropriately.
> > >>>
> > >>> We will arrange for authors who wish to attend and who
> > are selected
> > >>> to receive invitations, so that they can justify the
> > early arrival
> > >>> to their management if necessary.
> > >>>
> > >>> Thanks!
> > >>
> > >
> > >
> >
> >

From ynir@checkpoint.com  Mon Jan 20 23:03:38 2014
Return-Path: <ynir@checkpoint.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04DF51A02BB for <wgchairs@ietfa.amsl.com>; Mon, 20 Jan 2014 23:03:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.436
X-Spam-Level: 
X-Spam-Status: No, score=-7.436 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Uml3CxroDeWL for <wgchairs@ietfa.amsl.com>; Mon, 20 Jan 2014 23:03:37 -0800 (PST)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id C75351A005A for <wgchairs@ietf.org>; Mon, 20 Jan 2014 23:03:36 -0800 (PST)
Received: from IL-EX10.ad.checkpoint.com ([194.29.34.147]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id s0L73M13025813; Tue, 21 Jan 2014 09:03:22 +0200
X-CheckPoint: {52DE15C0-15-1B221DC2-1FFFF}
Received: from DAG-EX10.ad.checkpoint.com ([169.254.3.110]) by IL-EX10.ad.checkpoint.com ([169.254.2.228]) with mapi id 14.03.0123.003; Tue, 21 Jan 2014 09:03:22 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Subject: Re: Document language editing session in London
Thread-Topic: Document language editing session in London
Thread-Index: AQHPEzDTE6C8OuHMfUKweuWOkfxxuJqJqm2AgALsp4CAAQjygIAAuEWAgABH2wCAAAWugA==
Date: Tue, 21 Jan 2014 07:03:21 +0000
Message-ID: <CAD857FF-AEF2-4193-AA55-7FF3FB2BF06C@checkpoint.com>
References: <D6557C43-1445-4660-804D-BD17ED9DD486@nominum.com> <B0D29E0424F2DE47A0B36779EC66677925867D07@nkgeml501-mbs.china.huawei.com> <9ADCA470-8200-4C9E-A728-FD69D155A569@wjcerveny.com> <52DD401B.7000106@alum.mit.edu> <949EF20990823C4C85C18D59AA11AD8B11E9C3@FR712WXCHMBA11.zeu.alcatel-lucent.com> <E045AECD98228444A58C61C200AE1BD8416A2C00@xmb-rcd-x01.cisco.com>
In-Reply-To: <E045AECD98228444A58C61C200AE1BD8416A2C00@xmb-rcd-x01.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.20.194]
x-kse-antivirus-interceptor-info: protection disabled
Content-Type: text/plain; charset="us-ascii"
Content-ID: <0DEA480850066C41A956239B8FB906AC@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 07:03:38 -0000

On Jan 21, 2014, at 8:43 AM, "Pascal Thubert (pthubert)" <pthubert@cisco.co=
m>
 wrote:

> As a non-Native chair, Keith, I'm unclear how I can accomplish that.=20
> Maybe the WG could have a more official position for a secretary who woul=
d have to be fluent in English?
> Would that be a slippery slope?
>=20

Sure would. Define "fluent".

Do we need to be able to construct sentences like these to be considered fl=
uent?

"I would have been going to have had the document have some more language r=
eview before the next meeting, but then I would have had to have the author=
s not have time to polish the technical aspects sufficiently."

Not bad for someone whose native language does not have perfect tenses, rig=
ht?

Seriously, though, most of us are fluent enough to produce a clear technica=
l document, and to know one when we see one. Those who don't can and should=
 seek help. There are certain mistakes that we are more likely to make or o=
verlook. Improper (for English) use of commas is one. Mishandling of tenses=
 is another. Splitting infinitives. But those are not harmful to understand=
ing, and the RFC editor can and does fix them.=20

Yoav


From joelja@bogus.com  Mon Jan 20 23:16:54 2014
Return-Path: <joelja@bogus.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B4091A0053 for <wgchairs@ietfa.amsl.com>; Mon, 20 Jan 2014 23:16:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.435
X-Spam-Level: 
X-Spam-Status: No, score=-4.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_INVITATION=-2, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NSzUL1M-UJ1u for <wgchairs@ietfa.amsl.com>; Mon, 20 Jan 2014 23:16:51 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 955F51A005E for <wgchairs@ietf.org>; Mon, 20 Jan 2014 23:16:51 -0800 (PST)
Received: from mb-aye.local (c-50-174-18-221.hsd1.ca.comcast.net [50.174.18.221]) (authenticated bits=0) by nagasaki.bogus.com (8.14.7/8.14.7) with ESMTP id s0L7GYC7075243 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 21 Jan 2014 07:16:35 GMT (envelope-from joelja@bogus.com)
Message-ID: <52DE1ECD.5020004@bogus.com>
Date: Mon, 20 Jan 2014 23:16:29 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:27.0) Gecko/20100101 Thunderbird/27.0
MIME-Version: 1.0
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>, "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, "wgchairs@ietf.org" <wgchairs@ietf.org>
Subject: Re: Document language editing session in London
References: <D6557C43-1445-4660-804D-BD17ED9DD486@nominum.com> <B0D29E0424F2DE47A0B36779EC66677925867D07@nkgeml501-mbs.china.huawei.com> <9ADCA470-8200-4C9E-A728-FD69D155A569@wjcerveny.com> <52DD401B.7000106@alum.mit.edu> <949EF20990823C4C85C18D59AA11AD8B11E9C3@FR712WXCHMBA11.zeu.alcatel-lucent.com> <E045AECD98228444A58C61C200AE1BD8416A2C00@xmb-rcd-x01.cisco.com>
In-Reply-To: <E045AECD98228444A58C61C200AE1BD8416A2C00@xmb-rcd-x01.cisco.com>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="KJ15sO4rxEJGhb4VTFfTWWB6TqgKomOFn"
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (nagasaki.bogus.com [147.28.0.81]); Tue, 21 Jan 2014 07:16:35 +0000 (UTC)
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 07:16:54 -0000

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

On 1/20/14, 10:43 PM, Pascal Thubert (pthubert) wrote:
> As a non-Native chair, Keith, I'm unclear how I can accomplish that.=20
> Maybe the WG could have a more official position for a secretary who wo=
uld have to be fluent in English?
> Would that be a slippery slope?

I very much do not want to come out of this series of experiments with
more requirements.

> Cheers,
>=20
> Pascal
>=20
>> -----Original Message-----
>> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of DRAGE,
>> Keith (Keith)
>> Sent: mardi 21 janvier 2014 03:26
>> To: Paul Kyzivat; wgchairs@ietf.org
>> Subject: RE: Document language editing session in London
>>
>> Conversely, at the stage of IESG approval the Ads should not be worryi=
ng with
>> this at all.
>>
>> Given that the document is meant to be complete technically before WGL=
C, at
>> that point we should be able yo ascertain that:
>> -	the document is clearly written
>> -	that all requirements are clear
>> The WGLC will obviously polish this, but it is really the responsibili=
ty of the WG
>> chair to ensure this.
>>
>> Keith
>>
>>> -----Original Message-----
>>> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of Paul
>>> Kyzivat
>>> Sent: 20 January 2014 15:26
>>> To: wgchairs@ietf.org
>>> Subject: Re: Document language editing session in London
>>>
>>> I have a very different view of this from Bill.
>>>
>>> IMO, especially early in the process, what is important is to discuss=

>>> the *concepts* in a draft, not the language usage.
>>> This is true whether the author is just a grammatically inept native
>>> English speaker/writer, or if the author doesn't have English as his
>>> native language.
>>>
>>> I find that documents written by many non-native English writers have=

>>> usage that is "unusual" for natives, but in general it is still
>>> perfectly understandable. I find it easier to just "let it be" until
>>> the document is quite mature and the discussion of basics is over and=

>>> it is time for polishing.
>>>
>>> Discussing language style and grammar in the midst of technical
>>> discussions is very distracting.
>>>
>>> 	Thanks,
>>> 	Paul
>>>
>>> On 1/19/14 6:38 PM, Bill Cerveny wrote:
>>>> [My first rant as a WG chair. I first wrote the rant, then took out
>>>> maybe 2/3rds of what I wrote :-) ]
>>>>
>>>> Having documents cleaned up grammatically as early as
>>> possible is very important and will result in better technical
>>> discussions, better (final) documents and a faster document turnaroun=
d
>>> from submission to publication.
>>>>
>>>> Last year my daughter, a recent college graduate in
>>> English, told me she aspired to be a technical writer, at which time =
I
>>> told her, "Gee, how'd you like to get experience reviewing technical
>>> documents?" I recruited her to review WG documents primarily from a
>>> grammatical, non-technical perspective. She was successful at
>>> providing constructive grammatical feedback to WG draft authors.
>>>>
>>>> Having worked with my daughter in in helping her get up to
>>> speed in reviewing IETF documents, it seems there are challenges a
>>> volunteer reviewer faces:
>>>> 1) There doesn't appear to be a clear, concise web page new
>>> volunteer reviewers can use as a starting point.
>>>> 2) How does one determine which documents are fair game for
>>> document review?  In theory, any document submitted to the IETF shoul=
d
>>> be open for grammatical review the moment it is submitted, but given
>>> limited resources, from a WG perspective, we encourage reviewing WG
>>> documents first.
>>>> 3) How should a reviewer submit proposed changes? There
>>> isn't a consistent IETF recommendation for how to submit review
>>> comments/changes (such as format and/or tools) and it seems a
>>> consistent recommendation would be useful.
>>>> 4) There isn't any mechanism for encouraging (or even
>>> rewarding) reviewers who may not be intimately interested in the
>>> technical aspects of the documents. I sent my daughter an
>>> IETF88 T-shirt, but other than a thanks from the authors and/or the W=
G
>>> chairs, there isn't much that is done to encourage or reward the
>>> reviewers.
>>>>
>>>> At the risk of sounding non-IETFish here (we're mostly all
>>> "volunteers"), in a perfect world, it would make sense for authors to=

>>> pay a document reviewer to review a document before it is even
>>> submitted to the IETF. The time involved with reviewing documents for=

>>> grammatical correctness can be non-trivial. Certainly, there is an
>>> implied financial cost for the time that a volunteer reviewer spends
>>> to review a document. If the author is serious about submitting a
>>> concise technical document and having a concise technical document
>>> published, it would behoove the author to ensure that the document is=

>>> grammatically correct before it is submitted to engineers for
>>> technical scrutiny. In this perfect world, there might be some sort o=
f
>>> central list of people willing to review documents, although at a
>>> larger organization, it should be possible for the author to ask
>>> someone at the organization to review the document.
>>>>
>>>> Bill Cerveny
>>>>
>>>> On Jan 17, 2014, at 9:58 PM, Zongning <zongning@huawei.com> wrote:
>>>>
>>>>> Dear Ted, and all,
>>>>>
>>>>> As a non-native English speaker, I agree that this is a
>>> good practice to improve the quality of IETF I-Ds.
>>>>>
>>>>> I also share the opinion of Thomas that more volunteers
>>> should be called to help the whole community. Probably the similar
>>> practice could be conducted in a more "distributed"
>>> way, e.g., in WG level, led by WG co-chairs.
>>>>>
>>>>> Anyway, I will plan to submit I-D to this session in London, learn
>>>>> something important, then talk to my group, especially as a
>>>>> non-native English WG co-chair. :-)
>>>>>
>>>>> Thanks.
>>>>>
>>>>> -Ning
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On
>>> Behalf Of Ted
>>>>>> Lemon
>>>>>> Sent: Friday, January 17, 2014 11:04 AM
>>>>>> To: wgchairs@ietf.org Chairs
>>>>>> Cc: Heather Flanagan (RFC Series Editor)
>>>>>> Subject: Document language editing session in London
>>>>>>
>>>>>> Dear WG Chairs:
>>>>>>
>>>>>> The IESG has decided to repeat the experiment that we
>>> tried in Berlin at the
>>>>>> upcoming London IETF meeting.   We would like to invite
>>> ten document
>>>>>> authors to a language editing session in London on the
>>> Saturday prior to the
>>>>>> IETF meeting.   The goal of this editing session will be
>>> for two area directors,
>>>>>> me and Joel Jaeggli, to each sit with a group of five
>>> document editors and work
>>>>>> on each editors' document for 30 minutes in a group
>>> setting.   Benoit Claise
>>>>>> has also offered to help if there are any French-speaking authors
>>>>>> who would like to participate.
>>>>>>
>>>>>> The plan for this work is to do two things: first, to review the
>>>>>> documents, and secondly, for the participants to have the
>>> opportunity to work with Joel or with
>>>>>> me to improve the quality of their documents.   The goal
>>> is specifically for
>>>>>> non-native english speakers who have documents that the working
>>>>>> group considers important, but which are felt to need
>>> help with english language
>>>>>> editing.   It is important that the authors _want_ to get
>>> help-that they
>>>>>> recognize that they could use help and that they are comfortable
>>>>>> getting that help in a small group setting.
>>>>>>
>>>>>> What the meeting will look like is that there will be one or two
>>>>>> tables in a meeting room; I will be at one table with
>>> five authors and a representative
>>>>>> from the RFC Editor.   Joel will be at a separate table,
>>> with the same
>>>>>> arrangement.   If there aren't enough authors, we may do
>>> a single table, as
>>>>>> we did in Berlin.
>>>>>>
>>>>>> Each of us will have briefly reviewed the five documents prior to
>>>>>> the meeting, and we expect that the authors will be
>>> familiar with each others' documents as
>>>>>> well.   For thirty minutes per document, we will sit with
>>> the author and go
>>>>>> over the document, offering comments and suggestions and
>>> getting feedback
>>>>>> from the author.   The other authors will follow this.
>>> Then we will move on to
>>>>>> the next author.   Joel will be doing the same thing at
>>> the other table.   The
>>>>>> RFC Editor will be observing and offering advice on
>>> request, or if
>>>>>> they can't resist, but the main goal is to take advantage
>>> of the technical editorial
>>>>>> expertise of the two ADs for this experiment.   At the
>>> end of the editing
>>>>>> session, we will have a half hour session where we talk
>>> about what
>>>>>> went well, if anything, and what went wrong, if anything,
>>> and how we
>>>>>> might do it better next time.
>>>>>>
>>>>>> Neither Joel nor I are experts on teaching english to non-native
>>>>>> speakers, so we do not claim any specific knowledge other
>>> than that
>>>>>> we both have a keen interest in improving the quality of IETF
>>>>>> documents, a fair amount of experience in at least trying
>>> to do so,
>>>>>> and a desire to help our colleagues to accomplish their goals.
>>>>>>
>>>>>> Our desired outcome from this meeting is twofold: first,
>>> to help the
>>>>>> specific authors who attend; secondly, to learn how to
>>> help authors
>>>>>> in general: what frustrations they have in writing documents for
>>>>>> IETF, what stumbling blocks they trip over, and how we
>>> can help them.
>>>>>>
>>>>>> What we are asking working group chairs to do is think
>>> about whether there
>>>>>> are documents in their working group that could use this
>>> sort of help.   If you
>>>>>> believe there are, please contact the authors of those
>>> documents and
>>>>>> ask them in a non-pushy way whether they would like to
>>> participate in this experiment.
>>>>>> Please let us know if any of your authors are interested
>>> in this.   If you have
>>>>>> more than one document that you'd like worked on, please
>>> tell us which one is
>>>>>> most important to you.   We will have to do a triage
>>> process unless the
>>>>>> response to this call for participants is tiny, so it's
>>> likely that we will only take
>>>>>> the document you think is more important.   If we get a
>>> really good response,
>>>>>> we won't be able to take documents from every working group that
>>>>>> responds; please don't take this as a criticism if your
>>> document isn't chosen.
>>>>>>
>>>>>> If you think this is a good idea and want to take
>>> advantage of it,
>>>>>> please contact your authors as soon as possible, so that
>>> they can make travel plans that allow
>>>>>> them to get to the venue on Saturday rather than on
>>> Sunday.   Please bear in
>>>>>> mind that the document selection process will take time,
>>> and set your authors'
>>>>>> expectations appropriately.
>>>>>>
>>>>>> We will arrange for authors who wish to attend and who
>>> are selected
>>>>>> to receive invitations, so that they can justify the
>>> early arrival
>>>>>> to their management if necessary.
>>>>>>
>>>>>> Thanks!
>>>>>
>>>>
>>>>
>>>
>>>
>=20



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

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

iEYEARECAAYFAlLeHs0ACgkQ8AA1q7Z/VrLSlwCggMr51zCeO2WW+vqfXPIrcT9I
CpYAnionpnDO5qlTRE8Toagj4AqWmh1i
=D9hT
-----END PGP SIGNATURE-----

--KJ15sO4rxEJGhb4VTFfTWWB6TqgKomOFn--

From keith.drage@alcatel-lucent.com  Tue Jan 21 00:28:14 2014
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 685BA1A006B for <wgchairs@ietfa.amsl.com>; Tue, 21 Jan 2014 00:28:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.9
X-Spam-Level: 
X-Spam-Status: No, score=-8.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_INVITATION=-2, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VxMAOSPvc91X for <wgchairs@ietfa.amsl.com>; Tue, 21 Jan 2014 00:28:11 -0800 (PST)
Received: from hoemail2.alcatel.com (hoemail2.alcatel.com [192.160.6.149]) by ietfa.amsl.com (Postfix) with ESMTP id F274A1A0068 for <wgchairs@ietf.org>; Tue, 21 Jan 2014 00:28:10 -0800 (PST)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by hoemail2.alcatel.com (8.13.8/IER-o) with ESMTP id s0L8S7ZV005378 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 21 Jan 2014 02:28:08 -0600 (CST)
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id s0L8S6UY026608 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 21 Jan 2014 09:28:06 +0100
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.26]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.02.0247.003; Tue, 21 Jan 2014 09:28:06 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, "wgchairs@ietf.org" <wgchairs@ietf.org>
Subject: RE: Document language editing session in London
Thread-Topic: Document language editing session in London
Thread-Index: AQHPEzDHgXTubRI/uUmbfruOsivErpqKMIqAgALsp4CAAQjxgIAAuEaA///hEkCAAAQi4A==
Date: Tue, 21 Jan 2014 08:28:06 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B11F0CB@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <D6557C43-1445-4660-804D-BD17ED9DD486@nominum.com> <B0D29E0424F2DE47A0B36779EC66677925867D07@nkgeml501-mbs.china.huawei.com> <9ADCA470-8200-4C9E-A728-FD69D155A569@wjcerveny.com> <52DD401B.7000106@alum.mit.edu> <949EF20990823C4C85C18D59AA11AD8B11E9C3@FR712WXCHMBA11.zeu.alcatel-lucent.com> <E045AECD98228444A58C61C200AE1BD8416A2C00@xmb-rcd-x01.cisco.com>
In-Reply-To: <E045AECD98228444A58C61C200AE1BD8416A2C00@xmb-rcd-x01.cisco.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.40]
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.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 08:28:14 -0000

I'm not saying that a chair has to do it, only ensure that it is done.

Given that we have non-native ADs it is certainly more ridiculous to expect=
 them to do it.

I'd also indicate that in many respects requirement writing is not good eng=
lish. We are not looking for creating a variety of style, good prose or any=
thing like that. We are looking for absolute clarity in the specification, =
such that there can be no misinterpretation. As such anyone who can learn a=
 variety of programming languages should not find this substantially more d=
ifficult.=20

Keith

> -----Original Message-----
> From: Pascal Thubert (pthubert) [mailto:pthubert@cisco.com]=20
> Sent: 21 January 2014 06:43
> To: DRAGE, Keith (Keith); Paul Kyzivat; wgchairs@ietf.org
> Subject: RE: Document language editing session in London
>=20
> As a non-Native chair, Keith, I'm unclear how I can accomplish that.=20
> Maybe the WG could have a more official position for a=20
> secretary who would have to be fluent in English?
> Would that be a slippery slope?
>=20
> Cheers,
>=20
> Pascal
>=20
> > -----Original Message-----
> > From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf=20
> Of DRAGE,=20
> > Keith (Keith)
> > Sent: mardi 21 janvier 2014 03:26
> > To: Paul Kyzivat; wgchairs@ietf.org
> > Subject: RE: Document language editing session in London
> >=20
> > Conversely, at the stage of IESG approval the Ads should not be=20
> > worrying with this at all.
> >=20
> > Given that the document is meant to be complete technically before=20
> > WGLC, at that point we should be able yo ascertain that:
> > -	the document is clearly written
> > -	that all requirements are clear
> > The WGLC will obviously polish this, but it is really the=20
> > responsibility of the WG chair to ensure this.
> >=20
> > Keith
> >=20
> > > -----Original Message-----
> > > From: WGChairs [mailto:wgchairs-bounces@ietf.org] On=20
> Behalf Of Paul=20
> > > Kyzivat
> > > Sent: 20 January 2014 15:26
> > > To: wgchairs@ietf.org
> > > Subject: Re: Document language editing session in London
> > >
> > > I have a very different view of this from Bill.
> > >
> > > IMO, especially early in the process, what is important is to=20
> > > discuss the *concepts* in a draft, not the language usage.
> > > This is true whether the author is just a grammatically=20
> inept native=20
> > > English speaker/writer, or if the author doesn't have=20
> English as his=20
> > > native language.
> > >
> > > I find that documents written by many non-native English writers=20
> > > have usage that is "unusual" for natives, but in general=20
> it is still=20
> > > perfectly understandable. I find it easier to just "let=20
> it be" until=20
> > > the document is quite mature and the discussion of basics is over=20
> > > and it is time for polishing.
> > >
> > > Discussing language style and grammar in the midst of technical=20
> > > discussions is very distracting.
> > >
> > > 	Thanks,
> > > 	Paul
> > >
> > > On 1/19/14 6:38 PM, Bill Cerveny wrote:
> > > > [My first rant as a WG chair. I first wrote the rant, then took=20
> > > > out maybe 2/3rds of what I wrote :-) ]
> > > >
> > > > Having documents cleaned up grammatically as early as
> > > possible is very important and will result in better technical=20
> > > discussions, better (final) documents and a faster document=20
> > > turnaround from submission to publication.
> > > >
> > > > Last year my daughter, a recent college graduate in
> > > English, told me she aspired to be a technical writer, at=20
> which time=20
> > > I told her, "Gee, how'd you like to get experience reviewing=20
> > > technical documents?" I recruited her to review WG documents=20
> > > primarily from a grammatical, non-technical perspective. She was=20
> > > successful at providing constructive grammatical feedback=20
> to WG draft authors.
> > > >
> > > > Having worked with my daughter in in helping her get up to
> > > speed in reviewing IETF documents, it seems there are=20
> challenges a=20
> > > volunteer reviewer faces:
> > > > 1) There doesn't appear to be a clear, concise web page new
> > > volunteer reviewers can use as a starting point.
> > > > 2) How does one determine which documents are fair game for
> > > document review?  In theory, any document submitted to the IETF=20
> > > should be open for grammatical review the moment it is submitted,=20
> > > but given limited resources, from a WG perspective, we encourage=20
> > > reviewing WG documents first.
> > > > 3) How should a reviewer submit proposed changes? There
> > > isn't a consistent IETF recommendation for how to submit review=20
> > > comments/changes (such as format and/or tools) and it seems a=20
> > > consistent recommendation would be useful.
> > > > 4) There isn't any mechanism for encouraging (or even
> > > rewarding) reviewers who may not be intimately interested in the=20
> > > technical aspects of the documents. I sent my daughter an
> > > IETF88 T-shirt, but other than a thanks from the authors=20
> and/or the=20
> > > WG chairs, there isn't much that is done to encourage or=20
> reward the=20
> > > reviewers.
> > > >
> > > > At the risk of sounding non-IETFish here (we're mostly all
> > > "volunteers"), in a perfect world, it would make sense=20
> for authors=20
> > > to pay a document reviewer to review a document before it is even=20
> > > submitted to the IETF. The time involved with reviewing documents=20
> > > for grammatical correctness can be non-trivial.=20
> Certainly, there is=20
> > > an implied financial cost for the time that a volunteer reviewer=20
> > > spends to review a document. If the author is serious about=20
> > > submitting a concise technical document and having a concise=20
> > > technical document published, it would behoove the author=20
> to ensure=20
> > > that the document is grammatically correct before it is=20
> submitted to=20
> > > engineers for technical scrutiny. In this perfect world,=20
> there might=20
> > > be some sort of central list of people willing to review=20
> documents,=20
> > > although at a larger organization, it should be possible for the=20
> > > author to ask someone at the organization to review the document.
> > > >
> > > > Bill Cerveny
> > > >
> > > > On Jan 17, 2014, at 9:58 PM, Zongning=20
> <zongning@huawei.com> wrote:
> > > >
> > > >> Dear Ted, and all,
> > > >>
> > > >> As a non-native English speaker, I agree that this is a
> > > good practice to improve the quality of IETF I-Ds.
> > > >>
> > > >> I also share the opinion of Thomas that more volunteers
> > > should be called to help the whole community. Probably=20
> the similar=20
> > > practice could be conducted in a more "distributed"
> > > way, e.g., in WG level, led by WG co-chairs.
> > > >>
> > > >> Anyway, I will plan to submit I-D to this session in London,=20
> > > >> learn something important, then talk to my group,=20
> especially as a=20
> > > >> non-native English WG co-chair. :-)
> > > >>
> > > >> Thanks.
> > > >>
> > > >> -Ning
> > > >>
> > > >>> -----Original Message-----
> > > >>> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On
> > > Behalf Of Ted
> > > >>> Lemon
> > > >>> Sent: Friday, January 17, 2014 11:04 AM
> > > >>> To: wgchairs@ietf.org Chairs
> > > >>> Cc: Heather Flanagan (RFC Series Editor)
> > > >>> Subject: Document language editing session in London
> > > >>>
> > > >>> Dear WG Chairs:
> > > >>>
> > > >>> The IESG has decided to repeat the experiment that we
> > > tried in Berlin at the
> > > >>> upcoming London IETF meeting.   We would like to invite
> > > ten document
> > > >>> authors to a language editing session in London on the
> > > Saturday prior to the
> > > >>> IETF meeting.   The goal of this editing session will be
> > > for two area directors,
> > > >>> me and Joel Jaeggli, to each sit with a group of five
> > > document editors and work
> > > >>> on each editors' document for 30 minutes in a group
> > > setting.   Benoit Claise
> > > >>> has also offered to help if there are any French-speaking=20
> > > >>> authors who would like to participate.
> > > >>>
> > > >>> The plan for this work is to do two things: first, to=20
> review the=20
> > > >>> documents, and secondly, for the participants to have the
> > > opportunity to work with Joel or with
> > > >>> me to improve the quality of their documents.   The goal
> > > is specifically for
> > > >>> non-native english speakers who have documents that=20
> the working=20
> > > >>> group considers important, but which are felt to need
> > > help with english language
> > > >>> editing.   It is important that the authors _want_ to get
> > > help-that they
> > > >>> recognize that they could use help and that they are=20
> comfortable=20
> > > >>> getting that help in a small group setting.
> > > >>>
> > > >>> What the meeting will look like is that there will be=20
> one or two=20
> > > >>> tables in a meeting room; I will be at one table with
> > > five authors and a representative
> > > >>> from the RFC Editor.   Joel will be at a separate table,
> > > with the same
> > > >>> arrangement.   If there aren't enough authors, we may do
> > > a single table, as
> > > >>> we did in Berlin.
> > > >>>
> > > >>> Each of us will have briefly reviewed the five=20
> documents prior=20
> > > >>> to the meeting, and we expect that the authors will be
> > > familiar with each others' documents as
> > > >>> well.   For thirty minutes per document, we will sit with
> > > the author and go
> > > >>> over the document, offering comments and suggestions and
> > > getting feedback
> > > >>> from the author.   The other authors will follow this.
> > > Then we will move on to
> > > >>> the next author.   Joel will be doing the same thing at
> > > the other table.   The
> > > >>> RFC Editor will be observing and offering advice on
> > > request, or if
> > > >>> they can't resist, but the main goal is to take advantage
> > > of the technical editorial
> > > >>> expertise of the two ADs for this experiment.   At the
> > > end of the editing
> > > >>> session, we will have a half hour session where we talk
> > > about what
> > > >>> went well, if anything, and what went wrong, if anything,
> > > and how we
> > > >>> might do it better next time.
> > > >>>
> > > >>> Neither Joel nor I are experts on teaching english to=20
> non-native=20
> > > >>> speakers, so we do not claim any specific knowledge other
> > > than that
> > > >>> we both have a keen interest in improving the quality of IETF=20
> > > >>> documents, a fair amount of experience in at least trying
> > > to do so,
> > > >>> and a desire to help our colleagues to accomplish their goals.
> > > >>>
> > > >>> Our desired outcome from this meeting is twofold: first,
> > > to help the
> > > >>> specific authors who attend; secondly, to learn how to
> > > help authors
> > > >>> in general: what frustrations they have in writing=20
> documents for=20
> > > >>> IETF, what stumbling blocks they trip over, and how we
> > > can help them.
> > > >>>
> > > >>> What we are asking working group chairs to do is think
> > > about whether there
> > > >>> are documents in their working group that could use this
> > > sort of help.   If you
> > > >>> believe there are, please contact the authors of those
> > > documents and
> > > >>> ask them in a non-pushy way whether they would like to
> > > participate in this experiment.
> > > >>> Please let us know if any of your authors are interested
> > > in this.   If you have
> > > >>> more than one document that you'd like worked on, please
> > > tell us which one is
> > > >>> most important to you.   We will have to do a triage
> > > process unless the
> > > >>> response to this call for participants is tiny, so it's
> > > likely that we will only take
> > > >>> the document you think is more important.   If we get a
> > > really good response,
> > > >>> we won't be able to take documents from every working=20
> group that=20
> > > >>> responds; please don't take this as a criticism if your
> > > document isn't chosen.
> > > >>>
> > > >>> If you think this is a good idea and want to take
> > > advantage of it,
> > > >>> please contact your authors as soon as possible, so that
> > > they can make travel plans that allow
> > > >>> them to get to the venue on Saturday rather than on
> > > Sunday.   Please bear in
> > > >>> mind that the document selection process will take time,
> > > and set your authors'
> > > >>> expectations appropriately.
> > > >>>
> > > >>> We will arrange for authors who wish to attend and who
> > > are selected
> > > >>> to receive invitations, so that they can justify the
> > > early arrival
> > > >>> to their management if necessary.
> > > >>>
> > > >>> Thanks!
> > > >>
> > > >
> > > >
> > >
> > >
> =

From michael.scharf@alcatel-lucent.com  Tue Jan 21 02:45:53 2014
Return-Path: <michael.scharf@alcatel-lucent.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D95361A00A2 for <wgchairs@ietfa.amsl.com>; Tue, 21 Jan 2014 02:45:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.9
X-Spam-Level: 
X-Spam-Status: No, score=-8.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_INVITATION=-2, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AFmkwJtpeZN8 for <wgchairs@ietfa.amsl.com>; Tue, 21 Jan 2014 02:45:50 -0800 (PST)
Received: from hoemail2.alcatel.com (hoemail2.alcatel.com [192.160.6.149]) by ietfa.amsl.com (Postfix) with ESMTP id 5CC451A0050 for <wgchairs@ietf.org>; Tue, 21 Jan 2014 02:45:50 -0800 (PST)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by hoemail2.alcatel.com (8.13.8/IER-o) with ESMTP id s0LAjk3H010526 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 21 Jan 2014 04:45:48 -0600 (CST)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id s0LAjgrN009728 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 21 Jan 2014 11:45:46 +0100
Received: from FR712WXCHMBA15.zeu.alcatel-lucent.com ([169.254.7.112]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.02.0247.003; Tue, 21 Jan 2014 11:45:45 +0100
From: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>, "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, "wgchairs@ietf.org" <wgchairs@ietf.org>
Subject: RE: Document language editing session in London
Thread-Topic: Document language editing session in London
Thread-Index: AQHPEzDJKT6KI8m6NEOuWqwWykLd5JqJuzGAgALsp4CAAQjxgIAAuEaAgABH2wCAAFIcwA==
Date: Tue, 21 Jan 2014 10:45:45 +0000
Message-ID: <655C07320163294895BBADA28372AF5D191DF8@FR712WXCHMBA15.zeu.alcatel-lucent.com>
References: <D6557C43-1445-4660-804D-BD17ED9DD486@nominum.com> <B0D29E0424F2DE47A0B36779EC66677925867D07@nkgeml501-mbs.china.huawei.com> <9ADCA470-8200-4C9E-A728-FD69D155A569@wjcerveny.com> <52DD401B.7000106@alum.mit.edu> <949EF20990823C4C85C18D59AA11AD8B11E9C3@FR712WXCHMBA11.zeu.alcatel-lucent.com> <E045AECD98228444A58C61C200AE1BD8416A2C00@xmb-rcd-x01.cisco.com>
In-Reply-To: <E045AECD98228444A58C61C200AE1BD8416A2C00@xmb-rcd-x01.cisco.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.41]
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.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 10:45:54 -0000

> -----Original Message-----
> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of Pascal
> Thubert (pthubert)
> Sent: Tuesday, January 21, 2014 7:43 AM
> To: DRAGE, Keith (Keith); Paul Kyzivat; wgchairs@ietf.org
> Subject: RE: Document language editing session in London
>=20
> As a non-Native chair, Keith, I'm unclear how I can accomplish that.
> Maybe the WG could have a more official position for a secretary who
> would have to be fluent in English?
> Would that be a slippery slope?

As a non-native speaker, I am not sure if we could indeed find native speak=
ers inside the WG who would be really eager to do this kind of work.

My observation is that usually some native speakers are willing to help out=
 (e.g., during WGLC), but on a voluntary basis only, i.e., if they happen t=
o have spare cycles.

Michael


>=20
> Cheers,
>=20
> Pascal
>=20
> > -----Original Message-----
> > From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of DRAGE,
> > Keith (Keith)
> > Sent: mardi 21 janvier 2014 03:26
> > To: Paul Kyzivat; wgchairs@ietf.org
> > Subject: RE: Document language editing session in London
> >
> > Conversely, at the stage of IESG approval the Ads should not be
> worrying with
> > this at all.
> >
> > Given that the document is meant to be complete technically before
> WGLC, at
> > that point we should be able yo ascertain that:
> > -	the document is clearly written
> > -	that all requirements are clear
> > The WGLC will obviously polish this, but it is really the
> responsibility of the WG
> > chair to ensure this.
> >
> > Keith
> >
> > > -----Original Message-----
> > > From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of Paul
> > > Kyzivat
> > > Sent: 20 January 2014 15:26
> > > To: wgchairs@ietf.org
> > > Subject: Re: Document language editing session in London
> > >
> > > I have a very different view of this from Bill.
> > >
> > > IMO, especially early in the process, what is important is to
> discuss
> > > the *concepts* in a draft, not the language usage.
> > > This is true whether the author is just a grammatically inept
> native
> > > English speaker/writer, or if the author doesn't have English as
> his
> > > native language.
> > >
> > > I find that documents written by many non-native English writers
> have
> > > usage that is "unusual" for natives, but in general it is still
> > > perfectly understandable. I find it easier to just "let it be"
> until
> > > the document is quite mature and the discussion of basics is over
> and
> > > it is time for polishing.
> > >
> > > Discussing language style and grammar in the midst of technical
> > > discussions is very distracting.
> > >
> > > 	Thanks,
> > > 	Paul
> > >
> > > On 1/19/14 6:38 PM, Bill Cerveny wrote:
> > > > [My first rant as a WG chair. I first wrote the rant, then took
> out
> > > > maybe 2/3rds of what I wrote :-) ]
> > > >
> > > > Having documents cleaned up grammatically as early as
> > > possible is very important and will result in better technical
> > > discussions, better (final) documents and a faster document
> turnaround
> > > from submission to publication.
> > > >
> > > > Last year my daughter, a recent college graduate in
> > > English, told me she aspired to be a technical writer, at which
> time I
> > > told her, "Gee, how'd you like to get experience reviewing
> technical
> > > documents?" I recruited her to review WG documents primarily from a
> > > grammatical, non-technical perspective. She was successful at
> > > providing constructive grammatical feedback to WG draft authors.
> > > >
> > > > Having worked with my daughter in in helping her get up to
> > > speed in reviewing IETF documents, it seems there are challenges a
> > > volunteer reviewer faces:
> > > > 1) There doesn't appear to be a clear, concise web page new
> > > volunteer reviewers can use as a starting point.
> > > > 2) How does one determine which documents are fair game for
> > > document review?  In theory, any document submitted to the IETF
> should
> > > be open for grammatical review the moment it is submitted, but
> given
> > > limited resources, from a WG perspective, we encourage reviewing WG
> > > documents first.
> > > > 3) How should a reviewer submit proposed changes? There
> > > isn't a consistent IETF recommendation for how to submit review
> > > comments/changes (such as format and/or tools) and it seems a
> > > consistent recommendation would be useful.
> > > > 4) There isn't any mechanism for encouraging (or even
> > > rewarding) reviewers who may not be intimately interested in the
> > > technical aspects of the documents. I sent my daughter an
> > > IETF88 T-shirt, but other than a thanks from the authors and/or the
> WG
> > > chairs, there isn't much that is done to encourage or reward the
> > > reviewers.
> > > >
> > > > At the risk of sounding non-IETFish here (we're mostly all
> > > "volunteers"), in a perfect world, it would make sense for authors
> to
> > > pay a document reviewer to review a document before it is even
> > > submitted to the IETF. The time involved with reviewing documents
> for
> > > grammatical correctness can be non-trivial. Certainly, there is an
> > > implied financial cost for the time that a volunteer reviewer
> spends
> > > to review a document. If the author is serious about submitting a
> > > concise technical document and having a concise technical document
> > > published, it would behoove the author to ensure that the document
> is
> > > grammatically correct before it is submitted to engineers for
> > > technical scrutiny. In this perfect world, there might be some sort
> of
> > > central list of people willing to review documents, although at a
> > > larger organization, it should be possible for the author to ask
> > > someone at the organization to review the document.
> > > >
> > > > Bill Cerveny
> > > >
> > > > On Jan 17, 2014, at 9:58 PM, Zongning <zongning@huawei.com>
> wrote:
> > > >
> > > >> Dear Ted, and all,
> > > >>
> > > >> As a non-native English speaker, I agree that this is a
> > > good practice to improve the quality of IETF I-Ds.
> > > >>
> > > >> I also share the opinion of Thomas that more volunteers
> > > should be called to help the whole community. Probably the similar
> > > practice could be conducted in a more "distributed"
> > > way, e.g., in WG level, led by WG co-chairs.
> > > >>
> > > >> Anyway, I will plan to submit I-D to this session in London,
> learn
> > > >> something important, then talk to my group, especially as a
> > > >> non-native English WG co-chair. :-)
> > > >>
> > > >> Thanks.
> > > >>
> > > >> -Ning
> > > >>
> > > >>> -----Original Message-----
> > > >>> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On
> > > Behalf Of Ted
> > > >>> Lemon
> > > >>> Sent: Friday, January 17, 2014 11:04 AM
> > > >>> To: wgchairs@ietf.org Chairs
> > > >>> Cc: Heather Flanagan (RFC Series Editor)
> > > >>> Subject: Document language editing session in London
> > > >>>
> > > >>> Dear WG Chairs:
> > > >>>
> > > >>> The IESG has decided to repeat the experiment that we
> > > tried in Berlin at the
> > > >>> upcoming London IETF meeting.   We would like to invite
> > > ten document
> > > >>> authors to a language editing session in London on the
> > > Saturday prior to the
> > > >>> IETF meeting.   The goal of this editing session will be
> > > for two area directors,
> > > >>> me and Joel Jaeggli, to each sit with a group of five
> > > document editors and work
> > > >>> on each editors' document for 30 minutes in a group
> > > setting.   Benoit Claise
> > > >>> has also offered to help if there are any French-speaking
> authors
> > > >>> who would like to participate.
> > > >>>
> > > >>> The plan for this work is to do two things: first, to review
> the
> > > >>> documents, and secondly, for the participants to have the
> > > opportunity to work with Joel or with
> > > >>> me to improve the quality of their documents.   The goal
> > > is specifically for
> > > >>> non-native english speakers who have documents that the working
> > > >>> group considers important, but which are felt to need
> > > help with english language
> > > >>> editing.   It is important that the authors _want_ to get
> > > help-that they
> > > >>> recognize that they could use help and that they are
> comfortable
> > > >>> getting that help in a small group setting.
> > > >>>
> > > >>> What the meeting will look like is that there will be one or
> two
> > > >>> tables in a meeting room; I will be at one table with
> > > five authors and a representative
> > > >>> from the RFC Editor.   Joel will be at a separate table,
> > > with the same
> > > >>> arrangement.   If there aren't enough authors, we may do
> > > a single table, as
> > > >>> we did in Berlin.
> > > >>>
> > > >>> Each of us will have briefly reviewed the five documents prior
> to
> > > >>> the meeting, and we expect that the authors will be
> > > familiar with each others' documents as
> > > >>> well.   For thirty minutes per document, we will sit with
> > > the author and go
> > > >>> over the document, offering comments and suggestions and
> > > getting feedback
> > > >>> from the author.   The other authors will follow this.
> > > Then we will move on to
> > > >>> the next author.   Joel will be doing the same thing at
> > > the other table.   The
> > > >>> RFC Editor will be observing and offering advice on
> > > request, or if
> > > >>> they can't resist, but the main goal is to take advantage
> > > of the technical editorial
> > > >>> expertise of the two ADs for this experiment.   At the
> > > end of the editing
> > > >>> session, we will have a half hour session where we talk
> > > about what
> > > >>> went well, if anything, and what went wrong, if anything,
> > > and how we
> > > >>> might do it better next time.
> > > >>>
> > > >>> Neither Joel nor I are experts on teaching english to non-
> native
> > > >>> speakers, so we do not claim any specific knowledge other
> > > than that
> > > >>> we both have a keen interest in improving the quality of IETF
> > > >>> documents, a fair amount of experience in at least trying
> > > to do so,
> > > >>> and a desire to help our colleagues to accomplish their goals.
> > > >>>
> > > >>> Our desired outcome from this meeting is twofold: first,
> > > to help the
> > > >>> specific authors who attend; secondly, to learn how to
> > > help authors
> > > >>> in general: what frustrations they have in writing documents
> for
> > > >>> IETF, what stumbling blocks they trip over, and how we
> > > can help them.
> > > >>>
> > > >>> What we are asking working group chairs to do is think
> > > about whether there
> > > >>> are documents in their working group that could use this
> > > sort of help.   If you
> > > >>> believe there are, please contact the authors of those
> > > documents and
> > > >>> ask them in a non-pushy way whether they would like to
> > > participate in this experiment.
> > > >>> Please let us know if any of your authors are interested
> > > in this.   If you have
> > > >>> more than one document that you'd like worked on, please
> > > tell us which one is
> > > >>> most important to you.   We will have to do a triage
> > > process unless the
> > > >>> response to this call for participants is tiny, so it's
> > > likely that we will only take
> > > >>> the document you think is more important.   If we get a
> > > really good response,
> > > >>> we won't be able to take documents from every working group
> that
> > > >>> responds; please don't take this as a criticism if your
> > > document isn't chosen.
> > > >>>
> > > >>> If you think this is a good idea and want to take
> > > advantage of it,
> > > >>> please contact your authors as soon as possible, so that
> > > they can make travel plans that allow
> > > >>> them to get to the venue on Saturday rather than on
> > > Sunday.   Please bear in
> > > >>> mind that the document selection process will take time,
> > > and set your authors'
> > > >>> expectations appropriately.
> > > >>>
> > > >>> We will arrange for authors who wish to attend and who
> > > are selected
> > > >>> to receive invitations, so that they can justify the
> > > early arrival
> > > >>> to their management if necessary.
> > > >>>
> > > >>> Thanks!
> > > >>
> > > >
> > > >
> > >
> > >

From narten@us.ibm.com  Tue Jan 21 07:53:11 2014
Return-Path: <narten@us.ibm.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B8B61A036A for <wgchairs@ietfa.amsl.com>; Tue, 21 Jan 2014 07:53:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.436
X-Spam-Level: 
X-Spam-Status: No, score=-7.436 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sB8YkB1gw0SP for <wgchairs@ietfa.amsl.com>; Tue, 21 Jan 2014 07:53:10 -0800 (PST)
Received: from e39.co.us.ibm.com (e39.co.us.ibm.com [32.97.110.160]) by ietfa.amsl.com (Postfix) with ESMTP id 4A6791A0366 for <wgchairs@ietf.org>; Tue, 21 Jan 2014 07:53:08 -0800 (PST)
Received: from /spool/local by e39.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <wgchairs@ietf.org> from <narten@us.ibm.com>; Tue, 21 Jan 2014 08:53:08 -0700
Received: from d01dlp03.pok.ibm.com (9.56.250.168) by e39.co.us.ibm.com (192.168.1.139) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Tue, 21 Jan 2014 08:53:05 -0700
Received: from b01cxnp23033.gho.pok.ibm.com (b01cxnp23033.gho.pok.ibm.com [9.57.198.28]) by d01dlp03.pok.ibm.com (Postfix) with ESMTP id 7E22BC90026 for <wgchairs@ietf.org>; Tue, 21 Jan 2014 10:53:02 -0500 (EST)
Received: from d01av02.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by b01cxnp23033.gho.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id s0LFr4ic63045680 for <wgchairs@ietf.org>; Tue, 21 Jan 2014 15:53:04 GMT
Received: from d01av02.pok.ibm.com (localhost [127.0.0.1]) by d01av02.pok.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id s0LFr43m031212 for <wgchairs@ietf.org>; Tue, 21 Jan 2014 10:53:04 -0500
Received: from cichlid.raleigh.ibm.com (sig-9-76-156-183.mts.ibm.com [9.76.156.183]) by d01av02.pok.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id s0LFr2iX031089 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 21 Jan 2014 10:53:03 -0500
Received: from cichlid.raleigh.ibm.com.us.ibm.com (localhost [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id s0LFr1Kj001251; Tue, 21 Jan 2014 10:53:01 -0500
Date: Tue, 21 Jan 2014 10:53:01 -0500
Message-ID: <m3zjmppc0y.wl%narten@us.ibm.com>
From: Thomas Narten <narten@us.ibm.com>
To: Bill Cerveny <bill@wjcerveny.com>
Subject: Re: [BOFChairs] Document language editing session in London
In-Reply-To: <9ADCA470-8200-4C9E-A728-FD69D155A569@wjcerveny.com>
References: <D6557C43-1445-4660-804D-BD17ED9DD486@nominum.com> <B0D29E0424F2DE47A0B36779EC66677925867D07@nkgeml501-mbs.china.huawei.com> <9ADCA470-8200-4C9E-A728-FD69D155A569@wjcerveny.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.8 EasyPG/1.0.0 Emacs/23.1 (x86_64-redhat-linux-gnu) MULE/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 14012115-9332-0000-0000-000002D5E7A0
Cc: "wgchairs@ietf.org Chairs" <wgchairs@ietf.org>, "Heather Flanagan \(RFC Series Editor\)" <rse@rfc-editor.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 15:53:11 -0000

My larger point about all this is:

1) Per my first message, the ADs shouldn't be sitting down with
authors to teach them how to write. It doesn't scale and I have a hard
time seeing it address the real problem in a meaningful way. If that
were part of a larger plan, maybe it would make sense, but I don't
recall discussion of a larger plan.

2) The problem of poor writing is big and hard. If we were seriously
interested in fixing it, my usual recommendation is to create a design
team of sorts (formal or informal) that looks at the bigger picture
and thinks through it in more detail - and then has the output of the
group reviewed by others. I.e, having a clear problem statement, clear
goals, and an execution strategy, etc. And an important thing here is
to have a real plan that folk think might actually help the overall
problem. Otherwise, the community ends up making poor use of our
(limited) cycles.

For example, what probably has to happen with any document that
suffers from poor writing is pair the existing authors with a new
author (that has the required skills). But that raises authorship
issues... But the idea that you can do a one-off review to fix writing
issues and expecting the existing authors to continue to edit the
document without continuing to make repeat mistakes seems naive.

For me, I absolutely hate reviewing other peoples documents for basic
english stuff. It takes 3 times as long to type up such a review as it
does to just make the editing changes in place. Not a great use of
time, especially if it doesn't fix the problem going forward.

Thomas


From pkyzivat@alum.mit.edu  Tue Jan 21 07:55:47 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFDE01A018B for <wgchairs@ietfa.amsl.com>; Tue, 21 Jan 2014 07:55:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pCe0P9VhkyOx for <wgchairs@ietfa.amsl.com>; Tue, 21 Jan 2014 07:55:46 -0800 (PST)
Received: from qmta08.westchester.pa.mail.comcast.net (qmta08.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:80]) by ietfa.amsl.com (Postfix) with ESMTP id CEE5A1A0368 for <wgchairs@ietf.org>; Tue, 21 Jan 2014 07:55:45 -0800 (PST)
Received: from omta18.westchester.pa.mail.comcast.net ([76.96.62.90]) by qmta08.westchester.pa.mail.comcast.net with comcast id GduG1n0011wpRvQ58fvlMP; Tue, 21 Jan 2014 15:55:45 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta18.westchester.pa.mail.comcast.net with comcast id Gfvl1n00Q3ZTu2S3efvlc0; Tue, 21 Jan 2014 15:55:45 +0000
Message-ID: <52DE9881.4010901@alum.mit.edu>
Date: Tue, 21 Jan 2014 10:55:45 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: [BOFChairs] Document language editing session in London
References: <D6557C43-1445-4660-804D-BD17ED9DD486@nominum.com> <B0D29E0424F2DE47A0B36779EC66677925867D07@nkgeml501-mbs.china.huawei.com> <9ADCA470-8200-4C9E-A728-FD69D155A569@wjcerveny.com> <m3zjmppc0y.wl%narten@us.ibm.com>
In-Reply-To: <m3zjmppc0y.wl%narten@us.ibm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1390319745; bh=jD6VMGXjlmw0zednO5RyAYcmCqEhLJTgyZy29fKUPqk=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=qbljBjdfhSfQvWRbMxao2Ei0OBeCelv+4WaZXu0nky2RalxLvXGEtEF78LnGzgTYu S/hLdkeKP6OxvjHHTgqNfhRFZ0Ll0ffx4CfWN9xqFxpU2NJpKIXvvLkHynm+nB/Eiy 89t+zgTIiaKKKWo6CYqME3E/tWfX+7g4GizOgg1lY4OEsqdJ4+u7gWmrlh0g+n2Df8 U6x4g0pcswKhBqG14zv+GYjDlV8OR4e20X1v4fWiypT2cm/iWckN46zmLaxBNjVIOG 0ndk6W44Yv5dc1G6ZgTB6PO4CFnd0TaPzJZ5Q6jn8OLXqQz7SbIHzk6UBa3gYXfw1u Fp/ojd9ZUiA0g==
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 15:55:48 -0000

Well said!
+1

On 1/21/14 10:53 AM, Thomas Narten wrote:
> My larger point about all this is:
>
> 1) Per my first message, the ADs shouldn't be sitting down with
> authors to teach them how to write. It doesn't scale and I have a hard
> time seeing it address the real problem in a meaningful way. If that
> were part of a larger plan, maybe it would make sense, but I don't
> recall discussion of a larger plan.
>
> 2) The problem of poor writing is big and hard. If we were seriously
> interested in fixing it, my usual recommendation is to create a design
> team of sorts (formal or informal) that looks at the bigger picture
> and thinks through it in more detail - and then has the output of the
> group reviewed by others. I.e, having a clear problem statement, clear
> goals, and an execution strategy, etc. And an important thing here is
> to have a real plan that folk think might actually help the overall
> problem. Otherwise, the community ends up making poor use of our
> (limited) cycles.
>
> For example, what probably has to happen with any document that
> suffers from poor writing is pair the existing authors with a new
> author (that has the required skills). But that raises authorship
> issues... But the idea that you can do a one-off review to fix writing
> issues and expecting the existing authors to continue to edit the
> document without continuing to make repeat mistakes seems naive.
>
> For me, I absolutely hate reviewing other peoples documents for basic
> english stuff. It takes 3 times as long to type up such a review as it
> does to just make the editing changes in place. Not a great use of
> time, especially if it doesn't fix the problem going forward.
>
> Thomas
>
>


From chair@ietf.org  Tue Jan 21 08:18:29 2014
Return-Path: <chair@ietf.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F7051A03D6 for <wgchairs@ietfa.amsl.com>; Tue, 21 Jan 2014 08:18:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qg2SNfcErfiy for <wgchairs@ietfa.amsl.com>; Tue, 21 Jan 2014 08:18:26 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.21]) by ietfa.amsl.com (Postfix) with ESMTP id EA69F1A03B8 for <wgchairs@ietf.org>; Tue, 21 Jan 2014 08:18:18 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id 38FBDA72A6; Tue, 21 Jan 2014 08:18:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c9a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fMbmlZPOfXKZ; Tue, 21 Jan 2014 08:18:06 -0800 (PST)
Received: from [IPv6:2a00:1d50:2:101:fce8:2357:766:d053] (unknown [IPv6:2a00:1d50:2:101:fce8:2357:766:d053]) by c9a.amsl.com (Postfix) with ESMTPSA id 898FEA60EF; Tue, 21 Jan 2014 08:18:05 -0800 (PST)
From: IETF Chair <chair@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Web-based email list archive search and browsing tool ready for use
Date: Tue, 21 Jan 2014 18:18:16 +0200
Message-Id: <CF21F08E-DA1F-457D-B4C4-80F27FAAC1F8@ietf.org>
To: Working Group Chairs <wgchairs@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
X-Mailer: Apple Mail (2.1510)
Cc: Robert Sparks <rjsparks@nostrum.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 16:18:29 -0000

Chairs:

The tool realizing the requirements we developed in RFC 6778 is ready =
for your use. We are announcing it to the working group chairs first to =
bring the load onto this new service incrementally. We will send an =
announcement to the entire community later this week.

You'll find the service at https://mailarchive.ietf.org/

If you choose to log in, use your datatracker credentials.

If you encounter problems or have suggestions for future improvements, =
please file a report using =
http://trac.tools.ietf.org/tools/ietfdb/newticket=20

If you find spam, please send a request to remove it including a link to =
the message to action@ietf.org.

We are still working towards providing IMAP access to the archives. That =
is not part of the tool at this time. The old archives will continue to =
receive new messages and will be available in their current locations =
until further notice.

Early testers have reported this tool to be very useful. I hope you also =
find it to be so.

Jari


From sob@harvard.edu  Tue Jan 21 08:27:14 2014
Return-Path: <sob@harvard.edu>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EF2A1A0153; Tue, 21 Jan 2014 08:27:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.135
X-Spam-Level: 
X-Spam-Status: No, score=-3.135 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uOswLyEoO5bO; Tue, 21 Jan 2014 08:27:12 -0800 (PST)
Received: from ackroyd.harvard.edu (ackroyd.harvard.edu [128.103.208.29]) by ietfa.amsl.com (Postfix) with ESMTP id 3F55A1A016D; Tue, 21 Jan 2014 08:27:12 -0800 (PST)
Received: from ENTWEDGE0000004.university.harvard.edu (entwedge0000004.university.harvard.edu [10.35.202.51]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ackroyd.harvard.edu (Postfix) with ESMTP id 07802E8F7B; Tue, 21 Jan 2014 11:27:12 -0500 (EST)
Received: from ENTWHUBT0000003.university.harvard.edu (192.168.36.24) by entwedge0000004.university.harvard.edu (10.35.202.51) with Microsoft SMTP Server (TLS) id 14.3.146.0; Tue, 21 Jan 2014 11:27:02 -0500
Received: from ENTWEXMB0000008.university.harvard.edu ([169.254.1.46]) by entwhubt0000003.university.harvard.edu ([192.168.36.24]) with mapi id 14.03.0146.000; Tue, 21 Jan 2014 11:27:11 -0500
From: "Bradner, Scott" <sob@harvard.edu>
To: IETF Chair <chair@ietf.org>
Subject: Re: Web-based email list archive search and browsing tool ready for use
Thread-Topic: Web-based email list archive search and browsing tool ready for use
Thread-Index: AQHPFsRuk/mqlpVHsUqHnUOv7EK6jpqPsYwA
Date: Tue, 21 Jan 2014 16:27:10 +0000
Message-ID: <935A6EDB-52BC-4E01-B726-E2C6E5BA99F4@harvard.edu>
References: <CF21F08E-DA1F-457D-B4C4-80F27FAAC1F8@ietf.org>
In-Reply-To: <CF21F08E-DA1F-457D-B4C4-80F27FAAC1F8@ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [128.103.229.199]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <20CB96D69A8E5743AE8776CB8D96395A@Exchange.university.harvard.edu>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Working Group Chairs <wgchairs@ietf.org>, Robert Sparks <rjsparks@nostrum.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 16:27:14 -0000

seems slow even with out many people using it

how far back does the database go?  (I did the normal =91search-for-myself=
=92 and only found postings since July 1996)

Scott


On Jan 21, 2014, at 11:18 AM, IETF Chair <chair@ietf.org> wrote:

> Chairs:
>=20
> The tool realizing the requirements we developed in RFC 6778 is ready for=
 your use. We are announcing it to the working group chairs first to bring =
the load onto this new service incrementally. We will send an announcement =
to the entire community later this week.
>=20
> You'll find the service at https://mailarchive.ietf.org/
>=20
> If you choose to log in, use your datatracker credentials.
>=20
> If you encounter problems or have suggestions for future improvements, pl=
ease file a report using http://trac.tools.ietf.org/tools/ietfdb/newticket=
=20
>=20
> If you find spam, please send a request to remove it including a link to =
the message to action@ietf.org.
>=20
> We are still working towards providing IMAP access to the archives. That =
is not part of the tool at this time. The old archives will continue to rec=
eive new messages and will be available in their current locations until fu=
rther notice.
>=20
> Early testers have reported this tool to be very useful. I hope you also =
find it to be so.
>=20
> Jari
>=20


From sob@harvard.edu  Tue Jan 21 08:32:43 2014
Return-Path: <sob@harvard.edu>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 731FE1A0359; Tue, 21 Jan 2014 08:32:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.135
X-Spam-Level: 
X-Spam-Status: No, score=-3.135 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7vY57BijtoP2; Tue, 21 Jan 2014 08:32:42 -0800 (PST)
Received: from ackroyd.harvard.edu (ackroyd.harvard.edu [128.103.208.29]) by ietfa.amsl.com (Postfix) with ESMTP id D905E1A0157; Tue, 21 Jan 2014 08:32:41 -0800 (PST)
Received: from ENTWEDGE0000001.university.harvard.edu (entwedge0000001.university.harvard.edu [10.35.2.152]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ackroyd.harvard.edu (Postfix) with ESMTP id A7161E9605; Tue, 21 Jan 2014 11:32:41 -0500 (EST)
Received: from ENTWHUBT0000005.university.harvard.edu (10.32.208.51) by ENTWEDGE0000001.university.harvard.edu (10.35.2.152) with Microsoft SMTP Server (TLS) id 14.3.146.0; Tue, 21 Jan 2014 11:32:17 -0500
Received: from ENTWEXMB0000008.university.harvard.edu ([169.254.1.46]) by ENTWHUBT0000005.university.harvard.edu ([10.32.208.51]) with mapi id 14.03.0146.000; Tue, 21 Jan 2014 11:32:41 -0500
From: "Bradner, Scott" <sob@harvard.edu>
To: IETF Chair <chair@ietf.org>
Subject: Re: Web-based email list archive search and browsing tool ready for use
Thread-Topic: Web-based email list archive search and browsing tool ready for use
Thread-Index: AQHPFsRuk/mqlpVHsUqHnUOv7EK6jpqPsxYA
Date: Tue, 21 Jan 2014 16:32:40 +0000
Message-ID: <0FB6C935-5BA0-4F74-B960-5B6BF3474848@harvard.edu>
References: <CF21F08E-DA1F-457D-B4C4-80F27FAAC1F8@ietf.org>
In-Reply-To: <CF21F08E-DA1F-457D-B4C4-80F27FAAC1F8@ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [128.103.229.199]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <A05561D537B2B249B7D068EDD379DCA6@Exchange.university.harvard.edu>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Working Group Chairs <wgchairs@ietf.org>, Robert Sparks <rjsparks@nostrum.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 16:32:43 -0000

also seems to be quite incomplete - I find a number of responses to message=
s I sent on various lists but
do not find the messages themselves

Scott


On Jan 21, 2014, at 11:18 AM, IETF Chair <chair@ietf.org> wrote:

> Chairs:
>=20
> The tool realizing the requirements we developed in RFC 6778 is ready for=
 your use. We are announcing it to the working group chairs first to bring =
the load onto this new service incrementally. We will send an announcement =
to the entire community later this week.
>=20
> You'll find the service at https://mailarchive.ietf.org/
>=20
> If you choose to log in, use your datatracker credentials.
>=20
> If you encounter problems or have suggestions for future improvements, pl=
ease file a report using http://trac.tools.ietf.org/tools/ietfdb/newticket=
=20
>=20
> If you find spam, please send a request to remove it including a link to =
the message to action@ietf.org.
>=20
> We are still working towards providing IMAP access to the archives. That =
is not part of the tool at this time. The old archives will continue to rec=
eive new messages and will be available in their current locations until fu=
rther notice.
>=20
> Early testers have reported this tool to be very useful. I hope you also =
find it to be so.
>=20
> Jari
>=20


From rjsparks@nostrum.com  Tue Jan 21 08:35:03 2014
Return-Path: <rjsparks@nostrum.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 893CF1A01A5 for <wgchairs@ietfa.amsl.com>; Tue, 21 Jan 2014 08:35:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.036
X-Spam-Level: 
X-Spam-Status: No, score=-1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vjhlAxlefv6Q for <wgchairs@ietfa.amsl.com>; Tue, 21 Jan 2014 08:35:02 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 1CD1E1A0194 for <wgchairs@ietf.org>; Tue, 21 Jan 2014 08:35:02 -0800 (PST)
Received: from unnumerable.local (pool-173-71-10-88.dllstx.fios.verizon.net [173.71.10.88]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id s0LGZ1SP016872 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK) for <wgchairs@ietf.org>; Tue, 21 Jan 2014 10:35:01 -0600 (CST) (envelope-from rjsparks@nostrum.com)
Message-ID: <52DEA1B4.2020608@nostrum.com>
Date: Tue, 21 Jan 2014 10:35:00 -0600
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: Web-based email list archive search and browsing tool ready for use
References: <CF21F08E-DA1F-457D-B4C4-80F27FAAC1F8@ietf.org> <0FB6C935-5BA0-4F74-B960-5B6BF3474848@harvard.edu>
In-Reply-To: <0FB6C935-5BA0-4F74-B960-5B6BF3474848@harvard.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.71.10.88 is authenticated by a trusted mechanism)
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 16:35:03 -0000

(removing IETF chair from the recipient list)

Thanks Scott -

These go as far back as the existing archives go. If you can find a 
message in either the mbox files or the mhonarc archives that's not 
here, please send a reference to it and we'll see why it's not here.

On 1/21/14, 10:32 AM, Bradner, Scott wrote:
> also seems to be quite incomplete - I find a number of responses to messages I sent on various lists but
> do not find the messages themselves
>
> Scott
>
>
> On Jan 21, 2014, at 11:18 AM, IETF Chair <chair@ietf.org> wrote:
>
>> Chairs:
>>
>> The tool realizing the requirements we developed in RFC 6778 is ready for your use. We are announcing it to the working group chairs first to bring the load onto this new service incrementally. We will send an announcement to the entire community later this week.
>>
>> You'll find the service at https://mailarchive.ietf.org/
>>
>> If you choose to log in, use your datatracker credentials.
>>
>> If you encounter problems or have suggestions for future improvements, please file a report using http://trac.tools.ietf.org/tools/ietfdb/newticket
>>
>> If you find spam, please send a request to remove it including a link to the message to action@ietf.org.
>>
>> We are still working towards providing IMAP access to the archives. That is not part of the tool at this time. The old archives will continue to receive new messages and will be available in their current locations until further notice.
>>
>> Early testers have reported this tool to be very useful. I hope you also find it to be so.
>>
>> Jari
>>


From rjsparks@nostrum.com  Tue Jan 21 08:37:07 2014
Return-Path: <rjsparks@nostrum.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED23D1A02E7 for <wgchairs@ietfa.amsl.com>; Tue, 21 Jan 2014 08:37:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.036
X-Spam-Level: 
X-Spam-Status: No, score=-1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wZ1XPzfYCRBn for <wgchairs@ietfa.amsl.com>; Tue, 21 Jan 2014 08:37:06 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id D7EF81A01C8 for <wgchairs@ietf.org>; Tue, 21 Jan 2014 08:37:05 -0800 (PST)
Received: from unnumerable.local (pool-173-71-10-88.dllstx.fios.verizon.net [173.71.10.88]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id s0LGb5Gj016960 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK) for <wgchairs@ietf.org>; Tue, 21 Jan 2014 10:37:05 -0600 (CST) (envelope-from rjsparks@nostrum.com)
Message-ID: <52DEA230.2040909@nostrum.com>
Date: Tue, 21 Jan 2014 10:37:04 -0600
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: Web-based email list archive search and browsing tool ready for use
References: <CF21F08E-DA1F-457D-B4C4-80F27FAAC1F8@ietf.org>
In-Reply-To: <CF21F08E-DA1F-457D-B4C4-80F27FAAC1F8@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.71.10.88 is authenticated by a trusted mechanism)
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 16:37:07 -0000

It looks like newer messages haven't been imported in the last few days 
(the most recent I'm seeing on several lists is from Jan 14).
We'll find out why and get this up to date.

RjS

On 1/21/14, 10:18 AM, IETF Chair wrote:
> Chairs:
>
> The tool realizing the requirements we developed in RFC 6778 is ready for your use. We are announcing it to the working group chairs first to bring the load onto this new service incrementally. We will send an announcement to the entire community later this week.
>
> You'll find the service at https://mailarchive.ietf.org/
>
> If you choose to log in, use your datatracker credentials.
>
> If you encounter problems or have suggestions for future improvements, please file a report using http://trac.tools.ietf.org/tools/ietfdb/newticket
>
> If you find spam, please send a request to remove it including a link to the message to action@ietf.org.
>
> We are still working towards providing IMAP access to the archives. That is not part of the tool at this time. The old archives will continue to receive new messages and will be available in their current locations until further notice.
>
> Early testers have reported this tool to be very useful. I hope you also find it to be so.
>
> Jari
>


From lberger@labn.net  Tue Jan 21 09:08:57 2014
Return-Path: <lberger@labn.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CADF1A03D5 for <wgchairs@ietfa.amsl.com>; Tue, 21 Jan 2014 09:08:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.667
X-Spam-Level: 
X-Spam-Status: No, score=-1.667 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X25MLlovsXaY for <wgchairs@ietfa.amsl.com>; Tue, 21 Jan 2014 09:08:55 -0800 (PST)
Received: from oproxy6-pub.mail.unifiedlayer.com (oproxy6-pub.mail.unifiedlayer.com [67.222.54.6]) by ietfa.amsl.com (Postfix) with SMTP id E634C1A03D4 for <wgchairs@ietf.org>; Tue, 21 Jan 2014 09:08:54 -0800 (PST)
Received: (qmail 32019 invoked by uid 0); 22 Jan 2014 00:08:52 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by oproxy6.mail.unifiedlayer.com with SMTP; 22 Jan 2014 00:08: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=tFloeaqVVyntbLWcGWchiJJpE/iLi+oQurnflr9MTys=;  b=I+luEEphUqxKmfKTNIYLmPQ/8+FxdqAuo4RUB0z35oGKIGnw5zF6VJ/a9JbkTNqKlMgWVhTyQSDCATOm2omCZOOo16hC6DC5lLSzBl6SuehfbisuJrJ6CWIdhq1zWorG;
Received: from box313.bluehost.com ([69.89.31.113]:46176 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.80) (envelope-from <lberger@labn.net>) id 1W5eoo-0000iO-Fc; Tue, 21 Jan 2014 10:08:54 -0700
Message-ID: <52DEA9A3.3080402@labn.net>
Date: Tue, 21 Jan 2014 12:08:51 -0500
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "Bradner, Scott" <sob@harvard.edu>
Subject: Re: Web-based email list archive search and browsing tool ready for use
References: <CF21F08E-DA1F-457D-B4C4-80F27FAAC1F8@ietf.org> <935A6EDB-52BC-4E01-B726-E2C6E5BA99F4@harvard.edu>
In-Reply-To: <935A6EDB-52BC-4E01-B726-E2C6E5BA99F4@harvard.edu>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Cc: Working Group Chairs <wgchairs@ietf.org>, Robert Sparks <rjsparks@nostrum.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 17:08:57 -0000

You had better luck then I did!

After clicking date to sort search results:

Server Error (500)

Lou

On 01/21/2014 11:27 AM, Bradner, Scott wrote:
> seems slow even with out many people using it
> 
> how far back does the database go?  (I did the normal ‘search-for-myself’ and only found postings since July 1996)
> 
> Scott
> 
> 
> On Jan 21, 2014, at 11:18 AM, IETF Chair <chair@ietf.org> wrote:
> 
>> Chairs:
>>
>> The tool realizing the requirements we developed in RFC 6778 is ready for your use. We are announcing it to the working group chairs first to bring the load onto this new service incrementally. We will send an announcement to the entire community later this week.
>>
>> You'll find the service at https://mailarchive.ietf.org/
>>
>> If you choose to log in, use your datatracker credentials.
>>
>> If you encounter problems or have suggestions for future improvements, please file a report using http://trac.tools.ietf.org/tools/ietfdb/newticket 
>>
>> If you find spam, please send a request to remove it including a link to the message to action@ietf.org.
>>
>> We are still working towards providing IMAP access to the archives. That is not part of the tool at this time. The old archives will continue to receive new messages and will be available in their current locations until further notice.
>>
>> Early testers have reported this tool to be very useful. I hope you also find it to be so.
>>
>> Jari
>>
> 
> 


From rjsparks@nostrum.com  Tue Jan 21 09:46:46 2014
Return-Path: <rjsparks@nostrum.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 247321A018E for <wgchairs@ietfa.amsl.com>; Tue, 21 Jan 2014 09:46:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.036
X-Spam-Level: 
X-Spam-Status: No, score=-1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FHgCsRFF2evG for <wgchairs@ietfa.amsl.com>; Tue, 21 Jan 2014 09:46:45 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id D898D1A01B4 for <wgchairs@ietf.org>; Tue, 21 Jan 2014 09:46:44 -0800 (PST)
Received: from unnumerable.local (pool-173-71-10-88.dllstx.fios.verizon.net [173.71.10.88]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id s0LHkibn019977 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK) for <wgchairs@ietf.org>; Tue, 21 Jan 2014 11:46:44 -0600 (CST) (envelope-from rjsparks@nostrum.com)
Message-ID: <52DEB283.3080803@nostrum.com>
Date: Tue, 21 Jan 2014 11:46:43 -0600
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: Web-based email list archive search and browsing tool ready for use
References: <CF21F08E-DA1F-457D-B4C4-80F27FAAC1F8@ietf.org> <935A6EDB-52BC-4E01-B726-E2C6E5BA99F4@harvard.edu> <52DEA9A3.3080402@labn.net>
In-Reply-To: <52DEA9A3.3080402@labn.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Received-SPF: pass (shaman.nostrum.com: 173.71.10.88 is authenticated by a trusted mechanism)
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 17:46:46 -0000

Hi Lou -

Is that repeatable? If so, can you send me the URL your browser is 
pointed to just before you hit that sort?

RjS

On 1/21/14, 11:08 AM, Lou Berger wrote:
> You had better luck then I did!
>
> After clicking date to sort search results:
>
> Server Error (500)
>
> Lou
>
> On 01/21/2014 11:27 AM, Bradner, Scott wrote:
>> seems slow even with out many people using it
>>
>> how far back does the database go?  (I did the normal ‘search-for-myself’ and only found postings since July 1996)
>>
>> Scott
>>
>>
>> On Jan 21, 2014, at 11:18 AM, IETF Chair <chair@ietf.org> wrote:
>>
>>> Chairs:
>>>
>>> The tool realizing the requirements we developed in RFC 6778 is ready for your use. We are announcing it to the working group chairs first to bring the load onto this new service incrementally. We will send an announcement to the entire community later this week.
>>>
>>> You'll find the service at https://mailarchive.ietf.org/
>>>
>>> If you choose to log in, use your datatracker credentials.
>>>
>>> If you encounter problems or have suggestions for future improvements, please file a report using http://trac.tools.ietf.org/tools/ietfdb/newticket
>>>
>>> If you find spam, please send a request to remove it including a link to the message to action@ietf.org.
>>>
>>> We are still working towards providing IMAP access to the archives. That is not part of the tool at this time. The old archives will continue to receive new messages and will be available in their current locations until further notice.
>>>
>>> Early testers have reported this tool to be very useful. I hope you also find it to be so.
>>>
>>> Jari
>>>
>>


From sob@harvard.edu  Tue Jan 21 10:12:06 2014
Return-Path: <sob@harvard.edu>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A872C1A0150 for <wgchairs@ietfa.amsl.com>; Tue, 21 Jan 2014 10:12:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.135
X-Spam-Level: 
X-Spam-Status: No, score=-3.135 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nHSJbOx10AER for <wgchairs@ietfa.amsl.com>; Tue, 21 Jan 2014 10:12:05 -0800 (PST)
Received: from ackroyd.harvard.edu (ackroyd.harvard.edu [128.103.208.29]) by ietfa.amsl.com (Postfix) with ESMTP id 4A16C1A011D for <wgchairs@ietf.org>; Tue, 21 Jan 2014 10:12:05 -0800 (PST)
Received: from ENTWEDGE0000003.university.harvard.edu (entwedge0000003.university.harvard.edu [10.35.202.50]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ackroyd.harvard.edu (Postfix) with ESMTP id 01DDEE946C; Tue, 21 Jan 2014 13:12:04 -0500 (EST)
Received: from ENTWHUBT0000005.university.harvard.edu (10.32.208.51) by entwedge0000003.university.harvard.edu (10.35.202.50) with Microsoft SMTP Server (TLS) id 14.3.146.0; Tue, 21 Jan 2014 13:11:54 -0500
Received: from ENTWEXMB0000008.university.harvard.edu ([169.254.1.46]) by ENTWHUBT0000005.university.harvard.edu ([10.32.208.51]) with mapi id 14.03.0146.000; Tue, 21 Jan 2014 13:12:03 -0500
From: "Bradner, Scott" <sob@harvard.edu>
To: Robert Sparks <rjsparks@nostrum.com>
Subject: Re: Web-based email list archive search and browsing tool ready for use
Thread-Topic: Web-based email list archive search and browsing tool ready for use
Thread-Index: AQHPFsRuk/mqlpVHsUqHnUOv7EK6jpqPtFAAgAAaiIA=
Date: Tue, 21 Jan 2014 18:12:02 +0000
Message-ID: <F16A7ACD-F848-458C-9060-7E3930923527@harvard.edu>
References: <CF21F08E-DA1F-457D-B4C4-80F27FAAC1F8@ietf.org> <52DEA230.2040909@nostrum.com>
In-Reply-To: <52DEA230.2040909@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [128.103.229.199]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <061355E31CBF6A4EB2A5AC74DC17231D@Exchange.university.harvard.edu>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Working Group Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 18:12:06 -0000

for whatever its worth, a grep through my archives of just the ITEF list (n=
ever mind the many other lists)
comes up with 25K hits (more than one per message in some cases) but the se=
arch tool only gets about 6.4K messages
across all lists=20

Scott



From rse@rfc-editor.org  Tue Jan 21 10:35:34 2014
Return-Path: <rse@rfc-editor.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7D121A016E for <wgchairs@ietfa.amsl.com>; Tue, 21 Jan 2014 10:35:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d1gQOIJWBD1A for <wgchairs@ietfa.amsl.com>; Tue, 21 Jan 2014 10:35:31 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.21]) by ietfa.amsl.com (Postfix) with ESMTP id 6CE561A0151 for <wgchairs@ietf.org>; Tue, 21 Jan 2014 10:35:31 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id 41A25A8F0D for <wgchairs@ietf.org>; Tue, 21 Jan 2014 10:35:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c9a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ne_jPB7_PcOx for <wgchairs@ietf.org>; Tue, 21 Jan 2014 10:35:18 -0800 (PST)
Received: from Heathers-MacBook-Pro.local (98-125-162-19.dyn.centurytel.net [98.125.162.19]) by c9a.amsl.com (Postfix) with ESMTPSA id 080F4A61FA for <wgchairs@ietf.org>; Tue, 21 Jan 2014 10:35:17 -0800 (PST)
Message-ID: <52DEBDF2.6080503@rfc-editor.org>
Date: Tue, 21 Jan 2014 10:35:30 -0800
From: "Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: 'Working Group Chairs' <wgchairs@ietf.org>
Subject: Collecting input on future xml2rfc vocabulary
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 21 Jan 2014 10:48:35 -0800
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 18:35:34 -0000

Hello WG Chairs,

I would like to enlist your assistance in getting the word out to active
authors about current efforts to update the xml2rfc vocabulary and DTD.
Some of the best input comes at the point when an author is trying to
create a draft and finds themselves wishing that xml2rfc had a
particular feature, or behaved in a different way.  Now is the best time
to collect that information, since the RFC Format Design Team is in the
process of recommending a variety of changes to support the new proposed
formats for RFCs.

Authors should send their suggestions to the rfc-interest@rfc-editor.org
mailing list, where they will be discussed and then captured by the
design team.  The archives of that list (available from
<http://www.rfc-editor.org/pipermail/rfc-interest/2014-January/thread.html>)
provide details on what has already been discussed.  The Design Team
wiki (read-only) has also captured some of the discussion and decisions
so far.  See:
<http://www.rfc-editor.org/rse/wiki/doku.php?id=design:xml-tags>.

Thank you for your help,
Heather Flanagan
RFC Series Editor

From jhaas@slice.pfrc.org  Tue Jan 21 10:57:58 2014
Return-Path: <jhaas@slice.pfrc.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA1AD1A018E for <wgchairs@ietfa.amsl.com>; Tue, 21 Jan 2014 10:57:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.103
X-Spam-Level: 
X-Spam-Status: No, score=-2.103 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dakb7YclHHK6 for <wgchairs@ietfa.amsl.com>; Tue, 21 Jan 2014 10:57:58 -0800 (PST)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id E5C7A1A0180 for <wgchairs@ietf.org>; Tue, 21 Jan 2014 10:57:57 -0800 (PST)
Received: by slice.pfrc.org (Postfix, from userid 1001) id C10E5C17E; Tue, 21 Jan 2014 13:57:57 -0500 (EST)
Date: Tue, 21 Jan 2014 13:57:57 -0500
From: Jeffrey Haas <jhaas@pfrc.org>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Subject: Re: Document language editing session in London
Message-ID: <20140121185757.GD4366@pfrc>
References: <D6557C43-1445-4660-804D-BD17ED9DD486@nominum.com> <B0D29E0424F2DE47A0B36779EC66677925867D07@nkgeml501-mbs.china.huawei.com> <9ADCA470-8200-4C9E-A728-FD69D155A569@wjcerveny.com> <13255.1390175631@sandelman.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <13255.1390175631@sandelman.ca>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: "wgchairs@ietf.org Chairs" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 18:57:59 -0000

On Sun, Jan 19, 2014 at 06:53:51PM -0500, Michael Richardson wrote:
>     > 4) There isn???t any mechanism for encouraging (or even rewarding)
>     > reviewers who may not be intimately interested in the technical aspects
>     > of the documents. I sent my daughter an IETF88 T-shirt, but other than
>     > a thanks from the authors and/or the WG chairs, there isn???t much that
>     > is done to encourage or reward the reviewers.
> 
> I just want to leave this part here.
> We have some significant incentive issues to work out.

I had sent a feature request to the IAOC folk to implement a "karma" system
in our tools.  

While certainly not as good as being taken out to dinner, it's something.

-- Jeff

From Bert.Greevenbosch@huawei.com  Tue Jan 21 16:47:01 2014
Return-Path: <Bert.Greevenbosch@huawei.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFE141A0233 for <wgchairs@ietfa.amsl.com>; Tue, 21 Jan 2014 16:47:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.736
X-Spam-Level: 
X-Spam-Status: No, score=-6.736 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_INVITATION=-2, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ojyDACy6rklI for <wgchairs@ietfa.amsl.com>; Tue, 21 Jan 2014 16:46:57 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0D7BE1A0125 for <wgchairs@ietf.org>; Tue, 21 Jan 2014 16:46:56 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BCT65479; Wed, 22 Jan 2014 00:46:55 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 22 Jan 2014 00:46:42 +0000
Received: from SZXEMA406-HUB.china.huawei.com (10.82.72.38) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 22 Jan 2014 00:46:38 +0000
Received: from SZXEMA510-MBX.china.huawei.com ([169.254.3.206]) by SZXEMA406-HUB.china.huawei.com ([10.82.72.38]) with mapi id 14.03.0158.001; Wed, 22 Jan 2014 08:46:36 +0800
From: Bert Greevenbosch <Bert.Greevenbosch@huawei.com>
To: "wgchairs@ietf.org" <wgchairs@ietf.org>
Subject: RE: Document language editing session in London
Thread-Topic: Document language editing session in London
Thread-Index: AQHPEzDJUNltU0xQL0ijow/5BhpSG5qJRdiAgALsp4CAAQjygIAAuEWAgABH2wCAAEPRgIABbNig
Date: Wed, 22 Jan 2014 00:46:35 +0000
Message-ID: <46A1DF3F04371240B504290A071B4DB63E3E300E@SZXEMA510-MBX.china.huawei.com>
References: <D6557C43-1445-4660-804D-BD17ED9DD486@nominum.com> <B0D29E0424F2DE47A0B36779EC66677925867D07@nkgeml501-mbs.china.huawei.com> <9ADCA470-8200-4C9E-A728-FD69D155A569@wjcerveny.com> <52DD401B.7000106@alum.mit.edu> <949EF20990823C4C85C18D59AA11AD8B11E9C3@FR712WXCHMBA11.zeu.alcatel-lucent.com> <E045AECD98228444A58C61C200AE1BD8416A2C00@xmb-rcd-x01.cisco.com> <655C07320163294895BBADA28372AF5D191DF8@FR712WXCHMBA15.zeu.alcatel-lucent.com>
In-Reply-To: <655C07320163294895BBADA28372AF5D191DF8@FR712WXCHMBA15.zeu.alcatel-lucent.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.66.162.63]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2014 00:47:02 -0000

> -----Original Message-----
> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of Scharf,
> Michael (Michael)
> Sent: 21 January 2014 18:46
> To: Pascal Thubert (pthubert); DRAGE, Keith (Keith); Paul Kyzivat;
> wgchairs@ietf.org
> Subject: RE: Document language editing session in London
>=20
> > -----Original Message-----
> > From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of Pascal
> > Thubert (pthubert)
> > Sent: Tuesday, January 21, 2014 7:43 AM
> > To: DRAGE, Keith (Keith); Paul Kyzivat; wgchairs@ietf.org
> > Subject: RE: Document language editing session in London
> >
> > As a non-Native chair, Keith, I'm unclear how I can accomplish that.
> > Maybe the WG could have a more official position for a secretary who
> > would have to be fluent in English?
> > Would that be a slippery slope?
>=20
> As a non-native speaker, I am not sure if we could indeed find native
> speakers inside the WG who would be really eager to do this kind of
> work.
>=20
> My observation is that usually some native speakers are willing to help
> out (e.g., during WGLC), but on a voluntary basis only, i.e., if they
> happen to have spare cycles.

Indeed, I agree this kind of work should be done on a voluntary basis.

But I certainly see value in it. So I think it is a very good initiative fr=
om Ted and Joel to initiate such a language session.

One could also consider to create a list of volunteers generally willing to=
 help on reviewing the language in the documents. In that way such work is =
not restricted to a Saturday session, and it also gives volunteers the free=
dom to help when it is convenient to them. It may also lead to better quali=
ty documents before the meeting, as the documents could be updated before t=
he submission deadline.

Although not a native speaker, I would be happy to be on that list. :-)

> Michael
>=20
>=20
> >
> > Cheers,
> >
> > Pascal
> >
> > > -----Original Message-----
> > > From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of
> DRAGE,
> > > Keith (Keith)
> > > Sent: mardi 21 janvier 2014 03:26
> > > To: Paul Kyzivat; wgchairs@ietf.org
> > > Subject: RE: Document language editing session in London
> > >
> > > Conversely, at the stage of IESG approval the Ads should not be
> > worrying with
> > > this at all.
> > >
> > > Given that the document is meant to be complete technically before
> > WGLC, at
> > > that point we should be able yo ascertain that:
> > > -	the document is clearly written
> > > -	that all requirements are clear
> > > The WGLC will obviously polish this, but it is really the
> > responsibility of the WG
> > > chair to ensure this.
> > >
> > > Keith
> > >
> > > > -----Original Message-----
> > > > From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of
> Paul
> > > > Kyzivat
> > > > Sent: 20 January 2014 15:26
> > > > To: wgchairs@ietf.org
> > > > Subject: Re: Document language editing session in London
> > > >
> > > > I have a very different view of this from Bill.
> > > >
> > > > IMO, especially early in the process, what is important is to
> > discuss
> > > > the *concepts* in a draft, not the language usage.
> > > > This is true whether the author is just a grammatically inept
> > native
> > > > English speaker/writer, or if the author doesn't have English as
> > his
> > > > native language.
> > > >
> > > > I find that documents written by many non-native English writers
> > have
> > > > usage that is "unusual" for natives, but in general it is still
> > > > perfectly understandable. I find it easier to just "let it be"
> > until
> > > > the document is quite mature and the discussion of basics is over
> > and
> > > > it is time for polishing.
> > > >
> > > > Discussing language style and grammar in the midst of technical
> > > > discussions is very distracting.
> > > >
> > > > 	Thanks,
> > > > 	Paul
> > > >
> > > > On 1/19/14 6:38 PM, Bill Cerveny wrote:
> > > > > [My first rant as a WG chair. I first wrote the rant, then took
> > out
> > > > > maybe 2/3rds of what I wrote :-) ]
> > > > >
> > > > > Having documents cleaned up grammatically as early as
> > > > possible is very important and will result in better technical
> > > > discussions, better (final) documents and a faster document
> > turnaround
> > > > from submission to publication.
> > > > >
> > > > > Last year my daughter, a recent college graduate in
> > > > English, told me she aspired to be a technical writer, at which
> > time I
> > > > told her, "Gee, how'd you like to get experience reviewing
> > technical
> > > > documents?" I recruited her to review WG documents primarily from
> a
> > > > grammatical, non-technical perspective. She was successful at
> > > > providing constructive grammatical feedback to WG draft authors.
> > > > >
> > > > > Having worked with my daughter in in helping her get up to
> > > > speed in reviewing IETF documents, it seems there are challenges
> a
> > > > volunteer reviewer faces:
> > > > > 1) There doesn't appear to be a clear, concise web page new
> > > > volunteer reviewers can use as a starting point.
> > > > > 2) How does one determine which documents are fair game for
> > > > document review?  In theory, any document submitted to the IETF
> > should
> > > > be open for grammatical review the moment it is submitted, but
> > given
> > > > limited resources, from a WG perspective, we encourage reviewing
> WG
> > > > documents first.
> > > > > 3) How should a reviewer submit proposed changes? There
> > > > isn't a consistent IETF recommendation for how to submit review
> > > > comments/changes (such as format and/or tools) and it seems a
> > > > consistent recommendation would be useful.
> > > > > 4) There isn't any mechanism for encouraging (or even
> > > > rewarding) reviewers who may not be intimately interested in the
> > > > technical aspects of the documents. I sent my daughter an
> > > > IETF88 T-shirt, but other than a thanks from the authors and/or
> the
> > WG
> > > > chairs, there isn't much that is done to encourage or reward the
> > > > reviewers.
> > > > >
> > > > > At the risk of sounding non-IETFish here (we're mostly all
> > > > "volunteers"), in a perfect world, it would make sense for
> authors
> > to
> > > > pay a document reviewer to review a document before it is even
> > > > submitted to the IETF. The time involved with reviewing documents
> > for
> > > > grammatical correctness can be non-trivial. Certainly, there is
> an
> > > > implied financial cost for the time that a volunteer reviewer
> > spends
> > > > to review a document. If the author is serious about submitting a
> > > > concise technical document and having a concise technical
> document
> > > > published, it would behoove the author to ensure that the
> document
> > is
> > > > grammatically correct before it is submitted to engineers for
> > > > technical scrutiny. In this perfect world, there might be some
> sort
> > of
> > > > central list of people willing to review documents, although at a
> > > > larger organization, it should be possible for the author to ask
> > > > someone at the organization to review the document.
> > > > >
> > > > > Bill Cerveny
> > > > >
> > > > > On Jan 17, 2014, at 9:58 PM, Zongning <zongning@huawei.com>
> > wrote:
> > > > >
> > > > >> Dear Ted, and all,
> > > > >>
> > > > >> As a non-native English speaker, I agree that this is a
> > > > good practice to improve the quality of IETF I-Ds.
> > > > >>
> > > > >> I also share the opinion of Thomas that more volunteers
> > > > should be called to help the whole community. Probably the
> similar
> > > > practice could be conducted in a more "distributed"
> > > > way, e.g., in WG level, led by WG co-chairs.
> > > > >>
> > > > >> Anyway, I will plan to submit I-D to this session in London,
> > learn
> > > > >> something important, then talk to my group, especially as a
> > > > >> non-native English WG co-chair. :-)
> > > > >>
> > > > >> Thanks.
> > > > >>
> > > > >> -Ning
> > > > >>
> > > > >>> -----Original Message-----
> > > > >>> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On
> > > > Behalf Of Ted
> > > > >>> Lemon
> > > > >>> Sent: Friday, January 17, 2014 11:04 AM
> > > > >>> To: wgchairs@ietf.org Chairs
> > > > >>> Cc: Heather Flanagan (RFC Series Editor)
> > > > >>> Subject: Document language editing session in London
> > > > >>>
> > > > >>> Dear WG Chairs:
> > > > >>>
> > > > >>> The IESG has decided to repeat the experiment that we
> > > > tried in Berlin at the
> > > > >>> upcoming London IETF meeting.   We would like to invite
> > > > ten document
> > > > >>> authors to a language editing session in London on the
> > > > Saturday prior to the
> > > > >>> IETF meeting.   The goal of this editing session will be
> > > > for two area directors,
> > > > >>> me and Joel Jaeggli, to each sit with a group of five
> > > > document editors and work
> > > > >>> on each editors' document for 30 minutes in a group
> > > > setting.   Benoit Claise
> > > > >>> has also offered to help if there are any French-speaking
> > authors
> > > > >>> who would like to participate.
> > > > >>>
> > > > >>> The plan for this work is to do two things: first, to review
> > the
> > > > >>> documents, and secondly, for the participants to have the
> > > > opportunity to work with Joel or with
> > > > >>> me to improve the quality of their documents.   The goal
> > > > is specifically for
> > > > >>> non-native english speakers who have documents that the
> working
> > > > >>> group considers important, but which are felt to need
> > > > help with english language
> > > > >>> editing.   It is important that the authors _want_ to get
> > > > help-that they
> > > > >>> recognize that they could use help and that they are
> > comfortable
> > > > >>> getting that help in a small group setting.
> > > > >>>
> > > > >>> What the meeting will look like is that there will be one or
> > two
> > > > >>> tables in a meeting room; I will be at one table with
> > > > five authors and a representative
> > > > >>> from the RFC Editor.   Joel will be at a separate table,
> > > > with the same
> > > > >>> arrangement.   If there aren't enough authors, we may do
> > > > a single table, as
> > > > >>> we did in Berlin.
> > > > >>>
> > > > >>> Each of us will have briefly reviewed the five documents
> prior
> > to
> > > > >>> the meeting, and we expect that the authors will be
> > > > familiar with each others' documents as
> > > > >>> well.   For thirty minutes per document, we will sit with
> > > > the author and go
> > > > >>> over the document, offering comments and suggestions and
> > > > getting feedback
> > > > >>> from the author.   The other authors will follow this.
> > > > Then we will move on to
> > > > >>> the next author.   Joel will be doing the same thing at
> > > > the other table.   The
> > > > >>> RFC Editor will be observing and offering advice on
> > > > request, or if
> > > > >>> they can't resist, but the main goal is to take advantage
> > > > of the technical editorial
> > > > >>> expertise of the two ADs for this experiment.   At the
> > > > end of the editing
> > > > >>> session, we will have a half hour session where we talk
> > > > about what
> > > > >>> went well, if anything, and what went wrong, if anything,
> > > > and how we
> > > > >>> might do it better next time.
> > > > >>>
> > > > >>> Neither Joel nor I are experts on teaching english to non-
> > native
> > > > >>> speakers, so we do not claim any specific knowledge other
> > > > than that
> > > > >>> we both have a keen interest in improving the quality of IETF
> > > > >>> documents, a fair amount of experience in at least trying
> > > > to do so,
> > > > >>> and a desire to help our colleagues to accomplish their goals.
> > > > >>>
> > > > >>> Our desired outcome from this meeting is twofold: first,
> > > > to help the
> > > > >>> specific authors who attend; secondly, to learn how to
> > > > help authors
> > > > >>> in general: what frustrations they have in writing documents
> > for
> > > > >>> IETF, what stumbling blocks they trip over, and how we
> > > > can help them.
> > > > >>>
> > > > >>> What we are asking working group chairs to do is think
> > > > about whether there
> > > > >>> are documents in their working group that could use this
> > > > sort of help.   If you
> > > > >>> believe there are, please contact the authors of those
> > > > documents and
> > > > >>> ask them in a non-pushy way whether they would like to
> > > > participate in this experiment.
> > > > >>> Please let us know if any of your authors are interested
> > > > in this.   If you have
> > > > >>> more than one document that you'd like worked on, please
> > > > tell us which one is
> > > > >>> most important to you.   We will have to do a triage
> > > > process unless the
> > > > >>> response to this call for participants is tiny, so it's
> > > > likely that we will only take
> > > > >>> the document you think is more important.   If we get a
> > > > really good response,
> > > > >>> we won't be able to take documents from every working group
> > that
> > > > >>> responds; please don't take this as a criticism if your
> > > > document isn't chosen.
> > > > >>>
> > > > >>> If you think this is a good idea and want to take
> > > > advantage of it,
> > > > >>> please contact your authors as soon as possible, so that
> > > > they can make travel plans that allow
> > > > >>> them to get to the venue on Saturday rather than on
> > > > Sunday.   Please bear in
> > > > >>> mind that the document selection process will take time,
> > > > and set your authors'
> > > > >>> expectations appropriately.
> > > > >>>
> > > > >>> We will arrange for authors who wish to attend and who
> > > > are selected
> > > > >>> to receive invitations, so that they can justify the
> > > > early arrival
> > > > >>> to their management if necessary.
> > > > >>>
> > > > >>> Thanks!
> > > > >>
> > > > >
> > > > >
> > > >
> > > >

From fred@cisco.com  Tue Jan 21 17:45:49 2014
Return-Path: <fred@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 866F61A027D for <wgchairs@ietfa.amsl.com>; Tue, 21 Jan 2014 17:45:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -112.036
X-Spam-Level: 
X-Spam-Status: No, score=-112.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, GB_I_INVITATION=-2, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xOsF_EP8f01c for <wgchairs@ietfa.amsl.com>; Tue, 21 Jan 2014 17:45:47 -0800 (PST)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) by ietfa.amsl.com (Postfix) with ESMTP id C660D1A01B8 for <wgchairs@ietf.org>; Tue, 21 Jan 2014 17:45:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12049; q=dns/txt; s=iport; t=1390355146; x=1391564746; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=1NxprW+pG0mk13Oi5SDiFNum+t+TKGYPELAbsrrsJDU=; b=IXh9DUNCOK4GkCtCpJ/g9hyDLCHVzNsx/9NgU46JwgzMNrXG7nzrBIfR +G5DtOVcv0uzwNRKfpFGslYu8yIyAsck16S0mFxB8xqC2uK3bLwWpuRlQ OpO6Mnd7lQKIxIb3K/TvplR6JPnqKbboi+CTEoDdw+2DPPm8HwH8cWron g=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgwFAJYi31KtJV2d/2dsb2JhbABagws4VrtugRQWdIIlAQEBAwEdTg4FBwQCAQgRBAEBAScHMhQJCAIEDgUOBgWHZAjCXheOJwRUBwaDHoEUBJA7gTGCDoQogTKQZoMtgWhC
X-IronPort-AV: E=Sophos;i="4.95,697,1384300800";  d="asc'?scan'208";a="14526422"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-8.cisco.com with ESMTP; 22 Jan 2014 01:45:42 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [173.37.183.81]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id s0M1jgXF000615 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 22 Jan 2014 01:45:42 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.230]) by xhc-rcd-x07.cisco.com ([173.37.183.81]) with mapi id 14.03.0123.003; Tue, 21 Jan 2014 19:45:42 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: Bill Cerveny <bill@wjcerveny.com>
Subject: Re: Document language editing session in London
Thread-Topic: Document language editing session in London
Thread-Index: AQHPEzDHMVbgSeXcKUW1+GZusD2fSpqKMIqAgALsp4CAA0hQgA==
Date: Wed, 22 Jan 2014 01:45:41 +0000
Message-ID: <909B8981-E21E-43D7-BEE2-AFE6D64FEA92@cisco.com>
References: <D6557C43-1445-4660-804D-BD17ED9DD486@nominum.com> <B0D29E0424F2DE47A0B36779EC66677925867D07@nkgeml501-mbs.china.huawei.com> <9ADCA470-8200-4C9E-A728-FD69D155A569@wjcerveny.com>
In-Reply-To: <9ADCA470-8200-4C9E-A728-FD69D155A569@wjcerveny.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.117]
Content-Type: multipart/signed; boundary="Apple-Mail=_E7B5F8A4-F103-46B7-B4FC-A688C3FC3659"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: "wgchairs@ietf.org Chairs" <wgchairs@ietf.org>, "Heather Flanagan \(RFC Series Editor\)" <rse@rfc-editor.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2014 01:45:49 -0000

--Apple-Mail=_E7B5F8A4-F103-46B7-B4FC-A688C3FC3659
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Jan 19, 2014, at 3:38 PM, Bill Cerveny <bill@wjcerveny.com> wrote:

> [My first rant as a WG chair. I first wrote the rant, then took out =
maybe 2/3rds of what I wrote :-) ]
>=20
> Having documents cleaned up grammatically as early as possible is very =
important and will result in better technical discussions, better =
(final) documents and a faster document turnaround from submission to =
publication.
>=20
> Last year my daughter, a recent college graduate in English, told me =
she aspired to be a technical writer, at which time I told her, =93Gee, =
how=92d you like to get experience reviewing technical documents?=94 I =
recruited her to review WG documents primarily from a grammatical, =
non-technical perspective. She was successful at providing constructive =
grammatical feedback to WG draft authors.
>=20
> Having worked with my daughter in in helping her get up to speed in =
reviewing IETF documents, it seems there are challenges a volunteer =
reviewer faces:
> 1) There doesn=92t appear to be a clear, concise web page new =
volunteer reviewers can use as a starting point.

This is probably a question for your daughter. What would they want on =
the web page? For example, the RFC Editor has a style guide; I presume =
thats of interest. I could imagine a "what would you hope to find in an =
RFC" discussion, but you know as well as I that the topic is all over =
the map.=20

> 2) How does one determine which documents are fair game for document =
review?  In theory, any document submitted to the IETF should be open =
for grammatical review the moment it is submitted, but given limited =
resources, from a WG perspective, we encourage reviewing WG documents =
first.

Yes. draft-ietf-*. There is room for individual submissions as well, but =
they come and go.

> 3) How should a reviewer submit proposed changes? There isn=92t a =
consistent IETF recommendation for how to submit review comments/changes =
(such as format and/or tools) and it seems a consistent recommendation =
would be useful.

Well, I don't have an RFC to point you to. I can comment on AUTH48 =
guidelines.=20

*** OLD ***
A really strange bit of text this is
*** NEW ***
This is a really strange bit of text
***

I might add that, since this is presumably a friendly amendment to some =
well-meaning person's document, that there be a note to say *why* the =
new text is suggested.

> 4) There isn=92t any mechanism for encouraging (or even rewarding) =
reviewers who may not be intimately interested in the technical aspects =
of the documents. I sent my daughter an IETF88 T-shirt, but other than a =
thanks from the authors and/or the WG chairs, there isn=92t much that is =
done to encourage or reward the reviewers.

For you and me, it's part of what we do.

"That depends". If they're willing to do it and good at it, I could =
imagine them getting paid. There's a service in London, a bit of spam =
told me once, that will take a document formatted in Microsoft Word, =
turn it into English, and send it back. Since this is done with "Track =
Changes", the author has the option of wondering whether the suggested =
edits are in fact in keeping with the document. They do it for a set =
price scaled by the document size. I haven't actually used the service, =
but I have thought about it.

If your daughter is coming to the IETF meeting, I'd buy her a beverage =
of her choice...

> At the risk of sounding non-IETFish here (we=92re mostly all =
=93volunteers=94), in a perfect world, it would make sense for authors =
to pay a document reviewer to review a document before it is even =
submitted to the IETF.

If the authors are paying, so be it. The ESL co-authors I have worked =
with seem to have the idea that an english-speaking co-author solves =
that problem.

See comment above about individual submissions. I have seen a lot of =
documents that are well described as having a lot of blanks that the =
author plans to fill in, or which are going to need a lot of work before =
they even resemble an output. It would be nice to have perfect input, =
but ...=20

The place I'd suggest that is the transition from an individual =
submission to a working group document, or just before working group =
last call.

> The time involved with reviewing documents for grammatical correctness =
can be non-trivial. Certainly, there is an implied financial cost for =
the time that a volunteer reviewer spends to review a document. If the =
author is serious about submitting a concise technical document and =
having a concise technical document published, it would behoove the =
author to ensure that the document is grammatically correct before it is =
submitted to engineers for technical scrutiny. In this perfect world, =
there might be some sort of central list of people willing to review =
documents, although at a larger organization, it should be possible for =
the author to ask someone at the organization to review the document.

No complaint about the perfect world, but - to be very blunt and honest, =
I work in a global company, and the IETF is a global bunch of engineers. =
"Accents" and their written counterparts are part of life. I'm far more =
interested in the content being technically astute than written in =
perfect English.=20

> Bill Cerveny
>=20
> On Jan 17, 2014, at 9:58 PM, Zongning <zongning@huawei.com> wrote:
>=20
>> Dear Ted, and all,
>>=20
>> As a non-native English speaker, I agree that this is a good practice =
to improve the quality of IETF I-Ds.
>>=20
>> I also share the opinion of Thomas that more volunteers should be =
called to help the whole community. Probably the similar practice could =
be conducted in a more "distributed" way, e.g., in WG level, led by WG =
co-chairs.
>>=20
>> Anyway, I will plan to submit I-D to this session in London, learn =
something important, then talk to my group, especially as a non-native =
English WG co-chair. :-)
>>=20
>> Thanks.
>>=20
>> -Ning
>>=20
>>> -----Original Message-----
>>> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of Ted =
Lemon
>>> Sent: Friday, January 17, 2014 11:04 AM
>>> To: wgchairs@ietf.org Chairs
>>> Cc: Heather Flanagan (RFC Series Editor)
>>> Subject: Document language editing session in London
>>>=20
>>> Dear WG Chairs:
>>>=20
>>> The IESG has decided to repeat the experiment that we tried in =
Berlin at the
>>> upcoming London IETF meeting.   We would like to invite ten document
>>> authors to a language editing session in London on the Saturday =
prior to the
>>> IETF meeting.   The goal of this editing session will be for two =
area directors,
>>> me and Joel Jaeggli, to each sit with a group of five document =
editors and work
>>> on each editors' document for 30 minutes in a group setting.   =
Benoit Claise
>>> has also offered to help if there are any French-speaking authors =
who would like
>>> to participate.
>>>=20
>>> The plan for this work is to do two things: first, to review the =
documents, and
>>> secondly, for the participants to have the opportunity to work with =
Joel or with
>>> me to improve the quality of their documents.   The goal is =
specifically for
>>> non-native english speakers who have documents that the working =
group
>>> considers important, but which are felt to need help with english =
language
>>> editing.   It is important that the authors _want_ to get help-that =
they
>>> recognize that they could use help and that they are comfortable =
getting that
>>> help in a small group setting.
>>>=20
>>> What the meeting will look like is that there will be one or two =
tables in a
>>> meeting room; I will be at one table with five authors and a =
representative
>>> from the RFC Editor.   Joel will be at a separate table, with the =
same
>>> arrangement.   If there aren't enough authors, we may do a single =
table, as
>>> we did in Berlin.
>>>=20
>>> Each of us will have briefly reviewed the five documents prior to =
the meeting,
>>> and we expect that the authors will be familiar with each others' =
documents as
>>> well.   For thirty minutes per document, we will sit with the author =
and go
>>> over the document, offering comments and suggestions and getting =
feedback
>>> from the author.   The other authors will follow this. Then we will =
move on to
>>> the next author.   Joel will be doing the same thing at the other =
table.   The
>>> RFC Editor will be observing and offering advice on request, or if =
they can't
>>> resist, but the main goal is to take advantage of the technical =
editorial
>>> expertise of the two ADs for this experiment.   At the end of the =
editing
>>> session, we will have a half hour session where we talk about what =
went well, if
>>> anything, and what went wrong, if anything, and how we might do it =
better
>>> next time.
>>>=20
>>> Neither Joel nor I are experts on teaching english to non-native =
speakers, so we
>>> do not claim any specific knowledge other than that we both have a =
keen
>>> interest in improving the quality of IETF documents, a fair amount =
of experience
>>> in at least trying to do so, and a desire to help our colleagues to =
accomplish
>>> their goals.
>>>=20
>>> Our desired outcome from this meeting is twofold: first, to help the =
specific
>>> authors who attend; secondly, to learn how to help authors in =
general: what
>>> frustrations they have in writing documents for IETF, what stumbling =
blocks
>>> they trip over, and how we can help them.
>>>=20
>>> What we are asking working group chairs to do is think about whether =
there
>>> are documents in their working group that could use this sort of =
help.   If you
>>> believe there are, please contact the authors of those documents and =
ask them
>>> in a non-pushy way whether they would like to participate in this =
experiment.
>>> Please let us know if any of your authors are interested in this.   =
If you have
>>> more than one document that you'd like worked on, please tell us =
which one is
>>> most important to you.   We will have to do a triage process unless =
the
>>> response to this call for participants is tiny, so it's likely that =
we will only take
>>> the document you think is more important.   If we get a really good =
response,
>>> we won't be able to take documents from every working group that =
responds;
>>> please don't take this as a criticism if your document isn't chosen.
>>>=20
>>> If you think this is a good idea and want to take advantage of it, =
please contact
>>> your authors as soon as possible, so that they can make travel plans =
that allow
>>> them to get to the venue on Saturday rather than on Sunday.   Please =
bear in
>>> mind that the document selection process will take time, and set =
your authors'
>>> expectations appropriately.
>>>=20
>>> We will arrange for authors who wish to attend and who are selected =
to receive
>>> invitations, so that they can justify the early arrival to their =
management if
>>> necessary.
>>>=20
>>> Thanks!
>>=20
>=20

------------------------------------------------------
8 issues in virtual infrastructure
http://dcrocker.net/#fallacies


--Apple-Mail=_E7B5F8A4-F103-46B7-B4FC-A688C3FC3659
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iD8DBQFS3yLEbjEdbHIsm0MRAiypAJ4yfRNQwhV4Vg+yaoNqnwMTJILimwCgm97o
roxawJh3XSN/2o4eAsrWye4=
=WWpD
-----END PGP SIGNATURE-----

--Apple-Mail=_E7B5F8A4-F103-46B7-B4FC-A688C3FC3659--

From loa@pi.nu  Tue Jan 21 21:22:30 2014
Return-Path: <loa@pi.nu>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B29721A0229 for <wgchairs@ietfa.amsl.com>; Tue, 21 Jan 2014 21:22:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XDSwBHXAGldD for <wgchairs@ietfa.amsl.com>; Tue, 21 Jan 2014 21:22:29 -0800 (PST)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id D26A81A0030 for <wgchairs@ietf.org>; Tue, 21 Jan 2014 21:22:28 -0800 (PST)
Received: from [192.168.1.3] (unknown [112.208.45.113]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 86392180145E; Wed, 22 Jan 2014 06:22:26 +0100 (CET)
Message-ID: <52DF5588.1050606@pi.nu>
Date: Wed, 22 Jan 2014 13:22:16 +0800
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Thomas Narten <narten@us.ibm.com>, Bill Cerveny <bill@wjcerveny.com>
Subject: Re: [BOFChairs] Document language editing session in London
References: <D6557C43-1445-4660-804D-BD17ED9DD486@nominum.com> <B0D29E0424F2DE47A0B36779EC66677925867D07@nkgeml501-mbs.china.huawei.com> <9ADCA470-8200-4C9E-A728-FD69D155A569@wjcerveny.com> <m3zjmppc0y.wl%narten@us.ibm.com>
In-Reply-To: <m3zjmppc0y.wl%narten@us.ibm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "wgchairs@ietf.org Chairs" <wgchairs@ietf.org>, "Heather Flanagan \(RFC Series Editor\)" <rse@rfc-editor.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2014 05:22:30 -0000

Thomas,

I think this is a two way process, both ADs and authors learn.
Why block or discourage ADs form taking part if they see it useful?

You are right, having ADs as the means to make this happen does not
scale.

/Loa


On 2014-01-21 23:53, Thomas Narten wrote:
> My larger point about all this is:
>
> 1) Per my first message, the ADs shouldn't be sitting down with
> authors to teach them how to write. It doesn't scale and I have a hard
> time seeing it address the real problem in a meaningful way. If that
> were part of a larger plan, maybe it would make sense, but I don't
> recall discussion of a larger plan.

-- 


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

From agenda@ietf.org  Wed Jan 22 11:12:18 2014
Return-Path: <agenda@ietf.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51AFC1A0379; Wed, 22 Jan 2014 11:12:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id niV_dgoF2KsU; Wed, 22 Jan 2014 11:12:16 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CB5B1A02D6; Wed, 22 Jan 2014 11:12:16 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Agenda <agenda@ietf.org>
To: Working Group Chairs <wgchairs@ietf.org>
Subject: IETF 89 - Working Group Chairs Training Lunch
X-Test-IDTracker: no
X-IETF-IDTracker: 4.90.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140122191216.17770.49151.idtracker@ietfa.amsl.com>
Date: Wed, 22 Jan 2014 11:12:16 -0800
Cc: edu-team@ietf.org, irsg@irtf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: IETF Agenda <agenda@ietf.org>
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2014 19:12:19 -0000

Hello Everyone,

We will be holding a WG Chairs training lunch at IETF 89 in London.  All cu=
rrent WG chairs, BOF chairs, IRTF chairs, and IESG members are welcome to a=
ttend. The lunch training will take place on Wednesday, March 5th, 2014 at =
11:30am, and a complimentary lunch will be provided.  The location will be =
announced separately to those who RSVP.

The topic of the training will be "On Consensus" lead by Pete Resnick, Meli=
nda Shore and Peter Saint-Andre.

If you would like to attend this session, please RSVP using the registratio=
n page: https://www.ietf.org/registration/ietf89/rsvp.py?eventid=3D1&eventc=
ode=3D348905 =


Please register prior to the cut-off on Monday, February 10th.

If you have RSVP'd for the training lunch but will not be able to attend, o=
r have any issues registering for the event, please send a message to agend=
a@ietf.org.  =



Thank You!

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

From rjsparks@nostrum.com  Wed Jan 22 13:50:19 2014
Return-Path: <rjsparks@nostrum.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57A2D1A034A for <wgchairs@ietfa.amsl.com>; Wed, 22 Jan 2014 13:50:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.036
X-Spam-Level: 
X-Spam-Status: No, score=-1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 53XgMF9Wm_qm for <wgchairs@ietfa.amsl.com>; Wed, 22 Jan 2014 13:50:17 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id C95A31A02F0 for <wgchairs@ietf.org>; Wed, 22 Jan 2014 13:50:17 -0800 (PST)
Received: from unnumerable.local (pool-173-71-10-88.dllstx.fios.verizon.net [173.71.10.88]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id s0MLoG6I019098 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK) for <wgchairs@ietf.org>; Wed, 22 Jan 2014 15:50:17 -0600 (CST) (envelope-from rjsparks@nostrum.com)
Message-ID: <52E03D0E.5060703@nostrum.com>
Date: Wed, 22 Jan 2014 15:50:06 -0600
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "<wgchairs@ietf.org>" <wgchairs@ietf.org>
Subject: Please double-check your group's archive in the web-based email list archive tool
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.71.10.88 is authenticated by a trusted mechanism)
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2014 21:50:19 -0000

Chairs -

If you have not already done so, please look briefly at your lists in 
the new tool and make sure you see what you expect.

You can browse quickly to them with a URL like:

<https://mailarchive.ietf.org/arch/search/?email_list=stir>

Click the date column header twice (the first time will give you a 
most-recent to least-recent view, and the second the reverse),
or jump straight to a URL like
<https://mailarchive.ietf.org/arch/search/?email_list=stir&so=date>
and check that the archive goes back as far as you expect.

Note that you can pull the division between the message list pane and 
the message preview pane down to allow you to see more of the messages 
in the list at one time.

If you discover something that needs attention, please file a ticket at
<http://trac.tools.ietf.org/tools/ietfdb/newticket>

RjS

From rjsparks@nostrum.com  Wed Jan 22 13:58:43 2014
Return-Path: <rjsparks@nostrum.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 788F01A0487 for <wgchairs@ietfa.amsl.com>; Wed, 22 Jan 2014 13:58:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.036
X-Spam-Level: 
X-Spam-Status: No, score=-1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5GV4o60r-ski for <wgchairs@ietfa.amsl.com>; Wed, 22 Jan 2014 13:58:42 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 87F021A0111 for <wgchairs@ietf.org>; Wed, 22 Jan 2014 13:58:42 -0800 (PST)
Received: from unnumerable.local (pool-173-71-10-88.dllstx.fios.verizon.net [173.71.10.88]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id s0MLwfRQ019410 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK) for <wgchairs@ietf.org>; Wed, 22 Jan 2014 15:58:42 -0600 (CST) (envelope-from rjsparks@nostrum.com)
Message-ID: <52E03F06.5050409@nostrum.com>
Date: Wed, 22 Jan 2014 15:58:30 -0600
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: Web-based email list archive search and browsing tool ready for use
References: <CF21F08E-DA1F-457D-B4C4-80F27FAAC1F8@ietf.org> <52DEA230.2040909@nostrum.com>
In-Reply-To: <52DEA230.2040909@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.71.10.88 is authenticated by a trusted mechanism)
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2014 21:58:43 -0000

As you might have already noticed, this was addressed, as was the 500 
issue Lou was running into.

Scott notes that he has found several messages for ietf@ in his archive 
(and that are in the mbox files) that don't show here.
They are not lost - they are moved away. The load into this archive used 
the contents of mhonarc as a filter since we
have several years of work of spam being identified and suppressed 
there. If mhonarc wasn't populated correctly for those
very old messages, we can adjust.

If you find (particularly for very old lists) that there are messages 
missing that you think _should_ be there, please look
for them in mhonarc. If you find them there, please send me a note with 
a pointer to the message in mhonarc.
If you find they're not there, please open a ticket - if it's easy to 
see a date before which the import into mhonarc looks wrong,
include that in the ticket.

Thanks for your help,

RjS

On 1/21/14, 10:37 AM, Robert Sparks wrote:
> It looks like newer messages haven't been imported in the last few 
> days (the most recent I'm seeing on several lists is from Jan 14).
> We'll find out why and get this up to date.
>
> RjS
>
> On 1/21/14, 10:18 AM, IETF Chair wrote:
>> Chairs:
>>
>> The tool realizing the requirements we developed in RFC 6778 is ready 
>> for your use. We are announcing it to the working group chairs first 
>> to bring the load onto this new service incrementally. We will send 
>> an announcement to the entire community later this week.
>>
>> You'll find the service at https://mailarchive.ietf.org/
>>
>> If you choose to log in, use your datatracker credentials.
>>
>> If you encounter problems or have suggestions for future 
>> improvements, please file a report using 
>> http://trac.tools.ietf.org/tools/ietfdb/newticket
>>
>> If you find spam, please send a request to remove it including a link 
>> to the message to action@ietf.org.
>>
>> We are still working towards providing IMAP access to the archives. 
>> That is not part of the tool at this time. The old archives will 
>> continue to receive new messages and will be available in their 
>> current locations until further notice.
>>
>> Early testers have reported this tool to be very useful. I hope you 
>> also find it to be so.
>>
>> Jari
>>
>


From adam@nostrum.com  Wed Jan 22 14:21:54 2014
Return-Path: <adam@nostrum.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C83461A04E6 for <wgchairs@ietfa.amsl.com>; Wed, 22 Jan 2014 14:21:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.036
X-Spam-Level: 
X-Spam-Status: No, score=-1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YCJgBrdmmmFk for <wgchairs@ietfa.amsl.com>; Wed, 22 Jan 2014 14:21:53 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id B7BAE1A04E2 for <wgchairs@ietf.org>; Wed, 22 Jan 2014 14:21:53 -0800 (PST)
Received: from orochi-2.roach.at (99-152-145-110.lightspeed.dllstx.sbcglobal.net [99.152.145.110]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id s0MMLqQK020440 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 22 Jan 2014 16:21:53 -0600 (CST) (envelope-from adam@nostrum.com)
Message-ID: <52E0447B.1080906@nostrum.com>
Date: Wed, 22 Jan 2014 16:21:47 -0600
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Robert Sparks <rjsparks@nostrum.com>, "<wgchairs@ietf.org>" <wgchairs@ietf.org>
Subject: Re: Please double-check your group's archive in the web-based email list archive tool
References: <52E03D0E.5060703@nostrum.com>
In-Reply-To: <52E03D0E.5060703@nostrum.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 99.152.145.110 is authenticated by a trusted mechanism)
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2014 22:21:55 -0000

On 1/22/14 15:50, Robert Sparks wrote:
> Chairs -
>
> If you have not already done so, please look briefly at your lists in 
> the new tool and make sure you see what you expect.
> ...
> If you discover something that needs attention, please file a ticket at
> <http://trac.tools.ietf.org/tools/ietfdb/newticket>

To prevent anyone else from opening a duplicate ticket: I opened 
<http://trac.tools.ietf.org/tools/ietfdb/ticket/1255> to track the older 
SIP working group missing messages.

/a

From tjc@ecs.soton.ac.uk  Thu Jan 23 02:06:57 2014
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F10971A03E5 for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 02:06:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.755
X-Spam-Level: 
X-Spam-Status: No, score=-1.755 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.535, SPF_NEUTRAL=0.779] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NzSiV3KN3Dc6 for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 02:06:54 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 509571A03E1 for <wgchairs@ietf.org>; Thu, 23 Jan 2014 02:06:54 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id s0NA6lpl031090; Thu, 23 Jan 2014 10:06:47 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk s0NA6lpl031090
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1390471608; bh=XumybYM/qkDkK+vWyqL7YyETiB4=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=VnXKbVfziX/Fg1OaWHXJ4YEdx+onXjvV73tJGQEy5lcPJ+OiBsBTPtUExWVyJDbgJ hii1TnjxjLGYH/JBinxMv57VKdyC/yTFJAPgJ/JO5Yfre50Nfep6GMhae3wXW0GkmN 66KquPITqq7uTpXh7jBLS0Sa8EZXNwP4kpCuuKgw=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id q0MA6l0959663368j7 ret-id none; Thu, 23 Jan 2014 10:06:47 +0000
Received: from dhcp-161-136.wireless.soton.ac.uk (dhcp-161-136.wireless.soton.ac.uk [152.78.161.136] (may be forged)) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id s0NA6hkH004272 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 23 Jan 2014 10:06:43 GMT
Content-Type: multipart/alternative; boundary="Apple-Mail=_490C1C0E-09D4-4171-9999-A331681498F8"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Please double-check your group's archive in the web-based email list archive tool
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <52E03D0E.5060703@nostrum.com>
Date: Thu, 23 Jan 2014 10:06:44 +0000
Message-ID: <EMEW3|5588d604ea84af6799fdb2e2240bb970q0MA6l03tjc|ecs.soton.ac.uk|7BB26AEF-90AF-445E-A4FF-FFA4B351A66A@ecs.soton.ac.uk>
References: <52E03D0E.5060703@nostrum.com> <7BB26AEF-90AF-445E-A4FF-FFA4B351A66A@ecs.soton.ac.uk>
To: Robert Sparks <rjsparks@nostrum.com>
X-Mailer: Apple Mail (2.1510)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=q0MA6l095966336800; tid=q0MA6l0959663368j7; client=relay,ipv6; mail=; rcpt=; nrcpt=2:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: s0NA6lpl031090
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: "<wgchairs@ietf.org>" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 10:06:57 -0000

--Apple-Mail=_490C1C0E-09D4-4171-9999-A331681498F8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Hi,

On 22 Jan 2014, at 21:50, Robert Sparks <rjsparks@nostrum.com> wrote:

> Chairs -
>=20
> If you have not already done so, please look briefly at your lists in =
the new tool and make sure you see what you expect.
>=20
> You can browse quickly to them with a URL like:
>=20
> <https://mailarchive.ietf.org/arch/search/?email_list=3Dstir>

This looks really nice - =
https://mailarchive.ietf.org/arch/search/?email_list=3Ddnssd is good.

Can we advertise this yet to our WGs?

Tim

>=20
> Click the date column header twice (the first time will give you a =
most-recent to least-recent view, and the second the reverse),
> or jump straight to a URL like
> <https://mailarchive.ietf.org/arch/search/?email_list=3Dstir&so=3Ddate>
> and check that the archive goes back as far as you expect.
>=20
> Note that you can pull the division between the message list pane and =
the message preview pane down to allow you to see more of the messages =
in the list at one time.
>=20
> If you discover something that needs attention, please file a ticket =
at
> <http://trac.tools.ietf.org/tools/ietfdb/newticket>
>=20
> RjS


--Apple-Mail=_490C1C0E-09D4-4171-9999-A331681498F8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Diso-8859-1"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Hi,<div><br><div><div>On 22 Jan 2014, at 21:50, Robert Sparks &lt;<a =
href=3D"mailto:rjsparks@nostrum.com">rjsparks@nostrum.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">Chairs -<br><br>If you have not already done so, please =
look briefly at your lists in the new tool and make sure you see what =
you expect.<br><br>You can browse quickly to them with a URL =
like:<br><br>&lt;<a =
href=3D"https://mailarchive.ietf.org/arch/search/?email_list=3Dstir">https=
://mailarchive.ietf.org/arch/search/?email_list=3Dstir</a>&gt;<br></blockq=
uote><div><br></div>This looks really nice -&nbsp;<a =
href=3D"https://mailarchive.ietf.org/arch/search/?email_list=3Ddnssd">http=
s://mailarchive.ietf.org/arch/search/?email_list=3Ddnssd</a>&nbsp;is =
good.</div><div><br></div><div>Can we advertise this yet to our =
WGs?</div><div><br></div><div>Tim</div><div><br><blockquote =
type=3D"cite"><br>Click the date column header twice (the first time =
will give you a most-recent to least-recent view, and the second the =
reverse),<br>or jump straight to a URL like<br>&lt;<a =
href=3D"https://mailarchive.ietf.org/arch/search/?email_list=3Dstir&amp;so=
=3Ddate">https://mailarchive.ietf.org/arch/search/?email_list=3Dstir&amp;s=
o=3Ddate</a>&gt;<br>and check that the archive goes back as far as you =
expect.<br><br>Note that you can pull the division between the message =
list pane and the message preview pane down to allow you to see more of =
the messages in the list at one time.<br><br>If you discover something =
that needs attention, please file a ticket at<br>&lt;<a =
href=3D"http://trac.tools.ietf.org/tools/ietfdb/newticket">http://trac.too=
ls.ietf.org/tools/ietfdb/newticket</a>&gt;<br><br>RjS<br></blockquote></di=
v><br></div></body></html>=

--Apple-Mail=_490C1C0E-09D4-4171-9999-A331681498F8--

From rjsparks@nostrum.com  Thu Jan 23 06:12:10 2014
Return-Path: <rjsparks@nostrum.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EF5B1A0443 for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 06:12:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.035
X-Spam-Level: 
X-Spam-Status: No, score=-1.035 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qvp0oLfgbqgZ for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 06:12:08 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 75B5E1A00CA for <wgchairs@ietf.org>; Thu, 23 Jan 2014 06:12:07 -0800 (PST)
Received: from unnumerable.local (pool-173-71-10-88.dllstx.fios.verizon.net [173.71.10.88]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id s0NEBVOx054573 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK); Thu, 23 Jan 2014 08:11:32 -0600 (CST) (envelope-from rjsparks@nostrum.com)
Message-ID: <52E12302.8030808@nostrum.com>
Date: Thu, 23 Jan 2014 08:11:14 -0600
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Re: Please double-check your group's archive in the web-based email list archive tool
References: <52E03D0E.5060703@nostrum.com> <7BB26AEF-90AF-445E-A4FF-FFA4B351A66A@ecs.soton.ac.uk> <EMEW3|5588d604ea84af6799fdb2e2240bb970q0MA6l03tjc|ecs.soton.ac.uk|7BB26AEF-90AF-445E-A4FF-FFA4B351A66A@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|5588d604ea84af6799fdb2e2240bb970q0MA6l03tjc|ecs.soton.ac.uk|7BB26AEF-90AF-445E-A4FF-FFA4B351A66A@ecs.soton.ac.uk>
Content-Type: multipart/alternative; boundary="------------030506030703040301040908"
Received-SPF: pass (shaman.nostrum.com: 173.71.10.88 is authenticated by a trusted mechanism)
Cc: "<wgchairs@ietf.org>" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 14:12:10 -0000

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

On 1/23/14, 4:06 AM, Tim Chown wrote:
> Hi,
>
> On 22 Jan 2014, at 21:50, Robert Sparks <rjsparks@nostrum.com 
> <mailto:rjsparks@nostrum.com>> wrote:
>
>> Chairs -
>>
>> If you have not already done so, please look briefly at your lists in 
>> the new tool and make sure you see what you expect.
>>
>> You can browse quickly to them with a URL like:
>>
>> <https://mailarchive.ietf.org/arch/search/?email_list=stir>
>
> This looks really nice - 
> https://mailarchive.ietf.org/arch/search/?email_list=dnssd is good.
Thanks for the quick reply!
>
> Can we advertise this yet to our WGs?
Please hold off just a little while (I'm currently thinking Monday) to 
give other chairs a chance to sanity check their lists.
>
> Tim
>
>>
>> Click the date column header twice (the first time will give you a 
>> most-recent to least-recent view, and the second the reverse),
>> or jump straight to a URL like
>> <https://mailarchive.ietf.org/arch/search/?email_list=stir&so=date>
>> and check that the archive goes back as far as you expect.
>>
>> Note that you can pull the division between the message list pane and 
>> the message preview pane down to allow you to see more of the 
>> messages in the list at one time.
>>
>> If you discover something that needs attention, please file a ticket at
>> <http://trac.tools.ietf.org/tools/ietfdb/newticket>
>>
>> RjS
>


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

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 1/23/14, 4:06 AM, Tim Chown wrote:<br>
    </div>
    <blockquote
cite="mid:EMEW3|5588d604ea84af6799fdb2e2240bb970q0MA6l03tjc|ecs.soton.ac.uk|7BB26AEF-90AF-445E-A4FF-FFA4B351A66A@ecs.soton.ac.uk"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      Hi,
      <div><br>
        <div>
          <div>On 22 Jan 2014, at 21:50, Robert Sparks &lt;<a
              moz-do-not-send="true" href="mailto:rjsparks@nostrum.com">rjsparks@nostrum.com</a>&gt;
            wrote:</div>
          <br class="Apple-interchange-newline">
          <blockquote type="cite">Chairs -<br>
            <br>
            If you have not already done so, please look briefly at your
            lists in the new tool and make sure you see what you expect.<br>
            <br>
            You can browse quickly to them with a URL like:<br>
            <br>
            &lt;<a moz-do-not-send="true"
              href="https://mailarchive.ietf.org/arch/search/?email_list=stir">https://mailarchive.ietf.org/arch/search/?email_list=stir</a>&gt;<br>
          </blockquote>
          <div><br>
          </div>
          This looks really nice -&nbsp;<a moz-do-not-send="true"
            href="https://mailarchive.ietf.org/arch/search/?email_list=dnssd">https://mailarchive.ietf.org/arch/search/?email_list=dnssd</a>&nbsp;is
          good.</div>
      </div>
    </blockquote>
    Thanks for the quick reply!<br>
    <blockquote
cite="mid:EMEW3|5588d604ea84af6799fdb2e2240bb970q0MA6l03tjc|ecs.soton.ac.uk|7BB26AEF-90AF-445E-A4FF-FFA4B351A66A@ecs.soton.ac.uk"
      type="cite">
      <div>
        <div><br>
        </div>
        <div>Can we advertise this yet to our WGs?</div>
      </div>
    </blockquote>
    Please hold off just a little while (I'm currently thinking Monday)
    to give other chairs a chance to sanity check their lists.<br>
    <blockquote
cite="mid:EMEW3|5588d604ea84af6799fdb2e2240bb970q0MA6l03tjc|ecs.soton.ac.uk|7BB26AEF-90AF-445E-A4FF-FFA4B351A66A@ecs.soton.ac.uk"
      type="cite">
      <div>
        <div><br>
        </div>
        <div>Tim</div>
        <div><br>
          <blockquote type="cite"><br>
            Click the date column header twice (the first time will give
            you a most-recent to least-recent view, and the second the
            reverse),<br>
            or jump straight to a URL like<br>
            &lt;<a moz-do-not-send="true"
href="https://mailarchive.ietf.org/arch/search/?email_list=stir&amp;so=date">https://mailarchive.ietf.org/arch/search/?email_list=stir&amp;so=date</a>&gt;<br>
            and check that the archive goes back as far as you expect.<br>
            <br>
            Note that you can pull the division between the message list
            pane and the message preview pane down to allow you to see
            more of the messages in the list at one time.<br>
            <br>
            If you discover something that needs attention, please file
            a ticket at<br>
            &lt;<a moz-do-not-send="true"
              href="http://trac.tools.ietf.org/tools/ietfdb/newticket">http://trac.tools.ietf.org/tools/ietfdb/newticket</a>&gt;<br>
            <br>
            RjS<br>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------030506030703040301040908--

From tnadeau@lucidvision.com  Thu Jan 23 06:13:31 2014
Return-Path: <tnadeau@lucidvision.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 288541A0434 for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 06:13:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.434
X-Spam-Level: 
X-Spam-Status: No, score=-2.434 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5xRuInVxUO_1 for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 06:13:28 -0800 (PST)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 9E1651A00CA for <wgchairs@ietf.org>; Thu, 23 Jan 2014 06:13:28 -0800 (PST)
Received: from [192.168.1.110] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id 86AC426C4F60; Thu, 23 Jan 2014 09:13:27 -0500 (EST)
Content-Type: multipart/signed; boundary="Apple-Mail=_CC0BA5CA-4210-479A-867D-FCA022F2E753"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Please double-check your group's archive in the web-based email list archive tool
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <EMEW3|5588d604ea84af6799fdb2e2240bb970q0MA6l03tjc|ecs.soton.ac.uk|7BB26AEF-90AF-445E-A4FF-FFA4B351A66A@ecs.soton.ac.uk>
Date: Thu, 23 Jan 2014 09:13:27 -0500
Message-Id: <52866EA5-DE35-4300-A6A1-5337B6DD284B@lucidvision.com>
References: <52E03D0E.5060703@nostrum.com> <7BB26AEF-90AF-445E-A4FF-FFA4B351A66A@ecs.soton.ac.uk> <EMEW3|5588d604ea84af6799fdb2e2240bb970q0MA6l03tjc|ecs.soton.ac.uk|7BB26AEF-90AF-445E-A4FF-FFA4B351A66A@ecs.soton.ac.uk>
To: Tim Chown <tjc@ecs.soton.ac.uk>
X-Mailer: Apple Mail (2.1827)
Cc: "<wgchairs@ietf.org>" <wgchairs@ietf.org>, Robert Sparks <rjsparks@nostrum.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 14:13:31 -0000

--Apple-Mail=_CC0BA5CA-4210-479A-867D-FCA022F2E753
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_F75657E1-1C7B-42B9-B25B-0E2D849D4A95"


--Apple-Mail=_F75657E1-1C7B-42B9-B25B-0E2D849D4A95
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


	Just checked out: =
https://mailarchive.ietf.org/arch/search/?email_list=3Dnetmod
and I have to agree that its a cool interface. Nice work.

	--Tom


On Jan 23, 2014:5:06 AM, at 5:06 AM, Tim Chown <tjc@ecs.soton.ac.uk> =
wrote:

> Hi,
>=20
> On 22 Jan 2014, at 21:50, Robert Sparks <rjsparks@nostrum.com> wrote:
>=20
>> Chairs -
>>=20
>> If you have not already done so, please look briefly at your lists in =
the new tool and make sure you see what you expect.
>>=20
>> You can browse quickly to them with a URL like:
>>=20
>> <https://mailarchive.ietf.org/arch/search/?email_list=3Dstir>
>=20
> This looks really nice - =
https://mailarchive.ietf.org/arch/search/?email_list=3Ddnssd is good.
>=20
> Can we advertise this yet to our WGs?
>=20
> Tim
>=20
>>=20
>> Click the date column header twice (the first time will give you a =
most-recent to least-recent view, and the second the reverse),
>> or jump straight to a URL like
>> <https://mailarchive.ietf.org/arch/search/?email_list=3Dstir&so=3Ddate>=

>> and check that the archive goes back as far as you expect.
>>=20
>> Note that you can pull the division between the message list pane and =
the message preview pane down to allow you to see more of the messages =
in the list at one time.
>>=20
>> If you discover something that needs attention, please file a ticket =
at
>> <http://trac.tools.ietf.org/tools/ietfdb/newticket>
>>=20
>> RjS
>=20


--Apple-Mail=_F75657E1-1C7B-42B9-B25B-0E2D849D4A95
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Diso-8859-1"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;"><div><br></div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>Just checked out: <a =
href=3D"https://mailarchive.ietf.org/arch/search/?email_list=3Dnetmod">htt=
ps://mailarchive.ietf.org/arch/search/?email_list=3Dnetmod</a><div>and I =
have to agree that its a cool interface. Nice =
work.<br><div><br></div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	=
</span>--Tom</div><div><br></div><div><br><div><div>On Jan 23, 2014:5:06 =
AM, at 5:06 AM, Tim Chown &lt;<a =
href=3D"mailto:tjc@ecs.soton.ac.uk">tjc@ecs.soton.ac.uk</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Diso-8859-1"><div style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Hi,<div><br><div><div>On 22 Jan 2014, at 21:50, Robert Sparks &lt;<a =
href=3D"mailto:rjsparks@nostrum.com">rjsparks@nostrum.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">Chairs -<br><br>If you have not already done so, please =
look briefly at your lists in the new tool and make sure you see what =
you expect.<br><br>You can browse quickly to them with a URL =
like:<br><br>&lt;<a =
href=3D"https://mailarchive.ietf.org/arch/search/?email_list=3Dstir">https=
://mailarchive.ietf.org/arch/search/?email_list=3Dstir</a>&gt;<br></blockq=
uote><div><br></div>This looks really nice -&nbsp;<a =
href=3D"https://mailarchive.ietf.org/arch/search/?email_list=3Ddnssd">http=
s://mailarchive.ietf.org/arch/search/?email_list=3Ddnssd</a>&nbsp;is =
good.</div><div><br></div><div>Can we advertise this yet to our =
WGs?</div><div><br></div><div>Tim</div><div><br><blockquote =
type=3D"cite"><br>Click the date column header twice (the first time =
will give you a most-recent to least-recent view, and the second the =
reverse),<br>or jump straight to a URL like<br>&lt;<a =
href=3D"https://mailarchive.ietf.org/arch/search/?email_list=3Dstir&amp;so=
=3Ddate">https://mailarchive.ietf.org/arch/search/?email_list=3Dstir&amp;s=
o=3Ddate</a>&gt;<br>and check that the archive goes back as far as you =
expect.<br><br>Note that you can pull the division between the message =
list pane and the message preview pane down to allow you to see more of =
the messages in the list at one time.<br><br>If you discover something =
that needs attention, please file a ticket at<br>&lt;<a =
href=3D"http://trac.tools.ietf.org/tools/ietfdb/newticket">http://trac.too=
ls.ietf.org/tools/ietfdb/newticket</a>&gt;<br><br>RjS<br></blockquote></di=
v><br></div></div></blockquote></div><br></div></div></body></html>=

--Apple-Mail=_F75657E1-1C7B-42B9-B25B-0E2D849D4A95--

--Apple-Mail=_CC0BA5CA-4210-479A-867D-FCA022F2E753
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJS4SOHAAoJEPcO+I7eiUJZMWEP/i2n82pmL+XCntRyqjeaHS0x
wlOEoU+XWPl4tqKZU/unu8DE+Lsceaw90pH2OO9vvaqgUFOAojW+Y/kEu3OviwWj
qvlLGZ3VCrnRFdsmBbO6yPS902UUKG5dtpN98TwsZTcuqgpwdvvQr9GiY14nF8E9
S23Fbeg4K71LoewelqC7BL1Pm9xDWhESjvR8KRcptx+RTNoRNVEiLdY819OU7VjS
c2/G7MSv/OeYdMCiHRTBTZt/HzPHSm27JPoNaOhdTNHIt+WH4xnz9zsS/nnzzWgI
Lf2p5eBVkn6M1b5P+BStOGAKdYwGj54bKucZH74Sg4Kcnw0tP9Dg7bjWf3k1pMXB
4cGHFQBlo/KV7v6H1QR88/73AgLBz6pr8PxmaSO/EiiygXJNpj/FmsNOc3VSa7MW
a88S61gWfdtuft3gCVOrCoCQnF4DpTi00Ed2ASxhosfm4HuYJ5HxKX3Y57dFKNB5
+bbuJEVYIuuOMEZRtyapl90rXDrIFamlHv4TKmhi+MZGJt5RK/SAlbnOptkOI1Tp
avYArSVc6rsaegbB1CwG/CkPcJHXOKActlE3MipjB5349UqpjKCZIDjCIypunC6M
ooPvTBUk+cduAq+RInrwVhMd9U4T+rbt8CPPZfF70Mn8pTa4+0naKoOFgBTphL2k
qgZplKPlxbpY7WJ0UpYZ
=Se44
-----END PGP SIGNATURE-----

--Apple-Mail=_CC0BA5CA-4210-479A-867D-FCA022F2E753--

From bertietf@bwijnen.net  Thu Jan 23 06:19:23 2014
Return-Path: <bertietf@bwijnen.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 389E41A00F2 for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 06:19:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MpI1R3BwlJ5b for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 06:19:21 -0800 (PST)
Received: from kaka.ripe.net (kaka.ripe.net [IPv6:2001:67c:2e8:11::c100:1347]) by ietfa.amsl.com (Postfix) with ESMTP id 014141A00CA for <wgchairs@ietf.org>; Thu, 23 Jan 2014 06:19:20 -0800 (PST)
Received: from titi.ripe.net ([193.0.23.11]) by kaka.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1W6L7k-0001SZ-R0; Thu, 23 Jan 2014 15:19:17 +0100
Received: from kitten.ipv6.ripe.net ([2001:67c:2e8:1::c100:1f0] helo=guest129.guestnet.ripe.net) by titi.ripe.net with esmtp (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1W6L7k-0007qU-Jm; Thu, 23 Jan 2014 15:19:16 +0100
Message-ID: <52E124E4.2050404@bwijnen.net>
Date: Thu, 23 Jan 2014 15:19:16 +0100
From: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Robert Sparks <wgchairs@ietf.org>
Subject: Re: FW: Please double-check your group's archive in the web-based email list archive tool
References: <E4DE949E6CE3E34993A2FF8AE79131F8267D5E@DEMUMBX005.nsn-intra.net> <52E0D26E.60500@bwijnen.net>
In-Reply-To: <52E0D26E.60500@bwijnen.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-RIPE-Spam-Level: --
X-RIPE-Spam-Report: Spam Total Points:   -2.9 points pts rule name              description ---- ---------------------- ------------------------------------ -1.0 ALL_TRUSTED            Passed through trusted hosts only via SMTP -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1% [score: 0.0000]
X-RIPE-Signature: 86ab03e524994f79ca2c75a176445dd41d2318f927b0ea7a4d4bcf35eb161086
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 14:19:23 -0000

I checked, and as far as I can tell, all looks fine (for Netconf)

nice work.

Bert co-chair NETCONF WG

>> -----Original Message-----
>> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of ext Adam Roach
>> Sent: Wednesday, January 22, 2014 11:22 PM
>> To: Robert Sparks; <wgchairs@ietf.org>
>> Subject: Re: Please double-check your group's archive in the web-based email list archive tool
>>
>> On 1/22/14 15:50, Robert Sparks wrote:
>>> Chairs -
>>>
>>> If you have not already done so, please look briefly at your lists in
>>> the new tool and make sure you see what you expect.
>>> ...
>>> If you discover something that needs attention, please file a ticket at
>>> <http://trac.tools.ietf.org/tools/ietfdb/newticket>
>>
>> To prevent anyone else from opening a duplicate ticket: I opened
>> <http://trac.tools.ietf.org/tools/ietfdb/ticket/1255> to track the older
>> SIP working group missing messages.
>>
>> /a
>>
>

From giheron@cisco.com  Thu Jan 23 06:34:36 2014
Return-Path: <giheron@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B2911A00CA for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 06:34:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.036
X-Spam-Level: 
X-Spam-Status: No, score=-15.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 07PruRZ8PDKh for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 06:34:34 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id E1D7C1A00BE for <wgchairs@ietf.org>; Thu, 23 Jan 2014 06:34:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1631; q=dns/txt; s=iport; t=1390487673; x=1391697273; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=ACt/vrwX+LcqTfkcDViKa66spFd5aaQfu6xCRJ8UFcc=; b=WvHl6adrnixvTMb/pluSGEKKZ3UYiJX1rVzEJdlNiLIeqS1vPQc7ga2E Qzr0QK1a/d+NfG9GX7aYcHR5xGqz7/QEsT5poYr8oxEO/w9QQVCwQ5VLN XNqEKLxiLRW6iRnwiHULflEjfSrgMwn1tbqc9aMAp8vcnJRvVPwPPf2vS k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgsFAGIn4VKtJV2b/2dsb2JhbABbgww4VrtzgRAWdIIlAQEBAwF5EAIBCA4KLjIlAgQOBYd9CA3FZxeOHhEBCxIzB4MkgRQEiRCPE4EykGaBb4E+gXE5
X-IronPort-AV: E=Sophos;i="4.95,706,1384300800"; d="scan'208";a="296220483"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-9.cisco.com with ESMTP; 23 Jan 2014 14:34:33 +0000
Received: from xhc-aln-x03.cisco.com (xhc-aln-x03.cisco.com [173.36.12.77]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s0NEYWcP008662 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 23 Jan 2014 14:34:32 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.37]) by xhc-aln-x03.cisco.com ([173.36.12.77]) with mapi id 14.03.0123.003; Thu, 23 Jan 2014 08:34:32 -0600
From: "Giles Heron (giheron)" <giheron@cisco.com>
To: Thomas Nadeau <tnadeau@lucidvision.com>
Subject: Re: Please double-check your group's archive in the web-based email list archive tool
Thread-Topic: Please double-check your group's archive in the web-based email list archive tool
Thread-Index: AQHPF7v2912/LK2XCkuHyZIEeMOy4JqSesAAgABE7oCAAAXkAA==
Date: Thu, 23 Jan 2014 14:34:31 +0000
Message-ID: <AC20C805-48AF-480E-9B5C-132CDB8A7271@cisco.com>
References: <52E03D0E.5060703@nostrum.com> <7BB26AEF-90AF-445E-A4FF-FFA4B351A66A@ecs.soton.ac.uk> <EMEW3|5588d604ea84af6799fdb2e2240bb970q0MA6l03tjc|ecs.soton.ac.uk|7BB26AEF-90AF-445E-A4FF-FFA4B351A66A@ecs.soton.ac.uk> <52866EA5-DE35-4300-A6A1-5337B6DD284B@lucidvision.com>
In-Reply-To: <52866EA5-DE35-4300-A6A1-5337B6DD284B@lucidvision.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.147.57.5]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <D379E53E7A4801499469E5D9821C65FB@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<wgchairs@ietf.org>" <wgchairs@ietf.org>, Robert Sparks <rjsparks@nostrum.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 14:34:36 -0000

yes - checked L2VPN and looks good.

On 23 Jan 2014, at 14:13, Thomas Nadeau <tnadeau@lucidvision.com>
 wrote:

>=20
> 	Just checked out: https://mailarchive.ietf.org/arch/search/?email_list=
=3Dnetmod
> and I have to agree that its a cool interface. Nice work.
>=20
> 	--Tom
>=20
>=20
> On Jan 23, 2014:5:06 AM, at 5:06 AM, Tim Chown <tjc@ecs.soton.ac.uk> wrot=
e:
>=20
>> Hi,
>>=20
>> On 22 Jan 2014, at 21:50, Robert Sparks <rjsparks@nostrum.com> wrote:
>>=20
>>> Chairs -
>>>=20
>>> If you have not already done so, please look briefly at your lists in t=
he new tool and make sure you see what you expect.
>>>=20
>>> You can browse quickly to them with a URL like:
>>>=20
>>> <https://mailarchive.ietf.org/arch/search/?email_list=3Dstir>
>>=20
>> This looks really nice - https://mailarchive.ietf.org/arch/search/?email=
_list=3Ddnssd is good.
>>=20
>> Can we advertise this yet to our WGs?
>>=20
>> Tim
>>=20
>>>=20
>>> Click the date column header twice (the first time will give you a most=
-recent to least-recent view, and the second the reverse),
>>> or jump straight to a URL like
>>> <https://mailarchive.ietf.org/arch/search/?email_list=3Dstir&so=3Ddate>
>>> and check that the archive goes back as far as you expect.
>>>=20
>>> Note that you can pull the division between the message list pane and t=
he message preview pane down to allow you to see more of the messages in th=
e list at one time.
>>>=20
>>> If you discover something that needs attention, please file a ticket at
>>> <http://trac.tools.ietf.org/tools/ietfdb/newticket>
>>>=20
>>> RjS
>>=20
>=20


From kathleen.moriarty@emc.com  Thu Jan 23 06:38:53 2014
Return-Path: <kathleen.moriarty@emc.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 266AE1A01BC for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 06:38:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level: 
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wNRV7n8PN6hP for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 06:38:49 -0800 (PST)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) by ietfa.amsl.com (Postfix) with ESMTP id C20121A00FC for <wgchairs@ietf.org>; Thu, 23 Jan 2014 06:38:48 -0800 (PST)
Received: from maildlpprd51.lss.emc.com (maildlpprd51.lss.emc.com [10.106.48.155]) by mailuogwprd51.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0NEccRf020578 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 23 Jan 2014 09:38:40 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd51.lss.emc.com s0NEccRf020578
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1390487920; bh=xwUxYgWcbZ6fyfAyYuLPIk7V4yo=; h=From:To:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=LqqP+oavV50utoBmz4rvCVn7y1X8sHBhzOxLddGh+lUR57etoDX0fdjHc8ZE2e5YF SEZtW/jS6jUGpIoXN5DVahgAHoRBg5fzOCt5O/OwBnjslyi7aID3dHpG0fRv2x/kS3 t1jDf6Rtj6DFIsIq0GX9onQ9Q8sNEs59FBLx3Xvc=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd51.lss.emc.com s0NEccRf020578
Received: from mailusrhubprd52.lss.emc.com (mailusrhubprd52.lss.emc.com [10.106.48.25]) by maildlpprd51.lss.emc.com (RSA Interceptor); Thu, 23 Jan 2014 09:38:27 -0500
Received: from mxhub14.corp.emc.com (mxhub14.corp.emc.com [128.222.70.235]) by mailusrhubprd52.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0NEcQgY027439 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 23 Jan 2014 09:38:27 -0500
Received: from mx15a.corp.emc.com ([169.254.1.107]) by mxhub14.corp.emc.com ([128.222.70.235]) with mapi; Thu, 23 Jan 2014 09:38:26 -0500
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>, Robert Sparks <wgchairs@ietf.org>
Date: Thu, 23 Jan 2014 09:38:24 -0500
Subject: RE: FW: Please double-check your group's archive in the web-based email list archive tool
Thread-Topic: FW: Please double-check your group's archive in the web-based email list archive tool
Thread-Index: Ac8YRmuevtRK1yGyQG+te7uS9uNdsQAAkljw
Message-ID: <F5063677821E3B4F81ACFB7905573F2406584BAF17@MX15A.corp.emc.com>
References: <E4DE949E6CE3E34993A2FF8AE79131F8267D5E@DEMUMBX005.nsn-intra.net> <52E0D26E.60500@bwijnen.net> <52E124E4.2050404@bwijnen.net>
In-Reply-To: <52E124E4.2050404@bwijnen.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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd52.lss.emc.com
X-RSA-Classifications: public
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 14:38:53 -0000

SXQgbG9va3MgZ3JlYXQgZm9yIE1JTEUsIHRoYW5rIHlvdSEgIFRoaXMgaXMgYSB2ZXJ5IG5pY2Ug
aW1wcm92ZW1lbnQhDQoNCkJlc3QgcmVnYXJkcywNCkthdGhsZWVuIA0KDQotLS0tLU9yaWdpbmFs
IE1lc3NhZ2UtLS0tLQ0KRnJvbTogV0dDaGFpcnMgW21haWx0bzp3Z2NoYWlycy1ib3VuY2VzQGll
dGYub3JnXSBPbiBCZWhhbGYgT2YgQmVydCBXaWpuZW4gKElFVEYpDQpTZW50OiBUaHVyc2RheSwg
SmFudWFyeSAyMywgMjAxNCA5OjE5IEFNDQpUbzogUm9iZXJ0IFNwYXJrcw0KU3ViamVjdDogUmU6
IEZXOiBQbGVhc2UgZG91YmxlLWNoZWNrIHlvdXIgZ3JvdXAncyBhcmNoaXZlIGluIHRoZSB3ZWIt
YmFzZWQgZW1haWwgbGlzdCBhcmNoaXZlIHRvb2wNCg0KSSBjaGVja2VkLCBhbmQgYXMgZmFyIGFz
IEkgY2FuIHRlbGwsIGFsbCBsb29rcyBmaW5lIChmb3IgTmV0Y29uZikNCg0KbmljZSB3b3JrLg0K
DQpCZXJ0IGNvLWNoYWlyIE5FVENPTkYgV0cNCg0KPj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0t
LS0NCj4+IEZyb206IFdHQ2hhaXJzIFttYWlsdG86d2djaGFpcnMtYm91bmNlc0BpZXRmLm9yZ10g
T24gQmVoYWxmIE9mIGV4dCANCj4+IEFkYW0gUm9hY2gNCj4+IFNlbnQ6IFdlZG5lc2RheSwgSmFu
dWFyeSAyMiwgMjAxNCAxMToyMiBQTQ0KPj4gVG86IFJvYmVydCBTcGFya3M7IDx3Z2NoYWlyc0Bp
ZXRmLm9yZz4NCj4+IFN1YmplY3Q6IFJlOiBQbGVhc2UgZG91YmxlLWNoZWNrIHlvdXIgZ3JvdXAn
cyBhcmNoaXZlIGluIHRoZSANCj4+IHdlYi1iYXNlZCBlbWFpbCBsaXN0IGFyY2hpdmUgdG9vbA0K
Pj4NCj4+IE9uIDEvMjIvMTQgMTU6NTAsIFJvYmVydCBTcGFya3Mgd3JvdGU6DQo+Pj4gQ2hhaXJz
IC0NCj4+Pg0KPj4+IElmIHlvdSBoYXZlIG5vdCBhbHJlYWR5IGRvbmUgc28sIHBsZWFzZSBsb29r
IGJyaWVmbHkgYXQgeW91ciBsaXN0cyANCj4+PiBpbiB0aGUgbmV3IHRvb2wgYW5kIG1ha2Ugc3Vy
ZSB5b3Ugc2VlIHdoYXQgeW91IGV4cGVjdC4NCj4+PiAuLi4NCj4+PiBJZiB5b3UgZGlzY292ZXIg
c29tZXRoaW5nIHRoYXQgbmVlZHMgYXR0ZW50aW9uLCBwbGVhc2UgZmlsZSBhIHRpY2tldCANCj4+
PiBhdCA8aHR0cDovL3RyYWMudG9vbHMuaWV0Zi5vcmcvdG9vbHMvaWV0ZmRiL25ld3RpY2tldD4N
Cj4+DQo+PiBUbyBwcmV2ZW50IGFueW9uZSBlbHNlIGZyb20gb3BlbmluZyBhIGR1cGxpY2F0ZSB0
aWNrZXQ6IEkgb3BlbmVkIA0KPj4gPGh0dHA6Ly90cmFjLnRvb2xzLmlldGYub3JnL3Rvb2xzL2ll
dGZkYi90aWNrZXQvMTI1NT4gdG8gdHJhY2sgdGhlIA0KPj4gb2xkZXIgU0lQIHdvcmtpbmcgZ3Jv
dXAgbWlzc2luZyBtZXNzYWdlcy4NCj4+DQo+PiAvYQ0KPj4NCj4NCg0K

From jguichar@cisco.com  Thu Jan 23 06:43:08 2014
Return-Path: <jguichar@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A37461A0430 for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 06:43:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.036
X-Spam-Level: 
X-Spam-Status: No, score=-10.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IXpnzgf3qirW for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 06:43:07 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) by ietfa.amsl.com (Postfix) with ESMTP id D7CA41A00FC for <wgchairs@ietf.org>; Thu, 23 Jan 2014 06:43:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2102; q=dns/txt; s=iport; t=1390488186; x=1391697786; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=zG8jyHtCOsBv/SVgjesz6IvIbCLS33FRn2GpZlm4YcM=; b=D2ZEIVIIB+7eY2W0HzpxMZsduKflDZ8PiZV9N6q3vmKROQXk3gg4n1ky EQk3qa65gD/3al6NdOvSB0eZ6kdMCnp1yBy9/7ubmv+YW53b5/6htCBHj MUpUcIX4PuGsi84FTE53bUSBeoHMNReIX0HZj6AFJi3ksH58uJEFSpoao E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgsFAAkq4VKtJV2Z/2dsb2JhbABbgww4VrtzgRAWdIIlAQEBBDo/EgEIGB5CJQIEAQ0FiAUNxVwXjh4RAQsSMweEOASYI4EykGaBb4E+gXE5
X-IronPort-AV: E=Sophos;i="4.95,706,1384300800"; d="scan'208";a="14973310"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-6.cisco.com with ESMTP; 23 Jan 2014 14:43:04 +0000
Received: from xhc-aln-x06.cisco.com (xhc-aln-x06.cisco.com [173.36.12.80]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s0NEh47T007390 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 23 Jan 2014 14:43:05 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.207]) by xhc-aln-x06.cisco.com ([173.36.12.80]) with mapi id 14.03.0123.003; Thu, 23 Jan 2014 08:43:04 -0600
From: "Jim Guichard (jguichar)" <jguichar@cisco.com>
To: "Giles Heron (giheron)" <giheron@cisco.com>, Thomas Nadeau <tnadeau@lucidvision.com>
Subject: Re: Please double-check your group's archive in the web-based email list archive tool
Thread-Topic: Please double-check your group's archive in the web-based email list archive tool
Thread-Index: AQHPF7v2h0tCL5Op3kGfSWZcWsdSupqSesAAgABE7oCAAAXjgP//ro6A
Date: Thu, 23 Jan 2014 14:43:03 +0000
Message-ID: <CF0693BA.1477E%jguichar@cisco.com>
In-Reply-To: <AC20C805-48AF-480E-9B5C-132CDB8A7271@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
x-originating-ip: [10.98.43.183]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <A88F7292804D174783C3C7DA9207E201@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<wgchairs@ietf.org>" <wgchairs@ietf.org>, Robert Sparks <rjsparks@nostrum.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 14:43:08 -0000

I just checked out:
https://mailarchive.ietf.org/arch/search/?email_list=3Dsfc and although all
messages are shown the content is not provided and an error "Error reading
message file" is returned. We just migrated the WG name from nsc to sfc;
the nsc archive works fine but sfc does not. I raised a ticket to fix
this.=20

On 1/23/14 9:34 AM, "Giles Heron (giheron)" <giheron@cisco.com> wrote:

>yes - checked L2VPN and looks good.
>
>On 23 Jan 2014, at 14:13, Thomas Nadeau <tnadeau@lucidvision.com>
> wrote:
>
>>=20
>> 	Just checked out:
>>https://mailarchive.ietf.org/arch/search/?email_list=3Dnetmod
>> and I have to agree that its a cool interface. Nice work.
>>=20
>> 	--Tom
>>=20
>>=20
>> On Jan 23, 2014:5:06 AM, at 5:06 AM, Tim Chown <tjc@ecs.soton.ac.uk>
>>wrote:
>>=20
>>> Hi,
>>>=20
>>> On 22 Jan 2014, at 21:50, Robert Sparks <rjsparks@nostrum.com> wrote:
>>>=20
>>>> Chairs -
>>>>=20
>>>> If you have not already done so, please look briefly at your lists in
>>>>the new tool and make sure you see what you expect.
>>>>=20
>>>> You can browse quickly to them with a URL like:
>>>>=20
>>>> <https://mailarchive.ietf.org/arch/search/?email_list=3Dstir>
>>>=20
>>> This looks really nice -
>>>https://mailarchive.ietf.org/arch/search/?email_list=3Ddnssd is good.
>>>=20
>>> Can we advertise this yet to our WGs?
>>>=20
>>> Tim
>>>=20
>>>>=20
>>>> Click the date column header twice (the first time will give you a
>>>>most-recent to least-recent view, and the second the reverse),
>>>> or jump straight to a URL like
>>>> <https://mailarchive.ietf.org/arch/search/?email_list=3Dstir&so=3Ddate=
>
>>>> and check that the archive goes back as far as you expect.
>>>>=20
>>>> Note that you can pull the division between the message list pane and
>>>>the message preview pane down to allow you to see more of the messages
>>>>in the list at one time.
>>>>=20
>>>> If you discover something that needs attention, please file a ticket
>>>>at
>>>> <http://trac.tools.ietf.org/tools/ietfdb/newticket>
>>>>=20
>>>> RjS
>>>=20
>>=20
>


From acee.lindem@ericsson.com  Thu Jan 23 06:55:38 2014
Return-Path: <acee.lindem@ericsson.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A19CF1A03ED for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 06:55:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9NlGMJIjxUbt for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 06:55:37 -0800 (PST)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id 060A71A00D3 for <wgchairs@ietf.org>; Thu, 23 Jan 2014 06:55:36 -0800 (PST)
X-AuditID: c6180641-b7f2f8e000002cdc-79-52e12d6725fc
Received: from EUSAAHC001.ericsson.se (Unknown_Domain [147.117.188.75]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 3F.08.11484.76D21E25; Thu, 23 Jan 2014 15:55:35 +0100 (CET)
Received: from EUSAAMB101.ericsson.se ([147.117.188.118]) by EUSAAHC001.ericsson.se ([147.117.188.75]) with mapi id 14.02.0387.000; Thu, 23 Jan 2014 09:55:34 -0500
From: Acee Lindem <acee.lindem@ericsson.com>
To: "Jim Guichard (jguichar)" <jguichar@cisco.com>
Subject: Re: Please double-check your group's archive in the web-based email list archive tool
Thread-Topic: Please double-check your group's archive in the web-based email list archive tool
Thread-Index: AQHPF7v/kSdLzOQgWUaDkkbjytRVrpqSafwAgABE74CAAAXjgIAAAmKAgAADegA=
Date: Thu, 23 Jan 2014 14:55:34 +0000
Message-ID: <8A3E231E-38CB-4F8B-A9F0-DB14A2064AB2@ericsson.com>
References: <CF0693BA.1477E%jguichar@cisco.com>
In-Reply-To: <CF0693BA.1477E%jguichar@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <27740BB08DC901408C57506651C7BC7A@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrJLMWRmVeSWpSXmKPExsUyuXSPt2667sMgg62bbCzuNexktlg6T93i 2pxGNouHky+xW/zfP4XRgdVjyu+NrB5Llvxk8tj6ZAm7x6ydT1gCWKK4bFJSczLLUov07RK4 Mq6+v8Je0CFU8edEVAPjA74uRnYOCQETiQ1VXYycQJaYxIV769m6GLk4hASOMEr8+d8K5Sxn lLj1aTIbSBWbgI7E80f/mEFsEQEjie5L71lBipgF1jNKvJ/xi7GLkYNDWCBBYuaCfIiaRInV T3tZIWw/iXfbpzKC2CwCqhIXVx0As3kF7CXOnr4MZgsJ6EvMnbEIzOYUMJD4PnslWC8j0HXf T61hArGZBcQlbj2ZzwRxtYDEkj3nmSFsUYmXj/+xQthKEpOWnmOFqNeRWLD7ExvIacwC1hIf 5gdBhLUlli18zQxxgqDEyZlPWCYwis9CsmEWku5ZCN2zkHTPQtK9gJF1FSNHaXFqWW66keEm RmD0HZNgc9zBuOCT5SFGaQ4WJXHeL2+dg4QE0hNLUrNTUwtSi+KLSnNSiw8xMnFwSjUwKqrv uy/tEHn+zu8sp37teXed3hzIUJec+YhFld/4w7mVWn1xNhf/LmmPKX6RvrebL7FirWxpw6M5 r7efCPJwbSubN91zf6Ofrc6TPKttS93Nl0/OdF+fmfhr+8Kne16ZzXTwWl8f0uwacO6XW3Hb hcs8ost8+KqO3M2b98aLrWrTAze17nknlViKMxINtZiLihMBzrDC8owCAAA=
Cc: Robert Sparks <rjsparks@nostrum.com>, "<wgchairs@ietf.org>" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 14:55:38 -0000

Looks good for OSPF.=20
Acee=20
On Jan 23, 2014, at 9:43 AM, Jim Guichard (jguichar) wrote:

> I just checked out:
> https://mailarchive.ietf.org/arch/search/?email_list=3Dsfc and although a=
ll
> messages are shown the content is not provided and an error "Error readin=
g
> message file" is returned. We just migrated the WG name from nsc to sfc;
> the nsc archive works fine but sfc does not. I raised a ticket to fix
> this.=20
>=20
> On 1/23/14 9:34 AM, "Giles Heron (giheron)" <giheron@cisco.com> wrote:
>=20
>> yes - checked L2VPN and looks good.
>>=20
>> On 23 Jan 2014, at 14:13, Thomas Nadeau <tnadeau@lucidvision.com>
>> wrote:
>>=20
>>>=20
>>> 	Just checked out:
>>> https://mailarchive.ietf.org/arch/search/?email_list=3Dnetmod
>>> and I have to agree that its a cool interface. Nice work.
>>>=20
>>> 	--Tom
>>>=20
>>>=20
>>> On Jan 23, 2014:5:06 AM, at 5:06 AM, Tim Chown <tjc@ecs.soton.ac.uk>
>>> wrote:
>>>=20
>>>> Hi,
>>>>=20
>>>> On 22 Jan 2014, at 21:50, Robert Sparks <rjsparks@nostrum.com> wrote:
>>>>=20
>>>>> Chairs -
>>>>>=20
>>>>> If you have not already done so, please look briefly at your lists in
>>>>> the new tool and make sure you see what you expect.
>>>>>=20
>>>>> You can browse quickly to them with a URL like:
>>>>>=20
>>>>> <https://mailarchive.ietf.org/arch/search/?email_list=3Dstir>
>>>>=20
>>>> This looks really nice -
>>>> https://mailarchive.ietf.org/arch/search/?email_list=3Ddnssd is good.
>>>>=20
>>>> Can we advertise this yet to our WGs?
>>>>=20
>>>> Tim
>>>>=20
>>>>>=20
>>>>> Click the date column header twice (the first time will give you a
>>>>> most-recent to least-recent view, and the second the reverse),
>>>>> or jump straight to a URL like
>>>>> <https://mailarchive.ietf.org/arch/search/?email_list=3Dstir&so=3Ddat=
e>
>>>>> and check that the archive goes back as far as you expect.
>>>>>=20
>>>>> Note that you can pull the division between the message list pane and
>>>>> the message preview pane down to allow you to see more of the message=
s
>>>>> in the list at one time.
>>>>>=20
>>>>> If you discover something that needs attention, please file a ticket
>>>>> at
>>>>> <http://trac.tools.ietf.org/tools/ietfdb/newticket>
>>>>>=20
>>>>> RjS
>>>>=20
>>>=20
>>=20
>=20


From jhaas@slice.pfrc.org  Thu Jan 23 07:14:50 2014
Return-Path: <jhaas@slice.pfrc.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1B901A0006 for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 07:14:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.103
X-Spam-Level: 
X-Spam-Status: No, score=-2.103 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N3a9CkuGGCJr for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 07:14:44 -0800 (PST)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 1F50D1A001E for <wgchairs@ietf.org>; Thu, 23 Jan 2014 07:14:44 -0800 (PST)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 4A732C2C3; Thu, 23 Jan 2014 10:14:43 -0500 (EST)
Date: Thu, 23 Jan 2014 10:14:43 -0500
From: Jeffrey Haas <jhaas@pfrc.org>
To: Robert Sparks <rjsparks@nostrum.com>
Subject: Re: Please double-check your group's archive in the web-based email list archive tool
Message-ID: <20140123151443.GB4683@pfrc>
References: <52E03D0E.5060703@nostrum.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <52E03D0E.5060703@nostrum.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: "<wgchairs@ietf.org>" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 15:14:50 -0000

On Wed, Jan 22, 2014 at 03:50:06PM -0600, Robert Sparks wrote:
> If you have not already done so, please look briefly at your lists
> in the new tool and make sure you see what you expect.
> 
> You can browse quickly to them with a URL like:
> 
> <https://mailarchive.ietf.org/arch/search/?email_list=stir>
> 
> Click the date column header twice (the first time will give you a
> most-recent to least-recent view, and the second the reverse),
> or jump straight to a URL like
> <https://mailarchive.ietf.org/arch/search/?email_list=stir&so=date>
> and check that the archive goes back as far as you expect.

1700 messages are listed as the results for BFD.  The thread preview pane
only shows a few dozen.

The search interface is significantly nicer than mhonarc.  Thanks for that.

While I see the URL for a given message in the message view pane, when
clicking it I no longer have the ability to navigate through messages or
threads as in mhonarc.

> Note that you can pull the division between the message list pane
> and the message preview pane down to allow you to see more of the
> messages in the list at one time.

Thanks for mentioning that - it's not visually obvious in the interface.

This is almost nice enough to let me skip downloading the .mail files from
ftp.ietf.org and viewing in mutt.. almost.

-- Jeff

> If you discover something that needs attention, please file a ticket at
> <http://trac.tools.ietf.org/tools/ietfdb/newticket>
> 
> RjS

From bill@wjcerveny.com  Thu Jan 23 07:51:23 2014
Return-Path: <bill@wjcerveny.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDC631A000C for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 07:51:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UXr5oBWTxADy for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 07:51:22 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 32F231A000A for <wgchairs@ietf.org>; Thu, 23 Jan 2014 07:51:21 -0800 (PST)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 4CB112084D for <wgchairs@ietf.org>; Thu, 23 Jan 2014 10:51:17 -0500 (EST)
Received: from web1 ([10.202.2.211]) by compute5.internal (MEProxy); Thu, 23 Jan 2014 10:51:17 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:mime-version :content-transfer-encoding:content-type:reply-to:in-reply-to :references:subject:date; s=smtpout; bh=ELqSP4p9+Yops1lSeyxcy5BZ f6I=; b=FbSP1xXrTstONIZFupDm+rCZIUU0jzoimE+u9gDPpRB/XdfAo077T7XA q+n3YoD4Dvm1euyjCJF9sK4eD+yrexfnfNa2tUktdZR9xXMXzKSb/H6pEAaxLeft NPsAbqSl+EeCiaBHoeAtpJMCeS0lqxUXlyIUtUocrRobqCN2PkQ=
Received: by web1.nyi.mail.srv.osa (Postfix, from userid 99) id 2C1F4F00008; Thu, 23 Jan 2014 10:51:17 -0500 (EST)
Message-Id: <1390492277.19336.74444029.55F46F36@webmail.messagingengine.com>
X-Sasl-Enc: PBGBY5oVC8IgVZ60+4LlvghHgv7bKJGvhYytrmnkJxu2 1390492277
From: Bill Cerveny <bill@wjcerveny.com>
To: wgchairs@ietf.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
X-Mailer: MessagingEngine.com Webmail Interface - ajax-aec78a11
In-Reply-To: <52E03D0E.5060703@nostrum.com>
References: <52E03D0E.5060703@nostrum.com>
Subject: Re: Please double-check your group's archive in the web-based email list archive tool
Date: Thu, 23 Jan 2014 10:51:17 -0500
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: bill@wjcerveny.com
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 15:51:24 -0000

IPPM mail list looks good; I like the UI.

Thanks!

Bill Cerveny

On Wed, Jan 22, 2014, at 04:50 PM, Robert Sparks wrote:
> Chairs -
> 
> If you have not already done so, please look briefly at your lists in 
> the new tool and make sure you see what you expect.
> 
> You can browse quickly to them with a URL like:
> 
> <https://mailarchive.ietf.org/arch/search/?email_list=stir>
> 
> Click the date column header twice (the first time will give you a 
> most-recent to least-recent view, and the second the reverse),
> or jump straight to a URL like
> <https://mailarchive.ietf.org/arch/search/?email_list=stir&so=date>
> and check that the archive goes back as far as you expect.
> 
> Note that you can pull the division between the message list pane and 
> the message preview pane down to allow you to see more of the messages 
> in the list at one time.
> 
> If you discover something that needs attention, please file a ticket at
> <http://trac.tools.ietf.org/tools/ietfdb/newticket>
> 
> RjS

From pkyzivat@alum.mit.edu  Thu Jan 23 08:36:01 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D7FD1A0008 for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 08:36:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ak317evgKTiO for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 08:36:00 -0800 (PST)
Received: from qmta04.westchester.pa.mail.comcast.net (qmta04.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:40]) by ietfa.amsl.com (Postfix) with ESMTP id 23DA21A001C for <wgchairs@ietf.org>; Thu, 23 Jan 2014 08:36:00 -0800 (PST)
Received: from omta14.westchester.pa.mail.comcast.net ([76.96.62.60]) by qmta04.westchester.pa.mail.comcast.net with comcast id HQn91n0091HzFnQ54UbzE2; Thu, 23 Jan 2014 16:35:59 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta14.westchester.pa.mail.comcast.net with comcast id HUbz1n0063ZTu2S3aUbzal; Thu, 23 Jan 2014 16:35:59 +0000
Message-ID: <52E144EE.1090908@alum.mit.edu>
Date: Thu, 23 Jan 2014 11:35:58 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: Please double-check your group's archive in the web-based email list archive tool
References: <52E03D0E.5060703@nostrum.com> <7BB26AEF-90AF-445E-A4FF-FFA4B351A66A@ecs.soton.ac.uk> <EMEW3|5588d604ea84af6799fdb2e2240bb970q0MA6l03tjc|ecs.soton.ac.uk|7BB26AEF-90AF-445E-A4FF-FFA4B351A66A@ecs.soton.ac.uk> <52E12302.8030808@nostrum.com>
In-Reply-To: <52E12302.8030808@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1390494959; bh=rs+yEqovoc3qOmVhnPJFewN2ihQynWn0nhPEKIo0eR8=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=DZyK1klJoRAGUSh5b60TnYTSuR7peC+aX+WIknBs4dvzdSB53H/3CO/wEA0OJEks7 rij5b7/8d04DP8IVdsKue0kY7ur7A+/BiNyebG6WIZ5c7GqVSGqx0BP0tJEaPVrN9c hFKlXKrPmVm/mOCyKbhedkxVGTIus82wRSBB0uVglKwQmTut2frP02evbAcKGs0v5U rVZKNSEYjRKvOS9+13lKUjKBQXaDboQpLit8UQ3NwNsnW94v7NuuuwygYOOzWrP53T P/Qo9Uq+uBe2fOarsZ/D7TkKEVI77IIqUFRVWVu9gbix1FTQ7KsKhjaakhiBhw5zh6 yLub74Gg9ToMQ==
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 16:36:01 -0000

On 1/23/14 9:11 AM, Robert Sparks wrote:

>> Can we advertise this yet to our WGs?
> Please hold off just a little while (I'm currently thinking Monday) to
> give other chairs a chance to sanity check their lists.

Will this be linked on the WG charter pages? (the email archive link)

	Thanks,
	Paul


From housley@vigilsec.com  Thu Jan 23 08:45:41 2014
Return-Path: <housley@vigilsec.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB5731A0036 for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 08:45:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.899
X-Spam-Level: 
X-Spam-Status: No, score=-101.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w-RepYC80TIQ for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 08:45:39 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [209.135.209.4]) by ietfa.amsl.com (Postfix) with ESMTP id 002481A0006 for <wgchairs@ietf.org>; Thu, 23 Jan 2014 08:45:38 -0800 (PST)
Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id 3EA2E9A429A; Thu, 23 Jan 2014 11:45:28 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id w2DC9qAkbP0b; Thu, 23 Jan 2014 11:45:06 -0500 (EST)
Received: from [192.168.2.110] (pool-71-178-10-80.washdc.fios.verizon.net [71.178.10.80]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 9F6299A429C; Thu, 23 Jan 2014 11:45:06 -0500 (EST)
Subject: Re: Problem with new Note Well
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: multipart/alternative; boundary=Apple-Mail-14--128564821
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com>
Date: Thu, 23 Jan 2014 11:44:55 -0500
Message-Id: <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
X-Mailer: Apple Mail (2.1085)
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 16:45:41 -0000

--Apple-Mail-14--128564821
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

It seems that the shorter one is now being used on the IETF web site:
http://www.ietf.org/about/note-well.html


On Jan 8, 2014, at 3:57 PM, Mary Barnes wrote:

> Personally, I've never seen significant value in this shorter note =
well and while others have been using this new text for the past few =
meetings, I've stuck to the old.   Now that this is considered the =
recommended note well for chairs to use, I guess I'll use it.  But, I =
personally think accuracy should trump brevity.  I think the "must" in =
that bullet  ought to at least be a should and that adding an =
"otherwise, one should not contribute to or participate in any related =
IETF activities." would add more value.  =20
>=20
> Mary.
>=20
>=20
> On Wed, Jan 8, 2014 at 1:17 PM, Bradner, Scott <sob@harvard.edu> =
wrote:
> you are correct - we (Barry, the IESG & me) discussed this before the =
IESG approved this text - they felt that
> being brief was more important than being fully accurate (or at least =
that is the way I expressed it)
>=20
> Scott
>=20
> Scott O Bradner
> Senior Technology Consultant
>=20
> Harvard University Information Technology
> Innovation & Architecture
> (P) +1 (617) 495 3864
> 8 Story St, room 5014
> Cambridge, MA 02138
>=20
>=20
>=20
> On Jan 8, 2014, at 2:13 PM, Cullen Jennings (fluffy) =
<fluffy@cisco.com> wrote:
>=20
> >
> >
> > On Dec 16, 2013, at 12:56 PM, Barry Leiba <barryleiba@computer.org> =
wrote:
> >
> >> The IESG has made final edits to the updated Note Well statement, =
and
> >> it has been officially updated:
> >> http://www.ietf.org/about/note-well.html
> >>
> >> I have just uploaded the final versions of the Note Well meeting
> >> slides, attached to the bottom of the WG Chairs wiki:
> >> http://wiki.tools.ietf.org/group/wgchairs/wiki/WikiStart
> >>
> >> Please use this new version now, and please remember that as you
> >> prepare slides for the London meeting.
> >>
> >> Barry
> >
> >
> > The new note well says
> >
> >       =95 If you are aware that any contribution (something written, =
said, or discussed in any IETF context) is covered by patents or patent =
applications, you must disclose that fact.
> >
> > Is that true?  Or is it missing something along the lines of section =
y of BCP 79 such as
> >
> >   or must not contribute to or participate in IETF activities with
> >   respect to technologies that he or she reasonably and personally
> >   knows to be Covered by IPR which he or she will not disclose.
> >
> > Thanks, Cullen


--Apple-Mail-14--128564821
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">It =
seems that the shorter one is now being used on the IETF web =
site:<div><a =
href=3D"http://www.ietf.org/about/note-well.html">http://www.ietf.org/abou=
t/note-well.html</a><div><br></div><div><br><div><div>On Jan 8, 2014, at =
3:57 PM, Mary Barnes wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
dir=3D"ltr">Personally, I've never seen significant value in this =
shorter note well and while others have been using this new text for the =
past few meetings, I've stuck to the old. &nbsp; Now that this is =
considered the recommended note well for chairs to use, I guess I'll use =
it. &nbsp;But, I personally think accuracy should trump brevity. &nbsp;I =
think the "must" in that bullet &nbsp;ought to at least be a should and =
that adding an "otherwise, one should not contribute to or participate =
in any related IETF activities." would add more value. &nbsp;&nbsp;<div>
<br></div><div>Mary.<br><div class=3D"gmail_extra"><br><br><div =
class=3D"gmail_quote">On Wed, Jan 8, 2014 at 1:17 PM, Bradner, Scott =
<span dir=3D"ltr">&lt;<a href=3D"mailto:sob@harvard.edu" =
target=3D"_blank">sob@harvard.edu</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; =
border-left-width: 1px; border-left-color: rgb(204, 204, 204); =
border-left-style: solid; padding-left: 1ex; position: static; z-index: =
auto; ">you are correct - we (Barry, the IESG &amp; me) discussed this =
before the IESG approved this text - they felt that<br>
being brief was more important than being fully accurate (or at least =
that is the way I expressed it)<br>
<br>
Scott<br>
<br>
Scott O Bradner<br>
Senior Technology Consultant<br>
<br>
Harvard University Information Technology<br>
Innovation &amp; Architecture<br>
(P) <a href=3D"tel:%2B1%20%28617%29%20495%203864" =
value=3D"+16174953864">+1 (617) 495 3864</a><br>
8 Story St, room 5014<br>
Cambridge, MA 02138<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
<br>
On Jan 8, 2014, at 2:13 PM, Cullen Jennings (fluffy) &lt;<a =
href=3D"mailto:fluffy@cisco.com">fluffy@cisco.com</a>&gt; wrote:<br>
<br>
&gt;<br>
&gt;<br>
&gt; On Dec 16, 2013, at 12:56 PM, Barry Leiba &lt;<a =
href=3D"mailto:barryleiba@computer.org">barryleiba@computer.org</a>&gt; =
wrote:<br>
&gt;<br>
&gt;&gt; The IESG has made final edits to the updated Note Well =
statement, and<br>
&gt;&gt; it has been officially updated:<br>
&gt;&gt; <a href=3D"http://www.ietf.org/about/note-well.html" =
target=3D"_blank">http://www.ietf.org/about/note-well.html</a><br>
&gt;&gt;<br>
&gt;&gt; I have just uploaded the final versions of the Note Well =
meeting<br>
&gt;&gt; slides, attached to the bottom of the WG Chairs wiki:<br>
&gt;&gt; <a =
href=3D"http://wiki.tools.ietf.org/group/wgchairs/wiki/WikiStart" =
target=3D"_blank">http://wiki.tools.ietf.org/group/wgchairs/wiki/WikiStart=
</a><br>
&gt;&gt;<br>
&gt;&gt; Please use this new version now, and please remember that as =
you<br>
&gt;&gt; prepare slides for the London meeting.<br>
&gt;&gt;<br>
&gt;&gt; Barry<br>
&gt;<br>
&gt;<br>
&gt; The new note well says<br>
&gt;<br>
&gt; &nbsp; &nbsp; &nbsp; =95 If you are aware that any contribution =
(something written, said, or discussed in any IETF context) is covered =
by patents or patent applications, you must disclose that fact.<br>
&gt;<br>
&gt; Is that true? &nbsp;Or is it missing something along the lines of =
section y of BCP 79 such as<br>
&gt;<br>
&gt; &nbsp; or must not contribute to or participate in IETF activities =
with<br>
&gt; &nbsp; respect to technologies that he or she reasonably and =
personally<br>
&gt; &nbsp; knows to be Covered by IPR which he or she will not =
disclose.<br>
&gt;<br>
&gt; Thanks, =
Cullen<br></div></div></blockquote></div></div></div></div></blockquote></=
div><br></div></div></body></html>=

--Apple-Mail-14--128564821--

From RMarshall@telecomsys.com  Thu Jan 23 09:04:23 2014
Return-Path: <RMarshall@telecomsys.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6FC01A00A6 for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 09:04:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qviwCeLJJ5Gm for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 09:04:22 -0800 (PST)
Received: from sea-mx-02.telecomsys.com (sea-mx-02.telecomsys.com [199.165.246.42]) by ietfa.amsl.com (Postfix) with ESMTP id 3A9501A0055 for <wgchairs@ietf.org>; Thu, 23 Jan 2014 09:04:22 -0800 (PST)
Received: from SEA-EXCAS-3.telecomsys.com  (exc2010-local3.telecomsys.com [10.32.12.6]) by  sea-mx-02.telecomsys.com (8.14.5/8.14.5) with ESMTP id s0NH4Jlp023903  (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Thu, 23  Jan 2014 09:04:19 -0800
Received: from SEA-EXMB-2.telecomsys.com ([169.254.2.111]) by  SEA-EXCAS-3.telecomsys.com ([10.32.12.6]) with mapi id 14.01.0218.012; Thu, 23 Jan 2014 09:04:19 -0800
From: Roger Marshall <RMarshall@telecomsys.com>
To: Robert Sparks <rjsparks@nostrum.com>, "<wgchairs@ietf.org>"  <wgchairs@ietf.org>
Subject: RE: Please double-check your group's archive in the web-based email list archive tool
Thread-Topic: Please double-check your group's archive in the web-based email  list archive tool
Thread-Index: AQHPF7v1DKyjJB9qdki8W/kR+qrpF5qSgBvw
Date: Thu, 23 Jan 2014 17:04:18 +0000
Message-ID: <FBD5AAFFD0978846BF6D3FAB4C892ACC10019832@SEA-EXMB-2.telecomsys.com>
References: <52E03D0E.5060703@nostrum.com>
In-Reply-To: <52E03D0E.5060703@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.32.12.134]
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.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 17:04:24 -0000

ECRIT content looks like it's in there, the tool looks really good.

I did spot a few things, so I logged a couple of tickets on the subject (se=
arch) and group (default display) features at:
http://trac.tools.ietf.org/tools/ietfdb

-roger.

-----Original Message-----
From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of Robert Sparks
Sent: Wednesday, January 22, 2014 1:50 PM
To: <wgchairs@ietf.org>
Subject: Please double-check your group's archive in the web-based email li=
st archive tool

Chairs -

If you have not already done so, please look briefly at your lists in the n=
ew tool and make sure you see what you expect.

You can browse quickly to them with a URL like:

<https://mailarchive.ietf.org/arch/search/?email_list=3Dstir>

Click the date column header twice (the first time will give you a most-rec=
ent to least-recent view, and the second the reverse), or jump straight to =
a URL like <https://mailarchive.ietf.org/arch/search/?email_list=3Dstir&so=
=3Ddate>
and check that the archive goes back as far as you expect.

Note that you can pull the division between the message list pane and the m=
essage preview pane down to allow you to see more of the messages in the li=
st at one time.

If you discover something that needs attention, please file a ticket at <ht=
tp://trac.tools.ietf.org/tools/ietfdb/newticket>

RjS

CONFIDENTIALITY NOTICE: The information contained in this message may be pr=
ivileged and/or confidential. If you are not the intended recipient, or res=
ponsible for delivering this message to the intended recipient, any review,=
 forwarding, dissemination, distribution or copying of this communication o=
r any attachment(s) is strictly prohibited. If you have received this messa=
ge in error, please notify the sender immediately, and delete it and all at=
tachments from your computer and network.

From twatteyne@gmail.com  Thu Jan 23 09:20:35 2014
Return-Path: <twatteyne@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98FB71A0148 for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 09:20:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dMO3XMa2Bso8 for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 09:20:31 -0800 (PST)
Received: from mail-pd0-x232.google.com (mail-pd0-x232.google.com [IPv6:2607:f8b0:400e:c02::232]) by ietfa.amsl.com (Postfix) with ESMTP id BA7F01A013C for <wgchairs@ietf.org>; Thu, 23 Jan 2014 09:20:31 -0800 (PST)
Received: by mail-pd0-f178.google.com with SMTP id y13so2032579pdi.9 for <wgchairs@ietf.org>; Thu, 23 Jan 2014 09:20:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=3cML1IDnP7FwrTlA6oWJgS05mSFEKEnbMBJWAKZYBIs=; b=sM/lO+4CdKM+bWXZvNWHVNFiOS+yaWugTcKXqtMRqvHnWDrW6kgx/5VrQ/ry2QDzwH bAs1+wnAswMRZnybtR83Q+13kWj8AYLqdd0bdE/6imJdt05ZlUa/n5JDpvjdrZ9fLMug q3Vyt2jSLcv3R9kX89bm1gJgh4ovPikf4oZ5asQ/x3hx3DiwAzRxokbkpUjxHT5noCgz sDPbcffTMyYaIfleoFPJIOrPTCLQEpqU6yPP+CJRhnnriGMyDYO4J0ihxzjlj0MKVwJB fROUo+1v+Ds5qSddxo877ovE7KyWlMfyyDS50Q82CVD0Bqz9SecaoLz13G+pLclz1iOV Asfw==
X-Received: by 10.68.66.1 with SMTP id b1mr9273331pbt.43.1390497630835; Thu, 23 Jan 2014 09:20:30 -0800 (PST)
MIME-Version: 1.0
Sender: twatteyne@gmail.com
Received: by 10.66.47.227 with HTTP; Thu, 23 Jan 2014 09:20:10 -0800 (PST)
In-Reply-To: <FBD5AAFFD0978846BF6D3FAB4C892ACC10019832@SEA-EXMB-2.telecomsys.com>
References: <52E03D0E.5060703@nostrum.com> <FBD5AAFFD0978846BF6D3FAB4C892ACC10019832@SEA-EXMB-2.telecomsys.com>
From: Thomas Watteyne <watteyne@eecs.berkeley.edu>
Date: Thu, 23 Jan 2014 09:20:10 -0800
X-Google-Sender-Auth: 9RvBeeUPVOV-6T1GPpfABbGEGdQ
Message-ID: <CADJ9OA9HLC=883ONWN2davbAkMStfjy1sLpV6ksgkudnqVdR5w@mail.gmail.com>
Subject: Re: Please double-check your group's archive in the web-based email list archive tool
To: Roger Marshall <RMarshall@telecomsys.com>
Content-Type: multipart/alternative; boundary=bcaec543079a58db7a04f0a67515
Cc: "<wgchairs@ietf.org>" <wgchairs@ietf.org>, Robert Sparks <rjsparks@nostrum.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 17:20:35 -0000

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

Looks good for 6TiSCH. I really like the interface, this is a great
improvement.
Thomas


On Thu, Jan 23, 2014 at 9:04 AM, Roger Marshall <RMarshall@telecomsys.com>wrote:

> ECRIT content looks like it's in there, the tool looks really good.
>
> I did spot a few things, so I logged a couple of tickets on the subject
> (search) and group (default display) features at:
> http://trac.tools.ietf.org/tools/ietfdb
>
> -roger.
>
> -----Original Message-----
> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of Robert
> Sparks
> Sent: Wednesday, January 22, 2014 1:50 PM
> To: <wgchairs@ietf.org>
> Subject: Please double-check your group's archive in the web-based email
> list archive tool
>
> Chairs -
>
> If you have not already done so, please look briefly at your lists in the
> new tool and make sure you see what you expect.
>
> You can browse quickly to them with a URL like:
>
> <https://mailarchive.ietf.org/arch/search/?email_list=stir>
>
> Click the date column header twice (the first time will give you a
> most-recent to least-recent view, and the second the reverse), or jump
> straight to a URL like <
> https://mailarchive.ietf.org/arch/search/?email_list=stir&so=date>
> and check that the archive goes back as far as you expect.
>
> Note that you can pull the division between the message list pane and the
> message preview pane down to allow you to see more of the messages in the
> list at one time.
>
> If you discover something that needs attention, please file a ticket at <
> http://trac.tools.ietf.org/tools/ietfdb/newticket>
>
> RjS
>
> CONFIDENTIALITY NOTICE: The information contained in this message may be
> privileged and/or confidential. If you are not the intended recipient, or
> responsible for delivering this message to the intended recipient, any
> review, forwarding, dissemination, distribution or copying of this
> communication or any attachment(s) is strictly prohibited. If you have
> received this message in error, please notify the sender immediately, and
> delete it and all attachments from your computer and network.
>

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

<div dir=3D"ltr">Looks good for 6TiSCH. I really like the interface, this i=
s a great improvement.<div>Thomas</div></div><div class=3D"gmail_extra"><br=
><br><div class=3D"gmail_quote">On Thu, Jan 23, 2014 at 9:04 AM, Roger Mars=
hall <span dir=3D"ltr">&lt;<a href=3D"mailto:RMarshall@telecomsys.com" targ=
et=3D"_blank">RMarshall@telecomsys.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">ECRIT content looks like it&#39;s in there, =
the tool looks really good.<br>
<br>
I did spot a few things, so I logged a couple of tickets on the subject (se=
arch) and group (default display) features at:<br>
<a href=3D"http://trac.tools.ietf.org/tools/ietfdb" target=3D"_blank">http:=
//trac.tools.ietf.org/tools/ietfdb</a><br>
<br>
-roger.<br>
<div><div class=3D"h5"><br>
-----Original Message-----<br>
From: WGChairs [mailto:<a href=3D"mailto:wgchairs-bounces@ietf.org">wgchair=
s-bounces@ietf.org</a>] On Behalf Of Robert Sparks<br>
Sent: Wednesday, January 22, 2014 1:50 PM<br>
To: &lt;<a href=3D"mailto:wgchairs@ietf.org">wgchairs@ietf.org</a>&gt;<br>
Subject: Please double-check your group&#39;s archive in the web-based emai=
l list archive tool<br>
<br>
Chairs -<br>
<br>
If you have not already done so, please look briefly at your lists in the n=
ew tool and make sure you see what you expect.<br>
<br>
You can browse quickly to them with a URL like:<br>
<br>
&lt;<a href=3D"https://mailarchive.ietf.org/arch/search/?email_list=3Dstir"=
 target=3D"_blank">https://mailarchive.ietf.org/arch/search/?email_list=3Ds=
tir</a>&gt;<br>
<br>
Click the date column header twice (the first time will give you a most-rec=
ent to least-recent view, and the second the reverse), or jump straight to =
a URL like &lt;<a href=3D"https://mailarchive.ietf.org/arch/search/?email_l=
ist=3Dstir&amp;so=3Ddate" target=3D"_blank">https://mailarchive.ietf.org/ar=
ch/search/?email_list=3Dstir&amp;so=3Ddate</a>&gt;<br>


and check that the archive goes back as far as you expect.<br>
<br>
Note that you can pull the division between the message list pane and the m=
essage preview pane down to allow you to see more of the messages in the li=
st at one time.<br>
<br>
If you discover something that needs attention, please file a ticket at &lt=
;<a href=3D"http://trac.tools.ietf.org/tools/ietfdb/newticket" target=3D"_b=
lank">http://trac.tools.ietf.org/tools/ietfdb/newticket</a>&gt;<br>
<br>
RjS<br>
<br>
</div></div>CONFIDENTIALITY NOTICE: The information contained in this messa=
ge may be privileged and/or confidential. If you are not the intended recip=
ient, or responsible for delivering this message to the intended recipient,=
 any review, forwarding, dissemination, distribution or copying of this com=
munication or any attachment(s) is strictly prohibited. If you have receive=
d this message in error, please notify the sender immediately, and delete i=
t and all attachments from your computer and network.<br>


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

--bcaec543079a58db7a04f0a67515--

From fluffy@cisco.com  Thu Jan 23 09:25:28 2014
Return-Path: <fluffy@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EAEA11A0097; Thu, 23 Jan 2014 09:25:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -115.036
X-Spam-Level: 
X-Spam-Status: No, score=-115.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2AsioC8Awrcm; Thu, 23 Jan 2014 09:25:22 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 898531A008E; Thu, 23 Jan 2014 09:25:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4744; q=dns/txt; s=iport; t=1390497922; x=1391707522; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=PyVmN5+k3lP+L1rXDge0tNjsPJ7uWr2n3N/v1Mk8mhU=; b=TNy55b0FsOrAzuKdNBt4PbAF3U0VdwswyBATy/V+429x0Hnmx4aY2/nJ Ueh5UnBarq5X3MexXnP7rWSue+l7PzIn/ONgYiB2hMhc0XbLlgb4PBhqw EFqgG9q5ZC2adsn8ouaO0YmcY3WQI+8/RF/DXyWEoAC5qb67GK9c81NXs U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgsFAHFP4VKtJXG//2dsb2JhbABYA4MMOFa7e4ETFnSCJQEBAQMBeQULAgEIEgYuMhcOAgQBDQUJh3QIDcYIF40PgR0hIxACBRGDE4EUBJgjgTKQZoMtgio
X-IronPort-AV: E=Sophos;i="4.95,706,1384300800"; d="scan'208";a="299340950"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-4.cisco.com with ESMTP; 23 Jan 2014 17:25:21 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id s0NHPLIu006171 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 23 Jan 2014 17:25:21 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.76]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.03.0123.003; Thu, 23 Jan 2014 11:25:20 -0600
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Russ Housley <housley@vigilsec.com>, Jari Arkko <jari.arkko@piuha.net>
Subject: Re: Problem with new Note Well
Thread-Topic: Problem with new Note Well
Thread-Index: AQHPGFpx6U6AfiunqkWV7evY6wlIJZqS9A2A
Date: Thu, 23 Jan 2014 17:25:20 +0000
Message-ID: <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com>
In-Reply-To: <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <89BD4672CA5554479439815A68F00696@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 17:25:28 -0000

This new note well is a real problem for me and  I can not register without=
 clicking "I agree" to it. It is not consistent with the BCPs. The problem =
is the line that says

	=95 If you are aware that any contribution (something written, said, or di=
scussed in any IETF context) is covered by patents or patent applications, =
you must disclose that fact.

I do not agree to that - I can=92t given my NDA with my employer does not a=
llow me to disclose confidential information. Yes, I realize there is some =
weasel words near the top that say "Exceptions may apply." but that does no=
t help me. When you are testifying in court on patents, credibility is incr=
edibly important. You can not have the lawyers on the other side saying tha=
t you clicked yes I agree to the line above but you did not actually do wha=
t that lines says. You may think this does to matter but the exact topic of=
 how Cisco employees deal with IPR at the IETF is a topic that I have testi=
fied on in an East Texas court so this really does happen and really does h=
appen to me. It may happen to you next and you will be much happier if you =
say what you mean and mean what you say. This new note well fails that test=
.=20

I realize some people would like to change the IETF policy to be that you d=
o have to do what that line says but I do not think that is a change the IE=
SG can make without IETF updating the BCP or at least having IETF consensus=
 on the change. I would respectfully ask the IESG to change this line to so=
mething that is still brief but that people can agree with it. Simply addin=
g something like "or not contribute to the discussion on that contribution"=
 would probably solve this problem for me.=20

Thank you,=20

Cullen

I will note that above line is not consistent with Cisco employment contrac=
ts and if we can not resolve this I will be asking Cisco legal to inform Ci=
sco employees they can not agree with this without violating their employme=
nt agreement.=20



On Jan 23, 2014, at 9:44 AM, Russ Housley <housley@vigilsec.com> wrote:

> It seems that the shorter one is now being used on the IETF web site:
> http://www.ietf.org/about/note-well.html
>=20
>=20
> On Jan 8, 2014, at 3:57 PM, Mary Barnes wrote:
>=20
>> Personally, I've never seen significant value in this shorter note well =
and while others have been using this new text for the past few meetings, I=
've stuck to the old.   Now that this is considered the recommended note we=
ll for chairs to use, I guess I'll use it.  But, I personally think accurac=
y should trump brevity.  I think the "must" in that bullet  ought to at lea=
st be a should and that adding an "otherwise, one should not contribute to =
or participate in any related IETF activities." would add more value.  =20
>>=20
>> Mary.
>>=20
>>=20
>> On Wed, Jan 8, 2014 at 1:17 PM, Bradner, Scott <sob@harvard.edu> wrote:
>> you are correct - we (Barry, the IESG & me) discussed this before the IE=
SG approved this text - they felt that
>> being brief was more important than being fully accurate (or at least th=
at is the way I expressed it)
>>=20
>> Scott
>>=20
>> Scott O Bradner
>> Senior Technology Consultant
>>=20
>> Harvard University Information Technology
>> Innovation & Architecture
>> (P) +1 (617) 495 3864
>> 8 Story St, room 5014
>> Cambridge, MA 02138
>>=20
>>=20
>>=20
>> On Jan 8, 2014, at 2:13 PM, Cullen Jennings (fluffy) <fluffy@cisco.com> =
wrote:
>>=20
>> >
>> >
>> > On Dec 16, 2013, at 12:56 PM, Barry Leiba <barryleiba@computer.org> wr=
ote:
>> >
>> >> The IESG has made final edits to the updated Note Well statement, and
>> >> it has been officially updated:
>> >> http://www.ietf.org/about/note-well.html
>> >>
>> >> I have just uploaded the final versions of the Note Well meeting
>> >> slides, attached to the bottom of the WG Chairs wiki:
>> >> http://wiki.tools.ietf.org/group/wgchairs/wiki/WikiStart
>> >>
>> >> Please use this new version now, and please remember that as you
>> >> prepare slides for the London meeting.
>> >>
>> >> Barry
>> >
>> >
>> > The new note well says
>> >
>> >       =95 If you are aware that any contribution (something written, s=
aid, or discussed in any IETF context) is covered by patents or patent appl=
ications, you must disclose that fact.
>> >
>> > Is that true?  Or is it missing something along the lines of section y=
 of BCP 79 such as
>> >
>> >   or must not contribute to or participate in IETF activities with
>> >   respect to technologies that he or she reasonably and personally
>> >   knows to be Covered by IPR which he or she will not disclose.
>> >
>> > Thanks, Cullen
>=20


From sbanks@akamai.com  Thu Jan 23 09:40:55 2014
Return-Path: <sbanks@akamai.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AE691A002F for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 09:40:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z2WzyerD802V for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 09:40:50 -0800 (PST)
Received: from prod-mail-xrelay06.akamai.com (prod-mail-xrelay06.akamai.com [96.6.114.98]) by ietfa.amsl.com (Postfix) with ESMTP id 580511A00C5 for <wgchairs@ietf.org>; Thu, 23 Jan 2014 09:40:50 -0800 (PST)
Received: from prod-mail-xrelay06.akamai.com (localhost.localdomain [127.0.0.1]) by postfix.imss70 (Postfix) with ESMTP id 30D0B165632; Thu, 23 Jan 2014 17:40:49 +0000 (GMT)
Received: from prod-mail-relay03.akamai.com (prod-mail-relay03.akamai.com [172.27.8.26]) by prod-mail-xrelay06.akamai.com (Postfix) with ESMTP id 2490816562F; Thu, 23 Jan 2014 17:40:49 +0000 (GMT)
Received: from ustx2ex-cashub.dfw01.corp.akamai.com (ustx2ex-cashub5.dfw01.corp.akamai.com [172.27.25.71]) by prod-mail-relay03.akamai.com (Postfix) with ESMTP id 1B2B72FD6B; Thu, 23 Jan 2014 17:40:49 +0000 (GMT)
Received: from USMBX2.msg.corp.akamai.com ([169.254.1.225]) by ustx2ex-cashub5.dfw01.corp.akamai.com ([172.27.25.71]) with mapi; Thu, 23 Jan 2014 11:40:48 -0600
From: "Banks, Sarah" <sbanks@akamai.com>
To: Robert Sparks <rjsparks@nostrum.com>, "<wgchairs@ietf.org>" <wgchairs@ietf.org>
Date: Thu, 23 Jan 2014 11:40:46 -0600
Subject: Re: Please double-check your group's archive in the web-based email list archive tool
Thread-Topic: Please double-check your group's archive in the web-based email list archive tool
Thread-Index: Ac8YYkAHCdd/aSq6TEucfyDpTxZdjA==
Message-ID: <CF0693EB.AAB%sbanks@akamai.com>
References: <52E03D0E.5060703@nostrum.com>
In-Reply-To: <52E03D0E.5060703@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.9.131030
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 17:40:55 -0000

SGkgUm9iZXJ0LA0KCUJNV0cgbG9va3MgZ3JlYXQ7IG91ciBhcmNoaXZlcyBnbyBiYWNrIHRvIDIw
MDEsIGJ1dCB0aGF0J3MgcHJvYmFibHkgT0suDQpUaGUgaW50ZXJmYWNlIGlzIGF3ZXNvbWUhIFRo
YW5rcyENCg0KUmVnYXJkcywNClNhcmFoDQoNCk9uIDEvMjIvMTQsIDE6NTAgUE0sICJSb2JlcnQg
U3BhcmtzIiA8cmpzcGFya3NAbm9zdHJ1bS5jb20+IHdyb3RlOg0KDQo+Q2hhaXJzIC0NCj4NCj5J
ZiB5b3UgaGF2ZSBub3QgYWxyZWFkeSBkb25lIHNvLCBwbGVhc2UgbG9vayBicmllZmx5IGF0IHlv
dXIgbGlzdHMgaW4NCj50aGUgbmV3IHRvb2wgYW5kIG1ha2Ugc3VyZSB5b3Ugc2VlIHdoYXQgeW91
IGV4cGVjdC4NCj4NCj5Zb3UgY2FuIGJyb3dzZSBxdWlja2x5IHRvIHRoZW0gd2l0aCBhIFVSTCBs
aWtlOg0KPg0KPjxodHRwczovL21haWxhcmNoaXZlLmlldGYub3JnL2FyY2gvc2VhcmNoLz9lbWFp
bF9saXN0PXN0aXI+DQo+DQo+Q2xpY2sgdGhlIGRhdGUgY29sdW1uIGhlYWRlciB0d2ljZSAodGhl
IGZpcnN0IHRpbWUgd2lsbCBnaXZlIHlvdSBhDQo+bW9zdC1yZWNlbnQgdG8gbGVhc3QtcmVjZW50
IHZpZXcsIGFuZCB0aGUgc2Vjb25kIHRoZSByZXZlcnNlKSwNCj5vciBqdW1wIHN0cmFpZ2h0IHRv
IGEgVVJMIGxpa2UNCj48aHR0cHM6Ly9tYWlsYXJjaGl2ZS5pZXRmLm9yZy9hcmNoL3NlYXJjaC8/
ZW1haWxfbGlzdD1zdGlyJnNvPWRhdGU+DQo+YW5kIGNoZWNrIHRoYXQgdGhlIGFyY2hpdmUgZ29l
cyBiYWNrIGFzIGZhciBhcyB5b3UgZXhwZWN0Lg0KPg0KPk5vdGUgdGhhdCB5b3UgY2FuIHB1bGwg
dGhlIGRpdmlzaW9uIGJldHdlZW4gdGhlIG1lc3NhZ2UgbGlzdCBwYW5lIGFuZA0KPnRoZSBtZXNz
YWdlIHByZXZpZXcgcGFuZSBkb3duIHRvIGFsbG93IHlvdSB0byBzZWUgbW9yZSBvZiB0aGUgbWVz
c2FnZXMNCj5pbiB0aGUgbGlzdCBhdCBvbmUgdGltZS4NCj4NCj5JZiB5b3UgZGlzY292ZXIgc29t
ZXRoaW5nIHRoYXQgbmVlZHMgYXR0ZW50aW9uLCBwbGVhc2UgZmlsZSBhIHRpY2tldCBhdA0KPjxo
dHRwOi8vdHJhYy50b29scy5pZXRmLm9yZy90b29scy9pZXRmZGIvbmV3dGlja2V0Pg0KPg0KPlJq
Uw0KDQo=

From gsalguei@cisco.com  Thu Jan 23 09:55:56 2014
Return-Path: <gsalguei@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF8F51A00FC for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 09:55:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.036
X-Spam-Level: 
X-Spam-Status: No, score=-15.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GB_VsJUcxQfa for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 09:55:52 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 543161A00A7 for <wgchairs@ietf.org>; Thu, 23 Jan 2014 09:55:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1406; q=dns/txt; s=iport; t=1390499752; x=1391709352; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=eT3n4EqLdd6kQOhggo0apbjSuhGfrZtRTmMoRQkDPxE=; b=EnRwPHsPQmQ9pql+32f7H355zZjiDGwqVNfDmOR3WO+XUFL4910gpYsh TkD2kgK3moo9a7A5IYuXOS+1SLEZ2rUGMWm7vJK/48JAIRK81IvVXd7tM 04sA7UUOAucYNI9Sd4svG1fB80SDcL+99op/zQO8+Hcor0O0Z8GTdbY6Z 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgsFADJX4VKtJXHA/2dsb2JhbABbgww4Vrt7gRMWdIIlAQEBAwE6PwULAgEIDgoeEDIlAgQOBYd9CA3FcxeOHhEBCxIzB4MkgRQBA5gjgTKQZoFvgT6BcTk
X-IronPort-AV: E=Sophos;i="4.95,707,1384300800"; d="scan'208";a="299252339"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-7.cisco.com with ESMTP; 23 Jan 2014 17:55:51 +0000
Received: from xhc-aln-x12.cisco.com (xhc-aln-x12.cisco.com [173.36.12.86]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id s0NHtpx4025856 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 23 Jan 2014 17:55:51 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.37]) by xhc-aln-x12.cisco.com ([173.36.12.86]) with mapi id 14.03.0123.003; Thu, 23 Jan 2014 11:55:50 -0600
From: "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>
To: Robert Sparks <rjsparks@nostrum.com>
Subject: Re: Please double-check your group's archive in the web-based email list archive tool
Thread-Topic: Please double-check your group's archive in the web-based email list archive tool
Thread-Index: AQHPF7v2jLeVcGII+EaiimrIf5RZNpqS+ZsAgAAENQA=
Date: Thu, 23 Jan 2014 17:55:50 +0000
Message-ID: <28D170D7-DAB9-45A9-A08E-CE9AA678CF16@cisco.com>
References: <52E03D0E.5060703@nostrum.com> <CF0693EB.AAB%sbanks@akamai.com>
In-Reply-To: <CF0693EB.AAB%sbanks@akamai.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.116.132.51]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <C7DFFFE0DFFC6E478E667D11B58ACF60@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<wgchairs@ietf.org>" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 17:55:56 -0000

Great improvement in an area where we were woefully lacking. Thanks, Robert=
!

INSIPID content appears to be just fine.

Cheers,

Gonzalo


On Jan 23, 2014, at 12:40 PM, Banks, Sarah <sbanks@akamai.com> wrote:

> Hi Robert,
> 	BMWG looks great; our archives go back to 2001, but that's probably OK.
> The interface is awesome! Thanks!
>=20
> Regards,
> Sarah
>=20
> On 1/22/14, 1:50 PM, "Robert Sparks" <rjsparks@nostrum.com> wrote:
>=20
>> Chairs -
>>=20
>> If you have not already done so, please look briefly at your lists in
>> the new tool and make sure you see what you expect.
>>=20
>> You can browse quickly to them with a URL like:
>>=20
>> <https://mailarchive.ietf.org/arch/search/?email_list=3Dstir>
>>=20
>> Click the date column header twice (the first time will give you a
>> most-recent to least-recent view, and the second the reverse),
>> or jump straight to a URL like
>> <https://mailarchive.ietf.org/arch/search/?email_list=3Dstir&so=3Ddate>
>> and check that the archive goes back as far as you expect.
>>=20
>> Note that you can pull the division between the message list pane and
>> the message preview pane down to allow you to see more of the messages
>> in the list at one time.
>>=20
>> If you discover something that needs attention, please file a ticket at
>> <http://trac.tools.ietf.org/tools/ietfdb/newticket>
>>=20
>> RjS
>=20


From sob@harvard.edu  Thu Jan 23 09:58:27 2014
Return-Path: <sob@harvard.edu>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BA271A01A1; Thu, 23 Jan 2014 09:58:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.135
X-Spam-Level: 
X-Spam-Status: No, score=-3.135 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KtkdGqoyV1db; Thu, 23 Jan 2014 09:58:19 -0800 (PST)
Received: from ackroyd.harvard.edu (ackroyd.harvard.edu [128.103.208.29]) by ietfa.amsl.com (Postfix) with ESMTP id 72E121A0189; Thu, 23 Jan 2014 09:58:13 -0800 (PST)
Received: from ENTWEDGE0000003.university.harvard.edu (entwedge0000003.university.harvard.edu [10.35.202.50]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ackroyd.harvard.edu (Postfix) with ESMTP id 9EF76E8EEF; Thu, 23 Jan 2014 12:58:12 -0500 (EST)
Received: from ENTWHUBT0000000.university.harvard.edu (10.32.8.201) by entwedge0000003.university.harvard.edu (10.35.202.50) with Microsoft SMTP Server (TLS) id 14.3.146.0; Thu, 23 Jan 2014 12:58:01 -0500
Received: from ENTWEXMB0000008.university.harvard.edu ([169.254.1.46]) by ENTWHUBT0000000.university.harvard.edu ([10.32.8.201]) with mapi id 14.03.0146.000; Thu, 23 Jan 2014 12:58:12 -0500
From: "Bradner, Scott" <sob@harvard.edu>
To: Mike StJohns <mstjohns@comcast.net>
Subject: Re: Problem with new Note Well
Thread-Topic: Problem with new Note Well
Thread-Index: AQHPGGAibruxKTnnVUu65PwElpA1yg==
Date: Thu, 23 Jan 2014 17:58:12 +0000
Message-ID: <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu>
In-Reply-To: <20140123175052.CC016E8F3D@ackroyd.harvard.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [128.103.229.199]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <3EE725A95AB8144AB3E380EC9DB859D7@Exchange.university.harvard.edu>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 17:58:27 -0000

the actual rules are
	1/ if you know of any of your IPR in a contribution you make, you must dis=
close
	2/ if you know of any of your IPR in any contribution from someone else an=
d you are participating in discussions
	    that involve that contribution, then you must disclose
	3/ if you know of any of your IPR in any contribution from someone else an=
d you are not participating in discussions
	    that involve that contribution, then you are requested to disclose

see - its not that hard to say this briefly

Scott

On Jan 23, 2014, at 12:49 PM, Michael StJohns <mstjohns@comcast.net> wrote:

> Is the issue the difference between "any contribution YOU MAKE" and "any =
contribution"?  E.g. if you happen to hear someone discussing something you=
 think is covered by patent, you can't say anything, but conversely, if YOU=
 are making a contribution that's covered by patent then the NDA doesn't ap=
ply (because you have approval to make the contribution and disclosure).
>=20
> Mike
>=20
>=20
> At 12:25 PM 1/23/2014, Cullen Jennings (fluffy) wrote:
>=20
>> This new note well is a real problem for me and  I can not register with=
out clicking "I agree" to it. It is not consistent with the BCPs. The probl=
em is the line that says
>>=20
>>       . If you are aware that any contribution (something written, said,=
 or discussed in any IETF context) is covered by patents or patent applicat=
ions, you must disclose that fact.
>>=20
>> I do not agree to that - I can't given my NDA with my employer does not =
allow me to disclose confidential information. Yes, I realize there is some=
 weasel words near the top that say "Exceptions may apply." but that does n=
ot help me. When you are testifying in court on patents, credibility is inc=
redibly important. You can not have the lawyers on the other side saying th=
at you clicked yes I agree to the line above but you did not actually do wh=
at that lines says. You may think this does to matter but the exact topic o=
f how Cisco employees deal with IPR at the IETF is a topic that I have test=
ified on in an East Texas court so this really does happen and really does =
happen to me. It may happen to you next and you will be much happier if you=
 say what you mean and mean what you say. This new note well fails that tes=
t.=20
>>=20
>> I realize some people would like to change the IETF policy to be that yo=
u do have to do what that line says but I do not think that is a change the=
 IESG can make without IETF updating the BCP or at least having IETF consen=
sus on the change. I would respectfully ask the IESG to change this line to=
 something that is still brief but that people can agree with it. Simply ad=
ding something like "or not contribute to the discussion on that contributi=
on" would probably solve this problem for me.=20
>>=20
>> Thank you,=20
>>=20
>> Cullen
>>=20
>> I will note that above line is not consistent with Cisco employment cont=
racts and if we can not resolve this I will be asking Cisco legal to inform=
 Cisco employees they can not agree with this without violating their emplo=
yment agreement.=20
>>=20
>>=20
>>=20
>> On Jan 23, 2014, at 9:44 AM, Russ Housley <housley@vigilsec.com> wrote:
>>=20
>>> It seems that the shorter one is now being used on the IETF web site:
>>> http://www.ietf.org/about/note-well.html
>>>=20
>>>=20
>>> On Jan 8, 2014, at 3:57 PM, Mary Barnes wrote:
>>>=20
>>>> Personally, I've never seen significant value in this shorter note wel=
l and while others have been using this new text for the past few meetings,=
 I've stuck to the old.   Now that this is considered the recommended note =
well for chairs to use, I guess I'll use it.  But, I personally think accur=
acy should trump brevity.  I think the "must" in that bullet  ought to at l=
east be a should and that adding an "otherwise, one should not contribute t=
o or participate in any related IETF activities." would add more value.  =20
>>>>=20
>>>> Mary.
>>>>=20
>>>>=20
>>>> On Wed, Jan 8, 2014 at 1:17 PM, Bradner, Scott <sob@harvard.edu> wrote=
:
>>>> you are correct - we (Barry, the IESG & me) discussed this before the =
IESG approved this text - they felt that
>>>> being brief was more important than being fully accurate (or at least =
that is the way I expressed it)
>>>>=20
>>>> Scott
>>>>=20
>>>> Scott O Bradner
>>>> Senior Technology Consultant
>>>>=20
>>>> Harvard University Information Technology
>>>> Innovation & Architecture
>>>> (P) +1 (617) 495 3864
>>>> 8 Story St, room 5014
>>>> Cambridge, MA 02138
>>>>=20
>>>>=20
>>>>=20
>>>> On Jan 8, 2014, at 2:13 PM, Cullen Jennings (fluffy) <fluffy@cisco.com=
> wrote:
>>>>=20
>>>>>=20
>>>>>=20
>>>>> On Dec 16, 2013, at 12:56 PM, Barry Leiba <barryleiba@computer.org> w=
rote:
>>>>>=20
>>>>>> The IESG has made final edits to the updated Note Well statement, an=
d
>>>>>> it has been officially updated:
>>>>>> http://www.ietf.org/about/note-well.html
>>>>>>=20
>>>>>> I have just uploaded the final versions of the Note Well meeting
>>>>>> slides, attached to the bottom of the WG Chairs wiki:
>>>>>> http://wiki.tools.ietf.org/group/wgchairs/wiki/WikiStart
>>>>>>=20
>>>>>> Please use this new version now, and please remember that as you
>>>>>> prepare slides for the London meeting.
>>>>>>=20
>>>>>> Barry
>>>>>=20
>>>>>=20
>>>>> The new note well says
>>>>>=20
>>>>>      . If you are aware that any contribution (something written, sai=
d, or discussed in any IETF context) is covered by patents or patent applic=
ations, you must disclose that fact.
>>>>>=20
>>>>> Is that true?  Or is it missing something along the lines of section =
y of BCP 79 such as
>>>>>=20
>>>>>  or must not contribute to or participate in IETF activities with
>>>>>  respect to technologies that he or she reasonably and personally
>>>>>  knows to be Covered by IPR which he or she will not disclose.
>>>>>=20
>>>>> Thanks, Cullen
>>>=20
>=20
>=20


From bensons@queuefull.net  Thu Jan 23 09:59:13 2014
Return-Path: <bensons@queuefull.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 010891A01B8 for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 09:59:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ye6xoJyz2VvZ for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 09:59:02 -0800 (PST)
Received: from mail-bk0-f53.google.com (mail-bk0-f53.google.com [209.85.214.53]) by ietfa.amsl.com (Postfix) with ESMTP id 10FF01A0185 for <wgchairs@ietf.org>; Thu, 23 Jan 2014 09:58:58 -0800 (PST)
Received: by mail-bk0-f53.google.com with SMTP id my13so533563bkb.26 for <wgchairs@ietf.org>; Thu, 23 Jan 2014 09:58:57 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type; bh=9yBOtYWKqw5Xv+v8P+YubOvsFmJ+QEHRilxwJSNBFS8=; b=ePjt96QvamGjjLR1rzlU+j5Pdfz5WNT9Op2GHxzsmb7NQ2dYOvUBpI5TumOYMVzLj1 ui+bLghkvMMWj3lgVdTIx1XCjXWsMP+vkMrjMBLNdl7pxfSxbpvp3VolPAmXowvKocJr XdWH+o1aoctLle82k68kVki2qKFVXqMb+z/+po17qXeYeaDvLwmIIWzQZSSFdl62QDyy ykX9my+0aRbMLtcdIkYkK7lFnTK47lLv5LgEEeGKm8phYIoMrTWAZ5fnglgNEMOcAaUr yOvNOBduQ7uz4X6mfVA0IfODVxE9Etbo1fDIV7qEXq31cNYIeauRdyuqriGuqFX21UNq VKPQ==
X-Gm-Message-State: ALoCoQkkbhTf9bVv3LXqr80uEFVxdZwp2TlVyopwJB/k1cOoWWxL7H98zfHFVk1Ozh19CUp2cr2/
X-Received: by 10.204.236.134 with SMTP id kk6mr29221bkb.188.1390499937506; Thu, 23 Jan 2014 09:58:57 -0800 (PST)
Received: from wasteland.neohaven.net ([2602:100:4473:9afe:b569:8cfc:3806:f9]) by mx.google.com with ESMTPSA id dj5sm9804004bkc.7.2014.01.23.09.58.55 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 23 Jan 2014 09:58:56 -0800 (PST)
Message-ID: <52E1585A.9020506@queuefull.net>
Date: Thu, 23 Jan 2014 12:58:50 -0500
From: Benson Schliesser <bensons@queuefull.net>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: Robert Sparks <rjsparks@nostrum.com>,  "<wgchairs@ietf.org>" <wgchairs@ietf.org>
Subject: Re: Please double-check your group's archive in the web-based email list archive tool
References: <52E03D0E.5060703@nostrum.com> <CF0693EB.AAB%sbanks@akamai.com>
In-Reply-To: <CF0693EB.AAB%sbanks@akamai.com>
Content-Type: multipart/alternative; boundary="------------040607030909090407050207"
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 17:59:13 -0000

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

I browsed through the NVO3 archive, and it looks good. The web interface 
is nice, and I'm looking forward to IMAP support.

One minor issue: The page's title is set to a generic "Mail Archive", 
rather than something specific to the list being viewed. This makes it 
difficult to navigate multiple archives (e.g. in browser tabs), create 
browser bookmarks, etc. I opened an enhancement ticket at 
http://trac.tools.ietf.org/tools/ietfdb/ticket/1258 for this.

Thanks,
-Benson

>
> Robert Sparks <mailto:rjsparks@nostrum.com>
> January 22, 2014 4:50 PM
> Chairs -
>
> If you have not already done so, please look briefly at your lists in 
> the new tool and make sure you see what you expect.
>
> You can browse quickly to them with a URL like:
>
> <https://mailarchive.ietf.org/arch/search/?email_list=stir>
>
> Click the date column header twice (the first time will give you a 
> most-recent to least-recent view, and the second the reverse),
> or jump straight to a URL like
> <https://mailarchive.ietf.org/arch/search/?email_list=stir&so=date>
> and check that the archive goes back as far as you expect.
>
> Note that you can pull the division between the message list pane and 
> the message preview pane down to allow you to see more of the messages 
> in the list at one time.
>
> If you discover something that needs attention, please file a ticket at
> <http://trac.tools.ietf.org/tools/ietfdb/newticket>
>
> RjS

--------------040607030909090407050207
Content-Type: multipart/related;
 boundary="------------000608090101000706070504"


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

<html><head>
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
</head><body bgcolor="#FFFFFF" text="#000000">I browsed through the NVO3
 archive, and it looks good. The web interface is nice, and I'm looking 
forward to IMAP support.<br>
<br>
One minor issue: The page's title is set to a generic "Mail Archive", 
rather than something specific to the list being viewed. This makes it 
difficult to navigate multiple archives (e.g. in browser tabs), create 
browser bookmarks, etc. I opened an enhancement ticket at 
<a class="moz-txt-link-freetext" href="http://trac.tools.ietf.org/tools/ietfdb/ticket/1258">http://trac.tools.ietf.org/tools/ietfdb/ticket/1258</a> for this.<br>
<br>
Thanks,<br>
-Benson<br>
<br>
<blockquote style="border: 0px none;" 
cite="mid:CF0693EB.AAB%25sbanks@akamai.com" type="cite">
  <div style="color:#888888;margin-left:24px;margin-right:24px;" 
__pbrmquotes="true" class="__pbConvBody"><div><!----><br></div></div>
  <div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div 
style="display:table;width:100%;border-top:1px solid 
#EDEEF0;padding-top:5px"> 	<div 
style="display:table-cell;vertical-align:middle;padding-right:6px;"><img
 photoaddress="rjsparks@nostrum.com" photoname="Robert Sparks" 
src="cid:part1.08000904.09080108@queuefull.net" 
name="compose-unknown-contact.jpg" height="25px" width="25px"></div>   <div
 
style="display:table-cell;white-space:nowrap;vertical-align:middle;width:100%">
   	<a moz-do-not-send="true" href="mailto:rjsparks@nostrum.com" 
style="color:#737F92 
!important;padding-right:6px;font-weight:bold;text-decoration:none 
!important;">Robert Sparks</a></div>   <div 
style="display:table-cell;white-space:nowrap;vertical-align:middle;">   
  <font color="#9FA2A5"><span style="padding-left:6px">January 22, 2014 
4:50 PM</span></font></div></div></div>
  <div style="color:#888888;margin-left:24px;margin-right:24px;" 
__pbrmquotes="true" class="__pbConvBody">Chairs -
<br>
<br>If you have not already done so, please look briefly at your lists 
in 
the new tool and make sure you see what you expect.
<br>
<br>You can browse quickly to them with a URL like:
<br>
<br><a class="moz-txt-link-rfc2396E" href="https://mailarchive.ietf.org/arch/search/?email_list=stir">&lt;https://mailarchive.ietf.org/arch/search/?email_list=stir&gt;</a>
<br>
<br>Click the date column header twice (the first time will give you a 
most-recent to least-recent view, and the second the reverse),
<br>or jump straight to a URL like
<br><a class="moz-txt-link-rfc2396E" href="https://mailarchive.ietf.org/arch/search/?email_list=stir&amp;so=date">&lt;https://mailarchive.ietf.org/arch/search/?email_list=stir&amp;so=date&gt;</a>
<br>and check that the archive goes back as far as you expect.
<br>
<br>Note that you can pull the division between the message list pane 
and 
the message preview pane down to allow you to see more of the messages 
in the list at one time.
<br>
<br>If you discover something that needs attention, please file a ticket
 at
<br><a class="moz-txt-link-rfc2396E" href="http://trac.tools.ietf.org/tools/ietfdb/newticket">&lt;http://trac.tools.ietf.org/tools/ietfdb/newticket&gt;</a>
<br>
<br>RjS
<br></div>
</blockquote>
</body></html>

--------------000608090101000706070504
Content-Type: image/jpeg; x-apple-mail-type=stationery;
 name="compose-unknown-contact.jpg"
Content-Transfer-Encoding: base64
Content-ID: <part1.08000904.09080108@queuefull.net>
Content-Disposition: inline;
 filename="compose-unknown-contact.jpg"

/9j/4AAQSkZJRgABAQEARwBHAAD/2wBDAAEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEC
AQEBAQEBAgICAgICAgICAgICAgICAgICAgICAgICAgICAgL/2wBDAQEBAQEBAQICAgICAgIC
AgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgL/wAAR
CAAZABkDAREAAhEBAxEB/8QAGAAAAwEBAAAAAAAAAAAAAAAABgcICQr/xAA0EAABAwMCAgUK
BwAAAAAAAAACAQMEBQYRABITIQcUMUF2CBUXIjI2N0JRtVRWkZOV0dL/xAAYAQEAAwEAAAAA
AAAAAAAAAAADAAEEAv/EACQRAAICAAQGAwAAAAAAAAAAAAABAhEDMrHREyExM0FxgfDx/9oA
DAMBAAIRAxEAPwDuEt+gW/ULet6oVC3rfqNQqFv0OfPn1GhUqfOmzZtKZlS5UqZMaNwzNwiJ
VIl7eXLCaZIGwBl3TY8epPx2+jy2ZNPjvkwc9uhW8j7nCPhvOsQliYIeS7cvCpp8o50qwrC4
v3lsNSDbdmTEhvs2tahxpfV3WnmbbozJEw/gwdadbYExVRXKEKoSdvJcaOSqxE7/AAiX0gXx
+a69/JSf9alIlste0VzaNpeFrcT9KKymotyiaZ0KRCnzacoE7Kjzn4gi2KqUh3jqDHDHv4mR
UfruTWlMzlVUKIVNp9GguEJnAh0+IZjyAiisgyRDnu5azS8miKqjOTVkKqS/psG37fo1Fbab
eg25b8eZPeFJBBJSjMG5HjMeyihnaauZwe4OGiju13GAcpOwBeN+U8/IkGbsiS8b7ryogmbz
hbyc9REROfZhERO5ETShjPtvpGqTUyLErytS4siSwx5x2tRH4hPOI0DkjZtaJtFxuVEbIUUi
yeNujlBUJGbJN6nM/Cyf2Hf60YgjvKA+NPSP4gT7axpcPtr51YWJnYn9dnAQWl722p4ot37y
zqnlfp6FrqbwawG8/9k=
--------------000608090101000706070504--

--------------040607030909090407050207--

From presnick@qti.qualcomm.com  Thu Jan 23 10:02:47 2014
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2914A1A00DF; Thu, 23 Jan 2014 10:02:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level: 
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sYCreSvAdGGi; Thu, 23 Jan 2014 10:02:43 -0800 (PST)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id 1A3EC1A0052; Thu, 23 Jan 2014 10:02:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1390500156; x=1422036156; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=mjlox8GK7GbC8nh/TP6foRKgkMuRFOZitdGRBDHnEmg=; b=ggFvQnJwumrAlFBmGPgNhHCh0wb+w9raZ1YTvrx0luVuJlCWzoMGGHgK g0ahMxWY1qDARIJ5HOC2G1n5Lnf1kPlxVJKSOSOon8IYrlOVDpgONn0OS V/2oquE496YJNA2f7RwydGamgQEw9xVJfT9Oq4zqU5MmRap2kXppp/MHb 0=;
X-IronPort-AV: E=McAfee;i="5400,1158,7327"; a="58459355"
Received: from ironmsg01-lv.qualcomm.com ([10.47.202.180]) by sabertooth01.qualcomm.com with ESMTP; 23 Jan 2014 10:02:36 -0800
X-IronPort-AV: E=McAfee;i="5400,1158,7327"; a="26198272"
Received: from nasanexhc02.na.qualcomm.com ([172.30.48.24]) by ironmsg01-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 23 Jan 2014 10:02:35 -0800
Received: from nasanexhc05.na.qualcomm.com (172.30.48.2) by NASANEXHC02.na.qualcomm.com (172.30.48.24) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 23 Jan 2014 10:02:35 -0800
Received: from presnick-mac.local (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.2) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 23 Jan 2014 10:02:34 -0800
Message-ID: <52E15937.8010600@qti.qualcomm.com>
Date: Thu, 23 Jan 2014 12:02:31 -0600
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Subject: Re: Problem with new Note Well
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com>
In-Reply-To: <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com>
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>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 18:02:47 -0000

On 1/23/14 11:25 AM, Cullen Jennings (fluffy) wrote:
> This new note well is a real problem for me and  I can not register without clicking "I agree" to it.

You are not asked to click "I agree" to any statement. You are asked to 
"Acknowledge" that you read it. And the statement says right at the top:

"This summary is only meant to point you in the right direction, and 
does not contain all the details. Exceptions may apply."

So by participating, there are things that you are agreeing to that are 
not on this page, and there are exceptions to things on this page that 
you don't have to agree to do.

The only thing that this page does is make you "Acknowledge" that you've 
got homework to do about rules for your participation.

pr

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


From fluffy@cisco.com  Thu Jan 23 10:07:13 2014
Return-Path: <fluffy@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 984781A0012; Thu, 23 Jan 2014 10:07:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -115.036
X-Spam-Level: 
X-Spam-Status: No, score=-115.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X2AWDFTAL-Qv; Thu, 23 Jan 2014 10:07:09 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id D62251A000A; Thu, 23 Jan 2014 10:07:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1175; q=dns/txt; s=iport; t=1390500429; x=1391710029; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=eDoZbefKl4CVsrsxiAvuUhu82cpqQ9W+8dxONZ4Nd7k=; b=UQEhTDfehJ7QCG2iFGQDQSzQ6AR5C1hsEfA7truXZV47pdxUOzKy8HXz JGzZCw7u+fBUdGK8CLHVhTyt91byGx+OA47uEgMV+GRpE/A+n0d4P0IBQ dBaILKyxNfexLMsNdy7IJ2mKpTcBFcDUwxplJ904Mhk/T1+HzXGRfvg0l M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgwFAGxZ4VKtJXG8/2dsb2JhbABYAxaCdjhWu3uBExZ0giUBAQEDAXkFCwIBCA4KLjIlAgQOBYd9CA3FeheOTSMQBxGDE4EUBIkQjxOSGIMtgio
X-IronPort-AV: E=Sophos;i="4.95,707,1384300800"; d="scan'208";a="299296652"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-3.cisco.com with ESMTP; 23 Jan 2014 18:07:08 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id s0NI77nG005078 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 23 Jan 2014 18:07:07 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.76]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.03.0123.003; Thu, 23 Jan 2014 12:07:07 -0600
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Problem with new Note Well
Thread-Topic: Problem with new Note Well
Thread-Index: AQHPGGVI6U6AfiunqkWV7evY6wlIJZqS/6QA
Date: Thu, 23 Jan 2014 18:07:07 +0000
Message-ID: <18480766-BA47-445B-8C75-5DD261F94A76@cisco.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <52E15937.8010600@qti.qualcomm.com>
In-Reply-To: <52E15937.8010600@qti.qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <46FFC73E42D86C4FAF1A35DA54BCA737@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 18:07:13 -0000

Pete,  what do you think "Acknowledge" means on a from like this? ( I will =
note it does not say "I Acknowledge I read this but may not agree with it" =
)



On Jan 23, 2014, at 11:02 AM, Pete Resnick <presnick@qti.qualcomm.com> wrot=
e:

> On 1/23/14 11:25 AM, Cullen Jennings (fluffy) wrote:
>> This new note well is a real problem for me and  I can not register with=
out clicking "I agree" to it.
>=20
> You are not asked to click "I agree" to any statement. You are asked to "=
Acknowledge" that you read it. And the statement says right at the top:
>=20
> "This summary is only meant to point you in the right direction, and does=
 not contain all the details. Exceptions may apply."
>=20
> So by participating, there are things that you are agreeing to that are n=
ot on this page, and there are exceptions to things on this page that you d=
on't have to agree to do.
>=20
> The only thing that this page does is make you "Acknowledge" that you've =
got homework to do about rules for your participation.
>=20
> pr
>=20
> --=20
> Pete Resnick<http://www.qualcomm.com/~presnick/>
> Qualcomm Technologies, Inc. - +1 (858)651-4478
>=20


From presnick@qti.qualcomm.com  Thu Jan 23 10:09:46 2014
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 829A21A000A; Thu, 23 Jan 2014 10:09:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level: 
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T1j8jkFwnM84; Thu, 23 Jan 2014 10:09:42 -0800 (PST)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id 1B8101A0028; Thu, 23 Jan 2014 10:09:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1390500581; x=1422036581; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=VQN4XO27kBoVTraJjoWJdXaBdupIUOHprzlMsgaKMfc=; b=k/YRRDUsgqGjgMn9ZA84nv21tSoUWYkrOAFpRdsB9/wdbgfcFaRw6yyH mRCus0dLKU8T+NbO0oBGxlNCdrRCCHYgnlVKyNvx34PImtJIeZeYajuau QDItBGm1ZGFEVJgnxEe0VeU3RmkrpipqXD3V/EWz5wL4TZeB66guAapns Y=;
X-IronPort-AV: E=McAfee;i="5400,1158,7327"; a="58557099"
Received: from ironmsg04-r.qualcomm.com ([172.30.46.18]) by sabertooth02.qualcomm.com with ESMTP; 23 Jan 2014 10:09:41 -0800
X-IronPort-AV: E=McAfee;i="5400,1158,7327"; a="672416311"
Received: from nasanexhc14.na.qualcomm.com ([172.30.48.23]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 23 Jan 2014 10:09:41 -0800
Received: from nasanexhc05.na.qualcomm.com (172.30.48.2) by nasanexhc14.na.qualcomm.com (172.30.48.23) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 23 Jan 2014 10:09:40 -0800
Received: from presnick-mac.local (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.2) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 23 Jan 2014 10:09:40 -0800
Message-ID: <52E15AE2.7030508@qti.qualcomm.com>
Date: Thu, 23 Jan 2014 12:09:38 -0600
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: "Bradner, Scott" <sob@harvard.edu>
Subject: Re: Problem with new Note Well
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu>
In-Reply-To: <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, Mike StJohns <mstjohns@comcast.net>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 18:09:46 -0000

On 1/23/14 11:58 AM, Bradner, Scott wrote:
> the actual rules are
> 	1/ if you know of any of your IPR in a contribution you make, you must disclose
>    

No, that's not true. If you know of any of your own IPR *that is 
necessarily infringed* by implementing your contribution, you must 
disclose. And what it means to be "necessarily infringed" has some 
details to it, and it might not be even implementation that causes the 
problem. And that's why it says at the top of the current document that 
there are exceptions.

> see - its not that hard to say this briefly

Really, it is quite hard to state the rules briefly such that it doesn't 
include *more* than you are required to do. Your statement did not.

pr

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


From mariainesrobles@googlemail.com  Thu Jan 23 09:40:23 2014
Return-Path: <mariainesrobles@googlemail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E28851A00E0 for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 09:40:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.777
X-Spam-Level: 
X-Spam-Status: No, score=-0.777 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_74=0.6, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D6hpuCtMSS2x for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 09:40:20 -0800 (PST)
Received: from mail-vc0-x232.google.com (mail-vc0-x232.google.com [IPv6:2607:f8b0:400c:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id BF0BF1A00C5 for <wgchairs@ietf.org>; Thu, 23 Jan 2014 09:40:19 -0800 (PST)
Received: by mail-vc0-f178.google.com with SMTP id ik5so1243370vcb.37 for <wgchairs@ietf.org>; Thu, 23 Jan 2014 09:40:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Vu5lqmwz82beUsYIVWzeqguQGdKUJq4ahKbxRcl5fBY=; b=C3DQvoWudtOJMA9C8z9yGvpsC1bWgzHPRaokgJNPeyv1YVSM0xn1naHnFhyGwrheLs MiwqMcAKk0Wtv4QnWHnqKFxUiqLX1ydRGqbJrVSR2VFefSDwZKcC1TC7U38s07+SJ3as N3bybcv8WzdSjH4lZAjm515G9UtSN9qcYl2uJ7wd9xJMr+yng5ua27HF/tvcDL+e8Gw1 rhCUv1HWqeOF3xJTOA+Q4gXHHScQFCtttnXoqB3EWx9D9vjm7M80G6T/vX1vtDDDcXSL iEk/QUN4f5Ay7FaHhFJ0Su+IFWAttqXDmOOV9FJDeUp9BUvLrkV2YfV84yRGhE4qJq1b x2Kw==
MIME-Version: 1.0
X-Received: by 10.220.133.80 with SMTP id e16mr5099475vct.13.1390498818572; Thu, 23 Jan 2014 09:40:18 -0800 (PST)
Received: by 10.220.49.68 with HTTP; Thu, 23 Jan 2014 09:40:18 -0800 (PST)
In-Reply-To: <CADJ9OA9HLC=883ONWN2davbAkMStfjy1sLpV6ksgkudnqVdR5w@mail.gmail.com>
References: <52E03D0E.5060703@nostrum.com> <FBD5AAFFD0978846BF6D3FAB4C892ACC10019832@SEA-EXMB-2.telecomsys.com> <CADJ9OA9HLC=883ONWN2davbAkMStfjy1sLpV6ksgkudnqVdR5w@mail.gmail.com>
Date: Thu, 23 Jan 2014 15:40:18 -0200
Message-ID: <CAP+sJUfv46Y5xUiON8w6oNJ=fuzpqOHcq66u+7Q0DJg7XiQ-MA@mail.gmail.com>
Subject: Re: Please double-check your group's archive in the web-based email list archive tool
From: Ines  Robles <mariainesrobles@googlemail.com>
To: Thomas Watteyne <watteyne@eecs.berkeley.edu>
Content-Type: multipart/alternative; boundary=001a11362cd424466604f0a6bc0e
X-Mailman-Approved-At: Thu, 23 Jan 2014 10:19:45 -0800
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, "<wgchairs@ietf.org>" <wgchairs@ietf.org>, Robert Sparks <rjsparks@nostrum.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 17:40:24 -0000

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

*Hello,Thank you very much for this new interface, it looks good for roll
wg.I just created some tickets, #1264
<http://trac.tools.ietf.org/tools/ietfdb/ticket/1264>, #1265
<http://trac.tools.ietf.org/tools/ietfdb/ticket/1265>, #1266
<http://trac.tools.ietf.org/tools/ietfdb/ticket/1266> and #1267
<http://trac.tools.ietf.org/tools/ietfdb/ticket/1267>.Kind Regards,Ines
Robles.*


2014/1/23 Thomas Watteyne <watteyne@eecs.berkeley.edu>

> Looks good for 6TiSCH. I really like the interface, this is a great
> improvement.
> Thomas
>
>
> On Thu, Jan 23, 2014 at 9:04 AM, Roger Marshall <RMarshall@telecomsys.com>wrote:
>
>> ECRIT content looks like it's in there, the tool looks really good.
>>
>> I did spot a few things, so I logged a couple of tickets on the subject
>> (search) and group (default display) features at:
>> http://trac.tools.ietf.org/tools/ietfdb
>>
>> -roger.
>>
>> -----Original Message-----
>> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of Robert
>> Sparks
>> Sent: Wednesday, January 22, 2014 1:50 PM
>> To: <wgchairs@ietf.org>
>> Subject: Please double-check your group's archive in the web-based email
>> list archive tool
>>
>> Chairs -
>>
>> If you have not already done so, please look briefly at your lists in the
>> new tool and make sure you see what you expect.
>>
>> You can browse quickly to them with a URL like:
>>
>> <https://mailarchive.ietf.org/arch/search/?email_list=stir>
>>
>> Click the date column header twice (the first time will give you a
>> most-recent to least-recent view, and the second the reverse), or jump
>> straight to a URL like <
>> https://mailarchive.ietf.org/arch/search/?email_list=stir&so=date>
>> and check that the archive goes back as far as you expect.
>>
>> Note that you can pull the division between the message list pane and the
>> message preview pane down to allow you to see more of the messages in the
>> list at one time.
>>
>> If you discover something that needs attention, please file a ticket at <
>> http://trac.tools.ietf.org/tools/ietfdb/newticket>
>>
>> RjS
>>
>> CONFIDENTIALITY NOTICE: The information contained in this message may be
>> privileged and/or confidential. If you are not the intended recipient, or
>> responsible for delivering this message to the intended recipient, any
>> review, forwarding, dissemination, distribution or copying of this
>> communication or any attachment(s) is strictly prohibited. If you have
>> received this message in error, please notify the sender immediately, and
>> delete it and all attachments from your computer and network.
>>
>
>

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

<div dir=3D"ltr"><b style=3D"font-weight:normal" id=3D"docs-internal-guid-5=
e9fc2de-c030-bede-d84f-5a13291b23ae"><p dir=3D"ltr" style=3D"line-height:1.=
15;margin-top:0pt;margin-bottom:0pt;margin-right:1pt"><span style=3D"font-s=
ize:15px;font-family:Arial;vertical-align:baseline;white-space:pre-wrap">He=
llo,</span></p>
<br><span style=3D"font-size:15px;font-family:Arial;vertical-align:baseline=
;white-space:pre-wrap"></span><p dir=3D"ltr" style=3D"line-height:1.15;marg=
in-top:0pt;margin-bottom:0pt;margin-right:1pt"><span style=3D"font-size:15p=
x;font-family:Arial;vertical-align:baseline;white-space:pre-wrap">Thank you=
 very much for this new interface, it looks good for roll wg.</span></p>
<br><span style=3D"font-size:15px;font-family:Arial;vertical-align:baseline=
;white-space:pre-wrap"></span><p dir=3D"ltr" style=3D"line-height:1.15;marg=
in-top:0pt;margin-bottom:0pt;margin-right:1pt"><span style=3D"font-size:15p=
x;font-family:Arial;vertical-align:baseline;white-space:pre-wrap">I just cr=
eated some tickets, </span><a href=3D"http://trac.tools.ietf.org/tools/ietf=
db/ticket/1264" style=3D"text-decoration:none"><span style=3D"font-size:15p=
x;font-family:Arial;text-decoration:underline;vertical-align:baseline;white=
-space:pre-wrap">#1264</span></a><span style=3D"font-size:15px;font-family:=
Arial;vertical-align:baseline;white-space:pre-wrap">, </span><a href=3D"htt=
p://trac.tools.ietf.org/tools/ietfdb/ticket/1265" style=3D"text-decoration:=
none"><span style=3D"font-size:15px;font-family:Arial;text-decoration:under=
line;vertical-align:baseline;white-space:pre-wrap">#1265</span></a><span st=
yle=3D"font-size:15px;font-family:Arial;vertical-align:baseline;white-space=
:pre-wrap">, </span><a href=3D"http://trac.tools.ietf.org/tools/ietfdb/tick=
et/1266" style=3D"text-decoration:none"><span style=3D"font-size:15px;font-=
family:Arial;text-decoration:underline;vertical-align:baseline;white-space:=
pre-wrap">#1266</span></a><span style=3D"font-size:15px;font-family:Arial;v=
ertical-align:baseline;white-space:pre-wrap"> and </span><a href=3D"http://=
trac.tools.ietf.org/tools/ietfdb/ticket/1267" style=3D"text-decoration:none=
"><span style=3D"font-size:15px;font-family:Arial;text-decoration:underline=
;vertical-align:baseline;white-space:pre-wrap">#1267</span></a><span style=
=3D"font-size:15px;font-family:Arial;vertical-align:baseline;white-space:pr=
e-wrap">.</span></p>
<br><span style=3D"font-size:15px;font-family:Arial;vertical-align:baseline=
;white-space:pre-wrap"></span><p dir=3D"ltr" style=3D"line-height:1.15;marg=
in-top:0pt;margin-bottom:0pt;margin-right:1pt"><span style=3D"font-size:15p=
x;font-family:Arial;vertical-align:baseline;white-space:pre-wrap">Kind Rega=
rds,</span></p>
<br><span style=3D"font-size:15px;font-family:Arial;vertical-align:baseline=
;white-space:pre-wrap"></span><span style=3D"font-size:15px;font-family:Ari=
al;vertical-align:baseline;white-space:pre-wrap">Ines Robles.</span></b><br=
>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">2014/1/=
23 Thomas Watteyne <span dir=3D"ltr">&lt;<a href=3D"mailto:watteyne@eecs.be=
rkeley.edu" target=3D"_blank">watteyne@eecs.berkeley.edu</a>&gt;</span><br>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div dir=3D"ltr">Looks good for 6TiSCH. I really like the interface, this i=
s a great improvement.<span class=3D"HOEnZb"><font color=3D"#888888"><div>T=
homas</div></font></span></div><div class=3D"HOEnZb"><div class=3D"h5"><div=
 class=3D"gmail_extra">
<br><br><div class=3D"gmail_quote">On Thu, Jan 23, 2014 at 9:04 AM, Roger M=
arshall <span dir=3D"ltr">&lt;<a href=3D"mailto:RMarshall@telecomsys.com" t=
arget=3D"_blank">RMarshall@telecomsys.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">ECRIT content looks like it&#39;s in there, =
the tool looks really good.<br>
<br>
I did spot a few things, so I logged a couple of tickets on the subject (se=
arch) and group (default display) features at:<br>
<a href=3D"http://trac.tools.ietf.org/tools/ietfdb" target=3D"_blank">http:=
//trac.tools.ietf.org/tools/ietfdb</a><br>
<br>
-roger.<br>
<div><div><br>
-----Original Message-----<br>
From: WGChairs [mailto:<a href=3D"mailto:wgchairs-bounces@ietf.org" target=
=3D"_blank">wgchairs-bounces@ietf.org</a>] On Behalf Of Robert Sparks<br>
Sent: Wednesday, January 22, 2014 1:50 PM<br>
To: &lt;<a href=3D"mailto:wgchairs@ietf.org" target=3D"_blank">wgchairs@iet=
f.org</a>&gt;<br>
Subject: Please double-check your group&#39;s archive in the web-based emai=
l list archive tool<br>
<br>
Chairs -<br>
<br>
If you have not already done so, please look briefly at your lists in the n=
ew tool and make sure you see what you expect.<br>
<br>
You can browse quickly to them with a URL like:<br>
<br>
&lt;<a href=3D"https://mailarchive.ietf.org/arch/search/?email_list=3Dstir"=
 target=3D"_blank">https://mailarchive.ietf.org/arch/search/?email_list=3Ds=
tir</a>&gt;<br>
<br>
Click the date column header twice (the first time will give you a most-rec=
ent to least-recent view, and the second the reverse), or jump straight to =
a URL like &lt;<a href=3D"https://mailarchive.ietf.org/arch/search/?email_l=
ist=3Dstir&amp;so=3Ddate" target=3D"_blank">https://mailarchive.ietf.org/ar=
ch/search/?email_list=3Dstir&amp;so=3Ddate</a>&gt;<br>



and check that the archive goes back as far as you expect.<br>
<br>
Note that you can pull the division between the message list pane and the m=
essage preview pane down to allow you to see more of the messages in the li=
st at one time.<br>
<br>
If you discover something that needs attention, please file a ticket at &lt=
;<a href=3D"http://trac.tools.ietf.org/tools/ietfdb/newticket" target=3D"_b=
lank">http://trac.tools.ietf.org/tools/ietfdb/newticket</a>&gt;<br>
<br>
RjS<br>
<br>
</div></div>CONFIDENTIALITY NOTICE: The information contained in this messa=
ge may be privileged and/or confidential. If you are not the intended recip=
ient, or responsible for delivering this message to the intended recipient,=
 any review, forwarding, dissemination, distribution or copying of this com=
munication or any attachment(s) is strictly prohibited. If you have receive=
d this message in error, please notify the sender immediately, and delete i=
t and all attachments from your computer and network.<br>



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

--001a11362cd424466604f0a6bc0e--

From mstjohns@comcast.net  Thu Jan 23 09:50:57 2014
Return-Path: <mstjohns@comcast.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 904E21A016F for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 09:50:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.038
X-Spam-Level: 
X-Spam-Status: No, score=-2.038 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, MISSING_MID=0.497, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4RYvvB2n5LVF for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 09:50:52 -0800 (PST)
Received: from qmta15.emeryville.ca.mail.comcast.net (qmta15.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:44:76:96:27:228]) by ietfa.amsl.com (Postfix) with ESMTP id 91EB21A0164 for <wgchairs@ietf.org>; Thu, 23 Jan 2014 09:50:52 -0800 (PST)
Received: from omta05.emeryville.ca.mail.comcast.net ([76.96.30.43]) by qmta15.emeryville.ca.mail.comcast.net with comcast id HT2z1n0080vp7WLAFVqhy4; Thu, 23 Jan 2014 17:50:41 +0000
Received: from Mike-T530ssd.comcast.net ([76.14.1.153]) by omta05.emeryville.ca.mail.comcast.net with comcast id HVpv1n00S3J4Au48RVq14J; Thu, 23 Jan 2014 17:50:46 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 23 Jan 2014 12:49:59 -0500
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>, Russ Housley <housley@vigilsec.com>,Jari Arkko <jari.arkko@piuha.net>
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: Problem with new Note Well
In-Reply-To: <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1390499441; bh=WeedSkUFXQu0ApZ+mrRzs8GiwXgttB/3A0MHE/Vmc8I=; h=Received:Received:Date:To:From:Subject:Mime-Version:Content-Type; b=Ji73xkKReK1vmZ9twe+KLnwYAUJ+R9LP5L6Vlaif1P1WyqGTo0xQHDk5EUSGlyY+W C6tAobrjfif4bpKUxFs4pRg7wQgI0Bzpwvk5zFdvK7A2SKDXtV8mvpL4GiXMN3QdZp PHzxuDYaGrwDpgJTY4gZ/YEf7HS5rcgPVSKk5osFR3s8wW+nqiLOpVgb8ucwAzOsIG ozhdWhxRia+TLqUaSVCbx853yUTB6ZFiwWcxs2rFGA2vHhMsfY04kwMmgGiixwv96O Y2iokV7/Gf+iWaWfLjxdYR5ETLDLz2TMd8H51/rujo27wYg8IFQHiy1GDRzsiWD5/X ifbMtPB9paQyw==
X-Mailman-Approved-At: Thu, 23 Jan 2014 10:19:53 -0800
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 17:50:57 -0000

Is the issue the difference between "any contribution YOU MAKE" and "any=
 contribution"?  E.g. if you happen to hear someone discussing something you=
 think is covered by patent, you can't say anything, but conversely, if YOU=
 are making a contribution that's covered by patent then the NDA doesn't=
 apply (because you have approval to make the contribution and disclosure).

Mike


At 12:25 PM 1/23/2014, Cullen Jennings (fluffy) wrote:

>This new note well is a real problem for me and  I can not register without=
 clicking "I agree" to it. It is not consistent with the BCPs. The problem=
 is the line that says
>
>        =95 If you are aware that any contribution (something written,=
 said, or discussed in any IETF context) is covered by patents or patent=
 applications, you must disclose that fact.
>
>I do not agree to that - I can=92t given my NDA with my employer does not=
 allow me to disclose confidential information. Yes, I realize there is some=
 weasel words near the top that say "Exceptions may apply." but that does=
 not help me. When you are testifying in court on patents, credibility is=
 incredibly important. You can not have the lawyers on the other side saying=
 that you clicked yes I agree to the line above but you did not actually do=
 what that lines says. You may think this does to matter but the exact topic=
 of how Cisco employees deal with IPR at the IETF is a topic that I have=
 testified on in an East Texas court so this really does happen and really=
 does happen to me. It may happen to you next and you will be much happier=
 if you say what you mean and mean what you say. This new note well fails=
 that test.=20
>
>I realize some people would like to change the IETF policy to be that you=
 do have to do what that line says but I do not think that is a change the=
 IESG can make without IETF updating the BCP or at least having IETF=
 consensus on the change. I would respectfully ask the IESG to change this=
 line to something that is still brief but that people can agree with it.=
 Simply adding something like "or not contribute to the discussion on that=
 contribution" would probably solve this problem for me.=20
>
>Thank you,=20
>
>Cullen
>
>I will note that above line is not consistent with Cisco employment=
 contracts and if we can not resolve this I will be asking Cisco legal to=
 inform Cisco employees they can not agree with this without violating their=
 employment agreement.=20
>
>
>
>On Jan 23, 2014, at 9:44 AM, Russ Housley <housley@vigilsec.com> wrote:
>
>> It seems that the shorter one is now being used on the IETF web site:
>> http://www.ietf.org/about/note-well.html
>>=20
>>=20
>> On Jan 8, 2014, at 3:57 PM, Mary Barnes wrote:
>>=20
>>> Personally, I've never seen significant value in this shorter note well=
 and while others have been using this new text for the past few meetings,=
 I've stuck to the old.   Now that this is considered the recommended note=
 well for chairs to use, I guess I'll use it.  But, I personally think=
 accuracy should trump brevity.  I think the "must" in that bullet  ought to=
 at least be a should and that adding an "otherwise, one should not=
 contribute to or participate in any related IETF activities." would add=
 more value.  =20
>>>=20
>>> Mary.
>>>=20
>>>=20
>>> On Wed, Jan 8, 2014 at 1:17 PM, Bradner, Scott <sob@harvard.edu> wrote:
>>> you are correct - we (Barry, the IESG & me) discussed this before the=
 IESG approved this text - they felt that
>>> being brief was more important than being fully accurate (or at least=
 that is the way I expressed it)
>>>=20
>>> Scott
>>>=20
>>> Scott O Bradner
>>> Senior Technology Consultant
>>>=20
>>> Harvard University Information Technology
>>> Innovation & Architecture
>>> (P) +1 (617) 495 3864
>>> 8 Story St, room 5014
>>> Cambridge, MA 02138
>>>=20
>>>=20
>>>=20
>>> On Jan 8, 2014, at 2:13 PM, Cullen Jennings (fluffy) <fluffy@cisco.com>=
 wrote:
>>>=20
>>> >
>>> >
>>> > On Dec 16, 2013, at 12:56 PM, Barry Leiba <barryleiba@computer.org>=
 wrote:
>>> >
>>> >> The IESG has made final edits to the updated Note Well statement, and
>>> >> it has been officially updated:
>>> >> http://www.ietf.org/about/note-well.html
>>> >>
>>> >> I have just uploaded the final versions of the Note Well meeting
>>> >> slides, attached to the bottom of the WG Chairs wiki:
>>> >> http://wiki.tools.ietf.org/group/wgchairs/wiki/WikiStart
>>> >>
>>> >> Please use this new version now, and please remember that as you
>>> >> prepare slides for the London meeting.
>>> >>
>>> >> Barry
>>> >
>>> >
>>> > The new note well says
>>> >
>>> >       =95 If you are aware that any contribution (something written,=
 said, or discussed in any IETF context) is covered by patents or patent=
 applications, you must disclose that fact.
>>> >
>>> > Is that true?  Or is it missing something along the lines of section y=
 of BCP 79 such as
>>> >
>>> >   or must not contribute to or participate in IETF activities with
>>> >   respect to technologies that he or she reasonably and personally
>>> >   knows to be Covered by IPR which he or she will not disclose.
>>> >
>>> > Thanks, Cullen
>>=20



From scott.brim@gmail.com  Thu Jan 23 10:15:23 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90CE31A0024; Thu, 23 Jan 2014 10:15:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PvWM3OnW3WWq; Thu, 23 Jan 2014 10:15:22 -0800 (PST)
Received: from mail-qa0-x231.google.com (mail-qa0-x231.google.com [IPv6:2607:f8b0:400d:c00::231]) by ietfa.amsl.com (Postfix) with ESMTP id 03FAC1A000A; Thu, 23 Jan 2014 10:15:21 -0800 (PST)
Received: by mail-qa0-f49.google.com with SMTP id w8so2590222qac.22 for <multiple recipients>; Thu, 23 Jan 2014 10:15:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=IcFDFJL49BTRHZgRsH6pttCFnNOr+fve3gno97eirtw=; b=J9InLZrp3wB7f2kKZOKrI0d1IWSIzliHNP88vN44/UnSPMouWdw6dSWLJ53e5oz5Xq YH3oDk4L0EWdHN4OfVVb+CnPUNKuaTJVDkki5jipGz7QvPVwQSUXXN5KH1PHb8NepTYm 3ifjHWDR3+5H5bnN0yTSCmSS9HN4TSzNUEd9hKHXj3Yc2sFgypdBXaxpEvO++9dGOvEu GJoP6xJzLj2uPHs1MK5CXKrUXKoCBfKOw/5NKu8fQ93C1GZ/YtK+IXZHGOOxUYWhIFnH qyrasT86GinknndL1Dq0tyPTO5Dmn7ZCiI4Hpm/bfgHdlGcBMCTz1VwEynBEMzXne72r eK6A==
MIME-Version: 1.0
X-Received: by 10.224.5.69 with SMTP id 5mr13887903qau.11.1390500920885; Thu, 23 Jan 2014 10:15:20 -0800 (PST)
Received: by 10.182.48.9 with HTTP; Thu, 23 Jan 2014 10:15:20 -0800 (PST)
Received: by 10.182.48.9 with HTTP; Thu, 23 Jan 2014 10:15:20 -0800 (PST)
In-Reply-To: <52E15AE2.7030508@qti.qualcomm.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E15AE2.7030508@qti.qualcomm.com>
Date: Thu, 23 Jan 2014 13:15:20 -0500
Message-ID: <CAPv4CP-K+zfMV--pamd27SaPgZ2=Tg4UVeNuyn8oN+apsp3znw@mail.gmail.com>
Subject: Re: Problem with new Note Well
From: Scott Brim <scott.brim@gmail.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Content-Type: multipart/alternative; boundary=001a11c2c28e730a1c04f0a73932
X-Mailman-Approved-At: Thu, 23 Jan 2014 10:20:12 -0800
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 18:15:23 -0000

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

Also, instant disclosure is not expected. I remember in the discussions it
was decided that a reasonable amount of time could be allowed for
consultation with lawyers, decisions about who would say what, etc.

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

<p dir="ltr">Also, instant disclosure is not expected. I remember in the discussions it was decided that a reasonable amount of time could be allowed for consultation with lawyers, decisions about who would say what, etc. </p>


--001a11c2c28e730a1c04f0a73932--

From presnick@qti.qualcomm.com  Thu Jan 23 10:25:56 2014
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B2F41A00DE; Thu, 23 Jan 2014 10:25:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.836
X-Spam-Level: 
X-Spam-Status: No, score=-4.836 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xiwLMdy1rF_3; Thu, 23 Jan 2014 10:25:51 -0800 (PST)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id C204C1A004A; Thu, 23 Jan 2014 10:25:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1390501551; x=1422037551; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=VIj2Pea93ajbO2VE5FPbT/v6TrSRxH0Tth/car5HwJI=; b=cZ3Y94KIBkRI2/2qna9LyIxQdpc1wGucZjp4V2DnHBjb6e85le6usiRt 0vzAG72TgZKofrDqUC0Jwe68t+FLi03hzWRCW9VEMRPCYeMY3dy2MWP54 UNr0aGmmTDFbRHVJgfOtf+kDn0irvnFSYeF1oXKvgR+PJCqN5RTut0+YP I=;
X-IronPort-AV: E=McAfee;i="5400,1158,7327"; a="10035369"
Received: from ironmsg03-r.qualcomm.com ([172.30.46.17]) by wolverine01.qualcomm.com with ESMTP; 23 Jan 2014 10:25:49 -0800
X-IronPort-AV: E=McAfee;i="5400,1158,7327"; a="618367016"
Received: from nasanexhc01.na.qualcomm.com ([172.30.48.25]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 23 Jan 2014 10:25:49 -0800
Received: from nasanexhc05.na.qualcomm.com (172.30.48.2) by NASANEXHC01.na.qualcomm.com (172.30.48.25) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 23 Jan 2014 10:25:48 -0800
Received: from presnick-mac.local (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.2) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 23 Jan 2014 10:25:48 -0800
Message-ID: <52E15EAA.8060301@qti.qualcomm.com>
Date: Thu, 23 Jan 2014 12:25:46 -0600
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Subject: Re: Problem with new Note Well
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <52E15937.8010600@qti.qualcomm.com> <18480766-BA47-445B-8C75-5DD261F94A76@cisco.com>
In-Reply-To: <18480766-BA47-445B-8C75-5DD261F94A76@cisco.com>
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>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 18:25:56 -0000

On 1/23/14 12:07 PM, Cullen Jennings (fluffy) wrote:
> Pete,  what do you think "Acknowledge" means on a from like this? ( I will note it does not say "I Acknowledge I read this but may not agree with it" )
>    

You are acknowledging that there are rules (not fully specified here) 
that you have to go read and abide by if you show up and participate at 
the meeting. When you show up and participate at the meeting, you are 
agreeing to a bunch of things that are not on this page.

Are you saying that you don't agree that there are exceptions to what's 
on this page?

pr

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


From suresh.krishnan@ericsson.com  Thu Jan 23 10:27:57 2014
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A0631A01E0 for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 10:27:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qk0vAV6QSsqJ for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 10:27:52 -0800 (PST)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id 3C1551A0208 for <wgchairs@ietf.org>; Thu, 23 Jan 2014 10:27:37 -0800 (PST)
X-AuditID: c618062d-b7f858e0000031c7-16-52e15f15e739
Received: from EUSAAHC004.ericsson.se (Unknown_Domain [147.117.188.84]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 03.13.12743.51F51E25; Thu, 23 Jan 2014 19:27:33 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC004.ericsson.se ([147.117.188.84]) with mapi id 14.02.0387.000; Thu, 23 Jan 2014 13:27:36 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Robert Sparks <rjsparks@nostrum.com>, "<wgchairs@ietf.org>" <wgchairs@ietf.org>
Subject: RE: Please double-check your group's archive in the web-based email list archive tool
Thread-Topic: Please double-check your group's archive in the web-based email list archive tool
Thread-Index: AQHPF7v/4ETgbie7GEmvuqU6d3EFRZqSmd1A
Date: Thu, 23 Jan 2014 18:27:35 +0000
Message-ID: <E87B771635882B4BA20096B589152EF628579158@eusaamb107.ericsson.se>
References: <52E03D0E.5060703@nostrum.com>
In-Reply-To: <52E03D0E.5060703@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.12]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrALMWRmVeSWpSXmKPExsUyuXRPiK5o/MMgg6uLpCyuzWlks/i/fwqj A5PHkiU/mTxm7XzCEsAUxWWTkpqTWZZapG+XwJWx9cZGtoJ7PBX73n5hbmBcytXFyMkhIWAi saj3GDuELSZx4d56ti5GLg4hgSOMEu2/JzFDOMsZJZ5+u84MUsUG1LFh52cmEFtEIFRixZI5 YN3CAgkSD0/ug4onSqx+2svaxcgBZBtJXDliA2KyCKhK/DyVDVLBK+Ar0TKplRXEFhLQkpj6 bQMjiM0poC3x880MsDgj0D3fT60Bm8gsIC5x68l8Jog7BSSW7DnPDGGLSrx8/I8VwlaSmPP6 GjNEvY7Egt2f2CBsbYllC18zQ+wVlDg58wnLBEbRWUjGzkLSMgtJyywkLQsYWVYxcpQWp5bl phsZbGIExsIxCTbdHYx7XloeYpTmYFES5/3y1jlISCA9sSQ1OzW1ILUovqg0J7X4ECMTB6dU A6PL29k3TjZtfpka8mmhedQp2cZi8a4Aptzb/XdVDqlyhhb7Jrz1Y3uSy1C6wJmrc8/yX3te f5qSy83UOId1znYus3V7vvdc6TQ9vP543SppQRX3RT8mWIjxTVvCl1OeFhW/1lB14YU9Ir7V Jnze7Hm9gaY9Zr9s2ROiGUVCxAsEpKtztlzoUGIpzkg01GIuKk4EAACxztNTAgAA
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 18:27:57 -0000

Hi Robert,
  This tool is extremely useful. int-area and softwire wg lists look fine. =
So does the gen-art list. Great to know that we will also get IMAP access t=
o the archive.

Thanks
Suresh

<rant>I am all for progress, but I am really uncomfortable with the "infini=
te scrolling" like behavior in the UI. I would rather see a nice paged inte=
rface.=20

Customary xkcd reference -> http://xkcd.com/1309/
</rant>

> -----Original Message-----
> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of Robert
> Sparks
> Sent: January-22-14 4:50 PM
> To: <wgchairs@ietf.org>
> Subject: Please double-check your group's archive in the web-based email
> list archive tool
>=20
> Chairs -
>=20
> If you have not already done so, please look briefly at your lists in the
> new tool and make sure you see what you expect.
>=20
> You can browse quickly to them with a URL like:
>=20
> <https://mailarchive.ietf.org/arch/search/?email_list=3Dstir>
>=20
> Click the date column header twice (the first time will give you a most-
> recent to least-recent view, and the second the reverse), or jump straigh=
t
> to a URL like
> <https://mailarchive.ietf.org/arch/search/?email_list=3Dstir&so=3Ddate>
> and check that the archive goes back as far as you expect.
>=20
> Note that you can pull the division between the message list pane and the
> message preview pane down to allow you to see more of the messages in the
> list at one time.
>=20
> If you discover something that needs attention, please file a ticket at
> <http://trac.tools.ietf.org/tools/ietfdb/newticket>
>=20
> RjS

From mariainesrobles@googlemail.com  Thu Jan 23 10:31:40 2014
Return-Path: <mariainesrobles@googlemail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E3111A001B for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 10:31:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.777
X-Spam-Level: 
X-Spam-Status: No, score=-0.777 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_74=0.6, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mgS63HRGtDlK for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 10:31:36 -0800 (PST)
Received: from mail-vb0-x236.google.com (mail-vb0-x236.google.com [IPv6:2607:f8b0:400c:c02::236]) by ietfa.amsl.com (Postfix) with ESMTP id CA0711A000A for <wgchairs@ietf.org>; Thu, 23 Jan 2014 10:31:35 -0800 (PST)
Received: by mail-vb0-f54.google.com with SMTP id w20so1259628vbb.41 for <wgchairs@ietf.org>; Thu, 23 Jan 2014 10:31:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=UcnPnBBAkirINKVYgXXr/mVXsN4Ax09q+HLmUf+IIn8=; b=gzSBOeEOCfI0SHTAELrKRhC/bLl0zVCNiT3tDmf7HPwN54/T6xFZHyz50mtETuAzkQ ji+JRpG4tjYpJPrkSDlTjjEysd7UtDBjRxc0aZ5Z4s6cEX7CTIYVB+ocaDeNw8h9kqpH V41g4HHbXmeLgrzB9Q9siAe+v81RUYpUnbv7sU21SAnlp+0UJVrKFJM6iZM2ndfYPkV1 oe+83Hqoml6A6RUSa+8RYFKKxdM/ZcoXEHFEJM9R5imgYzSRUguj03Jc1HmiMyA6VhJB agvDfQX0T7Yr8umFPDinM8ZGu+C5ibLp/SNR5WUJGydQZWMY1g0FBzwd/WMMVs0UNxym oKSg==
MIME-Version: 1.0
X-Received: by 10.221.2.138 with SMTP id nu10mr616079vcb.52.1390501894748; Thu, 23 Jan 2014 10:31:34 -0800 (PST)
Received: by 10.220.49.68 with HTTP; Thu, 23 Jan 2014 10:31:34 -0800 (PST)
In-Reply-To: <CAP+sJUfv46Y5xUiON8w6oNJ=fuzpqOHcq66u+7Q0DJg7XiQ-MA@mail.gmail.com>
References: <52E03D0E.5060703@nostrum.com> <FBD5AAFFD0978846BF6D3FAB4C892ACC10019832@SEA-EXMB-2.telecomsys.com> <CADJ9OA9HLC=883ONWN2davbAkMStfjy1sLpV6ksgkudnqVdR5w@mail.gmail.com> <CAP+sJUfv46Y5xUiON8w6oNJ=fuzpqOHcq66u+7Q0DJg7XiQ-MA@mail.gmail.com>
Date: Thu, 23 Jan 2014 16:31:34 -0200
Message-ID: <CAP+sJUdEthVEamQv7AmHop=cH64+1Yeygggk_mi1YVMKX0auag@mail.gmail.com>
Subject: Re: Please double-check your group's archive in the web-based email list archive tool
From: Ines  Robles <mariainesrobles@googlemail.com>
To: "<wgchairs@ietf.org>" <wgchairs@ietf.org>
Content-Type: multipart/alternative; boundary=089e011609167eff5504f0a773d1
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 18:31:40 -0000

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

*Hello,Thank you very much for this new interface, it looks good for roll
wg.I just created some tickets, #1264
<http://trac.tools.ietf.org/tools/ietfdb/ticket/1264>, #1265
<http://trac.tools.ietf.org/tools/ietfdb/ticket/1265>, #1266
<http://trac.tools.ietf.org/tools/ietfdb/ticket/1266> and #1267
<http://trac.tools.ietf.org/tools/ietfdb/ticket/1267>.Kind Regards,Ines
Robles.*



> 2014/1/23 Thomas Watteyne <watteyne@eecs.berkeley.edu>
>
>> Looks good for 6TiSCH. I really like the interface, this is a great
>> improvement.
>> Thomas
>>
>>
>> On Thu, Jan 23, 2014 at 9:04 AM, Roger Marshall <RMarshall@telecomsys.com
>> > wrote:
>>
>>> ECRIT content looks like it's in there, the tool looks really good.
>>>
>>> I did spot a few things, so I logged a couple of tickets on the subject
>>> (search) and group (default display) features at:
>>> http://trac.tools.ietf.org/tools/ietfdb
>>>
>>> -roger.
>>>
>>> -----Original Message-----
>>> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of Robert
>>> Sparks
>>> Sent: Wednesday, January 22, 2014 1:50 PM
>>> To: <wgchairs@ietf.org>
>>> Subject: Please double-check your group's archive in the web-based email
>>> list archive tool
>>>
>>> Chairs -
>>>
>>> If you have not already done so, please look briefly at your lists in
>>> the new tool and make sure you see what you expect.
>>>
>>> You can browse quickly to them with a URL like:
>>>
>>> <https://mailarchive.ietf.org/arch/search/?email_list=stir>
>>>
>>> Click the date column header twice (the first time will give you a
>>> most-recent to least-recent view, and the second the reverse), or jump
>>> straight to a URL like <
>>> https://mailarchive.ietf.org/arch/search/?email_list=stir&so=date>
>>> and check that the archive goes back as far as you expect.
>>>
>>> Note that you can pull the division between the message list pane and
>>> the message preview pane down to allow you to see more of the messages in
>>> the list at one time.
>>>
>>> If you discover something that needs attention, please file a ticket at <
>>> http://trac.tools.ietf.org/tools/ietfdb/newticket>
>>>
>>> RjS
>>>
>>> CONFIDENTIALITY NOTICE: The information contained in this message may be
>>> privileged and/or confidential. If you are not the intended recipient, or
>>> responsible for delivering this message to the intended recipient, any
>>> review, forwarding, dissemination, distribution or copying of this
>>> communication or any attachment(s) is strictly prohibited. If you have
>>> received this message in error, please notify the sender immediately, and
>>> delete it and all attachments from your computer and network.
>>>
>>
>>
>

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div=
><b style=3D"font-family:arial,sans-serif;font-size:13px;font-weight:normal=
"><p dir=3D"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt=
;margin-right:1pt">
<span style=3D"font-size:15px;font-family:Arial;vertical-align:baseline;whi=
te-space:pre-wrap">Hello,</span></p><br><span style=3D"font-size:15px;font-=
family:Arial;vertical-align:baseline;white-space:pre-wrap"></span><p dir=3D=
"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt;margin-rig=
ht:1pt">
<span style=3D"font-size:15px;font-family:Arial;vertical-align:baseline;whi=
te-space:pre-wrap">Thank you very much for this new interface, it looks goo=
d for roll wg.</span></p><br><span style=3D"font-size:15px;font-family:Aria=
l;vertical-align:baseline;white-space:pre-wrap"></span><p dir=3D"ltr" style=
=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt;margin-right:1pt">
<span style=3D"font-size:15px;font-family:Arial;vertical-align:baseline;whi=
te-space:pre-wrap">I just created some tickets, </span><a href=3D"http://tr=
ac.tools.ietf.org/tools/ietfdb/ticket/1264" target=3D"_blank" style=3D"text=
-decoration:none"><span style=3D"font-size:15px;font-family:Arial;text-deco=
ration:underline;vertical-align:baseline;white-space:pre-wrap">#1264</span>=
</a><span style=3D"font-size:15px;font-family:Arial;vertical-align:baseline=
;white-space:pre-wrap">, </span><a href=3D"http://trac.tools.ietf.org/tools=
/ietfdb/ticket/1265" target=3D"_blank" style=3D"text-decoration:none"><span=
 style=3D"font-size:15px;font-family:Arial;text-decoration:underline;vertic=
al-align:baseline;white-space:pre-wrap">#1265</span></a><span style=3D"font=
-size:15px;font-family:Arial;vertical-align:baseline;white-space:pre-wrap">=
, </span><a href=3D"http://trac.tools.ietf.org/tools/ietfdb/ticket/1266" ta=
rget=3D"_blank" style=3D"text-decoration:none"><span style=3D"font-size:15p=
x;font-family:Arial;text-decoration:underline;vertical-align:baseline;white=
-space:pre-wrap">#1266</span></a><span style=3D"font-size:15px;font-family:=
Arial;vertical-align:baseline;white-space:pre-wrap"> and </span><a href=3D"=
http://trac.tools.ietf.org/tools/ietfdb/ticket/1267" target=3D"_blank" styl=
e=3D"text-decoration:none"><span style=3D"font-size:15px;font-family:Arial;=
text-decoration:underline;vertical-align:baseline;white-space:pre-wrap">#12=
67</span></a><span style=3D"font-size:15px;font-family:Arial;vertical-align=
:baseline;white-space:pre-wrap">.</span></p>
<br><span style=3D"font-size:15px;font-family:Arial;vertical-align:baseline=
;white-space:pre-wrap"></span><p dir=3D"ltr" style=3D"line-height:1.15;marg=
in-top:0pt;margin-bottom:0pt;margin-right:1pt"><span style=3D"font-size:15p=
x;font-family:Arial;vertical-align:baseline;white-space:pre-wrap">Kind Rega=
rds,</span></p>
<br><span style=3D"font-size:15px;font-family:Arial;vertical-align:baseline=
;white-space:pre-wrap"></span><span style=3D"font-size:15px;font-family:Ari=
al;vertical-align:baseline;white-space:pre-wrap">Ines Robles.</span></b><br=
>
</div><div><br></div><div>=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(20=
4,204,204);border-left-style:solid;padding-left:1ex"><div class=3D""><div c=
lass=3D"h5">
<div class=3D"gmail_extra"><b style=3D"color:rgb(34,34,34);font-family:aria=
l,sans-serif;font-size:13px;font-weight:normal"><p dir=3D"ltr" style=3D"lin=
e-height:1.15;margin-top:0pt;margin-bottom:0pt;margin-right:1pt"></p></b><d=
iv class=3D"gmail_quote">
2014/1/23 Thomas Watteyne <span dir=3D"ltr">&lt;<a href=3D"mailto:watteyne@=
eecs.berkeley.edu" target=3D"_blank">watteyne@eecs.berkeley.edu</a>&gt;</sp=
an><br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;=
border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:=
solid;padding-left:1ex">

<div dir=3D"ltr">Looks good for 6TiSCH. I really like the interface, this i=
s a great improvement.<span><font color=3D"#888888"><div>Thomas</div></font=
></span></div><div><div><div class=3D"gmail_extra">
<br><br><div class=3D"gmail_quote">On Thu, Jan 23, 2014 at 9:04 AM, Roger M=
arshall <span dir=3D"ltr">&lt;<a href=3D"mailto:RMarshall@telecomsys.com" t=
arget=3D"_blank">RMarshall@telecomsys.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">ECRIT content looks like it&#39;s in there, the tool looks=
 really good.<br>

<br>
I did spot a few things, so I logged a couple of tickets on the subject (se=
arch) and group (default display) features at:<br>
<a href=3D"http://trac.tools.ietf.org/tools/ietfdb" target=3D"_blank">http:=
//trac.tools.ietf.org/tools/ietfdb</a><br>
<br>
-roger.<br>
<div><div><br>
-----Original Message-----<br>
From: WGChairs [mailto:<a href=3D"mailto:wgchairs-bounces@ietf.org" target=
=3D"_blank">wgchairs-bounces@ietf.org</a>] On Behalf Of Robert Sparks<br>
Sent: Wednesday, January 22, 2014 1:50 PM<br>
To: &lt;<a href=3D"mailto:wgchairs@ietf.org" target=3D"_blank">wgchairs@iet=
f.org</a>&gt;<br>
Subject: Please double-check your group&#39;s archive in the web-based emai=
l list archive tool<br>
<br>
Chairs -<br>
<br>
If you have not already done so, please look briefly at your lists in the n=
ew tool and make sure you see what you expect.<br>
<br>
You can browse quickly to them with a URL like:<br>
<br>
&lt;<a href=3D"https://mailarchive.ietf.org/arch/search/?email_list=3Dstir"=
 target=3D"_blank">https://mailarchive.ietf.org/arch/search/?email_list=3Ds=
tir</a>&gt;<br>
<br>
Click the date column header twice (the first time will give you a most-rec=
ent to least-recent view, and the second the reverse), or jump straight to =
a URL like &lt;<a href=3D"https://mailarchive.ietf.org/arch/search/?email_l=
ist=3Dstir&amp;so=3Ddate" target=3D"_blank">https://mailarchive.ietf.org/ar=
ch/search/?email_list=3Dstir&amp;so=3Ddate</a>&gt;<br>




and check that the archive goes back as far as you expect.<br>
<br>
Note that you can pull the division between the message list pane and the m=
essage preview pane down to allow you to see more of the messages in the li=
st at one time.<br>
<br>
If you discover something that needs attention, please file a ticket at &lt=
;<a href=3D"http://trac.tools.ietf.org/tools/ietfdb/newticket" target=3D"_b=
lank">http://trac.tools.ietf.org/tools/ietfdb/newticket</a>&gt;<br>
<br>
RjS<br>
<br>
</div></div>CONFIDENTIALITY NOTICE: The information contained in this messa=
ge may be privileged and/or confidential. If you are not the intended recip=
ient, or responsible for delivering this message to the intended recipient,=
 any review, forwarding, dissemination, distribution or copying of this com=
munication or any attachment(s) is strictly prohibited. If you have receive=
d this message in error, please notify the sender immediately, and delete i=
t and all attachments from your computer and network.<br>




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

--089e011609167eff5504f0a773d1--

From ned.freed@mrochek.com  Thu Jan 23 10:27:31 2014
Return-Path: <ned.freed@mrochek.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D69D1A01E0; Thu, 23 Jan 2014 10:27:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level: 
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cft9vIuQm5XX; Thu, 23 Jan 2014 10:27:30 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id F0B4C1A01EE; Thu, 23 Jan 2014 10:27:12 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P3HNC8W334003JH7@mauve.mrochek.com>; Thu, 23 Jan 2014 10:22:10 -0800 (PST)
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=Windows-1252
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P2SI6PLQJK0000AS@mauve.mrochek.com>; Thu, 23 Jan 2014 10:22:06 -0800 (PST)
Message-id: <01P3HNC7BYKK0000AS@mauve.mrochek.com>
Date: Thu, 23 Jan 2014 09:41:59 -0800 (PST)
From: Ned Freed <ned.freed@mrochek.com>
Subject: Re: Problem with new Note Well
In-reply-to: "Your message dated Thu, 23 Jan 2014 17:25:20 +0000" <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com>
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
X-Mailman-Approved-At: Thu, 23 Jan 2014 10:40:32 -0800
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 18:27:31 -0000

> This new note well is a real problem for me and  I can not register without
> clicking "I agree" to it. It is not consistent with the BCPs. The problem is
> the line that says

>     If you are aware that any contribution (something written, said, or
>     discussed in any IETF context) is covered by patents or patent applications,
>     you must disclose that fact.

> I do not agree to that - I can’t given my NDA with my employer does not allow
> me to disclose confidential information. Yes, I realize there is some weasel
> words near the top that say "Exceptions may apply." but that does not help me.

It's actually much worse than that. This wording would require that not only do
I disclose not only past and present employer/sponsor/personal IPR, but also
IPR third parties have asserted that I happen to be aware of as a result of,
say, a patent dispute. In constrast, the relevant BCPs are clear that while
I'm encouraged to disclose third party IPR I'm aware of, I'm not required to.

The resulting glut of disclosures created by following such a rule would in
turn create serious problems of its own. A lot of people, myself included,
operate under restricitons as to what sort of information about IPR we're
supposed to see. This could easily cross the line.

> When you are testifying in court on patents, credibility is incredibly
> important. You can not have the lawyers on the other side saying that you
> clicked yes I agree to the line above but you did not actually do what that
> lines says. You may think this does to matter but the exact topic of how Cisco
> employees deal with IPR at the IETF is a topic that I have testified on in an
> East Texas court so this really does happen and really does happen to me. It
> may happen to you next and you will be much happier if you say what you mean
> and mean what you say. This new note well fails that test.

The issue of how Oracle employees deal with IPR at the IETF hasn't come up for
me - at least not yet. But this is highly problematic for me in other ways,
as noted above.

> I realize some people would like to change the IETF policy to be that you do
> have to do what that line says but I do not think that is a change the IESG can
> make without IETF updating the BCP or at least having IETF consensus on the
> change.

I realize that a some people think they would like to make such a change, but
having spent a fair bit of time on patent matters, IMO this is a case of "be
careful what you wish for".

> I would respectfully ask the IESG to change this line to something that
> is still brief but that people can agree with it. Simply adding something like
> "or not contribute to the discussion on that contribution" would probably solve
> this problem for me.

Not sufficient for me. This also needs to be changed so that the
employee/sponsor restrictions set forth in sections 6.1.1 and 6.1.2 and most
especially 6.1.3 of BCP 79 are included.

> I will note that above line is not consistent with Cisco employment contracts
> and if we can not resolve this I will be asking Cisco legal to inform Cisco
> employees they can not agree with this without violating their employment
> agreement.

I haven't checked Oracle's contract, but the same may be true here as well, and
if so I will have no choice but to do something similar.

				Ned

From sob@harvard.edu  Thu Jan 23 11:56:52 2014
Return-Path: <sob@harvard.edu>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8575C1A004E; Thu, 23 Jan 2014 11:56:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.135
X-Spam-Level: 
X-Spam-Status: No, score=-3.135 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pj9UXrjN9Z6R; Thu, 23 Jan 2014 11:56:50 -0800 (PST)
Received: from ackroyd.harvard.edu (ackroyd.harvard.edu [128.103.208.29]) by ietfa.amsl.com (Postfix) with ESMTP id B17B01A001D; Thu, 23 Jan 2014 11:56:50 -0800 (PST)
Received: from ENTWEDGE0000004.university.harvard.edu (entwedge0000004.university.harvard.edu [10.35.202.51]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ackroyd.harvard.edu (Postfix) with ESMTP id 65843E939C; Thu, 23 Jan 2014 14:56:47 -0500 (EST)
Received: from ENTWHUBT0000000.university.harvard.edu (10.32.8.201) by entwedge0000004.university.harvard.edu (10.35.202.51) with Microsoft SMTP Server (TLS) id 14.3.146.0; Thu, 23 Jan 2014 14:56:35 -0500
Received: from ENTWEXMB0000008.university.harvard.edu ([169.254.1.46]) by ENTWHUBT0000000.university.harvard.edu ([10.32.8.201]) with mapi id 14.03.0146.000; Thu, 23 Jan 2014 14:56:47 -0500
From: "Bradner, Scott" <sob@harvard.edu>
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Problem with new Note Well 
Thread-Topic: Problem with new Note Well 
Thread-Index: AQHPGHU+CFZ0F6AtJEKMoMTuYGDa1Q==
Date: Thu, 23 Jan 2014 19:56:46 +0000
Message-ID: <E3E4E04A-B342-4FDC-89EC-5FC8F7CEAAF0@harvard.edu>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E15AE2.7030508@qti.qualcomm.com>
In-Reply-To: <52E15AE2.7030508@qti.qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [136.248.127.162]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <EB04A132A483394FA54E23C9D9A08C7C@Exchange.university.harvard.edu>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, Jorge Contreras <contreraslegal@att.net>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 19:56:52 -0000

while, in the end, this is true (the "necessarily infringed=94 requirement)=
 I do not think it is a good thing
to obsess about at the disclose-so-the-working-group-can-evaluate-the-techn=
ology stage since it is impossible
to know if any particular IPR will wind up in this catagory until a RFC is =
finished - which would negate=20
the whole reason for the disclosure

 maybe we should make that clear (disclose if you suspect that IPR relates =
not =93is necessarily infringed=94)
in the 3979 update - this is what the rule used to be and the language Pete=
 is focussing on
was added and, apparently, has an undesired side effect

Scott

On Jan 23, 2014, at 1:09 PM, Pete Resnick <presnick@qti.qualcomm.com> wrote=
:

> On 1/23/14 11:58 AM, Bradner, Scott wrote:
>> the actual rules are
>> 	1/ if you know of any of your IPR in a contribution you make, you must =
disclose
>>  =20
>=20
> No, that's not true. If you know of any of your own IPR *that is necessar=
ily infringed* by implementing your contribution, you must disclose. And wh=
at it means to be "necessarily infringed" has some details to it, and it mi=
ght not be even implementation that causes the problem. And that's why it s=
ays at the top of the current document that there are exceptions.
>=20
>> see - its not that hard to say this briefly
>=20
> Really, it is quite hard to state the rules briefly such that it doesn't =
include *more* than you are required to do. Your statement did not.
>=20
> pr
>=20
> --=20
> Pete Resnick<http://www.qualcomm.com/~presnick/>
> Qualcomm Technologies, Inc. - +1 (858)651-4478
>=20


From samita.chakrabarti@ericsson.com  Thu Jan 23 11:57:41 2014
Return-Path: <samita.chakrabarti@ericsson.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B39A1A0056 for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 11:57:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8sBXvF73-Nzk for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 11:57:38 -0800 (PST)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id 0CC991A001D for <wgchairs@ietf.org>; Thu, 23 Jan 2014 11:57:38 -0800 (PST)
X-AuditID: c6180641-b7f2f8e000002cdc-59-52e17431dad7
Received: from EUSAAHC004.ericsson.se (Unknown_Domain [147.117.188.84]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id E4.AA.11484.13471E25; Thu, 23 Jan 2014 20:57:37 +0100 (CET)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC004.ericsson.se ([147.117.188.84]) with mapi id 14.02.0387.000; Thu, 23 Jan 2014 14:57:37 -0500
From: Samita Chakrabarti <samita.chakrabarti@ericsson.com>
To: Robert Sparks <rjsparks@nostrum.com>
Subject: RE: Please double-check your group's archive in the web-based email list archive tool
Thread-Topic: Please double-check your group's archive in the web-based email list archive tool
Thread-Index: AQHPF7v/zVwBAIJ7HE6QAT4o+BHigpqS3qcAgAAEbwCAAAWgAP//0D3g
Date: Thu, 23 Jan 2014 19:57:35 +0000
Message-ID: <ECA43DA70480A3498E43C3471FB2E1F01C145A7A@eusaamb103.ericsson.se>
References: <52E03D0E.5060703@nostrum.com> <FBD5AAFFD0978846BF6D3FAB4C892ACC10019832@SEA-EXMB-2.telecomsys.com> <CADJ9OA9HLC=883ONWN2davbAkMStfjy1sLpV6ksgkudnqVdR5w@mail.gmail.com> <CAP+sJUfv46Y5xUiON8w6oNJ=fuzpqOHcq66u+7Q0DJg7XiQ-MA@mail.gmail.com>
In-Reply-To: <CAP+sJUfv46Y5xUiON8w6oNJ=fuzpqOHcq66u+7Q0DJg7XiQ-MA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.9]
Content-Type: multipart/alternative; boundary="_000_ECA43DA70480A3498E43C3471FB2E1F01C145A7Aeusaamb103erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrKLMWRmVeSWpSXmKPExsUyuXRPiK5hycMggydd6hbX5jSyWfzfP4XR gcljyZKfTB6zdj5hCWCK4rJJSc3JLEst0rdL4MrovjuTpeCDfcXTjx1MDYz7zbsYOTgkBEwk Zm1N7GLkBDLFJC7cW8/WxcjFISRwhFFi3omDzBDOckaJ091djCBVbAJWEh29e9hBbBEBDYlr S5aA2cwCuhKHPm5kArGFBRIkHp7cxwRRkyix+mkvK4TtJrGm9xBYnEVAVeLN81tgNq+Ar8SW 0y/YIZb9Z5TYfXY5M8h1nAKBEmv+g+1lBLru+6k1TBC7xCVuPZnPBHG1gMSSPeeZIWxRiZeP /7FC2IoS+/qnQ92WL3Hvzx12iF2CEidnPmGZwCg6C8moWUjKZiEpg4jrSCzY/YkNwtaWWLbw NTOMfebAYyZk8QWM7KsYOUqLU8ty040MNzECo+qYBJvjDsYFnywPMUpzsCiJ83556xwkJJCe WJKanZpakFoUX1Sak1p8iJGJg1OqgVHuzmLR/KfaP+7peu/rqRYpnbky10cifnXUDyfZb/mv j/iHnJ83PbFiYZbLq56U80leh8WTJb9lW19aZ7J663rLTb+THFaEM7D91/2494D3d9MDr/y3 2z2+/dRqWffZqqfbp+2e3NeiwplxdaLpDY0uyz//wh6s2yHzb4HgNN7ODo4ScbP9RjOVWIoz Eg21mIuKEwHLm0h6eAIAAA==
Cc: "<wgchairs@ietf.org>" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 19:57:41 -0000

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


Cool searching tool! I like the feature of going to https://mailarchive.iet=
f.org/arch/  and then  searching for the "wg" name to begin with and it als=
o shows other related working groups in the filtered list.

-Samita

-----Original Message-----
From: WGChairs [mailto:wgchairs-bounces@ietf.org<mailto:wgchairs-bounces@ie=
tf.org>] On Behalf Of Robert Sparks
Sent: Wednesday, January 22, 2014 1:50 PM
To: <wgchairs@ietf.org<mailto:wgchairs@ietf.org>>
Subject: Please double-check your group's archive in the web-based email li=
st archive tool

Chairs -

If you have not already done so, please look briefly at your lists in the n=
ew tool and make sure you see what you expect.

You can browse quickly to them with a URL like:

<https://mailarchive.ietf.org/arch/search/?email_list=3Dstir>

Click the date column header twice (the first time will give you a most-rec=
ent to least-recent view, and the second the reverse), or jump straight to =
a URL like <https://mailarchive.ietf.org/arch/search/?email_list=3Dstir&so=
=3Ddate>
and check that the archive goes back as far as you expect.

Note that you can pull the division between the message list pane and the m=
essage preview pane down to allow you to see more of the messages in the li=
st at one time.

If you discover something that needs attention, please file a ticket at <ht=
tp://trac.tools.ietf.org/tools/ietfdb/newticket>

RjS
CONFIDENTIALITY NOTICE: The information contained in this message may be pr=
ivileged and/or confidential. If you are not the intended recipient, or res=
ponsible for delivering this message to the intended recipient, any review,=
 forwarding, dissemination, distribution or copying of this communication o=
r any attachment(s) is strictly prohibited. If you have received this messa=
ge in error, please notify the sender immediately, and delete it and all at=
tachments from your computer and network.



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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.hoenzb
	{mso-style-name:hoenzb;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Cool searching tool! I li=
ke the feature of going to
<a href=3D"https://mailarchive.ietf.org/arch/">https://mailarchive.ietf.org=
/arch/</a>&nbsp; and then&nbsp; searching for the &#8220;wg&#8221; name to =
begin with and it also shows other related working groups in the filtered l=
ist.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">-Samita<o:p></o:p></span>=
</p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:0in;margin-right:0in;mar=
gin-bottom:12.0pt;margin-left:.5in">
<br>
-----Original Message-----<br>
From: WGChairs [mailto:<a href=3D"mailto:wgchairs-bounces@ietf.org" target=
=3D"_blank">wgchairs-bounces@ietf.org</a>] On Behalf Of Robert Sparks<br>
Sent: Wednesday, January 22, 2014 1:50 PM<br>
To: &lt;<a href=3D"mailto:wgchairs@ietf.org" target=3D"_blank">wgchairs@iet=
f.org</a>&gt;<br>
Subject: Please double-check your group's archive in the web-based email li=
st archive tool<br>
<br>
Chairs -<br>
<br>
If you have not already done so, please look briefly at your lists in the n=
ew tool and make sure you see what you expect.<br>
<br>
You can browse quickly to them with a URL like:<br>
<br>
&lt;<a href=3D"https://mailarchive.ietf.org/arch/search/?email_list=3Dstir"=
 target=3D"_blank">https://mailarchive.ietf.org/arch/search/?email_list=3Ds=
tir</a>&gt;<br>
<br>
Click the date column header twice (the first time will give you a most-rec=
ent to least-recent view, and the second the reverse), or jump straight to =
a URL like &lt;<a href=3D"https://mailarchive.ietf.org/arch/search/?email_l=
ist=3Dstir&amp;so=3Ddate" target=3D"_blank">https://mailarchive.ietf.org/ar=
ch/search/?email_list=3Dstir&amp;so=3Ddate</a>&gt;<br>
and check that the archive goes back as far as you expect.<br>
<br>
Note that you can pull the division between the message list pane and the m=
essage preview pane down to allow you to see more of the messages in the li=
st at one time.<br>
<br>
If you discover something that needs attention, please file a ticket at &lt=
;<a href=3D"http://trac.tools.ietf.org/tools/ietfdb/newticket" target=3D"_b=
lank">http://trac.tools.ietf.org/tools/ietfdb/newticket</a>&gt;<br>
<br>
RjS<o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">CONFIDENTIALITY NOTICE: T=
he information contained in this message may be privileged and/or confident=
ial. If you are not the intended recipient, or responsible for delivering t=
his message to the intended recipient,
 any review, forwarding, dissemination, distribution or copying of this com=
munication or any attachment(s) is strictly prohibited. If you have receive=
d this message in error, please notify the sender immediately, and delete i=
t and all attachments from your
 computer and network.<o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_ECA43DA70480A3498E43C3471FB2E1F01C145A7Aeusaamb103erics_--

From sob@harvard.edu  Thu Jan 23 12:19:23 2014
Return-Path: <sob@harvard.edu>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA6401A00ED for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 12:19:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.135
X-Spam-Level: 
X-Spam-Status: No, score=-3.135 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ax2KqJOeCvjI for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 12:19:22 -0800 (PST)
Received: from ackroyd.harvard.edu (ackroyd.harvard.edu [128.103.208.29]) by ietfa.amsl.com (Postfix) with ESMTP id 53CB61A0049 for <wgchairs@ietf.org>; Thu, 23 Jan 2014 12:19:22 -0800 (PST)
Received: from ENTWEDGE0000001.university.harvard.edu (entwedge0000001.university.harvard.edu [10.35.2.152]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ackroyd.harvard.edu (Postfix) with ESMTP id 2DA74E94F9; Thu, 23 Jan 2014 15:19:21 -0500 (EST)
Received: from ENTWHUBT0000004.university.harvard.edu (10.32.208.50) by ENTWEDGE0000001.university.harvard.edu (10.35.2.152) with Microsoft SMTP Server (TLS) id 14.3.146.0; Thu, 23 Jan 2014 15:18:48 -0500
Received: from ENTWEXMB0000008.university.harvard.edu ([169.254.1.46]) by ENTWHUBT0000004.university.harvard.edu ([10.32.208.50]) with mapi id 14.03.0146.000; Thu, 23 Jan 2014 15:19:20 -0500
From: "Bradner, Scott" <sob@harvard.edu>
To: "Banks, Sarah" <sbanks@akamai.com>
Subject: Re: Please double-check your group's archive in the web-based email list archive tool
Thread-Topic: Please double-check your group's archive in the web-based email list archive tool
Thread-Index: AQHPGHhlJxpUWzmzg0GGx6pKnotZOA==
Date: Thu, 23 Jan 2014 20:19:19 +0000
Message-ID: <8D1B238B-3A4E-48F7-BCD6-C5F7ED404A9C@harvard.edu>
References: <52E03D0E.5060703@nostrum.com> <CF0693EB.AAB%sbanks@akamai.com>
In-Reply-To: <CF0693EB.AAB%sbanks@akamai.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [136.248.127.162]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <C806A704EE6B4745886284BEDB54C05F@Exchange.university.harvard.edu>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<wgchairs@ietf.org>" <wgchairs@ietf.org>, Robert Sparks <rjsparks@nostrum.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 20:19:24 -0000

since bmwg goes back to 1990 it would be better if all of the email was inc=
luded

Scott

On Jan 23, 2014, at 12:40 PM, Banks, Sarah <sbanks@akamai.com> wrote:

> Hi Robert,
> 	BMWG looks great; our archives go back to 2001, but that's probably OK.
> The interface is awesome! Thanks!
>=20
> Regards,
> Sarah
>=20
> On 1/22/14, 1:50 PM, "Robert Sparks" <rjsparks@nostrum.com> wrote:
>=20
>> Chairs -
>>=20
>> If you have not already done so, please look briefly at your lists in
>> the new tool and make sure you see what you expect.
>>=20
>> You can browse quickly to them with a URL like:
>>=20
>> <https://mailarchive.ietf.org/arch/search/?email_list=3Dstir>
>>=20
>> Click the date column header twice (the first time will give you a
>> most-recent to least-recent view, and the second the reverse),
>> or jump straight to a URL like
>> <https://mailarchive.ietf.org/arch/search/?email_list=3Dstir&so=3Ddate>
>> and check that the archive goes back as far as you expect.
>>=20
>> Note that you can pull the division between the message list pane and
>> the message preview pane down to allow you to see more of the messages
>> in the list at one time.
>>=20
>> If you discover something that needs attention, please file a ticket at
>> <http://trac.tools.ietf.org/tools/ietfdb/newticket>
>>=20
>> RjS
>=20

Scott O. Bradner
Senior Technical Consultant

Harvard University Information Technology
Innovation & Architecture
+1 617 495 3864
8 Story St, Room 5014
Cambridge, MA 02138
www.huit.harvard.edu





From presnick@qti.qualcomm.com  Thu Jan 23 12:56:15 2014
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBE021A01B3; Thu, 23 Jan 2014 12:56:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level: 
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r3-Mxf6YeCU8; Thu, 23 Jan 2014 12:56:14 -0800 (PST)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id 0B95B1A0161; Thu, 23 Jan 2014 12:56:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1390510573; x=1422046573; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=oByWaso0T/b65bQQh3DHhEEyJIfaRK6176tfe7Sd0nk=; b=svWhhvE+AEe5wPvqjdSUKu7IRwgaB3yZhGChScxeJBRqR3Qml9evUZQt zYhrSqP0Tnp9ewdc5naNxvNV5bx/mFIYqeFNACyrKi6fNVtWfRkkALQLb glIIyuVi75ak/ZzoRbcpWtSect50Dz76LbgNDKv2jYfJ7zafNW76wfnUY w=;
X-IronPort-AV: E=McAfee;i="5400,1158,7327"; a="58466922"
Received: from ironmsg02-lv.qualcomm.com ([10.47.202.183]) by sabertooth01.qualcomm.com with ESMTP; 23 Jan 2014 12:56:12 -0800
X-IronPort-AV: E=McAfee;i="5400,1158,7327"; a="26081114"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by ironmsg02-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 23 Jan 2014 12:56:12 -0800
Received: from presnick-mac.local (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 23 Jan 2014 12:50:12 -0800
Message-ID: <52E18081.1010709@qti.qualcomm.com>
Date: Thu, 23 Jan 2014 14:50:09 -0600
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: "Bradner, Scott" <sob@harvard.edu>
Subject: Re: Problem with new Note Well
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E15AE2.7030508@qti.qualcomm.com> <E3E4E04A-B342-4FDC-89EC-5FC8F7CEAAF0@harvard.edu>
In-Reply-To: <E3E4E04A-B342-4FDC-89EC-5FC8F7CEAAF0@harvard.edu>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 8bit
X-Originating-IP: [172.30.48.1]
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, Jorge Contreras <contreraslegal@att.net>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 20:56:16 -0000

On 1/23/14 1:56 PM, Bradner, Scott wrote:
> while, in the end, this is true (the "necessarily infringed” requirement) I do not think it is a good thing to obsess about at the disclose-so-the-working-group-can-evaluate-the-technology stage since it is impossible to know if any particular IPR will wind up in this catagory until a RFC is finished - which would negate the whole reason for the disclosure
>    

I generally agree with that, though I think this gets to why I think 
having the "Note Well" state a plain-English, imprecise, overbroad 
summary is the right thing to do: The Note Well text should say, "You 
have to disclose IPR you know about. Not always, but maybe more than you 
think. If you're worried about specifically what, when, who, and how, 
you need to go read these other documents, and once you start 
participating, you've agreed to the specifics of what's in those 
documents. Got it?" Part of the reason that some of us pushed to change 
the current Note Well text was because people were *underdisclosing* 
what they were absolutely required to disclose by the BCP.

I'm really concerned about the amateur lawyering. If you're worried 
about this, go consult an attorney. The IESG consulted with Jorge about 
what's up there now, and though he preferred some additional escape 
clauses, he found the current text acceptable. If a bunch of corporate 
attorneys come out of the woodwork and say that they can't let their 
employees hit the "Acknowledge" button on the registration page, we'll 
revisit the issue I'm sure. But my guess is that you'll find that the 
exception language on the page now is sufficient to make them happy.

> maybe we should make that clear (disclose if you suspect that IPR relates not “is necessarily infringed”) in the 3979 update - this is what the rule used to be and the language Pete is focussing on was added and, apparently, has an undesired side effect
>    

I think you'll find that such a change is likely to (a) produce an 
unmanageable number of disclosures (because "you suspect that IPR 
relates" is a pretty low bar) and (b) that such a rule will cause 
heartburn among a bunch of folks. I'm not saying it's the wrong 
direction, but it's not obvious that it's the right direction either.

pr

> On Jan 23, 2014, at 1:09 PM, Pete Resnick<presnick@qti.qualcomm.com>  wrote:
>
>    
>> On 1/23/14 11:58 AM, Bradner, Scott wrote:
>>      
>>> the actual rules are
>>> 	1/ if you know of any of your IPR in a contribution you make, you must disclose
>>>
>>>        
>> No, that's not true. If you know of any of your own IPR *that is necessarily infringed* by implementing your contribution, you must disclose. And what it means to be "necessarily infringed" has some details to it, and it might not be even implementation that causes the problem. And that's why it says at the top of the current document that there are exceptions.
>>
>>      
>>> see - its not that hard to say this briefly
>>>        
>> Really, it is quite hard to state the rules briefly such that it doesn't include *more* than you are required to do. Your statement did not.
>>
>> pr

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


From ted.ietf@gmail.com  Thu Jan 23 13:48:17 2014
Return-Path: <ted.ietf@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CBA81A0384; Thu, 23 Jan 2014 13:48:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2r8n21OQq4pU; Thu, 23 Jan 2014 13:48:14 -0800 (PST)
Received: from mail-ie0-x236.google.com (mail-ie0-x236.google.com [IPv6:2607:f8b0:4001:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 90D241A0380; Thu, 23 Jan 2014 13:48:14 -0800 (PST)
Received: by mail-ie0-f182.google.com with SMTP id lx4so1946832iec.13 for <multiple recipients>; Thu, 23 Jan 2014 13:48:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=0jPnA73ijg2L2TDlU5j13UgZLJblLZp/4g+ki8rvJSU=; b=FjpDpCCtniYnHzUehm+vuiCGpeelpzerBbVIdKQQGrEfTU9lf6YLlCTJAyHa4LNmB3 fGj1KN8hiS4xvvDesrxmUfJCOoGnhxyQZ2icnAbmTQvUbEaoy6NNATgKKrFQes2nQZTE Xlu/h0u928EH28ixVQx99JkzyU+iZ1OdeaM6OijrDcbIl/5A7rqHXWgLZzRPbyB8aVyt NkwvFp/anreO2tVkKouAbQHufAUVsc7uMooDRL7Pjai7dDKEU4r2MWUt6AtZVLKPBOLS 0tLswQ6sg4IPjU9zABBa1247e1DTQpAAAY1s1/FPfPrcEhptKLMZZnPoGWtTegLeynPa 8gVQ==
MIME-Version: 1.0
X-Received: by 10.50.60.99 with SMTP id g3mr1443626igr.13.1390513693577; Thu, 23 Jan 2014 13:48:13 -0800 (PST)
Received: by 10.43.65.14 with HTTP; Thu, 23 Jan 2014 13:48:13 -0800 (PST)
In-Reply-To: <52E18081.1010709@qti.qualcomm.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E15AE2.7030508@qti.qualcomm.com> <E3E4E04A-B342-4FDC-89EC-5FC8F7CEAAF0@harvard.edu> <52E18081.1010709@qti.qualcomm.com>
Date: Thu, 23 Jan 2014 13:48:13 -0800
Message-ID: <CA+9kkMAdBnwGEVf86F8wiX1R3h81cADuv7RS-L3a1ttML-bP_g@mail.gmail.com>
Subject: Re: Problem with new Note Well
From: Ted Hardie <ted.ietf@gmail.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Content-Type: multipart/alternative; boundary=047d7b10cf25c2d82404f0aa3228
Cc: IETF WG Chairs <wgchairs@ietf.org>, Jorge Contreras <contreraslegal@att.net>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 21:48:17 -0000

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

On Thu, Jan 23, 2014 at 12:50 PM, Pete Resnick <presnick@qti.qualcomm.com>w=
rote:

> On 1/23/14 1:56 PM, Bradner, Scott wrote:
>
>> while, in the end, this is true (the "necessarily infringed=94 requireme=
nt)
>> I do not think it is a good thing to obsess about at the
>> disclose-so-the-working-group-can-evaluate-the-technology stage since it
>> is impossible to know if any particular IPR will wind up in this catagor=
y
>> until a RFC is finished - which would negate the whole reason for the
>> disclosure
>>
>>
>
> I generally agree with that, though I think this gets to why I think
> having the "Note Well" state a plain-English, imprecise, overbroad summar=
y
> is the right thing to do: The Note Well text should say, "You have to
> disclose IPR you know about. Not always, but maybe more than you think. I=
f
> you're worried about specifically what, when, who, and how, you need to g=
o
> read these other documents, and once you start participating, you've agre=
ed
> to the specifics of what's in those documents. Got it?" Part of the reaso=
n
> that some of us pushed to change the current Note Well text was because
> people were *underdisclosing* what they were absolutely required to
> disclose by the BCP.
>
> I'm really concerned about the amateur lawyering. If you're worried about
> this, go consult an attorney. The IESG consulted with Jorge about what's =
up
> there now, and though he preferred some additional escape clauses, he fou=
nd
> the current text acceptable. If a bunch of corporate attorneys come out o=
f
> the woodwork and say that they can't let their employees hit the
> "Acknowledge" button on the registration page, we'll revisit the issue I'=
m
> sure. But my guess is that you'll find that the exception language on the
> page now is sufficient to make them happy.
>
> I had a quick chat with our legal folks.  They understood that the intent
of the new Note Well language was to give a heads up that there are rules
which are presented elsewhere.  They did feel, however, that the second
bullet captured that
spirit
less well than the first.  Perhaps language that said something like "You
are aware that there are patent disclosure requirements" would do that
slightly better.


regards,

Ted





>
>  maybe we should make that clear (disclose if you suspect that IPR relate=
s
>> not =93is necessarily infringed=94) in the 3979 update - this is what th=
e rule
>> used to be and the language Pete is focussing on was added and, apparent=
ly,
>> has an undesired side effect
>>
>>
>
> I think you'll find that such a change is likely to (a) produce an
> unmanageable number of disclosures (because "you suspect that IPR relates=
"
> is a pretty low bar) and (b) that such a rule will cause heartburn among =
a
> bunch of folks. I'm not saying it's the wrong direction, but it's not
> obvious that it's the right direction either.
>
> pr
>
>
>  On Jan 23, 2014, at 1:09 PM, Pete Resnick<presnick@qti.qualcomm.com>
>>  wrote:
>>
>>
>>
>>> On 1/23/14 11:58 AM, Bradner, Scott wrote:
>>>
>>>
>>>> the actual rules are
>>>>         1/ if you know of any of your IPR in a contribution you make,
>>>> you must disclose
>>>>
>>>>
>>>>
>>> No, that's not true. If you know of any of your own IPR *that is
>>> necessarily infringed* by implementing your contribution, you must
>>> disclose. And what it means to be "necessarily infringed" has some deta=
ils
>>> to it, and it might not be even implementation that causes the problem.=
 And
>>> that's why it says at the top of the current document that there are
>>> exceptions.
>>>
>>>
>>>
>>>> see - its not that hard to say this briefly
>>>>
>>>>
>>> Really, it is quite hard to state the rules briefly such that it doesn'=
t
>>> include *more* than you are required to do. Your statement did not.
>>>
>>> pr
>>>
>>
> --
> Pete Resnick<http://www.qualcomm.com/~presnick/>
> Qualcomm Technologies, Inc. - +1 (858)651-4478
>
>

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

<div dir=3D"ltr"><div class=3D"gmail_extra">On Thu, Jan 23, 2014 at 12:50 P=
M, Pete Resnick <span dir=3D"ltr">&lt;<a href=3D"mailto:presnick@qti.qualco=
mm.com" target=3D"_blank">presnick@qti.qualcomm.com</a>&gt;</span> wrote:<b=
r><div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex"><div class=3D"im">On 1/23=
/14 1:56 PM, Bradner, Scott wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
while, in the end, this is true (the &quot;necessarily infringed=94 require=
ment) I do not think it is a good thing to obsess about at the disclose-so-=
the-working-group-<u></u>can-evaluate-the-technology stage since it is impo=
ssible to know if any particular IPR will wind up in this catagory until a =
RFC is finished - which would negate the whole reason for the disclosure<br=
>

=A0 =A0<br>
</blockquote>
<br></div>
I generally agree with that, though I think this gets to why I think having=
 the &quot;Note Well&quot; state a plain-English, imprecise, overbroad summ=
ary is the right thing to do: The Note Well text should say, &quot;You have=
 to disclose IPR you know about. Not always, but maybe more than you think.=
 If you&#39;re worried about specifically what, when, who, and how, you nee=
d to go read these other documents, and once you start participating, you&#=
39;ve agreed to the specifics of what&#39;s in those documents. Got it?&quo=
t; Part of the reason that some of us pushed to change the current Note Wel=
l text was because people were *underdisclosing* what they were absolutely =
required to disclose by the BCP.<br>

<br>
I&#39;m really concerned about the amateur lawyering. If you&#39;re worried=
 about this, go consult an attorney. The IESG consulted with Jorge about wh=
at&#39;s up there now, and though he preferred some additional escape claus=
es, he found the current text acceptable. If a bunch of corporate attorneys=
 come out of the woodwork and say that they can&#39;t let their employees h=
it the &quot;Acknowledge&quot; button on the registration page, we&#39;ll r=
evisit the issue I&#39;m sure. But my guess is that you&#39;ll find that th=
e exception language on the page now is sufficient to make them happy.<div =
class=3D"im">
<br></div></blockquote><div><span style=3D"color:rgb(34,34,34);font-family:=
arial,sans-serif;font-size:12.8px;font-style:normal;font-variant:normal;fon=
t-weight:normal;letter-spacing:normal;line-height:normal;text-align:left;te=
xt-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;backg=
round-color:rgb(255,255,255);display:inline!important;float:none">I had a q=
uick chat with our legal folks. =A0They understood that the intent of the n=
ew Note Well language was to give a heads up that there are rules which are=
 presented elsewhere. =A0They did feel, however, that the second bullet cap=
tured that=A0<div class=3D"gmail_default" style=3D"font-family:georgia,seri=
f;display:inline">
spirit</div> less well than the first. =A0Perhaps language that said someth=
ing like &quot;You are aware that there are patent disclosure requirements&=
quot; would do that slightly better.</span><br><br><br><div class=3D"gmail_=
default" style=3D"font-family:georgia,serif">
regards,<br><br>Ted</div><br><br><br>=A0</div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,20=
4);padding-left:1ex"><div class=3D"im">
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
maybe we should make that clear (disclose if you suspect that IPR relates n=
ot =93is necessarily infringed=94) in the 3979 update - this is what the ru=
le used to be and the language Pete is focussing on was added and, apparent=
ly, has an undesired side effect<br>

=A0 =A0<br>
</blockquote>
<br></div>
I think you&#39;ll find that such a change is likely to (a) produce an unma=
nageable number of disclosures (because &quot;you suspect that IPR relates&=
quot; is a pretty low bar) and (b) that such a rule will cause heartburn am=
ong a bunch of folks. I&#39;m not saying it&#39;s the wrong direction, but =
it&#39;s not obvious that it&#39;s the right direction either.<span class=
=3D""><font color=3D"#888888"><br>

<br>
pr</font></span><div class=3D""><div class=3D"h5"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
On Jan 23, 2014, at 1:09 PM, Pete Resnick&lt;<a href=3D"mailto:presnick@qti=
.qualcomm.com" target=3D"_blank">presnick@qti.qualcomm.<u></u>com</a>&gt; =
=A0wrote:<br>
<br>
=A0 =A0<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
On 1/23/14 11:58 AM, Bradner, Scott wrote:<br>
=A0 =A0 =A0<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
the actual rules are<br>
=A0 =A0 =A0 =A0 1/ if you know of any of your IPR in a contribution you mak=
e, you must disclose<br>
<br>
=A0 =A0 =A0 =A0<br>
</blockquote>
No, that&#39;s not true. If you know of any of your own IPR *that is necess=
arily infringed* by implementing your contribution, you must disclose. And =
what it means to be &quot;necessarily infringed&quot; has some details to i=
t, and it might not be even implementation that causes the problem. And tha=
t&#39;s why it says at the top of the current document that there are excep=
tions.<br>

<br>
=A0 =A0 =A0<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
see - its not that hard to say this briefly<br>
=A0 =A0 =A0 =A0<br>
</blockquote>
Really, it is quite hard to state the rules briefly such that it doesn&#39;=
t include *more* than you are required to do. Your statement did not.<br>
<br>
pr<br>
</blockquote></blockquote>
<br>
-- <br>
Pete Resnick&lt;<a href=3D"http://www.qualcomm.com/~presnick/" target=3D"_b=
lank">http://www.qualcomm.<u></u>com/~presnick/</a>&gt;<br>
Qualcomm Technologies, Inc. - <a href=3D"tel:%2B1%20%28858%29651-4478" valu=
e=3D"+18586514478" target=3D"_blank">+1 (858)651-4478</a><br>
<br>
</div></div></blockquote></div><br></div></div>

--047d7b10cf25c2d82404f0aa3228--

From fluffy@cisco.com  Thu Jan 23 14:30:28 2014
Return-Path: <fluffy@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 749BD1A035C; Thu, 23 Jan 2014 14:30:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.036
X-Spam-Level: 
X-Spam-Status: No, score=-110.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S3uPF6wX4CFy; Thu, 23 Jan 2014 14:30:24 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) by ietfa.amsl.com (Postfix) with ESMTP id E1E951A023D; Thu, 23 Jan 2014 14:30:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1284; q=dns/txt; s=iport; t=1390516223; x=1391725823; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=BQ6Wn+QTo3jfS3CYV/2fFkEaUZbmJ816z/BUf5IbU0o=; b=RlxKfYJbHjZ9mpG0ScusRvK0bVx+EFbfhkHr9NdM4DNICIu10E6gFMCL S6q+2BPDBwXoI/WjKtOKTdx1/YguCuzfian2nzqcDujEkCA7PmoFt3umb YtjCCornDQF0a7FcG7biBy4X7RGUTDvahcbP7H2P0FnT1x1eGm2GvZCwa w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhYFACqX4VKtJV2b/2dsb2JhbABagwyBDrw3gRUWdIIlAQEBAwF5BQsCAQgOCi4yJQIEDgWHfQjHHheOTTMHgySBFAEDiRCPE5IYgy2CKg
X-IronPort-AV: E=Sophos;i="4.95,709,1384300800"; d="scan'208";a="15116727"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-6.cisco.com with ESMTP; 23 Jan 2014 22:30:18 +0000
Received: from xhc-aln-x02.cisco.com (xhc-aln-x02.cisco.com [173.36.12.76]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s0NMUI1Y026540 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 23 Jan 2014 22:30:18 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.76]) by xhc-aln-x02.cisco.com ([173.36.12.76]) with mapi id 14.03.0123.003; Thu, 23 Jan 2014 16:30:18 -0600
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Problem with new Note Well
Thread-Topic: Problem with new Note Well
Thread-Index: AQHPGIqxCJjiC+6Mn0KbkcizeejIsw==
Date: Thu, 23 Jan 2014 22:30:17 +0000
Message-ID: <057D93E6-9311-44AA-A7B0-685FBB850D5F@cisco.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <52E15937.8010600@qti.qualcomm.com> <18480766-BA47-445B-8C75-5DD261F94A76@cisco.com> <52E15EAA.8060301@qti.qualcomm.com>
In-Reply-To: <52E15EAA.8060301@qti.qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <C0286DA5CB82B94DBC3E3F7992761733@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 22:30:28 -0000

On Jan 23, 2014, at 11:25 AM, Pete Resnick <presnick@qti.qualcomm.com> wrot=
e:

> On 1/23/14 12:07 PM, Cullen Jennings (fluffy) wrote:
>> Pete,  what do you think "Acknowledge" means on a from like this? ( I wi=
ll note it does not say "I Acknowledge I read this but may not agree with i=
t" )
>>  =20
>=20
> You are acknowledging that there are rules (not fully specified here) tha=
t you have to go read and abide by if you show up and participate at the me=
eting. When you show up and participate at the meeting, you are agreeing to=
 a bunch of things that are not on this page.
>=20
> Are you saying that you don't agree that there are exceptions to what's o=
n this page?
>=20

Pete, I am saying that this page is likely to be used to undermine the cred=
ibility of IETF participants in patent trials. That is a bad thing.=20

We both agree the BCPs do NOT say=20

    If you are aware that any contribution (something written, said, or dis=
cussed in any IETF context) is covered by patents or patent applications, y=
ou must disclose that fact.

So I do not think it is OK for the IESG to be making me click "Acknowledge"=
 to a page that contains the above sentence. I have no problem with acknowl=
edging I am bound by the rules BCP 79.=20











From l.wood@surrey.ac.uk  Thu Jan 23 14:08:48 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82F891A00AA; Thu, 23 Jan 2014 14:08:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nX8fG-v5Wz7s; Thu, 23 Jan 2014 14:08:47 -0800 (PST)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.153]) by ietfa.amsl.com (Postfix) with ESMTP id 37EC71A0091; Thu, 23 Jan 2014 14:08:46 -0800 (PST)
Received: from [85.158.136.51:43593] by server-17.bemta-5.messagelabs.com id 65/FB-19152-CE291E25; Thu, 23 Jan 2014 22:08:44 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-4.tower-49.messagelabs.com!1390514924!18829655!1
X-Originating-IP: [131.227.200.31]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 26082 invoked from network); 23 Jan 2014 22:08:44 -0000
Received: from exht011p.surrey.ac.uk (HELO EXHT011P.surrey.ac.uk) (131.227.200.31) by server-4.tower-49.messagelabs.com with AES128-SHA encrypted SMTP; 23 Jan 2014 22:08:44 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT011P.surrey.ac.uk ([131.227.200.31]) with mapi; Thu, 23 Jan 2014 22:08:43 +0000
From: <l.wood@surrey.ac.uk>
To: <presnick@qti.qualcomm.com>, <fluffy@cisco.com>
Date: Thu, 23 Jan 2014 22:08:12 +0000
Subject: RE: Problem with new Note Well
Thread-Topic: Problem with new Note Well
Thread-Index: Ac8YZWs8U98barEPT3q+jCOoIA73CAAIjBFM
Message-ID: <290E20B455C66743BE178C5C84F1240847E63346E5@EXMB01CMS.surrey.ac.uk>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com>, <52E15937.8010600@qti.qualcomm.com>
In-Reply-To: <52E15937.8010600@qti.qualcomm.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Thu, 23 Jan 2014 14:39:06 -0800
Cc: wgchairs@ietf.org, ietf@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 22:08:48 -0000

Pete,

is that your qualified legal opinion in the appropriate jurisdiction?

thanks,

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Pete Resnick [presnick@qti.=
qualcomm.com]
Sent: 23 January 2014 18:02
To: Cullen Jennings (fluffy)
Cc: IETF WG Chairs; ietf@ietf.org Mailing List; Scott Bradner; IESG IESG; M=
ary Barnes
Subject: Re: Problem with new Note Well

On 1/23/14 11:25 AM, Cullen Jennings (fluffy) wrote:
> This new note well is a real problem for me and  I can not register witho=
ut clicking "I agree" to it.

You are not asked to click "I agree" to any statement. You are asked to
"Acknowledge" that you read it. And the statement says right at the top:

"This summary is only meant to point you in the right direction, and
does not contain all the details. Exceptions may apply."

So by participating, there are things that you are agreeing to that are
not on this page, and there are exceptions to things on this page that
you don't have to agree to do.

The only thing that this page does is make you "Acknowledge" that you've
got homework to do about rules for your participation.

pr

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


From worley@shell01.TheWorld.com  Thu Jan 23 14:45:16 2014
Return-Path: <worley@shell01.TheWorld.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E3B71A0380 for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 14:45:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OGSAoMwpTgnm for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2014 14:45:15 -0800 (PST)
Received: from TheWorld.com (pcls6.std.com [192.74.137.146]) by ietfa.amsl.com (Postfix) with ESMTP id 50F3C1A045A for <wgchairs@ietf.org>; Thu, 23 Jan 2014 14:45:14 -0800 (PST)
Received: from shell.TheWorld.com (root@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id s0NMj79x030817; Thu, 23 Jan 2014 17:45:09 -0500
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id s0NMj6CJ3448760; Thu, 23 Jan 2014 17:45:06 -0500 (EST)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id s0NMj6uH3447931; Thu, 23 Jan 2014 17:45:06 -0500 (EST)
Date: Thu, 23 Jan 2014 17:45:06 -0500 (EST)
Message-Id: <201401232245.s0NMj6uH3447931@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: Pete Resnick <presnick@qti.qualcomm.com>
In-reply-to: <52E15937.8010600@qti.qualcomm.com> (presnick@qti.qualcomm.com)
Subject: Re: Problem with new Note Well
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <52E15937.8010600@qti.qualcomm.com>
X-Mailman-Approved-At: Thu, 23 Jan 2014 14:50:03 -0800
Cc: fluffy@cisco.com, wgchairs@ietf.org, ietf@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 22:45:16 -0000

> From: Pete Resnick <presnick@qti.qualcomm.com>
> 
> You are not asked to click "I agree" to any statement. You are asked
> to "Acknowledge" that you read it. And the statement says right at
> the top:
> 
> "This summary is only meant to point you in the right direction, and 
> does not contain all the details. Exceptions may apply."

> From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
> 
> "If you are aware that any contribution (something written, said, or
> discussed in any IETF context) is covered by patents or patent
> applications, you must disclose that fact."

Surely we can write a better statement than what Cullen quotes.  To
begin with, it contains the word "must".  And while the statment is
amplified with "does not contain all the details", can we not provide
a proper pointer to the details?

Not being fully informed about this subject, it seems to me that it
would be far better to say:

    "By participating in an IETF discussion, you agree that if you are
    aware that any contribution (something written, said, or discussed
    in any IETF context) to that discussion is covered by patents or
    patent applications, you may be required to disclose that fact.
    The specific requirements are described in BCP 79."

Dale

From fluffy@cisco.com  Thu Jan 23 14:50:40 2014
Return-Path: <fluffy@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A420F1A0403; Thu, 23 Jan 2014 14:50:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -115.036
X-Spam-Level: 
X-Spam-Status: No, score=-115.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fbmSC2rKxRf6; Thu, 23 Jan 2014 14:50:37 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id C5BA31A007C; Thu, 23 Jan 2014 14:50:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1467; q=dns/txt; s=iport; t=1390517437; x=1391727037; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=+KUxHza109fhyW0j1DNTqxTElZWmUUKlsPcbx8uhwmQ=; b=T86SHDRgcZAUc9MePpWk/MPN8rQxMpns8NziGHSM4h/7Jjn0y6tU00EL wxReI/SM/l0frVZCyrYIDUekmPdDjNNdg0FL6HfSiP50HtQ7MetHs96lY aC/MB/c6PlYtHnnc+DOT5nRRWt5EYQ7AWmdZ6ibtxavKzFsi+LH1Z5faR E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhYFAGqc4VKtJXHB/2dsb2JhbABagwyBDrw3gRYWdIIlAQEBAwF5EAIBCBUxMiUCBA4Fh30IxyAXjwAHgySBFAEDmCOSGIMtgio
X-IronPort-AV: E=Sophos;i="4.95,709,1384300800"; d="scan'208";a="299370729"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-3.cisco.com with ESMTP; 23 Jan 2014 22:50:36 +0000
Received: from xhc-aln-x12.cisco.com (xhc-aln-x12.cisco.com [173.36.12.86]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id s0NMoZHP030051 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 23 Jan 2014 22:50:35 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.76]) by xhc-aln-x12.cisco.com ([173.36.12.86]) with mapi id 14.03.0123.003; Thu, 23 Jan 2014 16:50:35 -0600
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: "Dale R. Worley" <worley@ariadne.com>
Subject: Re: Problem with new Note Well
Thread-Topic: Problem with new Note Well
Thread-Index: AQHPGIzTSIiTtRgEUkSf0hEoiuKs/ZqTToUA
Date: Thu, 23 Jan 2014 22:50:34 +0000
Message-ID: <97F802E5-6E15-4BDF-A0D1-EF299DCBBAC4@cisco.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <52E15937.8010600@qti.qualcomm.com> <201401232245.s0NMj6uH3447931@shell01.TheWorld.com>
In-Reply-To: <201401232245.s0NMj6uH3447931@shell01.TheWorld.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <C1720E7E6D65294FACE2516DB48D3BCA@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, Pete Resnick <presnick@qti.qualcomm.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 22:50:40 -0000

On Jan 23, 2014, at 3:45 PM, Dale R. Worley <worley@ariadne.com> wrote:

>> From: Pete Resnick <presnick@qti.qualcomm.com>
>>=20
>> You are not asked to click "I agree" to any statement. You are asked
>> to "Acknowledge" that you read it. And the statement says right at
>> the top:
>>=20
>> "This summary is only meant to point you in the right direction, and=20
>> does not contain all the details. Exceptions may apply."
>=20
>> From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
>>=20
>> "If you are aware that any contribution (something written, said, or
>> discussed in any IETF context) is covered by patents or patent
>> applications, you must disclose that fact."
>=20
> Surely we can write a better statement than what Cullen quotes.  To
> begin with, it contains the word "must".  And while the statment is
> amplified with "does not contain all the details", can we not provide
> a proper pointer to the details?
>=20
> Not being fully informed about this subject, it seems to me that it
> would be far better to say:
>=20
>    "By participating in an IETF discussion, you agree that if you are
>    aware that any contribution (something written, said, or discussed
>    in any IETF context) to that discussion is covered by patents or
>    patent applications, you may be required to disclose that fact.
>    The specific requirements are described in BCP 79."
>=20
> Dale

I=92d be fine with Dale=92s proposal.=20


From lars@netapp.com  Fri Jan 24 00:20:12 2014
Return-Path: <lars@netapp.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F03AA1A01DD; Fri, 24 Jan 2014 00:20:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.437
X-Spam-Level: 
X-Spam-Status: No, score=-7.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hCTva3_iPb8E; Fri, 24 Jan 2014 00:20:04 -0800 (PST)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id 1E5321A0199; Fri, 24 Jan 2014 00:20:04 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.95,711,1384329600";  d="asc'?scan'208";a="138801597"
Received: from vmwexceht06-prd.hq.netapp.com ([10.106.77.104]) by mx12-out.netapp.com with ESMTP; 24 Jan 2014 00:17:45 -0800
Received: from SACEXCMBX06-PRD.hq.netapp.com ([169.254.9.60]) by vmwexceht06-prd.hq.netapp.com ([10.106.77.104]) with mapi id 14.03.0123.003; Fri, 24 Jan 2014 00:17:45 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: Cullen Jennings <fluffy@cisco.com>
Subject: Re: Problem with new Note Well
Thread-Topic: Problem with new Note Well
Thread-Index: AQHPDLRewts4Z03OwUmpMDWCPAmms5qTIZaAgAALSwCAAApkgP//yPPdgACHiACAAJ5zgA==
Date: Fri, 24 Jan 2014 08:17:44 +0000
Message-ID: <E871E20C-EC8D-41AA-A556-103246C90EA0@netapp.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <52E15937.8010600@qti.qualcomm.com> <201401232245.s0NMj6uH3447931@shell01.TheWorld.com> <97F802E5-6E15-4BDF-A0D1-EF299DCBBAC4@cisco.com>
In-Reply-To: <97F802E5-6E15-4BDF-A0D1-EF299DCBBAC4@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: multipart/signed; boundary="Apple-Mail=_FB351A87-10AF-45F2-BB6D-11EC879479D4"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, Pete Resnick <presnick@qti.qualcomm.com>, "Dale R. Worley" <worley@ariadne.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 08:20:12 -0000

--Apple-Mail=_FB351A87-10AF-45F2-BB6D-11EC879479D4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Hi,

I will (again) point at the IPR text for the I*R*TF, that we changed =
last year in an attempt to be more descriptive: http://irtf.org/ipr

I believe it captures Cullen's (and my) concern, and is still quite =
short.

Lars


The IRTF follows the IETF Intellectual Property Rights (IPR) disclosure =
rules. This is a summary of these rules as they relate to IRTF research =
group discussions, mailing lists and Internet Drafts:

	=95 If you include your own or your employer=92s IPR in a =
contribution to an IRTF research group, then you must file an IPR =
disclosure with the IETF.

	=95 If you recognize your own or your employer=92s IPR in =
someone else=92s contribution and you are participating in the =
discussions in the research group relating to that contribution, then =
you must file an IPR disclosure with the IETF. Even if you are not =
participating in the discussion, the IRTF still requests that you file =
an IPR disclosure with the IETF.

	=95 Finally, the IRTF requests that you file an IPR disclosure =
with the IETF if you recognize IPR owned by others in any IRTF =
contribution.

The IRTF expects that you file IPR disclosures in a timely manner, i.e., =
in a period measured in days or weeks, not months. The IRTF prefers that =
the most liberal licensing terms possible are available for IRTF Stream =
documents, see RFC 5743. You may file an IPR disclosure =
here:http://www.ietf.org/ipr/file-disclosure

See RFC 3979 (BCP 79) for definitions of =93IPR=94 and =93contribution=94 =
and for the detailed rules (substituting =93IRTF=94 for =93IETF=94).

--Apple-Mail=_FB351A87-10AF-45F2-BB6D-11EC879479D4
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iQCVAwUBUuIhpdZcnpRveo1xAQKHvwP/eryEnXj0oB/sIi9jg8uHnlWmQ26m/fof
aUGheeQBfW3lKPnZ3Xizy3Xc2lXA+q7NGxans7QejaDP9S1z5jW5MnbtLVdoMItA
hnvn3IhLTC9DvqsyA8wWgFFfojvftF5r3buewu0SywBrYy5vf/gh47zBy/iQXo3N
Vvn+2szIyQE=
=9o2c
-----END PGP SIGNATURE-----

--Apple-Mail=_FB351A87-10AF-45F2-BB6D-11EC879479D4--

From tom.taylor.stds@gmail.com  Fri Jan 24 03:43:06 2014
Return-Path: <tom.taylor.stds@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C8171A02BA; Fri, 24 Jan 2014 03:43:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hX5zss1eSBuE; Fri, 24 Jan 2014 03:43:05 -0800 (PST)
Received: from mail-ig0-x22c.google.com (mail-ig0-x22c.google.com [IPv6:2607:f8b0:4001:c05::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 9C9E51A02B8; Fri, 24 Jan 2014 03:43:04 -0800 (PST)
Received: by mail-ig0-f172.google.com with SMTP id k19so2310217igc.5 for <multiple recipients>; Fri, 24 Jan 2014 03:43:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=zsOpZiK7mukcXr3NGnkXrUrPoTHHYxs6TNYhP7Zsf9g=; b=s4zGC6erGq/hNFbxT5NKOssShTI+nZxg3bRXc10fdcxySn21NyexcgEFVEp+7xzPGR 4ZwFTgUCGgayDsE/UVGAgaWp8oet9vhJ67/T5+eiYwA/MiJ7jYuKizU+zZeZWc1fUHkk IoZfsAEmyij4aYPdC2G91CnYHT6xDHHnydIbX5IaIWdkFsBZbvE9YsQBeYBqVj0QoeSI 3lVR8C9pN0ZdvB2xmuyyDXjhPVzSuPWlUIAgMvf0IqbaRgk7R+eZd+s4gOYppgM1C1WQ bWV3oROhkNlnX4BaOu3mQ1erEPDygniiT/b574Sy63iWaXLsCzzZuvyxeBS2U4S0dOxn RDzA==
X-Received: by 10.43.19.66 with SMTP id qj2mr10191883icb.31.1390563783443; Fri, 24 Jan 2014 03:43:03 -0800 (PST)
Received: from [192.168.1.69] ([64.56.225.169]) by mx.google.com with ESMTPSA id f15sm7917128igd.3.2014.01.24.03.43.02 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 24 Jan 2014 03:43:02 -0800 (PST)
Message-ID: <52E251C2.7060009@gmail.com>
Date: Fri, 24 Jan 2014 06:42:58 -0500
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "Bradner, Scott" <sob@harvard.edu>, Pete Resnick <presnick@qualcomm.com>
Subject: Re: Problem with new Note Well
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu>
In-Reply-To: <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 11:43:06 -0000

Couldn't sleep last night as often happens because of the medication I'm 
on. So how about this medication-inspired effort, starting with Scott's 
summation:

"BCP79 provides authoritative rules regarding your obligations to 
disclose IPR when participating in the activities of the IETF, and 
should be referred to when the issue arises. The following summary is 
not totally accurate but provides a brief reminder.

General rule: if you make a contribution to IETF discussion, and you 
know or have reason to believe (without making a search) that you or 
your employer or sponsor owns IPR that has a high probability of being 
infringed by implementations based on that contribution, you or your 
employer must disclose that IPR in timely fashion.

Secondly, if you know or have reason to believe (without making a 
search) that implementations of the content of an IETF discussion in 
which you have not yet participated have a high probability of 
infringing on IPR owned by you or your employer then you must either
  -- not participate in the discussion, or
  -- participate and disclose in accordance with the general rule.

Finally, if you are aware of third party IPR in a contribution to the 
IETF, you are encouraged to send an email message to ietf-ipr@ietf.org 
as soon as reasonable disclosing that information."

On 23/01/2014 12:58 PM, Bradner, Scott wrote:
> the actual rules are
> 	1/ if you know of any of your IPR in a contribution you make, you must disclose
> 	2/ if you know of any of your IPR in any contribution from someone else and you are participating in discussions
> 	    that involve that contribution, then you must disclose
> 	3/ if you know of any of your IPR in any contribution from someone else and you are not participating in discussions
> 	    that involve that contribution, then you are requested to disclose
>
> see - its not that hard to say this briefly
>
> Scott
>
...

From hsantos@isdg.net  Fri Jan 24 05:48:24 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F5B61A0466 for <wgchairs@ietfa.amsl.com>; Fri, 24 Jan 2014 05:48:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.002
X-Spam-Level: 
X-Spam-Status: No, score=-102.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SDO39aLOBugO for <wgchairs@ietfa.amsl.com>; Fri, 24 Jan 2014 05:48:20 -0800 (PST)
Received: from winserver.com (news.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 42F931A03A7 for <wgchairs@ietf.org>; Fri, 24 Jan 2014 05:45:47 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=6403; t=1390571141; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=qYp0RrovwTjeNpdU3Se+dj+LItI=; b=e0/yde1avrUXRPSHUFFB RKTiHTpkcfBy0EN4LVhPakPUm7e1y21VmsiiFi040ba4/bp6PeUUvWDZaMCuE7+T mlwNV1sbu4okPJvm3kf4AoiT8W4pdluEIENNhwhCl3eQtYg4j5OVtfaitu1Ae5jV 5cYB980/vBrvzNVgwoQbcuQ=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for wgchairs@ietf.org; Fri, 24 Jan 2014 08:45:41 -0500
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from beta.winserver.com (hector.wildcatblog.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 4148600879.13414.2788; Fri, 24 Jan 2014 08:45:40 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=6403; t=1390570557; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=ztVMOo+ bsC+7TSDq1ceMEpt+cgdprxDMxvkSJRl2wR4=; b=ain4MSNlnJGSKOZ5HFMZnAb snfHHTRkbpUOwa4XMXzhYu9iUlYGV3TTg6+S1czajxYnyugmx3vewsfoF8STo/7X qQjspaYoTvlozboT1hD763ZhagltkzLtwOA2gcud9jPDLeyWPCDYmeR0a6ljhej6 5eyj+lBzABxSuciPf6vY=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for wgchairs@ietf.org; Fri, 24 Jan 2014 08:35:57 -0500
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 3594903036.9.6860; Fri, 24 Jan 2014 08:35:56 -0500
Message-ID: <52E26E81.2000000@isdg.net>
Date: Fri, 24 Jan 2014 08:45:37 -0500
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Subject: Re: Problem with new Note Well
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com>
In-Reply-To: <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailman-Approved-At: Fri, 24 Jan 2014 08:06:06 -0800
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 13:48:24 -0000

I'm not quite following the concern. First, I am little surprise that 
this would be anything new in a patent case with lawyers asking 
questions, seeking facts related to prior art discovery. Second, I 
don't see how you (speaking in general, but mostly top IETF Key cogs 
and industry market leaders) can escape any awareness. Ignorance is 
difficult to claim, however, it can lead to a claim of negligence, and 
IMO, this is more the case today. I am more surprise that the employer 
is not enforcing their NDA more, especially in regards with IETF 
participation which is really wide now with international, and 
countries involved with laws are not consistent with the US.  But I 
suppose your corporation would be in an unique position here given its 
long history and presence within the IETF and industry. This is 
something you should be talking with your corporate chief council. 
Despite whatever the Note Well says, despite the non-binding "I Agree" 
click or statement present or not, it is pretty difficult today to 
escape awareness.  Of course, there are many fine lines here, but that 
is even the more reason your corporate legal guys should be advising 
you -- first.

BTW, I think the first item on the note well page, can be argued as 
the "agreement":

    * By participating with the IETF, you agree to follow IETF 
processes and policies.

It then gets down to defining what is meant by "participating" and 
defining what is meant by "follow."

Does it include the lurkers?  Does it include readers, reviewers, but 
not actually implementators?  etc, and all other similar related 
questions about this.

Its difficult to escape awareness if you are involved in the IETF.


--
HLS

On 1/23/2014 12:25 PM, Cullen Jennings (fluffy) wrote:
>
> This new note well is a real problem for me and  I can not register without clicking "I agree" to it. It is not consistent with the BCPs. The problem is the line that says
>
> 	ï¿½ If you are aware that any contribution (something written, said, or discussed in any IETF context) is covered by patents or patent applications, you must disclose that fact.
>
> I do not agree to that - I canï¿½t given my NDA with my employer does not allow me to disclose confidential information. Yes, I realize there is some weasel words near the top that say "Exceptions may apply." but that does not help me. When you are testifying in court on patents, credibility is incredibly important. You can not have the lawyers on the other side saying that you clicked yes I agree to the line above but you did not actually do what that lines says. You may think this does to matter but the exact topic of how Cisco employees deal with IPR at the IETF is a topic that I have testified on in an East Texas court so this really does happen and really does happen to me. It may happen to you next and you will be much happier if you say what you mean and mean what you say. This new note well fails that test.
>
> I realize some people would like to change the IETF policy to be that you do have to do what that line says but I do not think that is a change the IESG can make without IETF updating the BCP or at least having IETF consensus on the change. I would respectfully ask the IESG to change this line to something that is still brief but that people can agree with it. Simply adding something like "or not contribute to the discussion on that contribution" would probably solve this problem for me.
>
> Thank you,
>
> Cullen
>
> I will note that above line is not consistent with Cisco employment contracts and if we can not resolve this I will be asking Cisco legal to inform Cisco employees they can not agree with this without violating their employment agreement.
>
>
>
> On Jan 23, 2014, at 9:44 AM, Russ Housley <housley@vigilsec.com> wrote:
>
>> It seems that the shorter one is now being used on the IETF web site:
>> http://www.ietf.org/about/note-well.html
>>
>>
>> On Jan 8, 2014, at 3:57 PM, Mary Barnes wrote:
>>
>>> Personally, I've never seen significant value in this shorter note well and while others have been using this new text for the past few meetings, I've stuck to the old.   Now that this is considered the recommended note well for chairs to use, I guess I'll use it.  But, I personally think accuracy should trump brevity.  I think the "must" in that bullet  ought to at least be a should and that adding an "otherwise, one should not contribute to or participate in any related IETF activities." would add more value.
>>>
>>> Mary.
>>>
>>>
>>> On Wed, Jan 8, 2014 at 1:17 PM, Bradner, Scott <sob@harvard.edu> wrote:
>>> you are correct - we (Barry, the IESG & me) discussed this before the IESG approved this text - they felt that
>>> being brief was more important than being fully accurate (or at least that is the way I expressed it)
>>>
>>> Scott
>>>
>>> Scott O Bradner
>>> Senior Technology Consultant
>>>
>>> Harvard University Information Technology
>>> Innovation & Architecture
>>> (P) +1 (617) 495 3864
>>> 8 Story St, room 5014
>>> Cambridge, MA 02138
>>>
>>>
>>>
>>> On Jan 8, 2014, at 2:13 PM, Cullen Jennings (fluffy) <fluffy@cisco.com> wrote:
>>>
>>>>
>>>>
>>>> On Dec 16, 2013, at 12:56 PM, Barry Leiba <barryleiba@computer.org> wrote:
>>>>
>>>>> The IESG has made final edits to the updated Note Well statement, and
>>>>> it has been officially updated:
>>>>> http://www.ietf.org/about/note-well.html
>>>>>
>>>>> I have just uploaded the final versions of the Note Well meeting
>>>>> slides, attached to the bottom of the WG Chairs wiki:
>>>>> http://wiki.tools.ietf.org/group/wgchairs/wiki/WikiStart
>>>>>
>>>>> Please use this new version now, and please remember that as you
>>>>> prepare slides for the London meeting.
>>>>>
>>>>> Barry
>>>>
>>>>
>>>> The new note well says
>>>>
>>>>        ï¿½ If you are aware that any contribution (something written, said, or discussed in any IETF context) is covered by patents or patent applications, you must disclose that fact.
>>>>
>>>> Is that true?  Or is it missing something along the lines of section y of BCP 79 such as
>>>>
>>>>    or must not contribute to or participate in IETF activities with
>>>>    respect to technologies that he or she reasonably and personally
>>>>    knows to be Covered by IPR which he or she will not disclose.
>>>>
>>>> Thanks, Cullen
>>
>
>
>

-- 
HLS



From fluffy@cisco.com  Fri Jan 24 08:31:43 2014
Return-Path: <fluffy@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27C301A0023; Fri, 24 Jan 2014 08:31:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.036
X-Spam-Level: 
X-Spam-Status: No, score=-110.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VWWvQMyeDZT5; Fri, 24 Jan 2014 08:31:41 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) by ietfa.amsl.com (Postfix) with ESMTP id DBAEF1A0010; Fri, 24 Jan 2014 08:31:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2439; q=dns/txt; s=iport; t=1390581100; x=1391790700; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=rN4LpuVoSbVP6WJxFtEb2G9V3JZwKDLui4qaxJhqmiY=; b=LtmV1riqWUE74H23TziWseRKvmaiLEXAXLC8kCsO8d7oVDa8JloHV/pH btrA7lBN1xUifskdTW1KLOUfyhpratNgJnTG/o37XGjdbDDvEBe+WNmd5 PloLZE2gB+MFruWn5YzwxCF5c5P0k2WN+tA6a+a38aGxO395e1DuLEjtP Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah8FAKGU4lKtJXHB/2dsb2JhbABZAYMMgQ6ISLNtgQwWdIIlAQEBAwF5BQsCAQgOChkBARMhERQRAgQOBYdxAwkIwlkNhVYXjHaBNBEBHTMHIwQBgnyBFASJEI0rgWyMXYVBgy2BcTk
X-IronPort-AV: E=Sophos;i="4.95,713,1384300800"; d="scan'208";a="15299105"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by alln-iport-6.cisco.com with ESMTP; 24 Jan 2014 16:31:39 +0000
Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id s0OGVd8r028626 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 24 Jan 2014 16:31:39 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.76]) by xhc-aln-x08.cisco.com ([173.36.12.82]) with mapi id 14.03.0123.003; Fri, 24 Jan 2014 10:31:39 -0600
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Pete Resnick <presnick@qualcomm.com>
Subject: Re: Problem with new Note Well
Thread-Topic: Problem with new Note Well
Thread-Index: AQHPGSHBHRiLKTI0hE2ZsfFwjVVpSg==
Date: Fri, 24 Jan 2014 16:31:38 +0000
Message-ID: <3F350057-8BF4-4A41-BC6D-3141AE419765@cisco.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E251C2.7060009@gmail.com>
In-Reply-To: <52E251C2.7060009@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <490E46E22E7D7341816AF343C73C01B1@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 16:31:43 -0000

Both Tom and Lars text would work for me. There seem to be so many ways to =
write it such that it is still brief but captures the key elements of the B=
CP. =20

Pete, I really think it is that putting a sentences in it that is clearly f=
alse is just wrong and I can not understand why you are arguing for that?



On Jan 24, 2014, at 4:42 AM, Tom Taylor <tom.taylor.stds@gmail.com> wrote:

> Couldn't sleep last night as often happens because of the medication I'm =
on. So how about this medication-inspired effort, starting with Scott's sum=
mation:
>=20
> "BCP79 provides authoritative rules regarding your obligations to disclos=
e IPR when participating in the activities of the IETF, and should be refer=
red to when the issue arises. The following summary is not totally accurate=
 but provides a brief reminder.
>=20
> General rule: if you make a contribution to IETF discussion, and you know=
 or have reason to believe (without making a search) that you or your emplo=
yer or sponsor owns IPR that has a high probability of being infringed by i=
mplementations based on that contribution, you or your employer must disclo=
se that IPR in timely fashion.
>=20
> Secondly, if you know or have reason to believe (without making a search)=
 that implementations of the content of an IETF discussion in which you hav=
e not yet participated have a high probability of infringing on IPR owned b=
y you or your employer then you must either
> -- not participate in the discussion, or
> -- participate and disclose in accordance with the general rule.
>=20
> Finally, if you are aware of third party IPR in a contribution to the IET=
F, you are encouraged to send an email message to ietf-ipr@ietf.org as soon=
 as reasonable disclosing that information."
>=20
> On 23/01/2014 12:58 PM, Bradner, Scott wrote:
>> the actual rules are
>> 	1/ if you know of any of your IPR in a contribution you make, you must =
disclose
>> 	2/ if you know of any of your IPR in any contribution from someone else=
 and you are participating in discussions
>> 	    that involve that contribution, then you must disclose
>> 	3/ if you know of any of your IPR in any contribution from someone else=
 and you are not participating in discussions
>> 	    that involve that contribution, then you are requested to disclose
>>=20
>> see - its not that hard to say this briefly
>>=20
>> Scott
>>=20
> ...


From presnick@qti.qualcomm.com  Fri Jan 24 12:24:24 2014
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E2A61A018E; Fri, 24 Jan 2014 12:24:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level: 
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f9Erk9040MQH; Fri, 24 Jan 2014 12:24:22 -0800 (PST)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id D6AE21A012D; Fri, 24 Jan 2014 12:24:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1390595062; x=1422131062; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=hFBkb9K6s9FXn4fZtGRtBDcQe2NkD4zqae/IRozthjw=; b=cfAePG9dXSbJATOAA4iGdT/vfLMIDGLQCO/Ev07XxTAf/4fpZoBTXWSf y08hl7J5WKBEuIvj6D0H9EdZo+8DmPJ7qW4qSoltkPYugyMV67xM1AZOi d8nN0/P89Ya2MSpxjl68B+P41nP00Ejx/jiA5IzrBdZLkM/9AMIg42QR5 o=;
X-IronPort-AV: E=McAfee;i="5400,1158,7328"; a="58608756"
Received: from ironmsg02-lv.qualcomm.com ([10.47.202.183]) by sabertooth02.qualcomm.com with ESMTP; 24 Jan 2014 12:24:22 -0800
X-IronPort-AV: E=McAfee;i="5400,1158,7328"; a="26130709"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by ironmsg02-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 24 Jan 2014 12:24:21 -0800
Received: from resnick2.qualcomm.com (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 24 Jan 2014 12:24:20 -0800
Message-ID: <52E2CBF2.7070807@qti.qualcomm.com>
Date: Fri, 24 Jan 2014 14:24:18 -0600
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Subject: Re: Problem with new Note Well
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E251C2.7060009@gmail.com> <3F350057-8BF4-4A41-BC6D-3141AE419765@cisco.com>
In-Reply-To: <3F350057-8BF4-4A41-BC6D-3141AE419765@cisco.com>
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>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 20:24:24 -0000

On 1/24/14 10:31 AM, Cullen Jennings (fluffy) wrote:
> Both Tom and Lars text would work for me. There seem to be so many ways to write it such that it is still brief but captures the key elements of the BCP.
>
> Pete, I really think it is that putting a sentences in it that is clearly false is just wrong and I can not understand why you are arguing for that?
>    

So here's the key for me (and maybe this means we have a separate Note 
Well for the room from the one on the web site):

In the room, I want something short enough that the chairs might 
actually be inclined to read out loud. It should have the three basic 
messages:

- By participating here, you've agreed to our rules.
- You can be recorded.
- You have to disclose your IPR.
Details on the above specified elsewhere. Go read if you're worried 
about it.

I want those statements extended as little as possible to keep it so 
that the chair might be willing to say it.

And (and this is probably the one where we might still disagree) if it's 
going to be inaccurate, and it will *have* to be inaccurate just by 
nature of being a summary, I want it to be inaccurate such that it 
includes *more* things to disclose than you are actually required to, 
not less. I don't want the excuse for not disclosing to be "I didn't 
understand all of the detail in BCP 79, but the Note Well sure didn't 
say that I had to disclose anything like *that*." If there's going to be 
an inaccuracy in the statement, I want it to be that BCP 79 says to 
disclose *less* than the summarized warning we give folks in the room.

Both Tom's and Lars's summaries are fine, but they're not reasonable 
things to read in the room.

We wrestled with this for a while. I'm open to suggestions. But the 
above are really my design criteria, at least for the one we put on a 
slide for the room.

pr

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


From rlb@ipv.sx  Fri Jan 24 12:38:02 2014
Return-Path: <rlb@ipv.sx>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCC2B1A01EC for <wgchairs@ietfa.amsl.com>; Fri, 24 Jan 2014 12:38:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7y5Q5WjXrXA6 for <wgchairs@ietfa.amsl.com>; Fri, 24 Jan 2014 12:38:00 -0800 (PST)
Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by ietfa.amsl.com (Postfix) with ESMTP id 019EE1A01E5 for <wgchairs@ietf.org>; Fri, 24 Jan 2014 12:37:59 -0800 (PST)
Received: by mail-ob0-f182.google.com with SMTP id wm4so4180512obc.27 for <wgchairs@ietf.org>; Fri, 24 Jan 2014 12:37:58 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=NMIx45lNMifRSAjmzAWQYxXMbVUUcIaaLN6P9hxDWqQ=; b=esbMAj3/WU3mBbitO4grMbKreWlaJq5iXS6CE7/gdZf2DkE3EXrNyro14DB3v5wMWW ZdiJOeWj+/7QElnsJA/gvncMnN+QUBdfJqSIERBOD6G893Hh9dUTnUyI16cXXp4OmPTS LyYKcxPiawZreGbCq2vR28xEIqI/BZleVnE88MQvm9202UZcEBxr83nOiqsW7tobJo3N K/Rto0kYtWcApH9J6zzDWQu8rXec5cTIIGhGJvTFLpWzoJFA3lMx9F2MeiUesNMPnibR swZvblcqX0p00DQwf0CZVGSKmi3Uxsm7Bx7OqUBXuuAqBmXgFFZQ11FRnqx5CW8YcJpN QF7A==
X-Gm-Message-State: ALoCoQk7e0lBCtx6L1UEvuLV0Xvj8FXzsNCmWnTYyge7Uu5hgYle9PQDLRJAaGBiFyo09mvZxUby
MIME-Version: 1.0
X-Received: by 10.60.84.199 with SMTP id b7mr3028681oez.55.1390595878574; Fri, 24 Jan 2014 12:37:58 -0800 (PST)
Received: by 10.60.54.65 with HTTP; Fri, 24 Jan 2014 12:37:58 -0800 (PST)
In-Reply-To: <52E2CBF2.7070807@qti.qualcomm.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E251C2.7060009@gmail.com> <3F350057-8BF4-4A41-BC6D-3141AE419765@cisco.com> <52E2CBF2.7070807@qti.qualcomm.com>
Date: Fri, 24 Jan 2014 21:37:58 +0100
Message-ID: <CAL02cgSeyk0SYGwe-hHbOOe4Y-KJqo9Yd-2wpHQvjrO=jnAxZQ@mail.gmail.com>
Subject: Re: Problem with new Note Well
From: Richard Barnes <rlb@ipv.sx>
To: Pete Resnick <presnick@qti.qualcomm.com>
Content-Type: multipart/alternative; boundary=089e0102dc825e714704f0bd55ca
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 20:38:03 -0000

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

On Fri, Jan 24, 2014 at 9:24 PM, Pete Resnick <presnick@qti.qualcomm.com>wrote:

> On 1/24/14 10:31 AM, Cullen Jennings (fluffy) wrote:
>
>> Both Tom and Lars text would work for me. There seem to be so many ways
>> to write it such that it is still brief but captures the key elements of
>> the BCP.
>>
>> Pete, I really think it is that putting a sentences in it that is clearly
>> false is just wrong and I can not understand why you are arguing for that?
>>
>>
>
> So here's the key for me (and maybe this means we have a separate Note
> Well for the room from the one on the web site):
>
> In the room, I want something short enough that the chairs might actually
> be inclined to read out loud. It should have the three basic messages:
>
> - By participating here, you've agreed to our rules.
> - You can be recorded.
> - You have to disclose your IPR.
>

It seems like this last part is what Cullen and others are catching on,
since it misses an essential caveat.  You *don't* have to disclose IPR on
things you where don't participate in the discussion.



> Details on the above specified elsewhere. Go read if you're worried about
> it.
>
> I want those statements extended as little as possible to keep it so that
> the chair might be willing to say it.
>

All Cullen proposed changing was the following:
OLD: "If you are aware that any contribution (something written, said, or
discussed in any IETF context) is covered by patents or patent
applications, you must disclose that fact."
NEW:  "If you are aware that any contribution (something written, said, or
discussed in any IETF context) is covered by patents or patent
applications, you must disclose that fact, or not contribute to the
discussion on that contribution"

Nine more words is really too long?

--Richard



>
> And (and this is probably the one where we might still disagree) if it's
> going to be inaccurate, and it will *have* to be inaccurate just by nature
> of being a summary, I want it to be inaccurate such that it includes *more*
> things to disclose than you are actually required to, not less. I don't
> want the excuse for not disclosing to be "I didn't understand all of the
> detail in BCP 79, but the Note Well sure didn't say that I had to disclose
> anything like *that*." If there's going to be an inaccuracy in the
> statement, I want it to be that BCP 79 says to disclose *less* than the
> summarized warning we give folks in the room.
>
> Both Tom's and Lars's summaries are fine, but they're not reasonable
> things to read in the room.
>
> We wrestled with this for a while. I'm open to suggestions. But the above
> are really my design criteria, at least for the one we put on a slide for
> the room.
>
>
> pr
>
> --
> Pete Resnick<http://www.qualcomm.com/~presnick/>
> Qualcomm Technologies, Inc. - +1 (858)651-4478
>
>

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Fri, Jan 24, 2014 at 9:24 PM, Pete Resnick <span dir=3D"ltr">&lt=
;<a href=3D"mailto:presnick@qti.qualcomm.com" target=3D"_blank">presnick@qt=
i.qualcomm.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex"><div class=3D"im">On 1/24=
/14 10:31 AM, Cullen Jennings (fluffy) wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
Both Tom and Lars text would work for me. There seem to be so many ways to =
write it such that it is still brief but captures the key elements of the B=
CP.<br>
<br>
Pete, I really think it is that putting a sentences in it that is clearly f=
alse is just wrong and I can not understand why you are arguing for that?<b=
r>
=A0 =A0<br>
</blockquote>
<br></div>
So here&#39;s the key for me (and maybe this means we have a separate Note =
Well for the room from the one on the web site):<br>
<br>
In the room, I want something short enough that the chairs might actually b=
e inclined to read out loud. It should have the three basic messages:<br>
<br>
- By participating here, you&#39;ve agreed to our rules.<br>
- You can be recorded.<br>
- You have to disclose your IPR.<br></blockquote><div><br></div><div>It see=
ms like this last part is what Cullen and others are catching on, since it =
misses an essential caveat.=A0 You *don&#39;t* have to disclose IPR on thin=
gs you where don&#39;t participate in the discussion.=A0 <br>
</div><div><br>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0=
px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Details on the above specified elsewhere. Go read if you&#39;re worried abo=
ut it.<br>
<br>
I want those statements extended as little as possible to keep it so that t=
he chair might be willing to say it.<br></blockquote><div><br></div><div>Al=
l Cullen proposed changing was the following:<br>OLD: &quot;If you are awar=
e that any contribution (something written, said, or=20
discussed in any IETF context) is covered by patents or patent=20
applications, you must disclose that fact.&quot;<br>NEW:=A0 &quot;If you ar=
e aware that any contribution (something written, said, or=20
discussed in any IETF context) is covered by patents or patent=20
applications, you must disclose that fact, or not contribute to the discuss=
ion on that contribution&quot;=A0 <br><br>Nine more words is really too lon=
g?=A0 <br><br></div><div>--Richard<br></div><div><br>=A0</div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px soli=
d rgb(204,204,204);padding-left:1ex">

<br>
And (and this is probably the one where we might still disagree) if it&#39;=
s going to be inaccurate, and it will *have* to be inaccurate just by natur=
e of being a summary, I want it to be inaccurate such that it includes *mor=
e* things to disclose than you are actually required to, not less. I don&#3=
9;t want the excuse for not disclosing to be &quot;I didn&#39;t understand =
all of the detail in BCP 79, but the Note Well sure didn&#39;t say that I h=
ad to disclose anything like *that*.&quot; If there&#39;s going to be an in=
accuracy in the statement, I want it to be that BCP 79 says to disclose *le=
ss* than the summarized warning we give folks in the room.<br>

<br>
Both Tom&#39;s and Lars&#39;s summaries are fine, but they&#39;re not reaso=
nable things to read in the room.<br>
<br>
We wrestled with this for a while. I&#39;m open to suggestions. But the abo=
ve are really my design criteria, at least for the one we put on a slide fo=
r the room.<div class=3D""><div class=3D"h5"><br>
<br>
pr<br>
<br>
-- <br>
Pete Resnick&lt;<a href=3D"http://www.qualcomm.com/~presnick/" target=3D"_b=
lank">http://www.qualcomm.<u></u>com/~presnick/</a>&gt;<br>
Qualcomm Technologies, Inc. - <a href=3D"tel:%2B1%20%28858%29651-4478" valu=
e=3D"+18586514478" target=3D"_blank">+1 (858)651-4478</a><br>
<br>
</div></div></blockquote></div><br></div></div>

--089e0102dc825e714704f0bd55ca--

From paul.hoffman@vpnc.org  Fri Jan 24 12:56:48 2014
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F8811A0099; Fri, 24 Jan 2014 12:56:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.347
X-Spam-Level: 
X-Spam-Status: No, score=-1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MUTSi3-xuFhx; Fri, 24 Jan 2014 12:56:47 -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 2B8C71A0090; Fri, 24 Jan 2014 12:56:47 -0800 (PST)
Received: from [10.20.30.90] (50-1-98-67.dsl.dynamic.sonic.net [50.1.98.67]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.7) with ESMTP id s0OKaXY8031132 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 24 Jan 2014 13:36:34 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-1-98-67.dsl.dynamic.sonic.net [50.1.98.67] claimed to be [10.20.30.90]
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Problem with new Note Well
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <52E2CBF2.7070807@qti.qualcomm.com>
Date: Fri, 24 Jan 2014 12:56:42 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <FF96DC31-A2B8-400D-913F-C66A278DA2B6@vpnc.org>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E251C2.7060009@gmail.com> <3F350057-8BF4-4A41-BC6D-3141AE419765@cisco.com> <52E2CBF2.7070807@qti.qualcomm.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
X-Mailer: Apple Mail (2.1827)
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 20:56:48 -0000

On Jan 24, 2014, at 12:24 PM, Pete Resnick <presnick@qti.qualcomm.com> =
wrote:

> So here's the key for me (and maybe this means we have a separate Note =
Well for the room from the one on the web site):
>=20
> In the room, I want something short enough that the chairs might =
actually be inclined to read out loud.

So, you want IPR theater. Lovely.

Everyone in the room has already seen the full Note Well at least twice: =
once upon registering, and once on the agenda. If your actual mission is =
to get people to read what they have already seen, then the in-room =
message should simply be:

You already received the IPR rules at least twice. If you haven't read =
them,
do so right now on on the little schedule or at =
<http://www.ietf.org/ipr/policy.html>.

That statement lets the WG get to the real purpose of the face-to-face =
meeting, and does not badly summarize the actual rules.

--Paul Hoffman=

From mary.ietf.barnes@gmail.com  Fri Jan 24 13:03:57 2014
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB0211A01CC; Fri, 24 Jan 2014 13:03:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o8B-UlpczmVm; Fri, 24 Jan 2014 13:03:55 -0800 (PST)
Received: from mail-ie0-x22e.google.com (mail-ie0-x22e.google.com [IPv6:2607:f8b0:4001:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id DF42C1A011B; Fri, 24 Jan 2014 13:03:54 -0800 (PST)
Received: by mail-ie0-f174.google.com with SMTP id tp5so3345627ieb.5 for <multiple recipients>; Fri, 24 Jan 2014 13:03:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3YkDX4zhn1nYaoiS36WrwwgcRPtcfDDMk1/8IsENrMc=; b=FpZRjOdX97hLa+c7X7PTIMFPW0QweBUuDXNRXD5kg0h+0+65ZupmWnAfL+gfcxI4gg fUuVpPvl+LHB2t7I14gv6nl1r4M1Zart0UrDeFhfGjknB04UlASxy9jqnvBpuWHiKh8N rB2rI332CEjy0LxsXEr1eqM40ygFwhFNxhI5kz1GLhLloR5QGp594dySuCihmG3z/kbw 3c98NFWRdnGbUBzy/zoIdRK+hs08l2Ra6lCGfh513tk+k7eOaocCr27M979l0HQNLSN4 vAz/1g7X9+2eyViqNLfLMiNM16TwGnKkMyurbfpXuhvx8s9ecMQsW7pkXIRV4t86gWVh 7m6w==
MIME-Version: 1.0
X-Received: by 10.43.103.67 with SMTP id dh3mr2852899icc.60.1390597433633; Fri, 24 Jan 2014 13:03:53 -0800 (PST)
Received: by 10.43.58.137 with HTTP; Fri, 24 Jan 2014 13:03:53 -0800 (PST)
In-Reply-To: <52E2CBF2.7070807@qti.qualcomm.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E251C2.7060009@gmail.com> <3F350057-8BF4-4A41-BC6D-3141AE419765@cisco.com> <52E2CBF2.7070807@qti.qualcomm.com>
Date: Fri, 24 Jan 2014 15:03:53 -0600
Message-ID: <CAHBDyN5dm+=najR5LVGDyxrcpAyivx+hEnF0Zzhzzik6wmO_gw@mail.gmail.com>
Subject: Re: Problem with new Note Well
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Content-Type: multipart/alternative; boundary=bcaec517201f0eb23b04f0bdb293
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 21:03:58 -0000

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

On Fri, Jan 24, 2014 at 2:24 PM, Pete Resnick <presnick@qti.qualcomm.com>wrote:

> On 1/24/14 10:31 AM, Cullen Jennings (fluffy) wrote:
>
>> Both Tom and Lars text would work for me. There seem to be so many ways
>> to write it such that it is still brief but captures the key elements of
>> the BCP.
>>
>> Pete, I really think it is that putting a sentences in it that is clearly
>> false is just wrong and I can not understand why you are arguing for that?
>>
>>
>
> So here's the key for me (and maybe this means we have a separate Note
> Well for the room from the one on the web site):
>
> In the room, I want something short enough that the chairs might actually
> be inclined to read out loud. It should have the three basic messages:
>
> - By participating here, you've agreed to our rules.
> - You can be recorded.
> - You have to disclose your IPR.
> Details on the above specified elsewhere. Go read if you're worried about
> it.
>

[MB] As a chair, I would not be reading the statement out loud. As far as
I'm concerned, my responsibility as a chair is to make sure everyone in the
room is aware of the IETF IPR rules - it's not up to me to summarize them
for the group.  And, saying go read the details "if you're worried" isn't
sufficient.  Everyone should have read the documents in detail and make
sure that anyone that has a say on how they disclose and deal with IPR in
IETF (i.e., corporate lawyers) are aware of IETF policy.  [/MB]

>
> I want those statements extended as little as possible to keep it so that
> the chair might be willing to say it.
>
> And (and this is probably the one where we might still disagree) if it's
> going to be inaccurate, and it will *have* to be inaccurate just by nature
> of being a summary, I want it to be inaccurate such that it includes *more*
> things to disclose than you are actually required to, not less. I don't
> want the excuse for not disclosing to be "I didn't understand all of the
> detail in BCP 79, but the Note Well sure didn't say that I had to disclose
> anything like *that*." If there's going to be an inaccuracy in the
> statement, I want it to be that BCP 79 says to disclose *less* than the
> summarized warning we give folks in the room.
>
> Both Tom's and Lars's summaries are fine, but they're not reasonable
> things to read in the room.
>
[MB] I don't at all think that's too much text to read aloud should someone
think they should do that.  We have lots of slides presented in WGs that
have just as much information and (sadly) sometimes those are just read out
versus someone just hitting on the key points. [/MB]

>
> We wrestled with this for a while. I'm open to suggestions. But the above
> are really my design criteria, at least for the one we put on a slide for
> the room.
>
> pr
>
> --
> Pete Resnick<http://www.qualcomm.com/~presnick/>
> Qualcomm Technologies, Inc. - +1 (858)651-4478
>
>

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

<div dir=3D"ltr"><div class=3D"gmail_extra">On Fri, Jan 24, 2014 at 2:24 PM=
, Pete Resnick <span dir=3D"ltr">&lt;<a href=3D"mailto:presnick@qti.qualcom=
m.com" target=3D"_blank">presnick@qti.qualcomm.com</a>&gt;</span> wrote:<br=
><div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On 1/24/14 10:31 AM, Culle=
n Jennings (fluffy) wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Both Tom and Lars text would work for me. There seem to be so many ways to =
write it such that it is still brief but captures the key elements of the B=
CP.<br>
<br>
Pete, I really think it is that putting a sentences in it that is clearly f=
alse is just wrong and I can not understand why you are arguing for that?<b=
r>
=A0 =A0<br>
</blockquote>
<br></div>
So here&#39;s the key for me (and maybe this means we have a separate Note =
Well for the room from the one on the web site):<br>
<br>
In the room, I want something short enough that the chairs might actually b=
e inclined to read out loud. It should have the three basic messages:<br>
<br>
- By participating here, you&#39;ve agreed to our rules.<br>
- You can be recorded.<br>
- You have to disclose your IPR.<br>
Details on the above specified elsewhere. Go read if you&#39;re worried abo=
ut it.<br></blockquote><div><br></div><div>[MB] As a chair, I would not be =
reading the statement out loud. As far as I&#39;m concerned, my responsibil=
ity as a chair is to make sure everyone in the room is aware of the IETF IP=
R rules - it&#39;s not up to me to summarize them for the group. =A0And, sa=
ying go read the details &quot;if you&#39;re worried&quot; isn&#39;t suffic=
ient. =A0Everyone should have read the documents in detail and make sure th=
at anyone that has a say on how they disclose and deal with IPR in IETF (i.=
e., corporate lawyers) are aware of IETF policy. =A0[/MB]</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
I want those statements extended as little as possible to keep it so that t=
he chair might be willing to say it.<br>
<br>
And (and this is probably the one where we might still disagree) if it&#39;=
s going to be inaccurate, and it will *have* to be inaccurate just by natur=
e of being a summary, I want it to be inaccurate such that it includes *mor=
e* things to disclose than you are actually required to, not less. I don&#3=
9;t want the excuse for not disclosing to be &quot;I didn&#39;t understand =
all of the detail in BCP 79, but the Note Well sure didn&#39;t say that I h=
ad to disclose anything like *that*.&quot; If there&#39;s going to be an in=
accuracy in the statement, I want it to be that BCP 79 says to disclose *le=
ss* than the summarized warning we give folks in the room.<br>

<br>
Both Tom&#39;s and Lars&#39;s summaries are fine, but they&#39;re not reaso=
nable things to read in the room.<br></blockquote><div>[MB] I don&#39;t at =
all think that&#39;s too much text to read aloud should someone think they =
should do that. =A0We have lots of slides presented in WGs that have just a=
s much information and (sadly) sometimes those are just read out versus som=
eone just hitting on the key points. [/MB]=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
We wrestled with this for a while. I&#39;m open to suggestions. But the abo=
ve are really my design criteria, at least for the one we put on a slide fo=
r the room.<span class=3D"HOEnZb"><font color=3D"#888888"><br>
<br>
pr<br>
<br>
-- <br>
Pete Resnick&lt;<a href=3D"http://www.qualcomm.com/~presnick/" target=3D"_b=
lank">http://www.qualcomm.<u></u>com/~presnick/</a>&gt;<br>
Qualcomm Technologies, Inc. - <a href=3D"tel:%2B1%20%28858%29651-4478" valu=
e=3D"+18586514478" target=3D"_blank">+1 (858)651-4478</a><br>
<br>
</font></span></blockquote></div><br></div></div>

--bcaec517201f0eb23b04f0bdb293--

From brian.e.carpenter@gmail.com  Fri Jan 24 19:41:34 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E03C1A0211; Fri, 24 Jan 2014 19:41:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TvA64UflrJbc; Fri, 24 Jan 2014 19:41:31 -0800 (PST)
Received: from mail-pa0-x234.google.com (mail-pa0-x234.google.com [IPv6:2607:f8b0:400e:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id BAD7D1A01C9; Fri, 24 Jan 2014 19:41:31 -0800 (PST)
Received: by mail-pa0-f52.google.com with SMTP id bj1so3951948pad.25 for <multiple recipients>; Fri, 24 Jan 2014 19:41:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=dHJGTfgw4tnjafBq4m6H+ABEXaiaYplioxAooq2O+r8=; b=0Q0/BJDyR6eLzYKXhH2HcVxpd4JjZBibz0t54+X6NPceIqTyN60WZnfDwiVpq6veHv QUcPavQDTnJskfAH5BYgFFRCDdLRerfMgfZaWuifdu22i16ckvR3DcbMOZschBpMhncA AIRjGAcn4ApeZj9voOeXAQ/MRlawlQXoY0ukW4eaShRjQP1TD5o5BprBkj6DIQFFSdfz bSuhtilNDapapkrrDt4/eP+0ubkQAfNyKGwawUaU15+k/QxbjN8AqfCnw1zlILMDw+SK +lYq5+4cmBXAUzY00JtHSQVQ7gLPP3TWv4tuXU9clr8OqmeBGHNczSBgwaRqVUgWn9GP 9/0w==
X-Received: by 10.68.230.137 with SMTP id sy9mr17768010pbc.126.1390621290492;  Fri, 24 Jan 2014 19:41:30 -0800 (PST)
Received: from [192.168.178.23] (218.194.69.111.dynamic.snap.net.nz. [111.69.194.218]) by mx.google.com with ESMTPSA id ns7sm8152367pbc.32.2014.01.24.19.41.26 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 24 Jan 2014 19:41:29 -0800 (PST)
Message-ID: <52E3326E.3080007@gmail.com>
Date: Sat, 25 Jan 2014 16:41:34 +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: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Subject: Re: Problem with new Note Well
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com>
In-Reply-To: <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Jan 2014 03:41:34 -0000

It's quite obvious from reading this thread that the IAOC needs
to revert to the previous Note Well text right now, until the
wording issue is resolved.

It is apparent to me though that the BCP *requires* disclosure
as a condition of participation, regardless of employment agreements,
and always has done. That's why there has always been tolerance extended
to allow corporate IPR departments to have time to prepare and make
disclosures at lawyerly speed. Nothing new here except the more brutal
wording.

Regards
   Brian

On 24/01/2014 06:25, Cullen Jennings (fluffy) wrote:
> This new note well is a real problem for me and  I can not register wit=
hout clicking "I agree" to it. It is not consistent with the BCPs. The pr=
oblem is the line that says
>=20
> 	=E2=80=A2 If you are aware that any contribution (something written, s=
aid, or discussed in any IETF context) is covered by patents or patent ap=
plications, you must disclose that fact.
>=20
> I do not agree to that - I can=E2=80=99t given my NDA with my employer =
does not allow me to disclose confidential information. Yes, I realize th=
ere is some weasel words near the top that say "Exceptions may apply." bu=
t that does not help me. When you are testifying in court on patents, cre=
dibility is incredibly important. You can not have the lawyers on the oth=
er side saying that you clicked yes I agree to the line above but you did=
 not actually do what that lines says. You may think this does to matter =
but the exact topic of how Cisco employees deal with IPR at the IETF is a=
 topic that I have testified on in an East Texas court so this really doe=
s happen and really does happen to me. It may happen to you next and you =
will be much happier if you say what you mean and mean what you say. This=
 new note well fails that test.=20
>=20
> I realize some people would like to change the IETF policy to be that y=
ou do have to do what that line says but I do not think that is a change =
the IESG can make without IETF updating the BCP or at least having IETF c=
onsensus on the change. I would respectfully ask the IESG to change this =
line to something that is still brief but that people can agree with it. =
Simply adding something like "or not contribute to the discussion on that=
 contribution" would probably solve this problem for me.=20
>=20
> Thank you,=20
>=20
> Cullen
>=20
> I will note that above line is not consistent with Cisco employment con=
tracts and if we can not resolve this I will be asking Cisco legal to inf=
orm Cisco employees they can not agree with this without violating their =
employment agreement.=20
>=20
>=20
>=20
> On Jan 23, 2014, at 9:44 AM, Russ Housley <housley@vigilsec.com> wrote:=

>=20
>> It seems that the shorter one is now being used on the IETF web site:
>> http://www.ietf.org/about/note-well.html
>>
>>
>> On Jan 8, 2014, at 3:57 PM, Mary Barnes wrote:
>>
>>> Personally, I've never seen significant value in this shorter note we=
ll and while others have been using this new text for the past few meetin=
gs, I've stuck to the old.   Now that this is considered the recommended =
note well for chairs to use, I guess I'll use it.  But, I personally thin=
k accuracy should trump brevity.  I think the "must" in that bullet  ough=
t to at least be a should and that adding an "otherwise, one should not c=
ontribute to or participate in any related IETF activities." would add mo=
re value.  =20
>>>
>>> Mary.
>>>
>>>
>>> On Wed, Jan 8, 2014 at 1:17 PM, Bradner, Scott <sob@harvard.edu> wrot=
e:
>>> you are correct - we (Barry, the IESG & me) discussed this before the=
 IESG approved this text - they felt that
>>> being brief was more important than being fully accurate (or at least=
 that is the way I expressed it)
>>>
>>> Scott
>>>
>>> Scott O Bradner
>>> Senior Technology Consultant
>>>
>>> Harvard University Information Technology
>>> Innovation & Architecture
>>> (P) +1 (617) 495 3864
>>> 8 Story St, room 5014
>>> Cambridge, MA 02138
>>>
>>>
>>>
>>> On Jan 8, 2014, at 2:13 PM, Cullen Jennings (fluffy) <fluffy@cisco.co=
m> wrote:
>>>
>>>>
>>>> On Dec 16, 2013, at 12:56 PM, Barry Leiba <barryleiba@computer.org> =
wrote:
>>>>
>>>>> The IESG has made final edits to the updated Note Well statement, a=
nd
>>>>> it has been officially updated:
>>>>> http://www.ietf.org/about/note-well.html
>>>>>
>>>>> I have just uploaded the final versions of the Note Well meeting
>>>>> slides, attached to the bottom of the WG Chairs wiki:
>>>>> http://wiki.tools.ietf.org/group/wgchairs/wiki/WikiStart
>>>>>
>>>>> Please use this new version now, and please remember that as you
>>>>> prepare slides for the London meeting.
>>>>>
>>>>> Barry
>>>>
>>>> The new note well says
>>>>
>>>>       =E2=80=A2 If you are aware that any contribution (something wr=
itten, said, or discussed in any IETF context) is covered by patents or p=
atent applications, you must disclose that fact.
>>>>
>>>> Is that true?  Or is it missing something along the lines of section=
 y of BCP 79 such as
>>>>
>>>>   or must not contribute to or participate in IETF activities with
>>>>   respect to technologies that he or she reasonably and personally
>>>>   knows to be Covered by IPR which he or she will not disclose.
>>>>
>>>> Thanks, Cullen
>=20
>=20


From fluffy@cisco.com  Sat Jan 25 06:21:48 2014
Return-Path: <fluffy@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21B3A1A02D3; Sat, 25 Jan 2014 06:21:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.036
X-Spam-Level: 
X-Spam-Status: No, score=-110.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qxn-yYoxuyCT; Sat, 25 Jan 2014 06:21:46 -0800 (PST)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) by ietfa.amsl.com (Postfix) with ESMTP id E2BEB1A02C2; Sat, 25 Jan 2014 06:21:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3704; q=dns/txt; s=iport; t=1390659704; x=1391869304; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=IagNhy1J0UeNQKRbGiy9P3kCxco+DqUM0GeNPLaAC4M=; b=gQ+7QPeGxvJBx20apJaGvsQa1d+/r9eDOdMEqx51wIS+Va4JyKr4H5ad 5ZbhdQF7PBuwPIIMzVJVeI09Q77QChra1g8lFlFDMZdBHq+ZyDeZqNr6p w+eRoabObcOkVLSv9UgbWk0MLclOJwaBvJfQYMjI57rdceYgoMC3+9gZ5 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag8FABjH41KtJV2d/2dsb2JhbABXAxaCdjhWvEmBBhZ0giUBAQEDAXkFCwIBCA4KLjIlAgQOBYd9CA3IcReOWiMQBxGDE4EUBJgnkh6DLYIq
X-IronPort-AV: E=Sophos;i="4.95,719,1384300800"; d="scan'208";a="15497084"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-5.cisco.com with ESMTP; 25 Jan 2014 14:21:42 +0000
Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com [173.37.183.89]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id s0PELgkm010550 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 25 Jan 2014 14:21:42 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.76]) by xhc-rcd-x15.cisco.com ([173.37.183.89]) with mapi id 14.03.0123.003; Sat, 25 Jan 2014 08:21:42 -0600
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Problem with new Note Well
Thread-Topic: Problem with new Note Well
Thread-Index: AQHPGUJBoZGQwbDO+0qJCUaQbh9tI5qV45iA
Date: Sat, 25 Jan 2014 14:21:41 +0000
Message-ID: <29860DAF-ABE7-4EAD-B79B-5537D661B89B@cisco.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E251C2.7060009@gmail.com> <3F350057-8BF4-4A41-BC6D-3141AE419765@cisco.com> <52E2CBF2.7070807@qti.qualcomm.com>
In-Reply-To: <52E2CBF2.7070807@qti.qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <800C0B52F6818E47B570431EAAD9677E@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Jan 2014 14:21:48 -0000

Pete, inline =85


On Jan 24, 2014, at 1:24 PM, Pete Resnick <presnick@qti.qualcomm.com> wrote=
:

> On 1/24/14 10:31 AM, Cullen Jennings (fluffy) wrote:
>> Both Tom and Lars text would work for me. There seem to be so many ways =
to write it such that it is still brief but captures the key elements of th=
e BCP.
>>=20
>> Pete, I really think it is that putting a sentences in it that is clearl=
y false is just wrong and I can not understand why you are arguing for that=
?
>>  =20
>=20
> So here's the key for me (and maybe this means we have a separate Note We=
ll for the room from the one on the web site):
>=20
> In the room, I want something short enough that the chairs might actually=
 be inclined to read out loud. It should have the three basic messages:

I certainly don=92t plan to read it out in meetings I chair as I do not see=
 any way that it will actually improve the situation at IETF but none the l=
ess I still basically agree with your design goals (include keeping it rela=
tively short).=20

>=20
> - By participating here, you've agreed to our rules.
> - You can be recorded.
> - You have to disclose your IPR.

It=92s this above point that I don=92t believe is true. I think the point y=
ou need to make is, I think what you need to say is=20

      "You have to disclose your IPR, or not participate in the discussion"

I do want to point out that if you truly wanted this short the total slides=
 would say=20

      "This meeting may be recorded. To be in this meeting you must agree t=
o the rules in BCP 79. "


> Details on the above specified elsewhere. Go read if you're worried about=
 it.
>=20
> I want those statements extended as little as possible to keep it so that=
 the chair might be willing to say it.
>=20
> And (and this is probably the one where we might still disagree) if it's =
going to be inaccurate, and it will *have* to be inaccurate just by nature =
of being a summary, I want it to be inaccurate such that it includes *more*=
 things to disclose than you are actually required to, not less. I don't wa=
nt the excuse for not disclosing to be "I didn't understand all of the deta=
il in BCP 79, but the Note Well sure didn't say that I had to disclose anyt=
hing like *that*." If there's going to be an inaccuracy in the statement, I=
 want it to be that BCP 79 says to disclose *less* than the summarized warn=
ing we give folks in the room.

The core issue here is that you are making the summary be a sentence which =
is not wrong and which people can not and will not comply with. At that poi=
nt you toss the whole thing into questions. People who need to testify in c=
ourt on patents will have their credibility undermined by having agreed to =
this and then not doing it. You need to come up with a summary is not wrong=
 even if it is not be complete.

I would also like to point out we are not talking about just what goes up o=
n the front of the room but also what I must click agree to when I register=
.=20

>=20
> Both Tom's and Lars's summaries are fine, but they're not reasonable thin=
gs to read in the room.
>=20
> We wrestled with this for a while. I'm open to suggestions. But the above=
 are really my design criteria, at least for the one we put on a slide for =
the room.

Good to hear, I am very hopeful that someone will come up with a suggestion=
 that is not wrong, and at the same time does not increase the total length=
 of the Note Well by more than lets say 20%. Would that work for you ?


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


From fluffy@cisco.com  Sat Jan 25 06:51:01 2014
Return-Path: <fluffy@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E5A81A0377; Sat, 25 Jan 2014 06:51:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -115.036
X-Spam-Level: 
X-Spam-Status: No, score=-115.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AA1TnvY54-vk; Sat, 25 Jan 2014 06:50:59 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 8C9A61A026C; Sat, 25 Jan 2014 06:50:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2716; q=dns/txt; s=iport; t=1390661458; x=1391871058; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=TMBI58sb5EgpPFfyO9g0JAdogc3fsHfJzgwogQ6SHbY=; b=YO4WTDyZ/Xg41IzPGfhop1ihSjPehqyzYjcmkUYKUXfpd0F7kGAA1pw4 nGbyQq6+rfJtboZgTbWhg77UjQ4xxaaTDEgMGkUhgKtI7bJ+fqpMyoauU eijHEQAKqNj8SWRKbwpGoHTp/Nb0EA7phVWAHlMk09NQS0SutguZqA+23 s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag0FAOTO41KtJXG+/2dsb2JhbABagwyBDrxJgQYWdIIlAQEBBHkQAgEIGC4yJQIEDgWIBckDF45aMweDJIEUAQOYJ5Iegy2CKg
X-IronPort-AV: E=Sophos;i="4.95,719,1384300800"; d="scan'208";a="299753196"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-4.cisco.com with ESMTP; 25 Jan 2014 14:50:58 +0000
Received: from xhc-rcd-x10.cisco.com (xhc-rcd-x10.cisco.com [173.37.183.84]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id s0PEov5d027388 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 25 Jan 2014 14:50:57 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.76]) by xhc-rcd-x10.cisco.com ([173.37.183.84]) with mapi id 14.03.0123.003; Sat, 25 Jan 2014 08:50:57 -0600
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Problem with new Note Well
Thread-Topic: Problem with new Note Well
Thread-Index: AQHPGUJBoZGQwbDO+0qJCUaQbh9tI5qVhdvZgABl6QA=
Date: Sat, 25 Jan 2014 14:50:56 +0000
Message-ID: <D8D0971F-57F9-405A-B25D-61F9C88B84EE@cisco.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E251C2.7060009@gmail.com> <3F350057-8BF4-4A41-BC6D-3141AE419765@cisco.com> <52E2CBF2.7070807@qti.qualcomm.com> <29860DAF-ABE7-4EAD-B79B-5537D661B89B@cisco.com> <9393741FAF54D30498339914@JcK-HP8200.jck.com>
In-Reply-To: <9393741FAF54D30498339914@JcK-HP8200.jck.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <936585A394D32647BEDD31B18F77C491@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, Pete Resnick <presnick@qti.qualcomm.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Jan 2014 14:51:01 -0000

John,

Point taken and I understand how hard it is to get the right words. I=92m n=
ot trying to propose exact words as I=92m hoping that someone else can come=
 up with something that meets Pete=92s goals of relatively short and my goa=
ls of not looking like an idiot in some court room.=20

Cullen


On Jan 25, 2014, at 7:46 AM, John C Klensin <john-ietf@jck.com> wrote:

>=20
>=20
> --On Saturday, January 25, 2014 14:21 +0000 "Cullen Jennings
> (fluffy)" <fluffy@cisco.com> wrote:
>=20
>> ...
>>> - By participating here, you've agreed to our rules.
>>> - You can be recorded.
>>> - You have to disclose your IPR.
>>=20
>> It's this above point that I don't believe is true. I
>> think the point you need to make is, I think what you need to
>> say is=20
>>=20
>>      "You have to disclose your IPR, or not participate in
>> the discussion"
>=20
> And, of course, this drags us into the precise definition of
> "participate", an axle around which we've gotten wrapped several
> times.  In particular,=20
>=20
>> I do want to point out that if you truly wanted this short the
>> total slides would say=20
>>=20
>>      "This meeting may be recorded. To be in this meeting you
>> must agree to the rules in BCP 79. "
>=20
> but "to be in this meeting" means that sitting in the room
> during a WG session constitutes "participation".  I like that
> definition, but we've been around it several times and my
> recollection is that I was in the minority.  If "participate"
> for IPR purposes has any resemblance to "making a Contribution",
> e.g., opening your mouth, then the above statement is as false
> as some of those to which you object.
>=20
>> ...
>> The core issue here is that you are making the summary be a
>> sentence which is not wrong and which people can not and will
>> not comply with. At that point you toss the whole thing into
>> questions. People who need to testify in court on patents will
>> have their credibility undermined by having agreed to this and
>> then not doing it. You need to come up with a summary is not
>> wrong even if it is not be complete.
>=20
> Yep.  See earlier comments by Brian and myself, but this
> credibility effect is equally important.
>=20
> Perhaps the appropriate short statement might be more like:
>=20
> 	"If you are in this room two minutes from now or
> 	thereafter, you are deemed to have read, understood, and
> 	agreed to BCP 79.  If you have not read and understood
> 	it, please leave until after you do."
> =09
> I hope that is a joke, but it is short, says nothing false, and
> doesn't get entangled with terms like "participate".
>=20
>> ...
>=20
>   john
>=20
>=20


From suzworldwide@gmail.com  Sat Jan 25 11:15:35 2014
Return-Path: <suzworldwide@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD5731A0028; Sat, 25 Jan 2014 11:15:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, J_CHICKENPOX_42=0.6, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XRLU_7Z9UB2Y; Sat, 25 Jan 2014 11:15:34 -0800 (PST)
Received: from mail-qa0-x236.google.com (mail-qa0-x236.google.com [IPv6:2607:f8b0:400d:c00::236]) by ietfa.amsl.com (Postfix) with ESMTP id C5B131A003C; Sat, 25 Jan 2014 11:15:33 -0800 (PST)
Received: by mail-qa0-f54.google.com with SMTP id i13so5496048qae.13 for <multiple recipients>; Sat, 25 Jan 2014 11:15:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=bDUIwPr4w/WEZfUoBGTcpE+LT275dKeAeL9bUb7yK34=; b=gqu0AncOwpwQNJU2zTPRgzAZefS/hlp6my/CyXccoLywvJOwjLktMdkEuHy5VXGe7y u2Noqi/YBRsqvPguBTGvmrVLMzAPaV6/9+r08GWxsiezJ06J0ahPv6ncn8eKfihksGNz r+qaU+XTPa0kjlzV3pvTQejuqLBNC5ItVmKmxY3WsLxabNdaDidbMOTc4ebZ5BazKE15 LsFdBSziDI838ik0kDwjpiioeztZpUA59hrQ7ouFvSyXo6Ym0p0vl6IoT5zS8jok0RIb YKgP+d6yGG3wFXp9fWv+1E7i0uQYfUSY9f6xZvV5EOSYHL/FZ405Kb17Yc6AEorwoczC ChXQ==
X-Received: by 10.224.16.72 with SMTP id n8mr30975013qaa.76.1390677332156; Sat, 25 Jan 2014 11:15:32 -0800 (PST)
Received: from [10.0.0.5] (c-24-63-89-87.hsd1.ma.comcast.net. [24.63.89.87]) by mx.google.com with ESMTPSA id i38sm4036446qge.1.2014.01.25.11.15.31 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 25 Jan 2014 11:15:31 -0800 (PST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Problem with new Note Well
From: Suzanne Woolf <suzworldwide@gmail.com>
In-Reply-To: <D8D0971F-57F9-405A-B25D-61F9C88B84EE@cisco.com>
Date: Sat, 25 Jan 2014 14:15:33 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <B627AAAB-5F7B-4230-AB9E-99838C0BC63E@gmail.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E251C2.7060009@gmail.com> <3F350057-8BF4-4A41-BC6D-3141AE419765@cisco.com> <52E2CBF2.7070807@qti.qualcomm.com> <29860DAF-ABE7-4EAD-B79B-5537D661B89B@cisco.com> <9393741FAF54D30498339914@JcK-HP8200.jck.com> <D8D0971F-57F9-405A-B25D-61F9C88B84EE@cisco.com>
To: IETF WG Chairs <wgchairs@ietf.org>
X-Mailer: Apple Mail (2.1510)
Cc: John C Klensin <john-ietf@jck.com>, Pete Resnick <presnick@qti.qualcomm.com>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Jan 2014 19:15:35 -0000

Colleagues,

As a long-time IETF'er and new WG chair, I want a) something I can say =
in the room as part of the opening to a meeting, if only to support =
Cullen's non-idiocy requirement; b) something that will make sense to =
those with the ability/inclination to pay attention to boilerplate; and =
c) something not wrong, for which Pete's requirements sound reasonable =
to me.

It also sounds like Richard's suggested change meets the requirements, =
including the one that encourages us to err on the side of disclosure or =
non-participation.

If we can't agree on that, I'd prefer to revert to the old wording while =
we hash this out, but I really hope more hashing isn't needed.


best,
Suzanne

On Jan 25, 2014, at 9:50 AM, Cullen Jennings (fluffy) <fluffy@cisco.com> =
wrote:

>=20
> John,
>=20
> Point taken and I understand how hard it is to get the right words. =
I=92m not trying to propose exact words as I=92m hoping that someone =
else can come up with something that meets Pete=92s goals of relatively =
short and my goals of not looking like an idiot in some court room.=20
>=20
> Cullen
>=20
>=20
> On Jan 25, 2014, at 7:46 AM, John C Klensin <john-ietf@jck.com> wrote:
>=20
>>=20
>>=20
>> --On Saturday, January 25, 2014 14:21 +0000 "Cullen Jennings
>> (fluffy)" <fluffy@cisco.com> wrote:
>>=20
>>> ...
>>>> - By participating here, you've agreed to our rules.
>>>> - You can be recorded.
>>>> - You have to disclose your IPR.
>>>=20
>>> It's this above point that I don't believe is true. I
>>> think the point you need to make is, I think what you need to
>>> say is=20
>>>=20
>>>     "You have to disclose your IPR, or not participate in
>>> the discussion"
>>=20
>> And, of course, this drags us into the precise definition of
>> "participate", an axle around which we've gotten wrapped several
>> times.  In particular,=20
>>=20
>>> I do want to point out that if you truly wanted this short the
>>> total slides would say=20
>>>=20
>>>     "This meeting may be recorded. To be in this meeting you
>>> must agree to the rules in BCP 79. "
>>=20
>> but "to be in this meeting" means that sitting in the room
>> during a WG session constitutes "participation".  I like that
>> definition, but we've been around it several times and my
>> recollection is that I was in the minority.  If "participate"
>> for IPR purposes has any resemblance to "making a Contribution",
>> e.g., opening your mouth, then the above statement is as false
>> as some of those to which you object.
>>=20
>>> ...
>>> The core issue here is that you are making the summary be a
>>> sentence which is not wrong and which people can not and will
>>> not comply with. At that point you toss the whole thing into
>>> questions. People who need to testify in court on patents will
>>> have their credibility undermined by having agreed to this and
>>> then not doing it. You need to come up with a summary is not
>>> wrong even if it is not be complete.
>>=20
>> Yep.  See earlier comments by Brian and myself, but this
>> credibility effect is equally important.
>>=20
>> Perhaps the appropriate short statement might be more like:
>>=20
>> 	"If you are in this room two minutes from now or
>> 	thereafter, you are deemed to have read, understood, and
>> 	agreed to BCP 79.  If you have not read and understood
>> 	it, please leave until after you do."
>> =09
>> I hope that is a joke, but it is short, says nothing false, and
>> doesn't get entangled with terms like "participate".
>>=20
>>> ...
>>=20
>>  john
>>=20
>>=20
>=20


From bill@wjcerveny.com  Sun Jan 26 08:38:55 2014
Return-Path: <bill@wjcerveny.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F31B1A0159 for <wgchairs@ietfa.amsl.com>; Sun, 26 Jan 2014 08:38:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, GB_I_INVITATION=-2, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S_ZxypoS389w for <wgchairs@ietfa.amsl.com>; Sun, 26 Jan 2014 08:38:51 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id CC5331A0157 for <wgchairs@ietf.org>; Sun, 26 Jan 2014 08:38:50 -0800 (PST)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id B3549209CD for <wgchairs@ietf.org>; Sun, 26 Jan 2014 11:38:46 -0500 (EST)
Received: from frontend1 ([10.202.2.160]) by compute6.internal (MEProxy); Sun, 26 Jan 2014 11:38:46 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id :references:to; s=smtpout; bh=V+VcIN/dwH9HlDPECgnPHJavG3A=; b=UQ Ob31jSrAz+Ov4MyeT7mWDsdCykXLWXZarvI3lXjT4OW1CvRAEYfwCVnLRbQ18YKJ 4bmJLZUgtED5nfCSiEFUgP7sks6Hs3c5ELgKT04oOMyPekiU+xDKw0z7caE7pYsJ 0isD9GDdcsshGyOM1WX0aVALs3UcSMI+vbvv+va70=
X-Sasl-enc: ekaufBFuXnXVrFyWpdhrZ02CLr8XKDmjaO+5BXrW/cb9 1390754325
Received: from [192.168.1.110] (unknown [24.231.177.41]) by mail.messagingengine.com (Postfix) with ESMTPA id 9DC59C00E8D; Sun, 26 Jan 2014 11:38:44 -0500 (EST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Document language editing session in London
From: Bill Cerveny <bill@wjcerveny.com>
In-Reply-To: <909B8981-E21E-43D7-BEE2-AFE6D64FEA92@cisco.com>
Date: Sun, 26 Jan 2014 11:38:48 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <E3E4A954-020D-4EA8-BCA7-8E652A1529EB@wjcerveny.com>
References: <D6557C43-1445-4660-804D-BD17ED9DD486@nominum.com> <B0D29E0424F2DE47A0B36779EC66677925867D07@nkgeml501-mbs.china.huawei.com> <9ADCA470-8200-4C9E-A728-FD69D155A569@wjcerveny.com> <909B8981-E21E-43D7-BEE2-AFE6D64FEA92@cisco.com>
To: Fred Baker <fred@cisco.com>
X-Mailer: Apple Mail (2.1827)
Cc: "wgchairs@ietf.org Chairs" <wgchairs@ietf.org>, "Heather Flanagan \(RFC Series Editor\)" <rse@rfc-editor.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Jan 2014 16:38:55 -0000

As Fred suggested, I pinged my daughter (a recent English grad who has =
reviewed some IETF Internet-drafts) on this topic ... below is her =
response ...

<begin response>
1) There doesn=92t appear to be a clear, concise web page new volunteer =
reviewers can use as a starting point.
	=95 Agreed. While the 'Info for Newcomers' tab is pretty =
straightforward, and I found a lot of great resources on there, it might =
be more helpful as it's own page with it's own tabs. Perhaps something a =
bit more all-inclusive than having to hop around the website to connect =
dots, such as with finding WG groups, or stumbling upon the RFC Style =
Guide (which, by the way, I found tremendously helpful).=20

2) How does one determine which documents are fair game for document =
review?  In theory, any document submitted to the IETF should be open =
for grammatical review the moment it is submitted, but given limited =
resources, from a WG perspective, we encourage reviewing WG documents =
first.
	=95 It's hard for me to comment on this, because the WG I =
subscribed to never got back to me. There was definitely confusion on my =
end in regards to what I should focus on, and as a new comer I wasn't =
sure if all documents were within my right to edit... if that makes any =
sense.

3) How should a reviewer submit proposed changes? There isn=92t a =
consistent IETF recommendation for how to submit review comments/changes =
(such as format and/or tools) and it seems a consistent recommendation =
would be useful.
	=95 This was, by far, the most difficult part of starting up as =
a new comer. I tried editor after editor, which consequently weren't =
compatible with my laptop, and finally settled on XML Editor. My end =
result has been opening the drafts through my XML Editor and =
transcribing mistakes and corrections into Google Word Docs, =
corresponding line numbers. It was hard for me to gage what my =
corrections should look like without samples.

4) There isn=92t any mechanism for encouraging (or even rewarding) =
reviewers who may not be intimately interested in the technical aspects =
of the documents. I sent my daughter an IETF88 T-shirt, but other than a =
thanks from the authors and/or the WG chairs, there isn=92t much that is =
done to encourage or reward the reviewers.
	=95 This is an interesting point. I see it from two very =
different angles. The first being that I don't expect to be paid for my =
contributions. I love editing, it's a passion of mine, and I like =
helping because I get to fuse my interest in the internet and IT with my =
enjoyment of writing. Receiving 'Thank-Yous' from people who appreciated =
my commentary was above and beyond what I expected, and I treasured it =
because I felt like my input was valued and helpful. As an editor, that =
is all you can hope for.=20
          On the other hand, there is definitely merit in paying someone =
to edit submissions. It would certainly heighten the incentive to review =
documents in a more timely manner, lengthen the input and detail, and =
enhance the quality.=20

Also, grammatically, you used "in" twice in the third paragraph =
(directly above your bullet points).
<end response>

Regards,

Bill Cerveny

On Jan 21, 2014, at 8:45 PM, Fred Baker (fred) <fred@cisco.com> wrote:

>=20
> On Jan 19, 2014, at 3:38 PM, Bill Cerveny <bill@wjcerveny.com> wrote:
>=20
>> [My first rant as a WG chair. I first wrote the rant, then took out =
maybe 2/3rds of what I wrote :-) ]
>>=20
>> Having documents cleaned up grammatically as early as possible is =
very important and will result in better technical discussions, better =
(final) documents and a faster document turnaround from submission to =
publication.
>>=20
>> Last year my daughter, a recent college graduate in English, told me =
she aspired to be a technical writer, at which time I told her, =93Gee, =
how=92d you like to get experience reviewing technical documents?=94 I =
recruited her to review WG documents primarily from a grammatical, =
non-technical perspective. She was successful at providing constructive =
grammatical feedback to WG draft authors.
>>=20
>> Having worked with my daughter in in helping her get up to speed in =
reviewing IETF documents, it seems there are challenges a volunteer =
reviewer faces:
>> 1) There doesn=92t appear to be a clear, concise web page new =
volunteer reviewers can use as a starting point.
>=20
> This is probably a question for your daughter. What would they want on =
the web page? For example, the RFC Editor has a style guide; I presume =
thats of interest. I could imagine a "what would you hope to find in an =
RFC" discussion, but you know as well as I that the topic is all over =
the map.=20
>=20
>> 2) How does one determine which documents are fair game for document =
review?  In theory, any document submitted to the IETF should be open =
for grammatical review the moment it is submitted, but given limited =
resources, from a WG perspective, we encourage reviewing WG documents =
first.
>=20
> Yes. draft-ietf-*. There is room for individual submissions as well, =
but they come and go.
>=20
>> 3) How should a reviewer submit proposed changes? There isn=92t a =
consistent IETF recommendation for how to submit review comments/changes =
(such as format and/or tools) and it seems a consistent recommendation =
would be useful.
>=20
> Well, I don't have an RFC to point you to. I can comment on AUTH48 =
guidelines.=20
>=20
> *** OLD ***
> A really strange bit of text this is
> *** NEW ***
> This is a really strange bit of text
> ***
>=20
> I might add that, since this is presumably a friendly amendment to =
some well-meaning person's document, that there be a note to say *why* =
the new text is suggested.
>=20
>> 4) There isn=92t any mechanism for encouraging (or even rewarding) =
reviewers who may not be intimately interested in the technical aspects =
of the documents. I sent my daughter an IETF88 T-shirt, but other than a =
thanks from the authors and/or the WG chairs, there isn=92t much that is =
done to encourage or reward the reviewers.
>=20
> For you and me, it's part of what we do.
>=20
> "That depends". If they're willing to do it and good at it, I could =
imagine them getting paid. There's a service in London, a bit of spam =
told me once, that will take a document formatted in Microsoft Word, =
turn it into English, and send it back. Since this is done with "Track =
Changes", the author has the option of wondering whether the suggested =
edits are in fact in keeping with the document. They do it for a set =
price scaled by the document size. I haven't actually used the service, =
but I have thought about it.
>=20
> If your daughter is coming to the IETF meeting, I'd buy her a beverage =
of her choice...
>=20
>> At the risk of sounding non-IETFish here (we=92re mostly all =
=93volunteers=94), in a perfect world, it would make sense for authors =
to pay a document reviewer to review a document before it is even =
submitted to the IETF.
>=20
> If the authors are paying, so be it. The ESL co-authors I have worked =
with seem to have the idea that an english-speaking co-author solves =
that problem.
>=20
> See comment above about individual submissions. I have seen a lot of =
documents that are well described as having a lot of blanks that the =
author plans to fill in, or which are going to need a lot of work before =
they even resemble an output. It would be nice to have perfect input, =
but ...=20
>=20
> The place I'd suggest that is the transition from an individual =
submission to a working group document, or just before working group =
last call.
>=20
>> The time involved with reviewing documents for grammatical =
correctness can be non-trivial. Certainly, there is an implied financial =
cost for the time that a volunteer reviewer spends to review a document. =
If the author is serious about submitting a concise technical document =
and having a concise technical document published, it would behoove the =
author to ensure that the document is grammatically correct before it is =
submitted to engineers for technical scrutiny. In this perfect world, =
there might be some sort of central list of people willing to review =
documents, although at a larger organization, it should be possible for =
the author to ask someone at the organization to review the document.
>=20
> No complaint about the perfect world, but - to be very blunt and =
honest, I work in a global company, and the IETF is a global bunch of =
engineers. "Accents" and their written counterparts are part of life. =
I'm far more interested in the content being technically astute than =
written in perfect English.=20
>=20
>> Bill Cerveny
>>=20
>> On Jan 17, 2014, at 9:58 PM, Zongning <zongning@huawei.com> wrote:
>>=20
>>> Dear Ted, and all,
>>>=20
>>> As a non-native English speaker, I agree that this is a good =
practice to improve the quality of IETF I-Ds.
>>>=20
>>> I also share the opinion of Thomas that more volunteers should be =
called to help the whole community. Probably the similar practice could =
be conducted in a more "distributed" way, e.g., in WG level, led by WG =
co-chairs.
>>>=20
>>> Anyway, I will plan to submit I-D to this session in London, learn =
something important, then talk to my group, especially as a non-native =
English WG co-chair. :-)
>>>=20
>>> Thanks.
>>>=20
>>> -Ning
>>>=20
>>>> -----Original Message-----
>>>> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of Ted =
Lemon
>>>> Sent: Friday, January 17, 2014 11:04 AM
>>>> To: wgchairs@ietf.org Chairs
>>>> Cc: Heather Flanagan (RFC Series Editor)
>>>> Subject: Document language editing session in London
>>>>=20
>>>> Dear WG Chairs:
>>>>=20
>>>> The IESG has decided to repeat the experiment that we tried in =
Berlin at the
>>>> upcoming London IETF meeting.   We would like to invite ten =
document
>>>> authors to a language editing session in London on the Saturday =
prior to the
>>>> IETF meeting.   The goal of this editing session will be for two =
area directors,
>>>> me and Joel Jaeggli, to each sit with a group of five document =
editors and work
>>>> on each editors' document for 30 minutes in a group setting.   =
Benoit Claise
>>>> has also offered to help if there are any French-speaking authors =
who would like
>>>> to participate.
>>>>=20
>>>> The plan for this work is to do two things: first, to review the =
documents, and
>>>> secondly, for the participants to have the opportunity to work with =
Joel or with
>>>> me to improve the quality of their documents.   The goal is =
specifically for
>>>> non-native english speakers who have documents that the working =
group
>>>> considers important, but which are felt to need help with english =
language
>>>> editing.   It is important that the authors _want_ to get help-that =
they
>>>> recognize that they could use help and that they are comfortable =
getting that
>>>> help in a small group setting.
>>>>=20
>>>> What the meeting will look like is that there will be one or two =
tables in a
>>>> meeting room; I will be at one table with five authors and a =
representative
>>>> from the RFC Editor.   Joel will be at a separate table, with the =
same
>>>> arrangement.   If there aren't enough authors, we may do a single =
table, as
>>>> we did in Berlin.
>>>>=20
>>>> Each of us will have briefly reviewed the five documents prior to =
the meeting,
>>>> and we expect that the authors will be familiar with each others' =
documents as
>>>> well.   For thirty minutes per document, we will sit with the =
author and go
>>>> over the document, offering comments and suggestions and getting =
feedback
>>>> from the author.   The other authors will follow this. Then we will =
move on to
>>>> the next author.   Joel will be doing the same thing at the other =
table.   The
>>>> RFC Editor will be observing and offering advice on request, or if =
they can't
>>>> resist, but the main goal is to take advantage of the technical =
editorial
>>>> expertise of the two ADs for this experiment.   At the end of the =
editing
>>>> session, we will have a half hour session where we talk about what =
went well, if
>>>> anything, and what went wrong, if anything, and how we might do it =
better
>>>> next time.
>>>>=20
>>>> Neither Joel nor I are experts on teaching english to non-native =
speakers, so we
>>>> do not claim any specific knowledge other than that we both have a =
keen
>>>> interest in improving the quality of IETF documents, a fair amount =
of experience
>>>> in at least trying to do so, and a desire to help our colleagues to =
accomplish
>>>> their goals.
>>>>=20
>>>> Our desired outcome from this meeting is twofold: first, to help =
the specific
>>>> authors who attend; secondly, to learn how to help authors in =
general: what
>>>> frustrations they have in writing documents for IETF, what =
stumbling blocks
>>>> they trip over, and how we can help them.
>>>>=20
>>>> What we are asking working group chairs to do is think about =
whether there
>>>> are documents in their working group that could use this sort of =
help.   If you
>>>> believe there are, please contact the authors of those documents =
and ask them
>>>> in a non-pushy way whether they would like to participate in this =
experiment.
>>>> Please let us know if any of your authors are interested in this.   =
If you have
>>>> more than one document that you'd like worked on, please tell us =
which one is
>>>> most important to you.   We will have to do a triage process unless =
the
>>>> response to this call for participants is tiny, so it's likely that =
we will only take
>>>> the document you think is more important.   If we get a really good =
response,
>>>> we won't be able to take documents from every working group that =
responds;
>>>> please don't take this as a criticism if your document isn't =
chosen.
>>>>=20
>>>> If you think this is a good idea and want to take advantage of it, =
please contact
>>>> your authors as soon as possible, so that they can make travel =
plans that allow
>>>> them to get to the venue on Saturday rather than on Sunday.   =
Please bear in
>>>> mind that the document selection process will take time, and set =
your authors'
>>>> expectations appropriately.
>>>>=20
>>>> We will arrange for authors who wish to attend and who are selected =
to receive
>>>> invitations, so that they can justify the early arrival to their =
management if
>>>> necessary.
>>>>=20
>>>> Thanks!
>>>=20
>>=20
>=20
> ------------------------------------------------------
> 8 issues in virtual infrastructure
> http://dcrocker.net/#fallacies


From ned.freed@mrochek.com  Sun Jan 26 15:13:53 2014
Return-Path: <ned.freed@mrochek.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0E411A015B; Sun, 26 Jan 2014 15:13:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level: 
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FCB9MstZvySy; Sun, 26 Jan 2014 15:13:51 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 55AC51A0092; Sun, 26 Jan 2014 15:13:51 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P3M48I2WOW003GG2@mauve.mrochek.com>; Sun, 26 Jan 2014 15:08:43 -0800 (PST)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P2SI6PLQJK0000AS@mauve.mrochek.com>; Sun, 26 Jan 2014 15:08:35 -0800 (PST)
Message-id: <01P3M48DZNS80000AS@mauve.mrochek.com>
Date: Sun, 26 Jan 2014 14:45:47 -0800 (PST)
From: Ned Freed <ned.freed@mrochek.com>
Subject: Re: Problem with new Note Well
In-reply-to: "Your message dated Sat, 25 Jan 2014 08:19:26 -0500" <82D163D29DC1D4A7B4797E8F@JcK-HP8200.jck.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <52E3326E.3080007@gmail.com> <82D163D29DC1D4A7B4797E8F@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Jan 2014 23:13:54 -0000

> --On Saturday, January 25, 2014 16:41 +1300 Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:

> > It's quite obvious from reading this thread that the IAOC needs
> > to revert to the previous Note Well text right now, until the
> > wording issue is resolved.
> >
> > It is apparent to me though that the BCP *requires* disclosure
> > as a condition of participation, regardless of employment
> > agreements, and always has done. That's why there has always
> > been tolerance extended to allow corporate IPR departments to
> > have time to prepare and make disclosures at lawyerly speed.
> > Nothing new here except the more brutal wording.

Nonsense. The BCP is careful to make it clear that you're obliged to
dislose your IPR when you're contributing.

The Note Well grossly misprepresents the BCP by talking about any contribution
and any IPR without qualification. This is incorrect in two ways: It conflates
contributions in general with someone acting in the role of a contributor, and
it fails to distingish between "your" IPR and third party IPR. 

The wording is not brutal, or as others have claimed, overly broad. It's sloppy
and wrong.

And I'm far more worried about 3rd party IPR here. BCP 79 section 6.1.3 makes
disclosure of that a MAY. (The exact word used is "encouraged".) This languages
makes it a MUST. Would we tolerate a MUST where a MAY is needed in any other
context, even with an "exceptions may apply" disclaimer attached? I think not.

> Agreed.  Noting that the likely effect of "regardless of
> employment agreements" if there really is a conflict in a
> particular company-participant relations is "don't participate
> in that" under the BCP and "don't attend" if the wording is more
> brutal, we should have a lot of incentive to clean the language
> up... and go back to the tested language until a cleaned-up
> version is ready.

Mandating disclosure of 3rd party IPR drags in a whole lot more than employment
contracts.

				Ned

From brian.e.carpenter@gmail.com  Sun Jan 26 20:53:02 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B87631A01A2; Sun, 26 Jan 2014 20:53:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PGgCnZXUx450; Sun, 26 Jan 2014 20:53:01 -0800 (PST)
Received: from mail-pd0-x22f.google.com (mail-pd0-x22f.google.com [IPv6:2607:f8b0:400e:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id F22D21A0185; Sun, 26 Jan 2014 20:53:00 -0800 (PST)
Received: by mail-pd0-f175.google.com with SMTP id w10so5225519pde.6 for <multiple recipients>; Sun, 26 Jan 2014 20:52:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=aLWwR9IVxGi4lfaRwL7E8JDVajiOIvjC/utSUvyvB54=; b=osssolj4t+hKyTHXV2DJOxhBR6pmA0LQhMKGIBDC7hmtKAPOKeRLmGdChsj7fIsI2p AU/tBsT55eESOXPDSOGfs2yimIa8r4pAqIuGzc3ZqOF2oZKF+a/7MqHrX5kUqtRw66vX 69TNH8Ft3W3E9jsxk3Q6+HOKheRWSontVWClMDoC3dUD9oqI6lFVuzz50ppJN0AmEDYp iulm3fOoG/kKaz3p1px3vBvI9FVYUFZDJcEVoPgs7eFWXpqgaEiTxP9OH5ZgVhG+/oDy Y1uRs70YtdYnti+wqy17CvQiUIUfkA3SrOE8bokaUGBHgdwmk4eP9FgXoeF3x8qJEQxL 4ZJw==
X-Received: by 10.68.195.4 with SMTP id ia4mr1015652pbc.142.1390798378991; Sun, 26 Jan 2014 20:52:58 -0800 (PST)
Received: from [192.168.178.23] (100.199.69.111.dynamic.snap.net.nz. [111.69.199.100]) by mx.google.com with ESMTPSA id iu7sm27511270pbc.45.2014.01.26.20.52.55 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 26 Jan 2014 20:52:58 -0800 (PST)
Message-ID: <52E5E624.4080003@gmail.com>
Date: Mon, 27 Jan 2014 17:52:52 +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: Ned Freed <ned.freed@mrochek.com>
Subject: Re: Problem with new Note Well
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <52E3326E.3080007@gmail.com> <82D163D29DC1D4A7B4797E8F@JcK-HP8200.jck.com> <01P3M48DZNS80000AS@mauve.mrochek.com>
In-Reply-To: <01P3M48DZNS80000AS@mauve.mrochek.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, John C Klensin <john-ietf@jck.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 04:53:03 -0000

On 27/01/2014 11:45, Ned Freed wrote:
>> --On Saturday, January 25, 2014 16:41 +1300 Brian E Carpenter
>> <brian.e.carpenter@gmail.com> wrote:
> 
>>> It's quite obvious from reading this thread that the IAOC needs
>>> to revert to the previous Note Well text right now, until the
>>> wording issue is resolved.
>>>
>>> It is apparent to me though that the BCP *requires* disclosure
>>> as a condition of participation, regardless of employment
>>> agreements, and always has done. That's why there has always
>>> been tolerance extended to allow corporate IPR departments to
>>> have time to prepare and make disclosures at lawyerly speed.
>>> Nothing new here except the more brutal wording.
> 
> Nonsense. The BCP is careful to make it clear that you're obliged to
> dislose your IPR when you're contributing.

Yes. I should have written "as a condition of contribution". Sorry.

Anyway - same conclusion, we should use the old wording until
the new wording has been corrected.

    Brian

> 
> The Note Well grossly misprepresents the BCP by talking about any contribution
> and any IPR without qualification. This is incorrect in two ways: It conflates
> contributions in general with someone acting in the role of a contributor, and
> it fails to distingish between "your" IPR and third party IPR. 
> 
> The wording is not brutal, or as others have claimed, overly broad. It's sloppy
> and wrong.
> 
> And I'm far more worried about 3rd party IPR here. BCP 79 section 6.1.3 makes
> disclosure of that a MAY. (The exact word used is "encouraged".) This languages
> makes it a MUST. Would we tolerate a MUST where a MAY is needed in any other
> context, even with an "exceptions may apply" disclaimer attached? I think not.
> 
>> Agreed.  Noting that the likely effect of "regardless of
>> employment agreements" if there really is a conflict in a
>> particular company-participant relations is "don't participate
>> in that" under the BCP and "don't attend" if the wording is more
>> brutal, we should have a lot of incentive to clean the language
>> up... and go back to the tested language until a cleaned-up
>> version is ready.
> 
> Mandating disclosure of 3rd party IPR drags in a whole lot more than employment
> contracts.
> 
> 				Ned
> 

From suzworldwide@gmail.com  Mon Jan 27 06:53:09 2014
Return-Path: <suzworldwide@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F40F1A0237 for <wgchairs@ietfa.amsl.com>; Mon, 27 Jan 2014 06:53:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sK4TLsNavAAP for <wgchairs@ietfa.amsl.com>; Mon, 27 Jan 2014 06:53:07 -0800 (PST)
Received: from mail-qc0-x231.google.com (mail-qc0-x231.google.com [IPv6:2607:f8b0:400d:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id 375DE1A0239 for <wgchairs@ietf.org>; Mon, 27 Jan 2014 06:53:07 -0800 (PST)
Received: by mail-qc0-f177.google.com with SMTP id i8so7947226qcq.8 for <wgchairs@ietf.org>; Mon, 27 Jan 2014 06:53:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=fe+NLL4ZM56/o8+EGtRBTtMFMMUvZeNdlL57ugjmrkc=; b=pOibYCTDglOs04hw3CLSj3L9ARyEZpKE9BD2ftNUE8fbHIijbVKjYVYd7CmVP2x1pP KWZ8fuovs51UygMtOdFBkJH/jkC87C8KYKOg3ltGm9tCbnOCnpsI66eXo/sae/kPOui+ rboVmRXptG/fwE44GL9PG++/fRAJMgZDY77xTjGC4P75wrqhW4dok+mbZujeb04zcpfh vcAOelY54jYFdQjCxv/dO/YbOGGMPv8/r67u8c0NB2PojOQU/DSS+hGjrvSSJjRDmG/G ZvHLomaQKC0PYQaTZmCQGU+t5FFmBqE/N988F+6XSbw2FdBkpxLPE/fva1v4/krHaG3/ mYkA==
X-Received: by 10.224.26.15 with SMTP id b15mr43078398qac.46.1390834384820; Mon, 27 Jan 2014 06:53:04 -0800 (PST)
Received: from [10.0.0.15] (c-24-63-89-87.hsd1.ma.comcast.net. [24.63.89.87]) by mx.google.com with ESMTPSA id a7sm768546qaj.14.2014.01.27.06.53.03 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 27 Jan 2014 06:53:03 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Please double-check your group's archive in the web-based email list archive tool
From: Suzanne Woolf <suzworldwide@gmail.com>
In-Reply-To: <8D1B238B-3A4E-48F7-BCD6-C5F7ED404A9C@harvard.edu>
Date: Mon, 27 Jan 2014 09:53:03 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <476F48FD-0C08-4E30-8FE7-F245293176FF@gmail.com>
References: <52E03D0E.5060703@nostrum.com> <CF0693EB.AAB%sbanks@akamai.com> <8D1B238B-3A4E-48F7-BCD6-C5F7ED404A9C@harvard.edu>
To: wgchairs@ietf.org
X-Mailer: Apple Mail (2.1510)
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 14:53:09 -0000

Hi,

I did a quick few minutes on this for DNSOP.

I like the new search interface lots!

The behavior using "group by thread" seems a little weird, if I turn it =
on I get the behavior I expect (similar to mhonarc "thread index") but =
it seems to stop a month ago, even if the lookback I chose is "past =
year" or "anytime". I'll tinker a little more and submit a ticket.

thanks,
Suzanne

On Jan 23, 2014, at 3:19 PM, "Bradner, Scott" <sob@harvard.edu> wrote:

> since bmwg goes back to 1990 it would be better if all of the email =
was included
>=20
> Scott
>=20
> On Jan 23, 2014, at 12:40 PM, Banks, Sarah <sbanks@akamai.com> wrote:
>=20
>> Hi Robert,
>> 	BMWG looks great; our archives go back to 2001, but that's =
probably OK.
>> The interface is awesome! Thanks!
>>=20
>> Regards,
>> Sarah
>>=20
>> On 1/22/14, 1:50 PM, "Robert Sparks" <rjsparks@nostrum.com> wrote:
>>=20
>>> Chairs -
>>>=20
>>> If you have not already done so, please look briefly at your lists =
in
>>> the new tool and make sure you see what you expect.
>>>=20
>>> You can browse quickly to them with a URL like:
>>>=20
>>> <https://mailarchive.ietf.org/arch/search/?email_list=3Dstir>
>>>=20
>>> Click the date column header twice (the first time will give you a
>>> most-recent to least-recent view, and the second the reverse),
>>> or jump straight to a URL like
>>> <https://mailarchive.ietf.org/arch/search/?email_list=3Dstir&so=3Ddate=
>
>>> and check that the archive goes back as far as you expect.
>>>=20
>>> Note that you can pull the division between the message list pane =
and
>>> the message preview pane down to allow you to see more of the =
messages
>>> in the list at one time.
>>>=20
>>> If you discover something that needs attention, please file a ticket =
at
>>> <http://trac.tools.ietf.org/tools/ietfdb/newticket>
>>>=20
>>> RjS
>>=20
>=20
> Scott O. Bradner
> Senior Technical Consultant
>=20
> Harvard University Information Technology
> Innovation & Architecture
> +1 617 495 3864
> 8 Story St, Room 5014
> Cambridge, MA 02138
> www.huit.harvard.edu
>=20
>=20
>=20
>=20


From geoff.mulligan@nist.gov  Sat Jan 25 08:52:01 2014
Return-Path: <geoff.mulligan@nist.gov>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F5D71A0025; Sat, 25 Jan 2014 08:52:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bBbQ-ooDPmDH; Sat, 25 Jan 2014 08:51:57 -0800 (PST)
Received: from mail.coslabs.com (mail.coslabs.com [199.233.92.34]) by ietfa.amsl.com (Postfix) with ESMTP id B8FE11A001D; Sat, 25 Jan 2014 08:51:56 -0800 (PST)
Received: from [192.168.224.46] (unknown [209.117.47.254]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.coslabs.com (Postfix) with ESMTPSA id C527623744; Sat, 25 Jan 2014 09:51:52 -0700 (MST)
Message-ID: <52E3EBA9.4050005@nist.gov>
Date: Sat, 25 Jan 2014 09:51:53 -0700
From: Geoff Mulligan <geoff.mulligan@nist.gov>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "Bradner, Scott" <sob@harvard.edu>,  Mike StJohns <mstjohns@comcast.net>
Subject: Re: Problem with new Note Well
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu>
In-Reply-To: <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu>
Content-Type: multipart/alternative; boundary="------------090104000507010602050804"
X-Mailman-Approved-At: Mon, 27 Jan 2014 07:19:15 -0800
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 14:25:04 -0000

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

Scott,
   Maybe this is a potential rat-hole - I don't know - but what if:
     -  I'm working as a consultant and attending the IETF representing 
myself
     -  I know of IPR in someone else's contribution
     -  I'm participating in the discussion
     -  I'm under an NDA with that company that covers their IPR

    Geoff

*Presidential Innovation Fellow | Executive Office of the President | 
301.975.6283*

On 01/23/2014 10:58 AM, Bradner, Scott wrote:
> the actual rules are
> 	1/ if you know of any of your IPR in a contribution you make, you must disclose
> 	2/ if you know of any of your IPR in any contribution from someone else and you are participating in discussions
> 	    that involve that contribution, then you must disclose
> 	3/ if you know of any of your IPR in any contribution from someone else and you are not participating in discussions
> 	    that involve that contribution, then you are requested to disclose
>
> see - its not that hard to say this briefly
>
> Scott
>
> On Jan 23, 2014, at 12:49 PM, Michael StJohns <mstjohns@comcast.net> wrote:
>
>> Is the issue the difference between "any contribution YOU MAKE" and "any contribution"?  E.g. if you happen to hear someone discussing something you think is covered by patent, you can't say anything, but conversely, if YOU are making a contribution that's covered by patent then the NDA doesn't apply (because you have approval to make the contribution and disclosure).
>>
>> Mike
>>
>>
>> At 12:25 PM 1/23/2014, Cullen Jennings (fluffy) wrote:
>>
>>> This new note well is a real problem for me and  I can not register without clicking "I agree" to it. It is not consistent with the BCPs. The problem is the line that says
>>>
>>>        . If you are aware that any contribution (something written, said, or discussed in any IETF context) is covered by patents or patent applications, you must disclose that fact.
>>>
>>> I do not agree to that - I can't given my NDA with my employer does not allow me to disclose confidential information. Yes, I realize there is some weasel words near the top that say "Exceptions may apply." but that does not help me. When you are testifying in court on patents, credibility is incredibly important. You can not have the lawyers on the other side saying that you clicked yes I agree to the line above but you did not actually do what that lines says. You may think this does to matter but the exact topic of how Cisco employees deal with IPR at the IETF is a topic that I have testified on in an East Texas court so this really does happen and really does happen to me. It may happen to you next and you will be much happier if you say what you mean and mean what you say. This new note well fails that test.
>>>
>>> I realize some people would like to change the IETF policy to be that you do have to do what that line says but I do not think that is a change the IESG can make without IETF updating the BCP or at least having IETF consensus on the change. I would respectfully ask the IESG to change this line to something that is still brief but that people can agree with it. Simply adding something like "or not contribute to the discussion on that contribution" would probably solve this problem for me.
>>>
>>> Thank you,
>>>
>>> Cullen
>>>
>>> I will note that above line is not consistent with Cisco employment contracts and if we can not resolve this I will be asking Cisco legal to inform Cisco employees they can not agree with this without violating their employment agreement.
>>>
>>>
>>>
>>> On Jan 23, 2014, at 9:44 AM, Russ Housley <housley@vigilsec.com> wrote:
>>>
>>>> It seems that the shorter one is now being used on the IETF web site:
>>>> http://www.ietf.org/about/note-well.html
>>>>
>>>>
>>>> On Jan 8, 2014, at 3:57 PM, Mary Barnes wrote:
>>>>
>>>>> Personally, I've never seen significant value in this shorter note well and while others have been using this new text for the past few meetings, I've stuck to the old.   Now that this is considered the recommended note well for chairs to use, I guess I'll use it.  But, I personally think accuracy should trump brevity.  I think the "must" in that bullet  ought to at least be a should and that adding an "otherwise, one should not contribute to or participate in any related IETF activities." would add more value.
>>>>>
>>>>> Mary.
>>>>>
>>>>>
>>>>> On Wed, Jan 8, 2014 at 1:17 PM, Bradner, Scott <sob@harvard.edu> wrote:
>>>>> you are correct - we (Barry, the IESG & me) discussed this before the IESG approved this text - they felt that
>>>>> being brief was more important than being fully accurate (or at least that is the way I expressed it)
>>>>>
>>>>> Scott
>>>>>
>>>>> Scott O Bradner
>>>>> Senior Technology Consultant
>>>>>
>>>>> Harvard University Information Technology
>>>>> Innovation & Architecture
>>>>> (P) +1 (617) 495 3864
>>>>> 8 Story St, room 5014
>>>>> Cambridge, MA 02138
>>>>>
>>>>>
>>>>>
>>>>> On Jan 8, 2014, at 2:13 PM, Cullen Jennings (fluffy) <fluffy@cisco.com> wrote:
>>>>>
>>>>>>
>>>>>> On Dec 16, 2013, at 12:56 PM, Barry Leiba <barryleiba@computer.org> wrote:
>>>>>>
>>>>>>> The IESG has made final edits to the updated Note Well statement, and
>>>>>>> it has been officially updated:
>>>>>>> http://www.ietf.org/about/note-well.html
>>>>>>>
>>>>>>> I have just uploaded the final versions of the Note Well meeting
>>>>>>> slides, attached to the bottom of the WG Chairs wiki:
>>>>>>> http://wiki.tools.ietf.org/group/wgchairs/wiki/WikiStart
>>>>>>>
>>>>>>> Please use this new version now, and please remember that as you
>>>>>>> prepare slides for the London meeting.
>>>>>>>
>>>>>>> Barry
>>>>>>
>>>>>> The new note well says
>>>>>>
>>>>>>       . If you are aware that any contribution (something written, said, or discussed in any IETF context) is covered by patents or patent applications, you must disclose that fact.
>>>>>>
>>>>>> Is that true?  Or is it missing something along the lines of section y of BCP 79 such as
>>>>>>
>>>>>>   or must not contribute to or participate in IETF activities with
>>>>>>   respect to technologies that he or she reasonably and personally
>>>>>>   knows to be Covered by IPR which he or she will not disclose.
>>>>>>
>>>>>> Thanks, Cullen
>>


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

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Scott,<br>
    &nbsp; Maybe this is a potential rat-hole - I don't know - but what if:<br>
    &nbsp;&nbsp;&nbsp; -&nbsp; I'm working as a consultant and attending the IETF
    representing myself<br>
    &nbsp; &nbsp; -&nbsp; I know of IPR in someone else's contribution<br>
    &nbsp;&nbsp;&nbsp; -&nbsp; I'm participating in the discussion<br>
    &nbsp;&nbsp;&nbsp; -&nbsp; I'm under an NDA with that company that covers their IPR<br>
    <br>
    &nbsp;&nbsp; Geoff<br>
    <br>
    <small><b><font face="serif">Presidential Innovation Fellow |
          Executive Office of the President | 301.975.6283</font></b></small><br>
    <br>
    <div class="moz-cite-prefix">On 01/23/2014 10:58 AM, Bradner, Scott
      wrote:<br>
    </div>
    <blockquote
      cite="mid:77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu"
      type="cite">
      <pre wrap="">the actual rules are
	1/ if you know of any of your IPR in a contribution you make, you must disclose
	2/ if you know of any of your IPR in any contribution from someone else and you are participating in discussions
	    that involve that contribution, then you must disclose
	3/ if you know of any of your IPR in any contribution from someone else and you are not participating in discussions
	    that involve that contribution, then you are requested to disclose

see - its not that hard to say this briefly

Scott

On Jan 23, 2014, at 12:49 PM, Michael StJohns <a class="moz-txt-link-rfc2396E" href="mailto:mstjohns@comcast.net">&lt;mstjohns@comcast.net&gt;</a> wrote:

</pre>
      <blockquote type="cite">
        <pre wrap="">Is the issue the difference between "any contribution YOU MAKE" and "any contribution"?  E.g. if you happen to hear someone discussing something you think is covered by patent, you can't say anything, but conversely, if YOU are making a contribution that's covered by patent then the NDA doesn't apply (because you have approval to make the contribution and disclosure).

Mike


At 12:25 PM 1/23/2014, Cullen Jennings (fluffy) wrote:

</pre>
        <blockquote type="cite">
          <pre wrap="">This new note well is a real problem for me and  I can not register without clicking "I agree" to it. It is not consistent with the BCPs. The problem is the line that says

      . If you are aware that any contribution (something written, said, or discussed in any IETF context) is covered by patents or patent applications, you must disclose that fact.

I do not agree to that - I can't given my NDA with my employer does not allow me to disclose confidential information. Yes, I realize there is some weasel words near the top that say "Exceptions may apply." but that does not help me. When you are testifying in court on patents, credibility is incredibly important. You can not have the lawyers on the other side saying that you clicked yes I agree to the line above but you did not actually do what that lines says. You may think this does to matter but the exact topic of how Cisco employees deal with IPR at the IETF is a topic that I have testified on in an East Texas court so this really does happen and really does happen to me. It may happen to you next and you will be much happier if you say what you mean and mean what you say. This new note well fails that test. 

I realize some people would like to change the IETF policy to be that you do have to do what that line says but I do not think that is a change the IESG can make without IETF updating the BCP or at least having IETF consensus on the change. I would respectfully ask the IESG to change this line to something that is still brief but that people can agree with it. Simply adding something like "or not contribute to the discussion on that contribution" would probably solve this problem for me. 

Thank you, 

Cullen

I will note that above line is not consistent with Cisco employment contracts and if we can not resolve this I will be asking Cisco legal to inform Cisco employees they can not agree with this without violating their employment agreement. 



On Jan 23, 2014, at 9:44 AM, Russ Housley <a class="moz-txt-link-rfc2396E" href="mailto:housley@vigilsec.com">&lt;housley@vigilsec.com&gt;</a> wrote:

</pre>
          <blockquote type="cite">
            <pre wrap="">It seems that the shorter one is now being used on the IETF web site:
<a class="moz-txt-link-freetext" href="http://www.ietf.org/about/note-well.html">http://www.ietf.org/about/note-well.html</a>


On Jan 8, 2014, at 3:57 PM, Mary Barnes wrote:

</pre>
            <blockquote type="cite">
              <pre wrap="">Personally, I've never seen significant value in this shorter note well and while others have been using this new text for the past few meetings, I've stuck to the old.   Now that this is considered the recommended note well for chairs to use, I guess I'll use it.  But, I personally think accuracy should trump brevity.  I think the "must" in that bullet  ought to at least be a should and that adding an "otherwise, one should not contribute to or participate in any related IETF activities." would add more value.   

Mary.


On Wed, Jan 8, 2014 at 1:17 PM, Bradner, Scott <a class="moz-txt-link-rfc2396E" href="mailto:sob@harvard.edu">&lt;sob@harvard.edu&gt;</a> wrote:
you are correct - we (Barry, the IESG &amp; me) discussed this before the IESG approved this text - they felt that
being brief was more important than being fully accurate (or at least that is the way I expressed it)

Scott

Scott O Bradner
Senior Technology Consultant

Harvard University Information Technology
Innovation &amp; Architecture
(P) +1 (617) 495 3864
8 Story St, room 5014
Cambridge, MA 02138



On Jan 8, 2014, at 2:13 PM, Cullen Jennings (fluffy) <a class="moz-txt-link-rfc2396E" href="mailto:fluffy@cisco.com">&lt;fluffy@cisco.com&gt;</a> wrote:

</pre>
              <blockquote type="cite">
                <pre wrap="">

On Dec 16, 2013, at 12:56 PM, Barry Leiba <a class="moz-txt-link-rfc2396E" href="mailto:barryleiba@computer.org">&lt;barryleiba@computer.org&gt;</a> wrote:

</pre>
                <blockquote type="cite">
                  <pre wrap="">The IESG has made final edits to the updated Note Well statement, and
it has been officially updated:
<a class="moz-txt-link-freetext" href="http://www.ietf.org/about/note-well.html">http://www.ietf.org/about/note-well.html</a>

I have just uploaded the final versions of the Note Well meeting
slides, attached to the bottom of the WG Chairs wiki:
<a class="moz-txt-link-freetext" href="http://wiki.tools.ietf.org/group/wgchairs/wiki/WikiStart">http://wiki.tools.ietf.org/group/wgchairs/wiki/WikiStart</a>

Please use this new version now, and please remember that as you
prepare slides for the London meeting.

Barry
</pre>
                </blockquote>
                <pre wrap="">

The new note well says

     . If you are aware that any contribution (something written, said, or discussed in any IETF context) is covered by patents or patent applications, you must disclose that fact.

Is that true?  Or is it missing something along the lines of section y of BCP 79 such as

 or must not contribute to or participate in IETF activities with
 respect to technologies that he or she reasonably and personally
 knows to be Covered by IPR which he or she will not disclose.

Thanks, Cullen
</pre>
              </blockquote>
            </blockquote>
            <pre wrap="">
</pre>
          </blockquote>
        </blockquote>
        <pre wrap="">

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

--------------090104000507010602050804--

From john-ietf@jck.com  Fri Jan 24 19:04:18 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D31E1A0445; Fri, 24 Jan 2014 19:04:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.135
X-Spam-Level: 
X-Spam-Status: No, score=-5.135 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_INVITATION=-2, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rZlVuB2sBoU0; Fri, 24 Jan 2014 19:04:17 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id E993A1A047A; Fri, 24 Jan 2014 19:04:16 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1W6tXU-00064X-Au; Fri, 24 Jan 2014 22:04:08 -0500
Date: Fri, 24 Jan 2014 22:04:03 -0500
From: John C Klensin <john-ietf@jck.com>
To: Pete Resnick <presnick@qti.qualcomm.com>, "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Subject: Re: Problem with new Note Well
Message-ID: <3F2BCC58F9BDF9731C6E7A8C@JcK-HP8200.jck.com>
In-Reply-To: <52E2CBF2.7070807@qti.qualcomm.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E251C2.7060009@gmail.com> <3F350057-8BF4-4A41-BC6D-3141AE419765@cisco.com> <52E2CBF2.7070807@qti.qualcomm.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: Mon, 27 Jan 2014 07:19:33 -0800
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Jan 2014 03:04:18 -0000

--On Friday, January 24, 2014 14:24 -0600 Pete Resnick
<presnick@qti.qualcomm.com> wrote:

>...
> And (and this is probably the one where we might still
> disagree) if it's going to be inaccurate, and it will *have*
> to be inaccurate just by nature of being a summary, I want it
> to be inaccurate such that it includes *more* things to
> disclose than you are actually required to, not less. I don't
> want the excuse for not disclosing to be "I didn't understand
> all of the detail in BCP 79, but the Note Well sure didn't say
> that I had to disclose anything like *that*." If there's going
> to be an inaccuracy in the statement, I want it to be that BCP
> 79 says to disclose *less* than the summarized warning we give
> folks in the room.
>...
> We wrestled with this for a while. I'm open to suggestions.
> But the above are really my design criteria, at least for the
> one we put on a slide for the room.

Pete,

If the announcement appears to require more than what is
actually required, you will divide the part of the audience that
pays any attention at all [1] into three categories:

(1) Those who will be scared off by it, or who will discuss it
with their corporate lawyers who will be scared off.  Perhaps
that will be because they will be concerned that the superset
notice is what they were actually told and for which they might
be held accountable, perhaps they conclude that, in the event of
confusion, conservatism is best.  Perhaps something else, but
the net effect is likely to be as much to reduce IETF
participation by those who are concerned as it would be to get
more disclosures.

(2) Those who will say "Well, the announcement distorts the
meaning of BCP 79, so there must be loopholes they are trying to
hide.  Let's go find them."

(3) Those who will go reread BCP 79, and do exactly what it says
regardless of your exaggerations.

Remembering that our goal should be to enable and encourage as
much participation as possible consistent with getting the
disclosures we actually need, I don't see most of those options
as desirable.

    john

[1] Some of us have a talent for tuning out boilerplate.  As a
sometime WG chair, if I have any choice at all, I won't spend
time trying to read things that I'm pretty sure that those who
will listen have already seen and those who won't, won't (I
think that puts my position in alignment with Paul Hoffman's).
As an individual, as soon as the WG Chair says something that
implies "I have this obligatory statement to read that you have
heard before", I'm likely to decide it is an invitation to open
a tunnel to my mailbox (or equivalent).  If that describes a
significant set of patterns, then anything you do to alter the
in-meeting version is a waste of time.
 


From john-ietf@jck.com  Sat Jan 25 05:19:38 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F53D1A02EE; Sat, 25 Jan 2014 05:19:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.135
X-Spam-Level: 
X-Spam-Status: No, score=-3.135 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ErVvyD58Z99m; Sat, 25 Jan 2014 05:19:36 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 4B8281A02EA; Sat, 25 Jan 2014 05:19:36 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1W7391-000789-Qc; Sat, 25 Jan 2014 08:19:31 -0500
Date: Sat, 25 Jan 2014 08:19:26 -0500
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Subject: Re: Problem with new Note Well
Message-ID: <82D163D29DC1D4A7B4797E8F@JcK-HP8200.jck.com>
In-Reply-To: <52E3326E.3080007@gmail.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <52E3326E.3080007@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Mailman-Approved-At: Mon, 27 Jan 2014 07:19:34 -0800
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Jan 2014 13:19:38 -0000

--On Saturday, January 25, 2014 16:41 +1300 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

> It's quite obvious from reading this thread that the IAOC needs
> to revert to the previous Note Well text right now, until the
> wording issue is resolved.
> 
> It is apparent to me though that the BCP *requires* disclosure
> as a condition of participation, regardless of employment
> agreements, and always has done. That's why there has always
> been tolerance extended to allow corporate IPR departments to
> have time to prepare and make disclosures at lawyerly speed.
> Nothing new here except the more brutal wording.

Agreed.  Noting that the likely effect of "regardless of
employment agreements" if there really is a conflict in a
particular company-participant relations is "don't participate
in that" under the BCP and "don't attend" if the wording is more
brutal, we should have a lot of incentive to clean the language
up... and go back to the tested language until a cleaned-up
version is ready.

    john



From john-ietf@jck.com  Sat Jan 25 06:46:13 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AEBE1A037D; Sat, 25 Jan 2014 06:46:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.135
X-Spam-Level: 
X-Spam-Status: No, score=-3.135 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Az-SbAeTZnyo; Sat, 25 Jan 2014 06:46:11 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id B70771A026C; Sat, 25 Jan 2014 06:46:11 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1W74Uq-0007ED-HI; Sat, 25 Jan 2014 09:46:08 -0500
Date: Sat, 25 Jan 2014 09:46:03 -0500
From: John C Klensin <john-ietf@jck.com>
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>, Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Problem with new Note Well
Message-ID: <9393741FAF54D30498339914@JcK-HP8200.jck.com>
In-Reply-To: <29860DAF-ABE7-4EAD-B79B-5537D661B89B@cisco.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E251C2.7060009@gmail.com> <3F350057-8BF4-4A41-BC6D-3141AE419765@cisco.com> <52E2CBF2.7070807@qti.qualcomm.com> <29860DAF-ABE7-4EAD-B79B-5537D661B89B@cisco.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Mailman-Approved-At: Mon, 27 Jan 2014 07:19:34 -0800
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Jan 2014 14:46:13 -0000

--On Saturday, January 25, 2014 14:21 +0000 "Cullen Jennings
(fluffy)" <fluffy@cisco.com> wrote:

>...
>> - By participating here, you've agreed to our rules.
>> - You can be recorded.
>> - You have to disclose your IPR.
> 
> It's this above point that I don't believe is true. I
> think the point you need to make is, I think what you need to
> say is 
> 
>       "You have to disclose your IPR, or not participate in
> the discussion"

And, of course, this drags us into the precise definition of
"participate", an axle around which we've gotten wrapped several
times.  In particular, 

> I do want to point out that if you truly wanted this short the
> total slides would say 
> 
>       "This meeting may be recorded. To be in this meeting you
> must agree to the rules in BCP 79. "

but "to be in this meeting" means that sitting in the room
during a WG session constitutes "participation".  I like that
definition, but we've been around it several times and my
recollection is that I was in the minority.  If "participate"
for IPR purposes has any resemblance to "making a Contribution",
e.g., opening your mouth, then the above statement is as false
as some of those to which you object.

>...
> The core issue here is that you are making the summary be a
> sentence which is not wrong and which people can not and will
> not comply with. At that point you toss the whole thing into
> questions. People who need to testify in court on patents will
> have their credibility undermined by having agreed to this and
> then not doing it. You need to come up with a summary is not
> wrong even if it is not be complete.

Yep.  See earlier comments by Brian and myself, but this
credibility effect is equally important.

Perhaps the appropriate short statement might be more like:

	"If you are in this room two minutes from now or
	thereafter, you are deemed to have read, understood, and
	agreed to BCP 79.  If you have not read and understood
	it, please leave until after you do."
	
I hope that is a joke, but it is short, says nothing false, and
doesn't get entangled with terms like "participate".

>...

   john



From scott.brim@gmail.com  Sat Jan 25 11:25:44 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB4ED1A002F; Sat, 25 Jan 2014 11:25:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level: 
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_42=0.6, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W-NwtcsVAJAh; Sat, 25 Jan 2014 11:25:44 -0800 (PST)
Received: from mail-oa0-x22c.google.com (mail-oa0-x22c.google.com [IPv6:2607:f8b0:4003:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id CE8EF1A0028; Sat, 25 Jan 2014 11:25:43 -0800 (PST)
Received: by mail-oa0-f44.google.com with SMTP id g12so5251621oah.31 for <multiple recipients>; Sat, 25 Jan 2014 11:25:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=jCSTZYhUafSIeAyvC0oDr0L0+eP3/ZPtBvbmQW0uQPQ=; b=L6LeqWht1ZJh/GG8UCZucMvkVi8HUXmd/OLP6flz1GmsaxOSZ4tXulSkbS1yOZVxAc nr3x4J6PgzMHqeBv2XsoNwZPSXcphLgXGhDVO4CuCxw/Rm/NcAkXokzgMlclnG3jC92n I8LlOr8X7NIs60AgLBCtbeA37Tv9oRJXuGJIPjokwGwXNyWTIt/J3/cRNUhQDJjIDgwr iEugs5E/eixx5VhCiI86nzZrijhCOEY7YIZLbrrPBKVW9/wbWfiEtMGIMEXxj503IN9G aAi00gR03Rw/suQYbH0M6zXozYyFpLQ9CggTGzGGIvnBsWDplRB8FQdm8EdoxGG5QgYd XZ5g==
MIME-Version: 1.0
X-Received: by 10.182.16.33 with SMTP id c1mr17500362obd.4.1390677942212; Sat, 25 Jan 2014 11:25:42 -0800 (PST)
Received: by 10.182.48.9 with HTTP; Sat, 25 Jan 2014 11:25:41 -0800 (PST)
Received: by 10.182.48.9 with HTTP; Sat, 25 Jan 2014 11:25:41 -0800 (PST)
In-Reply-To: <B627AAAB-5F7B-4230-AB9E-99838C0BC63E@gmail.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E251C2.7060009@gmail.com> <3F350057-8BF4-4A41-BC6D-3141AE419765@cisco.com> <52E2CBF2.7070807@qti.qualcomm.com> <29860DAF-ABE7-4EAD-B79B-5537D661B89B@cisco.com> <9393741FAF54D30498339914@JcK-HP8200.jck.com> <D8D0971F-57F9-405A-B25D-61F9C88B84EE@cisco.com> <B627AAAB-5F7B-4230-AB9E-99838C0BC63E@gmail.com>
Date: Sat, 25 Jan 2014 14:25:41 -0500
Message-ID: <CAPv4CP9ecuVsNJXo1k0ALAhs8cJQK5ihirAo7aPaqLik4pwLyg@mail.gmail.com>
Subject: Re: Problem with new Note Well
From: Scott Brim <scott.brim@gmail.com>
To: Suzanne Woolf <suzworldwide@gmail.com>
Content-Type: multipart/alternative; boundary=f46d04479f93be1e9304f0d070e7
X-Mailman-Approved-At: Mon, 27 Jan 2014 07:19:35 -0800
Cc: John C Klensin <john-ietf@jck.com>, wgchairs@ietf.org, Pete Resnick <presnick@qti.qualcomm.com>, IETF discussion list <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Jan 2014 19:25:45 -0000

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

On Jan 25, 2014 2:16 PM, "Suzanne Woolf" <suzworldwide@gmail.com> wrote:
> As a long-time IETF'er and new WG chair, I want a) something I can say in
the room as part of the opening ...

What I did last time I chaired was put up the Note Well and tell everyone
it was important and they should read it; pass out blue sheets; when I came
back, ask if anyone had not read it. I didn't have to turn anyone off by
reading something to them, but I did get to call their attention to it
twice.

Scott

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

<p dir=3D"ltr"><br>
On Jan 25, 2014 2:16 PM, &quot;Suzanne Woolf&quot; &lt;<a href=3D"mailto:su=
zworldwide@gmail.com">suzworldwide@gmail.com</a>&gt; wrote:<br>
&gt; As a long-time IETF&#39;er and new WG chair, I want a) something I can=
 say in the room as part of the opening ...</p>
<p dir=3D"ltr">What I did last time I chaired was put up the Note Well and =
tell everyone it was important and they should read it; pass out blue sheet=
s; when I came back, ask if anyone had not read it. I didn&#39;t have to tu=
rn anyone off by reading something to them, but I did get to call their att=
ention to it twice. </p>

<p dir=3D"ltr">Scott</p>

--f46d04479f93be1e9304f0d070e7--

From john-ietf@jck.com  Sun Jan 26 15:24:51 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9EE91A0169; Sun, 26 Jan 2014 15:24:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.135
X-Spam-Level: 
X-Spam-Status: No, score=-3.135 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0kICEHxdElsE; Sun, 26 Jan 2014 15:24:50 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 36ADE1A0092; Sun, 26 Jan 2014 15:24:50 -0800 (PST)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1W7Z4B-000AkQ-6r; Sun, 26 Jan 2014 18:24:39 -0500
X-Vipre-Scanned: 0536E268002C310536E3B5-TDI
Date: Sun, 26 Jan 2014 18:24:37 -0500
From: John C Klensin <john-ietf@jck.com>
To: Ned Freed <ned.freed@mrochek.com>
Subject: Re: Problem with new Note Well
Message-ID: <9244D7CE10A93EC07BBD46C6@[192.168.1.128]>
In-Reply-To: <01P3M48DZNS80000AS@mauve.mrochek.com>
References: <01P3M48DZNS80000AS@mauve.mrochek.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: Mon, 27 Jan 2014 07:19:35 -0800
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Jan 2014 23:24:52 -0000

--On Sunday, 26 January, 2014 14:45 -0800 Ned Freed
<ned.freed@mrochek.com> wrote:

>...
>> Agreed.  Noting that the likely effect of "regardless of
>> employment agreements" if there really is a conflict in a
>> particular company-participant relations is "don't participate
>> in that" under the BCP and "don't attend" if the wording is
>> more brutal, we should have a lot of incentive to clean the
>> language up... and go back to the tested language until a
>> cleaned-up version is ready.
> 
> Mandating disclosure of 3rd party IPR drags in a whole lot
> more than employment contracts.

Of course.  And some of what gets dragged in is, or may be, more
important than the employment contracts.  I was just responding
to Brian's specific point and trying to suggest that "regardless
of employment agreements" was really not something one could say
if an open, broadly representative, IETF was part of one's
target.

I agree about "sloppy and wrong" too.

best,
   john





From john-ietf@jck.com  Mon Jan 27 07:46:03 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A2D81A0228; Mon, 27 Jan 2014 07:46:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.135
X-Spam-Level: 
X-Spam-Status: No, score=-3.135 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zQKc8X5igdCb; Mon, 27 Jan 2014 07:46:01 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id CB2F61A021B; Mon, 27 Jan 2014 07:45:57 -0800 (PST)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1W7oNk-000D0z-9p; Mon, 27 Jan 2014 10:45:52 -0500
X-Vipre-Scanned: 08B93933002C3108B93A80-TDI
Date: Mon, 27 Jan 2014 10:45:51 -0500
From: John C Klensin <john-ietf@jck.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>, Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Problem with new Note Well
Message-ID: <2B1C52E87C5B3A5C2D68E3E1@[192.168.1.128]>
In-Reply-To: <CAHBDyN5dm+=najR5LVGDyxrcpAyivx+hEnF0Zzhzzik6wmO_gw@mail.gmail.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E251C2.7060009@gmail.com> <3F350057-8BF4-4A41-BC6D-3141AE419765@cisco.com> <52E2CBF2.7070807@qti.qualcomm.com> <CAHBDyN5dm+=najR5LVGDyxrcpAyivx+hEnF0Zzhzzik6wmO_gw@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 15:46:03 -0000

--On Friday, 24 January, 2014 15:03 -0600 Mary Barnes
<mary.ietf.barnes@gmail.com> wrote:

>...
> [MB] As a chair, I would not be reading the statement out
> loud. As far as I'm concerned, my responsibility as a chair is
> to make sure everyone in the room is aware of the IETF IPR
> rules - it's not up to me to summarize them for the group.

For both this new statement and its predecessors, it seems to me
that we have to recognize the limitations of what we are trying
to do and think about and balance policy plans accordingly.   If
your "responsibility as a chair is to make sure everyone in the
room is aware..." then you need to repeat the announcement every
time someone walks into the room who wasn't there when you made
your check, showed your slides, or did your reading.  Unless we
are going to take to locking doors so that no one can enter a WG
meeting after the "Note Well" announcement is made, such
repetition would be disruptive and absurd.  

Similarly, if one were really inclined to "make sure", the right
way to do it would be to ask at the beginning of the session for
everyone who was familiar with the IPR policies to put up their
hands, ask everyone else to leave, and then take pictures of
everyone who was left for later correlation with the blue
sheets.  But that is almost equally absurd and the community has
been fairly clear about its distaste for pictures that can be
correlated with names.

Given our registration procedures, we could take the possession
of a badge as evidence that someone had been adequately exposed
to the Note Well (if not actually to the BCP) and arrange to
check for badges at meeting room doors.  But we've decided, IMO,
for good reason, to not do that either.


> And, saying go read the details "if you're worried" isn't
> sufficient.  Everyone should have read the documents in detail
> and make sure that anyone that has a say on how they disclose
> and deal with IPR in IETF (i.e., corporate lawyers) are aware
> of IETF policy.  [/MB]

Yes.  But "the documents" there are BCP 79 (and probably BCP 78
and various Trust policies) and not some summary.  And, no
matter how much it might make those who are IPR-fascinated
happy, as a WG participant and sometime chair, I don't want
people spending time in WG meetings trying to decipher BCP79 and
its implications (or bringing their lawyers with them to do so)
any more than I want them buried in email -- I want them paying
attention to the meeting, else why are they present.  

For someone (and their organizations if relevant) who is
adequately familiar with BCP 79 before walking into the WG
meeting, further announcements, regardless of their precise
content, are a waste of time except maybe as a small reminder.
For anyone who isn't, the announcements are useless unless we
are just trying to tell them that they might be in big trouble
if they stay in the room.

best,
   john

 





From jari.arkko@piuha.net  Mon Jan 27 08:02:15 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13B4C1A0297; Mon, 27 Jan 2014 08:02:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ekyPX4cf7-LX; Mon, 27 Jan 2014 08:02:13 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 5ADA61A0231; Mon, 27 Jan 2014 08:02:13 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id D56202CCBE; Mon, 27 Jan 2014 18:02:10 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I6CU8y0JMJ6C; Mon, 27 Jan 2014 18:02:10 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 62CFC2CC5D; Mon, 27 Jan 2014 18:02:10 +0200 (EET)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Third party disclosures and NDAs (Re: Problem with new Note Well )
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <52E3EBA9.4050005@nist.gov>
Date: Mon, 27 Jan 2014 18:02:10 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <CB2D10B9-DAD4-4C47-B984-A55D136C3126@piuha.net>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E3EBA9.4050005@nist.gov>
To: Geoff Mulligan <geoff.mulligan@nist.gov>
X-Mailer: Apple Mail (2.1510)
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 16:02:15 -0000

Starting a separate thread, because this is not related to the original =
complaint about inaccurate new note well text.

>   Maybe this is a potential rat-hole - I don't know - but what if:
>     -  I'm working as a consultant and attending the IETF representing =
myself
>     -  I know of IPR in someone else's contribution
>     -  I'm participating in the discussion
>     -  I'm under an NDA with that company that covers their IPR

That is a rat-^H^H^H^Hhard problem. Something has to give. You can't =
simultaneously follow two incompatible sets of rules. If you end up in =
that situation and can't convince parties to disclose, maybe =
"participating in the discussion" has to give. Of course this is a =
specific example of things that can happen in people's lives in other =
ways, too. Two consulting contracts that have incompatible requirements. =
Board position and a job that creates a conflict interest for you to be =
in the board. And so on.

Jari


From scott.brim@gmail.com  Mon Jan 27 08:07:04 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5982E1A029C; Mon, 27 Jan 2014 08:07:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AubJ-WyhqhLk; Mon, 27 Jan 2014 08:07:03 -0800 (PST)
Received: from mail-ob0-x234.google.com (mail-ob0-x234.google.com [IPv6:2607:f8b0:4003:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id 01DBC1A0255; Mon, 27 Jan 2014 08:07:02 -0800 (PST)
Received: by mail-ob0-f180.google.com with SMTP id wp4so6689502obc.11 for <multiple recipients>; Mon, 27 Jan 2014 08:07:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=S/l1ErEhC7iExKjtlMhPgmbw03D93KhGidOWBeFzf4A=; b=OYwtIBPzEteL/WaLq0A5ke7unyqYa2kmyqaBgRgxROR4NyYLZ3/urpOQjqUpqvLrUS rgl2XcXZBhPW4qxuimDdrxFWNX/Je1eu85ZdATwoBP/yz9MnbIEBt/I1jradsoSCFM/R op6n6+y8hPV6u5fJZ14ETujF1TiRTKUy1sYnXC6j9VFSGPqYJEb6VK6IA3BZJzSu4I4/ khHVzo6sLm0rbmy5+V3nye1lEusRCE1Dzud8vNep3pTl6+o6uUFAZx8wkFTHt54SiXxA HwLnekNw6O5MdgXutrupkcQOernlWnCJIxnBZ1Fcmkdqbr0uxa36F+k5zyPPiXe/XEG1 QZuw==
X-Received: by 10.182.148.106 with SMTP id tr10mr617384obb.65.1390838820642; Mon, 27 Jan 2014 08:07:00 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Mon, 27 Jan 2014 08:06:40 -0800 (PST)
In-Reply-To: <CB2D10B9-DAD4-4C47-B984-A55D136C3126@piuha.net>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E3EBA9.4050005@nist.gov> <CB2D10B9-DAD4-4C47-B984-A55D136C3126@piuha.net>
From: Scott Brim <scott.brim@gmail.com>
Date: Mon, 27 Jan 2014 11:06:40 -0500
Message-ID: <CAPv4CP8dGLrPfsq_Jrz7mFk2eCuxs58gQ1xGqR-BeT=ZFoWhmQ@mail.gmail.com>
Subject: Re: Third party disclosures and NDAs (Re: Problem with new Note Well )
To: Jari Arkko <jari.arkko@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, Geoff Mulligan <geoff.mulligan@nist.gov>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 16:07:04 -0000

On Mon, Jan 27, 2014 at 11:02 AM, Jari Arkko <jari.arkko@piuha.net> wrote:
> Starting a separate thread, because this is not related to the original c=
omplaint about inaccurate new note well text.
>
>>   Maybe this is a potential rat-hole - I don't know - but what if:
>>     -  I'm working as a consultant and attending the IETF representing m=
yself
>>     -  I know of IPR in someone else's contribution
>>     -  I'm participating in the discussion
>>     -  I'm under an NDA with that company that covers their IPR
>
> That is a rat-^H^H^H^Hhard problem. Something has to give. You can't simu=
ltaneously follow two incompatible sets of rules. If you end up in that sit=
uation and can't convince parties to disclose, maybe "participating in the =
discussion" has to give. Of course this is a specific example of things tha=
t can happen in people's lives in other ways, too. Two consulting contracts=
 that have incompatible requirements. Board position and a job that creates=
 a conflict interest for you to be in the board. And so on.
>
> Jari

Right. IMHO if you haven't anticipated this situation you would do
best to shut up until you talk to your lawyers. However, thankfully,
you have learned that you need to anticipate the problem and you can
talk to them before the problem arises.

Scott

From hallam@gmail.com  Mon Jan 27 08:12:42 2014
Return-Path: <hallam@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 078CE1A0242; Mon, 27 Jan 2014 08:12:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pUxH57PAJB1P; Mon, 27 Jan 2014 08:12:39 -0800 (PST)
Received: from mail-lb0-x236.google.com (mail-lb0-x236.google.com [IPv6:2a00:1450:4010:c04::236]) by ietfa.amsl.com (Postfix) with ESMTP id 425271A0231; Mon, 27 Jan 2014 08:12:39 -0800 (PST)
Received: by mail-lb0-f182.google.com with SMTP id w7so4699692lbi.27 for <multiple recipients>; Mon, 27 Jan 2014 08:12:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Ii/ajS5A5SGtzVnZV8vN7T/VUx7HtNL9YBWfKVr5FrM=; b=c9D2TTqk+p/6W77E2nTeJBio2l7cEJyxTJbouD6lUCwlK743gtvru49pnlZGvtfOsI Ha+1DhAvMW47ZGszlO8HnGKneDWrgMePv3JR4fbVFzEC1B90fhldLmf9nncAvvgb954O jesqxaq9shsvzhzEna9PGY5b8RTyrXDqw7xKysd/uzfcLTtw3e57GrL1Ju8QKcEh2wcy XtPiwfVAm5t+KmyX5zcbYV8nJO2APKnTSgWhZKDfz0wACEvvgZ0ONN5z+5eklybciehs QVmjNDCHBKd13E9mZHqCrJZaGpWDI8vrw3x5mCYZaKd2GU6w3PRN9jWXXYKjtBfaczOU xY1A==
MIME-Version: 1.0
X-Received: by 10.153.0.33 with SMTP id av1mr12750303lad.14.1390839155701; Mon, 27 Jan 2014 08:12:35 -0800 (PST)
Received: by 10.112.37.168 with HTTP; Mon, 27 Jan 2014 08:12:35 -0800 (PST)
In-Reply-To: <CB2D10B9-DAD4-4C47-B984-A55D136C3126@piuha.net>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E3EBA9.4050005@nist.gov> <CB2D10B9-DAD4-4C47-B984-A55D136C3126@piuha.net>
Date: Mon, 27 Jan 2014 11:12:35 -0500
Message-ID: <CAMm+LwgArQzBO+fs=k=oc31s9ShCnYJF-B25WHw4rYUGCiQ57w@mail.gmail.com>
Subject: Re: Third party disclosures and NDAs (Re: Problem with new Note Well )
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Jari Arkko <jari.arkko@piuha.net>
Content-Type: multipart/alternative; boundary=001a11381264d0beb604f0f5f95a
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, Geoff Mulligan <geoff.mulligan@nist.gov>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 16:12:42 -0000

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

On Mon, Jan 27, 2014 at 11:02 AM, Jari Arkko <jari.arkko@piuha.net> wrote:

> Starting a separate thread, because this is not related to the original
> complaint about inaccurate new note well text.
>
> >   Maybe this is a potential rat-hole - I don't know - but what if:
> >     -  I'm working as a consultant and attending the IETF representing
> myself
> >     -  I know of IPR in someone else's contribution
> >     -  I'm participating in the discussion
> >     -  I'm under an NDA with that company that covers their IPR
>
> That is a rat-^H^H^H^Hhard problem. Something has to give. You can't
> simultaneously follow two incompatible sets of rules. If you end up in that
> situation and can't convince parties to disclose, maybe "participating in
> the discussion" has to give. Of course this is a specific example of things
> that can happen in people's lives in other ways, too. Two consulting
> contracts that have incompatible requirements. Board position and a job
> that creates a conflict interest for you to be in the board. And so on.
>
> Jari
>
>
And it is not just IPR, it is IPR claims that are covered.

I know a lot of IPR claims that are utter hogwash. But if I am working with
a company that is defending itself against a lawsuit asserting that claim,
their lawyers usually don't want that to be public knowledge until they
tell the plaintiff.

The IETF IPR rules were crafted to address one particular IPR problem that
doesn't really exist any more because the courts have effectively
eliminated any incentive. Anyone who goes to a standards body with the
objective of covertly ensuring that the standard necessarily infringes is
risking getting their patent invalidated at the very least.

The IPR problems we have at the moment are an industry wide patent war that
has broken out between groups of companies with very broad portfolios of
claims which come from significant investments in R&D and a large number of
non-practicing entities, some of which have attempted claims that are so
ridiculous the lawyers behind them are facing civil lawsuits from the FTC.


-- 
Website: http://hallambaker.com/

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Mon, Jan 27, 2014 at 11:02 AM, Jari Arkko <span dir=3D"ltr">&lt;=
<a href=3D"mailto:jari.arkko@piuha.net" target=3D"_blank">jari.arkko@piuha.=
net</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Starting a separate thread, because this is =
not related to the original complaint about inaccurate new note well text.<=
br>

<br>
&gt; =A0 Maybe this is a potential rat-hole - I don&#39;t know - but what i=
f:<br>
&gt; =A0 =A0 - =A0I&#39;m working as a consultant and attending the IETF re=
presenting myself<br>
&gt; =A0 =A0 - =A0I know of IPR in someone else&#39;s contribution<br>
&gt; =A0 =A0 - =A0I&#39;m participating in the discussion<br>
&gt; =A0 =A0 - =A0I&#39;m under an NDA with that company that covers their =
IPR<br>
<br>
That is a rat-^H^H^H^Hhard problem. Something has to give. You can&#39;t si=
multaneously follow two incompatible sets of rules. If you end up in that s=
ituation and can&#39;t convince parties to disclose, maybe &quot;participat=
ing in the discussion&quot; has to give. Of course this is a specific examp=
le of things that can happen in people&#39;s lives in other ways, too. Two =
consulting contracts that have incompatible requirements. Board position an=
d a job that creates a conflict interest for you to be in the board. And so=
 on.<br>

<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Jari<br>
<br>
</font></span></blockquote></div><br>And it is not just IPR, it is IPR clai=
ms that are covered.</div><div class=3D"gmail_extra"><br></div><div class=
=3D"gmail_extra">I know a lot of IPR claims that are utter hogwash. But if =
I am working with a company that is defending itself against a lawsuit asse=
rting that claim, their lawyers usually don&#39;t want that to be public kn=
owledge until they tell the plaintiff.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">The IETF IP=
R rules were crafted to address one particular IPR problem that doesn&#39;t=
 really exist any more because the courts have effectively eliminated any i=
ncentive. Anyone who goes to a standards body with the objective of covertl=
y ensuring that the standard necessarily infringes is risking getting their=
 patent invalidated at the very least.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">The IPR pro=
blems we have at the moment are an industry wide patent war that has broken=
 out between groups of companies with very broad portfolios of claims which=
 come from significant investments in R&amp;D and a large number of non-pra=
cticing entities, some of which have attempted claims that are so ridiculou=
s the lawyers behind them are facing civil lawsuits from the FTC.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><div><br></=
div>-- <br>Website: <a href=3D"http://hallambaker.com/">http://hallambaker.=
com/</a><br>
</div></div>

--001a11381264d0beb604f0f5f95a--

From jari.arkko@piuha.net  Mon Jan 27 08:17:26 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5283B1A02E8; Mon, 27 Jan 2014 08:17:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qCyDXtBA5IXn; Mon, 27 Jan 2014 08:17:25 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id C90FF1A025D; Mon, 27 Jan 2014 08:17:24 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 4EFBB2CCBE; Mon, 27 Jan 2014 18:17:22 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oVvaTZl1HdlB; Mon, 27 Jan 2014 18:17:21 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id BB37C2CC5D; Mon, 27 Jan 2014 18:17:20 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Problem with new Note Well 
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <52E5E624.4080003@gmail.com>
Date: Mon, 27 Jan 2014 18:17:20 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <19AAADA2-8E3B-456F-B0CE-9A27D2BB5FE9@piuha.net>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <52E3326E.3080007@gmail.com> <82D163D29DC1D4A7B4797E8F@JcK-HP8200.jck.com> <01P3M48DZNS80000AS@mauve.mrochek.com> <52E5E624.4080003@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "Cullen Jennings (fluffy)" <fluffy@cisco.com>
X-Mailer: Apple Mail (2.1510)
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 16:17:26 -0000

All - it is clear that you have a concern about the new note well text. =
The problem has been well articulated; personally, I'd be happy with =
some of the edits suggested. However, it is probably better if we do the =
word-smithing separately and come back with a proposal. I have asked the =
IESG to consider the situation and the need for a new version of the =
note well and/or reverting to the old version.

Thanks for the feedback, as always!

Jari


From geoff.mulligan@nist.gov  Mon Jan 27 09:01:02 2014
Return-Path: <geoff.mulligan@nist.gov>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B07E1A0353; Mon, 27 Jan 2014 09:01:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WJUGh93uLETU; Mon, 27 Jan 2014 09:01:00 -0800 (PST)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0212.outbound.protection.outlook.com [207.46.163.212]) by ietfa.amsl.com (Postfix) with ESMTP id 37E461A0345; Mon, 27 Jan 2014 09:01:00 -0800 (PST)
Received: from BLUPR09MB054.namprd09.prod.outlook.com (10.255.211.148) by BLUPR09MB053.namprd09.prod.outlook.com (10.255.211.146) with Microsoft SMTP Server (TLS) id 15.0.859.15; Mon, 27 Jan 2014 17:00:56 +0000
Received: from BLUPR09MB054.namprd09.prod.outlook.com ([169.254.9.155]) by BLUPR09MB054.namprd09.prod.outlook.com ([169.254.9.155]) with mapi id 15.00.0859.020; Mon, 27 Jan 2014 17:00:56 +0000
From: "Mulligan, Geoff" <geoff.mulligan@nist.gov>
To: Jari Arkko <jari.arkko@piuha.net>
Subject: RE: Third party disclosures and NDAs (Re: Problem with new Note Well )
Thread-Topic: Third party disclosures and NDAs (Re: Problem with new Note Well )
Thread-Index: AQHPG3klyCBjqxHw+E6Dqsh/YOVH+ZqYyr7p
Date: Mon, 27 Jan 2014 17:00:55 +0000
Message-ID: <126fb3003777478a93ac346b525150af@BLUPR09MB054.namprd09.prod.outlook.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E3EBA9.4050005@nist.gov>,<CB2D10B9-DAD4-4C47-B984-A55D136C3126@piuha.net>
In-Reply-To: <CB2D10B9-DAD4-4C47-B984-A55D136C3126@piuha.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [129.6.33.54]
x-forefront-prvs: 0104247462
x-forefront-antispam-report: SFV:NSPM; SFS:(10009001)(6009001)(189002)(199002)(377454003)(54356001)(76482001)(53806001)(74662001)(74502001)(47446002)(87266001)(31966008)(46102001)(2656002)(51856001)(93516002)(50986001)(47976001)(85306002)(81686001)(76576001)(87936001)(76786001)(76796001)(69226001)(81816001)(77096001)(4396001)(47736001)(33646001)(49866001)(83322001)(19580405001)(56816005)(81342001)(19580395003)(93136001)(65816001)(74706001)(80022001)(92566001)(74316001)(81542001)(80976001)(90146001)(86362001)(54316002)(56776001)(85852003)(83072002)(59766001)(77982001)(74876001)(63696002)(79102001)(74366001)(66066001)(94316002)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:BLUPR09MB053; H:BLUPR09MB054.namprd09.prod.outlook.com; CLIP:129.6.33.54; FPR:; MLV:nspm; InfoNoRecordsMX:1; A:1; LANG:en; 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: nist.gov
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 17:01:02 -0000

So because I know of IPR that someone else has and is not disclosing and be=
cause I cannot legally disclose it - I can't continue to participate in the=
 discussion doesn't seem right.  I'm not the holder of the IPR that isn't b=
eing disclosed, but I'm penalized.=0A=
=0A=
Geoff=0A=
=0A=
=0A=
Geoff Mulligan | Presidential Innovation Fellow | Cyber Physical Systems | =
301.975.6283=0A=
=0A=
________________________________________=0A=
From: Jari Arkko <jari.arkko@piuha.net>=0A=
Sent: Monday, January 27, 2014 11:02 AM=0A=
To: Mulligan, Geoff=0A=
Cc: IETF WG Chairs; ietf@ietf.org Mailing List=0A=
Subject: Third party disclosures and NDAs (Re: Problem with new Note Well )=
=0A=
=0A=
Starting a separate thread, because this is not related to the original com=
plaint about inaccurate new note well text.=0A=
=0A=
>   Maybe this is a potential rat-hole - I don't know - but what if:=0A=
>     -  I'm working as a consultant and attending the IETF representing my=
self=0A=
>     -  I know of IPR in someone else's contribution=0A=
>     -  I'm participating in the discussion=0A=
>     -  I'm under an NDA with that company that covers their IPR=0A=
=0A=
That is a rat-^H^H^H^Hhard problem. Something has to give. You can't simult=
aneously follow two incompatible sets of rules. If you end up in that situa=
tion and can't convince parties to disclose, maybe "participating in the di=
scussion" has to give. Of course this is a specific example of things that =
can happen in people's lives in other ways, too. Two consulting contracts t=
hat have incompatible requirements. Board position and a job that creates a=
 conflict interest for you to be in the board. And so on.=0A=
=0A=
Jari=0A=
=0A=

From geoff.mulligan@nist.gov  Mon Jan 27 09:04:03 2014
Return-Path: <geoff.mulligan@nist.gov>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB59B1A0378; Mon, 27 Jan 2014 09:04:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u7E1z1GQHznQ; Mon, 27 Jan 2014 09:04:01 -0800 (PST)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1blp0188.outbound.protection.outlook.com [207.46.163.188]) by ietfa.amsl.com (Postfix) with ESMTP id 587121A0363; Mon, 27 Jan 2014 09:04:01 -0800 (PST)
Received: from BLUPR09MB054.namprd09.prod.outlook.com (10.255.211.148) by BLUPR09MB055.namprd09.prod.outlook.com (10.255.211.152) with Microsoft SMTP Server (TLS) id 15.0.859.15; Mon, 27 Jan 2014 17:03:58 +0000
Received: from BLUPR09MB054.namprd09.prod.outlook.com ([169.254.9.155]) by BLUPR09MB054.namprd09.prod.outlook.com ([169.254.9.155]) with mapi id 15.00.0859.020; Mon, 27 Jan 2014 17:03:58 +0000
From: "Mulligan, Geoff" <geoff.mulligan@nist.gov>
To: Scott Brim <scott.brim@gmail.com>, Jari Arkko <jari.arkko@piuha.net>
Subject: RE: Third party disclosures and NDAs (Re: Problem with new Note Well )
Thread-Topic: Third party disclosures and NDAs (Re: Problem with new Note Well )
Thread-Index: AQHPG3klyCBjqxHw+E6Dqsh/YOVH+ZqYvJQAgAAPTFk=
Date: Mon, 27 Jan 2014 17:03:57 +0000
Message-ID: <b416b4c6ea2248d393f90fe0860d4165@BLUPR09MB054.namprd09.prod.outlook.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E3EBA9.4050005@nist.gov> <CB2D10B9-DAD4-4C47-B984-A55D136C3126@piuha.net>, <CAPv4CP8dGLrPfsq_Jrz7mFk2eCuxs58gQ1xGqR-BeT=ZFoWhmQ@mail.gmail.com>
In-Reply-To: <CAPv4CP8dGLrPfsq_Jrz7mFk2eCuxs58gQ1xGqR-BeT=ZFoWhmQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [129.6.33.54]
x-forefront-prvs: 0104247462
x-forefront-antispam-report: SFV:NSPM; SFS:(10009001)(6009001)(377454003)(51704005)(199002)(189002)(24454002)(79102001)(59766001)(77982001)(46102001)(80976001)(81542001)(4396001)(74316001)(81342001)(56776001)(83322001)(19580405001)(53806001)(47976001)(47736001)(49866001)(50986001)(19580395003)(54316002)(85852003)(83072002)(74876001)(81686001)(2656002)(81816001)(94316002)(90146001)(56816005)(87936001)(74706001)(87266001)(92566001)(80022001)(47446002)(85306002)(74366001)(66066001)(65816001)(31966008)(74662001)(74502001)(86362001)(93516002)(33646001)(63696002)(77096001)(54356001)(76482001)(51856001)(76796001)(76786001)(69226001)(76576001)(93136001)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:BLUPR09MB055; H:BLUPR09MB054.namprd09.prod.outlook.com; CLIP:129.6.33.54; FPR:; MLV:nspm; InfoNoRecordsA:1; MX:1; LANG:en; 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: nist.gov
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 17:04:04 -0000

I do want to be clear - I am not currently facing this situation and I have=
n't yet faced this situation, but I fear that as a consultant (in the futur=
e when this current job ends) I may face this.  I want to understand my opt=
ions as I would like to continue my participation and affiliation with the =
IETF.=0A=
=0A=
   Geoff=0A=
=0A=
=0A=
Geoff Mulligan | Presidential Innovation Fellow | Cyber Physical Systems | =
301.975.6283=0A=
    =0A=
________________________________________=0A=
From: Scott Brim <scott.brim@gmail.com>=0A=
Sent: Monday, January 27, 2014 11:06 AM=0A=
To: Jari Arkko=0A=
Cc: Mulligan, Geoff; IETF WG Chairs; ietf@ietf.org Mailing List=0A=
Subject: Re: Third party disclosures and NDAs (Re: Problem with new Note We=
ll )=0A=
=0A=
On Mon, Jan 27, 2014 at 11:02 AM, Jari Arkko <jari.arkko@piuha.net> wrote:=
=0A=
> Starting a separate thread, because this is not related to the original c=
omplaint about inaccurate new note well text.=0A=
>=0A=
>>   Maybe this is a potential rat-hole - I don't know - but what if:=0A=
>>     -  I'm working as a consultant and attending the IETF representing m=
yself=0A=
>>     -  I know of IPR in someone else's contribution=0A=
>>     -  I'm participating in the discussion=0A=
>>     -  I'm under an NDA with that company that covers their IPR=0A=
>=0A=
> That is a rat-^H^H^H^Hhard problem. Something has to give. You can't simu=
ltaneously follow two incompatible sets of rules. If you end up in that sit=
uation and can't convince parties to disclose, maybe "participating in the =
discussion" has to give. Of course this is a specific example of things tha=
t can happen in people's lives in other ways, too. Two consulting contracts=
 that have incompatible requirements. Board position and a job that creates=
 a conflict interest for you to be in the board. And so on.=0A=
>=0A=
> Jari=0A=
=0A=
Right. IMHO if you haven't anticipated this situation you would do=0A=
best to shut up until you talk to your lawyers. However, thankfully,=0A=
you have learned that you need to anticipate the problem and you can=0A=
talk to them before the problem arises.=0A=
=0A=
Scott=0A=

From presnick@qti.qualcomm.com  Mon Jan 27 09:16:44 2014
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 202FE1A038C; Mon, 27 Jan 2014 09:16:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level: 
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bwGgQjtAVq0h; Mon, 27 Jan 2014 09:16:42 -0800 (PST)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id ED6641A0372; Mon, 27 Jan 2014 09:16:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1390843000; x=1422379000; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=mhJMSTSoyvCkA8tVzxb+1utFXq/wEqwg/F8YxDBgkAE=; b=T7S5kqern91whxrA2JO1yS8oXeRj73USAVAKe0AKQKrV5R2K8tSmJ1dl 7lfKWlMn5w2N3dZSdyvSszecNWMf1o1QQstCRUZ086xpMoyBmiNPSSA7x 2KQtXoyXmEddlcShHyMqzK98ReyX/L4k35pLExRICdD7vm4twzFarLvU9 s=;
X-IronPort-AV: E=McAfee;i="5400,1158,7330"; a="58688827"
Received: from ironmsg03-r.qualcomm.com ([172.30.46.17]) by sabertooth02.qualcomm.com with ESMTP; 27 Jan 2014 09:16:39 -0800
X-IronPort-AV: E=McAfee;i="5400,1158,7330"; a="620168779"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 27 Jan 2014 09:16:39 -0800
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 27 Jan 2014 09:16:38 -0800
Message-ID: <52E69475.6020403@qti.qualcomm.com>
Date: Mon, 27 Jan 2014 11:16:37 -0600
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Subject: Re: Problem with new Note Well
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E251C2.7060009@gmail.com> <3F350057-8BF4-4A41-BC6D-3141AE419765@cisco.com> <52E2CBF2.7070807@qti.qualcomm.com> <29860DAF-ABE7-4EAD-B79B-5537D661B89B@cisco.com>
In-Reply-To: <29860DAF-ABE7-4EAD-B79B-5537D661B89B@cisco.com>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 8bit
X-Originating-IP: [172.30.39.5]
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 17:16:44 -0000

Re-reading, apparently I was in a particularly foul mood last week. My 
apologies for the amount of foulness that leaked through.

Closing the loop:

On 1/25/14 8:21 AM, Cullen Jennings (fluffy) wrote:
> It’s this above point that I don’t believe is true. I think the point you need to make is, I think what you need to say is
>
>        "You have to disclose your IPR, or not participate in the discussion"
>    

For in the room, I'd be fine with that. If all you want to do is add "or 
not participate in the discussion" to the end of what's there now, cool 
with me.

I am completely ambivalent about what goes on the registration page or 
elsewhere on the web site. I am fine with that text being different than 
what is used in the room as the reminder. I would like something that is 
more of a "plain language" version.

> I do want to point out that if you truly wanted this short the total slides would say
>
>        "This meeting may be recorded. To be in this meeting you must agree to the rules in BCP 79. "
>    

Well, that's the problem with the original text. All it says is "you 
have to abide by BCP 79" and doesn't mention "IPR" at all. Nobody 
reading it could be expected to know that there are IPR rules in the 
IETF from only reading that. For practical purposes, I think that's 
next-to-useless.

Anyway, it sounds like Jari is asking for a regroup. A fine plan.

pr

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


From scott.brim@gmail.com  Mon Jan 27 09:35:05 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71D1A1A025D; Mon, 27 Jan 2014 09:35:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id es6uSZuhSOnA; Mon, 27 Jan 2014 09:35:03 -0800 (PST)
Received: from mail-ob0-x230.google.com (mail-ob0-x230.google.com [IPv6:2607:f8b0:4003:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id 896B71A015A; Mon, 27 Jan 2014 09:35:03 -0800 (PST)
Received: by mail-ob0-f176.google.com with SMTP id gq1so6797373obb.35 for <multiple recipients>; Mon, 27 Jan 2014 09:35:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=p/DRpa9aJElSth7LdkQmyoEyinOqO3bcLuV+etgGaeA=; b=B7CKHl6z7x/eI4CjFDJnBN8pKx8lgF8CJP/j+VFweZC9bymGVlyi6E5wkbAxH7TkLf ksk38C8JZW5rCE/8rV2dPlUBNmCA2mjV4rJtwDs1+76fJKwCn0l4bFphPI+ZcpIaNBtn QEjiakUBcuQWNpzr0RWyGN0wUhUO2+t9c+WQ21HTLi8fqet63A30BlkrOui753OKeJ+u 87AJ44YLLJoXr3hZadQQemQma3evDMs/qMn9KzR/d2xD/5kq9GnL2vQeOL5piqTlVkT8 Mal0TNW2mfYumnKD2nFjk+um+HytNvMPYdlgdtxnK2OWUHEvIhNLnNxBYfupQFeqz02K OAtQ==
X-Received: by 10.182.247.68 with SMTP id yc4mr926787obc.67.1390844101240; Mon, 27 Jan 2014 09:35:01 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Mon, 27 Jan 2014 09:34:41 -0800 (PST)
In-Reply-To: <b416b4c6ea2248d393f90fe0860d4165@BLUPR09MB054.namprd09.prod.outlook.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E3EBA9.4050005@nist.gov> <CB2D10B9-DAD4-4C47-B984-A55D136C3126@piuha.net> <CAPv4CP8dGLrPfsq_Jrz7mFk2eCuxs58gQ1xGqR-BeT=ZFoWhmQ@mail.gmail.com> <b416b4c6ea2248d393f90fe0860d4165@BLUPR09MB054.namprd09.prod.outlook.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Mon, 27 Jan 2014 12:34:41 -0500
Message-ID: <CAPv4CP_QU=SSpQxAiw9_VWZ5O1ZG4fiKVScOi7yUNNDX5_GB9Q@mail.gmail.com>
Subject: Re: Third party disclosures and NDAs (Re: Problem with new Note Well )
To: "Mulligan, Geoff" <geoff.mulligan@nist.gov>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 17:35:05 -0000

On Mon, Jan 27, 2014 at 12:03 PM, Mulligan, Geoff
<geoff.mulligan@nist.gov> wrote:
> I do want to be clear - I am not currently facing this situation and I ha=
ven't yet faced this situation, but I fear that as a consultant (in the fut=
ure when this current job ends) I may face this.  I want to understand my o=
ptions as I would like to continue my participation and affiliation with th=
e IETF.

Geoff, IMHO (and I have done this): when you start a consulting gig
that involves speaking up in SDOs, set up time to review the SDO IPR
policies with your management and lawyers, and get a baseline for how
they want you to handle gray area situations.

From pkyzivat@alum.mit.edu  Mon Jan 27 09:42:34 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0B391A015E for <wgchairs@ietfa.amsl.com>; Mon, 27 Jan 2014 09:42:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IeHOwOXODA_u for <wgchairs@ietfa.amsl.com>; Mon, 27 Jan 2014 09:42:33 -0800 (PST)
Received: from qmta02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:24]) by ietfa.amsl.com (Postfix) with ESMTP id 785CA1A0353 for <wgchairs@ietf.org>; Mon, 27 Jan 2014 09:42:27 -0800 (PST)
Received: from omta23.westchester.pa.mail.comcast.net ([76.96.62.74]) by qmta02.westchester.pa.mail.comcast.net with comcast id K0hf1n0071c6gX8515iRLf; Mon, 27 Jan 2014 17:42:25 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta23.westchester.pa.mail.comcast.net with comcast id K5iQ1n00x3ZTu2S3j5iRtY; Mon, 27 Jan 2014 17:42:25 +0000
Message-ID: <52E69A80.5010206@alum.mit.edu>
Date: Mon, 27 Jan 2014 12:42:24 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: Problem with new Note Well
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E251C2.7060009@gmail.com> <3F350057-8BF4-4A41-BC6D-3141AE419765@cisco.com> <52E2CBF2.7070807@qti.qualcomm.com> <29860DAF-ABE7-4EAD-B79B-5537D661B89B@cisco.com> <52E69475.6020403@qti.qualcomm.com>
In-Reply-To: <52E69475.6020403@qti.qualcomm.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1390844545; bh=tL2jbZucLWxk6SdVCscgzmJzLMLeE0vs2v/vmj74Z2M=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=KozcGcMrMVqZSDJKBfMLmsray+PMXWCUC2WZ0YtxOtpuNkuTC9SY1Z5/Ur135RXnl YhtjRNv4Hxjp2nzag+lqDjYBU3kWs/xRDUoLitNXmIv9a5wr1a46QJBX5zMxegZFf6 +F5SCDozfLnfLbAsSMxRFp8PzxGF6f/oZKnwc42jLAg2Ab1W+CA9OZ8A5ytFn8SmPJ EPPxpWI6/PjYEMWVBZfSQlt1KF7ZXJFbe5MAppu5cOcOZmTyJnG0nnj7BRe2c0AkO6 LIYxwsvwZfo8tTYQd2ua5iJxZ/FFXf7XoNJ2mF5qVja7HGOPK9dsasyQK1qUl1PA93 klkrAlmlNnh6g==
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 17:42:35 -0000

Given all this mess, why don't we just:

- rely on the checkoff at registration time to verify that registered 
attendees are aware of our rules

- replace the note well with one that says: If you have not registered 
for this meeting then don't belong here.

	Thanks,
	Paul

On 1/27/14 12:16 PM, Pete Resnick wrote:
> Re-reading, apparently I was in a particularly foul mood last week. My
> apologies for the amount of foulness that leaked through.
>
> Closing the loop:
>
> On 1/25/14 8:21 AM, Cullen Jennings (fluffy) wrote:
>> It’s this above point that I don’t believe is true. I think the point
>> you need to make is, I think what you need to say is
>>
>>        "You have to disclose your IPR, or not participate in the
>> discussion"
>
> For in the room, I'd be fine with that. If all you want to do is add "or
> not participate in the discussion" to the end of what's there now, cool
> with me.
>
> I am completely ambivalent about what goes on the registration page or
> elsewhere on the web site. I am fine with that text being different than
> what is used in the room as the reminder. I would like something that is
> more of a "plain language" version.
>
>> I do want to point out that if you truly wanted this short the total
>> slides would say
>>
>>        "This meeting may be recorded. To be in this meeting you must
>> agree to the rules in BCP 79. "
>
> Well, that's the problem with the original text. All it says is "you
> have to abide by BCP 79" and doesn't mention "IPR" at all. Nobody
> reading it could be expected to know that there are IPR rules in the
> IETF from only reading that. For practical purposes, I think that's
> next-to-useless.
>
> Anyway, it sounds like Jari is asking for a regroup. A fine plan.
>
> pr
>


From dhc@dcrocker.net  Mon Jan 27 09:21:38 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CD021A0246; Mon, 27 Jan 2014 09:21:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NgDGyVEe4wMY; Mon, 27 Jan 2014 09:21:35 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 7E19E1A0141; Mon, 27 Jan 2014 09:21:35 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s0RHLBVx020732 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 27 Jan 2014 09:21:15 -0800
Message-ID: <52E69572.7000903@dcrocker.net>
Date: Mon, 27 Jan 2014 09:20:50 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>, Brian E Carpenter <brian.e.carpenter@gmail.com>, "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Subject: Re: Problem with new Note Well
X-Priority: 2 (High)
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <52E3326E.3080007@gmail.com> <82D163D29DC1D4A7B4797E8F@JcK-HP8200.jck.com> <01P3M48DZNS80000AS@mauve.mrochek.com> <52E5E624.4080003@gmail.com> <19AAADA2-8E3B-456F-B0CE-9A27D2BB5FE9@piuha.net>
In-Reply-To: <19AAADA2-8E3B-456F-B0CE-9A27D2BB5FE9@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Mon, 27 Jan 2014 09:21:15 -0800 (PST)
X-Mailman-Approved-At: Mon, 27 Jan 2014 09:45:28 -0800
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 17:21:38 -0000

On 1/27/2014 8:17 AM, Jari Arkko wrote:
> All - it is clear that you have a concern about the new note well text. The problem has been well articulated;


Jari, et al,


There are a number of different problems, and only some of them have 
been articulated.  Worse, the problems include the IPR rules themselves, 
not just the Note Well:

      0.  We have had IPR rules and a Note Well for many years and have 
revised both a number of times.  Normally, work we do that has been 
around that long warrants being called "mature", which means that it 
works well and is well understood.  The latest discussion demonstrates 
that that model does not apply to the IETF's IPR handling.  In fact, the 
exchange looks more like the disparities we see early in a working group 
effort, not what normally takes place after many years.

      1. The participants in the discussion are extremely experienced 
with the IETF and with this topic.  Yet they demonstrated a strong 
/lack/ of rough consensus about what the /current/ IPR rules mean.

      2.  The current rules are too complex for use by average 
engineers.  Engineers are not attorneys, nevermind IPR attorneys.  IPR 
is considered by attorneys to be an esoteric and difficult specialty. 
The IETF's IPR rules need to be simple and simply stated, if we expect 
average engineers to understand them.

      3.  The current IPR rules appear to impose an unreasonable demand 
on IETF participants, such as conflicting with employment arrangements. 
(And if the demand is reasonable, then what is noteworthy is that 
someone who has read this latest IETF discussion has developed the 
impression that it isn't.  See point 6.)

      4.  The current Note Well is too complex and apparently erroneous. 
  (And if it is not erroneous, then what is noteworthy is that a serious 
attempt to review the thread has resulted in someone coming to the 
conclusion that the Note Well is erroneous.  See point 6.)

      5.  Expecting an average IETF engineer to consult 4 different 
BCPs, in order to understand what is required of them is not reasonable. 
  Nor is all each document relevant.  So, in effect, the references are 
overly broad, as well as too complicated. (See point 6.)

      6.  Having a range of experienced, diligent IETF participants 
demonstrate substantive disagreement about the meaning of our current 
IPR rules undermines whatever utility the rules might have.  It sets up 
a litigation argument that the participant did not understand the rules, 
citing this thread as demonstrating that others also don't.


The remedies we need are not just with the Note Well.  We need to fix 
the IPR rules too.


      0.  We need to establish clear and compelling community rough 
consensus about the meaning of our IPR rules and the utility of our Note 
Well.  We are currently /very/ far from being able to do that.

      1.  We need a consensus statement that describes our 'model' of an 
IETF particpant, in terms of what is reasonable for them to know and 
what is reasonable for them to be responsible for and what is reasonable 
for them to do, especially within the real time performance constraints 
of a working group meeting. The premise of that model needs to be 
extreme simplicity and clarity.  Any rules we assert need to be vetted 
against that model.  Our current arrangement requires an average 
engineer to be more knowledgeable and more diligent than is reasonable. 
  (By 'diligent' I'm not referring to intent; I'm referring to classic 
human factors usability limits.)

      2.  One of the distinctions in the latest discussion is between 
having the Note Well attempt to summarize what the IPR rules are, versus 
having it merely declare that we have IPR rules and point the reader to 
them.  For summary instruments, like a Note Well, the latter approach 
makes far more sense.

      3.  We need all of the IPR rules for IETF participation to be in a 
single, simple, clear document that is easily understandable by an 
average engineer. (See point 1.)


d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From keith.drage@alcatel-lucent.com  Mon Jan 27 11:25:00 2014
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE7B21A0341; Mon, 27 Jan 2014 11:25:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NUKnR4Hxa6QZ; Mon, 27 Jan 2014 11:24:58 -0800 (PST)
Received: from hoemail1.alcatel.com (hoemail1.alcatel.com [192.160.6.148]) by ietfa.amsl.com (Postfix) with ESMTP id 0C8F61A033D; Mon, 27 Jan 2014 11:24:57 -0800 (PST)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by hoemail1.alcatel.com (8.13.8/IER-o) with ESMTP id s0RJOrch013849 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 27 Jan 2014 13:24:54 -0600 (CST)
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id s0RJOqYh016110 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 27 Jan 2014 20:24:52 +0100
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.26]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.02.0247.003; Mon, 27 Jan 2014 20:24:52 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: "Mulligan, Geoff" <geoff.mulligan@nist.gov>, Jari Arkko <jari.arkko@piuha.net>
Subject: RE: Third party disclosures and NDAs (Re: Problem with new Note Well )
Thread-Topic: Third party disclosures and NDAs (Re: Problem with new Note Well )
Thread-Index: AQHPG3klyCBjqxHw+E6Dqsh/YOVH+ZqYyr7pgAAnw3A=
Date: Mon, 27 Jan 2014 19:24:51 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B123A69@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E3EBA9.4050005@nist.gov>,<CB2D10B9-DAD4-4C47-B984-A55D136C3126@piuha.net> <126fb3003777478a93ac346b525150af@BLUPR09MB054.namprd09.prod.outlook.com>
In-Reply-To: <126fb3003777478a93ac346b525150af@BLUPR09MB054.namprd09.prod.outlook.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.39]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 19:25:01 -0000

An you clarify whether you consider your use case as trying to meet the req=
uirements of 6.1.2 or the requirements of 6.1.3 of RFC 3979.

Regards

Keith=20

> -----Original Message-----
> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf=20
> Of Mulligan, Geoff
> Sent: 27 January 2014 17:01
> To: Jari Arkko
> Cc: IETF WG Chairs; ietf@ietf.org Mailing List
> Subject: RE: Third party disclosures and NDAs (Re: Problem=20
> with new Note Well )
>=20
> So because I know of IPR that someone else has and is not=20
> disclosing and because I cannot legally disclose it - I can't=20
> continue to participate in the discussion doesn't seem right.=20
>  I'm not the holder of the IPR that isn't being disclosed,=20
> but I'm penalized.
>=20
> Geoff
>=20
>=20
> Geoff Mulligan | Presidential Innovation Fellow | Cyber=20
> Physical Systems | 301.975.6283
>=20
> ________________________________________
> From: Jari Arkko <jari.arkko@piuha.net>
> Sent: Monday, January 27, 2014 11:02 AM
> To: Mulligan, Geoff
> Cc: IETF WG Chairs; ietf@ietf.org Mailing List
> Subject: Third party disclosures and NDAs (Re: Problem with=20
> new Note Well )
>=20
> Starting a separate thread, because this is not related to=20
> the original complaint about inaccurate new note well text.
>=20
> >   Maybe this is a potential rat-hole - I don't know - but what if:
> >     -  I'm working as a consultant and attending the IETF=20
> representing myself
> >     -  I know of IPR in someone else's contribution
> >     -  I'm participating in the discussion
> >     -  I'm under an NDA with that company that covers their IPR
>=20
> That is a rat-^H^H^H^Hhard problem. Something has to give.=20
> You can't simultaneously follow two incompatible sets of=20
> rules. If you end up in that situation and can't convince=20
> parties to disclose, maybe "participating in the discussion"=20
> has to give. Of course this is a specific example of things=20
> that can happen in people's lives in other ways, too. Two=20
> consulting contracts that have incompatible requirements.=20
> Board position and a job that creates a conflict interest for=20
> you to be in the board. And so on.
>=20
> Jari
>=20
> =

From lenny@juniper.net  Mon Jan 27 11:29:15 2014
Return-Path: <lenny@juniper.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DDE01A03C5 for <wgchairs@ietfa.amsl.com>; Mon, 27 Jan 2014 11:29:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EiusMLlFwUwu for <wgchairs@ietfa.amsl.com>; Mon, 27 Jan 2014 11:29:12 -0800 (PST)
Received: from co9outboundpool.messaging.microsoft.com (co9ehsobe004.messaging.microsoft.com [207.46.163.27]) by ietfa.amsl.com (Postfix) with ESMTP id 662B01A0264 for <wgchairs@ietf.org>; Mon, 27 Jan 2014 11:29:12 -0800 (PST)
Received: from mail152-co9-R.bigfish.com (10.236.132.243) by CO9EHSOBE023.bigfish.com (10.236.130.86) with Microsoft SMTP Server id 14.1.225.22; Mon, 27 Jan 2014 19:29:09 +0000
Received: from mail152-co9 (localhost [127.0.0.1])	by mail152-co9-R.bigfish.com (Postfix) with ESMTP id C63BE360104;	Mon, 27 Jan 2014 19:29:09 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:66.129.239.16; KIP:(null); UIP:(null); IPV:NLI; H:P-EMF02-SAC.jnpr.net; RD:none; EFVD:NLI
X-SpamScore: -17
X-BigFish: VPS-17(z579ehz98dIzz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h2189h1d1ah1d2ah21bch1fc6h1082kzz1033IL17326ah8275dh1de097h186068hz31h2a8h839h944hd25hf0ah11b5h121eh1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h16a6h1758h18e1h1946h19b5h1ad9h1b0ah1b2fh224fh1fb3h1d0ch1d2eh1d3fh1de2h1dfeh1dffh1fe8h1ff5h2216h22d0h2336h2438h2461h2487h24d7h2388i1155h)
Received-SPF: softfail (mail152-co9: transitioning domain of juniper.net does not designate 66.129.239.16 as permitted sender) client-ip=66.129.239.16; envelope-from=lenny@juniper.net; helo=P-EMF02-SAC.jnpr.net ; SAC.jnpr.net ; 
Received: from mail152-co9 (localhost.localdomain [127.0.0.1]) by mail152-co9 (MessageSwitch) id 1390850948492428_8226; Mon, 27 Jan 2014 19:29:08 +0000 (UTC)
Received: from CO9EHSMHS023.bigfish.com (unknown [10.236.132.238])	by mail152-co9.bigfish.com (Postfix) with ESMTP id 6F42040085;	Mon, 27 Jan 2014 19:29:08 +0000 (UTC)
Received: from P-EMF02-SAC.jnpr.net (66.129.239.16) by CO9EHSMHS023.bigfish.com (10.236.130.33) with Microsoft SMTP Server (TLS) id 14.16.227.3; Mon, 27 Jan 2014 19:29:07 +0000
Received: from magenta.juniper.net (172.17.27.123) by P-EMF02-SAC.jnpr.net (172.24.192.21) with Microsoft SMTP Server (TLS) id 14.3.146.0; Mon, 27 Jan 2014 11:29:05 -0800
Received: from eng-mail01.juniper.net (eng-mail01.juniper.net [172.17.28.114]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id s0RJSxL33299; Mon, 27 Jan 2014 11:29:00 -0800 (PST)	(envelope-from lenny@juniper.net)
Received: by eng-mail01.juniper.net (Postfix, from userid 1709)	id C6C901145A;  Mon, 27 Jan 2014 11:28:53 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])	by eng-mail01.juniper.net (Postfix) with ESMTP id AE6DC11446;	Mon, 27 Jan 2014 11:28:53 -0800 (PST)
Date: Mon, 27 Jan 2014 11:28:53 -0800
From: Leonard Giuliano <lenny@juniper.net>
To: Robert Sparks <rjsparks@nostrum.com>
Subject: Re: Please double-check your group's archive in the web-based email list archive tool
In-Reply-To: <52E03D0E.5060703@nostrum.com>
Message-ID: <20140127112517.C38491@eng-mail01.juniper.net>
References: <52E03D0E.5060703@nostrum.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: "<wgchairs@ietf.org>" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 19:29:15 -0000

The searching and filtering functions are great enhancements.  Will the 
old mhonarc system still be available, or will it be killed?  I may be 
the only one, but I kind of like that old interface.  Can we have both 
available?


On Wed, 22 Jan 2014, Robert Sparks wrote:

-) Chairs -
-) 
-) If you have not already done so, please look briefly at your lists in the new
-) tool and make sure you see what you expect.
-) 
-) You can browse quickly to them with a URL like:
-) 
-) <https://mailarchive.ietf.org/arch/search/?email_list=stir>
-) 
-) Click the date column header twice (the first time will give you a
-) most-recent to least-recent view, and the second the reverse),
-) or jump straight to a URL like
-) <https://mailarchive.ietf.org/arch/search/?email_list=stir&so=date>
-) and check that the archive goes back as far as you expect.
-) 
-) Note that you can pull the division between the message list pane and the
-) message preview pane down to allow you to see more of the messages in the
-) list at one time.
-) 
-) If you discover something that needs attention, please file a ticket at
-) <http://trac.tools.ietf.org/tools/ietfdb/newticket>
-) 
-) RjS
-) 


From rjsparks@nostrum.com  Mon Jan 27 11:41:08 2014
Return-Path: <rjsparks@nostrum.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 160751A0237 for <wgchairs@ietfa.amsl.com>; Mon, 27 Jan 2014 11:41:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.036
X-Spam-Level: 
X-Spam-Status: No, score=-1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CMIITO8LgwYv for <wgchairs@ietfa.amsl.com>; Mon, 27 Jan 2014 11:41:07 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 17BC51A007C for <wgchairs@ietf.org>; Mon, 27 Jan 2014 11:41:06 -0800 (PST)
Received: from unnumerable.local (pool-173-71-10-88.dllstx.fios.verizon.net [173.71.10.88]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id s0RJf4iO071743 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK) for <wgchairs@ietf.org>; Mon, 27 Jan 2014 13:41:04 -0600 (CST) (envelope-from rjsparks@nostrum.com)
Message-ID: <52E6B650.8090507@nostrum.com>
Date: Mon, 27 Jan 2014 13:41:04 -0600
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: Please double-check your group's archive in the web-based email list archive tool
References: <52E03D0E.5060703@nostrum.com> <20140127112517.C38491@eng-mail01.juniper.net>
In-Reply-To: <20140127112517.C38491@eng-mail01.juniper.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.71.10.88 is authenticated by a trusted mechanism)
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 19:41:08 -0000

On 1/27/14, 1:28 PM, Leonard Giuliano wrote:
> The searching and filtering functions are great enhancements.  Will the
> old mhonarc system still be available, or will it be killed?  I may be
> the only one, but I kind of like that old interface.  Can we have both
> available?
The existing system will run in parallel for some time, but will eventually
be taken offline.
>
>
> On Wed, 22 Jan 2014, Robert Sparks wrote:
>
> -) Chairs -
> -)
> -) If you have not already done so, please look briefly at your lists in the new
> -) tool and make sure you see what you expect.
> -)
> -) You can browse quickly to them with a URL like:
> -)
> -) <https://mailarchive.ietf.org/arch/search/?email_list=stir>
> -)
> -) Click the date column header twice (the first time will give you a
> -) most-recent to least-recent view, and the second the reverse),
> -) or jump straight to a URL like
> -) <https://mailarchive.ietf.org/arch/search/?email_list=stir&so=date>
> -) and check that the archive goes back as far as you expect.
> -)
> -) Note that you can pull the division between the message list pane and the
> -) message preview pane down to allow you to see more of the messages in the
> -) list at one time.
> -)
> -) If you discover something that needs attention, please file a ticket at
> -) <http://trac.tools.ietf.org/tools/ietfdb/newticket>
> -)
> -) RjS
> -)
>


From caozhen@chinamobile.com  Mon Jan 27 20:11:58 2014
Return-Path: <caozhen@chinamobile.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F02C1A03FE for <wgchairs@ietfa.amsl.com>; Mon, 27 Jan 2014 20:11:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.213
X-Spam-Level: 
X-Spam-Status: No, score=-0.213 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RELAY_IS_221=2.222, RP_MATCHES_RCVD=-0.535] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dz8z-Oda0sqx for <wgchairs@ietfa.amsl.com>; Mon, 27 Jan 2014 20:11:56 -0800 (PST)
Received: from cmccmta.chinamobile.com (cmccmta.chinamobile.com [221.176.64.232]) by ietfa.amsl.com (Postfix) with SMTP id DADB61A017F for <wgchairs@ietf.org>; Mon, 27 Jan 2014 20:11:55 -0800 (PST)
Received: from spf.mail.chinamobile.com (unknown[172.16.20.21]) by rmmx-oa_allagent02-12002 (RichMail) with SMTP id 2ee252e72d850c3-830c3; Tue, 28 Jan 2014 12:09:41 +0800 (CST)
X-RM-TRANSID: 2ee252e72d850c3-830c3
Received: from cmccPC (unknown[10.2.52.172]) by rmsmtp-oa_rmapp03-12003 (RichMail) with SMTP id 2ee352e72d846bd-7c379; Tue, 28 Jan 2014 12:09:41 +0800 (CST)
X-RM-TRANSID: 2ee352e72d846bd-7c379
From: "Cao Zhen \(CZ\)" <caozhen@chinamobile.com>
To: "'Robert Sparks'" <rjsparks@nostrum.com>, <wgchairs@ietf.org>
References: <52E03D0E.5060703@nostrum.com>
In-Reply-To: <52E03D0E.5060703@nostrum.com>
Subject: RE: Please double-check your group's archive in the web-based email list archive tool
Date: Tue, 28 Jan 2014 12:11:46 +0800
Message-ID: <00e601cf1bdf$11098fd0$331caf70$@chinamobile.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQD6jUv1GeF9mBKCSO3FN8VEFoT5UpxCjR5g
Content-Language: zh-cn
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 04:11:58 -0000

Hi Robert,=20

Nice work, thank you so much.

I have an issue to report, e.g., the Lwig working group 's mailing list =
is lwip@ietf.org.=20
If I just search the wg name 'lwig', I found nothing.

Any way to put synonym?

Best regards,
Zhen=20

> -----Original Message-----
> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of Robert =
Sparks
> Sent: Thursday, January 23, 2014 5:50 AM
> To: <wgchairs@ietf.org>
> Subject: Please double-check your group's archive in the web-based =
email list
> archive tool
>=20
> Chairs -
>=20
> If you have not already done so, please look briefly at your lists in =
the new tool
> and make sure you see what you expect.
>=20
> You can browse quickly to them with a URL like:
>=20
> <https://mailarchive.ietf.org/arch/search/?email_list=3Dstir>
>=20
> Click the date column header twice (the first time will give you a =
most-recent to
> least-recent view, and the second the reverse), or jump straight to a =
URL like
> =
<https://mailarchive.ietf.org/arch/search/?email_list=3Dstir&so=3Ddate>
> and check that the archive goes back as far as you expect.
>=20
> Note that you can pull the division between the message list pane and =
the
> message preview pane down to allow you to see more of the messages in =
the list
> at one time.
>=20
> If you discover something that needs attention, please file a ticket =
at
> <http://trac.tools.ietf.org/tools/ietfdb/newticket>
>=20
> RjS




From jari.arkko@piuha.net  Mon Jan 27 23:44:07 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA9EB1A02A1; Mon, 27 Jan 2014 23:44:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a20CEbrs_sgS; Mon, 27 Jan 2014 23:44:07 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id DFCBF1A0276; Mon, 27 Jan 2014 23:44:06 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 2CF112CC61; Tue, 28 Jan 2014 09:44:04 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nVLtCgRKNEDU; Tue, 28 Jan 2014 09:44:03 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id A4DC72CC5D; Tue, 28 Jan 2014 09:44:03 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Problem with new Note Well 
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <19AAADA2-8E3B-456F-B0CE-9A27D2BB5FE9@piuha.net>
Date: Tue, 28 Jan 2014 09:44:03 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <31F38883-AA9F-420F-877F-394C283A779F@piuha.net>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <52E3326E.3080007@gmail.com> <82D163D29DC1D4A7B4797E8F@JcK-HP8200.jck.com> <01P3M48DZNS80000AS@mauve.mrochek.com> <52E5E624.4080003@gmail.com> <19AAADA2-8E3B-456F-B0CE-9A27D2BB5FE9@piuha.net>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "Cullen Jennings (fluffy)" <fluffy@cisco.com>
X-Mailer: Apple Mail (2.1510)
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 07:44:08 -0000

For your information, as a temporary measure we have pulled back the =
change and the web site (registration etc) should now display the old =
note well text.

Jari


From prvs=710514c311=sandra.murphy@parsons.com  Tue Jan 28 10:08:31 2014
Return-Path: <prvs=710514c311=sandra.murphy@parsons.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0B751A0265 for <wgchairs@ietfa.amsl.com>; Tue, 28 Jan 2014 10:08:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.436
X-Spam-Level: 
X-Spam-Status: No, score=-2.436 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H-Bro44razWS for <wgchairs@ietfa.amsl.com>; Tue, 28 Jan 2014 10:08:29 -0800 (PST)
Received: from txdal11mx03.parsons.com (txdal11mx03.parsons.com [206.219.199.111]) by ietfa.amsl.com (Postfix) with ESMTP id CFF4C1A0230 for <wgchairs@ietf.org>; Tue, 28 Jan 2014 10:08:29 -0800 (PST)
Received: from pps.filterd (txdal11mx03 [127.0.0.1]) by txdal11mx03.parsons.com (8.14.5/8.14.5) with SMTP id s0SI5i3P030360; Tue, 28 Jan 2014 12:08:27 -0600
Received: from m4.sparta.com (m4.sparta.com [157.185.61.2]) by txdal11mx03.parsons.com with ESMTP id 1hpgp40ap0-1 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Tue, 28 Jan 2014 12:08:26 -0600
Received: from Beta5.sparta.com ([10.62.8.21]) by M4.sparta.com (8.14.4/8.14.4) with ESMTP id s0SI8PGD031123; Tue, 28 Jan 2014 12:08:25 -0600
Received: from tanis.huntsville.ads.sparta.com ([10.62.8.118]) by Beta5.sparta.com (8.13.8/8.13.8) with ESMTP id s0SI8N5D000435; Tue, 28 Jan 2014 12:08:25 -0600
Received: from HSV-MB002.huntsville.ads.sparta.com ([fe80::2521:a783:a30c:d057]) by tanis.huntsville.ads.sparta.com ([::1]) with mapi id 14.02.0342.003; Tue, 28 Jan 2014 12:08:23 -0600
From: "Murphy, Sandra" <Sandra.Murphy@parsons.com>
To: Robert Sparks <rjsparks@nostrum.com>, "<wgchairs@ietf.org>" <wgchairs@ietf.org>
Subject: RE: Please double-check your group's archive in the web-based email list archive tool
Thread-Topic: Please double-check your group's archive in the web-based email list archive tool
Thread-Index: AQHPF7v/+VnEVrgEmkW2Nc6uHSp/+JqaYBIg
Date: Tue, 28 Jan 2014 18:08:23 +0000
Message-ID: <24B20D14B2CD29478C8D5D6E9CBB29F678F25186@HSV-MB002.huntsville.ads.sparta.com>
References: <52E03D0E.5060703@nostrum.com>
In-Reply-To: <52E03D0E.5060703@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.185.61.23]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.11.87, 1.0.14, 0.0.0000 definitions=2014-01-28_07:2014-01-28,2014-01-28,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 kscore.is_bulkscore=0 kscore.compositescore=0 circleOfTrustscore=0 compositescore=0.0477310383801818 urlsuspect_oldscore=0.289562094914583 suspectscore=0 recipient_domain_to_sender_totalscore=4066 phishscore=0 bulkscore=0 kscore.is_spamscore=0 recipient_to_sender_totalscore=0 recipient_domain_to_sender_domain_totalscore=12528 rbsscore=0.0477310383801818 spamscore=0 recipient_to_sender_domain_totalscore=0 urlsuspectscore=0.3 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1305240000 definitions=main-1401280105
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 18:08:31 -0000

I've checked sidr, and it looks great!  Thanks!=0A=
=0A=
I checked and the tool goes back as far as the sidr mailing list archives, =
so all is well there.=0A=
=0A=
I tried a couple of searches for recurrent topics and people and the respon=
ses look thorough.=0A=
=0A=
Could you publish the syntax for the search field?  I found that the search=
 terms are generalized beyond what I expected - responsibility and respons*=
 returned the same results (ie messages containing the word response).  Tha=
t threw me at first, but of course, that could be just a one of the typical=
 generalizations I've just never encountered before.   By experimentation, =
the usual regex work - word1 word2 is an OR, word1 AND word2 works, respons=
* worked, and "responsibility" in quotes did not find the word response.=0A=
=0A=
--Sandy=0A=
=0A=
________________________________________=0A=
From: WGChairs [wgchairs-bounces@ietf.org] on behalf of Robert Sparks [rjsp=
arks@nostrum.com]=0A=
Sent: Wednesday, January 22, 2014 4:50 PM=0A=
To: <wgchairs@ietf.org>=0A=
Subject: Please double-check your group's archive in the web-based email li=
st archive tool=0A=
=0A=
Chairs -=0A=
=0A=
If you have not already done so, please look briefly at your lists in=0A=
the new tool and make sure you see what you expect.=0A=
=0A=
You can browse quickly to them with a URL like:=0A=
=0A=
<https://mailarchive.ietf.org/arch/search/?email_list=3Dstir>=0A=
=0A=
Click the date column header twice (the first time will give you a=0A=
most-recent to least-recent view, and the second the reverse),=0A=
or jump straight to a URL like=0A=
<https://mailarchive.ietf.org/arch/search/?email_list=3Dstir&so=3Ddate>=0A=
and check that the archive goes back as far as you expect.=0A=
=0A=
Note that you can pull the division between the message list pane and=0A=
the message preview pane down to allow you to see more of the messages=0A=
in the list at one time.=0A=
=0A=
If you discover something that needs attention, please file a ticket at=0A=
<http://trac.tools.ietf.org/tools/ietfdb/newticket>=0A=
=0A=
RjS=0A=

From worley@shell01.TheWorld.com  Tue Jan 28 10:16:10 2014
Return-Path: <worley@shell01.TheWorld.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB6801A02C7 for <wgchairs@ietfa.amsl.com>; Tue, 28 Jan 2014 10:16:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hEuBUvo3qQ2j for <wgchairs@ietfa.amsl.com>; Tue, 28 Jan 2014 10:16:09 -0800 (PST)
Received: from TheWorld.com (pcls5.std.com [192.74.137.145]) by ietfa.amsl.com (Postfix) with ESMTP id D2E221A0240 for <wgchairs@ietf.org>; Tue, 28 Jan 2014 10:16:07 -0800 (PST)
Received: from shell.TheWorld.com (svani@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id s0SIF9E1021120; Tue, 28 Jan 2014 13:15:11 -0500
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id s0SICWxR3772471; Tue, 28 Jan 2014 13:12:32 -0500 (EST)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id s0SICTXk3778564; Tue, 28 Jan 2014 13:12:29 -0500 (EST)
Date: Tue, 28 Jan 2014 13:12:29 -0500 (EST)
Message-Id: <201401281812.s0SICTXk3778564@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: "Mulligan, Geoff" <geoff.mulligan@nist.gov>
In-reply-to: <126fb3003777478a93ac346b525150af@BLUPR09MB054.namprd09.prod.outlook.com> (geoff.mulligan@nist.gov)
Subject: Re: Third party disclosures and NDAs (Re: Problem with new Note Well )
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E3EBA9.4050005@nist.gov>, <CB2D10B9-DAD4-4C47-B984-A55D136C3126@piuha.net> <126fb3003777478a93ac346b525150af@BLUPR09MB054.namprd09.prod.outlook.com>
Cc: wgchairs@ietf.org, ietf@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 18:16:11 -0000

> From: "Mulligan, Geoff" <geoff.mulligan@nist.gov>
> 
> So because I know of IPR that someone else has and is not disclosing
> and because I cannot legally disclose it - I can't continue to
> participate in the discussion doesn't seem right.  I'm not the
> holder of the IPR that isn't being disclosed, but I'm penalized.

That is the rule (it seems).  It's hard on you, but the IETF seems to
hold to the principle "You can't participate if you know of
undisclosed IPR claims", presumably so the participant can't secretly
steer the solution to include or exclude the IPR.  It's a choice of
who gets inconvenienced, you or the IETF?

Indeed, if the IETF didn't have this rule, a company with undisclosed
IPR could hire consultants, put them under NDA, and have them advocate
at the IETF to include the IPR in standards.

Dale

From ned.freed@mrochek.com  Tue Jan 28 10:50:41 2014
Return-Path: <ned.freed@mrochek.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10B711A041F for <wgchairs@ietfa.amsl.com>; Tue, 28 Jan 2014 10:50:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level: 
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id moWH6DLGW5TN for <wgchairs@ietfa.amsl.com>; Tue, 28 Jan 2014 10:50:39 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id B28321A0263 for <wgchairs@ietf.org>; Tue, 28 Jan 2014 10:50:39 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P3ONM07NOG003QK5@mauve.mrochek.com> for wgchairs@ietf.org; Tue, 28 Jan 2014 10:45:34 -0800 (PST)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P3NP4TEOIO0000AS@mauve.mrochek.com>; Tue, 28 Jan 2014 10:45:26 -0800 (PST)
Message-id: <01P3ONLTEKWA0000AS@mauve.mrochek.com>
Date: Tue, 28 Jan 2014 10:31:36 -0800 (PST)
From: Ned Freed <ned.freed@mrochek.com>
Subject: RE: Third party disclosures and NDAs (Re: Problem with new Note Well )
In-reply-to: "Your message dated Mon, 27 Jan 2014 17:00:55 +0000" <126fb3003777478a93ac346b525150af@BLUPR09MB054.namprd09.prod.outlook.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E3EBA9.4050005@nist.gov> <CB2D10B9-DAD4-4C47-B984-A55D136C3126@piuha.net> <126fb3003777478a93ac346b525150af@BLUPR09MB054.namprd09.prod.outlook.com>
To: "Mulligan, Geoff" <geoff.mulligan@nist.gov>
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 18:50:41 -0000

> So because I know of IPR that someone else has and is not disclosing and
> because I cannot legally disclose it - I can't continue to participate in the
> discussion doesn't seem right.  I'm not the holder of the IPR that isn't being
> disclosed, but I'm penalized.

As I have pointed out several times now, that's incorrect. Section 6.1.3 of
BCP 79 discusses "IPR of Others", and says:

   If a person has information about IPR that may Cover IETF
   Contributions, but the participant is not required to disclose
   because they do not meet the criteria in Section 6.6 (e.g., the IPR
   is owned by some other company), such person is encouraged to notify
   the IETF by sending an email message to ietf-ipr@ietf.org.  Such a
   notice should be sent as soon as reasonably possible after the person
   realizes the connection.

And the referenced section 6.6 says:

   6.6.  When is a Disclosure Required?

   IPR disclosures under Sections 6.1.1. and 6.1.2 are required with
   respect to IPR that is owned directly or indirectly, by the
   individual or his/her employer or sponsor (if any) or that such
   persons otherwise have the right to license or assert.

Encouraged != required.

The wrinkle here - and why I think you're getting some odd answers to your
questions - is that you're not being clear about what role the "someone else"
you're talking about has in the IETF. If the "someone else" is not
participating in the IETF, then there's no problem, other than possibly your
own conscience.

If the "someone else" is participating while meeting the disclosure
requirements, then once again there's no problem since the disclosure has
already been done and there's no need for you to repeat it.

But if they are participating and not disclosing, then there's a big problem,
and in that case it may indeed suck to be you. My advice in such cases would be
to consult an attorney with substantive expertise in IP law as to what your
obligations are.

I do expect such cases to be quite rare though.


				Ned

From adrian@olddog.co.uk  Tue Jan 28 11:03:55 2014
Return-Path: <adrian@olddog.co.uk>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 616FC1A03B7; Tue, 28 Jan 2014 11:03:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.553
X-Spam-Level: 
X-Spam-Status: No, score=-0.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_BL_SPAMCOP_NET=1.347, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3xsr3ya14PDR; Tue, 28 Jan 2014 11:03:54 -0800 (PST)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id 012971A0159; Tue, 28 Jan 2014 11:03:53 -0800 (PST)
Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id s0SJ3og3007547; Tue, 28 Jan 2014 19:03:50 GMT
Received: from 950129200 (13.17.90.92.rev.sfr.net [92.90.17.13]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id s0SJ3l2h007519 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 28 Jan 2014 19:03:48 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Ned Freed'" <ned.freed@mrochek.com>, "'Mulligan, Geoff'" <geoff.mulligan@nist.gov>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E3EBA9.4050005@nist.gov> <CB2D10B9-DAD4-4C47-B984-A55D136C3126@piuha.net> <126fb3003777478a93ac346b525150af@BLUPR09MB054.namprd09.prod.outlook.com> <01P3ONLTEKWA0000AS@mauve.mrochek.com>
In-Reply-To: <01P3ONLTEKWA0000AS@mauve.mrochek.com>
Subject: RE: Third party disclosures and NDAs (Re: Problem with new Note Well )
Date: Tue, 28 Jan 2014 19:03:45 -0000
Message-ID: <047901cf1c5b$ad1c7a00$07556e00$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJJCP7mxrFZ7FpkefVpkZtALbnGxwHO9euCAaaLxDsCUoT0BwN3skPlAiUGdNAB1IqIxAMvTub5AZSy7CABe0denQHbXiYvAj5/8f+Y6g/AoA==
Content-Language: en-gb
X-TM-AS-MML: No
Cc: 'IETF WG Chairs' <wgchairs@ietf.org>, ietf@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 19:03:55 -0000

Ned's reading agrees with mine.

It must suck to be under contract or NDA to someone who is participating in the
IETF and wilfully ignoring the IETF's IPR rules.

The first step may be to check with them direct that they are wilfully ignoring
those rules - it is possible that they have missed something and will thank you
for pointing it out. Both the company concerned and the participating individual
may be glad to hear from you.

Why might they thank you? Because if the company later tries to enforce a
license on their patent and it comes out that they sent people to participate
against the IETF's rules, then it is possible that a court might take a dim view
of their claim. Because if the IETF later discovers that the individual has
participated against the IETF's rules then the IETF might read and apply RFC
6701.

Cheers,
Adrian

PS It is not unheard of for a third party (such as an AD) to discover (through
whatever means) the existence of IPR that might be relevant and file a 3rd-party
notice accordingly.

> -----Original Message-----
> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of Ned Freed
> Sent: 28 January 2014 18:32
> To: Mulligan, Geoff
> Cc: IETF WG Chairs; ietf@ietf.org Mailing List
> Subject: RE: Third party disclosures and NDAs (Re: Problem with new Note Well
)
> 
> > So because I know of IPR that someone else has and is not disclosing and
> > because I cannot legally disclose it - I can't continue to participate in
the
> > discussion doesn't seem right.  I'm not the holder of the IPR that isn't
being
> > disclosed, but I'm penalized.
> 
> As I have pointed out several times now, that's incorrect. 


From dwm@xpasc.com  Tue Jan 28 11:01:38 2014
Return-Path: <dwm@xpasc.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 459651A03B7; Tue, 28 Jan 2014 11:01:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.23
X-Spam-Level: *
X-Spam-Status: No, score=1.23 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, IP_NOT_FRIENDLY=0.334, RDNS_NONE=0.793, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jv8rLtoWK_ZT; Tue, 28 Jan 2014 11:01:37 -0800 (PST)
Received: from c2w3p-2.abacamail.com (unknown [67.231.154.153]) by ietfa.amsl.com (Postfix) with ESMTP id 465671A0159; Tue, 28 Jan 2014 11:01:37 -0800 (PST)
Received: from xpasc.com (h-68-164-244-188.snva.ca.megapath.net [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id 9C8A340876; Tue, 28 Jan 2014 19:01:25 +0000 (UTC)
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by xpasc.com (8.13.8/8.13.8) with ESMTP id s0SJ1ORw005387; Tue, 28 Jan 2014 11:01:24 -0800
Date: Tue, 28 Jan 2014 11:01:24 -0800 (PST)
From: David Morris <dwm@xpasc.com>
To: "Dale R. Worley" <worley@ariadne.com>
Subject: Re: Third party disclosures and NDAs (Re: Problem with new Note Well )
In-Reply-To: <201401281812.s0SICTXk3778564@shell01.TheWorld.com>
Message-ID: <alpine.LRH.2.01.1401281053460.5198@egate.xpasc.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E3EBA9.4050005@nist.gov>, <CB2D10B9-DAD4-4C47-B984-A55D136C3126@piuha.net> <126fb3003777478a93ac346b525150af@BLUPR09MB054.namprd09.prod.outlook.com> <201401281812.s0SICTXk3778564@shell01.TheWorld.com>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailman-Approved-At: Tue, 28 Jan 2014 11:18:46 -0800
Cc: wgchairs@ietf.org, ietf@ietf.org, "Mulligan, Geoff" <geoff.mulligan@nist.gov>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 19:01:38 -0000

On Tue, 28 Jan 2014, Dale R. Worley wrote:

> > From: "Mulligan, Geoff" <geoff.mulligan@nist.gov>
> >
> > So because I know of IPR that someone else has and is not disclosing
> > and because I cannot legally disclose it - I can't continue to
> > participate in the discussion doesn't seem right.  I'm not the
> > holder of the IPR that isn't being disclosed, but I'm penalized.
>
> That is the rule (it seems).  It's hard on you, but the IETF seems to
> hold to the principle "You can't participate if you know of
> undisclosed IPR claims", presumably so the participant can't secretly
> steer the solution to include or exclude the IPR.  It's a choice of
> who gets inconvenienced, you or the IETF?
>
> Indeed, if the IETF didn't have this rule, a company with undisclosed
> IPR could hire consultants, put them under NDA, and have them advocate
> at the IETF to include the IPR in standards.

Um ... if you are currently working for the IPR owner as a consultant,
it isn't 3rd party IPR ... if one is being paid to advocate related
to IPR, it is not the case Geoff outlined.

From ned.freed@mrochek.com  Tue Jan 28 16:02:34 2014
Return-Path: <ned.freed@mrochek.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48EC51A03D1 for <wgchairs@ietfa.amsl.com>; Tue, 28 Jan 2014 16:02:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level: 
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NfhCXE2w-jzD for <wgchairs@ietfa.amsl.com>; Tue, 28 Jan 2014 16:02:33 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 29A4F1A028F for <wgchairs@ietf.org>; Tue, 28 Jan 2014 16:02:33 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P3OYIKUQNK003OBB@mauve.mrochek.com> for wgchairs@ietf.org; Tue, 28 Jan 2014 15:57:23 -0800 (PST)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P3NP4TEOIO0000AS@mauve.mrochek.com>; Tue, 28 Jan 2014 15:57:18 -0800 (PST)
Message-id: <01P3OYII11RI0000AS@mauve.mrochek.com>
Date: Tue, 28 Jan 2014 15:51:17 -0800 (PST)
From: Ned Freed <ned.freed@mrochek.com>
Subject: Re: Third party disclosures and NDAs (Re: Problem with new Note Well )
In-reply-to: "Your message dated Tue, 28 Jan 2014 11:01:24 -0800 (PST)" <alpine.LRH.2.01.1401281053460.5198@egate.xpasc.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E3EBA9.4050005@nist.gov> <CB2D10B9-DAD4-4C47-B984-A55D136C3126@piuha.net> <126fb3003777478a93ac346b525150af@BLUPR09MB054.namprd09.prod.outlook.com> <201401281812.s0SICTXk3778564@shell01.TheWorld.com> <alpine.LRH.2.01.1401281053460.5198@egate.xpasc.com>
To: David Morris <dwm@xpasc.com>
Cc: wgchairs@ietf.org, "Dale R. Worley" <worley@ariadne.com>, ietf@ietf.org, "Mulligan, Geoff" <geoff.mulligan@nist.gov>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 00:02:34 -0000

> On Tue, 28 Jan 2014, Dale R. Worley wrote:

> > > From: "Mulligan, Geoff" <geoff.mulligan@nist.gov>
> > >
> > > So because I know of IPR that someone else has and is not disclosing
> > > and because I cannot legally disclose it - I can't continue to
> > > participate in the discussion doesn't seem right.  I'm not the
> > > holder of the IPR that isn't being disclosed, but I'm penalized.
> >
> > That is the rule (it seems).  It's hard on you, but the IETF seems to
> > hold to the principle "You can't participate if you know of
> > undisclosed IPR claims", presumably so the participant can't secretly
> > steer the solution to include or exclude the IPR.  It's a choice of
> > who gets inconvenienced, you or the IETF?
> >
> > Indeed, if the IETF didn't have this rule, a company with undisclosed
> > IPR could hire consultants, put them under NDA, and have them advocate
> > at the IETF to include the IPR in standards.

> Um ... if you are currently working for the IPR owner as a consultant,
> it isn't 3rd party IPR ... if one is being paid to advocate related
> to IPR, it is not the case Geoff outlined.

Quite right.

There's also the case of where you're consulting for two entities, one of which
has IP they won't let you disclose and the other wants you to do IETF work in
an area touched on by that IP.

But here both the involvement in the IETF as well as this being an IP matter
are really just red herrings. This is a conflict of interest between the two
entities you're consulting for, nothing more and nothing less. And once again
it sucks to be you, but handling such conflicts of interest is decidedly out of
scope.

There are certainly other variations, leading to the general observation that
the more interests you're involved with and/or representing, the more
constrained you're going to be. That's ineluctable.

				Ned

From narten@us.ibm.com  Wed Jan 29 05:12:20 2014
Return-Path: <narten@us.ibm.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C83C1A020C for <wgchairs@ietfa.amsl.com>; Wed, 29 Jan 2014 05:12:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.436
X-Spam-Level: 
X-Spam-Status: No, score=-7.436 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vGPvFmtgUgli for <wgchairs@ietfa.amsl.com>; Wed, 29 Jan 2014 05:12:16 -0800 (PST)
Received: from e32.co.us.ibm.com (e32.co.us.ibm.com [32.97.110.150]) by ietfa.amsl.com (Postfix) with ESMTP id 2E92E1A01FE for <wgchairs@ietf.org>; Wed, 29 Jan 2014 05:12:15 -0800 (PST)
Received: from /spool/local by e32.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <wgchairs@ietf.org> from <narten@us.ibm.com>; Wed, 29 Jan 2014 06:12:12 -0700
Received: from d03dlp01.boulder.ibm.com (9.17.202.177) by e32.co.us.ibm.com (192.168.1.132) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Wed, 29 Jan 2014 06:12:11 -0700
Received: from b03cxnp08028.gho.boulder.ibm.com (b03cxnp08028.gho.boulder.ibm.com [9.17.130.20]) by d03dlp01.boulder.ibm.com (Postfix) with ESMTP id 91CEF1FF003F; Wed, 29 Jan 2014 06:12:10 -0700 (MST)
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by b03cxnp08028.gho.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id s0TDCAI21442112; Wed, 29 Jan 2014 14:12:10 +0100
Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1]) by d03av04.boulder.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id s0TDCAro015570; Wed, 29 Jan 2014 06:12:10 -0700
Received: from cichlid.raleigh.ibm.com (sig-9-65-3-183.mts.ibm.com [9.65.3.183]) by d03av04.boulder.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id s0TDC98C015461 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 29 Jan 2014 06:12:09 -0700
Received: from cichlid.raleigh.ibm.com.us.ibm.com (localhost [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id s0TDC8TK009724; Wed, 29 Jan 2014 08:12:08 -0500
Date: Wed, 29 Jan 2014 08:12:08 -0500
Message-ID: <m3ha8n6ifr.wl%narten@us.ibm.com>
From: Thomas Narten <narten@us.ibm.com>
To: Robert Elz <kre@munnari.OZ.AU>
Subject: Re: IPR disclosure rules in general (Was: various other stuff...)
In-Reply-To: <4111.1390994763@perseus.noi.kre.to>
References: <201401281812.s0SICTXk3778564@shell01.TheWorld.com> <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E3EBA9.4050005@nist.gov>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.8 EasyPG/1.0.0 Emacs/23.1 (x86_64-redhat-linux-gnu) MULE/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-TM-AS-MML: disable
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 14012913-0928-0000-0000-0000060FDAC1
Cc: wgchairs@ietf.org, ietf@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 13:12:20 -0000

At Wed, 29 Jan 2014 18:26:03 +0700, Robert Elz wrote:

> Much easier, for such nefarious company, is simply to hire (as employees, or
> consultants, it makes no difference) people to "represent" the company's
> interest at the IETF, and make sure that those people are unaware of any
> and all IPR claims that the company may possess.

And doing this could even be a violation of our rules (for the IPR
holder at least), depending on the details.

RFC 3668 says:

   l. "Reasonably and personally known": means something an individual
      knows personally or, because of the job the individual holds,
      would reasonably be expected to know.  This wording is used to
      indicate that an organization cannot purposely keep an individual
      in the dark about patents or patent applications just to avoid the
      disclosure requirement.  But this requirement should not be
      interpreted as requiring the IETF Contributor or participant (or
      his or her represented organization, if any) to perform a patent
      search to find applicable IPR.

Thomas


From abdussalambaryun@gmail.com  Wed Jan 29 02:39:21 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D8031A016A; Wed, 29 Jan 2014 02:39:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K0B_4E0YNxDj; Wed, 29 Jan 2014 02:39:19 -0800 (PST)
Received: from mail-pd0-x234.google.com (mail-pd0-x234.google.com [IPv6:2607:f8b0:400e:c02::234]) by ietfa.amsl.com (Postfix) with ESMTP id F3BE71A014C; Wed, 29 Jan 2014 02:39:18 -0800 (PST)
Received: by mail-pd0-f180.google.com with SMTP id x10so1553124pdj.11 for <multiple recipients>; Wed, 29 Jan 2014 02:39:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=H5TvdShZnT8eatK38c0OvSEsHvOwn/Q90eeBwyccKDQ=; b=KANCOR09MVGV1bn2N6s1MLKY0A/kRcQ27yKN7zzU731gs5vUBwmd/5u2TkOggxl/XI lFpZqbYDrI0FzCUXOQFIyR+W7nFm3QyA46AIFfauSG+4oqe5omCL1yu15WJrPtxTEFkP Q/RpFW1nprVb1WVhPZQxLo3XaVIv23iBejUwVAGXNVZFqw8VgpspCE5lWe3qJUT+VoRG bO7kq8jsDZDMzXQ3ctirDMtO3cTGFokIaJyG8LnTgp8LUNPqwiAdsZvSZAAlZdaNOr1e TIcTARjz3tIxW9AYay7zXb+rmL5wvczxDRjc472BRDlPMaV49XGOm/Vrs5ZzGhzp79Z7 HH0w==
MIME-Version: 1.0
X-Received: by 10.68.229.106 with SMTP id sp10mr7157438pbc.23.1390991956271; Wed, 29 Jan 2014 02:39:16 -0800 (PST)
Received: by 10.68.0.104 with HTTP; Wed, 29 Jan 2014 02:39:16 -0800 (PST)
In-Reply-To: <52E69572.7000903@dcrocker.net>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <52E3326E.3080007@gmail.com> <82D163D29DC1D4A7B4797E8F@JcK-HP8200.jck.com> <01P3M48DZNS80000AS@mauve.mrochek.com> <52E5E624.4080003@gmail.com> <19AAADA2-8E3B-456F-B0CE-9A27D2BB5FE9@piuha.net> <52E69572.7000903@dcrocker.net>
Date: Wed, 29 Jan 2014 11:39:16 +0100
Message-ID: <CADnDZ8_X-APwa6BSYF+taXw01XGCH-ffsAnneo+6HsXo4WqbHg@mail.gmail.com>
Subject: Re: Problem with new Note Well
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Mailman-Approved-At: Wed, 29 Jan 2014 06:17:12 -0800
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 10:39:21 -0000

I agree with the suggestions below and that I never liked the note
well wordings. In addition, from Cullen's first message and others, it
seems like most IETF participants are not practicing or understandning
the note well. The reason may be because engineers are not good in
legal issues, so do we have a current legal advisor/position in IETF
organisation, or still IETF has no progress in legal experience, so we
will need to go back to external legal. Why IETF just leaves its
participants alone to do the legal advise but when it comes to their
works it encourages inputs? Does the note well consider all
countries/regions legal policies? Is it practical/agreeable for all
participants any where, or was it tested?

For me I don't agree with the way the note well is forced on all, it
needs more discussions between WGs and their Chairs, but no time for
it or no advisors or group discussion/meeting for legal issues (may be
only IESG decides for us so far which is never practical).

AB

On 1/27/14, Dave Crocker <dhc@dcrocker.net> wrote:
> On 1/27/2014 8:17 AM, Jari Arkko wrote:
>> All - it is clear that you have a concern about the new note well text.
>> The problem has been well articulated;
>
>
> Jari, et al,
>
>
> There are a number of different problems, and only some of them have
> been articulated.  Worse, the problems include the IPR rules themselves,
> not just the Note Well:
>
>       0.  We have had IPR rules and a Note Well for many years and have
> revised both a number of times.  Normally, work we do that has been
> around that long warrants being called "mature", which means that it
> works well and is well understood.  The latest discussion demonstrates
> that that model does not apply to the IETF's IPR handling.  In fact, the
> exchange looks more like the disparities we see early in a working group
> effort, not what normally takes place after many years.
>
>       1. The participants in the discussion are extremely experienced
> with the IETF and with this topic.  Yet they demonstrated a strong
> /lack/ of rough consensus about what the /current/ IPR rules mean.
>
>       2.  The current rules are too complex for use by average
> engineers.  Engineers are not attorneys, nevermind IPR attorneys.  IPR
> is considered by attorneys to be an esoteric and difficult specialty.
> The IETF's IPR rules need to be simple and simply stated, if we expect
> average engineers to understand them.
>
>       3.  The current IPR rules appear to impose an unreasonable demand
> on IETF participants, such as conflicting with employment arrangements.
> (And if the demand is reasonable, then what is noteworthy is that
> someone who has read this latest IETF discussion has developed the
> impression that it isn't.  See point 6.)
>
>       4.  The current Note Well is too complex and apparently erroneous.
>   (And if it is not erroneous, then what is noteworthy is that a serious
> attempt to review the thread has resulted in someone coming to the
> conclusion that the Note Well is erroneous.  See point 6.)
>
>       5.  Expecting an average IETF engineer to consult 4 different
> BCPs, in order to understand what is required of them is not reasonable.
>   Nor is all each document relevant.  So, in effect, the references are
> overly broad, as well as too complicated. (See point 6.)
>
>       6.  Having a range of experienced, diligent IETF participants
> demonstrate substantive disagreement about the meaning of our current
> IPR rules undermines whatever utility the rules might have.  It sets up
> a litigation argument that the participant did not understand the rules,
> citing this thread as demonstrating that others also don't.
>
>
> The remedies we need are not just with the Note Well.  We need to fix
> the IPR rules too.
>
>
>       0.  We need to establish clear and compelling community rough
> consensus about the meaning of our IPR rules and the utility of our Note
> Well.  We are currently /very/ far from being able to do that.
>
>       1.  We need a consensus statement that describes our 'model' of an
> IETF particpant, in terms of what is reasonable for them to know and
> what is reasonable for them to be responsible for and what is reasonable
> for them to do, especially within the real time performance constraints
> of a working group meeting. The premise of that model needs to be
> extreme simplicity and clarity.  Any rules we assert need to be vetted
> against that model.  Our current arrangement requires an average
> engineer to be more knowledgeable and more diligent than is reasonable.
>   (By 'diligent' I'm not referring to intent; I'm referring to classic
> human factors usability limits.)
>
>       2.  One of the distinctions in the latest discussion is between
> having the Note Well attempt to summarize what the IPR rules are, versus
> having it merely declare that we have IPR rules and point the reader to
> them.  For summary instruments, like a Note Well, the latter approach
> makes far more sense.
>
>       3.  We need all of the IPR rules for IETF participation to be in a
> single, simple, clear document that is easily understandable by an
> average engineer. (See point 1.)
>
>
> d/
>
> --
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net
>

From kre@munnari.OZ.AU  Wed Jan 29 03:29:01 2014
Return-Path: <kre@munnari.OZ.AU>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FD0B1A02BA; Wed, 29 Jan 2014 03:29:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.336
X-Spam-Level: 
X-Spam-Status: No, score=0.336 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HOST_EQ_AU=0.327, HOST_MISMATCH_AU=2.444, RP_MATCHES_RCVD=-0.535] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZhMviMin6Ojx; Wed, 29 Jan 2014 03:29:00 -0800 (PST)
Received: from munnari.OZ.AU (munnari.OZ.AU [202.29.151.3]) by ietfa.amsl.com (Postfix) with ESMTP id 7E6AF1A014C; Wed, 29 Jan 2014 03:28:59 -0800 (PST)
Received: from perseus.noi.kre.to (localhost [IPv6:::1]) by munnari.OZ.AU with ESMTP id s0TBQigl009171; Wed, 29 Jan 2014 18:27:05 +0700 (ICT)
Received: from perseus.noi.kre.to (localhost [127.0.0.1]) by perseus.noi.kre.to (8.14.7/8.14.2) with ESMTP id s0TBQ3Ue003385; Wed, 29 Jan 2014 18:26:08 +0700 (ICT)
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.5
From: Robert Elz <kre@munnari.OZ.AU>
To: ietf@ietf.org
Subject: IPR disclosure rules in general (Was: various other stuff...)
In-Reply-To: <201401281812.s0SICTXk3778564@shell01.TheWorld.com>
References: <201401281812.s0SICTXk3778564@shell01.TheWorld.com> <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E3EBA9.4050005@nist.gov>, <CB2D10B9-DAD4-4C47-B984-A55D136C3126@piuha.net> <126fb3003777478a93ac346b525150af@BLUPR09MB054.namprd09.prod.outlook.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 29 Jan 2014 18:26:03 +0700
Message-ID: <4111.1390994763@perseus.noi.kre.to>
X-Mailman-Approved-At: Wed, 29 Jan 2014 06:17:11 -0800
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 11:29:01 -0000

    Date:        Tue, 28 Jan 2014 13:12:29 -0500 (EST)
    From:        worley@ariadne.com (Dale R. Worley)
    Message-ID:  <201401281812.s0SICTXk3778564@shell01.TheWorld.com>

  | Indeed, if the IETF didn't have this rule, a company with undisclosed
  | IPR could hire consultants, put them under NDA, and have them advocate
  | at the IETF to include the IPR in standards.

Much easier, for such nefarious company, is simply to hire (as employees, or
consultants, it makes no difference) people to "represent" the company's
interest at the IETF, and make sure that those people are unaware of any
and all IPR claims that the company may possess.

In that case, the person attending the IETF cannot possibly disclose the
IPR, as they're unaware of it, the company can't be expected to disclose
anything - companies don't attend the IETF (except as sponsors perhaps, and
I am fairly sure that no-one asks the sponsors to reveal all their IPR before
we take their money) the people all attend as individuals.

We may not like this kind of behaviour, but other than completely changing
the way the IETF is designed to operate (to actually have company's explicitly
become members, and enter into membership agreements, with only representatives
of member companies permitted to participate) which I don't think anyone wants,
there really is nothing that can be done about it.

Now this by no means guarantees that the courts won't take a dim view of
this kind of behaviour, if an attempt is later made to enforce the IPR claim,
but it won't be because of any breach of IETF rules - there hasn't been any
in this scenario.

All of these problems are brought about by yet another instance of the
IETF attempting to fix something that is simply way outside our competence
or ability to fix.  It isn't surprising - after all, the IETF is made up
(mostly) of engineers, and when an engineer sees something broken, the
natural inclination is to attempt to fix it.  But sometimes the underlying
problem is something that simply cannot be fixed by any amount of engineering.
Hidden IPR is one of those, the problem is in people's attitudes - how
willing they are to put their own interests ahead of the general community
interest.   You simply cannot engineer a fix to this, it is a social issue.

Everything beyond simply encouraging people to disclose any IPR that they're
aware of, which they are able to disclose - or if unable, to attempt to
encourage those who are able to disclose it, is beyond what is rational for
the IETF to attempt to do, and what's more, the "rules" that people spend
so much time debating (people waste so much time debating) are essentially
useless, as they have no enforcement mechanism.  What exactly is the IETF
supposed to do, if it is revealed, some time later, that some IPR was not
disclosed by a participant in some discussions that they could have
disclosed?   As I understand it, there is simply some hope that some court
will use that to invalidate the IPR claim - but nothing I've seen suggests
that the "rule" is actually necessary for that, and even if it is, as above,
it is trivial to work around.

These days the IETF is spending far too much time on issues that have nothing
to do with actually improving the protocols in use on the internet, and
should go back to doing what it can do, and simply allow the rest to be 
handled in the places designed to handle such things.   Stepping back, and
saying "I cannot fix that problem" seems like being defeated, but it isn't,
it is just accepting reality.  That is good engineering.

kre


From synp71@live.com  Wed Jan 29 04:43:06 2014
Return-Path: <synp71@live.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A9C21A03F8; Wed, 29 Jan 2014 04:43:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level: 
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, MSGID_FROM_MTA_HEADER=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wH_2-TAKIB8C; Wed, 29 Jan 2014 04:43:05 -0800 (PST)
Received: from blu0-omc2-s34.blu0.hotmail.com (blu0-omc2-s34.blu0.hotmail.com [65.55.111.109]) by ietfa.amsl.com (Postfix) with ESMTP id EEC051A0375; Wed, 29 Jan 2014 04:43:04 -0800 (PST)
Received: from BLU0-SMTP152 ([65.55.111.72]) by blu0-omc2-s34.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 29 Jan 2014 04:43:02 -0800
X-TMN: [cqoIPkFlIovQgaYouUsOebbZ3/tFCxLr]
X-Originating-Email: [synp71@live.com]
Message-ID: <BLU0-SMTP15291D6479F17C5A697960DB1AC0@phx.gbl>
Received: from ynir-MBA.local ([194.29.32.131]) by BLU0-SMTP152.phx.gbl over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 29 Jan 2014 04:43:00 -0800
Date: Wed, 29 Jan 2014 14:42:55 +0200
From: Yoav Nir <synp71@live.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Robert Elz <kre@munnari.OZ.AU>, ietf@ietf.org
Subject: Re: IPR disclosure rules in general (Was: various other stuff...)
References: <201401281812.s0SICTXk3778564@shell01.TheWorld.com> <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E3EBA9.4050005@nist.gov>, <CB2D10B9-DAD4-4C47-B984-A55D136C3126@piuha.net> <126fb3003777478a93ac346b525150af@BLUPR09MB054.namprd09.prod.outlook.com> <4111.1390994763@perseus.noi.kre.to>
In-Reply-To: <4111.1390994763@perseus.noi.kre.to>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms040406050608070901010903"
X-OriginalArrivalTime: 29 Jan 2014 12:43:00.0323 (UTC) FILETIME=[A4B6AB30:01CF1CEF]
X-Mailman-Approved-At: Wed, 29 Jan 2014 06:17:11 -0800
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 12:43:06 -0000

--------------ms040406050608070901010903
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

On 29/1/14 1:26 PM, Robert Elz wrote:
>      Date:        Tue, 28 Jan 2014 13:12:29 -0500 (EST)
>      From:        worley@ariadne.com (Dale R. Worley)
>      Message-ID:  <201401281812.s0SICTXk3778564@shell01.TheWorld.com>
>
>    | Indeed, if the IETF didn't have this rule, a company with undisclo=
sed
>    | IPR could hire consultants, put them under NDA, and have them advo=
cate
>    | at the IETF to include the IPR in standards.
>
> Much easier, for such nefarious company, is simply to hire (as employee=
s, or
> consultants, it makes no difference) people to "represent" the company'=
s
> interest at the IETF, and make sure that those people are unaware of an=
y
> and all IPR claims that the company may possess.

That's not so nefarious. If those people are unaware of the IPR claims,=20
they're unable to steer the working group towards infringing technology. =

I suspect that some companies are hiring people for their "IETF=20
experience" and intentionally keeping them away from the R&D side of the =

company.

We may not like the idea of a professional IETF-er any more than people=20
used to like the idea of a professional athlete. For years professional=20
were banned from the Olympics. But I don't think such people or their=20
participation are a problem.


--------------ms040406050608070901010903
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIO4zCC
BJ0wggOFoAMCAQICEDQ96SusJzT/j8s0lPvMcFQwDQYJKoZIhvcNAQEFBQAwbzELMAkGA1UE
BhMCU0UxFDASBgNVBAoTC0FkZFRydXN0IEFCMSYwJAYDVQQLEx1BZGRUcnVzdCBFeHRlcm5h
bCBUVFAgTmV0d29yazEiMCAGA1UEAxMZQWRkVHJ1c3QgRXh0ZXJuYWwgQ0EgUm9vdDAeFw0w
NTA2MDcwODA5MTBaFw0yMDA1MzAxMDQ4MzhaMIGuMQswCQYDVQQGEwJVUzELMAkGA1UECBMC
VVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUgVVNFUlRSVVNUIE5l
dHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQGA1UEAxMtVVRO
LVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsMIIBIjANBgkqhkiG
9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsjmFpPJ9q0E7YkY3rs3BYHW8OWX5ShpHornMSMxqmNVN
NRm5pELlzkniii8efNIxB8dOtINknS4p1aJkxIW9hVE1eaROaJB7HHqkkqgX8pgV8pPMyaQy
lbsMTzC9mKALi+VuG6JG+ni8om+rWV6lL8/K2m2qL+usobNqqrcuZzWLeeEeaYji5kbNoKXq
vgvOdjp6Dpvq/NonWz1zHyLmSGHGTPNpsaguG7bUMSAsvIKKjqQOpdeJQ/wWWq8dcdcRWdq6
hw2v+vPhwvCkxWeM1tZUOt4KpLoDd7NlyP0e03RiqhjKaJMeoYV+9Udly/hNVyh00jT/MLbu
9mIwFIws6wIDAQABo4H0MIHxMB8GA1UdIwQYMBaAFK29mHo0tCb3+sQmVO8DveAky1QaMB0G
A1UdDgQWBBSJgmd9xJ0mcABLtFBIfN49rgRufTAOBgNVHQ8BAf8EBAMCAQYwDwYDVR0TAQH/
BAUwAwEB/zARBgNVHSAECjAIMAYGBFUdIAAwRAYDVR0fBD0wOzA5oDegNYYzaHR0cDovL2Ny
bC51c2VydHJ1c3QuY29tL0FkZFRydXN0RXh0ZXJuYWxDQVJvb3QuY3JsMDUGCCsGAQUFBwEB
BCkwJzAlBggrBgEFBQcwAYYZaHR0cDovL29jc3AudXNlcnRydXN0LmNvbTANBgkqhkiG9w0B
AQUFAAOCAQEAAbyc42MosPMxAcLfe91ioAGdIzEPnJJzU1HqH0z61p/Eyi9nfngzD3QWuZGH
kfWKJvpkcADYHvkLBGJQh5OB1Nr1I9s0u4VWtHA0bniDNx6FHMURFZJfhxe9rGr98cLRzIlf
sXzwPlHyNfN87GCYazor4O/fs32G67Ub9VvsonyYE9cAULnRLXPeA3h04QWFMV7LmrmdlMa5
lDd1ctxE+2fo8PolHlKn2iXpR+CgxzygTrEKNvt3SJ/vl4r7tP7jlBSog7xcLT/SYHFg7sJx
ggzpiDbj2iC0o6BsqpZLuICOdcpJB/Y7FLrf3AXZn9vgsuZNoHgm5+ctbn9fxh6IFTCCBRow
ggQCoAMCAQICEG0Z6qcZT2ozIuYiMnqqcd4wDQYJKoZIhvcNAQEFBQAwga4xCzAJBgNVBAYT
AlVTMQswCQYDVQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRo
ZSBVU0VSVFJVU1QgTmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29t
MTYwNAYDVQQDEy1VVE4tVVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1h
aWwwHhcNMTEwNDI4MDAwMDAwWhcNMjAwNTMwMTA0ODM4WjCBkzELMAkGA1UEBhMCR0IxGzAZ
BgNVBAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEaMBgGA1UEChMR
Q09NT0RPIENBIExpbWl0ZWQxOTA3BgNVBAMTMENPTU9ETyBDbGllbnQgQXV0aGVudGljYXRp
b24gYW5kIFNlY3VyZSBFbWFpbCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEB
AJKEhFtLV5jUXi+LpOFAyKNTWF9mZfEyTvefMn1V0HhMVbdClOD5J3EHxcZppLkyxPFAGpDM
J1Zifxe1cWmu5SAb5MtjXmDKokH2auGj/7jfH0htZUOMKi4rYzh337EXrMLaggLW1DJq1Gdv
IBOPXDX65VSAr9hxCh03CgJQU2yVHakQFLSZlVkSMf8JotJM3FLb3uJAAVtIaN3FSrTg7SQf
Oq9xXwfjrL8UO7AlcWg99A/WF1hGFYE8aIuLgw9teiFX5jSw2zJ+40rhpVJyZCaRTqWSD//g
sWD9Gm9oUZljjRqLpcxCm5t9ImPTqaD8zp6Q30QZ9FxbNboW86eb/8ECAwEAAaOCAUswggFH
MB8GA1UdIwQYMBaAFImCZ33EnSZwAEu0UEh83j2uBG59MB0GA1UdDgQWBBR6E04AdFvGeGNk
J8Ev4qBbvHnFezAOBgNVHQ8BAf8EBAMCAQYwEgYDVR0TAQH/BAgwBgEB/wIBADARBgNVHSAE
CjAIMAYGBFUdIAAwWAYDVR0fBFEwTzBNoEugSYZHaHR0cDovL2NybC51c2VydHJ1c3QuY29t
L1VUTi1VU0VSRmlyc3QtQ2xpZW50QXV0aGVudGljYXRpb25hbmRFbWFpbC5jcmwwdAYIKwYB
BQUHAQEEaDBmMD0GCCsGAQUFBzAChjFodHRwOi8vY3J0LnVzZXJ0cnVzdC5jb20vVVROQWRk
VHJ1c3RDbGllbnRfQ0EuY3J0MCUGCCsGAQUFBzABhhlodHRwOi8vb2NzcC51c2VydHJ1c3Qu
Y29tMA0GCSqGSIb3DQEBBQUAA4IBAQCF1r54V1VtM39EUv5C1QaoAQOAivsNsv1Kv/avQUn1
G1rF0q0bc24+6SZ85kyYwTAo38v7QjyhJT4KddbQPTmGZtGhm7VNm2+vKGwdr+XqdFqo2rHA
8XV6L566k3nK/uKRHlZ0sviN0+BDchvtj/1gOSBH+4uvOmVIPJg9pSW/ve9g4EnlFsjrP0OD
8ODuDcHTzTNfm9C9YGqzO/761Mk6PB/tm/+bSTO+Qik5g+4zaS6CnUVNqGnagBsePdIaXXxH
maWbCG0SmYbWXVcHG6cwvktJRLiQfsrReTjrtDP6oDpdJlieYVUYtCHVmdXgQ0BCML7qpeeU
0rD+83X5f27nMIIFIDCCBAigAwIBAgIRAJLy3rLPGBD9qh6TW+ZG9DowDQYJKoZIhvcNAQEF
BQAwgZMxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNV
BAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBDQSBMaW1pdGVkMTkwNwYDVQQDEzBDT01P
RE8gQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0EwHhcNMTMxMTE3
MDAwMDAwWhcNMTQxMTE3MjM1OTU5WjAgMR4wHAYJKoZIhvcNAQkBFg9zeW5wNzFAbGl2ZS5j
b20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCow0TXP0M95fIMY0Fsd3xpZj55
m1mkkKhUWLjVtQcd57MyVmBZNQkAmxp9PrzqdHw5eIIBn1EI9foIoynEnUSZzv6pIEXAqdYu
xBH0AdvjoPCzWb9uYrqBtbmxnLh9k9ox1pVJG4hit6WEpK+LZ7uvLj5GUWMdmzghC/+fVEZS
W8U62xlhd8Hq8ded9bfqjM4psDgqUubjcCkMIUnkD9yuXhzfzwF0wwtD66vXrUe8T4/m6XHO
iIqvvVMjzYyKrdLE7zuPyDcDjkxLCCdi2j4c44anq8Pj/yEh5JGU0XSKSfwm2m0UDHj7P/6u
B74JwiAyMtqWzdQBHVOphHKDI0ZTAgMBAAGjggHfMIIB2zAfBgNVHSMEGDAWgBR6E04AdFvG
eGNkJ8Ev4qBbvHnFezAdBgNVHQ4EFgQUq+f5Y55gheJJpWtJDEPf6j2uzhQwDgYDVR0PAQH/
BAQDAgWgMAwGA1UdEwEB/wQCMAAwIAYDVR0lBBkwFwYIKwYBBQUHAwQGCysGAQQBsjEBAwUC
MBEGCWCGSAGG+EIBAQQEAwIFIDBGBgNVHSAEPzA9MDsGDCsGAQQBsjEBAgEBATArMCkGCCsG
AQUFBwIBFh1odHRwczovL3NlY3VyZS5jb21vZG8ubmV0L0NQUzBXBgNVHR8EUDBOMEygSqBI
hkZodHRwOi8vY3JsLmNvbW9kb2NhLmNvbS9DT01PRE9DbGllbnRBdXRoZW50aWNhdGlvbmFu
ZFNlY3VyZUVtYWlsQ0EuY3JsMIGIBggrBgEFBQcBAQR8MHowUgYIKwYBBQUHMAKGRmh0dHA6
Ly9jcnQuY29tb2RvY2EuY29tL0NPTU9ET0NsaWVudEF1dGhlbnRpY2F0aW9uYW5kU2VjdXJl
RW1haWxDQS5jcnQwJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3NwLmNvbW9kb2NhLmNvbTAaBgNV
HREEEzARgQ9zeW5wNzFAbGl2ZS5jb20wDQYJKoZIhvcNAQEFBQADggEBACRvTZSZMhI7HrJr
jTpnm5FZXyYwJYVhhc643/94hv8pxAQzIY6vH+BlVwmG4Z0Dt6vWYwaUUYdGmvlH0bti8aql
JPe4fUgTxbDlTldhOYfISl3ky9+4CEPg4QvX6tOGIusOrvaIszGUIdvKHzvYM4ZapdTxyFCt
oe1RXq/17ifvIklgmuh+QcB1xNBmE3lBNj+Vy8xLvsAQlqf9ZAIcBNL2yQGCaBcr6XoR24/D
oCNCTAOCR/J2nN/okuGsEF+kvxP/BCPBnDph9coFLNOEwR4ZataT6H4vq0fwGxm5SROTDYis
SUTKc+YYKY2RllEwOxX1NZUSmISuGKrGhr2aCaUxggQcMIIEGAIBATCBqTCBkzELMAkGA1UE
BhMCR0IxGzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEa
MBgGA1UEChMRQ09NT0RPIENBIExpbWl0ZWQxOTA3BgNVBAMTMENPTU9ETyBDbGllbnQgQXV0
aGVudGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQQIRAJLy3rLPGBD9qh6TW+ZG9DowCQYF
Kw4DAhoFAKCCAkcwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcN
MTQwMTI5MTI0MjU1WjAjBgkqhkiG9w0BCQQxFgQUxvQU4CBXXYr92WWw9Ehz00OzMdYwbAYJ
KoZIhvcNAQkPMV8wXTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4G
CCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB
ugYJKwYBBAGCNxAEMYGsMIGpMIGTMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBN
YW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRl
ZDE5MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgU2VjdXJlIEVt
YWlsIENBAhEAkvLess8YEP2qHpNb5kb0OjCBvAYLKoZIhvcNAQkQAgsxgayggakwgZMxCzAJ
BgNVBAYTAkdCMRswGQYDVQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZv
cmQxGjAYBgNVBAoTEUNPTU9ETyBDQSBMaW1pdGVkMTkwNwYDVQQDEzBDT01PRE8gQ2xpZW50
IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0ECEQCS8t6yzxgQ/aoek1vmRvQ6
MA0GCSqGSIb3DQEBAQUABIIBACMUeQXYelaKtK+KN1v9fhA229xINtwSiyi8ozgyrI4/Ip5x
p3zNLW1uigyzhicp1EmpN+mIVWLHiJoJOMSC6SA9Vl02kmzPu/h9gIj1QuaQKsTjjam8CFGg
fmJmOCumI99a6nrihpX5iV9okWMunBoIE4T65wKJJocs8SbHCiokmTfOQevLwHsJG6uBIzki
3Ccis7LcMNrvqQZtLOXeiZLwpXsit7VnBNlD3/1QPanFXRPoLpDjaTEJaHvOcTlekE5IwNqn
Lm9NXRh74REF3L0+EVsBKOPXM06SsdNLt0hgdzZ1IwbWoT995IIwg1XeL0caaumeJtAVxUyX
oehGo1sAAAAAAAA=
--------------ms040406050608070901010903--

From kre@munnari.OZ.AU  Wed Jan 29 06:05:38 2014
Return-Path: <kre@munnari.OZ.AU>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4C6A1A0375; Wed, 29 Jan 2014 06:05:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.336
X-Spam-Level: 
X-Spam-Status: No, score=0.336 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HOST_EQ_AU=0.327, HOST_MISMATCH_AU=2.444, RP_MATCHES_RCVD=-0.535] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xyDxOXyV8srD; Wed, 29 Jan 2014 06:05:37 -0800 (PST)
Received: from munnari.OZ.AU (munnari.OZ.AU [202.29.151.3]) by ietfa.amsl.com (Postfix) with ESMTP id A74211A0371; Wed, 29 Jan 2014 06:05:36 -0800 (PST)
Received: from perseus.noi.kre.to (localhost [IPv6:::1]) by munnari.OZ.AU with ESMTP id s0TE2PeN010020; Wed, 29 Jan 2014 21:02:46 +0700 (ICT)
Received: from perseus.noi.kre.to (localhost [127.0.0.1]) by perseus.noi.kre.to (8.14.7/8.14.2) with ESMTP id s0TE1EBL005738; Wed, 29 Jan 2014 21:01:29 +0700 (ICT)
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.5
From: Robert Elz <kre@munnari.OZ.AU>
To: Yoav Nir <synp71@live.com>, Thomas Narten <narten@us.ibm.com>
Subject: Re: IPR disclosure rules in general (Was: various other stuff...)
In-Reply-To: <BLU0-SMTP15291D6479F17C5A697960DB1AC0@phx.gbl>
References: <BLU0-SMTP15291D6479F17C5A697960DB1AC0@phx.gbl> <201401281812.s0SICTXk3778564@shell01.TheWorld.com> <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E3EBA9.4050005@nist.gov>, <CB2D10B9-DAD4-4C47-B984-A55D136C3126@piuha.net> <126fb3003777478a93ac346b525150af@BLUPR09MB054.namprd09.prod.outlook.com> <4111.1390994763@perseus.noi.kre.to>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 29 Jan 2014 21:01:14 +0700
Message-ID: <8982.1391004074@perseus.noi.kre.to>
X-Mailman-Approved-At: Wed, 29 Jan 2014 06:17:11 -0800
Cc: wgchairs@ietf.org, ietf@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 14:05:38 -0000

    Date:        Wed, 29 Jan 2014 14:42:55 +0200
    From:        Yoav Nir <synp71@live.com>
    Message-ID:  <BLU0-SMTP15291D6479F17C5A697960DB1AC0@phx.gbl>

  | If those people are unaware of the IPR claims,
  | they're unable to steer the working group towards infringing technology.

No, the people are aware of all the technology, they just have no idea
there's any patents (or other IPR) involved.  They can easily (and genuinely)
advocate some great new technology that would solve a problem, without
having the slightest idea that their company is planning on later asserting
its IPR and claiming royalties.

  | I suspect that some companies are hiring people for their "IETF
  | experience" and intentionally keeping them away from the R&D side of the
  | company.

Yes, I think you're right, this has been happening for some time now.

  | We may not like the idea of a professional IETF-er any more than people
  | used to like the idea of a professional athlete.

I don't think that's a good analogy.   There's nothing wrong in
principle with organisations having people whose job it is to interact
with all the appropriate SDOs (after all, that allows the actual R&D
people to do their jobs instead of constantly being side tracked by
nonsense like IETF IPR rules...) but for the IETF, too much of this is
not a good thing.  The problem is that if the actual developers of
whatever is relevant are in a meeting when the technology is being discussed,
they (hopefully) know what are the real issues and problems, and what are
irrelevant side issues that don't really matter.  The professional SDO
attendee tends not to be closely involved enough with the development
and reasons for it, and so will more often simply advocate their company's
way of doing things, regardless whether it is on a point where it really
matters, or one where it really doesn't.


In another reply, Thomas Narten <narten@us.ibm.com> said:

  | And doing this could even be a violation of our rules (for the IPR holder at
  | least), depending on the details.

Violation of the rules by whom?  The excerpt you quoted clearly says that
people are not required to go do patent searches to find out whether IPR
might exists, so clearly the attendees (in the situation I postulated)
are not violating any rules.

And the company has (according to IETF theory anyway) no relationship with
the IETF at all - IETF rules and procedures cannot possibly be relevant to
random outside organisations.  Note that the company does not accept the
IETF rules, or tick the box on the registration form, or however it is
done these days, and the company does not join any mailing lists etc - and
certainly is not participating in any discussions, just their unknowing
employees.

Or consider a slightly different scenario - consider a company with some
new (and just recently subject of a patent application) technology that
they'd (for obvious reasons) like to become widely used.  The company then
hires a consultant (or two, or three) to evaluate possible future uses of
the technology.  The consultants are told nothing about the patent application
(which after all, has no bearing on what they've been asked to consult about).

One (or perhaps more) of the consultants asks the company "Have you considered
submitting this to the IETF, it could solve a problem they're having ..."
to which the company replies "We know nothing about that, but we have no
objections if you think it would be useful for them".

The consultant (on his own dime) then attends an IETF meeting, and submits
this new technology to the IETF.

What rules do you think have been broken there?  What rules could possibly 
exist that would make a difference?

Perhaps you might believe that the consultant should have explicitly asked
the company if there were any patents or patent applications on this
technology?  Perhaps he/she should have, and didn't.  Or perhaps that
question was asked, and the company said no.   That might have even been
truthful at the time - it might have been that very question that inspired
the company to file its patent application.

This is all very messy, and once again, dealing with all these issues is
way beyond what network engineers should even be attempting.

Simply make it clear that knowing about IPR, and licensing terms, allows
the IETF to build better protocols that are more useful to the network as
a whole, and so disclosing IPR to the IETF is a good thing to do.  Those
companies (I suspect the majority, especially of the bigger ones) will
(and have in the past) comply, and file the relevant disclosure.  The ones
that refuse are not likely to be swayed in any way by any IETF rules, and
particularly not ones that lack even a hint of any enforcement mechanism.

kre

ps: this will be my final message on this topic.  I don't want to encourage,
or contribute to, even more IETF time wasting on non-engineering issues.


From keith.drage@alcatel-lucent.com  Wed Jan 29 07:31:19 2014
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B8E91A0218; Wed, 29 Jan 2014 07:31:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id drKlSdsOaFw9; Wed, 29 Jan 2014 07:31:16 -0800 (PST)
Received: from hoemail1.alcatel.com (hoemail1.alcatel.com [192.160.6.148]) by ietfa.amsl.com (Postfix) with ESMTP id 346CF1A008E; Wed, 29 Jan 2014 07:31:15 -0800 (PST)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by hoemail1.alcatel.com (8.13.8/IER-o) with ESMTP id s0TFV9v9026667 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 29 Jan 2014 09:31:11 -0600 (CST)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id s0TFV8QC005015 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 29 Jan 2014 16:31:09 +0100
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.26]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.02.0247.003; Wed, 29 Jan 2014 16:31:09 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>, ietf <ietf@ietf.org>
Subject: RE: Problem with new Note Well
Thread-Topic: Problem with new Note Well
Thread-Index: AQHPHPzckxdedUpOzkK4h72KmTW/JZqbxCPw
Date: Wed, 29 Jan 2014 15:31:08 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B1250B2@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <52E3326E.3080007@gmail.com> <82D163D29DC1D4A7B4797E8F@JcK-HP8200.jck.com> <01P3M48DZNS80000AS@mauve.mrochek.com> <52E5E624.4080003@gmail.com> <19AAADA2-8E3B-456F-B0CE-9A27D2BB5FE9@piuha.net> <52E69572.7000903@dcrocker.net> <CADnDZ8_X-APwa6BSYF+taXw01XGCH-ffsAnneo+6HsXo4WqbHg@mail.gmail.com>
In-Reply-To: <CADnDZ8_X-APwa6BSYF+taXw01XGCH-ffsAnneo+6HsXo4WqbHg@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.38]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 15:31:19 -0000

In regard to "all countries / regions" the disclosure requirements are not =
that different from the disclosure requirements of every SDO, all with memb=
erships from just about every country in the world.=20

I would have expected that if there was a legal problem with disclosure, th=
en it would have been spotted by now, given the level of test it has been g=
iven by all those SDOs.

The difference with IETF is with representation by individual. For the SDOs=
 the membership is by company or equivalent, and they sign up (on behalf of=
 all their employees or consultants) to the disclosure requirements when th=
ey join the SDO.

But in general the disclosure requires as defined in RFC 3979 are not that =
complex and it is entirely reasonable that all participants should be requi=
red to read it. I do not believe it requires a trained legal expert to unde=
rstand it.

And as for being left alone, if you really are an individual (alone) with "=
contributor's IPR" or "participants IPR" then you are paying any awful lot =
of legal fees to keep that IPR; why not spend some of it on your responsibi=
lities to IETF.

As for consultants, if you are paid to participate in the IETF, then you sh=
ould ensure your contract allows you to meet the requirements of the IETF. =
It might help if RFC 3979 made this point, but it should be self evident an=
yway.

Regards

Keith=20

> -----Original Message-----
> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf=20
> Of Abdussalam Baryun
> Sent: 29 January 2014 10:39
> To: ietf
> Cc: Cullen Jennings (fluffy); IETF WG Chairs
> Subject: Re: Problem with new Note Well
>=20
> I agree with the suggestions below and that I never liked the=20
> note well wordings. In addition, from Cullen's first message=20
> and others, it seems like most IETF participants are not=20
> practicing or understandning the note well. The reason may be=20
> because engineers are not good in legal issues, so do we have=20
> a current legal advisor/position in IETF organisation, or=20
> still IETF has no progress in legal experience, so we will=20
> need to go back to external legal. Why IETF just leaves its=20
> participants alone to do the legal advise but when it comes=20
> to their works it encourages inputs? Does the note well=20
> consider all countries/regions legal policies? Is it=20
> practical/agreeable for all participants any where, or was it tested?
>=20
> For me I don't agree with the way the note well is forced on=20
> all, it needs more discussions between WGs and their Chairs,=20
> but no time for it or no advisors or group discussion/meeting=20
> for legal issues (may be only IESG decides for us so far=20
> which is never practical).
>=20
> AB
>=20
> On 1/27/14, Dave Crocker <dhc@dcrocker.net> wrote:
> > On 1/27/2014 8:17 AM, Jari Arkko wrote:
> >> All - it is clear that you have a concern about the new=20
> note well text.
> >> The problem has been well articulated;
> >
> >
> > Jari, et al,
> >
> >
> > There are a number of different problems, and only some of=20
> them have=20
> > been articulated.  Worse, the problems include the IPR rules=20
> > themselves, not just the Note Well:
> >
> >       0.  We have had IPR rules and a Note Well for many years and=20
> > have revised both a number of times.  Normally, work we do that has=20
> > been around that long warrants being called "mature", which=20
> means that=20
> > it works well and is well understood.  The latest discussion=20
> > demonstrates that that model does not apply to the IETF's IPR=20
> > handling.  In fact, the exchange looks more like the disparities we=20
> > see early in a working group effort, not what normally=20
> takes place after many years.
> >
> >       1. The participants in the discussion are extremely=20
> experienced=20
> > with the IETF and with this topic.  Yet they demonstrated a strong=20
> > /lack/ of rough consensus about what the /current/ IPR rules mean.
> >
> >       2.  The current rules are too complex for use by average=20
> > engineers.  Engineers are not attorneys, nevermind IPR=20
> attorneys.  IPR=20
> > is considered by attorneys to be an esoteric and difficult=20
> specialty.
> > The IETF's IPR rules need to be simple and simply stated,=20
> if we expect=20
> > average engineers to understand them.
> >
> >       3.  The current IPR rules appear to impose an unreasonable=20
> > demand on IETF participants, such as conflicting with=20
> employment arrangements.
> > (And if the demand is reasonable, then what is noteworthy is that=20
> > someone who has read this latest IETF discussion has developed the=20
> > impression that it isn't.  See point 6.)
> >
> >       4.  The current Note Well is too complex and=20
> apparently erroneous.
> >   (And if it is not erroneous, then what is noteworthy is that a=20
> > serious attempt to review the thread has resulted in=20
> someone coming to=20
> > the conclusion that the Note Well is erroneous.  See point 6.)
> >
> >       5.  Expecting an average IETF engineer to consult 4 different=20
> > BCPs, in order to understand what is required of them is=20
> not reasonable.
> >   Nor is all each document relevant.  So, in effect, the references=20
> > are overly broad, as well as too complicated. (See point 6.)
> >
> >       6.  Having a range of experienced, diligent IETF participants=20
> > demonstrate substantive disagreement about the meaning of=20
> our current=20
> > IPR rules undermines whatever utility the rules might have.=20
>  It sets=20
> > up a litigation argument that the participant did not=20
> understand the=20
> > rules, citing this thread as demonstrating that others also don't.
> >
> >
> > The remedies we need are not just with the Note Well.  We=20
> need to fix=20
> > the IPR rules too.
> >
> >
> >       0.  We need to establish clear and compelling community rough=20
> > consensus about the meaning of our IPR rules and the utility of our=20
> > Note Well.  We are currently /very/ far from being able to do that.
> >
> >       1.  We need a consensus statement that describes our=20
> 'model' of=20
> > an IETF particpant, in terms of what is reasonable for them to know=20
> > and what is reasonable for them to be responsible for and what is=20
> > reasonable for them to do, especially within the real time=20
> performance=20
> > constraints of a working group meeting. The premise of that model=20
> > needs to be extreme simplicity and clarity.  Any rules we=20
> assert need=20
> > to be vetted against that model.  Our current arrangement=20
> requires an=20
> > average engineer to be more knowledgeable and more diligent=20
> than is reasonable.
> >   (By 'diligent' I'm not referring to intent; I'm referring=20
> to classic=20
> > human factors usability limits.)
> >
> >       2.  One of the distinctions in the latest discussion=20
> is between=20
> > having the Note Well attempt to summarize what the IPR rules are,=20
> > versus having it merely declare that we have IPR rules and=20
> point the=20
> > reader to them.  For summary instruments, like a Note Well,=20
> the latter=20
> > approach makes far more sense.
> >
> >       3.  We need all of the IPR rules for IETF=20
> participation to be in=20
> > a single, simple, clear document that is easily=20
> understandable by an=20
> > average engineer. (See point 1.)
> >
> >
> > d/
> >
> > --
> > Dave Crocker
> > Brandenburg InternetWorking
> > bbiw.net
> >
> =

From d3e3e3@gmail.com  Wed Jan 29 08:16:48 2014
Return-Path: <d3e3e3@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82BE61A0427; Wed, 29 Jan 2014 08:16:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level: 
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GSAv9FihoeEn; Wed, 29 Jan 2014 08:16:46 -0800 (PST)
Received: from mail-oa0-x22b.google.com (mail-oa0-x22b.google.com [IPv6:2607:f8b0:4003:c02::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 7C0F61A03BF; Wed, 29 Jan 2014 08:16:46 -0800 (PST)
Received: by mail-oa0-f43.google.com with SMTP id h16so2275265oag.16 for <multiple recipients>; Wed, 29 Jan 2014 08:16:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=5EUH2LRrrJBcDqRDHIoI5LRX5KhMmmsb3YzqRsyBQuI=; b=wlPd/h3J9Jf3V+fPkGjZQV9xdWQGUnsCLtP1ZHSYGazexifl+wIuC8f6hv3GKHKcGz GjpCBsumlyWCTgzfn9OrpqJEFEgTpDF0h5Qti7FA3WqApvI19YHqdd0rUYHTDitF0D0D YKFqhCJOTArU29wIMIiaRADe/WtfFDPzULkeibVHk2/oLTU5pS9sxC35b7eGXJdTOkJz Vb/CYoIy17JgKXLk9VBoX6H6PSzQMJYUW3YOdWeW+ILgOcsMfTvJ3xgKKFrjUnrXyzIY 741SsQOAK+VftN5em4sJCU56tuG2ZuuQEG61Q4/cwtZ1hJVUjHX5nNaFUbdgQ3i0egn6 tKaA==
X-Received: by 10.183.3.102 with SMTP id bv6mr7058660obd.18.1391012203430; Wed, 29 Jan 2014 08:16:43 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.33.102 with HTTP; Wed, 29 Jan 2014 08:16:23 -0800 (PST)
In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B1250B2@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <52E3326E.3080007@gmail.com> <82D163D29DC1D4A7B4797E8F@JcK-HP8200.jck.com> <01P3M48DZNS80000AS@mauve.mrochek.com> <52E5E624.4080003@gmail.com> <19AAADA2-8E3B-456F-B0CE-9A27D2BB5FE9@piuha.net> <52E69572.7000903@dcrocker.net> <CADnDZ8_X-APwa6BSYF+taXw01XGCH-ffsAnneo+6HsXo4WqbHg@mail.gmail.com> <949EF20990823C4C85C18D59AA11AD8B1250B2@FR712WXCHMBA11.zeu.alcatel-lucent.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Wed, 29 Jan 2014 11:16:23 -0500
Message-ID: <CAF4+nEEhZRVp931ayK2LpVyEYje=3zkZ0pej5qhgoXVD+vR=Rw@mail.gmail.com>
Subject: Re: Problem with new Note Well
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF WG Chairs <wgchairs@ietf.org>, ietf <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 16:16:48 -0000

Hi Keith,

On Wed, Jan 29, 2014 at 10:31 AM, DRAGE, Keith (Keith)
<keith.drage@alcatel-lucent.com> wrote:
> In regard to "all countries / regions" the disclosure requirements are not that different from the disclosure requirements of every SDO, all with memberships from just about every country in the world.
>
> I would have expected that if there was a legal problem with disclosure, then it would have been spotted by now, given the level of test it has been given by all those SDOs.
>
> The difference with IETF is with representation by individual. For the SDOs the membership is by company or equivalent, and they sign up (on behalf of all their employees or consultants) to the disclosure requirements when they join the SDO.

The IETF is by no means unique in this regard. IEEE 802 and all its
working groups (802.3 (Ethernet), 802.11 (Wi-Fi), 802.15
(Bluetooth/Zigbee/etc)) all have "representation by individual".

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com


> But in general the disclosure requires as defined in RFC 3979 are not that complex and it is entirely reasonable that all participants should be required to read it. I do not believe it requires a trained legal expert to understand it.
>
> And as for being left alone, if you really are an individual (alone) with "contributor's IPR" or "participants IPR" then you are paying any awful lot of legal fees to keep that IPR; why not spend some of it on your responsibilities to IETF.
>
> As for consultants, if you are paid to participate in the IETF, then you should ensure your contract allows you to meet the requirements of the IETF. It might help if RFC 3979 made this point, but it should be self evident anyway.
>
> Regards
>
> Keith
>
>> -----Original Message-----
>> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf
>> Of Abdussalam Baryun
>> Sent: 29 January 2014 10:39
>> To: ietf
>> Cc: Cullen Jennings (fluffy); IETF WG Chairs
>> Subject: Re: Problem with new Note Well
>>
>> I agree with the suggestions below and that I never liked the
>> note well wordings. In addition, from Cullen's first message
>> and others, it seems like most IETF participants are not
>> practicing or understandning the note well. The reason may be
>> because engineers are not good in legal issues, so do we have
>> a current legal advisor/position in IETF organisation, or
>> still IETF has no progress in legal experience, so we will
>> need to go back to external legal. Why IETF just leaves its
>> participants alone to do the legal advise but when it comes
>> to their works it encourages inputs? Does the note well
>> consider all countries/regions legal policies? Is it
>> practical/agreeable for all participants any where, or was it tested?
>>
>> For me I don't agree with the way the note well is forced on
>> all, it needs more discussions between WGs and their Chairs,
>> but no time for it or no advisors or group discussion/meeting
>> for legal issues (may be only IESG decides for us so far
>> which is never practical).
>>
>> AB
>>
>> On 1/27/14, Dave Crocker <dhc@dcrocker.net> wrote:
>> > On 1/27/2014 8:17 AM, Jari Arkko wrote:
>> >> All - it is clear that you have a concern about the new
>> note well text.
>> >> The problem has been well articulated;
>> >
>> >
>> > Jari, et al,
>> >
>> >
>> > There are a number of different problems, and only some of
>> them have
>> > been articulated.  Worse, the problems include the IPR rules
>> > themselves, not just the Note Well:
>> >
>> >       0.  We have had IPR rules and a Note Well for many years and
>> > have revised both a number of times.  Normally, work we do that has
>> > been around that long warrants being called "mature", which
>> means that
>> > it works well and is well understood.  The latest discussion
>> > demonstrates that that model does not apply to the IETF's IPR
>> > handling.  In fact, the exchange looks more like the disparities we
>> > see early in a working group effort, not what normally
>> takes place after many years.
>> >
>> >       1. The participants in the discussion are extremely
>> experienced
>> > with the IETF and with this topic.  Yet they demonstrated a strong
>> > /lack/ of rough consensus about what the /current/ IPR rules mean.
>> >
>> >       2.  The current rules are too complex for use by average
>> > engineers.  Engineers are not attorneys, nevermind IPR
>> attorneys.  IPR
>> > is considered by attorneys to be an esoteric and difficult
>> specialty.
>> > The IETF's IPR rules need to be simple and simply stated,
>> if we expect
>> > average engineers to understand them.
>> >
>> >       3.  The current IPR rules appear to impose an unreasonable
>> > demand on IETF participants, such as conflicting with
>> employment arrangements.
>> > (And if the demand is reasonable, then what is noteworthy is that
>> > someone who has read this latest IETF discussion has developed the
>> > impression that it isn't.  See point 6.)
>> >
>> >       4.  The current Note Well is too complex and
>> apparently erroneous.
>> >   (And if it is not erroneous, then what is noteworthy is that a
>> > serious attempt to review the thread has resulted in
>> someone coming to
>> > the conclusion that the Note Well is erroneous.  See point 6.)
>> >
>> >       5.  Expecting an average IETF engineer to consult 4 different
>> > BCPs, in order to understand what is required of them is
>> not reasonable.
>> >   Nor is all each document relevant.  So, in effect, the references
>> > are overly broad, as well as too complicated. (See point 6.)
>> >
>> >       6.  Having a range of experienced, diligent IETF participants
>> > demonstrate substantive disagreement about the meaning of
>> our current
>> > IPR rules undermines whatever utility the rules might have.
>>  It sets
>> > up a litigation argument that the participant did not
>> understand the
>> > rules, citing this thread as demonstrating that others also don't.
>> >
>> >
>> > The remedies we need are not just with the Note Well.  We
>> need to fix
>> > the IPR rules too.
>> >
>> >
>> >       0.  We need to establish clear and compelling community rough
>> > consensus about the meaning of our IPR rules and the utility of our
>> > Note Well.  We are currently /very/ far from being able to do that.
>> >
>> >       1.  We need a consensus statement that describes our
>> 'model' of
>> > an IETF particpant, in terms of what is reasonable for them to know
>> > and what is reasonable for them to be responsible for and what is
>> > reasonable for them to do, especially within the real time
>> performance
>> > constraints of a working group meeting. The premise of that model
>> > needs to be extreme simplicity and clarity.  Any rules we
>> assert need
>> > to be vetted against that model.  Our current arrangement
>> requires an
>> > average engineer to be more knowledgeable and more diligent
>> than is reasonable.
>> >   (By 'diligent' I'm not referring to intent; I'm referring
>> to classic
>> > human factors usability limits.)
>> >
>> >       2.  One of the distinctions in the latest discussion
>> is between
>> > having the Note Well attempt to summarize what the IPR rules are,
>> > versus having it merely declare that we have IPR rules and
>> point the
>> > reader to them.  For summary instruments, like a Note Well,
>> the latter
>> > approach makes far more sense.
>> >
>> >       3.  We need all of the IPR rules for IETF
>> participation to be in
>> > a single, simple, clear document that is easily
>> understandable by an
>> > average engineer. (See point 1.)
>> >
>> >
>> > d/
>> >
>> > --
>> > Dave Crocker
>> > Brandenburg InternetWorking
>> > bbiw.net
>> >
>>

From keith.drage@alcatel-lucent.com  Wed Jan 29 10:09:14 2014
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC4B21A04D7; Wed, 29 Jan 2014 10:09:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jw2b6_Zo8LLs; Wed, 29 Jan 2014 10:09:10 -0800 (PST)
Received: from hoemail1.alcatel.com (hoemail1.alcatel.com [192.160.6.148]) by ietfa.amsl.com (Postfix) with ESMTP id 7FB0F1A036B; Wed, 29 Jan 2014 10:08:47 -0800 (PST)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by hoemail1.alcatel.com (8.13.8/IER-o) with ESMTP id s0TI8gPE014986 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 29 Jan 2014 12:08:44 -0600 (CST)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id s0TI8gOS002277 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 29 Jan 2014 19:08:42 +0100
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.26]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.02.0247.003; Wed, 29 Jan 2014 19:08:42 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Subject: RE: Problem with new Note Well
Thread-Topic: Problem with new Note Well
Thread-Index: AQHPHPzckxdedUpOzkK4h72KmTW/JZqbxCPwgAAMB4CAAC+MEA==
Date: Wed, 29 Jan 2014 18:08:41 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B1253DF@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <52E3326E.3080007@gmail.com> <82D163D29DC1D4A7B4797E8F@JcK-HP8200.jck.com> <01P3M48DZNS80000AS@mauve.mrochek.com> <52E5E624.4080003@gmail.com> <19AAADA2-8E3B-456F-B0CE-9A27D2BB5FE9@piuha.net> <52E69572.7000903@dcrocker.net> <CADnDZ8_X-APwa6BSYF+taXw01XGCH-ffsAnneo+6HsXo4WqbHg@mail.gmail.com> <949EF20990823C4C85C18D59AA11AD8B1250B2@FR712WXCHMBA11.zeu.alcatel-lucent.com> <CAF4+nEEhZRVp931ayK2LpVyEYje=3zkZ0pej5qhgoXVD+vR=Rw@mail.gmail.com>
In-Reply-To: <CAF4+nEEhZRVp931ayK2LpVyEYje=3zkZ0pej5qhgoXVD+vR=Rw@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.38]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF WG Chairs <wgchairs@ietf.org>, ietf <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 18:09:15 -0000

Agreed. IETF is not unique in this.

The point was to try and explain why individual participants in other SDOs =
may not have realised how they were committed to similar rules, although th=
ey are generally reminded of that commitment at the start of every meeting.

Regards

Keith

> -----Original Message-----
> From: Donald Eastlake [mailto:d3e3e3@gmail.com]=20
> Sent: 29 January 2014 16:16
> To: DRAGE, Keith (Keith)
> Cc: ietf; IETF WG Chairs
> Subject: Re: Problem with new Note Well
>=20
> Hi Keith,
>=20
> On Wed, Jan 29, 2014 at 10:31 AM, DRAGE, Keith (Keith)=20
> <keith.drage@alcatel-lucent.com> wrote:
> > In regard to "all countries / regions" the disclosure=20
> requirements are not that different from the disclosure=20
> requirements of every SDO, all with memberships from just=20
> about every country in the world.
> >
> > I would have expected that if there was a legal problem=20
> with disclosure, then it would have been spotted by now,=20
> given the level of test it has been given by all those SDOs.
> >
> > The difference with IETF is with representation by=20
> individual. For the SDOs the membership is by company or=20
> equivalent, and they sign up (on behalf of all their=20
> employees or consultants) to the disclosure requirements when=20
> they join the SDO.
>=20
> The IETF is by no means unique in this regard. IEEE 802 and=20
> all its working groups (802.3 (Ethernet), 802.11 (Wi-Fi), 802.15
> (Bluetooth/Zigbee/etc)) all have "representation by individual".
>=20
> Thanks,
> Donald
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  155 Beaver Street, Milford, MA 01757 USA  d3e3e3@gmail.com
>=20
>=20
> > But in general the disclosure requires as defined in RFC=20
> 3979 are not that complex and it is entirely reasonable that=20
> all participants should be required to read it. I do not=20
> believe it requires a trained legal expert to understand it.
> >
> > And as for being left alone, if you really are an=20
> individual (alone) with "contributor's IPR" or "participants=20
> IPR" then you are paying any awful lot of legal fees to keep=20
> that IPR; why not spend some of it on your responsibilities to IETF.
> >
> > As for consultants, if you are paid to participate in the=20
> IETF, then you should ensure your contract allows you to meet=20
> the requirements of the IETF. It might help if RFC 3979 made=20
> this point, but it should be self evident anyway.
> >
> > Regards
> >
> > Keith
> >
> >> -----Original Message-----
> >> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of=20
> >> Abdussalam Baryun
> >> Sent: 29 January 2014 10:39
> >> To: ietf
> >> Cc: Cullen Jennings (fluffy); IETF WG Chairs
> >> Subject: Re: Problem with new Note Well
> >>
> >> I agree with the suggestions below and that I never liked the note=20
> >> well wordings. In addition, from Cullen's first message=20
> and others,=20
> >> it seems like most IETF participants are not practicing or=20
> >> understandning the note well. The reason may be because=20
> engineers are=20
> >> not good in legal issues, so do we have a current legal=20
> >> advisor/position in IETF organisation, or still IETF has=20
> no progress=20
> >> in legal experience, so we will need to go back to external legal.=20
> >> Why IETF just leaves its participants alone to do the legal advise=20
> >> but when it comes to their works it encourages inputs?=20
> Does the note=20
> >> well consider all countries/regions legal policies? Is it=20
> >> practical/agreeable for all participants any where, or was=20
> it tested?
> >>
> >> For me I don't agree with the way the note well is forced=20
> on all, it=20
> >> needs more discussions between WGs and their Chairs, but=20
> no time for=20
> >> it or no advisors or group discussion/meeting for legal=20
> issues (may=20
> >> be only IESG decides for us so far which is never practical).
> >>
> >> AB
> >>
> >> On 1/27/14, Dave Crocker <dhc@dcrocker.net> wrote:
> >> > On 1/27/2014 8:17 AM, Jari Arkko wrote:
> >> >> All - it is clear that you have a concern about the new
> >> note well text.
> >> >> The problem has been well articulated;
> >> >
> >> >
> >> > Jari, et al,
> >> >
> >> >
> >> > There are a number of different problems, and only some of
> >> them have
> >> > been articulated.  Worse, the problems include the IPR rules=20
> >> > themselves, not just the Note Well:
> >> >
> >> >       0.  We have had IPR rules and a Note Well for many=20
> years and=20
> >> > have revised both a number of times.  Normally, work we=20
> do that has=20
> >> > been around that long warrants being called "mature", which
> >> means that
> >> > it works well and is well understood.  The latest discussion=20
> >> > demonstrates that that model does not apply to the IETF's IPR=20
> >> > handling.  In fact, the exchange looks more like the=20
> disparities we=20
> >> > see early in a working group effort, not what normally
> >> takes place after many years.
> >> >
> >> >       1. The participants in the discussion are extremely
> >> experienced
> >> > with the IETF and with this topic.  Yet they=20
> demonstrated a strong=20
> >> > /lack/ of rough consensus about what the /current/ IPR=20
> rules mean.
> >> >
> >> >       2.  The current rules are too complex for use by average=20
> >> > engineers.  Engineers are not attorneys, nevermind IPR
> >> attorneys.  IPR
> >> > is considered by attorneys to be an esoteric and difficult
> >> specialty.
> >> > The IETF's IPR rules need to be simple and simply stated,
> >> if we expect
> >> > average engineers to understand them.
> >> >
> >> >       3.  The current IPR rules appear to impose an unreasonable=20
> >> > demand on IETF participants, such as conflicting with
> >> employment arrangements.
> >> > (And if the demand is reasonable, then what is=20
> noteworthy is that=20
> >> > someone who has read this latest IETF discussion has=20
> developed the=20
> >> > impression that it isn't.  See point 6.)
> >> >
> >> >       4.  The current Note Well is too complex and
> >> apparently erroneous.
> >> >   (And if it is not erroneous, then what is noteworthy is that a=20
> >> > serious attempt to review the thread has resulted in
> >> someone coming to
> >> > the conclusion that the Note Well is erroneous.  See point 6.)
> >> >
> >> >       5.  Expecting an average IETF engineer to consult=20
> 4 different=20
> >> > BCPs, in order to understand what is required of them is
> >> not reasonable.
> >> >   Nor is all each document relevant.  So, in effect, the=20
> references=20
> >> > are overly broad, as well as too complicated. (See point 6.)
> >> >
> >> >       6.  Having a range of experienced, diligent IETF=20
> participants=20
> >> > demonstrate substantive disagreement about the meaning of
> >> our current
> >> > IPR rules undermines whatever utility the rules might have.
> >>  It sets
> >> > up a litigation argument that the participant did not
> >> understand the
> >> > rules, citing this thread as demonstrating that others=20
> also don't.
> >> >
> >> >
> >> > The remedies we need are not just with the Note Well.  We
> >> need to fix
> >> > the IPR rules too.
> >> >
> >> >
> >> >       0.  We need to establish clear and compelling=20
> community rough=20
> >> > consensus about the meaning of our IPR rules and the=20
> utility of our=20
> >> > Note Well.  We are currently /very/ far from being able=20
> to do that.
> >> >
> >> >       1.  We need a consensus statement that describes our
> >> 'model' of
> >> > an IETF particpant, in terms of what is reasonable for=20
> them to know=20
> >> > and what is reasonable for them to be responsible for=20
> and what is=20
> >> > reasonable for them to do, especially within the real time
> >> performance
> >> > constraints of a working group meeting. The premise of=20
> that model=20
> >> > needs to be extreme simplicity and clarity.  Any rules we
> >> assert need
> >> > to be vetted against that model.  Our current arrangement
> >> requires an
> >> > average engineer to be more knowledgeable and more diligent
> >> than is reasonable.
> >> >   (By 'diligent' I'm not referring to intent; I'm referring
> >> to classic
> >> > human factors usability limits.)
> >> >
> >> >       2.  One of the distinctions in the latest discussion
> >> is between
> >> > having the Note Well attempt to summarize what the IPR=20
> rules are,=20
> >> > versus having it merely declare that we have IPR rules and
> >> point the
> >> > reader to them.  For summary instruments, like a Note Well,
> >> the latter
> >> > approach makes far more sense.
> >> >
> >> >       3.  We need all of the IPR rules for IETF
> >> participation to be in
> >> > a single, simple, clear document that is easily
> >> understandable by an
> >> > average engineer. (See point 1.)
> >> >
> >> >
> >> > d/
> >> >
> >> > --
> >> > Dave Crocker
> >> > Brandenburg InternetWorking
> >> > bbiw.net
> >> >
> >>
> =

From geoff.mulligan@nist.gov  Wed Jan 29 10:22:53 2014
Return-Path: <geoff.mulligan@nist.gov>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 397B41A03D4; Wed, 29 Jan 2014 10:22:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WjFoCBxYALQ8; Wed, 29 Jan 2014 10:22:50 -0800 (PST)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0241.outbound.protection.outlook.com [207.46.163.241]) by ietfa.amsl.com (Postfix) with ESMTP id 06A9E1A03CB; Wed, 29 Jan 2014 10:22:49 -0800 (PST)
Received: from BLUPR09MB054.namprd09.prod.outlook.com (10.255.211.148) by BLUPR09MB054.namprd09.prod.outlook.com (10.255.211.148) with Microsoft SMTP Server (TLS) id 15.0.859.15; Wed, 29 Jan 2014 18:22:45 +0000
Received: from BLUPR09MB054.namprd09.prod.outlook.com ([10.255.211.148]) by BLUPR09MB054.namprd09.prod.outlook.com ([169.254.9.198]) with mapi id 15.00.0859.020; Wed, 29 Jan 2014 18:22:45 +0000
From: "Mulligan, Geoff" <geoff.mulligan@nist.gov>
To: Ned Freed <ned.freed@mrochek.com>
Subject: RE: Third party disclosures and NDAs (Re: Problem with new Note Well )
Thread-Topic: Third party disclosures and NDAs (Re: Problem with new Note Well )
Thread-Index: AQHPG3klyCBjqxHw+E6Dqsh/YOVH+ZqYyr7pgAGx/bGAAYnplQ==
Date: Wed, 29 Jan 2014 18:22:45 +0000
Message-ID: <db83aff680884b6789f9a981db6e4e9e@BLUPR09MB054.namprd09.prod.outlook.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E3EBA9.4050005@nist.gov> <CB2D10B9-DAD4-4C47-B984-A55D136C3126@piuha.net> <126fb3003777478a93ac346b525150af@BLUPR09MB054.namprd09.prod.outlook.com>, <01P3ONLTEKWA0000AS@mauve.mrochek.com>
In-Reply-To: <01P3ONLTEKWA0000AS@mauve.mrochek.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [129.6.33.54]
x-forefront-prvs: 01068D0A20
x-forefront-antispam-report: SFV:NSPM; SFS:(10009001)(6009001)(377454003)(189002)(199002)(47736001)(47976001)(74366001)(46102001)(74706001)(4396001)(53806001)(56816005)(90146001)(49866001)(50986001)(33646001)(86362001)(85852003)(93516002)(93136001)(51856001)(81686001)(81816001)(76576001)(76796001)(76786001)(54356001)(92566001)(94316002)(74316001)(69226001)(76482001)(74876001)(56776001)(81542001)(87936001)(19580405001)(80976001)(74502001)(47446002)(87266001)(83322001)(77982001)(59766001)(19580395003)(85306002)(551944002)(63696002)(81342001)(79102001)(74662001)(80022001)(65816001)(2656002)(83072002)(31966008)(54316002)(66066001)(94946001)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:BLUPR09MB054; H:BLUPR09MB054.namprd09.prod.outlook.com; CLIP:129.6.33.54; FPR:; InfoNoRecordsMX:1; A:1; LANG:en; 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: nist.gov
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 18:22:53 -0000

Great.  I can understand the "Encouraged !=3D required".  I had understood =
from previous messages that  I would be required.=0A=
=0A=
I'm happy now - well at least about this.=0A=
=0A=
Geoff=0A=
=0A=
=0A=
Geoff Mulligan | Presidential Innovation Fellow | Executive Office of the P=
resident | 301.975.6283=0A=
=0A=
________________________________________=0A=
From: Ned Freed <ned.freed@mrochek.com>=0A=
Sent: Tuesday, January 28, 2014 1:31 PM=0A=
To: Mulligan, Geoff=0A=
Cc: Jari Arkko; IETF WG Chairs; ietf@ietf.org Mailing List=0A=
Subject: RE: Third party disclosures and NDAs (Re: Problem with new Note We=
ll )=0A=
=0A=
> So because I know of IPR that someone else has and is not disclosing and=
=0A=
> because I cannot legally disclose it - I can't continue to participate in=
 the=0A=
> discussion doesn't seem right.  I'm not the holder of the IPR that isn't =
being=0A=
> disclosed, but I'm penalized.=0A=
=0A=
As I have pointed out several times now, that's incorrect. Section 6.1.3 of=
=0A=
BCP 79 discusses "IPR of Others", and says:=0A=
=0A=
   If a person has information about IPR that may Cover IETF=0A=
   Contributions, but the participant is not required to disclose=0A=
   because they do not meet the criteria in Section 6.6 (e.g., the IPR=0A=
   is owned by some other company), such person is encouraged to notify=0A=
   the IETF by sending an email message to ietf-ipr@ietf.org.  Such a=0A=
   notice should be sent as soon as reasonably possible after the person=0A=
   realizes the connection.=0A=
=0A=
And the referenced section 6.6 says:=0A=
=0A=
   6.6.  When is a Disclosure Required?=0A=
=0A=
   IPR disclosures under Sections 6.1.1. and 6.1.2 are required with=0A=
   respect to IPR that is owned directly or indirectly, by the=0A=
   individual or his/her employer or sponsor (if any) or that such=0A=
   persons otherwise have the right to license or assert.=0A=
=0A=
Encouraged !=3D required.=0A=
=0A=
The wrinkle here - and why I think you're getting some odd answers to your=
=0A=
questions - is that you're not being clear about what role the "someone els=
e"=0A=
you're talking about has in the IETF. If the "someone else" is not=0A=
participating in the IETF, then there's no problem, other than possibly you=
r=0A=
own conscience.=0A=
=0A=
If the "someone else" is participating while meeting the disclosure=0A=
requirements, then once again there's no problem since the disclosure has=
=0A=
already been done and there's no need for you to repeat it.=0A=
=0A=
But if they are participating and not disclosing, then there's a big proble=
m,=0A=
and in that case it may indeed suck to be you. My advice in such cases woul=
d be=0A=
to consult an attorney with substantive expertise in IP law as to what your=
=0A=
obligations are.=0A=
=0A=
I do expect such cases to be quite rare though.=0A=
=0A=
=0A=
                                Ned=0A=

From gtw@gtwassociates.com  Wed Jan 29 09:51:53 2014
Return-Path: <gtw@gtwassociates.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C3211A0370; Wed, 29 Jan 2014 09:51:53 -0800 (PST)
X-Quarantine-ID: <wNHj6seIxsek>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace (char 20 hex): X-Spam-Report: ...that system for details.\n \n Content previ[...]
X-Spam-Flag: NO
X-Spam-Score: 1.239
X-Spam-Level: *
X-Spam-Status: No, score=1.239 tagged_above=-999 required=5 tests=[BAYES_50=0.8, STOX_REPLY_TYPE=0.439] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wNHj6seIxsek; Wed, 29 Jan 2014 09:51:51 -0800 (PST)
Received: from s2.mail.rcig.net (s2.mail.rcig.net [216.87.38.202]) by ietfa.amsl.com (Postfix) with ESMTP id C8B2F1A0276; Wed, 29 Jan 2014 09:51:51 -0800 (PST)
Received: from pool-108-28-107-161.washdc.fios.verizon.net ([108.28.107.161]:62674 helo=GTWPC) by s2.mail.rcig.net with esmtpa (Exim 4.72) (envelope-from <gtw@gtwassociates.com>) id 1W8ZIh-0004Vd-H1; Wed, 29 Jan 2014 11:51:48 -0600
Message-ID: <B04A33F733FD475B99006902BBC1FE18@GTWPC>
From: "GTW" <gtw@gtwassociates.com>
To: "Robert Elz" <kre@munnari.OZ.AU>, <ietf@ietf.org>
References: <201401281812.s0SICTXk3778564@shell01.TheWorld.com> <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E3EBA9.4050005@nist.gov>, <CB2D10B9-DAD4-4C47-B984-A55D136C3126@piuha.net> <126fb3003777478a93ac346b525150af@BLUPR09MB054.namprd09.prod.outlook.com> <4111.1390994763@perseus.noi.kre.to>
In-Reply-To: <4111.1390994763@perseus.noi.kre.to>
Subject: Re: IPR disclosure rules in general (Was: various other stuff...)
Date: Wed, 29 Jan 2014 12:51:42 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 16.4.3505.912
X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3505.912
X-ACL-Warn: X-The email account used to send this email was: gtw@gtwassociates.com
X-Mailman-Approved-At: Wed, 29 Jan 2014 10:28:45 -0800
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: GTW <gtw@gtwassociates.com>
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 17:51:53 -0000

I believe practical experience should play a significant role  shaping 
policies and procedures of any organization.

Much of the discussion has focused on addressing hypothetical situations ... 
and those mainly to do with disclosure obligations.

What  problems has IETF experienced due to non disclosure of IP that has 
turned out to be essential to some RFC but was not disclosed by any party 
... IETF participant, non-participant, consultant, ...anyone.   I do recall 
some sharing about "late disclosures" but I do not have any specifics.  Does 
anyone have data about our practical  experiences?  My opinion is that first 
priority should be do address whatever may be current problems.

I believe most of the current litigation has more to do with differences of 
opinion between licensees and licensors over license assurances made and 
less  to do with allegations  of non disclosure of a disclosure that should 
have been made.

George T. Willingmyre, P.E.
President GTW Associates

-----Original Message----- 
From: Robert Elz
Sent: Wednesday, January 29, 2014 6:26 AM
To: ietf@ietf.org
Cc: wgchairs@ietf.org
Subject: IPR disclosure rules in general (Was: various other stuff...)

    Date:        Tue, 28 Jan 2014 13:12:29 -0500 (EST)
    From:        worley@ariadne.com (Dale R. Worley)
    Message-ID:  <201401281812.s0SICTXk3778564@shell01.TheWorld.com>

  | Indeed, if the IETF didn't have this rule, a company with undisclosed
  | IPR could hire consultants, put them under NDA, and have them advocate
  | at the IETF to include the IPR in standards.

Much easier, for such nefarious company, is simply to hire (as employees, or
consultants, it makes no difference) people to "represent" the company's
interest at the IETF, and make sure that those people are unaware of any
and all IPR claims that the company may possess.

In that case, the person attending the IETF cannot possibly disclose the
IPR, as they're unaware of it, the company can't be expected to disclose
anything - companies don't attend the IETF (except as sponsors perhaps, and
I am fairly sure that no-one asks the sponsors to reveal all their IPR 
before
we take their money) the people all attend as individuals.

We may not like this kind of behaviour, but other than completely changing
the way the IETF is designed to operate (to actually have company's 
explicitly
become members, and enter into membership agreements, with only 
representatives
of member companies permitted to participate) which I don't think anyone 
wants,
there really is nothing that can be done about it.

Now this by no means guarantees that the courts won't take a dim view of
this kind of behaviour, if an attempt is later made to enforce the IPR 
claim,
but it won't be because of any breach of IETF rules - there hasn't been any
in this scenario.

All of these problems are brought about by yet another instance of the
IETF attempting to fix something that is simply way outside our competence
or ability to fix.  It isn't surprising - after all, the IETF is made up
(mostly) of engineers, and when an engineer sees something broken, the
natural inclination is to attempt to fix it.  But sometimes the underlying
problem is something that simply cannot be fixed by any amount of 
engineering.
Hidden IPR is one of those, the problem is in people's attitudes - how
willing they are to put their own interests ahead of the general community
interest.   You simply cannot engineer a fix to this, it is a social issue.

Everything beyond simply encouraging people to disclose any IPR that they're
aware of, which they are able to disclose - or if unable, to attempt to
encourage those who are able to disclose it, is beyond what is rational for
the IETF to attempt to do, and what's more, the "rules" that people spend
so much time debating (people waste so much time debating) are essentially
useless, as they have no enforcement mechanism.  What exactly is the IETF
supposed to do, if it is revealed, some time later, that some IPR was not
disclosed by a participant in some discussions that they could have
disclosed?   As I understand it, there is simply some hope that some court
will use that to invalidate the IPR claim - but nothing I've seen suggests
that the "rule" is actually necessary for that, and even if it is, as above,
it is trivial to work around.

These days the IETF is spending far too much time on issues that have 
nothing
to do with actually improving the protocols in use on the internet, and
should go back to doing what it can do, and simply allow the rest to be
handled in the places designed to handle such things.   Stepping back, and
saying "I cannot fix that problem" seems like being defeated, but it isn't,
it is just accepting reality.  That is good engineering.

kre


From agenda@ietf.org  Thu Jan 30 11:34:05 2014
Return-Path: <agenda@ietf.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E91521A0435; Thu, 30 Jan 2014 11:34:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bHgFZQPghrfa; Thu, 30 Jan 2014 11:34:03 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F4461A046B; Thu, 30 Jan 2014 11:34:03 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Agenda <agenda@ietf.org>
To: Working Group Chairs <wgchairs@ietf.org>
Subject: REMINDER - IETF 89 Working Group Chairs Training Lunch
X-Test-IDTracker: no
X-IETF-IDTracker: 4.90.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140130193403.14223.97300.idtracker@ietfa.amsl.com>
Date: Thu, 30 Jan 2014 11:34:03 -0800
Cc: edu-team@ietf.org, irsg@irtf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: IETF Agenda <agenda@ietf.org>
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jan 2014 19:34:05 -0000

Hello Everyone,

This is a friendly reminder to register for the WG Chairs training lunch th=
at will be held at IETF 89 in London before Monday, February 10th.  =


All current WG chairs, BOF chairs, IRTF chairs, and IESG members are welcom=
e to attend. The lunch training will take place on Wednesday, March 5th, 20=
14 at 11:30am, and a complimentary lunch will be provided.  The location wi=
ll be announced separately to those who RSVP.

The topic of the training will be "On Consensus" lead by Pete Resnick, Meli=
nda Shore and Peter Saint-Andre.

If you would like to attend this session, please RSVP using the registratio=
n page: https://www.ietf.org/registration/ietf89/rsvp.py?eventid=3D1&eventc=
ode=3D348905 =


If you have RSVP'd for the training lunch but will not be able to attend, o=
r have any issues registering for the event, please send a message to agend=
a@ietf.org.  =



Thank You!

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

From agenda@ietf.org  Fri Jan 31 16:54:53 2014
Return-Path: <agenda@ietf.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB9F21ACCDA; Fri, 31 Jan 2014 16:54:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tkDVdEOq6OMf; Fri, 31 Jan 2014 16:54:51 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C16901ACC92; Fri, 31 Jan 2014 16:54:51 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Agenda <agenda@ietf.org>
To: Working Group Chairs <wgchairs@ietf.org>
Subject: IETF 89 Preliminary Agenda
X-Test-IDTracker: no
X-IETF-IDTracker: 5.0.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140201005451.8686.25003.idtracker@ietfa.amsl.com>
Date: Fri, 31 Jan 2014 16:54:51 -0800
Cc: irsg@irtf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: IETF Agenda <agenda@ietf.org>
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Feb 2014 00:54:53 -0000

NOTE: You will not receive an automatic notification informing you that your session has been scheduled.  Please see https://datatracker.ietf.org/meeting/89/agenda.html to determine the time(s) of your session(s).  

The IETF 89 preliminary agenda has been posted.  The final agenda will be published on Friday, February 7th, 2014.  

If you would like to request a change to the preliminary agenda, please send a message to agenda@ietf.org and copy all relevant Area Directors.

Please note the cut-off date for requests to reschedule Working Group sessions and BOFs is February 3rd, 2014 at UTC 23:59.

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

Thank you!

IETF Secretariat

From denghui02@hotmail.com  Fri Jan 31 17:02:15 2014
Return-Path: <denghui02@hotmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 715ED1ACCE8; Fri, 31 Jan 2014 17:02:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.984
X-Spam-Level: 
X-Spam-Status: No, score=-0.984 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_36=0.6, J_CHICKENPOX_38=0.6, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D2OvzBHXnuD9; Fri, 31 Jan 2014 17:02:14 -0800 (PST)
Received: from col0-omc2-s4.col0.hotmail.com (col0-omc2-s4.col0.hotmail.com [65.55.34.78]) by ietfa.amsl.com (Postfix) with ESMTP id 66FEF1ACCDE; Fri, 31 Jan 2014 17:02:14 -0800 (PST)
Received: from COL125-W17 ([65.55.34.73]) by col0-omc2-s4.col0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 31 Jan 2014 17:02:11 -0800
X-TMN: [NhjSwbq5petUpFsfWgPyokvd6724Do51Xn7YA+ga3nE=]
X-Originating-Email: [denghui02@hotmail.com]
Message-ID: <COL125-W1776D708C4571AB314AEA9B1A90@phx.gbl>
Content-Type: multipart/alternative; boundary="_56063684-26df-46a9-977b-e0de90a65883_"
From: Hui Deng <denghui02@hotmail.com>
To: IETF Agenda <agenda@ietf.org>, Working Group Chairs <wgchairs@ietf.org>
Subject: RE: IETF 89 Preliminary Agenda
Date: Sat, 1 Feb 2014 09:02:10 +0800
Importance: Normal
In-Reply-To: <20140201005451.8686.25003.idtracker@ietfa.amsl.com>
References: <20140201005451.8686.25003.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
X-OriginalArrivalTime: 01 Feb 2014 01:02:11.0180 (UTC) FILETIME=[3CB5E2C0:01CF1EE9]
Cc: "irsg@irtf.org" <irsg@irtf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Feb 2014 01:02:15 -0000

--_56063684-26df-46a9-977b-e0de90a65883_
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64

SnVzdCB3YW5kZXJpbmcgd2hldGhlciBNSUYoTW9uZGF5IG1vcm5pbmcpIGNhbiBiZSBleGNoYW5n
ZWQgd2l0aCBESEMoVGh1cnNkYXkgbW9ybmluZykNCiANCnRoYW5rcw0KIA0KLUh1aQ0KIA0KPiBG
cm9tOiBhZ2VuZGFAaWV0Zi5vcmcNCj4gVG86IHdnY2hhaXJzQGlldGYub3JnDQo+IFN1YmplY3Q6
IElFVEYgODkgUHJlbGltaW5hcnkgQWdlbmRhDQo+IERhdGU6IEZyaSwgMzEgSmFuIDIwMTQgMTY6
NTQ6NTEgLTA4MDANCj4gQ0M6IGlyc2dAaXJ0Zi5vcmcNCj4gDQo+IA0KPiBOT1RFOiBZb3Ugd2ls
bCBub3QgcmVjZWl2ZSBhbiBhdXRvbWF0aWMgbm90aWZpY2F0aW9uIGluZm9ybWluZyB5b3UgdGhh
dCB5b3VyIHNlc3Npb24gaGFzIGJlZW4gc2NoZWR1bGVkLiAgUGxlYXNlIHNlZSBodHRwczovL2Rh
dGF0cmFja2VyLmlldGYub3JnL21lZXRpbmcvODkvYWdlbmRhLmh0bWwgdG8gZGV0ZXJtaW5lIHRo
ZSB0aW1lKHMpIG9mIHlvdXIgc2Vzc2lvbihzKS4gIA0KPiANCj4gVGhlIElFVEYgODkgcHJlbGlt
aW5hcnkgYWdlbmRhIGhhcyBiZWVuIHBvc3RlZC4gIFRoZSBmaW5hbCBhZ2VuZGEgd2lsbCBiZSBw
dWJsaXNoZWQgb24gRnJpZGF5LCBGZWJydWFyeSA3dGgsIDIwMTQuICANCj4gDQo+IElmIHlvdSB3
b3VsZCBsaWtlIHRvIHJlcXVlc3QgYSBjaGFuZ2UgdG8gdGhlIHByZWxpbWluYXJ5IGFnZW5kYSwg
cGxlYXNlIHNlbmQgYSBtZXNzYWdlIHRvIGFnZW5kYUBpZXRmLm9yZyBhbmQgY29weSBhbGwgcmVs
ZXZhbnQgQXJlYSBEaXJlY3RvcnMuDQo+IA0KPiBQbGVhc2Ugbm90ZSB0aGUgY3V0LW9mZiBkYXRl
IGZvciByZXF1ZXN0cyB0byByZXNjaGVkdWxlIFdvcmtpbmcgR3JvdXAgc2Vzc2lvbnMgYW5kIEJP
RnMgaXMgRmVicnVhcnkgM3JkLCAyMDE0IGF0IFVUQyAyMzo1OS4NCj4gDQo+IGh0dHBzOi8vZGF0
YXRyYWNrZXIuaWV0Zi5vcmcvbWVldGluZy84OS9hZ2VuZGEuaHRtbA0KPiBodHRwczovL2RhdGF0
cmFja2VyLmlldGYub3JnL21lZXRpbmcvODkvYWdlbmRhLnR4dA0KPiANCj4gVGhhbmsgeW91IQ0K
PiANCj4gSUVURiBTZWNyZXRhcmlhdA0KIAkJIAkgICAJCSAg

--_56063684-26df-46a9-977b-e0de90a65883_
Content-Type: text/html; charset="gb2312"
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxzdHlsZT48IS0tDQouaG1tZXNzYWdlIFANCnsNCm1hcmdpbjowcHg7
DQpwYWRkaW5nOjBweA0KfQ0KYm9keS5obW1lc3NhZ2UNCnsNCmZvbnQtc2l6ZTogMTJwdDsNCmZv
bnQtZmFtaWx5OkNhbGlicmkNCn0NCi0tPjwvc3R5bGU+PC9oZWFkPg0KPGJvZHkgY2xhc3M9J2ht
bWVzc2FnZSc+PGRpdiBkaXI9J2x0cic+SnVzdCB3YW5kZXJpbmcgd2hldGhlciBNSUYoTW9uZGF5
IG1vcm5pbmcpIGNhbiBiZSBleGNoYW5nZWQgd2l0aCBESEMoVGh1cnNkYXkgbW9ybmluZyk8QlI+
Jm5ic3A7PEJSPnRoYW5rczxCUj4mbmJzcDs8QlI+LUh1aTxicj4mbmJzcDs8QlI+PGRpdj4mZ3Q7
IEZyb206IGFnZW5kYUBpZXRmLm9yZzxicj4mZ3Q7IFRvOiB3Z2NoYWlyc0BpZXRmLm9yZzxicj4m
Z3Q7IFN1YmplY3Q6IElFVEYgODkgUHJlbGltaW5hcnkgQWdlbmRhPGJyPiZndDsgRGF0ZTogRnJp
LCAzMSBKYW4gMjAxNCAxNjo1NDo1MSAtMDgwMDxicj4mZ3Q7IENDOiBpcnNnQGlydGYub3JnPGJy
PiZndDsgPGJyPiZndDsgPGJyPiZndDsgTk9URTogWW91IHdpbGwgbm90IHJlY2VpdmUgYW4gYXV0
b21hdGljIG5vdGlmaWNhdGlvbiBpbmZvcm1pbmcgeW91IHRoYXQgeW91ciBzZXNzaW9uIGhhcyBi
ZWVuIHNjaGVkdWxlZC4gIFBsZWFzZSBzZWUgaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9t
ZWV0aW5nLzg5L2FnZW5kYS5odG1sIHRvIGRldGVybWluZSB0aGUgdGltZShzKSBvZiB5b3VyIHNl
c3Npb24ocykuICA8YnI+Jmd0OyA8YnI+Jmd0OyBUaGUgSUVURiA4OSBwcmVsaW1pbmFyeSBhZ2Vu
ZGEgaGFzIGJlZW4gcG9zdGVkLiAgVGhlIGZpbmFsIGFnZW5kYSB3aWxsIGJlIHB1Ymxpc2hlZCBv
biBGcmlkYXksIEZlYnJ1YXJ5IDd0aCwgMjAxNC4gIDxicj4mZ3Q7IDxicj4mZ3Q7IElmIHlvdSB3
b3VsZCBsaWtlIHRvIHJlcXVlc3QgYSBjaGFuZ2UgdG8gdGhlIHByZWxpbWluYXJ5IGFnZW5kYSwg
cGxlYXNlIHNlbmQgYSBtZXNzYWdlIHRvIGFnZW5kYUBpZXRmLm9yZyBhbmQgY29weSBhbGwgcmVs
ZXZhbnQgQXJlYSBEaXJlY3RvcnMuPGJyPiZndDsgPGJyPiZndDsgUGxlYXNlIG5vdGUgdGhlIGN1
dC1vZmYgZGF0ZSBmb3IgcmVxdWVzdHMgdG8gcmVzY2hlZHVsZSBXb3JraW5nIEdyb3VwIHNlc3Np
b25zIGFuZCBCT0ZzIGlzIEZlYnJ1YXJ5IDNyZCwgMjAxNCBhdCBVVEMgMjM6NTkuPGJyPiZndDsg
PGJyPiZndDsgaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9tZWV0aW5nLzg5L2FnZW5kYS5o
dG1sPGJyPiZndDsgaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9tZWV0aW5nLzg5L2FnZW5k
YS50eHQ8YnI+Jmd0OyA8YnI+Jmd0OyBUaGFuayB5b3UhPGJyPiZndDsgPGJyPiZndDsgSUVURiBT
ZWNyZXRhcmlhdDxicj48L2Rpdj4gCQkgCSAgIAkJICA8L2Rpdj48L2JvZHk+DQo8L2h0bWw+

--_56063684-26df-46a9-977b-e0de90a65883_--

From pkyzivat@alum.mit.edu  Fri Jan 31 20:07:12 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 241551A1F56 for <wgchairs@ietfa.amsl.com>; Fri, 31 Jan 2014 20:07:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wlehUPyxU6So for <wgchairs@ietfa.amsl.com>; Fri, 31 Jan 2014 20:07:11 -0800 (PST)
Received: from qmta07.westchester.pa.mail.comcast.net (qmta07.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:64]) by ietfa.amsl.com (Postfix) with ESMTP id E98C21A052C for <wgchairs@ietf.org>; Fri, 31 Jan 2014 20:07:10 -0800 (PST)
Received: from omta22.westchester.pa.mail.comcast.net ([76.96.62.73]) by qmta07.westchester.pa.mail.comcast.net with comcast id Ls5B1n0021ap0As57s76Mq; Sat, 01 Feb 2014 04:07:06 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta22.westchester.pa.mail.comcast.net with comcast id Ls761n0033ZTu2S3is76oz; Sat, 01 Feb 2014 04:07:06 +0000
Message-ID: <52EC72EA.7080205@alum.mit.edu>
Date: Fri, 31 Jan 2014 23:07:06 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: IETF Agenda <agenda@ietf.org>,  Working Group Chairs <wgchairs@ietf.org>
Subject: Re: IETF 89 Preliminary Agenda - STIR?
References: <20140201005451.8686.25003.idtracker@ietfa.amsl.com>
In-Reply-To: <20140201005451.8686.25003.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1391227626; bh=+Xy9Iok2wnkYk/xj7yjyYrNMAu+63xh6XV06CtBUhQ0=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=mHQWirJQSVQHQVE3nOL8Zq47gMuPTGwBS9K5exVVkk61fN9afpGl1pvmhfpu0qZ7l r0MwzxzBW97nWgpYcxIwklsCvBYLnxmgCXTh6JSMVOQeRz2amyanaPHpSJdWB32Q3+ HuC5bVrmfctHFgAB5/4Ac9LhWpTZ047Dd3uV72RHnJbYPSingcL5KTPnFbtPI3n1rx 70rWX1Ysmd9fmnxk5gfocBExbkvstrKCcACH6eT7wTJ/oidfAAnKPixAuyxSFoajRK 7gTf7wKgv6c7nvqOrfMaq3mKxNcL3rzA4CRQUJk3Ax9bdVrc6inAbEZSoftyEpH4hZ GqQ7WopNr3lGg==
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Feb 2014 04:07:12 -0000

I hate that stir is opposite mmusic.

Unfortunately there aren't any great matches, especially if it needs 2.5 
hrs.

Sunday?

	Thanks,
	Paul

On 1/31/14 7:54 PM, IETF Agenda wrote:
>
> NOTE: You will not receive an automatic notification informing you that your session has been scheduled.  Please see https://datatracker.ietf.org/meeting/89/agenda.html to determine the time(s) of your session(s).
>
> The IETF 89 preliminary agenda has been posted.  The final agenda will be published on Friday, February 7th, 2014.
>
> If you would like to request a change to the preliminary agenda, please send a message to agenda@ietf.org and copy all relevant Area Directors.
>
> Please note the cut-off date for requests to reschedule Working Group sessions and BOFs is February 3rd, 2014 at UTC 23:59.
>
> https://datatracker.ietf.org/meeting/89/agenda.html
> https://datatracker.ietf.org/meeting/89/agenda.txt
>
> Thank you!
>
> IETF Secretariat
>


From rjsparks@nostrum.com  Fri Jan 31 21:49:53 2014
Return-Path: <rjsparks@nostrum.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DC931A0530 for <wgchairs@ietfa.amsl.com>; Fri, 31 Jan 2014 21:49:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.036
X-Spam-Level: 
X-Spam-Status: No, score=-1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DMBwhWVWrbum for <wgchairs@ietfa.amsl.com>; Fri, 31 Jan 2014 21:49:52 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 581D61A052F for <wgchairs@ietf.org>; Fri, 31 Jan 2014 21:49:52 -0800 (PST)
Received: from unnumerable.local (pool-173-71-10-88.dllstx.fios.verizon.net [173.71.10.88]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id s115nmrq076589 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK) for <wgchairs@ietf.org>; Fri, 31 Jan 2014 23:49:48 -0600 (CST) (envelope-from rjsparks@nostrum.com)
Message-ID: <52EC8AFC.1020700@nostrum.com>
Date: Fri, 31 Jan 2014 23:49:48 -0600
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: IETF 89 Preliminary Agenda - STIR?
References: <20140201005451.8686.25003.idtracker@ietfa.amsl.com> <52EC72EA.7080205@alum.mit.edu>
In-Reply-To: <52EC72EA.7080205@alum.mit.edu>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.71.10.88 is authenticated by a trusted mechanism)
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Feb 2014 05:49:53 -0000

On 1/31/14, 10:07 PM, Paul Kyzivat wrote:
> I hate that stir is opposite mmusic.
>
> Unfortunately there aren't any great matches, especially if it needs 
> 2.5 hrs.
Stir requested 2 hours, but this seems to be the best fit for placing it.
MMUSIC has two sessions, which allows any work that has principal 
contributors in conflict to be scheduled in the other session.
Any other swap I can see doesn't have that property.

>
> Sunday?
>
>     Thanks,
>     Paul
>
> On 1/31/14 7:54 PM, IETF Agenda wrote:
>>
>> NOTE: You will not receive an automatic notification informing you 
>> that your session has been scheduled.  Please see 
>> https://datatracker.ietf.org/meeting/89/agenda.html to determine the 
>> time(s) of your session(s).
>>
>> The IETF 89 preliminary agenda has been posted.  The final agenda 
>> will be published on Friday, February 7th, 2014.
>>
>> If you would like to request a change to the preliminary agenda, 
>> please send a message to agenda@ietf.org and copy all relevant Area 
>> Directors.
>>
>> Please note the cut-off date for requests to reschedule Working Group 
>> sessions and BOFs is February 3rd, 2014 at UTC 23:59.
>>
>> https://datatracker.ietf.org/meeting/89/agenda.html
>> https://datatracker.ietf.org/meeting/89/agenda.txt
>>
>> Thank you!
>>
>> IETF Secretariat
>>
>

