RFC 4595 on Use of IKEv2 in the Fibre Channel Security Association Management Protocol

rfc-editor@rfc-editor.org Thu, 27 July 2006 17:13 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G69Q4-0000fP-00; Thu, 27 Jul 2006 13:13:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G69Q1-0000fI-CI for ietf-announce@ietf.org; Thu, 27 Jul 2006 13:13:05 -0400
Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G69Q0-0001Jy-06 for ietf-announce@ietf.org; Thu, 27 Jul 2006 13:13:05 -0400
Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id k6RHD3nN024590; Thu, 27 Jul 2006 10:13:03 -0700
Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id k6RHD39g024589; Thu, 27 Jul 2006 10:13:03 -0700
Date: Thu, 27 Jul 2006 10:13:03 -0700
Message-Id: <200607271713.k6RHD39g024589@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
X-Spam-Score: -14.8 (--------------)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: rfc-editor@rfc-editor.org
Subject: RFC 4595 on Use of IKEv2 in the Fibre Channel Security Association Management Protocol
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Errors-To: ietf-announce-bounces@ietf.org

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

        
        RFC 4595

        Title:      Use of IKEv2 in the 
                    Fibre Channel Security Association Management 
                    Protocol 
        Author:     F. Maino, D. Black
        Status:     Informational
        Date:       July 2006
        Mailbox:    fmaino@cisco.com, 
                    black_david@emc.com
        Pages:      16
        Characters: 32268
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-maino-fcsp-02.txt

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

This document describes the use of IKEv2 to negotiate security
protocols and transforms for Fibre Channel as part of the Fibre
Channel Security Association Management Protocol.  This usage
requires that IKEv2 be extended with Fibre-Channel-specific
security protocols, transforms, and name types.  This document
specifies these IKEv2 extensions and allocates identifiers for them.
Using new IKEv2 identifiers for Fibre Channel security protocols
avoids any possible confusion between IKEv2 negotiation for IP
networks and IKEv2 negotiation for Fibre Channel.  This memo provides 
information for the Internet community.

INFORMATIONAL: This memo provides information for the Internet community. 
It does not specify an Internet standard of any kind. 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@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

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

help: ways_to_get_rfcs. For example:

        To: rfc-info@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@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@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


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

...



_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce