Re: [alto] Revised interop document
"Y. Richard Yang" <yry@cs.yale.edu> Fri, 11 September 2015 20:30 UTC
Return-Path: <yang.r.yang@gmail.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 9550C1B4453 for <alto@ietfa.amsl.com>; Fri, 11 Sep 2015 13:30:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level:
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 Y-xraQ9lejYl for <alto@ietfa.amsl.com>; Fri, 11 Sep 2015 13:30:43 -0700 (PDT)
Received: from mail-vk0-x22f.google.com (mail-vk0-x22f.google.com [IPv6:2607:f8b0:400c:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF76F1B30B5 for <alto@ietf.org>; Fri, 11 Sep 2015 13:30:43 -0700 (PDT)
Received: by vkgd64 with SMTP id d64so32066631vkg.0 for <alto@ietf.org>; Fri, 11 Sep 2015 13:30:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=2wJGt0yVOAWdjwSJY3ziM7iECv5y6WH81mWQSDaQdLk=; b=dRCThUpSVJHDgIVUmcJ495l0fDvtrBPnmeN0jV4+rfW9mCMwd4Q7NqJxH98SWa4GEJ yCy24IiUbV5t1jthaJyEAPKlnzxOB0EjXhNP0VT1F3gxoHdAapHQc80s0NYHJ3DTxUvH CRuEdIB5sPfFC+EgSWNFdkaJwf4pddgISK77HnbY1q80e4QDOTzxUPDjK8SGuqrxI45W D3WhBDwT8y7gf/XBLhBqwcUCcB7HJySjzj266AWB8tWA43xPh+uftHS5aLODRhY1U6PR sj3D8YCNG5ORIRGFxyd33+iqlSfEhcckFRoWxrAQpVZIloT5miffxc+Qeku8lLtujqJY EwjA==
MIME-Version: 1.0
X-Received: by 10.31.153.77 with SMTP id b74mr302632vke.118.1442003442839; Fri, 11 Sep 2015 13:30:42 -0700 (PDT)
Sender: yang.r.yang@gmail.com
Received: by 10.103.15.133 with HTTP; Fri, 11 Sep 2015 13:30:42 -0700 (PDT)
In-Reply-To: <D218AE30.491259%w.roome@alcatel-lucent.com>
References: <D218AE30.491259%w.roome@alcatel-lucent.com>
Date: Fri, 11 Sep 2015 16:30:42 -0400
X-Google-Sender-Auth: yUvfh39pKMCKpVeWBcke26vnIrM
Message-ID: <CANUuoLoc=Xy9M3o8cLRr+kgYf92NEXtCV5vc5PEdYEJqcuswyw@mail.gmail.com>
From: "Y. Richard Yang" <yry@cs.yale.edu>
To: Wendy Roome <w.roome@alcatel-lucent.com>
Content-Type: multipart/alternative; boundary="001a113d33b0f9b93e051f7e9621"
Archived-At: <http://mailarchive.ietf.org/arch/msg/alto/f9uoY1u_cIvGPagtmG8sSVwO3Bg>
Cc: IETF ALTO <alto@ietf.org>
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: Fri, 11 Sep 2015 20:30:45 -0000
Wendy, Hans, Great work! I did a search of existing RFCs on interop related documents and found the following: http://www.rfc-editor.org/search/rfc_search_detail.php?title=interop&pubstatus%5B%5D=Any&pub_date_type=any One example is http://www.rfc-editor.org/info/rfc6984 which reports the settings and results of an ForCES interop. Given that we are planning to have more interop features available online for alto, it is a good idea to have a more formal, updated document. Just my two cents. Richard On Fri, Sep 11, 2015 at 4:13 PM, Wendy Roome <w.roome@alcatel-lucent.com> wrote: > Hans & I have updated the Interop document. We revised the routingcost and > hopcount values to represent more reasonable network topologies. The PIDs > and CIDRs remain the same, though. > > Also, Hans added very nice interconnect diagrams for the two network maps, > along with link-weights from which you can derive routingcost. > > 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 Roome > > > _______________________________________________ > alto mailing list > alto@ietf.org > > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_alto&d=AwICAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=4G36iiEVb2m_v-0RnP2gx9KZJjYQgfvrOCE3789JGIA&m=K5rk0XcLXbBrRXybcMNPaZI3KqhO1mAbOlD0Tfmt1Ow&s=RlZyP0eRn0vvpuqUOwJFvML1ueAcVy9gwThnmclGWuU&e= >
- [alto] Revised interop document Wendy Roome
- Re: [alto] Revised interop document Y. Richard Yang
- Re: [alto] Revised interop document Vijay K. Gurbani