Re: [alto] Revised interop document

"Vijay K. Gurbani" <vkg@bell-labs.com> Mon, 14 September 2015 22:40 UTC

Return-Path: <vkg@bell-labs.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59BD81B375B for <alto@ietfa.amsl.com>; Mon, 14 Sep 2015 15:40:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-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 xKqm6r-x--82 for <alto@ietfa.amsl.com>; Mon, 14 Sep 2015 15:40:57 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-01.alcatel-lucent.com [135.245.210.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E85911B37C4 for <alto@ietf.org>; Mon, 14 Sep 2015 15:40:54 -0700 (PDT)
Received: from us70tusmtp2.zam.alcatel-lucent.com (unknown [135.5.2.64]) by Websense Email Security Gateway with ESMTPS id 68FA78FF59080 for <alto@ietf.org>; Mon, 14 Sep 2015 22:40:49 +0000 (GMT)
Received: from umail.lucent.com (umail.ndc.lucent.com [135.3.40.61]) by us70tusmtp2.zam.alcatel-lucent.com (GMO) with ESMTP id t8EMeon4032022 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <alto@ietf.org>; Mon, 14 Sep 2015 22:40:50 GMT
Received: from [135.185.238.169] (shoonya.ih.lucent.com [135.185.238.169]) by umail.lucent.com (8.13.8/TPES) with ESMTP id t8EMeoeh012931; Mon, 14 Sep 2015 17:40:50 -0500 (CDT)
To: Wendy Roome <w.roome@alcatel-lucent.com>, IETF ALTO <alto@ietf.org>
References: <D218AE30.491259%w.roome@alcatel-lucent.com>
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Message-ID: <55F74CF2.3060504@bell-labs.com>
Date: Mon, 14 Sep 2015 17:40:50 -0500
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <D218AE30.491259%w.roome@alcatel-lucent.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/alto/BQ04FmRJAL0CEAPpQsMAkuHxfxU>
Subject: Re: [alto] Revised interop document
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/alto/>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Sep 2015 22:40:59 -0000

w.roome@alcatel-lucent.com writes:
> Question for you all -- and especially for our chairpeople: are you
> interested in upgrading this to a WG document, with the intent of turning
> it into an RFC. In other words, would you like to turn this into an
> official test suite for ALTO, rather than being a one-shot deal for
> IETF-93? For the seasoned IETFers, does the IETF allow such test suite?

Wendy, all: my advice to you would be to continue moving the document
ahead, irrespective of whether or not it is upgraded to a WG document.

There are other streams by which an I-D can be made into an RFC.  In my
opinion, the biggest input to the process of a WG moving work ahead to
RFC status is whether or not the draft is valuable to the WG members.
Clearly it appears that the interoperability document meets that
bar, so I would advise you to continue moving the work ahead.  We (i.e.,
the chairs and AD) will get it on some stream towards an RFC so your
efforts are not wasted.

Cheers,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
Web: http://ect.bell-labs.com/who/vkg/  | Calendar: http://goo.gl/x3Ogq