[alto] PID Properties in ALTO

Richard Alimi <rich@velvetsea.net> Fri, 27 May 2011 16:48 UTC

Return-Path: <richard.alimi@gmail.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 05E2BE070C for <alto@ietfa.amsl.com>; Fri, 27 May 2011 09:48:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.314
X-Spam-Level:
X-Spam-Status: No, score=-2.314 tagged_above=-999 required=5 tests=[AWL=0.663, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
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 5kMQfh4cPt-u for <alto@ietfa.amsl.com>; Fri, 27 May 2011 09:48:37 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6D72BE0819 for <alto@ietf.org>; Fri, 27 May 2011 09:48:37 -0700 (PDT)
Received: by iwn39 with SMTP id 39so2395741iwn.31 for <alto@ietf.org>; Fri, 27 May 2011 09:48:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:from:date :x-google-sender-auth:message-id:subject:to:content-type; bh=I11TsauIq2gdKuH0zZMv5blfsdJdC9nVp3b8Fq9S54U=; b=YNg4EScALlryz2mAWjUXNkSpamWue3lMtEGtDYpWO455LToFx2+PtLdzFeVdKFR5d8 ZGZejK/PUGv9YJIzmYtiPcLm3UUdyAwGgGil1pqt0rh52jHnzcTqiPADGWJKhnT/ca58 C1TY64zz8lPJuX/cDNFdHzt9EU3E6GpvnIVeo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:from:date:x-google-sender-auth:message-id :subject:to:content-type; b=nFJHROgkXgiubYK/kvmJUHIfSvqHFBBtV+GLGIjUPTOUzee/mxJo5LUJQR+Su9N7vT Z1NHXNeCfuTNpmBcEOQ5VNbxRGLoctZ3Zz5ph4mghNI31GYyv9wIiaTUjr+BlAoz+WxH NV1Kh8ynGyU8QU+MdP6BEj4XjRP2c8zrEo47w=
Received: by 10.231.63.198 with SMTP id c6mr2457575ibi.159.1306514917057; Fri, 27 May 2011 09:48:37 -0700 (PDT)
MIME-Version: 1.0
Sender: richard.alimi@gmail.com
Received: by 10.231.85.143 with HTTP; Fri, 27 May 2011 09:48:17 -0700 (PDT)
From: Richard Alimi <rich@velvetsea.net>
Date: Fri, 27 May 2011 09:48:17 -0700
X-Google-Sender-Auth: mNpLCas7UuwO-h0NGhgIg1Yx3TE
Message-ID: <BANLkTiknMWOURcPQOpzKrFwaYzSNJ5=TbA@mail.gmail.com>
To: alto@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
Subject: [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 16:48:38 -0000

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