IETF Logo Mail Archive

Re: [Taps] On Profiles for TAPS Preconnections

"Philipp S. Tiesel" <philipp@tiesel.net> Tue, 23 July 2019 14:28 UTC

Return-Path: <philipp@tiesel.net>
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 6EB47120323 for <taps@ietfa.amsl.com>; Tue, 23 Jul 2019 07:28:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level:
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 tL2nEUcxamYL for <taps@ietfa.amsl.com>; Tue, 23 Jul 2019 07:28:06 -0700 (PDT)
Received: from einhorn-mail.in-berlin.de (einhorn-mail.in-berlin.de [217.197.80.20]) (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 B8F28120309 for <taps@ietf.org>; Tue, 23 Jul 2019 07:28:05 -0700 (PDT)
X-Envelope-From: philipp@tiesel.net
Received: from x-berg.in-berlin.de (x-change.in-berlin.de [217.197.86.40]) by einhorn.in-berlin.de with ESMTPS id x6NES0bb023753 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 23 Jul 2019 16:28:00 +0200
Received: from [2001:67c:1232:144:2195:9781:734:997d] by x-berg.in-berlin.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from <philipp@tiesel.net>) id 1hpvjo-0003ys-8L; Tue, 23 Jul 2019 16:25:56 +0200
Content-Type: multipart/alternative; boundary="Apple-Mail=_F548D14C-AB81-4CD8-94AB-8675C2C72A58"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: "Philipp S. Tiesel" <philipp@tiesel.net>
X-Priority: 3
In-Reply-To: <7DB06BAF-BC10-4367-BD5E-C7EFB698200B@ifi.uio.no>
Date: Tue, 23 Jul 2019 10:27:57 -0400
Cc: Maximilian Franke <mfranke@inet.tu-berlin.de>, Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org>, "taps@ietf.org" <taps@ietf.org>
Message-Id: <9D63340C-3116-476F-B758-D015A3A5A6A4@tiesel.net>
References: <f71bd460-e0a3-47eb-b384-d3dc9b0f1962@email.android.com> <7DB06BAF-BC10-4367-BD5E-C7EFB698200B@ifi.uio.no>
To: Michael Welzl <michawe@ifi.uio.no>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/_dWeGN3Vi3zbcT5uPnxAdQKxj1Q>
Subject: Re: [Taps] On Profiles for TAPS Preconnections
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, 23 Jul 2019 14:28:19 -0000


> On 23. Jul 2019, at 10:17, Michael Welzl <michawe@ifi.uio.no> wrote:
> 
> 
> 
>> On Jul 23, 2019, at 9:51 AM, Max Franke <mfranke@inet.tu-berlin.de <mailto:mfranke@inet.tu-berlin.de>> wrote:
>> 
>> 
>> 
>> The API prescribed by this document is abstract, and needs to give freedom to implementations to make things elegant in their particular languages.
>> 
>> What about having an appending, that's non-normative and not required for RFC compliance, that describes suggested conveniences, such as "properties.prefer()" and the concept of convenience profiles?
>> Yes, I like this idea. I also agree that the API is complex enough as it is and requiring convenience features to be RFC compliant is probably not a good idea. As long as we are consistent with moving all conveniences to the appendix this is my preferred option.
> 
> +1 on this if it’s a workable solution (sounds like it is), and a particular +1 on the side comment about "consistently moving all conveniences to the appendix”

I am fine with moving all conveniences to the appendix, but we might still need to reference them in the main text to make sure the API does not look overly inconvenient. I also would like to use the profiles in one of the examples.

AVE!
   Philipp S. Tiesel

-- 
Philipp S. Tiesel 
https://philipp.tiesel.net/

v2.23.0 | Report a Bug | By Email