From nobody Tue Oct 9 13:37:58 2018 Return-Path: X-Original-To: pearg@ietfa.amsl.com Delivered-To: pearg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B402C1293FB for ; Tue, 9 Oct 2018 13:37:57 -0700 (PDT) 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 QBnIU4UpgbPx for ; Tue, 9 Oct 2018 13:37:55 -0700 (PDT) Received: from oz.law.harvard.edu (imap.metalab.harvard.edu [128.103.64.104]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2DA7D127148 for ; Tue, 9 Oct 2018 13:37:54 -0700 (PDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by oz.law.harvard.edu (Postfix) with ESMTP id 74D9610743; Tue, 9 Oct 2018 16:37:53 -0400 (EDT) Received: from oz.law.harvard.edu ([127.0.0.1]) by localhost (oz.law.harvard.edu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 01346-09; Tue, 9 Oct 2018 16:37:53 -0400 (EDT) Received: from turok.law.harvard.edu (adam.law.harvard.edu [128.103.64.74]) by oz.law.harvard.edu (Postfix) with ESMTP id 128BF1073A; Tue, 9 Oct 2018 16:37:53 -0400 (EDT) Received: from roundcube.berkman (localhost.localdomain [127.0.0.1]) by turok.law.harvard.edu (Postfix) with ESMTP id E62CC65B; Tue, 9 Oct 2018 16:37:52 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Tue, 09 Oct 2018 16:37:51 -0400 From: Griffin Boyce To: Stephen Farrell Cc: Sara Dickinson , pearg@irtf.org In-Reply-To: References: <9A133F31-500C-4B3B-9E17-432E87ABE204@sinodun.com> Message-ID: <5b2d01ecdba30a3ac6de8f3610f713f5@cyber.harvard.edu> X-Sender: gboyce@cyber.harvard.edu User-Agent: Roundcube Webmail/1.2-git X-Virus-Scanned: Debian amavisd-new at oz.law.harvard.edu Archived-At: Subject: Re: [Pearg] Updated Charter and meeting at IETF 103 X-BeenThere: pearg@irtf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Privacy Enhancements and Assessment Proposed RG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Oct 2018 20:37:58 -0000 On 2018-09-26 16:27, Stephen Farrell wrote: > "The chairs may at times appoint at their pleasure “closed” design > teams > with lesser reporting requirements (though results will be open). This > will allow for some limited discussions in which participants require > extra privacy/confidentiality." > > I think that's undesirable. I've also no idea what kind of design > team might make sense in an RG. I don't think any other current or > recent RG has been anything but fully open. I'd prefer that this > not be an exception. If there is a justification for such an > exception then I think that ought be explicit, but I don't recall > hearing one. (It's possible this was discussed in Montreal at the > bit of the f2f meeting I missed.) I agree that this is broadly undesirable. Unless there's an obvious use-case for confidentiality, *and* people foresee that happening imminently, I think that this would be a point of contention longer-term. (But full disclosure, I have missed the F2F meetings and this may have been covered there). all the best, Griffin Boyce On 2018-09-26 16:27, Stephen Farrell wrote: > Hiya, > > On 19/09/18 14:18, Sara Dickinson wrote: >> Hi All, >> >> Many thanks for all the feedback on the proposed Charter for the >> group. Based on this please find an updated Charter for PEARG on the >> wiki: https://trac.ietf.org/trac/irtf/wiki/pearg >> >> >> If you have further comments on this please make them on this list. > > The charter is looking pretty good generally. One comment below and > some nits that you could take or leave. > > "The chairs may at times appoint at their pleasure “closed” design > teams > with lesser reporting requirements (though results will be open). This > will allow for some limited discussions in which participants require > extra privacy/confidentiality." > > I think that's undesirable. I've also no idea what kind of design > team might make sense in an RG. I don't think any other current or > recent RG has been anything but fully open. I'd prefer that this > not be an exception. If there is a justification for such an > exception then I think that ought be explicit, but I don't recall > hearing one. (It's possible this was discussed in Montreal at the > bit of the f2f meeting I missed.) > > Nits: > > - The IETF hasn't only suggested more encryption as a mitigation > for PM. For example Christian Huitema has done fine work on DHCP. > There are more examples. I think you could tweak the charter text > in various places to not give the impression that all the IETF and > IAB have done is "moar crypto." > > - PETS and SOUPS aren't standards bodies > > - "PEARG will participate" assumes PEARG is an entity whereas it'll > be a set of participants. > > If it helps I'd be fine to suggest/review specific wording changes > as per the above, but I don't think RG charters needs to be as > wordsmithed as IETF WG charters so I've not done that. > > Cheers, > S. > >> Also, we are planning to meet in Bangkok at IETF 103 and will have a >> short review of the Charter then. We are currently putting together >> the agenda for that meeting so if you have something you would like >> to present then please email Shivan and I to discuss. >> >> Best regards >> >> Sara. >> >> >> >> >> From nobody Tue Oct 16 09:46:36 2018 Return-Path: X-Original-To: pearg@ietfa.amsl.com Delivered-To: pearg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A88C130DF6 for ; Tue, 16 Oct 2018 09:46:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.001 X-Spam-Level: X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=salesforce.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 Qr8snVMfmiqW for ; Tue, 16 Oct 2018 09:46:32 -0700 (PDT) Received: from mail-it1-x135.google.com (mail-it1-x135.google.com [IPv6:2607:f8b0:4864:20::135]) (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 52647130DFD for ; Tue, 16 Oct 2018 09:46:32 -0700 (PDT) Received: by mail-it1-x135.google.com with SMTP id k206-v6so27905759ite.0 for ; Tue, 16 Oct 2018 09:46:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salesforce.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=PcYVN1WlTS8hsijDf2ThckZUujpyJgrhJVwSjXUKCB0=; b=BJNAf4Nc3b4iyNIFM66yGHX49Y/TR4t9ONCbivJ3kC4e8XcT+/ifSlUR0QogoVpCti J9k3NZ6BnxHVdeaNaEDbVRzIMaFbyeBt1nwaTSBsb0O9dJ+QXn/Q242417PUMeQ2A9CT odNOSuEKxVoCJlQ5npAx/h0hMTQ1vVfp/TzO4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=PcYVN1WlTS8hsijDf2ThckZUujpyJgrhJVwSjXUKCB0=; b=q827gSEkH5PksJVDe7vC6e8gZJJg9gBkngWntYTEsLYLyjYbIpg2Bf4lp1jHqsKxwO G0BrVut3ci3lQVLdlB9Z7JzgzRhvvBbfQOgtuziQWsVf05Ny0tNpieSYGDmNxJ306wn0 KmOCPOZjpSwdegDCTh6sq/Jvau4AP+l8uC4mJOfj0ez3f9dGrqIOgi//HqlUQzbuLeXD mCq37RUZ1F0qPjR6k/hBaJyGUo6cS0NYemvROu9eu6zWk/gidAAXvRwud1mo1pq2+x7M pRsrzQb50Ld+HwMX90eODPsm2O6S4taSuBccLb15lFCl6e63tuSNLmSpDZRGSHsqm8G3 eNow== X-Gm-Message-State: ABuFfoi/1dYN6mt30PuD1mVLmQ3JqL4MTPzNFy2WhmVCURHBimzZsNBT qumA9MYLnueHFHuPbZmGyHxUB/6BOeYGA/2/SS/xH8948KDp0A== X-Google-Smtp-Source: ACcGV610Kjrk3cYYHKVEZ4qhmJgkM69cFAasSnaPYfQc73gApOMTD8X5couNFSW1uFvO0W2ZTPZFSpRQVcKu3lp0pYk= X-Received: by 2002:a24:edc3:: with SMTP id r186-v6mr15670032ith.100.1539708391236; Tue, 16 Oct 2018 09:46:31 -0700 (PDT) MIME-Version: 1.0 References: <153938238379.29148.2724428032621852258.idtracker@ietfa.amsl.com> In-Reply-To: <153938238379.29148.2724428032621852258.idtracker@ietfa.amsl.com> From: Shivan Sahib Date: Tue, 16 Oct 2018 09:46:20 -0700 Message-ID: To: pearg@irtf.org Content-Type: multipart/alternative; boundary="000000000000b7e7d105785b4b3b" Archived-At: Subject: [Pearg] Fwd: [irsg] IETF 103 Final Agenda X-BeenThere: pearg@irtf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Privacy Enhancements and Assessment Proposed RG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Oct 2018 16:46:35 -0000 --000000000000b7e7d105785b4b3b Content-Type: text/plain; charset="UTF-8" Hi all, PEARG is scheduled for 15:40 - 17:10 pm (Bangkok time; ICT GMT+7) on Wednesday, Nov 7. We'll be on the 7th floor, meeting 1 breakout room. MeetEcho link (for remote participation): https://www.meetecho.com/ietf103/pearg/ ---------- Forwarded message -------- IETF 103 Bangkok, Thailand November 3-9, 2018 Hosts: Huawei and Cisco The IETF 103 final agenda is now available. At this point only Area Directors can submit changes in the form of a swap to agenda@ietf.org. https://datatracker.ietf.org/meeting/103/agenda.html https://datatracker.ietf.org/meeting/103/agenda.txt While this is considered the final agenda for printing, changes may be made to the agenda up until and during the meeting. Updates will be reflected on the web versions of the agenda. Code Lounge At IETF 103 WG Chairs will have the ability to organize sessions focused on running code in an effort to diversify the type of work that happens during IETF meetings. This will allow for groups to informally meet to brainstorm, code, and test ideas in the Code Lounge, a portion of the IETF lounge set aside for such activities. The area will be designated by signage. WG chairs can sign up for timeslots here: https://trac.ietf.org/trac/ietf/meeting/wiki/103codelounge WG Chairs are encouraged to look at the final agenda and determine timeslots that have the least conflict to ensure successful attendance to the Code Lounge sessions as well as any traditional working group sessions. It is okay for multiple WG chairs to sign up for the same timeslots. This is in fact encouraged for work that spans multiple WGs. Unofficial Side Meetings As communicated back in May ( https://www.ietf.org/mail-archive/web/ietf/current/msg107813.html), the IESG is running an agenda experiment on Friday of the IETF 103 meeting week. Monday through Thursday, we will have two rooms available for attendees to reserve for side meetings, as usual. On Friday, because there will be no working group meetings, we will have eight rooms available for unofficial side meetings. Projectors will be provided in all of the meeting rooms. Meetecho will not be recording or providing remote participation on Friday. Please note that all side meetings must conclude by 13:30. We realize that keeping track of all of these side meetings may prove challenging, so a calendar with subscription details can be found here: https://www.ietf.org/how/meetings/103/side-meetings/ - Meeting wiki: https://trac.ietf.org/trac/ietf/meeting/wiki/ietf103 - To reserve a side meeting room: https://trac.ietf.org/trac/ietf/meeting/wiki/103sidemeetings - IETF Meeting Room Policy: https://www.ietf.org/how/meetings/meeting-rooms-policy/ Thank you! IETF Secretariat --000000000000b7e7d105785b4b3b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi all,
<= br>
PEARG is scheduled for 15:40 - 17:10 pm (Bangkok time; ICT GM= T+7) on Wednesday, Nov 7. We'll be on the 7th floor, me= eting 1 breakout room.
MeetEcho link (for remote participatio= n): https://www.meetech= o.com/ietf103/pearg/


---------- Forwarded message --------
=
IETF 103
Bangkok, Thailand
November 3-9, 2018
Hosts: Huawei and Cisco

The IETF 103 final agenda is now available. At this point only Area Directo= rs can submit changes in the form of a swap to agenda@ietf.org.

https://datatracker.ietf.org/meeting/103/agenda.= html
https://datatracker.ietf.org/meeting/103/agenda.t= xt

While this is considered the final agenda for printing, changes may be made= to the agenda up until and during the meeting. Updates will be reflected o= n the web versions of the agenda.


Code Lounge

At IETF 103 WG Chairs will have the ability to organize sessions focused on= running code in an effort to diversify the type of=C2=A0work that happens = during IETF meetings. This will allow for groups to informally meet to brai= nstorm, code, and test ideas in=C2=A0the Code Lounge, a portion of the IETF= lounge set aside for such activities. The area will be designated by signa= ge. WG=C2=A0chairs can sign up for timeslots here:=C2=A0https://trac.ietf.org/trac/ietf/meeting/wiki/103codelounge

WG Chairs are encouraged to look at the final agenda and determine timeslot= s that have the least conflict to ensure=C2=A0successful attendance to the = Code Lounge sessions as well as any traditional working group sessions. It = is okay for multiple=C2=A0WG chairs to sign up for the same timeslots. This= is in fact encouraged for work that spans multiple WGs.


Unofficial Side Meetings

As communicated back in May (https:= //www.ietf.org/mail-archive/web/ietf/current/msg107813.html),=C2=A0the = IESG is running an agenda experiment on Friday of the IETF 103 meeting week= .

Monday through Thursday, we will have two rooms available for attendees to = reserve for side meetings, as usual. On Friday, because there will be no wo= rking group meetings, we will have eight rooms available for unofficial sid= e meetings. Projectors will be provided in all of the meeting rooms. Meetec= ho will not be recording or providing remote participation on Friday. Pleas= e note that all side meetings must conclude by 13:30.

We realize that keeping track of all of these side meetings may prove chall= enging, so a calendar with subscription details can be found here: https://www.ietf.org/how/meetings/103/side-meetings/

- Meeting wiki:=C2=A0https://trac.ietf.org/trac/= ietf/meeting/wiki/ietf103=C2=A0
- To reserve a side meeting room:=C2=A0h= ttps://trac.ietf.org/trac/ietf/meeting/wiki/103sidemeetings=C2=A0
- IETF Meeting Room Policy:=C2=A0https://www.= ietf.org/how/meetings/meeting-rooms-policy/

Thank you!

IETF Secretariat

--000000000000b7e7d105785b4b3b-- From nobody Fri Oct 19 12:36:22 2018 Return-Path: X-Original-To: pearg@irtf.org Delivered-To: pearg@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E406F13108C; Fri, 19 Oct 2018 11:56:32 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "\"IETF Secretariat\"" To: , Cc: pearg@irtf.org, irtf-chair@irtf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.87.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <153997539292.6592.145730620123717959.idtracker@ietfa.amsl.com> Date: Fri, 19 Oct 2018 11:56:32 -0700 Archived-At: X-Mailman-Approved-At: Fri, 19 Oct 2018 12:36:20 -0700 Subject: [Pearg] pearg - Requested session has been scheduled for IETF 103 X-BeenThere: pearg@irtf.org X-Mailman-Version: 2.1.29 List-Id: Privacy Enhancements and Assessment Proposed RG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Oct 2018 18:56:41 -0000 Dear Shivan Sahib, The session(s) that you have requested have been scheduled. Below is the scheduled session information followed by the original request. pearg Session 1 (1:30 requested) Wednesday, 7 November 2018, Afternoon Session II 1540-1710 Room Name: Meeting 1 size: 150 --------------------------------------------- iCalendar: https://datatracker.ietf.org/meeting/103/sessions/pearg.ics Request Information: --------------------------------------------------------- Working Group Name: Privacy Enhancements and Assessments Proposed Research Group Area Name: IRTF Session Requester: Shivan Sahib Number of Sessions: 1 Length of Session(s): 1.5 Hours Number of Attendees: 80 Conflicts to Avoid: First Priority: hrpc cfrg irtfopen Second Priority: dprive mls rtcweb tls httpbis quic dnssd saag People who must be present: Sara Dickinson Shivan Kaul Sahib Resources Requested: Special Requests: ---------------------------------------------------------