Re: [OPSAWG] FW: New Version Notification for draft-dahm-opsawg-tacacs-01.txt

Joe Clarke <jclarke@cisco.com> Mon, 16 November 2015 19:48 UTC

Return-Path: <jclarke@cisco.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 710E61A88B4 for <opsawg@ietfa.amsl.com>; Mon, 16 Nov 2015 11:48:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.086
X-Spam-Level:
X-Spam-Status: No, score=-15.086 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, RP_MATCHES_RCVD=-0.585, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 43Vg50dohUlz for <opsawg@ietfa.amsl.com>; Mon, 16 Nov 2015 11:48:55 -0800 (PST)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 090681A88CE for <opsawg@ietf.org>; Mon, 16 Nov 2015 11:48:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2751; q=dns/txt; s=iport; t=1447703315; x=1448912915; h=subject:to:references:from:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=qXrVjuHbQnw6/pYCCM/KR6XM9ztOR4mVv1Sq2pkbvqQ=; b=LR+EWcJaVUJxFJrMF//4j4/JQtG3c4whLPhoDvr/spN5vzdyuECIXomf pEynmEwPWAMF/EJKoCETtJbAidjFs0rkmOtIMESN1eX5ScuWS+TerKMak 7c89ke6ph8zAaC9ig+Ee+zagHFDsJZ4cQkKjxXsLYV/j9am3+8kRaak5h Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AWAgBFMkpW/4ENJK1dgztTb7xGghoBDYFlIYVvAoFHOBQBAQEBAQEBgQqENAEBAQMBOD8BEQsYCRYPCQMCAQIBPAkGAQwGAgEBiCIIDbsfAQEBAQEBAQEBAQEBAQEBAQEBARqGVIR+iTkBBI0bdog3hR2ICoFbSYN3gwIjjxODch8BAUKEIiA0AYUJAQEB
X-IronPort-AV: E=Sophos;i="5.20,304,1444694400"; d="scan'208";a="208947567"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 16 Nov 2015 19:48:35 +0000
Received: from [10.117.46.173] (rtp-jclarke-89112.cisco.com [10.117.46.173]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id tAGJmYhg005744; Mon, 16 Nov 2015 19:48:35 GMT
To: Warren Kumari <warren@kumari.net>, "opsawg@ietf.org" <opsawg@ietf.org>
References: <20151002152505.26594.74925.idtracker@ietfa.amsl.com> <D237455F.BC00F%dcmgash@cisco.com> <CAHw9_iKOM5N3-HS3ZOFFaDHYTV7rDaf3YHo-dEmdTU9-4W49aw@mail.gmail.com>
From: Joe Clarke <jclarke@cisco.com>
Organization: Cisco Systems, Inc.
Message-ID: <564A3312.4030103@cisco.com>
Date: Mon, 16 Nov 2015 14:48:34 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <CAHw9_iKOM5N3-HS3ZOFFaDHYTV7rDaf3YHo-dEmdTU9-4W49aw@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/ieYRV0FVoAfQNtFj-mwPUVx8l7c>
Subject: Re: [OPSAWG] FW: New Version Notification for draft-dahm-opsawg-tacacs-01.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
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, 16 Nov 2015 19:48:56 -0000

On 11/13/15 13:37, Warren Kumari wrote:
> We would really appreciate any feedback on this document. Personally I
> think it is really useful, but we need the WG to review and provide
> feedback.
>
> Over the years I've heard a number of people kvetch that TACACS+ isn't
> documented -- well, now you can, you know, actually do something about
> this...

I may be biased, but I have read the doc, and I support the WG working 
on it.  I agree with your last sentiment that this would be good to 
final document this with industry consensus.

One thing I wonder is if there shouldn't be some version change for the 
support of TLS, or if the Type of 0x00 is enough?

Joe

>
> W
>
> On Sun, Oct 4, 2015 at 4:18 PM, Douglas Gash (dcmgash)
> <dcmgash@cisco.com> wrote:
>> Dear Opsawg List,
>>
>> We have uploaded a second revision of the TACACS+ protocol specification
>> which we believe is ready for publication subject subject to port
>> allocation.
>>
>> Please see details below.
>>
>> The essential difference from the first revision is the change of TLS
>> option support using a separate port as opposed to the original Start TLS
>> mechanism.
>>
>> We would be very grateful for the opinion of the list regarding the
>> suitability of document for publication as an RFC.
>>
>> Many thanks,
>>
>> Thorsten, Andrej, Doug.
>>
>>
>> On 02/10/2015 16:25, "internet-drafts@ietf.org" <internet-drafts@ietf.org>
>> wrote:
>>
>>>
>>> A new version of I-D, draft-dahm-opsawg-tacacs-01.txt
>>> has been successfully submitted by Douglas C. Medway Gash and posted to
>>> the
>>> IETF repository.
>>>
>>> Name:          draft-dahm-opsawg-tacacs
>>> Revision:      01
>>> Title:         The TACACS+ Protocol
>>> Document date: 2015-10-02
>>> Group:         Individual Submission
>>> Pages:         38
>>> URL:
>>> https://www.ietf.org/internet-drafts/draft-dahm-opsawg-tacacs-01.txt
>>> Status:         https://datatracker.ietf.org/doc/draft-dahm-opsawg-tacacs/
>>> Htmlized:       https://tools.ietf.org/html/draft-dahm-opsawg-tacacs-01
>>> Diff:
>>> https://www.ietf.org/rfcdiff?url2=draft-dahm-opsawg-tacacs-01
>>>
>>> Abstract:
>>>    TACACS+ provides access control for routers, network access servers
>>>    and other networked computing devices via one or more centralized
>>>    servers.  TACACS+ provides separate authentication, authorization and
>>>    accounting services.  This document describes the protocol that is
>>>    used by TACACS+.
>>>
>>>
>>>
>>>
>>>
>>> Please note that it may take a couple of minutes from the time of
>>> submission
>>> until the htmlized version and diff are available at tools.ietf.org.
>>>
>>> The IETF Secretariat
>>>
>>
>
>
>