Re: [tap] RFC Status?

Ovid <> Wed, 13 August 2014 04:10 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 6D7631A6FD6 for <>; Tue, 12 Aug 2014 21:10:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 0.035
X-Spam-Status: No, score=0.035 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.668, SPF_PASS=-0.001, URIBL_DBL_ABUSE_REDIR=0.001, URIBL_DBL_REDIR=0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id HGaqHazEbf37 for <>; Tue, 12 Aug 2014 21:10:02 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 56E3B1A6FE5 for <>; Tue, 12 Aug 2014 21:10:02 -0700 (PDT)
Received: from [] by with NNFMP; 13 Aug 2014 04:10:00 -0000
Received: from [] by with NNFMP; 13 Aug 2014 04:10:00 -0000
Received: from [] by with NNFMP; 13 Aug 2014 04:10:00 -0000
X-Yahoo-Newman-Property: ymail-3
Received: (qmail 89518 invoked by uid 60001); 13 Aug 2014 04:10:00 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=s1024; t=1407903000; bh=w/Fkg4J218Mh3jlde8Fb6zIecgr300dqO+BPIL/XAOE=; h=References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=3IZqgq8EiBKLLxPBAAcvoItB4VKGM4hQCe3IqKuKYpTddhRLq2DUm9HvmVMPJgJ2SnuR3LZv2IdVtwrHL9avul6t65XZsxTzgMd0vvemz7jI2qtMCr9YOrWrOOZ7VSP5JoSEsEuhnG/wSiDQ0Dd8J8tDk+VMhznchAJavnRzwB4=
X-YMail-OSG: rZt.hJsVM1nrsdZlgZ7NjpNuDNUZQfMM6BLT7RVP5cXflu7 eS9xWYa9F6JEvKMFx901DNG0jSBcQs6nDUgBsQ.x7MHl2IcsCBrQ61zxfv.0 w3cYuyJGvoIu6_wx13ZVWV0CzdZ2XuW3AvGpusU7cd6u2NAsveRO4JCa8U8n ZEkQt1WS2PbS2uDHia_uZsPvCpBByr__qEts1PTAxaQwwhhE7Wt.mdmfPJiv t2MR4I.SI7gqPHokBUwEv5EX9i.WBPkTn0lfdsLY8Nj1.6hL5pkk_OQYfZ_7 EIraSHvcm7tBJ8.WsSMGKtiiUadcqFTHU4iJcK90_VtqbIPwxSDSr7MySbxM mcSocKSYr8y_iS996rAkInDK.N9peFSS8mv9VqAm4EkUCYX8CjFSVcYJNowR PqfYWXmY09QJkRB2aA0TBkkkq7mXqHKZGKXXDYaB3ucjBO4Su24NqPrs.iXQ OMgT5dFfb72ug.xOaRRk8eNPDWSOFIqwzzwx3XTRQe1NOrLrtTW9_cBDWWec bu0rqSdA_fYHGZeg8pDMOuLHE4NlLOrinoh._mMeAhGlR.tz0xUH6Bmw0oEx WywN3o77cnCvnylM1qoxDK.abmg7SnHCqXgwlbqj3nOOhNKjdsnvZLoaHVVD aCW0HVUhzoVIRmGsuiQu.JiMzIXwNjcK4rysaY2levaMTErQJWps6yrzFvWA yaMatlAbaN7epOw1tp5EEuSdkvkN6_eXE92Vi2gP38FtJIjrUX9yRmZztfZl j9VBkXTHx2523.9P.jffVz7bkY.b92n5b7WRtofNL
Received: from [] by via HTTP; Tue, 12 Aug 2014 21:10:00 PDT
X-Rocket-MIMEInfo: 002.001, V2hhdCBkbyB5b3UgdGhpbmsgdGhhdCB3b3VsZCBiZSB0aGUgbmV4dCBzdGVwcyB0byBwdXNoIGZvcndhcmQgYSBUQVAgMTQgZHJhZnQsIGFuZCBtYWtlIHNvbWUgcHJvZ3Jlc3Mgb24gdGhlIFJGQz8gTWF5YmUgc29tZXRoaW5nIGxpa2UgbW9udGhseSBtZWV0aW5ncyBpbiBJUkMgb3Igc29tZSBvdGhlciBJTSwgYW5kIHNvbWUgZGlzY3Vzc2lvbiBwYW5lbHMgaW4gaGFja2F0aG9ucy9tZWV0dXBzP8KgClRoZSBpbW1lZGlhdGUgbmVlZCBpcyBmb3Igc29tZW9uZSB0byB0YWtlIG93bmVyc2hpcCBvZiB0aGUgSUUBMAEBAQE-
X-Mailer: YahooMailWebService/
References: <> <> <> <> <> <>
Message-ID: <>
Date: Tue, 12 Aug 2014 21:10:00 -0700
From: Ovid <>
To: "Bruno P. Kinoshita" <>, Andrew de Andrade <>
In-Reply-To: <>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-588606924-589986613-1407903000=:34343"
X-Mailman-Approved-At: Wed, 13 Aug 2014 00:07:02 -0700
Cc: "" <>
Subject: Re: [tap] RFC Status?
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Ovid <>
List-Id: Test Anything Protocol WG discussions <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 13 Aug 2014 04:10:09 -0000

What do you think that would be the next steps to push forward a TAP 14 draft, and make some progress on the RFC? Maybe something like monthly meetings in IRC or some other IM, and some discussion panels in hackathons/meetups? 
The immediate need is for someone to take ownership of the IETF process and publicly say "I'll see this through." There was a lot of great work done in the past, but we're obviously not there yet.

Next, the goal needs to be clearly defined. I would also suggest we define why we want the goal accomplished. Once done:
	1. What we've successfully done.

	2. What we still need to do.

	3. What might need to change (danger, Will Robinson!)

Those three items can give us a TODO list. Item #1 might seem superfluous, but when tackling a large project, I like to remind people of all of the groundwork already laid to keep things in perspective. Plus, a sense of historical context might help those who are unfamiliar with the history.

With that, we can start scratching items off out TODO list one-by-one. I would humbly suggest that we not go with monthly meetings as they're so hard to organize. Instead, keep the list open, have the TODO list on a github wiki and let's see what we can make happen.

IT consulting, training, international recruiting
Buy my book! -
Live and work overseas -