Docstoc

XLS - T11 - Download as Excel

Document Sample
XLS - T11 - Download as Excel Powered By Docstoc
					                                                                         FC-GS-4 Revision 7.6 Comments
                                                                                    09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                           Problem Description                         Suggested solution                            Response                     Status     Edit Status
             /Edito Page    figure locator
               rial
Cisco-002       T         2 2.2            remove and update references                   remove old approved references
                                                                                          (e.g., FG, SW, AL) and update        Craig to incorporate changes from 02-
                                                                                          references under development.        751v0 into document. .                         A      Done.
                           3                Could the 'Managed Objects' and MIB
                                2.4 (Other references be replaced with a reference to                                                                                                Partial, removed
ENDL-009       T               references) the MIB-FA TR?                                                                      Remove all references to MIBs (see xxx).       A      from references.
QLogic-002     T           4 2.4, 2nd left There is no information about where to find    An address or other contact
                             justified      the Open Group CAE Specifications             information needs to be specified
                             paragraph on                                                 for these documents.
                             page (editor's
                             comment)
                                                                                                                               Use Suggested solution in Andiamo-04           O
                           6 3.2.29        The statement << Each Client assigns its
                             Secured       own SAID for a Secured Association. SAIDs
                             Association   allow multiple concurrent Secured
                             Identifier    Associations to be active between two
                             (SAID):       Clients. Each Secured Association contains
                                           the SAID assigned by each Client, the
                                           secret key, and the encryption algorithm. >>
                                           should be placed in the main body of the
                                           document that describes the SAID. It is too
                                           detailed for a glossary entry.                                                      Keep first and third sentence and delete
IBM-009        T                                                                                                               others.                                        A      Done.
QLogic-003     T           6 3.2.20        Link_Control_Facility is not defined here.     Define Link_Control_Facility, and    Reference back to FC-FS, correct
                                           Plus some things are considered N-Ports        add allowance for well-known         spelling to that in FC-FS. Hardware
                                           (such as the Name Server address               ports which may not have a           entity is correct for N_Ports, check to
                                           FFFFFCh) even though they do not               physical basis.                      make sure that well known services are
                                           correspond to a physical port.                                                      referred to as address identifiers             A      Done.
QLogic-004     T           6 3.2.32        This definition is not accurate.               Maybe it would be clearer to say
                                                                                          "The Fabric does not enforce a
                                                                                          Soft Zone on frames sent directly
                                                                                          between ports.", since Soft Zones    Change the last sentence of the
                                                                                          are enforced for Name Server         definition to "The Fabric does not enforce
                                                                                          access.                              a Soft Zone on a frame-by-frame basis."        A      Done.
Cisco-003      T           7 3.2           requirements in definitions                    move all requirements specified in
                                                                                          the definitions to an appropriate
                                                                                          subclause in the normative text
                                                                                          (e.g., 3.2.39, 3.2.43, 3.2.46,       Proposed solution in 03-491v0.
                                                                                          3.2.47, 3.2.52)                      Proposed solution needs more detail.           O
                           7 3.2.39        The statement << A user-defined name for
                             Symbolic      an object, >> should be << vendor-specific                                          This is a user defined value and not a
IBM-012        T             Name:         name for an object >>                                                               vendor specific name.                          R




                                                                                         Page 1 of 91
                                                                          FC-GS-4 Revision 7.6 Comments
                                                                                     09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                                 Problem Description                       Suggested solution                        Response                 Status     Edit Status
             /Edito Page    figure locator
               rial
                          7 3.2.47 Zone The list << 1) a port on a Switch, (specifically
                            Member          by Domain_ID and port number);
                            Definition:     or,<CRLF>2) the device\220s
                                            N_Port_Name; or, 3) the device\220s
                                            address identifier; or, 4) the device\220s
                                            Node_Name. >> if needs to be a list needs
                                            to be labeled a,b,c and use the standard
                                            format for a list. A better solution would be
                                            to move everything after the first sentence
                                            into the zone section as it is too detailed for
                                            a glossary entry. In addition the statement
                                            << (specifically by Domain_ID and port
                                            number) >> does not make any sense.
                                            Maybe it means << a switch ports
                                            Domain_ID and port number >>.
IBM-017         T                                                                                                              Keep first sentence and delete others.     A      Done.
QLogic-005      T         7 3.2.43          FC-PH is referenced here.                       Replace FC-PH with FC-FS. FC-
                                                                                            FS is already referenced many
                                                                                            times in the glossary. For most of                                                   Done. All
                                                                                            the life of FC-GS-4, FC-FS will                                                      referecnes to FC-
                                                                                            have replaced FC-PH. There are                                                       PH or FC-PH-x
                                                                                            other references to FC-PH that                                                       have been
                                                                                            should add FC-FS, such as                                                            replaced with
                                                                                            clauses 4.1, 4.5, and 5.2.3.2.     Accept the proposed solution.              A      FC-FS.
QLogic-006      T         7 3.2.44          Replace "but not made aware of Zone
                                            Members outside the Zone." with "but not
                                            made aware of N-Ports outside the Zone.".                                          Accept the proposed solution. Change
                                                                                                                               N_Ports to Nx_Ports.                       A      Done.
Cisco-005       T        11 4.1             first sentence in the overview specifies "…     remove "at the FC-4 level".
                                            at the FC-4 level". I agree that generic
                                            services share a common transport but I
                                            don't think its necessarily at the FC-4 level.                                     Dave Peterson to provide alternate
                                                                                                                               description.                               O
                         12 many            Global. The second to the last item in an                                          This requires a case by case comment
                                            a,b,c list or a 1,2,3 list should be an << and                                     since the change is dependant on the
                                            >> or an << or >> at the end.                                                      context. Recommend rejection of this
                                                                                                                               comment for the global case unless
IBM-024         T                                                                                                              someone proposes specific solutions.       R
Andiamo-06      T        13             4.2 Is Class 1 used for CT?                         Update accordingly.                                                           R




                                                                                         Page 2 of 91
                                                                             FC-GS-4 Revision 7.6 Comments
                                                                                        09/23/03 (03-083vA)


              Techn
               ical Physical Section/table/
 Company-#                                               Problem Description                     Suggested solution                                    Response                     Status      Edit Status
              /Edito Page    figure locator
                rial
                          13 4.2 General The following << NOTE 2 - The Class of
                             concepts       service preference is specified according to
                                            the local service interface (see annex
                                            A).Since the Class of service is only
                                            meaningful to the local node, this indication
                                            is not transported as part of the CT
                                            preamble information. >> looks like it should
IBM-026          T                          be main text not a note.                                                                   This note is informative.                      R
Andiamo-08       T        14 Note 4         The new version number should indicate        Update accordingly.
                                            support for all the new features of GS-4,
                                            such as new platform names, new rules for
                                            extended preamble, or enhanced zoning,                                                                                                           Done. Used
                                            not only for what is specified in the note.                                                Editor will include important changes "all            '(e.g.,' instead of
                                                                                                                                       new FC-GS-4 features including …".             A      'including'.
                           14 4.3 CT          global The term << Vendor Specified >>
                              information     should be << vendor specific >>.
IBM-028         T             unit                                                                                                     As suggested                                   A      Done.
                           15 table 4        global<CRLF>The term << Vendor Unique
                                             >> should be changed to << vendor specific
IBM-031         T                            >>.                                                                                       As suggested                                   A      Done.
QLogic-008      T          15 Table 4        GS_Type '20' is reserved for FC-SW-2.              Change to FC-SW-3.                     Accept the proposed solution.                  A      Done.
                           16 table 5        The statement << (See note below.) >> and
                                             the note are a problem. The note should be
                                             in the table either in the cell where the
                                             description is located or in a table footer with
                                             a specific reference from the text in the cell                                            Change note to I.e., and move it into the
IBM-033         T                            to that note.                                                                             table cell.                                    A      Done.
                              4.3.2.7, Table FC-SW-3 makes use of commands in the               Reserve values x'0400-04FF' and
                              7              range of x'0400-04FF' and x'E000'-'EFFF'           x'E000'-'EFFF' for FC-SW-3 use.
                                             for Fabric Internal CT operations. These                                                  As suggested. And reserve 400-5FF for
                                             values should be explicitly reserved for FC-                                              SW-3. Change the CMIT code inTable
Brocade-004     T          17                SW-3 use in FC-GS-4.                                                                      246 to 7FFB.                                   A      Done.
                              4.3.2.7, Table FC-SW-3 makes use of commands in the               Reserve values x'F000'-'FFFF' for
                              7              range of x'F000'-'FFFF' for Fabric Internal        FC-SW-3 use.
                                             Vendor Unique CT operations. These values
                                             should be explicitly reserved for FC-SW-3
Brocade-005     T          17                use in FC-GS-4.                                                                           As suggested.                                  A      Done
                              4.3.2.8        There is no provision for the                      Allow a residual size to be
                                             Responding_CT to specify a residual size if        specified even if the total response
                                             the response is larger than what the               size is less than the maximum
                                             responding agent is able to provide in a           specified by the Requesting_CT.
Brocade-019     T          18                single CT_IU.                                                                             Withdrawn by commentor.                       W




                                                                                            Page 3 of 91
                                                                           FC-GS-4 Revision 7.6 Comments
                                                                                      09/23/03 (03-083vA)


              Techn
               ical Physical Section/table/
 Company-#                                               Problem Description                        Suggested solution                        Response                     Status      Edit Status
              /Edito Page    figure locator
                rial
                             4.4.4, Table A new reason code needs to be defined              Add reason codes "server not
                             10             when invalid GS_Types and GS_Subtypes            defined" and server not
                                            are specified in the CT request. Both "invalid   implemented"                       Add reason code of "Server Not
                                            command code" and "command not                                                      Available" and give an explanation of
                                            supported" are inadquate to indicate this                                           "The server identified by the GS_Type
Brocade-003      T        22                type of error.                                                                      and GS_Subtype is not available."            A      Done.
                             4.4.4          Hard Enforcement Failed does not appear to     Change Hard Enforcement Failed Suggested solution rejected, remove the
                                            mean anything. It is also unclear what it      to "Not Authorized", indicating a    CT_IU Reason Code of Hard
                                            should mean in the context of a CT reject.     reject due to the enforcement of a Enforcement Failed and move it to the
                                                                                           configured policy (such as zoning Fabric Zone Server CT_IU Reason Code
                                                                                           or software license or vendor        explanations. Then modify the last
                                                                                           specific policy mechanism). This sentence of second paragraph of
                                                                                           is distinct from a authentication    6.4.6.2.1 to reflect that In case of an
                                                                                           failure. Authentication indicates    activation fail, the CT_RJT shall return
                                                                                           verifying the "who" is allowed part. the reason code Unable to perform
                                                                                           Authorization indicates enforcing command requested with a reason code
                                                                                           the "what" is allowed part.          explanation of "Hard Enforcement
                                                                                                                                Failed". Combine Table 271 and 272
Brocade-020     T           22                                                                                                  and add "Hard Enforcement failed".           A      Done.
Andiamo-10      T           23 4.3.4.4.1      Hard Enforcement Failed: definition missing Add: "The activation of an Hard
                                                                                           Zone failed. The reason code
                                                                                           explanation field contains
                                                                                           additional information. See
                                                                                           6.4.6.2.1."                          See QLogic-009.                              R
McDATA-10       T           23 4.4.4          Hard Enforcement Failed is not defined.      Define it.                           See Brocade-20.                              R
McDATA-11       T           23 Craig's note Answer the question.                                                                See Brocade-20.                              R
QLogic-009      T           23 4.4.4          There is no defintion for "Hard Enforcement Add a definition.
                                              Failed".                                                                          See Brocade 20.                              R
                            24 4.5.2.1 Fabric Globally The abbreviation << WKA >> is
                               login and      used in some places and in others << well
                               N_Port login known address >> is used. One or the other                                          WKA is a recognized abbreviation. Do a              Done, changed
                                              needs to be consistently used. I would pick                                       global search and replace different                 all references to
                                              << well known address >> and dump <<                                              spellings of well-known address to that             the abbeviation
IBM-047         T                             WKA >>.                                                                           specified in the definition.                 R      "WKA".
                            24 4.5.2.1 Fabric This note << NOTE 9 - An N_Port that has
                               login and      completed any other requests with a Server
                               N_Port login should also perform explicit N_Port Logout
                                              with the Service. >> looks like it should be                                      Convert the note to normative text and
                                              part of the main body not a note.                                                 add it to the end of the previous
IBM-049         T                                                                                                               paragraph.                                   A      Done.




                                                                                         Page 4 of 91
                                                                         FC-GS-4 Revision 7.6 Comments
                                                                                    09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                              Problem Description                      Suggested solution                         Response                   Status     Edit Status
             /Edito Page    figure locator
               rial
                         24 4.5.2.3          The statement << For example, a single
                            Exchange         Exchange cannot be used for both Name
                            and              Server and Alias Server requests. >>
                            Sequence         contains the 'can' word and should be
                            management       changed to <<( e.g., a single Exchange shall
                                             not be used for both Name Server and Alias
IBM-050        T                             Server requests. ) >>                                                           As suggested.                               A      Done.
QLogic-010     T          24 4.5.2.1         The references to "N_Port" in this clause     CHange to Nx_Port. Also, the
                                             should be "Nx_Port".                          whole document needs to undergo Do a global search for N_Port and
                                                                                           this change.                      evaluate if it should be Nx_Port.           A      Pending.
                          26 4.5.2.4.10      The term << implementation specific.>>
                             Continue        should be << vender specific >>.
                             Sequence                                                                                        Change to "The use of this parameter is
IBM-055        T             condition                                                                                       as defined in FC-FS."                       A      Done.
                          26 4.5.2.4.11      The statement << The CT shall set this
                             Continue        parameter false. >> gives no indication as to
                             Sequence        what 'false' is. This needs to be more                                          Change to "The CT shall set this
IBM-056        T             condition       specific as to what value represents false.                                     parameter to zero."                         A      Done.
QLogic-011     T          26 4.5.2.4.12      Relative offset is optional, but should be    Make Relative Offset required for
                                             mandatory. Use of Relative Offsets greatly FC-GS-4 commands (with the GS-
                                             facilitates frame reassembly for multi-frame 4 revision in the CT header).
                                             sequences. As CT IU request and response
                                             sizes are getting larger and larger, and as
                                             we start seeing frames for other FC-4's
                                             interleaved with CT frames, requiring use of
                                             relative offsets is the way to go.
                                                                                                                             As suggested.                               A      Done.
                          28 4.5.3.4.10      The term << implementation specific.>>
                             Continue        should be << vender specific >>.
                             Sequence
IBM-065        T             condition                                                                                       Same as IBM-055                             A      Done.
                          28 4.5.3.4.10      The statement << The CT shall set this
                             Continue        parameter false. >> gives no indication as to
                             Sequence        what 'false' is. This needs to be more                                                                                             Keep IBM-056
IBM-066        T             condition       specific as to what value represents false.                                     See IBM-056                                 A      solution.
Andiamo-11     T          30 Note 17         Add a reference to FC-SP                      Say: "Use of CT Authentication or
                                                                                           of other methods to ensure
                                                                                           message integrity and
                                                                                           authentication (see FC-SP) is
                                                                                           recommended for use within the
                                                                                           management service."              Add a reference to FC-SP to clause 2.3.     A      Done.




                                                                                        Page 5 of 91
                                                                       FC-GS-4 Revision 7.6 Comments
                                                                                 09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                              Problem Description                   Suggested solution                   Response                   Status     Edit Status
             /Edito Page    figure locator
               rial
                         30                Regarding 'In either case, the Server shall
                                           preserve the results of the prior actions
                                   4.7     requested by the Client following the Logout
                             (Persistence and following any subsequent Login.' Are
                               of actions there any exceptions to this rule resulting                               Proposed text in 03-289v0. Bob to
                            after Logout), from the newly defined SSB/SSE                                           incoporate changes and repost.
ENDL-015        T                  p2      commands?                                                                Accepted as changed.                        A      Done.
Andiamo-12      T        31 Note 19        The key server is no more present.           Remove or update the note   See Brocade-026.                            A      Done.
                         32                Based on the contents of the 1st p after the
                            4.8.2 (Secure a,b list on the preceding page, it seems like
                              Association 'secret_key' should be 'secret key'
                              Attributes),                                                                          Change the first sentence to "The value
                              6th p after                                                                           of the secret key used by the security
ENDL-021        T               table 14                                                                            algorithm."                                 A      Done.
                         32 4.8.2 Secure The statement << This information important
                            Association to subsequent secured communication. >>
                            Attributes     makes no sense. Should it be << This
                                           information is important to subsequent
                                           secured communication. >>?
IBM-074         T                                                                                                   As suggested                                A      Done.




                                                                                     Page 6 of 91
                                                                           FC-GS-4 Revision 7.6 Comments
                                                                                      09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                             Problem Description                          Suggested solution                   Response                       Status     Edit Status
             /Edito Page    figure locator
               rial                                                                                                      Change 4.8.2 to:
Andiamo-13      T        33 Table 15       These are not encryption algorithms, they         Update accordingly.
                                           are signing algorithms.                                                       client_said: The SAID of the Client.
                                                                                                                         peer_said: The SAID of the peer Client
                                                                                                                         with which the credentials were
                                                                                                                         exchanged.
                                                                                                                         peer_id: The address identifier of the
                                                                                                                         peer Client with which the credentials
                                                                                                                         were exchanged.
                                                                                                                         peer_name: The N_Port_Name of the
                                                                                                                         peer Client with which the credentials
                                                                                                                         were exchanged.
                                                                                                                         algorithm_id: The identifier of the security
                                                                                                                         algorithm for the credentials. See 4.8.3.
                                                                                                                         credentials: The value of the credentials
                                                                                                                         (e.g., keys, secrets, passwords) used by
                                                                                                                         the security algorithm. The format of this
                                                                                                                         field is outside the scope of this
                                                                                                                         Standard.

                                                                                                                         Change 4.8.3 to:

                                                                                                                         4.8.3 Security Algorithms
                                                                                                                         This Standard allows the use of security
                                                                                                                         algorithms other than those identified
                                                                                                                         here.
                                                                                                                         The security algorithm and any
                                                                                                                         associated credentials (e.g., keys,
                                                                                                                         secrets, passwords) shall be a
                                                                                                                         characteristic of the algorithm identifier.
                                                                                                                         Table 15 defines algorithm identifiers for
                                                                                                                         several popular security algorithms
                                                                                                                         including recommended credential                 A      Done.
                          33 4.8.3          The statement << User defined >> should
                             Encryption     be << vendor specific >>.
IBM-076        T             Algorithm                                                                                   see IBM-055                                      A      Done.
                          33 4.8.3          The << can >> should be a << may >>.
                             Encryption
IBM-077        T             Algorithm                                                                                   As suggested.                                    A      Done.
                          33 4.8.3          This note << NOTE 20 - HMAC-MD5 and
                             Encryption     HMAC-SHA1 have been defined for CT
                             Algorithm      Authentication. >> looks like it should be in
                                            the table footer in table 15. I say move it                                  This note is unnecessary since this is in               Done. Note has
IBM-078        T                            there.                                                                       the CT authentication clause.                    A      been removed.




                                                                                            Page 7 of 91
                                                                           FC-GS-4 Revision 7.6 Comments
                                                                                     09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                              Problem Description                     Suggested solution                                Response                   Status      Edit Status
             /Edito Page     figure locator
               rial
QLogic-012      T        33 4.9.1           There are no rules specifiing how the       For interoperability, define rules for   Add "GS_Type and GS_Subtype shall be
                                            common requests use GS_Type and             GS_Type and GS_Subtype use.              set as defined by the server to which the
                                            GS_Subtype values.                                                                   common request is applied."                   A      Done.
                         34 4.9.4 (Get will [s/b] shall
                                  More
                             Information),
ENDL-028        T               p 2, s 5                                                                                         as suggested                                  A      Done.
                         34 4.9.4 Get       The statement << value will be >> should be
                            More            changed to << value shall be >>.
                            Information
IBM-081         T           (GMI)                                                                                                See ENDL-028.                                 A      Done.
                         35      4.9.5.1    can [s/b] may [or s/b] needs to
                                (Server
                              Registration
                            ... Overview),
                            1st p on pg, s
ENDL-031        T                   3                                                                                            accept as may.                                A      Done.
QLogic-015      T        35 4.9.5.4         Incorrect well-known address FFFFFEh.       Replace FFFFFEh with FFFFFCh.

                                                                                                                                 Accept the proposed solution.                 A      Done.
Andiamo-15     T           37 Note 21        could we reference FC-DA instead than FC- Update
                                             FLA?                                                                                Remove note 21.                               A      Done.
                           37                Based on the contents of note 22, 'Obsolete
                              5.1 (Directory (see 3.5.7)' seems to describe this code
                                 Service     value better than 'Reserved'.
                               Overview),                                                                                                                                             Done. Changed
                                Table 22,                                                                                                                                             type '01' (NOT
ENDL-039       T                 value 0a                                                                                        Change to obsolete.                           A      '0a') to obsolete.
                           37 5.1 Overview This note << NOTE 21 - The Name Server is
                                             a Required feature of FC-FLA compliant
                                             Fabrics. >> should deleted as we do not call
                                             out any other FC-FLA compliant things.
IBM-087        T                                                                                                                 see Andiamo-15.                               A      Done.
                           37 5.1 Overview This note << NOTE 22 - Value 01h indicated
                                            the X.500 Server defined in the first
                                            publication of this standard. >> should be
                                            deleted because it should no longer be
IBM-088        T                            relevant.                                                                            Delete note.                                  A      Done.
QLogic-016     T           37 Note 21       Note refences FC-FLA.                          Change this to FC-MI.                 see Andiamo-15.                               R
                                        5.2 Need a "GID_DP - Get ID from                   Commentor will supply proposal to     See proposed command in 03-471v0.
                                            Domain/Port" to solve interoperability issues. create this command.                  For Zoning warnings, keep the
                                                                                                                                 interoperability warning, and include
QLogic-L02     T           37                                                                                                    reference.                                    A      Done.




                                                                                         Page 8 of 91
                                                                             FC-GS-4 Revision 7.6 Comments
                                                                                        09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                                 Problem Description                         Suggested solution                          Response                     Status     Edit Status
             /Edito Page    figure locator
               rial
                            Table 22,         Description says objects 1 through D, but         Update the dscription to descibe
                            Aggregated        object numbers don't exist anymore.               the Objects properly. This will also
McDATA-23       T        38 Objects                                                             affect 5.2.5.2.                      See QLogic-017.                              A      Done.
QLogic-017      T        38 Table 22,         Aggregated Objects uses numberes that             Since objects no longer have
                            Aggregated        have been removed.                                numbers, must list the objects
                            objects                                                             included.                            Change description to: "A combination of
                                                                                                                                     objects or object types."                    A      Done.
                               Table 23,      Objects in Accept CT_IU for GA_NXT says           I don't know the answer, just the
                               GA_NXT         all but it doesn't include FC-4 Descriptors,      problem.
McDATA-24      T          39                  FC-4 Features and PPN.                                                                 Editor will update Table 23 accordingly.     A
                          42                  Regarding: 'Registrations are limited to a
                                              single Name Server object at a time.' 'Time'
                                              is an imprecise delimiter for the stated
                                              restriction. Is 'time' meant to imply within a
                                              single SSB/SSE session? Is 'time' meant to
                                              imply within a single request (or command)?
                                              Does 'time' have some other meaning
                                              beyond those guessed above? In any case,
                                              please replace 'time' is a more precise
                                   5.2.2.3    description of the delimiter for the
                               (Registration) requirement.
ENDL-042       T                  , p 1, s 1                                                                                       Delete first sentence.                         A      Done.
                          42   5.2.2.3        There should cross-references to the
                               Registration standard that defines Hunt groups and                                                  Add (See FC-FS) to Hunt Groups and
IBM-090        T                              Multicast group identifiers;                                                         Multicast group identifiers.                   A      Done.
                          43                  Regarding: 'Only one global deregistration
                                              request is defined for the Name Server.'
                                              This statement is imprecise in many ways. Is
                                              it true that this standard defines is one
                                              global and several non-global deregistration
                                              requests? How global is the 'one global
                                              deregistration request'? Does it wipe the
                                              entire Name Server database clean, erasing
                                   5.2.2.5    all objects registered for all Port Identifiers
                               (Deregistratio and Node Names? Please clarify.
ENDL-045       T                 n), p 1, s 1                                                                                      Delete the word "global".                      A      Done.




                                                                                            Page 9 of 91
                                                                           FC-GS-4 Revision 7.6 Comments
                                                                                     09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                                 Problem Description                          Suggested solution                   Response                     Status     Edit Status
             /Edito Page     figure locator
               rial
                         43                 Regarding: 'In the event a Server Session
                                            End is not received after a successfully
                                            accepted Server Session Begin, the server
                                            shall initiate registered state change
                                 5.2.2.6    notification based on vendor unique
                                 (Name      procedures.' The absence of a time interval
                                 Server     in this statement opens the possibility that
                               Interaction (in the most absurd of all cases) the server
                                   with     initiates registered state change notification
                                Common immediately subsequent to processing the
                                Requests SSB. Perhaps discussion of a time interval
                                SSB and should be added to the statement.
ENDL-046        T               SSE), p 2                                                                                    See 03-494v0 page 4.                           A      Done.
                         43 5.2.2.6 Name The statement << vendor unique
                            Server          procedures. >> should be << vendor specific
                            Interaction     procedures. >>.
                            with
                            Common
                            Requests
                            SSB and
IBM-093         T           SSE                                                                                              See IBM-031                                    A      Done.
                            e)              After e), add Permanent Port Name                Add Permanent Port Name as
McDATA-26       T        43                                                                  item f).                        Accept the proposed solution.                  A      Done.
                            Table 24        Permanent Port Name should be added to           Add PPN
McDATA-27       T        44                 the Indexed Fields for Port Identifier                                           Table 24 removed by ENDL-052.                  R
QLogic-018      T        44 5.2.2.6, first The requirement: "If a Server Session End         Clarify.
                            paragra on      request is successfully accepted without                                         Remove the last paragraph of 5.2.2.6.
                            page            previously having accepted an SSB                                                Change the last sentence of the first
                                            request, processing shall continue as if an                                      paragraph to "An SSE request, even in
                                            SSB request had been accepted."                                                  the absence of a prior SSB Request,
                                            Requirement is too vague. Questions: 1) is                                       signals that the Name Server, in
                                            this requiring an implicit SSB? 2) How far                                       conjuction with the Fabric Controller, has
                                            back does this implicit SSB go within the                                        initiative to begin the state change
                                            current ssession?                                                                notification process (see 4.9.5)."             A      Done.
                         49                 Regarding: 'The format of the Port Type
                                            object, shall be as shown in table 26.' Table
                                            26 shows value encodings. The format of
                                            the object containing these encodes is not
                                            clear. Is the Port Type formatted as a single                                    Change the sentence to "The format of
                            5.2.3.11 (Port byte, as a word, or in some other way?                                            the Port Type object is a one byte value
ENDL-050        T              Type), p 1 Please clarify.                                                                    encoded as shown in Table 26."                 A      Done.




                                                                                        Page 10 of 91
                                                                              FC-GS-4 Revision 7.6 Comments
                                                                                         09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                              Problem Description                              Suggested solution                            Response                      Status     Edit Status
             /Edito Page    figure locator
               rial
Andiamo-16      T        50 Note 24        Is that true? FCP-2 is now out.                      Update                                 Remove note 24. Add "Specific FC-4s
                                                                                                                                       may define the contents of this object." to
                                                                                                                                       the preceding paragraph. Also change
                                                                                                                                       "The contents of these bytes are not
                                                                                                                                       defined and shall not be restricted by the
                                                                                                                                       Name Server." to "The contents of these
                                                                                                                                       bytes are not defined by this standard
                                                                                                                                       and shall not be restricted by the Name
                                                                                                                                       Server."                                        A      Done.
                          50                    The statement, 'the FC-4 Descriptor is                                                 Change to "The FC-4 Descriptors in an
                                                indexed by the FC-4 TYPEs object' appears                                              FC-4 Descriptor object are selected by
                                                to conflict with table 24 and with several                                             the FC-4 TYPEs object."
                                                statements in the first paragraph of 5.2.2.3.
                                                                                                                                       Remove Table 24, and paragraph above
                               5.2.3.14 (FC-                                                                                           Table 24. Change Heading for Clause
                               4 Descriptor),                                                                                          5.2.3.1 to "Use of Null values for name
ENDL-052       T                  p 1, s 3                                                                                             server objects".                                A      Done.
                          51                 Please add a statement to introduce the list                                              Move Table 27 to the end of 5.2.3.15 and
                               5.2.3.15 (FC- that begins at the top of this page.                                                      change "as shown in Table 27" to
                                4 Features),                                                                                           "positioned in the FC-Features object as
ENDL-053       T                  top of pg                                                                                            follows (see also table 27):"                   A      Done.
                               5.2.3.16      The Permanent Port Name is the                     Add the following sentence to FC-
                                             Name_Identifier associated with the N_Port         GS-4, clause 5.2.3.16, paragraph
                                             ID assigned in the response to the FLOGI           1:
                                             request from the attached N_Port. This             “If the N_Port ID corresponding to
                                             FLOGI-assigned N_Port ID can be logged             the Name_Identifier equal to the
                                             out, just as other N_Port IDs assigned             Permanent Port Name logs out
                                             during FDISC. If this occurs, then the             from the F_Port, then the
                                             Permanent Port Name for the N_Port does            Permanent Port Name shall be set
                                             not change. If another F_Port on the same          to the Name_Identifier
                                             fabric receives an FLOGI or FDISC                  corresponding to another N_Port
                                             containing the same Name_Identifier,               ID which is currently logged in with
                                             however, then either:                              the same F_Port.
                                             1) if the Fabric accepts an FLOGI, then two
                                             N_Ports on the same fabric will have the
                                             same Permanent port name, or
                                             2) if the Fabric accepts an FDISC, then one
                                             of the N_Port IDs on the second F_Port will
                                             have the same Name_Identifier as the
                                             Permanent Port Name of the first N_Port,
                                             which will confuse a SAN manager.

IBM-L01        T          51                                                                                                           Withdrawn by commentor by 03-275v0.            W
                               5.2.3.16         We should add a note saying that there is       Add a note similar to Note 23.
McDATA-28      T          51                    no explicit registration of the PPN.                                                   As suggested.                                   A      Done.



                                                                                            Page 11 of 91
                                                                           FC-GS-4 Revision 7.6 Comments
                                                                                     09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                               Problem Description                        Suggested solution                              Response                     Status     Edit Status
             /Edito Page    figure locator
               rial
                         52       5.2.4       Is it necessary to add a reason code
                                (Reason       explanation for 'Permanent Port Name not
                                  code        registered'?
                            explanations)                                                                                         The PPN is implicitly registered, so it will
ENDL-056        T             , Table 28                                                                                          always exist for a valid port identifier.        R
Andiamo-17      T        53 Note 26           Add domain controller addresses              Update                                 Accept the proposed solution.                    A      Done.
                         54      5.2.5.2      function [s/b] command
                             (Query - Get
                            all next), Note
ENDL-057        T                27, s 1                                                                                          Delete this note.                                R      Done.
                            Last              The IN_ID should be included in the HMAC     Include the IN_ID HMAC                 The IN_ID field was not included
McDATA-17       T        54 Paragraph         Algorithm.                                   algorithm.                             because it can be changed in flight.             R
                         56      5.2.5.2      Is it necessary/appropriate to add a
                             (Query - Get     Permanent Port Name field to the Accept
                                all next),    CT_IU to GA_NXT Request?                                                            GA_NXT will not include PPN or other
ENDL-058        T              Table 30                                                                                           newer descriptors like FC-4 Features.            R
                         56 note 28        This note should be part of the main text <<
                                           NOTE 28 - FC-4 Descriptor(s) are not
                                           returned in the Accept CT_IU of the
IBM-104        T                           GA_NXT request. >>                                                                     Delete Note 28.                                  R      Done.
                          57 5.2.5.3 Query Why is there no definition for reference to a
                             - Get         definition for Domain_ID or Area_ID in this
                             identifiers   section? This needs to be fixed.                                                       Add definitions for Domain_ID and
IBM-106        T             (GID_A)                                                                                              Area_ID from SW.                                 A      Ponder.
                             last sentence "The Node Name field returns the registered Change to: "The Node Name field            Change to: "The Node Name field returns
                                           value for the Node Name." is incorrect.         returns the registered value for the   the registered value for the Port
