
From nobody Wed Feb  1 10:12:53 2017
Return-Path: <henrik@levkowetz.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D86D6129517; Wed,  1 Feb 2017 10:12:41 -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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 OR33XUBAi9bq; Wed,  1 Feb 2017 10:12:40 -0800 (PST)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 02DB41294EF; Wed,  1 Feb 2017 10:12:38 -0800 (PST)
Received: from henrik by zinfandel.tools.ietf.org with local (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1cYzOX-0008FU-GY; Wed, 01 Feb 2017 10:12:37 -0800
To: codesprints@ietf.org, iesg@ietf.org, wgchairs@ietf.org
Subject: New datatracker release: v6.42.0
Message-Id: <E1cYzOX-0008FU-GY@zinfandel.tools.ietf.org>
From: Henrik Levkowetz <henrik@levkowetz.com>
Date: Wed, 01 Feb 2017 10:12:37 -0800
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Rcpt-To: codesprints@ietf.org, henrik@levkowetz.com, iesg@ietf.org,  wgchairs@ietf.org
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/W-CCJ7FXImFwEWBHG1AoHSXH--E>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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, 01 Feb 2017 18:12:42 -0000

Hi,

This is an automatic notification about a new datatracker release, 
v6.42.0, generated when running the mkrelease script.

Release notes:

ietfdb (6.42.0) ietf; urgency=medium

  **Django 1.9**

  This release upgrades the datatracker to use version 1.9 of the Django
  framework.  Django 1.9 provides pluggable password validation support,
  stricter template syntax (which prevents some common mistakes), simplified
  call syntax for some common API calls, better database consistency checks
  when creating many-to-many key relationship (preventing references to
  nonexistent entries), and more [a].  A full diff of the upgrade changes is
  available in changeset [12764].

  [a] https://docs.djangoproject.com/en/1.9/releases/1.9/

 -- Henrik Levkowetz <henrik@levkowetz.com>  31 Jan 2017 7:23:04 +0100

The new version is available for installation through SVN checkout, with
  'svn checkout https://svn.tools.ietf.org/svn/tools/ietfdb/tags/6.42.0'

For development, copy the new development version instead:
  'svn copy https://svn.tools.ietf.org/svn/tools/ietfdb/tags/dev/6.42.1.dev0' <YOURBRANCH>

Regards,

	Henrik
	(via the mkrelease script)


From nobody Tue Feb  7 13:40:12 2017
Return-Path: <akatlas@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9626D1294CC for <wgchairs@ietfa.amsl.com>; Tue,  7 Feb 2017 13:40:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 LG5uD9rR7hYH for <wgchairs@ietfa.amsl.com>; Tue,  7 Feb 2017 13:40:09 -0800 (PST)
Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 10E6C129492 for <wgchairs@ietf.org>; Tue,  7 Feb 2017 13:40:09 -0800 (PST)
Received: by mail-wm0-x229.google.com with SMTP id v186so29324943wmd.0 for <wgchairs@ietf.org>; Tue, 07 Feb 2017 13:40:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=w+3IHte39RikZqXKSIzqYmMntOWw1zpOBnFhvk7KA1A=; b=SJBZ3kWEwRCzDcSyHB6GjASdJUPkSIJ6NtHDdHLrOYqfmCINnDXg7ZgGW1uRXyscbK DYxDOq9pENu+fydXoub9CEJPyb4JS/z2U6RjfQj4TIYTx4yea0pX0usxSEa3Ix2b8L81 ELY2vLjL1fKR0SIv36rag9MtDfvieX93PPvmH1tA8UeCkjfVTDT/epsL2b07/P3dl7WP sRtcYTSPh0DwL1FcLyFUOIZHIOlb1+XxncfibMagB1CSRZJJthwlnnD8fT227ny6eKQb 8374lk3juHpHdOnLuY/oMuZkfKyCCZJQgjZ7rE4EQpXjFtW3Q9sfs791IFCseonXeVFS QEWw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=w+3IHte39RikZqXKSIzqYmMntOWw1zpOBnFhvk7KA1A=; b=G4pPsRTrVZx64C+c8tjwKBQf+W0k52n3UDbTma6ZFWk72AfFE1bYbq/akVjKwtSj5I DdZY0NqgKLJgPQjjyH5nRQIowLsZQvffRq2uX0G1HEzNB0shMUOpoDd7FU6RsawsnI9W qcBZGrW5Ad5DglGtxL5YruiS94mkAejREWrDKjcbWiAN8aSA3hkzOoUk4ui+rNqXJA9a GHG8ww5cKoKcFtVmBIvo0B24F9NqyOOS4QU/Qo0UVjSf26VuLBtlKuVnpXFlVmKcIoKd Wd7ZuVSbQcqlExhJTen0ZW/6KbLPPHvcz6RtMlNIqAkyPPsHgCN8TGbsm8FldGyQ8Ahr aB4g==
X-Gm-Message-State: AMke39n+ExqqN3dHfo7pcQgbIDcZCFSMVWDVkN+ICdf3cXLKjPusd8wTxprBA2KqH2YDizllRt39U3UKRUQBaQ==
X-Received: by 10.28.125.22 with SMTP id y22mr15268058wmc.112.1486503607429; Tue, 07 Feb 2017 13:40:07 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.142.108 with HTTP; Tue, 7 Feb 2017 13:40:07 -0800 (PST)
From: Alia Atlas <akatlas@gmail.com>
Date: Tue, 7 Feb 2017 16:40:07 -0500
Message-ID: <CAG4d1rffaTjQSLOQdBEaxt=4YTm_BeNf7RmHAqkM0Vhh_Ws9QQ@mail.gmail.com>
Subject: Small Group Discussion experiment in NVO3 from IETF 97
To: "wgchairs@ietf.org" <wgchairs@ietf.org>
Content-Type: multipart/alternative; boundary=001a1141e5c67a71a70547f79765
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/-hN9hoRO19f89LJNSZR9DO4zfBU>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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, 07 Feb 2017 21:40:10 -0000

--001a1141e5c67a71a70547f79765
Content-Type: text/plain; charset=UTF-8

At IETF 97, during the WG Chairs Lunch, we talked about experimenting with
different ways to hold effective meetings.  One experiment that NVO3 did
was break into separate small groups with different focuses for intense
"design-team like" discussion and then come together to summarize.

I've written up my perspective of this on the IESG wiki at:

https://trac.ietf.org/trac/iesg/wiki/MeetingExperiments

Regards,
Alia

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

<div dir=3D"ltr">At IETF 97, during the WG Chairs Lunch, we talked about ex=
perimenting with different ways to hold effective meetings.=C2=A0 One exper=
iment that NVO3 did was break into separate small groups with different foc=
uses for intense &quot;design-team like&quot; discussion and then come toge=
ther to summarize.<div><br></div><div>I&#39;ve written up my perspective of=
 this on the IESG wiki at:</div><div><br></div><div><a href=3D"https://trac=
.ietf.org/trac/iesg/wiki/MeetingExperiments">https://trac.ietf.org/trac/ies=
g/wiki/MeetingExperiments</a><br></div><div><br></div><div>Regards,</div><d=
iv>Alia</div></div>

--001a1141e5c67a71a70547f79765--


From nobody Tue Feb  7 15:42:21 2017
Return-Path: <jon.hudson@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A3A7129669 for <wgchairs@ietfa.amsl.com>; Tue,  7 Feb 2017 15:42:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 7x8MkmIVqoYf for <wgchairs@ietfa.amsl.com>; Tue,  7 Feb 2017 15:42:18 -0800 (PST)
Received: from mail-it0-x236.google.com (mail-it0-x236.google.com [IPv6:2607:f8b0:4001:c0b::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69B53129553 for <wgchairs@ietf.org>; Tue,  7 Feb 2017 15:42:18 -0800 (PST)
Received: by mail-it0-x236.google.com with SMTP id c7so88932357itd.1 for <wgchairs@ietf.org>; Tue, 07 Feb 2017 15:42:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=H81Zng70iigbGXgtwp0fvUlp6SU0rLM67G1jfhwxSx0=; b=FdvfvXcSOYEtXEdkNF5vb3aXPgj5QXph2LRLa0tnG4TrqCXP6Vm3tLV2iZFpq0U0xh uVcH8UL1nDuxx7aksZkGUZ+s+8oMazD29xhW6mymTqxPrvqC6PAX6HO5CjAIjj56hhEC JNDVF7jwkspEapxsrLzKd1E5jyDYm4uZ3FUapIAJtNtmgU4JuUQZMey1xoXdZ/h7oLYx CjLMCVdGx6xa/s1+zrGLIABjO7ZV2rKr+RpILj6PLhNZB4zsWkPyz38tuoVI49C8ASON bu4rEOz8mmtdu0CD3Z6aI2ABU3lDwerls2xDthmvM61BkIp3b9c6vY41fpWHKO3D1CDQ yeQg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=H81Zng70iigbGXgtwp0fvUlp6SU0rLM67G1jfhwxSx0=; b=IZGq11zoi243KJZTDeJAFu17YfPvZSM63TRPjwNBpjDwYVPTLou+gGuX4mxHLphzlc 4RhUpK9JiJkXbARtKTkt0+P/V8AnWKcFqcC13PWhlLz0aQTdIOYUW6DyGSy/NsSgedpc RIoqXCdqHkeVIoANew+CXzyqCcabiwd+lmFCclL1kuKyBDJgDP/Oy7TtpCsQyq2sH1u/ WNd37JGNOC0Jyzy+ZGkorQR0Z3gXIoJILLU7Y0vpbuT2UeRrf3I16Gi8p/zuaBZ/lJe6 w6MG3QpTWltl4H7Bvhs+JXANMWcBy0Qhcpsuo1tuZF/6ZfVSC1yWGc5zL/X8EX3BDVA3 OvdQ==
X-Gm-Message-State: AIkVDXJeamWN2b6GQiQupjnSqUOeCQ9S7QqpdB715Xnmi/fgUDN2xgvXM+fktc00zPueN1iX0LtARV210bhSxw==
X-Received: by 10.36.0.69 with SMTP id 66mr14832968ita.31.1486510937746; Tue, 07 Feb 2017 15:42:17 -0800 (PST)
MIME-Version: 1.0
Received: by 10.79.26.133 with HTTP; Tue, 7 Feb 2017 15:42:17 -0800 (PST)
In-Reply-To: <CAG4d1rffaTjQSLOQdBEaxt=4YTm_BeNf7RmHAqkM0Vhh_Ws9QQ@mail.gmail.com>
References: <CAG4d1rffaTjQSLOQdBEaxt=4YTm_BeNf7RmHAqkM0Vhh_Ws9QQ@mail.gmail.com>
From: Jon Hudson <jon.hudson@gmail.com>
Date: Tue, 7 Feb 2017 15:42:17 -0800
Message-ID: <CANbjNQFLDk9sKU0+cgHjX56wCJ_xvAgCP-JZvKUdFpxjEiw_Vw@mail.gmail.com>
Subject: Re: Small Group Discussion experiment in NVO3 from IETF 97
To: Alia Atlas <akatlas@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c13fe46636500547f94c2f
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/kchNm5qbmAyG30yrkPkG_0aScxs>
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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, 07 Feb 2017 23:42:20 -0000

--001a11c13fe46636500547f94c2f
Content-Type: text/plain; charset=UTF-8

So first off, Thank You! The apathy being experienced was difficult and
this seems to be have been a great catalyst.

This part:

4) One group ended up with a facilitator doing more lecturing and
explaining, but even in that group - no one was looking at laptops and
everyone seemed interested and engaged.

5) One group had 5-6 people coming up and drawing different scenarios and
actively brainstorming together.

6) The third group had the facilitator primarily writing but a front row of
5-6 people discussing and others actively listening and learning.

Is especially interesting and almost implies that dividing into method
groups instead of topic groups could be interesting.

I also wonder if we got lucky on the topics bubbling up. Sometimes the
issues that need to be worked on are not issues folks
feel comfortable taking about in the grand forum. If other WGs take try
this method, it will be interesting to see how topic selection goes and
what impact it has on individual WG success.

All and all awesome trial and much appreciated writeup.

My only concern is how motivation looks moving this forward. For example,
if folks knew that more "formal" design teams would be selected from
these exercises would less people have left when the process started? Or is
that the wrong motivator?

I would also add that I am not sure mail lists are the best way to continue
this as there is often more motivating someone not to speak up on a mail
list than there is motivation to do so. However I am not saying that group
phone calls work either as I have experienced those going VERY well and
VERY poorly depending from my view on the facilitator (quick shout to Erik
Nordmark who does this VERY well). And perhaps if energy is restored in a
subsequent meeting, then perhaps the activity has served it's purpose as a
stand along event.

My point is that in some cases to get the most out of these methods when
used we may need to be as creative and experimental with what the follow up
activity is as you were getting this going.

Finally, on a very personal note: YA!!!!!!
Jon


On Tue, Feb 7, 2017 at 1:40 PM, Alia Atlas <akatlas@gmail.com> wrote:

> At IETF 97, during the WG Chairs Lunch, we talked about experimenting with
> different ways to hold effective meetings.  One experiment that NVO3 did
> was break into separate small groups with different focuses for intense
> "design-team like" discussion and then come together to summarize.
>
> I've written up my perspective of this on the IESG wiki at:
>
> https://trac.ietf.org/trac/iesg/wiki/MeetingExperiments
>
> Regards,
> Alia
>



-- 
"Do not lie. And do not do what you hate."

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

<div dir=3D"ltr"><br><div><font face=3D"arial, helvetica, sans-serif">So fi=
rst off, Thank You! The apathy being experienced was difficult and this see=
ms to be have been a great catalyst.=C2=A0</font></div><div><font face=3D"a=
rial, helvetica, sans-serif"><br></font></div><div><font face=3D"arial, hel=
vetica, sans-serif">This part:</font></div><div><blockquote style=3D"color:=
rgb(0,0,0);font-size:13px"><p><font face=3D"arial, helvetica, sans-serif">4=
) One group ended up with a facilitator doing more lecturing and explaining=
, but even in that group - no one was looking at laptops and everyone seeme=
d interested and engaged.<br></font></p></blockquote><blockquote style=3D"c=
olor:rgb(0,0,0);font-size:13px"><p><font face=3D"arial, helvetica, sans-ser=
if">5) One group had 5-6 people coming up and drawing different scenarios a=
nd actively brainstorming together.<br></font></p></blockquote><blockquote =
style=3D"color:rgb(0,0,0);font-size:13px"><p><font face=3D"arial, helvetica=
, sans-serif">6) The third group had the facilitator primarily writing but =
a front row of 5-6 people discussing and others actively listening and lear=
ning.</font></p></blockquote><font color=3D"#000000" face=3D"arial, helveti=
ca, sans-serif">Is especially interesting and almost implies that dividing =
into method groups instead of topic groups could be interesting.=C2=A0</fon=
t></div><div><font color=3D"#000000" face=3D"arial, helvetica, sans-serif">=
<br></font></div><div><font color=3D"#000000" face=3D"arial, helvetica, san=
s-serif">I also wonder if we got lucky on the topics bubbling up. Sometimes=
 the issues that need to be worked on are not issues folks feel=C2=A0comfor=
table=C2=A0taking about in the grand forum. If other WGs take try this meth=
od, it will be interesting to see how topic selection goes and what impact =
it has on individual WG success.=C2=A0</font></div><div><font color=3D"#000=
000" face=3D"arial, helvetica, sans-serif"><br></font></div><div><font colo=
r=3D"#000000" face=3D"arial, helvetica, sans-serif">All and all awesome tri=
al and much appreciated writeup.=C2=A0</font></div><div><font color=3D"#000=
000" face=3D"arial, helvetica, sans-serif"><br></font></div><div><font colo=
r=3D"#000000" face=3D"arial, helvetica, sans-serif">My only concern is how=
=C2=A0motivation looks moving this forward. For example, if folks knew that=
 more &quot;formal&quot; design teams would be selected from these=C2=A0exe=
rcises would less people have left when the process started? Or is that the=
 wrong motivator?=C2=A0</font></div><div><font color=3D"#000000" face=3D"ar=
ial, helvetica, sans-serif"><br></font></div><div><font color=3D"#000000" f=
ace=3D"arial, helvetica, sans-serif">I would also add that I am not sure ma=
il lists are the best way to=C2=A0continue this as there is often more=C2=
=A0motivating someone not to speak up on a mail list than there is motivati=
on to do so. However I am not=C2=A0saying that=C2=A0group phone calls work =
either as I have=C2=A0experienced those going VERY well and VERY poorly dep=
ending from my view on the=C2=A0facilitator (quick shout to Erik Nordmark w=
ho does this VERY well). And perhaps if=C2=A0energy is=C2=A0restored in a s=
ubsequent meeting, then perhaps the activity has served it&#39;s=C2=A0purpo=
se as a stand along event.=C2=A0</font></div><div><font color=3D"#000000" f=
ace=3D"arial, helvetica, sans-serif"><br></font></div><div><font color=3D"#=
000000" face=3D"arial, helvetica, sans-serif">My point is that in some case=
s to get the most out of these methods when used we may=C2=A0need to be as =
creative and=C2=A0experimental with what the follow up activity is as you w=
ere getting this going.=C2=A0</font></div><div><font color=3D"#000000" face=
=3D"arial, helvetica, sans-serif"><br></font></div><div><font color=3D"#000=
000" face=3D"arial, helvetica, sans-serif">Finally, on a very personal note=
: YA!!!!!!</font></div><div><font color=3D"#000000" face=3D"arial, helvetic=
a, sans-serif">Jon</font></div><div><blockquote style=3D"color:rgb(0,0,0);f=
ont-size:13px"></blockquote></div><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Tue, Feb 7, 2017 at 1:40 PM, Alia Atlas <span dir=3D"lt=
r">&lt;<a href=3D"mailto:akatlas@gmail.com" target=3D"_blank">akatlas@gmail=
.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"lt=
r">At IETF 97, during the WG Chairs Lunch, we talked about experimenting wi=
th different ways to hold effective meetings.=C2=A0 One experiment that NVO=
3 did was break into separate small groups with different focuses for inten=
se &quot;design-team like&quot; discussion and then come together to summar=
ize.<div><br></div><div>I&#39;ve written up my perspective of this on the I=
ESG wiki at:</div><div><br></div><div><a href=3D"https://trac.ietf.org/trac=
/iesg/wiki/MeetingExperiments" target=3D"_blank">https://trac.ietf.org/trac=
/<wbr>iesg/wiki/MeetingExperiments</a><br></div><div><br></div><div>Regards=
,</div><div>Alia</div></div>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div class=
=3D"gmail_signature" data-smartmail=3D"gmail_signature">&quot;Do not lie. A=
nd do not do what you hate.&quot;<br></div>
</div></div>

