Re: [Rtg-ooam-dt] [nvo3] O-bit vs. OAM as Next Protocol (Re: Consensus call on encap proposals)

Tom Herbert <tom@herbertland.com> Tue, 09 August 2016 22:56 UTC

Return-Path: <tom@herbertland.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 0EA3012D1DE for <rtg-ooam-dt@ietfa.amsl.com>; Tue, 9 Aug 2016 15:56:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=herbertland-com.20150623.gappssmtp.com
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 iLfab38h0hIa for <rtg-ooam-dt@ietfa.amsl.com>; Tue, 9 Aug 2016 15:56:35 -0700 (PDT)
Received: from mail-it0-x22d.google.com (mail-it0-x22d.google.com [IPv6:2607:f8b0:4001:c0b::22d]) (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 F1E6B12D8D9 for <rtg-ooam-dt@ietf.org>; Tue, 9 Aug 2016 15:56:26 -0700 (PDT)
Received: by mail-it0-x22d.google.com with SMTP id f6so28642364ith.0 for <rtg-ooam-dt@ietf.org>; Tue, 09 Aug 2016 15:56:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=DpotvQ3u85+h0T5OsHlHGSIde92r8eJ3yZ3ZOzJDdTM=; b=eW/InXJqMrFeDhc2+XYthjc2Dnfg6+jTqMaLXi2Oi90MuczT5Ne1O7L+IAiyhGNWZV jETxKJGHljpdKPPRMo35Y7ym/UVPeTBLJOtCQt1bFIgvbvFEDgP/7Ioyo4yXgiSltVNk pnSWAXIOoLRyxCROyPhA0kB+M7klFMkCV5j2v2wj9276ZiBYxU5CV9y2NU1JdYX6PZTu tojo+znIndxAZSoEQgFimh7BYishxAddatZWe24fk282nxK8MJT/CW/UljhT6QBaLCym /lJxUFjtEQtOEp0D14gw2gTMj7DXqF5gWk2sZcbe9tIiqN8CXpWHFRhGeEUteOV2hecG 1kvQ==
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-transfer-encoding; bh=DpotvQ3u85+h0T5OsHlHGSIde92r8eJ3yZ3ZOzJDdTM=; b=VlOPoBpNG903agWtYDzmX1pP/Msr45xi1IXixTI7a6shljMAnF0Fbk/95HlO4pmf7f Tw2AzmdAY6HiS98+zE3CIiCpx/M92xJZGiD/QUkYSjNSwurqhTF5jF2eWgYnz7mNxApG jWj8Nesj6YBYBm3RPuP6T5mjITYXSEJBWiZiQH75MYfSnBHdA9c+4QQf37llc5Gyj+zb vrjY+U2ozh5mIopjyfMCGKLCpDNH9zKSWhlQl+NGe50B44ahtNJgIhJQA8O2e6VG6DyJ u0rUHkqezknV0pLrWPMqVRPVZVMrrDm4G8euljhxd0//0L+wJNiWpXSP3K8xJ1AUtKL+ TbsQ==
X-Gm-Message-State: AEkoouuYT5yu/4PMC2AYDMLRmE71tpRX0iwtRbWHaiNJpanMAnm7/FOYWnQSYK7RhMTk+LLGikStQqRtgGAttw==
X-Received: by 10.36.103.214 with SMTP id u205mr27817339itc.88.1470783386282; Tue, 09 Aug 2016 15:56:26 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.21.130 with HTTP; Tue, 9 Aug 2016 15:56:25 -0700 (PDT)
In-Reply-To: <80ABDBE3-BC90-4741-9230-F32B7FC06558@cisco.com>
References: <CA+RyBmVzweMMTK3=ystVBMgWt3pxfCQ35qWgWH8ewhB=JO5nvQ@mail.gmail.com> <CALx6S35_E+hwFPYvdYWLUm2rVGKpNMObD_cPy-ooEhDoUks4hQ@mail.gmail.com> <CA+RyBmXMQ_DWTSWcpHta34P2zMU96AzcRWUs6Pn5Vva6r9Y=Xw@mail.gmail.com> <CALx6S34WUnTEZ8H770eFvO+5wZ9XSfNRbuSYWDBtNKOBTeKVRA@mail.gmail.com> <6959298E-B4E9-4593-9F0C-A384CF730A74@cisco.com> <CALx6S36KPOcfnsjELHZ5pf2NVqbEihni_+1=PnzHX_d2Fc7JUw@mail.gmail.com> <80ABDBE3-BC90-4741-9230-F32B7FC06558@cisco.com>
From: Tom Herbert <tom@herbertland.com>
Date: Tue, 09 Aug 2016 15:56:25 -0700
Message-ID: <CALx6S36qG=544M7cS-NjUvrXzfTAAJSQrQqx6f15Y=GSpnk9zg@mail.gmail.com>
To: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-ooam-dt/3PL6HLzrq5keNqva8S2pxe1pYV4>
Cc: "Bocci, Matthew (Nokia - GB)" <matthew.bocci@nokia.com>, Greg Mirsky <gregimirsky@gmail.com>, NVO3 <nvo3@ietf.org>, Alia Atlas <akatlas@gmail.com>, "rtg-ooam-dt@ietf.org" <rtg-ooam-dt@ietf.org>
Subject: Re: [Rtg-ooam-dt] [nvo3] O-bit vs. OAM as Next Protocol (Re: Consensus call on encap proposals)
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: Tue, 09 Aug 2016 22:56:36 -0000

> Carlos,
>
> Thanks for the pointer, that looks like a good basis for an extensible
> and generic OAM inband measurement mechanism. I assume for IPv6 this
> would be appropriate as options in HBH extension headers, have you
> defined the formats for that?
>
>
> Thanks — and you are exactly right:
> https://tools.ietf.org/html/draft-brockners-inband-oam-transport-01#section-3
>
> This was demoed as IPv6 edge to edge in Bits-n-Bites in Berlin.
>
That's great and gives us the most flexibility. We can generically use
the OAM options in the extension headers of any IPv6 packet, or in the
case of GUE encapsulation we can put the options as the GUE payload
since the GUE header carries an IP protocol number as next protocol.

Thanks,
Tom