McDATA-31      T          59                                                               Port Name.".                           Identifier.".                                    A      Done.
                             Craig's Note Resolve note.                                    Reject the command with "unable
                                                                                           to perform command request" and
McDATA-32      T          65                                                               "Data base empty".                     See QLogic-019.                                  R
QLogic-019     T          65 5.2.5.13,     If one of the FC-4 TYPEs does not have a        Define a null response for this
                             Editor's      registered FC-4 Descriptor, how is that         command.
                             comment.      reflected in the
                                           Response? Especially since NULL is a valid                                             Add note at the end of 5.2.3.14 that says
                                           descriptor (i.e., you can register a descriptor                                        "Note - There is no distinction between a
                                           of zero                                                                                FC-4 Descriptor that has not been
                                           length). Should a reject be sent in this case?                                         registered and an FC-4 Descriptor that
                                                                                                                                  has been registered with zero length.".          A      Done.




                                                                                         Page 12 of 91
                                                                              FC-GS-4 Revision 7.6 Comments
                                                                                          09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                                 Problem Description                          Suggested solution                     Response                     Status     Edit Status
             /Edito Page     figure locator
               rial
                         77 5.2.5.27          The statement << 80h, i.e. Port Identifiers
                            Query - Get       for all registered Unidentified ports, N_Ports,
                            Port              NL_Ports, F/NL_Ports, etc. The >> is
                            Identifiers       confusing because it is an i.e. but contains
                            (GID_PT)          an etc at the end. i.e.s are usually complete
                                              were e.g.s have an implied etc at the end.
                                              So either the list needs to be complete or
                                              the i.e. changed to an e.g.. In any case the
                                              statement needs to be bordered with ( )s.
IBM-117        T                                                                                                               Change I.e. to e.g. and use () around it.      A      Done.
                             Table 86,        Objects in Request CT_IU should be Fabric          Change to Fabric Port Name.
McDATA-25      T          80 GID_FPN          Port Name, not Node Name.                                                        As suggested.                                  A      Done.
                             Craig's Note     Node Name should be FPN in Table 86.               Change table to FPN.
                             and Table 86     We do have a Fabric Port Name object to
McDATA-33      T          80                  answer Craig's question.                                                          See McDATA-25.                                A      Done.
QLogic-020     T          80 5.2.5.30,        How                                                The table says Node Name, but
                             Editor's         does the Fabric Port Name map to the Node          command gets Fabric Port Name.
                             comment.         Name?                                              This payload needs to be made
                                                                                                 consistent with the command
                                                                                                 description.                   See McDATA-25.                                A      Done
                          83 5.2.5.33         The statement << object. This means that
                             Register Port    any 64 bit Port Name value shall be
                             Name             accepted. >> should be << object (i.e., all 64                                   Change to "The Name Server shall not
                             (RPN_ID)         bit Port Name values are accepted). >>                                           attempt validation of the Port Name
IBM-122        T                                                                                                               object and shall accept any 64 bit value."     A      Done.
                          84 5.2.5.34         The statement << object. This means that
                             Register         any 64 bit Port Name value shall be
                             Node Name        accepted. >> should be << object (i.e., all 64                                   Change to "The Name Server shall not
                             (RNN_ID)         bit Port Name values are accepted). >>                                           attempt validation of the Node Name
IBM-123        T                                                                                                               object and shall accept any 64 bit value."     A      Done.
                          85 5.2.5.35         The statement << object. This means that
                             Register         any 32<CRLF>bit Class of Service object
                             Class of         value shall be accepted. >> should be <<                                         Change to "The Name Server shall not
                             Service          object (i.e., all 32 bit Class of Service object                                 attempt validation of the Clas of Service
IBM-124        T             (RCS_ID)         value are accepted). >>                                                          object and shall accept any 32 bit value."     A      Done.
                          86 5.2.5.36         The statement << object. This means that
                             Register FC-     any 32<CRLF>byte FC-4 TYPEs object                                               Change to "The Name Server shall not
                             4 TYPEs          value shall be accepted. >> should be <<                                         attempt validation of the FC-4 TYPEs
                             (RFT_ID)         object (i.e., all 32 byte FC-4 TYPEs object                                      object and shall accept any 32 byte
IBM-125        T                              value are accepted). >>                                                          value."                                        A      Done.




                                                                                             Page 13 of 91
                                                                           FC-GS-4 Revision 7.6 Comments
                                                                                      09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                                Problem Description                        Suggested solution                   Response                     Status      Edit Status
             /Edito Page     figure locator
               rial
                         86 5.2.5.37          The statement << object. This means that
                            Register          any<CRLF>variable length Symbolic Port
                            Symbolic          Name value up to 255 bytes long, including                                                                                        Done. New text
                            Port Name         a 0 length, shall be accepted. >> should be                                                                                       was not correct,
                            (RSPN_ID)         << object (i.e., any<CRLF>variable length                                                                                         changed to:
                                              Symbolic Port Name up to 255 bytes,                                                                                               "The Name
                                              including a 0 length, are accepted). >>.                                                                                          Server shall not
                                                                                                                                                                                attempt
                                                                                                                                                                                validation of the
                                                                                                                                                                                Symbolic Port
                                                                                                                                                                                Name object
                                                                                                                          Change to "The Name Server shall not                  and shall accept
                                                                                                                          attempt validation of the Symbolic Port               any value up to
                                                                                                                          Name object and shall accept any 255                  255 bytes in
IBM-126        T                                                                                                          byte value."                                   A      length."
                          87 5.2.5.38         The statement << object. This means that
                             Register Port    any 8 bit value,<CRLF>shall be accepted.                                    Change to "The Name Server shall not
                             Type             >> should be << object (i.e., any<CRLF>8                                    attempt validation of the Port TYPEs
IBM-127        T             (RPT_ID)         bit value is accepted). >>.                                                 object and shall accept any 8 bit value."      A      Done.
                          88 5.2.5.39         object. This means that any<CRLF>128 bit
                             Register IP      IP Address (Port) value shall be accepted.                                  Change to "The Name Server shall not
                             Address          >> should be << object (i.e., any<CRLF>128                                  attempt validation of the IP Address
                             (Port)           bit IP Address (Port) value is accepted). >>.                               object and shall accept any 128 bit
IBM-128        T             (RIPP_ID)                                                                                    value."                                        A      Done.
                          89 5.2.5.40     The statement << object. This means that
                             Register Hardany Hard<CRLF>Address value shall be
                             Address      accepted. >> should be << object (i.e.,                                         Change to "The Name Server shall not
                             (RHA_ID)     any<CRLF>Hard Address value is                                                  attempt validation of the Hard Address
IBM-129        T                          accepted). >>.                                                                  object and shall accept any 3 byte value."     A      Done.
                          90 5.2.5.41     The statement << object. This means that
                             Register FC- any<CRLF>variable length FC-4 Descriptor                                                                                              Done. New text
                             4 Descriptor value up to 255 bytes long, including a 0                                                                                             not correct.
                             (RFD_ID)     length, shall be accepted. >> should be <<                                                                                            Changed to:
                                          object (i.e., any<CRLF>variable length FC-4                                                                                           "The Name
                                          Descriptor value up to 255 bytes, including a                                                                                         Server shall not
                                          zero length, are accepted). >>.                                                                                                       attempt
                                                                                                                                                                                validation of the
                                                                                                                                                                                FC-4 Descriptor
                                                                                                                          Change to "The Name Server shall not                  object and shall
                                                                                                                          attempt validation of the FC-4 Descriptor             accept any
                                                                                                                          object and shall accept any 255 byte                  value up to 255
IBM-130        T                                                                                                          value."                                        A      bytes in length."




                                                                                            Page 14 of 91
                                                                           FC-GS-4 Revision 7.6 Comments
                                                                                      09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                                Problem Description                        Suggested solution                        Response                     Status      Edit Status
             /Edito Page     figure locator
               rial
                         91 5.2.5.42          The statement << bits. This means that any                                        Change to "The Name Server shall not
                            Register FC-      4-bit value<CRLF>shall be accepted. >>                                            attempt validation of the FC-4 Features
                            4 Features        should be << bits (i.e., any<CRLF>4-bit                                           object and shall accept any 32 byte
IBM-131         T           (RFF_ID)          value is accepted). >>.                                                           value."                                       A      Done.
                         92 5.2.5.43          The statement << object. This means that
                            Register IP       any<CRLF>128 bit IP Address (Node) value                                          Change to "The Name Server shall not
                            Address           shall be accepted. >> should be << object                                         attempt validation of the IP Address
                            (Node)            (i.e., any<CRLF>28 bit IP Address (Node\                                          object and shall accept any 128 bit
IBM-132         T           (RIP_NN)                                                                                            value."                                       A      Done.
                         93 5.2.5.44          The statement << object. This
                            Register          means<CRLF>that any 8 byte Initial Process
                            Initial           Associator value shall be accepted. <<                                            Change to "The Name Server shall not
                            Process           object (i.e., any<CRLF>8 byte Initial Process                                     attempt validation of the Initial Process
                            Associator        Associator value is accepted). >>.                                                Associators object and shall accept any 8
IBM-133         T           (RIPA_NN)                                                                                           byte value."                                  A      Done.
                         93 5.2.5.45          The statement << object. This means
                            Register          that<CRLF>any variable length Symbolic                                                                                                 Done. In oder to
                            Symbolic          Node Name value up to 255 bytes long,                                                                                                  be consistent
                            Node Name         including a 0 length, shall                                                                                                            with other
                            (RSNN_NN)         be<CRLF>accepted. should be << object                                                                                                  changes,
                                              (i.e., any<CRLF>variable length Symbolic                                                                                               changed to:
                                              Node Name value up to 255 bytes, including                                                                                             "The Name
                                              a zero length, are accepted). >>.                                                                                                      Server shall not
                                                                                                                                                                                     attempt
                                                                                                                                                                                     validation of the
                                                                                                                                                                                     Symbolic Node
                                                                                                                                Change to "The Name Server shall not                 Name object
                                                                                                                                attempt validation of the Symbolic Node              and shall accept
                                                                                                                                Name object and shall accept any 0-255               any value up to
                                                                                                                                byte value."                                         255 bytes in
IBM-134        T                                                                                                                                                              A      length."
Andiamo-20     T          96 5.3.2.3          Text says: "The IP Address Server shall         Add Domain controller addresses
                                              reject registrations associated with:                                             IP Address Server being Obsoleted. See
                                              – well-known address identifiers."                                                Andiamo-21.                                   R
Andiamo-21     T          98 Table 122        Why is the type of address encoded              Discuss
                                              separately from the address? This allows
                                              inconsistencies.                                                                  Obsoleting IP Address Server.                 R
Andiamo-23     T         102 Note 41          Add a reference to FC-SP                        Say: "Use of CT Authentication or
                                                                                              of other methods to ensure
                                                                                              message integrity and
                                                                                              authentication (see FC-SP) is
                                                                                              recommended for use within the
                                                                                              management service."              Accept the proposed solution.                 A      Done.




                                                                                         Page 15 of 91
                                                                             FC-GS-4 Revision 7.6 Comments
                                                                                        09/23/03 (03-083vA)


              Techn
               ical Physical Section/table/
 Company-#                                             Problem Description                           Suggested solution                             Response                    Status     Edit Status
              /Edito Page    figure locator
                rial
                             6.1, item f    Fabric may not always store information          Change "provides a data store for
                                            associated with attached devices.                attached device information." to
                                                                                             "provides access to data
                                                                                             associated with attached devices."
Brocade-006     T         102                                                                                                       As suggested.                                 A      Done.
                          103 6.1 Overview The statement << Note that this system view
                                           by a management application is not                                                       Change to "This system view by a
                                           constrained by the operational environment                                               management application shall not be
                                           (Zone) of its associated Node; therefore,                                                constrained
                                           some form of authentication and/or access                                                by the operational environment (Zone) of
                                           control may be desirable. >> should be                                                   its associated Node; therefore, some
                                           made into a note in a separate paragraph.                                                form of authentication
IBM-141         T                                                                                                                   and/or access control is desirable."          A      Done.
                                GPSC           Was command code 0127 used for anything Change the code if there is a
McDATA-40       T         105                  previously?                                      conflict.                           There was no conflict with GS-3.              R
                                table 131      add DPALL (0x39F)- Dereg all Plat objects Define and add new command to
Brocade-022     T         107                                                                   list.                               Command added in 03-210v0.                    A      Done.
                          107                  Regarding: 'Registrations are limited to a
                                               single Fabric Configuration Server attribute
                                               at a time.' 'Time' is an imprecise delimiter for
                                               the stated restriction. Is 'time' meant to imply
                                               within a single login session? Is 'time' meant
                                               to imply within a single request (or
                                               command)? Does 'time' have some other
                                               meaning beyond those guessed above? In
                                               any case, please replace 'time' is a more
                                    6.2.2.3    precise description of the delimiter for the
                                (Registration) requirement.
ENDL-069        T                  , p 1, s 1                                                                                       Delete first and second sentence.             A      Done.
                                6.2.2.3        The first sentence says registrations are        Either delete the sentence or add
                                               limited to a single attribute at a time. This is the exception for RPL.
McDATA-41       T         107                  not true for RPL.                                                                    See ENDL-069.                                 A      Done.
                                6.2.3.2.7      Invalid URL protocols are use in NOTE 42. We have many options here:
                                               Only protocols approved by the IETF (listed 1) Remove the unapproved
                                               trough IANA) can be call a URL. NOTE 42 protocols from GS-4. This is not
                                               mentions "SNMP" and "XML" which are both ideal since there are some useful
                                               not approved.                                    protocols.                          Craig C. and David Black to explore an
                                                                                                2) Have new protocol types added    IETF resolution to this. T10 also has the
                                               The approved list can be found at:               to the approved IANA list. This     same issues so there may be enough
                                               http://www.iana.org/assignments/uri-             requires a RFC and work through     reason to go the RFC route.
                                               schemes                                          the IETF.
                                                                                                3) Call the address identifier      Craig C. and Claudio to word-smith text
                                                                                                something other than a URL. We      that allows both URLs and FC specific
Editor-003      T         111                                                                   could make up a new term.           protocol strings (i.e., "SNMP:...").          O




                                                                                           Page 16 of 91
                                                                          FC-GS-4 Revision 7.6 Comments
                                                                                    09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                               Problem Description                      Suggested solution                          Response                   Status     Edit Status
             /Edito Page    figure locator
               rial
QLogic-021      T       111 6.2.3.2.7      This definition is too loose for                We need to come up with a more Transform the note to normative text.
                                           interoperability.                               rigorous definiton of Management Change to "The format of the
                                                                                           Address.                         Management Address shall be based on
                                                                                                                            the format of the Uniform Resource Lo-
                                                                                                                            cator
                                                                                                                            (URL). The general form of the URL shall
                                                                                                                            be:" Steve Wilson to look at entire
                                                                                                                            definition.

                                                                                                                              Initial proposal in 03-211v0. Claudio to
                                                                                                                              look at adding support for HTTPS and
                                                                                                                              SSH.                                         O
Andiamo-27     T         112 Table 135      The sizes are expressed with letters, not      Can we do better?                                                                      ??? How are
                                            references.                                                                                                                           these string
                                                                                                                                                                                  lengths
                                                                                                                                                                                  specified? Is is
                                                                                                                                                                                  simply the
                                                                                                                                                                                  length of the
                                                                                                                                                                                  printable string
                                                                                                                                                                                  push a '\0'? If
                                                                                                                                                                                  so, how do we
                                                                                                                                                                                  pad the payload
                                                                                                                                                                                  to a full word?

                                                                                                                                                                                  See 6.2.5.10.
                                                                                                                                                                                  Explain how
                                                                                                                                                                                  padding is done
                                                                                                                                 Yes.                                      O      with (256-m).
Andiamo-29     T         113 Table 137,     The encodings are different from those of      Update the MIB or update GS-4?
                             Note 43        the MIBs, old and new.                         Or nothing?                           Remove note 43.                           A      Done.
                             Table 136      Fabric Configuration server should allow for   In Table 136, define values 'c0 - ff'
QLogic-L01     T         113                Vendor Specific port types.                    to be Vendor Specific.                As suggested.                             A      Done.
Andiamo-31     T         114 Note 45        Is this still true?                            update                                Delete note and make 03h obsolete.        A      Done.




                                                                                        Page 17 of 91
                                                                           FC-GS-4 Revision 7.6 Comments
                                                                                      09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                             Problem Description                           Suggested solution                           Response                      Status      Edit Status
             /Edito Page    figure locator
               rial
                            Table 138      Add 0A to table for XFP                                                                I have sent this to the T11.2 reflector and
                                                                                                                                  had no objections for the following codes
                                                                                                                                  for Table 138:

                                                                                                                                  Encoded Value (hex) - Description
                                                                                                                                  0A - XFP
                                                                                                                                  0B - X2 Short
                                                                                                                                  0C - X2 Medium
                                                                                                                                  0D - X2 Tall
                                                                                                                                  0E - XPAK Short
                                                                                                                                  0F - XPAK Medium
                                                                                                                                  10 - XPAK Tall
                                                                                                                                  11 - XENPAK
McDATA-42      T         114                                                                                                                                                      A      Done.
                         115 6.2.3.3.6       As a result of RTIN being removed from FS
                             Attached Port   this bit should be made obsolete.
IBM-147        T             Name                                                                                                 See McDATA-43                                   A      Done.
                             Table 141       Bit 0 should be for GTIN instead of RTIN.        Change Report to Get.               Obsolete this bit and use another bit for
McDATA-43      T         115                                                                                                      GTIN.                                           A      Done.
                         116 Table 142      The term << user frame >> is used two
                                            times. I don't know what that is but I think it
IBM-148        T                            should be just << frame >>.                                                           Remover "user".                                 A      Done.
                         117 6.2.3.3.9 Port The statement << Speed not established' bit
                             Operating      is set. >> should be << Speed not
                             Speed          established' bit is set to one. >> I think.                                           Correct this sentence and the previous
IBM-151        T                                                                                                                  sentence.                                       A      Done.
                             Figure 6        The "0..* 1" notation seems oddly placed. I correct"0..*1" notation and move
                                             think the note under port is covering up part "Not Specified" text into box.
                                             of this notation. The "Not Specified in this
                                             standard" would be better in the box with -                                          George to fix and provide new figure with
                                             "FC-4 specific attributes" instead of floating                                       source. Also need to supply a reference
McDATA-44      T         119                 out in space.                                                                        or defninition for how to read UML.             A      Done.
                         121 Table 150       The statement << NOTE 46 - Unique
                                             Vendor ID Strings are maintained by ANSI
                                             T10. A list of current Vendor ID Strings and
                                             instructions for requesting a new Vendor ID
                                             String can be found on the T10 web site at
                                             \217www.t10.org\220.<CRLF> >> needs to                                                                                                      Done. Also,
                                             change to << NOTE 46 - The vendor                                                                                                           converted to a
                                             identification shall be one assigned by                                                                                                     table footnote to
                                             INCITS. A list of assigned vendor                                                                                                           be consistent
                                             identifications is on the T10 web site                                                                                                      with other
IBM-153        T                             (www.T10.org). >>                                                                    These are assigned by INCITS.                   A      tables.
Andiamo-34     T         123 Note 47         I did not find them in such a MIB.             Put the reference to the right MIB,
                                                                                            or the new MIB                        Remove note 47.                                 A      Done.



                                                                                          Page 18 of 91
                                                                            FC-GS-4 Revision 7.6 Comments
                                                                                       09/23/03 (03-083vA)


              Techn
               ical Physical Section/table/
 Company-#                                               Problem Description                          Suggested solution                           Response                    Status     Edit Status
              /Edito Page     figure locator
                rial
                             6.2.3.4.3,      Hubs and Switches are not Platform                Remove hubs and switches from
Brocade-007      T       123 Table 152       devices.                                          table.                              See IBM-155.                                  A      Done.
                         123 table 152       Don't believe Hub, Switch, Storage device
                                             should be included. Not consistent with                                               Remove Hub, Switch and Storage
IBM-155          T                           proceeding table.                                                                     Device from table 152.                        A      Done.
                         126 6.2.3.4.5       The statement << attribute. This means that                                           Change "attribute. This means that
                             Attribute       any value shall be accepted for this attribute.                                       any value shall be accepted for this
                             Entry Format >> should be << attribute (i.e., any value is                                            attribute." to "attribute, and any value
IBM-159          T                           valid). >>.                                                                           shall be accepted for this attribute."        A      Done.
                             Supported       This references 5.1.2.7 which is invalid.         Shouldn't this reference 5.2.3.8?
