From nobody Thu Jul 2 04:26:12 2020 Return-Path: X-Original-To: tools-development@ietfa.amsl.com Delivered-To: tools-development@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF2043A0AF4 for ; Thu, 2 Jul 2020 04:26:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -9.6 X-Spam-Level: X-Spam-Status: No, score=-9.6 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, DKIM_VALID_EF=-0.1, HTML_MESSAGE=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 gNiduS_4QK1i for ; Thu, 2 Jul 2020 04:26:08 -0700 (PDT) Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 037933A0AE2 for ; Thu, 2 Jul 2020 04:26:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1772; q=dns/txt; s=iport; t=1593689168; x=1594898768; h=from:mime-version:subject:message-id:date:cc:to; bh=zeZTTMCgFZP92CY08xAYO9E7ZPuKndMBuTMWqof/BGk=; b=SmaOhfJ+fbt0a42VSMUAOb+ZYpmuvrydYQ13H6zUM2JZaj67NdXouNZ3 tN8kpsUp+n8/kIjxBxmTjg10GIAoHHhwPKoIsWAQGCciiNW7Sx43cYGJE /JQXo23qkaNEd0/ynl55MaaCAEcIgluEBxsaQO2pqB/hvjueExmU1AU5q U=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CjAwBgw/1e/xbLJq1gHAEBAQEBAQc?= =?us-ascii?q?BARIBAQQEAQFAgUqDGVQBIBIsjTKcA4YtgWgLAQEBDAEBIwwEAQGER4IfJTg?= =?us-ascii?q?TAgMBAQsBAQUBAQECAQYEbYVbDIVlgQkeAYRYAYJ8D6pNGTV0gTSEOgGBFoU?= =?us-ascii?q?bBoE4jQKCAIE4HIQPgVgCAQKBJwESAW6CfIItBJo0mlaCZoMGhUWQfwMdnx2?= =?us-ascii?q?bdZBzg1ECBAYFAhWBaiJmcDMaCBsVZQGCPj4SGQ2ONohthUQ/AzACNQIGCAE?= =?us-ascii?q?BAwmPXgEB?= X-IronPort-AV: E=Sophos; i="5.75,304,1589241600"; d="scan'208,217"; a="27610679" Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 02 Jul 2020 11:26:03 +0000 Received: from ams3-vpn-dhcp5065.cisco.com (ams3-vpn-dhcp5065.cisco.com [10.61.83.200]) by aer-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id 062BQ3Vo017666 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 2 Jul 2020 11:26:03 GMT From: Eliot Lear Content-Type: multipart/alternative; boundary="Apple-Mail=_A50DBC91-161C-4F43-AC60-70047C62710B" Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) Message-Id: Date: Thu, 2 Jul 2020 13:26:03 +0200 Cc: tools-development@ietf.org, Cindy Morgan To: rfced-future@iab.org X-Mailer: Apple Mail (2.3608.80.23.2.2) X-Outbound-SMTP-Client: 10.61.83.200, ams3-vpn-dhcp5065.cisco.com X-Outbound-Node: aer-core-1.cisco.com Archived-At: Subject: [TOOLS-DEVELOPMENT] IETF 108 Preliminary Agenda X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Tools Development mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jul 2020 11:26:10 -0000 --Apple-Mail=_A50DBC91-161C-4F43-AC60-70047C62710B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii This can be found at = https://datatracker.ietf.org/meeting/108/agenda.html = Our meeting slot is currently Monday, July 27th, 14:10 - 15:50 UTC. = There is a bug in the calendar system that is causing the program not to = be listed in the customizable calendar. If you download a custom ICS = file, be sure to remember this group if you want to participate ;-). By this email, I hope I am making the appropriate tooling people aware = of the issue. Eliot= --Apple-Mail=_A50DBC91-161C-4F43-AC60-70047C62710B Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii This can be found at https://datatracker.ietf.org/meeting/108/agenda.html

Our meeting slot is currently Monday, July 27th, 14:10 - 15:50 UTC.  There is a bug in the calendar system that is causing the program not to be listed in the customizable calendar.  If you download a custom ICS file,  be sure to remember this group if you want to participate ;-).

By this email, I hope I am making the appropriate tooling people aware of the issue.

