Re: [OPSAWG] WG adoption poll for draft-zheng-opsawg-tacacs-yang-02

"Wubo (lana)" <lana.wubo@huawei.com> Wed, 10 July 2019 07:05 UTC

Return-Path: <lana.wubo@huawei.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 0FE0D120108; Wed, 10 Jul 2019 00:05:24 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 CSDh5xRzaUaU; Wed, 10 Jul 2019 00:05:20 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 5EAAD120103; Wed, 10 Jul 2019 00:05:20 -0700 (PDT)
Received: from LHREML711-CAH.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 357E33E522B8F14188FF; Wed, 10 Jul 2019 08:05:17 +0100 (IST)
Received: from dggeme702-chm.china.huawei.com (10.1.199.98) by LHREML711-CAH.china.huawei.com (10.201.108.34) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 10 Jul 2019 08:05:16 +0100
Received: from dggeme752-chm.china.huawei.com (10.3.19.98) by dggeme702-chm.china.huawei.com (10.1.199.98) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1591.10; Wed, 10 Jul 2019 15:05:14 +0800
Received: from dggeme752-chm.china.huawei.com ([10.6.80.76]) by dggeme752-chm.china.huawei.com ([10.6.80.76]) with mapi id 15.01.1591.008; Wed, 10 Jul 2019 15:05:14 +0800
From: "Wubo (lana)" <lana.wubo@huawei.com>
To: "Joe Clarke (jclarke)" <jclarke@cisco.com>, Eliot Lear <lear@cisco.com>
CC: Qin Wu <bill.wu@huawei.com>, Tianran Zhou <zhoutianran@huawei.com>, "opsawg@ietf.org" <opsawg@ietf.org>, OpsAWG Chairs <opsawg-chairs@ietf.org>
Thread-Topic: [OPSAWG] WG adoption poll for draft-zheng-opsawg-tacacs-yang-02
Thread-Index: AdU24sAA4GsEpuamTYWHaN0Xic9MVQ==
Date: Wed, 10 Jul 2019 07:05:14 +0000
Message-ID: <e2eae5fdd40b4b50b12692d5f181a726@huawei.com>
Accept-Language: en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.134.189.23]
Content-Type: multipart/alternative; boundary="_000_e2eae5fdd40b4b50b12692d5f181a726huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/U2EnnNMr7LPVh99wIFcnnMpR62I>
Subject: Re: [OPSAWG] WG adoption poll for draft-zheng-opsawg-tacacs-yang-02
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 10 Jul 2019 07:05:24 -0000

Thank Joe and Eliot for the comments and suggestions, I will specify these two points for discussion in my slides.

Thanks,
Bo

发件人: Joe Clarke (jclarke) [mailto:jclarke@cisco.com]
发送时间: 2019年7月9日 23:15
收件人: Eliot Lear <lear@cisco.com>
抄送: Wubo (lana) <lana.wubo@huawei.com>; Qin Wu <bill.wu@huawei.com>; Tianran Zhou <zhoutianran@huawei.com>; opsawg@ietf.org; OpsAWG Chairs <opsawg-chairs@ietf.org>
主题: Re: [OPSAWG] WG adoption poll for draft-zheng-opsawg-tacacs-yang-02




On Jul 9, 2019, at 05:35, Eliot Lear <lear@cisco.com<mailto:lear@cisco.com>> wrote:




On 9 Jul 2019, at 08:59, Wubo (lana) <lana.wubo@huawei.com<mailto:lana.wubo@huawei.com>> wrote:

Thank Eliot for pointing out these questions. I share a similar view with Qin, and I suggest to make the following changes in the next version:

1. draft-ietf-opsawg-tacacs will be changed as a normative reference according to RFC3967.

Several points: please take into account that RFC 8067 updates RFC 3967.  What this means is that you should probably have a brief chat with the chairs and Ignas on this point to see what he wants.  It may also be worth a little bit of discussion time.

Agreed on your points here.  I do think this should be a standards track document, and I think a downref would be acceptable in this case.  But this is worth addressing as an issue for your draft in your slot.




2. For the second point, I think your concern may be whether the TACACS + YANG model is flexible enough to accommodate the TACACS advanced features.

I think the augmentation is exactly what you want to do for this sort of thing.

This was also my thinking.  If/when a T+/TLS draft comes out and additional configuration is required, that could be an augmentation or even a bis to this model.  From a YANG versioning standpoint, we want models to evolve.

Joe