Re: [ippm] Fwd: New Version Notification for draft-mirsky-ippm-stamp-00.txt
Henrik Nydell <hnydell@accedian.com> Thu, 26 October 2017 11:28 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 B1AAF13F564 for <ippm@ietfa.amsl.com>; Thu, 26 Oct 2017 04:28:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.879
X-Spam-Level:
X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01, T_KAM_HTML_FONT_INVALID=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.20150623.gappssmtp.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 R3CCJ_SGq3UF for <ippm@ietfa.amsl.com>; Thu, 26 Oct 2017 04:28:15 -0700 (PDT)
Received: from mail-ua0-x230.google.com (mail-ua0-x230.google.com [IPv6:2607:f8b0:400c:c08::230]) (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 8CD4613B2BB for <ippm@ietf.org>; Thu, 26 Oct 2017 04:28:15 -0700 (PDT)
Received: by mail-ua0-x230.google.com with SMTP id i35so2180421uah.9 for <ippm@ietf.org>; Thu, 26 Oct 2017 04:28:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=accedian-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=bec27WF9FJeaqqCcp/cOHhJMitYCcJnbou49lun4yNE=; b=EQofszWgm0L1nhQ/PoAEm+K22kXCySrnLUiR+3B0f0ceTXWrFLhRVU1GcpnzNEpX3R aCZUlWPvbMvtqOxohG/3Db6FheUv4jOwft59UpPeaK3GwX6x3+jJfESdyUy6SDPXwlFm VZrU9d2ztWyREPIN/VyjaGX7yBdpRgAF688mPImxzpVsqa59XmuasqBCdspq8oFYHYNm 4D+L4Q56hjXjACY3yy0SruiTb+MZfPFTSPF3LXT+6jaXqE8frA8z2eMhqV0dxvOEd7ja L0xBkH6BRs3ASI1p61IsLq8RxaNzmbWIvKWU+R9Qco8vpf8MwljH1jn5eRFRjw3oI5KZ zVqQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=bec27WF9FJeaqqCcp/cOHhJMitYCcJnbou49lun4yNE=; b=Szq7ppk+jcrb+08XsOtCl4uGRIpvwFRBte5THEyNVFosuup79HqnmQI9Wzt8XB4QTB q6Z+hnu0ex3UaKT9yAhyb7qeKla4Gq6o8qcgx6lMROkwkFQP8DBgav3tslAEvbKSc7wJ BiNQDtxjvSMNY+SLVKl27qVU7nKfqbjXCGzfAabyRE1hlMvD9bxsC9tfcOX/l1Vk9fyW /tG7rh8LdUaz1+i1wTAuKB6wOFYxS09pj2WEcWdgtRVZoBq0hbMmiR9kJFYM9wA6IXDV R0Lq2/33IoRdCswKThamDhf7m8v64hF/8whhQqAzsq3W/z4sLwBg5c1eBHpGiN77t0Uz rEXQ==
X-Gm-Message-State: AMCzsaVAnPTIMfVAJO6HJ0EyKXN8EeO0IZAABtQv+YbTSOrSHGJriHgE 5HZCNYI7vg9PvsWMzwoxLUL0h4DZ1/eHJAnY5OagG2yUd+h0gyUw0E9GBt4fRokHk4dE9pWnrJn NY82qCN0/l5CI7BI=
X-Google-Smtp-Source: ABhQp+TkklR1ln/NcIPO/ysjJHNdcuC+iJLaFL5j17NJTYFV9ZfQYcqUMT+cdmFTcwhLoYR7h5X+xSMYtoNfFESCLYM=
X-Received: by 10.176.92.74 with SMTP id a10mr3933088uag.165.1509017294401; Thu, 26 Oct 2017 04:28:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.103.82.203 with HTTP; Thu, 26 Oct 2017 04:28:13 -0700 (PDT)
In-Reply-To: <CA+RyBmWHsGN9U8Ny=Xam9N9M0LSpaNrAYsiBnhABG4F9f1qptw@mail.gmail.com>
References: <150791020014.23806.9772394085541002363.idtracker@ietfa.amsl.com> <CA+RyBmWHsGN9U8Ny=Xam9N9M0LSpaNrAYsiBnhABG4F9f1qptw@mail.gmail.com>
From: Henrik Nydell <hnydell@accedian.com>
Date: Thu, 26 Oct 2017 13:28:13 +0200
Message-ID: <CALhTbpqySnod3RUA3OC1+-sm5808ohk1K-CxtTgZ7uaaKz3TcQ@mail.gmail.com>
To: Greg Mirsky <gregimirsky@gmail.com>
Cc: "ippm@ietf.org" <ippm@ietf.org>
Content-Type: multipart/alternative; boundary="f403043ef164cb0113055c7177dd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/ayXuPMPJJwEmPxdGe00B1O4JUqM>
Subject: Re: [ippm] Fwd: New Version Notification for draft-mirsky-ippm-stamp-00.txt
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.22
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, 26 Oct 2017 11:28:19 -0000
I did a quick glance through and there are some good things - PTP timestamp as an option - Finally! - Symmetric format - TLV support for vendor options - May prove useful Are you going to define how the encrypted and authenticated modes work, i.e what encryption method and what type of authentication, or will you rely on what was done for TWAMP and OWAMP? I haven't seen much use of the encrypted mode out there in the field, probably because it puts load on the CPUs to do the decryption and encryption, which may be sparse in supply in smaller edge devices. One useful addition would be if the Sender (and Reflector) could report (maybe in some of the MBZ bits) if it is synchronized to 0) Free running 1) NTP 2) PTP 3) Other (GPS, PPS, Radio e t c) Maybe some of these are already in the error estimate, but not all I believe. Also, if the responder could report timestamping method somehow 1) TX/RX Hardware Timestamp "close to wire" <--- Most accurate 2) TX/RX Hardware Timestamp in recv/txm buffers <--- Quite accurate 3) TX/RX Software Timestamp in recieve/transmit handler <--- Less accurate On the IANA registered TLVs you are proposing to define, there are a couple of parameters that are missing in TWAMP that could either go in as TLVs or into the standard packet format, but then of course causing incompatibility with existing reflectors which is not good. - TOS (Diffserv CP) - This one is not possible to "measure" one-way with TWAMP as the TOS field is just copied over at the Reflector. So errors in DSCP configuration cannot be isolated to a specific direction. - Destination/Source IP address, MAC address & Port (Can be used to detect NAT in the Path if Reflector can report what it sees as Destination/Source IP addresses, or detect routing changes close to the reflector, if source mac as seen from reflector changes) There are more ways the TLVs could be utilized, but I believe they have to be standardized and possibly mandatory to support the standardized set, otherwise vendor interoperability won't be able to use them of course. One other area is within burst measurements, where TLVs could be defined to contain burst information, so that the responder could build a burst accordingly in the same way a sender did. One other interresting TLV use case for my company in particular is for multi-hop measurements where we hold a patent ( https://www.google.com/patents/EP2690823A1?cl=en) but there are certainly other non-proprietary cases that this functionality will enable. On Mon, Oct 16, 2017 at 9:41 PM, Greg Mirsky <gregimirsky@gmail.com> wrote: > Dear All, > we've published the first version of STAMP ("Simple" Two-way Active > Measurement Protocol). Though it may be viewed as not really simple, but > STAMP is too catchy name to pass. > We greatly appreciate your reviews, comments, questions, and suggestions. > We hope to have good and productive on-list and at the IETF-100 meeting > discussion. > > Kind regards, > Greg and Guo > > ---------- Forwarded message ---------- > From: <internet-drafts@ietf.org> > Date: Fri, Oct 13, 2017 at 8:56 AM > Subject: New Version Notification for draft-mirsky-ippm-stamp-00.txt > To: Gregory Mirsky <gregimirsky@gmail.com>, Guo Jun <guo.jun2@zte.com.cn> > > > > A new version of I-D, draft-mirsky-ippm-stamp-00.txt > has been successfully submitted by Greg Mirsky and posted to the > IETF repository. > > Name: draft-mirsky-ippm-stamp > Revision: 00 > Title: Simple Two-way Active Measurement Protocol > Document date: 2017-10-12 > Group: Individual Submission > Pages: 12 > URL: https://www.ietf.org/internet- > drafts/draft-mirsky-ippm-stamp-00.txt > Status: https://datatracker.ietf.org/doc/draft-mirsky-ippm-stamp/ > Htmlized: https://tools.ietf.org/html/draft-mirsky-ippm-stamp-00 > Htmlized: https://datatracker.ietf.org/ > doc/html/draft-mirsky-ippm-stamp-00 > > > Abstract: > This document describes a Two-way Active Measurement Protocol which > enables measurement of both one-way and round-trip performance > metrics like delay, delay variation and packet loss. > > > > > Please note that it may take a couple of minutes from the time of > submission > until the htmlized version and diff are available at tools.ietf.org. > > The IETF Secretariat > > > > _______________________________________________ > ippm mailing list > ippm@ietf.org > https://www.ietf.org/mailman/listinfo/ippm > > -- [image: Accedian.com] Henrik Nydell Sr Manager Global Strategy & Solutions Cell Email Skype +46 709845992 hnydell@accedian.com <mkowalke@accedian.com> h <http://linkedin.com/in/maekowalk>nydell <http://accedian.com/> <http://blog.accedian.com/> <https://www.linkedin.com/company/accedian-networks> <https://twitter.com/Accedian> <https://www.facebook.com/accedian> <http://www.youtube.com/user/accedian> -- 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] Fwd: New Version Notification for draft-mi… Greg Mirsky
- Re: [ippm] Fwd: New Version Notification for draf… Wei Luo S
- Re: [ippm] Fwd: New Version Notification for draf… Greg Mirsky
- Re: [ippm] Fwd: New Version Notification for draf… Henrik Nydell
- Re: [ippm] Fwd: New Version Notification for draf… Greg Mirsky