[OPSAWG] draft-ietf-opsawg-tacacs-?? overview of significant changes over the last year

Andrej Ota <andrej@ota.si> Wed, 18 April 2018 18:50 UTC

Return-Path: <andrej@ota.si>
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 6A3C91270FC for <opsawg@ietfa.amsl.com>; Wed, 18 Apr 2018 11:50:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.997
X-Spam-Level:
X-Spam-Status: No, score=-0.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RDNS_NONE=0.793, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral (1024-bit key) reason="invalid (public key: does not support hash algorithm 'sha256')" header.d=ota.si
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 Gs3pxUI7mvqc for <opsawg@ietfa.amsl.com>; Wed, 18 Apr 2018 11:50:27 -0700 (PDT)
Received: from mta2.toshio.eu (unknown [IPv6:2001:470:99f7::b423]) by ietfa.amsl.com (Postfix) with ESMTP id E2A141252BA for <opsawg@ietf.org>; Wed, 18 Apr 2018 11:50:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mta2.toshio.eu (Postfix) with ESMTP id 21C9516A8E; Wed, 18 Apr 2018 18:50:09 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ota.si; h= message-id:date:date:subject:subject:mime-version:content-type :content-type:from:from:received; s=toshio; t=1524077391; x= 1525891792; bh=GM9DqVrLcY09mEhbXWUcYKXIzIVc4+KWiQNojfYroMk=; b=U zht3qgObPHg+6i7HsHiFxppH5diaFbYtvR91cn2J3/B4kQX/rJXl0HRoSkgQzdhm Js70hgxfY+4KHTVaOppKZ5AqtSFsSGL35hhaeTJctKZMQKkgS7egbfgZ3twQcnXh Flhr3pdgtDODUPFP6Y9FkAEIgeXh1BMOoEC6yfXkg0=
X-Virus-Scanned: amavisd-new at toshio.org
Received: from mta2.toshio.eu ([212.18.48.35]) by localhost (srv-fe-3.dom.ota.si [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 7heRZUC6hAtW; Wed, 18 Apr 2018 18:49:51 +0000 (UTC)
From: Andrej Ota <andrej@ota.si>
Content-Type: multipart/alternative; boundary="Apple-Mail=_E8BA3845-B759-46E3-B94D-3BCCFDC0D107"
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Date: Wed, 18 Apr 2018 19:49:33 +0100
Cc: Douglas Gash <dcmgash@cisco.com>, Thorsten Dahm <thorstendlux@google.com>
To: opsawg@ietf.org
Message-Id: <20180418184951.0506116A73@mta2.toshio.eu>
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/obgmKEFQ1qOgngCoKmdZH7zGvbo>
Subject: [OPSAWG] draft-ietf-opsawg-tacacs-?? overview of significant changes over the last year
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: Wed, 18 Apr 2018 18:50:29 -0000

Hi Everyone,


TACACS+ draft had undergone a number of changes since revision -06 back in the February 2017 and we, the "collective of authors" have been less than satisfactory on keeping the WG updated. This is an attempt to start fixing the problem by going through changes, enumerating them and explaining the reason for each significant change.

A year's worth of changes is a round number and -06 was also the version where we misread Alan's intention and made the mistake of including his text verbatim.

I will skip the minor changes that deal with things like 's/Connect/Connection/' or updates to author's contact details. I will also be sending the overview over multiple e-mails, each dealing with a specific section of the draft, so nobody will have to read through a single huge tome if you only care or wonder about specific parts of the draft. I understand this is far from ideal, but the damage had been done and this split into smaller and more manageable chunks should go a long way towards getting changes reviewed and understood, one by one.

I do not wish to ignore the metaphorical elephant in the room. However, I wish to split technical and organizational conversations into their separate threads to avoid confusing the two. While I'll be describing changes in the "technical" conversation, I and the rest of the authors will continue listening and responding to Alan's organizational criticism, past and future, in what we believe is the most constructive way: improving in the areas where we were found wanting.


Andrej Ota.