[storm] RFC 6172 on Deprecation of the Internet Fibre Channel Protocol (iFCP) Address Translation Mode

rfc-editor@rfc-editor.org Thu, 10 March 2011 03:23 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: storm@core3.amsl.com
Delivered-To: storm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0BE4A3A67F7; Wed, 9 Mar 2011 19:23:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.125
X-Spam-Level:
X-Spam-Status: No, score=-102.125 tagged_above=-999 required=5 tests=[AWL=-0.125, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q5iUx4XJAASg; Wed, 9 Mar 2011 19:23:19 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 4926D3A67F6; Wed, 9 Mar 2011 19:23:19 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id B70CFE0741; Wed, 9 Mar 2011 19:24:36 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20110310032436.B70CFE0741@rfc-editor.org>
Date: Wed, 9 Mar 2011 19:24:36 -0800 (PST)
Cc: storm@ietf.org, rfc-editor@rfc-editor.org
Subject: [storm] RFC 6172 on Deprecation of the Internet Fibre Channel Protocol (iFCP) Address Translation Mode
X-BeenThere: storm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Storage Maintenance WG <storm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/storm>, <mailto:storm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/storm>
List-Post: <mailto:storm@ietf.org>
List-Help: <mailto:storm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/storm>, <mailto:storm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Mar 2011 03:23:20 -0000

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

        
        RFC 6172

        Title:      Deprecation of the Internet Fibre 
                    Channel Protocol (iFCP) Address Translation Mode 
        Author:     D. Black, D. Peterson
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2011
        Mailbox:    david.black@emc.com, 
                    david.peterson@brocade.com
        Pages:      6
        Characters: 11625
        Updates:    RFC4172

        I-D Tag:    draft-ietf-storm-ifcp-ipn133-updates-03.txt

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

Changes to Fibre Channel have caused the specification of the Internet
Fibre Channel Protocol (iFCP) address translation mode to become 
incorrect.  Due to the absence of usage of iFCP address translation 
mode, it is deprecated by this document.  iFCP address transparent 
mode remains correctly specified.

iFCP address transparent mode has been implemented and is in current
use; therefore, it is not affected by this document.

This document also records the state of Protocol Number 133, which
was allocated for a pre-standard version of the Fibre Channel Internet
Protocol (FCIP).  [STANDARDS-TRACK]

This document is a product of the STORage Maintenance 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-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC