[ippm] Continue discussion draft-mirsky-ippm-time-format-01

Gregory Mirsky <gregory.mirsky@ericsson.com> Wed, 02 December 2015 19:11 UTC

Return-Path: <gregory.mirsky@ericsson.com>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 174D71ACED9 for <ippm@ietfa.amsl.com>; Wed, 2 Dec 2015 11:11:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.2
X-Spam-Level:
X-Spam-Status: No, score=-104.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 HsR-j8gXbUgW for <ippm@ietfa.amsl.com>; Wed, 2 Dec 2015 11:11:23 -0800 (PST)
Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D36D41ACED5 for <ippm@ietf.org>; Wed, 2 Dec 2015 11:11:20 -0800 (PST)
X-AuditID: c6180641-f799c6d000007d66-39-565f4254e2ab
Received: from EUSAAHC003.ericsson.se (Unknown_Domain [147.117.188.81]) by usplmg21.ericsson.net (Symantec Mail Security) with SMTP id B1.55.32102.4524F565; Wed, 2 Dec 2015 20:11:17 +0100 (CET)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC003.ericsson.se ([147.117.188.81]) with mapi id 14.03.0248.002; Wed, 2 Dec 2015 14:11:19 -0500
From: Gregory Mirsky <gregory.mirsky@ericsson.com>
To: "ippm@ietf.org" <ippm@ietf.org>
Thread-Topic: Continue discussion draft-mirsky-ippm-time-format-01
Thread-Index: AdEtMThqkdFud7vmRGKMMylXBNiYbQ==
Date: Wed, 02 Dec 2015 19:11:18 +0000
Message-ID: <7347100B5761DC41A166AC17F22DF1122194F378@eusaamb103.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.10]
Content-Type: multipart/alternative; boundary="_000_7347100B5761DC41A166AC17F22DF1122194F378eusaamb103erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrDLMWRmVeSWpSXmKPExsUyuXRPoG6oU3yYwYJVXBZTlmxkseh58I7Z gcljyZKfTB5fLn9mC2CK4rJJSc3JLEst0rdL4Mq413SAreCVVsX6o7uYGxhvqnQxcnJICJhI nLg9kwnCFpO4cG89WxcjF4eQwBFGic/LpjJBOMsYJU5sWMQMUsUmYCTxYmMPO4gtIqAs0fLt DyOIzSyQLLH7RTNYjbCArcTeeQsYIWqcJF6/ms4CYetJ9G94xwpiswioSPxacwlsM6+Ar8SP f7PAehmBrvh+ag0TxExxiVtP5kNdJyCxZM95ZghbVOLl43+sELaSxKSl51gh6vMlJq67wAgx U1Di5MwnLBMYhWchGTULSdksJGUQcR2JBbs/sUHY2hLLFr5mhrHPHHjMhCy+gJF9FSNHaXFB Tm66keEmRmCcHJNgc9zBuLfX8xCjAAejEg9vgVpcmBBrYllxZe4hRgkOZiURXgHz+DAh3pTE yqrUovz4otKc1OJDjNIcLErivIwMDAxCAumJJanZqakFqUUwWSYOTqkGRgfTsjKGq2tnsyVn J2xqud5aLXfCyKEl+aBh/yd3fsbbE98bPtZ42fp/fvi7u6XLzcTWWQu+vMTnwcPZIrVtya9j oa3SPUk7z3h7n97Dn2ohH37SzT3rodu1aqEVe6eJLz0m9mWP2BX5hua/31abdDUmuJhwTV1t q7xXRpDvfZqA7+8nj899VGIpzkg01GIuKk4EACSBMT2PAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/ippm/PZF1xZJQEBCWPjX2CJQ2RbzLA5U>
Cc: "draft-mirsky-ippm-time-format@tools.ietf.org" <draft-mirsky-ippm-time-format@tools.ietf.org>
Subject: [ippm] Continue discussion draft-mirsky-ippm-time-format-01
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 02 Dec 2015 19:11:26 -0000

Dear All,
I wanted to thank Kostas, Al and Brian for their questions, comments at the presentation in Yokohama. The discussion suggests that this work is of interest to the IPPM WG. As Brian suggested, let's continue the discussion on the mailing list.
I believe that we've discussed backward compatibility of the proposed TWAMP extension and Al and Brian asked for clarifications on scenario when TWAMP test cannot be conducted between supporting and non-supporting this extension NEs. Indeed, there's such case. When Session-Reflector supports this extension and uses only 1588 timestamp format while Session-Sender does not support the extension Server will close the TCP connection with the Control-Client (as displayed on slide 5 of the presentation slide-deck). In case if a Session-Reflector does not support the extension and the Session-Sender does, the TWAMP session can proceed as Session-Sender would be able to interpret both timestamp formats as noted in the slide 3 (MUST be capable to INTERPRET NTP and PTPv2 time stamp formats).
Hope I've captured questions that have been asked in Yokohama.
Always welcome comments and questions. Looking forward to hear from Al and Brian whether I've answered their questions. Authors greatly appreciate your interest in this work and looking forward to bring it to WG adoption call soon.

                Regards,
                                Greg