Subject: Re: [ippm] New Version Notification for draft-li-ippm-otwamp-on-lag-02.txt

From: Tianran Zhou <[email-masked]>
Date: Mon, 7 Feb 2022 01:25:18 +0000

Hi Henrik,

This draft follows the same pattern as RFC7130, where BFD is also a protocol over UDP, and applied to LAG.
I am not sure if I can agree with you that TWAMP is layer-3, nor an odd choice for LAG.
For the Y.1731, would you like to shed light how it could apply? So that we can compare.

Thanks,
Tianran

From: Henrik Nydell [mailto:[email-masked]]
Sent: Monday, January 31, 2022 8:56 PM
To: [email-masked]
Cc: Tianran Zhou <[email-masked]>; Giuseppe Fioccola <[email-masked]>; ippm <[email-masked]>
Subject: Re: Re: [ippm] New Version Notification for draft-li-ippm-otwamp-on-lag-02.txt

Yes, that is understood, which is why I think TWAMP (being layer-3) is an odd choice for this. A layer-2 test like Y.1731 would be more suitable to monitor performance of individual LAG links.

On Sat, Jan 29, 2022 at 10:28 AM [email-masked]<mailto:[email-masked]> <[email-masked]<mailto:[email-masked]>> wrote:
Hello Henrik and all,

We considered the situation you mentioned. Becase it is difficult to traverse all the possible link combinations, i.e. the number of possible substreams is huge, we try to address LAG that directly connects two devices first.

________________________________
Best Regards,
Zhenqiang Li

[email-masked]<mailto:[email-masked]>

From: Henrik Nydell<mailto:[email-masked]>
Date: 2022-01-28 19:56
To: Tianran Zhou<mailto:zhoutianran=[email-masked]>
CC: Giuseppe Fioccola<mailto:giuseppe.fioccola=[email-masked]>; IETF IPPM WG \([email-masked]\)<mailto:[email-masked]>
Subject: Re: [ippm] New Version Notification for draft-li-ippm-otwamp-on-lag-02.txt
I still think it would be much better to generalize this micro TWAMP concept and not tie this to LAG, since that will be implementation specific - only if you implement TWAMP directly on a LAG-device this draft would apply.
Better then to generalize the concept and call the added identifier "Substream ID" or something similar. Then this draft would also apply to for example a vendor that implements routing over different paths or as Tianran pointed out, MPLS-SR uses. Thus I would propose removing all references to LAG in this draft and widen the scope to any situation where there would be uses for labelled (ID:ed) substreams between the same TWAMP-sender and session-reflector.

On Fri, Jan 28, 2022 at 12:15 PM Tianran Zhou <zhoutianran=[email-masked]<mailto:[email-masked]>> wrote:
Hi Giuseppe,

Thanks very much for your review.
I will incorporate your suggestions in the next revision.

Cheers,
Tianran

-----Original Message-----
From: ippm [mailto:[email-masked]<mailto:[email-masked]>] On Behalf Of Giuseppe Fioccola
Sent: Friday, January 28, 2022 7:03 PM
To: Tianran Zhou <zhoutianran=[email-masked]<mailto:[email-masked]>>; IETF IPPM WG ([email-masked]<mailto:[email-masked]>) <[email-masked]<mailto:[email-masked]>>
Subject: Re: [ippm] New Version Notification for draft-li-ippm-otwamp-on-lag-02.txt

Hi Tianran, All,
I think that this is a useful work.
For LAG, the use of active methods (OWAMP, TWAMP, STAMP) can also complement passive and hybrid methods. Indeed, the extensions proposed in this draft allow to monitor all the links and not only the link crossed by the observed packet stream.
Maybe, you can also highlight this point in the introduction section.

Minor nits:
s/Reflector Member Link ID fields/Reflector Member Link ID field/

s/When sending a response to the received Test packet, the micro TWAMP Session-Sender/ When sending a response to the received Test packet, the micro TWAMP Session- Reflector/

Regards,

Giuseppe

-----Original Message-----
From: ippm <[email-masked]<mailto:[email-masked]>> On Behalf Of Tianran Zhou
Sent: Monday, January 24, 2022 7:23 AM
To: IETF IPPM WG ([email-masked]<mailto:[email-masked]>) <[email-masked]<mailto:[email-masked]>>
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: [email-masked]<mailto:[email-masked]> [mailto:[email-masked]<mailto:[email-masked]>]
Sent: Monday, January 24, 2022 2:17 PM
To: Greg Mirsky <[email-masked]<mailto:[email-masked]>>; Guo Jun <[email-masked]<mailto:[email-masked]>>; Jun Guo <[email-masked]<mailto:[email-masked]>>; Rakesh Gandhi <[email-masked]<mailto:[email-masked]>>; Tianran Zhou <[email-masked]<mailto:[email-masked]>>; Zhenqiang Li <[email-masked]<mailto:[email-masked]>>
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
[email-masked]<mailto:[email-masked]>
https://www.ietf.org/mailman/listinfo/ippm

_______________________________________________
ippm mailing list
[email-masked]<mailto:[email-masked]>
https://www.ietf.org/mailman/listinfo/ippm

_______________________________________________
ippm mailing list
[email-masked]<mailto:[email-masked]>
https://www.ietf.org/mailman/listinfo/ippm

--

Henrik Nydell
Sr Product Manager
1.866.685.8181
[email-masked]<mailto:[email-masked]>
[https://i.xink.io/Images/Get/N63832/a65.png]<http://accedian.com/>
[https://i.xink.io/Images/Get/N63832/f97.png]<https://www.facebook.com/accedian/> [https://i.xink.io/Images/Get/N63832/t99.png] <https://twitter.com/Accedian>  [https://i.xink.io/Images/Get/N63832/l54.png] <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
[email-masked]<mailto:[email-masked]>
[https://i.xink.io/Images/Get/N63832/a65.png]<http://accedian.com>
[https://i.xink.io/Images/Get/N63832/f97.png]<https://www.facebook.com/accedian/> [https://i.xink.io/Images/Get/N63832/t99.png] <https://twitter.com/Accedian>  [https://i.xink.io/Images/Get/N63832/l54.png] <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.