Re: [alto] Work related to ALTO at IETF82

"Vijay K. Gurbani" <vkg@bell-labs.com> Mon, 14 November 2011 14:56 UTC

Return-Path: <vkg@bell-labs.com>
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 A49BD11E82A4 for <alto@ietfa.amsl.com>; Mon, 14 Nov 2011 06:56:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.563
X-Spam-Level:
X-Spam-Status: No, score=-106.563 tagged_above=-999 required=5 tests=[AWL=0.036, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vIelIDx0zMsV for <alto@ietfa.amsl.com>; Mon, 14 Nov 2011 06:56:27 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 62F7E11E82A2 for <alto@ietf.org>; Mon, 14 Nov 2011 06:56:20 -0800 (PST)
Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id pAEEuJTp024270 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <alto@ietf.org>; Mon, 14 Nov 2011 08:56:19 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id pAEEuJTr008767 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <alto@ietf.org>; Mon, 14 Nov 2011 08:56:19 -0600
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.238.235]) by umail.lucent.com (8.13.8/TPES) with ESMTP id pAEEuJsL018569 for <alto@ietf.org>; Mon, 14 Nov 2011 08:56:19 -0600 (CST)
Message-ID: <4EC12CC6.4030608@bell-labs.com>
Date: Mon, 14 Nov 2011 08:59:18 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:7.0) Gecko/20110927 Thunderbird/7.0
MIME-Version: 1.0
To: alto@ietf.org
References: <4EBD379A.7050506@telecomitalia.it> <4EBF30F8.8010209@googlemail.com> <CA+cvDaZ_Vfcy4ZQzhGruUvSznueYm1_33yhAhrZ5mdeFs3oMaw@mail.gmail.com>
In-Reply-To: <CA+cvDaZ_Vfcy4ZQzhGruUvSznueYm1_33yhAhrZ5mdeFs3oMaw@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
Subject: Re: [alto] Work related to ALTO at IETF82
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: Mon, 14 Nov 2011 14:56:27 -0000

<As individual>

On 11/13/2011 07:31 PM, Richard Alimi wrote:
> One way forward is to split out Section 8 (redistribution) of
> draft-ietf-alto-protocol into a separate document as an extension, and
> only the extension would be blocked on the JOSE WG. Given that this
> part was not implemented by anyone at the interop event (to my
> knowledge -- please correct me if I'm wrong) event and there is more

Indeed, the test case document did not include any cases to test
for redistribution, and none of the participating server implementations
mentioned this as a supported feature.

> than enough in the base protocol to get this working for the large
> majority of use cases.

I think this is a reasonable path (again, speaking as an individual,
since I have not talked to Enrico about this yet as a co-chair).

I note that there is a now-expired draft on ALTO information re-
distribution [1].  This draft is mentioned in the alto-protocol
document (see second paragraph of S6.1.2).  What is the relationship
of [1] to Section 8 of the alto-protocol document?

[1] http://tools.ietf.org/html/draft-gu-alto-redistribution-03

Thanks,

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