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

heasley <heas@shrubbery.net> Fri, 13 November 2015 18:44 UTC

Return-Path: <heas@shrubbery.net>
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 4BB7D1B2B3E for <opsawg@ietfa.amsl.com>; Fri, 13 Nov 2015 10:44:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.726
X-Spam-Level:
X-Spam-Status: No, score=-2.726 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FAKE_REPLY_C=1.486, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 fLFSVTbr6VfE for <opsawg@ietfa.amsl.com>; Fri, 13 Nov 2015 10:44:04 -0800 (PST)
Received: from guelah.shrubbery.net (guelah.shrubbery.net [198.58.5.1]) by ietfa.amsl.com (Postfix) with ESMTP id C35981B2B3B for <opsawg@ietf.org>; Fri, 13 Nov 2015 10:44:04 -0800 (PST)
Received: by guelah.shrubbery.net (Postfix, from userid 7053) id 718F41196E6; Fri, 13 Nov 2015 18:44:04 +0000 (UTC)
Date: Fri, 13 Nov 2015 18:44:04 +0000
From: heasley <heas@shrubbery.net>
To: opsawg@ietf.org
Message-ID: <20151113184404.GH81506@shrubbery.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAHw9_iKOM5N3-HS3ZOFFaDHYTV7rDaf3YHo-dEmdTU9-4W49aw@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/MVO-UF5j3tRghMrZR4ozdHprlyc>
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: Fri, 13 Nov 2015 18:44:06 -0000

> 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.

I have read this draft and support publication.

> 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