[trill] Fwd: TRILL Liaison to IEEE 802.1
Donald Eastlake <d3e3e3@gmail.com> Wed, 25 September 2013 02:23 UTC
Return-Path: <d3e3e3@gmail.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BD6811E819F for <trill@ietfa.amsl.com>; Tue, 24 Sep 2013 19:23:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level:
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, NO_RELAYS=-0.001, 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 qGz-psALz9OP for <trill@ietfa.amsl.com>; Tue, 24 Sep 2013 19:23:17 -0700 (PDT)
Received: from mail-pd0-x229.google.com (mail-pd0-x229.google.com [IPv6:2607:f8b0:400e:c02::229]) by ietfa.amsl.com (Postfix) with ESMTP id 82DE511E81A4 for <trill@ietf.org>; Tue, 24 Sep 2013 19:23:16 -0700 (PDT)
Received: by mail-pd0-f169.google.com with SMTP id r10so5437304pdi.0 for <trill@ietf.org>; Tue, 24 Sep 2013 19:23:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=r7ympyRziFn2ms0JBuM+rUXFwEdcnP7Whyr0+aY1GAQ=; b=DmIy8ftnIal/3aEeH8v4jWorbsTsQjDvBCK46x2O4FHWPK57Amh69p6JLd+1MUp/OF ylQo9gCvOieFPw95S9yvx5sFVcJ+faXAlZMpTEgaCpC6wBkv9fm0sp6SwBOjVoV9LdtI H6GlI9NbbXAcwHwv98Hf42GveNhHMQgaj26pl9Ue/ezmANnIrGUwwwEi0HVVUNIAx01R X2P2ogBxsMJRHgVvozJeQESsWPPvzedvlS4EWIugr6q4KRjtXAzwMaejFytYwMnPpA32 w0ikvMvrrszNAbDjfQMu5z0HfPNdTgjqYRY6FjeN0K37IXVgXZT/OcAWjutSs+0HydOj 6Cvw==
X-Received: by 10.66.12.164 with SMTP id z4mr9466509pab.148.1380075795265; Tue, 24 Sep 2013 19:23:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.70.108.161 with HTTP; Tue, 24 Sep 2013 19:22:55 -0700 (PDT)
In-Reply-To: <CAF4+nEFAC9YhvjLe_cHh8Mpkf8S3H5Z9S7y_omik-XRwk0NFLQ@mail.gmail.com>
References: <CAF4+nEFAC9YhvjLe_cHh8Mpkf8S3H5Z9S7y_omik-XRwk0NFLQ@mail.gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 24 Sep 2013 22:22:55 -0400
Message-ID: <CAF4+nEHekM1i-C97Fn+iy-kXNwEQ+Cwc6LW3nOirJ9OXYV4Yeg@mail.gmail.com>
To: "trill@ietf.org" <trill@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"
Subject: [trill] Fwd: TRILL Liaison to IEEE 802.1
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/trill>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Sep 2013 02:23:18 -0000
The following liaison has been sent to Tony Jeffree, Chair of the IEEE 802.1 WG ---------- Forwarded message ---------- Date: Tue, Sep 24, 2013 at 10:15 PM Subject: TRILL Liaison to IEEE 802.1 To: Tony Jeffree Cc: Stephen Haddock, Paul Nikolich, Ted Lemon, Jari Arkko, Dan Romascanu, Eric Gray, Bernard Aboba, trill-chairs@tools.ietf.org Dear Tony, The IETF TRILL Working Group has been developing OAM facilities for the TRILL protocol. As you are aware, individual participants in the TRILL WG made some preliminary presentations to IEEE 802.1 on their view as to the direction these TRILL OAM facilities were taking. In addition, the IETF has issued Informational RFC 6905, "Requirements for Operations, Administration, and Maintenance (OAM) in Transparent Interconnection of Lots of Links (TRILL)". RFC 6905 has been determined to have IETF consensus. Additional TRILL OAM documents are under development in the TRILL Working Group as follows: https://datatracker.ietf.org/doc/draft-ietf-trill-oam-framework/ https://datatracker.ietf.org/doc/draft-ietf-trill-oam-fm/ The TRILL Working Group is grateful for the assistance of a number of voting members of the IEEE 802.1 Working Group who have been contributing as individuals to this TRILL WG effort. The -03 version of the OAM Framework draft has been determined to have TRILL Working Group consensus and publication as an RFC has been requested. But it is still subject to change. The TRILL Working Group has adopted draft-ietf-trill-oam-fm (Fault Management) as a Working Group draft. The methods presented in Fault Management document are patterned after IEEE 802.1ag Continuity Fault Management. You should note that Working Group draft status in the IETF can just indicate that the Working Group considers it an appropriate starting point. In particular, while we think the TRILL WG is favorably inclined towards this draft, a consensus determination has not been made on this draft or on any particular item within it. The Fault Management draft also suggests that IEEE 802.1ag code points could be allocated by the 802.1 Working Group for use in TRILL OAM in a manner somewhat similar to the way they were for use in ITU-T Recommendation Y.1731. Should such code points not be allocated, TRILL OAM would be reworked so as not to use that code point space. We would like the IEEE 802.1 Working Group to review these documents, particularly the oam-fm (Fault Management) draft. We would welcome comments, formal or informal, and your opinion as to whether allocation of IEEE 802.1 code points is possible based on the current technical direction of TRILL OAM. Sincerely Yours, Erik Nordmark & Donald Eastlake 3rd Co-Chairs, IETF TRILL Working Group
- [trill] Fwd: TRILL Liaison to IEEE 802.1 Donald Eastlake