IETF Logo Mail Archive

Re: [OPSAWG] example in tacacs yang was Re: Shepherd review of draft-ietf-opsawg-tacacs-yang

"Wubo (lana)" <lana.wubo@huawei.com> Fri, 19 June 2020 06:12 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 7CFA13A08BD; Thu, 18 Jun 2020 23:12:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, 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 ZkEw6YpK_CDM; Thu, 18 Jun 2020 23:12:16 -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 45D713A0841; Thu, 18 Jun 2020 23:12:16 -0700 (PDT)
Received: from lhreml735-chm.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id E94C5E50491CC61C0A63; Fri, 19 Jun 2020 07:12:09 +0100 (IST)
Received: from dggeme701-chm.china.huawei.com (10.1.199.97) by lhreml735-chm.china.huawei.com (10.201.108.86) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.1913.5; Fri, 19 Jun 2020 07:12:09 +0100
Received: from dggeme702-chm.china.huawei.com (10.1.199.98) by dggeme701-chm.china.huawei.com (10.1.199.97) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Fri, 19 Jun 2020 14:12:07 +0800
Received: from dggeme702-chm.china.huawei.com ([10.9.48.229]) by dggeme702-chm.china.huawei.com ([10.9.48.229]) with mapi id 15.01.1913.007; Fri, 19 Jun 2020 14:12:07 +0800
From: "Wubo (lana)" <lana.wubo@huawei.com>
To: "Joe Clarke (jclarke)" <jclarke@cisco.com>, tom petch <ietfc@btconnect.com>
CC: opsawg <opsawg@ietf.org>, "draft-ietf-opsawg-tacacs-yang@ietf.org" <draft-ietf-opsawg-tacacs-yang@ietf.org>
Thread-Topic: example in tacacs yang was Re: Shepherd review of draft-ietf-opsawg-tacacs-yang
Thread-Index: AdZGAIn427iPMWyAwkaTxJ9CxxxtKA==
Date: Fri, 19 Jun 2020 06:12:06 +0000
Message-ID: <fe299a038c2c4996b0743cc0a6b2e5cc@huawei.com>
Accept-Language: en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.164.123.110]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/FG3_u4uhAXj8xDgxUI66gawfrLY>
Subject: Re: [OPSAWG] example in tacacs yang was Re: Shepherd review of draft-ietf-opsawg-tacacs-yang
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: Fri, 19 Jun 2020 06:12:18 -0000

Hi Joe, Tom,

Thanks for the review. I will fix it in the next revision.

Best regards,
Bo

-----邮件原件-----
发件人: Joe Clarke (jclarke) [mailto:jclarke@cisco.com] 
发送时间: 2020年6月19日 1:16
收件人: tom petch <ietfc@btconnect.com>
抄送: opsawg <opsawg@ietf.org>; draft-ietf-opsawg-tacacs-yang@ietf.org
主题: Re: example in tacacs yang was Re: Shepherd review of draft-ietf-opsawg-tacacs-yang



> On Jun 18, 2020, at 12:01, tom petch <ietfc@btconnect.com> wrote:
> 
> From: OPSAWG <opsawg-bounces@ietf.org> on behalf of Joe Clarke (jclarke) <jclarke=40cisco.com@dmarc.ietf.org>
> Sent: 28 May 2020 15:52
> To: opsawg
> 
> 
> Looking at the example in tacacs-yang-06  I see it uses an address of 10.10..10.x. I think that this should be an address reserved for documentation 192.0.2 if I recall.

Yep, good catch.  Authors, can you update to something in 192.0.2.0/24?  Thanks.

Joe

v2.23.0 | Report a Bug | By Email