McDATA-48        T       126 FC-4 Types Does this support multiple FC-4s?                                                        Accept the proposed solution.                   A      Done.
                             subclause       Although the content of the OS LUN Map           Change "The OS LUN Map Entry
                             6.2.3.4.9.1,    Entry includes the content of the                contains port information for both
                             paragraph 2, HBA_FCPBindingEntry structure, the GS-4             the mapped OS LUN and FCP
                             sentence 2      OS LUN Map Entry is intended to represent        LUN, and is based directly on the
                                             HBA API Target Mappings, while the               HBA_FCPBindingEntry structure
                                             HBA_FCPBindingEntry structure relates to         defined in the Common HBA API
                                             HBA API Persistent Bindings. As these two        (see FC-HBA)" to "The OS LUN
                                             concepts are often relates to HBA API            Map Entry contains port
                                             Persistent Bindings. As these two concepts       information for both the mapped
                                             are often confused, this could easily mislead    OS LUN and FCP LUN. It is based
                                             an implementer to register the wrong thing.      directly on the content of the
                                                                                              HBA_FCPBindingEntry structure
                                                                                              defined in the Common HBA API;
                                                                                              however, it represents what is
                                                                                              referenced as a Target Mapping in
                                                                                              the Common HBA API (see FC-
Emulex-007      T          127                                                                HBA)"                              As suggested.                                   A      Done.
Andiamo-36      T          128 Table 157      The size "x-4" or "y-4" are a little convoluted Could we do better?                Yes! Remove '-4' from 'x' and 'y' and add
                                              to understand.                                                                     a note both to the table and the text
                                                                                                                                 explaning that the length of the string has
                                                                                                                                 4 extra bytes for the preceeding fields.
                                                                                                                                 Remove the definitions in '()''s from the
                                                                                                                                 table.

                                                                                                                                   Remove subclauses for table field
                                                                                                                                   definitions (to be consistent with other
                                                                                                                                   tables in document).                          A      Done.




                                                                                          Page 19 of 91
                                                                           FC-GS-4 Revision 7.6 Comments
                                                                                      09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                               Problem Description                           Suggested solution                             Response                      Status      Edit Status
             /Edito Page    figure locator
               rial
                                                                                              Eliminate the items FCP LUN
                                                                                              Name Length, FCP LUN Name
                                                                                              Format, and the following reserved
                                                                                              field from Table 157 and
                                                                                              subclauses 6.2.3.4.9.4 and
                                                                                              6.2.3.4.9.5. In Table 157, change
                                                                                              the length of FCP LUN Name
                                                                                              Value to "see SPC-3". Change
                                                                                              the body of 6.2.3.4.9.6 to "An
                                                                                              Identification Descriptor of
                                                                                              association zero for the logical unit
                                                                                              to which the OS LUN maps (see
                                                                                              SPC-3). A platform that supports
                                                                                              FC-HBA Target Mapping (see FC-
                                                                                              HBA) shall register the same
                                                                                              Identification Descriptor for a
                                                                                              mapping as it returns via the                                                                  ??? Proposal
                                                                                              FC_HBA interface. NOTE x: The                                                                  not complete
                                                                                              length and format of this field are                                                            (i.e., The
                                                                                              embedded in its value in accord                                                                descriptions
                                                                                              with SPC-3." Add normative                                                                     below table 157
                                                                                              references "ANSI/INCITS                                                                        were not
                                                                                              xxx/200x, SCSI Primary                                                                         updated to
                                             The FCP LUN Name Value field is required         Commands - 3 (SPC-3) T10                                                                       reflect new table
                                             to be determined by an SPC-3 Device              Project 1416-D" and                                                                            contents).
                                             Identification VPD Page Identification           "ANSI/INCITS xxx/200x, Fibre                                                                   Proposer needs
                                             Descriptor of association 0. The                 Channel - HBA API (FC-HBA) T11                                                                 to provide
                                             representation of the FCP LUN Name here          Project 1568-D"                                                                                updates
                                             completely obscures this requirement, and                                                                                                       requested by
Emulex-L01     T         129 6.2.3.4.9       in a few cases, prevents its representation.                                             Fixed by 03-430v0.                              A      editor.
                             Table 158       What is an LU identifier?                        Identify it.                            Remove Table 158. Change "All values
                                                                                                                                      (except “not mapped”) are defined by the
                                                                                                                                      Common HBA API (see FC-HBA).
                                                                                                                                      FCP Binding Types are defined in table
                                                                                                                                      158." to "All values except zero (i.e., not            Done, plus
                                                                                                                                      mapped) are defined by the Common                      added FC-HBA
                                                                                                                                      HBA API HBA_Bind_Type declaration                      to references
McDATA-50      T         129                                                                                                          (see FC-HBA).".                                 A      section.
Andiamo-37     T         130                 The definition of "OS Device Name Length" Update
                                             is missing. The definition of OS SCSI LUN is                                             Add: "OS Device Name Length: The
                                             out of order                                                                             length (in bytes) of the OS Device Name.
                                                                                                                                      Length includes OS Device Name                         Done. With
                                                                                                                                      Length and OS Device Name."                            some addtions
                                                                                                                                                                                      A      for clarity.




                                                                                            Page 20 of 91
                                                                              FC-GS-4 Revision 7.6 Comments
                                                                                         09/23/03 (03-083vA)


              Techn
               ical Physical Section/table/
 Company-#                                              Problem Description                               Suggested solution                          Response                       Status     Edit Status
              /Edito Page     figure locator
                rial
                             table 159       Reason Code Explanations x'64' -x'6F' are           Reassign codes for these reasons                                                             ??? Done, but
                                             already used by for switch to switch vendor         starting at x'70'. Reserve                                                                   part of the
                                             implemenation of the Platform database                                                                                                           Suggested
                                                                                                                                                                                              solution is
                                                                                                                                                                                              missing. Did I
                                                                                                                                                                                              do everything
Brocade-023     T         131                                                                                                        As suggested.                                     A      requested?
Andiamo-38      T         132 6.2.4.1         This entire Section should be placed under         update                              Move clause 6.2.4.1 to be a subclause of
                                              the "Port Object" section, 6.2.3.3.                                                    6.2.3.2.                                          A      Done.
                                6.2.4.1       F_Port Name is not described below Table           Explain that the F_Port_Name is
                                              160.                                               defined in FC-FS or something.      Editor will add F_Port Name to 6.2.4.1.

                                                                                                                                     F_Port_Name: This field contains the
                                                                                                                                     F_Port_Name of the switch port that the
McDATA-51       T         132                                                                                                        enforcment status object is referencing.          A      Done.
                              6.2.5.18, first The first sentence says that the Domain_ID         Either remove this sentence, or
                              sentence        is returned with a reject, but this is no longer   define a new method for notifying
                                              true with the way the Hard Zone Reject has         of the Domain_ID.
Editor-003      T         146                 been changed.                                                                          Remove first paragraph of 6.2.5.18.               A      Done.
                              Table 196       Describe Interconnect Element Name.                Explain what should go in the field
                                                                                                 below the table.                    Editor will add description of Interconnect
                                                                                                                                     Element Name.

                                                                                                                                     Add the following definiton to clause 3:

                                                                                                                                     Interconnect Element: Any device in a
                                                                                                                                     fabric that assists in the transport of Fibre
McDATA-16       T         146                                                                                                        Channel frames between FC_Ports.                  A      Done.
Andiamo-40      T         154 6.2.5.29        Can we enforce uniqueness?                         Discuss                             George Penokie will coordinate a
                                                                                                                                     solution for this in FC-GS-4 with the
                                                                                                                                     switch vendors. See 03-158v2 for final
                                                                                                                                     solution.                                         A      Done.
                                Overview      There is no mention of what the Unzoned            First we'll need overview text and                                                           Done. Moved to
                                              Name Server does for Broadcast and Hard            then explanations of how the                                                                 the end of
                                              Zoning. How shall it report broadcast zones        Unzoned Name Server shall report                                                             6.3.2.1 since no
                                              and Hard Zones?                                    queries with broadcast and hard    Remove all text and figures from "An                      specific
                                                                                                 zoning.                            example of Zoned and Un-zoned                             destination was
                                                                                                                                    access is illustrated in figure 7..." to the              named in the
McDATA-55       T         165                                                                                                       beginning of clause 6.3.2.                         A      reponse.
                              6.4.1 second This zoning mechanism is not one of the               Remove this item.
Brocade-029     T         168 list item d     enumerated types. - see table 245                                                     This is a new type in Table 261 value 06.          R
QLogic-025      T         168             6.4 A definition of Default Zones needs to be          The commentor will provide a       Craig C. action item. (Take Brocade-012
                                              provided.                                          proposl to accomplish this.        in consideration.)                                 O




                                                                                             Page 21 of 91
                                                                          FC-GS-4 Revision 7.6 Comments
                                                                                    09/23/03 (03-083vA)


              Techn
               ical Physical Section/table/
 Company-#                                               Problem Description                        Suggested solution                              Response                    Status     Edit Status
              /Edito Page    figure locator
                rial
                             6.4.2, second For Enhanced Zoning, the concepts of Zone        Do not include the enforced or
                             and third      Set Database and Zoning Database are still      active zone set as part of the
                             bullets        confusing. There really is just one database,   Zoning database and remove the          See minutes for 4/29 conference call for
                                            the zoning database, that includes all          Zone Set Database.                      resolution. Harry Paul to post document
                                            defined zone sets. Then there is the                                                    with text chagnes. Figure to be changed
                                            enforced Zone Set that is based on a Zone                                               as documented in minutes.
                                            Set defined in the Zoning Database.
Brocade-010      T       170                                                                                                        Posted as 03-267v1.                           O
                             6.4.2,paragra The term "default zone" should really be         Tighten up the definition of default
                             ph 5           "default zoning". There is no default zone      zone/zoning.
Brocade-012      T       170                per se.                                                                                 See QLogic-025.                               O
                         170 6.4.2          I cannot see any way to reword this so to
                             Terminology make it useful for the standard so I think it
                                            should be deleted <<To understand how
                                            Activate and Deactivate work, it is useful to
                                            understand the relationship
                                            between<CRLF>the Zone Set Database and
IBM-181          T                          the Zone Enforcement Entity. >>                                                         Useful for opening discussion.                R
                         170 6.4.2          The statement << note that<CRLF>the Zone
                             Terminology Set is not stored in the database, and
                                            therefore Zone and Zone Member objects
                                            cannot be<CRLF>added to or removed from
                                            this Zone Set. The contents of this Zone Set
                                            may be queried, however. >> should be
                                            made into a separate note and the <<
                                            cannot be >> changed to << are not >>.
IBM-183          T                                                                                                                  As suggested. Also, remove ", however".       A      Done.
                             6.4.2          The definition of the Zone Set database is      Change to :"Zone Set
                                            true but not sufficient.                        Database:the database of the
                                                                                            Zone Sets available to be
McDATA-56       T         170                                                               activated within a fabric.              As suggested.                                 A      Done.
QLogic-026      T         170 6.4.2          Clarify the Zone Set Database after a Zone     I think the way it is supposed to
                                             Set is activated.                              work is this:
                                                                                            When a Zone Set is activated, the
                                                                                            Zone Set is copied to the zoning
                                                                                            enforcement entity, and the Zone
                                                                                            Set Database retains a copy of the
                                                                                            Zone Set just activated. If the
                                                                                            Zone Set in the Zone Set
                                                                                            Database with the same name as          Add the following to the Basic Zoning
                                                                                            the Active Zone Set is editted, it      overview: "The zone set name of the
                                                                                            will be different from the Active       activated zone set has no relation to any
                                                                                            Zone Set until it is activated again.   zone set name in the database (i.e.,
                                                                                                                                    changes to the zone set database do not
                                                                                                                                    affect the active zone set)".                 A      Done.



                                                                                          Page 22 of 91
                                                                              FC-GS-4 Revision 7.6 Comments
                                                                                        09/23/03 (03-083vA)


              Techn
               ical Physical Section/table/
 Company-#                                               Problem Description                      Suggested solution                                    Response                    Status      Edit Status
              /Edito Page    figure locator
                rial
                             6.4.2          "A change in the Active Zone set shall cause Clarify exactly when an RSCN
                                            a Registered State Change Notification       must be sent.                                  Change text to: "A change in the Active
                                            (RSCN) Extended Link Service to be                                                          Zone set shall cause a Registered State
                                            originated to all Zone Members affected that                                                Change Notification (RSCN) Extended
                                            are registered to receive RSCN." - this                                                     Link Service to be originated. The RSCN
                                            statement is vague. Does the switch have to                                                 may be sent to all Nx_Ports that are
                                            determine which zone members are affected                                                   registered to receive RSCN or only to
                                            and which are not?                                                                          affected Nx_Ports that are registererd to
                                                                                                                                        receive RSCN. The determination of
                                                                                                                                        affected Nx_Ports is outside the scope of            Done. WIth
Brocade-034     T         171                                                                                                           this standard."                               A      corrections.
                                             "Shall" should be "should". I do not believe Change "shall" to "should".
                                6.4.4.1, first
                                paragraph    all implementations or configurations require
Brocade-016     T         172                a GFEZ to be used.                                                                         As suggested.                                 A      Done.
                          172 6.4.4.1        The statement << payloads will be rejected
                              Overview,      by >> should be << payloads shall be
IBM-187         T             3rd para       rejected by >>                                                                             See McDATA-63.                                O
                          172 6.4.4.1        The statement << payloads will be rejected
                              Overview, 4th by >> should be << payloads shall be
IBM-188         T             para           rejected by >>                                                                             As suggested.                                 A      Done.
                              Figure 10      This figure is incomplete without the Session Add SSB and SSE into the                     Add "Session Commands" block to Basic
                                             commands.                                     diagram.                                     Zoning Mode and state that this is
McDATA-61       T         172                                                                                                           optional.                                     A      Done.
                              first sentence Is "shall query" necessary?                   Change to "should".
McDATA-62       T         172                                                                                                           Accept the proposed solution.                 A      Done.
                              third          "Basic Zoning commands and payloads will Change to "may be rejected".                      Proposed change: "Basic Zoning
                              paragraph      be rejected by the Fabric Zone Server." is                                                 commands and payloads will be rejected
                                             unecessary. Management applications                                                        by the Fabric Zone Server." to "Basic
                                             should still be able to query the fabric with                                              Zoning commands that modify the zoning
                                             basic zoning commands. There is no                                                         configuration shall be rejected by the
                                             reason to obsolete these programs.                                                         Fabric Zone Server. Basic Zoning
                                                                                                                                        queries may be rejected by the Fabric
                                                                                                                                        Zone Server.".

McDATA-63       T         172                                                                                                           Proposed change accepted.                     A      Done.
Andiamo-41      T         173 6.4.5.2            Text says: "If all Zones are removed from a   Clarify: is this a requirement for the
                                                 Zone Set, that Zone Set shall also be         management application, or for
                                                 removed. If all Zone Members are removed      the Zone Server? What about              Clarify this is for basic Zoning, not
                                                 from a Zone, that Zone shall also be          enhanced zoning? I believe that          enhanced Zoning. Clarify that this is an
                                                 removed."                                     this does not apply to enhanced          implicit deletion by the Fabric Zone
                                                                                               Zoning.                                  Server. Editor will wordsmith.                A      Pending.




                                                                                           Page 23 of 91
                                                                           FC-GS-4 Revision 7.6 Comments
                                                                                      09/23/03 (03-083vA)


              Techn
               ical Physical Section/table/
 Company-#                                                 Problem Description                        Suggested solution                             Response                     Status     Edit Status
              /Edito Page     figure locator
                rial
                             6.4.5.2 5th     These paragraphs state the following two          clarify what is done with a Zoneset
                             and 6th         rules: "A request to add a Zone Set with          with zero Zones
                             paragraphs zero Zones shall not be considered an error.
                                             If all Zones are removed from a Zone Set,
                                             that Zone Set shall also be removed."
                                             When a Zoneset with sero Zones is added is
                                             it automatically removed? - see also
                                             6.4.9.4.12
Brocade-038      T       173                                                                                                         Withdrawn by commentor.                       W
                             6.4.5.2, 5th    What is the point of adding a zone set with       Add text to explain why.
McDATA-65        T       173 paragraph       no members?                                                                                                                            R
                             6.4.5.3         What is the point of stating "The Fabric          Delete the sentence and 6.4.5.3.
                                             Zone Server may reject any query requests
                                             for reasons not specified in this document."
                                             We might as well say do whatever you want.
McDATA-66        T       173                                                                                                         Accept the proposed solution.                  A      Done.
                             last sentence Why do we need to say that Basic Zoning             Delete this sentence.
                             of first        Management is for backward compatibility?
                             paragraph       Some people may prefer to use Basic.
McDATA-67        T       173                                                                                                         Accept the proposed solution.                  A      Done.
                             Second          " Differently from what is specified for          Change to " SSB and SSE work at
                             paragraph,      Enhanced Zoning (see 6.4.6), in Basic             the fabric level. SSB and SSE         Change to: "In contrast to Enhanced
                             second          Zoning no Fabric behavior is associated with      trigger a set of management           Zoning (see 6.4.6), Basic Zoning defines              Done. I replaced
                             sentence.       SSB and SSE; they act at the Switch level.        requests to achieve a lock on the     no Fabric behavior associated with SSB                the second
                                             They permit to relate together a set of           fabric.                               and SSE. In Basic Zoning, SSB and SSE                 setence as
                                             management requests, and to achieve a                                                   act only within a Switch (i.e., not Fabric            directed by the
                                             consistent behavior for the case of                                                     wide). SSB and SSE allow a set of                     comment, plus I
                                             two or more management applications                                                     management requests to be related to                  also removed
                                             operating over the same Switch." should be                                              each other within a single Switch. This               the third
                                             worded better. It is also untrue that GS                                                relationship may be used to achieve a                 sentence since I
                                             Sessions are switch based. They are fabric                                              consistent behavior when two or more                  believe this was
                                             based for any SSB.                                                                      management applications operate on a                  implicit in the
McDATA-68        T       173                                                                                                         single Switch."                                A      Response.
                             Table 245       In the atributes there is not a "number of        modify to "Zone Name; Number of
                             AZM             Zone Members" as in other commands.               Zone Members, List of Zone
                                                                                               Member Identifier Types and Zone
Brocade-039     T         175                                                                  Member Identifiers"                 Corrected in Enhanced Zoning.                    R
                                6.4.6.1      After the first GS session add (see 4.9.5.1).     Add "(see 4.9.5.1)" and add text in Replace all instances of "GS session"
                                             The only problem is that 4.9.5.1 doesn't          4.9.5.1 calling it a GS session.    with "Zoning session" in clause 6.4.6
McDATA-75       T         175                mention the term GS session.                                                          (Enhanced Zoning Management).                    A      Done.
                                6.4.6.2.1    Does a switch which does not support hard         Clarify this operation in the 5th
                                             zoning have to reject FLOGI from a device         paragraph
                                             which logs in after it has been included in a                                         This is covered by "not enough
Brocade-044     T         176                hard zone?                                                                            resources".                                      R




                                                                                             Page 24 of 91
                                                                               FC-GS-4 Revision 7.6 Comments
                                                                                           09/23/03 (03-083vA)


              Techn
               ical Physical Section/table/
 Company-#                                                Problem Description                      Suggested solution                      Response                             Status      Edit Status
              /Edito Page    figure locator
                rial
                             6.4.6.2.2.2    "This implies that if zoning…" Is this a rule or Remove the implication and make
                                            not. Implications are not part of a standard. a rule
                                            Also, is this what we want as a rule? If
                                            broadcast attributes are not defined then
                                            devices in the same zone cannot
                                            communicate with broadcast frames?
Brocade-046      T       176                                                                                                 Remove "This implies that".                          A      Done.
                         176 6.4.6.2.1      I don't know what this is trying to say but
                             Hard Zoning whatever it is it is not clear and needs to be                                                                                                  ??? Provided file
                                            fixed << enforces in hard manner an Hard                                                                                                     does not
                                            Zone, it shall enforce in the same manner all                                                                                                reference a valid
                                            the other Zones relevant to that F_Port. >>                                                                                                  clause in GS-4.
                                                                                                                                                                                         Where is this
IBM-198         T                                                                                                                     Closed by 03-377v0.                         A      meant to go?
                                6.4.6.2.1, fifth Poor wording again. I think I captured what       Change to: "To allow a Zoning
                                paragraph        was intended in the resolution column. If         configuration in which the
                                                 this is not correct, what is the point of the     enforcement is soft for some
                                                 soft zone since the soft ports won't be able      devices and hard for others, the
                                                 to communicate with the hard ports?               administrator should configure as
                                                                                                   many F_Ports as possible as Hard
McDATA-80       T         176                                                                      Zoned.                             See IBM-198.                                A
                                6.4.6.2.1,     The sentence is misleading and I'm not sure         I'm not sure if this is the right
                                third          what "it" refers to. If "it"refers to the F_Port,   solution, but we might change the
                                paragraph      how can the F_Port ensure that other                text to " To allow the coexistence
                                               switches enforce the hard zone in the same          across the same Fabric of Hard
                                               manner? What are best-effort zones? Shall           and flaccid Zones, an F_Port that
                                               we call them flaccid zones?                         enforces hard zoning on a frame-
                                                                                                   by-frame basis shall enforce all
                                                                                                   Zones relevant to that F_Port in
                                                                                                   the same manner."
McDATA-81       T         176                                                                                                         See McDATA-80.                              A
McDATA-82       T         176 6.4.6.2.2.1      Why is multi-protocol devices specified?            Delete "multi-protocol".           Accept the proposed solution.               A      Done.
                              6.4.6.2.2.2      "Zoning is enforced at the destination port."       Change this statement to:          Change to "Broadcast zoning shall be
                                               is incorrect and should limited to broadcast        "Broadcast zoning is enforced at   enforced at the destination switch with
McDATA-83       T         176                  zoning at the destinatin switch.                    the destination switch."           respect to each destination port."          A      Done.




                                                                                               Page 25 of 91
                                                                          FC-GS-4 Revision 7.6 Comments
                                                                                     09/23/03 (03-083vA)


              Techn
               ical Physical Section/table/
 Company-#                                               Problem Description                         Suggested solution                          Response                   Status     Edit Status
              /Edito Page    figure locator
                rial
QLogic-027       T       176 6.4.6.2.2.3    Does this mean that broadcast frames are        The word "Broadcast" could be
                                            delivered to all N-ports if there are no        removed from the heading of                                                              ??? No, the
                                            broadcast zones even if there is an Active      6.4.6.2.2.2 and 6.4.6.2.2.3 (which I                                                     suggested
                                            Zone Set (contradicts 6.4.6.2.2.2)?             believe restores the original text).                                                     solution is
                                                                                            Then the text in 6.4.6.2.2.2                                                             incorrect. These
                                                                                            describes how broadcast is                                                               cluases apply to
                                                                                            handled if there is an Active Zone                                                       Braodcast
                                                                                            Set, and the text in 6.4.6.2.2.3                                                         Zoning only.
                                                                                            describes how broadcast is           Accept the proposed solution. Mike                  Craig C. to
                                                                                            handled if there is no Active Zone ODonnell will reexamine broadcast                     clarify language
                                                                                            Set.                                 behavior with respect to Default Zone               which results in
                                                                                                                                 management.                                  A      contradictions.
                               6.4.6.2.1      "then the Fabric shall reject the FLOGI       FLOGI should be accepted. The
                                             requests."                                     zoning management should be
                                             Situation when device, which is currently      done on the different level.
                                             included into a hard zone, receives FLOGI
                                             RJT from a Fabric and after that is removed
                                             from this zone. Such a device may be not
                                             capable to reattempt FLOGI to a Fabric
                                             having the new hard zone configuration.
SANCastle-
L01             T         176                                                                                                   Bill Martin to persue.                        O
Andiamo-42      T         177 6.4.6.3        The text tells about consistency checks, but Define the consistency checks         Also in the preceding paragraph change
                                             they are not defined                                                               "As part of the commit function, the
                                                                                                                                Fabric Zone server ensures that the
                                                                                                                                changes made to the client‟s instance of
                                                                                                                                the database are propagated through the
                                                                                                                                Fabric." to "As part of the commit
                                                                                                                                function, the Fabric Zone server shall
                                                                                                                                propagate the changes made to the
                                                                                                                                client‟s instance of the database through
                                                                                                                                the Fabric.".

                                                                                                                                Also see 03-514v1.                            A
Andiamo-43      T         177 6.4.6.5        Add the timeout rule specified in FC-SW-3:     update
                                             If a management application does not                                               Add description of the FC-SW-3 timeout
                                             interact with the Fabric Zone Server for 2                                         rule to bullet d) of the "Management of
                                             minutes, then the session is automatically                                         the Zone Set Database is subject to the
                                             released                                                                           following rules:" list.

                                                                                                                                Also, remove bullet a) of the list.           A      Ponder.
                              6.4.6.3        Rules for consistency checking do not          Make rules regarding consistency
                              paragraph 3    appear to be consistent. What is the           checking consistent
                              and 6.4.6.5    "management function" in this case?
Brocade-017     T         177 item a.                                                                                           See Andiamo-42.                               A



                                                                                          Page 26 of 91
                                                                          FC-GS-4 Revision 7.6 Comments
                                                                                     09/23/03 (03-083vA)


              Techn
               ical Physical Section/table/
 Company-#                                              Problem Description                         Suggested solution                           Response                      Status     Edit Status
              /Edito Page    figure locator
                rial
                             6.4.6.2.2.4    "See FC-FLA." - a standard should not            Remove the reference to FLA         Change entire clause to: "If any NL_Port
                                            reference a technical report as a reason for                                         attached to an FL_Port shares a                        ??? Done, but I
                                            a rule.                                                                              broadcast zone with the source of the                  think it should
                                                                                                                                 broadcast                                              say "or
                                                                                                                                 frame, or zoning is not active, the frame              broadcast
                                                                                                                                 shall be sent to the all the devices on the            zoning not
Brocade-047     T         177                                                                                                    loop."                                          A      active".
                                6.4.6.3      Should we name the separate instance of         Name the separate instance the
                                             the zoning Database? What happens to the        "Session Zoning Database". Say
                                             separate instance of the Zoning Database        the Session Zoning Database is      Change second paragraph to: When the
                                             when the session ends or is terminated?         purged at the end of the session.   SSB request is received, the Fabric Zone
                                                                                                                                 server creates and maintains a
                                                                                                                                 temporary instance
                                                                                                                                 of the Zoning Database on behalf of the
                                                                                                                                 requesting client. Any changes requested
                                                                                                                                 by the client
                                                                                                                                 are then made to the client‟s temporary
                                                                                                                                 instance of the Zoning Database. Once
                                                                                                                                 the client has completed all
                                                                                                                                 changes and updates to its temporary
                                                                                                                                 instance of the database, the client
                                                                                                                                 issues a Commit Zone Changes request
                                                                                                                                 to the Fabric Zone server. As part of the
                                                                                                                                 commit function, the Fabric Zone server
                                                                                                                                 ensures that
                                                                                                                                 the changes made to the client‟s
                                                                                                                                 temporary instance of the database are
                                                                                                                                 propagated through the Fabric. After the
                                                                                                                                 SSE request is received, the tempory
                                                                                                                                 instance of the Zoning Database is
McDATA-85       T         177                                                                                                    deleted.                                        A




                                                                                           Page 27 of 91
                                                                          FC-GS-4 Revision 7.6 Comments
                                                                                     09/23/03 (03-083vA)


              Techn
               ical Physical Section/table/
 Company-#                                                Problem Description                       Suggested solution                           Response                      Status      Edit Status
              /Edito Page    figure locator
                rial
                             6.4.6.5        It would be helpful to add a column to           Remove "issuing" in all cases.
                                            specify which section each subtype is            Remove text describing the local
                                            specified in.                                    instance unless it has some effect                                                         ??? Partial.
                                                                                             on the client.                                                                             Text change has
                                                                                                                                  Change "Query commands return                         been done, but
                                                                                                                                  information based on the issuing client‟s             which table?
                                                                                                                                  view of the Zoning Database. If the                   There is no table
                                                                                                                                  Fabric Zone Server is currently                       in this clause,
                                                                                                                                  maintaining a local instance of the                   and Table 130 is
                                                                                                                                  database on behalf of the issuing client,             in clause 6.1. I
                                                                                                                                  then the results of the query commands                have no
                                                                                                                                  are based on information in maintained in             problem adding
                                                                                                                                  the local instance." to "Query commands               a list of clause
                                                                                                                                  return information based on the client‟s              refences in
                                                                                                                                  view of the Zoning Database. If the                   Table 130, but is
                                                                                                                                  Fabric Zone Server is currently                       that what this
                                                                                                                                  maintaining a local instance of the                   comment is
                                                                                                                                  database on behalf of the client, then the            referencing?
                                                                                                                                  results of the query commands are                     McDATA-38
                                                                                                                                  based on information in maintained in the             already requests
                                                                                                                                  local instance".                                      this change, and
                                                                                                                                                                                        I am willing to
                                                                                                                                  Editor to add column to Table 130 as                  accept that
McDATA-86       T         177                                                                                                     prosposed.                                     A      comment.
                              6.4.6.6, table The x'0400' for the CMIT is in a range    Change code to something not                                                                     Done. CMIT
                              246            reserved for use by FC-SW-3. See Brocade- reserved by FC-SW-3                                                                              code changed to
Brocade-011     T         178                004                                                                                  Editor to pick a new code.                     A      0x7FFB.

                                                                                             The following statement would be
                                                                                             added to the end of 6.2.4 of GS-4:

                                                                                             After a successful Zone Merge,
                                                                                             the Zone Set Name will change to
                                             The current standards do not specify what       " Successful Zone Set Merge:
                                             the Zone Set Name is after two zones            Active Zone Set Name has
                                             merge. There is also no indication that the     changed".
McDATA-L01      T         181           10.2 Active Zone Set has changed.




                                                                                           Page 28 of 91
                                                                         FC-GS-4 Revision 7.6 Comments
                                                                                    09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                               Problem Description                      Suggested solution                           Response                 Status   Edit Status
             /Edito Page     figure locator
               rial
Andiamo-44      T       184 Note 50         State that use of type 02 is also problematic Update, recommending the use of
                                            when a Fabric reconfiguration occurs. Also stable identifiers, such as           Add the following additional note: "Fabric
                                            type 03 is sensitive to this problem.         N_Port_Names.                      rebuilds may result in Domain IDs being
                                                                                                                             reassigned resulting in unpredictable
                                                                                                                             zoning enforcement behavior for Zone
                                                                                                                             Member Identifier Types 02 and 03.
                                                                                                                             Loop Initialization events may result in
                                                                                                                             arbitrated loop address reassignment
                                                                                                                             resulting in unpredictable zoning
                                                                                                                             enforcement behavior for Zone Member
                                                                                                                             Identifier Type 03."                         A    Done.
                            6.4.7.3         The data structures (zone objects) defined in Add a field length column for each
                                            this subclause do not have field lengths      data structure table.
Editor-002      T       186                 defined.                                                                         See 03-514v1.                                A
                        189 6.4.7.3.3       The statement << (expressed over 4 bytes)
                            Zone Set        >> should be deleted and the << n >> in
                            Object          table 256 replaced with << 0 - FFFF FFFFh
IBM-209         T                           >>                                                                               See Editor-002.                              A
                        190 6.4.7.3.5.1     The statement << (expressed over 4 bytes)
                            Zone Object >> should be deleted and the << n >> in
                            in the Zone     table 258 replaced with << 0 - FFFF FFFFh
                            Set Database >>
IBM-212         T                                                                                                            See Editor-002.                              A
                        191 Table 259       Replace the << m >> and << n >> with
                                            numeric ranges. For example 0 - FFFF
IBM-214         T                           FFFFh.                                                                           See Editor-002.                              A
Andiamo-46      T       192 Note            State that use of type 02 is also problematic Update, recommending the use of
                                            when a Fabric reconfiguration occurs. Also stable identifiers, such as
                                            type 03 is sensitive to this problem.         N_Port_Names or F_Port_Names.
                                                                                                                             See Andiamo-044.                             A    Done.
                        193 6.4.7.3.6       The term << Vendor Specified >> should be
                            Zone            << Vendor Specific >> in all cases.
                            Member
IBM-215         T           Object                                                                                           As suggested.                                A    Done.
                        194 Table 264       Replace the << n >> with numeric range.
IBM-216         T                           For example 0 - FFFF FFFFh.                                                      See Editor-002.                              A
                            Table 268       Protocol attribute is never defined.          Define it or delete it.            Use definition in FC-SW-3 rev 6.2, clause
McDATA-89       T       195                                                                                                  10.4.4.8.1.1                                 A    Pending.




                                                                                       Page 29 of 91
                                                                           FC-GS-4 Revision 7.6 Comments
                                                                                      09/23/03 (03-083vA)


              Techn
               ical Physical Section/table/
 Company-#                                                Problem Description                   Suggested solution                                Response                      Status     Edit Status
              /Edito Page    figure locator
                rial
Andiamo-47       T       196 6.4.7.3.8      FC-4 types: the FC-4 type for which protocol update                                   Add to "FC-4 Type" (below Table 269):
                                            zoning is enforced. Do we want to add a                                               "Device_Data and FC-4 Link_Data
                                            definition of protocol Zoning, taking it from                                         frames not having the specified FC-4
                                            FC-SW-3?                                                                              Type value shall not be transmitted
                                                                                                                                  between members of the Zone. All other
                                                                                                                                  frames shall be transmitted between
                                                                                                                                  members                                                ??? Promoted to
                                                                                                                                  of the zone."                                   A      Technical.
                                6.4.7.3.8   Zone attribute value as defined must be at Values should be assigned to
                                            least 1 byte in meaningful length. Therefore, allow an attribute to be active and At top of page 196, change to: Zone
                                            Broadcast Attribute value must define         not active.                         Attribute Value: This field specifies the
                                            values other then null--0 bytes.                                                  actual attribute value if one exsits for the
                                                                                                                              specified Zone Attribute. If present,
                                                                                                                              Attribute Values shall be at least four
                                                                                                                              bytes in length and the length shall be a
                                                                                                                              multiple of four. For Attribute Value fields,
                                                                                                                              fill bytes are added as necessary to the
                                                                                                                              end of the actual value in order to ensure
                                                                                                                              that the length of the value field is a
                                                                                                                              multiple of four. Fill bytes shall be 00h.

                                                                                                                                  Table 268, add column "Zone Attribute
                                                                                                                                  Required", "Protocol = Yes", "Hard =
                                                                                                                                  None", "Broadcast = None", "Vendor
Inrange-001     T      196                                                                                                        Specfied = Yes".                                A
                                6.5.7.3.8   Zone attribute value as defined must be at Values should be assigned to
                                            least 1 byte in meaningful length. Therefore, allow an attribute to be active and
                                            Hard Zone Attribute Value (10.4.4.8.1.3)      not active.
                                            must define values other then null--0 bytes.
Inrange-002     T      196                                                                                                        See Inrage-002.                                 A
                                Table 269   Isn't there a reference to the FC-4 Type          Reference the definition.
McDATA-90       T         196               definition? We need one.                                                              Add reference to FC-FS.                         A      Done.
                                Bit 4       Does Zone Set Database supported mean             Clarify that it is in the fabric.
                                            that it's supported on the entry switch or in                                         Tables 276 and 277 state whether they
McDATA-94       T         200               the fabric?                                                                           are Fabric or Switch values.                    R
                                Table 277   This is a duplicate table to Table 276            Remove table
                                                                                                                                  Table 276 relates to Fabrics, Table 277
Brocade-056     T         201                                                                                                     relates to Switches, so they are different.     R
                                6.4.9.1.2   What happens when a switch that is not         Clarify
                                second      capable of operating in enhanced mode
                                paragraph   attempts to join a fabric that is operating in
                                            enhanced mode? How can this switch ever
Brocade-058     T         202               be joined to the fabric?                                                              Already specified as not allowed.               R




                                                                                            Page 30 of 91
                                                                              FC-GS-4 Revision 7.6 Comments
                                                                                           09/23/03 (03-083vA)


              Techn
               ical Physical Section/table/
 Company-#                                             Problem Description                              Suggested solution                              Response                   Status      Edit Status
              /Edito Page    figure locator
                rial
                             Table 279 bit default zone - This term is not defined              change to "Default Zoning Setting.
                             position 3     anywhere in the standard.                           When this bit is one, the managing
                                                                                                application is requesting the Fabric
                                                                                                to deny traffic between all devices
                                                                                                not in any zone in the active
                                                                                                zoneset. When this bit is zero, the
                                                                                                managing application is requesting
                                                                                                the Fabric to permit traffic between
                                                                                                all devices not in any zone in the
                                                                                                active zoneset."                                                                            ??? See QLogic-
Brocade-033     T         203                                                                                                           Possible resolution to QLogic-025.           O      025.
                                Table 279, bit There is no SW-3 command to distribute the We need a proposal in SW-3 to
                                2              Merge Control Setting.                          support this or it is invalid and will   SFC does contain a payload to distribute
McDATA-98       T         203                                                                  have to be removed.                      zoning policies.                             R
                                Table 279,     "to deny traffic" is only part of the solution. Change to "to deny traffic and
                                Bit 3          We could eliminate the definition of the 0 bit visibility between members of the
                                               setting.                                        Default Zone." If we leave the
                                                                                               definition of the zero bit setting, we   Accept the proposed solution. Also,
                                                                                               should say it "permits traffic and       change replace "between" with "among"
McDATA-99       T         203                                                                  visibility".                             in 2 cases where it is used.                 A
                                6.4.9.2.3      What reject reason codes should be used         Tell us about it.
McDATA-100      T         204                  when the CMIT fails?                                                                     Fixed in 03-514v1.                           A
                                6.4.9.3.13     All other add commands have "Number of          Add "Number of Zone Members"
                                               Zone Members"                                   to this command as in other add
Brocade-040     T         220                                                                  commands.                                Withdrawn by commentor.                     W
                                6.4.9.3.14     Why does Add Zone not allow adding              Increase payload and put "Number
                                               multiple zones in one command?                  of Zones" and multiple instances
Brocade-063     T         220                                                                  of "Zone Name"                           Withdrawn by commentor.                     W
                                6.4.9.3.15     Remove Zone Members should include              Add this 4 byte field in text and
                                               "Number of Members" before the list of          Table
Brocade-064     T         221                  members                                                                                  Withdrawn by commentor.                     W
                                6.4.9.3.16     Why does Remove Zone not allow removing Increase payload and put "Number
                                               multiple zones in one command?                  of Zones" and multiple instances
Brocade-065     T         222                                                                  of "Zone Name"                           Withdrawn by commentor.                     W
                                Table 276      Default Zone is never defined.                  Define it.                                                                                   ??? See QLogic-
McDATA-95       T         223                                                                                                           Awaiting definition from Editor.             O      025.
                                6.4.9.4.5      Is there an expectation that the zone set        Please clarify this in the document.
                                               does exist in the database?                                                              Add as the third paragraph, "If the
                                                                                                                                        specified zone set does not exist, the
                                                                                                                                        command shall be rejected with a reason
                                                                                                                                        code of „Unable to perform command
                                                                                                                                        request‟, and addtional resaon                      Partial. Refix to
McDATA-101      T         226                                                                                                           explanation of "Zone Set Unknown"."          A      new response.




                                                                                             Page 31 of 91
                                                                           FC-GS-4 Revision 7.6 Comments
                                                                                      09/23/03 (03-083vA)


              Techn
               ical Physical Section/table/
 Company-#                                               Problem Description                        Suggested solution                          Response                      Status   Edit Status
              /Edito Page    figure locator
                rial
                             Table 324      It would be helpful if the GZSE command          Add Number of Zones for each
                                            followed the format of the GZSN command.         Zone Set Name as in Table 290.
McDATA-102       T       226                                                                                                    Withdrawn by commentor.                        W
                             Table 326      It would be helpful if the GZDE command          Add Number of Zone Members for
McDATA-103       T       227                followed the format of the GZD command.          each Zone as in Table 292.         Withdrawn by commentor.                        W
                             6.4.9.4.12     Is there a problem if a Zone in the Zone Set     Please explain what to do if the   No, there is not a problem if a Zone does
                                            does not exist?                                  Zone does not exist or if it is    not exist. Add a sentence: "The specified
                                                                                             allowed.                           zones may not exist at the time of the
                                                                                                                                CZS request.

                                                                                                                                Note: If all zones in a zone set are not
                                                                                                                                created by the time a CMIT request is
McDATA-104      T         232                                                                                                   sent, the CMIT fails."                          A
                                6.4.9.4.20    Add Alias Members should include "Number       Add "Number of Alias Members" to
                                              of Alias Members" - see Remove Alias           the text and Table.                  Add "Number of Alias Members" field to
Brocade-066     T         239                 Member                                                                              command payload.                              A
                                6.5.1         We found a big hole with the Performance       Knock the scope of the
                                              Server. If the Performance Server is for the   Performance Server to the switch
                                              Fabric, there are no SW_ILSs for that          level. This will require significant Mike ODonnell will email Predrag Spasic
                                              communication. A switch could support          changes throughout the whole         about the deficiency and discuss
                                              some probes, but no architecture is defined    section.                             resolution (e.g., make it informative,
McDATA-106      T         249                 for inter-switch communications.                                                    remove it, etc.).                             O
                                Table 375     There are two 0102 code points.                Change GPMML to another              Change GPMML to 0103, and GPMM to
McDATA-107      T         250                                                                number.                              0104. Also, sort table by code.               A
                          251 Figure 15       The ULM drawing needs work. There should
                                              be numbers at the end of the aggregations
                                              to indicate how many of the objects many be                                       Change to: Left vertical arrow put "1" at
                                              contained within the pointed to object.                                           top, and "0..*" at botton. Right horizontal
IBM-236         T                                                                                                               arrow put "1" at left, and "0..*" at right.     A
                                Table 378     How can 03h be NOT SUPPORTED?                  Remove this code point.
                                                                                                                                No, this is a status, so "Not Supported" is
McDATA-108      T         254                                                                                                   a valid response from a probed device.          R
                          255 6.5.3.3         The statement << is implementation
                              Performance     dependent. >> should be << is vendor
                              Metrics         specific >>
IBM-240         T             Object                                                                                            See xxx.                                        A
                          259 6.5.5.1 Query   The statement << is implementation
                              - Get           dependent. >> should be << is vendor
                              Performance     specific >>
                              Server
                              Payload
                              Sizes
IBM-245         T             (GPMPS)                                                                                           See xxx.                                        A




                                                                                         Page 32 of 91
                                                                           FC-GS-4 Revision 7.6 Comments
                                                                                     09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                                Problem Description                         Suggested solution                           Response                        Status   Edit Status
             /Edito Page     figure locator
               rial
                        259 6.5.5.1 Query     The statement << is implementation
                            - Get             dependent. >> should be << is vendor
                            Performance       specific >>
                            Server
                            Payload
                            Sizes
IBM-246         T           (GPMPS)                                                                                               See xxx.                                           A
Andiamo-54      T       265 Note 52           Any reference to the work of the HBA-API      discuss                               Remove note. At paragraph above note,
                                              WG?                                                                                 change "The HBA Management
                                                                                                                                  Information defined by
                                                                                                                                  FDMI is based on information defined by
                                                                                                                                  the Fibre Channel HBA API
                                                                                                                                  specification." to "The HBA Management
                                                                                                                                  Information defined by
                                                                                                                                  FDMI is based on information defined by
                                                                                                                                  the HBA API specification (see FC-MI
                                                                                                                                  and FC-HBA)."                                      A
                             Figure 16        Figure 16: Why is it necessary to have        Fix, clarify, or remove figure.
                                              multiple HBA's per Node in the figure? Are    Would like to see a Note added
                                              there physical connections between HBA's      about the physical relationships of
                                              in the same Node or are they independent?     HBA's to assist in assessing FC-
                                              Is an HBA as shown in the diagram meant       SP authentication needs.
                                              to portray a physical card or that multiple
                                              HBA's are on a single physical card?                                                There are implementations in the field
                                                                                                                                  where multiple HBAs make up one node.
McDATA-115     T         266                                                                                                      So, this figure is correct.                        R
                         268 6.7.4.3.3.2      The statement << or Port must<CRLF>be
                             Registration     de-registered prior to a >> should be << or
                             Rules            Port shall<CRLF>de-registered prior to a >>
IBM-255        T                                                                                                                  As suggested.                                      A
                             6.7.4.3.3.2      Note a) doesn't explain how it is possible to Clarify that the Register HBA
                                              have a Registered Port list to check without command is an exception to rule
                                              it being registered. Suggested that an        a).                                   Add a note after a): "For initial
                                              exception to the Register HBA command be                                            registration of an HBA the registed port
