Re: [OPSAWG] CALL FOR ADOPTION: draft-dahm-tacacs-tls13

Alan DeKok <aland@deployingradius.com> Mon, 11 July 2022 18:41 UTC

Return-Path: <aland@deployingradius.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EB25C06B98D for <opsawg@ietfa.amsl.com>; Mon, 11 Jul 2022 11:41:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sVJ3DtNzLqR8 for <opsawg@ietfa.amsl.com>; Mon, 11 Jul 2022 11:41:11 -0700 (PDT)
Received: from mail.networkradius.com (mail.networkradius.com [62.210.147.122]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D370C06B989 for <opsawg@ietf.org>; Mon, 11 Jul 2022 11:41:10 -0700 (PDT)
Received: from smtpclient.apple (unknown [75.98.136.130]) by mail.networkradius.com (Postfix) with ESMTPSA id DECEE357; Mon, 11 Jul 2022 18:41:00 +0000 (UTC)
Authentication-Results: NetworkRADIUS; dmarc=none (p=none dis=none) header.from=deployingradius.com
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.100.31\))
From: Alan DeKok <aland@deployingradius.com>
In-Reply-To: <BN9PR11MB53714D5E1F0E161087C8BDADB8829@BN9PR11MB5371.namprd11.prod.outlook.com>
Date: Mon, 11 Jul 2022 14:40:59 -0400
Cc: "opsawg@ietf.org" <opsawg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <360F40CB-E8BB-4EE3-B351-995CD6DE7688@deployingradius.com>
References: <BN9PR11MB53714D5E1F0E161087C8BDADB8829@BN9PR11MB5371.namprd11.prod.outlook.com>
To: "Joe Clarke (jclarke)" <jclarke=40cisco.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3696.100.31)
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/vIKA6NxA6J6JZGGPXEeXztZ7j1c>
Subject: Re: [OPSAWG] CALL FOR ADOPTION: draft-dahm-tacacs-tls13
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jul 2022 18:41:15 -0000

On Jul 8, 2022, at 10:16 AM, Joe Clarke (jclarke) <jclarke=40cisco.com@dmarc.ietf.org> wrote:
> 
> Hello, WG.  The chairs are starting a three week call for adoption for the TACACS+ TLS work that has been recently submitted.  This work was initially proposed at the same time the broader TACACS+ protocol was also brought the working group.  The consensus then was to create an informational draft describing the as-is TACACS+ protocol (with all of its security shortcomings) and to focus on more robust security later.
>  
> This call for adoption is only for the https://www.ietf.org/id/draft-dahm-tacacs-tls13-00.html draft and will go three weeks to take into account the IETF 114 meeting in Philadelphia.
>  
> Please reply on-list if you want the working group to adopt this work, as well as with comments on the work as it stands currently.  The CfA will end on July 29, 2022.

  I support adoption of this work.

  Alan DeKok.