[rfc-dist] RFC 4545 on Definitions of Managed Objects for IP Storage User Identity Authorization

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Tue May 30 16:14:13 PDT 2006


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4545

        Title:      Definitions of Managed Objects for 
                    IP Storage User Identity Authorization 
        Author:     M. Bakke, J. Muchow
        Status:     Standards Track
        Date:       May 2006
        Mailbox:    mbakke at cisco.com, 
                    james.muchow at qlogic.com
        Pages:      43
        Characters: 87345
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ips-auth-mib-08.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4545.txt

This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in TCP/IP-based internets.  In
particular, it defines objects for managing user identities and the
names, addresses, and credentials required manage access control, for use
with various protocols.  This document was motivated by the need for the
configuration of authorized user identities for the iSCSI protocol,
but has been extended to be useful for other protocols that have
similar requirements.  It is important to note that this MIB module
provides only the set of identities to be used within access lists; it is
the responsibility of other MIB modules making use of this one to tie
them to their own access lists or other authorization control methods.  
[STANDARDS TRACK]

This document is a product of the IP Storage Working Group of the 
IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and 
suggestions for improvements.Please refer to the current edition of the 
Internet Official Protocol Standards (STD 1) for the standardization 
state and status of this protocol.  Distribution of this memo is 
unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...




More information about the rfc-dist mailing list