Eliot
--Apple-Mail=_A50DBC91-161C-4F43-AC60-70047C62710B-- From nobody Fri Jul 10 13:47:29 2020 Return-Path: X-Original-To: tools-development@ietfa.amsl.com Delivered-To: tools-development@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFF063A09B5 for ; Fri, 10 Jul 2020 13:47:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.079 X-Spam-Level: X-Spam-Status: No, score=-2.079 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.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 f8faUIfvCL7s for ; Fri, 10 Jul 2020 13:47:15 -0700 (PDT) Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 93CD93A09A8 for ; Fri, 10 Jul 2020 13:47:15 -0700 (PDT) Received: from unescapeable.local ([47.186.30.41]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id 06AKlDoi049922 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Fri, 10 Jul 2020 15:47:14 -0500 (CDT) (envelope-from rjsparks@nostrum.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1594414034; bh=WSReWmrS9yLhkLhPKoSJ+XyNtDOdZ2N+UzoZzu1/3k4=; h=To:From:Subject:Date; b=cg3Z38M7EVQPBg23LFvBH3KnGoMYmRowVlML/sv+wx+kie2xvRHYHRTXqnYQ7f4Fx cKIB/tyeJkX637ifsGqB7IcDS97BGe6hESHTzXbncGkVMz55Oi6KElW/+zPZQ1hsEb u7/0ftWiXyxxvdAZfknRsPSHtGGjXOb/jBVV69K4= X-Authentication-Warning: raven.nostrum.com: Host [47.186.30.41] claimed to be unescapeable.local To: IETF Tools Development From: Robert Sparks Message-ID: Date: Fri, 10 Jul 2020 15:47:12 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Archived-At: Subject: [TOOLS-DEVELOPMENT] Tools call agenda -- 14 July 2020 at 1800 UTC X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Tools Development mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jul 2020 20:47:28 -0000 Note that, as usual, we do not have a tools call scheduled in August. The next call after this one is currently scheduled for 8 September. Please bash this agenda by email before we get to the meeting. I've added my notes to the message below instead of replying separately this time. If you have notes to add, please do so. ------------------------------------------------------------------------- Tools Call Agenda -- 14 July 2020 at 1800 UTC JOIN WEBEX MEETING https://ietf.webex.com/ietf/j.php?MTID=m440dd848726339c03e605b9956e38bac Meeting number (access code): 640 103 570 Meeting password: tools JOIN BY PHONE 1-877-668-4493 Call-in toll free number (US/Canada) 1-650-479-3208 Call-in toll number (US/Canada) Meeting number (access code): 640 103 570 Meeting password: tools 1. Hot Topics    - RFC Production blocking issues - Alice / Henrik    - IETF 108 tooling support - Robert / Alexa / Henrik    - Using the OpenID Connect / OAUTH2 provider - Robert    - Addressing larger infrastructure and architectural issues - Robert    - Are there any other priority tool changes needed? 2. Development Projects    - Reimplementing the IETF website wagtail templates - Robert    - Meeting Application Improvements (IOLA) - Robert    - Automated Scheduler Part II (DashCare) - Robert    - RPC Security Code Review (ZX Security) - Robert    - YangCatalog (Pantheon) - Éric / Robert    - Moving the datatracker to Django 2.2 - Robert    - DMARC/SPF for aliases - Henrik    - Capturing external resources in the datatracker - Robert    - Github backups - Robert 3. Operations Projects    - Are there any upcoming operations changes that need      coordination with this team? 4. Planning for upcoming projects    - Improving customization of calendars - Robert    - Exploring fronting web services with nginx - Robert    - Revising html/css/template structure for the website - Greg    - Moving the datatracker to postgresql - Robert 5. Are there any unmet needs?    - Open discussion 6. Any Other Business --------------------------------------------------------------------- My notes to help move the call along > 1. Hot Topics >    - RFC Production blocking issues - Alice / Henrik >    - IETF 108 tooling support - Robert / Alexa / Henrik This has been the primary focus the last several weeks for many of us. Between this and bufixes and contracted projects compeleting, there have been six releases of the datatracker since the last call. We are set up to use codimd instead of etherpad. We changed where codimd was deployed to provide ipv6. We've modified it (and the datatracker) to facilitate embedding codimd in frames in meetecho. Having many activities the week before the meeting "starts" (from the datatracker's perspective) has required manual work and creative solutions so that things appear on the agenda as we want them to. We have changed the configuration and a little code at the datatracker so that meeting materials (agenda, slides, minutes, etc) will be served through cloudflare. >   - Using the OpenID Connect / OAUTH2 provider - Robert Now that we are running an identity provider, we're starting to get requests to add clients. So far, the clients we've added have been driven by meeting support. Meetecho and codimd are set up. The programmers at gather.town are looking to see if they can integrate. We're getting queries from the community on how to integrate, including suggestions to use the provider for ietf.slack.com (which would involve adding a SAML provider). The way we plan to deal with requests to add clients is to have the tools implementation team vet the request, then make a recommendation to the IESG for approval or rejection. >   - Addressing larger infrastructure and architectural issues - Robert There are a set of things long in need of attention that we plan to work on between IETF 108 and 109. These include:   * Measuring and improving performance, particularly of the datatracker.   * Simplifying the filesystem structure that is used across applications.   * Removing the last dependencies on the www6 website pages.   * Adjusting the way the www.ietf.org url namespace is used. >   - Are there any other priority tool changes needed? > 2. Development Projects >    - Reimplementing the IETF website wagtail templates - Robert We have an RFP outstanding. It is about to enter the Q/A period with questions due 13Jul, and answers due 20Jul. Bids are due 27Jul. See: https://www.ietf.org/media/documents/RFP-WagtailDevelopment-20200629.pdf >    - Meeting Application Improvements (IOLA) - Robert IOLA continues to make steady progress, but still has several deliverables to complete. >    - Automated Scheduler Part II (DashCare) - Robert This is complete and deployed. Early testing shows there are a few rule additions we can make (easily) that would improve the algorithm. I am waiting until after 108 to show the secretariat how to use it. >    - RPC Security Code Review (ZX Security) - Robert The review is complete, and a (final?) report has been provided. The report doesn't cover how issues were resolved since the RPC will be doing that work, and have not yet completed it. >    - YangCatalog (Pantheon) - Éric / Robert Yangcatalog is now running as a set of Docker containers. Development of web frontends for the administration tasks that previously required shell access is well underway. We expect to see this deployed into amazon's cloud in the next few weeks. >    - Moving the datatracker to Django 2.2 - Robert This is complete. >    - DMARC/SPF for aliases - Henrik >    - Capturing external resources in the datatracker - Robert This should be ready to merge soon, possibly before the meeting. >    - Github backups - Robert Martin's CI tool and the extra script to capture metadata from repositories that are not using Marting's tool continue to improve. We are not yet making our own backups of repositories, but expect to be doing so within the next couple of weeks. > > 3. Operations Projects >    - Are there any upcoming operations changes that need >      coordination with this team? > > 4. Planning for upcoming projects >    - Improving customization of calendars - Robert We are gathering quotes from several contractors to improve the customized calendars on the main agenda page and to provide customized calendars for upcoming meetings. >    - Exploring fronting web services with nginx - Robert No progress this cycle. >    - Moving the datatracker to postgresql - Robert This will be included in the optimization work mentioned above. > > 5. Are there any unmet needs? >    - Open discussion > > 6. Any Other Business From nobody Wed Jul 15 19:05:30 2020 Return-Path: X-Original-To: tools-development@ietfa.amsl.com Delivered-To: tools-development@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A93A3A0991 for ; Wed, 15 Jul 2020 19:05:29 -0700 (PDT) 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=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 APjVoh4Kr_JI for ; Wed, 15 Jul 2020 19:05:25 -0700 (PDT) Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 674153A0943 for ; Wed, 15 Jul 2020 19:05:25 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 3D6FC203354 for ; Wed, 15 Jul 2020 19:04:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fdznMwL77ruI for ; Wed, 15 Jul 2020 19:04:57 -0700 (PDT) Received: from [192.168.0.3] (unknown [76.103.45.80]) by c8a.amsl.com (Postfix) with ESMTPSA id EEA0B203353 for ; Wed, 15 Jul 2020 19:04:56 -0700 (PDT) From: Liz Flynn Content-Type: multipart/alternative; boundary="Apple-Mail=_49EE431B-EDB1-4B04-B580-3A3A93E623C1" Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Message-Id: <64A04F6C-9B21-4FC0-B980-6A9266669271@amsl.com> Date: Wed, 15 Jul 2020 19:05:24 -0700 To: IETF Tools Development X-Mailer: Apple Mail (2.3273) Archived-At: Subject: [TOOLS-DEVELOPMENT] Notes from tools call 14 July X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Tools Development mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jul 2020 02:05:30 -0000 --Apple-Mail=_49EE431B-EDB1-4B04-B580-3A3A93E623C1 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi everyone, Please see below for notes from yesterday=E2=80=99s tools call. A couple = of reminders:=20 - There is no meeting in August, so our next call will be Tuesday 8 = September.=20 - We will be using a new Webex bridge starting with the September call. = I=E2=80=99ve updated the calendar and either Robert or I will make sure = to send out the new link shortly before the meeting as well.=20 Thanks, Liz Flynn Project Manager / IETF lflynn@amsl.com =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D 1. Hot Topics - RFC Production blocking issues - Alice / Henrik Alice: We are having some ongoing discussions but nothing is blocking. - IETF 108 tooling support - Robert / Alexa / Henrik This has been the primary focus the last several weeks for many of us. Between this and bufixes and contracted projects compeleting, there have been six releases of the datatracker since the last call. We are set up to use codimd instead of etherpad. We changed where codimd was deployed to provide ipv6. We've modified it (and the datatracker) to facilitate embedding codimd in frames in meetecho. Having many activities the week before the meeting "starts" (from the datatracker's perspective) has required manual work and creative = solutions so that things appear on the agenda as we want them to. We have changed the configuration and a little code at the datatracker = so that meeting materials (agenda, slides, minutes, etc) will be served = through cloudflare. - Using the OpenID Connect / OAUTH2 provider - Robert Now that we are running an identity provider, we're starting to get = requests to add clients. So far, the clients we've added have been driven by meeting support. = Meetecho and codimd are set up. The programmers at gather.town are looking to see = if they can integrate. We're getting queries from the community on how to = integrate, including suggestions to use the provider for ietf.slack.com (which = would involve adding a SAML provider). The way we plan to deal with requests to add = clients is to have the tools implementation team vet the request, then make a = recommendation to the IESG for approval or rejection. - Addressing larger infrastructure and architectural issues - Robert There are a set of things long in need of attention that we plan to work = on between IETF 108 and 109. These include: * Measuring and improving performance, particularly of the = datatracker. * Simplifying the filesystem structure that is used across = applications. * Removing the last dependencies on the www6 website pages. * Adjusting the way the www.ietf.org url namespace is used. - Are there any other priority tool changes needed? None mentioned. 2. Development Projects - Reimplementing the IETF website wagtail templates - Robert An RFP is out now. See: = https://www.ietf.org/media/documents/RFP-WagtailDevelopment-20200629.pdf - Meeting Application Improvements (IOLA) - Robert IOLA continues to make steady progress, but still has several = deliverables to complete. - Automated Scheduler Part II (DashCare) - Robert This has been completed and after IETF 108 will do a session with the = Secretariat to show how it can be used. First set of testing we did in = tools implementation group pointed out some improvements.=20 - RPC Security Code Review (ZX Security) - Robert The review is complete, and a (final?) report has been provided. The = report doesn't cover how issues were resolved since the RPC will be doing that = work, and have not yet completed it. Alice estimates two months for their work.=20 - YangCatalog (Pantheon) - =C3=89ric / Robert Yangcatalog is now running as a set of Docker containers. Development of = web frontends for the administration tasks that previously required shell = access is well underway. We expect to see this deployed into amazon's cloud in = the next few weeks. Web interface to administrative part. Things are progressing. Re = containerized version,=20 First estimate to run on AWS is very expensive. - Moving the datatracker to Django 2.2 - Robert This is complete. - DMARC/SPF for aliases - Henrik Meeting work has overtaken this for now. - Capturing external resources in the datatracker - Robert Ready to merge.=20 - Github backups - Robert Martin's CI tool and the extra script to capture metadata from = repositories that are not using Martin's tool continue to improve. We are not yet = making our own backups of repositories, but expect to be doing so within the = next couple of weeks. 3. Operations Projects - Are there any upcoming operations changes that need coordination with this team? None mentioned. 4. Planning for upcoming projects - Improving customization of calendars - Robert We are gathering quotes from several contractors to improve the = customized calendars on the main agenda page and to provide customized calendars = for upcoming meetings.=20 - Exploring fronting web services with nginx - Robert No progress this cycle. - Revising html/css/template structure for the website - Greg - Moving the datatracker to postgresql - Robert This will be included in the optimization work mentioned above. 5. Are there any unmet needs? None mentioned. --Apple-Mail=_49EE431B-EDB1-4B04-B580-3A3A93E623C1 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Hi everyone,

Please see below for notes from yesterday=E2=80=99s tools = call. A couple of reminders: 

- There is no meeting in August, so our = next call will be Tuesday 8 September. 
- We = will be using a new Webex bridge starting with the September call. = I=E2=80=99ve updated the calendar and either Robert or I will make sure = to send out the new link shortly before the meeting as = well. 

Thanks,

Liz Flynn
Project Manager / IETF

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



1. Hot Topics
 =  - RFC Production blocking issues - Alice / Henrik

Alice: We are having = some ongoing discussions but nothing is blocking.
   - IETF 108 tooling = support - Robert / Alexa / Henrik

This has been the = primary focus the last several weeks for many of us.
Between this and bufixes and contracted projects compeleting, = there have
been six releases of the datatracker = since the last call.

We are set up to use codimd instead of etherpad. We changed = where codimd
was deployed to provide ipv6. We've = modified it (and the datatracker) to
facilitate = embedding codimd in frames in meetecho.

Having many activities the week before = the meeting "starts" (from the
datatracker's = perspective) has required manual work and creative solutions
so that things appear on the agenda as we want them = to.

We have = changed the configuration and a little code at the datatracker = so
that meeting materials (agenda, slides, minutes, = etc) will be served through
cloudflare.


   - Using the OpenID Connect / OAUTH2 provider - = Robert

Now = that we are running an identity provider, we're starting to get = requests
to add clients.

So far, the clients we've added have = been driven by meeting support. Meetecho
and codimd = are set up. The programmers at gather.town are looking to see = if
they can integrate. We're getting queries from = the community on how to integrate,
including = suggestions to use the provider for ietf.slack.com (which would involve
adding a SAML provider). The way we plan to deal with = requests to add clients is
to have the tools = implementation team vet the request, then make a = recommendation
to the IESG for approval or = rejection.


   - Addressing larger = infrastructure and architectural issues - Robert

There are a set of things long in need = of attention that we plan to work on
between IETF = 108 and 109. These include:

  * Measuring and improving performance, particularly = of the datatracker.
  * Simplifying the = filesystem structure that is used across applications.
  * Removing the last dependencies on the www6 website = pages.
  * Adjusting the way the www.ietf.org url namespace = is used.


   - Are there any other = priority tool changes needed?
None = mentioned.


2. Development Projects
   - Reimplementing the IETF website wagtail = templates - Robert


   - Meeting Application Improvements (IOLA) - = Robert

IOLA continues to make steady progress, but still has several = deliverables
to complete.

   - Automated = Scheduler Part II (DashCare) - Robert

This has been completed and after IETF = 108 will do a session with the Secretariat to show how it can be used. = First set of testing we did in tools implementation group pointed out = some improvements. 

   - RPC Security Code Review (ZX Security) - = Robert

The = review is complete, and a (final?) report has been provided. The = report
doesn't cover how issues were resolved since = the RPC will be doing that work,
and have not yet = completed it.

Alice estimates two months for their work. 


   - YangCatalog (Pantheon) - =C3=89ric / = Robert

Yangcatalog is now running as a set of Docker containers. = Development of web
frontends for the administration = tasks that previously required shell access
is well = underway. We expect to see this deployed into amazon's cloud in = the
next few weeks.

Web interface to administrative part. = Things are progressing. Re containerized version, 
First estimate to run on AWS is very expensive.


   - Moving the datatracker to Django 2.2 - = Robert

This is = complete.

 =  - DMARC/SPF for aliases - Henrik

Meeting work has overtaken this for = now.

  =  - Capturing external resources in the datatracker - = Robert

Ready = to merge. 

   - Github backups - Robert
Martin's CI tool and the extra script = to capture metadata from repositories
that are not = using Martin's tool continue to improve. We are not yet making
our own backups of repositories, but expect to be doing so = within the next
couple of weeks.


3. Operations Projects
   - = Are there any upcoming operations changes that need
     coordination with this team?

None = mentioned.


4. Planning for upcoming = projects
   - Improving customization of = calendars - Robert

We are gathering quotes from several contractors to improve = the customized
calendars on the main agenda page = and to provide customized calendars for
upcoming = meetings. 

   - Exploring fronting web services with nginx - = Robert

No = progress this cycle.

   - Revising html/css/template structure for the = website - Greg
   - Moving the = datatracker to postgresql - Robert

This will be included in the = optimization work mentioned above.

5. Are there any unmet needs?

None = mentioned.


= --Apple-Mail=_49EE431B-EDB1-4B04-B580-3A3A93E623C1-- From nobody Wed Jul 29 10:42:18 2020 Return-Path: X-Original-To: tools-development@ietfa.amsl.com Delivered-To: tools-development@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B9BB3A0D70; Wed, 29 Jul 2020 10:42:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.12 X-Spam-Level: X-Spam-Status: No, score=-2.12 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, 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 (2048-bit key) header.d=apple.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 JCB9s58CRYk4; Wed, 29 Jul 2020 10:42:11 -0700 (PDT) Received: from ma1-aaemail-dr-lapp03.apple.com (ma1-aaemail-dr-lapp03.apple.com [17.171.2.72]) (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 E14D23A0D69; Wed, 29 Jul 2020 10:42:10 -0700 (PDT) Received: from pps.filterd (ma1-aaemail-dr-lapp03.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp03.apple.com (8.16.0.42/8.16.0.42) with SMTP id 06THXfXl042422; Wed, 29 Jul 2020 10:42:09 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=from : content-type : mime-version : subject : message-id : date : cc : to; s=20180706; bh=SOr6YWBbBZEIr271yUAZ3TgV9tRLar7jjS8ZaXLclnE=; b=vyVTyf5U21vvOhPKr6ggTsmDRWtrw8VME3fxNpdR+TV4vQzICqcARO3qEirPdfCnuPnE 2Sr56z7pdZzAVKNFCEpJhOZhUhW8ptyDEqJsXUGyGmQcANcKy6iUGRAjsQuH8Gbj/pj8 03LQIuSDLbcjSLy+1qKD0SlY7nBzzNjMa7f2x3TI1RfIdEIuGcSPJ9jGr8qGeXSX7FNf 4gIhsjJUCOp1sNuV+AuGeHXnRDmp4kQcVe5710uQor3bA09VrYt1ig/B64q2EenT6WhA gBfPro2daQqunBkn//qOIOu0TlFZgmCkqHw/l5q935geiNjTrgdz50FHYW10nPDX23n3 wg== Received: from rn-mailsvcp-mta-lapp02.rno.apple.com (rn-mailsvcp-mta-lapp02.rno.apple.com [10.225.203.150]) by ma1-aaemail-dr-lapp03.apple.com with ESMTP id 32gkqv1wra-4 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 29 Jul 2020 10:42:08 -0700 Received: from rn-mailsvcp-mmp-lapp04.rno.apple.com (rn-mailsvcp-mmp-lapp04.rno.apple.com [17.179.253.17]) by rn-mailsvcp-mta-lapp02.rno.apple.com (Oracle Communications Messaging Server 8.1.0.5.20200312 64bit (built Mar 12 2020)) with ESMTPS id <0QE800Q39RU6MVW0@rn-mailsvcp-mta-lapp02.rno.apple.com>; Wed, 29 Jul 2020 10:42:07 -0700 (PDT) Received: from process_milters-daemon.rn-mailsvcp-mmp-lapp04.rno.apple.com by rn-mailsvcp-mmp-lapp04.rno.apple.com (Oracle Communications Messaging Server 8.1.0.5.20200312 64bit (built Mar 12 2020)) id <0QE800V00RJI4000@rn-mailsvcp-mmp-lapp04.rno.apple.com>; Wed, 29 Jul 2020 10:42:07 -0700 (PDT) X-Va-A: X-Va-T-CD: 23b105219a9a5f0c83a6b19e6eadd264 X-Va-E-CD: 5c412877990064b83f58221405180151 X-Va-R-CD: e405f866de3fb907a08812c9b471b2be X-Va-CD: 0 X-Va-ID: 27ffcd61-615d-43ca-b419-70a3b78e14e2 X-V-A: X-V-T-CD: 23b105219a9a5f0c83a6b19e6eadd264 X-V-E-CD: 5c412877990064b83f58221405180151 X-V-R-CD: e405f866de3fb907a08812c9b471b2be X-V-CD: 0 X-V-ID: 8222af0d-4aff-4ae9-9d16-818235b06a1a X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.235, 18.0.687 definitions=2020-07-29_13:2020-07-29, 2020-07-29 signatures=0 Received: from [17.234.24.223] (unknown [17.234.24.223]) by rn-mailsvcp-mmp-lapp04.rno.apple.com (Oracle Communications Messaging Server 8.1.0.5.20200312 64bit (built Mar 12 2020)) with ESMTPSA id <0QE800GLWRU1XX00@rn-mailsvcp-mmp-lapp04.rno.apple.com>; Wed, 29 Jul 2020 10:42:03 -0700 (PDT) From: Tommy Pauly Content-type: multipart/alternative; boundary="Apple-Mail=_82727F70-AE33-455C-9364-D7F2A17E3EBC" MIME-version: 1.0 (Mac OS X Mail 13.4 \(3608.80.7.2.3\)) Message-id: <55DB1E91-5A51-4FEB-99E9-252CAFC77176@apple.com> Date: Wed, 29 Jul 2020 10:42:01 -0700 Cc: IAB To: tools-arch@ietf.org, tools-development@ietf.org X-Mailer: Apple Mail (2.3608.80.7.2.3) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.235, 18.0.687 definitions=2020-07-29_13:2020-07-29, 2020-07-29 signatures=0 Archived-At: Subject: [TOOLS-DEVELOPMENT] Tools and Tools-architecture team involvement in EDM IAB program X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Tools Development mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jul 2020 17:42:17 -0000 --Apple-Mail=_82727F70-AE33-455C-9364-D7F2A17E3EBC Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hello Tools Team & TAS Team, During the IAB Open meeting at IETF 108, the IAB shared its proposal for = a program on Evolvability, Deployability, and Maintainability (EDM). = This is a program aimed at looking at how we design, develop, and = maintain IETF protocols, and how these processes impact the flexibility = and evolvability of the protocols. As part of the program, we want to talk about how we can have various = IETF tools provide or hook into resources working groups provide for = tracking implementation status, interoperability testing, and = coordinating experimentation plans. These are items that some groups = provide in their own GitHub pages and Google docs, but we=E2=80=99d like = to discuss a =E2=80=9Cpreferred=E2=80=9D way that has low overhead for = setup. For this, it will be important to have input and thoughts from your = teams. Slides can be found here: = https://github.com/intarchboard/iabopen/blob/master/ietf108/IETF-108-IABOP= EN.pdf = If you=E2=80=99re interested in joining these discussions, please let me = know, and join the mailing list: edm@iab.org https://www.iab.org/mailman/listinfo/edm = Best, Tommy= --Apple-Mail=_82727F70-AE33-455C-9364-D7F2A17E3EBC Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Hello= Tools Team & TAS Team,

During the IAB Open meeting at IETF 108, the IAB shared its = proposal for a program on Evolvability, Deployability, and = Maintainability (EDM). This is a program aimed at looking at how we = design, develop, and maintain IETF protocols, and how these processes = impact the flexibility and evolvability of the protocols.

As part of the program, = we want to talk about how we can have various IETF tools provide or hook = into resources working groups provide for tracking implementation = status, interoperability testing, and coordinating experimentation = plans. These are items that some groups provide in their own GitHub = pages and Google docs, but we=E2=80=99d like to discuss a = =E2=80=9Cpreferred=E2=80=9D way that has low overhead for = setup.

For = this, it will be important to have input and thoughts from your = teams.

Slides = can be found here:

If you=E2=80=99re interested in joining these discussions, = please let me know, and join the mailing list:

Best,
Tommy
= --Apple-Mail=_82727F70-AE33-455C-9364-D7F2A17E3EBC--