--001a11c13fe46636500547f94c2f--


From nobody Thu Feb  9 00:48:28 2017
Return-Path: <mnot@mnot.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0426212973D for <wgchairs@ietfa.amsl.com>; Thu,  9 Feb 2017 00:48:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.878
X-Spam-Level: 
X-Spam-Status: No, score=-0.878 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_SBL=1.623, URIBL_SBL_A=0.1] autolearn=ham autolearn_force=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 l8PetsByFBw0 for <wgchairs@ietfa.amsl.com>; Thu,  9 Feb 2017 00:48:24 -0800 (PST)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EFC9512955D for <wgchairs@ietf.org>; Thu,  9 Feb 2017 00:48:23 -0800 (PST)
Received: from [192.168.3.104] (unknown [124.189.98.244]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 41D4722E256; Thu,  9 Feb 2017 03:48:16 -0500 (EST)
From: Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Remote participation in interims -- experiences
Message-Id: <3F2DBCB9-3D94-4DC3-A598-F0DC2B63D996@mnot.net>
Date: Thu, 9 Feb 2017 19:48:07 +1100
To: IETF WG Chairs <wgchairs@ietf.org>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/y6_RJxieH0tc9v4QtFFxJwuqbxE>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2017 08:48:27 -0000

Hi everyone,

We had a QUIC Interim meeting a couple of weeks back, supporting remote =
participants through WebEx. I thought it might be useful to summarise =
how we did it and what the feedback was, for other WGs' possible =
benefit. Feel free to ignore.

The meeting was hosted at Akamai's office in Tokyo, which I think is a =
fairly typical tech company sales-oriented office in a major city. The =
meeting took place in a large training room.


## Room setup

We wanted to facilitate open discussion among participants. In the past, =
WGs I've been involved with have done this using a boardroom or U-shape =
setup, but we had 50 (!) people register for the Interim. So, we used a =
series of concentric "U" shapes, with the chairs at a table at the open =
end of the "U" and the projection screens behind them.

This seemed to work pretty well; people could see and hear each other =
easily, and we had active engagement from people in the "outer" tiers =
(the document editors and very active participants tended to sit in the =
"centre" tier).

One thing that really helped was the tables; the room had a large number =
of two-person table/desks on rollers that we could configure how we =
liked. That let us tweak the setup to get the right density and layout.

The room was quite large, so we tightened things up a bit and closed a =
divider wall to make the space smaller, so that it was easier to see and =
hear, both for local and remote participants.


## A/V

Other WGs Iv'e been involved in have run Interims with remote =
participation before, but the experience was generally pretty bad, and =
few people took us up on it. Those that did tended to be silent, and to =
leave the meeting early.

For this meeting, we had a sizeable number of people (15-20) register =
for remote participation, with several of them key participants (e.g., =
document editors). So, we had to provide a better experience.

Originally we wanted to use in-room videoconferencing (the room has =
multiple built-in cameras and an array of ceiling microphones), but that =
was a proprietary system that isn't easily available to non-employees.

Instead, we used:

- A dedicated computer: Having a dedicated computer was really helpful. =
I used an old MacBook Air; the only problem was that it only has two USB =
ports, meaning that we needed to unplug the camera to put a USB stick in =
to transfer a presentation. Next time, I'll bring a USB hub.

- Microphone: We used one of these: =
<http://www.mxlmics.com/microphones/web-conferencing/AC-404/> and it =
worked really well. It has an advertised range of 8m / 25ft, and the =
remote participants didn't seem to have any problem following =
conversation (once or twice they couldn't hear someone, but we also =
couldn't hear that person in the room - we just asked them to speak up). =
In a larger room, I'd probably use a pair of them and mux them in the OS =
(possible in both Windows and Mac with appropriate extensions / =
configuration). It cost me AU$147, I think it's available in the US for =
US$80.

- Camera: I used a =
<http://www.logitech.com/en-us/product/c922-pro-stream-webcam?crid=3D34>, =
but I'd actually prefer =
<http://www.logitech.com/en-us/product/12131?crid=3D34> due to its wider =
angle. Both do H.264 on-camera. The one I got came with a miniature =
tabletop tripod, which was very useful. Somewhere around AU$100.

- Speakers: We used the room's speakers (over HDMI, along with the =
projector); otherwise, I brought a pair of USB-powered speakers. A =
bluetooth speaker would also work, if the battery lasted long enough or =
if we plugged it in.

- WebEx: As provided through the Secretariat.


## Feedback

Afterwards, we ran a survey of remote participants to gather their =
feedback. The results are here:
  https://mnot.wufoo.com/reports/january-2017-quic-interim-feedback/
(please don't share this link widely; the people who responded were made =
aware that it would be shared with Chairs and IESG, but not further)

As you can see, people had somewhat conflicting experiences, but the =
overall feedback seems pretty positive, considering that remote =
participation is always going to be challenging (especially for a 3-day =
meeting).


## How we can Improve

My takeaways for making it better next time:

1) I'm not thrilled about buying another camera so soon after buying a =
new one (and that replaced a perfectly good one :), but many people =
mentioned the angle of view. I'm not sure how much video actually helps =
with remote participation, beyond establishing a "feel" of how the room =
looks (unless there's whiteboard work, obviously).

2) A tripod capable of being placed on the floor might help get a better =
camera angle.

3) A second USB mic will probably help, especially with more challenging =
audio environments. That said, the mic we chose is remarkably good.

4) Having a dedicated way to let a remote participant "raise their hand" =
-- even if it's just having someone watch Jabber -- would probably be =
good. That said, remote folks who had video didn't seem to have any =
problem with this, because WebEx "hears" when they're becoming active, =
and their window becomes prominent.

5) We could do a better job communicating the channels for remote =
participants and their details beforehand.


Hope this helps,


--
Mark Nottingham   https://www.mnot.net/


From nobody Thu Feb  9 12:37:13 2017
Return-Path: <mnot@mnot.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9822129452 for <wgchairs@ietfa.amsl.com>; Thu,  9 Feb 2017 12:37:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.878
X-Spam-Level: 
X-Spam-Status: No, score=-0.878 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_SBL=1.623, URIBL_SBL_A=0.1] autolearn=ham autolearn_force=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 pnAt07ogTQa6 for <wgchairs@ietfa.amsl.com>; Thu,  9 Feb 2017 12:37:07 -0800 (PST)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DFA912706D for <wgchairs@ietf.org>; Thu,  9 Feb 2017 12:37:07 -0800 (PST)
Received: from [192.168.3.100] (unknown [124.189.98.244]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id A0CD822E25B for <wgchairs@ietf.org>; Thu,  9 Feb 2017 15:37:00 -0500 (EST)
From: Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Remote participation in interims -- experiences
Date: Fri, 10 Feb 2017 07:36:56 +1100
References: <3F2DBCB9-3D94-4DC3-A598-F0DC2B63D996@mnot.net>
To: IETF WG Chairs <wgchairs@ietf.org>
In-Reply-To: <3F2DBCB9-3D94-4DC3-A598-F0DC2B63D996@mnot.net>
Message-Id: <709DEAB3-E035-4074-9807-22CE0236C93B@mnot.net>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/45bnJaTJVG8x9PynoQMUO10Z3Rc>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2017 20:37:11 -0000

Link made public now, sorry!

https://mnot.wufoo.com/reports/january-2017-quic-interim-feedback/


> On 9 Feb 2017, at 7:48 pm, Mark Nottingham <mnot@mnot.net> wrote:
>=20
> Hi everyone,
>=20
> We had a QUIC Interim meeting a couple of weeks back, supporting =
remote participants through WebEx. I thought it might be useful to =
summarise how we did it and what the feedback was, for other WGs' =
possible benefit. Feel free to ignore.
>=20
> The meeting was hosted at Akamai's office in Tokyo, which I think is a =
fairly typical tech company sales-oriented office in a major city. The =
meeting took place in a large training room.
>=20
>=20
> ## Room setup
>=20
> We wanted to facilitate open discussion among participants. In the =
past, WGs I've been involved with have done this using a boardroom or =
U-shape setup, but we had 50 (!) people register for the Interim. So, we =
used a series of concentric "U" shapes, with the chairs at a table at =
the open end of the "U" and the projection screens behind them.
>=20
> This seemed to work pretty well; people could see and hear each other =
easily, and we had active engagement from people in the "outer" tiers =
(the document editors and very active participants tended to sit in the =
"centre" tier).
>=20
> One thing that really helped was the tables; the room had a large =
number of two-person table/desks on rollers that we could configure how =
we liked. That let us tweak the setup to get the right density and =
layout.
>=20
> The room was quite large, so we tightened things up a bit and closed a =
divider wall to make the space smaller, so that it was easier to see and =
hear, both for local and remote participants.
>=20
>=20
> ## A/V
>=20
> Other WGs Iv'e been involved in have run Interims with remote =
participation before, but the experience was generally pretty bad, and =
few people took us up on it. Those that did tended to be silent, and to =
leave the meeting early.
>=20
> For this meeting, we had a sizeable number of people (15-20) register =
for remote participation, with several of them key participants (e.g., =
document editors). So, we had to provide a better experience.
>=20
> Originally we wanted to use in-room videoconferencing (the room has =
multiple built-in cameras and an array of ceiling microphones), but that =
was a proprietary system that isn't easily available to non-employees.
>=20
> Instead, we used:
>=20
> - A dedicated computer: Having a dedicated computer was really =
helpful. I used an old MacBook Air; the only problem was that it only =
has two USB ports, meaning that we needed to unplug the camera to put a =
USB stick in to transfer a presentation. Next time, I'll bring a USB =
hub.
>=20
> - Microphone: We used one of these: =
<http://www.mxlmics.com/microphones/web-conferencing/AC-404/> and it =
worked really well. It has an advertised range of 8m / 25ft, and the =
remote participants didn't seem to have any problem following =
conversation (once or twice they couldn't hear someone, but we also =
couldn't hear that person in the room - we just asked them to speak up). =
In a larger room, I'd probably use a pair of them and mux them in the OS =
(possible in both Windows and Mac with appropriate extensions / =
configuration). It cost me AU$147, I think it's available in the US for =
US$80.
>=20
> - Camera: I used a =
<http://www.logitech.com/en-us/product/c922-pro-stream-webcam?crid=3D34>, =
but I'd actually prefer =
<http://www.logitech.com/en-us/product/12131?crid=3D34> due to its wider =
angle. Both do H.264 on-camera. The one I got came with a miniature =
tabletop tripod, which was very useful. Somewhere around AU$100.
>=20
> - Speakers: We used the room's speakers (over HDMI, along with the =
projector); otherwise, I brought a pair of USB-powered speakers. A =
bluetooth speaker would also work, if the battery lasted long enough or =
if we plugged it in.
>=20
> - WebEx: As provided through the Secretariat.
>=20
>=20
> ## Feedback
>=20
> Afterwards, we ran a survey of remote participants to gather their =
feedback. The results are here:
>  https://mnot.wufoo.com/reports/january-2017-quic-interim-feedback/
> (please don't share this link widely; the people who responded were =
made aware that it would be shared with Chairs and IESG, but not =
further)
>=20
> As you can see, people had somewhat conflicting experiences, but the =
overall feedback seems pretty positive, considering that remote =
participation is always going to be challenging (especially for a 3-day =
meeting).
>=20
>=20
> ## How we can Improve
>=20
> My takeaways for making it better next time:
>=20
> 1) I'm not thrilled about buying another camera so soon after buying a =
new one (and that replaced a perfectly good one :), but many people =
mentioned the angle of view. I'm not sure how much video actually helps =
with remote participation, beyond establishing a "feel" of how the room =
looks (unless there's whiteboard work, obviously).
>=20
> 2) A tripod capable of being placed on the floor might help get a =
better camera angle.
>=20
> 3) A second USB mic will probably help, especially with more =
challenging audio environments. That said, the mic we chose is =
remarkably good.
>=20
> 4) Having a dedicated way to let a remote participant "raise their =
hand" -- even if it's just having someone watch Jabber -- would probably =
be good. That said, remote folks who had video didn't seem to have any =
problem with this, because WebEx "hears" when they're becoming active, =
and their window becomes prominent.
>=20
> 5) We could do a better job communicating the channels for remote =
participants and their details beforehand.
>=20
>=20
> Hope this helps,
>=20
>=20
> --
> Mark Nottingham   https://www.mnot.net/
>=20

--
Mark Nottingham   https://www.mnot.net/





From nobody Fri Feb 10 02:52:45 2017
Return-Path: <henrik@levkowetz.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F341212711D; Fri, 10 Feb 2017 02:52:36 -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 autolearn_force=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 DWAtj4ek0MZl; Fri, 10 Feb 2017 02:52:35 -0800 (PST)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 926401270B4; Fri, 10 Feb 2017 02:52:35 -0800 (PST)
Received: from henrik by zinfandel.tools.ietf.org with local (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1cc8od-0004OC-DV; Fri, 10 Feb 2017 02:52:35 -0800
To: codesprints@ietf.org, iesg@ietf.org, wgchairs@ietf.org
Subject: New datatracker release: v6.43.0
Message-Id: <E1cc8od-0004OC-DV@zinfandel.tools.ietf.org>
From: Henrik Levkowetz <henrik@levkowetz.com>
Date: Fri, 10 Feb 2017 02:52:35 -0800
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Rcpt-To: codesprints@ietf.org, henrik@levkowetz.com, iesg@ietf.org,  wgchairs@ietf.org
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/MhSvy_wzaGsCIu_eRfLqT1zd6Xo>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 10:52:37 -0000

Hi,

This is an automatic notification about a new datatracker release, 
v6.43.0, generated when running the mkrelease script.

Release notes:

ietfdb (6.43.0) ietf; urgency=medium

  **Password Strength Meter**

  This release provides a zxcvbn-based password strenght meter when setting
  or changing a datatracker user password, and changes the default password
  hasher from PBKDF2 to BCrypt.  It adds support for datatracker management
  of additional wikis,  and changes the management of bower-packaged web
  assets to updating them to the latest minor release on each new datatracker
  release.  It also fixes a few bugs, and tweaks the IPR declaration pages to
  provide more complete information for declarations which indicate that 
  licensing conditions will be provided later.

  From the commit log:

  * Added a change password page, and linked to it from the account profile 
    page and user menu.  Added zxcvbn-based browser-side password strength 
    estimation on the various password setting, re-setting, and changing forms. 
    Added a change password test.  Changed ietfauth/urls.py to not use the 
    deprecated string form for views in urlpatterns.

  * Re-styled some auth-related forms to use a narrower form body on large 
    screens, for aesthethic reasons.

  * Added an explicit setting for the password hashers to use, in order to 
    place the bcrypt hasher first.  This makes BCrypt the default hasher.  
    Added the django_password_strength app to installed apps.

  * Added the zxcvbn bower component, for use in client-side password 
    strength estimation.

  * Added django-bcrypt (for bcrypt password hashing) and 
    django-password-strength (for browser-side zxcvbn password strength 
    estimation) to the requirements.

  * Added ordering for nomcom  Nominee objects.

  * Expanded the Nominee __unicode__() method to provide unique results by 
    including the nomcom year.

  * Tweaked the IPR Details page to show the possible a), b), and c) 
    choices under section 'V' when licensing declaration to be provided later 
    has been chosen.

  * Added a guard to prevent trying to get a document path for a meeting 
    document when the document is not associated with a meeting session.

  * Added support for management of trac wikis for explicitly named groups, 
    such as the IESG and IAOC.  Tweaked the dummy-run handling of the 
    create_group_wikis management command.

  * Added updating of static web assets to the release script.

  * Fixed a bug in a queryset argument in all_id_text(); __in was not used, 
    but the value given was a multi-row queryset.

  * @register.simple_tag now (in Django 1.9) needs explicit mark_safe() (or 
    format_html() which invokes mark_safe()).  Fixed one case which needed this.

 -- Henrik Levkowetz <henrik@levkowetz.com>  09 Feb 2017 09:03:53 -0800

The new version is available for installation through SVN checkout, with
  'svn checkout https://svn.tools.ietf.org/svn/tools/ietfdb/tags/6.43.0'

For development, copy the new development version instead:
  'svn copy https://svn.tools.ietf.org/svn/tools/ietfdb/tags/dev/6.43.1.dev0' <YOURBRANCH>

Regards,

	Henrik
	(via the mkrelease script)


From nobody Fri Feb 10 06:03:06 2017
Return-Path: <mlarson@amsl.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 493D8129978; Fri, 10 Feb 2017 06:02:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 7HRLUUuamn3F; Fri, 10 Feb 2017 06:02:56 -0800 (PST)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D8DEC1295EA; Fri, 10 Feb 2017 06:02:56 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 92B521E566B; Fri, 10 Feb 2017 06:02:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1-SNUIbGgAGa; Fri, 10 Feb 2017 06:02:33 -0800 (PST)
Received: from [192.168.0.6] (50-89-234-39.res.bhn.net [50.89.234.39]) by c8a.amsl.com (Postfix) with ESMTPA id 0036D1E5666; Fri, 10 Feb 2017 06:02:32 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [codesprints] New datatracker release: v6.43.0
From: Matt Larson <mlarson@amsl.com>
In-Reply-To: <E1cc8od-0004OC-DV@zinfandel.tools.ietf.org>
Date: Fri, 10 Feb 2017 09:02:55 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <E40C24C9-8D77-4396-95EB-40C6A45DD5E2@amsl.com>
References: <E1cc8od-0004OC-DV@zinfandel.tools.ietf.org>
To: Henrik Levkowetz <henrik@levkowetz.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/t9slUfIww0yZFtrmotpTeqjSoaw>
Cc: wgchairs@ietf.org, codesprints@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 14:02:58 -0000

Greetings all!

Datatracker 6.43.0 has been deployed to production.
Datatracker 6.43.1.dev0 has been deployed to the sandbox.

Matt

