Re: [ippm] FW: New Version Notification for draft-li-ippm-otwamp-on-lag-02.txt
Henrik Nydell <hnydell@accedian.com> Thu, 27 January 2022 09:29 UTC
Return-Path: <hnydell@accedian.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 DA9AF3A1B36 for <ippm@ietfa.amsl.com>; Thu, 27 Jan 2022 01:29:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.088
X-Spam-Level:
X-Spam-Status: No, score=-2.088 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=accedian.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 PUbbQ5H9VE25 for <ippm@ietfa.amsl.com>; Thu, 27 Jan 2022 01:28:59 -0800 (PST)
Received: from mail-yb1-xb2c.google.com (mail-yb1-xb2c.google.com [IPv6:2607:f8b0:4864:20::b2c]) (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 360A73A1B9A for <ippm@ietf.org>; Thu, 27 Jan 2022 01:28:53 -0800 (PST)
Received: by mail-yb1-xb2c.google.com with SMTP id 23so6743947ybf.7 for <ippm@ietf.org>; Thu, 27 Jan 2022 01:28:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=accedian.com; s=corp1; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Wu5+8rXRXimXit5rwWHcLysWhl0r/qmNajOAK2EpxoM=; b=O6XmBxoOuCpwsSG+UyNFkoyE9U1QCx73JKYOkrBLW9Q9Ot6hpkjL8BRc9I1kTXO0Hj 8yHAnMhBhFuq/CVkHg3+zJR8AQwvhAibPC8vcbqcpaI6hAF8NhQn7hM++1aiXJiEOtWJ lVcgTm0ZxqKb5y2hgOFgymfzxNTCXyqg592uIp7gM7WbqXpby5dGeCZmbn7nhI1R7b0c 4UFjV/e6jtj8ozSPz/O7r2q/DO1jcI6ncqqFZATL4hTpsRTJ0DTicSqMXBN+4j5ROC6W xXIVFYD974cn2AmepMHE5YIfrEjAR3g5X+P/0+6d6dzThQZu41EaykFT17D/tghPp4x4 KCLg==
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=Wu5+8rXRXimXit5rwWHcLysWhl0r/qmNajOAK2EpxoM=; b=H1hx2KvkECI/HrIaEdxBtUoOKNAXLm+Jajf8cP668KvL/SX97fBvUuumfG3xjVeRlt vAxH10jWoGd4pyA3yrnq0vv03LVYqiQUZpZ0vwIBFJkm2pxG6b/2SXW6wGXqVqcyH8lz 6AGjBFNBnda705TtQ2VXAfxmTkVYtJ6ZqoAEp1CMKdNZoi7qFl/TURErJDm+sQUfCDvK lT1NQIsXwQPykKDIz//T5sZgbtRimkdLjhi+SHydjsAylznoqcdjDN5ht2O+dPbXuc65 nFM7qBpP9+6npVpahYTz7so4aefQMw81f9uCbEwLOnxpxF4j8z2gTwmFKM/lLlXJWH/8 DsvA==
X-Gm-Message-State: AOAM533W5ixiB2N/fZaq+oogxmVeTi28jDjNUCpgit8Egj4Hw91vznI2 rFg/GJ9Hg1cRnKc3IE48j1tQKqXhXnu5631a8ZTWMItLiNqxJ/pp8ITO650zzfBqqiQXYqaM1wg gdLOB7dpm/CiDeCh+Ww==
X-Google-Smtp-Source: ABdhPJzFhNlblwAQekhf3SRFEB+2tgIsHRyIbFN7FdPxGcJPDn4ZhsxhEjFB1KeHyJ10E/WLzzblx3myRmaoJZpxAL4=
X-Received: by 2002:a05:6902:1028:: with SMTP id x8mr2061702ybt.716.1643275731325; Thu, 27 Jan 2022 01:28:51 -0800 (PST)
MIME-Version: 1.0
References: <164300504281.12619.16642699818590435984@ietfa.amsl.com> <f3bb01f8591e43e885d8a110f2d96e66@huawei.com> <015a01d81295$fdd37370$f97a5a50$@chinatelecom.cn> <70c388c86215411796ef55d48711b216@huawei.com> <CALhTbprmCqvSUPgMfR4BxkY=DzVsxJqc82CRHn_gKFR4qqLRRA@mail.gmail.com> <3a33416375314462af22d1837e8472dc@huawei.com>
In-Reply-To: <3a33416375314462af22d1837e8472dc@huawei.com>
From: Henrik Nydell <hnydell@accedian.com>
Date: Thu, 27 Jan 2022 10:28:34 +0100
Message-ID: <CALhTbpqMLRFEky0Z-2q22R7GuhU0+USLdDNp9vr1nT2MOO2Vjw@mail.gmail.com>
To: Tianran Zhou <zhoutianran@huawei.com>
Cc: "wangaj3@chinatelecom.cn" <wangaj3@chinatelecom.cn>, IETF IPPM WG <ippm@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003bee0a05d68cf297"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/3dxPFAovRvWSq98eFQmRRv0pZCQ>
Subject: Re: [ippm] FW: New Version Notification for draft-li-ippm-otwamp-on-lag-02.txt
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.29
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, 27 Jan 2022 09:29:04 -0000
Thanks for the clarification, but this "member link validation mechanism" depends fully on configuration between the session sender and the session reflector right? So even if they have agreed that a certain session ID belongs to lag link A, there is no way to be sure that this is the case, the intermediate switches may place these packets randomly over links A-C and the TWAMP/OWAMP sender/reflectors will have no knowledge of this. So I dont know if this addition adds much usefulnes over the already existing capabilities of TWAMP, where you can use the 5-tuple of port-pair, IP-pair and TOS to differentiate session from each other. On Thu, Jan 27, 2022 at 2:37 AM Tianran Zhou <zhoutianran@huawei.com> wrote: > Hi Henrik, > > > > Thanks very much for your review. > > Your perspective is absolutely correct. > > This draft is not able to “guarantee” a specific LAG path. For example, > there is a switch between the two end points, or in the case the reflector > is not capable. > > I.e., as you said, there is no "one method fits all" to guarantee the path. > > > > However, this draft seek another way round, the member link validation > mechanism. > > There is an assumption in the introduction “This document intends to > address the scenario where a LAG directly connects two nodes (A and B).” > > With the member link validation, sender/reflector will drop measurement > data, when the test packet is not from the expected member link. > > In this way, the measurement could always be correct. > > > > This is somewhat similar to Paris Traceroute ( > https://paris-traceroute.net/about/) IMHO. > > > > Cheers, > > Tianran > > > > *From:* Henrik Nydell [mailto:hnydell@accedian.com] > *Sent:* Wednesday, January 26, 2022 6:17 PM > *To:* Tianran Zhou <zhoutianran@huawei.com> > *Cc:* wangaj3@chinatelecom.cn; IETF IPPM WG <ippm@ietf.org> > *Subject:* Re: [ippm] FW: New Version Notification for > draft-li-ippm-otwamp-on-lag-02.txt > > > > I had a brief review but failed to find details on how the TWAMP sessions > would be "guaranteed" to travel on a certain LAG segment. As far as I know > the LAG implementation may be different between vendors and as such I know > of no "one method fits all" to actually accomplish the measurement. > > > > So this draft does not actually provide any solution to the problem of > being able to measure LAG segments separately and deterministically. > > > > On Wed, Jan 26, 2022 at 11:03 AM Tianran Zhou <zhoutianran= > 40huawei.com@dmarc.ietf.org> wrote: > > Hi Anjun, > > Thanks very much for your interest and comments. > Both are good questions. > Please see in line. > > Cheers, > Tianran > > -----Original Message----- > From: wangaj3@chinatelecom.cn [mailto:wangaj3@chinatelecom.cn] > Sent: Wednesday, January 26, 2022 5:21 PM > To: Tianran Zhou <zhoutianran@huawei.com>; 'IETF IPPM WG' <ippm@ietf.org> > Subject: RE: [ippm] FW: New Version Notification for > draft-li-ippm-otwamp-on-lag-02.txt > > Hi, Tianran: > > Have a brief review of this draft. I think its aim is straightforward and > will be useful to utilize the member link within the LAG. > Some comments are below: > 1) It seems there is no Sender/Reflector behavior description for the > Mirco OWAMP session and the packet format? > > > ZTR> OWAMP is simple and there is no reflector. The sender cannot get the > ack from the receiver. So we are not going to extend the OWAMP test packet. > The behavior is described in section 3.2: > " The micro OWAMP Sender MUST send the micro OWAMP-Test packets over the > member link with which the session is associated. When receives a Test > packet, the micro OWAMP receiver MUST use the member link from which the > Test packet is received to correlate the micro OWAMP session. If there is > no such a session, the Test packet MUST be discarded. " > > 2) For the newly defined Session-Sender Packet/Session-Reflector Packet, > how to assure the backward compatibility? What I have seen is that you add > two additional fields within the existing Packet? > > ZTR> I am not aware of the compatibility problem. If a node supports micro > session, it can understand the new packet extension. If a node does not > support micro session, it just ignores the new fields. Because the new > fields is in the reserved zone. > Moreover, the validation mechanism can figure out if the reflector can > support the micro session. > > Best Regards > > Aijun Wang > China Telecom > > -----Original Message----- > From: ippm <ippm-bounces@ietf.org> On Behalf Of Tianran Zhou > Sent: Monday, January 24, 2022 2:23 PM > To: IETF IPPM WG (ippm@ietf.org) <ippm@ietf.org> > Subject: [ippm] FW: New Version Notification for > draft-li-ippm-otwamp-on-lag-02.txt > > Hi WG, > > We think this is an useful work on adapting OWAMP/TWAMP in LAG performance > measurement. > We updated this draft based on the comments from the meeting discussion > and mailing list. > Thanks for all the suggestions. > More reviews and comments are welcome. > > Cheers, > Tianran > > -----Original Message----- > From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] > Sent: Monday, January 24, 2022 2:17 PM > To: Greg Mirsky <gregimirsky@gmail.com>; Guo Jun <guo.jun2@zte.com.cn>; > Jun Guo <guo.jun2@zte.com.cn>; Rakesh Gandhi <rgandhi@cisco.com>; Tianran > Zhou <zhoutianran@huawei.com>; Zhenqiang Li <li_zhenqiang@hotmail.com> > Subject: New Version Notification for draft-li-ippm-otwamp-on-lag-02.txt > > > A new version of I-D, draft-li-ippm-otwamp-on-lag-02.txt > has been successfully submitted by Tianran Zhou and posted to the IETF > repository. > > Name: draft-li-ippm-otwamp-on-lag > Revision: 02 > Title: One-way/Two-way Active Measurement Protocol Extensions for > Performance Measurement on LAG > Document date: 2022-01-24 > Group: Individual Submission > Pages: 13 > URL: > https://www.ietf.org/archive/id/draft-li-ippm-otwamp-on-lag-02.txt > Status: > https://datatracker.ietf.org/doc/draft-li-ippm-otwamp-on-lag/ > Htmlized: > https://datatracker.ietf.org/doc/html/draft-li-ippm-otwamp-on-lag > Diff: > https://www.ietf.org/rfcdiff?url2=draft-li-ippm-otwamp-on-lag-02 > > Abstract: > This document defines extensions to One-way Active Measurement > Protocol (OWAMP), and Two-way Active Measurement Protocol (TWAMP) to > implement performance measurement on every member link of a Link > Aggregation Group (LAG). Knowing the measured metrics of each member > link of a LAG enables operators to enforce the performance based > traffic steering policy across the member links. > > > > > > The IETF Secretariat > > > _______________________________________________ > ippm mailing list > ippm@ietf.org > https://www.ietf.org/mailman/listinfo/ippm > > _______________________________________________ > ippm mailing list > ippm@ietf.org > https://www.ietf.org/mailman/listinfo/ippm > > > > > -- > > > *Henrik Nydell* > *Sr Product Manager* > 1.866.685.8181 > hnydell@accedian.com > <http://accedian.com> > <https://www.facebook.com/accedian/> <https://twitter.com/Accedian> > <https://ca.linkedin.com/company/accedian> > <http://www.accedian.com> > *accedian.com <http://accedian.com>* > > > > Avis de confidentialité > > Les informations contenues dans le présent message et dans toute pièce qui > lui est jointe sont confidentielles et peuvent être protégées par le secret > professionnel. Ces informations sont à l’usage exclusif de son ou de ses > destinataires. Si vous recevez ce message par erreur, veuillez s’il vous > plait communiquer immédiatement avec l’expéditeur et en détruire tout > exemplaire. De plus, il vous est strictement interdit de le divulguer, de > le distribuer ou de le reproduire sans l’autorisation de l’expéditeur. > Merci. > > Confidentiality notice > > This e-mail message and any attachment hereto contain confidential > information which may be privileged and which is intended for the exclusive > use of its addressee(s). If you receive this message in error, please > inform sender immediately and destroy any copy thereof. Furthermore, any > disclosure, distribution or copying of this message and/or any attachment > hereto without the consent of the sender is strictly prohibited. Thank you. > -- *Henrik Nydell* *Sr Product Manager* 1.866.685.8181 hnydell@accedian.com <http://accedian.com> <https://www.facebook.com/accedian/> <https://twitter.com/Accedian> <https://ca.linkedin.com/company/accedian> <http://www.accedian.com> *accedian.com <http://accedian.com>* -- Avis de confidentialité Les informations contenues dans le présent message et dans toute pièce qui lui est jointe sont confidentielles et peuvent être protégées par le secret professionnel. Ces informations sont à l’usage exclusif de son ou de ses destinataires. Si vous recevez ce message par erreur, veuillez s’il vous plait communiquer immédiatement avec l’expéditeur et en détruire tout exemplaire. De plus, il vous est strictement interdit de le divulguer, de le distribuer ou de le reproduire sans l’autorisation de l’expéditeur. Merci. Confidentiality notice This e-mail message and any attachment hereto contain confidential information which may be privileged and which is intended for the exclusive use of its addressee(s). If you receive this message in error, please inform sender immediately and destroy any copy thereof. Furthermore, any disclosure, distribution or copying of this message and/or any attachment hereto without the consent of the sender is strictly prohibited. Thank you.
- [ippm] FW: New Version Notification for draft-li-… Tianran Zhou
- Re: [ippm] New Version Notification for draft-li-… Mach Chen
- Re: [ippm] New Version Notification for draft-li-… Jeff Tantsura
- Re: [ippm] New Version Notification for draft-li-… Tianran Zhou
- Re: [ippm] New Version Notification for draft-li-… Haoyu Song
- Re: [ippm] FW: New Version Notification for draft… Aijun Wang
- Re: [ippm] FW: New Version Notification for draft… Tianran Zhou
- Re: [ippm] FW: New Version Notification for draft… Henrik Nydell
- Re: [ippm] FW: New Version Notification for draft… Tianran Zhou
- Re: [ippm] FW: New Version Notification for draft… Henrik Nydell
- Re: [ippm] FW: New Version Notification for draft… Tianran Zhou
- Re: [ippm] FW: New Version Notification for draft… Henrik Nydell
- Re: [ippm] FW: New Version Notification for draft… Tianran Zhou
- Re: [ippm] FW: New Version Notification for draft… Henrik Nydell
- Re: [ippm] FW: New Version Notification for draft… Tianran Zhou
- Re: [ippm] FW: New Version Notification for draft… Henrik Nydell
- Re: [ippm] New Version Notification for draft-li-… Giuseppe Fioccola
- Re: [ippm] New Version Notification for draft-li-… Tianran Zhou
- Re: [ippm] New Version Notification for draft-li-… Henrik Nydell
- Re: [ippm] New Version Notification for draft-li-… Tianran Zhou
- Re: [ippm] New Version Notification for draft-li-… lizhenqiang@chinamobile.com
- Re: [ippm] New Version Notification for draft-li-… Henrik Nydell
- Re: [ippm] New Version Notification for draft-li-… Jeff Tantsura
- Re: [ippm] New Version Notification for draft-li-… Haoyu Song
- Re: [ippm] New Version Notification for draft-li-… Jeff Tantsura
- Re: [ippm] New Version Notification for draft-li-… Tianran Zhou
- Re: [ippm] New Version Notification for draft-li-… lizhenqiang@chinamobile.com
- Re: [ippm] New Version Notification for draft-li-… Jeff Tantsura
- Re: [ippm] FW: New Version Notification for draft… guo.jun2
- Re: [ippm] FW: New Version Notification for draft… xiao.min2
- Re: [ippm] FW: New Version Notification for draft… Tianran Zhou