< draft-mealling-pin-urn-00.txt		draft-mealling-pin-urn-01.txt >
	Network Working Group M.M. Mealling		Network Working Group M.M. Mealling
	Internet-Draft Network Solutions, Inc.		Internet-Draft Network Solutions, Inc.
	Expires: September 30, 2000 April 2000		Expires: March 27, 2001 September 26, 2000
	The Network Solutions Personal Internet Name (PIN): A URN Namespace		The Network Solutions Personal Internet Name (PIN): A URN Namespace
	for People and Organizations		for People and Organizations
	draft-mealling-pin-urn-00.txt		draft-mealling-pin-urn-01.txt
	Status of this Memo		Status of this Memo
	This document is an Internet-Draft and is NOT offered in accordance		This document is an Internet-Draft and is NOT offered in accordance
	with Section 10 of RFC2026, and the author does not provide the IETF		with Section 10 of RFC2026, and the author does not provide the IETF
	with any rights other than to publish as an Internet-Draft.		with any rights other than to publish as an Internet-Draft.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that		Task Force (IETF), its areas, and its working groups. Note that
	other groups may also distribute working documents as		other groups may also distribute working documents as
	skipping to change at page 1, line 33 ¶		skipping to change at page 1, line 33 ¶
	months and may be updated, replaced, or obsoleted by other documents		months and may be updated, replaced, or obsoleted by other documents
	at any time. It is inappropriate to use Internet-Drafts as reference		at any time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt		http://www.ietf.org/ietf/1id-abstracts.txt
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.		http://www.ietf.org/shadow.html.
	This Internet-Draft will expire on September 30, 2000.		This Internet-Draft will expire on March 27, 2001.
	Abstract		Abstract
	This document describes a URN namespace that is engineered by		This document describes a URN namespace that is engineered by
	Network Solutions, Inc for naming people and organizations.		Network Solutions, Inc for naming people and organizations.
	1. Introduction		1. Introduction
	In many cases, Network Solutions' directory applications require		In many cases Network Solutions' maintained directory applications
	some unique and persistent way to talk about an individual or		require some unique and persistent way to talk about an individual
	organization. For example, white pages services need to determine if		or organization. For example, white pages style services need to
	one user is distinct from another even if some of the data happens		determine if one entry is distinct from another even if some of the
	to be the same. Also, e-commerce authentication mechanisms need to		data happens to be the same. Also, e-commerce authentication
	identify a user uniquely and possibly over large spans of time. In		mechanisms needs to identify a user and/or company uniquely and
	many cases a customer relationship can last several decades. Such		possibly over large spans of time. In many cases a customer
	long term customer relationships can outlast any specific email		relationship can last several decades. Such long term customer
	address, Internet service provider, surname, or possibly even the		relationships can outlast any specific email address, Internet
	DNS itself.		service provider, surname, or possibly even the DNS itself.
	URNs are a uniquely suited solution for this due to the requirement		The intent for these applications is that they be used and
	that they also be unique and permanent. In addition, the		integrated into other, non-NSI maintained applications in much the
	availability of a standardized resolution mechanism makes it		same way that domain-names that exist in Network Solution's database
	possible for vastly different systems to utilize the PIN URN without		are primarily used in application that Network Solutions is _not_
	needing to utilize an application or protocol specific element.		involved in. In much the same way that ISBNs are maintained by
			specific entities but used in widely varrying 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.
			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.		This namespace specification is for a formal namespace.
	2. Specification Template		2. Specification Template
	Namespace ID:		Namespace ID:
	"pin" requested.		"pin" requested.
	Registration Information:		Registration Information:
	Registration Version Number: 1		Registration Version Number: 1
	Registration Date: 2000-04-30		Registration Date: 2000-09-30
	Declared registrant of the namespace:		Declared registrant of the namespace:
	Michael Mealling
	michaelm@netsol.com
	Network Solutions		Network Solutions
	505 Huntmar Park Drive		505 Huntmar Park Drive
	Herndon, VA 22070		Herndon, VA 22070
	Declaration of structure:		Declaration of structure:
	The structure of the NSS is a flat space of alphanumeric		The structure of the NSS is a flat space of alphanumeric
	characters which have no knowable structure outside of the		characters which have no knowable structure outside of the
	context of Network Solutions internal resolver.		context of Network Solutions internal resolver. Future changes
			to the assignement methods may allow others to assign
			sub-spaces of the flat namesapce but again, this knowledge is
			only valid internally and should never be inferred or relied
			upon externally.
	Relevant ancillary documentation:		Relevant ancillary documentation:
	None		None
	Identifier uniqueness considerations:		Identifier uniqueness considerations:
	Identifiers are assigned by Network Solutions proprietary		Identifiers are assigned by Network Solutions proprietary
	registration system in a way that guarantees uniqueness.		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
			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:		Identifier persistence considerations:
	The assignment process guarantees that names are not reassigned		The assignment process guarantees that names are not reassigned
	and that the binding between the name and the entity named is		and that the binding between the name and the person or
	permanent.		organization is permanent, regardless of any personal name
			changes, corporate restructuring, death or dissoluion..
	Process of identifier assignment:		Process of identifier assignment:
	Names are granted via Network Solutions proprietary registration		Names are granted via Network Solutions proprietary registration
	procedures.		procedures.
	Process of identifier resolution:		Process of identifier resolution:
	PIN URNs are resolved via URN resolvers run by Network		PIN URNs are resolved via URN resolvers run by Network
	Solutions. The data and databases used by those resolvers is		Solutions. Since a PIN URN identifies a person or
	proprietary data and can only be accessed by the resolver.		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:		Rules for Lexical Equivalence:
	The entire URN is case-insensitive.		The entire URN is case-insensitive.
	Conformance with URN Syntax:		Conformance with URN Syntax:
	There are no additional characters reserved.		There are no additional characters reserved.
	Validation mechanism:		Validation mechanism:
	skipping to change at page 3, line 21 ¶		skipping to change at page 3, line 56 ¶
	URN:pin:324kj5hkj45		URN:pin:324kj5hkj45
	URN:pin:mm2136		URN:pin:mm2136
	4. Security Considerations		4. Security Considerations
	Since the URNs in this namespace are opaque there are no additional		Since the URNs in this namespace are opaque there are no additional
	security considerations other than those normally associated with		security considerations other than those normally associated with
	the use and resolution of URNs in general.		the use and resolution of URNs in general.
	It is noted however that attempting to resolve a PIN URN through a		It is noted however that attempting to resolve a PIN URN through a
	resolver other than the one provided by Network Solution is prone to		resolver other than the one provided by Network Solution is error
	error and is not considered authoritative.		prone. In any case it is not considered authoritative.
	References		References
	[1] Moats, R., "URN Syntax", RFC 2141, May 1997.		[1] Moats, R., "URN Syntax", RFC 2141, May 1997.
	Author's Address		Author's Address
	Michael Mealling		Michael Mealling
	Network Solutions, Inc.		Network Solutions, Inc.
	505 Huntmar Park Drive		505 Huntmar Park Drive
End of changes. 12 change blocks.
	29 lines changed or deleted		52 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/