> On Feb 10, 2017, at 5:52 AM, Henrik Levkowetz <henrik@levkowetz.com> =
wrote:
>=20
>=20
> Hi,
>=20
> This is an automatic notification about a new datatracker release,=20
> v6.43.0, generated when running the mkrelease script.
>=20
> Release notes:
>=20
> ietfdb (6.43.0) ietf; urgency=3Dmedium
>=20
>  **Password Strength Meter**
>=20
>  This release provides a zxcvbn-based password strenght meter when =
setting
>  or changing a datatracker user password, and changes the default =
password
>  hasher from PBKDF2 to BCrypt.  It adds support for datatracker =
management
>  of additional wikis,  and changes the management of bower-packaged =
web
>  assets to updating them to the latest minor release on each new =
datatracker
>  release.  It also fixes a few bugs, and tweaks the IPR declaration =
pages to
>  provide more complete information for declarations which indicate =
that=20
>  licensing conditions will be provided later.
>=20
>  =46rom the commit log:
>=20
>  * Added a change password page, and linked to it from the account =
profile=20
>    page and user menu.  Added zxcvbn-based browser-side password =
strength=20
>    estimation on the various password setting, re-setting, and =
changing forms.=20
>    Added a change password test.  Changed ietfauth/urls.py to not use =
the=20
>    deprecated string form for views in urlpatterns.
>=20
>  * Re-styled some auth-related forms to use a narrower form body on =
large=20
>    screens, for aesthethic reasons.
>=20
>  * Added an explicit setting for the password hashers to use, in order =
to=20
>    place the bcrypt hasher first.  This makes BCrypt the default =
hasher. =20
>    Added the django_password_strength app to installed apps.
>=20
>  * Added the zxcvbn bower component, for use in client-side password=20=

>    strength estimation.
>=20
>  * Added django-bcrypt (for bcrypt password hashing) and=20
>    django-password-strength (for browser-side zxcvbn password strength=20=

>    estimation) to the requirements.
>=20
>  * Added ordering for nomcom  Nominee objects.
>=20
>  * Expanded the Nominee __unicode__() method to provide unique results =
by=20
>    including the nomcom year.
>=20
>  * Tweaked the IPR Details page to show the possible a), b), and c)=20
>    choices under section 'V' when licensing declaration to be provided =
later=20
>    has been chosen.
>=20
>  * Added a guard to prevent trying to get a document path for a =
meeting=20
>    document when the document is not associated with a meeting =
session.
>=20
>  * Added support for management of trac wikis for explicitly named =
groups,=20
>    such as the IESG and IAOC.  Tweaked the dummy-run handling of the=20=

>    create_group_wikis management command.
>=20
>  * Added updating of static web assets to the release script.
>=20
>  * Fixed a bug in a queryset argument in all_id_text(); __in was not =
used,=20
>    but the value given was a multi-row queryset.
>=20
>  * @register.simple_tag now (in Django 1.9) needs explicit mark_safe() =
(or=20
>    format_html() which invokes mark_safe()).  Fixed one case which =
needed this.
>=20
> -- Henrik Levkowetz <henrik@levkowetz.com>  09 Feb 2017 09:03:53 -0800
>=20
> The new version is available for installation through SVN checkout, =
with
>  'svn checkout =
https://svn.tools.ietf.org/svn/tools/ietfdb/tags/6.43.0'
>=20
> For development, copy the new development version instead:
>  'svn copy =
https://svn.tools.ietf.org/svn/tools/ietfdb/tags/dev/6.43.1.dev0' =
<YOURBRANCH>
>=20
> Regards,
>=20
> 	Henrik
> 	(via the mkrelease script)
>=20
> _______________________________________________
> codesprints mailing list
> codesprints@ietf.org
> https://www.ietf.org/mailman/listinfo/codesprints
>=20

-------------------------------------------
Matthew Larson, Software Engineer
Association Management Solutions
Forum Management, Meeting and Event Planning
5177 Brandin Court
Fremont, CA  94538


From nobody Fri Feb 10 07:15:49 2017
Return-Path: <henrik@levkowetz.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFFAF1299CB; Fri, 10 Feb 2017 07:15:40 -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 autolearn_force=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 nz9U6k_z5qaK; Fri, 10 Feb 2017 07:15:39 -0800 (PST)
Received: from durif.tools.ietf.org (durif.tools.ietf.org [IPv6:2001:1900:3001:11::3d]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 921C31293EB; Fri, 10 Feb 2017 07:15:39 -0800 (PST)
Received: from h-43-30.a357.priv.bahnhof.se ([79.136.43.30]:49730 helo=[192.168.1.120]) by durif.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1ccCvC-0001Z7-GS; Fri, 10 Feb 2017 07:15:39 -0800
To: Matt Larson <mlarson@amsl.com>
References: <E1cc8od-0004OC-DV@zinfandel.tools.ietf.org> <E40C24C9-8D77-4396-95EB-40C6A45DD5E2@amsl.com>
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <589DD90B.2040505@levkowetz.com>
Date: Fri, 10 Feb 2017 16:15:23 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <E40C24C9-8D77-4396-95EB-40C6A45DD5E2@amsl.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="o36gBf8lI1dPlPgMi5RtSlOtvTTNatOPE"
X-SA-Exim-Connect-IP: 79.136.43.30
X-SA-Exim-Rcpt-To: codesprints@ietf.org, wgchairs@ietf.org, mlarson@amsl.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
Subject: Re: [codesprints] New datatracker release: v6.43.0
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on durif.tools.ietf.org)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/-CueK9m3x5NTQ0zjJSjvJk_0b_U>
Cc: wgchairs@ietf.org, codesprints@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 15:15:41 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--o36gBf8lI1dPlPgMi5RtSlOtvTTNatOPE
Content-Type: multipart/mixed; boundary="BhEFv1CLa2RN5k3CnaGn376edGtGXGVD1";
 protected-headers="v1"
From: Henrik Levkowetz <henrik@levkowetz.com>
To: Matt Larson <mlarson@amsl.com>
Cc: wgchairs@ietf.org, codesprints@ietf.org
Message-ID: <589DD90B.2040505@levkowetz.com>
Subject: Re: [codesprints] New datatracker release: v6.43.0
References: <E1cc8od-0004OC-DV@zinfandel.tools.ietf.org>
 <E40C24C9-8D77-4396-95EB-40C6A45DD5E2@amsl.com>
In-Reply-To: <E40C24C9-8D77-4396-95EB-40C6A45DD5E2@amsl.com>

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

Thank you, Matt!

Best regards, Henrik

On 2017-02-10 15:02, Matt Larson wrote:
> Greetings all!
>=20
> Datatracker 6.43.0 has been deployed to production.
> Datatracker 6.43.1.dev0 has been deployed to the sandbox.
>=20
> Matt
>=20
>> On Feb 10, 2017, at 5:52 AM, Henrik Levkowetz <henrik@levkowetz.com> w=
rote:
>>=20
>>=20
>> Hi,
>>=20
>> This is an automatic notification about a new datatracker release,=20
>> v6.43.0, generated when running the mkrelease script.
>>=20
>> Release notes:
>>=20
>> ietfdb (6.43.0) ietf; urgency=3Dmedium
>>=20
>>  **Password Strength Meter**
>>=20
>>  This release provides a zxcvbn-based password strenght meter when set=
ting
>>  or changing a datatracker user password, and changes the default pass=
word
>>  hasher from PBKDF2 to BCrypt.  It adds support for datatracker manage=
ment
>>  of additional wikis,  and changes the management of bower-packaged we=
b
>>  assets to updating them to the latest minor release on each new datat=
racker
>>  release.  It also fixes a few bugs, and tweaks the IPR declaration pa=
ges to
>>  provide more complete information for declarations which indicate tha=
t=20
>>  licensing conditions will be provided later.
>>=20
>>  From the commit log:
>>=20
>>  * Added a change password page, and linked to it from the account pro=
file=20
>>    page and user menu.  Added zxcvbn-based browser-side password stren=
gth=20
>>    estimation on the various password setting, re-setting, and changin=
g forms.=20
>>    Added a change password test.  Changed ietfauth/urls.py to not use =
the=20
>>    deprecated string form for views in urlpatterns.
>>=20
>>  * Re-styled some auth-related forms to use a narrower form body on la=
rge=20
>>    screens, for aesthethic reasons.
>>=20
>>  * Added an explicit setting for the password hashers to use, in order=
 to=20
>>    place the bcrypt hasher first.  This makes BCrypt the default hashe=
r. =20
>>    Added the django_password_strength app to installed apps.
>>=20
>>  * Added the zxcvbn bower component, for use in client-side password=20
>>    strength estimation.
>>=20
>>  * Added django-bcrypt (for bcrypt password hashing) and=20
>>    django-password-strength (for browser-side zxcvbn password strength=
=20
>>    estimation) to the requirements.
>>=20
>>  * Added ordering for nomcom  Nominee objects.
>>=20
>>  * Expanded the Nominee __unicode__() method to provide unique results=
 by=20
>>    including the nomcom year.
>>=20
>>  * Tweaked the IPR Details page to show the possible a), b), and c)=20
>>    choices under section 'V' when licensing declaration to be provided=
 later=20
>>    has been chosen.
>>=20
>>  * Added a guard to prevent trying to get a document path for a meetin=
g=20
>>    document when the document is not associated with a meeting session=
=2E
>>=20
>>  * Added support for management of trac wikis for explicitly named gro=
ups,=20
>>    such as the IESG and IAOC.  Tweaked the dummy-run handling of the=20
>>    create_group_wikis management command.
>>=20
>>  * Added updating of static web assets to the release script.
>>=20
>>  * Fixed a bug in a queryset argument in all_id_text(); __in was not u=
sed,=20
>>    but the value given was a multi-row queryset.
>>=20
>>  * @register.simple_tag now (in Django 1.9) needs explicit mark_safe()=
 (or=20
>>    format_html() which invokes mark_safe()).  Fixed one case which nee=
ded this.
>>=20
>> -- Henrik Levkowetz <henrik@levkowetz.com>  09 Feb 2017 09:03:53 -0800=

>>=20
>> The new version is available for installation through SVN checkout, wi=
th
>>  'svn checkout https://svn.tools.ietf.org/svn/tools/ietfdb/tags/6.43.0=
'
>>=20
>> For development, copy the new development version instead:
>>  'svn copy https://svn.tools.ietf.org/svn/tools/ietfdb/tags/dev/6.43.1=
=2Edev0' <YOURBRANCH>
>>=20
>> Regards,
>>=20
>> 	Henrik
>> 	(via the mkrelease script)
>>=20
>> _______________________________________________
>> codesprints mailing list
>> codesprints@ietf.org
>> https://www.ietf.org/mailman/listinfo/codesprints
>>=20
>=20
> -------------------------------------------
> Matthew Larson, Software Engineer
> Association Management Solutions
> Forum Management, Meeting and Event Planning
> 5177 Brandin Court
> Fremont, CA  94538
>=20
>=20


--BhEFv1CLa2RN5k3CnaGn376edGtGXGVD1--

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

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

iQIcBAEBCAAGBQJYndkSAAoJEE6bV0uPuxcat6cP/11Ustb1l3ySdEhp36/LAWfD
sL1kDZz9UDXAmz0Oi2elS2IsvQLBWnwAopMduIFBh4955INnbAtOfYfAKa2rHXJM
FOj9doWC61QMPXFOTNDGY7yvUDDCpoesvQEKwDVUaQjv9oFUH+k5e5UKmo/PM0a5
95d8tYrj/1G9vCGhKthB1Z8Q6TKcSMoZCoCi6oqrLYj5Oq1R7kwP2N4LfAUSK2aJ
W9kZz5xv+PSbemwzCaGqiMUItreuHszTCdqI2yoFaYYjJyyil6o9FUScqL6BeASr
/ycTehlrukH4Vzt95+fPEiuK/o+/wBpPCms8H8S7aF+jZ4dFs/kbxIdFCS6lq7Ke
TP5NODUbMSiNGAZIr4fXu474X8Ce4k+YW39ipQT9qQaCe8AP13kFkfF3RCAHFWwT
fqJyKcwgyFL7QU631CwT1pKjeaUH6+nKKcFHfaY9IWSH68nnm7hz71NhZS7sdTeL
oGb1F9/Vqvm15DqSQKBk6OY69EDi7vKbasUQ0lMWngRiAIAaJOP4TtqWn/adY3CA
p54iA2z8Cqyt0QkTvuVJu40Xh5Qx1vvN5NVZSAWM20pVHeuf7n10MVnhOmpJWByL
z0CNhtBgaU3E6vSrwAzMCBkQQn1KB1Ig2B2XZPjJlO6urut/uRO2wdZ1SSevTaXO
xOOYTHJMfdqRlv0mH5ks
=gHl9
-----END PGP SIGNATURE-----

--o36gBf8lI1dPlPgMi5RtSlOtvTTNatOPE--


From nobody Mon Feb 13 02:18:35 2017
Return-Path: <agenda@ietf.org>
X-Original-To: wgchairs@ietf.org
Delivered-To: wgchairs@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9312D12956B; Mon, 13 Feb 2017 02:18:33 -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: Experimental Breakout Room Layout
X-Test-IDTracker: no
X-IETF-IDTracker: 6.43.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148698111357.24951.8789871690444791715.idtracker@ietfa.amsl.com>
Date: Mon, 13 Feb 2017 02:18:33 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/41166dGny53jYNgYwRL8936R4V4>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 10:18:33 -0000

Hello Working Group Chairs,

We will be running an experiment with one breakout room during IETF 98 on Thursday and Friday of the meeting week. The layout of the meeting room will have tables in a U-shape facing the projection screen for about 30 attendees, with theater seating (just chairs) behind the tables of the U. The room will be able to accommodate about 150 attendees total. 

If your working group would like to use this experimental layout, please modify your session request in the 'Special Request' field to indicate your interest, or send an email to smccammon@amsl.com. The session request tool will be open until 5pm Pacific time on Wednesday, February 15th to allow for this. 

Please note that submitting a request for the experimental layout does not guarantee a session in this room. 

Thank you!


From nobody Mon Feb 13 08:09:09 2017
Return-Path: <linda.dunbar@huawei.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1E131296E0; Mon, 13 Feb 2017 08:09:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 CPy6zbFtmIfB; Mon, 13 Feb 2017 08:09:06 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD33E1296DF; Mon, 13 Feb 2017 08:09:05 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml704-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DGK32225; Mon, 13 Feb 2017 16:08:54 +0000 (GMT)
Received: from SJCEML701-CHM.china.huawei.com (10.208.112.40) by lhreml704-cah.china.huawei.com (10.201.5.130) with Microsoft SMTP Server (TLS) id 14.3.301.0; Mon, 13 Feb 2017 16:08:53 +0000
Received: from SJCEML702-CHM.china.huawei.com ([169.254.4.133]) by SJCEML701-CHM.china.huawei.com ([169.254.3.132]) with mapi id 14.03.0235.001;  Mon, 13 Feb 2017 08:06:44 -0800
From: Linda Dunbar <linda.dunbar@huawei.com>
To: IETF Agenda <agenda@ietf.org>, Working Group Chairs <wgchairs@ietf.org>
Subject: RE: Experimental Breakout Room Layout
Thread-Topic: Experimental Breakout Room Layout
Thread-Index: AQHSheKQOKlc/e8Ng0WvZgYSyHD80aFnGefg
Date: Mon, 13 Feb 2017 16:06:42 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F659242257@SJCEML702-CHM.china.huawei.com>
References: <148698111357.24951.8789871690444791715.idtracker@ietfa.amsl.com>
In-Reply-To: <148698111357.24951.8789871690444791715.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.192.11.164]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090202.58A1DA16.0128, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.4.133, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 99bafbf5d549758ed45088060af676d3
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/zCgrh3HQSBtp0ZkK5lyZ2NK6YaU>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 16:09:08 -0000

UG9zc2libGUgdG8gYXJyYW5nZSB0aGlzIGJyZWFrb3V0IHJvb20gZm9yIGVhcmx5IHBhcnQgb2Yg
dGhlIHdlZWs/IExpa2UgTW9uZGF5IC1UdWVzZGF5LVdlZD8gSSBmaW5kIGdldHRpbmcgcGVvcGxl
IHRvZ2V0aGVyIGZvciBicmVha291dCBzZXNzaW9ucyBiZWZvcmUgdGhlIGZvcm1hbCBXRyBzZXNz
aW9uIGlzIHZlcnkgaGVscGZ1bCBpbiBnZXR0aW5nIGNvbnNlbnN1cyBhbmQgbWFraW5nIGdvb2Qg
cHJvZ3Jlc3MuIA0KDQpMaW5kYSBEdW5iYXIgDQoNCiANCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdl
LS0tLS0NCkZyb206IFdHQ2hhaXJzIFttYWlsdG86d2djaGFpcnMtYm91bmNlc0BpZXRmLm9yZ10g
T24gQmVoYWxmIE9mIElFVEYgQWdlbmRhDQpTZW50OiAyMDE35bm0MuaciDEz5pelIDQ6MTkNClRv
OiBXb3JraW5nIEdyb3VwIENoYWlycyA8d2djaGFpcnNAaWV0Zi5vcmc+DQpTdWJqZWN0OiBFeHBl
cmltZW50YWwgQnJlYWtvdXQgUm9vbSBMYXlvdXQNCg0KSGVsbG8gV29ya2luZyBHcm91cCBDaGFp
cnMsDQoNCldlIHdpbGwgYmUgcnVubmluZyBhbiBleHBlcmltZW50IHdpdGggb25lIGJyZWFrb3V0
IHJvb20gZHVyaW5nIElFVEYgOTggb24gVGh1cnNkYXkgYW5kIEZyaWRheSBvZiB0aGUgbWVldGlu
ZyB3ZWVrLiBUaGUgbGF5b3V0IG9mIHRoZSBtZWV0aW5nIHJvb20gd2lsbCBoYXZlIHRhYmxlcyBp
biBhIFUtc2hhcGUgZmFjaW5nIHRoZSBwcm9qZWN0aW9uIHNjcmVlbiBmb3IgYWJvdXQgMzAgYXR0
ZW5kZWVzLCB3aXRoIHRoZWF0ZXIgc2VhdGluZyAoanVzdCBjaGFpcnMpIGJlaGluZCB0aGUgdGFi
bGVzIG9mIHRoZSBVLiBUaGUgcm9vbSB3aWxsIGJlIGFibGUgdG8gYWNjb21tb2RhdGUgYWJvdXQg
MTUwIGF0dGVuZGVlcyB0b3RhbC4gDQoNCklmIHlvdXIgd29ya2luZyBncm91cCB3b3VsZCBsaWtl
IHRvIHVzZSB0aGlzIGV4cGVyaW1lbnRhbCBsYXlvdXQsIHBsZWFzZSBtb2RpZnkgeW91ciBzZXNz
aW9uIHJlcXVlc3QgaW4gdGhlICdTcGVjaWFsIFJlcXVlc3QnIGZpZWxkIHRvIGluZGljYXRlIHlv
dXIgaW50ZXJlc3QsIG9yIHNlbmQgYW4gZW1haWwgdG8gc21jY2FtbW9uQGFtc2wuY29tLiBUaGUg
c2Vzc2lvbiByZXF1ZXN0IHRvb2wgd2lsbCBiZSBvcGVuIHVudGlsIDVwbSBQYWNpZmljIHRpbWUg
b24gV2VkbmVzZGF5LCBGZWJydWFyeSAxNXRoIHRvIGFsbG93IGZvciB0aGlzLiANCg0KUGxlYXNl
IG5vdGUgdGhhdCBzdWJtaXR0aW5nIGEgcmVxdWVzdCBmb3IgdGhlIGV4cGVyaW1lbnRhbCBsYXlv
dXQgZG9lcyBub3QgZ3VhcmFudGVlIGEgc2Vzc2lvbiBpbiB0aGlzIHJvb20uIA0KDQpUaGFuayB5
b3UhDQoNCg==


