[Rtg-ooam-dt] Moving Overlay OAM forward ?
Dave Dolson <ddolson@sandvine.com> Mon, 19 September 2016 17:54 UTC
Return-Path: <ddolson@sandvine.com>
X-Original-To: rtg-ooam-dt@ietfa.amsl.com
Delivered-To: rtg-ooam-dt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5510B12B4B3 for <rtg-ooam-dt@ietfa.amsl.com>; Mon, 19 Sep 2016 10:54:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.215
X-Spam-Level:
X-Spam-Status: No, score=-4.215 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-2.316] autolearn=ham autolearn_force=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 YzaOE0c2uMXC for <rtg-ooam-dt@ietfa.amsl.com>; Mon, 19 Sep 2016 10:54:05 -0700 (PDT)
Received: from mail1.sandvine.com (Mail1.sandvine.com [64.7.137.134]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 359DE12B4A8 for <rtg-ooam-dt@ietf.org>; Mon, 19 Sep 2016 10:54:03 -0700 (PDT)
Received: from WTL-EXCHP-2.sandvine.com ([fe80::68ac:f071:19ff:3455]) by wtl-exchp-1.sandvine.com ([::1]) with mapi id 14.03.0319.002; Mon, 19 Sep 2016 13:54:01 -0400
From: Dave Dolson <ddolson@sandvine.com>
To: "rtg-ooam-dt@ietf.org" <rtg-ooam-dt@ietf.org>
Thread-Topic: Moving Overlay OAM forward ?
Thread-Index: AdISnWzP7IfsNIOuRtylRho8Xt/ygg==
Date: Mon, 19 Sep 2016 17:54:01 +0000
Message-ID: <E8355113905631478EFF04F5AA706E98310D4D1D@wtl-exchp-2.sandvine.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.200.63]
x-c2processedorg: b2f06e69-072f-40ee-90c5-80a34e700794
Content-Type: multipart/alternative; boundary="_000_E8355113905631478EFF04F5AA706E98310D4D1Dwtlexchp2sandvi_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-ooam-dt/1wuPcGAkb0HIwO2-ptzACdJKPhw>
Subject: [Rtg-ooam-dt] Moving Overlay OAM forward ?
X-BeenThere: rtg-ooam-dt@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: List is used by the Routing Area Overlay OAM Design team for internal coordination and discussion <rtg-ooam-dt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-ooam-dt>, <mailto:rtg-ooam-dt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-ooam-dt/>
List-Post: <mailto:rtg-ooam-dt@ietf.org>
List-Help: <mailto:rtg-ooam-dt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-ooam-dt>, <mailto:rtg-ooam-dt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Sep 2016 17:54:06 -0000
OOAM design team, The Overlay OAM header defined in draft-ooamdt-rtgwg-ooam-header-00 looks like something I'd like to use with SFC. (https://tools.ietf.org/html/draft-ooamdt-rtgwg-ooam-header-00) Is there interest in moving this forward? It is missing some descriptive detail. And I might argue for some bit shuffling (more bits for type, fewer bits for flags or length). -Dave
- [Rtg-ooam-dt] Moving Overlay OAM forward ? Dave Dolson
- Re: [Rtg-ooam-dt] Moving Overlay OAM forward ? Greg Mirsky