DOCSLIB.ORG

Extensible Resource Identifier (XRI) Resolution V2.0

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Extensible Resource Identifier (XRI) Resolution V2.0 1 2 Extensible Resource Identifier (XRI) 3 Resolution V2.0 4 Working Draft 10, 18 March 2006 5 Document identifier: 6 xri-resolution-V2.0-wd-10 7 Location: 8 http://docs.oasis-open.org/xri/xri/V2.0 9 Editors: 10 Gabe Wachob, Visa International <[email protected]> 11 Drummond Reed, Cordance <[email protected]> 12 Les Chasen, NeuStar <[email protected]> 13 William Tan, NeuStar <[email protected]> 14 Steve Churchill, XDI.ORG <[email protected]> 15 Contributors: 16 Dave McAlpin, Epok <[email protected]> 17 Chetan Sabnis, Epok <[email protected]> 18 Peter Davis, Neustar <[email protected]> 19 Victor Grey, PlaNetwork <[email protected]> 20 Mike Lindelsee, Visa International <[email protected]> 21 Abstract: 22 This document defines both generic and trusted HTTP(S)-based resolution protocols for 23 Extensible Resource Identifiers (XRIs) as defined by Extensible Resource Identifier (XRI) 24 Syntax V2.0 [XRISyntax] or higher. For the set of XRIs defined to provide identifier 25 metadata, see Extensible Resource Identifier (XRI) Metadata V2.0 [XRIMetadata]. For a 26 basic introduction to XRIs, see the XRI 2.0 FAQ [XRIFAQ]. 27 Status: 28 This document was last revised or approved by the XRI Technical Committee on the 29 above date. The level of approval is also listed above. Check the current location noted 30 above for possible later revisions of this document. This document is updated periodically 31 on no particular schedule. 32 Technical Committee members should send comments on this specification to the 33 Technical Committee's email list. Others should send comments to the Technical 34 Committee by using the "Send A Comment" button on the Technical Committee's web 35 page at http://www.oasis-open.org/committees/xri. 36 For information on whether any patents have been disclosed that may be essential to 37 implementing this specification, and any offers of patent licensing terms, please refer to 38 the Intellectual Property Rights section of the Technical Committee web page 39 (http://www.oasis-open.org/committees/xri/ipr.php. 40 The non-normative errata page for this specification is located at http://www.oasis- 41 open.org/committees/xri. xri-resolution-V2.0-wd-10 18 March 2006 Copyright © OASIS Open 2006. All Rights Reserved. Page 1 of 74 42 Table of Contents 43 1 Introduction ............................................................................................................................. 5 44 1.1 Overview of XRI Resolution Architecture.............................................................................. 5 45 1.2 Structure of this Specification................................................................................................ 7 46 1.3 Examples of XRI Resolution Requests and Responses....................................................... 8 47 1.4 Terminology and Notation ..................................................................................................... 8 48 2 Namespaces ........................................................................................................................... 9 49 2.1 XRI Namespaces for XRI Resolution.................................................................................... 9 50 2.1.1 XRIs Reserved for XRI Resolution ................................................................................ 9 51 2.1.2 XRIs Assigned to XRI Resolution Service Types .......................................................... 9 52 2.2 XML Namespaces for XRI Resolution................................................................................... 9 53 2.3 Media Types for XRI Resolution ......................................................................................... 10 54 3 XRDS Documents................................................................................................................. 11 55 3.1 XRDS and XRD Namespaces............................................................................................. 11 56 3.2 XRD Elements and Attributes ............................................................................................. 11 57 3.2.1 Management Elements................................................................................................ 13 58 3.2.2 Authority Trust Elements ............................................................................................. 13 59 3.2.3 Synonym Elements...................................................................................................... 14 60 3.2.4 Service Endpoint Elements.......................................................................................... 14 61 3.2.5 Service Endpoint Trust Elements ................................................................................ 15 62 3.2.6 Service Endpoint Selection Elements.......................................................................... 15 63 3.3 XRD Attribute Processing Rules ......................................................................................... 16 64 3.3.1 ID Attribute ................................................................................................................... 16 65 3.3.2 Version Attribute .......................................................................................................... 16 66 3.3.3 Priority Attribute ........................................................................................................... 16 67 3.4 XRI Encoding Requirements............................................................................................... 17 68 4 Inputs and Outputs................................................................................................................ 18 69 4.1 Inputs................................................................................................................................... 18 70 4.1.1 QXRI (Authority String, Path String, and Query String)............................................... 19 71 4.1.2 Resolution Media Type ................................................................................................ 19 72 4.1.3 Service Type ................................................................................................................ 20 73 4.1.4 Service Media Type ..................................................................................................... 20 74 4.2 Outputs................................................................................................................................21 75 4.2.1 XRDS Document.......................................................................................................... 21 76 4.2.2 XRD Document............................................................................................................ 21 77 4.2.3 URI List ........................................................................................................................ 22 78 4.2.4 HTTP(S) Redirect ........................................................................................................ 22 79 5 Generic Authority Resolution ................................................................................................ 23 80 5.1 XRI Authority Resolution ..................................................................................................... 23 81 5.1.1 Service Type and Service Media Type........................................................................ 23 82 5.1.2 Protocol........................................................................................................................ 24 83 5.1.3 Community Root Authorities ........................................................................................ 26 84 5.1.4 Qualified Subsegments................................................................................................ 26 xri-resolution-V2.0-wd-10 18 March 2006 Copyright © OASIS Open 2006. All Rights Reserved. Page 2 of 74 85 5.1.5 Cross-References........................................................................................................ 27 86 5.1.6 Recursing Authority Resolution ................................................................................... 27 87 5.1.7 Construction of the Next Authority URI........................................................................ 28 88 5.2 IRI Authority Resolution ...................................................................................................... 28 89 5.2.1 Service Type and Media Type ..................................................................................... 29 90 5.2.2 Protocol........................................................................................................................ 29 91 5.2.3 Optional Use of HTTPS ............................................................................................... 29 92 6 Trusted Authority Resolution................................................................................................. 30 93 6.1 HTTPS................................................................................................................................. 30 94 6.1.1 Service Type and Service Media Type........................................................................ 30 95 6.1.2 Protocol........................................................................................................................ 30 96 6.2 SAML................................................................................................................................... 30 97
Load more