From nobody Mon Feb 13 10:13:34 2017
Return-Path: <adrian@olddog.co.uk>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F4C3129721; Mon, 13 Feb 2017 10:13:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 r62mxJXVhyjj; Mon, 13 Feb 2017 10:13:31 -0800 (PST)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8403E1296F4; Mon, 13 Feb 2017 10:13:31 -0800 (PST)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id v1DIDT1i025634; Mon, 13 Feb 2017 18:13:29 GMT
Received: from 950129200 ([176.241.251.4]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id v1DIDLMA025529 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 13 Feb 2017 18:13:28 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'IETF Agenda'" <agenda@ietf.org>, "'Working Group Chairs'" <wgchairs@ietf.org>
References: <148698111357.24951.8789871690444791715.idtracker@ietfa.amsl.com> <4A95BA014132FF49AE685FAB4B9F17F659242257@SJCEML702-CHM.china.huawei.com>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F659242257@SJCEML702-CHM.china.huawei.com>
Subject: RE: Experimental Breakout Room Layout
Date: Mon, 13 Feb 2017 18:13:19 -0000
Message-ID: <01a101d28624$e082d160$a1887420$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHs4JyFYJ9tTMu1tHRO+YGINmpKTwHpQxexoSM83rA=
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.1.0.1062-22884.001
X-TM-AS-Result: No--7.780-10.0-31-10
X-imss-scan-details: No--7.780-10.0-31-10
X-TMASE-MatchedRID: VPleTT1nwdQF94UiDfmWyi1Hx9UxMGjddsM3mpA5g7LadW4iYSMjUfIL 3EilQkpCY6O9oTDdXNL21ZTKBNQQO+JVpHg0EXcOeP1J5vpgPKfWl5v8NYXwTkU3JOzc5wT/wB8 gzNQ+eE58LhiO3QnNS9wbk7jxATrkBA+nv6Ng9mjcYu6w+zOTEohKKllVYI0rC13My87/LbT3mu Lh+GPYbxGeuQoYrj88X7bicKxRIU23sNbcHjySQd0H8LFZNFG7bkV4e2xSge6vdj+X91SH36xQH iQJpa05UuDwni6sYJHR5FjJogGZLzZFEgw6u+Np
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/mT7EggaudWfpNtPFoprewT_MZaE>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 18:13:33 -0000

I wonder whether "breakout room" is carrying a different meaning to =
different people?

I *think* AMS might consider that all IETF WG meetings are held in =
breakout rooms. At least that is how the email below reads.

But Linda is asking about a room that can be used for side meetings or =
similar.

Adrian

> -----Original Message-----
> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of Linda =
Dunbar
> Sent: 13 February 2017 16:07
> To: IETF Agenda; Working Group Chairs
> Subject: RE: Experimental Breakout Room Layout
>=20
> Possible to arrange this breakout room for early part of the week? =
Like Monday -
> Tuesday-Wed? I find getting people together for breakout sessions =
before the
> formal WG session is very helpful in getting consensus and making good =
progress.
>=20
> Linda Dunbar
>=20
>=20
>=20
> -----Original Message-----
> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of IETF =
Agenda
> Sent: 2017=E5=B9=B42=E6=9C=8813=E6=97=A5 4:19
> To: Working Group Chairs <wgchairs@ietf.org>
> Subject: Experimental Breakout Room Layout
>=20
> Hello Working Group Chairs,
>=20
> We will be running an experiment with one breakout room during IETF 98 =
on
> Thursday and Friday of the meeting week. The layout of the meeting =
room will
> have tables in a U-shape facing the projection screen for about 30 =
attendees,
> with theater seating (just chairs) behind the tables of the U. The =
room will be
> able to accommodate about 150 attendees total.
>=20
> If your working group would like to use this experimental layout, =
please modify
> your session request in the 'Special Request' field to indicate your =
interest, or
> send an email to smccammon@amsl.com. The session request tool will be =
open
> until 5pm Pacific time on Wednesday, February 15th to allow for this.
>=20
> Please note that submitting a request for the experimental layout does =
not
> guarantee a session in this room.
>=20
> Thank you!



From nobody Mon Feb 13 13:24:58 2017
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 45B1A1293DA for <wgchairs@ietfa.amsl.com>; Mon, 13 Feb 2017 13:24:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.975
X-Spam-Level: 
X-Spam-Status: No, score=-0.975 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_SBL=1.623, URIBL_SBL_A=0.1] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 CV1pyqNf3TEN for <wgchairs@ietfa.amsl.com>; Mon, 13 Feb 2017 13:24:55 -0800 (PST)
Received: from mail-yw0-x233.google.com (mail-yw0-x233.google.com [IPv6:2607:f8b0:4002:c05::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B92B01298C8 for <wgchairs@ietf.org>; Mon, 13 Feb 2017 13:24:54 -0800 (PST)
Received: by mail-yw0-x233.google.com with SMTP id w75so56865305ywg.1 for <wgchairs@ietf.org>; Mon, 13 Feb 2017 13:24:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=GMhE3hGYt/Kmcv+5ZNiKsldrD10umuyKECiRosTBiBY=; b=X/A5mtZo3RIl8f9pKCWho5UuHMe1S9KMUtVynmCtg1PE0ZDs62eaN8qh6q0Bi6luiV YWBCfNIr/MemIUluz7Lj/yxmlOZOFbheF3+uxtkT5c54cWk+9NPPz25D1tH/Np0Eozmp 4sRD3Iy1Nbc2sYXNOKLaH7th8AJOIzMEauDCpAClhjtfcPUTtvROyh9TNGy6yyjDoCKL U3H/eAOYFsQcSH8jxeM81p+agL7g99gCeWANT04TePrMnHQo43+sHh2bvSU9s8DeSvbL 5f1fBgqhAVOeSIMoQll0GH8UyulR8QYhXEW8EsuGVHKk+H8ZskLLCvXxyq11ZhaCYxso I4Ng==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=GMhE3hGYt/Kmcv+5ZNiKsldrD10umuyKECiRosTBiBY=; b=f/x75nz0iRN9IKOkqVMtFLr0uPx0HozFTV+AM4gPJLJd+M/ApopzsbR2jVUUwAR8sR SvF5I6ElOWWi6H98rFOARosyX4tfES9EfBffBLkDi0WeFEyqBSUT44qrJbzIvS0h9Fq4 b6MsacKSGYphyFztMrW48Xtu8veQtncAmxqjFBgtgRgf0amM4HA5FQe/p7WJPKzvKbdL apxTJn2oGeoSHI80bnqKgaLFfWIm8i6TGBkoNqCsi2oP+5R1/AKuJ8Zog9MQYAMI8D3x mZygjNKCcSHvPDw2T0AlqDWc0hQINkGrUwjHBhMy5zu2mV82WQLF0+ZIjId/PEK9CyLT Y2iw==
X-Gm-Message-State: AMke39lnuthYUv/H5J0IXXn2fs21CBNwDW0Nognj0Bs8orq0DuQ3tZB8+HSO9GmPRBTXT7LMlVs14Z1Dw0fEzw==
X-Received: by 10.13.243.197 with SMTP id c188mr19244686ywf.248.1487021093862;  Mon, 13 Feb 2017 13:24:53 -0800 (PST)
MIME-Version: 1.0
Received: by 10.37.234.9 with HTTP; Mon, 13 Feb 2017 13:24:53 -0800 (PST)
Received: by 10.37.234.9 with HTTP; Mon, 13 Feb 2017 13:24:53 -0800 (PST)
In-Reply-To: <CAKKJt-f1XZo5rZFe_RZbdqB1kzU-kx_h3ep4dLadfv4Bguv0qQ@mail.gmail.com>
References: <3F2DBCB9-3D94-4DC3-A598-F0DC2B63D996@mnot.net> <CAKKJt-cob7qPL_rxP6f7AKiLDy0bO+hedFYbXjEw9V=pxaLrog@mail.gmail.com> <CAKKJt-e50dwUN0NOHeUzOknwuP=mbceAVjJ3W2nsFAT3JS9JwQ@mail.gmail.com> <CAKKJt-f1XZo5rZFe_RZbdqB1kzU-kx_h3ep4dLadfv4Bguv0qQ@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Mon, 13 Feb 2017 15:24:53 -0600
Message-ID: <CAKKJt-f2WPjg3oL=YJzCz+gX=5v8VQ8iqAZUfKg0bXrbx2c+fw@mail.gmail.com>
Subject: Re: Remote participation in interims -- experiences
To: Mark Nottingham <mnot@mnot.net>
Content-Type: multipart/alternative; boundary=94eb2c03569012c9c30548701422
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/aJCg7qUwrQxB16DMjQYiRThYscM>
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 21:24:57 -0000

--94eb2c03569012c9c30548701422
Content-Type: text/plain; charset=UTF-8

I was sitting in one of the U corners farthest from the chairs, and Mark's
summary matched my in-room experience. If I could add two points ...

I'm the responsible AD for QUIC, and having remote participation
consistently work as well as it seemed to work for this meeting makes me
feel much more comfortable with a working group that plans to do a
significant number of in-pdrson interims.

I've attended a fair number of interim meetings remotely, with a range of
experiences that were about as good as the meeting Mark described, all the
way down to "we ran speedtest this morning, and we're not sure the hotel
has enough bandwidth to let us monitor the jabber room", so I'm not sure
Jane Remoteattendee knows what to expect for any given meeting. Mark was
actively asking the remote addendees if they could see and hear (usually,
but not always, using jabber). Speaking only for myself, I value that level
of apparent interest, so that we don't have many awkward moments where we
poll the remote attendees and only then discover that they've all given up
hours ago!

Thanks,

Spencer

On Feb 9, 2017 02:48, "Mark Nottingham" <mnot@mnot.net> wrote:

Hi everyone,

We had a QUIC Interim meeting a couple of weeks back, supporting remote
participants through WebEx. I thought it might be useful to summarise how
we did it and what the feedback was, for other WGs' possible benefit. Feel
free to ignore.

The meeting was hosted at Akamai's office in Tokyo, which I think is a
fairly typical tech company sales-oriented office in a major city. The
meeting took place in a large training room.


## Room setup

We wanted to facilitate open discussion among participants. In the past,
WGs I've been involved with have done this using a boardroom or U-shape
setup, but we had 50 (!) people register for the Interim. So, we used a
series of concentric "U" shapes, with the chairs at a table at the open end
of the "U" and the projection screens behind them.

This seemed to work pretty well; people could see and hear each other
easily, and we had active engagement from people in the "outer" tiers (the
document editors and very active participants tended to sit in the "centre"
tier).

One thing that really helped was the tables; the room had a large number of
two-person table/desks on rollers that we could configure how we liked.
That let us tweak the setup to get the right density and layout.

The room was quite large, so we tightened things up a bit and closed a
divider wall to make the space smaller, so that it was easier to see and
hear, both for local and remote participants.


## A/V

Other WGs Iv'e been involved in have run Interims with remote participation
before, but the experience was generally pretty bad, and few people took us
up on it. Those that did tended to be silent, and to leave the meeting
early.

For this meeting, we had a sizeable number of people (15-20) register for
remote participation, with several of them key participants (e.g., document
editors). So, we had to provide a better experience.

Originally we wanted to use in-room videoconferencing (the room has
multiple built-in cameras and an array of ceiling microphones), but that
was a proprietary system that isn't easily available to non-employees.

Instead, we used:

- A dedicated computer: Having a dedicated computer was really helpful. I
used an old MacBook Air; the only problem was that it only has two USB
ports, meaning that we needed to unplug the camera to put a USB stick in to
transfer a presentation. Next time, I'll bring a USB hub.

- Microphone: We used one of these: <http://www.mxlmics.com/
microphones/web-conferencing/AC-404/> and it worked really well. It has an
advertised range of 8m / 25ft, and the remote participants didn't seem to
have any problem following conversation (once or twice they couldn't hear
someone, but we also couldn't hear that person in the room - we just asked
them to speak up). In a larger room, I'd probably use a pair of them and
mux them in the OS (possible in both Windows and Mac with appropriate
extensions / configuration). It cost me AU$147, I think it's available in
the US for US$80.

- Camera: I used a <http://www.logitech.com/en-us/product/c922-pro-stream-
webcam?crid=34>, but I'd actually prefer <http://www.logitech.com/en-
us/product/12131?crid=34> due to its wider angle. Both do H.264 on-camera.
The one I got came with a miniature tabletop tripod, which was very useful.
Somewhere around AU$100.

- Speakers: We used the room's speakers (over HDMI, along with the
projector); otherwise, I brought a pair of USB-powered speakers. A
bluetooth speaker would also work, if the battery lasted long enough or if
we plugged it in.

- WebEx: As provided through the Secretariat.


## Feedback

Afterwards, we ran a survey of remote participants to gather their
feedback. The results are here:
  https://mnot.wufoo.com/reports/january-2017-quic-interim-feedback/
(please don't share this link widely; the people who responded were made
aware that it would be shared with Chairs and IESG, but not further)

As you can see, people had somewhat conflicting experiences, but the
overall feedback seems pretty positive, considering that remote
participation is always going to be challenging (especially for a 3-day
meeting).


## How we can Improve

My takeaways for making it better next time:

1) I'm not thrilled about buying another camera so soon after buying a new
one (and that replaced a perfectly good one :), but many people mentioned
the angle of view. I'm not sure how much video actually helps with remote
participation, beyond establishing a "feel" of how the room looks (unless
there's whiteboard work, obviously).

2) A tripod capable of being placed on the floor might help get a better
camera angle.

3) A second USB mic will probably help, especially with more challenging
audio environments. That said, the mic we chose is remarkably good.

4) Having a dedicated way to let a remote participant "raise their hand" --
even if it's just having someone watch Jabber -- would probably be good.
That said, remote folks who had video didn't seem to have any problem with
this, because WebEx "hears" when they're becoming active, and their window
becomes prominent.

5) We could do a better job communicating the channels for remote
participants and their details beforehand.


Hope this helps,


--
Mark Nottingham   https://www.mnot.net/

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

<div dir=3D"auto">I was sitting in one of the U corners farthest from the c=
hairs, and Mark&#39;s summary matched my in-room experience. If I could add=
 two points ...<div dir=3D"auto"><br></div><div dir=3D"auto">I&#39;m the re=
sponsible AD for QUIC, and having remote participation consistently work as=
 well as it seemed to work for this meeting makes me feel much more comfort=
able with a working group that plans to do a significant number of in-pdrso=
n interims.=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"auto">I&#39;=
ve attended a fair number of interim meetings remotely, with a range of exp=
eriences that were about as good as the meeting Mark described, all the way=
 down to &quot;we ran speedtest this morning, and we&#39;re not sure the ho=
tel has enough bandwidth to let us monitor the jabber room&quot;, so I&#39;=
m not sure Jane Remoteattendee knows what to expect for any given meeting. =
Mark was actively asking the remote addendees if they could see and hear (u=
sually, but not always, using jabber). Speaking only for myself, I value th=
at level of apparent interest, so that we don&#39;t have many awkward momen=
ts where we poll the remote attendees and only then discover that they&#39;=
ve all given up hours ago!</div><div dir=3D"auto"><br></div><div dir=3D"aut=
o">Thanks,</div><div dir=3D"auto"><br></div><div dir=3D"auto">Spencer</div>=
</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Feb 9, 2=
017 02:48, &quot;Mark Nottingham&quot; &lt;<a href=3D"mailto:mnot@mnot.net"=
>mnot@mnot.net</a>&gt; wrote:<br type=3D"attribution"><blockquote class=3D"=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex">Hi everyone,<br>
<br>
We had a QUIC Interim meeting a couple of weeks back, supporting remote par=
ticipants through WebEx. I thought it might be useful to summarise how we d=
id it and what the feedback was, for other WGs&#39; possible benefit. Feel =
free to ignore.<br>
<br>
The meeting was hosted at Akamai&#39;s office in Tokyo, which I think is a =
fairly typical tech company sales-oriented office in a major city. The meet=
ing took place in a large training room.<br>
<br>
<br>
## Room setup<br>
<br>
We wanted to facilitate open discussion among participants. In the past, WG=
s I&#39;ve been involved with have done this using a boardroom or U-shape s=
etup, but we had 50 (!) people register for the Interim. So, we used a seri=
es of concentric &quot;U&quot; shapes, with the chairs at a table at the op=
en end of the &quot;U&quot; and the projection screens behind them.<br>
<br>
This seemed to work pretty well; people could see and hear each other easil=
y, and we had active engagement from people in the &quot;outer&quot; tiers =
(the document editors and very active participants tended to sit in the &qu=
ot;centre&quot; tier).<br>
<br>
One thing that really helped was the tables; the room had a large number of=
 two-person table/desks on rollers that we could configure how we liked. Th=