McDATA-117     T         268                  made for this rule.                                                                 list is included in the reqistration request."     A
                         269 6.7.4.4.2.4      There is no reference to or definition of the
                             Model            << CIM model >> this needs to be fixed or                                           Change: "To allow complete
                                              << CIM model >> deleted.                                                            representation in the CIM model of a host
                                                                                                                                  bus adapter, the length of this attribute
                                                                                                                                  SHOULD NOT exceed 63 bytes." to
                                                                                                                                  "Some management applications limit
IBM-263        T                                                                                                                  this attribute to 63 bytes."                       A




                                                                                         Page 33 of 91
                                                                            FC-GS-4 Revision 7.6 Comments
                                                                                       09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                               Problem Description                          Suggested solution                         Response                    Status   Edit Status
             /Edito Page    figure locator
               rial
                        270 6.7.4.4.2.7      The statement << The
                            Node             registration<CRLF>of this attribute is
                            Symbolic         optional. >> should be deleted as everything
                            Name -           is the standard is optional unless otherwise
                            6.7.4.4.2.13     stated.
                            Maximum CT
IBM-264         T           Payload                                                                                              This is a clarifying statement.               R
                        270 6.7.4.4.2.8      There is no reference to or definition of the                                       Change: "To allow complete
                            Hardware         << CIM model >> this needs to be fixed or                                           representation in the CIM model of a
                            Version          << CIM model >> deleted.                                                            host bus adapter, the length of this
                                                                                                                                 attribute SHOULD NOT exceed 63
                                                                                                                                 bytes." to "Some management
                                                                                                                                 applications limit this attribute to 63
IBM-265        T                                                                                                                 bytes."                                       A
                         272 6.7.4.4.3.6     The statement << if and only if that FC_Port
                             Supported       is or may be configured to act as a                                                 Change entire clause to: The Supported
                             FC-4 Types      participant >> should be I believe << if it is                                      FC-4 Types attribute has a format
                                             possible for that FC_Port to be configured to                                       identical to that of a Name Server FC-4
                                             act as a participant >>.                                                            TYPEs object. An FC_Port shall register
                                                                                                                                 a Supported FC-4 Types value that
                                                                                                                                 indicates “support” for any FC-4 TYPE
                                                                                                                                 that it can be configured to support. The
                                                                                                                                 Supported FC-4 Types attribute is
                                                                                                                                 registered with the HBA Management
IBM-267        T                                                                                                                 Server as a Port attribute.                   A
                         272 6.7.4.4.3.7     The statement << if and only if that FC_Port                                        The Active FC-4 Types attribute is
                             Active FC-4     is or may be configured to act as a                                                 registered with the Name Server as a
                             Types           participant >> should be I believe << if it is                                      Name Server FC-4 TYPEs object and is
                                             possible for that FC_Port to be configured to                                       subject to all the description and
                                             act as a participant >>.                                                            constraints of that object. An FC_Port
                                                                                                                                 shall register a Name Server FC-4
                                                                                                                                 TYPEs value that indicates support for
                                                                                                                                 any FC-4 TYPE that the FC_Port is
IBM-269        T                                                                                                                 completely configured to support.             A
                               6.7.4.5.1     How is the Identification Port_Name               Needs clarification/explanation on
                                             selected?                                         architectural responsibility to    A proposal for better wording may be
McDATA-118     T         273                                                                   ensure interoperability.           accepted. Scott Kipp to investigate.         O




                                                                                             Page 34 of 91
                                                                             FC-GS-4 Revision 7.6 Comments
                                                                                       09/23/03 (03-083vA)


              Techn
               ical Physical Section/table/
 Company-#                                              Problem Description                           Suggested solution                               Response    Status   Edit Status
              /Edito Page    figure locator
                rial
                             6.7.4.4.3 Port Host Name omitted from Information                Add a new subsection as follows:
                             Attributes     returned by FDMI                                  6.7.4.4.3.12 Host Name - The
                                                                                              Host Name attribute contains a 1
                                                                                              to 255 byte Printable ASCII String
                                                                                              that describes the name of the
                                                                                              host associated with the port.
                                                                                              Should there be several such
                                                                                              names which reference the same
                                                                                              host, this attribute MAY be a
                                                                                              comma-separated list of as many
                                                                                              such names as fit in 255 bytes.
                                                                                              Should the software that registers
                                                                                              Nx_Port attributes be unable to
                                                                                              determine any such Host Name, it
                                                                                              shall not register this attribute. The
                                                                                              Host Name attribute is registered
                                                                                              with the HBA Management Server
                                                                                              as a Port attribute. The registration
                                                                                              of this attribute is optional.

VERITAS-002     T         273                                                                                                     As suggested                       A
                                6.7.4.5.6 Port Host Name omitted from Information             Add an additional row to the table
                                Attributes     returned by FDMI                               containing the following
                                Table 411                                                     information - Type (hex) 0006,
                                                                                              Description - Host Name, Length 1-
                                                                                              256 bytes, Type - ASCII, Required -
VERITAS-001     T         277                                                                 No                                  As suggested.                      A
                                Subclause       Subclause 6.7.4.3.3.2 list item b requires a  Add a row to table 412: column 1
                                6.7.4.6 table   reason explanation code for rejecting an      is "24"; column 2 is "Port Already
                                412             attempt to register a port that is already    Registered"
                                                registered. There is no such reason code
Emulex-008      T         278                   explanation in the table.                                                              As suggested.                 A
                                Table 412       The following reason code explanations are Add them.
                                                missing:

                                                HBA Not Registered,
                                                Port Already Registered

                                                These would be appropriate for the
                                                commands DHBA (when an HBA is not
                                                registred) and RPRT (when the port is
QLogic-L03      T         278                   already registered) among others.                                                      As suggested.                 A
                          288 7.2.2.1           The abbreviation << TS >> is not defined.
IBM-279         T             Overview          This needs to be fixed.                                                                Change TS to Time Server.     A




                                                                                            Page 35 of 91
                                                                            FC-GS-4 Revision 7.6 Comments
                                                                                       09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                              Problem Description                            Suggested solution                             Response                     Status   Edit Status
             /Edito Page    figure locator
               rial
QLogic-028      T       288 7.2            The Time Server does not seem to be full            To possible actions:
                                           implemented. Many of the TSAP fields are            a) Remove the NTP based Time
                                           not used (see other comments), and these            Server from GS-4 and bring a
                                           fields would be required for a full NTP             complete defintion into a future GS
                                           implementation, also there is no method             and SW standards.
                                           within FC-SW-3 for doing distributed Time           b) Make the GS-4 implementation
                                           Service in an interoperable fashion within a        a real NTP implementation, and
                                           multi-vendor fabric.                                specify the distributed Time Server
                                                                                               within SW-3.
                                              We have gotten in trouble in the past when
                                              including incomplete implementations
                                              (remember FSPF backbone?), and should                                                   First part of comment withdrawn. The
                                              not do so here.                                                                         switch to switch functions will be defined
                                                                                                                                      in FC-SP.                                     W
QLogic-029     T         291 7.2.5.3          What does TSAP mean?                             Provide a definition for this          TSAP stands for "Time Service Access
                                                                                               ackronym.                              Protocol". Add to Ackronyms section.           A
QLogic-030     T         291 7.2.5.3, Table   There is no definition for the Message           Provide a definition for this field.
                             441              Digest field.                                                                           See QLogic-030.                                A
QLogic-032     T         291 7.2.5.3,         Why are we forcing "unspecified". A Time         Allow values other than 00, or set     Add a definition of the allowed Stratum
                             Stratum          Server may acutally be based on one of the       the field to "Reserved" if it's not    values from the NTP RFC including 00
                                              two primary/secodary references.                 used.                                  for "unspecified".                             A
QLogic-033     T         291 7.2.5.3, Poll    Why is this here if it's not used?               Set to "Reserved".
                                                                                                                                      Change: "This field is not used and is set
                                                                                                                                      to 00h for both the TSAP Request and
                                                                                                                                      Response blocks." to "This field shall be
                                                                                                                                      set to 00h for a TSAP Request."                A
QLogic-034     T         291 7.2.5.3,         Why are we fixing a particular percision? It     Allow different precisions here,       Change: "The value of this field in the
                             Precision        seems as though this is dictating                with a definiton of what the           Response Block is set to FAh to indicate
                                              implementation details.                          required minimum precision is.         a
                                                                                                                                      precision of 16 ms." to "A value in a
                                                                                                                                      TSAP Response indicates the precision
                                                                                                                                      in millisconds".                               A
QLogic-035     T         291 7.2.5.3, Root Why is this here if it's not used?                  Set to "Reserved".                     Delete last sentence: The value of this
                             Delay                                                                                                    field in the TSAP Request
                                                                                                                                      and Response blocks is set to
                                                                                                                                      00000000h."                                    A
QLogic-036     T         291 7.2.5.3, Root Why is this here if it's not used?                  Set to "Reserved".                     Change: "This value is set to
                             Dispersion                                                                                               hex‟00000000‟ in the TSAP Request and
                                                                                                                                      Response
                                                                                                                                      blocks." to "This value is set to
                                                                                                                                      00000000h in the TSAP Request."                A




                                                                                             Page 36 of 91
                                                                            FC-GS-4 Revision 7.6 Comments
                                                                                         09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                                 Problem Description                        Suggested solution                            Response                     Status   Edit Status
             /Edito Page     figure locator
               rial
QLogic-037      T       291 7.2.5.3,        Why set this to zero? It seems as though          Either allow values other than        Change: "This value is set to
                            Reference       this is valid information.                        zero, or change to a 'Reserved'       hex‟00000000‟ in the TSAP Request and
                            Identifier                                                        field.                                Response blocks." to "This value is set to
                                                                                                                                    00000000h in the TSAP Request. For a
                                                                                                                                    TSAP Response, this field may contain a
                                                                                                                                    value identifing the source clock (see
                                                                                                                                    RFC 1305)."                                    A
QLogic-038     T         291 7.2.5.3,        Why is this here if it's not used?               Set to "Reserved".                    Change: "The timestamp shall be set to
                             Reference                                                                                              all zeros in the TSAP Request
                             Timestamp                                                                                              and Response block." to "The timestamp
                                                                                                                                    shall be set to all zeros in the TSAP
                                                                                                                                    Request."                                      A
QLogic-039     T         291 7.2.5.3,      What is this? It's not listed in the table.        Is this maybe the Message Digest
                             Authenticator                                                    listed in the table? If so, make the
                                                                                              names consistent.                    See QLogic-040.                                 A
QLogic-040     T         291 7.2.5.3,      Why is this here if it's not used?                 Set to "Reserved".
                             Authenticator                                                                                         As suggested. This overides QLogic-
                                                                                                                                   030.                                            A
                         292 7.2.5.3 TSAP    The term << Message Authentication Code
                             Unicast         (MAC) >> is not defined nor is there a
                             Request/Res     reference to where it is defined. This needs
                             ponse Block     to be fixed.
IBM-286        T                                                                                                                    See QLogic-040.                                A
                         293 7.2.5.4.1   NOTE 58 contains a shall. the shall has to
                             Timestamp   be removed or the note made normative.
IBM-289        T             Format                                                                                                 Make normative as suggested.                   A
QLogic-041     T         294           8 An interoperable method of providing Alias           So, either:
                                         Serivce is not provide for mutli-vendor              1) Remove the Alias service from
                                         Fabrics.                                             GS-4 if this service is not deemed
                                                                                              important enough to specify an
                                                                                              interoperable solution, or
                                                                                              2) Request that FC-SW-3 provide
                                                                                              the distributed interoperable Alias
                                                                                              Server definition.
                                                                                                                                    Entertained in SW-4.                           R
                         297 8.2.2.3.2 Join NOTE 60 contains a shall and therefore
                             alias group    needs to be made normative.
IBM-298        T                                                                                                                    As suggested.                                  A
                         301 8.2.2.5.1       The statement << which cannot be spread
                             Hunt groups     across images. >> should be << which is not
IBM-312        T                             spread across images >>.                                                               Change to "that is not"                        A




                                                                                            Page 37 of 91
                                                                              FC-GS-4 Revision 7.6 Comments
                                                                                         09/23/03 (03-083vA)


              Techn
               ical Physical Section/table/
 Company-#                                                Problem Description                             Suggested solution                    Response                   Status   Edit Status
              /Edito Page     figure locator
                rial
                         316 Annex A:        There are shalls in this informative annex
                             Service         that need to be removed.
                             Interface
                             Provided by
                             FC-CT
IBM-338          T           (Informative)                                                                                      Editor to go through and fix.                A
Andiamo-59       T       324 Annex C         This clause may require updates: new                update
                                             platform properties, new Name Server                                               Remove RTIN from clause C.6.4.3. For
                                             attributes, RTIN obsoleted                                                         new propoerties and name server
                                                                                                                                attributes, the GS-4 WG will accept a
                                                                                                                                proposal by the commentor to add these,
                                                                                                                                otherwise no change to be made.              A
                          324 Annex C:      This annex contains several << can >> and
                              Discovery     << must >> words that have to be removed.
                              (Informative) Note the << must >> cannot be replaced
                                            with << shall >> because this is a
IBM-339         T                           informative annex.                                                                  Editor to go through and fix.                A
                          335 C.6.2.2.3     The reference << (see Unzoned Name                                                  Change: "Therefore a mechanism
                              Name Server Server Access Point) >> is not valid. If                                              (see Unzoned Name Server Access
                              and Zones     needs to be fixed.                                                                  Point) must be provided to allow a
                                                                                                                                management application to
                                                                                                                                obtain complete information from the
                                                                                                                                Name Server." to "Therefore a
                                                                                                                                mechanism must be provided to allow a
                                                                                                                                management application to
                                                                                                                                obtain complete information from the
IBM-341         T                                                                                                               Name Server (see 6.3).                       A
Brocade-025     T         337 C.6.4.3      RTIN are removed from FC-FS                Remove references to RTIN                 See Andiamo-59.                              A
                          337 C.6.4.3 RTIN As a result of RTIN being removed from FC-
                              and RNID     FS this section needs to be rewritten to
IBM-342         T                          remove any reference to RTIN.                                                        See Andiamo-59.                              A
                              C.8.3        This cluase metions the term URL. We may
                                           have to change this depending on the
Editor-004      T         339              outcome of Editor-003.                                                               See Editor-003.                              O
Andiamo-60      T         340 Annex D      This clause may require updates for        update                                    Will only be updated with a detailed
                                           enhanced zoning.                                                                     proposal to this effect. Change title to
                                                                                                                                "Examples of Basic Zone Service".            R
QLogic-042      T         344 Annex E         This list of future work items is out-of-date.     Either update it or remove the
                                                                                                 annex.                           Remove annex E.                            A
QLogic-043      T         345 Index           Out-of-date.                                       I would recommend that the index
                                                                                                 be removed since it serves no
                                                                                                 useful purpose in the world of
                                                                                                 electronic documents.            Remove index.                              A




                                                                                               Page 38 of 91
                                                                             FC-GS-4 Revision 7.6 Comments
                                                                                        09/23/03 (03-083vA)


              Techn
               ical Physical Section/table/
 Company-#                                                  Problem Description                          Suggested solution                            Response              Status   Edit Status
              /Edito Page    figure locator
                rial
Inrange-008      T   104/81  5.2.5.30       GID_FPN gets a list of Port Ids for a given          Remove the following sentence:
                                            Fabric Port Name. The description of the             “A single entry with a null Port
                                            response says that, when no ID is found, a           Identifier with Control Bit 7 set to
                                            null list is returned (and it describes the          one indicates that there are no
                                            format). However, Table 28 lists a reason            matching entries”.This lets the
                                            code explanation of “Fabric Port Name not            default processing described
                                            registered”, which would be the more                 earlier return the defined “not
                                            appropriate response. This allows a reject           registered” response.
                                            when the entry is not found, rather than
                                            making a special case of evaluating the data
                                            to discover it. This is the ONLY Name
                                            Server query that does this (and was also a
                                            late addition).
                                            Note that the text following Table 28 says
                                            that when the object was not found in the
                                            Name Server data base, it should report that
                                            the specified object is not registered. This is
                                            the preferred implementation.                                                               Keep as is.                            R
Inrange-009      T   121/98  5.3.4          Same as Inrange 003 (IP Address Server).             Same as Inrange 003.                   IP Address server being obsoleted.     R
Inrange-010      T   122/99  Table 123      Same as Inrange 004.                                 Same as Inrange 004.                   IP Address server being obsoleted.     R
Inrange-011      T   153/130 6.2.4          Same as Inrange 003 (Fabric Configuration            Same as Inrange 003.
                                            Server).
Inrange-012      T   174/151 6.2.5.24       What is the proper response to the Get               Should the device respond by:
                                            Platform Name List (GPNL) Request CT_IU                         2) Transmitting a Reject
                                            when there are no registered Platform Name           CT_IU with a Reason code
                                            Attributes?                                          explanation = Platform Name does
                                                                                                 not exist (60h). Or
                                                                                                            2) Transmitting an
                                                                                                 Accept CT_IU with the Number of
                                                                                                 Platform Name entries (n) = 0 and
                                                                                                 no Platform Name entries.
                               Table 245      In RMZ, ther should be "Number of Zone             Add "Number of Zone Members"
                               and            Members"                                           to this command.
Brocade-041     T     175, 222 6.4.9.3.14                                                                                               Withdrawn by commentor                W
Inrange-013     T    220/197 6.4.8            Same as Inrange 003 (Fabric Zone Server). Same as Inrange 003.

Inrange-014     T    230/207   6.4.9.3.3      Query – Get Zone Set List (GZSN) states:           The last part of the sentence
                                              The Fabric Zone Server shall, when it              should state..return the Zone Set
                                              receives a GZSN request, return the Zone           attributes of all Zone Sets in the
                                              Set attributes of all Zone Sets in the Fabric.     Zone Set Database.




                                                                                               Page 39 of 91
                                                                           FC-GS-4 Revision 7.6 Comments
                                                                                      09/23/03 (03-083vA)


               Techn
                ical Physical Section/table/
 Company-#                                                Problem Description                         Suggested solution                           Response                 Status   Edit Status
               /Edito Page    figure locator
                 rial
Inrange-015       T   240/217 6.4.9.3.10     Failure action not defined for Activate Zone     Add text: An AZSD command with
                                             Set Direct (AZSD) when Zone Set name is          a Zone Set Name registered in the
                                             contained in the Zone set Database.              Zone Set Database will be
                                                                                              rejected with a reason code
                                                                                              Unable to Perform Command
                                                                                              Request (09h) with reason code
                                                                                              explanation Invalid Zone Set
                                                                                              Definition (1Ah)
Inrange-016      T    240/217   6.4.9.3.10    Note b of table 245 states:”The Zone Set        Add to 6.4.9.3.10:”The Zone Set
                                              defined in the Request CT_IU is not added       defined in the Request CT_IU
                                              to the Zone Set Database.”                      shall not be added to the Zone Set
                                                                                              Database,” and remove the note
                                                                                              from table 245
Andiamo-52       T     244-247 Tables 368     The sizes are expressed with letters, not       update
                               and 369        references.                                                                           Editor to add references.                 A
Inrange-017      T    280/257 6.5.4           Same as Inrange 003 (Performance Server). Same as Inrange 003.

Inrange-018      T    300/277   6.7.4.6       Same as Inrange 003 (HBA Management             Same as Inrange 003.
                                              Server).
Inrange-019      T    329/306   8.2.4         Same as Inrange 003 (Alias Server).             Same as Inrange 003.
                                C.6.4.3       Reference to RTIN.This whole section            Delete paragraph C.6.4.3 entirely
                                              (about ½ a page), is referring to two new
                                              ELS functions– RNID and RTIN. The part
                                              on RTIN compares the ELS to the
                                              management function. I believe that the
                                              RTIN ELS was dropped in favor of the                                                  I believe this was closed by Andiamo-
Inrange-002a     T     360/337                management function (presumably GTIN).                                                059.
Inrange-024      T    360/337 C.6.4.3         Reference to RTIN.                              I‟m not sure if you should refer to
                                              This whole section (about ½ a page), is         the GTIN or rethink this section.
                                              referring to two new ELS functions – RNID       Obviously the part comparing the
                                              and RTIN. The part on RTIN compares the         ELS to the management function
                                              ELS to the management function. I believe       is not valid – does it make sense
                                              that the RTIN ELS was dropped in favor of       to keep the section and discuss
                                              the management function (presumably             the discovery with the
                                              GTIN).                                          management function alone?




                                                                                            Page 40 of 91
                                                                         FC-GS-4 Revision 7.6 Comments
                                                                                    09/23/03 (03-083vA)


              Techn
               ical Physical Section/table/
 Company-#                                               Problem Description                       Suggested solution                         Response   Status   Edit Status
              /Edito Page    figure locator
                rial
Inrange-003      T   74/51   5.2.4          Last paragraph says “A valid Name Server        Remove the statement. That
                                            request shall not be rejected with a Reason     Reason Code is the clearest way
                                            Code of „Command not supported‟                 to indicate why the command is
                                            Not all Name Server commands are                not being executed.
                                            required to be supported – several in fact
                                            are prohibited by FC-MI and FC-MI-2. For
                                            instance, GID_A and all the IP related
                                            commands are prohibited. If these, or any
                                            others, are not implemented, how are they
                                            to be rejected?
                                                                                                                              As suggested.                A
Inrange-004     T   75/52      Table 28      Code 12 – “Data base empty” is redundant, Footnote the entry as obsolete but
                                             since the same reason code explanation is may be used in legacy
                                             defined in Table 11 as valid for all servers. implementations.
                                             Since I suspect that the global definitions
                                             came later, I suspect that this specific Name
                                             Server variant is needed for legacy
                                             implementations, but it is inconsistent.

Inrange-005     T   76/53      5.2.4         Item c) removes from general “not              Remove item d, and remove the
                                             registered” processing two FC-4 Type           special case for GID_FT and
                                             queries, leaving them to have specific         GNN_FT in item c.
                                             handling in item d).
                                             Item d) lists the two specific FC-4 Type
                                             queries, and defines handling for when “no
                                             FC-4 TYPEs object is found in the Name
                                             Server data base within the specified
                                             scope”.
                                             I see no reason that the processing should
                                             not be done for when “the requested FC-4
                                             TYPEs object is not found…” As written, the
                                             document specifies what to do if NO FC-4
                                             TYPEs are registered in the specified scope,
                                             but not what to do if there are registered
                                             types, just not the one being queried. I think
                                             that the processing should only care if the
                                             requested type is not found. Furthermore, if
                                             the entire item is deleted, and the special
                                             case in the previous item is removed, then
                                             the default handling would have had the
                                             same effect.




                                                                                          Page 41 of 91
                                                                             FC-GS-4 Revision 7.6 Comments
                                                                                        09/23/03 (03-083vA)


              Techn
               ical Physical Section/table/
 Company-#                                               Problem Description                           Suggested solution                            Response   Status     Edit Status
              /Edito Page    figure locator
                rial
Inrange-006      T   76/53   5.2.4          Related to the previous item, if there was a        Hopefully nothing, if the comment
                                            reason to make a special case for FC-4              Inrange 005 is accepted.
                                            TYPE, then why was GPN_FT not                       Otherwise, add GPN_FT to the list
                                            mentioned in items c and d?                         (if there is a good reason for the
                                                                                                special treatment).

Inrange-007     T    76/53        5.2.4         Related to the previous two items, again if     Hopefully nothing, if the comment
                                                there is a reason for the special case, then    Inrange 005 is accepted.
                                                is there a reason to exclude GID_FF, which      Otherwise, add GID_FF to the list,
                                                does the same thing but also further            and also specify what to do if the
                                                qualifies the query (scope, FC-4 TYPE and       FC-4 Features is not found.
                                                FC-4 Features).Again, if item d is removed,
                                                then the default processing would leave “FC-
                                                4 TYPE not registered” or “FC-4 Features
                                                not registered”, depending on which was not
                                                found.
QLogic-045      T            ix   Introduction, FC-PH references should be replaced with
                                  1st paragrah FC-FS.                                                                                As suggested.                A      Done.
QLogic-046      T            ix   Introduction, FCP should be replaced with FCP-2
                                  2nd paragrah                                                                                       As suggested.                A
QLogic-047      T            ix   Introduction, FC-SB-2 should be replaced with FC-SB-3.
                                  2nd paragrah                                                                                       As suggested.                A
QLogic-048      T            ix   Introduction, "Server Clusters"? Which standard is this?      Remove this.
                                  2nd paragrah                                                                                       Remove last sentence.        A
QLogic-049      T            ix   Introduction, There are no new audio visual Standards         Remove this. Or, alternatively,
                                  2nd paragrah under development.                               remove the whole last sentence.      See QLogic-048.              A
Andiamo-48      T      several    6.4.9.3       In the section of Basic zoning commands,        update consistently
                                                the Zone Name lengths are expressed as "8
                                                to 68" instead than with a reference to
                                                clause 6.4.7.1, as in the enhanced zoning
                                                section                                                                              Editor to update.            A
                                  Table 11      The are no reason code explanations in          The following two
                                                table 11 - Reject CT_IU Reason Code             Reason Code explanations should
                                                explanations for all Servers that can be used   be added to table 11:
                                                to indicate the failure of a
                                                CT command to lock or unlock the fabric         Database Update Failed; and
                                                (e.g., SSB, SSE).                                  Lock Attempt Failed
IBM-L02         T
                               Section 1, 1st Reference to FC-PH should be changed to Change FC-PH references to FC-
Brocade-001     E            1 sentence       FC-FS                                          FS                                      As suggested.                A      Done.
                             1                Is it possible to describe the scope of FC-GS-
                                              4 in terms that do not reference FC-PH?
ENDL-006        E                1 (Scope)                                                                                           As suggested.                A      Done.




                                                                                           Page 42 of 91
                                                                              FC-GS-4 Revision 7.6 Comments
                                                                                         09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                              Problem Description                              Suggested solution                             Response             Status     Edit Status
             /Edito Page    figure locator
               rial
                          1                Either 'Services' ala 'Directory Services' or         The issue behind the comment is
                                           'Service' ala 'Alias Service', but not both.          that all the entries in the
                                                                                                 cited list should be either singular
                                                                                                 (i.e., 'Service') or
                                                                                                 plural (i.e., 'Services'). Currently
                                                                                                 there is a mix of
                                  1 (Scope),                                                     'Service' and 'Services'.
ENDL-007       E                   a,b,c list                                                                                           Should be singular in all cases.       A      Done.
                                O'Donnell -     New Address                                      Change to :
                                incorrect                                                        4 McDATA Parkway
                                address                                                          Broomfield, CO 80021
                                                                                                 (720) 558-4142
McDATA-1       E            1                                                                    (720) 558-8999                         As suggested                           A      Done.
                            2       2.3         FC-VI has been published as ANSI
                               (References      INCITS.357:2002.
                                   under
ENDL-008       E              development)                                                                                              As suggested.                          A      Done.
                            2 2 Normative      When possible the reference should be
IBM-004        E              References       made to the ISO version of a standard.                                                   Is this an ISO requirement?            R
                              third            The reference to FG, SILS and SHA-1 can Update references.
                              sentence         be removed. Update reference to SW-3 and
                                               FS. Move VI into approved references                                                     All as suggested except FC-FG. See
McDATA-6       E            2                  section.                                                                                 Cisco-002.                             A      Done.
Andiamo-03     E            3              2.4 References to MIBs need to be updated to Update references.
                                               the new FC MIB. Having removed the Key
                                               server clause, check the references related
                                               to security (MD-5, SHA-1, DES), etc.
                                                                                                                                        See ENDL-009                           A
                            3 2.4 Other         The statement << http://www.isi.edu/. >>
                              references        and << http://www.ietf.org/html.charters/ipfc-
                                                charter.html. >> are a weird font. They
                                                should be changed to match the reset of the
                                                document.
IBM-005        E                                                                                                                        As suggested                           A      Done.




                                                                                            Page 43 of 91
                                                                          FC-GS-4 Revision 7.6 Comments
                                                                                    09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                            Problem Description                          Suggested solution                         Response                     Status     Edit Status
             /Edito Page    figure locator
               rial
Andiamo-04      E         4            2.4 Reference to Open group incomplete               Add a pointer to
                                                                                            www.opengroup.org. Better
                                                                                            reference: "Open Group Technical
                                                                                            Standard C706, DCE 1.1: Remote
                                                                                            Procedure Call, August 1997,
                                                                                            http://www.opengroup.org/product
                                                                                            s/publications/catalog/c706.htm".
                                                                                            The Open Group, 44 Montgomery
                                                                                            Street, Suite 960, San Francisco,
                                                                                            CA 94104-4704 USA.                This doesn't seem to be in the correct
                                                                                                                              format for the referecnes section. Need
                                                                                                                              a format like the others.                      O
QLogic-001     E           4 2.4, first      Why is this on a new page?                     Fix it.
                             paragraph on
                             page                                                                                             Page break removed.                            A      Done.
                           5 3.2.7           The term << 'CT' >> should not be in quotes.
                             Common
IBM-006        E             Transport                                                                                        Remove quotes.                                 A      Done.
                           5 3.2.17 Link     The term << 'Fabric F_Port' >> should not
                             Service         be in quotes.
IBM-007        E             Facilitator:                                                                                     Remove quotes.                                 A      Done.
                             Copyright       Change 200x to 2003
McDATA-2       E           5 date                                                                                             Date will be changed prior to publication.     R
                           6 3.2.25          The following statement << defined in FC-
                             Network_Add     FS to indicate a Network_Address_Authority
                             ress_Authorit   (NAA). >> should be changed to <<
                             y Identifier:   indicates the Network_Address_Authority
                                             (NAA ). >> should be changed to <<
                                             indicates the Network_Address_Authority
                                             (NAA) (see FC-FS). >>
IBM-008        E                                                                                                              As suggested.                                  A      Done.
                           6 3.2.30          The statement << Service. For example, the
                             Server:         Name Server is<CRLF>accessed using the
                                             Directory Service. >> should be << Service
                                             (e.g., the Name Server is accessed using
IBM-010        E                             the Directory Service).                                                          As suggested.                                  A      Done.
                           6 3.2.31          The statement << Identifier. Examples of a
                             Service:        Service include the Directory Service
                                             and<CRLF>the Alias Service. >> should be
                                             << Identifier (e.g., Directory Service
IBM-011        E                             and<CRLF>Alias Service). >>                                                      As suggested.                                  A      Done.
                           7 3.2.43 Well-    Global<CRLF>All references to << FC-PH
                             known           >> should be changed to << FC-FS >>.
IBM-013        E             address:                                                                                         As suggested.                                  A      Done.




                                                                                         Page 44 of 91
                                                                          FC-GS-4 Revision 7.6 Comments
                                                                                    09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                                Problem Description                   Suggested solution                    Response                     Status     Edit Status
             /Edito Page     figure locator
               rial
                          7 3.2.43 Well- The statement << restrictions; i.e., a well-
                            known           known address is always<CRLF>accessible,
                            address:        irrespective of the current Active Zone Set.
                                            >> should be restrictions (i.e., a well-known
                                            address is always<CRLF>accessible,
                                            irrespective of the current Active Zone Set).
