The aim of this document is to provide an overview of best practices in on-demand provisioning of infrastructure services that includes both traditional Network Resources Provisioning Systems (NRPS) and emerging Cloud based infrastructure services. These provisioning processes must be both sufficiently explicit and flexible to dynamically instantiate complex task or project oriented infrastructures comprising of compute, storage, and application resources, as well network infrastructures interconnect them.

The proposed document summarises discussions among members of the OGF ISoD Research Group and aims to facilitate conversations on achieving interoperability, and effective use and development of modern and future infrastructure services provisioning systems.

The goal of the Authorization Interoperability activity is providing interoperability between middleware and authorization infrastructures. This is achieved by designing and implementing an authorization protocol common to OSG VO services, EGEE, Globus, and Condor. This protocol is based on the SAML profile of XACML v2.0 [XACML]. The C library that implements the profile is provided by the Globus Toolkit security group; the JAVA library by the SWITCH group of EGEE.

The authorization protocol is used by Policy Enforcement Points (PEP), i.e. resource gateways, to interact with Policy Decision Points (PDP), i.e. repository of authorization policies. For each access request, the PDP informs the PEP on whether access is granted or denied and the conditions to be enforced if access if granted. These conditions are expressed in the form of XACML Obligations and are the mechanism to restrict privileges at Grid resources.

URNs in the OGF namespace take the form urn:ogf:<snid>:<subnamespace-specific-string>.
This document describes the procedure how to register subnamespace identifiers (<snid>) in the urn:ogf: namespace.

This document defines the types of OGF documents and the development and review processes for each type. This document obsoletes GFD.1 and replaces it as the description of OGF community practice surrounding the document series. The process reflects several years of experience with OGF document publication, and borrows heavily from the Internet Engineering Task Force Request for Comments document process.