Re: Status of <draft-ietf-6man-default-iids-16.txt> in AUTH48

Fernando Gont <fgont@si6networks.com> Mon, 13 February 2017 04:11 UTC

Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA54B129596 for <ipv6@ietfa.amsl.com>; Sun, 12 Feb 2017 20:11:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=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 oABr57xRR_lu for <ipv6@ietfa.amsl.com>; Sun, 12 Feb 2017 20:11:27 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1763D12953A for <ipv6@ietf.org>; Sun, 12 Feb 2017 20:11:25 -0800 (PST)
Received: from [IPv6:2001:1291:200:42e::2] (cl-1071.udi-01.br.sixxs.net [IPv6:2001:1291:200:42e::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 298C280C5E; Mon, 13 Feb 2017 05:11:18 +0100 (CET)
Subject: Re: Status of <draft-ietf-6man-default-iids-16.txt> in AUTH48
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
References: <C9FDAEB9-9F79-4186-9C48-5F44E5E07235@gmail.com> <1be095d0-8165-b127-9dbb-5a9d06d7d141@gmail.com> <3F1A2F45-CD1D-4E66-85E7-CC331A78A160@employees.org> <5ff7c3e2-c450-ded4-d68b-e73d0b416364@gmail.com> <95381DDF-9261-4EC9-9626-DB6F9F494729@employees.org> <b886b05d-4c52-5b26-6295-f5a9251175b2@si6networks.com> <E44F0815-B800-4D09-93AE-D38B8480C220@ericsson.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <841e405d-0b03-98f6-d5eb-a9c802af5c08@si6networks.com>
Date: Mon, 13 Feb 2017 01:10:31 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <E44F0815-B800-4D09-93AE-D38B8480C220@ericsson.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/PfeClnayqxq2IiYMKV7WyUAvBfY>
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 04:11:30 -0000

On 02/12/2017 11:53 PM, Suresh Krishnan wrote:
>> 
>> In many (if not most/all) of these cases, the acks were added
>> during AUTH48, when I just got the time to think about the people
>> that had provided significative help/support.
>> 
>> It never crossed my mind that someone could have concerns with
>> this. As a guy that reads RFCs, I couldn't care less about the
>> Acks.
> 
> Either you care or you don’t. You cannot have it both ways. If you do
> not care about the Acks, I am not sure we are having this discussion
> and taking a chunk of everyone’s time.

What I meant is that, when reading an RFC, I don't care about what's in
the Acks. As an author, I try to give credit where I think is deserved.

In this particular case, my impression was that the decision to not
approve the document with the Acks was arbitrary. It was an editorial
change or, as Brian said, just "cosmetics". Given that there does not
seem to be any rules for writing Acknowledgements, and that the change
was editorial, I was puzzled for the author approval of an RFC to be
delayed for that. To be honest, it wasn't even clear to me what the
objection was. That's why I took your option of consulting the wg (if
you let go arbitrary decisions, you don't know where that stops).

Based on this discussion, the lesson that I've learned is that, during
AUTH48, an Acknowledgement cannot be added, unless all authors agree (or
not even, I guess). I'll make sure to put more energy on the
Acknowledgments of documents at an earlier stage next time, so that, if
anything, this discussion happens at such an earlier stage.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492