IBM-014         E                           >>                                                                       As suggested.                                   A      Done.
                          7 3.2.45 Zone The statement << Zone: the Zone Name,
                            Definition:     number of Zone<CRLF>Members, and Zone
                                            Member definition. >> should be << Zone
                                            (i.e.,: the Zone Name, number of
                                            Zone<CRLF>Members, and Zone Member
IBM-015         E                           definition\                                                              As suggested.                                   A      Done.
                          7 3.2.46 Zone The statement << N_Port (or NL_Port) >>
IBM-016         E           Member:         should be << N_Port or NL_Port >>.                                       Nx_Port is more appropiate here.                A      Done.
                          7 3.2.49 Zone The << which >> should be a << that >>.
IBM-018         E           Set:                                                                                     As suggested.                                   A      Done.
                          7 3.2.51 Zone The << which >> should be a << that >>.
IBM-019         E           Set State:                                                                               As suggested.                                   A      Done.
                          7 Global          The margins on left pages is set differently
                                            than on right pages. Although this was
                                            standard practice when printing was the
                                            norm now that electronic is the norm it is
                                            more of a distraction than a help. The
                                            margins on all pages should be set to the
                                            same. The left and right margins on all                                  People still print these things (believe it
IBM-020         E                           pages should be set to one inch.                                         or not). So, this should no change.             R
McDATA-7        E         7 3.2.52          Change activated to active in two places.                                As suggested.                                   A      Done.
                          9 3.4             As a result of RTIN being removed from FC-
                            Abbreviations FS the << RTIN Request Topology
                            , acronyms      Information Extended Link Service >>
IBM-021         E           and symbols should be deleted.                                                           Remove.                                         A      Done.
                         11        4.1      Would it be possible to reference figure 1 to
                              (Overview), FC-PI and FC-FS instead of FC-PH?                                          Changed to reference FC-FS. FC-PI is
ENDL-010        E               figure 1                                                                             not appropiate in this figure.                  A      Done.




                                                                                       Page 45 of 91
                                                                         FC-GS-4 Revision 7.6 Comments
                                                                                    09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                               Problem Description                      Suggested solution                   Response               Status     Edit Status
             /Edito Page    figure locator
               rial
                         11 4.1 Overview The statement << It is important to note that
                                            Fibre Channel Generic<CRLF>Services do
                                            not require a high performance
                                            communication channel as do high
                                            performance I/O<CRLF>protocols such as
                                            SCSI, IP, VI, etc. >> should be << Fibre
                                            Channel Generic<CRLF>Services do not
                                            require a high performance communication
                                            channel as do high performance
                                            I/O<CRLF>protocols (e.g., SCSI, IP, and
                                            VI). >>
IBM-022         E                                                                                                      As suggested.                            A      Done.
Andiamo-05      E        12             4.2 "Name Service" should be "Directory            Update accordingly.
                                            Service". Also, Key service has been
                                            obsoleted.                                                                 As suggested.                            A      Done.
                         12 4.2 (General As I understand it, the Service is the
                              concepts), Directory Service (not the Name Service).
                            2nd a,b,c list, There is a Name Server but not a Name
ENDL-011        E              entry a)     Service.                                                                   See Andiamo-05.                          A      Done.
                         12 4.2 (General If the table of contents and clause 1 are to
                              concepts), be believed, Key Service s/b Key
                            2nd a,b,c list, Distribution Service.
ENDL-012        E              entry e)                                                                                See Andiamo-05.                          A      Done.
                         12 many            Global<CRLF>There should be no line
                                            spacing between items in an a,b,c list or a
IBM-023         E                           1,2,3 list.                                                                Is this an ISO requirement?              R
                         13                 Regarding 'The following three Classes of
                                            service may be used to request a Service:
                                            ...' What classes of service are allowed for
                                            Unsolicited transactions? The list covers
                                            Request transactions (and by implication
                                            Responses), but Unsolicited transactions are
                             4.2 (General not covered. The sentence needs to be
                              concepts), reworded to avoid the words Request,                                          Re-written how? Without a suggestion
                              1st p after Response, and Unsolicited so that it can be                                  the editor does not know what the
ENDL-013        E               note 1      read as a general statement.                                               commentor has in mind.                   R
                         13 4.2 General << It is used to express the desire of the
                            concepts        Client in the order of availability. >> should
                                            be <<It is used by the Client to indicate a
                                            preference in the order of availability. >>
IBM-025         E                                                                                                      As suggested.                            A      Done.




                                                                                       Page 46 of 91
                                                                              FC-GS-4 Revision 7.6 Comments
                                                                                         09/23/03 (03-083vA)


              Techn
               ical Physical Section/table/
 Company-#                                                Problem Description                      Suggested solution                                     Response                    Status     Edit Status
              /Edito Page    figure locator
                rial
                          13 4.2 General The statement << A Client may wish to
                             concepts       restrict the size of IUs that it wants to
                                            receive from a Server... should be <<A
                                            Client may restrict the size of IUs it receives
IBM-027          E                          from a Server. >>                                                                             As suggested.                                 A      Done.
Andiamo-07       E        14 Table 2        CT_IU preamble word badly formatted             Update.                                       This needs to be fixed in a way that the
                                                                                                                                          "CT_IU Preamble" on the right is tied to
                                                                                                                                          the table, so that when the table moves,
                                                                                                                                          it is positioned correctly.                   A      Done.
Cisco-006       E           14 4.3.1            table 2                                          fix dangling CT_IU preamble              See Andiamo-07.                               A      Done
                            14 table 2          I have no clue with the <<
                                                CT_IU<CRLF>preamble >> on the right side
                                                of the table is supposed to represent. This
IBM-029         E                               needs to be fixed.                                                                        See Andiamo-07.                               A      Done.
                            14 table 2 -3 and   The heading and the first column should be
                               others like it   changed the format used in FC-FS for this
IBM-030         E                               kind of table.                                                                            Is this an ISO requirement?                   R
                               Table 2          The format of the table is wrong. Is the         Fix the table so that the text fits in
McDATA-8        E           14                  CT_IU Preamble in the right place.               the windows.                             See Andiamo-07.                               A      Done.
QLogic-007      E           14 Table 2          The right hand label "CT_IU preamble" is         Fix it.
                                                messed up.                                                                                See Andiamo-07.                               A      Done.
Andiamo-09      E           15 Table 4          Reserved for Key Distribution Service or         Update.                                  This has been updated. It is reserved for
                                                simply reserved?                                                                          the Key Disrtribution service.                R
                               4.3.2.4, Table   Encoded value x'20' should reference "FC-        Change reference to "FC-SW-
                               4                SW-family of standards" instead of FC-SW-        family of standards"                     Standards don't have families… See
Brocade-002     E           15                  2                                                                                         QLogic-008.                                   R
                            15 4.3.2.5          The statement in note 6 << N_ Port. For
                               GS_Subtype       example, if<CRLF>more than one Server is
                               Field            provided by the Directory Service at the well-
                                                known address FFFFFCh, then
                                                the<CRLF>GS_Subtype field is used to
                                                distinguish these different Servers. >>
                                                should be << N_ Port (e.g.,, if<CRLF>more
                                                than one Server is provided by the Directory
                                                Service at the well-known address
                                                FFFFFCh, then the<CRLF>GS_Subtype
                                                field is used to distinguish these different
IBM-032         E                               Servers). >>                                                                              As suggested.                                 A      Done.
                            18 4.3.2.8          The number << 65534 >> is not in ISO
                               Maximum/Re       format. It should be << 65 534>>.
                               sidual Size
IBM-034         E              field                                                                                                      As suggested.                                 A      Done.
                            18 4.3.2.9     The << which >> should be a << that >>.
                               Fragment ID
IBM-035         E              field                                                                                                      As suggested.                                 A      Done.



                                                                                            Page 47 of 91
                                                                            FC-GS-4 Revision 7.6 Comments
                                                                                         09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                                Problem Description                          Suggested solution                              Response                    Status     Edit Status
             /Edito Page     figure locator
               rial
                         19 4.3.3.1           The statement << Note that >> should be
IBM-036         E           Overview          deleted.                                                                                As suggested.                                  A      Done.
                         19 4.3.3.3           The << which >> should be a << that >>.
                            transaction_i
IBM-037         E           d                                                                                                         As suggested.                                  A      Done.
                         19 4.3.3.5 Time      The statement << increasing; i.e., the ...>>
                            Stamp             should be << increasing (i.e., the ...). >>
IBM-038         E                                                                                                                     As suggested.                                  A      Done.
                            4.3.3.5           reference is to table 7.2.5.4 instead of         Remove "table".
McDATA-9        E        19                   clause 7.2.5.4                                                                          As suggested.                                  A      Done.
                         20 4.3.3.6           The term << 'hash' >> should not have
                            Authenticatio     quotes.
                            n Hash Block
IBM-039         E                                                                                                                     Remove quotes.                                 A      Done.
                         20 4.3.4.2           The statement << NOTE 8 - Unique Vendor
                            Vendor            ID Strings are maintained by ANSI T10. A
                            Identifier        list of current Vendor ID Strings and
                                              instructions<CRLF>for requesting a new
                                              Vendor ID String can be found on the T10
                                              web site at \217www.t10.org\220. >> needs
                                              to change to << The vendor identification
                                              shall be one assigned by INCITS. A list of
                                              assigned vendor identifications is on the
                                              T10 web site (www.T10.org). >>
IBM-040        E                                                                                                                      As suggested.                                  A      Done.
Cisco-007      E          21 4.3.4.5          "the standard"                                   which standard is this referring to?
                                                                                                                                      THIS standard.                                 A      Done.
                          21 4.3.4.5       The statement << response (Accept or
                             Processing of Reject); >> should be << response (i.e.,
                             the Vendor    Accept or Reject);
                             Specified
                             Preamble
IBM-041        E                                                                                                                      As suggested.                                  A      Done.
                          21 4.3.4.5       The statement << in the<CRLF>standard.
                             Processing of >> should be << in this standard >> in two
                             the Vendor    places.
                             Specified
                             Preamble
IBM-042        E                                                                                                                      As suggested.                                  A      Done.
                          22 table 10         There is no notation on the encoded values.                                             Converted to hex. Added "(hex)" to
                                              There should be a << b >> at the end of                                                 column header to be consistent with
                                              each value or preferably change then to hex                                             other tables. Also, fixed other formatting
IBM-043        E                              value with the xxh notation.                                                            issues.                                        A      Done.




                                                                                             Page 48 of 91
                                                                         FC-GS-4 Revision 7.6 Comments
                                                                                    09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                                Problem Description                     Suggested solution                   Response                      Status     Edit Status
             /Edito Page     figure locator
               rial
                         22 4.4.4 Reject It seems the definitions of the reject reason
                            CT_IU           codes could easily fit in the table 10 in
                                            another column. So I say move them.                                        This is not consistent with other tables in
IBM-044         E                                                                                                      the Standard.                                   R
                         23 4.4.4 Reject The statement << {What does this mean? -
IBM-045         E           CT_IU           CWC} >> needs to be deleted.                                               See Brocade-020.                                A      Done.
                         23 4.4.4 Reject Globally<CRLF>The reasons code should
                            CT_IU           not be indicated by quotes, instead they
IBM-046         E                           should be all caps.                                                        Is this an ISO requirement?                     R
                         24 4.5.2.1 Fabric This needs to be deleted << {What about
                            login and       NL_Ports? Change to Nx_Port. - CWC} >>                                                                                            Pending. Need
                            N_Port login                                                                                                                                      to make this a
IBM-048         E                                                                                                      See QLogic-010.                                 A      global change.
                         24 4.5.2.3         The statement << The 'F/M/L' column
                            Exchange        indicates whether the Sequence may be the
                            and             First, Middle, or Last Sequence of the
                            Sequence        Exchange. The 'SI' column indicates
                            management whether Sequence Initiative is Held or
                                            Transferred. The 'M/O' column indicates
                                            whether support for the Sequence is
                                            Mandatory or Optional. >> should all be in a
                                            footer to table 12 not in text above the table.
                                            If is stays are text above the table then all
                                            the quoted terms should become unquoted.
IBM-051         E                                                                                                      Added to footnote.                              A      Done.
McDATA-12       E        24 4.5.2.1         Your note needs to be answered.                 Change it to Nx_Ports.     See QLogic-010.                                 A      Pending.
                         25 4.5.2.4.2       The term << (binary xxxx). >> should be                                    Change to standard binary notation
IBM-052         E           Routing bits either << (xxxxb) >> or << ( xh) >>.                                          xxxxb.                                          A      Done.
                         25 Many            4.5.2.4.2 Routing bits<CRLF>Many terms
                                            are quoted. In almost all cases they should
                                            not be be. Remove all the quoted terms in
IBM-053         E                           this standard.                                                             Remove quotes.                                  A      Done.
                         25 4.5.2.4.6       The term << (binary xxxx xxxx) >> should be
                            Type            either << (xxxx xxxxb) >> or << (xxh) >>.
IBM-054         E                                                                                                      Changed to hex notation.                        A      Done.
                         26 4.5.2.4.12      The statement << shall be set to 0. >>
                            Relative        should be << shall be set to zero. >>
IBM-057         E           offset                                                                                     As suggested.                                   A      Done.
                         26 4.5.2.5         The statement << synchronous mode
                            Correlation of transactions will typically correlate a request
                            requests and to a response >> should be << synchronous
                            responses       mode transactions typically correlate a
IBM-058         E                           request to a response >>                                                   As suggested.                                   A      Done.




                                                                                       Page 49 of 91
                                                                      FC-GS-4 Revision 7.6 Comments
                                                                                09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                                Problem Description                Suggested solution                   Response               Status     Edit Status
             /Edito Page     figure locator
               rial
                         27 Many            4.5.3.3 Exchange and Sequence
                                            management Global Everywhere the term
                                            << That is >> is used should be changed to                            Fixed two instances in Cluaus 4. And
IBM-059         E                           (i.e., ... ).                                                         three in clause 8.2.                     A      Done.
                         27 Many            4.5.3.3 Exchange and Sequence
                                            management<CRLF>In some places
                                            Sequence Initiative is listed as << Sequence
                                            (SI) >> in others it's << SI >> in other it's <<
                                            Sequence Initiative >>. Pick one and it in all                        Usage appears to be consistent with
IBM-060         E                           cases..                                                               context.                                 R
                         27 Many            4.5.3.3 Exchange and Sequence
                                            management<CRLF>global<CRLF>Every
                                            where the term << For example, >> is used
                                            it should be changed to << (e.g., ... ) >>.
IBM-061         E                                                                                                 As suggested.                            A      Done.
                         27 4.5.3.3         The statement << The 'F/M/L' column
                            Exchange        indicates whether the Sequence may be the
                            and             First, Middle, or Last Sequence of the
                            Sequence        Exchange. The 'SI' column indicates
                            management whether Sequence Initiative is Held or
                                            Transferred. The 'M/O' column indicates
                                            whether support for the Sequence is
                                            Mandatory or Optional.. >> should all be in a
                                            footer to table 12 not in text above the table.
                                            If is stays are text above the table then all
                                            the quoted terms should become unquoted.
IBM-062         E                                                                                                 Will make note to table.                 A      Done.
                            4.5.3.3 4th     second sentence should say asynchronous Change to asynchronous.
McDATA-13       E        27 paragraph       instead of synchronous.                                               As suggested.                            A      Done.
                         28 4.5.3.4.2       The term << (binary xxxx). >> should be
IBM-063         E           Routing bits either << (xxxxb) >> or << ( xh) >>.                                     Use standard binary notation.            A      Done.
                         28 4.5.3.4.6       The term << (binary xxxx xxxx) >> should be
                            Type            either << (xxxx xxxxb) >> or << (xxh) >>.
IBM-064         E                                                                                                 Use standard hex notation.               A      Done.
                         28 4.5.3.4.12      The statement << shall be set to 0. >>
                            Relative        should be << shall be set to zero. >>
IBM-067         E           offset                                                                                As suggested.                            A      Done.
                         29 4.5.3.5         The statement << synchronous mode
                            Correlation of transactions will typically >> should be <<
                            requests and synchronous mode transactions typically >>
IBM-068         E           responses                                                                             As suggested.                            A      Done.




                                                                                   Page 50 of 91
                                                                           FC-GS-4 Revision 7.6 Comments
                                                                                     09/23/03 (03-083vA)


              Techn
               ical Physical Section/table/
 Company-#                                                  Problem Description                     Suggested solution                   Response   Status     Edit Status
              /Edito Page    figure locator
                rial
                          30        4.7      'may (and is encouraged to)' sounds like a
                              (Persistence fancy way of saying 'should' to me
                               of actions
                             after Logout),
ENDL-014         E               p 1, s 1                                                                                Change to "should".          A      Done.
                          30                 This mechanism provides a means to
                                             validate requests and responses which are
                                             transferred without change between
                                             authorized CTs, and distinguish these from
                                             requests and responses which are corrupted
                                             ... [s/b] This mechanism provides a means
                                             to validate +that+ requests and responses -
                                             which- are transferred without change
                                4.8.1 (CT between authorized CTs, and distinguish
                             Authenticatio these from requests and responses +that+-
                              n Overview), which- are corrupted ...
ENDL-016         E               p 1, s 3                                                                                As suggested.                A      Done.
                          30 4.7             The statement << (and is encouraged to)
                             Persistence >> has not place in a standard and needs to
                             of actions      be deleted.
IBM-069          E           after Logout                                                                                See ENDL-014.                R
                          30 4.8.1           The << which >> should be a << that >> in
IBM-070          E           Overview        two places.                                                                 See ENDL-016.                R
                             4.7 first       "may (and is encouraged to do so)" is a          Change to "should"
McDATA-14        E        30 sentence        should                                                                      See ENDL-014.                A      Done.
                             Note 19 in      Note 19 refers to the Key Server, which has Remove Note 19
                             Section 4.8.1 been obsoleted
Brocade-026      E        31                                                                                             As suggested.                A      Done.
                          31 4.8.1 (CT which [s/b] that
                             Authenticatio
                              n Overview),
                             1st p after a,b
ENDL-017         E               list, s 1                                                                               As suggested.                A      Done.
                          31 4.8.1 (CT These limits are ... [s/b] The acceptable
                             Authenticatio limits on time stamp values are ...
                              n Overview),
ENDL-018         E               Note 18                                                                                 As suggested.                A      Done.
                          31 4.8.1 (CT criteria ... that is [s/b] criteria ... that are
                             Authenticatio [criteria is plural, criterion is singular form of
                              n Overview), criteria]
                               1st p after
ENDL-019         E            note 18, s 2                                                                               As suggested.                A      Done.




                                                                                        Page 51 of 91
                                                                             FC-GS-4 Revision 7.6 Comments
                                                                                         09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                                 Problem Description                        Suggested solution                    Response                   Status     Edit Status
             /Edito Page    figure locator
               rial
                         31 4.8.1 (CT         Key Server [s/b] Key Distribution Server
                            Authenticatio
                            n Overview),                                                                                   Note 19 hass been removed. See
ENDL-020        E              note 19                                                                                     Brocade-026.                                  R
                         31 4.8.1             The statement << (110 and 111) >> should
IBM-071         E           Overview          be << (110b and 111b) >>.                                                    As suggested.                                 A      Done.
                         31 4.8.1             <CRLF>Lots of needless quotes in this
IBM-072         E           Overview          section.                                                                     See McDATA-15                                 A      Done.
                         31 4.8.1             The statement << discarded (and rejected if
                            Overview          it is a Request CT_IU) if the above >>
                                              should be << discarded and rejected if it is a
IBM-073        E                              Request CT_IU if the above >>                                                As suggested.                                 A      Done.
                          32        4.8.3     ...the encryption identifier. table 15 defines
                                (Encryption ... [s/b] ...the encryption identifier. Table 15
                               Algorithm), p defines ...
ENDL-022       E                 2, s 1 & 2                                                                                As suggested.                                 A      Done.
                          32   4.8.3          The statement << (vendor specific
                               Encryption     algorithms) >> should be deleted as it has
IBM-075        E               Algorithm      no value here.                                                               As suggested.                                 A      Done.
                               below b)       " "s around message signature and hash           remove "s                   You're right. It's like watching Dr. Evil
McDATA-15      E          32                  should be removed.                                                           speak. Quotes removed.                        A      Done.
McDATA-18      E          32   4.8.2          "shall be able to" should just be "shall"        change to "shall".          As suggested.                                 A      Done.
                          33        4.9.1     Regarding, 'At present only one common
                                 (Common request is defined.' Table 16 appears to
                                 Requests define three common requests. Perhaps this
                                Description), paragraph should be removed.
ENDL-023       E                     p2                                                                                    As suggested.                                 A      Done.
                          33   4.9.1          The statement << Common Requests
                               Description    provide are able to be executed by all server
                                              types. >> makes no sense and I have no
                                              idea how to fix it but it does need to be fixed.                             Change to: "Common Requests may be
IBM-079        E                                                                                                           executed for all server types."               A      Done.
                               4.9.1          "Common Requests provide are able" is           Probably remove "provide".
McDATA-19      E          33                  incorrect.                                                                   See IBM-079.                                  R
                               4.9.1          Second sentence should be deleted since         Delete sentence.
McDATA-20      E          33                  three common requests are defined now.                                       See ENDL-023.                                 A      Done.
QLogic-013     E          33 4.9.1            3 common requests are defined.
                                                                                                                           See ENDL-023.                                 A      Done.
                          34       4.9.3     requestor [s/b] Requesting_CT [this
                                 (Reason     probably represents the tip of a messy
                                   Code      global change iceberg]                                                                                                             Pending. Yep it
                               Explanations)                                                                                                                                    does… Is this
ENDL-024       E                 , p 1, s 1                                                                                                                              O      really worth it?




                                                                                            Page 52 of 91
                                                                         FC-GS-4 Revision 7.6 Comments
                                                                                   09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                               Problem Description                     Suggested solution                   Response                   Status     Edit Status
             /Edito Page    figure locator
               rial
                         34       4.9.3    one ... are returned [s/b] one ... is returned
                                (Reason
                                  Code
                            Explanations)
ENDL-025        E               , p 3, s 1                                                                            As suggested.                                A      Done.
                         34                Regarding 'After a period of 6 times
                                           R_A_TOV has elapsed ... a service may
                                           discard any remaining information
                                           associated with the transaction.' This
                                           statement has no direct relationship with
                                  4.9.3    reason code explanations (the title of the
                                (Reason    subclause). To aid persons trying to find this
                                  Code     information it should be placed in a
                            Explanations) subclause more closely related to what it                                   I agree. I'm taking nominations as to
ENDL-026        E                  ,p4     says.                                                                      where this should be placed.                 O      ???
                         34                which [s/b] that [2 instances]
                               4.9.4 (Get
                                  More                                                                                Partial acceptance. The first "which" is
                             Information),                                                                            really needed, the second has been
ENDL-027        E           p 2, s 2 & s 3                                                                            changed to "that".                           A      Done.
                         34 4.9.3 Reason The statement << has been unsuccessfully
                            Code           completed. >> should be << has been
                            Explanations unsuccessful. >>.
IBM-080         E                                                                                                     Silly language replaced as requested.        A      Done.
                         34 4.9.5.1        The statement << (i.e.Name Server). >>
IBM-082         E           Overview       should be << (i.e., Name Server). >>.                                      As suggested.                                A      Done.
Andiamo-14      E        35 4.9.5.1        Change SCN in RSCN                             Update accordingly.         As suggested.                                A      Done.
                         35      4.9.5.1   extender link service [s/b] extended link
                                 (Server   service
                              Registration
                            ... Overview),
                            1st p on pg, s
ENDL-029        E                    1                                                                                As suggested.                                A      Done.
                         35      4.9.5.1   SCN is not in the acronyms list and the
                                 (Server   meaning is not obvious from the context.
                              Registration
                            ... Overview),
                            1st p on pg, s
