RFC 4939 on Definitions of Managed Objects for iSNS (Internet Storage Name Service)

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



        

        RFC 4939



        Title:      Definitions of Managed Objects for 

                    iSNS (Internet Storage Name Service) 

        Author:     K. Gibbons, G. Ramkumar,

                    S. Kipp

        Status:     Standards Track

        Date:       July 2007

        Mailbox:    [email protected], 

                    [email protected], 

                    [email protected]

        Pages:      80

        Characters: 165381

        Updates/Obsoletes/SeeAlso:   None



        I-D Tag:    draft-ietf-ips-isns-mib-11.txt



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



The iSNS (Internet Storage Name Service) protocol provides storage

name service functionality on an IP network that is being used for

iSCSI (Internet Small Computer System Interface) or iFCP (Internet

Fibre Channel Protocol) storage.  This document provides a mechanism to

monitor multiple iSNS Servers, including information about registered

objects in an iSNS Server.  [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 [email protected].  Requests to be

added to or deleted from the RFC-DIST distribution list should

be sent to [email protected].



Details on obtaining RFCs via FTP or EMAIL may be obtained by sending

an EMAIL message to [email protected] with the message body 



help: ways_to_get_rfcs. For example:



        To: [email protected]

        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 [email protected].  Unless

specifically noted otherwise on the RFC itself, all RFCs are for

unlimited distribution.



Submissions for Requests for Comments should be sent to

[email protected].  Please consult RFC 2223, Instructions to RFC

Authors, for further information.





The RFC Editor Team

USC/Information Sciences Institute



...






_______________________________________________
Ips mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/ips