Re: The IETF Data Tracker and non-IETF streams for RFCs

todd glassey <tglassey@earthlink.net> Thu, 15 July 2010 19:11 UTC

Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5971A3A69B8 for <ietf@core3.amsl.com>; Thu, 15 Jul 2010 12:11:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.196
X-Spam-Level:
X-Spam-Status: No, score=-2.196 tagged_above=-999 required=5 tests=[AWL=0.403, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c43RJeIBdBA5 for <ietf@core3.amsl.com>; Thu, 15 Jul 2010 12:11:49 -0700 (PDT)
Received: from elasmtp-scoter.atl.sa.earthlink.net (elasmtp-scoter.atl.sa.earthlink.net [209.86.89.67]) by core3.amsl.com (Postfix) with ESMTP id 8267A3A6B38 for <ietf@ietf.org>; Thu, 15 Jul 2010 12:11:49 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=pAKZuxa76/HHsjEfrjKfMM5iAGkdd2S2iJQZNGwHKGeBCLbqTcE3Q+T21+titZCw; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [64.125.79.149] (helo=[192.168.1.170]) by elasmtp-scoter.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1OZTqi-0007Ug-1Z for ietf@ietf.org; Thu, 15 Jul 2010 15:12:00 -0400
Message-ID: <4C3F5D84.90100@earthlink.net>
Date: Thu, 15 Jul 2010 12:12:04 -0700
From: todd glassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.4) Gecko/20100608 Thunderbird/3.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: The IETF Data Tracker and non-IETF streams for RFCs
References: <p06240842c864f01cfba3@[10.20.30.158]>
In-Reply-To: <p06240842c864f01cfba3@[10.20.30.158]>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79c71c77efb474a6089f5849ef38ebfb3b350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 64.125.79.149
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 15 Jul 2010 19:11:51 -0000

> Greetings again. The IAOC has asked me to prepare a document that describes extending the IETF Data Tracker to capture and display the progression of Internet Drafts that are intended to be published as RFCs by the IAB, IRTF, or Independent Submissions Editor. That document, currently at -02, can be found at <http://tools.ietf.org/html/draft-hoffman-alt-streams-tracker>.
>
> Although the document is exclusively about the three non-IETF streams, many folks in the IETF community care about those streams. If you are one of those people, please look over the document and let me know what you think. If you would like to discuss the document, the "RFC Interest" mailing list (<http://www.rfc-editor.org/mailman/listinfo/rfc-interest>) is a good place, and there has already been a bit of discussion there recently. Also, if you want to talk to me in Maastricht about the document, please get in touch.
>
> Just to be clear: draft-hoffman-alt-streams-tracker is about extending the Data Tracker for only the three non-IETF streams. The IAOC asked Ed Juskevicius to prepare documents on extending the Data Tracker for the IETF stream; those two documents, draft-juskevicius-datatracker-wgdocstate-reqts and draft-ietf-proto-wgdocument-states, have both gone through IETF Last Call.
>
> --Paul Hoffman, Director
> --VPN Consortium

Paul - the document looks good but are all of the streams provided the
same oversight processes? Is the IAB stream for instance also controlled
under the IETF oversight controls and processes? how about the other
streams?

Todd Glassey
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>