1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
|
<pre>Network Working Group M. Mealling
Request for Comments: 3043 Network Solutions, Inc.
Category: Informational January 2001
<span class="h1">The Network Solutions Personal Internet Name (PIN): A URN Namespace</span>
<span class="h1">for People and Organizations</span>
Status of this Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2001). All Rights Reserved.
Abstract
This document describes a Uniform Resource Name (URN) namespace that
is engineered by Network Solutions, Inc. for naming people and
organizations.
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
In many cases Network Solutions' maintained directory applications
require some unique and persistent way to talk about an individual or
organization. For example, white pages style services need to
determine if one entry is distinct from another even if some of the
data happens to be the same. Also, e-commerce authentication
mechanisms needs to identify a user and/or company uniquely and
possibly over large spans of time. In many cases a customer
relationship can last several decades. Such long term customer
relationships can outlast any specific email address, Internet
service provider, surname, or possibly even the DNS itself.
The intent for these applications is that they be used and integrated
into other, non-NSI maintained applications in much the same way that
domain-names that exist in Network Solution's database are primarily
used in application that Network Solutions is _not_ involved in. In
much the same way that ISBNs are maintained by specific entities but
used in widely varying applications, NSI's PIN namespace is intended
to be used in many applications where there is a need for a well
maintained identifier that names a person or organization.
<span class="grey">Mealling Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc3043">RFC 3043</a> NSI PIN URN Namespace January 2001</span>
A URN namespace is uniquely suited to solve the persistent
identification needs of these applications since they are also
required to be unique and persistent. The availability of a
standardized resolution mechanism makes it possible for other
applications to reference and resolve PIN URNs in their own systems
in an open, non-proprietary way.
This namespace specification is for a formal namespace.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Specification Template</span>
Namespace ID:
"pin" requested.
Registration Information:
Registration Version Number: 1
Registration Date: 2000-09-30
Declared registrant of the namespace:
Network Solutions
505 Huntmar Park Drive
Herndon, VA 22070
Declaration of structure:
The structure of the NSS is a flat space of alphanumeric
characters which have no knowable structure outside of the
context of Network Solutions internal resolver. Future changes
to the assignment methods may allow others to assign
sub-spaces of the flat namespace but again, this knowledge is
only valid internally and should never be inferred or relied
upon externally.
Relevant ancillary documentation:
None
Identifier uniqueness considerations:
Identifiers are assigned by Network Solutions proprietary
registration system in a way that guarantees uniqueness. At
this time the algorithm is to iterate from the last assigned
number by some positive integer. In the future this algorithm
may change to incorporate a full range of alphanumeric
<span class="grey">Mealling Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc3043">RFC 3043</a> NSI PIN URN Namespace January 2001</span>
elements. In either case, the system will compare the newly
created identifier with all of the previous ones to ensure
that it has not already been assigned.
Identifier persistence considerations:
The assignment process guarantees that names are not reassigned
and that the binding between the name and the person or
organization is permanent, regardless of any personal name
changes, corporate restructuring, death or dissolution.
Process of identifier assignment:
Names are granted via Network Solutions proprietary registration
procedures.
Process of identifier resolution:
PIN URNs are resolved via URN resolvers run by Network
Solutions. Since a PIN URN identifies a person or
organization, resolving a PIN URN will only be able to return
information from an electronic proxy that is merely a
representation of the actual person or organization being
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 specified
Scope:
Global
<span class="grey">Mealling Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc3043">RFC 3043</a> NSI PIN URN Namespace January 2001</span>
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Examples</span>
The following examples are not guaranteed to be real. They are
listed for pedagogical reasons only.
URN:pin:bs4321234
URN:pin:324kj5hkj45
URN:pin:mm2136
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
Since the URNs in this namespace are opaque there are no additional
security considerations other than those normally associated with the
use and resolution of URNs in general.
It is noted however that attempting to resolve a PIN URN through a
resolver other than the one provided by Network Solution is error
prone. In any case it is not considered authoritative.
References
[<a id="ref-1">1</a>] Moats, R., "URN Syntax", <a href="./rfc2141">RFC 2141</a>, May 1997.
Author's Address
Michael Mealling
Network Solutions, Inc.
505 Huntmar Park Drive
Herndon, VA 22070
US
Phone: +1 770 935 5492
EMail: michaelm@netsol.com
URI: <a href="http://www.netsol.com">http://www.netsol.com</a>
<span class="grey">Mealling Informational [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc3043">RFC 3043</a> NSI PIN URN Namespace January 2001</span>
Full Copyright Statement
Copyright (C) The Internet Society (2001). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
Mealling Informational [Page 5]
</pre>
|
