UserPreferences

GssPolicies/InumberPersistence

I-Number Persistence

TableOfContents

  1. Motivation
  2. Background
  3. Global I-Number Persistence Policy
  4. Global I-Number Delegated Control Policy
  5. Implications
    1. Persistence in Federated Identifiers
    2. Account Delegation
  6. Related Policies

1. Motivation

These policies specify the rules governing persistence of Global I-Numbers. They are motivated by the need to:

2. Background

I-Numbers differ from I-Names in one key respect: the former is persistent (non-reassignable) while the latter is reassignable. In other words, once assigned to represent a resource, an I-Number should never be reassigned to represent a different resource. Note that this does not mean that the binding between an I-Number and a specific resource representation cannot be changed; indeed, a primary purpose of I-Numbers is to ensure persistent identification of the same logical resource even it moves or changes its address(es) on the network. It simply means the I-Number will not be reassigned to represent a different logical resource (a constraint that does NOT apply to I-Names).

3. Global I-Number Persistence Policy

Once registered to represent a Resource, a Global I-Number MUST NOT be reassigned to represent a different Resource. Specifically, a Global I-Number MUST NOT be transferred between Registrants. Note that this does not mean that the original Registrant of a Global I-Number may not delegate control of a Global I-Number account to another party. Indeed, delegated control of Global I-Number accounts is essential for Global I-Numbers to continue to represent certain Resources (such as people or an organizations) after their natural lifetimes. (See the Global I-Number Delegated Control Policy.)

4. Global I-Number Delegated Control Policy

To meet the requirements of the Global I-Number Persistence Policy, GRSPs and XDI.ORG-Accredited I-Brokers MUST provide a means for Registrants to delegate control of their Global I-Number to other Registrants acting as Delegates. The GSS Operational Specifications (GssOpSpecs) MUST provide a means for Delegate authentication.

5. Implications

5.1. Persistence in Federated Identifiers

Persistence is an operational requirement that must be observed by all authorities who participate in segments of a federated persistent identifier. Although XDI.ORG policies and practices can ensure persistence at the Global Registry level, persistence of other segments of an XRI must be enforced by XDI.ORG-Accredited I-Brokers and other authorities that participate in the chain of segments composing a persistent XRI.

5.2. Account Delegation

Delegated control of i-name and i-number accounts at all levels should be a standard feature offered by I-Brokers. Typically this will be accomplished through establishing account links mediated by XDI Link Contracts. Depending on the policies of the I-Broker, account linking may only be available within the domain of a single I-Broker, or it may only be available with selected other I-Brokers.

6. Related Policies