IETF Logo Mail Archive

Re: [nvo3] What needs to be done about OAM?

Anoop Ghanwani <anoop@alumni.duke.edu> Tue, 10 April 2018 21:29 UTC

Return-Path: <ghanwani@gmail.com>
X-Original-To: nvo3@ietfa.amsl.com
Delivered-To: nvo3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D43481272E1 for <nvo3@ietfa.amsl.com>; Tue, 10 Apr 2018 14:29:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.398
X-Spam-Level:
X-Spam-Status: No, score=-1.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 r2wkVQGKaCWo for <nvo3@ietfa.amsl.com>; Tue, 10 Apr 2018 14:29:46 -0700 (PDT)
Received: from mail-qt0-x230.google.com (mail-qt0-x230.google.com [IPv6:2607:f8b0:400d:c0d::230]) (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 CEA751277BB for <nvo3@ietf.org>; Tue, 10 Apr 2018 14:29:45 -0700 (PDT)
Received: by mail-qt0-x230.google.com with SMTP id d50so15075297qtc.0 for <nvo3@ietf.org>; Tue, 10 Apr 2018 14:29:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=FA+tg5kIR4F/vW/F/okhyp1FaE0zE0hRGXIKk+7IxDc=; b=OqSVqywKHFhUN9wsA46+W0WmH/x8qiTvg285EX4LIPlJISWlpPeuirdrz8a5XXzqZP gpruFF4kWYXZXGRb8LkpMwL6Fhw/ZVBpnUQ4SJCVMylUOhluxnQZi0Eh4YjKVq4HH9j+ 68kN95pnNJPWB/3gumKwUHVHl9b///B2rd8wVrOvFYoNwFW4obRK9e2n/baUmNhUg5UB xjXfo8gPvpIOVfGddwfSs/IvNpAqHiqmwPD6ZyjjZhXTw5igg+RwZ2bFCveqEuu6mTIP 48vn9TQLzSWs5S1KUtURO2xreBsHh2uX9fNS/MRCZk4yM1fUh+djCJFugkTC7bNtosV+ +hNw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=FA+tg5kIR4F/vW/F/okhyp1FaE0zE0hRGXIKk+7IxDc=; b=XcqejLb02mLL9cusUI20VWi4GRGvypFCYVDEewjgDojeD+VlZKqwX7snSzzuy9XhSC XceN9hoGK9rBaovmNA+8XfLZEMSWp7NELSmKUkixUrmEtKew/ma1r+hcTXpVbC7KlEGU UWspZP4vypCbBZc0FPEcaNxYrrcu33wbcC4j8DU2/ftzZq/VzlzV52ZmvUFm8DEv44kZ Nk/rj96AQK/ti0FTQt54FOiVvtN9NYOBRyltNgVP5W1EcpiYAensgr48k12KoaztnmOm rYPerhX+yQ8hNnOWJxuUs9Okoz15OWZuJ0IoBERLU7WFH3vYO3xfOn3VpK3WDoWV+vuM jEyw==
X-Gm-Message-State: ALQs6tCrNyvZlw88d0TniqI3jOWhilYjLPbyRI3nQDyTjEHwZOdU1mQk bXO+3maSmHpBAtXV3+YwoPfzzJInEGUsgqoveRrgfw==
X-Google-Smtp-Source: AIpwx4+GIMyDauAE7LG4Hyr6dV2akp/7nBMSD3p/YMo42B9aSspqqZg5gKkKgEnMURQ8XwfpVY/hNiOIJWsfbjXMIBs=
X-Received: by 10.200.24.248 with SMTP id o53mr3330659qtk.79.1523395784922; Tue, 10 Apr 2018 14:29:44 -0700 (PDT)
MIME-Version: 1.0
Sender: ghanwani@gmail.com
Received: by 10.200.58.227 with HTTP; Tue, 10 Apr 2018 14:29:44 -0700 (PDT)
In-Reply-To: <49F4ECC0-53E6-4B60-8B97-1FEF69CB3BA3@nokia.com>
References: <87fu4914fc.fsf@hobgoblin.ariadne.com> <49F4ECC0-53E6-4B60-8B97-1FEF69CB3BA3@nokia.com>
From: Anoop Ghanwani <anoop@alumni.duke.edu>
Date: Tue, 10 Apr 2018 14:29:44 -0700
X-Google-Sender-Auth: x0-o7ts7mGCHckuqpKj2tOgFkC0
Message-ID: <CA+-tSzwsfbmegXj9B6jBDoDHEv8P5q5P5i7+6kNObcTCgCokbw@mail.gmail.com>
To: "Bocci, Matthew (Nokia - GB)" <matthew.bocci@nokia.com>
Cc: "Dale R. Worley" <worley@ariadne.com>, "nvo3@ietf.org" <nvo3@ietf.org>
Content-Type: multipart/alternative; boundary="001a114fe4f69cda8a056985382c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nvo3/rsbl-st9FD_nAK-oy4pbAklq2Ng>
Subject: Re: [nvo3] What needs to be done about OAM?
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Network Virtualization Overlays \(NVO3\) Working Group" <nvo3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nvo3>, <mailto:nvo3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nvo3/>
List-Post: <mailto:nvo3@ietf.org>
List-Help: <mailto:nvo3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nvo3>, <mailto:nvo3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Apr 2018 21:29:50 -0000

This is a more recent version:
https://tools.ietf.org/html/draft-ashwood-nvo3-oam-requirements-04

See also these drafts:
https://tools.ietf.org/html/draft-tissa-nvo3-oam-fm-04
https://tools.ietf.org/html/draft-singh-nvo3-vxlan-router-alert-02
https://tools.ietf.org/html/draft-nordmark-nvo3-transcending-traceroute-03

IIRC, there was an NVO3 OAM design team that was formed and we met
virtually at least a couple of times and then the effort died off.

Then there was another effort around OAM for overlays in the RTGWG.
https://tools.ietf.org/html/draft-ooamdt-rtgwg-ooam-requirement-02

And finally, BFD over VXLAN:
https://tools.ietf.org/html/draft-ietf-bfd-vxlan-00

I haven't been following stuff closely, so I may have missed some related
work.

Thanks,
Anoop




On Tue, Apr 10, 2018 at 5:22 AM, Bocci, Matthew (Nokia - GB) <
matthew.bocci@nokia.com> wrote:

> Dale
>
> There was a draft on OAM requirements in the working group a few years
> ago, but this somewhat fell by the wayside.
>
> https://www.ietf.org/archive/id/draft-ashwood-nvo3-
> operational-requirement-03.txt
>
> It may be a good time for an interested participant to pick this up again.
>
> Matthew
>
>
> On 06/04/2018, 02:58, "nvo3 on behalf of Dale R. Worley" <
> nvo3-bounces@ietf.org on behalf of worley@ariadne.com> wrote:
>
>     My apologies, but I'm new here.  There has been various discussion
> about
>     OAM packets, but what I've seen has been fairly vague -- the O bit in
>     Geneve and a proposal for an OAM encapsulation that was not detailed
>     about what application-level information the encapsulation would carry.
>
>     Is there solid information about what OAM is to achieve and what is
>     necessary to achieve it?  Or is that a discussion that we really need
> to
>     have?
>
>     I can see various different ways of opening up the subject.  One is to
>     show clearly useful implementations, and from that, start to abstract
>     the functions that they perform.  Conversely, we can show functions for
>     which there is a need, and start to work out implementations.
>
>     Dale
>
>     _______________________________________________
>     nvo3 mailing list
>     nvo3@ietf.org
>     https://www.ietf.org/mailman/listinfo/nvo3
>
>
> _______________________________________________
> nvo3 mailing list
> nvo3@ietf.org
> https://www.ietf.org/mailman/listinfo/nvo3
>

v2.23.0 | Report a Bug | By Email