IETF Logo Mail Archive

Re: [Taps] Transport Services (taps) WG Virtual Meeting: 2019-05-08

Max Franke <mfranke@inet.tu-berlin.de> Tue, 07 May 2019 05:34 UTC

Return-Path: <mfranke@inet.tu-berlin.de>
X-Original-To: taps@ietfa.amsl.com
Delivered-To: taps@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAF9B120072 for <taps@ietfa.amsl.com>; Mon, 6 May 2019 22:34:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.099
X-Spam-Level: *
X-Spam-Status: No, score=1.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTML_MIME_NO_HTML_TAG=0.377, MIME_HTML_ONLY=0.723, MISSING_MIMEOLE=1.899, SPF_PASS=-0.001] autolearn=no 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 w7N4I5UHiGTF for <taps@ietfa.amsl.com>; Mon, 6 May 2019 22:34:21 -0700 (PDT)
Received: from mail.net.t-labs.tu-berlin.de (mail.net.t-labs.tu-berlin.de [130.149.220.242]) by ietfa.amsl.com (Postfix) with ESMTP id C2C5512002F for <taps@ietf.org>; Mon, 6 May 2019 22:34:19 -0700 (PDT)
Received: from [IPv6:2a01:598:8192:546:1:1:bde:3347] (unknown [IPv6:2a01:598:8192:546:1:1:bde:3347]) by mail.net.t-labs.tu-berlin.de (Postfix) with ESMTPSA id 3F38D590; Tue, 7 May 2019 07:34:17 +0200 (CEST)
Date: Tue, 07 May 2019 07:34:16 +0200
Message-ID: <4a64f835-ed93-4207-a72c-03935d9244f1@email.android.com>
X-Android-Message-ID: <4a64f835-ed93-4207-a72c-03935d9244f1@email.android.com>
In-Reply-To: <A920F023-C5A7-4EB2-B088-FB0EACC6A539@akamai.com>
From: Max Franke <mfranke@inet.tu-berlin.de>
To: "Holland, Jake" <jholland@akamai.com>
Cc: "Brian Trammell (IETF)" <ietf@trammell.ch>, Aaron Falk <aaron.falk@gmail.com>, taps@ietf.org
Importance: Normal
X-Priority: 3
X-MSMail-Priority: Normal
MIME-Version: 1.0
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/CLZa8z36lAMar5YCZ6OdCi2i7lI>
Subject: Re: [Taps] Transport Services (taps) WG Virtual Meeting: 2019-05-08
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF Transport Services \(TAPS\) Working Group" <taps.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/taps>, <mailto:taps-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/taps/>
List-Post: <mailto:taps@ietf.org>
List-Help: <mailto:taps-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/taps>, <mailto:taps-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 May 2019 05:34:24 -0000

Hi Jake,

thanks a lot for the work on yang in PyTAPS! 

Side note:

There's a disconnect about the "multiple endpoint identifiers" clause
in the "Specifying Endpoints" section of taps-interface which I think the
current implementation doesn't follow.  I didn't try to fix it, but it looks
hard to support without tightening up what the semantics here are, exactly:

"Multiple endpoint identifiers can be specified for each Local Endpoint and Remote Endpoint. For example, a Local Endpoint could be configured with two interface names, or a Remote Endpoint could be specified via both IPv4 and IPv6 addresses. These multiple identifiers refer to the same transport endpoint."

Should this be opened as an issue against taps-interface?

We have indeed not implemented support for multiple identifiers as there is no racing yet, but as I understand it you would simply repeatedly call endpoint.with_address() with the different identifiers.

Best regards 
Max

v2.23.0 | Report a Bug | By Email