Proposal for IEEE company_id based formats for FC-PH world-wide identifiers
Larry Chen
larryc at maxstrat.com
Wed Dec 11 20:49:12 PST 1996
* From the SCSI Reflector (scsi at symbios.com), posted by:
* Larry Chen <larryc at maxstrat.com>
*
Bob,
I believe the SPC/SPC-2 document needs to be changed
to reflect the 128-bit IEEE registered extended format.
Table 113 - Identifier type
value description
4 The identifier field contains a FC-PH
128-bit Name_Identifier field as defined
in ..... In this case, the identifier length
shall be set to 16.
On Wed, 27 Nov 1996 13:08:19 -0800 Bob Snively wrote:
>
>To: SCSI reflector (scsi at symbios.com)
> Fibre Channel reflector (fc at network.com)
> IEEE (stds.rac at ieee.org)
>
>From: Bob Snively
>
>Date: November 27, 1996
>
>Subject: Proposal for identifier formats based on IEEE registration
>
>
>1.0 INFORMATIONAL OVERVIEW:
>
>I have been asked by the Fibre Channel working group to assemble a
>proposal for additional worldwide name formats. IEEE has accepted in
>principle the use of the IEEE company_id as a registration mechanism for
>Fibre Channel and for SCSI devices that use the Fibre Channel formats.
>
>Two items are required to complete this agreement. First, the formats
>described in this proposal must be added to the two IEEE formats already
>described in FC-PH. This proposal should be included in the appropriate
>edition of FC-PH or FC-AL. Second, tutorials must be prepared that
>explain to users of the IEEE company_id how to create Fibre Channel
>and SCSI identifiers.
>
>2.0 OVERVIEW OF ADDITIONS PROPOSED TO THE STRUCTURE
>
>To facilitate and simplify the use of the IEEE registration facility,
>two new Fibre Channel worldwide name formats are proposed by this
>document. The formats will be identified by two new NAA values.
>
>One provides a simple to manage 60 bit id. The high order bits
>(bits 59 - 36) contain the 24-bit IEEE identifier. The remaining bits
>are guaranteed to be unique for each worldwide name by the assignee of
>the identifier. The proposal defines this using an NAA field
>value of 0101.
>
>The second provides a simple to manage 124 bit id, separated into two
>octlets. The first octlet uses the same format as above. The
>additional 64-bits are also managed by the assignee of the identifier,
>but may be managed such that a relatively sparse name space is created.
>The actual location of the additional 64-bit field is not specified
>within the present FC-PH definitions, but is specified when using the
>FC-PH identifier within a SCSI identifier field. This allows the field
>to be used within FCP supported RAID devices and allows future
>specification of a native 124-bit id in Fibre Channel standards.
>
>
>3.0 PROPOSED ADDITION TO FC-PH
>
>The clause corresponding to 19.3.1, table 41, has two additional lines
>added:
>
>
>| Bits | NAA |
>| 63 62 61 60 | |
>|___________________|____________________________|
>| ....... | |
>|___________________|____________________________|
>| 0 1 0 1 | IEEE Registered |
>|___________________|____________________________|
>| 0 1 1 0 | IEEE Registered Extended |
>|___________________|____________________________|
>
>Two additional clauses are added to 19.3.2, 19.3.2.6 and 19.3.2.7.
>The text of the two sections follows:
>
>19.3.2.6 IEEE registered
>
>When D_NAA (or S_NAA) is IEEE registered, the Network_Destination_ID
>(or Network_Source_ID) field shall contain the 24-bit IEEE company_id
>followed by a 36-bit vendor specified identifier (VSID) which
>uniquely indicates a Node, an N_Port, an F_Port, a Fabric, or other
>object.
>
>| first byte | | | |
>|63 56|55 48|47 40|39 32|
>|________|________|________|________|________|________|________|_______|
>| NAA = | IEEE company_id | VSID |
>| | |
>| 0101 |23 20|19 12|11 04|03 00|35 32|
>|________|________|_________________|_________________|________|_______|
>
>
>| | | | last byte |
>|31 24|23 16|15 08|07 00|
>|________|________|________|________|________|________|________|_______|
>| Vendor Specific Identifier |
>| |
>|31 24|23 16|15 08|07 00|
>|_________________|_________________|_________________|________________|
>
>Uses:
>
>An IEEE registered name may be assigned to an N_Port, a
>Node, an F_Port, or a Fabric.
>
>19.3.2.7 IEEE registered extended
>
>When D_NAA (or S_NAA) is IEEE registered extended, the
>Network_Destination_ID (or Network_Source_ID) field shall contain
>the 24-bit IEEE company_id followed by a 36-bit vendor
>specified id. An additional 64-bit vendor specified identifier extension
>is defined. The separate vendor specified spaces allow a node to be
>identified by the 24-bit IEEE company_id and 36-bit vendor
>specified id. The node may then generate additional unique sub-ids using
>the vendor specified identifier extension. The location of the vendor
>specified identifier extension is defined for each type of object.
>
>| first byte | | | |
>|63 56|55 48|47 40|39 32|
>|________|________|________|________|________|________|________|_______|
>| NAA = | IEEE company_id | VSID |
>| | | |
>| 0110 |23 20|19 12|11 04|03 00|35 32|
>|________|________|_________________|_________________|________|_______|
>
>
>| | | | |
>|31 24|23 16|15 08|07 00|
>|________|________|________|________|________|________|________|_______|
>| |
>| Vendor Specific Identifier |
>|31 24|23 16|15 08|07 00|
>|_________________|_________________|_________________|________________|
>
>Vendor Specific Identifier Extension field
>
>| | | | |
>|63 56|55 48|47 40|39 32|
>|________|________|________|________|________|________|________|_______|
>| Vendor Specific Identifier Extension |
>| |
>|63 56|55 48|47 40|39 32|
>|_________________|_________________|_________________|________________|
>
>
>| | | | last byte |
>|31 24|23 16|15 08|07 00|
>|________|________|________|________|________|________|________|_______|
>| |
>| Vendor Specific Identifier Extension |
>|31 24|23 16|15 08|07 00|
>|_________________|_________________|_________________|________________|
>
>Uses:
>
>An IEEE registered extended name may be assigned to any Fibre Channel
>related object, but the Fibre Channel architecture does not provide
>a large enough space for it to be used as a node, N_Port, F_Port or
>fabric identifier.
>
----------------------------------------------------
Larry Chen Tel: 408.383.1600 (x116)
Maximum Strategy, Inc. Fax: 408.383.1616
801 Buckeye Court E-mail: larryc at maxstrat.com
Milpitas, CA 95035
----------------------------------------------------
*
* For SCSI Reflector information, send a message with
* 'info scsi' (no quotes) in the message body to majordomo at symbios.com
More information about the T10
mailing list