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

"Douglas Gash (dcmgash)" <dcmgash@cisco.com> Mon, 15 May 2017 18:12 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 8FF3A127077; Mon, 15 May 2017 11:12:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level:
X-Spam-Status: No, score=-14.523 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_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-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 KInbq7EDVtDa; Mon, 15 May 2017 11:12:40 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 602DF1293FD; Mon, 15 May 2017 11:10:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3527; q=dns/txt; s=iport; t=1494871802; x=1496081402; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=AOcWuVQLkl7RC7AzYNJO6yxTvfHMVohzFpQJLGeRv4s=; b=HCtLEm3OsOfBjGy11Pd2CkfOhsl7JeBIsZfWr6bECnxaQhcVRKT4SwJN N0Dd66EhUl05G0TOTkV4kNwTsMyGfvjNj6zJj4hOYDBv2iSv4Z4ge6w9Y lEC4/Fiqy7kMiLzlX6Zoq7leUmRIRYnW9Sig35hoNxNEP8RKELxiQZMn9 Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CYAABt7hlZ/4kNJK1cGQEBAQEBAQEBAQEBBwEBAQEBg1VigQwHjXyRX4gmjU+CDyELhS5KAoU0PxgBAgEBAQEBAQFrKIUYAQEBAQMBAWwGBQwEAgEIFQECLiEGCyUCBAENBRmJcgMVDq8KhzENgzgBAQEBAQEBAQEBAQEBAQEBAQEBAQEYBYtYglSBcgEBG4VyBZBlhgqGYDsBjkeEU5Friy2JFQEfOIEKcBVGhHccgWN2hjGBIYENAQEB
X-IronPort-AV: E=Sophos;i="5.38,346,1491264000"; d="scan'208";a="248651427"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 15 May 2017 18:10:01 +0000
Received: from XCH-RCD-014.cisco.com (xch-rcd-014.cisco.com [173.37.102.24]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id v4FIA02k020488 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 15 May 2017 18:10:01 GMT
Received: from xch-aln-014.cisco.com (173.36.7.24) by XCH-RCD-014.cisco.com (173.37.102.24) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 15 May 2017 13:10:00 -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.1210.000; Mon, 15 May 2017 13:10:00 -0500
From: "Douglas Gash (dcmgash)" <dcmgash@cisco.com>
To: "t.petch" <ietfc@btconnect.com>, Alan DeKok <aland@deployingradius.com>, Ignas Bagdonas <ibagdona@gmail.com>
CC: "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>
Thread-Topic: [OPSAWG] draft-ietf-opsawg-tacacs-06 Contributions, Status and Plans
Thread-Index: AQHSy08ttZSP0sW41keg1j/jrc0SIqHxblMAgADBTACAA2Ki4oAAEfVNgAB2p4A=
Date: Mon, 15 May 2017 18:10:00 +0000
Message-ID: <D53FAB1A.23396E%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>
In-Reply-To: <006101d2cd9c$e8c0afe0$4001a8c0@gateway.2wire.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.7.0.161029
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.55.1.6]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <6BD655D6FDC6B44380542641A953DFC7@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/nUWr-o87JxUmQhgOYLiRNFuOX40>
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 18:12:42 -0000

The lack of interactivity was more our fault than any one else's, we took
Alan¹s comments and incorporated them into the version we uploaded in Feb.

What we should have done was collate Alan¹s comments to promote
discussion. We¹re attempting to rectify than that now:

1) We put Alan¹s comments on v5 put on a single mail list a few days ago
2) We are going to give an initial response ASAP (will take a few days)
3) More discussions will ensure, and other comments on the doc may be
generated
4) We will hopefully steer towards a consensus that will feed into v7.

Regards,

Doug.

On 15/05/2017 18:00, "t.petch" <ietfc@btconnect.com> wrote:

>----- Original Message -----
>From: "Ignas Bagdonas" <ibagdona@gmail.com>
>To: "Alan DeKok" <aland@deployingradius.com>
>Sent: Monday, May 15, 2017 5:00 PM
>
>> 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.
>
>Ignas
>
>I echo part of what Alan says, that for a WG document, the editors
>should reflect the consensus of the WG.  The problem I see is the lack
>of consensus, not with people disagreeing, but with an absence of people
>agreeing.
>
>Alan made a number of comments in October last year, Alexander made some
>in  November but I did not see much follow up from anyone else to either
>set of comments.
>
>Trouble is, do the editors incorporate comments that one person has made
>and noone else has agreed or disagreed with?  There is no good answer.
>
>In other WGs, I have seen ping-pong, one person comments, comments
>incorporated, someone else then disagrees, disagreements incorporated
>into a new revision, first person comes back, changes incorporated into
>a newer revision and so on, circling around a lack of consensus.
>Changing editors, unless it is to someone remote from the subject, is
>unlikely to change things..
>
>I did look at Alan's comments, agreed with some, disagreed with others,
>ditto Alexander's, but was disinclined to do more with noone else
>chipping in, especially as several more did chip in in the initial
>stages of should we adopt this, and what status should it be.
>
>How you stir people into life is a challenge for WG chairs.
>
>Tom Petch
>
>> Thank you.
>>
>> Ignas
>>
>>
>>
>> _______________________________________________
>> OPSAWG mailing list
>> OPSAWG@ietf.org
>> https://www.ietf.org/mailman/listinfo/opsawg
>