From nobody Thu Oct 3 11:09:56 2019 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 CE584120045 for ; Thu, 3 Oct 2019 11:09:54 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=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 Fa6rWiEP7YV7 for ; Thu, 3 Oct 2019 11:09:52 -0700 (PDT) Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 00B4B120025 for ; Thu, 3 Oct 2019 11:09:51 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 78F53300AEF for ; Thu, 3 Oct 2019 14:09:50 -0400 (EDT) X-Virus-Scanned: amavisd-new at mail.smeinc.net Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id Z_WtLuZ3wUvE for ; Thu, 3 Oct 2019 14:09:48 -0400 (EDT) Received: from [5.5.33.172] (unknown [204.194.23.17]) by mail.smeinc.net (Postfix) with ESMTPSA id C70F8300AF7 for ; Thu, 3 Oct 2019 14:09:48 -0400 (EDT) From: Russ Housley Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Message-Id: Date: Thu, 3 Oct 2019 14:09:48 -0400 To: IETF Tools Development X-Mailer: Apple Mail (2.3445.104.11) Archived-At: Subject: [TOOLS-DEVELOPMENT] Tools Call Agenda -- 8 October 2019 at 1:00 Eastern X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Oct 2019 18:09:55 -0000 Tools Call Agenda -- 8 October 2019 at 1:00 Eastern 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. Datatracker Projects - Expected Datatracker Releases -- Robert and Henrik -- https://trac.tools.ietf.org/tools/ietfdb/browser/trunk/PLAN - Implementation of last-call@ietf.org -- Robert - Meeting Application Improvements by IOLA -- Robert - Datatracker maintenance by DashCare -- Robert - IRSG balloting -- Robert - Deployment of Python3 datatracker -- Robert -- Impacts on related applications 2. Community & Other Projects - WWW search to provide additional pointers -- Greg -- Give pointers to datatracker and mailarchive - Host third-party subresources on mailarchive -- Ryan 3. RFC Services Projects - RPC use of new RFC format tools -- Heather and Henrik - Deploying in-line errata on rfc-editor.org? -- Alice - Security Review of RPC Tools -- Robert and Heather 4. Server Infrastructure - Expected Website Releases -- Robert - IESG discussions of DMARC -- Henrik and Alexey -- When do we expect the next release of OpenARC? Ever? 5. YANG Catalog - Putting yangcatalog.org in a Docker container -- Robert 6. Parking Lot - Search over www, datatracker, and mailarchive - Transition Datatracker to Django2 - Transition Website to Django2 7. AOB From nobody Fri Oct 4 08:37:49 2019 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 ED1351208F1 for ; Fri, 4 Oct 2019 08:37:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.98 X-Spam-Level: X-Spam-Status: No, score=-1.98 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] 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 XwVTEzIq4pjI for ; Fri, 4 Oct 2019 08:37:43 -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 665FE1208F0 for ; Fri, 4 Oct 2019 08:37:43 -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 x94Fbf76015242 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Fri, 4 Oct 2019 10:37:42 -0500 (CDT) (envelope-from rjsparks@nostrum.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1570203462; bh=sLV4crFPIDlycQDavY4j5bVlJ1uWyOqipXEWNgCsbng=; h=Subject:To:References:From:Date:In-Reply-To; b=CDu/t1lAcaDatUsH5hf0Ih7vsVJ4PqWv7TXAyrh9duIoVWYUpL7lWAH7CJeGta2EE lrdSCg82hYg7IZ0ZQmyknJjWjNNOzjYfjGgTuG+Bu/LwELY5wzhz3LTRovyovH/Y96 I+C5mtTocXVmQBgO5XRCTR6SP9yhOvS8ZNX809gI= X-Authentication-Warning: raven.nostrum.com: Host [47.186.30.41] claimed to be unescapeable.local To: tools-development@ietf.org References: From: Robert Sparks Message-ID: <74e88b05-9993-c932-47de-928bbafb1951@nostrum.com> Date: Fri, 4 Oct 2019 10:37:40 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Tools Call Agenda -- 8 October 2019 at 1:00 Eastern X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Oct 2019 15:37:46 -0000 Some notes for the call. On 10/3/19 1:09 PM, Russ Housley wrote: > Tools Call Agenda -- 8 October 2019 at 1:00 Eastern > > > 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. Datatracker Projects > - Expected Datatracker Releases -- Robert and Henrik > -- https://trac.tools.ietf.org/tools/ietfdb/browser/trunk/PLAN The priorities in the plan have been tuned. Please look and see that they still meet expectations. > - Implementation of last-call@ietf.org -- Robert Most of the work for this (other than creating the new list) is in the datatracker. We plan to have this as a release ready to deploy on Oct 18. > - Meeting Application Improvements by IOLA -- Robert IOLA began work this week. They are significantly off their originally expected start date. I think it is still reasonable for them to finish this project this year. > - Datatracker maintenance by DashCare -- Robert The improvements to the review tool project continues to go well. The recent 6.104.0 release contained much of this work, and the next several will continue to include improvements. > - IRSG balloting -- Robert On track for completion before IETF106. > - Deployment of Python3 datatracker -- Robert We are going to have to separate and containerize trac, which isn't likely to become python3 enabled until sometime next year. We are currently planning to deploy the conversion to python 3 when the main ietf server is upgraded. > -- Impacts on related applications The mailarchive app will need to deploy on python 3 at the same time as the datatracker. > > 2. Community & Other Projects > - WWW search to provide additional pointers -- Greg > -- Give pointers to datatracker and mailarchive This is on my queue to implement. > - Host third-party subresources on mailarchive -- Ryan > > 3. RFC Services Projects > - RPC use of new RFC format tools -- Heather and Henrik > - Deploying in-line errata on rfc-editor.org? -- Alice > - Security Review of RPC Tools -- Robert and Heather We are in the period where we are gathering proposals. The deadline is 14Oct. We have received a few clarifying questions and have answers ready for the 7Oct question response deadline. > > 4. Server Infrastructure > - Expected Website Releases -- Robert I released a significant to the website behavior today (affecting blog page performance). It should be in production before we get to Tuesday's meeting. See . There will be several releases in the next couple of weeks that change database internals without changing the public's view of the website. The names of fields that editors use will be improved. After that, the major work items are to * Remove the current datatracker integration attempt * Migrate to Django 2 so that we can move to more recent wagtail releases * Investigate reimplementation of the Area and Topic templates We'll be making smaller improvements with regular releases from now on. We're discovering that the CSS framework used by the current system is undocumented, and hard to work with. We are beginning to discuss a project to rebase the site on Bootstrap4 while maintaining the look and feel of the site. > - IESG discussions of DMARC -- Henrik and Alexey > -- When do we expect the next release of OpenARC? Ever? > > 5. YANG Catalog > - Putting yangcatalog.org in a Docker container -- Robert As noted in the last meeting, this is prioritized behind major functionality issues in the yangcatalog project, but it is getting cycles. I am currently to the point where most of the containers come up the way they should in my development environment , but the confd and api_recovery containers are not reaching the expected steady run-state. I am keeping pressure on this, but I don't expect that we'll switch production to the containerized version in the near future. Certainly not before IETF106. > > 6. Parking Lot > - Search over www, datatracker, and mailarchive > - Transition Datatracker to Django2 > - Transition Website to Django2 > > 7. AOB > > _______________________________________________ > TOOLS-DEVELOPMENT mailing list > TOOLS-DEVELOPMENT@ietf.org > https://www.ietf.org/mailman/listinfo/tools-development From nobody Sat Oct 5 03:56:53 2019 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 26E64120124 for ; Sat, 5 Oct 2019 03:56:52 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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=isoc.org 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 qd4Hh3f6eFmh for ; Sat, 5 Oct 2019 03:56:50 -0700 (PDT) Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-eopbgr750044.outbound.protection.outlook.com [40.107.75.44]) (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 C2321120096 for ; Sat, 5 Oct 2019 03:56:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=cGM8CpNbHYMfuBsNBb26w9jSrTG2utBPtIFEjNqYXmu6LXiF8+jyyHSA/PIuyPTgb7sEFHiQDXs56ElF+HLl+Fbjzmmy6Kl1rz20mc1Gn+FKPh3UZg5e05WhvFdXPRJTPzGAcigHhifZZuuyNXc/v8qSwiViwXlO8gRmGQ1bn21d5rVxr4CkPj0BOpEJus1mWz878V3s9TKRufl0lGrjcU1QIkXg4e0kkb1ar7RiGqc9bEncc1mf7w9NWlrD7B/zuXNFc9CUV8TykmdA6vTqNN00mRfwcO3swBidKszOtZZdGqUBL0h1HcBtFxiPtLs3VQkpU0OR4rAy6yX+6iGiuQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=FSpAmofrG8K9Ybyw6AiGeRUsfLjdAqLw6XgAL8ARR6g=; b=ekcTYpDLqhPYKOBKVcJjt0iwx3lRuw4j0vMOhdAkrmfJKWK50HO2X13UPhWlv+cciwJ5seCvLutI297NLdANl6h4PC/YVECHJxZDVSDMOzTNrK35sH5XQh93ptspQ88wjeGlLz8NqJgiPQCh8yp5z+KWP8AmcA7TA3fp7HYdwkZLuwVna1Y74HL/RCHjI1G4AxcGk/HJBm4m8dgjwqbW9Gyi7XqnqyfWOawyXNGi92w/1ftEFYlghYSZRGQ8w6mC/VT05Ixykf1/MA7uYPnNn9ga0GiK1P+xBQ6G/jgZ5NmdRijUgG2UWqr7ZGiXDKHfnhHWxYZjBOMcyNaQkr1X/A== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=isoc.org; dmarc=pass action=none header.from=isoc.org; dkim=pass header.d=isoc.org; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isoc.org; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=FSpAmofrG8K9Ybyw6AiGeRUsfLjdAqLw6XgAL8ARR6g=; b=jIPkNMxVVVkXlLRxZTu4x3saGqCzuj6Msx5JmgpnBFk2aahu4x/RBxnWJFzxMJqTp5mD7UKydBjr7Ci3WxuOhMiNHkFCcfAaq6PjoSpLjZvcV6YZTQUF3vP1ANWZRYKZtPV2bz72Z3VQac9ZevJpSpntDS1d/+P+JldGd0fpnyo= Received: from DM6PR06MB4635.namprd06.prod.outlook.com (20.176.112.80) by DM6PR06MB4873.namprd06.prod.outlook.com (20.176.120.81) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2305.20; Sat, 5 Oct 2019 10:56:46 +0000 Received: from DM6PR06MB4635.namprd06.prod.outlook.com ([fe80::f8b0:2e7:3a0a:3491]) by DM6PR06MB4635.namprd06.prod.outlook.com ([fe80::f8b0:2e7:3a0a:3491%7]) with mapi id 15.20.2305.023; Sat, 5 Oct 2019 10:56:45 +0000 From: Greg Wood To: Russ Housley CC: IETF Tools Development Thread-Topic: [TOOLS-DEVELOPMENT] Tools Call Agenda -- 8 October 2019 at 1:00 Eastern Thread-Index: AQHVehXG/zSAok6k20yXFW/bWQfBKadL4veA Date: Sat, 5 Oct 2019 10:56:45 +0000 Message-ID: <36DF6903-A830-45A1-8C64-44FBC598745F@isoc.org> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-clientproxiedby: MN2PR13CA0013.namprd13.prod.outlook.com (2603:10b6:208:160::26) To DM6PR06MB4635.namprd06.prod.outlook.com (2603:10b6:5:fd::16) authentication-results: spf=none (sender IP is ) smtp.mailfrom=wood@isoc.org; x-ms-exchange-messagesentrepresentingtype: 1 x-mailer: Apple Mail (2.3445.104.11) x-originating-ip: [72.66.99.52] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: b0f1ff08-fd45-42bd-9c54-08d74982b536 x-ms-traffictypediagnostic: DM6PR06MB4873: x-ms-exchange-purlcount: 3 x-ld-processed: 89f84dfb-7285-4810-bc4d-8b9b5794554f,ExtAddr x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:8882; x-forefront-prvs: 0181F4652A x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(346002)(39840400004)(396003)(136003)(376002)(199004)(189003)(6436002)(6306002)(26005)(66066001)(229853002)(6486002)(36756003)(6246003)(11346002)(33656002)(4326008)(2616005)(486006)(476003)(66946007)(446003)(6512007)(66574012)(186003)(52116002)(86362001)(99286004)(305945005)(76176011)(16799955002)(71200400001)(966005)(5660300002)(102836004)(7736002)(71190400001)(478600001)(53546011)(6506007)(3846002)(6116002)(14454004)(386003)(2906002)(25786009)(66446008)(8676002)(256004)(64756008)(66556008)(81156014)(81166006)(66476007)(50226002)(6916009)(316002)(8936002)(14444005); DIR:OUT; SFP:1101; SCL:1; SRVR:DM6PR06MB4873; H:DM6PR06MB4635.namprd06.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: isoc.org does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: lkPdQuxK7qTnEOwWL+T+H7aCRnxVCVnYHEmTEyeHhYsrqn1r/CaBAk5qmEFGd9sfVB4czR3MxApx3MsSgBkbj6iNf9ljeRvJRhdj5xfjT+F8Cza6XVvZXxO8UmxWtbTuaVs5UL00RuJ8ogc3EUfxmFG8Eugwr8FjtLZ/JvipriBFgdLJtolWHjse/ou+QJSPkOPD8Bz7Qpk3NhiGgGEdqLa3L4H3oHCh1fgkV8Nfz0bvfnnnDxZlJ7cvWKLPnh8nQKHfWYydd+6rsQ4awI5XgLk0+kJYLaiuYIPlpw6uqLBNnbpPpAP5j0GzZxLPIrr+vOfx/JNNOu1XJ15j0uhAJAu3rDlHbyXICuB+ip47uUV1DzGVB1LhcfVG4NgxjP9buPRUlufKc23VmFKTQeEssHlGGcUwOJY2U7wqM5xGcsk3BUVU8W2Y/YntfMCfoEQH0T1fU11ZJlKKJtvv+7PAWg== x-ms-exchange-transport-forked: True Content-Type: text/plain; charset="us-ascii" Content-ID: <821CC587B1BAAA4F8E8DD658B1B62FF9@namprd06.prod.outlook.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: isoc.org X-MS-Exchange-CrossTenant-Network-Message-Id: b0f1ff08-fd45-42bd-9c54-08d74982b536 X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Oct 2019 10:56:45.7470 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 89f84dfb-7285-4810-bc4d-8b9b5794554f X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: NvX5b7oXeaqAnS7tQwopasWwnOlKbizNw8OsiAddUsfmKuiN/vjrQElZEz8uJ6vt X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR06MB4873 Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Tools Call Agenda -- 8 October 2019 at 1:00 Eastern X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Oct 2019 10:56:52 -0000 Hi Russ, Could analytics implementation be added under item 2? Thanks, -Greg > On Oct 3, 2019, at 2:09 PM, Russ Housley wrote: >=20 > Tools Call Agenda -- 8 October 2019 at 1:00 Eastern >=20 >=20 > JOIN WEBEX MEETING > https://ietf.webex.com/ietf/j.php?MTID=3Dm440dd848726339c03e605b9956e38ba= c > Meeting number (access code): 640 103 570 > Meeting password: tools >=20 > JOIN BY PHONE > 1-877-668-4493 Call-in toll free number (US/Canada)=20 > 1-650-479-3208 Call-in toll number (US/Canada) > Meeting number (access code): 640 103 570 > Meeting password: tools >=20 >=20 > 1. Datatracker Projects > - Expected Datatracker Releases -- Robert and Henrik > -- https://trac.tools.ietf.org/tools/ietfdb/browser/trunk/PLAN > - Implementation of last-call@ietf.org -- Robert > - Meeting Application Improvements by IOLA -- Robert > - Datatracker maintenance by DashCare -- Robert > - IRSG balloting -- Robert > - Deployment of Python3 datatracker -- Robert > -- Impacts on related applications >=20 > 2. Community & Other Projects > - WWW search to provide additional pointers -- Greg > -- Give pointers to datatracker and mailarchive > - Host third-party subresources on mailarchive -- Ryan >=20 > 3. RFC Services Projects > - RPC use of new RFC format tools -- Heather and Henrik > - Deploying in-line errata on rfc-editor.org? -- Alice > - Security Review of RPC Tools -- Robert and Heather >=20 > 4. Server Infrastructure > - Expected Website Releases -- Robert > - IESG discussions of DMARC -- Henrik and Alexey > -- When do we expect the next release of OpenARC? Ever? >=20 > 5. YANG Catalog > - Putting yangcatalog.org in a Docker container -- Robert >=20 > 6. Parking Lot > - Search over www, datatracker, and mailarchive > - Transition Datatracker to Django2 > - Transition Website to Django2 >=20 > 7. AOB >=20 > _______________________________________________ > TOOLS-DEVELOPMENT mailing list > TOOLS-DEVELOPMENT@ietf.org > https://www.ietf.org/mailman/listinfo/tools-development From nobody Mon Oct 7 08:50:04 2019 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 4FF6A120110 for ; Mon, 7 Oct 2019 08:50:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.98 X-Spam-Level: X-Spam-Status: No, score=-1.98 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] 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 e2fXliU1Etcb for ; Mon, 7 Oct 2019 08:50:00 -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 F137B120041 for ; Mon, 7 Oct 2019 08:49:59 -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 x97FnvIS055736 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Mon, 7 Oct 2019 10:49:59 -0500 (CDT) (envelope-from rjsparks@nostrum.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1570463399; bh=cued+qW+ZSzZJ5S6mfUVH5OVVpJn7DQ62HsSyh2c6i0=; h=Subject:From:To:References:Date:In-Reply-To; b=IdaPJwCCKphbrffopT0Co3GV3B03IrNyOkxJQSEtR3YmIR8MPgNI9gZCRm+FjjrHe IH9Mcj0iLL5I3L5rU3bAr1xwdK0Fq9EoEkC22xylG1PUj8lD7UQunbzWCSEHrrWPy/ FRw+dDi+GpOTkFDm+KX6xjTmNW4nQMaZfJ6lDY9I= X-Authentication-Warning: raven.nostrum.com: Host [47.186.30.41] claimed to be unescapeable.local From: Robert Sparks To: tools-development@ietf.org References: <74e88b05-9993-c932-47de-928bbafb1951@nostrum.com> Message-ID: <020c56b3-8d6d-6e37-1edd-c315a5c40d73@nostrum.com> Date: Mon, 7 Oct 2019 10:49:57 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: <74e88b05-9993-c932-47de-928bbafb1951@nostrum.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Tools Call Agenda -- 8 October 2019 at 1:00 Eastern X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2019 15:50:03 -0000 On 10/4/19 10:37 AM, Robert Sparks wrote: > Some notes for the call. > > On 10/3/19 1:09 PM, Russ Housley wrote: >> Tools Call Agenda -- 8 October 2019 at 1:00 Eastern >> >> >> 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. Datatracker Projects >>     - Expected Datatracker Releases -- Robert and Henrik >>       -- https://trac.tools.ietf.org/tools/ietfdb/browser/trunk/PLAN > > The priorities in the plan have been tuned. Please look and see that > they still meet expectations. > > >>     - Implementation of last-call@ietf.org -- Robert > > Most of the work for this (other than creating the new list) is in the > datatracker. > > We plan to have this as a release ready to deploy on Oct 18. > >>     - Meeting Application Improvements by IOLA -- Robert > IOLA began work this week. They are significantly off their originally > expected start date. I think it is still reasonable for them to finish > this project this year. >>     - Datatracker maintenance by DashCare -- Robert > The improvements to the review tool project continues to go well. The > recent 6.104.0 release contained much of this work, and the next > several will continue to include improvements. >>     - IRSG balloting -- Robert > On track for completion before IETF106. >>     - Deployment of Python3 datatracker -- Robert > > We are going to have to separate and containerize trac, which isn't > likely to become python3 enabled until sometime next year. > > We are currently planning to deploy the conversion to python 3 when > the main ietf server is upgraded. > >>       -- Impacts on related applications > The mailarchive app will need to deploy on python 3 at the same time > as the datatracker. >> >> 2. Community & Other Projects >>     - WWW search to provide additional pointers -- Greg >>       -- Give pointers to datatracker and mailarchive > This is on my queue to implement. >>     - Host third-party subresources on mailarchive -- Ryan >> >> 3. RFC Services Projects >>     - RPC use of new RFC format tools -- Heather and Henrik >>     - Deploying in-line errata on rfc-editor.org? -- Alice >>     - Security Review of RPC Tools -- Robert and Heather > We are in the period where we are gathering proposals. The deadline is > 14Oct. We have received a few clarifying questions and have answers > ready for the 7Oct question response deadline. >> >> 4. Server Infrastructure >>     - Expected Website Releases -- Robert > > I released a significant to the website behavior today (affecting blog > page performance). It should be in production before we get to > Tuesday's meeting. > > See . > > There will be several releases in the next couple of weeks that change > database internals without changing the public's view of the website. > The names of fields that editors use will be improved. > > After that, the major work items are to > > * Remove the current datatracker integration attempt > > * Migrate to Django 2 so that we can move to more recent wagtail releases > > * Investigate reimplementation of the Area and Topic templates > > We'll be making smaller improvements with regular releases from now on. > > We're discovering that the CSS framework used by the current system is > undocumented, and hard to work with. We are beginning to discuss a > project to rebase the site on Bootstrap4 while maintaining the look > and feel of the site. > >>     - IESG discussions of DMARC -- Henrik and Alexey >>       -- When do we expect the next release of OpenARC? Ever? >> >> 5. YANG Catalog >>     - Putting yangcatalog.org in a Docker container -- Robert > As noted in the last meeting, this is prioritized behind major > functionality issues in the yangcatalog project, but it is getting > cycles. I am currently to the point where most of the containers come > up the way they should in my development environment , but the confd > and api_recovery containers are not reaching the expected steady > run-state. I am keeping pressure on this, but I don't expect that > we'll switch production to the containerized version in the near > future. Certainly not before IETF106. >> >> 6. Parking Lot >>     - Search over www, datatracker, and mailarchive >>     - Transition Datatracker to Django2 >>     - Transition Website to Django2 >> >> 7. AOB I think we should talk briefly about the state of supporting markdown for minutes/agendas (and eventually other documents), and how we should prioritize improving it. >> >> _______________________________________________ >> TOOLS-DEVELOPMENT mailing list >> TOOLS-DEVELOPMENT@ietf.org >> https://www.ietf.org/mailman/listinfo/tools-development From nobody Tue Oct 8 07:12:01 2019 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 7105C12007C for ; Tue, 8 Oct 2019 07:11:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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=cooperw.in header.b=EABa7ByW; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Muto4ob1 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 JC7MF6EJXZFr for ; Tue, 8 Oct 2019 07:11:57 -0700 (PDT) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 32F11120052 for ; Tue, 8 Oct 2019 07:11:57 -0700 (PDT) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 6450A21910; Tue, 8 Oct 2019 10:11:56 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Tue, 08 Oct 2019 10:11:56 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=U VKQh8H9Xyv1Yea+C3VG+b1ml6wqVTM7MsPDr7gL0tc=; b=EABa7ByWtm/tl6IT/ zH13RNcPhNvQd/kn7L5LwbBmy3P5E9tP86eHLKw5CijYpeJsn8ndN7cNFWRkZhC3 yMLBdKQ1wA6cLjkyq9qA1nHpaJ5CMvLXBJ/DRFpjrqDn8/kN3PALtKzTliObbtAN 4MPDr6KeWJ2AMDnOJvpPFwm8Q67/uMGSigBiRRCAjMtH3MGWaPm2bqQ2vOjZMKYm k+KnEy53MqcVy+uI7zhJ43sPuIyaKYWX+eOd32ER+c7DjLpXle4z7z/7fS5BqQ6t UCQZGk6KJN59n5MBibuXGVEKmNywv2G/mX7cfr2nt7jjGlZPXzmqq757kFFHYaiX 7HegA== DKIM-Signature: v=1; a=rsa-sha256; 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-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=UVKQh8H9Xyv1Yea+C3VG+b1ml6wqVTM7MsPDr7gL0 tc=; b=Muto4ob1Dlv+CCMviP2F+CxQO7pvSsj0/ltYajbRiLmmuUp6wuL8wEj/K Ee8P6qsTUY4OekNmnRRbA8myHqInBAIWVwFBzK0o/SOqdn/hrPWv/5lDWNDzCq2C I0asCn+e2p41vENYYJiJzmQko7zbearcScCkZk0s3vvl5QatVsbo3l2iTEV1g5+8 +na5YLPMsBxCLhjBDX42MzWqj0dgakasJ1IckLKtZFjSixc84lRQjrg5xWt1PqJm lNj5dWkK6PRnFeEQgdAYl+v6OQGkK3k3MdrHylT4mPDgjXCK34xV7hEo917OU+qS QAKU8Ze58vQrFVEIbXfAQqffJy/fQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrheelgdejhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtdejnecuhfhrohhmpeetlhhishhs rgcuvehoohhpvghruceorghlihhsshgrsegtohhophgvrhifrdhinheqnecuffhomhgrih hnpeifvggsvgigrdgtohhmpdhivghtfhdrohhrghenucfkphepudejfedrfeekrdduudej rdekgeenucfrrghrrghmpehmrghilhhfrhhomheprghlihhsshgrsegtohhophgvrhifrd hinhenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from rtp-alcoop-nitro3.cisco.com (unknown [173.38.117.84]) by mail.messagingengine.com (Postfix) with ESMTPA id B45A3D60069; Tue, 8 Oct 2019 10:11:55 -0400 (EDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) From: Alissa Cooper In-Reply-To: <74e88b05-9993-c932-47de-928bbafb1951@nostrum.com> Date: Tue, 8 Oct 2019 10:11:54 -0400 Cc: tools-development@ietf.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <74e88b05-9993-c932-47de-928bbafb1951@nostrum.com> To: Robert Sparks X-Mailer: Apple Mail (2.3445.9.1) Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Tools Call Agenda -- 8 October 2019 at 1:00 Eastern X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2019 14:11:59 -0000 Hi Robert, > On Oct 4, 2019, at 11:37 AM, Robert Sparks = wrote: >=20 > Some notes for the call. >=20 > On 10/3/19 1:09 PM, Russ Housley wrote: >> Tools Call Agenda -- 8 October 2019 at 1:00 Eastern >>=20 >>=20 >> JOIN WEBEX MEETING >> = https://ietf.webex.com/ietf/j.php?MTID=3Dm440dd848726339c03e605b9956e38bac= >> Meeting number (access code): 640 103 570 >> Meeting password: tools >>=20 >> 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 >>=20 >>=20 >> 1. Datatracker Projects >> - Expected Datatracker Releases -- Robert and Henrik >> -- https://trac.tools.ietf.org/tools/ietfdb/browser/trunk/PLAN >=20 > The priorities in the plan have been tuned. Please look and see that = they still meet expectations. The 5th item down says: "Review and change the draft submission and handling code to deal with = UTF-8 instead of ascii before upload of utf-8 drafts should be = permitted.=E2=80=9D How is this working now given that we started allowing utf-8 drafts = months ago? Thanks, Alissa From nobody Tue Oct 8 07:40:17 2019 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 903F8120099 for ; Tue, 8 Oct 2019 07:40:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.095 X-Spam-Level: X-Spam-Status: No, score=-1.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no 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 A_nP2Cdt20F2 for ; Tue, 8 Oct 2019 07:40:14 -0700 (PDT) Received: from zinfandel.tools.ietf.org (unknown [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 59A6A120026 for ; Tue, 8 Oct 2019 07:40:11 -0700 (PDT) Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:65376 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1iHqeo-0006SA-Fg; Tue, 08 Oct 2019 07:40:11 -0700 To: Alissa Cooper , Robert Sparks References: <74e88b05-9993-c932-47de-928bbafb1951@nostrum.com> Cc: tools-development@ietf.org From: Henrik Levkowetz Message-ID: <7c3fa2e2-feff-b5a9-32f7-3b1796f5cda1@levkowetz.com> Date: Tue, 8 Oct 2019 16:40:02 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="QHseIRx6H0nl0ewjfF45aRrdaFp15Wncu" X-SA-Exim-Connect-IP: 158.174.202.242 X-SA-Exim-Rcpt-To: tools-development@ietf.org, rjsparks@nostrum.com, alissa@cooperw.in X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org) X-Clacks-Overhead: GNU Terry Pratchett Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Tools Call Agenda -- 8 October 2019 at 1:00 Eastern X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2019 14:40:16 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --QHseIRx6H0nl0ewjfF45aRrdaFp15Wncu Content-Type: multipart/mixed; boundary="0RxF0Gn8hT45Ki2LQdKoJBngV5j1XwOLl"; protected-headers="v1" From: Henrik Levkowetz To: Alissa Cooper , Robert Sparks Cc: tools-development@ietf.org Message-ID: <7c3fa2e2-feff-b5a9-32f7-3b1796f5cda1@levkowetz.com> Subject: Re: [TOOLS-DEVELOPMENT] Tools Call Agenda -- 8 October 2019 at 1:00 Eastern References: <74e88b05-9993-c932-47de-928bbafb1951@nostrum.com> In-Reply-To: --0RxF0Gn8hT45Ki2LQdKoJBngV5j1XwOLl Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Alissa, On 2019-10-08 16:11, Alissa Cooper wrote: > Hi Robert, >=20 >> On Oct 4, 2019, at 11:37 AM, Robert Sparks wrot= e: >>=20 >> Some notes for the call. >>=20 >> On 10/3/19 1:09 PM, Russ Housley wrote: >>> Tools Call Agenda -- 8 October 2019 at 1:00 Eastern >>>=20 >>>=20 >>> JOIN WEBEX MEETING >>> https://ietf.webex.com/ietf/j.php?MTID=3Dm440dd848726339c03e605b9956e= 38bac >>> Meeting number (access code): 640 103 570 >>> Meeting password: tools >>>=20 >>> 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 >>>=20 >>>=20 >>> 1. Datatracker Projects >>> - Expected Datatracker Releases -- Robert and Henrik >>> -- https://trac.tools.ietf.org/tools/ietfdb/browser/trunk/PLAN >>=20 >> The priorities in the plan have been tuned. Please look and see that t= hey still meet expectations. >=20 > The 5th item down says: >=20 > "Review and change the draft submission and handling code to deal > with UTF-8 instead of ascii before upload of utf-8 drafts should be > permitted.=E2=80=9D >=20 > How is this working now given that we started allowing utf-8 drafts > months ago? The status has been changing gradually over the last few months. The first step was to change idnits to not issue errors for non-ASCII content= s, only warnings. The next step was when we started accepting and convertin= g V3 XML uploads, which provides an improved ability to use non-ASCII. However, all parts of the code is still not fully able to deal with non-A= SCII: If V3 XML is not used for upload, but just a text-format draft is submitt= ed, the code that extracts author data from text has problems if it's given non-ASCII author names. This will not change with the transition to Pyth= on 3; we will either have to go back and refine the complex code that tries to figure out author names and addresses from text-only uploads, or (less wo= rk and better results) change the approach to requiring XML in order to supp= ort non-ASCII author names. The parts of the item you point at which refers to open() in general has been accomplished with the rewrite that gave Python3 compatibility. Regards, Henrik --0RxF0Gn8hT45Ki2LQdKoJBngV5j1XwOLl-- --QHseIRx6H0nl0ewjfF45aRrdaFp15Wncu Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEifjc5+rnL1MJBcZSTptXS4+7FxoFAl2cn8IACgkQTptXS4+7 FxrGig//Rr5u74SXm7DLQFplPn1zB5kc2ri2fLhu60hBhUwc/vRYEdbH0BAlnfyf SCl+FCMm3cnLkqn4/nZTbH7WPo/Y4uNmrOX5/T4jVcGJEOKbkFmX1weFHmA6kjF8 24uM4D4Sh88azL7j1LeIllHPkAhMmTB6bWyU8K3lYIbsXy21tWUAXJwfMrEoch9e BSvGACMVABckor37eJ3qCthEbpFxxCNuFEd18kSgSp0mWTwNsojJ+uCcAkUuGrC2 cawgenxTt/9eHlKH55Xo+RWxHWSvVVsghZ42288ZqdvnNB8bEVYRBcrg/w4bW++T cRWHIQANt2EnKzLgSzxWXzY+j7g7KBSx3HHoWtfCTV3lHp5IQdgG2SyYZNRKckNi PZFV2QpxMZpWbl5XDj+2cNPKD29VCWoVTIHt24WdhSv3gTIpEPloMOYARQ0N3H+e t41W//wNylV/juMoy6diXYaQASE7TsPI4U9iA1zOBA5J02powdOEOiKqwQOC3Hkd vZdnhLBKR5CZmQ6idYRAxR+HLs2EqfL2jk0QddnX42pzXBVbq14RkcPh3+8CcPtx hZVvHOslmaStsaytd0wqqrFwE/F3tSmuxthYlYMENBNZS2tGia/8z2TPpiK8fpdQ 8kOBpsJ2nzhwrs+b6z9iB1KJ3KKYvdFlI3yovE7U3lJUun4a8zw= =jQTR -----END PGP SIGNATURE----- --QHseIRx6H0nl0ewjfF45aRrdaFp15Wncu-- From nobody Tue Oct 8 13:23:34 2019 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 D323F120033 for ; Tue, 8 Oct 2019 13:23:32 -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, 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 tKqgGQ3p9Nv3 for ; Tue, 8 Oct 2019 13:23:29 -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 B342B120013 for ; Tue, 8 Oct 2019 13:23:29 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id C1AF8203AF7 for ; Tue, 8 Oct 2019 13:22:10 -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 LTy1ExUaNwxq for ; Tue, 8 Oct 2019 13:22:10 -0700 (PDT) Received: from [64.170.98.136] (unknown [64.170.98.136]) by c8a.amsl.com (Postfix) with ESMTPSA id 8781A203AF4 for ; Tue, 8 Oct 2019 13:22:10 -0700 (PDT) From: Cindy Morgan Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <15D21262-0C95-4F7D-AC3D-20D07E5E8F50@amsl.com> Date: Tue, 8 Oct 2019 13:23:21 -0700 To: tools-development@ietf.org Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) X-Mailer: Apple Mail (2.2104) Archived-At: Subject: [TOOLS-DEVELOPMENT] Tools Call Notes -- 8 October 2019 X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2019 20:23:33 -0000 Hi everyone, Below please find notes from today's Tools call. Best regards, Cindy -- Tools Call Notes -- 8 October 2019 at 1:00 Eastern 0. Attendance Glen Barney Alissa Cooper Ryan Cross Roman Danyliw Heather Flanagan Russ Housley Henrik Levkowetz Karen Moreland Cindy Morgan Alexa Morris Alice Russo Robert Sparks Portia Wenze-Danley Greg Wood 1. Datatracker Projects - Expected Datatracker Releases -- Robert and Henrik -- https://trac.tools.ietf.org/tools/ietfdb/browser/trunk/PLAN Robert: Nothing to highlight in the merge plan. Hopefully Henrik's email = answered Alissa's question about non-ASCII in UTF-8. Alissa: Does the item in place represent the work left to do, or not? Henrik: There are decisions to make and work left to do in order to = complete that item. If we decide that we will only permit non-ASCII = author names in XML upon upload, then we're done. Or we decide = otherwise, and then there is more work needed, on doing on parsing text = format in order to support new features. That decision needs to be made = before we take out that item. Robert; We still have the ability when someone is uploading text for = people to correct their name. Typically people just click through that = page, but that is a way we could present that with the full Unicode = character set; they'd just have to provide it to the Datatracker at = upload time. But it wouldn't show up in the text version that gets = displayed. I don't know what priority we need to put on making that = decision. Is it reasonable to say, if you want to have the non-ASCII = characters in your submission that you need to submit in the XML format? Alissa: I think so, but then again I kind of wish we only had one = submission format so I am maybe not the person to ask. Robert: I think we'll work forward with that as a tentative plan and if = it creates any tension in the community, we can work it out if anyone = pushes back. Russ: And if the IESG is not happy with that plan, they need to tell us. Alissa: Roman, can you put this on our action item list so that we talk = about it the next time we talk about action items? Roman: Will so. - Implementation of last-call@ietf.org -- Robert Robert via email: Most of the work for this (other than creating the new=20= list) is in the datatracker. We plan to have this as a release ready=20= to deploy on Oct 18. Robert: This is ready to add to a release that will happen right before = the deadline for the cutover. Not foreseeing any problems here. - Meeting Application Improvements by IOLA -- Robert Robert via email: IOLA began work this week. They are significantly off=20= their originally expected start date. I think it is still reasonable=20= for them to finish this project this year. Robert: IOLA is late getting started, but they still think they'll be = able to finish by the end of the year. Need to keep in mind any impact = this will have on things like the automated agenda scheduler. Some of = that work may depend on this work, and we shouldn't expect it until the = end of the year.=20 - Datatracker maintenance by DashCare -- Robert Robert via email: The improvements to the review tool project continues=20= to go well. The recent 6.104.0 release contained much of this work,=20 and the next several will continue to include improvements. Russ: We're seeing notes from them in release notes, how is this going? Robert: Exceeding well. Sasha is working through the things we've asked = to be corrected at a great rate, so I'm feeling good about where this = is. - IRSG balloting -- Robert Robert via email: On track for completion before IETF106. Robert: Been working with Peter on this. It is still planned to be = complete before 106. We spent some time last week working through some = of the harder design decisions about how to display ballots on search = result rows. Now down to finishing things up and taking care of corner = cases. Russ: My understanding is we started that work based on the IESG = balloting, and morphed it to fit the policies for the IRSG, but they've = made improvements? Robert: It's more generalizing what was there for the IESG, not making = improvements. Russ: Making sure it's on a common base, got it. - Deployment of Python3 datatracker -- Robert Robert via email: We are going to have to separate and containerize=20 trac, which isn't likely to become python3 enabled until sometime next=20= year. We are currently planning to deploy the conversion to python 3=20= when the main ietf server is upgraded. Robert: We are planning to deploy Python3 when Glen upgrades the main = IETF servers. Maybe we can talk about that when we get to the server = part of the agenda. We know we'll need to separate Trac into its own = container because they won't finish their Python migration until = sometime next year. -- Impacts on related applications 2. Community & Other Projects - WWW search to provide additional pointers -- Greg -- Give pointers to datatracker and mailarchive Robert via email: This is on my queue to implement. Russ: Greg, I understand we'll take links that say where else to look. = Has that been done? Robert: It's still in my queue to do. Russ: I thought it was done on www but not the other sides? Robert: No. Russ: When do we plan to do that? Robert: It might have been done with content inside the website, but if = there is code that needs to be touched, it will be in the next couple of = weeks. Greg: On www there are indeed search boxes for datatracker and = mailarchive, but I think there needs to be some text added to provide = context. And the other step on www is creating stub pages to match up = with the 10 most commonly searched terms. Those two parts of the search = improvement plan are still in the works. I think Robert mentioned that = doing the similar pointing for mailarchive and Datattracker are still in = the queue.=20 - Host third-party subresources on mailarchive -- Ryan Russ: This is so, right now when you go to a page it goes to another = site to get the fonts; the idea is you store them locally so we don't = get any cross-site leakage. Robert: Currently prioritizing when we would do this. My read is this = isn't as high priority as the registration system for the current = meeting, so I think we will address this just after IETF 106. Russ: I agree with that prioritization and think we should let the = community know when this is sorted out because I know some of them care = a lot about this. - Analytics implementation -- Greg Roman: We launched a week ago the final approach to do analytics, but in = that there is Javascript-only, and the original plan was to do something = that was pixel-based, so we were going to talk about how to proceed = forward. Some people liked the pixel-based way better because you can't = opt-out, and you can do reduced collection. Robert: Yes, you got the essence of it. Getting any information on the = robots accessing the website on the other side of the CDN, they will = definitely be in the opt-out camp. It comes down to what we are trying = to accomplish with the analytics. If we have opt-in by turning = Javascript on, we'll get different data than we're currently collecting, = but I'm not sure it will be better data. Is it okay if we get a large = section of the community that does opt out on JS, and we don't get the = data on robots? Greg: This is a bit beyond my technical depth. I am not sure I = understand entirely. I do understand that people who don't have JS on = will not get recorded in this system, which I think is fine. But I don't = understand the complication the CDN creates, because I thought = Cloudflare supports the JS approach? Robert: Anything accessing the site through Cloudflare with JS on will = get that information, which is a bit more invasive than we'd get with = the pixel-based approach. But robots won't do the JS things so we won't = get counters on that at all. Alissa: I don't think counting robots was the goal of this; it was human = visits. I also want to question the premise that people will turn JS off = to opt out of this. Henrik: The problem is that some people may turn JS off, but we won't = know whether it's 50% or 0.5%. We will collect data and we won't know if = it is representative or not. That is the issue here. If we knew how much = it was, that would be different, but we have no way of knowing. I would = be against having people collect JS-based data on me rather than just = registering which pages I visit based on the pixel-based approach. I = think the more invasive approach is not what I expected us to do. Alissa: Part of this is not about our personal preferences, since we = vetted this with the community. I think gross statistics about who = browses with JS off is something we should be able to find. I think most = people using the Web have JS turned on. Maybe we can do a data = collection exercise to figure that out. And we can address the concerns = about the representativeness of the data. Question about the pixel-based = approach where we can't opt out, what data would we be able to collect? = Is there a cookie attached? Is it IP data? Henrik: It would be the data we would get today if we didn't have the = CDN.=20 Alissa: So the JS is more robust. Henrik: Broader, but less robust and more invasive. Roman: If we did a pixel-based approach, which set of that data would we = get? Part of what I am reacting to is, we weren't exceedingly specific = on what fields we were going to be collecting. I think we need to be = clear on that, and what is the manifestation of that to whoever will be = the end users of that.=20 Henrik: I am not certain what you're asking for? What data fields we = would get for each approach? Roman: Yes, because I'm trying to figure out if this is robustness or = data collection. Henrik: One approach will collect a limited amount of data on all = visitors. The other will collect much more data on a percentage of the = visitors, and we won't know what that percentage actually is. Roman: I've never deployed this and don't know how configureable it is, = so it's about the specifics, would we collect less data than is in Table = 1 = (https://www.ietf.org/media/documents/www.ietf.org-AnalyticsProposal-Revis= ed-2019-09-24.pdf) Robert: Can it be tuned down so that it is not much more, and I think = the answer is yes. Surely the JS can collect vastly more data, but I = think we can tune it down to what we have in the table. Roman: Right, this is where we got burned initially on the hypothetical. = This is why we were very specific in the final proposal about what we're = collecting and why. Robert: I think the discussion quieted down when people saw they could = opt out based on IP. What we would get from the pixel-based approach = would be even smaller but there wouldn't be an opt-out, and I think that = is the key distinction. Roman: So I am back to what the use cases driving this are. Can we use = general Internet-based sampling of who opts out of JS to scale the data = that we have? Robert: For me, reinforcing what it is we are going to do with this data = once we have it is what tips this the furthest. One of these gives a = limited view into the community, but is it enough to give us enough to = do something different. Alissa: The use cases are laid out in the proposal, and what we vetted = with the community was the JS option where people can opt out by turning = of JS. That's what we told people we would do, so we should do it. Roman: That's where I'm at. Greg: Looking at the general stats on JS use, I don't see that as = preventing us from getting done what we need to get done. Henrik: I don't know that I have more to say. It's a tradeoff and it's = very much a matter of what we need the data for and what we plan to do = with it.=20 Robert: I think what I'm hearing is we move forward with the JS-only = based approach and we make sure it only collects the minimal data = described in the plan, deploy, and decide whether the information we get = is useful to us.=20 Roman: Yes, and we'll reassess whether this was valuable a year from. Russ: Did we tell the community when we would deploy this? Roman: We made no commitment on the timeline. We'll figure out the = implementation details and then move forward. And we promised to revisit = whether it was valuable a year after deployment. Russ: Greg and Robert, do you need anything else? Robert: I think we need to confirm that we can limit the data collection = to what has been discussed. Russ: But that's an experiment that you need to write some code to do. = Can you put that into the merge plan for the website? Robert: Yes. 3. RFC Services Projects - RPC use of new RFC format tools -- Heather and Henrik Russ: What did we learn about the tools? Heather: It's been a character-building experience. For the output, we = got some compliments, and then there is the conversation with Julian = about the fact that he doesn't consider it V3 complaint. The -bis = document for RFC 7991 is still in progress, so he will have to live with = disappointment for a while. Had a good suggestion about changing the = info pages to make the HTML icon first instead of the TXT since it's now = the preferred format. Still a lot of behind-the-scenes sorting things = out and trying to make sure that the XML is as it should be because = sometimes we have options on how things are accomplished, and Henrik has = been very supported there. A certain amount of irony on the quietness of = the community on the XML files versus the definition of the community. I = would like more feedback on the XML stuff, but-- Russ: By the time it's in the RFC Ed Queue they could care less about = the XML, they just want to know when they'll get the RFC. Heather: I didn't say I didn't understand this, but it's taking a lot of = time to get right. Robert: One thing that came out of this is we need to talk about when = and how we will link to the output of the new tools from the Datatracker = when an RFC is available. Is there anything to stop us from linking to = the RFC Ed version of that now? Henrik: We need to go by the cutoff date/number. I don't think we have = information to tell us whether it's published with or without XML. We = can figure it out and add links in the next release, certainly. Robert: I think there conversations about how they should affect the = grammar, Julian's comments about the ToC, the RPC's experience about = having to resort to artwork to get the layout that is expected should = come back to the grammar. Heather: Right now we're talking about what the goal is for = re-rendering, is the goal to do minimal re-rendering, pros and an cons. = Re the ToC, I started a thread with Henrik to discuss what we want to do = about that. Alice: Big thanks to Heather and Henrik for your support as the RPC has = been switching over.=20 Russ: Based on the number of releases this month, it's clear Henrik was = being very responsive to the RPC's needs; thanks very much. - XML2RFC Python3 only Henrik: Python2 will stop getting security updates at the end of the = year. Looking to turn off support for Python2 for all of our tools. The = library used to generate the PDF, we are currently 10 releases behind = because they stopped supporting Python2 10 releases ago. One of the = fixes since then is fixing an issue where you could have an infinite = loop. Alice ran into this with a PDF generation yesterday. Would like to = ask if we can move onto only Python3 so we can get past this issue. Russ: I see no problem about doing this with the RPC, but what if an = author isn't ready for this, can he still run Python2 on his own = machine? Robert: No. I think for XML2RFC we just need to tell people it's a = Python3 app, or else they can use the web application if needed. Henrik: And if we do it now, I would like to jump the XML2RFC version to = 3 at the same time; it's a strong signal that things are changing.=20 Russ: That makes sense to me. I think that we need to tell the community = that's where we're going. Does anyone thing otherwise?=20 [No] Russ: Henrik, can you draft a note to that effect, and I'll send it to = the community? Henrik: Sure. I have small things to push out for the RPC first, but = I'll draft the note and we can do the version change when we move to = Python3 only. - Deploying in-line errata on rfc-editor.org? -- Alice Alice: We touched on this on the last call. It's' currently in a beta = directory. The first step is to move it out of the beta directory, and = then adding links to it throughout the site, search results, info pages, = errata search results. It becomes a bigger thing if it's deployed more = widely. If we elevate this to the level of an additional format RFCs are = available in, it would also be listed in those places. A request to = include in the RFC-specific JSON record some updates that are = tangential. Right now, the files are only available for verified errata. = Right now there is an errata JSON file that has that information, but = getting the inline errata in places is not as simple as adding the = links, but I think the links plan could be a starting place, unless it's = more pressing to get it in the RFC-specific JSON files or elsewhere. Russ: Did we get rid of the beta part? Heather: We can do that, and I was IMing Sandy about what a better link = could be.=20 Russ: How about eliminating and putting it in errata? Heather: How about eliminating it and putting in inline-errata? The only = thing I won't compromise on was, the on rfc-interest someone said they = didn't like having the big scary warning label, but I will not get rid = of that.=20 - Security Review of RPC Tools -- Robert and Heather Robert via email: We are in the period where we are gathering proposals.=20= The deadline is 14Oct. We have received a few clarifying questions and=20= have answers ready for the 7Oct question response deadline. Robert: We are still gathering proposals and answering questions as they = are coming in. Nothing more to report right now. Russ: Bids are due next week? Robert: Correct. 4. Server Infrastructure - Expected Website Releases -- Robert Robert via email: I released a significant to the website behavior today=20= (affecting blog page performance). It should be in production before=20= we get to Tuesday's meeting. See . There will be several releases in the next couple of weeks that change=20= database internals without changing the public's view of the website.=20= The names of fields that editors use will be improved. After that, the major work items are to * Remove the current datatracker integration attempt * Migrate to Django 2 so that we can move to more recent wagtail=20 releases * Investigate reimplementation of the Area and Topic templates We'll be making smaller improvements with regular releases from now=20 on. We're discovering that the CSS framework used by the current system is=20= undocumented, and hard to work with. We are beginning to discuss a=20 project to rebase the site on Bootstrap4 while maintaining the look=20 and feel of the site. Robert: I'll focus on the Matomo integration so we can schedule = deploying it, and continue working through the list. One thing I want to = call attention to is at some point in the future we will want to = reimplement the styling basis for the website so that it uses the styles = correctly. Right now it's not internally consistent and I think we'd get = a lot of payback to moving to a system like bootstrap without doing any = redesign of how it is supposed to look. - IESG discussions of DMARC -- Henrik and Alexey -- When do we expect the next release of OpenARC? Ever? Henrik: I'll send another ping. Alissa: Roman and I will see Alexey tomorrow and can ask for an update. - Sever upgrades Glen: I've upgraded other servers I manage and am ready to do the = updates at any time, but given the complexity of what is running on the = IETF and RPC servers, I am trying to not rush blindly forward. There = will be a linear approach. I've reached out to Ryan, who has a = development server, and Priyanka who has a copy of the RPC server as her = development server, and we'll upgrade those in the next couple of weeks = and let them see what happens and what changes we need to make. Then = I'll circle back with the team and we will do this as we have in the = past, updating the sandbox and backup servers, and see how those go, and = then propose a day and time to do the production server. It will take = about 6 hours. It will be up for most of that time, but some services = can be interrupted. I would be inclined to try to do this on a Sunday or = Monday to give us time to recover, but in general it shouldn't be a big = deal. Short answer is, we're taking the steps and we'll keep you posted. Robert: More likely to be after 106 than before. Glen: That's wonderful. There is no fire here. I'd like to get it done = soon, but I can defer to the needs to the Tools Team and the IETF. Russ: I hear that it sounds like to Ryan + Priyanka and the sandbox = before 106, and then the other steps after. Glen: Yes. This is not a single event, it's a series of steps, due = diligence at a rate of speed we can control. The only one we have to = schedule is the one on the production server. Robert: I think we'll go with that. It may or may not make sense to move = the sandbox before the meeting. Glen: And offline we should talk about the sandbox and how use of it is = increasing. Robert: Agreed. 5. YANG Catalog - Putting yangcatalog.org in a Docker container -- Robert Robert via email: As noted in the last meeting, this is prioritized=20 behind major functionality issues in the yangcatalog project, but it=20= is getting cycles. I am currently to the point where most of the=20 containers come up the way they should in my development environment ,=20= but the confd and api_recovery containers are not reaching the=20 expected steady run-state. I am keeping pressure on this, but I don't=20= expect that we'll switch production to the containerized version in=20 the near future. Certainly not before IETF106. 6. Parking Lot - Search over www, datatracker, and mailarchive - Transition Datatracker to Django2 - Transition Website to Django2 7. AOB Robert via email: I think we should talk briefly about the state of=20 supporting markdown for minutes/agendas (and eventually other=20 documents), and how we should prioritize improving it. From nobody Mon Oct 28 08:19:24 2019 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 A9F32120137 for ; Mon, 28 Oct 2019 08:19:16 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=unavailable 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 JnVjT1ywYC55 for ; Mon, 28 Oct 2019 08:19:14 -0700 (PDT) Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 01974120098 for ; Mon, 28 Oct 2019 08:19:14 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 60BAC300B11 for ; Mon, 28 Oct 2019 11:19:12 -0400 (EDT) X-Virus-Scanned: amavisd-new at mail.smeinc.net Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 8x_6Rg-Q66La for ; Mon, 28 Oct 2019 11:19:11 -0400 (EDT) Received: from a860b60074bd.fios-router.home (pool-108-51-198-163.washdc.fios.verizon.net [108.51.198.163]) by mail.smeinc.net (Postfix) with ESMTPSA id 19CBE30055D; Mon, 28 Oct 2019 11:19:11 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) From: Russ Housley In-Reply-To: <9D5BE151-4B90-4D7F-BA1A-8FD8DAAFDF59@ietf.org> Date: Mon, 28 Oct 2019 11:19:11 -0400 Cc: IETF Tools Development Content-Transfer-Encoding: quoted-printable Message-Id: <3415A8C1-2615-4835-A3E3-71B18DB8FCD1@vigilsec.com> References: <9D5BE151-4B90-4D7F-BA1A-8FD8DAAFDF59@ietf.org> To: IETF Chair X-Mailer: Apple Mail (2.3445.104.11) Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] IESG strategic retreat X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2019 15:19:18 -0000 Alissa: The Datatracker had played a huge role in increasing transparency. I am = glad to hear that the IESG wants more transparency, but I cannot figure = out from the blog post what you really have in mind. Can we start a = discussion on the tools-development list to better understand you = desires? Russ > On Oct 28, 2019, at 11:14 AM, IETF Chair wrote: >=20 > Hi all, >=20 > The IESG held a retreat a few weeks ago and I wrote up a short blog = post about it here: https://www.ietf.org/blog/iesg-strategic-retreat/ >=20 > Best, > Alissa Cooper > IETF Chair From nobody Mon Oct 28 11:12:18 2019 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 62936120072 for ; Mon, 28 Oct 2019 11:12:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.701 X-Spam-Level: X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=PtI0xIFs; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=fQfkaj40 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 WkCtlA6D1c-f for ; Mon, 28 Oct 2019 11:12:15 -0700 (PDT) Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 344F412007A for ; Mon, 28 Oct 2019 11:12:15 -0700 (PDT) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id 419594F5; Mon, 28 Oct 2019 14:12:14 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Mon, 28 Oct 2019 14:12:14 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=E WS1r6JdrLW/g4JXFpnCgynfWJRniYC70QpHiBSxeA0=; b=PtI0xIFsy2rZycl9L KxPu6VZmG3/YE+vLX/l4r5KDgubQAdDWH1+f0kgUQXpEjcMwI5UD0t4hP5LlCMIO lJup1CWXnRJbRHe3uQSx2Wvok/ih2XEkXx3Wm5RtsIwJOADizIgobzGR5nIbWXZ9 NX5D5qa2h3ZrEmOiBccVWshkd8LoOjIZz2BNHzObZLwSCTJ4tusxkc2CJn0oj9zm aa4MtuWP2WmNVP/rE61OLDYKngI1ons09tI8wfcVg+Pu8bLo56RREP7teK1cVtGk GpXFpFNOTp6VCH0HaXaxkr3N7UQrxX5EXDWxFElLXMzRdkT2KfOzc1UGy/+ePTWb ry9PQ== DKIM-Signature: v=1; a=rsa-sha256; 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-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=EWS1r6JdrLW/g4JXFpnCgynfWJRniYC70QpHiBSxe A0=; b=fQfkaj40Kfcbd4kYZiJWqzDz96eozsqKe3XTGPCcZg48Mfr4L8gerXFnG fCqFxkvWmDviOvZlO2oy7hViRZzcNT4bMNxOGQnlPHSrx0RU/cFCQtpVMxUBQBK4 1/G/FGojKIhlSFwivf764Dj6VyKk5PT7B+xLwNSBsBXySMB5AWhVsn0UKiQ9qfE8 /vLq71RYVmgm0rbmWAd4d4YgMrUP3SH6cUPeRSgLKMX9twkpwwwaZdvf03d+HXZh K0s+TR2D83EcXU/Y8Qohr5pLCL4+7x4bjEOaluB3hW1XwOss5R6Z60/ga4u4p850 DZdT9Xt0A5uxWI9eQRn+LsWcpG/HA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrleelgdduuddtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhjgffgffkfhfvofesthhqmhdthhdtjeenucfhrhhomheptehlihhs shgrucevohhophgvrhcuoegrlhhishhsrgestghoohhpvghrfidrihhnqeenucffohhmrg hinhepihgvthhfrdhorhhgnecukfhppedujeefrdefkedruddujedrkeeknecurfgrrhgr mhepmhgrihhlfhhrohhmpegrlhhishhsrgestghoohhpvghrfidrihhnnecuvehluhhsth gvrhfuihiivgeptd X-ME-Proxy: Received: from rtp-vpn6-1429.cisco.com (unknown [173.38.117.88]) by mail.messagingengine.com (Postfix) with ESMTPA id 2063380068; Mon, 28 Oct 2019 14:12:13 -0400 (EDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) From: Alissa Cooper In-Reply-To: <3415A8C1-2615-4835-A3E3-71B18DB8FCD1@vigilsec.com> Date: Mon, 28 Oct 2019 13:12:12 -0500 Cc: IETF Tools Development , Alvaro Retana Content-Transfer-Encoding: quoted-printable Message-Id: <5BF15D2A-14EA-40C8-A0F3-C000DADC831E@cooperw.in> References: <9D5BE151-4B90-4D7F-BA1A-8FD8DAAFDF59@ietf.org> <3415A8C1-2615-4835-A3E3-71B18DB8FCD1@vigilsec.com> To: Russ Housley X-Mailer: Apple Mail (2.3445.9.1) Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] IESG strategic retreat X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2019 18:12:17 -0000 Hi Russ, Thanks. Alvaro took the action at the retreat to lead further = discussions about this, so he=E2=80=99s the person to chat with about = the status of those discussions. Best, Alissa > On Oct 28, 2019, at 10:19 AM, Russ Housley = wrote: >=20 > Alissa: >=20 > The Datatracker had played a huge role in increasing transparency. I = am glad to hear that the IESG wants more transparency, but I cannot = figure out from the blog post what you really have in mind. Can we = start a discussion on the tools-development list to better understand = you desires? >=20 > Russ >=20 >=20 >> On Oct 28, 2019, at 11:14 AM, IETF Chair wrote: >>=20 >> Hi all, >>=20 >> The IESG held a retreat a few weeks ago and I wrote up a short blog = post about it here: https://www.ietf.org/blog/iesg-strategic-retreat/ >>=20 >> Best, >> Alissa Cooper >> IETF Chair >=20 From nobody Thu Oct 31 01:04:56 2019 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 40442120834 for ; Thu, 31 Oct 2019 01:04:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.5 X-Spam-Level: X-Spam-Status: No, score=-14.5 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, SPF_PASS=-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 header.b=CEBq7feF; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=K7DD75C8 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 ogbqRSuRt1Ej for ; Thu, 31 Oct 2019 01:04:53 -0700 (PDT) Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F906120824 for ; Thu, 31 Oct 2019 01:04:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4861; q=dns/txt; s=iport; t=1572509093; x=1573718693; h=from:to:subject:date:message-id:mime-version; bh=AS8x2ONTPaaowaS37IG0ueC9isve/UlgK7xAU58sZ4M=; b=CEBq7feFcHDAPo9H4eap/N1Xv6lK75tdF30CtxChnVUR51ZaH6dSNGQH y8TuFskdago15iHYdu7AaH5Zd3fOxcbyOifDJXgg5Xgfo985rL236vNZg QQjvFsh2BPgufzQnzH2dAnPobHCkWTwpks8mONApDhqnR1SE7hu/mmX35 k=; IronPort-PHdr: =?us-ascii?q?9a23=3ASiMMQxFbFASNtljzhRsnh51GYnJ96bzpIg4Y7I?= =?us-ascii?q?YmgLtSc6Oluo7vJ1Hb+e4z1A3SRYuO7fVChqKWqK3mVWEaqbe5+HEZON0pNV?= =?us-ascii?q?cejNkO2QkpAcqLE0r+efP0fioxH8lqX15+9Hb9Ok9QS47z?= X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DjDQAclbpd/5RdJa1lHgELHIMZL1A?= =?us-ascii?q?FbFggBAsqhCiDRgOKdE6VGoRhglIDVAkBAQEMAQEtAgEBhFmDVSQ4EwIDCQE?= =?us-ascii?q?BBAEBAQIBBQRthTcBC4VqER0BATgRAQw+AgQwJwQ1gwABgXlNAy4BpjoCgTi?= =?us-ascii?q?IYHWBMoJ+AQEFgkmCShiCFwmBNoUYhnkYgUA/gREnH4pfMoIsjSAlgjiFPJg?= =?us-ascii?q?5CoIkhiyPBRuZX45AmU4CBAIEBQIOAQEFgWkigVhwFWUBgkFQEBSDBoNzilN?= =?us-ascii?q?0gSiNRAEB?= X-IronPort-AV: E=Sophos;i="5.68,250,1569283200"; d="scan'208,217";a="353828817" Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 31 Oct 2019 08:04:52 +0000 Received: from XCH-RCD-015.cisco.com (xch-rcd-015.cisco.com [173.37.102.25]) by rcdn-core-12.cisco.com (8.15.2/8.15.2) with ESMTPS id x9V84qUc003818 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL) for ; Thu, 31 Oct 2019 08:04:52 GMT Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-RCD-015.cisco.com (173.37.102.25) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 31 Oct 2019 03:04:51 -0500 Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 31 Oct 2019 04:04:51 -0400 Received: from NAM01-BN3-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Thu, 31 Oct 2019 04:04:50 -0400 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ZFMPGTybrMnsmxpGwIzj2fYNWheJl9dYEUszwadwGY/uG5TwM3LPNhVwlEMXJz/pKNeA+T+hWxBl9Ng4igGF7jxXQEfne770/5bjzPRw5txy6IVsE2ii0Zyhvz3BXgW1m2CrfEdv5qL+KF0Gr2YXjLc7hUPgKxov6HgDzh7Y9OdlTrMHI1Blyudop9xQyUCL5zTMIMOyWP3Eao0fHs0QdFpT4GnAvPb0oiV++AgwZRmT2uFVWxO0tlToSYKK2yi/nWVwIq7I5gEnKMB+QjqshFzElP3spa9tzf4DorFZ+9Z2SlhMPzrwu99qWlw8AqgbuYigb+DZSvatyE0aCESPMw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=AS8x2ONTPaaowaS37IG0ueC9isve/UlgK7xAU58sZ4M=; b=kBWn9mvjtAthMyTOrkioalicKyETYQ1Qluf8gk1mMKJNjsTbfp6kxxHdAqgXFxuX+ljqn5KeAiDDoT/t3/4UDrk31pr61yP9ENxPBG1AYSg4ZM8tO8zCKOXekRd5woA/xGSudwh39WWvQMKXjuD0b5EptgLi2YbbuuJadYgIo/1CuQULJa5+97yzAzVAKOEUAYtWMK+8XR2H9SGUPJDJA7SXs3+0ue1tqReq+wYXbnZqGH+7Ldh42xy9XEOwrk2DW8vOogHLn4ToFZ4N6pS+zpVFr0a7rZwD20LbhCL2RoT8jahm15atwhIQ2Uh1NosnQy4M0uQ9ZRfQjAHTtLYf8A== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=AS8x2ONTPaaowaS37IG0ueC9isve/UlgK7xAU58sZ4M=; b=K7DD75C8ImsJRd4xasecp4O+reYZIiLOtPeoPN74Q+hv5nXb4zs6dCtxP7rXbgNw1byVlVEJIF6ebfk6pgJPFp0HwlMvqpfpHJmOe/Ys2sqNgxyDUrehlDvBennZExeO3GOCYU8jgHL3Zy/gcWnciOrBEFsbI2xH2ZQmdq5AnRE= Received: from DM5PR11MB1753.namprd11.prod.outlook.com (10.175.88.141) by DM5PR11MB1675.namprd11.prod.outlook.com (10.172.38.136) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2387.24; Thu, 31 Oct 2019 08:04:50 +0000 Received: from DM5PR11MB1753.namprd11.prod.outlook.com ([fe80::c1f1:d33a:2203:5a39]) by DM5PR11MB1753.namprd11.prod.outlook.com ([fe80::c1f1:d33a:2203:5a39%7]) with mapi id 15.20.2387.028; Thu, 31 Oct 2019 08:04:49 +0000 From: "Eric Vyncke (evyncke)" To: "tools-development@ietf.org" Thread-Topic: IETF registration & NomCom info Thread-Index: AQHVj8He5Hp7PDiwyU6JjpXFVS/7dQ== Date: Thu, 31 Oct 2019 08:04:49 +0000 Message-ID: Accept-Language: fr-BE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/10.1e.0.191013 authentication-results: spf=none (sender IP is ) smtp.mailfrom=evyncke@cisco.com; x-originating-ip: [2001:420:c0c1:36:952f:79d4:bef1:7ff4] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 42919e64-d659-474c-1527-08d75dd900d0 x-ms-traffictypediagnostic: DM5PR11MB1675: x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:8273; x-forefront-prvs: 02070414A1 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(376002)(346002)(136003)(366004)(39860400002)(396003)(189003)(199004)(66446008)(186003)(64756008)(6506007)(81166006)(76116006)(86362001)(6116002)(2351001)(8676002)(66946007)(66476007)(54896002)(81156014)(6512007)(6306002)(102836004)(25786009)(256004)(46003)(8936002)(478600001)(9326002)(66556008)(4744005)(99286004)(71190400001)(2501003)(5660300002)(33656002)(71200400001)(6486002)(7736002)(2616005)(2906002)(486006)(14454004)(6916009)(36756003)(476003)(58126008)(5640700003)(6436002)(316002)(91956017); DIR:OUT; SFP:1101; SCL:1; SRVR:DM5PR11MB1675; H:DM5PR11MB1753.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: a7JKin1ef8Hwj8GqGZbh0Xl1dk7by0kBRSqexOEtuKcCxXQi3tUWNOw4WzcMMGZ4f+pw/l5yJ4jgLsoCJrocxM3PypNvyIqQiizZF2xYWraQM7iFLOZzxAWFZM9YfyHgYf9Thu+pYfmQNkw4MEapTnu9/UB04qNpJdDUrhVESmTN9vAgw3IuYmLGGqQguxLAGfNkt3xvYs5D+bhiywcgM+GbOz0CrT2DT7oadDRKaIDD5cLzej2Z+WzNL2CpI1O0PcNt5fAOcJAz4Xa7eDsLu451rQ1XW9brFRWd6nfpe7zagjbP1/LVjuWU5GsfuLSp3vkEIGophQJSN8LDEskwWKn/9uMwL9TUKENDOCp28mj6tSn10zJmyMG3vO5qrGnEXrjOLY1McTsb34v/0EXkIC5B0T3xtpW0Iw43cytBeetruT2lA9f0XKZBvZnUNI0R x-ms-exchange-transport-forked: True Content-Type: multipart/alternative; boundary="_000_D52B180642F24BD3969D2574BAB90B66ciscocom_" MIME-Version: 1.0 X-MS-Exchange-CrossTenant-Network-Message-Id: 42919e64-d659-474c-1527-08d75dd900d0 X-MS-Exchange-CrossTenant-originalarrivaltime: 31 Oct 2019 08:04:49.8288 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: 6f/rogRnp3RPjfLu3RitBDeoQrYkgXfPTt0QSZFM0618VyJ5z8gZk43P5LqJNq28uWjm50ohTmwJQZK15nNGug== X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR11MB1675 X-OriginatorOrg: cisco.com X-Outbound-SMTP-Client: 173.37.102.25, xch-rcd-015.cisco.com X-Outbound-Node: rcdn-core-12.cisco.com Archived-At: Subject: [TOOLS-DEVELOPMENT] IETF registration & NomCom info X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Oct 2019 08:04:55 -0000 --_000_D52B180642F24BD3969D2574BAB90B66ciscocom_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 SGVsbG8sDQoNCkkgdG9vayBhbiBhY3Rpb24gaXRlbSBhdCB0aGUgSUVTRyB0byBjbGFyaWZ5IHdo YXQgdGhlIOKAmERvIHlvdSBhZ3JlZSB0byBiZWNvbWUgYSBOb21Db20gbWVtYmVyP+KAmSBkdXJp bmcgdGhlIElFVEYgbWVldGluZyByZWdpc3RyYXRpb24gKHVuc3VyZSBhYm91dCB0aGUgZXhhY3Qg bGFiZWwgb2YgdGhpcyBjaGVjay1ib3gpIC4gVGhlIGFjdGlvbiBpdGVtIGlzIHRvIGRpc3BsYXkg KGJ5IGNsaWNraW5nIG9uIGEgPyBvciBwb3AtdXAgYm94IHdoZW4gcHV0dGluZyBhIOKAmGNyb3Nz 4oCZIGluIHRoZSBjaGVjay1ib3gpIGEgc21hbGwgdGV4dCBjbGFyaWZ5aW5nIHRoZSByb2xlIGFu ZCBjb25zdHJhaW50cyBvZiBhIGJlaW5nIGEgTm9tQ29tIG1lbWJlci4NCg0KV291bGQgdGhpcyBi ZSBwb3NzaWJsZT8gSWYgc28sIHRoZSB0ZXh0IGlzIHJlYWR5IG9uIG15IHNpZGUgdG8gYmUgYWRk ZWQgZm9yIG5leHQgdGltZSB0aGlzIE5vbUNvbSBjaGVjay1ib3ggaXMgZGlzcGxheWVkLCBzbywg aG93IGNhbiB3ZSBwcm9jZWVkPw0KDQpSZWdhcmRzDQoNCi3DqXJpYw0KDQo= --_000_D52B180642F24BD3969D2574BAB90B66ciscocom_ Content-Type: text/html; charset="utf-8" Content-ID: <1096B249F41E97409E9E824A5266BCB8@namprd11.prod.outlook.com> Content-Transfer-Encoding: base64 PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4 bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l dGEgbmFtZT0iR2VuZXJhdG9yIiBjb250ZW50PSJNaWNyb3NvZnQgV29yZCAxNSAoZmlsdGVyZWQg bWVkaXVtKSI+DQo8c3R5bGU+PCEtLQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFj ZQ0KCXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2 IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToy IDE1IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3Jt YWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1i b3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJp IixzYW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXBy aW9yaXR5Ojk5Ow0KCWNvbG9yOiMwNTYzQzE7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9 DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9y aXR5Ojk5Ow0KCWNvbG9yOiM5NTRGNzI7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpz cGFuLkVtYWlsU3R5bGUxNw0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1jb21wb3NlOw0KCWZv bnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0KLk1z b0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1mYW1pbHk6 IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6NjEyLjBw dCA3OTIuMHB0Ow0KCW1hcmdpbjo3Mi4wcHQgNzIuMHB0IDcyLjBwdCA3Mi4wcHQ7fQ0KZGl2Lldv cmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPg0KPC9oZWFkPg0K PGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9IiMwNTYzQzEiIHZsaW5rPSIjOTU0RjcyIj4NCjxkaXYg Y2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJG UiIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPkhlbGxvLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkZSIiBzdHlsZT0iZm9udC1zaXplOjEx LjBwdCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+ PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPkkgdG9vayBhbiBhY3Rpb24gaXRlbSBhdCB0 aGUgSUVTRyB0byBjbGFyaWZ5IHdoYXQgdGhlIOKAmERvIHlvdSBhZ3JlZSB0byBiZWNvbWUgYSBO b21Db20gbWVtYmVyP+KAmSBkdXJpbmcgdGhlIElFVEYgbWVldGluZyByZWdpc3RyYXRpb24gKHVu c3VyZSBhYm91dCB0aGUgZXhhY3QgbGFiZWwgb2YgdGhpcyBjaGVjay1ib3gpIC4gVGhlIGFjdGlv biBpdGVtIGlzIHRvDQogZGlzcGxheSAoYnkgY2xpY2tpbmcgb24gYSA/IG9yIHBvcC11cCBib3gg d2hlbiBwdXR0aW5nIGEg4oCYY3Jvc3PigJkgaW4gdGhlIGNoZWNrLWJveCkgYSBzbWFsbCB0ZXh0 IGNsYXJpZnlpbmcgdGhlIHJvbGUgYW5kIGNvbnN0cmFpbnRzIG9mIGEgYmVpbmcgYSBOb21Db20g bWVtYmVyLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu IHN0eWxlPSJmb250LXNpemU6MTEuMHB0Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8 cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+V291bGQg dGhpcyBiZSBwb3NzaWJsZT8gSWYgc28sIHRoZSB0ZXh0IGlzIHJlYWR5IG9uIG15IHNpZGUgdG8g YmUgYWRkZWQgZm9yIG5leHQgdGltZSB0aGlzIE5vbUNvbSBjaGVjay1ib3ggaXMgZGlzcGxheWVk LCBzbywgaG93IGNhbiB3ZSBwcm9jZWVkPzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0Ij48bzpwPiZuYnNwOzwv bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1z aXplOjExLjBwdCI+UmVnYXJkczxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0Ij48bzpwPiZuYnNwOzwvbzpwPjwv c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEx LjBwdCI+LcOpcmljPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+ PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv cD4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K --_000_D52B180642F24BD3969D2574BAB90B66ciscocom_-- From nobody Thu Oct 31 03:46:58 2019 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 1F3BD120118 for ; Thu, 31 Oct 2019 03:46:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.896 X-Spam-Level: X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=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 QpkPU4U4eqh8 for ; Thu, 31 Oct 2019 03:46:54 -0700 (PDT) Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69ECC1200F6 for ; Thu, 31 Oct 2019 03:46:54 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 91562300B0F for ; Thu, 31 Oct 2019 06:46:52 -0400 (EDT) X-Virus-Scanned: amavisd-new at mail.smeinc.net Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 33qb7SrqKcRj for ; Thu, 31 Oct 2019 06:46:50 -0400 (EDT) Received: from [172.26.8.135] (67-132-193-197.dia.static.qwest.net [67.132.193.197]) by mail.smeinc.net (Postfix) with ESMTPSA id 69C8B30021A; Thu, 31 Oct 2019 06:46:50 -0400 (EDT) From: Russ Housley Message-Id: <61D2B704-C436-4E26-B4D8-F396FEE06F73@vigilsec.com> Content-Type: multipart/alternative; boundary="Apple-Mail=_FB091765-4A0D-4377-8AA4-F77F2E216D46" Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Date: Thu, 31 Oct 2019 06:46:50 -0400 In-Reply-To: Cc: IETF Tools Development To: Eric Vyncke References: X-Mailer: Apple Mail (2.3445.104.11) Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] IETF registration & NomCom info X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Oct 2019 10:46:56 -0000 --Apple-Mail=_FB091765-4A0D-4377-8AA4-F77F2E216D46 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Eric: The registration tool is developed and maintained by the Secretariat. = You need to have this discussion with them. Russ > On Oct 31, 2019, at 4:04 AM, Eric Vyncke (evyncke) = wrote: >=20 > Hello, > =20 > I took an action item at the IESG to clarify what the =E2=80=98Do you = agree to become a NomCom member?=E2=80=99 during the IETF meeting = registration (unsure about the exact label of this check-box) . The = action item is to display (by clicking on a ? or pop-up box when putting = a =E2=80=98cross=E2=80=99 in the check-box) a small text clarifying the = role and constraints of a being a NomCom member. > =20 > Would this be possible? If so, the text is ready on my side to be = added for next time this NomCom check-box is displayed, so, how can we = proceed? > =20 > Regards > =20 > -=C3=A9ric >=20 --Apple-Mail=_FB091765-4A0D-4377-8AA4-F77F2E216D46 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Eric:

