Re: [TOOLS-DEVELOPMENT] Tools Call Agenda -- 9 April 2019 at 1:00 Eastern

"Eric Vyncke (evyncke)" <evyncke@cisco.com> Mon, 08 April 2019 05:53 UTC

Return-Path: <evyncke@cisco.com>
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 4CA9E1203B0 for <tools-development@ietfa.amsl.com>; Sun, 7 Apr 2019 22:53:05 -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=hSB3ZCwk; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=eHJ505e1
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 L68XbPcRmjzW for <tools-development@ietfa.amsl.com>; Sun, 7 Apr 2019 22:53:02 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 86B4B1203AB for <tools-development@ietf.org>; Sun, 7 Apr 2019 22:53:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11319; q=dns/txt; s=iport; t=1554702782; x=1555912382; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=08wwGCYVfxc2QEPFQ1pKpMnWWoTgJTfBE8s/cDsAcdw=; b=hSB3ZCwkGk+Qch57qvtU6KYNYAqpMk9+FMQsIHgFJQjBP5LAC9oojfCL k/1i0GdQx1eSvvRKys09GN2L7zNuTk50pu8vqRKJkXtsqJyzfcvdQD/2V eUpZBsb6S0L/n8M2PyDS9AZK3ZYK9K/f8tEz5OVvmJU3fHKNNjsl/GzNy A=;
IronPort-PHdr: =?us-ascii?q?9a23=3ASLaZfB+Nh8m6G/9uRHGN82YQeigqvan1NQcJ65?= =?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?A0AQAAAf4apc/5RdJa1lGgEBAQEBAgE?= =?us-ascii?q?BAQEHAgEBAQGBUQUBAQEBCwGBDi9QA2hUIAQLJ4QOg0cDhFKKVEqBaCWDCo9?= =?us-ascii?q?EhEqBLoEkA1QOAQEbEYRAAheFRSI0CQ0BAQMBAQkBAwJtHAyFSgEBAQMBIx0?= =?us-ascii?q?BASQUBAsCAQgRAwECAScDAgICMBQJCAIEAQkJgyIBgRFMAw0IAQKhXwKKFHG?= =?us-ascii?q?BL4J5AQEFgkaCMhiCDAiBMAGLRheBQD+BOAwTghcHLj6BBIMqNhaCVDGCJo0?= =?us-ascii?q?WhC6URQkCiAGMABqCYpF6g1aHfYhBiz0CBAIEBQIOAQEFgU84gVZwFWUBgkE?= =?us-ascii?q?JggEYg1eFFIU/coEoj0UBAQ?=
X-IronPort-AV: E=Sophos;i="5.60,324,1549929600"; d="scan'208,217";a="256463710"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 08 Apr 2019 05:53:01 +0000
Received: from XCH-ALN-016.cisco.com (xch-aln-016.cisco.com [173.36.7.26]) by rcdn-core-12.cisco.com (8.15.2/8.15.2) with ESMTPS id x385r0cT024750 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 8 Apr 2019 05:53:00 GMT
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by XCH-ALN-016.cisco.com (173.36.7.26) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 8 Apr 2019 00:52:59 -0500
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 8 Apr 2019 01:52:58 -0400
Received: from NAM03-DM3-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 8 Apr 2019 00:52:58 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector1-cisco-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=08wwGCYVfxc2QEPFQ1pKpMnWWoTgJTfBE8s/cDsAcdw=; b=eHJ505e1/SMSUWnIEedP/IlZnh5aKrtTa1SXO0oDMCqbGCj55I/UMjSZqmcOYPfAbOKIgAkicxJ0glegcx0CTAz+cI/OAaPrViBr6Rb4OekikUx6NGuDk17VYIzp8aN9KmOhiqhY14/jZQ6E9BmzpC6w2rZKWWd6FFPXSE5MVeY=
Received: from MN2PR11MB4144.namprd11.prod.outlook.com (20.179.150.210) by MN2PR11MB3840.namprd11.prod.outlook.com (20.178.254.147) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1771.21; Mon, 8 Apr 2019 05:52:58 +0000
Received: from MN2PR11MB4144.namprd11.prod.outlook.com ([fe80::9158:74ee:b94a:d51f]) by MN2PR11MB4144.namprd11.prod.outlook.com ([fe80::9158:74ee:b94a:d51f%3]) with mapi id 15.20.1771.011; Mon, 8 Apr 2019 05:52:58 +0000
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: Glen <glen@amsl.com>, IETF Tools Development <tools-development@ietf.org>
Thread-Topic: [TOOLS-DEVELOPMENT] Tools Call Agenda -- 9 April 2019 at 1:00 Eastern
Thread-Index: AQHU6lNXjRRTzmSI30CA3xaagI4tjKYt9VIAgAP2L4A=
Date: Mon, 8 Apr 2019 05:52:57 +0000
Message-ID: <A4C790AC-9696-499F-B3E1-5106E4D3D30E@cisco.com>
References: <C0F870F3-C8CC-478F-AC61-668E2D9BBDD4@vigilsec.com> <CABL0ig5FBCoYSJnhYmH437wsqV00_d=+A0UBp=nfe4MUBEDErw@mail.gmail.com>
In-Reply-To: <CABL0ig5FBCoYSJnhYmH437wsqV00_d=+A0UBp=nfe4MUBEDErw@mail.gmail.com>
Accept-Language: fr-BE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.17.1.190326
authentication-results: spf=none (sender IP is ) smtp.mailfrom=evyncke@cisco.com;
x-originating-ip: [2001:420:c0c1:36:cce:fa9a:1802:e38b]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: dbfe284c-1659-4420-ec7f-08d6bbe673da
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600139)(711020)(4605104)(2017052603328)(7193020); SRVR:MN2PR11MB3840;
x-ms-traffictypediagnostic: MN2PR11MB3840:
x-ms-exchange-purlcount: 3
x-microsoft-antispam-prvs: <MN2PR11MB3840CD2DF0EAFB6D687F357AA92C0@MN2PR11MB3840.namprd11.prod.outlook.com>
x-forefront-prvs: 0001227049
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(136003)(366004)(39860400002)(396003)(376002)(346002)(199004)(189003)(36756003)(46003)(2616005)(99286004)(53386004)(476003)(7736002)(82746002)(6246003)(256004)(110136005)(105586002)(33656002)(6436002)(606006)(14454004)(236005)(6306002)(106356001)(446003)(186003)(6116002)(53936002)(54896002)(2906002)(6512007)(58126008)(11346002)(76176011)(53546011)(486006)(6506007)(5660300002)(97736004)(8936002)(6486002)(8676002)(71200400001)(71190400001)(81156014)(81166006)(68736007)(83716004)(86362001)(478600001)(229853002)(316002)(102836004)(25786009); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3840; H:MN2PR11MB4144.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-message-info: 8ZeSTGZ+BaapOwynKLIYwnXYlAnhgfY0vhFmpU8UsnmPDYz8a6mUcAgYecrc1hsDhpJNr32qz81QpmfyyD0Wsax6vCtDMFn7v2y90O6EAJJ/gNCY0zOLUG4EZuxbInMI/AwWMqBv8mKy/dHm07d3IxZF10pI/TdpHLttSQa27qeD56w9Z2g6ljGG2RvFdo4ZXoTJDuKx/84XRvmg1Ei82uosDPRLHrvT91PTyV/uaY4+43KB4FEYvis4p6hWvwiVyTF8UVfFnU2IXudy1G861BanRGHsSTkyYiBCQsHdHeu5WyK3UJaaN83vX7W5zwvPFi47d+ZITfzqHJQtHU0MwzO1+2TAPWNYTKgALVr0t5fZjS7OS7xkJI28tgo8K/V5PV0EXoadelhsv3eDYbTuMY6yA/Ee1d9hwFwNa38xrRI=
Content-Type: multipart/alternative; boundary="_000_A4C790AC9696499FB3E15106E4D3D30Eciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: dbfe284c-1659-4420-ec7f-08d6bbe673da
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Apr 2019 05:52:57.8662 (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-Transport-CrossTenantHeadersStamped: MN2PR11MB3840
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.26, xch-aln-016.cisco.com
X-Outbound-Node: rcdn-core-12.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-development/brx5cfuo12SvwKLS3MFb9di92ng>
Subject: Re: [TOOLS-DEVELOPMENT] Tools Call Agenda -- 9 April 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 <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Apr 2019 05:53:06 -0000

Glen,

The domain can indeed be transferred at any time.

And yang.amsl.com runs indeed outside if the usual IETF infrastructure. The Docker containerization has started during the hackathon and AFAIK the Pantheon contractor works on it with good progress (but not yet there AFAIK)

-éric

From: TOOLS-DEVELOPMENT <tools-development-bounces@ietf.org> on behalf of Glen Barney <glen@amsl.com>
Date: Friday, 5 April 2019 at 21:23
To: IETF Tools Development <tools-development@ietf.org>
Subject: Re: [TOOLS-DEVELOPMENT] Tools Call Agenda -- 9 April 2019 at 1:00 Eastern

In the interest of pre-call clarifications:

On Wed, Apr 3, 2019 at 12:27 PM Russ Housley <housley@vigilsec.com<mailto:housley@vigilsec.com>> wrote:
> Tools Call Agenda -- 9 April 2019 at 1:00 Eastern
>    - Transfer yangcatalog.org<http://yangcatalog.org> to the IETF Trust -- Eric

I have the token for this.  I have a few steps to take before I'll be ready to complete the move, but expect the domain transfer to be completed within the next few weeks.

>    - Transfer operations to the IETF Secretariat -- Eric and Glen

There are probably a number of steps to this that remain.  The AMS-provided server in OVH Canada appears to have resolved the prior connection challenges faced by Eric.  The previous plan was for Eric to finish the work, and then for us to review the setup with an eye to integrating the service into the existing IETF service field.  If that is still the plan, then Eric has the token to finish his work, and then I have the token to review and migrate.

But I think there has also been discussion about using this as a containerization target, packaging it up instead into a Docker container for subsequent deployment.  If that is the plan, then I *think* maybe Eric has the token to finish his work, and then Robert wanted to review for Docker containerization.

I could be completely wrong, this is just how I recall prior discussions, and I mention it now so that we can clarify the plan on the call and keep the project moving in the desired direction.

Glen