Re: [CDNi] CDNI Metadata Interface
Kevin J Ma <kevin.ma@azukisystems.com> Tue, 11 October 2011 15:29 UTC
Return-Path: <kevin.ma@azukisystems.com>
X-Original-To: cdni@ietfa.amsl.com
Delivered-To: cdni@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F4ED21F8E4F for <cdni@ietfa.amsl.com>; Tue, 11 Oct 2011 08:29:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 ysaB2qOL14SQ for <cdni@ietfa.amsl.com>; Tue, 11 Oct 2011 08:29:36 -0700 (PDT)
Received: from mxout.myoutlookonline.com (mxout.myoutlookonline.com [64.95.72.241]) by ietfa.amsl.com (Postfix) with ESMTP id E35C221F8E4D for <cdni@ietf.org>; Tue, 11 Oct 2011 08:29:35 -0700 (PDT)
Received: from mxout.myoutlookonline.com (localhost [127.0.0.1]) by mxout.myoutlookonline.com (Postfix) with ESMTP id 79F275550B0; Tue, 11 Oct 2011 11:29:35 -0400 (EDT)
X-Virus-Scanned: by SpamTitan at mail.lan
Received: from HUB015.mail.lan (unknown [10.110.2.1]) by mxout.myoutlookonline.com (Postfix) with ESMTP id CA556554EC5; Tue, 11 Oct 2011 11:29:33 -0400 (EDT)
Received: from MAILR002.mail.lan ([10.110.18.15]) by HUB015.mail.lan ([10.110.17.15]) with mapi; Tue, 11 Oct 2011 11:29:16 -0400
From: Kevin J Ma <kevin.ma@azukisystems.com>
To: HeXiaoyan <hexiaoyan@huawei.com>, "cdni@ietf.org" <cdni@ietf.org>
Date: Tue, 11 Oct 2011 11:29:31 -0400
Thread-Topic: [CDNi] CDNI Metadata Interface
Thread-Index: AcyErDmDceDqNX+AQtKwjumpTmgL9wDNgegQABC/ZGA=
Message-ID: <291CC3F9E50E7641901A54E85D0977C651B51517AD@MAILR002.mail.lan>
References: <291CC3F9E50E7641901A54E85D0977C651B50AF9D2@MAILR002.mail.lan> <010d01cc87f8$10bc5940$32350bc0$@com>
In-Reply-To: <010d01cc87f8$10bc5940$32350bc0$@com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [CDNi] CDNI Metadata Interface
X-BeenThere: cdni@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "This list is to discuss issues associated with the Interconnection of Content Delivery Networks \(CDNs\)" <cdni.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cdni>, <mailto:cdni-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/cdni>
List-Post: <mailto:cdni@ietf.org>
List-Help: <mailto:cdni-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cdni>, <mailto:cdni-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Oct 2011 15:29:39 -0000
Hi Susan, thanx for the comments, responses inline: > -----Original Message----- > From: HeXiaoyan [mailto:hexiaoyan@huawei.com] > Sent: Tuesday, October 11, 2011 5:28 AM > To: Kevin J Ma; cdni@ietf.org > Subject: RE: [CDNi] CDNI Metadata Interface > > Hi Kevin, > Some quick questions and comments on this draft, > >The Metadata objects are each associated with a URI within the Domain and > accessible through any of the Hostnames... > - Could you further explain or give an example how a metadata is accessed > by > a Hostname within the Domain? And a further question is how the data model > works if a metadata is only associated with a specific Hostname within one > Doman? I was assuming that metadata would be valid for all hostnames. If a hostname needed separate metadata, a new domain would be required. I was thinking of hostname as a first level restriction. My implementation does something along the lines of the following (where hostname is checked before metadata lookup): domain = get_param_from_query_string(getenv("QUERY_STRING"), "domain") if (!db_verify_hostname_for_domain(getenv("SERVER_NAME"), domain)) return error metadata = db_get_metadata_by_uri_domain_agent(getenv("REQUEST_URI"), domain, getenv("REMOTE_USER")) xml = generate_xml_for_metadata(metadata) return xml > - The relationship between Agent objects and Metadata objects is a > one-to-one relationship, does this mean one agent can only access one > Metadata within one Domain? That is a typo in the doc, good catch, thanx! It should be one to many. Each metadata must be associated with a single agent, but an agent can be associated with multiple metadata. Agent-1 could have metadatas A, B, and C, while agent-2 could have a separate value for metadatas A and B, and also have its own metadata D (that agent-1 does not have access to) > > The association of each Metadata to an Agent allows different Agents to > retrieve different Metadata values for a given URI in the given Domain. > - Don't understand why each Metadata object needs to be bind with an Agent > explicitly, IMO, whether to return different value to different Agents is > an > inside process of the upCDN, what downCDN needs to do is just transmit its > identifier to the upCDN when retrieve a Metadata. I think the fact that a uCDN would want/need to give out different values to different dCDNs requires that there be a way to represent and store that information. Having it explicitly in the model, i think, simplifies the implementation and guarantees that all implementation give this issue proper consideration. > - Which entity is responsible for creating the Agent objects within one > Domain? Does the CP can 'see' the downCDNs and creates corresponding Agent > objects and other CDNs on the way just transmitted it or each upCDN > located > in the cascaded path creates a Agent object for each its downCDN? This is a good question. Different agents would need to be create by different entities, as you mention. I would expect each CDN to create agents to represent those (outside that CDN) who need access to the metadata interface. thanx! -- Kevin J. Ma > Thanks. > Best Regards > Xiaoyan(Susan) He > > -----Original Message----- > From: cdni-bounces@ietf.org [mailto:cdni-bounces@ietf.org] On Behalf Of > Kevin J Ma > Sent: Friday, October 07, 2011 1:21 PM > To: cdni@ietf.org > Subject: [CDNi] CDNI Metadata Interface > > Hi all, > > Just uploaded a new I-D with a proposed metadata model and API: > > http://www.ietf.org/internet-drafts/draft-ma-cdni-metadata-00.txt > > The model takes a rather generic approach to metadata representation > to support opaque metadata and addresses some of the security issues > associated with metadata retrieval. Comments welcome. > > thanx. > > -- Kevin J. Ma > > _______________________________________________ > CDNi mailing list > CDNi@ietf.org > https://www.ietf.org/mailman/listinfo/cdni
- [CDNi] CDNI Metadata Interface Kevin J Ma
- Re: [CDNi] CDNI Metadata Interface HeXiaoyan
- Re: [CDNi] CDNI Metadata Interface Kevin J Ma
- Re: [CDNi] CDNI Metadata Interface Francois Le Faucheur
- Re: [CDNi] CDNI Metadata Interface HeXiaoyan
- Re: [CDNi] CDNI Metadata Interface HeXiaoyan
- Re: [CDNi] CDNI Metadata Interface Kevin J Ma
- Re: [CDNi] CDNI Metadata Interface HeXiaoyan
- Re: [CDNi] CDNI Metadata Interface Kevin J Ma
- Re: [CDNi] CDNI Metadata Interface HeXiaoyan
- Re: [CDNi] CDNI Metadata Interface Francois Le Faucheur
- Re: [CDNi] CDNI Metadata Interface Kevin J Ma
- Re: [CDNi] CDNI Metadata Interface Kevin J Ma
- Re: [CDNi] CDNI Metadata Interface Francois Le Faucheur
- Re: [CDNi] CDNI Metadata Interface Kevin J Ma