at let us tweak the setup to get the right density and layout.<br>
<br>
The room was quite large, so we tightened things up a bit and closed a divi=
der wall to make the space smaller, so that it was easier to see and hear, =
both for local and remote participants.<br>
<br>
<br>
## A/V<br>
<br>
Other WGs Iv&#39;e been involved in have run Interims with remote participa=
tion before, but the experience was generally pretty bad, and few people to=
ok us up on it. Those that did tended to be silent, and to leave the meetin=
g early.<br>
<br>
For this meeting, we had a sizeable number of people (15-20) register for r=
emote participation, with several of them key participants (e.g., document =
editors). So, we had to provide a better experience.<br>
<br>
Originally we wanted to use in-room videoconferencing (the room has multipl=
e built-in cameras and an array of ceiling microphones), but that was a pro=
prietary system that isn&#39;t easily available to non-employees.<br>
<br>
Instead, we used:<br>
<br>
- A dedicated computer: Having a dedicated computer was really helpful. I u=
sed an old MacBook Air; the only problem was that it only has two USB ports=
, meaning that we needed to unplug the camera to put a USB stick in to tran=
sfer a presentation. Next time, I&#39;ll bring a USB hub.<br>
<br>
- Microphone: We used one of these: &lt;<a href=3D"http://www.mxlmics.com/m=
icrophones/web-conferencing/AC-404/" rel=3D"noreferrer" target=3D"_blank">h=
ttp://www.mxlmics.com/<wbr>microphones/web-conferencing/<wbr>AC-404/</a>&gt=
; and it worked really well. It has an advertised range of 8m / 25ft, and t=
he remote participants didn&#39;t seem to have any problem following conver=
sation (once or twice they couldn&#39;t hear someone, but we also couldn&#3=
9;t hear that person in the room - we just asked them to speak up). In a la=
rger room, I&#39;d probably use a pair of them and mux them in the OS (poss=
ible in both Windows and Mac with appropriate extensions / configuration). =
It cost me AU$147, I think it&#39;s available in the US for US$80.<br>
<br>
- Camera: I used a &lt;<a href=3D"http://www.logitech.com/en-us/product/c92=
2-pro-stream-webcam?crid=3D34" rel=3D"noreferrer" target=3D"_blank">http://=
www.logitech.com/en-<wbr>us/product/c922-pro-stream-<wbr>webcam?crid=3D34</=
a>&gt;, but I&#39;d actually prefer &lt;<a href=3D"http://www.logitech.com/=
en-us/product/12131?crid=3D34" rel=3D"noreferrer" target=3D"_blank">http://=
www.logitech.com/en-<wbr>us/product/12131?crid=3D34</a>&gt; due to its wide=
r angle. Both do H.264 on-camera. The one I got came with a miniature table=
top tripod, which was very useful. Somewhere around AU$100.<br>
<br>
- Speakers: We used the room&#39;s speakers (over HDMI, along with the proj=
ector); otherwise, I brought a pair of USB-powered speakers. A bluetooth sp=
eaker would also work, if the battery lasted long enough or if we plugged i=
t in.<br>
<br>
- WebEx: As provided through the Secretariat.<br>
<br>
<br>
## Feedback<br>
<br>
Afterwards, we ran a survey of remote participants to gather their feedback=
. The results are here:<br>
=C2=A0 <a href=3D"https://mnot.wufoo.com/reports/january-2017-quic-interim-=
feedback/" rel=3D"noreferrer" target=3D"_blank">https://mnot.wufoo.com/<wbr=
>reports/january-2017-quic-<wbr>interim-feedback/</a><br>
(please don&#39;t share this link widely; the people who responded were mad=
e aware that it would be shared with Chairs and IESG, but not further)<br>
<br>
As you can see, people had somewhat conflicting experiences, but the overal=
l feedback seems pretty positive, considering that remote participation is =
always going to be challenging (especially for a 3-day meeting).<br>
<br>
<br>
## How we can Improve<br>
<br>
My takeaways for making it better next time:<br>
<br>
1) I&#39;m not thrilled about buying another camera so soon after buying a =
new one (and that replaced a perfectly good one :), but many people mention=
ed the angle of view. I&#39;m not sure how much video actually helps with r=
emote participation, beyond establishing a &quot;feel&quot; of how the room=
 looks (unless there&#39;s whiteboard work, obviously).<br>
<br>
2) A tripod capable of being placed on the floor might help get a better ca=
mera angle.<br>
<br>
3) A second USB mic will probably help, especially with more challenging au=
dio environments. That said, the mic we chose is remarkably good.<br>
<br>
4) Having a dedicated way to let a remote participant &quot;raise their han=
d&quot; -- even if it&#39;s just having someone watch Jabber -- would proba=
bly be good. That said, remote folks who had video didn&#39;t seem to have =
any problem with this, because WebEx &quot;hears&quot; when they&#39;re bec=
oming active, and their window becomes prominent.<br>
<br>
5) We could do a better job communicating the channels for remote participa=
nts and their details beforehand.<br>
<br>
<br>
Hope this helps,<br>
<br>
<br>
--<br>
Mark Nottingham=C2=A0 =C2=A0<a href=3D"https://www.mnot.net/" rel=3D"norefe=
rrer" target=3D"_blank">https://www.mnot.net/</a><br>
<br>
</blockquote></div><br></div>

--94eb2c03569012c9c30548701422--


From nobody Tue Feb 14 13:20:54 2017
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64BEA1298AC for <wgchairs@ietfa.amsl.com>; Tue, 14 Feb 2017 13:20:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 X-V41F0ptJTu for <wgchairs@ietfa.amsl.com>; Tue, 14 Feb 2017 13:20:51 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2EA3612973E for <wgchairs@ietf.org>; Tue, 14 Feb 2017 13:20:51 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id E9348200A3; Tue, 14 Feb 2017 16:42:16 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id EE99F6381A; Tue, 14 Feb 2017 16:20:49 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
to: Mark Nottingham <mnot@mnot.net>, WG Chairs <wgchairs@ietf.org>
Subject: Re: Remote participation in interims -- experiences
In-Reply-To: <CAKKJt-f2WPjg3oL=YJzCz+gX=5v8VQ8iqAZUfKg0bXrbx2c+fw@mail.gmail.com>
References: <3F2DBCB9-3D94-4DC3-A598-F0DC2B63D996@mnot.net> <CAKKJt-cob7qPL_rxP6f7AKiLDy0bO+hedFYbXjEw9V=pxaLrog@mail.gmail.com> <CAKKJt-e50dwUN0NOHeUzOknwuP=mbceAVjJ3W2nsFAT3JS9JwQ@mail.gmail.com> <CAKKJt-f1XZo5rZFe_RZbdqB1kzU-kx_h3ep4dLadfv4Bguv0qQ@mail.gmail.com> <CAKKJt-f2WPjg3oL=YJzCz+gX=5v8VQ8iqAZUfKg0bXrbx2c+fw@mail.gmail.com>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.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-sha256; protocol="application/pgp-signature"
Date: Tue, 14 Feb 2017 16:20:49 -0500
Message-ID: <28247.1487107249@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/j1dkvzO_w9L_jWlbQ28e3BnQ_Ho>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 21:20:52 -0000

--=-=-=
Content-Type: text/plain


Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> wrote:
    > - WebEx: As provided through the Secretariat.

Webex -- JAVA ws app?
Or the newer WEBRTC version (not available again this week, but working
really well two weeks ago...)

