[PWE3] fc-encap draft: Forthcoming reference changes

<david.black@emc.com> Sun, 01 April 2012 09:33 UTC

Return-Path: <david.black@emc.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7016C21F869F for <pwe3@ietfa.amsl.com>; Sun, 1 Apr 2012 02:33:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.999
X-Spam-Level:
X-Spam-Status: No, score=-107.999 tagged_above=-999 required=5 tests=[BAYES_50=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mb9c3lDB4K7u for <pwe3@ietfa.amsl.com>; Sun, 1 Apr 2012 02:33:01 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id C82A421F867F for <pwe3@ietf.org>; Sun, 1 Apr 2012 02:33:00 -0700 (PDT)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q319Wu4F016141 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <pwe3@ietf.org>; Sun, 1 Apr 2012 05:32:56 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.251]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor) for <pwe3@ietf.org>; Sun, 1 Apr 2012 05:32:44 -0400
Received: from mxhub02.corp.emc.com (mxhub02.corp.emc.com [10.254.141.104]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q319Wg5G024244 for <pwe3@ietf.org>; Sun, 1 Apr 2012 05:32:43 -0400
Received: from mx14a.corp.emc.com ([169.254.1.70]) by mxhub02.corp.emc.com ([10.254.141.104]) with mapi; Sun, 1 Apr 2012 05:32:42 -0400
From: david.black@emc.com
To: pwe3@ietf.org
Date: Sun, 01 Apr 2012 05:32:40 -0400
Thread-Topic: fc-encap draft: Forthcoming reference changes
Thread-Index: Ac0P6mIwrF9jl7jIQTaGS6Cg+to+Pw==
Message-ID: <7C4DFCE962635144B8FAE8CA11D0BF1E05B2E807F9@MX14A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: [PWE3] fc-encap draft: Forthcoming reference changes
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Apr 2012 09:33:01 -0000

This is a heads-up that the editing changes needed to get draft-ietf-pwe3-fc-encap
published are going to be a little more involved than I've lead the WG to expect
in the past.

A reminder of the situation: The Fibre Channel pseudowire (FC PW) is specified by
a pair of related specifications, the IETF fc-encap draft, and an FC-BB-* spec from
INCITS T11 (the Fibre Channel standards body).  When we got the fc-encap draft
finished, we found ourselves badly out of sync with T11 - the draft contains a
normative reference to [FC-BB-6] which will not be published as a standard for a
while to come (2013, maybe).  As a result, the fc-encap draft has been stuck in
reference wait at the RFC Editor (all other editing is done) for most of a year.

In order to deal with this situation, T11 has prepared a new standard that contains
their portion of the FC PW spec, FC-BB-5 Amendment 1 [FC-BB-5/AM1].  That standard
has now cleared its final technical approval stage and can be normatively referenced
(will be actually published in the next few months, but all the stages from here are
entirely procedural).  The original plan was to simply change the normative [FC-BB-6]
reference in the fc-encap draft to [FC-BB-5/AM1], but ...

FC-BB-6 is a large specification that includes other FC encapsulations in addition
to the FC-PW.  In contrast, FC-BB-5 Amendment 1 has been cut down to just the FC PW
material.  In looking at the fc-encap draft, I've discovered that FC-BB-6 is cited
both normatively and informatively in the text - the normative citations are for
the T11 portion of the FC PW, whereas the informative citations are for other FC
encapsulations (e.g., FCIP).  Therefore what I intend to do is:
- Move the existing [FC-BB-6] normative reference to an informative "work
	in progress" reference.
- Add a new normative reference to [FC-BB-5/AM1]
- Examine every current citation of [FC-BB-6] to determine whether it is
	normative for the FC PW (and needs to be changed to [FC-BB-5/AM1]
	vs. informative for other encapsulations (and needs to remain as a
	citation of [FC-BB-6].
The resulting editing instructions will take a bit of time to prepare, but should
go to the RFC Editor sometime this week.

Thanks,
--David (as one of the editors of the fc-encap draft, and T11's liaison to IETF).
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953             FAX: +1 (508) 293-7786
david.black@emc.com        Mobile: +1 (978) 394-7754
----------------------------------------------------