SORT BY:

LIST ORDER
THREAD
AUTHOR
SUBJECT


SEARCH

IPS HOME


    [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

    IPS: New iSCSI and Auth MIB drafts



    
    After doing a post-last-call nit check on the iSCSI and Auth MIBs,
    we found a few (mostly editorial) things that needed to be fixed,
    as well as a few forgotten MIB attributes.
    
    The one semantic change to look at is the way that NodeIndex=0
    is used for discovery sessions.  This is much cleaner than the
    previous method of using fake nodes blank iSCSI names.
    
    I've posted new MIB drafts to address these issues.  They are available
    (along with the latest object model and .mi2 files) at:
    
    ftp://ftpeng.cisco.com/mbakke/ips/iscsi-mib/
    
    ftp://ftpeng.cisco.com/mbakke/ips/auth-mib/
    
    Here's a complete list of issues resolved.  Since we are beyond
    WG last call, please let me know as soon as possible if you have
    reason to believe that any of these changes are not appropriate.
    
    
    --
    Mark
    
    
    iSCSI MIB Modifications, draft-07 to draft-08:
    
    1. Add iscsiCxnMaxXmitDataSegLength to the Connection table.
    
       This was an oversight when we changed from a single PDU length
       for both directions, to a separate length for each.  We also
       need to remove the comment about being negotiated in blocks,
       since that's no longer true.
    
       Add:
    
    iscsiCxnMaxXmitDataSegLength OBJECT-TYPE
        SYNTAX        INTEGER (512..16777215)
        UNITS         "bytes"
        MAX-ACCESS    read-only
        STATUS        current
        DESCRIPTION
            "The maximum data payload size supported for command
            or data PDUs to be sent on this connection."
        DEFVAL { 8192 }
    ::= { iscsiConnectionAttributesEntry 11 }
    
       Change the description of iscsiCxnMaxRecvDataSegLength to:
    
            "The maximum data payload size supported for command
            or data PDUs received on this connection."
    
    
    2. Clarify the use of the NodeIndex for discovery sessions.
    
       Instead of using a dummy iSCSI node for sessions, discovery
       sessions will simply have a (valid) node index of 0, indicating
       that there is no node.
    
       In 6.7, delete the paragraph:
    
       Discovery sessions may be established without a particular target
       node specified as an endpoint.  Since sessions are indexed in part by
       the node index, a node must be provided under which to keep them.  An
       iscsiNode with a blank iSCSI Name may be created as a "discovery"
       node; discovery sessions must include this node as part of their
       indices.
    
       In 6.12, change the paragraph:
    
       The session type for each session indicates whether the session is
       used for normal SCSI commands or for discovery using the SendTargets
       text command.  Discovery sessions that do not belong to any
       particular node are placed under the "discovery" node.
    
       To:
    
       The session type for each session indicates whether the session is
       used for normal SCSI commands or for discovery using the SendTargets
       text command.  Discovery sessions that do not belong to any
       particular node have a node index field of 0.
    
       In the iscsiNodeName description, delete the paragraph:
    
            If this node is used as a discovery-only node, and supports
            only discovery sessions, this object contains a zero-length
            string.
    
       In the iscsiSessionAttributeEntry description, add the paragraph:
    
            If this session is a discovery session which is not attached
            to any particular node, the iscsiNodeIndex will be 0.
    
    3. Add a compliance statement saying that write-ability is not mandatory.
    
    4. Add iscsiCxnVersionActive to IscsiConnectionAttributesEntry.
       This was documented in the object model, but did not make it
       into the MIB.
    
    iscsiCxnVersionActive OBJECT-TYPE
        SYNTAX        INTEGER (0..255)
        MAX-ACCESS    read-only
        STATUS        current
        DESCRIPTION
            "Active version number of the iSCSI specification negotiated
            on this connection."
    ::= { iscsiConnectionAttributesEntry 16 }
    
    5. Clarify that iscsiInitiatorPortal and iscsiTargetPortal entries
       are created and destroyed automatically based on the value of
       the iscsiPortalRoles attribute.
     
     
    iSCSI MIB Nits:
     
     
    1. Lines more than 72 chars:
     
       iscsiInstVendorVersion
       iscsiSsnImmediateData
     
    2. Hyphens at line breaks: none
     
    3. Status of Memo, Abstract and Acknowledgements
       should not be numbered
     
    4. Need to add (unnumbered) table of contents after the Abstract
     
    5. Need to add boilerplate copyright notice to end
       from RFC 2026 10.4 (c)
     
    6. Remove [ISCSI] reference from Abstract (whole last sentence)
     
    7. Uncapitalize MUST in IscsiDigestMethod
     
    11. Remove space after - in Internet-Drafts in the status
        section.
     
    12. Replace .txt with .html for 1id-abstracts reference.
     
    13. Fix example domain names (RFC 2606)
      - Use 192.0.2.0/24 for IP address examples (RFC 3330)
    
    
    
    
    Auth MIB Edits:
    
    1. Remove the explicit references to "iSCSI" from the Auth MIB
       descriptions and comments.
    
       line 173: -- iSCSI User Identity Attributes Table
    
       line 230: -- iSCSI User Initiator Name Attributes Table
    
       line 291: -- iSCSI User Initiator Address Attributes Table
    
       line 412: The DESCRIPTION for the ipsAuthCredIndex:
    
       "An arbitrary integer used to uniquely identify a
       particular iSCSI Credential instance within an
       iSCSI instance present on the node."
     
    2. Change description
     
       -- Identity Credential Attributes Table
     
       to
     
       -- Credential Attributes Table
     
    3. Add a compliance statement saying that write-ability is not mandatory.
     
     
     
    Auth MIB Nits:
     
     
    1. Lines more than 72 chars: none
     
    2. Hyphens at line breaks: none
     
    3. Status of Memo, Abstract and Acknowledgements should not be numbered
     
    4. Need to add (unnumbered) table of contents after the Abstract
     
    5. Need to add boilerplate copyright notice to end
       from RFC 2026 10.4 (c)
     
    6. Remove space after - in Internet-Drafts in the status
        section.
     
    7. Replace .txt with .html for 1id-abstracts reference.
     
    8. Fixed a few typos and spelling errors
    


Home

Last updated: Fri Dec 06 17:18:57 2002
12057 messages in chronological order