Re: [Marnew] Co-authoring
"Joe Hildebrand (jhildebr)" <jhildebr@cisco.com> Thu, 18 June 2015 07:23 UTC
Return-Path: <jhildebr@cisco.com>
X-Original-To: marnew@ietfa.amsl.com
Delivered-To: marnew@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id 2E2AF1A017E
for <marnew@ietfa.amsl.com>; Thu, 18 Jun 2015 00:23:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, 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 Gi0uUW7UmZZo for <marnew@ietfa.amsl.com>;
Thu, 18 Jun 2015 00:23:02 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80])
(using TLSv1 with cipher RC4-SHA (128/128 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 8F0A51A014D
for <marnew@iab.org>; Thu, 18 Jun 2015 00:23:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;
d=cisco.com; i=@cisco.com; l=4893; q=dns/txt; s=iport;
t=1434612182; x=1435821782;
h=from:to:cc:subject:date:message-id:references:
in-reply-to:mime-version;
bh=lRjR1bq2edTUIOja0caYdzvBaZQZf7i5So174Pd88yI=;
b=kdBw1B+SjsqKPyIwZlnKr7Y1+hj4hYPMtPxskGa9RK44u04ag67mwmuB
9yQSxMJmTpZHYROgh8uV0m9UbGAKCPV3ykNYoOpt0imMor9Gy0u+RtV9D
aIE117ydSC0mmg7eBafAo3RvPMy7VGfDzuWlzkVFqDy0c52Q/5p/W72ft w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BPBQD3cIJV/4YNJK1cgkVLVF+9CoJKAQmFLkoCgTM8EAEBAQEBAQGBCoQjAQEEAQEBKkELEAIBCD8HJwsUEQIEDgWILw3FCQEBAQEBAQEBAQEBAQEBAQEBAQEBARMEikOBAoUCBAeDF4EUBZNwAYtIgTWTFYNbJoN5b4JIAQEB
X-IronPort-AV: E=Sophos;i="5.13,638,1427760000"; d="scan'208,217";a="2612245"
Received: from alln-core-12.cisco.com ([173.36.13.134])
by rcdn-iport-9.cisco.com with ESMTP; 18 Jun 2015 07:22:58 +0000
Received: from xhc-aln-x07.cisco.com (xhc-aln-x07.cisco.com [173.36.12.81])
by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id t5I7Mw3G018505
(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL);
Thu, 18 Jun 2015 07:22:58 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.123]) by
xhc-aln-x07.cisco.com ([173.36.12.81]) with mapi id 14.03.0195.001; Thu, 18
Jun 2015 02:22:58 -0500
From: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
To: "MAISONNEUVE, JULIEN (JULIEN)" <julien.maisonneuve@alcatel-lucent.com>
Thread-Topic: [Marnew] Co-authoring
Thread-Index: AQHQqZeackIMiG3eSEid76r/LuQxhg==
Date: Thu, 18 Jun 2015 07:22:58 +0000
Message-ID: <1BA830C8-1F8E-410E-BE5A-8565BED3955C@cisco.com>
References: <93A9AFC57E50B34199A715A1CA9E0EEC02644FF2@FR712WXCHMBA12.zeu.alcatel-lucent.com>
In-Reply-To: <93A9AFC57E50B34199A715A1CA9E0EEC02644FF2@FR712WXCHMBA12.zeu.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative;
boundary="_000_1BA830C81F8E410EBE5A8565BED3955Cciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/marnew/aoCDkyG0L9fQHPuDpfgJ5ACrJh0>
Cc: "marnew@iab.org" <marnew@iab.org>
Subject: Re: [Marnew] Co-authoring
X-BeenThere: marnew@iab.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Managing Radio Networks in an Encrypted World <marnew.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/marnew>,
<mailto:marnew-request@iab.org?subject=unsubscribe>
List-Archive: <http://www.iab.org/mail-archive/web/marnew/>
List-Post: <mailto:marnew@iab.org>
List-Help: <mailto:marnew-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/marnew>,
<mailto:marnew-request@iab.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Jun 2015 07:23:04 -0000
In the past, I think we have allowed co-authoring, but have basically made it so that your submission had to be #coauthors*(median submission quality) or better to be accepted, or we have asked the team to pick a delegate. You also would stand the risk of none of the co-authors being invited where a single author might have been. Mobile/terse. DYAC. On Jun 18, 2015, at 8:29 AM, MAISONNEUVE, JULIEN (JULIEN) <julien.maisonneuve@alcatel-lucent.com<mailto:julien.maisonneuve@alcatel-lucent.com>> wrote: Sorry to add another process question : is co-authoring OK for position papers ? Would it guarantee attendance to the workshop ? My concern here is to maximize technical input to the workshop. No co-authoring means you have to put all your weight on a minimal number of contributions to get a seat at the table, not to advance cooperative technical contributions. Best regards, Julien Maisonneuve, PhD Alcatel Lucent Corporate Standardisation, Corporate CTO Office _______________________________________________ Marnew mailing list Marnew@iab.org<mailto:Marnew@iab.org> https://www.iab.org/mailman/listinfo/marnew
- [Marnew] Co-authoring MAISONNEUVE, JULIEN (JULIEN)
- Re: [Marnew] Co-authoring Joe Hildebrand (jhildebr)