Did you have the benefit of having seen the room in question in advance?

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




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

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

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAlijdLEACgkQgItw+93Q
3WVOvAf+JpTDYNA9p96aWS5n4bUgdfB3BIvapOTjcWkJPstMRDCx5hdb4cV+nyot
IvIJKZuJOpqqEiTuq2HG6SB0Ykcp4dvv+fTfudrk/jNH7XhV7wcAQnkGzqLN8fBX
OZO7HBTIBEai/ekbpuFDJmEBDvcG6IzunZEtizaCcR93g9ICHaZoFPcm/cV01kvR
Gkh4bxbTDnYXca1qOpd70ORfVUZxACWaG6WJXkMbLxUtCGMZrBDSwPLkmY0TwWgG
tup+PGWCt8IMFfK4mQNnYxw58wpl5dQd3209A+AM7V+QL+xH5yk2uX7HqevLq9Z/
t01JYbE+cHjoDevX4NNdCQnUn+N/Bw==
=PmbN
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Feb 14 13:34:11 2017
Return-Path: <mnot@mnot.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C36D129585 for <wgchairs@ietfa.amsl.com>; Tue, 14 Feb 2017 13:34:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level: 
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 ZVuLWwqVGdVZ for <wgchairs@ietfa.amsl.com>; Tue, 14 Feb 2017 13:34:08 -0800 (PST)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF8421294CF for <wgchairs@ietf.org>; Tue, 14 Feb 2017 13:34:07 -0800 (PST)
Received: from [192.168.3.101] (unknown [124.189.98.244]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 28C2722E25B; Tue, 14 Feb 2017 16:34:01 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
Subject: Re: Remote participation in interims -- experiences
From: Mark Nottingham <mnot@mnot.net>
X-Mailer: iPhone Mail (14D27)
In-Reply-To: <28247.1487107249@obiwan.sandelman.ca>
Date: Wed, 15 Feb 2017 08:33:57 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <0D2B18D0-777F-44D4-9724-738B3A019584@mnot.net>
References: <3F2DBCB9-3D94-4DC3-A598-F0DC2B63D996@mnot.net> <CAKKJt-cob7qPL_rxP6f7AKiLDy0bO+hedFYbXjEw9V=pxaLrog@mail.gmail.com> <CAKKJt-e50dwUN0NOHeUzOknwuP=mbceAVjJ3W2nsFAT3JS9JwQ@mail.gmail.com> <CAKKJt-f1XZo5rZFe_RZbdqB1kzU-kx_h3ep4dLadfv4Bguv0qQ@mail.gmail.com> <CAKKJt-f2WPjg3oL=YJzCz+gX=5v8VQ8iqAZUfKg0bXrbx2c+fw@mail.gmail.com> <28247.1487107249@obiwan.sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/ZGmGJNsTnjQCIe5G33PFLp0P3oc>
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 21:34:10 -0000

We used traditional WebEx.=20

I have presented talks in that room before; knowing its setup was one of the=
 reasons we chose it.=20

Cheers,

Sent from my iPhone

> On 15 Feb 2017, at 8:20 am, Michael Richardson <mcr+ietf@sandelman.ca> wro=
te:
>=20
> advance?
>=20
> --


From nobody Thu Feb 16 02:14:31 2017
Return-Path: <henrik@levkowetz.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1E1C1294E5; Thu, 16 Feb 2017 02:14:26 -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 autolearn_force=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 THeXuH7ulW60; Thu, 16 Feb 2017 02:14:25 -0800 (PST)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E3BB12947A; Thu, 16 Feb 2017 02:14:25 -0800 (PST)
Received: from henrik by zinfandel.tools.ietf.org with local (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1ceJ4z-0001xv-2I; Thu, 16 Feb 2017 02:14:25 -0800
To: codesprints@ietf.org, iesg@ietf.org, wgchairs@ietf.org
Subject: New datatracker release: v6.44.0
Message-Id: <E1ceJ4z-0001xv-2I@zinfandel.tools.ietf.org>
From: Henrik Levkowetz <henrik@levkowetz.com>
Date: Thu, 16 Feb 2017 02:14:25 -0800
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Rcpt-To: codesprints@ietf.org, henrik@levkowetz.com, iesg@ietf.org,  wgchairs@ietf.org
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/ajeClGmSASD7kfBNSLl-GLdJ5qs>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 10:14:26 -0000

Hi,

This is an automatic notification about a new datatracker release, 
v6.44.0, generated when running the mkrelease script.

Release notes:

ietfdb (6.44.0) ietf; urgency=medium

  **Improved account editing**

  This is a small feature release with some bugfixes.  It introduces the
  ability for datatracker users to change their username from the current
  one to one of the (other) active email addresses of their account, and
  the ability to indicate which of the active email addresses should be
  considered the primary email address.  It adds a menu endtry for document
  search, which was not easy to navigate to internally if you didn't know how.
  Other minor fixes are mentioned in the commit log:

  * Added the ability for logged-in users to change their login (username) 
    to any of the active email addresses of the account.  Fixes ticket #2052.

  * Tweaked the company name extraction code in class Draft.

  * Added support for indicating the primary email address of one's 
    datatracker account.  Fixes issue #2106.

  * Merged in [12835] from rcross@amsl.com:
    Fixes #2202.  Interim sessions appear unordered.  Switch templates to 
    use ordered assignments() related object manager.  Also removed now unused 
    template filters.   

  * Added a menu entry for Document Search

  * Fixed an issue with the test-crawler which could cause false positives 
    for urls containing apostrophe.

  * Fixed a html entity issue.

  * Tweaked the author extraction to recognize short lines as paragraph 
    ends, not only lines ending in '.' or ':'

  * Stabilized a number of nomcom tests by enforcing queryset ordering.

  * Added more information about submission errors and a full idnits run to 
    the manual post email sent to the secretariat.

  * Added some updates to /release/about

  * Added ordering by name to group personnel lists in edit and about 
    views.  This ordering is by the person's profile name, without attempting 
    to determine which name part is family name or given name.  Fixes #2184.

  * Extended the name_parts() method to consider military rank prefixes.

 -- Henrik Levkowetz <henrik@levkowetz.com>  15 Feb 2017 08:59:35 -0800

The new version is available for installation through SVN checkout, with
  'svn checkout https://svn.tools.ietf.org/svn/tools/ietfdb/tags/6.44.0'

For development, copy the new development version instead:
  'svn copy https://svn.tools.ietf.org/svn/tools/ietfdb/tags/dev/6.44.1.dev0' <YOURBRANCH>

Regards,

	Henrik
	(via the mkrelease script)


From nobody Sun Feb 19 03:43:00 2017
Return-Path: <henrik@levkowetz.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88109129469; Sun, 19 Feb 2017 03:42:54 -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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 agbT6WRzzZ4T; Sun, 19 Feb 2017 03:42:53 -0800 (PST)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 65F16129464; Sun, 19 Feb 2017 03:42:53 -0800 (PST)
Received: from henrik by zinfandel.tools.ietf.org with local (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1cfPtE-00008W-Vi; Sun, 19 Feb 2017 03:42:52 -0800
To: codesprints@ietf.org, iesg@ietf.org, wgchairs@ietf.org
Subject: New datatracker release: v6.44.1
Message-Id: <E1cfPtE-00008W-Vi@zinfandel.tools.ietf.org>
From: Henrik Levkowetz <henrik@levkowetz.com>
Date: Sun, 19 Feb 2017 03:42:52 -0800
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Rcpt-To: codesprints@ietf.org, henrik@levkowetz.com, iesg@ietf.org,  wgchairs@ietf.org
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/_qDGzil0TiTJRgA14yOWqtZJOlA>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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 Feb 2017 11:42:54 -0000

Hi,

This is an automatic notification about a new datatracker release, 
v6.44.1, generated when running the mkrelease script.

Release notes:

ietfdb (6.44.1) ietf; urgency=medium

  **Non-ASCII Name Support for Email Address Fields**

  This is a bugfix relelease which provides a reworked email address handling
  in order to be able to support non-ascii names as part of email address
  fields.  It also provides reworked generation of user names in the test
  suite in order to generate names from multiple non-ascii locales.  This
  fixes issue #2080.  The release also cleans the slate for the upcoming merge
  in of the Django 1.10 branch.

 -- Henrik Levkowetz <henrik@levkowetz.com>  18 Feb 2017 13:50:40 -0800

The new version is available for installation through SVN checkout, with
  'svn checkout https://svn.tools.ietf.org/svn/tools/ietfdb/tags/6.44.1'

For development, copy the new development version instead:
  'svn copy https://svn.tools.ietf.org/svn/tools/ietfdb/tags/dev/6.44.2.dev0' <YOURBRANCH>

Regards,

	Henrik
	(via the mkrelease script)


From nobody Mon Feb 20 03:45:56 2017
Return-Path: <henrik@levkowetz.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 634DA1299BC; Mon, 20 Feb 2017 03:45:55 -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 autolearn_force=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 1F4n9Ymxdeq1; Mon, 20 Feb 2017 03:45:54 -0800 (PST)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E347C1299B8; Mon, 20 Feb 2017 03:45:53 -0800 (PST)
Received: from henrik by zinfandel.tools.ietf.org with local (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1cfmPh-0000zv-HH; Mon, 20 Feb 2017 03:45:53 -0800
To: codesprints@ietf.org, iesg@ietf.org, wgchairs@ietf.org
Subject: New datatracker release: v6.45.0
Message-Id: <E1cfmPh-0000zv-HH@zinfandel.tools.ietf.org>
From: Henrik Levkowetz <henrik@levkowetz.com>
Date: Mon, 20 Feb 2017 03:45:53 -0800
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Rcpt-To: codesprints@ietf.org, henrik@levkowetz.com, iesg@ietf.org,  wgchairs@ietf.org
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/h3SwGX_aDjV9eu1Jq8CCbm75jDs>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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 Feb 2017 11:45:55 -0000

Hi,

This is an automatic notification about a new datatracker release, 
v6.45.0, generated when running the mkrelease script.

Release notes:

ietfdb (6.45.0) ietf; urgency=medium

  **Django 1.10**

  This release upgrades the datatracker to use version 1.10 of the Django
  framework.  Django 1.10 provides support for unicode login names, the new
  Argon2 password hasher, and makes available a number of minor conveniences.

  This release also removed support for automatic generation of dotted-path
  names for the view function in urlpatterns, which seems to violate the DRY
  (Don't Repeat Yourself) principle in programming.  I plan to have words with
  the Django developers about this during DjangoCon Europe in May.  That
  change necessitated a workaround url() function and a lot of clean-up and
  conversion.  The conversion work is not finished, but we're getting there,
  and meanwhile everything is functional with Django 1.10.  For the Django
  1.10 release notes, see [a].

  A full diff of the upgrade changes is available in changeset [12881].

  The next Django release, 1.11, will be the last version which will run on
  Python 2.7; the following release, 2.0, will require Python 3; probably
  python 3.4 or higher.  The Django 1.11 release will be a LTS (Long Term
  Support) release which will get security upgrades for 3 years after its
  release.  We should upgrade to 1.11 when it's released later this year, and
  then plan on converting the datatracker code base to Python 3, in order to
  be ready for Django 2.x before LTS ends some time in 2020.

  [a] https://docs.djangoproject.com/en/1.10/releases/1.10/

 -- Henrik Levkowetz <henrik@levkowetz.com>  20 Feb 2017 03:14:45 -0800

The new version is available for installation through SVN checkout, with
  'svn checkout https://svn.tools.ietf.org/svn/tools/ietfdb/tags/6.45.0'

For development, copy the new development version instead:
  'svn copy https://svn.tools.ietf.org/svn/tools/ietfdb/tags/dev/6.45.1.dev0' <YOURBRANCH>

Regards,

	Henrik
	(via the mkrelease script)


From nobody Tue Feb 21 02:44:30 2017
Return-Path: <bclaise@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35E87129529 for <wgchairs@ietfa.amsl.com>; Tue, 21 Feb 2017 02:44:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level: 
X-Spam-Status: No, score=-14.521 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 72yRH1CfOcCy for <wgchairs@ietfa.amsl.com>; Tue, 21 Feb 2017 02:44:27 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 05B06129431 for <wgchairs@ietf.org>; Tue, 21 Feb 2017 02:44:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=17756; q=dns/txt; s=iport; t=1487673867; x=1488883467; h=subject:references:to:from:message-id:date:mime-version: in-reply-to; bh=nJSPMWoCNaF6FR3OJfZ+piMe61CiQ2mTjl8We3OJ624=; b=hYnUiW03zVTL5TqtNHK4c+i1ag42tWcVlO55oHB7B3EC8YM1AXc2pvd+ ocov6u1E6L/EWPTohl1kPam2GXOYugfKWLRL8bfi0oy4IcqFqlvIVaX/K Bq5wSiL+PHjQtNEZWIJzH71JIiRQ6RK36T+kTkLHpdlWbgJkte3zlNeWf 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CaAwBPGaxY/xbLJq1eGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBgm+BQwMnX41jcpEFH4gMixmCD4INLIV2AoMfGAECAQEBAQEBAWIohHA?= =?us-ascii?q?BBi1cHAMBAhYZISwCCAYNBgIBAYlSAxUOrGqDRiuHDA2EEwEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBARgFhkyCBQiCYoJRRoEPEAIBBjUfhSYFlWCFbjqGdIY0WoQbgXu?= =?us-ascii?q?FG4MthkuKQV2IBh84eAggFAgXFYU+gUk/NQGIVII7AQEB?=
X-IronPort-AV: E=Sophos;i="5.35,189,1484006400";  d="scan'208,217";a="692413338"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 Feb 2017 10:44:24 +0000
Received: from [10.61.70.135] (ams3-vpn-dhcp1671.cisco.com [10.61.70.135]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id v1LAiOEw019585 for <wgchairs@ietf.org>; Tue, 21 Feb 2017 10:44:24 GMT
Subject: Fwd: Introducing the new Datatracker Review Tracking tool for YANG Module Reviews
References: <bf07f029-3a1c-190c-ba9d-503240f160b9@cisco.com>
To: WG Chairs <wgchairs@ietf.org>
From: Benoit Claise <bclaise@cisco.com>
X-Forwarded-Message-Id: <bf07f029-3a1c-190c-ba9d-503240f160b9@cisco.com>
Message-ID: <cba7522d-5595-6b68-fe6c-ef7760f93969@cisco.com>
Date: Tue, 21 Feb 2017 11:44:24 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <bf07f029-3a1c-190c-ba9d-503240f160b9@cisco.com>
Content-Type: multipart/alternative; boundary="------------E85152AC52B45B7682FD30A4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/B0z6gvPwlO_FjLMYD0bZr9pfPwI>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 10:44:29 -0000

This is a multi-part message in MIME format.
--------------E85152AC52B45B7682FD30A4
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit

FYI.
The YANG doctor process is now part of the datatracker review tracking tool.
It will help from a tracking point of view. However, you still have to 
warn me (or the YANG secretary Mehmet) when you have a YANG module to 
review (like it was the case with the MIB doctors).
 From https://www.ietf.org/iesg/directorate/yang-doctors.html:

    All YANG documents will be passed by a YANG doctor reviewer before
    they will be approved by the IESG. The YANG doctor review must be
    done after the Working Group Last Call and before the IETF Last
    Call. ADs and WG chairs responsible on I-Ds that include YANG
    documents should ask the OPS ADs for a review as soon as the
    document completed WGLC. Failing that request, the review will be
    conducted during the IETF Last Call.

Regards, Benoit

-------- Forwarded Message --------
Subject: 	Introducing the new Datatracker Review Tracking tool for YANG 
Module Reviews
Date: 	Sun, 19 Feb 2017 20:37:43 +0100
From: 	Mehmet Ersue <mersue@gmail.com>
To: 	yang-doctors@ietf.org
CC: 	'Robert Sparks' <rjsparks@nostrum.com>, 'Benoit Claise' 
<bclaise@cisco.com>, 'Dan Romascanu' <dromasca@gmail.com>, 'Gunter Van 
De Velde' <guntervandeveldecc@icloud.com>



Dear YANG Doctors,

as discussed with Benoit this mail is to introduce the new datatracker 
review tracking tool for YANG module reviews.

The updated entry page for YANG Doctors team is at: 
https://www.ietf.org/iesg/directorate/yang-doctors.html

The entry page of the YANG review tracking tool is at: 
https://datatracker.ietf.org/dir/yangdoctors/about/

Some of you know the review tracking tool already from OPS-DIR reviews.

The usual process for YANG Doctor’s reviews using the new datatracker 
tool is summarized below.

A) ADs, WG chairs or draft authors request the review of a YANG module 
on Datatracker.

    - Sign in on Datatracker: 
https://datatracker.ietf.org/accounts/login/?next=/

    - Go to the draft page (example): 
https://datatracker.ietf.org/doc/draft-ietf-netmod-schema-mount/

    - Click on the button "Review request" which brings you to 
(example): 
https://datatracker.ietf.org/doc/draft-ietf-netmod-schema-mount/reviewrequest/ 


    - Choose the type of review (Early, LC, Telechat) and set a 
recommended deadline

    - If required propose a reviewer in comments.

B) YANG secretary assigns the requested review to a reviewer.

    - Datatracker generates an email to the reviewer indicating the 
draft with the YANG module and the review deadline.

    - All assigned open review requests and closed review requests can 
be always listed at: 
https://datatracker.ietf.org/group/yangdoctors/reviews/

    Notes:

    - Datatracker proposes a reviewer using based on the round robin 
approach.

    - YANG doctors can enter their availability into their datatracker 
account profile to avoid wrong assignments.

C) The reviewer enters the review result into the review tool.

    - The reviewer goes to the draft review request page at (example): 
https://datatracker.ietf.org/doc/draft-ietf-netmod-syslog-model/reviewrequest/8317/ 


    - Clicks on "Complete review"

    - Enters state, reviewed revision, and the review result.

    - In case the reviewer enters the review result directly into the 
tool or uploads a text file, the tool generates an email to YANG Doctors 
maillist, draft authors and the related WG maillist.

Z) YANG doctors secretary will send a weekly summary of requested and 
ongoing reviews to YANG doctors maillist.

The first summary mail will be send out in parallel to this mail.

Notes:

- Old review assignments on the current review history page 
(https://trac.ietf.org/trac/ops/wiki/yang-doctors-review-history) will 
be migrated to the datatracker tool by the admin soon. The old page will 
be used for external review requests only.

- The Wiki page for the YANG review process will be updated within a 
week based on the collected feedback.

Thank you in advance for your suggestions and comments.

Please let us know if you have any questions.

Cheers,

Mehmet

(YANG Doctors Secretary)


--------------E85152AC52B45B7682FD30A4
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=windows-1252">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    FYI.<br>
    <div class="moz-forward-container"> The YANG doctor process is now
      part of the datatracker review tracking tool.<br>
      It will help from a tracking point of view. However, you still
      have to warn me (or the YANG secretary Mehmet) when you have a
      YANG module to review (like it was the case with the MIB doctors).<br>
      From <a class="moz-txt-link-freetext" href="https://www.ietf.org/iesg/directorate/yang-doctors.html">https://www.ietf.org/iesg/directorate/yang-doctors.html</a>:<br>
      <blockquote>All YANG documents will be passed by a YANG doctor
        reviewer before they will be approved by the IESG. The YANG
        doctor review must be done after the Working Group Last Call and
        before the IETF Last Call. ADs and WG chairs responsible on I-Ds
        that include YANG documents should ask the OPS ADs for a review
        as soon as the document completed WGLC. Failing that request,
        the review will be conducted during the IETF Last Call.</blockquote>
      Regards, Benoit<br>
      <br>
      <div class="moz-forward-container">-------- Forwarded Message
        --------
        <table class="moz-email-headers-table" border="0"
          cellpadding="0" cellspacing="0">
          <tbody>
            <tr>
              <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Subject:
              </th>
              <td>Introducing the new Datatracker Review Tracking tool
                for YANG Module Reviews</td>
            </tr>
            <tr>
              <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date:
              </th>
              <td>Sun, 19 Feb 2017 20:37:43 +0100</td>
            </tr>
            <tr>
              <th align="RIGHT" nowrap="nowrap" valign="BASELINE">From:
              </th>
              <td>Mehmet Ersue <a moz-do-not-send="true"
                  class="moz-txt-link-rfc2396E"
                  href="mailto:mersue@gmail.com">&lt;mersue@gmail.com&gt;</a></td>
            </tr>
            <tr>
              <th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th>
              <td><a moz-do-not-send="true"
                  class="moz-txt-link-abbreviated"
                  href="mailto:yang-doctors@ietf.org">yang-doctors@ietf.org</a></td>
            </tr>
            <tr>
              <th align="RIGHT" nowrap="nowrap" valign="BASELINE">CC: </th>
              <td>'Robert Sparks' <a moz-do-not-send="true"
                  class="moz-txt-link-rfc2396E"
                  href="mailto:rjsparks@nostrum.com">&lt;rjsparks@nostrum.com&gt;</a>,
                'Benoit Claise' <a moz-do-not-send="true"
                  class="moz-txt-link-rfc2396E"
                  href="mailto:bclaise@cisco.com">&lt;bclaise@cisco.com&gt;</a>,
                'Dan Romascanu' <a moz-do-not-send="true"
                  class="moz-txt-link-rfc2396E"
                  href="mailto:dromasca@gmail.com">&lt;dromasca@gmail.com&gt;</a>,
                'Gunter Van De Velde' <a moz-do-not-send="true"
                  class="moz-txt-link-rfc2396E"
                  href="mailto:guntervandeveldecc@icloud.com">&lt;guntervandeveldecc@icloud.com&gt;</a></td>
            </tr>
          </tbody>
        </table>
        <br>
        <br>
        <meta http-equiv="Content-Type" content="text/html;
          charset=windows-1252">
        <meta name="Generator" content="Microsoft Word 15 (filtered
          medium)">
        <style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:#0000CC;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
        <div class="WordSection1">
          <p class="MsoNormal"><span style="color:#0000CC">Dear YANG
              Doctors,<o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC"><o:p> </o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC">as discussed
              with Benoit this mail is to introduce the new datatracker
              review tracking tool for YANG module reviews. <o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC"><o:p> </o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC">The updated
              entry page for YANG Doctors team is at:</span> <span
              style="color:#0000CC"><a moz-do-not-send="true"
                href="https://www.ietf.org/iesg/directorate/yang-doctors.html">https://www.ietf.org/iesg/directorate/yang-doctors.html</a><o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC">The entry
              page of the YANG review tracking tool is at: <a
                moz-do-not-send="true"
                href="https://datatracker.ietf.org/dir/yangdoctors/about/">https://datatracker.ietf.org/dir/yangdoctors/about/</a>
              <o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC"><o:p> </o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC">Some of you
              know the review tracking tool already from OPS-DIR
              reviews. <o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC">The usual
              process for YANG Doctor’s reviews using the new
              datatracker tool is summarized below.<o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC"><o:p> </o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC">A) ADs, WG
              chairs or draft authors request the review of a YANG
              module on Datatracker.<o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC">   - Sign in
              on Datatracker: <a moz-do-not-send="true"
                class="moz-txt-link-freetext"
                href="https://datatracker.ietf.org/accounts/login/?next=/">https://datatracker.ietf.org/accounts/login/?next=/</a><o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC">   - Go to
              the draft page (example): <a moz-do-not-send="true"
                href="https://datatracker.ietf.org/doc/draft-ietf-netmod-schema-mount/">https://datatracker.ietf.org/doc/draft-ietf-netmod-schema-mount/</a>
              <o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC">   - Click on
              the button "Review request" which brings you to (example):
              <a moz-do-not-send="true"
href="https://datatracker.ietf.org/doc/draft-ietf-netmod-schema-mount/reviewrequest/">https://datatracker.ietf.org/doc/draft-ietf-netmod-schema-mount/reviewrequest/</a>
              <o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC">   - Choose
              the type of review (Early, LC, Telechat) and set a
              recommended deadline<o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC">   - If
              required propose a reviewer in comments.<o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC"><o:p> </o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC">B) YANG
              secretary assigns the requested review to a reviewer.<o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC">   -
              Datatracker generates an email to the reviewer indicating
              the draft with the YANG module and the review deadline.<o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC">   - All
              assigned open review requests and closed review requests
              can be always listed at: <a moz-do-not-send="true"
                href="https://datatracker.ietf.org/group/yangdoctors/reviews/">https://datatracker.ietf.org/group/yangdoctors/reviews/</a>
              <o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC"><o:p> </o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC">   Notes: <o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC">   -
              Datatracker proposes a reviewer using based on the round
              robin approach.<o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC">   - YANG
              doctors can enter their availability into their
              datatracker account profile to avoid wrong assignments. <o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC"><o:p> </o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC">C) The
              reviewer enters the review result into the review tool.<o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC">   - The
              reviewer goes to the draft review request page at
              (example): <a moz-do-not-send="true"