The = registration tool is developed and maintained by the Secretariat. =  You need to have this discussion with them.

Russ


On Oct 31, 2019, at 4:04 AM, Eric Vyncke (evyncke) <evyncke@cisco.com> = wrote:

Hello,
 
I took an action = item at the IESG to clarify what the =E2=80=98Do you agree to become a = NomCom member?=E2=80=99 during the IETF meeting registration (unsure = about the exact label of this check-box) . The action item is to display = (by clicking on a ? or pop-up box when putting a =E2=80=98cross=E2=80=99 = in the check-box) a small text clarifying the role and constraints of a = being a NomCom member.
 
Would this be = possible? If so, the text is ready on my side to be added for next time = this NomCom check-box is displayed, so, how can we proceed?
 
Regards
 
-=C3=A9ric

= --Apple-Mail=_FB091765-4A0D-4377-8AA4-F77F2E216D46-- From nobody Thu Oct 31 03:55:31 2019 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 40010120273 for ; Thu, 31 Oct 2019 03:55:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.499 X-Spam-Level: X-Spam-Status: No, score=-14.499 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, 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 header.b=N9g1HcKh; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=SxDrtzdg 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 IuFQT7pZlq7A for ; Thu, 31 Oct 2019 03:55:27 -0700 (PDT) Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 50F851201DC for ; Thu, 31 Oct 2019 03:55:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9361; q=dns/txt; s=iport; t=1572519327; x=1573728927; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=ll3ikHt3z7ewHVnt1QyBtcJezpOn+t+jS26wEVA+zc0=; b=N9g1HcKh7/+MFuGvqWOzdKlK0TjZAWy5WaTpalPepJ0Mov7HlxtQyOuP cteI0/bJQYprjL8jbhCYPfm3PXjNYHj2JTm3tclqrAKLJGBRIbWcj9mgk STY1M+TUkhv+lEq35HYSPCXONWZUzGV53KPwMXO4xiatCWTvmV7l6dhdR Q=; IronPort-PHdr: =?us-ascii?q?9a23=3AP8BWZh94bzO8Tf9uRHGN82YQeigqvan1NQcJ65?= =?us-ascii?q?0hzqhDabmn44+8ZB7E/fs4iljPUM2b8P9Ch+fM+4HYEW0bqdfk0jgZdYBUER?= =?us-ascii?q?oMiMEYhQslVcObGEvwL/PCZC0hF8MEX1hgrDm2?= X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DUAADjvLpd/4gNJK1lGgEBAQEBAQE?= =?us-ascii?q?BAQMBAQEBEQEBAQICAQEBAYF9gRwvUAVsWCAECyqEKINGA4p0gjklkwqEYYJ?= =?us-ascii?q?SA1QJAQEBDAEBLQIBAYRAAheDWiQ4EwIDCQEBBAEBAQIBBQRthTcMhVEBAQE?= =?us-ascii?q?BAxIRHQEBNwEPAgEIEQMBAigDAgICMBQJCAIEDgUigwABgXlNAy4BpXACgTi?= =?us-ascii?q?IYHWBMoJ+AQEFgkmCUxiCFwmBNoUYhnkYgUA/gREnDBOCTD6EZRaCWjKCLI0?= =?us-ascii?q?gJYI4hTyYOwqCJIYtjwgbmWGoEwIEAgQFAg4BAQWBaSKBWHAVZQGCQVAQFIM?= =?us-ascii?q?Gg3OKU3SBKI1EAQE?= X-IronPort-AV: E=Sophos;i="5.68,250,1569283200"; d="scan'208,217";a="362265350" Received: from alln-core-3.cisco.com ([173.36.13.136]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 31 Oct 2019 10:55:26 +0000 Received: from XCH-RCD-018.cisco.com (xch-rcd-018.cisco.com [173.37.102.28]) by alln-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id x9VAtQ3c019815 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 31 Oct 2019 10:55:26 GMT Received: from xhs-rtp-001.cisco.com (64.101.210.228) by XCH-RCD-018.cisco.com (173.37.102.28) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 31 Oct 2019 05:55:25 -0500 Received: from xhs-aln-001.cisco.com (173.37.135.118) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 31 Oct 2019 06:55:24 -0400 Received: from NAM03-DM3-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Thu, 31 Oct 2019 05:55:24 -0500 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=DLYTMz0sH7psBkWsIzs3BjJ+EEK6Onkn+XNlcNOeHc1fwEYyEa150iMoOX1BmndtBgOq/nlsVt3c6oAM8Rh9I+XnzVarDzrkgEuSgBXkkHBh+Di5W1apx1tQxmUJPNbG+QyfvUkA99LeWHcfYqA0MR4zeQKf8WVQLnMmYktRIg2Hae8MUnv7AjNut/4Ngt9nPRLr+8NSacJdJYFSUFLU1vps/kswQJXgYqMmDhbCQrtT4BQTp+GD0UGrTxrxpJ5GeAaf1ApHFY/0iX27vqs3/zWgZmUB6NtzbxEGbVmKPENDVvZQ3HaW4LdJuld6sIZJ+zW+wqTwU5/nCPcgfp6MoA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ll3ikHt3z7ewHVnt1QyBtcJezpOn+t+jS26wEVA+zc0=; b=SFMafyWWfSjuWymJ/t2bDOkDxcMcLGixVj+aVrFrwoa7unRjkp8t8obHdRN03rcgWBtoBlkgapDkOxzuYmarFicSUQ+CalfrJTD+DV/EvWS3exr2Tst2npKRtXKcZW8/fE1GO0Ne8OOPkCVMqo7g+ebKsx/CHgnvuvMqJkkQTsC0JNKUkbUO4MgrE3axVLt6eny5M0unnea+r8lJU+6M/BhTfcaFozBYYVLYo/fFzeQHlX8Oylsm4uDqycE0T3NpuKwJ2A0/203NnREHQLtbYlqE1zIrfBqS48lqmD6xgrMVfEnaoNlZIeT78mSpdPG6Qj9/q4x9Fo4Itpx0CGXMYA== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ll3ikHt3z7ewHVnt1QyBtcJezpOn+t+jS26wEVA+zc0=; b=SxDrtzdg41Pvjil28HrjnpgvEGFRf7mYtsFKpYmV7fIex8otDb5GCZ6ksc5Zt3vOHpiwguixSWfrw2HGWbWvhzJqXhdjljBIxbPjUMqVYz4hfIZC/QmQmE8r+KDyBmgd7wMdT9LHdno2V3xElQpYY0TncJ0s1DGOuHNb9nBuhOE= Received: from DM5PR11MB1753.namprd11.prod.outlook.com (10.175.88.141) by DM5PR11MB1420.namprd11.prod.outlook.com (10.168.106.138) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2387.22; Thu, 31 Oct 2019 10:55:24 +0000 Received: from DM5PR11MB1753.namprd11.prod.outlook.com ([fe80::c1f1:d33a:2203:5a39]) by DM5PR11MB1753.namprd11.prod.outlook.com ([fe80::c1f1:d33a:2203:5a39%7]) with mapi id 15.20.2387.028; Thu, 31 Oct 2019 10:55:22 +0000 From: "Eric Vyncke (evyncke)" To: Russ Housley CC: IETF Tools Development Thread-Topic: [TOOLS-DEVELOPMENT] IETF registration & NomCom info Thread-Index: AQHVj8He5Hp7PDiwyU6JjpXFVS/7dad0kXwAgAATJgA= Date: Thu, 31 Oct 2019 10:55:22 +0000 Message-ID: References: <61D2B704-C436-4E26-B4D8-F396FEE06F73@vigilsec.com> In-Reply-To: <61D2B704-C436-4E26-B4D8-F396FEE06F73@vigilsec.com> Accept-Language: fr-BE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/10.1e.0.191013 authentication-results: spf=none (sender IP is ) smtp.mailfrom=evyncke@cisco.com; x-originating-ip: [2001:420:c0c1:36:301d:dd02:8648:82d4] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 8438edd1-cb04-41e2-8a1d-08d75df0d420 x-ms-traffictypediagnostic: DM5PR11MB1420: x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:8882; x-forefront-prvs: 02070414A1 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(376002)(39860400002)(366004)(136003)(346002)(396003)(199004)(189003)(236005)(14454004)(6436002)(6512007)(54896002)(33656002)(478600001)(446003)(6916009)(6306002)(2616005)(229853002)(71200400001)(6486002)(71190400001)(2906002)(11346002)(46003)(36756003)(256004)(486006)(476003)(6116002)(81166006)(99286004)(316002)(86362001)(6246003)(102836004)(5660300002)(8676002)(58126008)(186003)(81156014)(8936002)(4326008)(66446008)(66946007)(91956017)(53546011)(76176011)(6506007)(7736002)(25786009)(64756008)(66476007)(76116006)(66556008); DIR:OUT; SFP:1101; SCL:1; SRVR:DM5PR11MB1420; H:DM5PR11MB1753.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: TbT1KtmBYGrdQi9kEHbSMooQqJHt9tMoB+bMPtMA9DBwVX2QemYEW25lHlZY/24MsqWAc5gMri96CKBcqM8YSmM7VT9iie8LYHmj3FPDskEkEd+ZMRSShvVRfEZn/LE4XxPLUgJZx10iYQSTTAHKHzDR38UY9XNf1T47EOh87+fo7UmCKCKjE3pnJK/fPJ8s3ipHznMmEtCiiAYwi0T5bozeSo8bJ8w+9ZWXWiegGu8D37LIVXw/poVhJ7gwELBJZqGN0vEhI7V9ONBdVmCYUtTAhipag5irL50VtraWt/yGSN7D7fFbwyugGxxO9B+fR2Qmd2BB2gYd/4fLyGVI85t4TAs/bnFM7UACrE/iStfQ+442bIRQIhVQoszDTzj3279/CcCUKz0e4ITBrGdGvqVxthQGXnT3/j8mygNNbejwnsNP7P43K3KDxySEBOMc x-ms-exchange-transport-forked: True Content-Type: multipart/alternative; boundary="_000_FA04EB5EA13D42848D43E6A594A6508Cciscocom_" MIME-Version: 1.0 X-MS-Exchange-CrossTenant-Network-Message-Id: 8438edd1-cb04-41e2-8a1d-08d75df0d420 X-MS-Exchange-CrossTenant-originalarrivaltime: 31 Oct 2019 10:55:22.7271 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: bjNF/9BT3mApg3n6GzWWTs5nmkB1n+ZZdIsK+S3cXWeRDtbJtWL3gOZeSvVT2enc21tzZ+lwcwBWFbdBqe795A== X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR11MB1420 X-OriginatorOrg: cisco.com X-Outbound-SMTP-Client: 173.37.102.28, xch-rcd-018.cisco.com X-Outbound-Node: alln-core-3.cisco.com Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] IETF registration & NomCom info X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Oct 2019 10:55:29 -0000 --_000_FA04EB5EA13D42848D43E6A594A6508Cciscocom_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 77u/VGhhbmsgeW91IGZvciB0aGlzIHByb21wdCByZXBseSwgSSBhbSBjb250YWN0aW5nIHRoZSBz ZWNyZXRhcmlhdA0KDQotw6lyaWMNCg0KRnJvbTogUnVzcyBIb3VzbGV5IDxob3VzbGV5QHZpZ2ls c2VjLmNvbT4NCkRhdGU6IFRodXJzZGF5LCAzMSBPY3RvYmVyIDIwMTkgYXQgMTE6NDcNClRvOiBF cmljIFZ5bmNrZSA8ZXZ5bmNrZUBjaXNjby5jb20+DQpDYzogSUVURiBUb29scyBEZXZlbG9wbWVu dCA8dG9vbHMtZGV2ZWxvcG1lbnRAaWV0Zi5vcmc+DQpTdWJqZWN0OiBSZTogW1RPT0xTLURFVkVM T1BNRU5UXSBJRVRGIHJlZ2lzdHJhdGlvbiAmIE5vbUNvbSBpbmZvDQoNCkVyaWM6DQoNClRoZSBy ZWdpc3RyYXRpb24gdG9vbCBpcyBkZXZlbG9wZWQgYW5kIG1haW50YWluZWQgYnkgdGhlIFNlY3Jl dGFyaWF0LiAgWW91IG5lZWQgdG8gaGF2ZSB0aGlzIGRpc2N1c3Npb24gd2l0aCB0aGVtLg0KDQpS dXNzDQoNCg0KDQpPbiBPY3QgMzEsIDIwMTksIGF0IDQ6MDQgQU0sIEVyaWMgVnluY2tlIChldnlu Y2tlKSA8ZXZ5bmNrZUBjaXNjby5jb208bWFpbHRvOmV2eW5ja2VAY2lzY28uY29tPj4gd3JvdGU6 DQoNCkhlbGxvLA0KDQpJIHRvb2sgYW4gYWN0aW9uIGl0ZW0gYXQgdGhlIElFU0cgdG8gY2xhcmlm eSB3aGF0IHRoZSDigJhEbyB5b3UgYWdyZWUgdG8gYmVjb21lIGEgTm9tQ29tIG1lbWJlcj/igJkg ZHVyaW5nIHRoZSBJRVRGIG1lZXRpbmcgcmVnaXN0cmF0aW9uICh1bnN1cmUgYWJvdXQgdGhlIGV4 YWN0IGxhYmVsIG9mIHRoaXMgY2hlY2stYm94KSAuIFRoZSBhY3Rpb24gaXRlbSBpcyB0byBkaXNw bGF5IChieSBjbGlja2luZyBvbiBhID8gb3IgcG9wLXVwIGJveCB3aGVuIHB1dHRpbmcgYSDigJhj cm9zc+KAmSBpbiB0aGUgY2hlY2stYm94KSBhIHNtYWxsIHRleHQgY2xhcmlmeWluZyB0aGUgcm9s ZSBhbmQgY29uc3RyYWludHMgb2YgYSBiZWluZyBhIE5vbUNvbSBtZW1iZXIuDQoNCldvdWxkIHRo aXMgYmUgcG9zc2libGU/IElmIHNvLCB0aGUgdGV4dCBpcyByZWFkeSBvbiBteSBzaWRlIHRvIGJl IGFkZGVkIGZvciBuZXh0IHRpbWUgdGhpcyBOb21Db20gY2hlY2stYm94IGlzIGRpc3BsYXllZCwg c28sIGhvdyBjYW4gd2UgcHJvY2VlZD8NCg0KUmVnYXJkcw0KDQotw6lyaWMNCg0K --_000_FA04EB5EA13D42848D43E6A594A6508Cciscocom_ Content-Type: text/html; charset="utf-8" Content-ID: <330F7E1CA4CBAC4B95015990161E5B27@namprd11.prod.outlook.com> Content-Transfer-Encoding: base64 PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4 bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l dGEgbmFtZT0iR2VuZXJhdG9yIiBjb250ZW50PSJNaWNyb3NvZnQgV29yZCAxNSAoZmlsdGVyZWQg bWVkaXVtKSI+DQo8c3R5bGU+PCEtLQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFj ZQ0KCXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2 IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToy IDE1IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3Jt YWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1i b3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJp IixzYW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXBy aW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQph OnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5 Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnAubXNv bm9ybWFsMCwgbGkubXNvbm9ybWFsMCwgZGl2Lm1zb25vcm1hbDANCgl7bXNvLXN0eWxlLW5hbWU6 bXNvbm9ybWFsOw0KCW1zby1tYXJnaW4tdG9wLWFsdDphdXRvOw0KCW1hcmdpbi1yaWdodDowY207 DQoJbXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87DQoJbWFyZ2luLWxlZnQ6MGNtOw0KCWZvbnQt c2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0Kc3Bhbi5F bWFpbFN0eWxlMTgNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1p bHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6d2luZG93dGV4dDt9DQouTXNvQ2hwRGVm YXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LXNpemU6MTAuMHB0O30N CkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjYxMi4wcHQgNzkyLjBwdDsNCgltYXJnaW46NzIu MHB0IDcyLjBwdCA3Mi4wcHQgNzIuMHB0O30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3Jk U2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5r PSJibHVlIiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBj bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBjbGFzcz0iRW1haWxTdHlsZTE4Ij7vu79UaGFuayB5b3Ug Zm9yIHRoaXMgcHJvbXB0IHJlcGx5LCBJIGFtIGNvbnRhY3RpbmcgdGhlIHNlY3JldGFyaWF0PG86 cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gY2xhc3M9IkVt YWlsU3R5bGUxOCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v cm1hbCI+PHNwYW4gY2xhc3M9IkVtYWlsU3R5bGUxOCI+LcOpcmljPC9zcGFuPjxvOnA+PC9vOnA+ PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2IHN0 eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNCNUM0REYgMS4wcHQ7cGFkZGluZzoz LjBwdCAwY20gMGNtIDBjbSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxl ZnQ6MzYuMHB0Ij48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtjb2xvcjpibGFjayI+ RnJvbToNCjwvc3Bhbj48L2I+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Y29sb3I6Ymxh Y2siPlJ1c3MgSG91c2xleSAmbHQ7aG91c2xleUB2aWdpbHNlYy5jb20mZ3Q7PGJyPg0KPGI+RGF0 ZTogPC9iPlRodXJzZGF5LCAzMSBPY3RvYmVyIDIwMTkgYXQgMTE6NDc8YnI+DQo8Yj5UbzogPC9i PkVyaWMgVnluY2tlICZsdDtldnluY2tlQGNpc2NvLmNvbSZndDs8YnI+DQo8Yj5DYzogPC9iPklF VEYgVG9vbHMgRGV2ZWxvcG1lbnQgJmx0O3Rvb2xzLWRldmVsb3BtZW50QGlldGYub3JnJmd0Ozxi cj4NCjxiPlN1YmplY3Q6IDwvYj5SZTogW1RPT0xTLURFVkVMT1BNRU5UXSBJRVRGIHJlZ2lzdHJh dGlvbiAmYW1wOyBOb21Db20gaW5mbzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRp dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDozNi4wcHQiPjxvOnA+ Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFy Z2luLWxlZnQ6MzYuMHB0Ij5FcmljOiA8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0i TXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MzYuMHB0Ij48bzpwPiZuYnNwOzwvbzpwPjwv cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVm dDozNi4wcHQiPlRoZSByZWdpc3RyYXRpb24gdG9vbCBpcyBkZXZlbG9wZWQgYW5kIG1haW50YWlu ZWQgYnkgdGhlIFNlY3JldGFyaWF0LiAmbmJzcDtZb3UgbmVlZCB0byBoYXZlIHRoaXMgZGlzY3Vz c2lvbiB3aXRoIHRoZW0uDQo8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y bWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MzYuMHB0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwv ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDozNi4w cHQiPlJ1c3M8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt YWwiIHN0eWxlPSJtYXJnaW4tbGVmdDozNi4wcHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRp dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDozNi4wcHQiPjxicj4N Cjxicj4NCjxvOnA+PC9vOnA+PC9wPg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6NS4w cHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5 bGU9Im1hcmdpbi1sZWZ0OjM2LjBwdCI+T24gT2N0IDMxLCAyMDE5LCBhdCA0OjA0IEFNLCBFcmlj IFZ5bmNrZSAoZXZ5bmNrZSkgJmx0OzxhIGhyZWY9Im1haWx0bzpldnluY2tlQGNpc2NvLmNvbSI+ ZXZ5bmNrZUBjaXNjby5jb208L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjM2LjBwdCI+PG86cD4mbmJz cDs8L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJt YXJnaW4tbGVmdDozNi4wcHQiPjxzcGFuIGxhbmc9IkZSIj5IZWxsbyw8L3NwYW4+PHNwYW4gc3R5 bGU9ImZvbnQtc2l6ZToxMi4wcHQiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRp dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDozNi4wcHQiPjxzcGFu IGxhbmc9IkZSIj4mbmJzcDs8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQiPjxv OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi IHN0eWxlPSJtYXJnaW4tbGVmdDozNi4wcHQiPkkgdG9vayBhbiBhY3Rpb24gaXRlbSBhdCB0aGUg SUVTRyB0byBjbGFyaWZ5IHdoYXQgdGhlIOKAmERvIHlvdSBhZ3JlZSB0byBiZWNvbWUgYSBOb21D b20gbWVtYmVyP+KAmSBkdXJpbmcgdGhlIElFVEYgbWVldGluZyByZWdpc3RyYXRpb24gKHVuc3Vy ZSBhYm91dCB0aGUgZXhhY3QgbGFiZWwgb2YgdGhpcyBjaGVjay1ib3gpIC4gVGhlIGFjdGlvbiBp dGVtIGlzIHRvIGRpc3BsYXkNCiAoYnkgY2xpY2tpbmcgb24gYSA/IG9yIHBvcC11cCBib3ggd2hl biBwdXR0aW5nIGEg4oCYY3Jvc3PigJkgaW4gdGhlIGNoZWNrLWJveCkgYSBzbWFsbCB0ZXh0IGNs YXJpZnlpbmcgdGhlIHJvbGUgYW5kIGNvbnN0cmFpbnRzIG9mIGEgYmVpbmcgYSBOb21Db20gbWVt YmVyLjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0Ij48bzpwPjwvbzpwPjwvc3Bhbj48L3A+ DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6 MzYuMHB0Ij4mbmJzcDs8c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdCI+PG86cD48L286cD48 L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1h cmdpbi1sZWZ0OjM2LjBwdCI+V291bGQgdGhpcyBiZSBwb3NzaWJsZT8gSWYgc28sIHRoZSB0ZXh0 IGlzIHJlYWR5IG9uIG15IHNpZGUgdG8gYmUgYWRkZWQgZm9yIG5leHQgdGltZSB0aGlzIE5vbUNv bSBjaGVjay1ib3ggaXMgZGlzcGxheWVkLCBzbywgaG93IGNhbiB3ZSBwcm9jZWVkPzxzcGFuIHN0 eWxlPSJmb250LXNpemU6MTIuMHB0Ij48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxk aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MzYuMHB0Ij4mbmJz cDs8c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdCI+PG86cD48L286cD48L3NwYW4+PC9wPg0K PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjM2 LjBwdCI+UmVnYXJkczxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0Ij48bzpwPjwvbzpwPjwv c3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFy Z2luLWxlZnQ6MzYuMHB0Ij4mbmJzcDs8c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdCI+PG86 cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIg c3R5bGU9Im1hcmdpbi1sZWZ0OjM2LjBwdCI+LcOpcmljPHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox Mi4wcHQiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN c29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDozNi4wcHQiPjxzcGFuIHN0eWxlPSJmb250LXNp emU6MTIuMHB0Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0K PC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8 L2h0bWw+DQo= --_000_FA04EB5EA13D42848D43E6A594A6508Cciscocom_-- From nobody Thu Oct 31 08:03:35 2019 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 E899912081C for ; Thu, 31 Oct 2019 08:03:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.996 X-Spam-Level: X-Spam-Status: No, score=-1.996 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_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 4TcCN05UEfmn for ; Thu, 31 Oct 2019 08:03:30 -0700 (PDT) Received: from mail-wm1-x32b.google.com (mail-wm1-x32b.google.com [IPv6:2a00:1450:4864:20::32b]) (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 508BA120811 for ; Thu, 31 Oct 2019 08:03:30 -0700 (PDT) Received: by mail-wm1-x32b.google.com with SMTP id t26so2179208wmi.4 for ; Thu, 31 Oct 2019 08:03:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=0trWZH8zCcVPu2FQ9GYCvO0AWs1p3zVUyQaaOCufEIM=; b=kxsd+D4O39fvqc7Xr3dPOmbuYXhTK//0dKubDNq1HflIIzCrINqznHkBjxqnQTfWnL wgzAe2qCdf79t/U1CywbBTqrnh/0ZN/FDkaUIVL1du9FHJG9pzPAwzcsnUb3pZURz9b9 FTgdNIZUhIWeDAYPf8zCgxXdcAub3pZaZlM55sdKWyFssKNy9hZBcplcRGJGVQPdmrp8 pdtFbZqCRIw/CKQUDfQr1SjHHObzfV2EXzbxzO8POM7W2iKs3NUQAl+tcJy5Rryn0yR0 97n8EASBAocZmLU8kwwGFlA+GbdSvHRCeMhuir1bjjyduoOvP7F/TdcqsrikpDngumZ0 cJYA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=0trWZH8zCcVPu2FQ9GYCvO0AWs1p3zVUyQaaOCufEIM=; b=NIWN1gGWsOzrl8Jly7/sRWppX/mctvnNmkvXn/tL/Q5ECYj8b9lhuZTehTbtZU3GKr zSJm9UxzrvHlknksleYmQOjNCpSlzcHK7D4LayJnnMa5//6IuwrlQevjBkI8LYzoe7g4 q+J48RNdJ5zmYZLEzgEtjgYjQL4EPStdxCYXiuCwBPFHKwJEXZcBDpIgVRLY8NDqv/eu JSrH5V3wpCdN4ofcJjtyVfNr/sLx7Wh9KBv3XogYar0ufdfA2BqLR3pTs7cnjsqtynIv chorFWAmT0tHenJrEQPf6gbdYlhh/mjIuhCqRADhnOKPs8k0ilTrQaQ0Hik6fbxmo8/k NA6w== X-Gm-Message-State: APjAAAXrkT4QYZNANPtS1LfdEPhooQVHb7E2fgr7nJPKaIXpXR8+OhY9 g/p+IZDnji6ivWSF8HsPpg4xC4aR+8BK5pWHEfca3A== X-Google-Smtp-Source: APXvYqztTRZnqWPKBwhNedztDdcU0P29A6hy5RaUN4It07gai5x/jr9/cp7aIgX6EpLPn+3pB/kFxCGndwQs5j76Pbo= X-Received: by 2002:a7b:c924:: with SMTP id h4mr5933841wml.143.1572534208830; Thu, 31 Oct 2019 08:03:28 -0700 (PDT) Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Thu, 31 Oct 2019 08:03:28 -0700 From: Alvaro Retana In-Reply-To: <5BF15D2A-14EA-40C8-A0F3-C000DADC831E@cooperw.in> References: <9D5BE151-4B90-4D7F-BA1A-8FD8DAAFDF59@ietf.org> <3415A8C1-2615-4835-A3E3-71B18DB8FCD1@vigilsec.com> <5BF15D2A-14EA-40C8-A0F3-C000DADC831E@cooperw.in> MIME-Version: 1.0 Date: Thu, 31 Oct 2019 08:03:28 -0700 Message-ID: To: Russ Housley Cc: IETF Tools Development , Alissa Cooper Content-Type: multipart/alternative; boundary="000000000000ea232105963626a1" Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] IESG strategic retreat X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Oct 2019 15:03:33 -0000 --000000000000ea232105963626a1 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Russ: Hi! We really haven=E2=80=99t had any movement on this item. The conversation = that triggered the AI was about the possibility of clearly tracking who has the ball during WG processing=E2=80=A6similar to what we have now for the IESG (=E2=80=9CRevised ID Needed=E2=80=9D, =E2=80=9CAD Followup=E2=80=9D, etc.). There are 5 other ADs who showed interest in this topic=E2=80=A6. Personall= y, I think that we should first have a clear understanding of what actions we want to track and who should/may be triggering them before we start thinking about changes to the datatracker (or anything else). Again, we haven=E2=80=99t started working on this yet. Roman is one of the interested ADs =E2=80=94 I=E2=80=99m sure he=E2=80=99ll keep the rest of th= e team in the loop=E2=80=A6but we might also come back later (when the idea/purpose is clearer) to consult with the team as needed; and definitely before anything is finalized. Thanks!! Alvaro. On October 28, 2019 at 2:12:16 PM, Alissa Cooper (alissa@cooperw.in) wrote: Hi Russ, Thanks. Alvaro took the action at the retreat to lead further discussions about this, so he=E2=80=99s the person to chat with about the status of tho= se discussions. Best, Alissa > On Oct 28, 2019, at 10:19 AM , Russ Housley wrote: > > Alissa: > > The Datatracker had played a huge role in increasing transparency. I am glad to hear that the IESG wants more transparency, but I cannot figure out from the blog post what you really have in mind. Can we start a discussion on the tools-development list to better understand you desires? > > Russ > --000000000000ea232105963626a1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable =
Russ:

Hi!

W= e really haven=E2=80=99t had any movement on this item.=C2=A0 The conversat= ion that triggered the AI was about the possibility of clearly tracking who= has the ball during WG processing=E2=80=A6similar to what we have now for = the IESG (=E2=80=9CRevised ID Needed=E2=80=9D, =E2=80=9CAD Followup=E2=80= =9D, etc.).
=
There a= re 5 other ADs who showed interest in this topic=E2=80=A6. Personally, I th= ink that we should first have a clear understanding of what actions we want= to track and who should/may be triggering them before we start thinking ab= out changes to the datatracker (or anything else).

Again, we haven=E2=80=99t started working o= n this yet.=C2=A0 Roman is one of the interested ADs =E2=80=94 I=E2=80=99m = sure he=E2=80=99ll keep the rest of the team in the loop=E2=80=A6but we mig= ht also come back later (when the idea/purpose is clearer) to consult with = the team as needed; and definitely before anything is finalized.

Thanks!!

Alvaro.

On October 28, 2019 at 2:12:16 PM, Alissa Cooper (alissa@cooperw.in) wrote:

Hi Ru= ss,=C2=A0

Thanks. Alvaro took the action at the retrea= t to lead further discussions about this, so he=E2=80=99s the person to cha= t with about the status of those discussions.=C2=A0

Be= st,=C2=A0
Alissa=C2=A0


>=C2=A0On Oct 28, 2019, at 10:19 AM, Russ Housley <h= ousley@vigilsec.com> wrote:=C2=A0
>=C2=A0
> Alissa:=C2=A0
>=C2=A0
> The Datatracker had played a= huge role in increasing transparency. I am glad to hear that the IESG want= s more transparency, but I cannot figure out from the blog post what you re= ally have in mind. Can we start a discussion on the tools-development list = to better understand you desires?=C2= =A0
>=C2=A0
> Russ=C2=A0
>=C2=A0
--000000000000ea232105963626a1--