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

Glen <glen@amsl.com> Fri, 05 April 2019 19:23 UTC

Return-Path: <glen@amsl.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 18C8412009E for <tools-development@ietfa.amsl.com>; Fri, 5 Apr 2019 12:23:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.199
X-Spam-Level:
X-Spam-Status: No, score=-104.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_WHITELIST=-100] 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 Kz-kxj96fQY1 for <tools-development@ietfa.amsl.com>; Fri, 5 Apr 2019 12:23:15 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 09E7B120073 for <tools-development@ietf.org>; Fri, 5 Apr 2019 12:23:15 -0700 (PDT)
Received: from mail.amsl.com (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTPS id 9A0FC1C38D0 for <tools-development@ietf.org>; Fri, 5 Apr 2019 12:23:12 -0700 (PDT)
Received: from mail-ot1-f45.google.com (mail-ot1-f45.google.com [209.85.210.45]) by c8a.amsl.com (Postfix) with ESMTPSA id 806941C38CE for <tools-development@ietf.org>; Fri, 5 Apr 2019 12:23:12 -0700 (PDT)
Received: by mail-ot1-f45.google.com with SMTP id j10so6680892otq.0 for <tools-development@ietf.org>; Fri, 05 Apr 2019 12:23:14 -0700 (PDT)
X-Gm-Message-State: APjAAAXgnpxJBROSLW4siwEgeATzDC8tzP0XvIifnEwLIwfwrzI/nn1C xUmKm8iGUOu7mfYcHPPYwLXse5zbOzfIDfssQKE=
X-Google-Smtp-Source: APXvYqxTfvCkwHFIcbgRKrDkHPMI2rkPOvO+LRCFUGW0zrvczjoXPA7HWL+UI/uGsi2dp9EsIu5DnJmUVoF2IykeoG0=
X-Received: by 2002:a9d:61d6:: with SMTP id h22mr9304226otk.251.1554492193996; Fri, 05 Apr 2019 12:23:13 -0700 (PDT)
MIME-Version: 1.0
References: <C0F870F3-C8CC-478F-AC61-668E2D9BBDD4@vigilsec.com>
In-Reply-To: <C0F870F3-C8CC-478F-AC61-668E2D9BBDD4@vigilsec.com>
From: Glen <glen@amsl.com>
Date: Fri, 5 Apr 2019 12:23:02 -0700
X-Gmail-Original-Message-ID: <CABL0ig5FBCoYSJnhYmH437wsqV00_d=+A0UBp=nfe4MUBEDErw@mail.gmail.com>
Message-ID: <CABL0ig5FBCoYSJnhYmH437wsqV00_d=+A0UBp=nfe4MUBEDErw@mail.gmail.com>
To: IETF Tools Development <tools-development@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000007848c0585cd6b0c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-development/mSbPalIhLMC1gVNQ1_O7elfy9lg>
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: Fri, 05 Apr 2019 19:23:17 -0000

In the interest of pre-call clarifications:

On Wed, Apr 3, 2019 at 12:27 PM Russ Housley <housley@vigilsec.com> wrote:
> Tools Call Agenda -- 9 April 2019 at 1:00 Eastern
>    - Transfer 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