IETF Logo Mail Archive

Re: [Rtg-ooam-dt] Moving Overlay OAM forward ?

Greg Mirsky <gregimirsky@gmail.com> Mon, 19 September 2016 18:05 UTC

Return-Path: <gregimirsky@gmail.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 11F6012B4CD for <rtg-ooam-dt@ietfa.amsl.com>; Mon, 19 Sep 2016 11:05:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham 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 butVxv0-25rH for <rtg-ooam-dt@ietfa.amsl.com>; Mon, 19 Sep 2016 11:05:17 -0700 (PDT)
Received: from mail-yw0-x236.google.com (mail-yw0-x236.google.com [IPv6:2607:f8b0:4002:c05::236]) (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 B278712B4C7 for <rtg-ooam-dt@ietf.org>; Mon, 19 Sep 2016 11:05:17 -0700 (PDT)
Received: by mail-yw0-x236.google.com with SMTP id g192so160190170ywh.1 for <rtg-ooam-dt@ietf.org>; Mon, 19 Sep 2016 11:05:17 -0700 (PDT)
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; bh=hNPIijAlepLiE6CQI1U0of+uKkLSyaPI64JMtaRTRTk=; b=Rl7YVZg24nb7okM11lh6CFkBxmsdGL6foCW3eGGRshlTgnn4tphchgjxtESN+ChAIC ZyveB+IiGkLyDT2oaFTgP2raDhaxoVQu+JIldrbpZv0iPKNTvjCDfdn1jYz1UbU5PZn9 0Ihy+sH6IzqokXNCj95F88DCa4T8VPon9kuczj670tmv4ZJ2uhxpeCaqLDdjeX2H6sA5 uAQF6LsipvqOvGK8EnaGDPWPordebHI/kVY15CxOe1zg+TNJXKTs938mU/i81zmMgfYx 76c7TNIhmwhn+NLIM3qH9oGj5bBxbOF6GWE3hgBkey6B6RSK6z8RltNdlABPEuzB+bwO gP4A==
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; bh=hNPIijAlepLiE6CQI1U0of+uKkLSyaPI64JMtaRTRTk=; b=fPYWopo40E88zXxre0fDXyQWW7KUXoh2csSrLRPi1wQCjD9J7qlUZ+EOplWXYjAhul o5BoxBLxqhw9blMYZc1dcZcGHdIys1/uhEbIAH+zaVaqMfG4uRYpzy2WC8vH2NDsmC7W e95SgseyJrW6ErFR4kB9TFUKr6BNBuZ7fNtR8rC+QydDQTG3MWtnxkJjNSiZ1gKB/Z4L y8z8iZPOIhBJJ3k7AOdVkgsuCsyv4+QTlb2BojVEc7OjQKuRZsyGe/U6ObS9aXooxYM3 kqCO/p19lXecuxmAtHcPwyP6+wXOUCVWvGKrzIuFIi6U2cAtIKDfpUJLnkkSGbVe4ZGm 4NNw==
X-Gm-Message-State: AE9vXwNUfJZtetgMsXt0rl9j8JE+POP5tougVKDxuCrIBrk7y4SHUnoSF3mkvkBevDyG+hUsM27A76mvzulsfg==
X-Received: by 10.129.155.17 with SMTP id s17mr28771127ywg.203.1474308316967; Mon, 19 Sep 2016 11:05:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.172.134 with HTTP; Mon, 19 Sep 2016 11:05:16 -0700 (PDT)
In-Reply-To: <E8355113905631478EFF04F5AA706E98310D4D1D@wtl-exchp-2.sandvine.com>
References: <E8355113905631478EFF04F5AA706E98310D4D1D@wtl-exchp-2.sandvine.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Mon, 19 Sep 2016 11:05:16 -0700
Message-ID: <CA+RyBmVCeivcPwasZX+VQMU8d87q4WNDkxajY0h7BE=SqQQ1MA@mail.gmail.com>
To: Dave Dolson <ddolson@sandvine.com>
Content-Type: multipart/alternative; boundary="94eb2c0b8c9885bff2053ce02748"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-ooam-dt/p0WddBwDVYNRHhMJ6ZqZoE9Do8Q>
Cc: "rtg-ooam-dt@ietf.org" <rtg-ooam-dt@ietf.org>
Subject: Re: [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 18:05:19 -0000

Hi Dave,
thank you for your questions and please share your ideas, proposals.
I don't know where, i.e. which WG, would be home for this and other OOAM-DT
documents. I think that there is enough substantive work that should be
done in Overlay OAM, including active OAM methods, ability to perform
meaningful monitoring and performance measurement as by passive method and
newer group of OAM methods, a.k.a. iOAM. Would appreciate if members of the
list share their thoughts on that and indicate their willingness to work
over these three weeks to form agenda for the BoF in Seoul.

Regards, Greg

On Mon, Sep 19, 2016 at 10:54 AM, Dave Dolson <ddolson@sandvine.com> wrote:

> 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 mailing list
> Rtg-ooam-dt@ietf.org
> https://www.ietf.org/mailman/listinfo/rtg-ooam-dt
>
>

v2.23.0 | Report a Bug | By Email