RFC 3722 (rfc3722) - Page 1 of 8
String Profile for Internet Small Computer Systems Interface (iSCSI) Names
Alternative Format: Original Text Document
Network Working Group M. Bakke
Request for Comments: 3722 Cisco
Category: Standards Track April 2004
String Profile for Internet Small Computer
Systems Interface (iSCSI) Names
Status of this Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract
This document describes how to prepare internationalized iSCSI names
to increase the likelihood that name input and comparison work in
ways that make sense for typical users throughout the world.
The Internet Small Computer Systems Interface (iSCSI) protocol
provides a way for hosts to access SCSI devices over an IP network.
The iSCSI end-points, called initiators and targets, each have a
globally-unique name that must be transcribable, as well as easily
compared.
1. Introduction
The iSCSI protocol [RFC 3720] provides a way for hosts to access SCSI
[SAM2] devices over an IP network. The iSCSI end-points, called
initiators and targets, each have a globally-unique name, defined in
[RFC 3721].
An iSCSI name is a string of UTF-8 [RFC 3629] characters that includes
a type designator, a naming authority based on domain names, and a
unique part within the naming authority. The unique part may be
generated based on anything the naming authority deems useful, and
may include user input.
These names may need to be transcribed (sent between two
administrators via email, voice, paper, etc), so a case-insensitive
comparison would be desirable. However, these names must often be
Bakke Standards Track