Re: [ippm] Updates to twamp light/stamp messages

xiao.min2@zte.com.cn Thu, 12 March 2020 02:15 UTC

Return-Path: <xiao.min2@zte.com.cn>
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 DCECC3A0365; Wed, 11 Mar 2020 19:15:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 ljB_6JYxIEBk; Wed, 11 Mar 2020 19:15:28 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.217.80.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 778AD3A00E1; Wed, 11 Mar 2020 19:14:53 -0700 (PDT)
Received: from mxct.zte.com.cn (unknown [192.168.164.215]) by Forcepoint Email with ESMTPS id 8EF911C6EC9C1A58BCFD; Thu, 12 Mar 2020 10:14:51 +0800 (CST)
Received: from mse-fl1.zte.com.cn (unknown [10.30.14.238]) by Forcepoint Email with ESMTPS id 6473BE660AE55A90A6B2; Thu, 12 Mar 2020 10:14:51 +0800 (CST)
Received: from njxapp01.zte.com.cn ([10.41.132.200]) by mse-fl1.zte.com.cn with SMTP id 02C1eceS020233; Thu, 12 Mar 2020 09:40:38 +0800 (GMT-8) (envelope-from xiao.min2@zte.com.cn)
Received: from mapi (njxapp01[null]) by mapi (Zmail) with MAPI id mid201; Thu, 12 Mar 2020 09:40:38 +0800 (CST)
Date: Thu, 12 Mar 2020 09:40:38 +0800
X-Zmail-TransId: 2af95e6993165423701f
X-Mailer: Zmail v1.0
Message-ID: <202003120940380487407@zte.com.cn>
In-Reply-To: <CAMZsk6cdrZz7ojexUXSc9WHxvz=URM8G-Y8czcbYtSLYkRYCrw@mail.gmail.com>
References: CAMZsk6cdrZz7ojexUXSc9WHxvz=URM8G-Y8czcbYtSLYkRYCrw@mail.gmail.com
Mime-Version: 1.0
From: xiao.min2@zte.com.cn
To: rgandhi.ietf@gmail.com
Cc: ippm@ietf.org, draft-ietf-ippm-stamp-option-tlv@ietf.org, mach.chen@huawei.com, ippm-chairs@ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl1.zte.com.cn 02C1eceS020233
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/zZCPXrkh8SIFiVlxJxgz5zBxpc8>
Subject: Re: [ippm] Updates to twamp light/stamp messages
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, 12 Mar 2020 02:15:30 -0000

Hi Rakesh,







I'm a bit confused why separate TWAMP-Light and STAMP messages need to be defined, because as  I understand STAMP can be seen as the standardized and enhanced version of TWAMP-Light, and STAMP is backward compatible with the existing TWAMP-Light implementations.






Best Regards,


Xiao Min









原始邮件



发件人:RakeshGandhi <rgandhi.ietf@gmail.com>
收件人:IETF IPPM WG <ippm@ietf.org>;draft-ietf-ippm-stamp-option-tlv@ietf.org <draft-ietf-ippm-stamp-option-tlv@ietf.org>;Mach Chen <mach.chen@huawei.com>;
抄送人:IPPM Chairs <ippm-chairs@ietf.org>;
日 期 :2020年03月12日 06:36
主 题 :[ippm] Updates to twamp light/stamp messages




_______________________________________________
ippm mailing list
ippm@ietf.org
https://www.ietf.org/mailman/listinfo/ippm


Hi WG,



I have prepared few slides as follows to discuss the various options for adding session id and control code in the twamp light and stamp messages. 




https://github.com/rakgandhi/ietf-public/blob/master/ietf-stamp-session-id-rev1.pdf






Drafts discussed are:



draft-gandhi-spring-twamp-srpm


draft-ietf-ippm-stamp-option-tlv






Welcome your comments and suggestions.







Thanks,


Rakesh