Re: [alto] PID Properties in ALTO

Robert Varga <robert.varga@pantheon.sk> Fri, 27 May 2011 18:12 UTC

Return-Path: <robert.varga@pantheon.sk>
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 419E1E0726 for <alto@ietfa.amsl.com>; Fri, 27 May 2011 11:12:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.694
X-Spam-Level:
X-Spam-Status: No, score=-0.694 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SK=1.35, HOST_EQ_SK=0.555]
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 IrU68V7WEKl7 for <alto@ietfa.amsl.com>; Fri, 27 May 2011 11:12:04 -0700 (PDT)
Received: from amalka.pantheon.sk (amalka.pantheon.sk [81.89.59.174]) by ietfa.amsl.com (Postfix) with ESMTP id 737FAE0671 for <alto@ietf.org>; Fri, 27 May 2011 11:12:04 -0700 (PDT)
Received: from [10.0.2.15] (natint3.juniper.net [66.129.224.36]) by amalka.pantheon.sk (Postfix) with ESMTPSA id 3AA98215FB for <alto@ietf.org>; Fri, 27 May 2011 20:13:22 +0200 (CEST)
Message-ID: <4DDFE96E.5070104@pantheon.sk>
Date: Fri, 27 May 2011 20:11:58 +0200
From: Robert Varga <robert.varga@pantheon.sk>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110502 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: alto@ietf.org
References: <BANLkTiknMWOURcPQOpzKrFwaYzSNJ5=TbA@mail.gmail.com>
In-Reply-To: <BANLkTiknMWOURcPQOpzKrFwaYzSNJ5=TbA@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
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: Fri, 27 May 2011 18:12:05 -0000

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