ENDL-030        E                    3                                                                                See Andiamo-14.                              R
                         35      4.9.5.1   SSB and SSE methods [s/b SSB and SSE
                                 (Server   commands [if I read table 16 correctly]
                              Registration
                            ... Overview),
                             2nd p on pg,
ENDL-032        E                   s2                                                                                Actually should be "requests".               A      Done.



                                                                                      Page 53 of 91
                                                                               FC-GS-4 Revision 7.6 Comments
                                                                                          09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                                Problem Description                         Suggested solution                   Response                  Status     Edit Status
             /Edito Page    figure locator
               rial
                         35                  ...a client notifies that particular server that a
                                4.9.5.2      collection of requests is beginning and when
                             (Delineating    registration is complete. [s/b] ...a client
                                 Server      notifies that particular server that a collection
                             Registration    of requests is beginning and when -
                             Sessions), p    registration-+the collection+ is complete.                                    Suggested text is close, but not yet               ??? Any
ENDL-033        E                1, s 2                                                                                    correct.                                    O      suggestions?
                         35     4.9.5.2      methods [s/b] commands [twice]
                             (Delineating
                                 Server
                             Registration
                             Sessions), p                                                                                  This sentence needs more work than just            ??? Any
ENDL-034        E             2, s 1 & s 2                                                                                 replacing methods with requests.            O      suggestions?
                         35     4.9.5.3      sender [s/b] requestor [or s/b]
                                (Server      Requesting_CT
                                Session
                            Begin), p 1, s
ENDL-035        E                   3                                                                                      Should be "requestor".                      A      Done.
                         35     4.9.5.3      ...respond with a Server Session End
                                (Server      request. [s/b] identify the end of the
                                Session      registration with a Server Session End
                            Begin), p 1, s   request.
ENDL-036        E                   3                                                                                      As suggested.                               A      Done.
                         35 4.9.5.1          The statement << database changes
                            Overview         (through the<CRLF>Registered State
                                             Change Notification extender link service).
                                             >> should be << database changes through
                                             the<CRLF>Registered State Change
                                             Notification extender link service (see FC-
IBM-083        E                             FS).                                                                          As suggested.                               A      Done.
                          35 4.9.5.1         The statement << for that services
                             Overview        (versus<CRLF>the server determining
                                             registration is complete via implementation
                                             specific techniques and
                                             potentially<CRLF>generating notifications in
                                             a less optimal manner). >> should be << for
                                             that services versus<CRLF>the server
                                             determining registration is complete via
                                             implementation specific techniques and
                                             potentially<CRLF>generating notifications in
IBM-084        E                             a less optimal manner. >>                                                     As suggested.                               A      Done.




                                                                                             Page 54 of 91
                                                                            FC-GS-4 Revision 7.6 Comments
                                                                                       09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                                Problem Description                         Suggested solution                          Response              Status     Edit Status
             /Edito Page     figure locator
               rial
                         35 4.9.5.2           The statement << and subtype for with the
                            Delineating       session is being bracketed. >> makes no
                            Server            sense and I don't know how to fix it but it
                            Registration      needs to be fixed.
IBM-085         E           Sessions                                                                                              Agreed.                                 O      ??? Any ideas?
                            4.9.5.4           FFFFFEh is the Fabric F_Port and not the         Change to Fabric F_Port.
McDATA-21       E        35                   Name Server.                                                                        See QLogic-015.                         R
                            first             "RSCN extender link service" is incorrect.       change to "extended link service". I don't see any such phrase on said
McDATA-22       E        35 paragraph                                                                                             page.                                   R
QLogic-014      E        35 1st               Typo: "Extender Link Service".                   Should be "Extended Link
                            paragraph on                                                       Service".
                            page.                                                                                                 As suggested.                           A      Done.
                         37                   The Directory Service is provided as a
                            5.1 (Directory    means to discover ... [wrba (would read
                                Service       better as)] The Directory Service provides a
                             Overview), p     means to discover ...
ENDL-037        E                 1, s 1                                                                                          As suggested.                           A      Done.
                         37                   This document defines a standard model for
                            5.1 (Directory    requests and responses ... [wrba] This
                                Service       standard defines the model for requests and
                             Overview), p     responses ...
ENDL-038        E                 2, s 1                                                                                          As suggested.                           A      Done.
                         37 5.1 Overview      The statement << This document defines >>
                                              should be << This standard defines >>.
IBM-086        E                                                                                                                  See ENDL-038.                           A      Done.
                          39     5.2.2.1      Please add a cross reference to a clause
                                 (Name        describing zoning in the following: 'If Zones
                                 Server       exist within the fabric, the Name Server shall
                                protocol      restrict access to information in the Name                                                                                         ??? Good point
                             Overview), p     Server database based on the Zone                                                                                                  in the light of
ENDL-040       E                    3         configuration.'                                                                                                             O      Hard Zoning…
                          39     5.2.2.2      ... request and their responses; [s/b] ...
                                (CT_IU        requests and their responses;
                               preamble
                              values), p 1,
ENDL-041       E                   s1                                                                                             As suggested.                           A      Done.
                          39 5.2.2.1          A reference to the zone section would be
                             Overview         useful after the statement << Zone
IBM-089        E                              configuration.>>.                                                                   See ENDL-040.                           O




                                                                                            Page 55 of 91
                                                                              FC-GS-4 Revision 7.6 Comments
                                                                                         09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                                 Problem Description                         Suggested solution                   Response                  Status     Edit Status
             /Edito Page    figure locator
               rial
                         43                   this document. [s/b] this standard. [twice]
                                  5.2.2.3     [capitalized or not as per the global decision
                            (Registration)    noted in these comments]
                              , 1st p after
                            1st b,c list on
                            pg & 5.2.2.4,
                               p 1, s 1 &
                            5.2.2.5, p 2, s
ENDL-043        E                    1                                                                                      As suggested (Withoug Capililization).      A      Done.
                         43       5.2.2.3     If overlapping registrations for the same
                            (Registration)    object is performed, ... [s/b] If overlapping
                                , last p in   registrations for the same object are
                             subclause, s     performed, ...
ENDL-044        E                    1                                                                                      As suggested.                               A      Done.
                         43 5.2.2.3           The statement << this document. >> should
IBM-091         E           Registration      be << this standard >>.                                                       As suggested.                               A      Done.
                         43 5.2.2.3           The statement <<registration requests will                                    I don't think it's a matter of winning.
                            Registration      have won. >> should be << registration                                        Change to "registration requests take
IBM-092         E                             requests won. >>.                                                             precedence."                                A      Done.
                         44       5.2.3.1     The object Permanent Port Name appears
                                  (Name       in table 22 but not in table 24.
                                  Server
                               objects ...
                              Overview),
ENDL-047        E                table 24                                                                                   See McData-27.                              A      Done.
                         44 5.2.3.2 thru      Would it be possible to reference a standard
                                5.2.3.4 &     other than FC-PH? [5 instances]
                                5.2.3.7 &
ENDL-048        E                5.2.3.12                                                                                   Yes. FC-FS.                                 A      Done.
                         44 5.2.3.1        The statement << table 22 are described
                            Overview       below. >> should be << table 22 are
IBM-094         E                          described in 5.2.3 >>.                                                           As suggested.                               A      Done.
                         44 5.2.3.1        The statement << (note that this only
                            Overview       represents the model and does not seek to
                                           dictate specific implementation details). >>
IBM-095        E                           should be made into a real note.                                                 As suggested.                               A      Done.
                          47 5.2.3.8 (FC-4 Could table 25 be positioned after the rules
                                TYPEs),    instead of between the introduction to the
ENDL-049       E                Table 25   rules and the rules themselves?                                                  Move (see also) Paragaph after table.       A      Done.
                          47 5.2.3.8 FC-4 The statement << see also table 25 >>
                             TYPEs -       should be << see table 25 >>.
IBM-096        E             Format                                                                                         As suggested.                               A      Done.




                                                                                              Page 56 of 91
                                                                             FC-GS-4 Revision 7.6 Comments
                                                                                        09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                                Problem Description                         Suggested solution                    Response   Status     Edit Status
             /Edito Page     figure locator
               rial
                         49     5.2.3.13      Is it possible to reference a standard other
                                 (Hard        than FC-PH-2?
                              Address), p
ENDL-051        E                 1, s 1                                                                                    Yes. Change to FC-FS.        A      Done.
                         50 5.2.3.14 FC-4     The statement << As of this writing, FCP-2
                            Descriptor -      was expected<CRLF>to contain such a
                            Format            definition. >> should be << (e.g., FCP-2
IBM-097         E                             contains such a definition). >>                                               As suggested.                A      Done.
                         51 5.2.3.15 (FC-     128-bytes [s/b] 128 bytes
                              4 Features),
                                last p in
ENDL-054        E              subclause                                                                                    As suggested.                A      Done.
                         51 5.2.4 Reason      The statement << has been unsuccessfully
                            code              completed. >> should be << has failed. >>.
IBM-098         E           explanations                                                                                    As suggested.                A      Done.
                            last sentence     Port Name should be Permanent Port Name Change to Permanent Port Name.
McDATA-29       E        51                                                                                                 As suggested.                A      Done.
                         52                   ... one of the reason code explanations,
                                  5.2.4       shown in table 28, are returned. [s/b] ... one
                                (Reason       of the reason code explanations shown in
                                  code        table 28 is returned.
                            explanations)
ENDL-055        E            , 1st p on pg                                                                                  As suggested.                A      Done.
                         53 5.2.4 Reason      The statement << because the Port
                            code              Identifier<CRLF>cannot be registered, >>
                            explanations      should be << because the Port
IBM-099         E                             Identifier<CRLF>fails registration,>>                                         As suggested.                A      Done.
                         53 5.2.5.2 Query     The statement << A requestor wishing to
                            - Get all next    obtain all information on a specific Port
                            (GA_NXT)          Identifier may set the value of the Port>>
                                              should be << To obtain all information on a
                                              specific Port Identifier a requestor may set
IBM-100        E                              the value of the Port >>                                                      As suggested.                A      Done.
                             Table 29         GA_NXT should reference 4.3 like the other Change 16 to See 4.3 in the size
McDATA-30      E          53                  commands do for CT_IU Preamble.              of the CT_IU preamble.           See Andiamo-18.              A      Done.
Andiamo-18     E          54 Table 29         CT_IU preamble size incorrect                Change to "see 4.3"              As suggested.                A      Done.




                                                                                             Page 57 of 91
                                                                           FC-GS-4 Revision 7.6 Comments
                                                                                      09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                                Problem Description                      Suggested solution                   Response               Status     Edit Status
             /Edito Page     figure locator
               rial
                         54 5.2.5.2 Query The statement << The GA_NXT request
                            - Get all next may be used to find all registered Port
                            (GA_NXT)        Identifiers in the Fabric, by reissuing
                                            the<CRLF>GA_NXT request, using the Port
                                            Identifier obtained from the Accept CT_IU,
                                            stopping when the initially<CRLF>used Port
                                            Identifier threshold is recrossed. >>
                                             should be << The GA_NXT request may be
                                            used to find all registered Port Identifiers in
                                            the Fabric, by reissuing the<CRLF>GA_NXT
                                            request, using the Port Identifier obtained
                                            from the Accept CT_IU, and then stopping
                                            when the initially<CRLF>used Port Identifier
                                            threshold is recrossed. >>

IBM-101        E                                                                                                        As suggested.                            A      Done.
                           54 5.2.5.2 Query The statement << This function cannot be
                              - Get all next used to find >> should be << This function
                              (GA_NXT)       does not find >>.
IBM-102        E                                                                                                        See ENDL-057.                            R
                           54 5.2.5.2 Query In the definitions of the fields, fields are
                              - Get all next returned or fields contain. Why are there two
                              (GA_NXT)       different ways of saying the same thing. Pick
IBM-103        E                             one and use it consistently.                                               Usage is based on context.               R
                           57 5.2.5.3 Query The statement << any order. Furthermore,
                              - Get          the order >> should be << any order and the
                              identifiers    order >>
IBM-105        E              (GID_A)                                                                                   As suggested.                            A      Done.
                           64 Many           5.2.5 Commands<CRLF>There are no
                                             references to where the fields sent or
                                             returned in the CT commands are defined.                                   I'm sorry which fields? Need a more
IBM-107        E                             This needs to be fixed.                                                    percise location.                        R
                           65 5.2.5.13       The statement needs to be deleted << {If
                              Query - Get one of the FC-4 TYPEs does not have a
                              FC-4           registered FC-4 Descriptor, how is that
                              Descriptors    reflected in the<CRLF>Response?
                              (GFD_ID)       Especially since NULL is a valid descriptor
                                             (i.e., you can register a descriptor of
                                             zero<CRLF>length). Should a reject be sent                                 Question needs to be resolved before
IBM-108        E                             in this case? - CWC} >>.                                                   this can removed.                        O
                           68 5.2.5.17       The statement << in any order. Furthermore,
                              Query - Get the order may >> should be << in any order
                              Port           and the order may >>.
                              Identifiers
IBM-109        E              (GID_NN)                                                                                  As suggested.                            A      Done.



                                                                                          Page 58 of 91
                                                                            FC-GS-4 Revision 7.6 Comments
                                                                                       09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                                Problem Description                         Suggested solution                   Response   Status     Edit Status
             /Edito Page     figure locator
               rial
                         69 5.2.5.18          The statement << in any order. Furthermore,
                            Query - Get       the order may >> should be << in any order
                            Port Names        and the order may >>.
IBM-110         E           (GPN_NN)                                                                                       As suggested.                A      Done.
                         72 5.2.5.24          The statement << (as defined in FC-PH) >>
                            Query - Get       should be << (see FC-FS) >>.
                            Port
                            Identifiers
IBM-111         E           (GID_FT)                                                                                       As suggested.                A      Done.
                         73 5.2.5.24          The statement << in any order. Furthermore,
                            Query - Get       the order may >> should be << in any order
                            Port              and the order may >>.
                            Identifiers
IBM-112         E           (GID_FT)                                                                                       As suggested.                A      Done.
                         74 5.2.5.25          The statement << (as defined in FC-PH) >>
                            Query - Get       should be << (see FC-FS) >>.
                            Port Names
IBM-113         E           (GPN_FT)                                                                                       As suggested.                A      Done.
                         75                   Is it possible to reference a standard other
                                5.2.5.26      than FC-PH? [2 instances]
                             (Query - Get
                                 Node
                             Names), p 1,
ENDL-059        E           s 3 & note 34                                                                                  Reference FC-FS.             A      Done.
                         75 5.2.5.25          The statement << in any order. Furthermore,
                            Query - Get       the order may >> should be << in any order
                            Port Names        and the order may >>.
IBM-114         E           (GPN_FT)                                                                                       As suggested.                A      Done.
                         75 5.2.5.26          The statement << (as defined in FC-PH) >>
                            Query - Get       should be << (see FC-FS) >>.
                            Node Names
IBM-115         E           (GNN_FT)                                                                                       As suggested.                A      Done.
                         77 5.2.5.26          The statement << in any order. Furthermore,
                            Query - Get       the order may >> should be << in any order
                            Node Names        and the order may >>.
IBM-116         E           (GNN_FT)                                                                                       As suggested.                A      Done.
                         77 5.2.5.27          This last sentence on this page is split
                            Query - Get       between pages 77 and 78 before the end of
                            Port              the printable area on page 77. This should
                            Identifiers       be corrected in frame.
IBM-118         E           (GID_PT)                                                                                       As suggested.                A      Done.




                                                                                             Page 59 of 91
                                                                               FC-GS-4 Revision 7.6 Comments
                                                                                         09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                                    Problem Description                        Suggested solution                     Response             Status     Edit Status
             /Edito Page     figure locator
               rial
                         78 5.2.5.27              The statement << in any order. Furthermore,
                            Query - Get           the order may >> should be << in any order
                            Port                  and the order may >>.
                            Identifiers
IBM-119         E           (GID_PT)                                                                                            As suggested.                          A      Done.
Andiamo-19      E        79 Table 83              In other standards hexadecimal values are       Use a consistent convention   This is the ISO notation. Other
                                                  written as hex'number                                                         standards should be changed to the
                                                                                                                                notation used in GS-4.                 R
                          80       5.2.5.30       table 60 [s/b] table 86
                                (Query - Get
                                       Port
                                Identifiers), p
ENDL-060       E                     1, s 2                                                                                     As suggested.                          A      Done.
                          80       5.2.5.30       table 61 [s/b] table 87
                                (Query - Get
                                       Port
                                Identifiers), p
ENDL-061       E                         2                                                                                      As suggested.                          A      Done.
                          80   5.2.5.30           The statement << {How does the Fabric Port
                               Query - Get        Name map to the Node Name? Seems like
                               Port               what we really need is a Fabric
                               Identifiers        Port<CRLF>Name object definition. - CWC}
                               (Fabric Port       >> needs to be deleted.
                               Name)
IBM-120        E               (GID_FPN)                                                                                        See McDATA-25.                         A      Done.
                          81       5.2.5.31       Remove the dash before 'Query' in ' - Query -
                                (Query - Get      Get Permanent Port Name ...'
                                 Permanent
                                 Port Name
                                       ...),
                                  subclause
ENDL-062       E                       title                                                                                    How did that get there?                A      Done.
                          81       5.2.5.31       table 124 [s/b] table 88
                                (Query - Get
                                 Permanent
                                 Port Name
ENDL-063       E                 ...), p 1, s 2                                                                                 As suggested.                          A      Done.
                          81       5.2.5.31       table 125 [s/b] table 89
                                (Query - Get
                                 Permanent
                                 Port Name
ENDL-064       E                    ...), p 2                                                                                   As suggested.                          A      Done.




                                                                                              Page 60 of 91
                                                                           FC-GS-4 Revision 7.6 Comments
                                                                                     09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                               Problem Description                      Suggested solution                          Response                     Status     Edit Status
             /Edito Page     figure locator
               rial
                         83 5.2.5.32          The statement << in any order. Furthermore,
                            Query - Get       the order may >> should be << in any order
                            Port              and the order may >>.
                            Identifiers
IBM-121         E           (GID_FF)                                                                                          As suggested.                                  A      Done.
                            second            Cut and paste error again. Name Server       Change to Node Name, class of
                            paragraph,        may reject registration of the Port Name… is service, FC-4 Typoes, FC-4         Couldn't quite place where this is, but in
                            2nd sentence      incorrect.                                   Features, in 5.2.5.34-36 and 42.   5.2.5.34, change to "Node Name". In
                                                                                                                              5.2.5.35, change to "Class of Service".
McDATA-34      E          84                                                                                                  In 5.2.5.36, chqange to "FC-4 TYPEs".          A      Done.
                               second       Cut and paste error again. Name Server       Change to deregistration of all.
                               paragraph,   may reject registration of the Port Name… is
                               2nd sentence incorrect.                                                                                                                              ??? Which
McDATA-35      E          84                                                                                                                                                        clause?
                          95 5.3.1         The statement << party registration for
                             Overview      unspecified reasons. >> should be << party
                                           registration for reasons not specified by this                                     IP Address Server Obsoleted. See
IBM-135        E                           standard. >>                                                                       Andiamo-21.                                    R
                          96               Regarding: 'Registrations are limited to a
                                           single IP Address object at a time.' 'Time' is
                                           an imprecise delimiter for the stated
                                           restriction. Is 'time' meant to imply within a
                                           single login session? Is 'time' meant to imply
                                           within a single request (or command)? Does
                                           'time' have some other meaning beyond
                                           those guessed above? In any case, please
                                 5.3.2.3   replace 'time' is a more precise description
                             Registration, of the delimiter for the requirement.                                              IP Address Server Obsoleted. See
ENDL-065       E                p 1, s 1                                                                                      Andiamo-21.                                    R
                          97 5.3.3.1       The statement << are described below. >>
                             Overview      should be << are described in 5.3.3. >>.                                           IP Address Server Obsoleted. See
IBM-136        E                                                                                                              Andiamo-21.                                    R
                          97 5.3.3.1          The statement << IP Address Server needs
                             Overview         to return an Accept CT_IU >> should be <<
                                              IP Server is required to return an Accept                                       IP Address Server Obsoleted. See
IBM-137        E                              CT_IU >>.                                                                       Andiamo-21.                                    R
                          97 5.3.3.1          The statement << (note that this only
                             Overview         represents the model and does not seek to
                                              dictate specific                                                                IP Address Server Obsoleted. See
IBM-138        E                              implementation<CRLF>details\                                                    Andiamo-21.                                    R




                                                                                        Page 61 of 91
                                                                           FC-GS-4 Revision 7.6 Comments
                                                                                      09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                                Problem Description                          Suggested solution                          Response                   Status     Edit Status
             /Edito Page    figure locator
               rial
                         97 5.3.3.2 IP      Everything from the start of this section up to
                            Address -       the end of 2nr a,b,c list is a duplicate of
                            Format          section 5.2.3.6. The duplicate information
                                            should be deleted and replaced with a
                                            reference. << See 5.2.3.6 for a description                                           IP Address Server Obsoleted. See
IBM-139         E                           of the IP Address format. >>                                                          Andiamo-21.                                   R
                         98 5.3.3.3 (Port Could a standard other than FC-PH be
                             Identifier), p referenced?                                                                           IP Address Server Obsoleted. See
ENDL-066        E                1, s 2                                                                                           Andiamo-21.                                   R
Andiamo-22      E       100 Table 127       In other standards hexadecimal values are         Use a consistent convention
                                            written as hex'number                                                                 ISO convention.                               R
Andiamo-24      E       102 Table 130       Reserved for Lock Server or simply                update
                                            reserved?                                                                             It says "Lock Server" doesn't it?             R
                        102       6.1       This document defines a standard model for
                            (Managemen requests and responses ... [wrba] This
                               t Service    standard defines the model for requests and
                            Overview), p responses ...
ENDL-067        E                2, s 1                                                                                           As suggested.                                 A      Done.
                        102 6.1 Overview The statement << This document defines >>
                                            should be << This standard defines >>.
IBM-140         E                                                                                                                 See ENDL-067.                                 A      Done.
McDATA-37       E       102 6.1 c)          "Zone information" should be "Zoning.             Change to "Zoning information".     As suggested.                                 A      Done.
                            Table 130       It would be helpful to add a column to            Add a new column and then
                                            specify which section each subtype is             specify that the Fabric
                                            specified in.                                     Configuration Server is in Clause
                                                                                              6.2, Unzoned Name Server in….
                                                                                              Remove the reference in FDMI
McDATA-38      E          102                                                                 row.                                As suggested.                                 A      Done.
McDATA-39      E          102 Table 130      Lock Server is no more.                          Delete Lock Server.                 See Andiamo-24.                               R
                          104 6.2.1          The statement << Server is intended to be                                            No, we are not saying it should be
                              Overview       distributed >> should << Server should be                                            disributed, but that it is intended to be
IBM-142        E                             distributed >> .                                                                     distributed.                                  R
Andiamo-25     E          106 Table 131      GPFCP badly formatted                            update                              Cell width increased.                         A      Done.
                          106     6.2.2.2    Is it possible to remove the line wrap in
                                  (CT_IU     GPFCP?
                                 preamble
                                  values),
                                Table 131,
ENDL-068       E                code 01A4                                                                                         Yep.                                          A      Done.
                          106 table 131      The term << LUN >> needs to be added to                                              Wouldn't this also require a definition?
IBM-143        E                             the abbreviations list.                                                              Any volunteers to provide?                    O      Pending.
                          107 6.2.2.3        The statement << Note that >> should be
IBM-144        E              Registration   deleted.                                                                             As suggested.                                 A      Done.
                          108 6.2.2.3        The statement << requests will have won.                                             It's not about WINNING… Change to
IBM-145        E              Registration   >> should be << requests have won. >>.                                               "take precedence."                            A      Done.



                                                                                         Page 62 of 91
                                                                            FC-GS-4 Revision 7.6 Comments
                                                                                         09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                              Problem Description                  Suggested solution                                    Response                   Status     Edit Status
             /Edito Page    figure locator
               rial
Andiamo-26      E       109 Figure 5       Add the new attributes: Zoning Enforcement update
                                           Status to the Interconnect Element Object,
                                           and Speed to the Port Object
                                                                                                                                   As suggested.                                A      Done.
Andiamo-28     E         113 Table 136        Add a note with a definition of F/NL_Port       update
                                                                                                                                                                                       ??? Which
                                                                                                                                   Actually, this should be a definition in            defintions
                                                                                                                                   clause 3. Also need to define F_Port,               should be used?
                                                                                                                                   B_Port, E_Port, FL_Port, NL_Port, and               I'm assuming
                                                                                                                                   Nx_Port.                                     O      FC-SW-3?
                         113 table 137        The numbers in this table are not in ISO
IBM-146        E                              format. This needs to be fixed.                                                      As suggested.                                A      Done.
Andiamo-30     E         114 Note 44          refer to the new MIB                            update                               Which MIB is the new MIB?                    O      ???
                             End of           Last sentence could say more.                   Add "due to non-standard
                             NOTE                                                             methods for numbering physical
                                                                                              ports" to the end of the sentence.   Which Note? Cluase number? Note
McDATA-36      E         115                                                                                                       Number?                                      O      ???
                         117 6.2.3.3.8 Port   The statement << appropriate bit to 1. >>
                             Speed            should be << appropriate bit to one. >>.
IBM-149        E             Capabilities                                                                                          As suggested.                                A      Done.
                         117 6.2.3.3.9 Port   The statement << bit is set to 1, >> should
                             Operating        be << bit is set to one >>.
                             Speed
IBM-150        E                                                                                                             As suggested.                                      A      Done.
                         118 6.2.3.3.9 Port The statement << If the port\220s operating
                             Operating      speed can't be identified, >> should be << If
                             Speed          the port's operating speed isn't identifiable,
IBM-152        E                            >>.                                                                              As suggested.                                      A      Done.
Andiamo-32     E         120 6.2.3.4.2      double dot at the end of the first paragraph Remove a dot                        As suggested.                                      A      Done.
Andiamo-33     E         121 Table 150      Update the CAE reference                       Better reference: "Open Group
                                                                                           Technical Standard C706, DCE
                                                                                           1.1: Remote Procedure Call,                                                                 Pending. Need
                                                                                           August 1997,                                                                                to provide
                                                                                           http://www.opengroup.org/product                                                            correct formant
                                                                                           s/publications/catalog/c706.htm".                                                           for references
                                                                                                                                                                                O      section.
                         121 table 150     There are two periods at the end of the
IBM-154        E                           following << CAE Specification C309.. >>.                                             Remove period.                                 A      Done.
                             Table 150, 4f The Open Group CAE spec C309 is not               Add CAE to the Other References
                                           specified properly.                               section and reference it from Table
McDATA-45      E         121                                                                 150.                                See Andiamo-33.                                O
Andiamo-35     E         124 6.2.3.4.4        Platform Attribut Entry text says "an Platform Say: "a Platform Object"
                                              Object"                                                                            As suggested.                                  A      Done.




                                                                                            Page 63 of 91
                                                                          FC-GS-4 Revision 7.6 Comments
                                                                                     09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                                Problem Description                      Suggested solution                           Response                  Status     Edit Status
             /Edito Page     figure locator
               rial
                        124 end of page global<CRLF>Strange place for a page
                            124             break.<CRLF>The reason for this unusual
                                            break is because the table anchor is in the
                                            same paragraph as the text above the
                                            paragraph. The fix is to create a paragraph
                                            with no text that contains the table anchor.                                                                                           Pending. We'll
IBM-156         E                           This should be done for all tables.                                                                                             O      see…
                            last sentence The last sentence should finish on this page I know this is a Framemaker bug
                                            instead of the next page.                     that attaches the table to the next
                                                                                          paragraph. You can insert a blank
                                                                                          paragraph to fix the break.
McDATA-46       E       124                                                                                                                                                 O      Ponder.
                            Platform        "an Platform object" is incorrect.            change to "a Platform object"
                            Attribute
McDATA-47       E       124 Entry                                                                                               As suggested.                               A      Done.
                        126 6.2.3.4.5       6.1.2.1.7. - bad reference Replace with
                            Attribute       6.2.3.2.7 which is the Interconnect Element
IBM-157         E           Entry Format Management Address section.                                                            As suggested.                               A      Done.
                        126 6.2.3.4.5       6.1.2.1.7. - bad reference. Replace with
                            Attribute       6.2.3.2.7 which is the Interconnect Element
IBM-158         E           Entry Format Management Address section.                                                            As suggested.                               A      Done.
QLogic-022      E       128 Table 157       The "Null Value" for OS SCSI Bus Number Change this to '0'.
                                            uses the word 'zero'.                                                               As suggested.                               A      Done.
QLogic-023      E       128 Table 157       The "Null Value" for OS SCSI Target           Change this to '0'.
                                            Number uses the word 'zero'.                                                        As suggested.                               A      Done.
                        129 6.2.3.4.9.5     The reference << defined in table xxxx137,
                            FCP LUN         >> needs to be changed to << defined in
                            Name Format table 150 and table 149,>>.
IBM-160         E                                                                                                               As suggested.                               A      Done.
                            6.2.3.4.9.2     Reference to FC-HBA doesn't go anywhere. Add a reference to FC-HBA in 2.3
                                                                                          and properly reference it. This
                                                                                          improper reference is in a few        Reference added to clause 2.3 and it is
McDATA-49       E       129                                                               places, so do a search.               properly referenced.                        A      Done.
                        132 Global          Some random number of tables << depict
                                            >> things and some random number <<
                                            show >> things and some random number
                                            << illustrate >>. All these should be changed
IBM-161         E                           to one or the other.                                                                Is this an ISO convention?                  R
                        136 Globally        The statement << in any order. Furthermore,
                                            the order may >> should be << in any order
                                            and the order may >>. This occurs several
                                            times and should be changed in all cases.
                                            Hint: search on 'furthermore'.                                                                                                         Done. Did global
IBM-162         E                                                                                                               As suggested.                               A      search destroy.




                                                                                        Page 64 of 91
                                                                             FC-GS-4 Revision 7.6 Comments
                                                                                           09/23/03 (03-083vA)


              Techn
               ical Physical Section/table/
 Company-#                                                 Problem Description                         Suggested solution                        Response               Status     Edit Status
              /Edito Page     figure locator
                rial
                             6.2.5.17,         For GATIN, the reference to GPL is incorrect Change reference to 6.2.5.11
Brocade-024      E       146 GPL Note                                                                                            As suggested.                            A      Done.
                         146 6.2.5.18          The statement << Then he may change >>
                             Query - Get       uses << he >> who is << he >>. The << he
                             Switch            >> needs to be replaced with what ever <<
                             Enforcement       he >> is.
                             Status
IBM-163          E           (GSES)                                                                                              She?                                     A      Done.
                             6.2.5.18          "he" should be "administrator". We              Change "he" to "administrator".
McDATA-52        E       146                   shouldn't be sexist, just vague and boring.                                       See IBM-163.                             A      Done.
                             6.2.5.18          second paragraph says "Broadcast                Change to "Broadcast Zoning
McDATA-53        E       146                   Attributes" incorrectly.                        attributes"                       As suggested.                            A      Done.
                             6.2.5.18          "an Hard Zone" is incorrect                     Change to "a Hard Zone" in
McDATA-54        E       146                                                                   multiple places.                  As suggesed.                             A      Done.
Andiamo-39       E       147 Table 197         Update the reference to the new table           update
                                               number (see Andiamo-38)                                                           Updated automatically by FM.             A      Done.
                          150 6.2.5.22         6.7.4.5.1. - bad reference. Replace with
                              Query - Get      6.2.3.4.2 which is the Platform Name
                              PLATFORM         section.
                              Attribute
                              Block
IBM-164         E             (GPAB)                                                                                             As suggested.                            A      Done.
                          150 6.2.5.22         6.7.4.5.4. - bad reference. Replace with
                              Query - Get      6.2.3.4.4 which is the Platform Attribute
                              PLATFORM         Block section
                              Attribute
                              Block
IBM-165         E             (GPAB)                                                                                             As suggested.                            A      Done.
                          153 6.2.5.27         should be 'Node identification'
                              Query - Get
                              Node
                              Identification                                                                                     No, seems like "Node Identifiacation
IBM-166         E             Data (GNID)                                                                                        Data" is correct.                        R




                                                                                             Page 65 of 91
                                                                            FC-GS-4 Revision 7.6 Comments
                                                                                       09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                                Problem Description                        Suggested solution                   Response                     Status      Edit Status
             /Edito Page     figure locator
               rial
                        154 6.2.5.29          The following wording is not accurate <<
                            Register          The RPL Fabric Configuration Server
                            Platform          request shall be used to associate a
                            (RPL)             Platform Name with its attributes. This
                                              request allows the registration of a Platform
                                              and all of its attributes using a single
                                              transaction. >>. RPL does not provide for
                                              registration of ALL platform attributes.
                                              Suggest new wording <<The RPL Fabric
                                              Configuration Server request shall be used
                                              to associate a Platform Name with its
                                              Platform Node Names and key platform
                                              attributes. This request allows the
                                              registration of a Platform, associated
                                              Platform Node Names, and key attributes
                                              using a single transaction. >><CRLF>
IBM-167        E                                                                                                          As suggested.                                  A      Done.
                         158 6.2.5.33     6.7.4.5.1. - bad reference. Replace with
                             Register     6.2.3.4.2 which is the Platform Name
                             Platform     section.
                             Attribute
                             Block (RPAB)
IBM-168        E                                                                                                          As suggested.                                  A      Done.
                         158 6.2.5.33     6.7.4.5.4. - bad reference. Replace with
                             Register     6.2.3.4.4 which is the Platform Attribute
                             Platform     Block section
                             Attribute
                             Block (RPAB)
IBM-169        E                                                                                                          As suggested.                                  A      Done.
                         159 table 229        RPFP should be RPFCP                                                        Also fixed incorrect spelling in paragraph
IBM-170        E                                                                                                          immediately previous.                          A      Done.
                         160 6.2.5.36         The statement << used to destroy a
                             Deregister       registered >> should be << used to remove
                             Platform         a registered >>.
IBM-171        E             (DPL)                                                                                        As suggested.                                  A      Done.
                         162 6.2.5.38         The statement << The format of the
                             Deregister       Platform Name and Platform Management
                             Platform         Address fields are as defined in FC-GS-                                                                                           ??? All right, but
                             Management       3.>> should be removed. Platform Name                                                                                             we still need to
                             Address          format in particular is superseded by GS-4.                                                                                       define these
IBM-172        E             (DPLM)                                                                                                                                      O      fields.
QLogic-024     E         162 6.2.5.38, 2nd    The reference to FC-GS-3 should be
                             paragraph        changed t oa specific reference.                                            See IBM-172                                    O      Pending.




                                                                                            Page 66 of 91
                                                                              FC-GS-4 Revision 7.6 Comments
                                                                                          09/23/03 (03-083vA)


              Techn
               ical Physical Section/table/
 Company-#                                                 Problem Description                          Suggested solution                          Response                 Status     Edit Status
              /Edito Page    figure locator
                rial
                         166 6.3.1            The statement << Now, let\220s suppose
                             Overview         that N_Port M is >> should be << If that
IBM-173          E                            N_Port M is >>.                                                                       As suggested.                              A      Done.
                             6.4.1,           Sentence implies only soft zoning when it          Reword sentence to be more
                             paragraph,       should be general enough to include all            general; perhaps position zoning
                             1st sentence     types of enforcement.                              as an access control mechanism     Which Paragraph? Also, suggest
Brocade-009      E       168                                                                                                        wording.                                   O      ???
                             6.4.1 first      "… in that the fabric can group N_Port_ID          Change to "… in that the fabric
                             paragraph        identifiers into Zones." is restrictive to imply   can group devices into Zones."
Brocade-027      E       168                  one specific type of zoning.                                                          As suggested.                              A      Done.
                             6.4.1 first      "Zones may be configured through a switch          re-write as "Zones may be
                             paragraph        vendors‟ management tool, or via this              configured this Server, or via a
                             after first      Server." is only one mechanism outside the         mechanism outside the scope of     Changed to: Zones may be configured
                             unordered list   scope of this standard                             this standard."                    *via* this Server, or via a mechanism
Brocade-028      E       168                                                                                                        outside the scope of this standard.        A      Done.
                         168 6.4.1            The statement << that the fabric can group
                             Overview         N_Port_ID identifiers >> should be << that
                                              the fabric groups N_Port_ID identifiers >>.
IBM-174         E                                                                                                                   Reworded to "has the ability to group"     A      Done.
                          168 6.4.1           The statement << another can delete or
                              Overview        corrupt >> should be << another may delete
IBM-175         E                             or corrupt >>.                                                                        As suggested.                              A      Done.
                          168 6.4.1           The statement << An N_Port (or NL_Port)
                              Overview        may be a member >> should be << An
                                              N_Port or NL_Port may be a member >>.
IBM-176         E                                                                                                                   Actually, this should be Nx_Port.          A      Done.
                          168 6.4.1           The statement << attached; e.g., as
                              Overview        'Domain 1, Port 1'. The format >> should be
                                              < attached (e.g., as Domain 1, Port 1). The
IBM-177         E                             format >> .                                                                           As suggested.                              A      Done.
                          168 6.4.1           The statement << Fabric. For example, you
                              Overview        could have two Zone Sets, one for normal
                                              operation, and another for backup during off-
                                              hours. >> should be << Fabric (e.g., you
                                              could have two Zone Sets, one for normal
                                              operation, and another for backup during off-
IBM-178         E                             hours). >>                                                                            As suggested.                              A      Done.
                          168 6.4.1           The statement << Note that >> should be
                              Overview        deleted in the sentence << Note that only
                                              one Zone Set may be activated at
IBM-179         E                             one time. >>.                                                                         As suggested.                              A      Done.
                                6.4.2         default zone - This term is not defined       Page 170 change to "default
Brocade-030     E         170                 anywhere in the standard.                     zoning". See Brocade-012                See QLogic-025.                            O




                                                                                             Page 67 of 91
                                                                           FC-GS-4 Revision 7.6 Comments
                                                                                      09/23/03 (03-083vA)


              Techn
               ical Physical Section/table/
 Company-#                                                Problem Description                      Suggested solution                           Response                   Status     Edit Status
              /Edito Page    figure locator
                rial
                         170 6.4.2          There is a bulleted list that needs to be an
                             Terminology a,b,c list. Also, that list has italicized phrases
                                            that need to be made into normal text.
IBM-180          E                                                                                                              As suggested.                                A      Done.
                         170 6.4.2          The statement << restriction (or no ports
                             Terminology may communicate, depending
                                            on<CRLF>the implemented default zone
                                            behavior). >> should be << restriction or no
                                            ports may communicate, depending
                                            on<CRLF>the implemented default zone
IBM-182          E                          behavior. >>                                                                        As suggested.                                A      Done.
                             6.4.4.1 first  " … two distinct set of management              change to "… two distinct sets of
Brocade-035      E       171 sentence       requests, ..." should be "sets"                 management requests, …"             As suggested.                                A      Done.
                         171 6.4.3          The statement << Server adds and
                             Protocol       removes, activations, and queries >> should
                                            be << Server adds, removes, activations,
IBM-184          E                          and queries >>                                                                      As suggestd.                                 A      Done.
                         171 6.4.3          The statement << specified in the following
                             Protocol       sections. >> should be << specified in 6.4.4                                                                                            Done. Changed
                                            >>.                                                                                                                                     to references to
                                                                                                                                                                                    Basic and
                                                                                                                                                                                    Enhanced
                                                                                                                                Sentiment is correct, but reference is              zoning
IBM-185         E                                                                                                               wrong.                                       O      commands.
                           171 6.4.4.1        The statement << to deal with these two
                               Overview       distinct request sets: >> adds nothing and                                        I disagree. These commands are
IBM-186         E                             should be deleted.                                                                speciffically used to querly these sets.     R
                                 6.4.4.1      We suggest some rewording of the first          Change to "From a management
                                              paragraph to clarify how basic and              perspective, two distinct set of
                                              enhanced should work together.                  management requests are
                                                                                              provided: Enhanced and Basic.
                                                                                              Enhanced zoning requests can be
                                                                                              invoked if all the switches in the
                                                                                              fabric support Enhanced Zoning.
                                                                                              Otherwise, Basic Zoning is
McDATA-57       E          171                                                                supported.".                       It already says this.                       R
                                 6.4.4.1      What is the point of making 6.4.4.1 when it     Remove 6.4.4.1 and Overview so
McDATA-58       E          171                is the only clause in 6.4.4?                    that it becomes 6.4.4.             Aggreed. As suggested.                      A      Done.




                                                                                            Page 68 of 91
                                                                         FC-GS-4 Revision 7.6 Comments
                                                                                  09/23/03 (03-083vA)


              Techn
               ical Physical Section/table/
 Company-#                                             Problem Description                    Suggested solution                             Response                Status     Edit Status
              /Edito Page    figure locator
                rial
                             Last           Suggested rewording.                       Change to "If the Fabric is working
                             pragraph of                                               in Basic Zoning mode and is able
                             6.4.4.1                                                   to work in Enhanced mode, then
                                                                                       the management application may
                                                                                       change the Zoning operational
                                                                                       mode of the Fabric by issuing a
                                                                                       SFEZ request. If the Fabric is
                                                                                       unable to support Enhanced
                                                                                       Zoning mode, the management
                                                                                       application can discover which
                                                                                       Switches in the Fabric do not
                                                                                       support Enhanced Zoning through
                                                                                       the GEZ command."
McDATA-59       E         172                                                                                                As suggested.                             A      Done.
                              second        "work or in" is incorrect.                 remove "or".
McDATA-60       E         172 paragraph                                                                                      As suggested.                             A      Done.
                              6.4.5.1        "They permit to relate together a set of     rewrite.
                              second         management requests, and to achieve a
                              paragraph      consistent behavior for the case of two or
                                             more management applications operating
                                             over the same Switch." is an awkward                                            Changed to: They permit the Switch to
Brocade-037     E         173                sentence                                                                        relate                                    A      Done.
                          173 6.4.5.2 Add The statement << specified in this
                              and Remove document. >> should be << specified in this
IBM-189         E                            standard >>.                                                                    As suggested.                             A      Done.
                          173 6.4.5.2 Add The statement << overlapping requests will
                              and Remove have won. >> should be << overlapping                                               It's not about WINNING. Changed to
IBM-190         E                            requests won. >>.                                                               "take precedence".                        A      Done.
                          173 6.4.5.3        The statement << specified in this
                              Queries        document. >> should be << specified in this
IBM-191         E                            standard >>.                                                                    As suggested.                             A      Done.
                              first sentence "at the same time" is a misplaced modifier   Change to "may manage the Zone     Change to "multiple management
                                                                                          Set Database at the same time,     applications may manage, at the same
McDATA-64       E         173                                                             with unpredictable results."       time, the Zone Set Database"              A      Done.
                          174 6.4.5.4 Basic The statement << The following CT requests
                              Zoning         are defined to manage >> should be << See
                              Management table 245 for the CT requests defined to
IBM-192         E             Commands manage >>.                                                                            As suggested.                             A      Done.
                              Table 245      Why are brackets around the attributes of    Remove the brackets.
McDATA-69       E         174                GZC and GEST?                                                                   I don't know. Remove as suggested.        A      Done.
                              6.4.6.1        "Query requests (read access to the Zoning rewrite as "Query requests (read
                                             Database) do not require to be issued inside access to the Zoning Database)
                                             a GS session," is poor grammar               may be issued outside a GS
