Re: [alto] PID Properties in ALTO
Reinaldo Penno <rpenno@juniper.net> Tue, 25 October 2011 19:37 UTC
Return-Path: <rpenno@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 9292121F8B33 for <alto@ietfa.amsl.com>; Tue, 25 Oct 2011 12:37:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.556
X-Spam-Level:
X-Spam-Status: No, score=-6.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 40EPbFfw-lDS for <alto@ietfa.amsl.com>; Tue, 25 Oct 2011 12:37:27 -0700 (PDT)
Received: from exprod7og114.obsmtp.com (exprod7og114.obsmtp.com [64.18.2.215]) by ietfa.amsl.com (Postfix) with ESMTP id ECBAC21F8B32 for <alto@ietf.org>; Tue, 25 Oct 2011 12:37:22 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob114.postini.com ([64.18.6.12]) with SMTP; Tue, 25 Oct 2011 12:37:26 PDT
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.3.213.0; Tue, 25 Oct 2011 12:36:12 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Tue, 25 Oct 2011 15:36:11 -0400
From: Reinaldo Penno <rpenno@juniper.net>
To: Richard Alimi <rich@velvetsea.net>, Robert Varga <robert.varga@pantheon.sk>
Date: Tue, 25 Oct 2011 15:36:09 -0400
Thread-Topic: [alto] PID Properties in ALTO
Thread-Index: AcySb/6pHwSqNoWHTVi+9eDO+yqNbAA3Vmjn
Message-ID: <CACC5DB9.5642C%rpenno@juniper.net>
In-Reply-To: <CA+cvDaYnRz7as-0uG1TkxrCRDKX6_+eWhCtA3oiX_3qX17CHxA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-Entourage/13.11.0.110726
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] PID Properties in ALTO
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: Tue, 25 Oct 2011 19:37:27 -0000
As one of the proponents I like the idea but an extension is fine. On 10/24/11 10:10 AM, "Richard Alimi" <rich@velvetsea.net> wrote: > I'm fine with leaving this as an extension, I agree it falls outside > of the core set of functionality and could easily be done as an > extension. Objections to that? > > Rich > > On Fri, May 27, 2011 at 11:11 AM, Robert Varga <robert.varga@pantheon.sk> > wrote: >> Hi, >> >> I agree we should support it. I am just not sure we need it the base >> protocol, though, as it can easily be specified as an extension. >> >> Bye, >> Robert >> >> On 05/27/11 18:48, Richard Alimi wrote: >>> Hi All, >>> >>> Okay, third and final thread for discussion today :) Another proposed >>> extension to the ALTO protocol has been to associate properties (like >>> we currently have with Endpoints) with PIDs. >>> >>> A proposed use case in draft-penno-alto-cdn was to indicate what types >>> of endpoints lived within a single PID. A more general mechanism to >>> support this would be to allow properties to be associated with a PID >>> as whole. In one light, this could be seen as an efficient way to >>> query for the properties of all endpoints within a PID (in which >>> membership in the PID determines the value of the property). It could >>> also be used to attach some semantic meaning to a PID (instead of >>> being an opaque identifier) in particular deployments. >>> >>> One way to support this would be to provide an additional "PID >>> Property" service, with a similar structure to the Endpoint Property >>> Service. Basically, it would amount to defining a registry, allowing >>> an ALTO Server to indicate its supported properties via capabilities, >>> defining encodings for the request and response, etc. >>> >>> Thoughts about supporting this? >>> >>> Thanks, >>> Rich >>> _______________________________________________ >>> alto mailing list >>> alto@ietf.org >>> https://www.ietf.org/mailman/listinfo/alto >> >> >> -- >> Robert Varga >> Pantheon Technologies, s.r.o. >> Mlynske Nivy 56 >> 831 05 Bratislava >> >> _______________________________________________ >> 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] PID Properties in ALTO Richard Alimi
- Re: [alto] PID Properties in ALTO Robert Varga
- Re: [alto] PID Properties in ALTO Ben Niven-Jenkins
- Re: [alto] PID Properties in ALTO Richard Alimi
- Re: [alto] PID Properties in ALTO Ben Niven-Jenkins
- Re: [alto] PID Properties in ALTO Richard Alimi
- Re: [alto] PID Properties in ALTO Richard Alimi
- Re: [alto] PID Properties in ALTO Reinaldo Penno
- Re: [alto] PID Properties in ALTO Y. Richard Yang