Re: IESG Statement on surprised authors
"Larry Kreeger (kreeger)" <kreeger@cisco.com> Mon, 01 June 2015 23:21 UTC
Return-Path: <kreeger@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFEFD1A1B4E for <ietf@ietfa.amsl.com>; Mon, 1 Jun 2015 16:21:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 rbXA__byj1GK for <ietf@ietfa.amsl.com>; Mon, 1 Jun 2015 16:21:20 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 55D281A1B0C for <ietf@ietf.org>; Mon, 1 Jun 2015 16:21:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2617; q=dns/txt; s=iport; t=1433200880; x=1434410480; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=uWVsly2+osFkBs1VZjsLem4M8X13ueMPpvhsS/OULiM=; b=CifA4oRTUjpa8fbH1+pkHFocf5oqBQkRZ96BBBzPHgLEWRBovakSg61T CiCBtVUZFhyGrLOH7wekMqmt6KghYBx/4rsPs73TcvlGK6dD1qNzmr+kT S38lj+eECD/eXdoB0yR/MCKCvVRbxVLOKQoHE9An0tUlYyuW7Cpe5PGmk o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AOBQBv6GxV/40NJK1cgxBUXgbAOYV3AoE5TAEBAQEBAYELhCMBAQQ6TwIBCBgeECERJQIEExSIBAMSDdM8DYUbAQEBAQEBAQMBAQEBAQEBARqLQ4JNgkCELQWTEIQ2hQSBXIErPoM1ijhdgyyDWSNhgxdvAYFFgQEBAQE
X-IronPort-AV: E=Sophos;i="5.13,535,1427760000"; d="scan'208";a="16625490"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by rcdn-iport-8.cisco.com with ESMTP; 01 Jun 2015 23:21:19 +0000
Received: from xhc-rcd-x02.cisco.com (xhc-rcd-x02.cisco.com [173.37.183.76]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id t51NLJ3S005371 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <ietf@ietf.org>; Mon, 1 Jun 2015 23:21:19 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.61]) by xhc-rcd-x02.cisco.com ([173.37.183.76]) with mapi id 14.03.0195.001; Mon, 1 Jun 2015 18:21:19 -0500
From: "Larry Kreeger (kreeger)" <kreeger@cisco.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: IESG Statement on surprised authors
Thread-Topic: IESG Statement on surprised authors
Thread-Index: AQHQmlHrteXwgLU5d0ylk2ZEyn/PgJ2TYbKAgAN3MwCAAVRYAA==
Date: Mon, 01 Jun 2015 23:21:18 +0000
Message-ID: <D1923685.1498B2%kreeger@cisco.com>
References: <20150529205551.22495.73800.idtracker@ietfa.amsl.com> <D18E2F33.14965E%kreeger@cisco.com> <556B6910.1080805@gmail.com>
In-Reply-To: <556B6910.1080805@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.9.150325
x-originating-ip: [10.155.166.41]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <E87D4BBFAF81524497DAE5310CD9914E@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/-Vd30xk2c0r8AJ7PpVS4haYIc0U>
X-Mailman-Approved-At: Tue, 02 Jun 2015 08:03:00 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Jun 2015 23:21:22 -0000
Hi Brian, I agree that there will always be exceptions (we have them now), that will need to be handled manually, but I don't think that is a reason not to try to handle 80% of the cases. On your question about withdrawal, no I don't see why other authors should have any say in whether an author withdraws or not. It this somehow related to the "right to be forgotten" law? :-) - Larry On 5/31/15 1:03 PM, "Brian E Carpenter" <brian.e.carpenter@gmail.com> wrote: >Larry, > >The tools could do pretty much whatever we want, if we know what we >want, which is the tricky bit. But (as my draft points out) there >will always be exceptions, so the tools have to allow for them too. > >Here's one that isn't even in my draft. Sometimes an author wants to >withdraw. Does that need approval from the co-authors? > >Regards > Brian > >On 30/05/2015 10:07, Larry Kreeger (kreeger) wrote: >> Hi Brian and Benoit, >> >> If authors are added purposefully to a draft without their consent, it >>is >> indeed disturbing, but I hate to see IETF cycles spent dealing with >> investigations if they can be avoided in an automated manner. >> >> Isn't one way to deal with this to build additional mechanisms into the >> draft submittal confirmation procedure? I believe that currently, only >> one of the author's needs to approve submission/update. If this were >> changed to require all authors to confirm the original submission, then >>it >> would save people-hours investigating and dealing with this. When >> submitting an updated draft, only a single author would need to approve >>if >> the author list didn't change. Of course, newly added authors would >>need >> to approve as well if the updated draft included a new author. >> >> Thanks, Larry >> >> On 5/29/15 1:55 PM, "IESG Secretary" <iesg-secretary@ietf.org> wrote: >> >>> IETF community, >>> >>> The IESG is planning to publish an IESG statement concerning the >>> authorship of Internet drafts. This statement is only focused on the >>> situation where an IETF participant feels he/she has been erroneously >>> listed as an author on a draft. The statement can be seen here: >>> >>> http://trac.tools.ietf.org/group/iesg/trac/wiki/SurprisedAuthors >>> >>> We are seeking community feedback on this statement and welcome input >>> that will help encourage proper behavior. Please provide any feedback >>> by June 10, 2015 to either ietf@ietf.org or the IESG directly at >>> iesg@ietf.org. >>> >>> Regards, >>> Brian and Benoit (on behalf of the IESG) >>> >> >>
- Re: IESG Statement on surprised authors Toerless Eckert
- Re: IESG Statement on surprised authors John C Klensin
- Re: IESG Statement on surprised authors Jari Arkko
- Re: IESG Statement on surprised authors joel jaeggli
- Re: IESG Statement on surprised authors Brian E Carpenter
- Re: IESG Statement on surprised authors John C Klensin
- Re: IESG Statement on surprised authors Eliot Lear
- Re: IESG Statement on surprised authors Benoit Claise
- Re: IESG Statement on surprised authors Carsten Bormann
- Re: IESG Statement on surprised authors Spencer Dawkins at IETF
- Re: IESG Statement on surprised authors John C Klensin
- Re: IESG Statement on surprised authors Benoit Claise
- Re: IESG Statement on surprised authors John C Klensin
- Re: IESG Statement on surprised authors Harald Alvestrand
- Re: IESG Statement on surprised authors David Farmer
- Re: IESG Statement on surprised authors John C Klensin
- Re: IESG Statement on surprised authors Brian E Carpenter
- Re: IESG Statement on surprised authors Spencer Dawkins at IETF
- Re: IESG Statement on surprised authors John C Klensin
- Re: IESG Statement on surprised authors Eliot Lear
- Re: IESG Statement on surprised authors Eliot Lear
- Re: IESG Statement on surprised authors Harald Alvestrand
- Re: IESG Statement on surprised authors Larry Kreeger (kreeger)
- Re: IESG Statement on surprised authors Alexandru Petrescu
- Re: IESG Statement on surprised authors Eliot Lear
- Re: IESG Statement on surprised authors John C Klensin
- Re: IESG Statement on surprised authors John C Klensin
- Re: IESG Statement on surprised authors John Levine
- Re: IESG Statement on surprised authors Melinda Shore
- Re: IESG Statement on surprised authors Melinda Shore
- Re: IESG Statement on surprised authors John C Klensin
- Re: IESG Statement on surprised authors Spencer Dawkins at IETF
- Re: IESG Statement on surprised authors Randy Bush
- Re: IESG Statement on surprised authors Spencer Dawkins at IETF
- Re: IESG Statement on surprised authors Brian E Carpenter
- Re: IESG Statement on surprised authors John Levine
- Re: IESG Statement on surprised authors Ted Lemon
- Re: IESG Statement on surprised authors John R Levine
- Re: IESG Statement on surprised authors S Moonesamy
- Re: IESG Statement on surprised authors Larry Kreeger (kreeger)
- Re: IESG Statement on surprised authors Larry Kreeger (kreeger)
- Re: IESG Statement on surprised authors Larry Kreeger (kreeger)
- Re: IESG Statement on surprised authors Larry Kreeger (kreeger)
- Re: IESG Statement on surprised authors Joe Abley
- RE: IESG Statement on surprised authors Tony Hain
- Re: IESG Statement on surprised authors Ted Lemon
- Re: IESG Statement on surprised authors John Levine
- RE: IESG Statement on surprised authors Tony Hain
- Re: IESG Statement on surprised authors Warren Kumari
- Re: IESG Statement on surprised authors Ted Lemon
- Re: IESG Statement on surprised authors Warren Kumari
- Re: IESG Statement on surprised authors Stewart Bryant
- Re: IESG Statement on surprised authors Loa Andersson
- Re: proposed surprise hack, was IESG Statement on… John Levine
- Re: proposed surprise hack, was IESG Statement on… Ted Lemon
- Re: proposed surprise hack, was IESG Statement on… Warren Kumari
- Re: proposed surprise hack, was IESG Statement on… John R Levine