Re: [OPSAWG] draft-ietf-opsawg-tacacs-06 Contributions, Status and Plans

Ignas Bagdonas <ibagdona@gmail.com> Mon, 15 May 2017 16:04 UTC

Return-Path: <ibagdona@gmail.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 3C2B312009C; Mon, 15 May 2017 09:04:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Level:
X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 Z2VfiWVCEZOW; Mon, 15 May 2017 09:04:56 -0700 (PDT)
Received: from mail-wm0-x242.google.com (mail-wm0-x242.google.com [IPv6:2a00:1450:400c:c09::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C586E12960D; Mon, 15 May 2017 09:00:42 -0700 (PDT)
Received: by mail-wm0-x242.google.com with SMTP id y10so29568311wmh.0; Mon, 15 May 2017 09:00:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=BIvkChuRtGfbCwrnkWGOZQt/QrJgh4rBfodcD3PI5UU=; b=QE8RAevm1DqSkdJjiew4v2bEITYMul/0Rkxnt56Ku21sdtvmGiKW0P5Vn7ROyiSXNS DP14Efm/54lr3cXZ/2eaWHTDpa7t4T2rprdaPa4croYy17PXO03TmLqZ/bzzIWcY955n BbfiIsE0iBVFxp1MtKDG8wF+gPR7W84lMuUzqTX+HoYqmuXJ8XxM1sUBTvzniSD5ra+X +ocfdENAQB3W0U0H636uggG0MSQ0YUCcKSpQ2BSLelHFht0YX6kFwe2CUCTGcccgAGDX ti2L5oe6t9+/3L5qIkhqNzuMWIEH6BiGJIVXUAUC5nnXkQ373iALPo2DV4qwa6NRsS/W HzYA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=BIvkChuRtGfbCwrnkWGOZQt/QrJgh4rBfodcD3PI5UU=; b=txm65SsJj8+VD9m6urRLBoEtSXQn+MAgB8myB0V/5Lm88b0sADKK5Xkx1sIV9/AxR+ yY2AIHscLguFTqkY8PcF+5rLvVz7wF8oD8vyIGMfQyBDFFFnQnKNnjoNWHHaf75HXBkR AuszJclh6IOvwcguNmkf4sPzB3wpmZZuuLK/pQh5noyOoKR+Yzr+tLA7PUD7xca239lb /UPTCJy7fIQaQxnPj6RIRS8ZDn3Wq+2GCTv+GZZLht/CGEwb+vAqfNgL8Z6dOOpvg1rL NtVKjF74APE960DytJKcg/uPRWIhdYJJJly0gGxE0hwEidq5e9bJp6uvE1oUEqppBsae 9AHg==
X-Gm-Message-State: AODbwcDxk1nLumF8J8KFSfssR4xRIhmHUSuQQdFaLmQKD8fj5lb7rTQs TcPN7zLc2zQbtQ==
X-Received: by 10.223.168.97 with SMTP id l88mr4709407wrc.54.1494864041282; Mon, 15 May 2017 09:00:41 -0700 (PDT)
Received: from [192.168.191.250] ([80.69.10.100]) by smtp.gmail.com with ESMTPSA id 4sm16276176wry.31.2017.05.15.09.00.37 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 15 May 2017 09:00:39 -0700 (PDT)
To: Alan DeKok <aland@deployingradius.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>
Cc: "Douglas Gash (dcmgash)" <dcmgash@cisco.com>, "opsawg@ietf.org" <opsawg@ietf.org>, "draft-ietf-opsawg-tacacs@ietf.org" <draft-ietf-opsawg-tacacs@ietf.org>, "opsawg-chairs@ietf.org" <opsawg-chairs@ietf.org>, "ops-ads@ietf.org" <ops-ads@ietf.org>
From: Ignas Bagdonas <ibagdona@gmail.com>
Message-ID: <fc8a1ff5-db6f-d463-8ff7-77ec03f1f25f@gmail.com>
Date: Mon, 15 May 2017 17:00:36 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <E7D62944-46B9-4091-BF16-0AF8CA47626D@deployingradius.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/DAviHnpj5l_8MB5LOzx1P9lhQO8>
Subject: Re: [OPSAWG] draft-ietf-opsawg-tacacs-06 Contributions, Status and Plans
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: Mon, 15 May 2017 16:04:57 -0000

Hi Alan,


On 13/05/2017 12:59, Alan DeKok wrote:
> The approach in the IETF is to have authors move towards WG consensus. 
> i.e. to prove to to the WG that the draft is ready for publication.
>    If you're not going to work towards WG consensus, I suggest the chairs replace you with authors who will.
>

WG chairs can appoint or change authors if needed under the process 
described in RFC7221 and its referenced documents. The individual draft 
has been accepted as a WG one a while ago with no changes in author 
list. If current document authors would like to make any changes to 
author/co-author/editor list WG chairs will certainly approve those 
changes. Otherwise unless there is clear evidence that current authors 
cannot make progress with the document, WG chairs do not have intentions 
of changing the author list. This decision may be revisited if evidence 
of author/co-author/editor duties not being performed to the expected 
level surfaces, but at this time there is no such evidence. The process 
of progressing the document is slow, slower than it could have been, but 
it is not stalled.

Thank you.

Ignas