[storm] Last Call complete on "iFCP and Protocol 133 Updates"
Tom Talpey <firstname.lastname@example.org> Fri, 26 February 2010 04:33 UTC
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1F8AE28C4DA for <email@example.com>; Thu, 25 Feb 2010 20:33:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Status: No, score=-10.199 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, J_CHICKENPOX_23=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([184.108.40.206]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GASbbILNnObb for <firstname.lastname@example.org>; Thu, 25 Feb 2010 20:33:37 -0800 (PST)
Received: from smtp.microsoft.com (smtp.microsoft.com [220.127.116.11]) by core3.amsl.com (Postfix) with ESMTP id 9556128C267 for <email@example.com>; Thu, 25 Feb 2010 20:33:37 -0800 (PST)
Received: from TK5EX14CASC129.redmond.corp.microsoft.com (18.104.22.168) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 22.214.171.124; Thu, 25 Feb 2010 20:35:50 -0800
Received: from TK5EX14MBXC118.redmond.corp.microsoft.com ([169.254.9.167]) by TK5EX14CASC129.redmond.corp.microsoft.com ([126.96.36.199]) with mapi; Thu, 25 Feb 2010 20:35:47 -0800
From: Tom Talpey <firstname.lastname@example.org>
To: "email@example.com" <firstname.lastname@example.org>
Thread-Topic: Last Call complete on "iFCP and Protocol 133 Updates"
Date: Fri, 26 Feb 2010 04:35:48 +0000
Content-Type: text/plain; charset="us-ascii"
Subject: [storm] Last Call complete on "iFCP and Protocol 133 Updates"
List-Id: Storage Maintenance WG <storm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/storm>, <mailto:email@example.com?subject=unsubscribe>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/storm>, <mailto:firstname.lastname@example.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Feb 2010 04:33:39 -0000
The deadline for comment having recently passed, the Working Group Last Call on draft-ietf-storm-ifcp-ipn133-updates is complete. Two comments were received (below), both of them concerning editorial changes and not affecting content. These changes will be addressed by the authors and an updated document will be available in the near future. Thanks to all those who reviewed the document; after the update the document will be forwarded to the next phase of IETF review. Tom Talpey STORM WG co-chair Comments: http://www.ietf.org/mail-archive/web/storm/current/msg00098.html http://www.ietf.org/mail-archive/web/storm/current/msg00099.html > -----Original Message----- > From: email@example.com [mailto:firstname.lastname@example.org] On Behalf > Of Tom Talpey > Sent: Thursday, February 04, 2010 6:50 AM > To: email@example.com > Subject: [storm] Working Group Last Call on "iFCP and Protocol 133 Updates" > Importance: High > > The STORM working group announces Last Call on the iFCP update document > > http://www.ietf.org/id/draft-ietf-storm-ifcp-ipn133-updates-00.txt > > which was chartered and published last November. The Last Call period will > extend through Sunday February 21, 2010 at 11:59pm Eastern Standard Time, > in expectation of completing any necessary edits prior to the March IETF > publication deadlines. > > Please send any and all technical comments directly to this mailing list: > firstname.lastname@example.org > > Any editorial or other comments should be sent to the authors, cc'ing me: > David Peterson david.peterson -at- brocade.com > David Black black_david -at- emc.com > Tom Talpey (STORM WG co-chair) ttalpey -at- microsoft.com > > Additional information on the STORM WG agenda, work items and links to > the active documents are available at > http://www.ietf.org/dyn/wg/charter/storm-charter.html > > The document Abstract is reproduced below. > > Changes to Fibre Channel have caused the specification of 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 Internet Protocol Number 133, > which was allocated for a pre-standard version of FCIP. > > Tom Talpey > STORM WG co-chair > _______________________________________________ > storm mailing list > email@example.com > https://www.ietf.org/mailman/listinfo/storm