Re: [yang-doctors] [Last-Call] Yangdoctors last call review of draft-ietf-opsawg-tacacs-yang-03

john heasley <heas@shrubbery.net> Thu, 07 May 2020 18:10 UTC

Return-Path: <heas@shrubbery.net>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F66D3A0C08; Thu, 7 May 2020 11:10:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-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 F2JQLM9iHN73; Thu, 7 May 2020 11:10:21 -0700 (PDT)
Received: from guelah.shrubbery.net (guelah.shrubbery.net [198.58.5.1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F2A463A0C11; Thu, 7 May 2020 11:10:20 -0700 (PDT)
Received: by guelah.shrubbery.net (Postfix, from userid 7053) id 6A3E3288F1F; Thu, 7 May 2020 18:10:20 +0000 (UTC)
Date: Thu, 07 May 2020 18:10:20 +0000
From: john heasley <heas@shrubbery.net>
To: Ladislav Lhotka <ladislav.lhotka@nic.cz>
Cc: tom petch <ietfc@btconnect.com>, "Wubo (lana)" <lana.wubo@huawei.com>, "Joe Clarke (jclarke)" <jclarke@cisco.com>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>, "draft-ietf-opsawg-tacacs-yang.all@ietf.org" <draft-ietf-opsawg-tacacs-yang.all@ietf.org>, "last-call@ietf.org" <last-call@ietf.org>
Message-ID: <20200507181020.GH56911@shrubbery.net>
References: <3f67cb112ccb4c5eb1ef3bc868cb76ec@huawei.com> <DB7PR07MB4522D597746CA882144AFF3EA0A50@DB7PR07MB4522.eurprd07.prod.outlook.com> <eb14bcb3-151a-9e27-37b9-1f6e8f389c10@nic.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <eb14bcb3-151a-9e27-37b9-1f6e8f389c10@nic.cz>
X-PGPkey: http://www.shrubbery.net/~heas/public-key.asc
X-note: live free, or die!
X-homer: i just want to have a beer while i am caring.
X-Claimation: an engineer needs a manager like a fish needs a bicycle
X-reality: only YOU can put an end to the embarrassment that is Tom Cruise
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/fcAfp-1Yuj-rLDXdGthtd9PKyCg>
Subject: Re: [yang-doctors] [Last-Call] Yangdoctors last call review of draft-ietf-opsawg-tacacs-yang-03
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Email list of the yang-doctors directorate <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 May 2020 18:10:24 -0000

Thu, May 07, 2020 at 03:02:24PM +0200, Ladislav Lhotka:
> > [Bo] Please see if the definition below is correct:
> >   typedef tcsplus-server-type {
> >        type bits {
> >          bit authentication {
> >            description
> >              "When set, the server is an authentication server.";
> >          }
> >          bit authorization {
> >            description
> >              "When set, the server is an authorization server.";
> >          }
> >          bit accounting {
> >            description
> >              "When set, the server is an accounting server.";
> >          }
> >          bit all {
> >            description
> >              "When set, the server can be all types of TACACS+ servers.";
> >          }
> > 
> >        }
> >        description
> >          "server-type can be set to authentication/authorization/accounting or any combination of the three types.
> >           When all three types are supported, either "all" or the three bits setting can be used;
> >      }
> > 
> > <tp>
> > I would drop the all.   I know that I suggested it, or an asterisk, but I was thinking that this was a common  case.  Joe suggests that no accounting is the commoner - I do not have sufficient exposure to know - in which case I would not bother with 'all'.  Whether or not to make auth/auth  the default I have no particular view on - as I say, I lack the exposure to be confident about that.
> > 
> > Having 'all' adds complexity, two ways to something, while making a small saving in message size - on balance, not worth it.
> 
> Agreed. Lada

Note that enabling certain types of accounting is rare, at least in my
opinion.  eg: enabling login accounting is not rare, while command
accounting is rare because it is expensive esp. on some particular devices.

Also, rare or not, enabling it for a tacacs server is sort of orthogonal.
it will not be used for that purpose unless some form of accounting is
enabled.

I'll have to look at the model again; i do not recall if the model allows
for particular accounting types w/o augmentation.