Brocade-042     E         175                                                             session,"                          Change to "are not required".             A      Done.




                                                                                     Page 69 of 91
                                                                         FC-GS-4 Revision 7.6 Comments
                                                                                   09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                              Problem Description                       Suggested solution                         Response                   Status     Edit Status
             /Edito Page    figure locator
               rial
                        175 6.4.6.1        The statement << In the context of
                            Overview       Enhanced Zoning Management, a
                                           management action (write access to the
                                           Zoning Database) to the Zone Server shall
                                           occur only inside a GS session. This rule
                                           apply to both the Zone Set Database and
                                           the Active Zone Set. A GS session is
                                           delimited by the CT requests Server Session
                                           Begin (SSB) and Server Session End (SSE),
                                           directed to the Management Service and
                                           with GS_Subtype specifying the Zone
                                           Server. Query requests (read access to the
                                           Zoning Database) do not require to be
                                           issued inside a GS session, although the
                                           information which they report can be
                                           guaranteed to be consistent only inside a
                                           GS session. >> Should be (I think) <<With
                                           Enhanced Zoning Management, a
                                           management action (i.e., write access to the
                                           Zoning Database) to the Zone Server shall
                                           occur only inside a GS session. This rule
                                           applies to both the Zone Set Database and
                                           the Active Zone Set. A GS session is
                                           delimited by the CT requests Server Session
                                           Begin (SSB) and Server Session End (SSE),
                                           directed to the Management Service with a
                                           GS_Subtype specifying the Zone Server.
IBM-193         E                          Query requests (i.e., read access to the                                          Added "i.e.," to first perens statement.     A      Done.
                            6.4.6.1        Second sentence are "This rule apply"
                                           Zoning Database) saysnot required to be         Change to "This rule applies".
McDATA-70       E       175                incorrectly.                                                                        As suggested.                              A      Done.
                            6.4.6.1        Second paragraph says "is associated with       Change to "is associated with a
McDATA-71       E       175                a lock of the fabric" incorrectly.              lock on the fabric-".               As suggested.                              A      Done.
McDATA-72       E       175 6.4.6.1        "This rule apply" is incorrect.                 Change to "This rule applies".      Already handled by McDATA-70.              A      Done.
                            6.4.6.1        "Query requests (read access to the Zoning      Change to "To ensure that Zoning
                                           Database) do not require to be issued inside    Database information is reported
                                           a GS session, although the information          consistently, Query requests to the
                                           which they report can be guaranteed to be       Fabric Zone Server should be
                                           consistent only inside a GS session." is        issued inside a GS session."        As suggested, but change "GS session"
McDATA-73       E       175                poorly worded.                                                                      to "Zoning session".                       A      Done.
                            6.4.6.1        "The GS session in Enhanced Zoning is           Change to "The GS session in
                                           associated with a lock of the Fabric (see FC-   Enhanced Zoning results in a lock
                                           SW-3)." is worded poorly.                       of the Fabric (see FC-SW-3)."
McDATA-74       E       175                                                                                                    Already fixed by McDATA-71.                R




                                                                                      Page 70 of 91
                                                                             FC-GS-4 Revision 7.6 Comments
                                                                                        09/23/03 (03-083vA)


              Techn
               ical Physical Section/table/
 Company-#                                                Problem Description                           Suggested solution                              Response              Status     Edit Status
              /Edito Page    figure locator
                rial
                             6.4.6.2.1,     First sentence not clear.                           Change wording to" this allows a Change to "This allows Zoning
                             paragraph 5                                                        zoning configuration to be defined configuration to be defined in where the
Brocade-008      E       176                                                                    in which…"                         enforcement".                                A      Done.
                             6.4.6.2.1      Third para is confusing. Is it trying to say that   Clarify
                                            if an Fport has enforced Zone in an Hard
                                            manner, that all the zones that it is in should
                                            be enforced in hard manner? Else what?                                                                                                     ??? Promoted to
Brocade-021      E       176                                                                                                                                                           technical.
                             6.4.6.2.1      "In case of an activation failure, the CT           rewrite as "In case of an activation
                                            reject shall return the reason code “Hard           failure, the CT reject shall return
                                            Enforcement Failed”, encoding in the reason         the reason code “Hard
                                            code explanation field the Domain_ID of one         Enforcement Failed”, with the
                                            of the Switches which failed the activation."       Domain_ID of one of the Switches
                                            is ambiguous - what does the worde                  which failed the activation in the
                                            "encoding" mean here?                               reason code explanation field."
Brocade-043      E       176                                                                                                           As suggested.                            A      Done.
                             6.4.6.2.1 last "Fabrics may be composed by Switches                rewrite as "Fabrics may be
Brocade-045      E       176 paragraph      that…" poor grammar                                 composed of Switches that…"            As suggested.                            A      Done.
                         176 6.4.6.2.1      The statement << is not specified, >> should
IBM-194          E           Hard Zoning be << is not set >>.                                                                          It is correct as written.                R
                         176 6.4.6.2.1      The statement << If the implementation is
                             Hard Zoning able to enforce the Zoning configuration on
                                            a frame-by-frame basis and has enough
                                            resources, it may do that.>> should be <<
                                            An implementation may enforce the Zoning
                                            configuration on a frame-by- frame basis. >>
IBM-195          E                                                                                                                     As suggested.                            A      Done.
                         176 6.4.6.2.1      The statement << attribute is specified, >>
IBM-196          E           Hard Zoning should be << attribute is set, >>                                                             It is correct as written.                R
                         176 6.4.6.2.1      The statement << If an implementation is
                             Hard Zoning not capable of doing it, or has not enough
                                            resources, the activation of the Zone
                                            configuration shall fail. >> should be << If an
                                            implementation is not capable of enforcing
                                            the Zone configuration the activation of the
                                            Zone configuration shall fail. >>
IBM-197          E                                                                                                                     As suggested.                            A      Done.
                         176 6.4.6.2.1      The statement << If when they connect, the
                             Hard Zoning Fabric has not enough resources to >>
                                            should be << When an Nx_Port connects if
                                            the Fabric does not have enough resources
IBM-199          E                          to >>.                                                                                     As suggested.                            A      Done.




                                                                                           Page 71 of 91
                                                                             FC-GS-4 Revision 7.6 Comments
                                                                                         09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                              Problem Description                          Suggested solution                       Response        Status     Edit Status
             /Edito Page    figure locator
               rial
                        176 6.4.6.2.1      The statement << This allow to define a
                            Hard Zoning Zoning configuration >> should be << This
                                           allows the the definition of a Zoning
IBM-200         E                          configuration >>.                                                                    Fixed by other comment.         R
                        176 6.4.6.2.1      The statement <<may be composed by
                            Hard Zoning Switches that >> should be << may be
IBM-201         E                          composed for Switches that >>.                                                       Fixed by other comment.         R
                            6.4.6.2        We need an explanation of soft Zoning.         Add a new 6.4.6.2.1 entitled Soft
                                                                                          Zoning. Add text: Soft Zoning, or
                                                                                          Name Server Zoning, uses the
                                                                                          Name Server to limit the visibility
                                                                                          of Nx_Ports in the Fabric. When
                                                                                          an Nx_Port queries the Name
                                                                                          Server, the Name Server responds
                                                                                          with the Nx_Ports that are in a
                                                                                          common zone with the querying
                                                                                          Nx_Port. The Fabric may not deny
                                                                                          traffic between Nx_Ports in a Soft                                           ??? Promoted to
McDATA-113     E         176                                                              Zone."                                                                       technical.
                               6.4.6.2.1      Last sentence of first paragraph says "name Add "(i.e., soft zoning)"
                                              server visibility." and could be clearer.
McDATA-76      E         176                                                                                                      As suggested.                 A      Done.
                               6.4.6.2.1, first The sentence "If the implemenation is able   Change to: "If the implemenation
                               paragraph        to enforce the Zoning configuration on a     is able to enforce the Zoning
                                                frame-by-frame basis and has enough          configuration on a frame-by-frame
                                                resources, it may do that." is poorly worded.basis, it may do so if it has enough
McDATA-77      E         176                                                                 resources.".                         Changed by other comment.     R
                               6.4.6.2.1,     This paragraph has poor wording. Why are Delete this paragraph and say that
                               fourth         we capturing these implementation details      "If the Fabric cannot support a
                               paragraph      as to why it fails if it isn't being reported? Zone Set, then the activation of
                                              We should either give reasons why it has       that Zone Set should fail. The
                                              failed or not go into the specifics in the     Fabric shall not allow changes to
                                              standard.                                      the Fabric that compromise the                                            ??? Promoted to
McDATA-78      E         176                                                                 Zone Set."                                                                technical




                                                                                            Page 72 of 91
                                                                            FC-GS-4 Revision 7.6 Comments
                                                                                          09/23/03 (03-083vA)


              Techn
               ical Physical Section/table/
 Company-#                                               Problem Description                          Suggested solution                       Response                    Status     Edit Status
              /Edito Page    figure locator
                rial
                             6.4.6.2.1,     The second paragraph is poorly worded and         Change to: "When the Hard
                             second         should be clearer. The Hard Zoning                Zoning attribute is specified, the
                             paragraph      Attribute should be specified in the first        Zone configuration shall be
                                            sentence. I have underlined the changed           enforced on a frame-by-frame
                                            text.                                             basis.
                                                                                              If an implementation is not
                                                                                              capable of enforcing hard zoning,
                                                                                              or does not have enough
                                                                                              resources, the activation of the
                                                                                              Zone configuration shall fail. In
                                                                                              case of an activation failure, the
                                                                                              CT reject shall return the reason
                                                                                              code “Hard Enforcement Failed”,
                                                                                              encoding in the reason code
                                                                                              explanation field the Domain_ID of
                                                                                              one or more of the Switches which
McDATA-79       E         176                                                                 failed the activation.".            Changed by other comment.                  R
                                6.4.6.3 last   "...command is failed with the appropriate     "...command is failed with the
                                paragraph      reason code explanation." should be            appropriate reason code and
Brocade-048     E         177                                                                 reason code explanation."           As suggestedf.                             A      Done.
                                6.4.6.5 last   remove extra in from "...based on              rewrite as "...based on information
                                paragraph      information in maintained in the local…"       maintained in the local…"
Brocade-049     E         177                                                                                                     As suggested.                              A      Done.
                          177 6.4.6.5      The statement << objects cannot be
                              Management   reconciled >> should be << objects are not
IBM-202         E             Rules        reconciled >>.                                                                      As suggested.                                 A      Done.
                              Table 247    This table should be consistent with table   Make consistent with table 245
                                           245 and include all portions of the request
                                           attributes. E.g., CZS has "Number of
                                           Zones" in it but that is not present in this                                        Editor will accept a detailed proposal to
Brocade-050     E         178              table.                                                                              make such changes.                            O      ???
                          178   6.4.6.6    The statement << The following CT requests
                                Session    are defined to manage >> should be << See
                                Commands table 246 for the CT requests defined to
IBM-203         E                          manage >>.                                                                          As suggested.                                 A      Done.
                          178   6.4.6.7    The statement << The following CT requests
                                Enhanced   are defined to manage >> should be << See
                                Zoning     table 247 for the CT requests defined to
                                Management manage >>.
IBM-204         E               Commands                                                                                       As suggested.                                 A      Done.
Brocade-051     E         181   6.4.7.1.1  State that the length is in bytes                                                   Added "Bytes".                                A      Done.
                          181   6.4.7.1.2  The term << actually >> should be deleted.                                          As suggested, also changed bulleted list
IBM-205         E               Name Value                                                                                     to (a, b, c) type list.                       A      Done.




                                                                                            Page 73 of 91
                                                                             FC-GS-4 Revision 7.6 Comments
                                                                                         09/23/03 (03-083vA)


              Techn
               ical Physical Section/table/
 Company-#                                                 Problem Description                         Suggested solution                             Response                    Status     Edit Status
              /Edito Page    figure locator
                rial
                         186 6.4.7.3.1        The statement << as defined in the following
                             Zone Set         clauses. >> should be deleted or the
                             Database         reference fixed to point to specific
IBM-206          E                            subclauses.                                                                             Delete the entire sentence.                   A      Done.
                         186 6.4.7.3.2        What does the statement << any reference
                             Active Zone      eventually<CRLF>present in a Zone Set or
                             Set              >> mean? I think the term << eventually >>
IBM-207          E                            should be deleted.                                                                      Remove "eventually".                          A      Done.
                         188 Figure 14        What happened to Figure 14? It's missing
Editor-001       E                            from the Frame Maker source.                                                                                                          O      ???
                         189 6.4.7.3.3        The statement << attributes described below
                             Zone Set         >> should be << attributes described in this
IBM-208          E           Object           subclause >>.                                                                           As suggested.                                 A      Done.
                         189 6.4.7.3.3        The statement << (Zone Set Member Type
                             Zone Set         04) >> should be << (i.e., Zone Set Member
IBM-210          E           Object           Type 04h)                                                                               As suggested.                                 A      Done.
                         189 6.4.7.3.3        The statement << (Zone Set Member Type
                             Zone Set         02h) >> should be << (i.e., Zone Set
IBM-211          E           Object           Member Type 02h) >>                                                                     As suggested.                                 A      Done.
                             6.4.7.3.3-8      There should be a table for the Object            Add table summarizing all of the
                                              Identifier that lists all of the current options. Object Identifiers and reference it
                                              The explanation of the Object Identifier is       under each Object table.
                                              probably needed after each table describing
                                              the different Zoning Objects.
McDATA-88       E         189                                                                                                         See 03-186v1.                                 A
                          191 6.4.7.3.5.2     The statement << described below >>
                              Zone Object     should be << described in this subclause >>.
                              in the Active
IBM-213         E             Zone Set                                                                                               As suggested.                                  A      Done.
Andiamo-45      E         192 Note            The note is not numbered                         Number the note                       It is numbered.                                A      Done.
                              6.4.7.3.8       "The format of the Zone Attribute object is      rewrite as "The format of the Zone
                                              depicted in table 407 and                        Attribute object is depicted in table
                                              table 266." should refer to Table 265 not 407    265 and                               Fixed first refence and moved second
Brocade-052     E         194                                                                  table 266."                           reference into table 265 where it is used.     A      Done.
                              6.4.7.3.8       This should state that for Hard Typa nad
                              "zone           Broadcast Type there is no Zone Attribute
                              attribute       Value                                                                                   I'm not sure what we are adding nor
Brocade-053     E         196 value"                                                                                                  where we are adding it.                       O      ???
                              Table 272       Label this table "Enhanced Zoning Reason
Brocade-054     E         198                 Code Explanations"                                                                      As suggested.                                 A      Done.
McDATA-91       E         198 Table 272       Table cells should be left justified.            Left justify them.                     As suggested.                                 A      Done.
                              6.4.9.1.1       For consistency, Switch Node Name should         Change switch node name to
Brocade-018     E         199 table 275       be changed to Switch_Name                        switch_name                                                                          O
                              6.4.9.1.1,      See Brocade-012                                  See Brocade-012
Brocade-013     E         200 table 276                                                                                               See QLogic-025.                               O



                                                                                            Page 74 of 91
                                                                             FC-GS-4 Revision 7.6 Comments
                                                                                        09/23/03 (03-083vA)


              Techn
               ical Physical Section/table/
 Company-#                                             Problem Description                              Suggested solution                               Response                     Status     Edit Status
              /Edito Page    figure locator
                rial
                             Table 276 bit default zone - This term is not defined              change to "Default Zoning Setting.
                             position 3     anywhere in the standard.                           When this bit is one the Fabric
                                                                                                denies traffic between all devices
                                                                                                that are not a member of any zone
                                                                                                in the active zoneset. When this
                                                                                                bit is zero the Fabric permits traffic
                                                                                                between all devices that are not a
                                                                                                member of any zone in the active
                                                                                                zoneset." See Brocade-012
Brocade-031     E         200                                                                                                            See QLogic-025.                                R
                                Table 276 bit Remove extra "is" from "...if its Zoning          rewrite as "if its Zoning Database       Cans are bad. So, rewrite as: "if its
                                position 2    Database is can merge with the Fabric‟s           can merge with the Fabric‟s              Zoning Database is able to merge with
Brocade-055     E         200                 Zoning Database."                                 Zoning Database."                        the Fabric‟s Zoning Database."                 A      Done.
IBM-217         E         200   Table 276     Widen this table out so it is not so long.                                                 As suggested.                                  A      Done.
                          200   table 276     Bit position 0 change << work in >> to <<
IBM-218         E                             support >>.                                                                                As suggested.                                  A      Done.
                          200   table 276     All the << bit is zero >> and << bit is one >>
                                              statements should be << bit is set to zero >>
IBM-219         E                             and << bit is set to one >>.                                                               As suggested.                                  A      Done.
                          200   table 276     The statement <<Fabric is working
                                              in<CRLF>Enhanced >> should be << Fabric                                                    Current table text consistent with rest of
IBM-220         E                             has enabled the Enhanced >>                                                                clause.                                        R
                          200   table 276     The statement << Fabric is working in Basic
                                              Zoning >> should be << Fabric has enabled                                                  Current table text consistent with rest of
IBM-221         E                             the Basic Zoning >>.                                                                       clause.                                        R
                          200   table 276     The statement << Fabric is working in Allow
                                              mode, >> should be << Fabric has enabled                                                   Current table text consistent with rest of
IBM-222         E                             the Allow mode >>.                                                                         clause.                                        R
McDATA-84       E         200   6.4.6.2.2.4   "to the all the devices" is incorrect.          Change to "to all the devices".            Changed by other comments.                     R
                                Table 276     Bit position 3 says "the Fabric permit traffic" Change to "the Fabric permits
McDATA-92       E         200                                                                 traffic"                            As suggested.                                         A      Done.
                                Table 276      Most bit descriptions should not say that 1 is Remove the description of 0 for all
                                               and 0 isn't. This just makes it wordy.         cases when it just means the        This is common language for a
                                                                                              opposite. Some times it is helpful. specification. It's better to be wordy than
McDATA-93       E         200                                                                                                     misunderstood.                                        R
                              6.4.9.1.1,       See Brocade-012                                See Brocade-012
Brocade-014     E         201 table 277                                                                                           See QLogic-025.                                       O




                                                                                           Page 75 of 91
                                                                            FC-GS-4 Revision 7.6 Comments
                                                                                      09/23/03 (03-083vA)


              Techn
               ical Physical Section/table/
 Company-#                                             Problem Description                          Suggested solution                              Response                 Status     Edit Status
              /Edito Page    figure locator
                rial
                             Table 277 bit default zone - This term is not defined          change to "Default Zoning Setting.
                             position 3     anywhere in the standard.                       When this bit is one the Fabric
                                                                                            denies traffic between all devices
                                                                                            that are not a member of any zone
                                                                                            in the active zoneset. When this
                                                                                            bit is zero the Fabric permits traffic
                                                                                            between all devices that are not a
                                                                                            member of any zone in the active
                                                                                            zoneset." See Brocade-012
Brocade-032     E         201                                                                                                        See QLogic-025.                           O
                          201 Table 277       All the comments on table 276 apply to table                                           All done except for IBM-220, IBM-221,
IBM-223         E                             277.                                                                                   and IBM-222 type comments.                A      Done.
                                6.4.6.7       First sentence is poorly worded.             Change to "The following CT
                                                                                           requests manage the Zoning
                                                                                           Database in Enhanced Zoning
McDATA-87       E         201                                                              mode.                                     "The following" is even worse.            R
                                6.4.9.1.2     "...is not capable to work in Enhanced…" fix rewrite as "...is not capable of
Brocade-057     E         202                 grammar                                      working in Enhanced…"                     As suggesed.                              A      Done.
                          202   6.4.9.1.2 Set The statement << set the Fabric to work in
                                Fabric        Enhanced >> should be << enable the
                                Enhanced      Enhanced mode within the Fabric. >>
                                Zoning
                                Support
IBM-224         E               (SFEZ)                                                                                               Current language is OK.                   R
                          202   6.4.9.1.2 Set The statement << Fabric is not capable to
                                Fabric        work in Enhanced Zoning, >> should be <<
                                Enhanced      Fabric does not support Enhanced Zoning,
                                Zoning        >>
                                Support
IBM-225         E               (SFEZ)                                                                                               Current language is OK.                   R
                          202   6.4.9.1.2 Set The statement << When the Fabric is
                                Fabric        working in Enhanced mode >> should be <<
                                Enhanced      If the Fabric has the Enhanced mode
                                Zoning        enabled >>
                                Support
IBM-226         E               (SFEZ)                                                                                               Current language is OK.                   R
                          202   6.4.9.1.2 Set The statement << When the Fabric is
                                Fabric        working in enhanced<CRLF>mode >>
                                Enhanced      should be << If the Fabric has the Enhanced
                                Zoning        mode enabled >>
                                Support
IBM-227         E               (SFEZ)                                                                                               Current language is OK.                   R
                                6.4.9.1.2     "If the Fabric is not capable to work in" is Change to "If the Fabric is not able
                                              poorly worded.                               to operat in Enhanced Zoning
McDATA-96       E         202                                                              mode,"                                    See Brocade-057.                          A      Done.



                                                                                          Page 76 of 91
                                                                           FC-GS-4 Revision 7.6 Comments
                                                                                     09/23/03 (03-083vA)


              Techn
               ical Physical Section/table/
 Company-#                                                 Problem Description                       Suggested solution                             Response               Status     Edit Status
              /Edito Page     figure locator
                rial
McDATA-97        E       202 6.4.9.1.2       second paragraph says "is no possible"          change to "is not possible".           As suggested.                            A      Done.
                             6.4.9.1.2,      See Brocade-012                                 See Brocade-012
Brocade-015      E       203 table 279                                                                                              See QLogic-025.                          O
                         205 table 285       The statement << Database; i.e., the only
                                             way to activate<CRLF>a Zone Set is via the
                                             AZSD request<CRLF>(see 6.4.9.3.10). >>
                                             should be << Database (i.e., the only way to
                                             activate<CRLF>a Zone Set is via the AZSD
                                             request<CRLF>(see 6.4.9.3.10)). >>
IBM-228          E                                                                                                                  As suggested.                            A      Done.
                             Table 290       Use of the term attribute here is confusing     "Number of Zoneset entries" -
                                             with the attributes defined in the enhanced     these are not attributes - remove
                                             zoning definitions. "Number of Zone Set         attributes from this entire section
Brocade-059      E       207                 attribute entries (n)" should be                                                                                                O      Ponder.
                             Table 292       Use of the term attribute here is confusing     "Number of Zone entries" - these
                                             with the attributes defined in the enhanced     are not attributes - remove
                                             zoning definitions. "Number of Zone attribute   "attributes" from the entire section
Brocade-060      E       208                 entries (n)" should be                                                                                                          O      Ponder.
                             Table 294       Use of the term attribute here is confusing     "Number of Zone Member entries" -
                                             with the attributes defined in the enhanced     these are not attributes - remove
                                             zoning definitions. "Number of Zone             "attributes" from the entire section
Brocade-061      E       209                 Member attribute entries (n)" should be                                                                                         O      Ponder.
                         211 Table 296       Globally<CRLF>When a table extends
                                             across multiple pages use the << (x of x) >>                                           Sounds cool, but how do you make
IBM-229          E                           format in the header.                                                                  framemaker do this automatically?        O      ???
                         213 6.4.9.3.8 Get The statement << Session Begin/End will
                             Activation      ensure that the GAR >> should be <<
                             Results         Session Begin/End ensures that the GAR >>
IBM-230          E           (GAR)                                                                                                  As suggested.                            A      Done.
                             6.4.9.3.8 Last Where is this specified in FC-SW-3               Give a more specific location
                             Paragraph                                                                                              Clause specific references to other
Brocade-062      E       214                                                                                                        standards cannot be done.                R
                         214 6.4.9.3.8 Get The statement << For each switch, the
                             Activation      Interconnect Element name, domain id and
                             Results         reason code are returned. >> is not a
                             (GAR)           complete sentence. This needs to be fixed.                                             It looks complete to me. Also, vauge
                                             Also the one sentence paragraph above this                                             uneasy feelings about odd paragraphs
                                             one reads odd but I cannot figure out why.                                             don't consitute a comment that I can
IBM-231          E                                                                                                                  respond to.                              R
Andiamo-49       E       224 6.4.9.4.1       extra space before the dot                      remove the space.
                                                                                                                                                                                    ??? This is a
                                                                                                                                                                                    problem with the
                                                                                                                                                                                    template. Care
                                                                                                                                                                                    must be taken
                                                                                                                                                                             O      when changing.



                                                                                        Page 77 of 91
                                                                             FC-GS-4 Revision 7.6 Comments
                                                                                          09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                                 Problem Description                           Suggested solution                       Response                    Status     Edit Status
             /Edito Page     figure locator
               rial
                        224 6.4.9.4.2 Get     The statement << Zone for which the Zone
                            Zone              Attribute Object Name is sought. >> should
                            Attribute         be << the requested Zone Attribute Object
                            Object Name       Name >>
                            (GZA)
IBM-232         E           Operation                                                                                             Changes the meaning incorrectly.              R
Andiamo-50      E       225 Table 322         Zone Attribute Block size expressed as "x"        update
                                              instead than see 6.4.7.3.8                                                          As suggested.                                 A      Done.
Andiamo-51     E         231 Table 337        See andiamo-50                                                                      OK, I see it.                                 A      Done.
                             Last             Is this the proper way to say that the            This same wording will apply to   Agreed. Remove this statement since
                             sentence         payload is null? It will still have the CT_IU     many more commands in             there is a table which shows the accept              ??? Done. But,
                                              preamble.                                         Enhanced zoning.                  payload. Apply to 6.4.9.4.16, 6.4.9.4.17,            since this
                                                                                                                                  6.4.9.4.18, 6.4.9.4.19, 6.4.9.4.20,                  change resulted
                                                                                                                                  6.4.9.4.21, 6.4.9.4.22, 6.4.9.4.23,                  in quite a few
                                                                                                                                  6.4.9.4.24, 6.4.9.4.25, 6.4.9.4.4,                   changes, WG
                                                                                                                                  6.4.9.4.7, 6.4.9.4.10, 6.4.9.4.11,                   should review to
                                                                                                                                  6.4.9.4.12, 6.4.9.4.13, 6.4.9.4.14,                  make sure they
McDATA-105     E         235                                                                                                      6.4.9.4.15,                                   A      concur.
Andiamo-53     E         248 Table 371       The Zone Set Name length is expressed as update
                                             "8 to 68" instead than with a reference to
                                             clause 6.4.7.1                                                                       Changed to refence.                           A      Done.
                         250   6.5.2.3       The statement << specified in this
                               Registration document. >> should be << specified in this
IBM-233        E                             standard. >>                                                                         As suggested.                                 A      Done.
                         250   6.5.2.4       The statement << specified in this
                               Queries       document. >> should be << specified in this
IBM-234        E                             standard. >>                                                                         As suggested.                                 A      Done.
                         250   6.5.3.1       The statement << raw counters that can be
                               Performance turned on >> should be << counter that may
                               Instrumentati be turned on >>.
IBM-235        E               on Objects                                                                                         As suggested.                                 A      Done.
                         254   Table 378     The statement << ON (Probe is turned ON,
                                             i.e. data collection is<CRLF>enabled) >>
                                             should be << Probe is turned ON (i.e., data
                                             collection is enabled) >>
IBM-237        E                                                                                                                  As suggested (with minor modification).       A      Done.
                         254 Table 378        The statement << OFF (Probe is turned
                                              OFF, i.e. data collection is disabled) >>
                                              should be << Probe is turned OFF (i.e.,
IBM-238        E                              data collection is disabled) >>                                                     As suggested (with minor modification).       A      Done.




                                                                                              Page 78 of 91
                                                                          FC-GS-4 Revision 7.6 Comments
                                                                                    09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                                Problem Description                      Suggested solution                   Response                   Status     Edit Status
             /Edito Page     figure locator
               rial
                        254 Table 378       The statement << NOT SUPPORTED
                                            (Enabling and disabling of<CRLF>data
                                            collection is not supported by this probe) >>
                                            should be << NOT SUPPORTED (i.e.,
                                            Enabling and disabling of<CRLF>data
                                            collection is not supported by this probe) >>
IBM-239         E                                                                                                       As suggested.                                A      Done.
                        256 6.5.3.3         The statement <<Returns 0x8000 if the >>
                            Performance should be << Returns 8000h if the >>.
                            Metrics
IBM-241         E           Object                                                                                      As suggested.                                A      Done.
                        256 Table 383       The statement << Address Format = 0x00
                                            >> should be << Address Format (00h) >>
IBM-242         E                                                                                                       As suggested.                                A      Done.
                        257 Table 384       The statement << Address Format = 0x01
                                            >> should be << Address Format (01h) >>
IBM-243         E                                                                                                       As suggested.                                A      Done.
                        257 Table 385       The statement << Address Format = 0x02
                                            >> should be << Address Format (02h) >>
IBM-244         E                                                                                                       As suggested.                                A      Done.
                        259 6.5.5.2 Query The statement << shall specify the Port
                            - Get           Identifiers<CRLF>for which the values are
                            Performance sought, >> should be << shall return the
                            Probes          requested Port Identifiers >>
IBM-247         E           (GPMP)                                                                                      That changes the meaning significantly.      R
                        262 6.5.5.6         The statement << is shown in see 397, and
                            Register        the reply payload is shown in see 398. >>
                            Performance should be << is shown in table 397, and the
                            Metrics         reply payload is shown in table 398. >>
IBM-248         E           (RPMM)                                                                                      As suggested.                                A      Done.
                        262 The             payload is shown in see 399, and the reply
                            statement << payload is shown in see 400. >> should be
                            6.5.5.7 De-     << 6.5.5.7 De-Register Performance Metrics
                            Register        (DPMM) payload is shown in table 399, and
                            Performance the reply payload is shown in table 400. >>
                            Metrics
IBM-249         E           (DPMM)                                                                                      As suggested.                                A      Done.
Andiamo-55      E       265             6.7 This section uses capital letters for "SHALL", discuss
                                            "MAY", and the words indicating
                                            requirements. It is much more readable.
                                            Could we do the same through the entire
                                            document?                                                                   No. They should be fixed in this cluase.     R
                        265 6.7.1           The statement << mechanism which
                            Overview        provides >> should be << mechanism that
IBM-250         E                           provides >>                                                                 As suggested.                                A      Done.



                                                                                       Page 79 of 91
                                                                        FC-GS-4 Revision 7.6 Comments
                                                                                  09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                               Problem Description                     Suggested solution                         Response                  Status     Edit Status
             /Edito Page    figure locator
               rial
                        265 6.7.1           The statement << Initially, the FDMI will
                            Overview        address only HBA type devices.>> should
                                            be << In this standard FDMI only applies to
IBM-251         E                           HBA type devices. >>.                                                           As suggested.                               A      Done.
                            6.7.4.2         figure figure 16 is wrong.                    remove one figure so we can
McDATA-109      E       265                                                               figure it out.                    As suggested.                               A      Done.
McDATA-114      E       265 6.7.2           Change "from" to by" in first sentence.       Change grammar.                   Suggestion seems like bad grammar.          R
                                        6.7 The acronym HBA needs to be added to the      Add "HBA" to definition of Host
McDATA-116      E       265                 definition section.                           Bus Adaptor.                                                                         Ponder.
                        267 6.7.4.3.3.1     The statement << Note that >> should be
IBM-252         E           Overview        deleted.                                                                        As suggested.                               A      Done.
                        267 6.7.4.3.3.1     The statement << specified in
                            Overview        this<CRLF>document. >> should be <<
