Re: [OPSAWG] draft-ietf-opsawg-tacacs-06 ASCII

"Douglas Gash (dcmgash)" <dcmgash@cisco.com> Sun, 17 September 2017 12:47 UTC

Return-Path: <dcmgash@cisco.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 E679B132D44 for <opsawg@ietfa.amsl.com>; Sun, 17 Sep 2017 05:47:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.52
X-Spam-Level:
X-Spam-Status: No, score=-14.52 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 wsqXOJVUyay0 for <opsawg@ietfa.amsl.com>; Sun, 17 Sep 2017 05:47:49 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C0F45132026 for <opsawg@ietf.org>; Sun, 17 Sep 2017 05:47:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1726; q=dns/txt; s=iport; t=1505652469; x=1506862069; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=PWVghrJW1i6wOCnyrvwfEm6IJGuzelw/8UW5yT5++Yw=; b=AjC5xWhfyc1IuL6Koi5/RFTfHYSI/cuJH+u9A59F1D6mp9GqbG+zELLi bZFjyrf+yJDFjap0p7TK5pJJeAZZJhbFFhUn9F5g3UWWfzyNCJWPPSa3+ DFob6KUDPXw6JNUlGCW5dRqK6tjA9LmeaBPsiPOlUDraOwqmtKPqP4DyB M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ChAABkbr5Z/5hdJa1eGQEBAQEBAQEBAQEBBwEBAQEBg1qBUicHg26KII9ymBqCEgqFOwIahBI/GAECAQEBAQEBAWsohRkGDiYxFBACAQgcKAICMCUCBA4FijOOGJ1eBoIpiyQBAQEBAQEBAQEBAQEBAQEBAQEBAQEdgQiCI4IChluFD4J2gmYFmECISAKLNYkeghOFaop7lQgCERkBgTgBHziBDXcVhWIcgWd2iBqBDwEBAQ
X-IronPort-AV: E=Sophos;i="5.42,407,1500940800"; d="scan'208";a="300073846"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 17 Sep 2017 12:47:46 +0000
Received: from XCH-ALN-011.cisco.com (xch-aln-011.cisco.com [173.36.7.21]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id v8HCljIa026096 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sun, 17 Sep 2017 12:47:46 GMT
Received: from xch-aln-014.cisco.com (173.36.7.24) by XCH-ALN-011.cisco.com (173.36.7.21) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Sun, 17 Sep 2017 07:47:45 -0500
Received: from xch-aln-014.cisco.com ([173.36.7.24]) by XCH-ALN-014.cisco.com ([173.36.7.24]) with mapi id 15.00.1263.000; Sun, 17 Sep 2017 07:47:45 -0500
From: "Douglas Gash (dcmgash)" <dcmgash@cisco.com>
To: Alan DeKok <aland@deployingradius.com>
CC: "t.petch" <ietfc@btconnect.com>, Eliot Lear <lear@cisco.com>, IETF OOPSAWG <opsawg@ietf.org>
Thread-Topic: [OPSAWG] draft-ietf-opsawg-tacacs-06 ASCII
Thread-Index: AQHS0IzaXjAQTdEMlkK3vjl1WRHGuKK6ExyAgAA4PIA=
Date: Sun, 17 Sep 2017 12:47:45 +0000
Message-ID: <D5E446E1.2996B3%dcmgash@cisco.com>
References: <D53BBCC7.22ECC8%dcmgash@cisco.com> <61D9FC7A-6F10-44E6-8400-578C4FEE1988@deployingradius.com> <D53C62F4.22F82E%dcmgash@cisco.com> <E7D62944-46B9-4091-BF16-0AF8CA47626D@deployingradius.com> <fc8a1ff5-db6f-d463-8ff7-77ec03f1f25f@gmail.com> <006101d2cd9c$e8c0afe0$4001a8c0@gateway.2wire.net> <D53FAB1A.23396E%dcmgash@cisco.com> <010d01d2ce79$477ceda0$4001a8c0@gateway.2wire.net> <D5411107.2340EF%dcmgash@cisco.com> <632EB4D0-15C0-4BF7-9187-9AFCD7EDE306@ll.mit.edu> <D54116DA.23412A%dcmgash@cisco.com> <6B9DFA23-41BD-4896-B80C-EC0EAB51D5FD@deployingradius.com> <017f01d2d08c$7096de20$4001a8c0@gateway.2wire.net> <61BFF2A7-680E-433F-8D7E-E0F0B95A2DC6@deployingradius.com> <D544ECD9.2353FB%dcmgash@cisco.com> <5210a082-6c5d-c7fc-b55d-abe11689c090@cisco.com> <00cd01d2d271$9fce4ac0$4001a8c0@gateway.2wire.net> <D5E2F829.299361%dcmgash@cisco.com> <817F293D-33C9-4842-A394-70A46DE2B02C@deployingradius.com>
In-Reply-To: <817F293D-33C9-4842-A394-70A46DE2B02C@deployingradius.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.7.1.161129
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.229.136.18]
Content-Type: text/plain; charset="euc-kr"
Content-ID: <0A1014277CA61D4B8615A3336740143F@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/UuJr4ddMZVfwv3EbuPB-zxp3shc>
Subject: Re: [OPSAWG] draft-ietf-opsawg-tacacs-06 ASCII
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.22
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: Sun, 17 Sep 2017 12:47:54 -0000

Thanks Alan, will correct the nit.

I need to correct by previous ambiguity: By: 'without changing too much
the draft spec' I should have said: 'without changing too much the
protocol that was "defined" draft spec. The original draft spec text has
already been largely rewritten by the recent submissions.

Thanks,

Regards,

Doug.


On 17/09/2017 15:26, "Alan DeKok" <aland@deployingradius.com> wrote:

>On Sep 16, 2017, at 11:41 PM, Douglas Gash (dcmgash) <dcmgash@cisco.com>
>wrote:
>> 
>> We¹re preparing the next revision. Regarding attribute value encoding,
>> we¹re proposing to add the following, then to assign a type to each
>> attribute. As always with T+, the issue is getting the right balance in
>> adding some order without changing too much the draft spec.
>
>  The right balance is to document the protocol.
>
>  If documenting the spec means tossing the draft and starting from
>scratch, then so be it.
>
>> Proposed content is as below, please share any views:
>
>  It definitely seems better that the previous ad-hoc definitions.
>
>>   Boolean
>> 
>>   All boolean attributes are encoded with values "true" or "false".
>
>  Nit: encoded as US-ASCII strings with values...
>
>
>  Alan DeKok.
>