Be professional and respectful (was Re: Status of <draft-ietf-6man-default-iids-16.txt> in AUTH48)

Suresh Krishnan <> Mon, 13 February 2017 01:31 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id BF16D12954B for <>; Sun, 12 Feb 2017 17:31:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id tuT7phdy0rQ8 for <>; Sun, 12 Feb 2017 17:31:09 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id DF71B129507 for <>; Sun, 12 Feb 2017 17:31:08 -0800 (PST)
X-AuditID: c618062d-d73ff700000009d8-a0-58a11c42daec
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id 7F.38.02520.24C11A85; Mon, 13 Feb 2017 03:39:00 +0100 (CET)
Received: from ([]) by ([]) with mapi id 14.03.0319.002; Sun, 12 Feb 2017 20:31:05 -0500
From: Suresh Krishnan <>
To: Fernando Gont <>
Subject: Be professional and respectful (was Re: Status of <draft-ietf-6man-default-iids-16.txt> in AUTH48)
Thread-Topic: Be professional and respectful (was Re: Status of <draft-ietf-6man-default-iids-16.txt> in AUTH48)
Thread-Index: AQHShZjXcOYqhBWyhkm6LDhKEgsQOg==
Date: Mon, 13 Feb 2017 01:31:04 +0000
Message-ID: <>
References: <> <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
x-originating-ip: []
Content-Type: multipart/signed; boundary="Apple-Mail=_CC1E9E93-CF6B-4D8C-89B4-5CF1F0289450"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrIIsWRmVeSWpSXmKPExsUyuXRPlK6LzMIIg+6/hhZtF/cxWTxZ9YbN 4uXZ90wWk9tWsDmweBw89pHRY+esu+weS5b8ZPL4cKiHPYAlissmJTUnsyy1SN8ugSvj9Ntv 7AWdoRXPvhU3MB727mLk5JAQMJHoP7mCqYuRi0NIYD2jxMVNfewQznJGiV8rWxlBqtiAqjbs /MwEYosIaErMfX4EyObgYBYokJj5UAHEFBbIlWjaGAdiiggUSbz4zwdh6kksPp8H0scioCrx 5s4iFhCbV8Be4uGfPywQi04ySXTsucgOkuAUcJZY1tcLZjMKiEl8P7UGbCmzgLjErSfzmSBO FpF4ePE0G4QtKvHy8T9WCFtJ4uPv+WDXMwtMYZSYsaSXEWKboMTJmU9YJjCKzEIyaxayullI 6iCKtCWWLXzNPAvsSx2JyQsZIcKmEq+PfoSyrSVm/DrIBmErSkzpfsi+gJFjFSNHaXFBTm66 kcEmRmDkHZNg093BeH+65yFGAQ5GJR7eDRsWRAixJpYVV+YeYlQBan20YfUFRimWvPy8VCUR 3vvcCyOEeFMSK6tSi/Lji0pzUosPMUpzsCiJ88atvh8uJJCeWJKanZpakFoEk2Xi4JRqYKzf 9sz5+eHk0t9vPd+1NDBxCc/5+DtQ6tHstQ9CJtpv0YrSXnpwLkuQUmKf7QGxh01WOrNEN3Af 5Lu9WNek5JtsoVds9dyznWLikbp5dgUODIfnv/td2zJR5pW9nJLUjtiArx0OeS+89mpfCk36 YfXgsGpAUfv6VYd1bu+/t8dSf/f1Du8PN5RYijMSDbWYi4oTAcmPMaDEAgAA
Archived-At: <>
Cc: 6man WG <>
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 13 Feb 2017 01:31:11 -0000

Hi Fernando,
  This was a chance for the other members of the WG (and not the authors) to comment on the change, since the authors could not agree. Several of your comments you made in this thread have been over the line and disrespectful. Please keep the discussion professional, respectful and to the point.


> On Feb 12, 2017, at 6:36 PM, Fernando Gont <> wrote:
> On 02/12/2017 07:21 PM, wrote:
>> The main concern here is the change during AUTH48, more than the
>> exact change. Why the author chose to add this and has done with many
>> documents at this point in the process is unknown to me. 
> I can comment on this one:
> Typically, documents take too much energy, and I don't take care too
> much care about details, because documents change all the time. When it
> comes to Acknowledgements, the only "acks" that I typically keep up to
> date are those regarding folks that sent comments (because otherwise I
> forget and then it's a pain to remember or look up their names).
> In AUTH48, it's the last chance to read the document, and I do a full
> re-read -- at times, it has been a long time since doing a full
> review... so for example I get to catch errors or editorial nits that
> have been there for a long time -- and that I just didn't find before
> because I was just doing patches to the document, rather than full reviews.
> When a document is just about to be done, I also think of the people
> that provided help beyond the usual reviews, or implementations of the
> document that really made a difference, etc.
> e.g., in RFC6274 you can find:
> --- cut here ---
>   The author wishes to thank Alfred Hoenes for providing very thorough
>   reviews of earlier versions of this document, thus leading to
>   numerous improvements.
> [..]
>   The author would like to thank Randall Atkinson and Roque Gagliano,
>   who generously answered a number of questions.
> --- cut here ---
> (besides the credits for the usual reviews).
> in RFC7872, you can find:
> ---- cut here ----
>   The authors would like to thank Fred Baker for his guidance in
>   improving this document.
>   Fernando Gont would like to thank Jan Zorz of Go6 Lab
>   <> and Jared Mauch of NTT America for providing
>   access to systems and networks that were employed to produce some of
>   the measurement results presented in this document.  Additionally, he
>   would like to thank SixXS <> for providing IPv6
>   connectivity.
> ---- cut here ----
> in RFC7217 you can find:
> ---- cut here ----
>   The algorithm specified in this document has been inspired by Steven
>   Bellovin's work ([RFC1948]) in the area of TCP sequence numbers.
> [...]
>   Hannes Frederic Sowa produced a reference implementation of this
>   specification for the Linux kernel.
> ---- cut here ----
> 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.. could never
> have "concerns". So the stage at which these were added was never a
> factor -- i.e., not that I thought "oh, let's add these now so that
> nobody figures".
> My understanding is that the Acks are editorial changes, and not
> technical changes, so there was not even a need for the authors to agree
> on them.
>> This seems
>> to me to be in conflict with the working group's document ownership
>> and change control. (Of course you can argue that's also problematic
>> when the IESG edits documents without the working group's involvement
>> as well.)
> Not just IESG.
> It's quite usual for the RFC Editor to apply *lots* of changes on the
> technical content of the document, which at times change the technical
> meaning of the document.
> Me, I can't believe that someone can object a sentence that says "Gont
> would like to thank X for their love and support". -- I even asked if
> removing the word "love" would get Alissa's approval, and the answer was
> "no". I will obviously respect whatever decision is taken. But that
> doesn't make the topic or the objection to the text less ridiculous.
> Thanks,
> -- 
> Fernando Gont
> SI6 Networks
> e-mail:
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> Administrative Requests:
> --------------------------------------------------------------------