Re: [v6ops] IETF 92 heads Up

"Fred Baker (fred)" <fred@cisco.com> Thu, 05 February 2015 19:29 UTC

Return-Path: <fred@cisco.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55FA31A8A8F for <v6ops@ietfa.amsl.com>; Thu, 5 Feb 2015 11:29:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.511
X-Spam-Level:
X-Spam-Status: No, score=-114.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, USER_IN_WHITELIST=-100] 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 0TAW57lNskK6 for <v6ops@ietfa.amsl.com>; Thu, 5 Feb 2015 11:29:16 -0800 (PST)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 230A81A8A97 for <v6ops@ietf.org>; Thu, 5 Feb 2015 11:29:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4098; q=dns/txt; s=iport; t=1423164552; x=1424374152; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=wiYv55DFHwgfmhvRni79/qU80newG/1FF/jjzIiA464=; b=WtFtdZJ1cdGge/A6j3QMvueW3leh8kKCOYweGt5pRmP0+QBqMYl4dsxL Rn3i9QF6w8H43BI4JeSMyBeNKXZu6dZNx8B2M0XfFP2S1c0Dex7SRaBxp RlMHJqO6ffZJIYvor/XjtFtmMV4hjgCJLIMeCv04Y9P+lWzNB2Uw0HhfA Q=;
X-Files: signature.asc : 487
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0A4BQBMxNNU/4YNJK1agwZSWQSCfb9QhW8CgShDAQEBAQF9hAwBAQEDASNEEgULAgEIGCoCAjIlAgQOBQkFiBcIDcBDli0BAQEBAQEBAQEBAQEBAQEBAQEBAQEXj3gHgmgugRMFjTWBY4FVgSxPhVySayKDbm8BgUN+AQEB
X-IronPort-AV: E=Sophos;i="5.09,525,1418083200"; d="asc'?scan'208";a="120877835"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by alln-iport-8.cisco.com with ESMTP; 05 Feb 2015 19:28:55 +0000
Received: from xhc-rcd-x13.cisco.com (xhc-rcd-x13.cisco.com [173.37.183.87]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id t15JStnv014618 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 5 Feb 2015 19:28:55 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.211]) by xhc-rcd-x13.cisco.com ([173.37.183.87]) with mapi id 14.03.0195.001; Thu, 5 Feb 2015 13:28:55 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: joel jaeggli <joelja@bogus.com>
Thread-Topic: [v6ops] IETF 92 heads Up
Thread-Index: AQHQQXn6aHb8e1Yj8kiQKUIm/2TKKA==
Date: Thu, 05 Feb 2015 19:28:54 +0000
Message-ID: <F986D043-F62A-46E6-A0EF-E260CA817D60@cisco.com>
References: <39A489D3-C0EB-49DC-90E6-3279A23EC60E@cisco.com> <CAAedzxqp1bXftJUkRX76=tmPT0ypqWP28QD-88N1iSNGzEbsMQ@mail.gmail.com> <441D3CE6-16C4-4CD2-9EB8-B63B2AA040A7@cisco.com> <54D244D8.9050709@bogus.com>
In-Reply-To: <54D244D8.9050709@bogus.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.19.64.121]
Content-Type: multipart/signed; boundary="Apple-Mail=_AFB8403C-A647-45C7-B2D0-49B65F900C82"; protocol="application/pgp-signature"; micalg="pgp-sha1"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/Bwlug28uMR1NzdHhXLSQhB3RSjw>
Cc: Erik Kline <ek@google.com>, V6 Ops List <v6ops@ietf.org>
Subject: Re: [v6ops] IETF 92 heads Up
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Feb 2015 19:29:18 -0000

> On Feb 4, 2015, at 8:12 AM, joel jaeggli <joelja@bogus.com> wrote:
>>>> Individual Submission NOT updated since IETF:
>>>> 
>>>> Aug 24  draft-v6ops-pmtud-ecmp-problem
>>> 
>>> I've seen this draft be usefully referred to a couple of times in
>>> the last few months.  +1 to keeping it afloat, if not moving
>>> forward for some reason (cc'ing Joel explicitly).
>> 
>> Up to Joel. If folks tell us it should be a working group draft, it
>> can be resubmitted as draft-ietf-v6ops-pmtud-ecmp-problem, following
>> the naming guideline that IETF tools depend on. Or whatever.
> 
> I am happy to undertake a revision, or encourage my co-authors to do so.

That would be fine.

> I throw myself at the mercy of the chairs with respect to the title.

I’m working from http://www.ietf.org/id-info/guidelines.html#naming and the fact that IETF tools depend on this.

Drafts can be named one of three ways:
    draft-ietf-<wg>-*-nn.txt       A working group draft
    draft-<author>-<wg>-*-nn.txt   An individual submission to a working group
    draft-<author>-*-nn.txt        An individual submission not targeted to a specific working group

The guidelines have a number of special "authors", such as -iab-, -iaoc-, and so on.

When you file a draft as draft-ietf-v6ops-*-00.txt, the working group chairs get a question from the secretariat: "is this an authorized working group draft?" If we say "yes", it's allowed to be posted, and if we say "no" or don't say anything, it doesn't. Once the -00 is posted, it can be updated at will. The status also show up in the data tracker: if you look up https://datatracker.ietf.org/doc/search/?name=v6ops&activedrafts=on&sort=, drafts named draft-ietf-v6ops-* are listed as "WG Documents", and other documents aren't. IETF tools depend on that naming - WG status is not a separate attribute (although I would prefer that it was), it is carried in the name of the draft.

My personal tools are a little more forgiving; if I find the character string "v6ops" anywhere in the name, I consider it related to v6ops somehow. In part, that is because we sometimes get documents with names like draft-tom-dick-harry-v6ops-*, that completely screw the naming guidelines. We also sometimes get documents that are individual submissions without respect to a working group that are shopped to several working groups. I'm perfectly willing to see people drop a note to the list saying "I filed draft-myname-stuff-i-am-worried-about, and wonder what the operational folks think", or for that matter drafts from other working groups, and if folks ask, we may fit those into an agenda somewhere. But if it has the word "v6ops" in the name, I electronic ear-equivalents perk up, my bot sends a note to the working group and a separate note to the authors, and it automatically shows up in my agenda analysis.

But really. We decided to accept this as a working group draft. I'm looking for a document with a name like draft-ietf-v6ops-pmtud-ecmp-problem.