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

Tianran Zhou <zhoutianran@huawei.com> Wed, 17 May 2017 02:27 UTC

Return-Path: <zhoutianran@huawei.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 8B509129BE6; Tue, 16 May 2017 19:27:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.222
X-Spam-Level:
X-Spam-Status: No, score=-4.222 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 PjPs9lCGkHIb; Tue, 16 May 2017 19:27:57 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D8731286D6; Tue, 16 May 2017 19:24:16 -0700 (PDT)
Received: from 172.18.7.190 (EHLO LHREML710-CAH.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DGT32289; Wed, 17 May 2017 02:24:14 +0000 (GMT)
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by LHREML710-CAH.china.huawei.com (10.201.108.33) with Microsoft SMTP Server (TLS) id 14.3.301.0; Wed, 17 May 2017 03:24:13 +0100
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0235.001; Wed, 17 May 2017 10:24:07 +0800
From: Tianran Zhou <zhoutianran@huawei.com>
To: Alan DeKok <aland@deployingradius.com>, Ignas Bagdonas <ibagdona.ietf@gmail.com>
CC: "Douglas Gash (dcmgash)" <dcmgash@cisco.com>, "opsawg@ietf.org" <opsawg@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/jrc0SIqHwlGUAgACwjQCAAF79gIADaB0AgAFZTwCAADIWAIAADS4AgAEp2vA=
Date: Wed, 17 May 2017 02:24:06 +0000
Message-ID: <BBA82579FD347748BEADC4C445EA0F21A237F4EA@NKGEML515-MBX.china.huawei.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> <CC6784CA-0F0D-4ACB-93CF-C398DFB30101@deployingradius.com> <aecfa188-d7cb-3395-8c41-fb89d8838fc7@gmail.com> <DEE86F3C-EF38-4346-910B-6CD05D628BC6@deployingradius.com>
In-Reply-To: <DEE86F3C-EF38-4346-910B-6CD05D628BC6@deployingradius.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.156.116]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020201.591BB44F.0087, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 6044e24cf37685d5e22354ed573d0de6
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/O0h9BBmc887wU0wHRlNKGN0wpUs>
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: Wed, 17 May 2017 02:27:58 -0000

> -----Original Message-----
> From: OPSAWG [mailto:opsawg-bounces@ietf.org] On Behalf Of Alan DeKok
> Sent: Wednesday, May 17, 2017 12:23 AM
> To: Ignas Bagdonas
> Cc: Douglas Gash (dcmgash); opsawg@ietf.org; ops-ads@ietf.org
> Subject: Re: [OPSAWG] draft-ietf-opsawg-tacacs-06 Contributions, Status
> and Plans
> 
> On May 16, 2017, at 11:35 AM, Ignas Bagdonas <ibagdona.ietf@gmail.com> wrote:
> >
> >>    I don't see how reviews (which were ignored) can be construed as "no
> evidence" that the authors were ignoring reviews.
> >>
> >>   Which was my point.  If document authors issue new revs irrespective
> of what the WG suggests, the chairs should replace the authors with ones
> who work towards WG consensus.
> >
> > No-one has seen the -07 revision yet, therefore it seems to be too early
> to make judgement whether comments and suggestions were or were not addressed.
> Authors have promised to address the raised comments discussing them on
> the list and responding to previous reviews.
> 
>   My comments (again) were that there was a history of ignoring the reviews.
> At the time I made that comment, it was true.  I find it troubling to see
> a response saying there's "no evidence" of such a problem.
 
Hi Alan,

Your reviews are appreciated. Via diff, I saw many of your comments are reflected in the 06 version. 
But the authors should have discussed your comments in the mailing list and gotten consensus on the revision.
Now, they are back on the right track. See Doug's latest post.
Let's back to the I-D discussion. ;-)

Regards,
Tianran


> >>   The alternative is to accept a draft as a WG document, and then to allow
> the authors to do pretty much whatever they want, and then to rubber-stamp
> the final document as an RFC.
> >
> > That is not how the IETF works. I fail to see what else could be commented
> here.
> 
>   I'm saying until I complained, that *was* largely the process being used
> in this WG.
> 
>   Alan DeKok.
> 
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg