Re: [alto] New draft on use cases for ALTO & CDNs
Jan Medved <jmedved@juniper.net> Thu, 28 April 2011 15:33 UTC
Return-Path: <jmedved@juniper.net>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6403CE0685 for <alto@ietfa.amsl.com>; Thu, 28 Apr 2011 08:33:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5KqYxZ8IMrG3 for <alto@ietfa.amsl.com>; Thu, 28 Apr 2011 08:33:03 -0700 (PDT)
Received: from exprod7og123.obsmtp.com (exprod7og123.obsmtp.com [64.18.2.24]) by ietfa.amsl.com (Postfix) with ESMTP id 70369E0670 for <alto@ietf.org>; Thu, 28 Apr 2011 08:33:03 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob123.postini.com ([64.18.6.12]) with SMTP ID DSNKTbmIqH3IgVgsOcFLEVx8ZZWnLLes8izY@postini.com; Thu, 28 Apr 2011 08:33:03 PDT
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB01-HQ.jnpr.net ([fe80::fc92:eb1:759:2c72%11]) with mapi; Thu, 28 Apr 2011 08:30:33 -0700
From: Jan Medved <jmedved@juniper.net>
To: stefano previdi <sprevidi@cisco.com>, Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
Date: Thu, 28 Apr 2011 08:30:30 -0700
Thread-Topic: [alto] New draft on use cases for ALTO & CDNs
Thread-Index: AcwFuTaEZ+VhbkoDSv2zy26TB5mc0A==
Message-ID: <C9DED2F8.27A3F%jmedved@juniper.net>
In-Reply-To: <63C0C7B3-BB9F-4D93-A02D-64ECB0AED615@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.10.0.110310
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Grant Watson <grant.watson@bt.com>, Nabil N Bitar <nabil.n.bitar@verizon.com>, "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] New draft on use cases for ALTO & CDNs
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 28 Apr 2011 15:33:04 -0000
On 4/28/11 2:58 AM, "stefano previdi" <sprevidi@cisco.com> wrote: >Ben, > >On Apr 27, 2011, at 5:45 PM, Ben Niven-Jenkins wrote: >> Colleagues, >> >> During the ALTO meeting at IETF80 I made some comments at the >> microphone highlighting my concerns with the scope of draft-penno- >> alto-cdn-03 being far too wide and that we should first focus on >> documenting the use cases and requirements. >> >> To that end I've been working with a couple of folks to co-author a >> draft focussed on documenting the use cases for ALTO & CDNs, the >> thinking being that a fresh draft with a tighter focus than draft- >> penno-alto-cdn-03 makes highlighting and discussing the use cases >> without slipping into possible solution mechanisms much simpler and >> cleaner. > > >makes sense. > > >> We have just published a -00 version which is available here: >> http://tools.ietf.org/html/draft-jenkins-alto-cdn-use-cases-00 >> >> So far we have only included details on two use cases and included >> placeholders for another two because we wanted to socialise the work >> early to see if others were interested in contributing text for the >> use cases they have as well as to solicit early feedback on the >> structure and focus of the draft. > > >splitting the current alto-cdn document makes sense to me and we >need to define: >a. use cases >b. requirements >c. proposed solutions This seems to be most logical split. > >your draft addresses the use cases and you may want to merge the >use cases sections we currently have in the alto-cdn draft so to >focus that one only on the proposed solution(s). The first two uses cases in draft-jenkins-cdn-use-cases are described in draft-penno-alto-cdn. Agreed that the text from draft-penno-alto-cdn should be merged into the appropriate sections of draft-jenkins-cdn-use-cases. > >The question is about requirements: do we want to include them >in one of the two drafts or into a separate document ? > >s. /Jan > > >> Comments/Suggestions/etc on the draft are welcomed. >> >> Ben >> >> >> >> >> >> >> _______________________________________________ >> alto mailing list >> alto@ietf.org >> https://www.ietf.org/mailman/listinfo/alto > >_______________________________________________ >alto mailing list >alto@ietf.org >https://www.ietf.org/mailman/listinfo/alto
- [alto] New draft on use cases for ALTO & CDNs Ben Niven-Jenkins
- Re: [alto] New draft on use cases for ALTO & CDNs stefano previdi
- Re: [alto] New draft on use cases for ALTO & CDNs Jan Medved
- Re: [alto] New draft on use cases for ALTO & CDNs Ben Niven-Jenkins
- Re: [alto] New draft on use cases for ALTO & CDNs stefano previdi
- Re: [alto] New draft on use cases for ALTO & CDNs Richard Alimi
- Re: [alto] New draft on use cases for ALTO & CDNs Bitar, Nabil N
- Re: [alto] New draft on use cases for ALTO & CDNs grant.watson