Re: [ieee-ietf-coord] Issue 19: Common OAM proposal / Layer Independent OAM

Donald Eastlake <d3e3e3@gmail.com> Mon, 01 February 2016 14:56 UTC

Return-Path: <d3e3e3@gmail.com>
X-Original-To: ieee-ietf-coord@ietfa.amsl.com
Delivered-To: ieee-ietf-coord@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C61791A92F5 for <ieee-ietf-coord@ietfa.amsl.com>; Mon, 1 Feb 2016 06:56:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id apaUtocMA8M1 for <ieee-ietf-coord@ietfa.amsl.com>; Mon, 1 Feb 2016 06:56:28 -0800 (PST)
Received: from mail-ob0-x234.google.com (mail-ob0-x234.google.com [IPv6:2607:f8b0:4003:c01::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 362241AC39D for <ieee-ietf-coord@ietf.org>; Mon, 1 Feb 2016 06:56:27 -0800 (PST)
Received: by mail-ob0-x234.google.com with SMTP id wb13so88210218obb.1 for <ieee-ietf-coord@ietf.org>; Mon, 01 Feb 2016 06:56:27 -0800 (PST)
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 :cc:content-type; bh=/+EhzLu4zWeXroSY7ZpVFFaq+m//S5Dcze5TLWqAEPw=; b=tYs0QfoaWLTePYn/s8TyXBXV/QQydz9Kz4BvZqgsnaGLVEkXnUycjtu7z3BtkD2gBz OtHM0RLUNcKqeyckhYTMr5SrhR90M9wTtRjrvUoNxzSiHFNuLXZiqBTh3eNTdAtu/3lw x3mXmEdujUnO1Zxr9AZX0Yl9ATNXxxYuaUETJurlr9hKzkRoSaZ2JtmkJpS64r5314md m4bVRrRhXfl3/gEUXYII9exo+od9HuCiLWwfiEbKxS5FVbYC3b7xoA8aOqJT6zxJQX8R GMRKnNPllCwov9k+n8SJwexKVnioQE6Xu+Nl/ydtcAx1jYazBl9aL38P9kXzn0kRJPgh 8YdA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=/+EhzLu4zWeXroSY7ZpVFFaq+m//S5Dcze5TLWqAEPw=; b=g6mXAkzhUglFYZMeqbcPU+8df3u3W6utGAfnZcQRgbpRJKDy4SREoUTMUUQbbv4LIv QBaZSa89a+HvP+/uIxWsn1Nl7MMKEh33FLKbGdIl/yRRAcg0awc8YFbK6wv01JI3jyM5 yehUXAAorGKs37p5i4hdEGdRV3F+IHAKX7gllNe4k0L5X8+oazLFzJch2a5MyqtWEk4I SnZ0tCt88udMZpGDnENu2bwccjrCZCBn3tnIgZpwSdF7HPu5bKsqPqn//toVUX3+bXNh UzFXQNL5uVJkIu+gNA4BZubxqfEQQW1r/9Stqqkt/+/AUVBStj/RRI+zd1GB0W/g/yN1 +MhA==
X-Gm-Message-State: AG10YOS4PQiAvu2qpeZRtiWzz1czYM488qLbeSR31PlR7pCu4d82iRthhuOKc2zXIf4uFD0I/3lncvouL+BUyA==
X-Received: by 10.60.232.164 with SMTP id tp4mr18561628oec.55.1454338586423; Mon, 01 Feb 2016 06:56:26 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.157.161 with HTTP; Mon, 1 Feb 2016 06:56:11 -0800 (PST)
In-Reply-To: <56AF6CC6.7000208@cisco.com>
References: <56AF6CC6.7000208@cisco.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Mon, 01 Feb 2016 09:56:11 -0500
Message-ID: <CAF4+nEGzk65ysAn_N70MH1NPtPUHBT3f3Dnk9GX26igHjMXFWQ@mail.gmail.com>
To: Benoit Claise <bclaise@cisco.com>
Content-Type: multipart/alternative; boundary="001a1136a112d3b8ba052ab696db"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ieee-ietf-coord/b1WjJqttctqAims4-qVTQCXG3vE>
Cc: Alia Atlas <akatlas@gmail.com>, "lime-chairs@tools.ietf.org" <lime-chairs@tools.ietf.org>, "ieee-ietf-coord@ietf.org" <ieee-ietf-coord@ietf.org>
Subject: Re: [ieee-ietf-coord] Issue 19: Common OAM proposal / Layer Independent OAM
X-BeenThere: ieee-ietf-coord@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Management-level discussions between IEEE and IETF on topics of interest to both SDOs <ieee-ietf-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ieee-ietf-coord>, <mailto:ieee-ietf-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ieee-ietf-coord/>
List-Post: <mailto:ieee-ietf-coord@ietf.org>
List-Help: <mailto:ieee-ietf-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ieee-ietf-coord>, <mailto:ieee-ietf-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Feb 2016 14:56:31 -0000

Hi,

I will probably not be able to make the call due to a conflict but I wanted
to also note RFC 7319 "IANA Considerations for Connectivity Fault
Management (CFM) Code Points" and the IANA registry at
https://www.iana.org/assignments/cfm-oam/cfm-oam.xhtml

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

On Mon, Feb 1, 2016 at 9:33 AM, Benoit Claise <bclaise@cisco.com> wrote:

> Dear all,
>
> Here is an update on this topic:
>
> 19. Common OAM proposal / Layer Independent OAM
> 19.1. Description - proposal made by Tissa Senevirathne and a group of
> TRILL contributors at the IEEE 802.1 meetings in July and September to
> reuse the IEEE 802.1ag frame format for TRILL OAM. Needs coordination
> and architectural consistency with the IEEE 802.1 architecture and OAM
> practice.
>
> - 8/20/13: The TRILL WG re-chartered, new charter includes OAM.
> Rechartering was communicated on the mail list.
>
> - 9/25/13: Liaison Statement sent by the TRILL chairs to the IEEE 802
> informing on the status of the work.
>
> - 12/9/13: draft-ietf-trill-oam-framework approved by the IESG
>
> - 1/22/14: new liaison statement sent by TRILL to IEEE 802.1
>
> - Status 1/27/14 (Norman Finn, Donald): liaison from TRILL asking for
> code points from the Connectivity Fault Management protocol, Ethernet
> OAM, as was done with ITU a few years back. It allocates the blocks of
> code points to the IETF with the understanding that they will be
> assigned by IANA based on IETF Standards Actions and TRILL will be an
> early user of some values. Expected to pass.
>
> - Status 9/15/14 (Dan Romascanu): New Non-WG Mailing List: Lime -- Layer
> Independent OAM Management in Multi-Layer Environment (LIME) discussion
> list -  https://www.ietf.org/mailman/listinfo/lime. Working on a
> charter, may request a BOF at IETF-91
>
> - Status 1/20/15 (Dan): while most of the TRILL OAM work progresses, the
> LIME WG was formed and its charter explicitly calls for coordination
> with other SDOs including the IEEE
>
> - Status 6/15/15 (Dan): TRILL - MIB work waiting for expert review, YANG
> document in WG; LIME - no WG I-Ds yet
>
> - August 2015: call for adoption of draft-tissa-lime-yang-oam-model-06
> as LIME WG document in LIME, announcement sent to the ieee-ietf list, now
> http://datatracker.ietf.org/doc/draft-ietf-lime-yang-oam-model/
>
> - Individual submission to follow:
> http://datatracker.ietf.org/doc/draft-zhuang-lime-yang-oam-model-applicability/
> (applicability document)
>
> - draft-ietf-trill-oam-mib-11.txt approved by the IESG
>
> 19.2. Relevant Documents
>
> https://datatracker.ietf.org/doc/draft-ietf-trill-oam-req - published as
> RFC 6905
>
> http://www.ieee802.org/1/files/public/docs2012/liaison-tissa-oam-ieee-
> trill-0912-v02.pptx
>
> https://datatracker.ietf.org/doc/draft-ietf-trill-oam-framework/ -
> published as RFC 7174
>
> https://datatracker.ietf.org/doc/draft-tissa-trill-oam-fm/ published as
> RFC 7455
>
> http://datatracker.ietf.org/wg/trill/charter/
>
> http://ieee802.org/1/files/public/docs2014/new-senevirathne-trill-oam-
> liaison-0114-v01.pptx
>
> http://datatracker.ietf.org/doc/draft-ietf-trill-yang-oam/
>
> http://datatracker.ietf.org/doc/draft-ietf-trill-oam-mib/
>
> https://datatracker.ietf.org/liaison/1302/
>
> http://datatracker.ietf.org/wg/lime/charter/
>
> http://datatracker.ietf.org/doc/draft-ietf-lime-yang-oam-model/
>
>
> http://datatracker.ietf.org/doc/draft-zhuang-lime-yang-oam-model-applicability/
>
>
> 19.3. Owners - Alia Atlas, Benoit Claise, Norm Finn
>
>
> 19.4. Action Items
> Follow the TRILL OAM documents progress in the WG and send them for
> review to IEEE 802.1 when they reach milestones (WGLC, IETF LC)
>
> This work item will remain open to monitor the status, as well as other
> more OAM-related I-Ds in the TRILL Working Group that should be reviewed
> by IEEE 802.1.
>
> TRILL and LIME documents to be communicated for review when relevant to
> the IEEE 802 (at LC)
>
> *The update, received from the LIME chairs:*
> 1. Draft-zhuang-lime-yang-oam-model-applicability is under development
> 2. Draft-ietf-lime-yang-oam-model is on hold waiting for
> draft-zhuang-lime-yang-oam-model-applicability
> 3. As it was difficult to find commonalities,
> draft-ietf-lime-yang-oam-model is being split into connectionless and
> connection-oriented parts
>
> Regarding TRILL, the update should come from Alia.
>
> Regards, Benoit
>
> _______________________________________________
> ieee-ietf-coord mailing list
> ieee-ietf-coord@ietf.org
> https://www.ietf.org/mailman/listinfo/ieee-ietf-coord
>
>