IBM-253         E                           specified in this standard >>                                                   As suggested.                               A      Done.
                        268 6.7.4.3.3.1     The statement << registration requests will
                            Overview        have won. >> should be << registration                                          It's not about winning. Change to "take
IBM-254         E                           requests won. >>.                                                               precendence."                               A      Done.
                        268 6.7.4.3.3.2     The statement << Attribute Block cannot be
                            Registration registered >> should be << Attribute Block
IBM-256         E           Rules           are not able to be registered >>                                                As suggested.                               A      Done.
                        268 6.7.4.3.3.2     The statement << It is acceptable for
                            Registration attributes to be >> should be << Attributes
IBM-257         E           Rules           may be >>.                                                                      As suggested.                               A      Done.
                        268 6.7.4.3.4       The statement << in this document. >>
IBM-258         E           Queries         should be << in this standard. >>.                                              As suggested.                               A      Done.
                        269 6.7.4.4.1       The statement << following sub clauses.>>
                            Overview        is not accurate enough. It should list the
                                            numbers of the subclauses. Also its <<
                                            subclause >> not << sub clause >>
IBM-259         E                                                                                                                                                       O      Ponder.
                        269 6.7.4.4.2.1     The statement << following sub clauses.>>
                            Overview        is not accurate enough. It should list the
                                            numbers of the subclauses. Also its <<
                                            subclause >> not << sub clause >>
IBM-260         E                                                                                                                                                       O      Ponder.
                        269 6.7.4.4.2       The term << Printable ASCII >> should be
                            Host Bus        << printable ASCII >>.
                            Adapter
IBM-261         E           Attributes                                                                                      As suggested.                               A      Done.
                        269 6.7.4.4.x       There are a bunch of << MAY >>, <<
                            Host Bus        SHOULD >>, << SHOULD NOT >>, <<
                            Adapter         TYPE >>. and << SHALL >> that are all
                            Attributes      caps. These all need to be made into normal                                     All except "FC4 TYPE" which may be the
IBM-262         E                           text.                                                                           way FS does it.                             O      Ponder.




                                                                                     Page 80 of 91
                                                                           FC-GS-4 Revision 7.6 Comments
                                                                                       09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                               Problem Description                       Suggested solution                       Response                 Status     Edit Status
             /Edito Page    figure locator
               rial
                            6.7.4.4.2.2      Key words are in ALL CAPS. These seems Revert to normal ANSI speak.
                            and beyond       like an IETF thing and has not place here.
McDATA-110      E       269                                                                                                 See IBM-262.                               A      Done.
                        271 6.7.4.4.2.13     The statement <<not an attribute can be
                            Maximum CT       registered with >> should be << not an
IBM-266         E           Payload          attribute is registered with >>.                                               As suggested.                              A      Done.
                        272 6.7.4.4.3.6      The statement << such as enabling a
                            Supported        configuration option<CRLF>or installing
                            FC-4 Types       firmware. >> should be << (e.g., enabling a
                                             configuration option<CRLF>or installing
IBM-268        E                             firmware). >>.                                                                 See IBM-267.
                         272 6.7.4.4.3.7     The statement << such as enabling a
                             Active FC-4     configuration option<CRLF>or installing
                             Types           firmware. >> should be << (e.g., enabling a
                                             configuration option<CRLF>or installing
IBM-270        E                             firmware). >>.                                                                 See IBM-269.
                         272 Table 403       Why are the Mask Values in decimal. It                                                                                           ??? Done, but
                                             would make more sense to show it in hex or                                                                                       WG should
IBM-271        E                             binary. This should be changed.                                                Aggreed. Values changed to hex.            A      review.
Andiamo-56     E         273 6.7.4.5         Typo in the title: sever instead than server update                            As suggested.                              A      Done.
Andiamo-57     E         273 6.7.4.5.1       The text mandates consistency, add same Add "(e.g., across power cicles)" to
                                             example, e.g. across poser cicles.           the last sentence of the first
                                                                                          paragraph.                        Sorry, I don't understand the comment.     O      ???
Andiamo-58     E         274 Tables 407,     The sizes are expressed with letters, not    update
                             410, 416,       references.
                             418, 421                                                                                                                                  O      Ponder.
                         275 6.7.4.5.4       The term << below. >> should be deleted.
                             Attribute
IBM-272        E             Entry Format                                                                                   As suggested.                              A      Done.
                         279 6.7.4.7.2       The statement << specify the HBA Identifier
                             Query - Get     which identifies the HBA for which attributes
                             HBA             are sought. .>> should be << shall return
                             Attributes      the requested HBA Identifier for the                                           Suggested wording changes meaning
IBM-273        E             (GHAT)          identified HBA.>>                                                              incorrectly.                               R
                         280 6.7.4.7.3       The statement << specify the HBA Identifier
                             Query - Get     for which the registered ports are sought.>>
                             Registered      should be << shall return the requested
                             Port List       HBA Identifier >>                                                              Suggested wording changes meaning
IBM-274        E             (GRPL)                                                                                         incorrectly.                               R
                         280 6.7.4.7.4       The statement << specify the name
                             Query - Get     identifying the Port for
                             Port            which<CRLF>attributes are sought. >>
                             Attributes      should be << shall return the requested
IBM-275        E             (GPAT)          name of the identified Port. >>.                                               Changes meaning incorrectly.               R




                                                                                         Page 81 of 91
                                                                             FC-GS-4 Revision 7.6 Comments
                                                                                        09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                                 Problem Description                           Suggested solution                          Response   Status     Edit Status
             /Edito Page     figure locator
               rial
                        285 6.7.4.7.10        The statement << Identifier which identifies
                            Deregister        >> should be << identifier that identifies >>.
                            HBA
                            Attributes
IBM-276         E           (DHAT)                                                                                                   As suggested.                A      Done.
                        286 6.7.4.7.12        The statement << Port_Name which
                            Deregister        identifies >> should be << Port_Name that
                            Port              identifies >>.
                            Attributes
IBM-277         E           (DPA)                                                                                                    As suggested.                A      Done.
                        288 7.1 Overview  The statement << indicated in Table 4.>>
                                          should be << indicated in table 4.>> The T
IBM-278        E                          is not capitalized.                                                                        As suggested.                A      Done.
                         291 7.2.5.3 TSAP The statement << Set to b\22000\220 to
                             Unicast      indicate >> should be << Set to 00b to
                             Request/Res indicate >>
                             ponse Block
IBM-280        E                                                                                                                     As suggested.                A      Done.
                         291 7.2.5.3 TSAP Delete the term << both >> in both the bits
                             Unicast      0-1 and bits 2-4 descriptions.
                             Request/Res
                             ponse Block
IBM-281        E                                                                                                                     As suggested.                A      Done.
                         291 7.2.5.3 TSAP The statement << Set to b\220001\220 to
                             Unicast      indicate >> should be << Set to 001b to
                             Request/Res indicate >>
                             ponse Block
IBM-282        E                                                                                                                     As suggested.                A      Done.
                         291 7.2.5.3 TSAP The statement << Set to b\220011\220 to
                             Unicast      indicate >> should be << Set to 011b to
                             Request/Res indicate >>
                             ponse Block
IBM-283        E                                                                                                                     As suggested.                A      Done.
                         291 7.2.5.3 TSAP The statement << Set to b\220100\220 to
                             Unicast      indicate >> should be << Set to 100b to
                             Request/Res indicate >>
                             ponse Block
IBM-284        E                                                                                                                     As suggested.                A      Done.
QLogic-031     E         291 7.2.5.3, Flags This description would be more appropiate            Change bit definitions to a table
                                            as a table.                                          format.                             As suggested.                A      Done.
                         292 7.2.5.3 TSAP The statement << set to
                             Unicast        hex\22000000000\220 >> should be << set
                             Request/Res to 0000 0000h >>
                             ponse Block
IBM-285        E                                                                                                                     As suggested.                A      Done.



                                                                                               Page 82 of 91
                                                                           FC-GS-4 Revision 7.6 Comments
                                                                                      09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                               Problem Description                      Suggested solution                   Response           Status     Edit Status
             /Edito Page    figure locator
               rial
                        292 7.2.5.3 TSAP     The statement << Digest.For >> is missing a
                            Unicast          space.
                            Request/Res
                            ponse Block
IBM-287         E                                                                                                      As suggested.                        A      Done.
                        293 7.2.5.4.1       The statement << number of seconds that
                            Timestamp       can be represented is >> should be <<
IBM-288         E           Format          number of seconds represented is >>                                        As suggested.                        A      Done.
                        293 7.2.5.4.1       The statement << it is acceptable to pad the
                            Timestamp       non-significant low order bits with zeros.>>
                            Format          should be << the low order bits may be
IBM-290         E                           padded with zeros. >>                                                      As suggested.                        A      Done.
                        293 7.2.5.5 Basic   The statement <<appropriate values
                            Operation       specified above. >> should be <<
IBM-291         E                           appropriate values (see x.xx.x.). >>                                                                            O      Ponder.
                        293 7.2.5.5 Basic   The statement in note 59 << the value can
                            Operation       be used as an added >> should be << the
IBM-292         E                           value may be used as an added >>                                           As suggested.                        A      Done.
                        294 8.1 Overview    The statement << The following sections
                                            describe >> should be << This clause
IBM-293        E                            describes >>.                                                              As suggested.                        A      Done.
                         294 8.1 Overview In the statement << indicated in Table 4. >>
IBM-294        E                            table should be capitalized.                                               Table should NOT be capitalized.     A      Done.
                         297 8.2.2.3.2 Join The statement << Is capable of supporting
                             alias group    >> should be << supports >> in two places.
IBM-295        E                                                                                                       As suggested.                        A      Done.
                         297 8.2.2.3.2 Join The statement << If the N_Port cannot
                             alias group    perform >> should be << If the N_Port is not
IBM-296        E                            able to perform >>.                                                        Change to "is unable to".            A      Done.
                         297 8.2.2.3.2 Join The bulleted list needs to be changed into
                             alias group    an a.b.c list.
IBM-297        E                                                                                                                                            O      Ponder.
                         297 8.2.2.3.2 Join The statement << Controller can assign this
                             alias group    alias >> should be << Controller may assign
IBM-299        E                            this alias >>.                                                             Change to "is able to".              A      Done.
                         297 8.2.2.3.2 Join The statement << If it cannot assign this
                             alias group    alias for >> should be << If it is not able to
IBM-300        E                            assign this alias for >>.                                                  Change to "is unable to".            A      Done.
                         297 8.2.2.3.2 Join The statement << Finally, >> should be
                             alias group    deleted.
IBM-301        E                                                                                                       As suggested.                        A      Done.
                         298 8.2.2.3.3   The statement << if the Fabric Controller
                             Remove from cannot de-assign this alias >> should be <<
                             alias group if the Fabric Controller is not able to de-
IBM-302        E                         assign this alias >>                                                          Change to "is unable to".            A      Done.



                                                                                         Page 83 of 91
                                                                           FC-GS-4 Revision 7.6 Comments
                                                                                      09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                               Problem Description                      Suggested solution                   Response    Status     Edit Status
             /Edito Page    figure locator
               rial
                        298 8.2.2.3.3        The statement << if the Fabric Controller
                            Remove from      can de-assign >> should be << If the Fabric
IBM-303         E           alias group      Control is able to de-assign >>.                                          As suggested.                 A      Done.
                        299 8.2.2.3.4        The statement << if the destination N_Port
                            Listen           can perform all of the >> should be << if the
                                             destination N_Port is able to perform all of
IBM-304        E                             the >>                                                                    As suggested.                 A      Done.
                         299 8.2.2.3.4       The statement << Is capable of supporting
                             Listen          >> should be << supports >> in two places.
IBM-305        E                                                                                                       As suggested.                 A      Done.
                         299 8.2.2.3.4       The statement << If the N_Port cannot
                             Listen          perform >> should be << If the N_Port is not
IBM-306        E                             able to perform >>.                                                       Change to "is unable to".     A      Done.
                         299 8.2.2.3.4       The bulleted list needs to be changed into
IBM-307        E             Listen          an a.b.c list.                                                                                          O      Ponder.
                         299 8.2.2.3.4       The statement << Fabric Controller can
                             Listen          assign this alias >> should be << Fabric
IBM-308        E                             Controller is able to assign this alias >>                                As suggested.                 A      Done.
                         299 8.2.2.3.4       The statement << If it cannot assign this
                             Listen          alias >> should be << If it is not able to
IBM-309        E                             assign this alias >>.                                                     Change to "is unable to".     A      Done.
                         299 8.2.2.3.4       The statement << (see 8.2.5.6, Membership,
                             Listen          and 8.2.2.3.3g). does not have valid
                                             references. Delete << membership >> and
IBM-310        E                             << g >>.
                         301 8.2.2.4 Alias   The statement << For example, the Receive
                             routing         Data Field Size for a multicast frame may be
                                             different than the<CRLF>Receive Data Field
                                             Size for a unicast frame. >> should be <<
                                             (e.g., the Receive Data Field Size for a
                                             multicast frame may be different than
                                             the<CRLF>Receive Data Field Size for a
                                             unicast frame). >>
IBM-311        E                                                                                                       As suggested.                 A      Done.
                         301 8.2.2.5.2       The statement << bits is set to binary
                             Multicast       \2171\220. >> should be << bits is set to
IBM-313        E             groups          one. >>                                                                   As suggested.                 A      Done.
                         302 8.2.3.2         The A,B,C list should be made into a table
                             Alias_Token     and the x'x' format changed to xh.<CRLF>A)
                                             x\2200\220 = Reserved<CRLF>B)
                                             x\2201\220 = Multicast Group<CRLF>C)
                                             x\2202\220 = Hunt Group<CRLF>D) Others
IBM-314        E                             = Reserved                                                                                              O      Ponder.




                                                                                         Page 84 of 91
                                                                          FC-GS-4 Revision 7.6 Comments
                                                                                     09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                                Problem Description                    Suggested solution                   Response   Status     Edit Status
             /Edito Page     figure locator
               rial
                        303 8.2.3.2         The statement << For example, a Multicast
                            Alias_Token Group can be created for all<CRLF>SCSI-
                                            FCP TYPEs and a different Multicast Group
                                            may be created for all SBCCS TYPEs. >>
                                            should be << (e.g., a Multicast Group can be
                                            created for all<CRLF>SCSI-FCP TYPEs and
                                            a different Multicast Group may be created
                                            for all SBCCS TYPEs). >>
IBM-315         E                                                                                                     As suggested.                A      Done.
                        303 8.2.3.2         The statement << The values that can be
                            Alias_Token assigned for these >> should be << The
IBM-316         E                           values that are assigned for these >>.                                    As suggested.                A      Done.
                        303 8.2.3.2         The << a) >> in the a,b,c list under
IBM-317         E           Alias_Token Alias_Class should be a << c) >>.                                             As suggested.                A      Done.
                        303 8.2.3.2         The statement << For example, an SBCCS
                            Alias_Token Multicast Group may be created for
                                            channels (TYPE =<CRLF>19h) and a
                                            different SBCCS Multicast Group may be
                                            created for control units (TYPE = 1Ah). >>
                                            should be << (e.g., an SBCCS Multicast
                                            Group may be created for channels (TYPE
                                            =<CRLF>19h) and a different SBCCS
                                            Multicast Group may be created for control
IBM-318         E                           units (TYPE = 1Ah)).                                                      As suggested.                A      Done.
                        304 8.2.3.3         All lists of hex codes and their definitions
                            Authorization should all be placed into a table.
IBM-319         E           _Control                                                                                                               O      Ponder.
                        306 table 447       There is no coding information on the values
                                            therefore they are decimal. I believe they are
                                            intended to be binary. This needs to be
IBM-320         E                           fixed.                                                                    Specify as "binary".         A      Done.
                        308 8.2.5.2 Join The statement << invalid (Reason Code
                            alias group     Explanation of 'Invalid<CRLF>Alias_Token'),
                            (JNA)           >> should be << invalid with a Reason
                                            Code Explanation of
                                            'Invalid<CRLF>Alias_Token', >>.
IBM-321         E                                                                                                     As suggested.                A      Done.
                        308 8.2.5.2 Join The statement << supported (Reason Code
                            alias group     Explanation<CRLF>of 'Unsupported
                            (JNA)           Alias_Token'). >> should be << supported
                                            with a Reason Code Explanation<CRLF>of
                                            'Unsupported Alias_Token'. >>
IBM-322         E                                                                                                     As suggested.                A      Done.




                                                                                        Page 85 of 91
                                                                            FC-GS-4 Revision 7.6 Comments
                                                                                       09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                                Problem Description                        Suggested solution                   Response   Status     Edit Status
             /Edito Page     figure locator
               rial
                        308 8.2.5.2 Join      NOTE 63 has no line space between it and
                            alias group       the next paragraph. This needs to be fixed.
IBM-323         E           (JNA)                                                                                         Fixed.                       A      Done.
                        309 8.2.5.2 Join    The statement << defines the Alias Group
                            alias group     that was just created. >> should be <<
                            (JNA)           defines the last Alias Group that was
IBM-324         E                           created. >>.                                                                  As suggested.                A      Done.
                        309 8.2.5.2 Join    The statement << That is, the high-order
                            alias group     byte of the entry shall be ignored and the
                            (JNA)           low-order 3 bytes shall<CRLF>contain the
                                            alias address identifier. >> should be <<
                                            (i.e., the high-order byte of the entry shall be
                                            ignored and the low-order 3 bytes
                                            shall<CRLF>contain the alias address
IBM-325        E                            identifier). >>                                                               Delete "That is".            A      Done.
                         309 8.2.5.2 Join The statement << an Alias_ID could not be
                             alias group    assigned >> should be << an Alias_ID is not
IBM-326        E             (JNA)          able to be assigned >>.                                                       As suggested.                A      Done.
                         311 8.2.5.4 Listen The statement << to which it wishes to
                             (LSN)          listen. >> should be << to which it is
IBM-327        E                            requesting to listen. >>.                                                     As suggested.                A      Done.
                         311 8.2.5.4 Listen The statement << that wishes to listen to all
                             (LSN)          >> should be << that is requesting to listen
IBM-328        E                            to all >>.                                                                    As suggested.                A      Done.
                         311 8.2.5.4 Listen The statement << That is, the high-order
                             (LSN)          byte of the entry shall be
                                            ignored<CRLF>and the low-order 3 bytes
                                            shall contain the N_Port address identifier.
                                            >> should be << (i.e., the high-order byte of
                                            the entry shall be ignored<CRLF>and the
                                            low-order 3 bytes shall contain the N_Port
                                            address identifier). >>
IBM-329        E                                                                                                          Remove "That is".            A      Done.
                         312 8.2.5.5 Stop The statement << the Alias_Class to which it
                             listen (SLSN) wishes to stop listening. >> should be << the
                                           Alias_Class to which it is requesting to stop
IBM-330        E                           listening. >>                                                                  As suggested.                A      Done.
                         312 8.2.5.5 Stop The statement << N_Port wishes to stop
                             listen (SLSN) listening. >> should be << N_Port requesting
IBM-331        E                           to stop listening. >>.                                                         As suggested.                A      Done.
                         313 8.2.5.5 Stop The statement << N_port that wishes to stop
                             listen (SLSN) listening<CRLF>to all traffic >> should be <<
                                           N_Port that is requesting to stop listening to
IBM-332        E                           all traffic >>.                                                                As suggested.                A      Done.




                                                                                            Page 86 of 91
                                                                          FC-GS-4 Revision 7.6 Comments
                                                                                    09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                                 Problem Description                  Suggested solution                   Response   Status     Edit Status
             /Edito Page     figure locator
               rial
                        313 8.2.5.5 Stop The statement << That is, the high-order
                            listen (SLSN) byte of the entry shall be<CRLF>ignored
                                            and the low-order 3 bytes shall contain the
                                            N_Port address identifier. >> should be <<
                                            (i.e., the high-order byte of the entry shall
                                            be<CRLF>ignored and the low-order 3 bytes
                                            shall contain the N_Port address identifier).
IBM-333         E                           >>                                                                       Remove "That is".            A      Done.
                        314 8.2.5.6 Read The a.b.c list should be a table and all the
                            alias group     << , i.e., >> should be << (i.e., ... )
                            (RAG)           >><CRLF>a) 0h = Grouped,<CRLF>b) 1h =
                                            Listening,<CRLF>c) Others =
IBM-334         E                           Not<CRLF>N_Port ID: The N_                                                                            O      Ponder.
                        314 8.2.5.6 Read The statement << Alias_Token, as
                            alias group     described above. >> needs a more accurate
                            (RAG)           reference or the << as described above. >>
IBM-335         E                           should be deleted.
                        315 9 Key           The statement << other N_Port Identifiers as
                            Distribution    well. >> should be << other N_Port
IBM-336         E           Service         Identifiers. >> .                                                        As suggested.                A      Done.
                        315 other N_Port The note << NOTE - The Key Server
                            Identifiers     defined in previous versions of this Standard
                                            has been obsoleted. >> is not numbered.
IBM-337         E                           This needs to be fixed.                                                  Fixed.                       A      Done.
                        332 C.6.2.1         The statement << (For this discussion we
                            Overview        will refer<CRLF>only to the Name Server
                                            specifically and the Management Service
                                            collectively; the IP Address Server<CRLF>is
                                            not discussed.) >> should be a note stated
                                            as << NOTE - xx This annex
                                            refers<CRLF>only to the Name Server
                                            specifically and the Management Service
                                            collectively; the IP Address Server<CRLF>is
                                            not discussed. >>.
IBM-340         E                                                                                                    As suggested.                A      Done.
                        340 D.1             The reference << (see 3.2): Zone
                            Introduction Members,<CRLF>Zones, and Zone Sets. >>
IBM-343         E                           is invalid. It should be << (see 3.2). >>                                As suggested.                A      Done.
                        340 D.1             The statement << Note that only one Zone
                            Introduction Set can be activated at a time which is
                                            referred to as<CRLF>the Active Zone Set.
                                            >> should be << Only one Zone Set is
                                            allowed to be active at a time and the Zone
                                            Set is referred to as the Active Zone Set. >>
IBM-344         E                           note there are no bold characters.                                       As suggested.                A      Done.



                                                                                       Page 87 of 91
                                                                          FC-GS-4 Revision 7.6 Comments
                                                                                     09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                               Problem Description                          Suggested solution                      Response                       Status     Edit Status
             /Edito Page    figure locator
               rial
                        342 D.3 Zone         There are several underlined words in this
                            management       section. The underlines have to be removed.
IBM-345         E           subsytems                                                                                         As suggested.                                    A      Done.
                        342 D.3 Zone         The statement << it can NOT be altered
                            management       while Active.>> should be << it is not
IBM-346         E           subsytems        alterable while Active >>                                                        As suggested.                                    A      Done.
                        342 D.4 Fabric       There are several << can >> and << will >>
                            Zone Server      terms that need to be removed from this
IBM-347         E           as a Conduit     annex.                                                                                                                            O      Ponder.
                        343 D.6 Fabric       The statement << repository has NO affect
                            Zone Server      on the Active Zone >> should be <<
                            Repository       repository has no affect on the Active Zone
IBM-348         E                            >>.                                                                              As suggested.                                    A      Done.
Andiamo-61      E       344 Annex E          This clause may require updates                 update                           There are no specific directions in this
                                                                                                                              comment.                                         R
                         344 Annex E:        The statement << This clause documents
                             Future Work     proposed >> should be << This annex
IBM-349        E             (Informative)   documents proposed >>.                                                           As suggested.                                    A      Done.
                             Annex E         Most of these future work items have been       Remove Lock Server, Additional
                                             overtaken by events.                            Key Servers and Performance
                                                                                             Servers. The others may be
McDATA-112     E         344                                                                 removed as well.                 See QLogic-XXX.
Cisco-008      E         345 index           index                                           remove it                        See QLogic-XXX.
IBM-350        E         345 Index           I would recommend deleting the index.                                            See QLogic-XXX.
                              Index          Index is outdated so should be updated or   Delete it.
McDATA-111     E         368                 deleted.                                                                                                                  345
                            i                There are several occurrences of both 'this
                                             standard' and 'this Standard'. One or the
                                             other should be used, but not both. My                                           "Standard" should be "standard" in all
ENDL-001       E                   Global    preference is for 'this standard'.                                               cases.                                           O      Ponder.
                            ii               Remove 'Release Notes' before Public
ENDL-002       E                             Review.                                                                          Yep, will do.                                    A
                            ii Front matter All the Release notes need to be deleted
IBM-001        E                             before sending this to public review.                                            Yep, will do.                                    A
                           ix                Is it possible to introduce FC-GS-4 with
                                             references to more modern members of the
                                             FC family of standards than FC-PH and FC-
ENDL-004       E                Introduction FG?                                                                              Need to re-word this.                            O      Ponder.
                           ix Acknowledge Is Sam Adams a member of T11?                                                       You don't have to be a member to be a
ENDL-005       E                   ments                                                                                      contributor.                                     R
                           ix Introduction The term << 'FC-4s' >> should not have
IBM-003        E                             quotes.                                                                          Need to re-word this intro.                      O      Ponder.




                                                                                           Page 88 of 91
                                                                                FC-GS-4 Revision 7.6 Comments
                                                                                           09/23/03 (03-083vA)


               Techn
                ical Physical Section/table/
 Company-#                                                  Problem Description                          Suggested solution                       Response                    Status     Edit Status
               /Edito Page     figure locator
                 rial
                            vi                Is it possible to describe FC-GS-4 in terms
                                              of a standard other than FC-PH, FC-PI for
                                              instance?




ENDL-003         E                 Foreword                                                                                        Yes.                                         O      Ponder.
                              vi Forward     The statement << during<CRLF>2000-2001.
                                             The standards approval process started in
                                             2001. >> is not correct. I best solution would
IBM-002          E                           be to just delete it.                                                                 Change to 2001-2003.                         A      Done.
Inrange-020      E    36/13              4.2 Reference to FC-SW-2                                 Change to FC-SW-3.
Inrange-022      E    360/337 C.6.4.2        Reference to FC-SW-2                                 Change to FC-SW-3.
Inrange-023      E    360/337 C.6.4.2        Reference to FC-GS-2                                 Change to FC-GS-4.
Inrange-025      E    365/342 D.3            Reference to FC-SW-2                                 Change to FC-SW-3.
Inrange-021      E    38/15     Table 4      Reference to FC-SW-2                                 Change to FC-SW-3.
                                Entire       Lists of more than 2 are written item1, item2        rewrite as "item1, item2, and
                                document     and item3. They are missing the comma                item3"
                                             before the and, which makes it difficult to                                           Will accept detailed proposal from
Brocade-036      E          all              parse                                                                                 commentor on how and where to fix.           O      ???
Cisco-004        E          all all          change FC-PH references                              to FC-FS                                                                      O      Ponder.
                                              INRANGE intends to submit comments to                                                Comment submission period ends at the
                                             clarify elements of this document.                                                    end of the letter ballot period. Any
                                             Comments presently in consideration within                                            additional comments will only be allowed
                                             INRANGE do not change the scope of the                                                for consideration on a case-by-case
Inrange-001a     E          all              proposed sstandard.                                                                   basis.                                       R
QLogic-044       E       Cover               No fax number for Mike O'Donnell                     Either provide a fax number or
                                                                                                  remove 'Fax:'.                   Fixed.                                       A      Done.
Cisco-001        E            ix Introduction     reference to FCP                                reference FCP-2                                                               O      Ponder.
                                 Introduction     The first paragraph is too generic to be of     Delete the first paragraph or
                                                  benefit.                                        update it with references to FC-
McDATA-3         E            ix                                                                  FS.
                                   Introduction   Replace PH references with FS references        Update references throughout the
McDATA-4         E            ix                                                                  document.



                                                                                                Page 89 of 91
                                                                        FC-GS-4 Revision 7.6 Comments
                                                                                   09/23/03 (03-083vA)


             Techn
              ical Physical Section/table/
 Company-#                                               Problem Description                   Suggested solution                            Response             Status     Edit Status
             /Edito Page     figure locator
               rial
McDATA-5        E         ix Names          delete Sam Adams and James Page
Andiamo-01      E   several several         The nomenclature should be consistent with Replace: Port Name -->
                                            FC-FS across the entire document.          N_Port_Name, Node Name -->
                                                                                       Node_Name, Port Identifier -->
                                                                                       N_Port_ID, Fabric Port Name -->
                                                                                       F_Port_Name. Also, when the
                                                                                       term Port is used, qualify it as
                                                                                       FC_Port, Nx_Port, Fx_Port or
                                                                                       other.
Andiamo-02      E   several several         References to FC-PH, FC-PH-2 and FC-PH- Update references.
                                            3 should be replaced by references to FC-
                                            FS. References to FC-FG should be
                                            removed of replaced by references to FC-
                                            SW-3. References to FC-SW or FC-SW-2
                                            should be replaced by references to FC-SW-
                                            3.
QLogic-050      E          x TOC            Column headers should be added.
QLogic-051      E        xiv LOF            Column headers should be added.
QLogic-052      E        xv LOT             Column headers should be added.
                             Subclause      FC-VI is an approved reference now.        Remove "ANSI INCITS xxx-199x,
                             2.3                                                       Fibre Channel - Virtual Interface
                                                                                       (FC-VI),T11/Project 1332D/Rev
                                                                                       1.84" and add "ANSI/NCITS 357-
                                                                                       2001, Fibre Channel - Virtual
                                                                                       Interface (FC-VI)" under approved
Emulex-001      E                                                                      references.                           As suggested.                          A      Done.
                             Subclause      The Internet Draft, "Fibre Channel         Remove "Internet Draft, Fibre
                             2.4            Management Framework Integration MIB"      Channel Management Framework
                                            long ago expired, but has now been         Integration MIB, December 28,
                                            archived as a T11 technical report.        1999" from the ipfc references and
                                                                                       add "ANSI INCITS xxx-200x, Fibre
                                                                                       Channel Management Information
                                                                                       Base (MIB-FA), T11/Project
                                                                                       1571DT/Rev 1.3" to subclause
                                                                                       2.3.                                  Is this really encompassed in that
Emulex-002      E                                                                                                            document?                              O      ???
                             Subclause      Definitions of Managed Objects for the     Change "Internet Draft, Definitions
                             2.4            Fabric Element in Fibre Channel Standard" of Managed Objects for the Fabric
                                            is now an RFC.                             Element in Fibre Channel
                                                                                       Standard, January 31, 2000" to
                                                                                       "RFC 2837, Definitions of
                                                                                       Managed Objects for the Fabric
                                                                                       Element in Fibre Channel
Emulex-003      E                                                                      Standard, May 2000                    As suggested.                          A      Done.




                                                                                      Page 90 of 91
                                                                               FC-GS-4 Revision 7.6 Comments
                                                                                          09/23/03 (03-083vA)


                Techn
                 ical Physical Section/table/
 Company-#                                                  Problem Description                          Suggested solution                        Response   Status     Edit Status
                /Edito Page    figure locator
                  rial
                               Subclause        The reference to RFC 2405 is no longer            Remove the reference to RFC
                               2.4              necessary, as it related only to the deleted      2405.
Emulex-004         E                            annex on DES encryption.                                                          As suggested.                 A      Done.
                               Subclause        The reference to RFC 1829 is no longer            Remove the reference to RFC
                               2.4              necessary, as it related only to the deleted      1829.
Emulex-005         E                            annex on DES encryption.                                                           As suggested.                A      Done.
                               Subclause        The three references to FIPS PUBs are no          Remove the three references to
                               2.4              longer necessary, as they related only to the     FIPS PUBs and the paragraph that
Emulex-006         E                            deleted annex on DES encryption.                  introduces them                  As suggested.                A      Done.
                                            3   In addition to adding the definition for F_Port   These are editorial and should
                                                and F/NL_Port in F735clause 3, also E_Port        reference as follows:
                                                and B_Port need to be added.
                                                                                                  B_Port - see FC-FS.
                                                                                                  E_Port - see FC-FS.
                                                                                                  F_Port - see FC-FS.
                                                                                                  F/NL_Port - see FC-AL-2.
Truefocus-001     E                                                                                                                                             O      Ponder.
                                6.4.6.2.2.4     In 6.4.6.2.2.4 Broadcast on FL_Ports
                                                Change "frame shall be sent to the all the
                                                devices on the loop..." to
                                                frame shall be sent to all devices on the
                                                loop... (see FC-AL-2)." Also,
                                                the following should be removed since it has
                                                no bearing on broadcast:
                                                "Use of the OPNyr selective replicate is
                                                prohibited. See FC-FLA."
Truefocus-002     E




                                                                                             Page 91 of 91

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:25
posted:7/31/2011
language:English
pages:91