Recommended publications
  • Trusted Computing Or Distributed Trust Management?
    Trusted computing or distributed trust management? Michele Tomaiuolo Dipartimento di Ingegneria dell’Informazione Università di Parma Via Usberti, 181/A – 43100 Parma – Italy [email protected] Abstract Nowadays, in contrast with centralized or hierarchical certification authorities and directory of names, other solutions are gaining momentum. Federation of already deployed security systems is considered the key to build global security infrastructures. In this field, trust management systems can play an important role, being based on a totally distributed architecture. The idea of distributed trust management can be confronted with the concept of trusted computing. Though having a confusingly similar denomination, the different interpretation of trust in these systems drives to divergent consequences with respect to system architectures and access policies, but also to law, ethics, politics. While trusted computing systems assure copyright holders and media producers that the hosting system will respect the access restrictions they defined, trust management systems, instead, allow users to grant trust to other users or software agents for accessing local resources. Keywords Data security, Security Management, Authentication, Authorization, Intellectual Property Rights, Information Access, Digital Books, Multimedia, Web Technologies Introduction A number of architectures and systems are being proposed as a ground for improved interoperability among diverse systems, mainly exploiting the idea of service-oriented architecture. Yet, some issues remain open. In fact, composition of services requires some delegation of goals and duties among partners. But these delegations cannot come into effect, if they’re not associated with a corresponding delegation of privileges, needed to access some resources and complete delegated tasks, or achieve desired goals.
    [Show full text]
  • Gs Ins 006 V1.1.1 (2011-11)
    ETSI GS INS 006 V1.1.1 (2011-11) Group Specification Identity and access management for Networks and Services; Study to Identify the need for a Global, Distributed Discovery Mechanism Disclaimer This document has been produced and approved by the Identity and access management for Networks and Services (INS) ETSI Industry Specification Group (ISG) and represents the views of those members who participated in this ISG. It does not necessarily represent the views of the entire ETSI membership. 2 ETSI GS INS 006 V1.1.1 (2011-11) Reference DGS/INS-006 Keywords access, control, ID, management, network, service ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N° 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88 Important notice Individual copies of the present document can be downloaded from: http://www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http://portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http://portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission.
    [Show full text]
  • Extensible Resource Identifier (XRI) Resolution Version 2.0 Committee Draft 02 25 November 2007
    Extensible Resource Identifier (XRI) Resolution Version 2.0 Committee Draft 02 25 November 2007 Specification URIs: This Version: http://docs.oasis-open.org/xri/2.0/specs/cd02/xri-resolution-V2.0-cd-02.html http://docs.oasis-open.org/xri/2.0/specs/cd02/xri-resolution-V2.0-cd-02.pdf http://docs.oasis-open.org/xri/2.0/specs/cd02/xri-resolution-V2.0-cd-02.doc Previous Version: N/A Latest Version: http://docs.oasis-open.org/xri/2.0/specs/xri-resolution-V2.0.html http://docs.oasis-open.org/xri/2.0/specs/xri-resolution-V2.0.pdf http://docs.oasis-open.org/xri/2.0/specs/xri-resolution-V2.0.doc Technical Committee: OASIS eXtensible Resource Identifier (XRI) TC Chairs: Gabe Wachob, AmSoft <[email protected]> Drummond Reed, Cordance <[email protected]> Editors: Gabe Wachob, AmSoft <[email protected]> Drummond Reed, Cordance <[email protected]> Les Chasen, NeuStar <[email protected]> William Tan, NeuStar <[email protected]> Steve Churchill, XDI.org <[email protected]> Related Work: This specification replaces or supercedes: • Extensible Resource Identifier (XRI) Resolution Version 2.0, Committee Draft 01, March 2005 • Extensible Resource Identifier (XRI) Version 1.0, Committee Draft 01, January 2004 This specification is related to: • Extensible Resource Identifier (XRI) Syntax Version 2.0, Committee Specification, December 2005 • Extensible Resource Identifier (XRI) Metadata Version 2.0, Committee Draft 01, March 2005 Declared XML Namespace(s) xri://$res xri://$xrds xri://$xrd XRI Resolution 2.0 Committee Draft 02 25 November 2007 Copyright © OASIS® 1993–2007.
    [Show full text]
  • OSCRE Industry Alliance Organizations Synopsis
    OSCRE Connecting the Real Estate Industry ALLIANCE ORGANIZATION SYNOPSIS OSCRE is the trading name of OSCRE Americas Inc., part of the OSCRE International global network supporting the Americas. OSCRE Americas Inc. is registered in Washington, District of Columbia. E-mail: [email protected] Web: www.oscre.org © 2003, 2004 OSCRE International. All Rights Reserved. Version History 1.0 Andy Fuhrman March 29, 2004 Document Creation 1.1 Andy Fuhrman April 4, 2004 Incorporated feedback from OSCRE International Executive Board 1.2 Chris Lees May 26, 2004 Section 2: Verbiage Modification OSCRE International OSCRE Americas PISCES Limited 2020 Pennsylvania Avenue, NW 7-8 Greenland Place Box #1024 LONDON, NW1 0AP Washington, DC 20006 www.pisces.co.uk www.oscre.org ALLIANCE ORGANIZATION SYNOPSIS © 2003-2004 OSCRE International. All Rights Reserved. 2 of 46 Contents 1 Mission ................................................................................................... 4 2 Industry Focus ......................................................................................... 4 3 Methodology ............................................................................................ 4 4 Document Purpose ................................................................................... 5 5 About OSCRE........................................................................................... 5 5.1 OSCRE International Executive Board Members ..................................... 6 5.2 Projected OSCRE Timeline .................................................................
    [Show full text]
  • Member of Security Technical Committees Spanning Federated Identity, Key Management, Health Care Privacy
    Security Standardization . Oasis Standards Consortium Geneva, 6-7 December Addressing security challenges on a global scale 2010 2 Speaker Anil Saldhana Co-Chair, Oasis Identity In The Cloud TC Member, Oasis IDTrust Steering Committee . Member of Security Technical Committees spanning Federated Identity, Key Management, Health Care Privacy . [email protected] Geneva, 6-7 December Addressing security challenges on a global scale 2010 3 About Oasis “Organization for the Advancement of Structured Information Standards” – Founded in 1993 as SGML Open – Not for profit consortium – Global Representation • 5000+ Participants. • 600+ Organizations/Individual Members. • 100+ Countries. Geneva, 6-7 December Addressing security challenges on a global scale 2010 4 Oasis Member Sections Member Sections include – IDTrust – Egov – Blue (SmartGrids/Intelligent Buildings) – WS-I etc. Geneva, 6-7 December Addressing security challenges on a global scale 2010 5 Oasis IDTrust Member Section Promotes greater understanding and adoption of standards for Identity and Trusted Infrastructure . Technologies, Policies and Practices Geneva, 6-7 December Addressing security challenges on a global scale 2010 6 Oasis IDTrust Member Section Technical Committees Identity Metasystems/Internet Identity . Identity In The Cloud (IDCloud) . Identity Metasystem Interoperability (IMI) . Extensible Resource Identifier(XRI) . XRI Data Interchange (XDI) Geneva, 6-7 December Addressing security challenges on a global scale 2010 7 Oasis IDTrust Member Section Technical Committees Encryption/Key Management . Key Mgmt. Interoperability Protocol (KMIP) . Enterprise Key Mgmt. Infrastructure (EKMI) Geneva, 6-7 December Addressing security challenges on a global scale 2010 8 Oasis IDTrust Member Section Technical Committees Trust/Privacy . Open Reputation Mgmt. Systems (ORMS) . Privacy Mgmt. Reference Model (PMRM) . Digital Signature Services Extended (DSS-X) .
    [Show full text]
  • An Introduction to XDI a White Paper for the OASIS XDI Technical Committee V2, April 12, 2004
    The Dataweb: An Introduction to XDI A White Paper for the OASIS XDI Technical Committee v2, April 12, 2004 Drummond Reed, Cordance Geoffrey Strongin, AMD Abstract XDI (XRI Data Interchange) is a new service for generalized distributed data sharing and mediation using XRIs (Extensible Resource Identifiers), a URI-compatible abstract identifier scheme developed by the OASIS XRI Technical Committee. The goal of XDI is to enable data from any data source to be identified, exchanged, linked, and synchronized into a machine-readable dataweb using XML documents just as content from any content source can linked into the human-readable Web using HTML documents today. Because the controls needed to mediate access and usage of shared data can be built right into every XDI link, the emergence of a global Dataweb has the potential to do for trusted data interchange what the Web did for open content exchange. This white paper presents several examples of classic cross-domain data sharing problems, explains how the Dataweb model can provide a generalized solution, and describes the key objectives of the newly formed OASIS XDI Technical Committee (http://www.oasis-open.org/committees/xdi). HTML HTML XML/ XML/ XDI XDI XDI link contract HTML HTML HTML HTML XML/ XML/ XML/ XML/ XDI XDI XDI XDI HTML HTML HTML HTML XML/ XML/ XML/ XML/ XDI XDI XDI XDI Website A Website B Dataweb Site A Dataweb Site B The Dataweb: An Introduction to XDI April 12, 2004 Page 2 Table of Contents INTRODUCTION.......................................................................................................................................3
    [Show full text]
  • Security for Future Networks: a Prospective Study of Aais
    Security for Future Networks : a Prospective Study of AAIs Hassane Aissaoui, Pascal Urien, Guy Pujolle, Fraga Joni da Silva, Böger Davi da Silva To cite this version: Hassane Aissaoui, Pascal Urien, Guy Pujolle, Fraga Joni da Silva, Böger Davi da Silva. Security for Future Networks : a Prospective Study of AAIs. IJNS, 2013, pp.CIT2013 Submission 6. hal-00841301 HAL Id: hal-00841301 https://hal.archives-ouvertes.fr/hal-00841301 Submitted on 4 Oct 2013 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Security for Future Networks : a Prospective Study of AAIs Hassane AISSAOUI MEHREZ, Pascal URIEN Guy PUJOLLE TELECOM-ParisTech : LTCI CNRS Laboratory CNRS, LIP6/UPMC Laboratory, IMT / TELECOM-ParisTech University Pierre and Marie Curie Paris VI 46, rue Barrault F 75634 Paris France 4 Place Jussieu, 75005 Paris, France Joni da Silva Fraga, Davi da Silva Böger Universidade Federal de Santa Catarina, Centro Tecnológico, Departamento de Engenharia Elétrica. LCMI/DAS/CTC - UFSC, C.P. : 476 88040-900 - Florianopolis, SC Brasil E-mails: {hassane.aissaoui, pascal.urien}@telecom-paristech.fr, [email protected], [email protected]. In Section 5 final considerations about the benefits Abstract: provided both to users and service providers, when identity The future Internet will rely heavily on virtualization and and User-Centric models are used in identity management, cloud networking.
    [Show full text]
  • The 7 Internet Identity Workshop 2008B BOOK of PROCEEDINGS
    The 7th Internet Identity Workshop 2008b November 10-12, 2008 BOOK OF PROCEEDINGS Version 1 Notes Gathered by Heidi Nobantu Saul, Complied by Kaliya Hamlin Notes in this book can be found online at http://iiw.idcommons.net/Notes_08b IIW is produced by Phil Windley, Doc Searls and Kaliya Hamlin Table of Contents for IIW 2008b INTRODUCTORY LETTERS..................................................................................................................................................................4 FROM MARY RUDDY – CHAIR OF THE IDENTITY COMMONS STEWARDS COUNCIL................................................................................4 FROM KALIYA HAMLIN – CO-PRODUCER AND FACILITATOR OF IIW .....................................................................................................5 INTRODUCTORY TALKS.......................................................................................................................................................................7 IDENTITY OVERVIEW – JOHANNES ERNST ...............................................................................................................................................7 OPENID – DAVID RECORDON.................................................................................................................................................................13 SAML – PAUL MADSEN .........................................................................................................................................................................15
    [Show full text]
  • The Venn of Identity Options and Issues in Federated Identity Management
    Identity Management The Venn of Identity Options and Issues in Federated Identity Management Federated identity management lets users dynamically distribute identity information across security domains, increasing the portability of their digital identities. It also raises new architectural challenges and significant security and privacy issues. EVE MALER espite aging and psychological and cosmetic Identity Sun changes, who you are as a person is fairly management Microsystems constant—Eve and Drummond will remain Eve and Drummond over time. The same and single sign-on DRUmmOND Disn’t true of your digital identity. Currently, eve@ Although many objects have digital identities—from Reed xmlgrrl.com is tied to Eve, for example, but might RFID-tagged equipment to software applications to Cordance later be tied to someone else or disappear entirely. companies—digital identities for humans raise the This is just one of the challenges people have with most interesting issues and challenges, whether in an digital identities. enterprise context or on the open Internet. Federated identity management is a set of tech- Large-enterprise IT departments view identities nologies and processes that let computer systems as the user accounts for employees (and others) that dynamically distribute identity information and they manage through a user store (often based on the delegate identity tasks across security domains. Fed- Lightweight Directory Access Protocol). As enterpris- erated identity is the means by which Web appli- es grow, management teams must synchronize their cations can offer users cross-domain single sign-on account stores, both to ensure proper account provi- (SSO), which lets them authenticate once and there- sioning and to govern users’ application access.
    [Show full text]
  • Business Information Systems
    + PA165 Enterprise Java 2013-2014 SOAP and WS* Webservices Bruno Rossi & Juha Rikkilä + 2 SOAP, in general terms Originally acronym for Simple Object Access Protocol, now a common name A communication protocol, designed to communicate via Internet Extends HTTP for XML messaging Provides data transport for Web services (SOAP, WSDL, UDDI) Exchanges complete documents or call a remote procedure Is used for broadcasting a message Is platform and language independent Is the XML way of defining what information gets sent and how + https://kore.fi.muni.cz/wiki/index.php/PA165/WebServices_(English) + 4 XML (Extensible Markup Language) created to structure, store, and transport data by defining a set of rules for encoding documents a format that is both human-readable and machine-readable defined in the XML 1.0 Specification produced by the W3C there are two current versions of XML. XML 1.0, currently in its fifth edition, and still recommended for general use XML 1.1, not very widely implemented and is recommended for use only by those who need its unique features + 5 XML emphasizes simplicity, generality, and usability over the Internet textual data format with Unicode support for the languages of the world focuses on documents, but is widely used for the representation of arbitrary data structures, for example in web services. many APIs for processing XML data several schema systems hundreds of XML-based languages (e.g. RSS, Atom, SOAP, and XHTML) the default for many office-productivity tools, including Microsoft Office
    [Show full text]
  • Description Read-1159341885-Webservice.Pdf
    PUCL6HXUDII4 Doc // Webservice W ebservice Filesize: 8.85 MB Reviews Simply no phrases to clarify. It is really basic but surprises from the 50 percent of the ebook. Once you begin to read the book, it is extremely difficult to leave it before concluding. (Mr. Noah Cummerata IV) DISCLAIMER | DMCA ZDMMQPRROTBF / Book » Webservice WEBSERVICE Reference Series Books LLC Jan 2013, 2013. Taschenbuch. Book Condition: Neu. 246x187x7 mm. Neuware - Quelle: Wikipedia. Seiten: 52. Kapitel: SOAP, Universal Description, Discovery and Integration, XML-RPC, Serviceorientierte Architektur, Amazon Web Services, Web Services Description Language, WS-Business Process Execution Language, Service Component Architecture, Representational State Transfer, Apache Axis, Sensor Observation Service, Mashup, W3C Geolocation API, Dienstekomposition, WS-Policy, JSON-RPC, Amazon CloudWatch, Zustellserver, Google App Engine, WS- , Soware-Ökosystem, Hessian, Apache CXF, WS-Transaction, Web Ontology Language for Web Services, JAX-WS, WS-Reliable Messaging, Scalr, Security Assertion Markup Language, WS-Notification, WS-Enumeration, JAX-RS, WS-Security, WS-Trust, Unternehmensserviceportal, SoapUI, Direct Internet Message Encapsulation, XFire, WS-BPEL4People, XL, XDI, Devices Profile for Web Services, WS- Distributed Management, Burlap, WebHooks, SOAP with Attachments, Semantic Web Services, EbXML, SOAP Message Transmission Optimization Mechanism, WS-Agreement, WS-Addressing, WS-HumanTask, Sensor Web Enablement, WS-SecurityPolicy, WS-Interoperability, JAX-RPC, WS- Discovery,
    [Show full text]
  • An XRI Naming System for Dynamic and Federated Clouds: a Performance Analysis
    J Internet Serv Appl (2011) 2:191–205 DOI 10.1007/s13174-011-0038-7 SI: CLOUD COMPUTING An XRI naming system for dynamic and federated clouds: a performance analysis Antonio Celesti · Massimo Villari · Antonio Puliafito Received: 19 November 2010 / Accepted: 19 September 2011 / Published online: 15 October 2011 © The Brazilian Computer Society 2011 Abstract Cloud platforms are dynamic, self-optimizing, competitive on the market [1]. Nowadays, cloud providers continuously changing environments where resources can supply many kinds of Infrastructure as a Service (IaaS), Plat- be composed with other ones in order to provide many form as a Service (PaaS), and Software as a Service (SaaS) types of services to their users, e.g., companies, govern- to their users, e.g., desktop/mobile clients, companies, gov- ments, organizations, and desktop/mobile clients. In order ernments, organizations, and other clouds. Such services can to enable cloud platforms to manage and control their as- be arranged composing and orchestrating several Virtual En- sets, they need to name, identify, and resolve their vir- vironments (VEs) or Virtual Machines (VMs) through Vir- tual resources in different operating contexts. In such a tual Machine Monitors commonly known as hypervisors scenario, naming, resource location, and information re- which are spread over a network and orchestrated by Cloud trieval raise several issues regarding name space man- Manager (CM) platforms [2, 40]. agement. This paper aims to propose a standard practice The overwhelming innovation of cloud computing is that for the implementation of a cloud naming system based cloud platforms can react to events internally rearranging on the eXtensible Resource Identifier (XRI) technology.
    [Show full text]