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

Benoit Claise <bclaise@cisco.com> Mon, 01 February 2016 14:43 UTC

Return-Path: <bclaise@cisco.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 913B41A92F3 for <ieee-ietf-coord@ietfa.amsl.com>; Mon, 1 Feb 2016 06:43:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 VblY-SJXr5Dc for <ieee-ietf-coord@ietfa.amsl.com>; Mon, 1 Feb 2016 06:43:24 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 890D21A92DC for <ieee-ietf-coord@ietf.org>; Mon, 1 Feb 2016 06:43:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11545; q=dns/txt; s=iport; t=1454337803; x=1455547403; h=to:cc:from:subject:message-id:date:mime-version; bh=bEQMR3B0BQYDTYLemCQhhe/WUSCfEZWFm4fAtV7YG8A=; b=E5mqZShbkl03DKGnT6+KzINlHGUH0MMBKkJ0HLM4Jpn9FyiBSwxYkux+ 15LETKnePim+6nsxgqxxh2cUB4APFYIXLXznQY6LswkJVGJdQ8qTrVcZs ZLGKqmPgybjuDeGqCy4nTx6wZo2aIBVIk5dDIqzsNe8kOdjkxHGa5fFPk o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ACAgCRbq9W/xbLJq1egm6BHm6IV7FdAQ2BZBgBC4UhSoFvFAEBAQEBAQF/C4RDAQUBARoGSAMKAS0PFgsCCwMCAQIBFSIUDQgBAYgXDq4PjkUBAQEBAQEEAQEBAQEBAQEYhg+ISgEBgmU4E4EnBZZvhUeIBIFbSoZ6hVGFbohQHgEBQoNtO4d7gTABAQE
X-IronPort-AV: E=Sophos;i="5.22,380,1449532800"; d="scan'208,217";a="648973499"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Feb 2016 14:43:21 +0000
Received: from [10.60.67.86] (ams-bclaise-8915.cisco.com [10.60.67.86]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id u11EhLoI023710; Mon, 1 Feb 2016 14:43:21 GMT
To: "ieee-ietf-coord@ietf.org" <ieee-ietf-coord@ietf.org>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <56AF6CC6.7000208@cisco.com>
Date: Mon, 01 Feb 2016 15:33:42 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------030303010601080602010704"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ieee-ietf-coord/t3dQGqf1vcmOZMPtcIOvJ1uMTeg>
Cc: "lime-chairs@tools.ietf.org" <lime-chairs@tools.ietf.org>, Alia Atlas <akatlas@gmail.com>
Subject: [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:43:26 -0000

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