Re: [ippm] Heads up on draft-ietf-opsawg-yang-vpn-service-pm
Greg Mirsky <gregimirsky@gmail.com> Thu, 05 May 2022 13:38 UTC
Return-Path: <gregimirsky@gmail.com>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5ECF7C14F75F; Thu, 5 May 2022 06:38:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AyhteDUkCLxF; Thu, 5 May 2022 06:38:47 -0700 (PDT)
Received: from mail-lf1-x12c.google.com (mail-lf1-x12c.google.com [IPv6:2a00:1450:4864:20::12c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 37E79C14F720; Thu, 5 May 2022 06:38:47 -0700 (PDT)
Received: by mail-lf1-x12c.google.com with SMTP id p10so7510677lfa.12; Thu, 05 May 2022 06:38:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=fOfRRjKgSy7Fx9P8JAK5ZqA9iTe2VqtTuiiKpAJi41I=; b=mJDXq9jDw79hfI4FiUPKCDXtN/im60AWTWz5mdicrqcKxcRfguNJ9DXFw1tLQ9cNZZ 3k0d2bdInOU2Up4VjHruurmfIdUXMc3Oad34l/0MJr1lkezuLn3L/S2HGstJdVL36N0v jxFHOgdfXOdAq+1nwRSDAv5O+nDNSNKnou379+x43UHvjiM9/4zfetsQefH+VoVLk9WG 9bXbrJ7qnUSlEx5U3OVTAwTRHcqxl2CKDJyUz2dYcQmNuDsEQLqktyfxbRcgYy5prwQ5 PdjmMR16V/56BUnfY1Izrbe09mRsSjU/ByO9EbyM9R8FIEy/OGnoCUFjErf50QknR25t GQdA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=fOfRRjKgSy7Fx9P8JAK5ZqA9iTe2VqtTuiiKpAJi41I=; b=z5C/ebeNvYboCkDjpjJphYHNNxtdAMnbbS0FvKFQPGJEhj0YFhhohAD9qNTYvbe1Ao 1L3GelUMOW+9oJnANNziooFM8HskUKfsYDdeicZmcNrVE8iO6mVNystowULD69cgEu3I lH4zuo8fL87WZOG0pBGeGm8O439+mH6zmDsQ3gX05QWbSLJ7JRTxiE3innZ8E8KwILKp EE9t7jBprGGD7uikbFD/zc12UUPM+VESezMUn4O+z7X4exQNou9Two5FUDVA9/fklFG7 55dNaHT3e266uMDapxJZCovvR8mloA3oVpdcYTmOxTt46X+IRdNE3F0qnO9shX5hXJRd VQGg==
X-Gm-Message-State: AOAM533vNypx6fh3s9nHlOFYJGgeOnhTJsdOA4eOIg3uKnOHwBEtNlwJ FLinix//v1jhsnscBR9r3cGeF+PtwTHeSFHqdOA=
X-Google-Smtp-Source: ABdhPJy/3jnJEGPJHA/pjnlCAabHRGWd9Rk0SwV5XWe1n/4kpZiDEFfhLc0JMbYi09+vpffQz0iylYKiRmzFfJHrY1U=
X-Received: by 2002:a05:6512:12c3:b0:473:c7e2:b46b with SMTP id p3-20020a05651212c300b00473c7e2b46bmr4393501lfg.382.1651757925083; Thu, 05 May 2022 06:38:45 -0700 (PDT)
MIME-Version: 1.0
References: <09bc01d85c12$c6906c30$53b14490$@olddog.co.uk> <CA+RyBmVQv-cEPjAsY7_gGhjj9Hdq1RmA2Km8w49k7_Xd5-ajzA@mail.gmail.com> <935f25105da8466883da5a699b0b71f0@huawei.com>
In-Reply-To: <935f25105da8466883da5a699b0b71f0@huawei.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Thu, 05 May 2022 06:38:33 -0700
Message-ID: <CA+RyBmW7gciQ6K0wFsjA+tj3Ljaddh7Lba0iu5MNeanHWwdePQ@mail.gmail.com>
To: "Wubo (lana)" <lana.wubo@huawei.com>
Cc: Adrian Farrel <adrian@olddog.co.uk>, IETF IPPM WG <ippm@ietf.org>, opsawg <opsawg@ietf.org>, "draft-ietf-opsawg-yang-vpn-service-pm@ietf.org" <draft-ietf-opsawg-yang-vpn-service-pm@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000612db405de43dce4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/hJ0jvg4jy_LFrtxV_VslxL49P88>
Subject: Re: [ippm] Heads up on draft-ietf-opsawg-yang-vpn-service-pm
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 May 2022 13:38:48 -0000
Hi Bo, thank you for your quick response to my comment and clarification. The updates fully address my comments. Regards, Greg On Thu, May 5, 2022 at 5:46 AM Wubo (lana) <lana.wubo@huawei.com> wrote: > Hi Greg, > > > > Thanks for the comments. STAMP referenced as RFC 8762 has been added as > one of PM measurement protocol. > > Please be aware this model is a network model and does not specifies the > details of STAMP. > > Please check whether rev-08 addresses your concerns: > > > https://www.ietf.org/rfcdiff?url2=draft-ietf-opsawg-yang-vpn-service-pm-08 > > > > Thanks, > > Bo > > *From:* Greg Mirsky [mailto:gregimirsky@gmail.com] > *Sent:* Wednesday, May 4, 2022 4:54 AM > *To:* Adrian Farrel <adrian@olddog.co.uk> > *Cc:* IETF IPPM WG <ippm@ietf.org>; opsawg <opsawg@ietf.org>; > draft-ietf-opsawg-yang-vpn-service-pm@ietf.org > *Subject:* Re: [ippm] Heads up on draft-ietf-opsawg-yang-vpn-service-pm > > > > Hi Adrian, > > thank you for bringing this work to my attention. I've read and shared my > comments earlier. The authors responded promptly and we've worked together > to address my comments. After reading the current version I have a question > about the importance of identifying the particular active measurement > protocol used to measure the reported performance metrics. If reporting the > protocol used for the performance measurement is deemed essential to > characterize the accuracy of the measurement method, then I would propose > to consider several additions to the model: > > · adding STAMP described in RFCs 8762 and 8972 to the list of > active measurement methods > > · adding Error Estimate for Session-Sender and > Session-Reciever/Session-Reflector for OWAMP, TWAMP, and STAMP > > Thank you for your kind consideration. > > > > Regards, > > Greg > > > > On Fri, Apr 29, 2022 at 2:48 PM Adrian Farrel <adrian@olddog.co.uk> wrote: > > Hi, > > I'm the document shepherd for draft-ietf-opsawg-yang-vpn-service-pm. It has > completed WG last call in the OPSAWG. > > The work may be of interest to IPPM and you might want to watch out for the > IETF last call which will be along in due course. > > But I'm sure that the authors would welcome any comments you have at any > time. > > Best, > Adrian > > _______________________________________________ > ippm mailing list > ippm@ietf.org > https://www.ietf.org/mailman/listinfo/ippm > >
- [ippm] Heads up on draft-ietf-opsawg-yang-vpn-ser… Adrian Farrel
- Re: [ippm] Heads up on draft-ietf-opsawg-yang-vpn… Greg Mirsky
- Re: [ippm] Heads up on draft-ietf-opsawg-yang-vpn… Wubo (lana)
- Re: [ippm] Heads up on draft-ietf-opsawg-yang-vpn… Greg Mirsky