CCNP Namespace

A CCNP Namespace is a hierarchical portion of the global CCNP content namespace that is delegated to and under the exclusive control of an individual user or organization. Unlike traditional domain names in the legacy DNS system, a CCNP namespace represents a personal identity space where the holder has complete authority over content naming, publication, and management within their assigned namespace segment.

Structure and Format

CCNP namespaces follow the same hierarchical naming convention as other CCNP content names, with namespace segments separated by forward slashes. A personal namespace typically follows the pattern username.provider.net, where:

username is the unique identifier assigned to the user
provider is the Namespace Provider that delegates the namespace
net is the top-level segment indicating network infrastructure

For example, a user named "alex" with a namespace provided by "example" would have the namespace /net.example.alex/, giving them full control over all content names beginning with that prefix.

Personal Namespace Capabilities

Once delegated a personal namespace, users gain several important capabilities:

Content Publication

Users can publish any content under their namespace without requiring additional permission or validation. A user with /net.example.alex/ can create content names like /net.example.alex/blog/, /net.example.alex/projects/, or /net.example.alex/gallery/photo.jpg at their discretion.

Sub-delegation

Advanced users can create sub-namespaces for their own projects or for delegation to others. A user might create /net.example.alex/projects/game/ to delegate control of a specific project namespace to a collaborator.

Identity and Reputation

Personal namespaces serve as the primary identity mechanism in the CCNP ecosystem. Content published under a user's namespace is cryptographically associated with that namespace, allowing verification of authorship and building reputation over time.

Obtaining a Personal Namespace

Personal namespaces are obtained through Namespace Providers, either as standalone services or as part of broader personal server offerings. Many providers offer free namespaces with basic features, while premium namespaces may include additional storage, custom sub-domains, and enhanced security features.

Some users opt to run their own personal servers and operate self-hosted namespaces, giving them complete control without depending on third-party providers. This approach requires more technical expertise but provides maximum autonomy.

Relationship to CCNP Namespace Hierarchy

Personal namespaces exist within the broader CCNP namespace hierarchy, beneath the /net/ top-level segment. This structure parallels the DNS domain name system but with semantic meaning tied to user identity rather than organizational registration. TheNamespace Provider maintains authority over the second-level segment (e.g., /net.example/), while the user controls their specific namespace (e.g., /net.example.alex/).