href="https://datatracker.ietf.org/doc/draft-ietf-netmod-syslog-model/reviewrequest/8317/">https://datatracker.ietf.org/doc/draft-ietf-netmod-syslog-model/reviewrequest/8317/</a>
              <o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC">   - Clicks
              on "Complete review"<o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC">   - Enters
              state, reviewed revision, and the review result.<o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC">   - In case
              the reviewer enters the review result directly into the
              tool or uploads a text file, the tool generates an email
              to YANG Doctors maillist, draft authors and the related WG
              maillist.<o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC"><o:p> </o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC">Z) YANG
              doctors secretary will send a weekly summary of requested
              and ongoing reviews to YANG doctors maillist. <o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC">The first
              summary mail will be send out in parallel to this mail.<o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC"><o:p> </o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC">Notes:<o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC">- Old review
              assignments on the current review history page (<a
                moz-do-not-send="true"
                href="https://trac.ietf.org/trac/ops/wiki/yang-doctors-review-history">https://trac.ietf.org/trac/ops/wiki/yang-doctors-review-history</a>)
              will be migrated to the datatracker tool by the admin
              soon. The old page will be used for external review
              requests only.<o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC">- The Wiki
              page for the YANG review process will be updated within a
              week based on the collected feedback.<o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC"><o:p> </o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC">Thank you in
              advance for your suggestions and comments.<o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC">Please let us
              know if you have any questions.<o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC"><o:p> </o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC">Cheers,<o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC">Mehmet<o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#0000CC">(YANG Doctors
              Secretary)<o:p></o:p></span></p>
          <p class="MsoNormal"><o:p> </o:p></p>
        </div>
      </div>
    </div>
  </body>
</html>

--------------E85152AC52B45B7682FD30A4--


From nobody Wed Feb 22 15:53:42 2017
Return-Path: <kwatsen@juniper.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9EED1289B0 for <wgchairs@ietfa.amsl.com>; Wed, 22 Feb 2017 15:53:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.922
X-Spam-Level: 
X-Spam-Status: No, score=-1.922 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=junipernetworks.onmicrosoft.com
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 6iTpyaWBwfu0 for <wgchairs@ietfa.amsl.com>; Wed, 22 Feb 2017 15:53:38 -0800 (PST)
Received: from NAM03-BY2-obe.outbound.protection.outlook.com (mail-by2nam03on0098.outbound.protection.outlook.com [104.47.42.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E4B21293DA for <wgchairs@ietf.org>; Wed, 22 Feb 2017 15:53:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=junipernetworks.onmicrosoft.com; s=selector1-juniper-net; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=m6wXUVwQJQT8OCXHrXFJuK43FNbJ28FSgOzz5+S4VJI=; b=lB4b4pw2CJuQOW3ghv8mLcUQPIWNR5RqcydYlwPjrfDBbCtIVSPD6XHOUUroxZYKS6C6moKb38u1p3yetRvaX6vJ0ROShD2uWCSx2QGHTSnvskx9RuUqgNcV45l1obvMpPD6v4hkrZD2pMqKlDyTt1qzEwbznuz4+t6kGiuLyDE=
Received: from BN3PR0501MB1442.namprd05.prod.outlook.com (10.160.117.151) by BN3PR0501MB1443.namprd05.prod.outlook.com (10.160.117.152) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.919.10; Wed, 22 Feb 2017 23:53:32 +0000
Received: from BN3PR0501MB1442.namprd05.prod.outlook.com ([10.160.117.151]) by BN3PR0501MB1442.namprd05.prod.outlook.com ([10.160.117.151]) with mapi id 15.01.0919.018; Wed, 22 Feb 2017 23:53:32 +0000
From: Kent Watsen <kwatsen@juniper.net>
To: Henrik Levkowetz <henrik@levkowetz.com>
Subject: draft's [Email] link using @tools.ietf.org again
Thread-Topic: draft's [Email] link using @tools.ietf.org again
Thread-Index: AQHSjWbfEf/GsQOMEUuukyONwr0pbA==
Date: Wed, 22 Feb 2017 23:53:31 +0000
Message-ID: <1E4DCDAC-2327-4768-B109-A9FBCE0B4C83@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.1f.0.170216
authentication-results: levkowetz.com; dkim=none (message not signed) header.d=none;levkowetz.com; dmarc=none action=none header.from=juniper.net;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [66.129.241.11]
x-ms-office365-filtering-correlation-id: 542cf0ff-35b1-4102-c1a1-08d45b7e01d8
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(48565401081); SRVR:BN3PR0501MB1443; 
x-microsoft-exchange-diagnostics: 1; BN3PR0501MB1443; 7:TPEEGVDdAaxK/NjDnSMJxsna/DP1TdkgJk7bq3CI1qFj9i/tD2ljfj5rKsKIpnQEUQaWd40sih6S959P+lMV4rYZT/wiLQKcBGk7j9PNL4VObT+6eb/J3PeGtRiEQStohzOZil72MHxkEXOTTJvqfQ9gRBOWSX5Yckt3dRIFKE25t0VMWeQTewjLO64M2FqrVBwFNXSdXFqBTKYZDiHbrW1w1TyEJkLrsgTMNfc3UcWkcswKP7WNKEn0BKRI94BUpWGhETLspIu6uKWx1UB0Myt+71hAl/hdPgbLw/PSUEdLNPgmYxObvaLJAs/XEYSkRR/iDMygNGAuIrtde02wSA==
x-microsoft-antispam-prvs: <BN3PR0501MB14435B5EA801526DA936E82AA5500@BN3PR0501MB1443.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6055026)(6041248)(20161123555025)(20161123562025)(20161123560025)(20161123558025)(20161123564025)(6072148); SRVR:BN3PR0501MB1443; BCL:0; PCL:0; RULEID:; SRVR:BN3PR0501MB1443; 
x-forefront-prvs: 022649CC2C
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(979002)(6009001)(7916002)(39860400002)(39450400003)(39840400002)(39410400002)(39850400002)(305945005)(6916009)(6116002)(3846002)(3660700001)(83716003)(8676002)(54356999)(81166006)(5660300001)(38730400002)(2906002)(6306002)(7736002)(77096006)(6486002)(6512007)(82746002)(4326007)(8936002)(6436002)(25786008)(110136004)(3280700002)(83506001)(6506006)(99286003)(102836003)(53936002)(2900100001)(33656002)(86362001)(122556002)(189998001)(92566002)(50986999)(66066001)(106116001)(36756003)(4001350100001)(104396002)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1102; SCL:1; SRVR:BN3PR0501MB1443; H:BN3PR0501MB1442.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <69653E60FC10D84A802903D1CD284EE0@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Feb 2017 23:53:31.8840 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR0501MB1443
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/ucaLQ_sifhX2wLTLpmoCOqnRq6Q>
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 23:53:41 -0000

SGkgSGVucmlrLA0KDQpJdCBsb29rcyBsaWtlIHRoZSBbRW1haWxdIGxpbmsgb24gZHJhZnQgcGFn
ZXMgaXMgdXNpbmcNCkB0b29scy5pZXRmLm9yZyBhZ2Fpbi4gIElJUkMsIGl0IHNob3VsZCBiZSBq
dXN0IEBpZXRmLm9yZy4NCkkgZG9uJ3Qga25vdyBob3cgbWFueSBkcmFmdHMgdGhpcyBlZmZlY3Rz
LCBidXQgaXQgZGVmaW5pdGVseQ0KZWZmZWN0cyBbMV0gYW5kIFsyXS4NCg0KRldJVywgZGF0YXRy
YWNrZXIncyAiRW1haWwgZXhwYW5zaW9ucyIgdGFiIHByb3ZpZGVzIHRoZQ0KY29ycmVjdCBlbWFp
bCBhZGRyZXNzZXMuDQoNClsxXSBodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0
Zi1hbmltYS12b3VjaGVyLTAwDQpbMl0gaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0
LWlldGYtbmV0bW9kLXJldmlzZWQtZGF0YXN0b3Jlcy0wMA0KDQpUaGFua3MsDQpLZW50DQoNCg0K


From nobody Thu Feb 23 04:55:58 2017
Return-Path: <henrik@levkowetz.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42840129721 for <wgchairs@ietfa.amsl.com>; Thu, 23 Feb 2017 04:55:56 -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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 OyH_3DV2_N_u for <wgchairs@ietfa.amsl.com>; Thu, 23 Feb 2017 04:55:55 -0800 (PST)
Received: from durif.tools.ietf.org (durif.tools.ietf.org [IPv6:2001:1900:3001:11::3d]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 102DE129715 for <wgchairs@ietf.org>; Thu, 23 Feb 2017 04:55:55 -0800 (PST)
Received: from h-43-30.a357.priv.bahnhof.se ([79.136.43.30]:61579 helo=[192.168.1.120]) by durif.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1cgsw5-0001lK-Ov; Thu, 23 Feb 2017 04:55:54 -0800
To: Kent Watsen <kwatsen@juniper.net>
References: <1E4DCDAC-2327-4768-B109-A9FBCE0B4C83@juniper.net>
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <58AEDBD1.9080907@levkowetz.com>
Date: Thu, 23 Feb 2017 13:55:45 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <1E4DCDAC-2327-4768-B109-A9FBCE0B4C83@juniper.net>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="XjIM0MC2jl16JfxFF9R1SBnoE10rreCtg"
X-SA-Exim-Connect-IP: 79.136.43.30
X-SA-Exim-Rcpt-To: wgchairs@ietf.org, kwatsen@juniper.net
X-SA-Exim-Mail-From: henrik@levkowetz.com
Subject: Re: draft's [Email] link using @tools.ietf.org again
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on durif.tools.ietf.org)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/WSWp3PdspT4DeIq1R-4rdCyq8io>
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 12:55:56 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--XjIM0MC2jl16JfxFF9R1SBnoE10rreCtg
Content-Type: multipart/mixed; boundary="vjNp9H2t2IbIQcnUq9Bc3TPdwQNhKdrs3";
 protected-headers="v1"
From: Henrik Levkowetz <henrik@levkowetz.com>
To: Kent Watsen <kwatsen@juniper.net>
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>
Message-ID: <58AEDBD1.9080907@levkowetz.com>
Subject: Re: draft's [Email] link using @tools.ietf.org again
References: <1E4DCDAC-2327-4768-B109-A9FBCE0B4C83@juniper.net>
In-Reply-To: <1E4DCDAC-2327-4768-B109-A9FBCE0B4C83@juniper.net>

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

Hi Kent,

On 2017-02-23 00:53, Kent Watsen wrote:
> Hi Henrik,
>=20
> It looks like the [Email] link on draft pages is using
> @tools.ietf.org again.  IIRC, it should be just @ietf.org.
> I don't know how many drafts this effects, but it definitely
> effects [1] and [2].

Ugh.  Didn't I fix this once?  If so, I think I've fixed it better
now ;-)

The @tools.ietf.org addresses will linger for a while, as the htmlized
versions are stored on disk and are refreshed by the script as the
cache times out.  But I've verified proper generation for the drafts
you mention below.

> FWIW, datatracker's "Email expansions" tab provides the
> correct email addresses.
>=20
> [1] https://tools.ietf.org/html/draft-ietf-anima-voucher-00
> [2] https://tools.ietf.org/html/draft-ietf-netmod-revised-datastores-00=



Best regards,

	Henrik



--vjNp9H2t2IbIQcnUq9Bc3TPdwQNhKdrs3--

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

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

iQIcBAEBCAAGBQJYrtvRAAoJEE6bV0uPuxcaoVkP/jiM9Q9TEzUs2w6wLes/Lhwa
XTm9a7nrAS4YZJQDwh8dlohUWjr9vw/HMNr5A7OvuBegcprdeRRQ9Nvu91ErXWiM
yDuEDWf1RvrnTwG8pGHT3uWUySLqQp1h4OY639E6zgK+baoYXzm0/nGgH1gtgrBn
gKIVp383HTr1Yg+cN6wfpl9PK62OEgjDHcpk5YoTx1o0Z22/TgfeMEzTkDfSLaWf
HSc0eGqPrc7eO6gRpVA7bmCBTJ6Zkt0Ok1e7cKUclvYTs45veseZBDsalB2dSdbg
Pb+krKvehbGOHso/V+gHHY89ZT3lDvCsLr9Zxq6p2ADcIQvh6xs6TxflyDaVfUh3
v/A0CDUStL0b2oFAhlhhyEm3mZiR+VlgtzqCB+YUDHRCWWKicJTP95ABmD7AItkZ
yFEgFy4jue42NNBFeFuCRO9XgvGX63xkTXc2sEMjR+y2UeNMEEVkkviVUcdEHAhh
Cy6qZk0XVvr1xOarYP1ORNXFWYs8mVGQShTLUfKpSByKOKkcftGT8/pJVqi2pfM1
++R3zqJT2oDaWnTVILcQfJZDxKFSNsAyh0aNKu6AEAyvBpxu6ngEgJW/a4QDgLFE
Af03S4j6FbQA4PAuI6RRtzDrLw5ZAPQUQ8B9WaruxPRYoErnMwdx+81Sw9eBdvzE
nQW8G72yXJjDCqUGWsEn
=nPZK
-----END PGP SIGNATURE-----

--XjIM0MC2jl16JfxFF9R1SBnoE10rreCtg--


From nobody Fri Feb 24 02:38:52 2017
Return-Path: <henrik@levkowetz.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFC7E1295C3; Fri, 24 Feb 2017 02:38: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] autolearn=ham autolearn_force=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 WcsLlJPLYSmJ; Fri, 24 Feb 2017 02:38:40 -0800 (PST)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 25FDE1294AF; Fri, 24 Feb 2017 02:38:40 -0800 (PST)
Received: from henrik by zinfandel.tools.ietf.org with local (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1chDGp-0006Ie-Uu; Fri, 24 Feb 2017 02:38:39 -0800
To: codesprints@ietf.org, iesg@ietf.org, wgchairs@ietf.org
Subject: New datatracker release: v6.46.0
Message-Id: <E1chDGp-0006Ie-Uu@zinfandel.tools.ietf.org>
From: Henrik Levkowetz <henrik@levkowetz.com>
Date: Fri, 24 Feb 2017 02:38:39 -0800
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Rcpt-To: codesprints@ietf.org, henrik@levkowetz.com, iesg@ietf.org,  wgchairs@ietf.org
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/szUWxrXyxeZ7has_HVrQ8kxCB78>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 10:38:42 -0000

Hi,

This is an automatic notification about a new datatracker release, 
v6.46.0, generated when running the mkrelease script.

Release notes:

ietfdb (6.46.0) ietf; urgency=medium

  **Name i18n Improvements, tweaks to Group Pages and Account Setup**

  This release introduces use of non-ascii names in the name parts of outgoing
  emails instead of always using asciified names.  It improves the account
  setup workflow, improves the ease of editing group attributes and makes it
  more apparent which attributes can be edited.  It also adds a code quality
  assurance tool which makes easy notification on unexpected states available,
  and applies it to one difficult-to-debug issue.  There are also a number of
  bugfixes, as usual.  From the commit log:

  * Changes to address ease of editing various group attributes, in particular
    intended to make it easier to see that you can edit things like the
    external/additional URLs:

    - Added the ability to edit individual fields in a group's about page, and
      added edit buttons for editable fields on the about page, just as for
      documents (the ability to edit all editable fields already was available
      from the 'Edit group' button on the /group//about/ page).

    - Made the tab label for the group-about tab consistently say 'About',
      instead of 'Charter' for some groups.

    - Shifted the position of the about tab to the start of the tab line.

    - Removed the datatracker account requirement information at the top of the
      group edit page for users logged in to their account.

    - Tweaked the 'Show update' link on the 'Status Update' line.

    - Changed the label for the external URLs from 'More Info' to 'Additional
      URLs', which was already in use on the edit form.

  * Fixed a html issue on the review request page.

  * Made some changes to the missing-email submission handling.  This may have
    fixed the creation of author records containing 'none' email entries, but
    as I've not been able to reproduce the issue, this is uncertain.

  * Made the logging settings explicit in ietf/settings.py (instead of copying
    default then modifying), and added enough surrounding information to make
    it possible to read also for people not very familiar with Python's
    intricate logging infrastructure.  To a large extent to understand myself
    how the logging is set up in Django, and where to hook in the affirm()
    function.

  * Added an affirm($statement) function, which acts like an assert, and
    lets us trigger an email message with traceback when the statement to
    affirm is False.  Use instead of assert if we still want the server to
    produce a response, even if something is wrong with the internal state.

  * Added a log.affirm() call at the point where we may discover new flawed
    document author records.  Fixed a place where the generation of
    Person.ascii from Person.name wasn't done well.

  * Changed the AD email list results from get_group_ad_emails() to make more
    sense when the group is an area, not a wg.

  * Fixed url lookups for doc.views_doc.document_main() to only use
    dotted-path, and removed the doc_view explicit url name.  Fixes a 500
    error in /submit/status/NNNN/.

  * Added explicit charset setting and consistent encoding to several email
    paths through the datatracker.  After introducing support for non-ascii
    names in email addresses, using role.formatted_email() to insert names
    into email content doesn't work any more, since uncode names will now be
    rfc2047-encoded in formatted_email().  Added another method
    role.name_and_email() for this case.  Replaced another case of '%s <%s>'
    name-and-email formatting with formataddr().  Fixed some tests which did
    not send unicode email bodies to the email functions.  Fixes issue #2017.

  * Added a validator to Document.title to prevent control chars in the title
    (this complements a recent cleanup of more than 120 instances of document
    titles containing vertical tabs).

  * Changed the New Account creation to require a proper name at the same time
    as the account password is set, before actually creating the account.
    Also tweaked the password strength and confirmation code.

 -- Henrik Levkowetz <henrik@levkowetz.com>  23 Feb 2017 13:07:38 -0800

The new version is available for installation through SVN checkout, with
  'svn checkout https://svn.tools.ietf.org/svn/tools/ietfdb/tags/6.46.0'

For development, copy the new development version instead:
  'svn copy https://svn.tools.ietf.org/svn/tools/ietfdb/tags/dev/6.46.1.dev0' <YOURBRANCH>

Regards,

	Henrik
	(via the mkrelease script)


From nobody Fri Feb 24 08:20:05 2017
Return-Path: <iad@ietf.org>
X-Original-To: wgchairs@ietf.org
Delivered-To: wgchairs@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 145FE129C19; Thu, 23 Feb 2017 15:27:10 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: IETF Administrative Director <iad@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Subject: Proposed IETF Statement Concerning Personal Data for Review
X-Test-IDTracker: no
X-IETF-IDTracker: 6.45.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148789243004.21178.7922360111519513594.idtracker@ietfa.amsl.com>
Date: Thu, 23 Feb 2017 15:27:10 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/ymHV8BGJ6v68b88ITH4mWvw94I0>
X-Mailman-Approved-At: Fri, 24 Feb 2017 08:20:05 -0800
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: ietf@ietf.org
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 23:27:10 -0000

The IAOC would like community input on a proposed IETF Statement
Concerning Personal Data.

The policy discusses the following:
  1.  General â€“ Most Personal Data Submitted to the Parties Will Become Public
  2.  You Consent to International Transmission of Your Data 
  3.  Exceptions â€“ Information That We Do Not Release to the Public
  4.  Security
  5.  Children
  6.  Inquiries
  7.  Compliance
  8.  Other Organizations
  9.  Links to other sites.
  10.  Consent

The proposed Privacy Policy is located here:
https://iaoc.ietf.org/documents/Privacy-Statement-23Feb17.htm

The previous policy was posted for community review on 24 February
2016. This new version reflects input received during that community
review and a diff file reflecting the changes since that version is
located here:

https://iaoc.ietf.org/documents/Diff-Privacy-2016-02-24-02-Privacy-23Feb17.pdf

The IAOC will consider all comments received by 9 March 2017.

Ray Pelletier
IETF Administrative Director


From nobody Fri Feb 24 14:55:02 2017
Return-Path: <agenda@ietf.org>
X-Original-To: wgchairs@ietf.org
Delivered-To: wgchairs@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EA58129527; Fri, 24 Feb 2017 14:55:01 -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 98 Preliminary Agenda
X-Test-IDTracker: no
X-IETF-IDTracker: 6.46.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148797690141.3184.13714089851024309599.idtracker@ietfa.amsl.com>
Date: Fri, 24 Feb 2017 14:55:01 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/0ZYeGaGGDPxRK6yMIJDkBmRlvZ8>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 22:55:01 -0000

The IETF 98 preliminary agenda has been posted. The final agenda will be published on Friday, March 3, 2017.  

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.

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

Thank you!

IETF Secretariat


From nobody Sat Feb 25 20:31:43 2017
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EB05129890; Sat, 25 Feb 2017 20:31:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 vawRi4LcPRfK; Sat, 25 Feb 2017 20:31:26 -0800 (PST)
Received: from mail-it0-x22b.google.com (mail-it0-x22b.google.com [IPv6:2607:f8b0:4001:c0b::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BCD4A129884; Sat, 25 Feb 2017 20:31:26 -0800 (PST)
Received: by mail-it0-x22b.google.com with SMTP id h10so43840428ith.1; Sat, 25 Feb 2017 20:31:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=vXEpMZqbv1wzOghG/aK5tGQUJzL8Nr71SQg5b5NCIsM=; b=AZfSIUq76cUX1TX4UA+Bk/MD3Lmiw6hGVL0U2QvOBg9zqVTLK/PQuisdKwkvK9eCoz fkAvPPj8eZnUXQgOOibzcWf600kU0iSGegpV7BLznqdmF6wEUoqtWfz/V3r4/Hj9/TmW +jT9H4eKaCmS1nGpB73PX7DJ3blQhnOccGgMJNNmkZzFK01Gxrk8J2f8lQvxvJKTz0E4 wH+fDdiy26pWnPLB5/sPHEj2okK9uzXRkVGwayhFyviAUpj3kTt6fLC6wKWDfmObaHBW 0QbWHRxl5R9OnOP8IMTtYR2WrgYyEOkBQJ/BV+mNnSUQKtbKvRucAS8nNYb+3S1onaSZ FZVQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=vXEpMZqbv1wzOghG/aK5tGQUJzL8Nr71SQg5b5NCIsM=; b=eBD+5NpJ7DK9SpN5wboiWr8n83KBk05eJWY7xtpr+SMX8o2Q9a3w1YKNumerrB9iV2 K78ab5Zl5ky2xbv22y2XtmozpJfe7M/zZbREUASXBoa0xtLYSj5fRDaxL0rBvCazKfy1 KZ+Jvjct8D+uhbdjxgCfy0XSlIe5nJR6ophVj1yqEHfB78nc9gRXnQzM0duzu7+D0cUR +d6qNm6DU2WIdEd0kmsvnptp6YfaX/2z8+RDH7h/nIgvCSQ9w6ggCyE+JrnG8KXe6J6L kF3xurekau8usFeDDQaeJcr95IpRDnk+smIQ4LfY/NmWgiH6za7ca+wn0yO1BmnvcJH0 OIWA==
X-Gm-Message-State: AMke39mgd7z0ZC1hlrRebvuWZuGNGBYGy/mlKY+nQeIh2pailfjzkLkl3xi50lm1wYi1/UTUhk+MPT+t7hp9IA==
X-Received: by 10.36.61.136 with SMTP id n130mr9890912itn.107.1488083485979; Sat, 25 Feb 2017 20:31:25 -0800 (PST)
MIME-Version: 1.0
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.107.55.134 with HTTP; Sat, 25 Feb 2017 20:31:25 -0800 (PST)
In-Reply-To: <148797690141.3184.13714089851024309599.idtracker@ietfa.amsl.com>
References: <148797690141.3184.13714089851024309599.idtracker@ietfa.amsl.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Sat, 25 Feb 2017 20:31:25 -0800
X-Google-Sender-Auth: ebaJAlhG0wZfD0jn1HwZLsJd_Yw
Message-ID: <CAC4RtVDAAYG0r92WwNFmuTY2By_kwiLpq6hQ2p4UGwHv6905Bg@mail.gmail.com>
Subject: Re: IETF 98 Preliminary Agenda
To: IETF Agenda <agenda@ietf.org>, IESG <iesg@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/6GTLMCLCvRqaAc6a0gFkvuyzmIE>
Cc: Working Group Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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 Feb 2017 04:31:38 -0000

It seems likely that ACE has some participants who also ought be at
DISPATCH, so it might be good to deconflict them.

UTA is a heavily Sec-related ART group, so it seems that having it in
conflict with a Sec BoF (teep) isn't great.

I'd like to avoid removing all Sec people from JMAP (by having JMAP
and SAAG conflict).  On the other hand, as it'll be the very start of
the JMAP work, we can probably tolerate that, and bring the Sec people
in later.

Barry


From nobody Sun Feb 26 06:21:46 2017
Return-Path: <aamelnikov@fastmail.fm>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 354B7129959; Sun, 26 Feb 2017 06:21:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.82
X-Spam-Level: 
X-Spam-Status: No, score=-0.82 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastmail.fm header.b=hOWy5iTm; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=cqWyVRV9
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 dbuAEoeyOqPb; Sun, 26 Feb 2017 06:21:36 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E4A931298CE; Sun, 26 Feb 2017 06:21:35 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id DAC5C20655; Sun, 26 Feb 2017 09:21:32 -0500 (EST)
Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Sun, 26 Feb 2017 09:21:32 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=eKCSWrlDvMQqvHK JTdQowSgzV4A=; b=hOWy5iTmo6ZUD9my9ee/PJsaLOf6EsfJnI5f3P4jkArRYtv KF7oozkVIlvnvDxnhQ6HsTBJESCTLHyZuFGAxg10c/iInLEzvtaXkFQRRhmPsXOw /HpiuPScIo7zAD/yPrUtRihmxNMukjNKrM4le2vP1uEnQJxoGBAJZKUifYwo=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= smtpout; bh=eKCSWrlDvMQqvHKJTdQowSgzV4A=; b=cqWyVRV9YM87ox55Q0F9 6FW8QoMEzL6vQ2pHOn5v/VUMyeiOMOtdR3UTmLpVyxebEt7X3THMKgW7NBrVtSxU w27kS6Rk28RxKXXuaAktyULEmfqT42MQ5fN6yfrNS+GYDiDWU/2RUpv4EiQrV+ng 2FxWTYc41hnphY6Cy+9E978=
X-ME-Sender: <xms:bOSyWPIXp6ZI15hM0aELKuDB7UG4GFj8BVKZ4eiQcApSicMfuxRjzg>
X-Sasl-enc: 1j5X5NlgjTKJATu/YH6V6WuXllXev8Tmfz2Q/XVm2QGq 1488118892
Received: from [192.168.0.6] (cpc5-nmal20-2-0-cust24.19-2.cable.virginm.net [92.234.84.25]) by mail.messagingengine.com (Postfix) with ESMTPA id 8E8CF7E334; Sun, 26 Feb 2017 09:21:32 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
Subject: Re: IETF 98 Preliminary Agenda
From: Alexey Melnikov <aamelnikov@fastmail.fm>
X-Mailer: iPad Mail (14A456)
In-Reply-To: <CAC4RtVDAAYG0r92WwNFmuTY2By_kwiLpq6hQ2p4UGwHv6905Bg@mail.gmail.com>
Date: Sun, 26 Feb 2017 14:40:40 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <74A828A9-1FA0-416E-83A9-EEDBF96EC45B@fastmail.fm>
References: <148797690141.3184.13714089851024309599.idtracker@ietfa.amsl.com> <CAC4RtVDAAYG0r92WwNFmuTY2By_kwiLpq6hQ2p4UGwHv6905Bg@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/sOOv5TB99A943ifl2uLwdbxHbhc>
Cc: Working Group Chairs <wgchairs@ietf.org>, IETF Agenda <agenda@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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 Feb 2017 14:21:41 -0000

Hi Barry,

> On 26 Feb 2017, at 04:31, Barry Leiba <barryleiba@computer.org> wrote:
>=20
> UTA is a heavily Sec-related ART group, so it seems that having it in
> conflict with a Sec BoF (teep) isn't great.

I don't think overlap is going to be that great. But if it helps, we can swa=
p UTA with CORE (same day, previous slot)?
>=20
> I'd like to avoid removing all Sec people from JMAP (by having JMAP
> and SAAG conflict).  On the other hand, as it'll be the very start of
> the JMAP work, we can probably tolerate that, and bring the Sec people
> in later.

Yes, this is unfortunate, but liveable.



From nobody Sun Feb 26 22:10:34 2017
Return-Path: <cabo@tzi.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67C4B129B0C; Sun, 26 Feb 2017 22:10:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 ybUAbBjSDX8H; Sun, 26 Feb 2017 22:10:32 -0800 (PST)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 34198129665; Sun, 26 Feb 2017 22:10:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v1R6APUR006267; Mon, 27 Feb 2017 07:10:25 +0100 (CET)
Received: from [192.168.217.124] (p5DCCCDC2.dip0.t-ipconnect.de [93.204.205.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3vWrsr5yzGzDHW7; Mon, 27 Feb 2017 07:10:24 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [irsg] IETF 98 Preliminary Agenda
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <74A828A9-1FA0-416E-83A9-EEDBF96EC45B@fastmail.fm>
Date: Mon, 27 Feb 2017 07:10:24 +0100
X-Mao-Original-Outgoing-Id: 509868624.220581-283964da554f012e910adf6ff3f1b6a9
Content-Transfer-Encoding: quoted-printable
Message-Id: <378FAF0E-6EC5-4D10-9931-6EB96A0D1A79@tzi.org>
References: <148797690141.3184.13714089851024309599.idtracker@ietfa.amsl.com> <CAC4RtVDAAYG0r92WwNFmuTY2By_kwiLpq6hQ2p4UGwHv6905Bg@mail.gmail.com> <74A828A9-1FA0-416E-83A9-EEDBF96EC45B@fastmail.fm>
To: Alexey Melnikov <aamelnikov@fastmail.fm>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/7L7YfuT7ppfO45EHthrqYRAO7jE>
Cc: Working Group Chairs <wgchairs@ietf.org>, Barry Leiba <barryleiba@computer.org>, IETF Agenda <agenda@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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 Feb 2017 06:10:33 -0000

I believe the TEEP BOF should be of very high interest to the CORE =
audience, so this would be unfortunate.

Gr=C3=BC=C3=9Fe, Carsten


> On 26 Feb 2017, at 15:40, Alexey Melnikov <aamelnikov@fastmail.fm> =
wrote:
>=20
> we can swap UTA with CORE


From nobody Mon Feb 27 01:28:57 2017
Return-Path: <aamelnikov@fastmail.fm>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26CFB1294CA; Mon, 27 Feb 2017 01:28:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.719
X-Spam-Level: 
X-Spam-Status: No, score=-2.719 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, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastmail.fm header.b=KZc1aIqj; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=CxBxaUYn
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 v8VoaSAtH6OD; Mon, 27 Feb 2017 01:28:55 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2FA5F129410; Mon, 27 Feb 2017 01:28:55 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 9E68E20575; Mon, 27 Feb 2017 04:28:54 -0500 (EST)
Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Mon, 27 Feb 2017 04:28:54 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=WFF6GbecWQnORr7 WyMKkKpSoxVQ=; b=KZc1aIqjs6PPJUjxZB3jJQhIjKgUW9yolOf3W4H/GQ3wIOG acZrhdJhIEFfEjjVP5qqVHcOa/caTn0pP6esimHvyRywNaul/pSSSLSXIdOv5Cnd gZbukOsxsMIOEEePr3+EHwUw9HcNnngIH7rYXW1zxCpdXAbV+agHv4nu9wS4=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= smtpout; bh=WFF6GbecWQnORr7WyMKkKpSoxVQ=; b=CxBxaUYnGGYO/SYreAFW eSFBO+so0/vVBrChOxb9nGNLJfwOJH/OmxUbB5en4DOgQpne+YiC5hqOpgzObS3M WKxVelIjkCXlmYtj97lLUJshKLMVrjfbvsPIa7FFOAg7lp+zq/jConXbGFDvD2N7 tJAZYwYONanwnECe7CMyw7o=
X-ME-Sender: <xms:VvGzWPJvglw82v2gTjkn3Gcx6YR61fjE2p_LcePut9bbu3YtUdWO6g>
X-Sasl-enc: jJvXWRX91veyZyGEwj6DRSrbUTOziQrdrBxaIK3GSVQi 1488187734
Received: from [10.213.251.207] (unknown [85.255.235.175]) by mail.messagingengine.com (Postfix) with ESMTPA id 3ED06240CA; Mon, 27 Feb 2017 04:28:54 -0500 (EST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
Subject: Re: [irsg] IETF 98 Preliminary Agenda
From: Alexey Melnikov <aamelnikov@fastmail.fm>
X-Mailer: iPhone Mail (13G35)
In-Reply-To: <378FAF0E-6EC5-4D10-9931-6EB96A0D1A79@tzi.org>
Date: Mon, 27 Feb 2017 09:41:02 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <D69A43ED-3035-46C5-A3FE-2411C96B0358@fastmail.fm>
References: <148797690141.3184.13714089851024309599.idtracker@ietfa.amsl.com> <CAC4RtVDAAYG0r92WwNFmuTY2By_kwiLpq6hQ2p4UGwHv6905Bg@mail.gmail.com> <74A828A9-1FA0-416E-83A9-EEDBF96EC45B@fastmail.fm> <378FAF0E-6EC5-4D10-9931-6EB96A0D1A79@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/Ao5_mKyDsL8OQQUIds4io7513y0>
Cc: Working Group Chairs <wgchairs@ietf.org>, Barry Leiba <barryleiba@computer.org>, IETF Agenda <agenda@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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 Feb 2017 09:28:56 -0000

> On 27 Feb 2017, at 06:10, Carsten Bormann <cabo@tzi.org> wrote:
>=20
> I believe the TEEP BOF should be of very high interest to the CORE audienc=
e, so this would be unfortunate.

Thank you for bring this up. Yes, TEEP/CORE conflict is worse than TEEP/UTA c=
onflict. So I am tempted to leave this as is.

> Gr=C3=BC=C3=9Fe, Carsten
>=20
>=20
>> On 26 Feb 2017, at 15:40, Alexey Melnikov <aamelnikov@fastmail.fm> wrote:=

>>=20
>> we can swap UTA with CORE
>=20


From nobody Mon Feb 27 06:25:34 2017
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20ADF12A020; Mon, 27 Feb 2017 06:25: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, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 i-v-gXUWe4Te; Mon, 27 Feb 2017 06:25:32 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0133A129FE3; Mon, 27 Feb 2017 06:25:31 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id F30ADE206; Mon, 27 Feb 2017 09:47:41 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 1DCA26381A; Mon, 27 Feb 2017 09:25:31 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Alexey Melnikov <aamelnikov@fastmail.fm>
Subject: Re: IETF 98 Preliminary Agenda
In-Reply-To: <74A828A9-1FA0-416E-83A9-EEDBF96EC45B@fastmail.fm>
References: <148797690141.3184.13714089851024309599.idtracker@ietfa.amsl.com> <CAC4RtVDAAYG0r92WwNFmuTY2By_kwiLpq6hQ2p4UGwHv6905Bg@mail.gmail.com> <74A828A9-1FA0-416E-83A9-EEDBF96EC45B@fastmail.fm>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.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-sha256; protocol="application/pgp-signature"
Date: Mon, 27 Feb 2017 09:25:31 -0500
Message-ID: <10488.1488205531@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/iASS6CDdHwJimJe6TfPRqIz3RC0>
Cc: Working Group Chairs <wgchairs@ietf.org>, Barry Leiba <barryleiba@computer.org>, IETF Agenda <agenda@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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 Feb 2017 14:25:33 -0000

--=-=-=
Content-Type: text/plain


Alexey Melnikov <aamelnikov@fastmail.fm> wrote:
    >> On 26 Feb 2017, at 04:31, Barry Leiba <barryleiba@computer.org> wrote:
    >>
    >> UTA is a heavily Sec-related ART group, so it seems that having it in
    >> conflict with a Sec BoF (teep) isn't great.

    > I don't think overlap is going to be that great. But if it helps, we
    > can swap UTA with CORE (same day, previous slot)?

So teep and core would overlap?  That seems worse to me.
(certainly for me)

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




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

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

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAli0NtoACgkQgItw+93Q
3WV4xQf9EOItSF0R4CHS4abydARNBGRORPI1NWsrEfm4piOjPcbAmwLlxUbwsO1e
mbf6QK7eFGhj2j7mpocxlNAXhu9vl+KIrLWdwt779dmHzALfyktWL6DiC4gr6H8A
tb8OWmosDWpbJaL5iSOmbaGjHkIMstjCMtvK3BSySwCINjlyJ7MftMsM34ts7pgN
sFO/PHi+TgEtjuvLL+g6kSd1GOh+274244R/3u7U1TrBxKCppz88FcTmoGtCGmLw
Nw9B/WtBstsOqPVr9W0X3BZU6+8Pd4fSGD6dlsdxhBQkkq92GOMRH+VlxXKvoZE2
Phf3XgafAtF4orwkF/W4gMUwUkzUbQ==
=uJBP
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Mon Feb 27 06:27:20 2017
Return-Path: <aamelnikov@fastmail.fm>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 544A712A028; Mon, 27 Feb 2017 06:27:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.719
X-Spam-Level: 
X-Spam-Status: No, score=-2.719 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, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastmail.fm header.b=qkp+oiZi; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=hxquKeCs
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 7uu-L_osXl5Q; Mon, 27 Feb 2017 06:27:17 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D0FA12A022; Mon, 27 Feb 2017 06:27:17 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id F25BD20708; Mon, 27 Feb 2017 09:27:16 -0500 (EST)
Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Mon, 27 Feb 2017 09:27:16 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=zgaYZzgaXGNdzuh wAtN0Qu6yWiw=; b=qkp+oiZiZxe/ZA8ozVjYOLboDkuj9lVxUQsqSu3KnFBYvPT YIQnpHyyg+k2k2OBlLVZK72VOmNgIhnlISNI98tlL27nfGHCynEN8sFysMzlJBU2 UPDLZhp7rLB/sfraVKyME2yBvlt71m0GByG+i/k23FYtiOFe7hXKM0sHlJHs=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= smtpout; bh=zgaYZzgaXGNdzuhwAtN0Qu6yWiw=; b=hxquKeCsL4IGN8a4FC/s Wh5nCaO3snQaD/cwCjYePEbQ1ulJNvX0HFMfU2pWBaL4FI24fmfr0lQV8CRgpbZW y4OIbZ6d8ysCof782lstMjzagAYtleuB1ZEc6C7gXEqx/20uyOWMpNdPlus5TrWZ vu9huhucOrvHiFcdfUTsM8E=
X-ME-Sender: <xms:RDe0WI8Ii9GG7OyMY_LTi02wSVFxsXd3XyukIrcOn7ARkpcG-roNSA>
X-Sasl-enc: ZvE9lSEJhOGRrFrusc9KQrblRcub8bJkDbr1qpYeU4lX 1488205636
Received: from [10.213.251.207] (unknown [85.255.235.175]) by mail.messagingengine.com (Postfix) with ESMTPA id 93CEC241DA; Mon, 27 Feb 2017 09:27:16 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
Subject: Re: IETF 98 Preliminary Agenda
From: Alexey Melnikov <aamelnikov@fastmail.fm>
X-Mailer: iPhone Mail (13G35)
In-Reply-To: <10488.1488205531@obiwan.sandelman.ca>
Date: Mon, 27 Feb 2017 14:39:25 +0000
Content-Transfer-Encoding: 7bit
Message-Id: <77B3611F-8AEF-45FA-87EB-85A5BBF2A3FD@fastmail.fm>
References: <148797690141.3184.13714089851024309599.idtracker@ietfa.amsl.com> <CAC4RtVDAAYG0r92WwNFmuTY2By_kwiLpq6hQ2p4UGwHv6905Bg@mail.gmail.com> <74A828A9-1FA0-416E-83A9-EEDBF96EC45B@fastmail.fm> <10488.1488205531@obiwan.sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/_j38ld45lievNjc06xTjbWpX-fQ>
Cc: Working Group Chairs <wgchairs@ietf.org>, Barry Leiba <barryleiba@computer.org>, IETF Agenda <agenda@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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 Feb 2017 14:27:18 -0000

Sent from my iPhone

> On 27 Feb 2017, at 14:25, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 
> 
> Alexey Melnikov <aamelnikov@fastmail.fm> wrote:
>>> On 26 Feb 2017, at 04:31, Barry Leiba <barryleiba@computer.org> wrote:
>>> 
>>> UTA is a heavily Sec-related ART group, so it seems that having it in
>>> conflict with a Sec BoF (teep) isn't great.
> 
>> I don't think overlap is going to be that great. But if it helps, we
>> can swap UTA with CORE (same day, previous slot)?
> 
> So teep and core would overlap?  That seems worse to me.
> (certainly for me)

No: currently TEEP and UTA overlap and I suggest no change.
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
> -= IPv6 IoT consulting =-
> 
> 
> 

