Re: IETF Tools Architecture and Strategy Team

"John Levine" <johnl@taugh.com> Thu, 06 February 2020 22:47 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6739E120840 for <ietf@ietfa.amsl.com>; Thu, 6 Feb 2020 14:47:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=kDKvx6OM; dkim=pass (1536-bit key) header.d=taugh.com header.b=N4C/skjf
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 tZPL8wXPGDny for <ietf@ietfa.amsl.com>; Thu, 6 Feb 2020 14:47:54 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 3820D120833 for <ietf@ietf.org>; Thu, 6 Feb 2020 14:47:54 -0800 (PST)
Received: (qmail 92149 invoked from network); 6 Feb 2020 22:47:52 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=167e9.5e3c9798.k2002; bh=hLc5zFvnox1ZFkVdtRFe8ndFnPpi123l/RWHX85Ro+s=; b=kDKvx6OMks8E5FS4L5eJfVRduz6U4DCgqPLX6SczvCXHuTZ2ENZoV5pgOBl6hvVjIQwRg0ultGYJqBJ6+amKyRZBbzIjw8xuNG630ItMLAv136DfDi0DM9LxGist5hl300szR4qgsHqMUAt4+m3a9btVYaeiZFTjQIlhym/LgqdfvsJ5eY//bfWVIGnesAPFfbIwo3nruvKODRejs/KnzTG01xhzveQ9dvtIsRyaU/w2OA2OWBWW+fW10y7O3bOg
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=167e9.5e3c9798.k2002; bh=hLc5zFvnox1ZFkVdtRFe8ndFnPpi123l/RWHX85Ro+s=; b=N4C/skjfTsINUllikrXDv1Yl0pw76ZmxDTofw6ktj8URo3O8P7r5PjJnjst688KkR/puELMso0TjOMLgRfdNaZErAcZHO6Wd/YW2aQ73v/8mBsCXjNJGhtCiO51hf0vEH4h/j8vqYl31/9qPkzh2lu2BV3ruI4Im37YdmDXmKLbJ8bamYJI8nTN4KEgX3aPVIfPDit8be9uxRxJufS56uzNU8vtxWB57sVbjTme95oJJf2dfwsFidJ5Rag1epAmN
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 06 Feb 2020 22:47:52 -0000
Received: by ary.qy (Postfix, from userid 501) id DD3C313CEF3E; Thu, 6 Feb 2020 17:47:51 -0500 (EST)
Date: Thu, 06 Feb 2020 17:47:51 -0500
Message-Id: <20200206224751.DD3C313CEF3E@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: IETF Tools Architecture and Strategy Team
In-Reply-To: <b5d87b84-ae42-e415-2b5a-09602470b2fd@gmail.com>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9Bv0KZxaAXNdurCXGCVut_zkHmQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Feb 2020 22:47:55 -0000

In article <b5d87b84-ae42-e415-2b5a-09602470b2fd@gmail.com> you write:
>Alissa, how will liaison with the RFC Production Center be managed? xml2rfc is not just an IETF tool, and it's in the middle of a complex deployment process with known discrepancies between the
>documented and implemented versions of the v3 syntax, not to mention some very tricky issues around SVG support. 

I'm on the tools team.  As you might expect, these issues are in the middle of my aRSE plate.

R's,
John