K. Sollins and L. Masinter. Functional requirements for uniform resource names, Dec 1994. RFC 1737. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
First 50 documents Next 50
Julian Satran Expires June 2003 1 IP Storage Working.. - Costa Sapuntzakis Cisco (Correct)
....same for the target regardless of the physical portion being addressed. This assists iSCSI initiators in determining that the two targets it has discovered are really two paths to the same target. The iSCSI name is designed to fulfill the functional requirements for Uniform Resource Names (URN) [RFC1737]. For example, it is required that the name have a global scope, be independent of address or location, and be persistent and globally unique. Names must be extensible and scalable with the use of naming authorities. The name encoding should be both human and machine readable. See [RFC1737] for ....
....(URN) RFC1737] For example, it is required that the name have a global scope, be independent of address or location, and be persistent and globally unique. Names must be extensible and scalable with the use of naming authorities. The name encoding should be both human and machine readable. See [RFC1737] for further requirements. 3.2.6.2 iSCSI Name Encoding An iSCSI name MUST be a UTF 8 encoding of a string of Unicode characters with the following properties: It is in Normalization Form C (see Unicode Normalization Forms [UNICODE] It only contains characters allowed by the output of ....
K. Sollins, L. Masinter "Functional Requirements for Uniform Resource Names".
Julian Satran Expires August 2003 1 - Ip Storage Working (Correct)
....Julian Satran Expires August 2003 33 physical portion being addressed. This assists iSCSI initiators in determining that the two targets it has discovered are really two paths to the same target. The iSCSI name is designed to fulfill the functional requirements for Uniform Resource Names (URN) [RFC1737]. For example, it is required that the name have a global scope, be independent of address or location, and be persistent and globally unique. Names must be extensible and scalable with the use of naming authorities. The name encoding should be both human and machine readable. See [RFC1737] for ....
....(URN) RFC1737] For example, it is required that the name have a global scope, be independent of address or location, and be persistent and globally unique. Names must be extensible and scalable with the use of naming authorities. The name encoding should be both human and machine readable. See [RFC1737] for further requirements. 3.2.6.2 iSCSI Name Encoding An iSCSI name MUST be a UTF 8 encoding of a string of Unicode characters with the following properties: It is in Normalization Form C (see Unicode Normalization Forms [UNICODE] It only contains characters allowed by the output of ....
K. Sollins, L. Masinter "Functional Requirements for Uniform Resource Names".
Architectural Principles of Uniform Resource Name Resolution - Sollins (1998) (25 citations) Self-citation (Sollins) (Correct)
No context found.
Sollins, K., and L. Masinter, "Functional Requirements for Uniform Resource Names", RFC 1738, December 1994.
Unknown - Self-citation (Masinter) (Correct)
No context found.
Sollins, K. and L. Masinter, "Functional Requirements for Uniform Resource Names", RFC 1737, MIT/LCS, Xerox Corporation, December 1994. <URL:ftp://ds.internic.net/rfc/rfc1737.txt>
Untangling the Web from DNS - Michael Walfish Hari (2004) (7 citations) (Correct)
No context found.
K. Sollins and L. Masinter. Functional requirements for uniform resource names, Dec 1994. RFC 1737.
Robust Hyperlinks Cost Just Five Words Each - Thomas Phelps And (4 citations) (Correct)
No context found.
K. Sollins and L. Masinter. Functional Requirements for Uniform Resource Names, Network Working Group Request for Comments 1737, December 1994.
What is Information Discovery About? - Proper Id Research (1999) (Correct)
No context found.
K. Sollins and L. Masinter. Functional requirements for uniform resource names. Technical Report RFC1737, IETF Network Working Group, http://www.ietf.org/rfc/rfc1737.txt, December 1994.
What is Information Discovery About? - Proper Id Research (1999) (Correct)
No context found.
K. Sollins and L. Masinter. Functional requirements for uniform resource names. Technical Report RFC1737, IETF Network Working Group, http://www.ietf.org/rfc/rfc1737.txt, December 1994.
A Layered Naming Architecture for the Internet - Balakrishnan.. (2004) (5 citations) (Correct)
No context found.
K. Sollins and L. Masinter. Functional requirements for Uniform Resource Names, December 1994. RFC 1737.
A Layered Naming Architecture for the Internet - Balakrishnan.. (2004) (5 citations) (Correct)
No context found.
K. Sollins and L. Masinter. Functional requirements for Uniform Resource Names, Dec 1994. RFC 1737.
Unknown - As Uniform Resource (Correct)
No context found.
Sollins, K., and L. Masinter, "Functional Requirements for Uniform Resource Names", RFC 1737, December
A Layered Naming Architecture for the Internet - Hari Balakrishnan Hari (2004) (5 citations) (Correct)
No context found.
K. Sollins and L. Masinter. Functional requirements for Uniform Resource Names, December 1994. RFC 1737.
Using DHTs to Untangle the Web from DNS - Michael Walfish Mit (Correct)
No context found.
K. Sollins and L. Masinter. Functional requirements for uniform resource names, Dec 1994. RFC 1737.
Network Working Group M. Mealling Request for.. - Dynamic Delegation.. (Correct)
No context found.
Sollins, K. and L. Masinter, "Functional Requirements for Uniform Resource Names", RFC 1737, December 1994.
Network Working Group S. Sun Request for Comments: 3650 L.. - Status Of This (Correct)
No context found.
Sollins, K. and L. Masinter, "Functional Requirements for Uniform Resource Names", RFC 1737, December 1994.
A Layered Naming Architecture for the Internet - Balakrishnan.. (2004) (5 citations) (Correct)
No context found.
K. Sollins and L. Masinter. Functional requirements for Uniform Resource Names, Dec 1994. RFC 1737.
Untangling the Web from DNS - Walfish, Balakrishnan, Shenker (2004) (7 citations) (Correct)
No context found.
K. Sollins and L. Masinter. Functional requirements for uniform resource names, Dec 1994. RFC 1737.
Untangling the Web from DNS - Michael Walfish Hari (2004) (7 citations) (Correct)
No context found.
K. Sollins and L. Masinter. Functional requirements for uniform resource names, Dec 1994. RFC 1737.
Unknown - (Correct)
No context found.
Sollins, K. and L. Masinter, "Functional Requirements for Uniform Resource Names", RFC 1737, December 1994.
Trustworthy 100-Year Digital Objects: Syntax and Sematics -.. - Gladney (2003) (Correct)
No context found.
K. Sollins and L. Masinter, Functional Requirements for Uniform Resource Names, IETF RFC 1737, 1994.
Network Working Group S. Rozenfeld Request for Comments.. - Urn Uniform Resource (Correct)
No context found.
Sollins, K. and L. Masinter, "Functional Requirements for Uniform Resource Names", RFC 1737, December 1994.
Network Working Group R. Moats Request for Comments: 2141 ATT .. - Status Of This (Correct)
No context found.
Sollins, K. and L. Masinter, "Functional Requirements for Uniform Resource Names," RFC 1737. December 1994.
Julian Satran Expires February 2003 1 - Ips Julian Satran (Correct)
No context found.
K. Sollins, L. Masinter "Functional Requirements for Uniform Resource Names".
Unknown - (Correct)
No context found.
K. Sollins, L. Masinter "Functional Requirements for Uniform Resource Names".
iSCSI - Satran, Sapuntzakis, Chadalapaka.. (2002) (Correct)
No context found.
K. Sollins, L. Masinter "Functional Requirements for Uniform Resource Names".
First 50 documents Next 50
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC