IETF Logo Mail Archive

Re: [ippm] Support for draft-mirsky-ippm-twamp-refl-registered-port

Henrik Nydell <hnydell@accedian.com> Wed, 22 March 2017 19:14 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 00A2A126BF6 for <ippm@ietfa.amsl.com>; Wed, 22 Mar 2017 12:14:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 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_LOW=-0.7, SPF_PASS=-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 08kH57_Jt3fN for <ippm@ietfa.amsl.com>; Wed, 22 Mar 2017 12:14:53 -0700 (PDT)
Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (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 12F7E129501 for <ippm@ietf.org>; Wed, 22 Mar 2017 12:14:53 -0700 (PDT)
Received: by mail-oi0-x22d.google.com with SMTP id r203so50228978oib.3 for <ippm@ietf.org>; Wed, 22 Mar 2017 12:14:53 -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=mv6MhfhLmAYv0n25C/tj6DZU+47doqakTTzJXPiKF88=; b=dOSqhlCo6+W6xzrfF6DBEp7q1zM1Q5699TwKKwurYfLPiqYEfNhZiRRqP51+mgXcNe 3pDAjNY2ys0PPeDHANVinB+tqnqnLO0x6F4u9pQSyUcMLUNNN2dDfENnz8YHSeWyAT31 kblRKSVO0P6zscld19f7BSWt1Djl35oniPrlTlXNo+Zwqo4IxDeMVWcFwcrkT+KaaTrF R7gowifcDgN3qlSk2FDO+FM3ry1UZlvqpi7hCqfC+o6vhMOO6I06rdFwJeppXh7eW5dB Vl1viBgxVZTT+axO6wZvlg+IEXDqBmfCEMYDAMCRL0bmKRdIk/SfRM9PxwNqffi1rS9v R8CQ==
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=mv6MhfhLmAYv0n25C/tj6DZU+47doqakTTzJXPiKF88=; b=uWuWQRYdzGhqfP3s1tO0NVymjrAlikuWKP876zWaKZSm73EM0D1qSAjpff674ZE9QM tynvJiOzZokMS5MEXljuRlagv4oGs+is2SPTaxHjD+HiOWiQKkhgo4/P6Pmut3fERKEa hFWlI4mubarvXOfHy5xoWs97ryf0AcZ9gcGJooczXmYBk9Y5woAuY/EBM6vKB0FAcTBa sxVV/5fbV+Wz6ZrFW91j2GglobTPJFi/jORdulSxSrMSEk1Jb/RMYsV8betJpUwSpMAW g9UAl0pkceCTsP0eppRP7lf29ugkCtqsgFsiEc3sukluZxjkf3KUE7xKnFp9HFIvot4z b4og==
X-Gm-Message-State: AFeK/H2/oQpFWs7OwX3vp7qzYrhWZ6U9XydeVwJrPBDiyhbdPA4JferG5D47Aa0M7l4l1M3yho2/YpjZZ70VZzsxJ0Efr/I+eBnY/S2Y4j+V6VP99TmJ4VcXrzZA47uZW/h0
X-Received: by 10.202.252.1 with SMTP id a1mr20762083oii.40.1490210092426; Wed, 22 Mar 2017 12:14:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.157.51.153 with HTTP; Wed, 22 Mar 2017 12:14:51 -0700 (PDT)
Received: by 10.157.51.153 with HTTP; Wed, 22 Mar 2017 12:14:51 -0700 (PDT)
In-Reply-To: <D6F9B78A-656B-46EE-A534-A0166F5A4261@nokia.com>
References: <D6F9B78A-656B-46EE-A534-A0166F5A4261@nokia.com>
From: Henrik Nydell <hnydell@accedian.com>
Date: Wed, 22 Mar 2017 20:14:51 +0100
Message-ID: <CALhTbppqA5mG4HRpdSC5xa9yGg7LCpn5gFK5H7SPqCG4mMdf_A@mail.gmail.com>
To: "Fabregas, Guiu (Nokia - ES/Madrid)" <guiu.fabregas@nokia.com>
Cc: ippm@ietf.org
Content-Type: multipart/alternative; boundary="001a113b00c8337299054b5693ff"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/mDzi4tOFfUdV6Q7d2ekat8Tjc8M>
Subject: Re: [ippm] Support for draft-mirsky-ippm-twamp-refl-registered-port
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: Wed, 22 Mar 2017 19:14:55 -0000

I have seen that some vendors of TWAMP senders (I believe EXFO and possibly
Spirent) use port UDP/862 as default port despite being defined only for
the TCP portion of TWAMP-control. Has consideration within ippm been done
on opting for that port to be used also for TWAMP-test or is there a
preference for a higher (>1024) port number?



On 22 Mar 2017 7:35 PM, "Fabregas, Guiu (Nokia - ES/Madrid)" <
guiu.fabregas@nokia.com> wrote:

> Hi all,
>
> I've gone through this draft and agree with the authors on the need of a
> well known port for TWAMP, so I wanted to expres my support this work.
>
> It will considerably simplify a number of deployment scenarios related to
> TWAMP light.
>
> Looking forward to seeing this draft progress.
>
> Thanks,
> Guiu
>
> _______________________________________________
> ippm mailing list
> ippm@ietf.org
> https://www.ietf.org/mailman/listinfo/ippm
>

-- 


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.

v2.23.0 | Report a Bug | By Email