Re: Unhelpful draft names

<l.wood@surrey.ac.uk> Wed, 11 March 2015 10:00 UTC

Return-Path: <l.wood@surrey.ac.uk>
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 C2CE91AC43C for <ietf@ietfa.amsl.com>; Wed, 11 Mar 2015 03:00:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 SBzGcfj1QPJK for <ietf@ietfa.amsl.com>; Wed, 11 Mar 2015 03:00:14 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.141]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 797491ACC85 for <ietf@ietf.org>; Wed, 11 Mar 2015 03:00:14 -0700 (PDT)
Received: from [85.158.136.51] by server-5.bemta-5.messagelabs.com id 6E/22-29647-C2210055; Wed, 11 Mar 2015 10:00:12 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-14.tower-49.messagelabs.com!1426068012!24402409!1
X-Originating-IP: [131.227.200.43]
X-StarScan-Received:
X-StarScan-Version: 6.13.4; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 7305 invoked from network); 11 Mar 2015 10:00:12 -0000
Received: from exht022p.surrey.ac.uk (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-14.tower-49.messagelabs.com with AES128-SHA encrypted SMTP; 11 Mar 2015 10:00:12 -0000
Received: from EXHY022V.surrey.ac.uk (131.227.201.104) by EXHT022P.surrey.ac.uk (131.227.200.43) with Microsoft SMTP Server (TLS) id 8.3.342.0; Wed, 11 Mar 2015 10:00:12 +0000
Received: from emea01-am1-obe.outbound.protection.outlook.com (131.227.201.241) by EXHY022v.surrey.ac.uk (131.227.201.104) with Microsoft SMTP Server (TLS) id 14.3.224.2; Wed, 11 Mar 2015 10:00:11 +0000
Received: from DB4PR06MB457.eurprd06.prod.outlook.com (10.141.238.15) by DB4PR06MB459.eurprd06.prod.outlook.com (10.141.238.21) with Microsoft SMTP Server (TLS) id 15.1.106.15; Wed, 11 Mar 2015 09:59:59 +0000
Received: from DB4PR06MB457.eurprd06.prod.outlook.com ([10.141.238.15]) by DB4PR06MB457.eurprd06.prod.outlook.com ([10.141.238.15]) with mapi id 15.01.0106.007; Wed, 11 Mar 2015 09:59:59 +0000
From: l.wood@surrey.ac.uk
To: loa@pi.nu, abdussalambaryun@gmail.com
Subject: Re: Unhelpful draft names
Thread-Topic: Unhelpful draft names
Thread-Index: AQHQWqqvWPHTGRNXX0mYd4WlLzGSv50W+MYAgAACdwCAABM1zA==
Date: Wed, 11 Mar 2015 09:59:58 +0000
Message-ID: <1426067997724.21805@surrey.ac.uk>
References: <54FE0776.8070300@gmail.com> <CADnDZ8-P_am8p2vjYd7sLHLvjwTVts6V6pgC3XO7yxjST_FJsw@mail.gmail.com>, <5500019A.20803@pi.nu>
In-Reply-To: <5500019A.20803@pi.nu>
Accept-Language: en-AU, en-US
Content-Language: en-AU
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [49.181.195.37]
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DB4PR06MB459;
x-microsoft-antispam-prvs: <DB4PR06MB459DD002C56079EE195EA77AD190@DB4PR06MB459.eurprd06.prod.outlook.com>
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(6009001)(24454002)(252514010)(51704005)(377454003)(377424004)(87936001)(54356999)(77156002)(40100003)(122556002)(74482002)(77096005)(2656002)(66066001)(102836002)(36756003)(117636001)(86362001)(19580395003)(19580405001)(15975445007)(106116001)(2950100001)(15395725005)(2900100001)(46102003)(76176999)(1720100001)(50986999)(92566002)(15198665003); DIR:OUT; SFP:1102; SCL:1; SRVR:DB4PR06MB459; H:DB4PR06MB457.eurprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(5002009); SRVR:DB4PR06MB459; BCL:0; PCL:0; RULEID:; SRVR:DB4PR06MB459;
x-forefront-prvs: 0512CC5201
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Mar 2015 09:59:58.9886 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 6b902693-1074-40aa-9e21-d89446a2ebb5
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB4PR06MB459
X-OrganizationHeadersPreserved: DB4PR06MB459.eurprd06.prod.outlook.com
X-CrossPremisesHeadersFiltered: EXHY022v.surrey.ac.uk
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/IpZH_FDQ-qWuUmMgGKXL7qJjBYM>
Cc: ietf@ietf.org
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: Wed, 11 Mar 2015 10:00:20 -0000

> Who is the owner of the draft the individual or the IETF?

What part of

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

is unclear?

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf <ietf-bounces@ietf.org> on behalf of Loa Andersson <loa@pi.nu>
Sent: Wednesday, 11 March 2015 7:49 PM
To: Abdussalam Baryun
Cc: ietf@ietf.org
Subject: Re: Unhelpful draft names

AB

Certainly if you want to submit a draft into an IETF owned repository,
IETF certainly have some rights to tell what file-name that can be used!

/Loa

On 2015-03-11 16:40, Abdussalam Baryun wrote:
> Who is the owner of the draft the individual or the IETF? IMHO only the
> owner has the right to make the name. The name may not be helpful to
> IETF but is may be helpful for the owner. IMHO the problem of
> unhelpfulness is because individual draft input should be distinguished
> per IETF Area and not per draft-name.
>
> So I suggest the IETF to fix the submission to ask the participant to
> submit per Area and choose any name.
>
> AB
>
> On Monday, March 9, 2015, Brian E Carpenter <brian.e.carpenter@gmail.com
> <mailto:brian.e.carpenter@gmail.com>> wrote:
>
>     Hi,
>
>     It's one of those three days in the year when we get hundreds of
>     drafts announced
>     in succession, which makes the job of deciding which drafts a person
>     needs to
>     read harder than ever.
>
>     I have no idea what draft-xmss-00.txt is about and have no plans to find
>     out. But it seems to me that we have a fairly strong convention that
>     non-WG drafts should be named something like
>       draft-<author>-<generalTopic>-<specificTopic>
>     where the generalTopic is often a WG name, if there is a relevant WG.
>
>     Now I realise we don't want to be too rigid, e.g. the author component
>     is sometimes ymbk or farresnickel, but should we have a bit more
>     enforcement
>     in the tools, at least such that draft-oneWord-00 would not be
>     acceptable?
>
>         Brian
>

--


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64