As per Relevance of the word identifier, we have this rfc below:
Network Working Group M.
Request for Comments: 3043 Network Solutions, Inc
Category: Informational January 2001
The Network Solutions Personal Internet Name (PIN): A URN
for People and
Status of this
This memo provides information for the Internet community. It
not specify an Internet standard of any kind. Distribution of
memo is unlimited
Copyright
Copyright (C) The Internet Society (2001). All Rights Reserved
This document describes a Uniform Resource Name (URN) namespace
is engineered by Network Solutions, Inc. for naming people
organizations
1.
In many cases Network Solutions' maintained directory
require some unique and persistent way to talk about an individual
organization. For example, white pages style services need
determine if one entry is distinct from another even if some of
data happens to be the same. Also, e-commerce
mechanisms needs to identify a user and/or company uniquely
possibly over large spans of time. In many cases a
relationship can last several decades. Such long term
relationships can outlast any specific email address,
service provider, surname, or possibly even the DNS itself
The intent for these applications is that they be used and
into other, non-NSI maintained applications in much the same way
domain-names that exist in Network Solution's database are
used in application that Network Solutions is _not_ involved in.
much the same way that ISBNs are maintained by specific entities
used in widely varying applications, NSI's PIN namespace is
to be used in many applications where there is a need for a
maintained identifier that names a person or organization
Mealling Informational [Page 1]
RFC 3043 NSI PIN URN Namespace January 2001
A URN namespace is uniquely suited to solve the
identification needs of these applications since they are
required to be unique and persistent. The availability of
standardized resolution mechanism makes it possible for
applications to reference and resolve PIN URNs in their own
in an open, non-proprietary way
This namespace specification is for a formal namespace
2. Specification
Namespace ID
"pin" requested
Registration Information
Registration Version Number: 1
Registration Date: 2000-09-30
Declared registrant of the namespace
Network
505 Huntmar Park
Herndon, VA 22070
Declaration of structure
The structure of the NSS is a flat space of
characters which have no knowable structure outside of
context of Network Solutions internal resolver. Future
to the assignment methods may allow others to
sub-spaces of the flat namespace but again, this knowledge
only valid internally and should never be inferred or
upon externally
Relevant ancillary documentation
Identifier uniqueness considerations
Identifiers are assigned by Network Solutions
registration system in a way that guarantees uniqueness.
this time the algorithm is to iterate from the last
number by some positive integer. In the future this
may change to incorporate a full range of
Mealling Informational [Page 2]
RFC 3043 NSI PIN URN Namespace January 2001
elements. In either case, the system will compare the
created identifier with all of the previous ones to
that it has not already been assigned
Identifier persistence considerations
The assignment process guarantees that names are not
and that the binding between the name and the person
organization is permanent, regardless of any personal
changes, corporate restructuring, death or dissolution
Process of identifier assignment
Names are granted via Network Solutions proprietary
procedures
Process of identifier resolution
PIN URNs are resolved via URN resolvers run by
Solutions. Since a PIN URN identifies a person
organization, resolving a PIN URN will only be able to
information from an electronic proxy that is merely
representation of the actual person or organization
named
Rules for Lexical Equivalence
The entire URN is case-insensitive
Conformance with URN Syntax
There are no additional characters reserved
Validation mechanism
None additional to resolution
Scope
Mealling Informational [Page 3]
RFC 3043 NSI PIN URN Namespace January 2001
3.
The following examples are not guaranteed to be real. They
listed for pedagogical reasons only
URN:pin:bs4321234
URN:pin:324kj5hkj45
URN:pin:mm2136
4. Security
Since the URNs in this namespace are opaque there are no
security considerations other than those normally associated with
use and resolution of URNs in general
It is noted however that attempting to resolve a PIN URN through
resolver other than the one provided by Network Solution is
prone. In any case it is not considered authoritative
[1] Moats, R., "URN Syntax", RFC 2141, May 1997.
Author's
Michael
Network Solutions, Inc
505 Huntmar Park
Herndon, VA 22070
Phone: +1 770 935 5492
EMail: michaelm@netsol.
URI: http://www.netsol.
Mealling Informational [Page 4]
RFC 3043 NSI PIN URN Namespace January 2001
Full Copyright
Copyright (C) The Internet Society (2001). All Rights Reserved
This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English
The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns
This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Funding for the RFC Editor function is currently provided by
Internet Society
Mealling Informational [Page 5]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
