
From nobody Wed Mar  4 06:41:21 2020
Return-Path: <michawe@ifi.uio.no>
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 EB9C13A100A for <taps@ietfa.amsl.com>; Wed,  4 Mar 2020 06:41:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham 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 hZkRlHhAYEZL for <taps@ietfa.amsl.com>; Wed,  4 Mar 2020 06:41:17 -0800 (PST)
Received: from mail-out01.uio.no (mail-out01.uio.no [IPv6:2001:700:100:10::50]) (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 366E83A1005 for <taps@ietf.org>; Wed,  4 Mar 2020 06:41:17 -0800 (PST)
Received: from mail-mx10.uio.no ([129.240.10.27]) by mail-out01.uio.no with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93.0.4) (envelope-from <michawe@ifi.uio.no>) id 1j9VD0-0007cJ-G1; Wed, 04 Mar 2020 15:41:14 +0100
Received: from ti0182q160-5615.bb.online.no ([84.202.72.50] helo=[10.0.0.12]) by mail-mx10.uio.no with esmtpsa (TLS1.2:ECDHE-RSA-AES256-GCM-SHA384:256) user michawe (Exim 4.93.0.4) (envelope-from <michawe@ifi.uio.no>) id 1j9VCz-000CVF-HH; Wed, 04 Mar 2020 15:41:14 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Michael Welzl <michawe@ifi.uio.no>
In-Reply-To: <CAJU8_nVyAvVzD6ZitxwzoVCYBYmT1y3oP7U8FhgyWfx8p6RR5w@mail.gmail.com>
Date: Wed, 4 Mar 2020 15:41:12 +0100
Cc: "taps@ietf.org" <taps@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <E9545535-178C-4B9F-91C2-0EB3356DB5B0@ifi.uio.no>
References: <CAJU8_nVyAvVzD6ZitxwzoVCYBYmT1y3oP7U8FhgyWfx8p6RR5w@mail.gmail.com>
To: Kyle Rose <krose@krose.org>
X-Mailer: Apple Mail (2.3445.104.11)
X-UiO-SPF-Received: Received-SPF: neutral (mail-mx10.uio.no: 84.202.72.50 is neither permitted nor denied by domain of ifi.uio.no) client-ip=84.202.72.50;  envelope-from=michawe@ifi.uio.no; helo=[10.0.0.12]; 
X-UiO-Spam-info: not spam, SpamAssassin (score=-5.0, required=5.0, autolearn=disabled, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO)
X-UiO-Scanned: 564DEF53B93D7566497860BDCE84B4004171EBB5
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/e-rkFYpwLDkBAWZYpOtvsUg7lAk>
Subject: Re: [Taps] draft-ietf-taps-interface-05 review
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: Wed, 04 Mar 2020 14:41:20 -0000

Dear Kyle,

Thanks so much for all your comments - and sorry for taking so long to =
get back to you!

I decided to begin attacking them now with a PR. Please see:
https://github.com/ietf-tapswg/api-drafts/pull/514
for the comments that I tried to address, my answers to them, and the =
changes that I propose to our draft.

For the record, if this PR can be merged, this still leaves us with the =
unresolved comments below. I inserted some answers below, prefixed with =
"MW:=E2=80=9D. I think that some of them can be addressed relatively =
easily by others, whereas some should probably best be filed as an issue =
for further discussion=E2=80=A6 let=E2=80=99s take this step by step. =
Easy ones first, to make the list a bit more digestable  :-)

Cheers,
Michael

-------

REMAINING UNADDRESSED COMMENTS FROM KYLE ROSE:


2. Terminology and Notation

 * The notation "Sender -> Event" says nothing about who receives the =
event. Is it just assumed to be the application in the context of the =
particular event (e.g., a thread processing a particular connection)?

MW: We have the following statement in this section: "Events could be =
implemented via event queues, handler functions or classes, =
communicating sequential processes, or other asynchronous calling =
conventions."
I wonder why this isn't enough information? E.g., if handlers are used, =
then the recipient of the event is a pre-registered handler -  and =
handlers must therefore be registered before events can occur; this =
function isn't visible in the API because this is platform- and =
language-specific.


4.2.1. Transport Property Names

 * The use of dashes in property names means they will necessarily look =
different in almost every widely-used language, in which dash is an =
operator.

 * If we're not currently asking IANA to create a registry of property =
names or namespaces, should we provide a recommendation that such =
symbols not listed explcitly in this document be prefixed with some =
experimental identifier?


5.2. Specifying Transport Properties

 * There are a lot of choices being made about how users will want to =
prioritize transport protocol selection. How confident are we that, for =
instance, path selection should take priority over protocol selection? I =
think that's right, but I wonder if it might not make more sense to have =
two interfaces: one that provides a purely numeric priority ordering of =
preferences, and one (based on the existing 5-level preferences) that =
maps into it.

 * Using the same enum (Require(d[sic])/Avoid/Ignore) for the queried =
output of selected properties seems like a shortcut that will lead to =
some confusion.

MW: I agree;  partially addressed: s/Required/Require wherever it's a =
Preference level.


5.2.5. Use 0-RTT Session Establishment with an Idempotent Message

 * I'll repeat the same statement I made at the mic a few years ago: =
idempotency !=3D replay-safe. DELETE is idempotent, but not safe for =
replay because someone might have done a PUT or POST in the meantime.

MW: I remember you saying this, sorry that we haven't addressed it yet! =
I didn't understand - is your concern about replaying that a Message may =
arrive later, i.e. as Message X, Messages Y and Z in between, then =
Message X again?  =3D> if so, are you saying that this could happen with =
TFO or QUIC?  (I didn't think so)


5.2.10. Interface Instance or Type

 * These type symbols really deserve an actual registry, or at least the =
start of one. Otherwise, we are likely to end up with a mess.

5.2.11. Provisioning Domain Instance or Type

 * What about ordering of similar interfaces? I have a 2-SIM cellphone =
with wifi.

5.3.2. Connection Establishment Callbacks

 * What constitutes trust verification prior to the handshake?

7.3.1. Sent

 * It seems like an abstract API would be helpful for the reference to =
the Message to which a Sent event applies: this seems like something =
many, many applications would need to do. With callbacks, the =
application can always curry in a reference to the original message =
(that's what my event system from ~2001 did), so maybe that should be =
the recommendation and the message reference removed...? I don't have a =
strong feeling here other than that if something is included then its =
use should be more well-defined.

7.3.3. SendError

 * Is there a reason why a single messageContext object is used for both =
sends and receives? I probably missed the original discussion about =
this, but I'd like to understand the reasoning.

MW: I don't get this, where does it say that it's only a single object? =
Or do you mean that it's the same type? Why is that problematic?


7.4.7. Reliable Data Transfer (Message)

 * The default isn't "true", it's whatever the underlying connection =
had, right?


8. Receiving Data

 * A connection can be used to receive data if it is not configured as =
unidirectional transmit.

MW: that's obviously correct - but I can't find a statement that would =
contradict what you say here.


8.2. Receive Events

 * "A call to Receive will be paired with a single Receive Event" or =
possibly multiple ReceivedPartial Events?

 * Also, can the draft be consistent about Receive vs. Received, et al.?


11. General comments

 * There's a lot of UNIXisms here that should probably be excised in =
favor of a more abstract presentation. The most obvious is the use of -1 =
to mean something other than the integer -1. In Python, for instance, =
you might want to use None for this purpose. I would specify non-numeric =
values symbolically, and maybe indicate in the appendix that a UNIX C =
implementation might want to use -1 to represent such values.

MW: agreed... TODO.


11.1.10. Capacity Profile

 * Very little of this section is about capacity. Traffic Profile?

 * "High Throughput Data" might be better phrased as "Capacity-Seeking".


From nobody Wed Mar  4 08:51:59 2020
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 BE7453A12CC for <taps@ietfa.amsl.com>; Wed,  4 Mar 2020 08:51:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 OFrCIYtRKWyy for <taps@ietfa.amsl.com>; Wed,  4 Mar 2020 08:51:47 -0800 (PST)
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 BB55B3A12C8 for <taps@ietf.org>; Wed,  4 Mar 2020 08:51:46 -0800 (PST)
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 024Gpi4f018339 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 4 Mar 2020 17:51:44 +0100
Received: from [2a01:598:818b:c666:48:44e8:27dc:387c] 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 1j9XCd-0003hT-7o; Wed, 04 Mar 2020 17:48:59 +0100
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
From: "Philipp S. Tiesel" <philipp@tiesel.net>
In-Reply-To: <E9545535-178C-4B9F-91C2-0EB3356DB5B0@ifi.uio.no>
Cc: Kyle Rose <krose@krose.org>, "taps@ietf.org" <taps@ietf.org>
Date: Wed, 4 Mar 2020 17:51:42 +0100
Message-Id: <5E98B07E-795C-4D87-B271-658EB03C7FCC@tiesel.net>
References: <E9545535-178C-4B9F-91C2-0EB3356DB5B0@ifi.uio.no>
To: Michael Welzl <michawe@ifi.uio.no>
X-Mailer: iPad Mail (17D50)
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/1V54trrM8TOMzt2s3647waiNkUM>
Subject: Re: [Taps] draft-ietf-taps-interface-05 review
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: Wed, 04 Mar 2020 16:51:57 -0000

Hi,

Some of the remaining issues had already been discussed, but either did not l=
ead to text or the text was lost. Let me comment on these issues:

>> On 4. Mar 2020, at 15:38, Michael Welzl <michawe@ifi.uio.no> wrote:
>=20
> REMAINING UNADDRESSED COMMENTS FROM KYLE ROSE:
>=20
>=20
> 2. Terminology and Notation
>=20
> * The notation "Sender -> Event" says nothing about who receives the event=
. Is it just assumed to be the application in the context of the particular e=
vent (e.g., a thread processing a particular connection)?
>=20
> MW: We have the following statement in this section: "Events could be impl=
emented via event queues, handler functions or classes, communicating sequen=
tial processes, or other asynchronous calling conventions."
> I wonder why this isn't enough information? E.g., if handlers are used, th=
en the recipient of the event is a pre-registered handler -  and handlers mu=
st therefore be registered before events can occur; this function isn't visi=
ble in the API because this is platform- and language-specific.
>=20
>=20
> 4.2.1. Transport Property Names
>=20
> * The use of dashes in property names means they will necessarily look dif=
ferent in almost every widely-used language, in which dash is an operator.

The solution for this issue was to allow implementations to change the prope=
rty names in consistent ways, e.g., by replacing the dashes with underscores=
 or removing them and use CamelCasing.
The text was removed as over-specific.

> * If we're not currently asking IANA to create a registry of property name=
s or namespaces, should we provide a recommendation that such symbols not li=
sted explcitly in this document be prefixed with some experimental identifie=
r?

The IANA registry question was explicitly postponed, be maybe we should re-i=
terate it now.
The idea of having an =E2=80=9Ex=E2=80=9C namespace was rejected in fear we e=
nd up with quasi-standard properties that have an x prefix then.=20
>=20
> 5.2. Specifying Transport Properties
>=20
> * There are a lot of choices being made about how users will want to prior=
itize transport protocol selection. How confident are we that, for instance,=
 path selection should take priority over protocol selection? I think that's=
 right, but I wonder if it might not make more sense to have two interfaces:=
 one that provides a purely numeric priority ordering of preferences, and on=
e (based on the existing 5-level preferences) that maps into it.

We had a lengthy discussion about this and rejected it as too complex and li=
miting for the implementation.
>=20
> * Using the same enum (Require(d[sic])/Avoid/Ignore) for the queried outpu=
t of selected properties seems like a shortcut that will lead to some confus=
ion.

We had text saying that these should turn into Boolean when queried and shou=
ld reflect whether the protocol stack chosen provides the feature. I will ha=
ve to double-check whether this text is still in the description of the pref=
erence type.

> MW: I agree;  partially addressed: s/Required/Require wherever it's a Pref=
erence level.
>=20
>=20
> 5.2.5. Use 0-RTT Session Establishment with an Idempotent Message
>=20
> * I'll repeat the same statement I made at the mic a few years ago: idempo=
tency !=3D replay-safe. DELETE is idempotent, but not safe for replay becaus=
e someone might have done a PUT or POST in the meantime.
>=20
> MW: I remember you saying this, sorry that we haven't addressed it yet! I d=
idn't understand - is your concern about replaying that a Message may arrive=
 later, i.e. as Message X, Messages Y and Z in between, then Message X again=
?  =3D> if so, are you saying that this could happen with TFO or QUIC?  (I d=
idn't think so)
>=20
>=20
> 5.2.10. Interface Instance or Type
>=20
> * These type symbols really deserve an actual registry, or at least the st=
art of one. Otherwise, we are likely to end up with a mess.

There is already one, but that one was not useful for our matters.=20
>=20
> 5.2.11. Provisioning Domain Instance or Type
>=20
> * What about ordering of similar interfaces? I have a 2-SIM cellphone with=
 wifi.

Each cellular provider will have a unique PVD.=20
>=20
> 5.3.2. Connection Establishment Callbacks
>=20
> * What constitutes trust verification prior to the handshake?
>=20
> 7.3.1. Sent
>=20
> * It seems like an abstract API would be helpful for the reference to the M=
essage to which a Sent event applies: this seems like something many, many a=
pplications would need to do. With callbacks, the application can always cur=
ry in a reference to the original message (that's what my event system from ~=
2001 did), so maybe that should be the recommendation and the message refere=
nce removed...? I don't have a strong feeling here other than that if someth=
ing is included then its use should be more well-defined.
>=20
> 7.3.3. SendError
>=20
> * Is there a reason why a single messageContext object is used for both se=
nds and receives? I probably missed the original discussion about this, but I=
'd like to understand the reasoning.
>=20
> MW: I don't get this, where does it say that it's only a single object? Or=
 do you mean that it's the same type? Why is that problematic?
>=20
>=20
> 7.4.7. Reliable Data Transfer (Message)
>=20
> * The default isn't "true", it's whatever the underlying connection had, r=
ight?

Ack
>=20
>=20
> 8. Receiving Data
>=20
> * A connection can be used to receive data if it is not configured as unid=
irectional transmit.
>=20
> MW: that's obviously correct - but I can't find a statement that would con=
tradict what you say here.
>=20
>=20
> 8.2. Receive Events
>=20
> * "A call to Receive will be paired with a single Receive Event" or possib=
ly multiple ReceivedPartial Events?
>=20
> * Also, can the draft be consistent about Receive vs. Received, et al.?
>=20
>=20
> 11. General comments
>=20
> * There's a lot of UNIXisms here that should probably be excised in favor o=
f a more abstract presentation. The most obvious is the use of -1 to mean so=
mething other than the integer -1. In Python, for instance, you might want t=
o use None for this purpose. I would specify non-numeric values symbolically=
, and maybe indicate in the appendix that a UNIX C implementation might want=
 to use -1 to represent such values.
>=20
> MW: agreed... TODO.
>=20
>=20
> 11.1.10. Capacity Profile
>=20
> * Very little of this section is about capacity. Traffic Profile?
>=20
> * "High Throughput Data" might be better phrased as "Capacity-Seeking".
>=20
> _______________________________________________
> Taps mailing list
> Taps@ietf.org
> https://www.ietf.org/mailman/listinfo/taps


From nobody Wed Mar  4 23:31:00 2020
Return-Path: <michawe@ifi.uio.no>
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 4FB573A0F13 for <taps@ietfa.amsl.com>; Wed,  4 Mar 2020 23:30:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 QaVVeXai9jyo for <taps@ietfa.amsl.com>; Wed,  4 Mar 2020 23:30:55 -0800 (PST)
Received: from mail-out01.uio.no (mail-out01.uio.no [IPv6:2001:700:100:10::50]) (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 5DEA93A0F0D for <taps@ietf.org>; Wed,  4 Mar 2020 23:30:53 -0800 (PST)
Received: from mail-mx12.uio.no ([129.240.10.84]) by mail-out01.uio.no with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93.0.4) (envelope-from <michawe@ifi.uio.no>) id 1j9ky1-0004cP-Rv; Thu, 05 Mar 2020 08:30:49 +0100
Received: from ti0182q160-5615.bb.online.no ([84.202.72.50] helo=[10.0.0.12]) by mail-mx12.uio.no with esmtpsa (TLS1.2:ECDHE-RSA-AES256-GCM-SHA384:256) user michawe (Exim 4.93.0.4) (envelope-from <michawe@ifi.uio.no>) id 1j9kxz-000D3H-9u; Thu, 05 Mar 2020 08:30:49 +0100
From: Michael Welzl <michawe@ifi.uio.no>
Message-Id: <BA384A88-089E-470C-A7D3-55CABC6DB94B@ifi.uio.no>
Content-Type: multipart/alternative; boundary="Apple-Mail=_A6622064-0580-42B4-92CA-38708276011A"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Thu, 5 Mar 2020 08:30:43 +0100
In-Reply-To: <5E98B07E-795C-4D87-B271-658EB03C7FCC@tiesel.net>
Cc: Kyle Rose <krose@krose.org>, "taps@ietf.org" <taps@ietf.org>
To: "Philipp S. Tiesel" <philipp@tiesel.net>
References: <E9545535-178C-4B9F-91C2-0EB3356DB5B0@ifi.uio.no> <5E98B07E-795C-4D87-B271-658EB03C7FCC@tiesel.net>
X-Mailer: Apple Mail (2.3445.104.11)
X-UiO-SPF-Received: Received-SPF: neutral (mail-mx12.uio.no: 84.202.72.50 is neither permitted nor denied by domain of ifi.uio.no) client-ip=84.202.72.50;  envelope-from=michawe@ifi.uio.no; helo=[10.0.0.12]; 
X-UiO-Spam-info: not spam, SpamAssassin (score=-5.0, required=5.0, autolearn=disabled, HTML_MESSAGE=0.001, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO)
X-UiO-Scanned: 2DBFC087E7BF88282ACD46ED7672EB4AA3951282
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/1Y44BPBcux7oNtmARm6v2NyVXtw>
Subject: Re: [Taps] draft-ietf-taps-interface-05 review
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: Thu, 05 Mar 2020 07:30:59 -0000

--Apple-Mail=_A6622064-0580-42B4-92CA-38708276011A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi,

A few comments in line:

> On Mar 4, 2020, at 5:51 PM, Philipp S. Tiesel <philipp@tiesel.net> =
wrote:
>=20
> Hi,
>=20
> Some of the remaining issues had already been discussed, but either =
did not lead to text or the text was lost. Let me comment on these =
issues:
>=20
>>> On 4. Mar 2020, at 15:38, Michael Welzl <michawe@ifi.uio.no> wrote:
>>=20
>> REMAINING UNADDRESSED COMMENTS FROM KYLE ROSE:
>>=20
>>=20
>> 2. Terminology and Notation
>>=20
>> * The notation "Sender -> Event" says nothing about who receives the =
event. Is it just assumed to be the application in the context of the =
particular event (e.g., a thread processing a particular connection)?
>>=20
>> MW: We have the following statement in this section: "Events could be =
implemented via event queues, handler functions or classes, =
communicating sequential processes, or other asynchronous calling =
conventions."
>> I wonder why this isn't enough information? E.g., if handlers are =
used, then the recipient of the event is a pre-registered handler - and =
handlers must therefore be registered before events can occur; this =
function isn't visible in the API because this is platform- and =
language-specific.
>>=20
>>=20
>> 4.2.1. Transport Property Names
>>=20
>> * The use of dashes in property names means they will necessarily =
look different in almost every widely-used language, in which dash is an =
operator.
>=20
> The solution for this issue was to allow implementations to change the =
property names in consistent ways, e.g., by replacing the dashes with =
underscores or removing them and use CamelCasing.
> The text was removed as over-specific.

I remember that. However, the proposal here would be to just replace the =
property names instead of adding new text.
Let me propose: can we just update them all to CamelCasing?


>> * If we're not currently asking IANA to create a registry of property =
names or namespaces, should we provide a recommendation that such =
symbols not listed explcitly in this document be prefixed with some =
experimental identifier?
>=20
> The IANA registry question was explicitly postponed, be maybe we =
should re-iterate it now.
> The idea of having an =E2=80=9Ex=E2=80=9C namespace was rejected in =
fear we end up with quasi-standard properties that have an x prefix =
then.=20
>>=20
>> 5.2. Specifying Transport Properties
>>=20
>> * There are a lot of choices being made about how users will want to =
prioritize transport protocol selection. How confident are we that, for =
instance, path selection should take priority over protocol selection? I =
think that's right, but I wonder if it might not make more sense to have =
two interfaces: one that provides a purely numeric priority ordering of =
preferences, and one (based on the existing 5-level preferences) that =
maps into it.
>=20
> We had a lengthy discussion about this and rejected it as too complex =
and limiting for the implementation.

Right. Maybe we should just remove this item from this list.


>> * Using the same enum (Require(d[sic])/Avoid/Ignore) for the queried =
output of selected properties seems like a shortcut that will lead to =
some confusion.
>=20
> We had text saying that these should turn into Boolean when queried =
and should reflect whether the protocol stack chosen provides the =
feature. I will have to double-check whether this text is still in the =
description of the preference type.
>=20
>> MW: I agree;  partially addressed: s/Required/Require wherever it's a =
Preference level.
>>=20
>>=20
>> 5.2.5. Use 0-RTT Session Establishment with an Idempotent Message
>>=20
>> * I'll repeat the same statement I made at the mic a few years ago: =
idempotency !=3D replay-safe. DELETE is idempotent, but not safe for =
replay because someone might have done a PUT or POST in the meantime.
>>=20
>> MW: I remember you saying this, sorry that we haven't addressed it =
yet! I didn't understand - is your concern about replaying that a =
Message may arrive later, i.e. as Message X, Messages Y and Z in =
between, then Message X again?  =3D> if so, are you saying that this =
could happen with TFO or QUIC?  (I didn't think so)
>>=20
>>=20
>> 5.2.10. Interface Instance or Type
>>=20
>> * These type symbols really deserve an actual registry, or at least =
the start of one. Otherwise, we are likely to end up with a mess.
>=20
> There is already one, but that one was not useful for our matters.=20
>>=20
>> 5.2.11. Provisioning Domain Instance or Type
>>=20
>> * What about ordering of similar interfaces? I have a 2-SIM cellphone =
with wifi.
>=20
> Each cellular provider will have a unique PVD.=20
>>=20
>> 5.3.2. Connection Establishment Callbacks
>>=20
>> * What constitutes trust verification prior to the handshake?
>>=20
>> 7.3.1. Sent
>>=20
>> * It seems like an abstract API would be helpful for the reference to =
the Message to which a Sent event applies: this seems like something =
many, many applications would need to do. With callbacks, the =
application can always curry in a reference to the original message =
(that's what my event system from ~2001 did), so maybe that should be =
the recommendation and the message reference removed...? I don't have a =
strong feeling here other than that if something is included then its =
use should be more well-defined.
>>=20
>> 7.3.3. SendError
>>=20
>> * Is there a reason why a single messageContext object is used for =
both sends and receives? I probably missed the original discussion about =
this, but I'd like to understand the reasoning.
>>=20
>> MW: I don't get this, where does it say that it's only a single =
object? Or do you mean that it's the same type? Why is that problematic?
>>=20
>>=20
>> 7.4.7. Reliable Data Transfer (Message)
>>=20
>> * The default isn't "true", it's whatever the underlying connection =
had, right?
>=20
> Ack

I agree too, but doesn=E2=80=99t this warrant some more discussion?
I think our defaults all translate into things that can work in some way =
when TCP is used - with =E2=80=9CReliable Data Transfer=E2=80=9D being =
an exception, as it just can=E2=80=99t work in a UDP-only system. Are =
there others?  I think I=E2=80=99ll open an issue for this one.



>> 8. Receiving Data
>>=20
>> * A connection can be used to receive data if it is not configured as =
unidirectional transmit.
>>=20
>> MW: that's obviously correct - but I can't find a statement that =
would contradict what you say here.
>>=20
>>=20
>> 8.2. Receive Events
>>=20
>> * "A call to Receive will be paired with a single Receive Event" or =
possibly multiple ReceivedPartial Events?
>>=20
>> * Also, can the draft be consistent about Receive vs. Received, et =
al.?
>>=20
>>=20
>> 11. General comments
>>=20
>> * There's a lot of UNIXisms here that should probably be excised in =
favor of a more abstract presentation. The most obvious is the use of -1 =
to mean something other than the integer -1. In Python, for instance, =
you might want to use None for this purpose. I would specify non-numeric =
values symbolically, and maybe indicate in the appendix that a UNIX C =
implementation might want to use -1 to represent such values.
>>=20
>> MW: agreed... TODO.
>>=20
>>=20
>> 11.1.10. Capacity Profile
>>=20
>> * Very little of this section is about capacity. Traffic Profile?
>>=20
>> * "High Throughput Data" might be better phrased as =
"Capacity-Seeking".
>>=20
>> _______________________________________________
>> Taps mailing list
>> Taps@ietf.org <mailto:Taps@ietf.org>
>> https://www.ietf.org/mailman/listinfo/taps =
<https://www.ietf.org/mailman/listinfo/taps>

Cheers,
Michael



--Apple-Mail=_A6622064-0580-42B4-92CA-38708276011A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D"">Hi,<div class=3D""><br class=3D""></div><div class=3D"">A few =
comments in line:<br class=3D""><div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D"">On Mar 4, 2020, at 5:51 PM, =
Philipp S. Tiesel &lt;<a href=3D"mailto:philipp@tiesel.net" =
class=3D"">philipp@tiesel.net</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">Hi,</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">Some of the remaining issues had =
already been discussed, but either did not lead to text or the text was =
lost. Let me comment on these issues:</span><br style=3D"caret-color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><blockquote type=3D"cite" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><blockquote type=3D"cite" class=3D"">On=
 4. Mar 2020, at 15:38, Michael Welzl &lt;<a =
href=3D"mailto:michawe@ifi.uio.no" class=3D"">michawe@ifi.uio.no</a>&gt; =
wrote:<br class=3D""></blockquote><br class=3D"">REMAINING UNADDRESSED =
COMMENTS FROM KYLE ROSE:<br class=3D""><br class=3D""><br class=3D"">2. =
Terminology and Notation<br class=3D""><br class=3D"">* The notation =
"Sender -&gt; Event" says nothing about who receives the event. Is it =
just assumed to be the application in the context of the particular =
event (e.g., a thread processing a particular connection)?<br =
class=3D""><br class=3D"">MW: We have the following statement in this =
section: "Events could be implemented via event queues, handler =
functions or classes, communicating sequential processes, or other =
asynchronous calling conventions."<br class=3D"">I wonder why this isn't =
enough information? E.g., if handlers are used, then the recipient of =
the event is a pre-registered handler - and handlers must therefore be =
registered before events can occur; this function isn't visible in the =
API because this is platform- and language-specific.<br class=3D""><br =
class=3D""><br class=3D"">4.2.1. Transport Property Names<br =
class=3D""><br class=3D"">* The use of dashes in property names means =
they will necessarily look different in almost every widely-used =
language, in which dash is an operator.<br class=3D""></blockquote><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">The solution for this issue was =
to allow implementations to change the property names in consistent =
ways, e.g., by replacing the dashes with underscores or removing them =
and use CamelCasing.</span><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">The text was removed as over-specific.</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" =
class=3D""></div></blockquote><div><br class=3D""></div><div>I remember =
that. However, the proposal here would be to just replace the property =
names instead of adding new text.</div><div>Let me propose: can we just =
update them all to CamelCasing?</div><div><br class=3D""></div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D"">* If =
we're not currently asking IANA to create a registry of property names =
or namespaces, should we provide a recommendation that such symbols not =
listed explcitly in this document be prefixed with some experimental =
identifier?<br class=3D""></blockquote><br style=3D"caret-color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">The IANA registry question was explicitly postponed, be maybe =
we should re-iterate it now.</span><br style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">The idea of having an =E2=80=9Ex=E2=80=9C namespace was =
rejected in fear we end up with quasi-standard properties that have an x =
prefix then.<span class=3D"Apple-converted-space">&nbsp;</span></span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" =
class=3D""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><br =
class=3D"">5.2. Specifying Transport Properties<br class=3D""><br =
class=3D"">* There are a lot of choices being made about how users will =
want to prioritize transport protocol selection. How confident are we =
that, for instance, path selection should take priority over protocol =
selection? I think that's right, but I wonder if it might not make more =
sense to have two interfaces: one that provides a purely numeric =
priority ordering of preferences, and one (based on the existing 5-level =
preferences) that maps into it.<br class=3D""></blockquote><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">We had a lengthy discussion =
about this and rejected it as too complex and limiting for the =
implementation.</span><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""></div></blockquote><div><br =
class=3D""></div>Right. Maybe we should just remove this item from this =
list.</div><div><br class=3D""></div><div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><blockquote type=3D"cite" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D"">* Using the same enum =
(Require(d[sic])/Avoid/Ignore) for the queried output of selected =
properties seems like a shortcut that will lead to some confusion.<br =
class=3D""></blockquote><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">We had text saying that these should turn into Boolean when =
queried and should reflect whether the protocol stack chosen provides =
the feature. I will have to double-check whether this text is still in =
the description of the preference type.</span><br style=3D"caret-color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><blockquote type=3D"cite" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D"">MW: I agree; &nbsp;partially =
addressed: s/Required/Require wherever it's a Preference level.<br =
class=3D""><br class=3D""><br class=3D"">5.2.5. Use 0-RTT Session =
Establishment with an Idempotent Message<br class=3D""><br class=3D"">* =
I'll repeat the same statement I made at the mic a few years ago: =
idempotency !=3D replay-safe. DELETE is idempotent, but not safe for =
replay because someone might have done a PUT or POST in the meantime.<br =
class=3D""><br class=3D"">MW: I remember you saying this, sorry that we =
haven't addressed it yet! I didn't understand - is your concern about =
replaying that a Message may arrive later, i.e. as Message X, Messages Y =
and Z in between, then Message X again? &nbsp;=3D&gt; if so, are you =
saying that this could happen with TFO or QUIC? &nbsp;(I didn't think =
so)<br class=3D""><br class=3D""><br class=3D"">5.2.10. Interface =
Instance or Type<br class=3D""><br class=3D"">* These type symbols =
really deserve an actual registry, or at least the start of one. =
Otherwise, we are likely to end up with a mess.<br =
class=3D""></blockquote><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">There is already one, but that one was not useful for our =
matters.<span class=3D"Apple-converted-space">&nbsp;</span></span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" =
class=3D""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><br =
class=3D"">5.2.11. Provisioning Domain Instance or Type<br class=3D""><br =
class=3D"">* What about ordering of similar interfaces? I have a 2-SIM =
cellphone with wifi.<br class=3D""></blockquote><br style=3D"caret-color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">Each cellular provider will have a unique PVD.<span =
class=3D"Apple-converted-space">&nbsp;</span></span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" =
class=3D""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><br =
class=3D"">5.3.2. Connection Establishment Callbacks<br class=3D""><br =
class=3D"">* What constitutes trust verification prior to the =
handshake?<br class=3D""><br class=3D"">7.3.1. Sent<br class=3D""><br =
class=3D"">* It seems like an abstract API would be helpful for the =
reference to the Message to which a Sent event applies: this seems like =
something many, many applications would need to do. With callbacks, the =
application can always curry in a reference to the original message =
(that's what my event system from ~2001 did), so maybe that should be =
the recommendation and the message reference removed...? I don't have a =
strong feeling here other than that if something is included then its =
use should be more well-defined.<br class=3D""><br class=3D"">7.3.3. =
SendError<br class=3D""><br class=3D"">* Is there a reason why a single =
messageContext object is used for both sends and receives? I probably =
missed the original discussion about this, but I'd like to understand =
the reasoning.<br class=3D""><br class=3D"">MW: I don't get this, where =
does it say that it's only a single object? Or do you mean that it's the =
same type? Why is that problematic?<br class=3D""><br class=3D""><br =
class=3D"">7.4.7. Reliable Data Transfer (Message)<br class=3D""><br =
class=3D"">* The default isn't "true", it's whatever the underlying =
connection had, right?<br class=3D""></blockquote><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">Ack</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" =
class=3D""></div></blockquote><div><br class=3D""></div><div>I agree =
too, but doesn=E2=80=99t this warrant some more discussion?</div><div>I =
think our defaults all translate into things that can work in some way =
when TCP is used - with =E2=80=9CReliable Data Transfer=E2=80=9D being =
an exception, as it just can=E2=80=99t work in a UDP-only system. Are =
there others? &nbsp;I think I=E2=80=99ll open an issue for this =
one.</div><div><br class=3D""></div><div><br class=3D""></div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D"">8. =
Receiving Data<br class=3D""><br class=3D"">* A connection can be used =
to receive data if it is not configured as unidirectional transmit.<br =
class=3D""><br class=3D"">MW: that's obviously correct - but I can't =
find a statement that would contradict what you say here.<br =
class=3D""><br class=3D""><br class=3D"">8.2. Receive Events<br =
class=3D""><br class=3D"">* "A call to Receive will be paired with a =
single Receive Event" or possibly multiple ReceivedPartial Events?<br =
class=3D""><br class=3D"">* Also, can the draft be consistent about =
Receive vs. Received, et al.?<br class=3D""><br class=3D""><br =
class=3D"">11. General comments<br class=3D""><br class=3D"">* There's a =
lot of UNIXisms here that should probably be excised in favor of a more =
abstract presentation. The most obvious is the use of -1 to mean =
something other than the integer -1. In Python, for instance, you might =
want to use None for this purpose. I would specify non-numeric values =
symbolically, and maybe indicate in the appendix that a UNIX C =
implementation might want to use -1 to represent such values.<br =
class=3D""><br class=3D"">MW: agreed... TODO.<br class=3D""><br =
class=3D""><br class=3D"">11.1.10. Capacity Profile<br class=3D""><br =
class=3D"">* Very little of this section is about capacity. Traffic =
Profile?<br class=3D""><br class=3D"">* "High Throughput Data" might be =
better phrased as "Capacity-Seeking".<br class=3D""><br =
class=3D"">_______________________________________________<br =
class=3D"">Taps mailing list<br class=3D""><a =
href=3D"mailto:Taps@ietf.org" class=3D"">Taps@ietf.org</a><br =
class=3D""><a href=3D"https://www.ietf.org/mailman/listinfo/taps" =
class=3D"">https://www.ietf.org/mailman/listinfo/taps</a></blockquote></di=
v></blockquote><br class=3D""></div><div><br =
class=3D""></div><div>Cheers,</div><div>Michael</div><div><br =
class=3D""></div><br class=3D""></div></body></html>=

--Apple-Mail=_A6622064-0580-42B4-92CA-38708276011A--


From nobody Wed Mar  4 23:55:40 2020
Return-Path: <gorry@erg.abdn.ac.uk>
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 996113A0F79 for <taps@ietfa.amsl.com>; Wed,  4 Mar 2020 23:55:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level: 
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 xB3LHhZ8jvaD for <taps@ietfa.amsl.com>; Wed,  4 Mar 2020 23:55:35 -0800 (PST)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [IPv6:2001:630:42:150::2]) by ietfa.amsl.com (Postfix) with ESMTP id B45FB3A0F6D for <taps@ietf.org>; Wed,  4 Mar 2020 23:55:34 -0800 (PST)
Received: from GF-MacBook-Pro.local (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id 89C7F1B00238; Thu,  5 Mar 2020 07:55:28 +0000 (GMT)
To: Michael Welzl <michawe@ifi.uio.no>, "Philipp S. Tiesel" <philipp@tiesel.net>
Cc: Kyle Rose <krose@krose.org>, "taps@ietf.org" <taps@ietf.org>
References: <E9545535-178C-4B9F-91C2-0EB3356DB5B0@ifi.uio.no> <5E98B07E-795C-4D87-B271-658EB03C7FCC@tiesel.net> <BA384A88-089E-470C-A7D3-55CABC6DB94B@ifi.uio.no>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Message-ID: <7e28ca42-334d-ecab-7984-55b58c24e639@erg.abdn.ac.uk>
Date: Thu, 5 Mar 2020 07:55:27 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:68.0) Gecko/20100101 Thunderbird/68.5.0
MIME-Version: 1.0
In-Reply-To: <BA384A88-089E-470C-A7D3-55CABC6DB94B@ifi.uio.no>
Content-Type: multipart/alternative; boundary="------------891203FC41D5868658EFEC75"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/9fTCLpLvTLOzuAJhdZlhDFAcGXU>
Subject: Re: [Taps] draft-ietf-taps-interface-05 review
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: Thu, 05 Mar 2020 07:55:39 -0000

This is a multi-part message in MIME format.
--------------891203FC41D5868658EFEC75
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

See in-line


On 05/03/2020 07:30, Michael Welzl wrote:
> Hi,
>
> A few comments in line:
>
>> On Mar 4, 2020, at 5:51 PM, Philipp S. Tiesel <philipp@tiesel.net 
>> <mailto:philipp@tiesel.net>> wrote:
>>
>> Hi,
>>
>> Some of the remaining issues had already been discussed, but either 
>> did not lead to text or the text was lost. Let me comment on these 
>> issues:
>>
>>>> On 4. Mar 2020, at 15:38, Michael Welzl <michawe@ifi.uio.no 
>>>> <mailto:michawe@ifi.uio.no>> wrote:
>>>
>>> REMAINING UNADDRESSED COMMENTS FROM KYLE ROSE:
>>>
>>>
>>> 2. Terminology and Notation
>>>
>>> * The notation "Sender -> Event" says nothing about who receives the 
>>> event. Is it just assumed to be the application in the context of 
>>> the particular event (e.g., a thread processing a particular 
>>> connection)?
>>>
>>> MW: We have the following statement in this section: "Events could 
>>> be implemented via event queues, handler functions or classes, 
>>> communicating sequential processes, or other asynchronous calling 
>>> conventions."
>>> I wonder why this isn't enough information? E.g., if handlers are 
>>> used, then the recipient of the event is a pre-registered handler - 
>>> and handlers must therefore be registered before events can occur; 
>>> this function isn't visible in the API because this is platform- and 
>>> language-specific.
>>>
>>>
>>> 4.2.1. Transport Property Names
>>>
>>> * The use of dashes in property names means they will necessarily 
>>> look different in almost every widely-used language, in which dash 
>>> is an operator.
>>
>> The solution for this issue was to allow implementations to change 
>> the property names in consistent ways, e.g., by replacing the dashes 
>> with underscores or removing them and use CamelCasing.
>> The text was removed as over-specific.
>
> I remember that. However, the proposal here would be to just replace 
> the property names instead of adding new text.
> Let me propose: can we just update them all to CamelCasing?
>
I like this idea.
>
>>> * If we're not currently asking IANA to create a registry of 
>>> property names or namespaces, should we provide a recommendation 
>>> that such symbols not listed explcitly in this document be prefixed 
>>> with some experimental identifier?
>>
>> The IANA registry question was explicitly postponed, be maybe we 
>> should re-iterate it now.
>> The idea of having an „x“ namespace was rejected in fear we end up 
>> with quasi-standard properties that have an x prefix then.
>>>
>>> 5.2. Specifying Transport Properties
>>>
>>> * There are a lot of choices being made about how users will want to 
>>> prioritize transport protocol selection. How confident are we that, 
>>> for instance, path selection should take priority over protocol 
>>> selection? I think that's right, but I wonder if it might not make 
>>> more sense to have two interfaces: one that provides a purely 
>>> numeric priority ordering of preferences, and one (based on the 
>>> existing 5-level preferences) that maps into it.
>>
>> We had a lengthy discussion about this and rejected it as too complex 
>> and limiting for the implementation.
>
> Right. Maybe we should just remove this item from this list.
>
>>> * Using the same enum (Require(d[sic])/Avoid/Ignore) for the queried 
>>> output of selected properties seems like a shortcut that will lead 
>>> to some confusion.
>>
>> We had text saying that these should turn into Boolean when queried 
>> and should reflect whether the protocol stack chosen provides the 
>> feature. I will have to double-check whether this text is still in 
>> the description of the preference type.
>>
>>> MW: I agree;  partially addressed: s/Required/Require wherever it's 
>>> a Preference level.
>>>
>>>
>>> 5.2.5. Use 0-RTT Session Establishment with an Idempotent Message
>>>
>>> * I'll repeat the same statement I made at the mic a few years ago: 
>>> idempotency != replay-safe. DELETE is idempotent, but not safe for 
>>> replay because someone might have done a PUT or POST in the meantime.
>>>
>>> MW: I remember you saying this, sorry that we haven't addressed it 
>>> yet! I didn't understand - is your concern about replaying that a 
>>> Message may arrive later, i.e. as Message X, Messages Y and Z in 
>>> between, then Message X again?  => if so, are you saying that this 
>>> could happen with TFO or QUIC?  (I didn't think so)
>>>
>>>
>>> 5.2.10. Interface Instance or Type
>>>
>>> * These type symbols really deserve an actual registry, or at least 
>>> the start of one. Otherwise, we are likely to end up with a mess.
>>
>> There is already one, but that one was not useful for our matters.
>>>
>>> 5.2.11. Provisioning Domain Instance or Type
>>>
>>> * What about ordering of similar interfaces? I have a 2-SIM 
>>> cellphone with wifi.
>>
>> Each cellular provider will have a unique PVD.
>>>
>>> 5.3.2. Connection Establishment Callbacks
>>>
>>> * What constitutes trust verification prior to the handshake?
>>>
>>> 7.3.1. Sent
>>>
>>> * It seems like an abstract API would be helpful for the reference 
>>> to the Message to which a Sent event applies: this seems like 
>>> something many, many applications would need to do. With callbacks, 
>>> the application can always curry in a reference to the original 
>>> message (that's what my event system from ~2001 did), so maybe that 
>>> should be the recommendation and the message reference removed...? I 
>>> don't have a strong feeling here other than that if something is 
>>> included then its use should be more well-defined.
>>>
>>> 7.3.3. SendError
>>>
>>> * Is there a reason why a single messageContext object is used for 
>>> both sends and receives? I probably missed the original discussion 
>>> about this, but I'd like to understand the reasoning.
>>>
>>> MW: I don't get this, where does it say that it's only a single 
>>> object? Or do you mean that it's the same type? Why is that problematic?
>>>
>>>
>>> 7.4.7. Reliable Data Transfer (Message)
>>>
>>> * The default isn't "true", it's whatever the underlying connection 
>>> had, right?
>>
>> Ack
>
> I agree too, but doesn’t this warrant some more discussion?
> I think our defaults all translate into things that can work in some 
> way when TCP is used - with “Reliable Data Transfer” being an 
> exception, as it just can’t work in a UDP-only system. Are there 
> others?  I think I’ll open an issue for this one.
>
I don't agree at all - To me this was just the default behaviour of the API.

I think the default needs to be "reliable" and an app will have to 
over-ride that to get datagram/unreliable operation. That doesn't mean 
if you have only UDP (for instance) that you can't offer TAPS, to me it 
simply means you always need to say that the app wants this service.

>
>
>>> 8. Receiving Data
>>>
>>> * A connection can be used to receive data if it is not configured 
>>> as unidirectional transmit.
>>>
>>> MW: that's obviously correct - but I can't find a statement that 
>>> would contradict what you say here.
>>>
>>>
>>> 8.2. Receive Events
>>>
>>> * "A call to Receive will be paired with a single Receive Event" or 
>>> possibly multiple ReceivedPartial Events?
>>>
>>> * Also, can the draft be consistent about Receive vs. Received, et al.?
>>>
>>>
>>> 11. General comments
>>>
>>> * There's a lot of UNIXisms here that should probably be excised in 
>>> favor of a more abstract presentation. The most obvious is the use 
>>> of -1 to mean something other than the integer -1. In Python, for 
>>> instance, you might want to use None for this purpose. I would 
>>> specify non-numeric values symbolically, and maybe indicate in the 
>>> appendix that a UNIX C implementation might want to use -1 to 
>>> represent such values.
>>>
>>> MW: agreed... TODO.
>>>
>>>
>>> 11.1.10. Capacity Profile
>>>
>>> * Very little of this section is about capacity. Traffic Profile?
>>>
>>> * "High Throughput Data" might be better phrased as "Capacity-Seeking".
>>>
I don't much like Traffic Profile - to a traffic profile specifies the 
characteristics of the traffic the sender is transmitting, not the 
treatment that traffic expects from the network service.

I also object to /bandwidth efficiency/ - since sounds like it should be 
measured in b/Hz which isn't at all what we are talking about. In fact, 
I did not see anything in the text about the efficiency or the use of 
bandwith ... as I read, it is all about capacity sharing tradeoffs.
>>> _______________________________________________
>>> Taps mailing list
>>> Taps@ietf.org <mailto:Taps@ietf.org>
>>> https://www.ietf.org/mailman/listinfo/taps
>
>
> Cheers,
> Michael
>
>
Best wishes,

Gorry



--------------891203FC41D5868658EFEC75
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>See in-line</p>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 05/03/2020 07:30, Michael Welzl
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:BA384A88-089E-470C-A7D3-55CABC6DB94B@ifi.uio.no">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      Hi,
      <div class=""><br class="">
      </div>
      <div class="">A few comments in line:<br class="">
        <div><br class="">
          <blockquote type="cite" class="">
            <div class="">On Mar 4, 2020, at 5:51 PM, Philipp S. Tiesel
              &lt;<a href="mailto:philipp@tiesel.net" class=""
                moz-do-not-send="true">philipp@tiesel.net</a>&gt; wrote:</div>
            <br class="Apple-interchange-newline">
            <div class=""><span style="caret-color: rgb(0, 0, 0);
                font-family: Helvetica; font-size: 12px; font-style:
                normal; font-variant-caps: normal; font-weight: normal;
                letter-spacing: normal; text-align: start; text-indent:
                0px; text-transform: none; white-space: normal;
                word-spacing: 0px; -webkit-text-stroke-width: 0px;
                text-decoration: none; float: none; display: inline
                !important;" class="">Hi,</span><br style="caret-color:
                rgb(0, 0, 0); font-family: Helvetica; font-size: 12px;
                font-style: normal; font-variant-caps: normal;
                font-weight: normal; letter-spacing: normal; text-align:
                start; text-indent: 0px; text-transform: none;
                white-space: normal; word-spacing: 0px;
                -webkit-text-stroke-width: 0px; text-decoration: none;"
                class="">
              <br style="caret-color: rgb(0, 0, 0); font-family:
                Helvetica; font-size: 12px; font-style: normal;
                font-variant-caps: normal; font-weight: normal;
                letter-spacing: normal; text-align: start; text-indent:
                0px; text-transform: none; white-space: normal;
                word-spacing: 0px; -webkit-text-stroke-width: 0px;
                text-decoration: none;" class="">
              <span style="caret-color: rgb(0, 0, 0); font-family:
                Helvetica; font-size: 12px; font-style: normal;
                font-variant-caps: normal; font-weight: normal;
                letter-spacing: normal; text-align: start; text-indent:
                0px; text-transform: none; white-space: normal;
                word-spacing: 0px; -webkit-text-stroke-width: 0px;
                text-decoration: none; float: none; display: inline
                !important;" class="">Some of the remaining issues had
                already been discussed, but either did not lead to text
                or the text was lost. Let me comment on these issues:</span><br
                style="caret-color: rgb(0, 0, 0); font-family:
                Helvetica; font-size: 12px; font-style: normal;
                font-variant-caps: normal; font-weight: normal;
                letter-spacing: normal; text-align: start; text-indent:
                0px; text-transform: none; white-space: normal;
                word-spacing: 0px; -webkit-text-stroke-width: 0px;
                text-decoration: none;" class="">
              <br style="caret-color: rgb(0, 0, 0); font-family:
                Helvetica; font-size: 12px; font-style: normal;
                font-variant-caps: normal; font-weight: normal;
                letter-spacing: normal; text-align: start; text-indent:
                0px; text-transform: none; white-space: normal;
                word-spacing: 0px; -webkit-text-stroke-width: 0px;
                text-decoration: none;" class="">
              <blockquote type="cite" style="font-family: Helvetica;
                font-size: 12px; font-style: normal; font-variant-caps:
                normal; font-weight: normal; letter-spacing: normal;
                orphans: auto; text-align: start; text-indent: 0px;
                text-transform: none; white-space: normal; widows: auto;
                word-spacing: 0px; -webkit-text-size-adjust: auto;
                -webkit-text-stroke-width: 0px; text-decoration: none;"
                class="">
                <blockquote type="cite" class="">On 4. Mar 2020, at
                  15:38, Michael Welzl &lt;<a
                    href="mailto:michawe@ifi.uio.no" class=""
                    moz-do-not-send="true">michawe@ifi.uio.no</a>&gt;
                  wrote:<br class="">
                </blockquote>
                <br class="">
                REMAINING UNADDRESSED COMMENTS FROM KYLE ROSE:<br
                  class="">
                <br class="">
                <br class="">
                2. Terminology and Notation<br class="">
                <br class="">
                * The notation "Sender -&gt; Event" says nothing about
                who receives the event. Is it just assumed to be the
                application in the context of the particular event
                (e.g., a thread processing a particular connection)?<br
                  class="">
                <br class="">
                MW: We have the following statement in this section:
                "Events could be implemented via event queues, handler
                functions or classes, communicating sequential
                processes, or other asynchronous calling conventions."<br
                  class="">
                I wonder why this isn't enough information? E.g., if
                handlers are used, then the recipient of the event is a
                pre-registered handler - and handlers must therefore be
                registered before events can occur; this function isn't
                visible in the API because this is platform- and
                language-specific.<br class="">
                <br class="">
                <br class="">
                4.2.1. Transport Property Names<br class="">
                <br class="">
                * The use of dashes in property names means they will
                necessarily look different in almost every widely-used
                language, in which dash is an operator.<br class="">
              </blockquote>
              <br style="caret-color: rgb(0, 0, 0); font-family:
                Helvetica; font-size: 12px; font-style: normal;
                font-variant-caps: normal; font-weight: normal;
                letter-spacing: normal; text-align: start; text-indent:
                0px; text-transform: none; white-space: normal;
                word-spacing: 0px; -webkit-text-stroke-width: 0px;
                text-decoration: none;" class="">
              <span style="caret-color: rgb(0, 0, 0); font-family:
                Helvetica; font-size: 12px; font-style: normal;
                font-variant-caps: normal; font-weight: normal;
                letter-spacing: normal; text-align: start; text-indent:
                0px; text-transform: none; white-space: normal;
                word-spacing: 0px; -webkit-text-stroke-width: 0px;
                text-decoration: none; float: none; display: inline
                !important;" class="">The solution for this issue was to
                allow implementations to change the property names in
                consistent ways, e.g., by replacing the dashes with
                underscores or removing them and use CamelCasing.</span><br
                style="caret-color: rgb(0, 0, 0); font-family:
                Helvetica; font-size: 12px; font-style: normal;
                font-variant-caps: normal; font-weight: normal;
                letter-spacing: normal; text-align: start; text-indent:
                0px; text-transform: none; white-space: normal;
                word-spacing: 0px; -webkit-text-stroke-width: 0px;
                text-decoration: none;" class="">
              <span style="caret-color: rgb(0, 0, 0); font-family:
                Helvetica; font-size: 12px; font-style: normal;
                font-variant-caps: normal; font-weight: normal;
                letter-spacing: normal; text-align: start; text-indent:
                0px; text-transform: none; white-space: normal;
                word-spacing: 0px; -webkit-text-stroke-width: 0px;
                text-decoration: none; float: none; display: inline
                !important;" class="">The text was removed as
                over-specific.</span><br style="caret-color: rgb(0, 0,
                0); font-family: Helvetica; font-size: 12px; font-style:
                normal; font-variant-caps: normal; font-weight: normal;
                letter-spacing: normal; text-align: start; text-indent:
                0px; text-transform: none; white-space: normal;
                word-spacing: 0px; -webkit-text-stroke-width: 0px;
                text-decoration: none;" class="">
            </div>
          </blockquote>
          <div><br class="">
          </div>
          <div>I remember that. However, the proposal here would be to
            just replace the property names instead of adding new text.</div>
          <div>Let me propose: can we just update them all to
            CamelCasing?</div>
          <div><br class="">
          </div>
        </div>
      </div>
    </blockquote>
    I like this idea.<br>
    <blockquote type="cite"
      cite="mid:BA384A88-089E-470C-A7D3-55CABC6DB94B@ifi.uio.no">
      <div class="">
        <div><br class="">
          <blockquote type="cite" class="">
            <div class="">
              <blockquote type="cite" style="font-family: Helvetica;
                font-size: 12px; font-style: normal; font-variant-caps:
                normal; font-weight: normal; letter-spacing: normal;
                orphans: auto; text-align: start; text-indent: 0px;
                text-transform: none; white-space: normal; widows: auto;
                word-spacing: 0px; -webkit-text-size-adjust: auto;
                -webkit-text-stroke-width: 0px; text-decoration: none;"
                class="">* If we're not currently asking IANA to create
                a registry of property names or namespaces, should we
                provide a recommendation that such symbols not listed
                explcitly in this document be prefixed with some
                experimental identifier?<br class="">
              </blockquote>
              <br style="caret-color: rgb(0, 0, 0); font-family:
                Helvetica; font-size: 12px; font-style: normal;
                font-variant-caps: normal; font-weight: normal;
                letter-spacing: normal; text-align: start; text-indent:
                0px; text-transform: none; white-space: normal;
                word-spacing: 0px; -webkit-text-stroke-width: 0px;
                text-decoration: none;" class="">
              <span style="caret-color: rgb(0, 0, 0); font-family:
                Helvetica; font-size: 12px; font-style: normal;
                font-variant-caps: normal; font-weight: normal;
                letter-spacing: normal; text-align: start; text-indent:
                0px; text-transform: none; white-space: normal;
                word-spacing: 0px; -webkit-text-stroke-width: 0px;
                text-decoration: none; float: none; display: inline
                !important;" class="">The IANA registry question was
                explicitly postponed, be maybe we should re-iterate it
                now.</span><br style="caret-color: rgb(0, 0, 0);
                font-family: Helvetica; font-size: 12px; font-style:
                normal; font-variant-caps: normal; font-weight: normal;
                letter-spacing: normal; text-align: start; text-indent:
                0px; text-transform: none; white-space: normal;
                word-spacing: 0px; -webkit-text-stroke-width: 0px;
                text-decoration: none;" class="">
              <span style="caret-color: rgb(0, 0, 0); font-family:
                Helvetica; font-size: 12px; font-style: normal;
                font-variant-caps: normal; font-weight: normal;
                letter-spacing: normal; text-align: start; text-indent:
                0px; text-transform: none; white-space: normal;
                word-spacing: 0px; -webkit-text-stroke-width: 0px;
                text-decoration: none; float: none; display: inline
                !important;" class="">The idea of having an „x“
                namespace was rejected in fear we end up with
                quasi-standard properties that have an x prefix then.<span
                  class="Apple-converted-space"> </span></span><br
                style="caret-color: rgb(0, 0, 0); font-family:
                Helvetica; font-size: 12px; font-style: normal;
                font-variant-caps: normal; font-weight: normal;
                letter-spacing: normal; text-align: start; text-indent:
                0px; text-transform: none; white-space: normal;
                word-spacing: 0px; -webkit-text-stroke-width: 0px;
                text-decoration: none;" class="">
              <blockquote type="cite" style="font-family: Helvetica;
                font-size: 12px; font-style: normal; font-variant-caps:
                normal; font-weight: normal; letter-spacing: normal;
                orphans: auto; text-align: start; text-indent: 0px;
                text-transform: none; white-space: normal; widows: auto;
                word-spacing: 0px; -webkit-text-size-adjust: auto;
                -webkit-text-stroke-width: 0px; text-decoration: none;"
                class=""><br class="">
                5.2. Specifying Transport Properties<br class="">
                <br class="">
                * There are a lot of choices being made about how users
                will want to prioritize transport protocol selection.
                How confident are we that, for instance, path selection
                should take priority over protocol selection? I think
                that's right, but I wonder if it might not make more
                sense to have two interfaces: one that provides a purely
                numeric priority ordering of preferences, and one (based
                on the existing 5-level preferences) that maps into it.<br
                  class="">
              </blockquote>
              <br style="caret-color: rgb(0, 0, 0); font-family:
                Helvetica; font-size: 12px; font-style: normal;
                font-variant-caps: normal; font-weight: normal;
                letter-spacing: normal; text-align: start; text-indent:
                0px; text-transform: none; white-space: normal;
                word-spacing: 0px; -webkit-text-stroke-width: 0px;
                text-decoration: none;" class="">
              <span style="caret-color: rgb(0, 0, 0); font-family:
                Helvetica; font-size: 12px; font-style: normal;
                font-variant-caps: normal; font-weight: normal;
                letter-spacing: normal; text-align: start; text-indent:
                0px; text-transform: none; white-space: normal;
                word-spacing: 0px; -webkit-text-stroke-width: 0px;
                text-decoration: none; float: none; display: inline
                !important;" class="">We had a lengthy discussion about
                this and rejected it as too complex and limiting for the
                implementation.</span><br style="caret-color: rgb(0, 0,
                0); font-family: Helvetica; font-size: 12px; font-style:
                normal; font-variant-caps: normal; font-weight: normal;
                letter-spacing: normal; text-align: start; text-indent:
                0px; text-transform: none; white-space: normal;
                word-spacing: 0px; -webkit-text-stroke-width: 0px;
                text-decoration: none;" class="">
            </div>
          </blockquote>
          <div><br class="">
          </div>
          Right. Maybe we should just remove this item from this list.</div>
      </div>
    </blockquote>
    <blockquote type="cite"
      cite="mid:BA384A88-089E-470C-A7D3-55CABC6DB94B@ifi.uio.no">
      <div class="">
        <div><br class="">
          <blockquote type="cite" class="">
            <div class="">
              <blockquote type="cite" style="font-family: Helvetica;
                font-size: 12px; font-style: normal; font-variant-caps:
                normal; font-weight: normal; letter-spacing: normal;
                orphans: auto; text-align: start; text-indent: 0px;
                text-transform: none; white-space: normal; widows: auto;
                word-spacing: 0px; -webkit-text-size-adjust: auto;
                -webkit-text-stroke-width: 0px; text-decoration: none;"
                class="">* Using the same enum
                (Require(d[sic])/Avoid/Ignore) for the queried output of
                selected properties seems like a shortcut that will lead
                to some confusion.<br class="">
              </blockquote>
              <br style="caret-color: rgb(0, 0, 0); font-family:
                Helvetica; font-size: 12px; font-style: normal;
                font-variant-caps: normal; font-weight: normal;
                letter-spacing: normal; text-align: start; text-indent:
                0px; text-transform: none; white-space: normal;
                word-spacing: 0px; -webkit-text-stroke-width: 0px;
                text-decoration: none;" class="">
              <span style="caret-color: rgb(0, 0, 0); font-family:
                Helvetica; font-size: 12px; font-style: normal;
                font-variant-caps: normal; font-weight: normal;
                letter-spacing: normal; text-align: start; text-indent:
                0px; text-transform: none; white-space: normal;
                word-spacing: 0px; -webkit-text-stroke-width: 0px;
                text-decoration: none; float: none; display: inline
                !important;" class="">We had text saying that these
                should turn into Boolean when queried and should reflect
                whether the protocol stack chosen provides the feature.
                I will have to double-check whether this text is still
                in the description of the preference type.</span><br
                style="caret-color: rgb(0, 0, 0); font-family:
                Helvetica; font-size: 12px; font-style: normal;
                font-variant-caps: normal; font-weight: normal;
                letter-spacing: normal; text-align: start; text-indent:
                0px; text-transform: none; white-space: normal;
                word-spacing: 0px; -webkit-text-stroke-width: 0px;
                text-decoration: none;" class="">
              <br style="caret-color: rgb(0, 0, 0); font-family:
                Helvetica; font-size: 12px; font-style: normal;
                font-variant-caps: normal; font-weight: normal;
                letter-spacing: normal; text-align: start; text-indent:
                0px; text-transform: none; white-space: normal;
                word-spacing: 0px; -webkit-text-stroke-width: 0px;
                text-decoration: none;" class="">
              <blockquote type="cite" style="font-family: Helvetica;
                font-size: 12px; font-style: normal; font-variant-caps:
                normal; font-weight: normal; letter-spacing: normal;
                orphans: auto; text-align: start; text-indent: 0px;
                text-transform: none; white-space: normal; widows: auto;
                word-spacing: 0px; -webkit-text-size-adjust: auto;
                -webkit-text-stroke-width: 0px; text-decoration: none;"
                class="">MW: I agree;  partially addressed:
                s/Required/Require wherever it's a Preference level.<br
                  class="">
                <br class="">
                <br class="">
                5.2.5. Use 0-RTT Session Establishment with an
                Idempotent Message<br class="">
                <br class="">
                * I'll repeat the same statement I made at the mic a few
                years ago: idempotency != replay-safe. DELETE is
                idempotent, but not safe for replay because someone
                might have done a PUT or POST in the meantime.<br
                  class="">
                <br class="">
                MW: I remember you saying this, sorry that we haven't
                addressed it yet! I didn't understand - is your concern
                about replaying that a Message may arrive later, i.e. as
                Message X, Messages Y and Z in between, then Message X
                again?  =&gt; if so, are you saying that this could
                happen with TFO or QUIC?  (I didn't think so)<br
                  class="">
                <br class="">
                <br class="">
                5.2.10. Interface Instance or Type<br class="">
                <br class="">
                * These type symbols really deserve an actual registry,
                or at least the start of one. Otherwise, we are likely
                to end up with a mess.<br class="">
              </blockquote>
              <br style="caret-color: rgb(0, 0, 0); font-family:
                Helvetica; font-size: 12px; font-style: normal;
                font-variant-caps: normal; font-weight: normal;
                letter-spacing: normal; text-align: start; text-indent:
                0px; text-transform: none; white-space: normal;
                word-spacing: 0px; -webkit-text-stroke-width: 0px;
                text-decoration: none;" class="">
              <span style="caret-color: rgb(0, 0, 0); font-family:
                Helvetica; font-size: 12px; font-style: normal;
                font-variant-caps: normal; font-weight: normal;
                letter-spacing: normal; text-align: start; text-indent:
                0px; text-transform: none; white-space: normal;
                word-spacing: 0px; -webkit-text-stroke-width: 0px;
                text-decoration: none; float: none; display: inline
                !important;" class="">There is already one, but that one
                was not useful for our matters.<span
                  class="Apple-converted-space"> </span></span><br
                style="caret-color: rgb(0, 0, 0); font-family:
                Helvetica; font-size: 12px; font-style: normal;
                font-variant-caps: normal; font-weight: normal;
                letter-spacing: normal; text-align: start; text-indent:
                0px; text-transform: none; white-space: normal;
                word-spacing: 0px; -webkit-text-stroke-width: 0px;
                text-decoration: none;" class="">
              <blockquote type="cite" style="font-family: Helvetica;
                font-size: 12px; font-style: normal; font-variant-caps:
                normal; font-weight: normal; letter-spacing: normal;
                orphans: auto; text-align: start; text-indent: 0px;
                text-transform: none; white-space: normal; widows: auto;
                word-spacing: 0px; -webkit-text-size-adjust: auto;
                -webkit-text-stroke-width: 0px; text-decoration: none;"
                class=""><br class="">
                5.2.11. Provisioning Domain Instance or Type<br class="">
                <br class="">
                * What about ordering of similar interfaces? I have a
                2-SIM cellphone with wifi.<br class="">
              </blockquote>
              <br style="caret-color: rgb(0, 0, 0); font-family:
                Helvetica; font-size: 12px; font-style: normal;
                font-variant-caps: normal; font-weight: normal;
                letter-spacing: normal; text-align: start; text-indent:
                0px; text-transform: none; white-space: normal;
                word-spacing: 0px; -webkit-text-stroke-width: 0px;
                text-decoration: none;" class="">
              <span style="caret-color: rgb(0, 0, 0); font-family:
                Helvetica; font-size: 12px; font-style: normal;
                font-variant-caps: normal; font-weight: normal;
                letter-spacing: normal; text-align: start; text-indent:
                0px; text-transform: none; white-space: normal;
                word-spacing: 0px; -webkit-text-stroke-width: 0px;
                text-decoration: none; float: none; display: inline
                !important;" class="">Each cellular provider will have a
                unique PVD.<span class="Apple-converted-space"> </span></span><br
                style="caret-color: rgb(0, 0, 0); font-family:
                Helvetica; font-size: 12px; font-style: normal;
                font-variant-caps: normal; font-weight: normal;
                letter-spacing: normal; text-align: start; text-indent:
                0px; text-transform: none; white-space: normal;
                word-spacing: 0px; -webkit-text-stroke-width: 0px;
                text-decoration: none;" class="">
              <blockquote type="cite" style="font-family: Helvetica;
                font-size: 12px; font-style: normal; font-variant-caps:
                normal; font-weight: normal; letter-spacing: normal;
                orphans: auto; text-align: start; text-indent: 0px;
                text-transform: none; white-space: normal; widows: auto;
                word-spacing: 0px; -webkit-text-size-adjust: auto;
                -webkit-text-stroke-width: 0px; text-decoration: none;"
                class=""><br class="">
                5.3.2. Connection Establishment Callbacks<br class="">
                <br class="">
                * What constitutes trust verification prior to the
                handshake?<br class="">
                <br class="">
                7.3.1. Sent<br class="">
                <br class="">
                * It seems like an abstract API would be helpful for the
                reference to the Message to which a Sent event applies:
                this seems like something many, many applications would
                need to do. With callbacks, the application can always
                curry in a reference to the original message (that's
                what my event system from ~2001 did), so maybe that
                should be the recommendation and the message reference
                removed...? I don't have a strong feeling here other
                than that if something is included then its use should
                be more well-defined.<br class="">
                <br class="">
                7.3.3. SendError<br class="">
                <br class="">
                * Is there a reason why a single messageContext object
                is used for both sends and receives? I probably missed
                the original discussion about this, but I'd like to
                understand the reasoning.<br class="">
                <br class="">
                MW: I don't get this, where does it say that it's only a
                single object? Or do you mean that it's the same type?
                Why is that problematic?<br class="">
                <br class="">
                <br class="">
                7.4.7. Reliable Data Transfer (Message)<br class="">
                <br class="">
                * The default isn't "true", it's whatever the underlying
                connection had, right?<br class="">
              </blockquote>
              <br style="caret-color: rgb(0, 0, 0); font-family:
                Helvetica; font-size: 12px; font-style: normal;
                font-variant-caps: normal; font-weight: normal;
                letter-spacing: normal; text-align: start; text-indent:
                0px; text-transform: none; white-space: normal;
                word-spacing: 0px; -webkit-text-stroke-width: 0px;
                text-decoration: none;" class="">
              <span style="caret-color: rgb(0, 0, 0); font-family:
                Helvetica; font-size: 12px; font-style: normal;
                font-variant-caps: normal; font-weight: normal;
                letter-spacing: normal; text-align: start; text-indent:
                0px; text-transform: none; white-space: normal;
                word-spacing: 0px; -webkit-text-stroke-width: 0px;
                text-decoration: none; float: none; display: inline
                !important;" class="">Ack</span><br style="caret-color:
                rgb(0, 0, 0); font-family: Helvetica; font-size: 12px;
                font-style: normal; font-variant-caps: normal;
                font-weight: normal; letter-spacing: normal; text-align:
                start; text-indent: 0px; text-transform: none;
                white-space: normal; word-spacing: 0px;
                -webkit-text-stroke-width: 0px; text-decoration: none;"
                class="">
            </div>
          </blockquote>
          <div><br class="">
          </div>
          <div>I agree too, but doesn’t this warrant some more
            discussion?</div>
          <div>I think our defaults all translate into things that can
            work in some way when TCP is used - with “Reliable Data
            Transfer” being an exception, as it just can’t work in a
            UDP-only system. Are there others?  I think I’ll open an
            issue for this one.</div>
          <div><br class="">
          </div>
        </div>
      </div>
    </blockquote>
    <p>I don't agree at all - To me this was just the default behaviour
      of the API.</p>
    <p>I think the default needs to be "reliable" and an app will have
      to over-ride that to get datagram/unreliable operation. That
      doesn't mean if you have only UDP (for instance) that you can't
      offer TAPS, to me it simply means you always need to say that the
      app wants this service.<br>
    </p>
    <blockquote type="cite"
      cite="mid:BA384A88-089E-470C-A7D3-55CABC6DB94B@ifi.uio.no">
      <div class="">
        <div>
          <div><br class="">
          </div>
          <br class="">
          <blockquote type="cite" class="">
            <div class="">
              <blockquote type="cite" style="font-family: Helvetica;
                font-size: 12px; font-style: normal; font-variant-caps:
                normal; font-weight: normal; letter-spacing: normal;
                orphans: auto; text-align: start; text-indent: 0px;
                text-transform: none; white-space: normal; widows: auto;
                word-spacing: 0px; -webkit-text-size-adjust: auto;
                -webkit-text-stroke-width: 0px; text-decoration: none;"
                class="">8. Receiving Data<br class="">
                <br class="">
                * A connection can be used to receive data if it is not
                configured as unidirectional transmit.<br class="">
                <br class="">
                MW: that's obviously correct - but I can't find a
                statement that would contradict what you say here.<br
                  class="">
                <br class="">
                <br class="">
                8.2. Receive Events<br class="">
                <br class="">
                * "A call to Receive will be paired with a single
                Receive Event" or possibly multiple ReceivedPartial
                Events?<br class="">
                <br class="">
                * Also, can the draft be consistent about Receive vs.
                Received, et al.?<br class="">
                <br class="">
                <br class="">
                11. General comments<br class="">
                <br class="">
                * There's a lot of UNIXisms here that should probably be
                excised in favor of a more abstract presentation. The
                most obvious is the use of -1 to mean something other
                than the integer -1. In Python, for instance, you might
                want to use None for this purpose. I would specify
                non-numeric values symbolically, and maybe indicate in
                the appendix that a UNIX C implementation might want to
                use -1 to represent such values.<br class="">
                <br class="">
                MW: agreed... TODO.<br class="">
                <br class="">
                <br class="">
                11.1.10. Capacity Profile<br class="">
                <br class="">
                * Very little of this section is about capacity. Traffic
                Profile?<br class="">
                <br class="">
                * "High Throughput Data" might be better phrased as
                "Capacity-Seeking".<br class="">
                <br class="">
              </blockquote>
            </div>
          </blockquote>
        </div>
      </div>
    </blockquote>
    I don't much like Traffic Profile - to a traffic profile specifies
    the characteristics of the traffic the sender is transmitting, not
    the treatment that traffic expects from the network service.<br>
    <br>
    I also object to /bandwidth efficiency/ - since sounds like it
    should be measured in b/Hz which isn't at all what we are talking
    about. In fact, I did not see anything in the text about the
    efficiency or the use of bandwith ... as I read, it is all about
    capacity sharing tradeoffs.
    <blockquote type="cite"
      cite="mid:BA384A88-089E-470C-A7D3-55CABC6DB94B@ifi.uio.no">
      <div class="">
        <div>
          <blockquote type="cite" class="">
            <div class="">
              <blockquote type="cite" style="font-family: Helvetica;
                font-size: 12px; font-style: normal; font-variant-caps:
                normal; font-weight: normal; letter-spacing: normal;
                orphans: auto; text-align: start; text-indent: 0px;
                text-transform: none; white-space: normal; widows: auto;
                word-spacing: 0px; -webkit-text-size-adjust: auto;
                -webkit-text-stroke-width: 0px; text-decoration: none;"
                class="">_______________________________________________<br
                  class="">
                Taps mailing list<br class="">
                <a href="mailto:Taps@ietf.org" class=""
                  moz-do-not-send="true">Taps@ietf.org</a><br class="">
                <a href="https://www.ietf.org/mailman/listinfo/taps"
                  class="" moz-do-not-send="true">https://www.ietf.org/mailman/listinfo/taps</a></blockquote>
            </div>
          </blockquote>
          <br class="">
        </div>
        <div><br class="">
        </div>
        <div>Cheers,</div>
        <div>Michael</div>
        <div><br class="">
        </div>
        <br>
      </div>
    </blockquote>
    <p>Best wishes,</p>
    <p>Gorry</p>
    <p><br>
    </p>
    <blockquote type="cite"
      cite="mid:BA384A88-089E-470C-A7D3-55CABC6DB94B@ifi.uio.no">
      <pre class="moz-quote-pre" wrap="">
</pre>
    </blockquote>
  </body>
</html>

--------------891203FC41D5868658EFEC75--


From nobody Thu Mar  5 04:53:41 2020
Return-Path: <internet-drafts@ietf.org>
X-Original-To: taps@ietf.org
Delivered-To: taps@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E251D3A1421; Thu,  5 Mar 2020 04:53:39 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: taps@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.119.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: taps@ietf.org
Message-ID: <158341281982.14659.15371800908798410675@ietfa.amsl.com>
Date: Thu, 05 Mar 2020 04:53:39 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/XDNVf6t5QzC2l86LZNGRmXCf970>
Subject: [Taps] I-D Action: draft-ietf-taps-transport-security-11.txt
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 05 Mar 2020 12:53:40 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Transport Services WG of the IETF.

        Title           : A Survey of the Interaction Between Security Protocols and Transport Services
        Authors         : Theresa Enghardt
                          Tommy Pauly
                          Colin Perkins
                          Kyle Rose
                          Christopher A. Wood
	Filename        : draft-ietf-taps-transport-security-11.txt
	Pages           : 22
	Date            : 2020-03-05

Abstract:
   This document provides a survey of commonly used or notable network
   security protocols, with a focus on how they interact and integrate
   with applications and transport protocols.  Its goal is to supplement
   efforts to define and catalog transport services by describing the
   interfaces required to add security protocols.  This survey is not
   limited to protocols developed within the scope or context of the
   IETF, and those included represent a superset of features a Transport
   Services system may need to support.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-taps-transport-security/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-taps-transport-security-11
https://datatracker.ietf.org/doc/html/draft-ietf-taps-transport-security-11

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-taps-transport-security-11


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.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Fri Mar  6 00:02:26 2020
Return-Path: <tapsbot@magpie.corvid.ch>
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 CC9253A098C for <taps@ietfa.amsl.com>; Fri,  6 Mar 2020 00:02:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham 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 4A6JhDmehnwv for <taps@ietfa.amsl.com>; Fri,  6 Mar 2020 00:02:23 -0800 (PST)
Received: from magpie.corvid.ch (magpie.corvid.ch [46.101.110.207]) (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 D0C463A097C for <taps@ietf.org>; Fri,  6 Mar 2020 00:02:22 -0800 (PST)
Received: from [127.0.0.1] (helo=magpie.corvid.ch) by magpie.corvid.ch with esmtp (Exim 4.92) (envelope-from <tapsbot@magpie.corvid.ch>) id 1jA7tt-0000jG-La for taps@ietf.org; Fri, 06 Mar 2020 08:00:05 +0000
Content-Type: multipart/alternative; boundary="===============4509793800712011128=="
MIME-Version: 1.0
From: TAPS WG status robot <tapsbot@magpie.corvid.ch>
To: taps@ietf.org
Message-Id: <E1jA7tt-0000jG-La@magpie.corvid.ch>
Date: Fri, 06 Mar 2020 08:00:05 +0000
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/1IXZsGYlOMN3YweBRN0LEkg2pPg>
Subject: [Taps] Weekly github digest (TAPS GitHub Activity Digest)
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: Fri, 06 Mar 2020 08:02:25 -0000

--===============4509793800712011128==
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"; format="flowed"




Issues
------
* ietf-tapswg/api-drafts (+3/-1/=F0=9F=92=AC3)
  3 issues created:
  - Bandwidth Efficiency as a term in API (by gorryfair)
    https://github.com/ietf-tapswg/api-drafts/issues/515 [API] =

  - Combine some errors? (by mwelzl)
    https://github.com/ietf-tapswg/api-drafts/issues/510 [API] =

  - ReceiveHandler per Receive? (by mwelzl)
    https://github.com/ietf-tapswg/api-drafts/issues/509 [API] =


  3 issues received 3 new comments:
  - #438 Retransmit notify (1 by mwelzl)
    https://github.com/ietf-tapswg/api-drafts/issues/438 [API] [ready for t=
ext] =

  - #507 More text on clone (1 by mwelzl)
    https://github.com/ietf-tapswg/api-drafts/issues/507 [Implementation] =

  - #453 Early data property on receive (1 by mwelzl)
    https://github.com/ietf-tapswg/api-drafts/issues/453 [API] =


  1 issues closed:
  - Early data property on receive https://github.com/ietf-tapswg/api-draft=
s/issues/453 [API] =




Pull requests
-------------
* ietf-tapswg/api-drafts (+4/-1/=F0=9F=92=AC5)
  4 pull requests submitted:
  - Addressing some of Kyle Rose's comments (by mwelzl)
    https://github.com/ietf-tapswg/api-drafts/pull/514 =

  - API receive semantics and DSCP text fixes; closes minor issues #454 #45=
0 #494 (by mwelzl)
    https://github.com/ietf-tapswg/api-drafts/pull/513 =

  - Update Multipath properties - closes #437 (by philsbln)
    https://github.com/ietf-tapswg/api-drafts/pull/512 [API] =

  - Move algorithm text to Implementation draft, make Interface draft more =
flexible (by theri)
    https://github.com/ietf-tapswg/api-drafts/pull/511 =


  4 pull requests received 5 new comments:
  - #497 Refactor Local Address Preference, fixes #436 (2 by philsbln, ther=
i)
    https://github.com/ietf-tapswg/api-drafts/pull/497 [API] =

  - #512 Update Multipath properties - closes #437 (1 by mirjak)
    https://github.com/ietf-tapswg/api-drafts/pull/512 [API] =

  - #501 First attempt to write some privacy considerations (1 by mirjak)
    https://github.com/ietf-tapswg/api-drafts/pull/501 =

  - #502 Clean up unnecessary normative language in arch (1 by gorryfair)
    https://github.com/ietf-tapswg/api-drafts/pull/502 [Architecture] =


  1 pull requests merged:
  - Mostly Editorial changes on Capacity Profile
    https://github.com/ietf-tapswg/api-drafts/pull/463 [API] =



Repositories tracked by this digest:
-----------------------------------
* https://github.com/ietf-tapswg/api-drafts

--===============4509793800712011128==
Content-Type: text/html; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

<!doctype html>
<html lang=3D"en">
<head>
<meta charset=3D"utf-8">
<title>Weekly github digest (TAPS GitHub Activity Digest)</title>
<style>
body { font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;=
 font-size: 14px; }
h2 { margin-top: 3em; color: #A52A2A; font-style: italic; font-weight: norm=
al; }
h3 { margin-bottom:0; margin-top: 2em; font-size: 1.2em; }
h1+h2 { margin-top: 1em; }
a { color: #bb6219; text-decoration: none; }
li { margin-bottom: .35em; }
.repos { margin-bottom: 0; margin-top:0; line-height: 1.2; }
.new { color: red; }
.label { display: inline;
	padding: .2em .6em .3em;
	font-size: 75%;
	font-weight: 700;
	line-height: 1;
	color: #fff;
	text-align: center;
	white-space: nowrap;
	vertical-align: baseline;
	border-radius: .25em;
}
</style>
</head>

<body>
<h1>Friday March 06, 2020</h1>


<h2>Issues</h2>

<h3>ietf-tapswg/api-drafts (+3/-1/=F0=9F=92=AC3)</h3>
  <p class=3D"new">3 issues created:</p>
  <ul>
  <li>#515 <a href=3D"https://github.com/ietf-tapswg/api-drafts/issues/515"=
>Bandwidth Efficiency as a term in API</a> (by gorryfair) <span class=3D"la=
bel" style=3D"background-color: #fbca04; color: #000000">API</span> </li>
  =

  <li>#510 <a href=3D"https://github.com/ietf-tapswg/api-drafts/issues/510"=
>Combine some errors?</a> (by mwelzl) <span class=3D"label" style=3D"backgr=
ound-color: #fbca04; color: #000000">API</span> </li>
  =

  <li>#509 <a href=3D"https://github.com/ietf-tapswg/api-drafts/issues/509"=
>ReceiveHandler per Receive?</a> (by mwelzl) <span class=3D"label" style=3D=
"background-color: #fbca04; color: #000000">API</span> </li>
  </ul>

  <p>3 issues received 3 new comments:</p>
  <ul>
  <li>#438 <a href=3D"https://github.com/ietf-tapswg/api-drafts/issues/438"=
>Retransmit notify</a> (1 by mwelzl) <span class=3D"label" style=3D"backgro=
und-color: #fbca04; color: #000000">API</span> <span class=3D"label" style=
=3D"background-color: #4ae0d1; color: #000000">ready for text</span> </li>
  =

  <li>#507 <a href=3D"https://github.com/ietf-tapswg/api-drafts/issues/507"=
>More text on clone</a> (1 by mwelzl) <span class=3D"label" style=3D"backgr=
ound-color: #fbca04; color: #000000">Implementation</span> </li>
  =

  <li>#453 <a href=3D"https://github.com/ietf-tapswg/api-drafts/issues/453"=
>Early data property on receive</a> (1 by mwelzl) <span class=3D"label" sty=
le=3D"background-color: #fbca04; color: #000000">API</span> </li>
  </ul>

  <p>1 issues closed:</p>
  <ul>
  <li>#453 <a href=3D"https://github.com/ietf-tapswg/api-drafts/issues/453"=
>Early data property on receive</a> <span class=3D"label" style=3D"backgrou=
nd-color: #fbca04; color: #000000">API</span> </li>
  </ul>



<h2>Pull requests</h2>
<h3>ietf-tapswg/api-drafts (+4/-1/=F0=9F=92=AC5)</h3>
  <p class=3D"new">4 pull requests submitted:</p>
  <ul>
  <li>#514 <a href=3D"https://github.com/ietf-tapswg/api-drafts/pull/514">A=
ddressing some of Kyle Rose&#x27;s comments</a> (by mwelzl) </li>
  =

  <li>#513 <a href=3D"https://github.com/ietf-tapswg/api-drafts/pull/513">A=
PI receive semantics and DSCP text fixes; closes minor issues #454 #450 #49=
4</a> (by mwelzl) </li>
  =

  <li>#512 <a href=3D"https://github.com/ietf-tapswg/api-drafts/pull/512">U=
pdate Multipath properties - closes #437</a> (by philsbln) <span class=3D"l=
abel" style=3D"background-color: #fbca04; color: #">API</span> </li>
  =

  <li>#511 <a href=3D"https://github.com/ietf-tapswg/api-drafts/pull/511">M=
ove algorithm text to Implementation draft, make Interface draft more flexi=
ble</a> (by theri) </li>
  </ul>

  <p>4 pull requests received 5 new comments:</p>
  <ul>
  <li>#497 <a href=3D"https://github.com/ietf-tapswg/api-drafts/pull/497">R=
efactor Local Address Preference, fixes #436</a> (2 by philsbln, theri) <sp=
an class=3D"label" style=3D"background-color: #fbca04; color: #000000">API<=
/span> </li>
  =

  <li>#512 <a href=3D"https://github.com/ietf-tapswg/api-drafts/pull/512">U=
pdate Multipath properties - closes #437</a> (1 by mirjak) <span class=3D"l=
abel" style=3D"background-color: #fbca04; color: #000000">API</span> </li>
  =

  <li>#501 <a href=3D"https://github.com/ietf-tapswg/api-drafts/pull/501">F=
irst attempt to write some privacy considerations</a> (1 by mirjak) </li>
  =

  <li>#502 <a href=3D"https://github.com/ietf-tapswg/api-drafts/pull/502">C=
lean up unnecessary normative language in arch</a> (1 by gorryfair) <span c=
lass=3D"label" style=3D"background-color: #fbca04; color: #000000">Architec=
ture</span> </li>
  </ul>

  <p>1 pull requests merged:</p>
  <ul>
  <li>#463 <a href=3D"https://github.com/ietf-tapswg/api-drafts/pull/463">M=
ostly Editorial changes on Capacity Profile</a> <span class=3D"label" style=
=3D"background-color: #fbca04; color: #">API</span> </li>
  </ul>


<h2>Repositories tracked by this digest:</h2>
<ul class=3D"repos">
  <li><a href=3D"https://github.com/ietf-tapswg/api-drafts">https://github.=
com/ietf-tapswg/api-drafts</a></li>
  </ul>
</body>
</html>

--===============4509793800712011128==--


From nobody Fri Mar  6 03:14:57 2020
Return-Path: <zaheduzzaman.sarker@ericsson.com>
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 4FB483A0CE3 for <taps@ietfa.amsl.com>; Fri,  6 Mar 2020 03:14:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, WEIRD_PORT=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.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 riCqeXtq-99Z for <taps@ietfa.amsl.com>; Fri,  6 Mar 2020 03:14:53 -0800 (PST)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-eopbgr150087.outbound.protection.outlook.com [40.107.15.87]) (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 CC6AE3A0CE0 for <taps@ietf.org>; Fri,  6 Mar 2020 03:14:52 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Duc0GePSyLxZ+eG3j1/dHcW/EX4sS/dcDAqroCYuARMNBma+XvOk6+BwY3X3Jxc0XSUXOP9oJ5jYzmOUafKoGe7lPhq1tjAvsxL8EU/2P7H+ynl9fcbcYi5YasMQmraoCEbegFst68dgQEBZ+RQxFHAURhld5k9ISc/Vuyl8ccAdG3BGz+N/aB7Ys04qhahuPiKBKBFvZCKMieJ8r2fsMtdHc8vmAZQj6r/PZfxGNrvSsTPTcmE+RJclQJ/DtOKGA2mJ0VrIubxC5FM64y+smy6G4J1r9ty0OVRWJxIgRvRFkcfL0bHdIVbCO5CC8/qHK+JK8IcB8Xj/4y0O9cwKnA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=NAN82rJL952S/XlgqSHAg4xoblz6OVncvCz7XnskuS8=; b=OLgseylGXvwIXdA3cDYfiFpSkF1QDnPjGxJv0Fv8qUWjebM875/A8Y3z4nqhgfNLfwEUnXi3auauN7B7ABxqBm7Z/dFtB/ANogFQAaYJ6Cit6qZxN8o3sVT68+PaDA8yptD9gaQWMAXMbytU2fC7p2xHlKyIde6S9BMJkszx/7VOFTcBiYA2+w31Oebf3UK0PlfEe+6B3Pfo+6tjNvTP8G+6fUhR1hdpSEK1uueFo91HMyAItmvTRPcuANcgaucD8DjNcou0xZ4luS/eor9923sBSRVWVmZ6RjZ90qRGIY+sODGivJigIEtvuH4j6fYr4igbwrSP0+ELCj1alLnqjA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=NAN82rJL952S/XlgqSHAg4xoblz6OVncvCz7XnskuS8=; b=bQeQ6bgOhci/q6JHAGyWxyM18PQ5hNMd7TIC4j56ZYTMn+Wcu4sxIVC8vIzf6DAZvc+H/LYImpAI9W6BQ8gBGLXgYcXVFnLNZfs2NRyEFjWsQlfPwqnRAZhBKHmTfa3e0+JObVBS7r3CQ849XijJ34u9NgpJp2G/ozaKVhW49uw=
Received: from HE1PR0701MB2170.eurprd07.prod.outlook.com (10.168.36.19) by HE1PR0701MB2540.eurprd07.prod.outlook.com (10.168.130.146) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2814.9; Fri, 6 Mar 2020 11:14:50 +0000
Received: from HE1PR0701MB2170.eurprd07.prod.outlook.com ([fe80::f9fc:6028:2c72:c29a]) by HE1PR0701MB2170.eurprd07.prod.outlook.com ([fe80::f9fc:6028:2c72:c29a%9]) with mapi id 15.20.2814.005; Fri, 6 Mar 2020 11:14:50 +0000
From: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
To: "taps@ietf.org" <taps@ietf.org>
Thread-Topic: TAPS 21st feb 2020 interim meeting notes
Thread-Index: AQHV86hz9wOWAAMyyEOS8LNhO6zmNw==
Date: Fri, 6 Mar 2020 11:14:50 +0000
Message-ID: <D47B352C-A8E5-4F9D-891C-2CBA839B361B@ericsson.com>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/10.22.0.200209
authentication-results: spf=none (sender IP is ) smtp.mailfrom=zaheduzzaman.sarker@ericsson.com; 
x-originating-ip: [192.176.1.84]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: bca3f7d5-3181-465f-547d-08d7c1bf9666
x-ms-traffictypediagnostic: HE1PR0701MB2540:
x-microsoft-antispam-prvs: <HE1PR0701MB254090A0EC68262632D81C179FE30@HE1PR0701MB2540.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:7219;
x-forefront-prvs: 0334223192
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(376002)(346002)(396003)(366004)(39860400002)(279900001)(189003)(199004)(2906002)(316002)(86362001)(36756003)(478600001)(966005)(5660300002)(66556008)(66946007)(64756008)(66446008)(66476007)(91956017)(26005)(76116006)(71200400001)(4744005)(6486002)(186003)(44832011)(6512007)(33656002)(2616005)(6916009)(8936002)(81166006)(81156014)(8676002)(6506007); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR0701MB2540; H:HE1PR0701MB2170.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 6CPvMoQic5ujRoggIZERZ+Xm1H+CRHdmqIOsDJBfMdv1Wgq6jrXPq4U3E0okN3MLwGK9V2ii7xSW2kAvvXXzb6+WClKkQQf3whhkcN0ArWSpZVcC/CC0yNGXiXh0mPXgkeMJc7i+eofPuxOaBoC6wTloXPf22XF06fB7ONkMxZC+LuIy8mHEdwARgzVmgSythhGmuRnVR1yLHhBkkSReUbEAYY8q18oti3GnxWo9MbS53zlMTlzX7hS0AGMI3ENwArTF1EOD4gzkNY7nDGeDmEjC1PseQHFV7GQXWwrKiI90Z9WQO++T/DyNHhG+ttOzS8pF3vGE+CU8KCsJ5ovElS/EhWMeAxpjNIsWU8gDJqmm8CaKW4Dv3MUedfyXEOPFHOQZotH4XdruLpMY1N9c+Hde4OsyUW9r22VMjx6nj8xnpL/bp8NZgqn38g7VwM0qEjGe8K62YbOIX73+PPURpVItagZi1UKm7by0ccTCR7Fcm5eB9ynyp+psCruQmcPRjZJBIKKCQEHgBGJNWK17rQ==
x-ms-exchange-antispam-messagedata: zk9rOxkfmS/DjF1TT/3WgPB/w+VmfSnZpho0y1KF8aa8mfZadQGsHnEZWwJmflXxro1P579TXTI3cpZ9JYdmCgIyFB2NkfvAu9jG4m/WnsLOF/9m3EDdPgPIn50h5CQ7R/jRff+eZKx+fJTblMbrcQ==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_D47B352CA8E54F9D891C2CBA839B361Bericssoncom_"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-Network-Message-Id: bca3f7d5-3181-465f-547d-08d7c1bf9666
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Mar 2020 11:14:50.1607 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 3/uL3FPfLCXjYZjKSYLMY0LtuHENZ/Gji0O2ltLAELlLrnzN45P4PuTx8Ijb4RPFqUdR2QmwM6y+30meimPD/xRMZ7OVwlMIOcqJiUZf7AFMgblJr3m9bZT0+yS3aInW
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0701MB2540
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/Tb2h4QEavepH00eOnoh7ETH6Krw>
Subject: [Taps] TAPS 21st feb 2020 interim meeting notes
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: Fri, 06 Mar 2020 11:14:55 -0000

--_000_D47B352CA8E54F9D891C2CBA839B361Bericssoncom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGksDQoNCkhlcmUgaXMgdGhlIG1lZXRpbmcgbm90ZXMgZnJvbSB0aGUgaW50ZXJpbSBodHRwOi8v
ZXRoZXJwYWQudG9vbHMuaWV0Zi5vcmc6OTAwMC9wL25vdGVzLWlldGYtaW50ZXJpbS0yMDIwLWZl
Yg0KDQpUaGFua3MgVGhlcmVzYSBFbmdoYXJkdCBmb3IgeW91ciBleGNlbGxlbnQgZWZmb3J0IHRv
IHRha2UgdGhlIG5vdGVzLg0KDQpCUg0KDQpaYWhlZA0KDQpFcmljc3NvbiBSZXNlYXJjaA0KDQpO
ZXR3b3JrIEFyY2hpdGVjdHVyZSBhbmQgUHJvdG9jb2xzDQpOZXR3b3JrIE9yY2hlc3RyYXRpb24g
JiBBdXRvbWF0aW9uDQp6YWhlZHV6emFtYW4uc2Fya2VyQGVyaWNzc29uLmNvbQ0KDQpFcmljc3Nv
bg0KVG9yc2hhbW5zZ2F0YW4gMjMNCjE2NCA4MywgU3RvY2tob2xtDQpTd2VkZW4NCg0K

--_000_D47B352CA8E54F9D891C2CBA839B361Bericssoncom_
Content-Type: text/html; charset="utf-8"
Content-ID: <223D4A61A3A81740BB0ABC3456B2ABBA@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4
bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo
dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l
dGEgbmFtZT0iR2VuZXJhdG9yIiBjb250ZW50PSJNaWNyb3NvZnQgV29yZCAxNSAoZmlsdGVyZWQg
bWVkaXVtKSI+DQo8c3R5bGU+PCEtLQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFj
ZQ0KCXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2
IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToy
IDE1IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3Jt
YWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1i
b3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJp
IixzYW5zLXNlcmlmOw0KCW1zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTO30NCmE6bGluaywgc3Bh
bi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOiMwNTYzQzE7
DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpzcGFuLkVtYWlsU3R5bGUxNw0KCXttc28t
c3R5bGUtdHlwZTpwZXJzb25hbC1jb21wb3NlOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5z
LXNlcmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxl
LXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJ
bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVM7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6
NjEyLjBwdCA3OTIuMHB0Ow0KCW1hcmdpbjo3Mi4wcHQgNzIuMHB0IDcyLjBwdCA3Mi4wcHQ7fQ0K
ZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPg0KPC9o
ZWFkPg0KPGJvZHkgbGFuZz0iZW4tU0UiIGxpbms9IiMwNTYzQzEiIHZsaW5rPSIjOTU0RjcyIj4N
CjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBs
YW5nPSJTViIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPkhpLDxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IlNWIiBzdHlsZT0iZm9udC1zaXpl
OjExLjBwdCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0Ij5IZXJlIGlzIHRo
ZSBtZWV0aW5nIG5vdGVzIGZyb20gdGhlIGludGVyaW0NCjxhIGhyZWY9Imh0dHA6Ly9ldGhlcnBh
ZC50b29scy5pZXRmLm9yZzo5MDAwL3Avbm90ZXMtaWV0Zi1pbnRlcmltLTIwMjAtZmViIj5odHRw
Oi8vZXRoZXJwYWQudG9vbHMuaWV0Zi5vcmc6OTAwMC9wL25vdGVzLWlldGYtaW50ZXJpbS0yMDIw
LWZlYjwvYT4NCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+PG86cD4mbmJzcDs8L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0Ij5UaGFua3MgVGhlcmVzYSBFbmdoYXJkdCBmb3IgeW91ciBl
eGNlbGxlbnQgZWZmb3J0IHRvIHRha2UgdGhlIG5vdGVzLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXpl
OjExLjBwdCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0Ij5CUjxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTEuMHB0Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8dGFibGUgY2xhc3M9Ik1z
b05vcm1hbFRhYmxlIiBib3JkZXI9IjAiIGNlbGxwYWRkaW5nPSIwIj4NCjx0Ym9keT4NCjx0cj4N
Cjx0ZCBzdHlsZT0icGFkZGluZzouNzVwdCAuNzVwdCAuNzVwdCAuNzVwdCI+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDttc28tZmFyZWFzdC1s
YW5ndWFnZTpFTi1HQiI+WmFoZWQmbmJzcDsgJm5ic3A7PG86cD48L286cD48L3NwYW4+PC9iPjwv
cD4NCjwvdGQ+DQo8L3RyPg0KPHRyPg0KPHRkIHN0eWxlPSJwYWRkaW5nOi43NXB0IC43NXB0IC43
NXB0IC43NXB0Ij48L3RkPg0KPC90cj4NCjx0cj4NCjx0ZCBzdHlsZT0icGFkZGluZzouNzVwdCAu
NzVwdCAuNzVwdCAuNzVwdCI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjExLjBwdDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1HQiI+Jm5ic3A7PG86cD48L286
cD48L3NwYW4+PC9wPg0KPC90ZD4NCjwvdHI+DQo8dHI+DQo8dGQgc3R5bGU9InBhZGRpbmc6Ljc1
cHQgLjc1cHQgLjc1cHQgLjc1cHQiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gbGFu
Zz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O21zby1mYXJlYXN0LWxhbmd1YWdlOkVO
LUdCIj5Fcmljc3NvbiBSZXNlYXJjaDxvOnA+PC9vOnA+PC9zcGFuPjwvYj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48Yj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4w
cHQ7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tR0IiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
Yj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQ7Y29sb3I6YmxhY2s7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tR0IiPk5l
dHdvcmsgQXJjaGl0ZWN0dXJlIGFuZCBQcm90b2NvbHMNCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXpl
OjExLjBwdDtjb2xvcjpibGFjazttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1HQiI+TmV0d29yayBP
cmNoZXN0cmF0aW9uICZhbXA7IEF1dG9tYXRpb248L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0O21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLUdCIj48bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8L3RkPg0KPC90cj4NCjx0cj4NCjx0ZCBzdHlsZT0icGFkZGluZzou
NzVwdCAuNzVwdCAuNzVwdCAuNzVwdCI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjExLjBwdDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1HQiI+emFoZWR1enph
bWFuLnNhcmtlckBlcmljc3Nvbi5jb208bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L3RkPg0KPC90
cj4NCjx0cj4NCjx0ZCBzdHlsZT0icGFkZGluZzouNzVwdCAuNzVwdCAuNzVwdCAuNzVwdCI+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDttc28tZmFy
ZWFzdC1sYW5ndWFnZTpFTi1HQiI+Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPC90ZD4N
CjwvdHI+DQo8dHI+DQo8dGQgc3R5bGU9InBhZGRpbmc6Ljc1cHQgLjc1cHQgLjc1cHQgLjc1cHQi
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7bXNv
LWZhcmVhc3QtbGFuZ3VhZ2U6RU4tR0IiPkVyaWNzc29uPG86cD48L286cD48L3NwYW4+PC9wPg0K
PC90ZD4NCjwvdHI+DQo8dHI+DQo8dGQgc3R5bGU9InBhZGRpbmc6Ljc1cHQgLjc1cHQgLjc1cHQg
Ljc1cHQiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4w
cHQ7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tR0IiPlRvcnNoYW1uc2dhdGFuIDIzPG86cD48L286
cD48L3NwYW4+PC9wPg0KPC90ZD4NCjwvdHI+DQo8dHI+DQo8dGQgc3R5bGU9InBhZGRpbmc6Ljc1
cHQgLjc1cHQgLjc1cHQgLjc1cHQiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQ7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tR0IiPjE2NCA4MywgU3Rv
Y2tob2xtPG86cD48L286cD48L3NwYW4+PC9wPg0KPC90ZD4NCjwvdHI+DQo8dHI+DQo8dGQgc3R5
bGU9InBhZGRpbmc6Ljc1cHQgLjc1cHQgLjc1cHQgLjc1cHQiPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4t
R0IiPlN3ZWRlbjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvdGQ+DQo8L3RyPg0KPHRyPg0KPHRk
IHN0eWxlPSJwYWRkaW5nOi43NXB0IC43NXB0IC43NXB0IC43NXB0Ij48L3RkPg0KPC90cj4NCjwv
dGJvZHk+DQo8L3RhYmxlPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_D47B352CA8E54F9D891C2CBA839B361Bericssoncom_--


From nobody Sun Mar  8 01:32:09 2020
Return-Path: <gorry@erg.abdn.ac.uk>
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 CEADE3A0763 for <taps@ietfa.amsl.com>; Sun,  8 Mar 2020 01:32:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham 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 lZV_zKpuRVX2 for <taps@ietfa.amsl.com>; Sun,  8 Mar 2020 01:32:06 -0800 (PST)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [137.50.19.135]) by ietfa.amsl.com (Postfix) with ESMTP id 11F153A0766 for <taps@ietf.org>; Sun,  8 Mar 2020 01:32:06 -0800 (PST)
Received: from GF-MacBook-Pro.local (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id A9D671B001B7 for <taps@ietf.org>; Sun,  8 Mar 2020 09:32:03 +0000 (GMT)
To: taps WG <taps@ietf.org>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Message-ID: <b08b337a-0f0e-c150-5e3b-9c49893a5d6b@erg.abdn.ac.uk>
Date: Sun, 8 Mar 2020 09:32:03 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:68.0) Gecko/20100101 Thunderbird/68.5.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/sRG4mpg0nUWGXp-5Ar7VMf9gQ74>
Subject: [Taps] Review of Arch wrt to normative requirements on the architecture
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: Sun, 08 Mar 2020 09:32:08 -0000

I have now reveiwed the Arch document for normative language, as promised.


After the review, I would still be in favour of using RFC2119 language 
to describe what is required architecturally to be a TAPS system. In my 
review, I agree the number of requirements is now reduced.

I really do wonder if we could (please) group all these requirements on 
architecture into a single subsection, so they are easy to read - and we 
can they say that these are the architectural requirements, explcitly 
refererence those in section XX relating to racing. I suggest we insert 
this requirements text either as short text blocks in their own section, 
or simply a set of bullets in section 1.3 (although I am open to other 
places where we can call-out the architectural requirements).

Perhaps we should also check we still have captured something along the 
lines of:

"The System should permit evolution of the system without affecting 
programs using it. In normal use, TAPS systems are RECOMMENDED to result 
in consistent selection for the same network conditions when they have 
the same set of preferences, but applications using the TAPS API are 
REQUIRED to be robust to the automated selection, including the 
possibility to express requirements that constrain the choices that can 
be made by the system." And possibly add "Applications using TAPS can 
explicitly require or prevent the use of specific transport features 
(and transport protocols) using the "REQUIRED" and "PROHIBIT"..." or 
something like that.

If this seems appropriate to add a section on overall requirements, I 
would then suggest to use lower case within the document and simply 
refer to this subsection, where necessary to get the RFC2119 sentences.

I made specific comments in pull request, #502:

https://github.com/ietf-tapswg/api-drafts/pull/502


--- Comments or imrpovements welcome!

Gorry


From nobody Mon Mar  9 10:36:04 2020
Return-Path: <internet-drafts@ietf.org>
X-Original-To: taps@ietf.org
Delivered-To: taps@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E03333A1403; Mon,  9 Mar 2020 10:35:55 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: taps@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.120.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: taps@ietf.org
Message-ID: <158377535583.5627.3611328778462952215@ietfa.amsl.com>
Date: Mon, 09 Mar 2020 10:35:55 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/j5Fmryaxfs8kol8UqaZU_118QdU>
Subject: [Taps] I-D Action: draft-ietf-taps-arch-07.txt
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 09 Mar 2020 17:35:58 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Transport Services WG of the IETF.

        Title           : An Architecture for Transport Services
        Authors         : Tommy Pauly
                          Brian Trammell
                          Anna Brunstrom
                          Godred Fairhurst
                          Colin Perkins
                          Philipp S. Tiesel
                          Chris Wood
	Filename        : draft-ietf-taps-arch-07.txt
	Pages           : 28
	Date            : 2020-03-09

Abstract:
   This document describes an architecture for exposing transport
   protocol features to applications for network communication, the
   Transport Services architecture.  The Transport Services Application
   Programming Interface (API) is based on an asynchronous, event-driven
   interaction pattern.  It uses messages for representing data transfer
   to applications, and it assumes an implementation that can use
   multiple IP addresses, multiple protocols, and multiple paths, and
   provide multiple application streams.  This document further defines
   common terminology and concepts to be used in definitions of
   Transport Services APIs and implementations.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-taps-arch/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-taps-arch-07
https://datatracker.ietf.org/doc/html/draft-ietf-taps-arch-07

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-taps-arch-07


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.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Mon Mar  9 10:58:53 2020
Return-Path: <internet-drafts@ietf.org>
X-Original-To: taps@ietf.org
Delivered-To: taps@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id F01A13A1232; Mon,  9 Mar 2020 10:58:46 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: taps@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.120.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: taps@ietf.org
Message-ID: <158377672691.5499.8734242352866079792@ietfa.amsl.com>
Date: Mon, 09 Mar 2020 10:58:46 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/oPjq_pl8HfPE5QHt_2pxeMP0Nj4>
Subject: [Taps] I-D Action: draft-ietf-taps-impl-06.txt
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 09 Mar 2020 17:58:47 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Transport Services WG of the IETF.

        Title           : Implementing Interfaces to Transport Services
        Authors         : Anna Brunstrom
                          Tommy Pauly
                          Theresa Enghardt
                          Karl-Johan Grinnemo
                          Tom Jones
                          Philipp S. Tiesel
                          Colin Perkins
                          Michael Welzl
	Filename        : draft-ietf-taps-impl-06.txt
	Pages           : 51
	Date            : 2020-03-09

Abstract:
   The Transport Services architecture [I-D.ietf-taps-arch] defines a
   system that allows applications to use transport networking protocols
   flexibly.  This document serves as a guide to implementation on how
   to build such a system.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-taps-impl/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-taps-impl-06
https://datatracker.ietf.org/doc/html/draft-ietf-taps-impl-06

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-taps-impl-06


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.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Mon Mar  9 11:31:36 2020
Return-Path: <internet-drafts@ietf.org>
X-Original-To: taps@ietf.org
Delivered-To: taps@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D39DF3A1500; Mon,  9 Mar 2020 11:31:34 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: taps@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.120.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: taps@ietf.org
Message-ID: <158377869478.5550.6734112179606790804@ietfa.amsl.com>
Date: Mon, 09 Mar 2020 11:31:34 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/J7gzIRgI33B2SvaVdUXXhqEwpLE>
Subject: [Taps] I-D Action: draft-ietf-taps-interface-06.txt
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 09 Mar 2020 18:31:35 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Transport Services WG of the IETF.

        Title           : An Abstract Application Layer Interface to Transport Services
        Authors         : Brian Trammell
                          Michael Welzl
                          Theresa Enghardt
                          Godred Fairhurst
                          Mirja Kuehlewind
                          Colin Perkins
                          Philipp S. Tiesel
                          Chris Wood
                          Tommy Pauly
	Filename        : draft-ietf-taps-interface-06.txt
	Pages           : 69
	Date            : 2020-03-09

Abstract:
   This document describes an abstract programming interface to the
   transport layer, following the Transport Services Architecture.  It
   supports the asynchronous, atomic transmission of messages over
   transport protocols and network paths dynamically selected at
   runtime.  It is intended to replace the traditional BSD sockets API
   as the lowest common denominator interface to the transport layer, in
   an environment where endpoints have multiple interfaces and potential
   transport protocols to select from.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-taps-interface/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-taps-interface-06
https://datatracker.ietf.org/doc/html/draft-ietf-taps-interface-06

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-taps-interface-06


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.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Tue Mar 10 07:07:08 2020
Return-Path: <krose@krose.org>
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 546933A1367 for <taps@ietfa.amsl.com>; Tue, 10 Mar 2020 07:07:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.087
X-Spam-Level: 
X-Spam-Status: No, score=-2.087 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=krose.org
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 9x_R6pkopNCl for <taps@ietfa.amsl.com>; Tue, 10 Mar 2020 07:06:58 -0700 (PDT)
Received: from mail-yw1-xc2f.google.com (mail-yw1-xc2f.google.com [IPv6:2607:f8b0:4864:20::c2f]) (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 4CB633A1365 for <taps@ietf.org>; Tue, 10 Mar 2020 07:06:57 -0700 (PDT)
Received: by mail-yw1-xc2f.google.com with SMTP id x5so12829983ywb.13 for <taps@ietf.org>; Tue, 10 Mar 2020 07:06:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=krose.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ieHGJqMCcluL+2FN6aMHYhWB5e1Nf+4mcbapl4I+64c=; b=DnJ0roDHpaQoNKLecQKdnO7YaAZQY8Pi+wNqI/Y4jQcO1vuonXhLzr8o+AkfOA5TV1 enavUWF9UlJYtYPFjHy29Dvkk3igGtlogLUDVQr+7F6RNrmM3NzWW0GLVVosF/1bw9Er 6SlbLnGLQc1H9Qn2S6SM2Q1saklDqJrhL2AMI=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ieHGJqMCcluL+2FN6aMHYhWB5e1Nf+4mcbapl4I+64c=; b=PqzJPyS5qEIi8spqkXOl7xU2xUDis9KhepjxSdSUhtqxSq4OMDHeFFnjFcnJ/kPPlo e/vzdtK5yogaq2lSsJG0nBkjOCGasl4VZRbDPQRqf3nyQHu3kqHvNbiI1cUPtLV2Zsw5 RW9h5Q7mMLBQYUfr8hSzuR47H3JpaTHRLIlaoJZgCJG8CGQ0RfBRq9dt3y706zcm5/C+ MKV/Xd5rC1AxsOaCC2UdYSLsxJHqa9XLY1dXDX9t7lLn//bDqwuUhQkvz3VRZR3BRoct bQpzJt7rWUeUZec7862SkhXCVmmoWk6233hm3uyL6OdDi339bPKzfYIw8tAfvuARd5/q KKfA==
X-Gm-Message-State: ANhLgQ2Pvo5KXJgxXASGpPIz/tOEMXA3350hNLGlzvOoinTLNKlMxSam 2rMXLqxjfCdSBKcf4SGqKOYoJg9lYWsNbGQ0sJAPapPMpn4=
X-Google-Smtp-Source: ADFU+vsuTZwsdHUm0B/noplneqy7xDOnZfqc/CSNTF8Qgz+6Ja/53cSDZVMIrizu/5eLCCpOhhJ0owPp/NP6jdzvgK0=
X-Received: by 2002:a0d:d106:: with SMTP id t6mr22004454ywd.211.1583849216702;  Tue, 10 Mar 2020 07:06:56 -0700 (PDT)
MIME-Version: 1.0
References: <CAJU8_nVyAvVzD6ZitxwzoVCYBYmT1y3oP7U8FhgyWfx8p6RR5w@mail.gmail.com> <E9545535-178C-4B9F-91C2-0EB3356DB5B0@ifi.uio.no>
In-Reply-To: <E9545535-178C-4B9F-91C2-0EB3356DB5B0@ifi.uio.no>
From: Kyle Rose <krose@krose.org>
Date: Tue, 10 Mar 2020 10:06:45 -0400
Message-ID: <CAJU8_nU4nx5_r8-kUJusAWR29S=+1x7NTf6NLQ-7XceNfpyOpQ@mail.gmail.com>
To: Michael Welzl <michawe@ifi.uio.no>
Cc: "taps@ietf.org" <taps@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f0983705a080a105"
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/FObeuIKJgD_V3QLjEitvtlt7Qrk>
Subject: Re: [Taps] draft-ietf-taps-interface-05 review
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, 10 Mar 2020 14:07:06 -0000

--000000000000f0983705a080a105
Content-Type: text/plain; charset="UTF-8"

On Wed, Mar 4, 2020 at 9:41 AM Michael Welzl <michawe@ifi.uio.no> wrote:

> 2. Terminology and Notation
>
>  * The notation "Sender -> Event" says nothing about who receives the
> event. Is it just assumed to be the application in the context of the
> particular event (e.g., a thread processing a particular connection)?
>
> MW: We have the following statement in this section: "Events could be
> implemented via event queues, handler functions or classes, communicating
> sequential processes, or other asynchronous calling conventions."
> I wonder why this isn't enough information? E.g., if handlers are used,
> then the recipient of the event is a pre-registered handler -  and handlers
> must therefore be registered before events can occur; this function isn't
> visible in the API because this is platform- and language-specific.
>

After some thought, I think I'm okay with this now. It feels like one of
those things that would make perfect sense if I were actually implementing
a TAPS interface.


> 4.2.1. Transport Property Names
>
>  * The use of dashes in property names means they will necessarily look
> different in almost every widely-used language, in which dash is an
> operator.
>

Following on to the discussion later in the thread, CamelCase would
probably be an improvement from this perspective. Underscores would also be
fine.



>   * If we're not currently asking IANA to create a registry of property
> names or namespaces, should we provide a recommendation that such symbols
> not listed explcitly in this document be prefixed with some experimental
> identifier?
>

Can't remember where I saw objection that this creates the possibility of a
bunch of long-lived X-* properties. To that I respond: which is worse? A
complete free-for-all, or a recommendation to have the free-for-all
confined to an X- namespace? Do properties starting with X- just offend
engineering sensibilities?

One "right" alternative is a documentation-required registry, but does that
raise the bar too high? How about a TAPS wiki as a compromise? The
important outcome is that properties be well-defined and not conflict with
each other. Since these properties have entirely local effects (e.g., they
don't get encoded as options and transmitted to the peer), we probably
don't need the level of precision motivating option registries, for
instance. Is there precedent at the IETF for a registry mechanism less
formal that what IANA provides?

5.2. Specifying Transport Properties
>
>  * There are a lot of choices being made about how users will want to
> prioritize transport protocol selection. How confident are we that, for
> instance, path selection should take priority over protocol selection? I
> think that's right, but I wonder if it might not make more sense to have
> two interfaces: one that provides a purely numeric priority ordering of
> preferences, and one (based on the existing 5-level preferences) that maps
> into it.
>

I'm okay with whoever said that this is unworkable. I'm sure I missed the
original discussion.


>  * Using the same enum (Require(d[sic])/Avoid/Ignore) for the queried
> output of selected properties seems like a shortcut that will lead to some
> confusion.
>
> MW: I agree;  partially addressed: s/Required/Require wherever it's a
> Preference level.
>

FWIW, my objection to the other issue (using a normative term as an
indication of what was chosen) isn't that it's underspecified, only that
it's confusing. I put it roughly in the same category as specifying -1 as
an error indicator in an abstract API. Is the idea that the output
parameters could be fed into the protocol selection logic for a subsequent
connection to select the same protocol? Is that useful?


> 5.2.5. Use 0-RTT Session Establishment with an Idempotent Message
>
>  * I'll repeat the same statement I made at the mic a few years ago:
> idempotency != replay-safe. DELETE is idempotent, but not safe for replay
> because someone might have done a PUT or POST in the meantime.
>
> MW: I remember you saying this, sorry that we haven't addressed it yet! I
> didn't understand - is your concern about replaying that a Message may
> arrive later, i.e. as Message X, Messages Y and Z in between, then Message
> X again?  => if so, are you saying that this could happen with TFO or
> QUIC?  (I didn't think so)
>

What I mean is maybe best illustrated by 0RTT in TLS or QUIC. If a user
sends a 0RTT DELETE /object, followed by a PUT /object, then within the
replay window and without any replay prevention at the application layer,
an attacker could replay the 0RTT DELETE /object and cause the object to be
deleted again. DELETE is idempotent but it's not safe to replay.

7.3.3. SendError
>
>  * Is there a reason why a single messageContext object is used for both
> sends and receives? I probably missed the original discussion about this,
> but I'd like to understand the reasoning.
>
> MW: I don't get this, where does it say that it's only a single object? Or
> do you mean that it's the same type? Why is that problematic?
>

Same type. (Maybe I should have said "class" instead of "object".) For
example, the "lifetime" property makes sense as metadata for sends, but is
completely irrelevant to the receiver. The same is true of several other
message properties. It might make sense for an implementation to use a
single type to represent metadata both for sends and receives, but is that
also true for an abstract API?


> 8. Receiving Data
>
>  * A connection can be used to receive data if it is not configured as
> unidirectional transmit.
>
> MW: that's obviously correct - but I can't find a statement that would
> contradict what you say here.
>

"Once a Connection is established, it can be used for receiving data." Not
true if it's a unidirectional connection.

I'll take a look at the subsequent replies and respond at the end of the
thread to anything that I didn't cover here.

--000000000000f0983705a080a105
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail=
_attr">On Wed, Mar 4, 2020 at 9:41 AM Michael Welzl &lt;<a href=3D"mailto:m=
ichawe@ifi.uio.no">michawe@ifi.uio.no</a>&gt; wrote:<br></div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px soli=
d rgb(204,204,204);padding-left:1ex">
2. Terminology and Notation<br>
<br>
=C2=A0* The notation &quot;Sender -&gt; Event&quot; says nothing about who =
receives the event. Is it just assumed to be the application in the context=
 of the particular event (e.g., a thread processing a particular connection=
)?<br>
<br>
MW: We have the following statement in this section: &quot;Events could be =
implemented via event queues, handler functions or classes, communicating s=
equential processes, or other asynchronous calling conventions.&quot;<br>
I wonder why this isn&#39;t enough information? E.g., if handlers are used,=
 then the recipient of the event is a pre-registered handler -=C2=A0 and ha=
ndlers must therefore be registered before events can occur; this function =
isn&#39;t visible in the API because this is platform- and language-specifi=
c.<br></blockquote><div><br></div><div><div style=3D"font-size:small" class=
=3D"gmail_default">After some thought, I think I&#39;m okay with this now. =
It feels like one of those things that would make perfect sense if I were a=
ctually implementing a TAPS interface.<br></div></div><div>=C2=A0</div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
:1px solid rgb(204,204,204);padding-left:1ex">


4.2.1. Transport Property Names<br>
<br>
=C2=A0* The use of dashes in property names means they will necessarily loo=
k different in almost every widely-used language, in which dash is an opera=
tor.<br></blockquote><div><br></div><div><div style=3D"font-size:small" cla=
ss=3D"gmail_default">Following on to the discussion later in the thread, Ca=
melCase would probably be an improvement from this perspective. Underscores=
 would also be fine.</div><br></div><div>=C2=A0<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex"><span class=3D"gmail_default" style=3D"fon=
t-size:small"></span>=C2=A0
* If we&#39;re not currently asking IANA to create a registry of property n=
ames or namespaces, should we provide a recommendation that such symbols no=
t listed explcitly in this document be prefixed with some experimental iden=
tifier?<br></blockquote><div><br></div><div><div style=3D"font-size:small" =
class=3D"gmail_default">Can&#39;t remember where I saw objection that this =
creates the possibility of a bunch of long-lived X-* properties. To that I =
respond: which is worse? A complete free-for-all, or a recommendation to ha=
ve the free-for-all confined to an X- namespace? Do properties starting wit=
h X- just offend engineering sensibilities?</div><div style=3D"font-size:sm=
all" class=3D"gmail_default"><br></div><div style=3D"font-size:small" class=
=3D"gmail_default">One &quot;right&quot; alternative is a documentation-req=
uired registry, but does that raise the bar too high? How about a TAPS wiki=
 as a compromise? The important outcome is that properties be well-defined =
and not conflict with each other. Since these properties have entirely loca=
l effects (e.g., they don&#39;t get encoded as options and transmitted to t=
he peer), we probably don&#39;t need the level of precision motivating opti=
on registries, for instance. Is there precedent at the IETF for a registry =
mechanism less formal that what IANA provides?<br></div><br></div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex">

5.2. Specifying Transport Properties<br>
<br>
=C2=A0* There are a lot of choices being made about how users will want to =
prioritize transport protocol selection. How confident are we that, for ins=
tance, path selection should take priority over protocol selection? I think=
 that&#39;s right, but I wonder if it might not make more sense to have two=
 interfaces: one that provides a purely numeric priority ordering of prefer=
ences, and one (based on the existing 5-level preferences) that maps into i=
t.<br></blockquote><div><br></div><div><div style=3D"font-size:small" class=
=3D"gmail_default">I&#39;m okay with whoever said that this is unworkable. =
I&#39;m sure I missed the original discussion.<br></div></div><div>=C2=A0</=
div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor=
der-left:1px solid rgb(204,204,204);padding-left:1ex">

=C2=A0* Using the same enum (Require(d[sic])/Avoid/Ignore) for the queried =
output of selected properties seems like a shortcut that will lead to some =
confusion.<br>
<br>
MW: I agree;=C2=A0 partially addressed: s/Required/Require wherever it&#39;=
s a Preference level.<br></blockquote><div><br></div><div><div style=3D"fon=
t-size:small" class=3D"gmail_default">FWIW, my objection to the other issue=
 (using a normative term as an indication of what was chosen) isn&#39;t tha=
t it&#39;s underspecified, only that it&#39;s confusing. I put it roughly i=
n the same category as specifying -1 as an error indicator in an abstract A=
PI. Is the idea that the output parameters could be fed into the protocol s=
election logic for a subsequent connection to select the same protocol? Is =
that useful?<br></div></div><div>=C2=A0</div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204=
);padding-left:1ex">

5.2.5. Use 0-RTT Session Establishment with an Idempotent Message<br>
<br>
=C2=A0* I&#39;ll repeat the same statement I made at the mic a few years ag=
o: idempotency !=3D replay-safe. DELETE is idempotent, but not safe for rep=
lay because someone might have done a PUT or POST in the meantime.<br>
<br>
MW: I remember you saying this, sorry that we haven&#39;t addressed it yet!=
 I didn&#39;t understand - is your concern about replaying that a Message m=
ay arrive later, i.e. as Message X, Messages Y and Z in between, then Messa=
ge X again?=C2=A0 =3D&gt; if so, are you saying that this could happen with=
 TFO or QUIC?=C2=A0 (I didn&#39;t think so)<br></blockquote><div><br></div>=
<div><div style=3D"font-size:small" class=3D"gmail_default">What I mean is =
maybe best illustrated by 0RTT in TLS or QUIC. If a user sends a 0RTT DELET=
E /object, followed by a PUT /object, then within the replay window and wit=
hout any replay prevention at the application layer, an attacker could repl=
ay the 0RTT DELETE /object and cause the object to be deleted again. DELETE=
 is idempotent but it&#39;s not safe to replay.<br></div><br></div><div></d=
iv><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bord=
er-left:1px solid rgb(204,204,204);padding-left:1ex">
7.3.3. SendError<br>
<br>
=C2=A0* Is there a reason why a single messageContext object is used for bo=
th sends and receives? I probably missed the original discussion about this=
, but I&#39;d like to understand the reasoning.<br>
<br>
MW: I don&#39;t get this, where does it say that it&#39;s only a single obj=
ect? Or do you mean that it&#39;s the same type? Why is that problematic?<b=
r></blockquote><div><br></div><div><div style=3D"font-size:small" class=3D"=
gmail_default">Same type. (Maybe I should have said &quot;class&quot; inste=
ad of &quot;object&quot;.) For example, the &quot;lifetime&quot; property m=
akes sense as metadata for sends, but is completely irrelevant to the recei=
ver. The same is true of several other message properties. It might make se=
nse for an implementation to use a single type to represent metadata both f=
or sends and receives, but is that also true for an abstract API?<br></div>=
</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0p=
x 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
8. Receiving Data<br>
<br>
=C2=A0* A connection can be used to receive data if it is not configured as=
 unidirectional transmit.<br>
<br>
MW: that&#39;s obviously correct - but I can&#39;t find a statement that wo=
uld contradict what you say here.<br></blockquote><div><br></div><div><div =
style=3D"font-size:small" class=3D"gmail_default">&quot;Once a Connection i=
s established, it can be used for receiving data.&quot; Not true if it&#39;=
s a unidirectional connection.</div></div><div>=C2=A0</div><div><div style=
=3D"font-size:small" class=3D"gmail_default">I&#39;ll take a look at the su=
bsequent replies and respond at the end of the thread to anything that I di=
dn&#39;t cover here.<br></div><br></div></div></div>

--000000000000f0983705a080a105--


From nobody Fri Mar 13 01:02:21 2020
Return-Path: <tapsbot@magpie.corvid.ch>
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 0FF653A122E for <taps@ietfa.amsl.com>; Fri, 13 Mar 2020 01:02:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham 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 1lCGmwoK1SY9 for <taps@ietfa.amsl.com>; Fri, 13 Mar 2020 01:02:17 -0700 (PDT)
Received: from magpie.corvid.ch (magpie.corvid.ch [46.101.110.207]) (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 207DB3A1335 for <taps@ietf.org>; Fri, 13 Mar 2020 01:02:15 -0700 (PDT)
Received: from [127.0.0.1] (helo=magpie.corvid.ch) by magpie.corvid.ch with esmtp (Exim 4.92) (envelope-from <tapsbot@magpie.corvid.ch>) id 1jCfEh-000239-MA for taps@ietf.org; Fri, 13 Mar 2020 08:00:03 +0000
Content-Type: multipart/alternative; boundary="===============5425530588836696038=="
MIME-Version: 1.0
From: TAPS WG status robot <tapsbot@magpie.corvid.ch>
To: taps@ietf.org
Message-Id: <E1jCfEh-000239-MA@magpie.corvid.ch>
Date: Fri, 13 Mar 2020 08:00:03 +0000
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/DcnojiavLf1P0TuMTeQJCZCKj0I>
Subject: [Taps] Weekly github digest (TAPS GitHub Activity Digest)
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: Fri, 13 Mar 2020 08:02:20 -0000

--===============5425530588836696038==
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"; format="flowed"




Issues
------
* ietf-tapswg/api-drafts (+2/-2/=F0=9F=92=AC2)
  2 issues created:
  - Inconsistencies in text realted to selection algorithm and racing (by a=
brunstrom)
    https://github.com/ietf-tapswg/api-drafts/issues/517 =

  - More protocol-specific properties? (by mwelzl)
    https://github.com/ietf-tapswg/api-drafts/issues/516 [API] [future work=
] [help wanted] =


  2 issues received 2 new comments:
  - #429 selection algorithm (text in API doc) (1 by abrunstrom)
    https://github.com/ietf-tapswg/api-drafts/issues/429 [API] [Implementat=
ion] =

  - #418 Use of normative language in Arch (1 by britram)
    https://github.com/ietf-tapswg/api-drafts/issues/418 [Architecture] [di=
scuss] =


  2 issues closed:
  - selection algorithm (text in API doc) https://github.com/ietf-tapswg/ap=
i-drafts/issues/429 [API] [Implementation] =

  - Local Address Preference always only preferred? https://github.com/ietf=
-tapswg/api-drafts/issues/436 [API] [ready for text] =




Pull requests
-------------
* ietf-tapswg/api-drafts (+0/-6/=F0=9F=92=AC7)
  4 pull requests received 7 new comments:
  - #512 Update Multipath properties - closes #437 (3 by mirjak, britram, p=
hilsbln)
    https://github.com/ietf-tapswg/api-drafts/pull/512 [API] =

  - #497 Refactor Local Address Preference, fixes #436 (2 by philsbln, ther=
i)
    https://github.com/ietf-tapswg/api-drafts/pull/497 [API] =

  - #514 Addressing some of Kyle Rose's comments (1 by britram)
    https://github.com/ietf-tapswg/api-drafts/pull/514 =

  - #433 Editorial nits to improve consistency (1 by mwelzl)
    https://github.com/ietf-tapswg/api-drafts/pull/433 [API] =


  6 pull requests merged:
  - Addressing some of Kyle Rose's comments
    https://github.com/ietf-tapswg/api-drafts/pull/514 =

  - Clean up unnecessary normative language in arch
    https://github.com/ietf-tapswg/api-drafts/pull/502 [Architecture] =

  - Move algorithm text to Implementation draft, make Interface draft more =
flexible
    https://github.com/ietf-tapswg/api-drafts/pull/511 [API] [Implementatio=
n] =

  - API receive semantics and DSCP text fixes; closes minor issues #454 #45=
0 #494
    https://github.com/ietf-tapswg/api-drafts/pull/513 =

  - Refactor Local Address Preference, fixes #436
    https://github.com/ietf-tapswg/api-drafts/pull/497 [API] =

  - First attempt to write some privacy considerations
    https://github.com/ietf-tapswg/api-drafts/pull/501 =



Repositories tracked by this digest:
-----------------------------------
* https://github.com/ietf-tapswg/api-drafts

--===============5425530588836696038==
Content-Type: text/html; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

<!doctype html>
<html lang=3D"en">
<head>
<meta charset=3D"utf-8">
<title>Weekly github digest (TAPS GitHub Activity Digest)</title>
<style>
body { font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;=
 font-size: 14px; }
h2 { margin-top: 3em; color: #A52A2A; font-style: italic; font-weight: norm=
al; }
h3 { margin-bottom:0; margin-top: 2em; font-size: 1.2em; }
h1+h2 { margin-top: 1em; }
a { color: #bb6219; text-decoration: none; }
li { margin-bottom: .35em; }
.repos { margin-bottom: 0; margin-top:0; line-height: 1.2; }
.new { color: red; }
.label { display: inline;
	padding: .2em .6em .3em;
	font-size: 75%;
	font-weight: 700;
	line-height: 1;
	color: #fff;
	text-align: center;
	white-space: nowrap;
	vertical-align: baseline;
	border-radius: .25em;
}
</style>
</head>

<body>
<h1>Friday March 13, 2020</h1>


<h2>Issues</h2>

<h3>ietf-tapswg/api-drafts (+2/-2/=F0=9F=92=AC2)</h3>
  <p class=3D"new">2 issues created:</p>
  <ul>
  <li>#517 <a href=3D"https://github.com/ietf-tapswg/api-drafts/issues/517"=
>Inconsistencies in text realted to selection algorithm and racing</a> (by =
abrunstrom) </li>
  =

  <li>#516 <a href=3D"https://github.com/ietf-tapswg/api-drafts/issues/516"=
>More protocol-specific properties?</a> (by mwelzl) <span class=3D"label" s=
tyle=3D"background-color: #fbca04; color: #000000">API</span> <span class=
=3D"label" style=3D"background-color: #0d5196; color: #ffffff">future work<=
/span> <span class=3D"label" style=3D"background-color: #008672; color: #ff=
ffff">help wanted</span> </li>
  </ul>

  <p>2 issues received 2 new comments:</p>
  <ul>
  <li>#429 <a href=3D"https://github.com/ietf-tapswg/api-drafts/issues/429"=
>selection algorithm (text in API doc)</a> (1 by abrunstrom) <span class=3D=
"label" style=3D"background-color: #fbca04; color: #000000">API</span> <spa=
n class=3D"label" style=3D"background-color: #fbca04; color: #000000">Imple=
mentation</span> </li>
  =

  <li>#418 <a href=3D"https://github.com/ietf-tapswg/api-drafts/issues/418"=
>Use of normative language in Arch</a> (1 by britram) <span class=3D"label"=
 style=3D"background-color: #fbca04; color: #000000">Architecture</span> <s=
pan class=3D"label" style=3D"background-color: #b60205; color: #ffffff">dis=
cuss</span> </li>
  </ul>

  <p>2 issues closed:</p>
  <ul>
  <li>#429 <a href=3D"https://github.com/ietf-tapswg/api-drafts/issues/429"=
>selection algorithm (text in API doc)</a> <span class=3D"label" style=3D"b=
ackground-color: #fbca04; color: #000000">API</span> <span class=3D"label" =
style=3D"background-color: #fbca04; color: #000000">Implementation</span> <=
/li>
  =

  <li>#436 <a href=3D"https://github.com/ietf-tapswg/api-drafts/issues/436"=
>Local Address Preference always only preferred?</a> <span class=3D"label" =
style=3D"background-color: #fbca04; color: #000000">API</span> <span class=
=3D"label" style=3D"background-color: #4ae0d1; color: #000000">ready for te=
xt</span> </li>
  </ul>



<h2>Pull requests</h2>
<h3>ietf-tapswg/api-drafts (+0/-6/=F0=9F=92=AC7)</h3>

  <p>4 pull requests received 7 new comments:</p>
  <ul>
  <li>#512 <a href=3D"https://github.com/ietf-tapswg/api-drafts/pull/512">U=
pdate Multipath properties - closes #437</a> (3 by mirjak, britram, philsbl=
n) <span class=3D"label" style=3D"background-color: #fbca04; color: #000000=
">API</span> </li>
  =

  <li>#497 <a href=3D"https://github.com/ietf-tapswg/api-drafts/pull/497">R=
efactor Local Address Preference, fixes #436</a> (2 by philsbln, theri) <sp=
an class=3D"label" style=3D"background-color: #fbca04; color: #000000">API<=
/span> </li>
  =

  <li>#514 <a href=3D"https://github.com/ietf-tapswg/api-drafts/pull/514">A=
ddressing some of Kyle Rose&#x27;s comments</a> (1 by britram) </li>
  =

  <li>#433 <a href=3D"https://github.com/ietf-tapswg/api-drafts/pull/433">E=
ditorial nits to improve consistency</a> (1 by mwelzl) <span class=3D"label=
" style=3D"background-color: #fbca04; color: #000000">API</span> </li>
  </ul>

  <p>6 pull requests merged:</p>
  <ul>
  <li>#514 <a href=3D"https://github.com/ietf-tapswg/api-drafts/pull/514">A=
ddressing some of Kyle Rose&#x27;s comments</a> </li>
  =

  <li>#502 <a href=3D"https://github.com/ietf-tapswg/api-drafts/pull/502">C=
lean up unnecessary normative language in arch</a> <span class=3D"label" st=
yle=3D"background-color: #fbca04; color: #">Architecture</span> </li>
  =

  <li>#511 <a href=3D"https://github.com/ietf-tapswg/api-drafts/pull/511">M=
ove algorithm text to Implementation draft, make Interface draft more flexi=
ble</a> <span class=3D"label" style=3D"background-color: #fbca04; color: #"=
>API</span> <span class=3D"label" style=3D"background-color: #fbca04; color=
: #">Implementation</span> </li>
  =

  <li>#513 <a href=3D"https://github.com/ietf-tapswg/api-drafts/pull/513">A=
PI receive semantics and DSCP text fixes; closes minor issues #454 #450 #49=
4</a> </li>
  =

  <li>#497 <a href=3D"https://github.com/ietf-tapswg/api-drafts/pull/497">R=
efactor Local Address Preference, fixes #436</a> <span class=3D"label" styl=
e=3D"background-color: #fbca04; color: #">API</span> </li>
  =

  <li>#501 <a href=3D"https://github.com/ietf-tapswg/api-drafts/pull/501">F=
irst attempt to write some privacy considerations</a> </li>
  </ul>


<h2>Repositories tracked by this digest:</h2>
<ul class=3D"repos">
  <li><a href=3D"https://github.com/ietf-tapswg/api-drafts">https://github.=
com/ietf-tapswg/api-drafts</a></li>
  </ul>
</body>
</html>

--===============5425530588836696038==--


From nobody Tue Mar 17 07:59:28 2020
Return-Path: <aaron.falk@gmail.com>
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 9E0513A08AE for <taps@ietfa.amsl.com>; Tue, 17 Mar 2020 07:59:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 oZlGV4WZ3UQP for <taps@ietfa.amsl.com>; Tue, 17 Mar 2020 07:59:25 -0700 (PDT)
Received: from mail-qt1-x835.google.com (mail-qt1-x835.google.com [IPv6:2607:f8b0:4864:20::835]) (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 1F0703A08AB for <taps@ietf.org>; Tue, 17 Mar 2020 07:59:24 -0700 (PDT)
Received: by mail-qt1-x835.google.com with SMTP id i26so7876477qtq.8 for <taps@ietf.org>; Tue, 17 Mar 2020 07:59:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=K1YgOz6/BHV406tzvpxf7U/2eUlB0NadR404a9SHSng=; b=IeiWCLPsjsb79Pbn1TUudKgVBCm8Tp1qDrteFhLfyNHD2v5zEl4PYosIKfxGx6c2cr atQ4SVsQQP7nQmy8YXmN0/jZQBjPHBhx1u3COFBmBfcp3inBRXGJ91gyk19f3RXbobeP Qi45Ejjdn83jws6QAoeX+wmHij+/qBFkKIudyLZCsEldjdKg/l1a2lMvwA8qtYDKv1qK Ly3qHbzfwK8MJHqYZBZMV4WKQtaNrpprMuJNUNrJ15P1+sCIw+qc9C9/0/CHWxwhZ9FY YHS6s5uc7oDUJbJ9vdP0LtzBq1j7rTgbLo48LJtvOUA7g34KHD7TXOK7BCQZL87uNw5k /1eQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=K1YgOz6/BHV406tzvpxf7U/2eUlB0NadR404a9SHSng=; b=OD4i78WGI5H2Vwwo8MjLAnSMyxiFGPGEiEiiiiy4fC/2m20kJiqgtFZHmjk702FRcV 1DBMjfGjWkQoVb0E4d3wiHuZHkAPEvood0Heh+ZOJUF2cBJnnP/i9DBVDWwAJ52Mn4lN b55d+a3vefWS3y43CHEQTYEz52pfaGUVJzPNhIdkVKxoBd4eWJEUmiCJCU+NqlpNdqv5 CxSr5bXgYw9P0hju1qnLhaRMJa222gdAPlZQxRmp+zUPNyWBeDHl4HjS8U25WyDz1UNa sPymq3zFgcGOmp/7BTeQIx3xGGUiU8DfsTmpH/kRlIke3NpHq3uRxvR5Nhd48pFi6o+H EAaw==
X-Gm-Message-State: ANhLgQ0ToIIMjVC41tyALjb5bVFLQJ8AjdMVuhfK+cnSQZ0MJwILkQco dNRV+MiwOyrS36EIQitw5OKgkXM/
X-Google-Smtp-Source: ADFU+vsciHX1jCvKlWOZ09jE1YfkyOkti0zO7ipz6TuYLYZVNgu6l82x8CbJyoURko+CzDIXBrgOHA==
X-Received: by 2002:ac8:4895:: with SMTP id i21mr5991152qtq.55.1584457163374;  Tue, 17 Mar 2020 07:59:23 -0700 (PDT)
Received: from [172.19.114.87] ([2601:184:4881:2420:6ca7:6a09:a5e:c696]) by smtp.gmail.com with ESMTPSA id h138sm2046959qke.86.2020.03.17.07.59.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 17 Mar 2020 07:59:22 -0700 (PDT)
From: "Aaron Falk" <aaron.falk@gmail.com>
To: "taps WG" <taps@ietf.org>
Cc: "Magnus Westerlund" <magnus.westerlund@ericsson.com>, "Zaheduzzaman Sarker" <zaheduzzaman.sarker@ericsson.com>
Date: Tue, 17 Mar 2020 10:59:21 -0400
X-Mailer: MailMate (1.13.1r5671)
Message-ID: <18805F34-42FE-42D8-AE3D-5D9AE2111A9A@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_7D7DBD73-DDE8-408C-B8FB-F9D01A765F76_="
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/ku6aRywklPqELGq2vUhQDkF1pAA>
Subject: [Taps] TAPS April Interim Scheduling
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, 17 Mar 2020 14:59:27 -0000

--=_MailMate_7D7DBD73-DDE8-408C-B8FB-F9D01A765F76_=
Content-Type: text/plain; charset="UTF-8"; format=flowed; markup=markdown
Content-Transfer-Encoding: 8bit

Doodle to select meeting date for April interim.  We’ve had good luck 
with Fridays 11am EDT so please vote.  (Preference given to authors.) 
Date will be selected at the end of this week.

https://doodle.com/poll/7b6p6a9twgrtf7ib

--aaron
--=_MailMate_7D7DBD73-DDE8-408C-B8FB-F9D01A765F76_=
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html>
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal"><=
p dir=3D"auto">Doodle to select meeting date for April interim.  We=E2=80=
=99ve had good luck with Fridays 11am EDT so please vote.  (Preference gi=
ven to authors.) Date will be selected at the end of this week.</p>
<p dir=3D"auto"><a href=3D"https://doodle.com/poll/7b6p6a9twgrtf7ib" styl=
e=3D"color:#3983C4">https://doodle.com/poll/7b6p6a9twgrtf7ib</a></p>
<p dir=3D"auto">--aaron</p>
</div>
</div>
</body>
</html>

--=_MailMate_7D7DBD73-DDE8-408C-B8FB-F9D01A765F76_=--


From nobody Thu Mar 19 04:25:08 2020
Return-Path: <michawe@ifi.uio.no>
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 8D4BB3A279F for <taps@ietfa.amsl.com>; Thu, 19 Mar 2020 04:25:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 LPm5WMZ5lhvH for <taps@ietfa.amsl.com>; Thu, 19 Mar 2020 04:24:57 -0700 (PDT)
Received: from mail-out02.uio.no (mail-out02.uio.no [IPv6:2001:700:100:8210::71]) (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 6273F3A279D for <taps@ietf.org>; Thu, 19 Mar 2020 04:24:56 -0700 (PDT)
Received: from mail-mx12.uio.no ([129.240.10.84]) by mail-out02.uio.no with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93.0.4) (envelope-from <michawe@ifi.uio.no>) id 1jEtIC-0007JR-OA for taps@ietf.org; Thu, 19 Mar 2020 12:24:52 +0100
Received: from ti0182q160-4479.bb.online.no ([84.202.168.179] helo=[192.168.1.4]) by mail-mx12.uio.no with esmtpsa (TLS1.2:ECDHE-RSA-AES256-GCM-SHA384:256) user michawe (Exim 4.93.0.4) (envelope-from <michawe@ifi.uio.no>) id 1jEtIC-0008mE-6d for taps@ietf.org; Thu, 19 Mar 2020 12:24:52 +0100
From: Michael Welzl <michawe@ifi.uio.no>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Message-Id: <59B01497-6F7A-4DE3-9B37-0F4C357383CE@ifi.uio.no>
Date: Thu, 19 Mar 2020 12:24:50 +0100
To: "taps@ietf.org" <taps@ietf.org>
X-Mailer: Apple Mail (2.3445.104.11)
X-UiO-SPF-Received: Received-SPF: neutral (mail-mx12.uio.no: 84.202.168.179 is neither permitted nor denied by domain of ifi.uio.no) client-ip=84.202.168.179; envelope-from=michawe@ifi.uio.no; helo=[192.168.1.4];
X-UiO-Spam-info: not spam, SpamAssassin (score=-5.0, required=5.0, autolearn=disabled, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO)
X-UiO-Scanned: 265B2BAECFCCEA059014F00A7AC007F924A8D689
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/yOqRBxDQ8LY57eu6gZdQdqCGJew>
Subject: [Taps] Measurements of the chance of network traversal for non-TCP protocols
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: Thu, 19 Mar 2020 11:25:05 -0000

Hi all,

I thought I=E2=80=99d point you at a paper that we just got published: a =
measurement study with the goal to better understand which protocols and =
encapsulations might be a good idea to consider for racing. We (authors) =
just received this URL from Elsevier, telling us that we could share it, =
as it gives free access to the article for 50 days: =
https://authors.elsevier.com/c/1alpp_VbShoaUs

Cheers,
Michael


From nobody Thu Mar 19 12:27:14 2020
Return-Path: <aaron.falk@gmail.com>
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 DBB9A3A0E05 for <taps@ietfa.amsl.com>; Thu, 19 Mar 2020 12:27:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 xXN5FvuuVtPS for <taps@ietfa.amsl.com>; Thu, 19 Mar 2020 12:27:02 -0700 (PDT)
Received: from mail-qt1-x82e.google.com (mail-qt1-x82e.google.com [IPv6:2607:f8b0:4864:20::82e]) (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 270493A0DB7 for <taps@ietf.org>; Thu, 19 Mar 2020 12:27:01 -0700 (PDT)
Received: by mail-qt1-x82e.google.com with SMTP id d12so461689qtj.4 for <taps@ietf.org>; Thu, 19 Mar 2020 12:27:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=3QoQHa+0AFb4S78qpecCHkhpXK7XGqNNw3vi6RjNmek=; b=qsECMVdgHNryZOh5rzo4+5XwbroVU9kF+yRsidncb64Fgdtn2WLt16UI2QrDD4MJ2F djku7cZk35IHrqxXB2zIHpgbTBIh+B+VvkSy8DWryfvtoagpI6cmGKX/RT2X+jXQ0E+s xNS/eW/dSGZRDeb8psvE6bZ6vpSUM+0fFAY10AEPbqjr9cjt6nw1SCqVvWPtetc3OqGO wtCVxk+f7Fk6ShgPazoXOCLiJg9FpAmB/qGgubf836af85zLRKUAD0TZRGrQURLbfRB8 jBMmLNf8pH6rUyc30yUaMCfjYTeKQdY3ZZUiySIcPceoqvyzbj4HwAXz877VmWlRV7RV l3Dg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=3QoQHa+0AFb4S78qpecCHkhpXK7XGqNNw3vi6RjNmek=; b=AN98ujb9ED7r43HPYCgNQL4XnIvRbzEbbXbeu4Uenr1r38bawCYbCffRloWgHFBIKs bZIT5wup18w3VE6zM4On9rTEIMR86kVMPm/sMyn/OqJlPT5xcFBxytEBF2PsQMZNkWz1 44CyaRzZayGZRO8v3lrvESQ5vqio8BIoH1Og4HK4UoaQp46UbXzjl53xHCGQsiVOJbPF SdPd+P6UqD4WUDgd7MkdBMr9UlgY6Pkhe5KqVAmKrLUII5tuswgQdreAL2BoEXIgwtow XEDDb6yfxI7f+UGDj4n9846c2ShTZlDwVAKqx6WBm2fjrZ8TtzvEDxP+KAJpiN7IEi5D pdzg==
X-Gm-Message-State: ANhLgQ2xuhV5AEwe38hY5U+BEEUndgBermWwVqEjkC97Vgm2Siga6DOP 8zOGXAd8oVHCShUpVhheM2Hyo5PG
X-Google-Smtp-Source: ADFU+vvqC/b9rhwuc+nsbAvSQCKjslXhNIC0VTYUsYKvenqpaC8SClj9OX7daMQpY1egM8mjtyl+5Q==
X-Received: by 2002:ac8:5159:: with SMTP id h25mr4787870qtn.165.1584646020644;  Thu, 19 Mar 2020 12:27:00 -0700 (PDT)
Received: from [172.19.116.117] ([2601:184:4881:2420:90ac:8bf2:6d5e:bdc0]) by smtp.gmail.com with ESMTPSA id d141sm2127364qke.68.2020.03.19.12.26.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 19 Mar 2020 12:26:59 -0700 (PDT)
From: "Aaron Falk" <aaron.falk@gmail.com>
To: "taps WG" <taps@ietf.org>
Cc: "Magnus Westerlund" <magnus.westerlund@ericsson.com>, "Zaheduzzaman Sarker" <zaheduzzaman.sarker@ericsson.com>
Date: Thu, 19 Mar 2020 15:26:57 -0400
X-Mailer: MailMate (1.13.1r5671)
Message-ID: <E4EBDD29-A18D-4B07-BA1A-F4D563A5EC08@gmail.com>
In-Reply-To: <18805F34-42FE-42D8-AE3D-5D9AE2111A9A@gmail.com>
References: <18805F34-42FE-42D8-AE3D-5D9AE2111A9A@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_F79E8CF7-0095-499A-AA28-F7F5C7BA0A6A_="
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/Y55f45A8DUEeXh2CSXS3q-tmo-k>
Subject: Re: [Taps] TAPS April Interim Scheduling
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: Thu, 19 Mar 2020 19:27:12 -0000

--=_MailMate_F79E8CF7-0095-499A-AA28-F7F5C7BA0A6A_=
Content-Type: text/plain; charset="UTF-8"; format=flowed; markup=markdown
Content-Transfer-Encoding: 8bit

Looks like everyone responding can make April 17, 11am - 1pm EDT / 8am - 
10am PDT / 4pm - 6pm UTC.  If you cannot, please complete the doodle 
poll ASAP.

Thanks,

--aaron

On 17 Mar 2020, at 10:59, Aaron Falk wrote:

> Doodle to select meeting date for April interim.  We’ve had good 
> luck with Fridays 11am EDT so please vote.  (Preference given to 
> authors.) Date will be selected at the end of this week.
>
> https://doodle.com/poll/7b6p6a9twgrtf7ib
>
> --aaron

--=_MailMate_F79E8CF7-0095-499A-AA28-F7F5C7BA0A6A_=
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html>
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal"><=
p dir=3D"auto">Looks like everyone responding can make April 17, 11am - 1=
pm EDT / 8am - 10am PDT / 4pm - 6pm UTC.  If you cannot, please complete =
the doodle poll ASAP.</p>
<p dir=3D"auto">Thanks,</p>
<p dir=3D"auto">--aaron</p>
<p dir=3D"auto">On 17 Mar 2020, at 10:59, Aaron Falk wrote:</p>
<blockquote style=3D"border-left:2px solid #777; color:#777; margin:0 0 5=
px; padding-left:5px"><p dir=3D"auto">Doodle to select meeting date for A=
pril interim.  We=E2=80=99ve had good luck with Fridays 11am EDT so pleas=
e vote.  (Preference given to authors.) Date will be selected at the end =
of this week.<br>
<br>
<a href=3D"https://doodle.com/poll/7b6p6a9twgrtf7ib" style=3D"color:#777"=
>https://doodle.com/poll/7b6p6a9twgrtf7ib</a><br>
<br>
--aaron</p>
</blockquote></div>
</div>
</body>
</html>

--=_MailMate_F79E8CF7-0095-499A-AA28-F7F5C7BA0A6A_=--


From nobody Fri Mar 20 11:49:30 2020
Return-Path: <aaron.falk@gmail.com>
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 E23C93A0DE5 for <taps@ietfa.amsl.com>; Fri, 20 Mar 2020 11:49:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 1DbFdQpY4ATt for <taps@ietfa.amsl.com>; Fri, 20 Mar 2020 11:49:14 -0700 (PDT)
Received: from mail-qk1-x731.google.com (mail-qk1-x731.google.com [IPv6:2607:f8b0:4864:20::731]) (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 E80ED3A0D2E for <taps@ietf.org>; Fri, 20 Mar 2020 11:49:13 -0700 (PDT)
Received: by mail-qk1-x731.google.com with SMTP id c145so7950336qke.12 for <taps@ietf.org>; Fri, 20 Mar 2020 11:49:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version; bh=eJ3PqFpNz5Y1oH+qee38KX3kJMyTDbS99TPr18hXK/Q=; b=eNOvtSF14+NnLatysRsH1i7JXX2ffkimuGz5zLuQN7KVu5aKqcE3yyXYTXbOwhkHBH ZcIUe3nxzGnyEJkX4Sc5PrhgkgnB+48ibT82lKnw43XGfmFyaMIxJnh64O8Pw2HtbSBL piEOotVnbG27PLZwBjF6jSaVGdmTQQuij9+pIs/EOCIQfNsKoAutRewp6kBkcr1oyL9G zKkS6NfGFETo+4/fVISa7qPh+qj4gDpGZRfVvT9CqQV3508adaonlme73YNjEuv3xOSK liFe22iicSO9zk2oY1v92bDtiBDxMmJevk8c30gDg8DWcclZrY3bjTZrlOKOhANKkiou yxpw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version; bh=eJ3PqFpNz5Y1oH+qee38KX3kJMyTDbS99TPr18hXK/Q=; b=gwpBbiG/Ze/wLp+bm2fTAfCz6jyl6oy0TLWhIstM2Kxfygyx0dgSC1BtqTGLMiKuXH QS4qZTggGfjsElrraCldbmkOcV6XEQr1VGAuAgu3ST+PHkwo1JxgQR7KlW5uzaDMklHM WYseYEb40Pzp499ObcI0dr3b1pR6YaUlUEdINqXV0ysXl7eMITuJ4Kzh1AJ2ZWZXMKfs 8nt2UVkiU442PG5wZk7eZAuwQcznZ7zmVahzOkDWq2qiYgg/iPczNMez3Zcy9c2d4Vm5 cezRFEgTWjHkBtDrdU8xVFkw15M+ZRjbihger+nG5YgrNSpVkG9DDv4Y+Y1yfWz7d0Cc QfIw==
X-Gm-Message-State: ANhLgQ36fJ9MvJZAA4gHo6gbgX2GhumKo4CJEiYa54yIdFVKQg1hB3eY Qjtp0p6lB7hamKKw4bjtZE/0KsvM
X-Google-Smtp-Source: ADFU+vtPVh/C+stLKi75wlbBRpyh2ks+XMbstR2ADhcS24L2C1UFEfQTLwOcmshkvgc//G1kRS+JoA==
X-Received: by 2002:ae9:e403:: with SMTP id q3mr4448038qkc.241.1584730152442;  Fri, 20 Mar 2020 11:49:12 -0700 (PDT)
Received: from [172.19.116.117] ([2601:184:4881:2420:3985:2fee:5db5:cd9c]) by smtp.gmail.com with ESMTPSA id o67sm4576052qka.114.2020.03.20.11.49.11 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 20 Mar 2020 11:49:11 -0700 (PDT)
From: "Aaron Falk" <aaron.falk@gmail.com>
To: "taps WG" <taps@ietf.org>
Cc: "Magnus Westerlund" <magnus.westerlund@ericsson.com>, "Zaheduzzaman Sarker" <zaheduzzaman.sarker@ericsson.com>
Date: Fri, 20 Mar 2020 14:49:10 -0400
X-Mailer: MailMate (1.13.1r5671)
Message-ID: <81D5CFCB-634F-41E0-AC22-D7BAFCC34D33@gmail.com>
In-Reply-To: <E4EBDD29-A18D-4B07-BA1A-F4D563A5EC08@gmail.com>
References: <18805F34-42FE-42D8-AE3D-5D9AE2111A9A@gmail.com> <E4EBDD29-A18D-4B07-BA1A-F4D563A5EC08@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_18C6A727-33B7-4BBC-8413-B9A87AA605ED_="
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/h6YFD20aCeT0yMAmYpgYKV0EwZw>
Subject: Re: [Taps] TAPS April Interim Scheduling
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: Fri, 20 Mar 2020 18:49:28 -0000

--=_MailMate_18C6A727-33B7-4BBC-8413-B9A87AA605ED_=
Content-Type: text/plain; charset="UTF-8"; format=flowed; markup=markdown
Content-Transfer-Encoding: quoted-printable

The IESG call runs until 5pm UTC which conflicts with Mirja and Magnus. =

So, I=E2=80=99d like to propose we adjust the time to fit.  Also, the tim=
es I =

pasted into the Doodle are messed up because of daylight savings in the =

US.  To get it right, I consulted [this =

site](https://www.worldtimebuddy.com/?qm=3D1&lid=3D100,5,8&h=3D100&date=3D=
2020-4-17&sln=3D17-19). =

  Bottom line: If you cannot attend on April 17 if we run the call from =

the times below please speak up.


| UTC | EDT | PDT |
| :---: | :---: | :---: |
| 5:00p - 7:00p | 1:00p - 3:00p | 10:00a - 12:00p |

Webex link: https://ietf.webex.com/meet/taps

Sorry for the confusion!

--aaron


On 19 Mar 2020, at 15:26, Aaron Falk wrote:

> Looks like everyone responding can make April 17, 11am - 1pm EDT / 8am =

> - 10am PDT / 4pm - 6pm UTC.  If you cannot, please complete the doodle =

> poll ASAP.
>
> Thanks,
>
> --aaron
>
> On 17 Mar 2020, at 10:59, Aaron Falk wrote:
>
>> Doodle to select meeting date for April interim.  We=E2=80=99ve had go=
od =

>> luck with Fridays 11am EDT so please vote.  (Preference given to =

>> authors.) Date will be selected at the end of this week.
>>
>> https://doodle.com/poll/7b6p6a9twgrtf7ib
>>
>> --aaron

--=_MailMate_18C6A727-33B7-4BBC-8413-B9A87AA605ED_=
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html>
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">The IESG call runs until 5pm UTC which conflicts with Mir=
ja and Magnus. So, I=E2=80=99d like to propose we adjust the time to fit.=
  Also, the times I pasted into the Doodle are messed up because of dayli=
ght savings in the US.  To get it right, I consulted <a href=3D"https://w=
ww.worldtimebuddy.com/?qm=3D1&amp;lid=3D100,5,8&amp;h=3D100&amp;date=3D20=
20-4-17&amp;sln=3D17-19" style=3D"color:#3983C4">this site</a>.  Bottom l=
ine: If you cannot attend on April 17 if we run the call from the times b=
elow please speak up.</p>

<table style=3D"background-color:#F7F7F7; border-collapse:collapse; borde=
r-radius:5px 5px 5px 5px; font-size:0.9em; margin:0 2em" bgcolor=3D"#F7F7=
F7"><thead>
<tr>
<th align=3D"center" style=3D"padding:0.5em">UTC</th>
<th align=3D"center" style=3D"padding:0.5em; border-left:1px solid lightg=
ray">EDT</th>
<th align=3D"center" style=3D"padding:0.5em; border-left:1px solid lightg=
ray">PDT</th>
</tr>
</thead><tbody>
<tr>
<td align=3D"center" style=3D"border-top:1px solid lightgray; padding:0.5=
em">5:00p - 7:00p</td>
<td align=3D"center" style=3D"border-top:1px solid lightgray; padding:0.5=
em; border-left:1px solid lightgray">1:00p - 3:00p</td>
<td align=3D"center" style=3D"border-top:1px solid lightgray; padding:0.5=
em; border-left:1px solid lightgray">10:00a - 12:00p</td>
</tr>
</tbody></table>

<p dir=3D"auto">Webex link: <a href=3D"https://ietf.webex.com/meet/taps" =
style=3D"color:#3983C4">https://ietf.webex.com/meet/taps</a></p>

<p dir=3D"auto">Sorry for the confusion!</p>

<p dir=3D"auto">--aaron</p>

<p dir=3D"auto">On 19 Mar 2020, at 15:26, Aaron Falk wrote:</p>

<blockquote style=3D"border-left:2px solid #777; color:#777; margin:0 0 5=
px; padding-left:5px">
<p dir=3D"auto">Looks like everyone responding can make April 17, 11am - =
1pm EDT / 8am - 10am PDT / 4pm - 6pm UTC.  If you cannot, please complete=
 the doodle poll ASAP.</p>

<p dir=3D"auto">Thanks,</p>

<p dir=3D"auto">--aaron</p>

<p dir=3D"auto">On 17 Mar 2020, at 10:59, Aaron Falk wrote:</p>

<blockquote style=3D"border-left:2px solid #777; color:#999; margin:0 0 5=
px; padding-left:5px; border-left-color:#999">
<p dir=3D"auto">Doodle to select meeting date for April interim.  We=E2=80=
=99ve had good luck with Fridays 11am EDT so please vote.  (Preference gi=
ven to authors.) Date will be selected at the end of this week.</p>

<p dir=3D"auto"><a href=3D"https://doodle.com/poll/7b6p6a9twgrtf7ib" styl=
e=3D"color:#999">https://doodle.com/poll/7b6p6a9twgrtf7ib</a></p>

<p dir=3D"auto">--aaron</p>
</blockquote>
</blockquote>
</div>
</div>
</body>
</html>

--=_MailMate_18C6A727-33B7-4BBC-8413-B9A87AA605ED_=--


From nobody Mon Mar 23 07:54:31 2020
Return-Path: <magnus.westerlund@ericsson.com>
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 62C1B3A08E7 for <taps@ietfa.amsl.com>; Mon, 23 Mar 2020 07:54:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.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 SA4H1vpLzWk2 for <taps@ietfa.amsl.com>; Mon, 23 Mar 2020 07:54:28 -0700 (PDT)
Received: from EUR03-VE1-obe.outbound.protection.outlook.com (mail-eopbgr50068.outbound.protection.outlook.com [40.107.5.68]) (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 817C03A076C for <taps@ietf.org>; Mon, 23 Mar 2020 07:54:27 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=FiHKAPpj0eYdGMFUK7jKH3WO14vcBElnTPyhfi7/asNM7HFptyiWOOvQQdfNzyKdgPL2Bt3eMjMUEE/4FPNjJVrhbb1FJDaX/3QUnnpXAss0Zdq/Wt9HRriSQjBWi5baRg+M+h/wjcERPQMmHMrwUpAAknqyeYhIs6shpo8Eew/VmkWpSkenbs1gYhvTeSImugB0GKtEv862PQwr8wBkWDuGjB/dFBOqZNNq+/JeXCeClIcOv/D7bGvkao5Jp+CUkpSCwrtCoKFS0yrJwLfyFYHSzSFuWqqPkaDUSw3yvD6zF7Bz0kGj4QRYaRpUdMT0CHV3mnAI+2R0q6/AEbgiwA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=rDYMV4pSViW7dDP8NnPyZXS9ftrcfxTwWni8iZUK1Fg=; b=P6EM9MTtiSzWCKylU6cX5gB6hlWr2R105GC9YayNaEExgOW/c09VocosgU/qIJUrAGFpzIYrdYuJ9xxRWxphRe68LkVAadbSfCTRhpfocebI6LwVGGay4BUK+Rxh+OWm+tHM6I/RFw08sf2aUq95eDkyssYxeMp8/eYOyMPWj9IkAogD2WESpaZ9GLcY4UZKDpVuefyx0kwSo1FRayZ50+I6+ShKpa7ve5QB9uAcEFyoCcHV2XnUVp6D7/63c+RTa7FKcH4Pu9U3mKqD9tCpcsYob3GnxU9qXH38mJw9hDyDxRYM1HONHiUD0T02wagzYTxEnmcrJgxP4RHc7AhsJA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=rDYMV4pSViW7dDP8NnPyZXS9ftrcfxTwWni8iZUK1Fg=; b=UyqhckwOAhDZ8B3xJwynFqMtkrZQOm7Xvt+y06WYENcwmqsfGAIIumZ7lz6C/3lY1I4HnbReC+BsHgbYtH2Ovq1EezxtwGpU7zsqmZFDsy1bY1bMpIPXDr8YqPQMMxnYpr+/UqfWfAJG47gJet6ex3ng21a7wx94siVt2rXiUjk=
Received: from HE1PR0702MB3772.eurprd07.prod.outlook.com (52.133.7.14) by HE1PR0702MB3803.eurprd07.prod.outlook.com (10.167.126.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2856.8; Mon, 23 Mar 2020 14:54:22 +0000
Received: from HE1PR0702MB3772.eurprd07.prod.outlook.com ([fe80::8bd:85b0:d547:9eed]) by HE1PR0702MB3772.eurprd07.prod.outlook.com ([fe80::8bd:85b0:d547:9eed%6]) with mapi id 15.20.2835.021; Mon, 23 Mar 2020 14:54:22 +0000
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
To: "taps@ietf.org" <taps@ietf.org>, "aaron.falk@gmail.com" <aaron.falk@gmail.com>
CC: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
Thread-Topic: [Taps] TAPS April Interim Scheduling
Thread-Index: AQHV/Gyu/7URO11Q0EWkwvtCTA2L5KhQT9uAgAGHxwCABHVkAA==
Date: Mon, 23 Mar 2020 14:54:22 +0000
Message-ID: <7cfeb3b3682826b7cbc0033d4bf691808f8e9bd2.camel@ericsson.com>
References: <18805F34-42FE-42D8-AE3D-5D9AE2111A9A@gmail.com> <E4EBDD29-A18D-4B07-BA1A-F4D563A5EC08@gmail.com> <81D5CFCB-634F-41E0-AC22-D7BAFCC34D33@gmail.com>
In-Reply-To: <81D5CFCB-634F-41E0-AC22-D7BAFCC34D33@gmail.com>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Evolution 3.28.5-0ubuntu0.18.04.1 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=magnus.westerlund@ericsson.com; 
x-originating-ip: [158.174.118.23]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 4754b2a1-c386-4d7b-b973-08d7cf3a12d4
x-ms-traffictypediagnostic: HE1PR0702MB3803:|HE1PR0702MB3803:
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <HE1PR0702MB3803F7CF31517FF6AA387B2795F00@HE1PR0702MB3803.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0351D213B3
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(39860400002)(376002)(346002)(136003)(396003)(366004)(199004)(26005)(6512007)(478600001)(66476007)(107886003)(66616009)(66556008)(66946007)(4326008)(64756008)(76116006)(6486002)(966005)(66446008)(2616005)(71200400001)(44832011)(8936002)(81166006)(2906002)(53546011)(6506007)(5660300002)(316002)(186003)(36756003)(8676002)(110136005)(86362001)(81156014)(99106002); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR0702MB3803; H:HE1PR0702MB3772.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: IkmNZQbu9LCKdFcID9rFYOkHYXfiU7Ts32xwju6bTxNEbPWpm46RLvE6qzFZDmORLyhFCnxabfJLyCEJYAs0zfPXni0Vi6VI/Wv6B9eB1l6nLAst2AIDoJYZ6PIQHPKyQgn+btdVAzAGXFFTQHCfNyTIq0LPHMj6ppdw1yMPIUGkX+dmq2a7mkezHbKUnKrE0KA6djyrF7Cb9NL16W+AYXACSnDHRVJib00A+nKxpanS6pgiKHeWzdUQXz+EnGwv1hCsmD6vS5WEV2UFL22toTF2DUxP4DUJWiMQYsqshkjIPD4eEwbzJGx7P5QduzKlPbremD2PKKfY3m1f888WlJviaMOvZ4WkXxmKcINFH7S3dzuUlpdW/elPfCsS5YoYl0hhXPf44knLgC7E25QIbxzVpLUECnnOqJQ+qDZQBbWObiT+F3Csm7MO6gNGSCw1W0W/vZ2R09lK6Rk9bJfBVAvvpqMGXwJ2vlT5zmQ6i3ZpRVhJfyCq4YxwpmlUSisPo1zQ/4z7ZIfXE9hX7U1N1aFTLrh0smKzdl/hMn5jFtKmvNh3tG2W7jF4oFo7tFBP
x-ms-exchange-antispam-messagedata: ouhd2QJ0UpMhsleGOpZf2uOJ5fbn2I6DCnIWjrbhropNOYOhcLN7SAVh69lPioFYuZJS6Hm1VZDZnPQ0pZJlSiDJtfncNwUdTri0gkL/fT34Npvs2cflQ5Y+0ALiHEBhuE8h3eXxbQSRx7mv0mwH2g==
Content-Type: multipart/signed; micalg="sha-256"; protocol="application/x-pkcs7-signature"; boundary="=-EmN6RepnkEMbFhqazMaQ"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 4754b2a1-c386-4d7b-b973-08d7cf3a12d4
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Mar 2020 14:54:22.6308 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: VRvbUgUB0dFjyW2wB9je3ZZ9/JgzHsAXb46ZU4vMnKjQDmC88h8OXrx8ZFaDcJX0Z+Wovnl0qi0NcTFIlOyyNFCMQWNq7gdUFGUtymjIQyQ=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0702MB3803
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/gAuKbV_Xo5H358a4oV22kkailzc>
Subject: Re: [Taps] TAPS April Interim Scheduling
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: Mon, 23 Mar 2020 14:54:30 -0000

--=-EmN6RepnkEMbFhqazMaQ
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi,

Actually the IESG meeting will have end at 16:00 UTC on the 17th of April, =
it is
16:00-18:00 CEST. The TAPS meeting scheduled is 19:00-21:00 CEST. It would =
work
for me, but so you have the right information.=20

Cheers

Magnus

On Fri, 2020-03-20 at 14:49 -0400, Aaron Falk wrote:
> The IESG call runs until 5pm UTC which conflicts with Mirja and Magnus. S=
o,
> I=E2=80=99d like to propose we adjust the time to fit. Also, the times I =
pasted into
> the Doodle are messed up because of daylight savings in the US. To get it
> right, I consulted this site. Bottom line: If you cannot attend on April =
17 if
> we run the call from the times below please speak up.
> UTC	EDT	PDT
> 5:00p - 7:00p	1:00p - 3:00p	10:00a - 12:00p
> Webex link: https://ietf.webex.com/meet/taps
> Sorry for the confusion!
> --aaron
> On 19 Mar 2020, at 15:26, Aaron Falk wrote:
> > Looks like everyone responding can make April 17, 11am - 1pm EDT / 8am =
-
> > 10am PDT / 4pm - 6pm UTC. If you cannot, please complete the doodle pol=
l
> > ASAP.
> > Thanks,
> > --aaron
> > On 17 Mar 2020, at 10:59, Aaron Falk wrote:
> > > Doodle to select meeting date for April interim. We=E2=80=99ve had go=
od luck with
> > > Fridays 11am EDT so please vote. (Preference given to authors.) Date =
will
> > > be selected at the end of this week.
> > > https://doodle.com/poll/7b6p6a9twgrtf7ib
> > > --aaron
--=20
Cheers

Magnus Westerlund=20


----------------------------------------------------------------------
Networks, Ericsson Research
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Torshamnsgatan 23           | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------



--=-EmN6RepnkEMbFhqazMaQ
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCCEtww
ggYHMIID76ADAgECAhALRm3NcHtuMGWutmt5cXntMA0GCSqGSIb3DQEBCwUAMEcxCzAJBgNVBAYT
AlNFMREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBD
QSB2MzAeFw0xNzEyMTUwNzIyMjNaFw0yMDEyMTUwNzIyMjJaMHAxETAPBgNVBAoMCEVyaWNzc29u
MRowGAYDVQQDDBFNYWdudXMgV2VzdGVybHVuZDEtMCsGCSqGSIb3DQEJARYebWFnbnVzLndlc3Rl
cmx1bmRAZXJpY3Nzb24uY29tMRAwDgYDVQQFEwdlcmFtc3dkMIIBIjANBgkqhkiG9w0BAQEFAAOC
AQ8AMIIBCgKCAQEAsKlHZvB3TsmLEDtPSiFFKAh73S2wApt+laqg5eXTqonqnzT9ykEGL2dx9mBT
+2WZiIKxo4w2sisVl3EEYTqXTkctpur7cN29gLC8F3tJHGI2sUVpO9AwpVrN+UuHEVetHt7hdxW9
uYd0LJJ8TP6/wGkIfAFaZxlZUn79O2eHElfih1iVIiTZXLcEe1rBJtzhUNRHWgOm2vQlDJ4sCpig
GFq5w+XSRviEQMkQZRvw1CQmb35QS/C/T36ogzIRHDuAdkoSaiUOY/S2dLp4HkwvOOg+tADpaHkr
bdmdnjKGrYSnJigmxw14pJugxL/Vb2EeVcgpAfVVst7Lm4POPRI8+wIDAQABo4IBxDCCAcAwSAYD
VR0fBEEwPzA9oDugOYY3aHR0cDovL2NybC50cnVzdC50ZWxpYS5jb20vZXJpY3Nzb25ubGluZGl2
aWR1YWxjYXYzLmNybDCBggYIKwYBBQUHAQEEdjB0MCgGCCsGAQUFBzABhhxodHRwOi8vb2NzcDIu
dHJ1c3QudGVsaWEuY29tMEgGCCsGAQUFBzAChjxodHRwOi8vY2EudHJ1c3QudGVsaWFzb25lcmEu
Y29tL2VyaWNzc29ubmxpbmRpdmlkdWFsY2F2My5jZXIwKQYDVR0RBCIwIIEebWFnbnVzLndlc3Rl
cmx1bmRAZXJpY3Nzb24uY29tMFUGA1UdIAROMEwwSgYMKwYBBAGCDwIDAQESMDowOAYIKwYBBQUH
AgEWLGh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYXNvbmVyYS5jb20vQ1BTMB0GA1UdJQQW
MBQGCCsGAQUFBwMEBggrBgEFBQcDAjAdBgNVHQ4EFgQU5ivuhpU51W4UhBDBWwf8XsU837YwHwYD
VR0jBBgwFoAUHHsZnpecdqwgPdjc45Fq49stplMwDgYDVR0PAQH/BAQDAgWgMA0GCSqGSIb3DQEB
CwUAA4ICAQBn0FKukg00UN/c/ESpxSIaYTrsd8liHHMu5rLpOBNOacpGNBMGNgUDDt4QihhoQR3c
vhYXCrAM59NTvw0HNlgqHZoEeVY7YnJJYnJXDCLUfkK5Dn28E3QrzykkF6giUOXDyF9mhWYbSAkJ
yx0Yj0Xc8en3wYNyoFYEqjlKtZrdV0pcgFzEeXVLS8DWrzSy7+KfUtDOEiM6H3zO3nsq++KBmsOi
SKkWn4oYERZg5KElEAHis9av+3KIaEPnOAt8QRWRpFfGZ4d89F16qFvElup5n7l864FqxnC2friD
o4hLQY6ENaOaYIihXhbl2UYxAGDk89aJm/S5pYyq7wzm+KK3IcUl60rmc8SJlt6QXKw0wXEOE1Mu
bauYKMsad2s8jD+rEkXp+agTRl+sezWaRxHBpxuUKDd6MhwDig3SZi1qP7D/Ds4V+JLIjjUJc25l
9tvMGC9+lqI0P+vMI3Zyrou0NNfb55uLQaq18O+7BZ8Kv7jvFdxYyUgbxQ0SPEiyhylcLHAmJeLC
QaiZHmCREBkCLKSf0O4lE2TrVzdOD38wjzuQ27U3UddVCD9EQ3tF7o6EVhpxJJUlB6xe/2UWwy4Z
la71dKLUhakdVrN5abzxqFWvzOAT9nBa2HzYVBtpbcu6KGh72YJ+M79fa9iIkcQCgUnw3gIAeWd/
/n4YbY2QhDCCBgcwggPvoAMCAQICEAtGbc1we24wZa62a3lxee0wDQYJKoZIhvcNAQELBQAwRzEL
MAkGA1UEBhMCU0UxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQDDBxFcmljc3NvbiBOTCBJbmRp
dmlkdWFsIENBIHYzMB4XDTE3MTIxNTA3MjIyM1oXDTIwMTIxNTA3MjIyMlowcDERMA8GA1UECgwI
RXJpY3Nzb24xGjAYBgNVBAMMEU1hZ251cyBXZXN0ZXJsdW5kMS0wKwYJKoZIhvcNAQkBFh5tYWdu
dXMud2VzdGVybHVuZEBlcmljc3Nvbi5jb20xEDAOBgNVBAUTB2VyYW1zd2QwggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQCwqUdm8HdOyYsQO09KIUUoCHvdLbACm36VqqDl5dOqieqfNP3K
QQYvZ3H2YFP7ZZmIgrGjjDayKxWXcQRhOpdORy2m6vtw3b2AsLwXe0kcYjaxRWk70DClWs35S4cR
V60e3uF3Fb25h3QsknxM/r/AaQh8AVpnGVlSfv07Z4cSV+KHWJUiJNlctwR7WsEm3OFQ1EdaA6ba
9CUMniwKmKAYWrnD5dJG+IRAyRBlG/DUJCZvflBL8L9PfqiDMhEcO4B2ShJqJQ5j9LZ0ungeTC84
6D60AOloeStt2Z2eMoathKcmKCbHDXikm6DEv9VvYR5VyCkB9VWy3subg849Ejz7AgMBAAGjggHE
MIIBwDBIBgNVHR8EQTA/MD2gO6A5hjdodHRwOi8vY3JsLnRydXN0LnRlbGlhLmNvbS9lcmljc3Nv
bm5saW5kaXZpZHVhbGNhdjMuY3JsMIGCBggrBgEFBQcBAQR2MHQwKAYIKwYBBQUHMAGGHGh0dHA6
Ly9vY3NwMi50cnVzdC50ZWxpYS5jb20wSAYIKwYBBQUHMAKGPGh0dHA6Ly9jYS50cnVzdC50ZWxp
YXNvbmVyYS5jb20vZXJpY3Nzb25ubGluZGl2aWR1YWxjYXYzLmNlcjApBgNVHREEIjAggR5tYWdu
dXMud2VzdGVybHVuZEBlcmljc3Nvbi5jb20wVQYDVR0gBE4wTDBKBgwrBgEEAYIPAgMBARIwOjA4
BggrBgEFBQcCARYsaHR0cHM6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhc29uZXJhLmNvbS9DUFMw
HQYDVR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMCMB0GA1UdDgQWBBTmK+6GlTnVbhSEEMFbB/xe
xTzftjAfBgNVHSMEGDAWgBQcexmel5x2rCA92NzjkWrj2y2mUzAOBgNVHQ8BAf8EBAMCBaAwDQYJ
KoZIhvcNAQELBQADggIBAGfQUq6SDTRQ39z8RKnFIhphOux3yWIccy7msuk4E05pykY0EwY2BQMO
3hCKGGhBHdy+FhcKsAzn01O/DQc2WCodmgR5VjtickliclcMItR+QrkOfbwTdCvPKSQXqCJQ5cPI
X2aFZhtICQnLHRiPRdzx6ffBg3KgVgSqOUq1mt1XSlyAXMR5dUtLwNavNLLv4p9S0M4SIzoffM7e
eyr74oGaw6JIqRafihgRFmDkoSUQAeKz1q/7cohoQ+c4C3xBFZGkV8Znh3z0XXqoW8SW6nmfuXzr
gWrGcLZ+uIOjiEtBjoQ1o5pgiKFeFuXZRjEAYOTz1omb9LmljKrvDOb4orchxSXrSuZzxImW3pBc
rDTBcQ4TUy5tq5goyxp3azyMP6sSRen5qBNGX6x7NZpHEcGnG5QoN3oyHAOKDdJmLWo/sP8OzhX4
ksiONQlzbmX228wYL36WojQ/68wjdnKui7Q019vnm4tBqrXw77sFnwq/uO8V3FjJSBvFDRI8SLKH
KVwscCYl4sJBqJkeYJEQGQIspJ/Q7iUTZOtXN04PfzCPO5DbtTdR11UIP0RDe0XujoRWGnEklSUH
rF7/ZRbDLhmVrvV0otSFqR1Ws3lpvPGoVa/M4BP2cFrYfNhUG2lty7ooaHvZgn4zv19r2IiRxAKB
SfDeAgB5Z3/+fhhtjZCEMIIGwjCCBKqgAwIBAgIQU7h+g+GcmSiTsJtJHOy46zANBgkqhkiG9w0B
AQsFADA3MRQwEgYDVQQKDAtUZWxpYVNvbmVyYTEfMB0GA1UEAwwWVGVsaWFTb25lcmEgUm9vdCBD
QSB2MTAeFw0xNTEwMjcxMjE2NDZaFw0yNTEwMjcxMjE2NDZaMEcxCzAJBgNVBAYTAlNFMREwDwYD
VQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MzCCAiIw
DQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBAOzy3wAAuFDyp7vYVLfGk/fjwao71MNGNLSzzl5D
tjQtMtl2ZLPZyX6ViqzTN9JOb7uZ6KxuGSpReQvt8XOh7iIhkKH9W5hRpbjTsJmUMJd6zifhOpNK
6iSU3q44+FjsQL1lVtcguUuFG6aZN0N3GFVbgt6jRrASF8t/3wy9bHPAIfMyPybpg6Y2PH5/1Nwk
TepoDSmK69LGV+lV2IK6U9OWayZXZFIFIDCoGyFlhFxAEgN+qZ2+Rqg/0TM0oCHvKO2ELSGmAdnJ
kwizR42ji/Y9SYTSuG75mzSe6OfCGWM8Db/xvy/20aLEPXNu1PvOgzY63WZ6cmkWnjMlVJ90pWC2
haqDm3Yf8TRdjUvAl7Pz1bTuexwShzIGakL7MkCYrEqHMRaojI/VStloQgW76E76zQ2byw5QxrhO
UbisBSKRzlTlOZQgYFFAbG6ViF8DOpJh/ygtQwuTLUM5r15G7eynQV1AMTNCWcX+HUvgArUw6RfW
9L58uA68GjktFTV8s9RlDsUqsNcLqeXaV28S2WMday0YGaq/bloS8AD7KuumUKH+Ri9IGO9mJvP0
5tvDHjKpLvv80c3WLJnJU/aznYHYEt2+jjKHOTqdGTxL/zMdpRSQFSuu+KM8NoYrkU1VJqKga+QL
sgqKghMp99gu1P1e6KsqseWHdXORrMbjqkBXAgMBAAGjggG4MIIBtDCBigYIKwYBBQUHAQEEfjB8
MC0GCCsGAQUFBzABhiFodHRwOi8vb2NzcC50cnVzdC50ZWxpYXNvbmVyYS5jb20wSwYIKwYBBQUH
MAKGP2h0dHA6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhc29uZXJhLmNvbS90ZWxpYXNvbmVyYXJv
b3RjYXYxLmNlcjASBgNVHRMBAf8ECDAGAQH/AgEAMFUGA1UdIAROMEwwSgYMKwYBBAGCDwIDAQEC
MDowOAYIKwYBBQUHAgEWLGh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYXNvbmVyYS5jb20v
Q1BTMEsGA1UdHwREMEIwQKA+oDyGOmh0dHA6Ly9jcmwtMy50cnVzdC50ZWxpYXNvbmVyYS5jb20v
dGVsaWFzb25lcmFyb290Y2F2MS5jcmwwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMA4G
A1UdDwEB/wQEAwIBBjAdBgNVHQ4EFgQUHHsZnpecdqwgPdjc45Fq49stplMwHwYDVR0jBBgwFoAU
8I9ZOACz9Y+algzV6/p7qhfoExIwDQYJKoZIhvcNAQELBQADggIBAFBYa/HVjDu0LqtXQ8iMp8PL
Fpqchf41ksQY6R1AsoZbaBUu0NQlAQ9GzlC1pmI5s0cJnuaZI0xV6TiWS3/R2p9UgW61XD9CTIUb
AL31mY3BdJf3P46gzKgQEca/DlFjq9GVmuPS4q90BLNgvgoxoHubc3C6s0OaY1sbnay5EhnvrAE4
Q511FlxmJPLnRmQGpieeXa3cPegFfY1kJDKyyFRypF1RuRLXcdMIgKEy5NX1bS3M9dQ4mgmUmVT2
d33UiKSEYQ6s/B+LFaaz4LywXSv2o3W4kbHoQs86IWst821ww0wxsCpEfClIvF7fBw2QkbG/1Pwu
zAuLVStEhDzkAqOrMGctKyNEaBsyAn7Eq2eCa8QDXnkmagp9QPsNFs/oqnXj9j1cVtH9a4OPzhtg
0pd7gd0NzU/5QxibXqbYvouQgihGXHQDmaL4ruN7C4arMUqRo82YnREsKL7h3j/jtmzcMLc9Q07F
04QQd/iSR1Y5pIi6PdNBiE2/4uyAXS6KOIGZrPbNQUNrZtwiQpqQNl8AUzgegfPwrYFlFocpaF3d
1m5r+2VKKqiRQVfYPGYeZnWfkcz06JoAhc/9mjbHXSP9hvWYzeLRuoZqHGUdjOX9DIQb926OneV7
C5WMIjSY8ORkamG/HKqngmjypL3gSc6oG/E6B+1i6Ds5j0Qpj5aQMYICzTCCAskCAQEwWzBHMQsw
CQYDVQQGEwJTRTERMA8GA1UECgwIRXJpY3Nzb24xJTAjBgNVBAMMHEVyaWNzc29uIE5MIEluZGl2
aWR1YWwgQ0EgdjMCEAtGbc1we24wZa62a3lxee0wDQYJYIZIAWUDBAIBBQCgggFDMBgGCSqGSIb3
DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTIwMDMyMzE0NTQyMlowLwYJKoZIhvcN
AQkEMSIEIKjtMjL4pmySpoTMbQgzV9zV3yPx06dOHitM4CL5amhqMGoGCSsGAQQBgjcQBDFdMFsw
RzELMAkGA1UEBhMCU0UxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQDDBxFcmljc3NvbiBOTCBJ
bmRpdmlkdWFsIENBIHYzAhALRm3NcHtuMGWutmt5cXntMGwGCyqGSIb3DQEJEAILMV2gWzBHMQsw
CQYDVQQGEwJTRTERMA8GA1UECgwIRXJpY3Nzb24xJTAjBgNVBAMMHEVyaWNzc29uIE5MIEluZGl2
aWR1YWwgQ0EgdjMCEAtGbc1we24wZa62a3lxee0wDQYJKoZIhvcNAQEBBQAEggEAbQdc/xE8wxC5
zQa96ddJsV5vvZLahLhDbZ9uMhHg3c5XLxl7+WhIJeJS/welu9jU5gly9TZn1+cpBkslJMfI8RgC
7okDEW54zDDowZ8q8UEHmtT2E2qIuok7Te2ukrWvQUvEaUp0unLVDSQJHZm8m2wUagduCQwjJalf
XLaChEjayV4W1SnlMsT/DF5ekPlozF1ieNzDEAYfR7SEnZlX2GBF9uxLHB3EDdJBsbfFfYI6LIQl
pefYofj4DbpjzrSgJA2MU4N/MFn6tsXhZWGSunE1cQpdmWVOJUN4OMW5przhUBee2oTzWx26YYb/
dm2y/3TjOAiYVUmWJFHKE0KCVwAAAAAAAA==


--=-EmN6RepnkEMbFhqazMaQ--


From nobody Mon Mar 23 08:16:00 2020
Return-Path: <aaron.falk@gmail.com>
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 44BF03A0767 for <taps@ietfa.amsl.com>; Mon, 23 Mar 2020 08:15:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 bbuIKht2jA-7 for <taps@ietfa.amsl.com>; Mon, 23 Mar 2020 08:15:48 -0700 (PDT)
Received: from mail-qk1-x733.google.com (mail-qk1-x733.google.com [IPv6:2607:f8b0:4864:20::733]) (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 0A1C83A074E for <taps@ietf.org>; Mon, 23 Mar 2020 08:15:47 -0700 (PDT)
Received: by mail-qk1-x733.google.com with SMTP id v7so6002599qkc.0 for <taps@ietf.org>; Mon, 23 Mar 2020 08:15:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=gLTGzBl9XLHuAd4Rm9/a/JKhT9nQ06+3sEkWwbwL45k=; b=XohgY5N467Yg1NqtyPhsP9j4idXhAo4SCeCORHIGBzbvFX2ba7qLrKvG47IUEIi5Vu ZLtV4VMgUZ+Se/KYuLN8IITXde3M2By+rAzizM4C4UqorzICU/7ivfBF7VotP1YLgHAl P8MONQAMcyQtPzrZu1Zq6pDMMl4XlFw5Qoi2t2QkFd3Wn65HY5hrQ0D/NRIhHO3LJh+Q gaf1potiVR7aSfLB0U6Ma3E7+rivZ6kCldczs/fbJEyiLuRUAQ35cViwh7A7dy09p9I9 b598DQcXMqR7z/cTalsS9KmDkvZQbl+2OtWgPd4VVYoJmy/Mww6xlaOb7fhrusbssitE X7gg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=gLTGzBl9XLHuAd4Rm9/a/JKhT9nQ06+3sEkWwbwL45k=; b=Mw6KW7+m+LpeZNIXUHxQs7ViXVjwQce9P130+GkPKUHSXnyJ1BFNXmSeoToi3GLzUH koCdIqMnI03UAasNINLarljYnW1XeserAc4mBTuFCHvSX8ABJanQnJLWJ0s+cGXE4JjK xBHN0uJbvMyNDK4DswI+UUYQNdT2XL2zcjGB5kopkA5/PsACd8ZjCtwEEfu7n8sqN8bq be19Ohm7ktu2Td+SPpoarvCijNfoAuzxBzfMeP1sJ+GRgVze9cxMmZ8stAFYmuk6vhqD bRnPBkeoxFiLXAvszF5GVHRxmJOATBbAmfNhadRb8arSMYUEMUsGneCfw2A2IrQhgKK9 i6Iw==
X-Gm-Message-State: ANhLgQ3GtYxaVTcmsKvLVEjZ7dvuRltSdq7x498iPuXr6OkiySQzfyd+ 3B46fXofSszroA5IhS9ce1Y=
X-Google-Smtp-Source: ADFU+vsfR8arPcXN4qDZdWbcXVKoCkdyFSBFTAM/C4YISfm5/e5IDT4ezQ+HzRAhG1qm/cWHL01Knw==
X-Received: by 2002:a05:620a:391:: with SMTP id q17mr8182634qkm.103.1584976546715;  Mon, 23 Mar 2020 08:15:46 -0700 (PDT)
Received: from [172.19.115.248] ([2601:184:4881:2420:f9cf:ce5d:57d7:9b29]) by smtp.gmail.com with ESMTPSA id x14sm3477973qkj.66.2020.03.23.08.15.45 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 23 Mar 2020 08:15:45 -0700 (PDT)
From: "Aaron Falk" <aaron.falk@gmail.com>
To: "Magnus Westerlund" <magnus.westerlund@ericsson.com>
Cc: taps@ietf.org, "Zaheduzzaman Sarker" <zaheduzzaman.sarker@ericsson.com>
Date: Mon, 23 Mar 2020 11:15:42 -0400
X-Mailer: MailMate (1.13.1r5671)
Message-ID: <350953BF-B45A-49EF-9AAD-369A6347A04B@gmail.com>
In-Reply-To: <7cfeb3b3682826b7cbc0033d4bf691808f8e9bd2.camel@ericsson.com>
References: <18805F34-42FE-42D8-AE3D-5D9AE2111A9A@gmail.com> <E4EBDD29-A18D-4B07-BA1A-F4D563A5EC08@gmail.com> <81D5CFCB-634F-41E0-AC22-D7BAFCC34D33@gmail.com> <7cfeb3b3682826b7cbc0033d4bf691808f8e9bd2.camel@ericsson.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_7E4BBD82-9C31-4F83-832C-DC520797634D_="
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/l7YIKCKfco45vaxkIFRaazgApis>
Subject: Re: [Taps] TAPS April Interim Scheduling
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: Mon, 23 Mar 2020 15:15:58 -0000

--=_MailMate_7E4BBD82-9C31-4F83-832C-DC520797634D_=
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 8bit

Thanks, Magnus.  Just to confirm (since I’ve been mistaken in the 
past): will the timing below work without conflicting with the IESG 
meeting?
--aaron



**CEST/CET, Central European Summer**

6:00p	Fri, Apr 17 2020

8:00p	Fri, Apr 17 2020


**UTC, Coordinated Universal Time**

4:00p	Fri, Apr 17 2020

6:00p	Fri, Apr 17 2020


**EDT/EST, Eastern Daylight Time (US)**

12:00p	Fri, Apr 17 2020

2:00p	Fri, Apr 17 2020


**PDT/PST, Pacific Daylight Time (US)**

9:00a	Fri, Apr 17 2020

11:00a	Fri, Apr 17 2020


On 23 Mar 2020, at 10:54, Magnus Westerlund wrote:

> Hi,
>
> Actually the IESG meeting will have end at 16:00 UTC on the 17th of 
> April, it is
> 16:00-18:00 CEST. The TAPS meeting scheduled is 19:00-21:00 CEST. It 
> would work
> for me, but so you have the right information.
>
> Cheers
>
> Magnus
>
> On Fri, 2020-03-20 at 14:49 -0400, Aaron Falk wrote:
>> The IESG call runs until 5pm UTC which conflicts with Mirja and 
>> Magnus. So,
>> I’d like to propose we adjust the time to fit. Also, the times I 
>> pasted into
>> the Doodle are messed up because of daylight savings in the US. To 
>> get it
>> right, I consulted this site. Bottom line: If you cannot attend on 
>> April 17 if
>> we run the call from the times below please speak up.
>> UTC	EDT	PDT
>> 5:00p - 7:00p	1:00p - 3:00p	10:00a - 12:00p
>> Webex link: https://ietf.webex.com/meet/taps
>> Sorry for the confusion!
>> --aaron
>> On 19 Mar 2020, at 15:26, Aaron Falk wrote:
>>> Looks like everyone responding can make April 17, 11am - 1pm EDT / 
>>> 8am -
>>> 10am PDT / 4pm - 6pm UTC. If you cannot, please complete the doodle 
>>> poll
>>> ASAP.
>>> Thanks,
>>> --aaron
>>> On 17 Mar 2020, at 10:59, Aaron Falk wrote:
>>>> Doodle to select meeting date for April interim. We’ve had good 
>>>> luck with
>>>> Fridays 11am EDT so please vote. (Preference given to authors.) 
>>>> Date will
>>>> be selected at the end of this week.
>>>> https://doodle.com/poll/7b6p6a9twgrtf7ib
>>>> --aaron
> -- 
> Cheers
>
> Magnus Westerlund
>
>
> ----------------------------------------------------------------------
> Networks, Ericsson Research
> ----------------------------------------------------------------------
> Ericsson AB                 | Phone  +46 10 7148287
> Torshamnsgatan 23           | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------

--=_MailMate_7E4BBD82-9C31-4F83-832C-DC520797634D_=
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html>
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">Thanks, Magnus.  Just to confirm (since I=E2=80=99ve been=
 mistaken in the past): will the timing below work without conflicting wi=
th the IESG meeting?<br>
--aaron</p>

<p dir=3D"auto"><strong>CEST/CET, Central European Summer</strong></p>

<p dir=3D"auto">6:00p    Fri, Apr 17 2020</p>

<p dir=3D"auto">8:00p    Fri, Apr 17 2020</p>

<p dir=3D"auto"><strong>UTC, Coordinated Universal Time</strong></p>

<p dir=3D"auto">4:00p    Fri, Apr 17 2020</p>

<p dir=3D"auto">6:00p    Fri, Apr 17 2020</p>

<p dir=3D"auto"><strong>EDT/EST, Eastern Daylight Time (US)</strong></p>

<p dir=3D"auto">12:00p    Fri, Apr 17 2020</p>

<p dir=3D"auto">2:00p    Fri, Apr 17 2020</p>

<p dir=3D"auto"><strong>PDT/PST, Pacific Daylight Time (US)</strong></p>

<p dir=3D"auto">9:00a    Fri, Apr 17 2020</p>

<p dir=3D"auto">11:00a    Fri, Apr 17 2020</p>

<p dir=3D"auto">On 23 Mar 2020, at 10:54, Magnus Westerlund wrote:</p>

</div>
<div style=3D"white-space:normal"><blockquote style=3D"border-left:2px so=
lid #777; color:#777; margin:0 0 5px; padding-left:5px"><p dir=3D"auto">H=
i,<br>
<br>
Actually the IESG meeting will have end at 16:00 UTC on the 17th of April=
, it is<br>
16:00-18:00 CEST. The TAPS meeting scheduled is 19:00-21:00 CEST. It woul=
d work<br>
for me, but so you have the right information.<br>
<br>
Cheers<br>
<br>
Magnus<br>
<br>
On Fri, 2020-03-20 at 14:49 -0400, Aaron Falk wrote:</p>
<blockquote style=3D"border-left:2px solid #777; color:#999; margin:0 0 5=
px; padding-left:5px; border-left-color:#999"><p dir=3D"auto">The IESG ca=
ll runs until 5pm UTC which conflicts with Mirja and Magnus. So,<br>
I=E2=80=99d like to propose we adjust the time to fit. Also, the times I =
pasted into<br>
the Doodle are messed up because of daylight savings in the US. To get it=
<br>
right, I consulted this site. Bottom line: If you cannot attend on April =
17 if<br>
we run the call from the times below please speak up.<br>
UTC	EDT	PDT<br>
5:00p - 7:00p	1:00p - 3:00p	10:00a - 12:00p<br>
Webex link: <a href=3D"https://ietf.webex.com/meet/taps" style=3D"color:#=
999">https://ietf.webex.com/meet/taps</a><br>
Sorry for the confusion!<br>
--aaron<br>
On 19 Mar 2020, at 15:26, Aaron Falk wrote:</p>
<blockquote style=3D"border-left:2px solid #777; color:#BBB; margin:0 0 5=
px; padding-left:5px; border-left-color:#BBB"><p dir=3D"auto">Looks like =
everyone responding can make April 17, 11am - 1pm EDT / 8am -<br>
10am PDT / 4pm - 6pm UTC. If you cannot, please complete the doodle poll<=
br>
ASAP.<br>
Thanks,<br>
--aaron<br>
On 17 Mar 2020, at 10:59, Aaron Falk wrote:</p>
<blockquote style=3D"border-left:2px solid #777; color:#BBB; margin:0 0 5=
px; padding-left:5px; border-left-color:#BBB"><p dir=3D"auto">Doodle to s=
elect meeting date for April interim. We=E2=80=99ve had good luck with<br=
>
Fridays 11am EDT so please vote. (Preference given to authors.) Date will=
<br>
be selected at the end of this week.<br>
<a href=3D"https://doodle.com/poll/7b6p6a9twgrtf7ib" style=3D"color:#BBB"=
>https://doodle.com/poll/7b6p6a9twgrtf7ib</a><br>
--aaron</p>
</blockquote></blockquote></blockquote><p dir=3D"auto">-- <br>
Cheers<br>
<br>
Magnus Westerlund<br>
<br>
<br>
----------------------------------------------------------------------<br=
>
Networks, Ericsson Research<br>
----------------------------------------------------------------------<br=
>
Ericsson AB                 | Phone  +46 10 7148287<br>
Torshamnsgatan 23           | Mobile +46 73 0949079<br>
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com<br>
----------------------------------------------------------------------</p=
>
</blockquote></div>
<div style=3D"white-space:normal">
</div>
</div>
</body>
</html>

--=_MailMate_7E4BBD82-9C31-4F83-832C-DC520797634D_=--


From nobody Tue Mar 24 07:39:32 2020
Return-Path: <magnus.westerlund@ericsson.com>
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 5ADB43A0840 for <taps@ietfa.amsl.com>; Tue, 24 Mar 2020 07:39:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.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 xWjtsbagQtVo for <taps@ietfa.amsl.com>; Tue, 24 Mar 2020 07:39:28 -0700 (PDT)
Received: from EUR02-VE1-obe.outbound.protection.outlook.com (mail-eopbgr20042.outbound.protection.outlook.com [40.107.2.42]) (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 B4A593A03FA for <taps@ietf.org>; Tue, 24 Mar 2020 07:39:25 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=fCjq7nc7E/VyPr6GhXHu1xyMx9Hh8I82uvVifmA4LZFP06dd/XP7fWuomNp/QB+E2nUoNpHTxeKjZ9IqoS3OIVdKK89HRipOqI6dDnmjITkXMq+KT8MDCjY5e1+JaaTTzr4d/9qeVRq/QenX/AYs3mcMkgXd9JtmD74SkKj9yvStdRFy3sgBVNZEVuDavT8o9tsU14RUoff1yXvUi2hH1mrioiiJuD+uHweAb21YR/aoQsa0R29dX+Qk/MYWmusfNwjP9MG0fVIpIpVVJiIQLho9omCI3+nkNxj0A3QMXTaAz2ObQ2KVCL5HIqbkzNZLv+3MAf1HrywSItU4QXSA+Q==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=iOod+Umdabktd/MA89CxHZIwnT+PeKgzYlhVW4dwyew=; b=GGaTSeZ1UEJYs29msoi62I5+qEnLovLpMxDTU9UQBe5WLuP7QUy1c6DUA6xGHw9kJcAcCqU7ljtAMTR9IIiPAH/ZTOqQcpfXaAMEV6Aeblx0E5oM1tIaSifWYLljPb6vi3TNBSgW0JL1yuISNrvjl1OMd9Ev6WTsBf9unJeqgND8gT7Ke3HO7kncJJ3YOC9rU7Kx4vhFS+D5JgfCj0anLOZwgHRtAgatDi/IKTui2WXKAS/w7V0d9jv3LO5SlAxYW3YOw0ZBz3rAZbL7oCAUkEodytyYsbamhcoPI4LsLf1DDavv2/Oc0KahoPaoFxq+6K3U2+GkSQU3LEs+box4PA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=iOod+Umdabktd/MA89CxHZIwnT+PeKgzYlhVW4dwyew=; b=u/PXGsNDgkjGFMkPPF5GRaxViOYAqzkISr+3QrFF8KQR9EilOIxteH9Q6bRkuW2ddP/zLYi4jnlfd50L2aSdpXAXhrRvbwOSivpGHQ/nH+71IGSTc5PHZjfzlF2oygy/Xn5N0X26xMgC9GPdXgH/8TQsGpbVsW7hVpEwz7uTmuQ=
Received: from HE1PR0702MB3772.eurprd07.prod.outlook.com (52.133.7.14) by HE1PR0702MB3580.eurprd07.prod.outlook.com (52.133.6.15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2856.15; Tue, 24 Mar 2020 14:39:22 +0000
Received: from HE1PR0702MB3772.eurprd07.prod.outlook.com ([fe80::8bd:85b0:d547:9eed]) by HE1PR0702MB3772.eurprd07.prod.outlook.com ([fe80::8bd:85b0:d547:9eed%6]) with mapi id 15.20.2835.021; Tue, 24 Mar 2020 14:39:22 +0000
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
To: "aaron.falk@gmail.com" <aaron.falk@gmail.com>
CC: "taps@ietf.org" <taps@ietf.org>, Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
Thread-Topic: [Taps] TAPS April Interim Scheduling
Thread-Index: AQHV/Gyu/7URO11Q0EWkwvtCTA2L5KhQT9uAgAGHxwCABHVkAIAABfYAgAGILYA=
Date: Tue, 24 Mar 2020 14:39:22 +0000
Message-ID: <a6b425f24c488ac240f7bebb17eae8d07427778b.camel@ericsson.com>
References: <18805F34-42FE-42D8-AE3D-5D9AE2111A9A@gmail.com> <E4EBDD29-A18D-4B07-BA1A-F4D563A5EC08@gmail.com> <81D5CFCB-634F-41E0-AC22-D7BAFCC34D33@gmail.com> <7cfeb3b3682826b7cbc0033d4bf691808f8e9bd2.camel@ericsson.com> <350953BF-B45A-49EF-9AAD-369A6347A04B@gmail.com>
In-Reply-To: <350953BF-B45A-49EF-9AAD-369A6347A04B@gmail.com>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Evolution 3.28.5-0ubuntu0.18.04.1 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=magnus.westerlund@ericsson.com; 
x-originating-ip: [158.174.118.23]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 7466edef-9cba-4bba-3364-08d7d00124d9
x-ms-traffictypediagnostic: HE1PR0702MB3580:|HE1PR0702MB3580:
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <HE1PR0702MB3580578F3B10BC43C88334DF95F10@HE1PR0702MB3580.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:7219;
x-forefront-prvs: 03524FBD26
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(366004)(86362001)(107886003)(8676002)(2906002)(66476007)(36756003)(6916009)(4326008)(2616005)(44832011)(5660300002)(66446008)(498600001)(81156014)(186003)(66556008)(76116006)(8936002)(53546011)(6512007)(71200400001)(66616009)(81166006)(54906003)(6506007)(6486002)(66946007)(966005)(26005)(64756008)(99106002); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR0702MB3580; H:HE1PR0702MB3772.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: Kq6N9t7YLSWTLjxJG4q1JTrHQSE3ho4nEOZ7E5J5T8Ffkyztck7ddp61S8Pg2fVKWAFFBKfaB5RVg3QgCNC176wfq8Z++u826YvHFsIIUTkCRGWN9iwkVlenS8WkN67HTAw7Vv3eTD3MigPHggb26Oz0+mdrHfKJyjG2aSNvyr1nOTmPu0QtIlUKKi7c3ySd/nS9sBqs3dufunsjeLlEGzCz0McffQcrerb9O5gK1FxaqrSGv2O7JH43K1otAJZ2AmkJ2n3+xEA0CcondDgzi3lorqMJkTEbn09ELdrh6GrTnK3Hj8P+NeE1hlvgwRqmXG6wMdXsMr1cUNTlRvp+DRTB5s9vL9F68vNBeklfogzu/rHAdwEKl6itD2y5ND/g0VKpUq5XV2sfpV5Wo8pJi5VO1peWxv7HevjoM9CzOA5FBvEicB3zEBCWn15qXCMeS/oj6QVCngeSGdPGpiaqVfvEj24jCGwrRU54hYRJc2emP/3PiGZif9UlixzTOmENHCHk2rwpWtxozD4biTweFDLTr6SgogS7DjXaUQ0sZ7r8YZYXBtRK+r2NxM0BzCFc
x-ms-exchange-antispam-messagedata: 4LgDmHtGmZnqT7lkJRQXbgLUPZivkGV60GYDi7PxlyApRKKfFBoh6XAa6QPCx2X3IhPmSz4QNoXKjCGg/4V/Omrr09hwA9tqOxxFEeDhnoUcK0lAc58ebSFeGE8Ox/TpWGL5rswCmoW+cyz3UcjjoQ==
Content-Type: multipart/signed; micalg="sha-256"; protocol="application/x-pkcs7-signature"; boundary="=-ghOuTrUYuw70WnDwyyhh"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 7466edef-9cba-4bba-3364-08d7d00124d9
X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Mar 2020 14:39:22.6904 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 2g7JuySz10T3PpQh6Vo5XlPHAz++gYdZrFjsO7yhUC6tnA8s2E6Bh/wp0r9zL1fR4SbhmR8NNf6uVWuwLa7FB3aLREPSpovC6UGJYxF6JrI=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0702MB3580
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/GftAEbAirEP9-EuF2blgOOtK5bQ>
Subject: Re: [Taps] TAPS April Interim Scheduling
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, 24 Mar 2020 14:39:31 -0000

--=-ghOuTrUYuw70WnDwyyhh
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi,

Yes, that will not collide with the IESG meeting.=20

/Magnus

On Mon, 2020-03-23 at 11:15 -0400, Aaron Falk wrote:
> Thanks, Magnus. Just to confirm (since I=E2=80=99ve been mistaken in the =
past): will
> the timing below work without conflicting with the IESG meeting?
> --aaron
> CEST/CET, Central European Summer
> 6:00p Fri, Apr 17 2020
> 8:00p Fri, Apr 17 2020
> UTC, Coordinated Universal Time
> 4:00p Fri, Apr 17 2020
> 6:00p Fri, Apr 17 2020
> EDT/EST, Eastern Daylight Time (US)
> 12:00p Fri, Apr 17 2020
> 2:00p Fri, Apr 17 2020
> PDT/PST, Pacific Daylight Time (US)
> 9:00a Fri, Apr 17 2020
> 11:00a Fri, Apr 17 2020
> On 23 Mar 2020, at 10:54, Magnus Westerlund wrote:
> > Hi,
> >=20
> > Actually the IESG meeting will have end at 16:00 UTC on the 17th of Apr=
il,
> > it is
> > 16:00-18:00 CEST. The TAPS meeting scheduled is 19:00-21:00 CEST. It wo=
uld
> > work
> > for me, but so you have the right information.
> >=20
> > Cheers
> >=20
> > Magnus
> >=20
> > On Fri, 2020-03-20 at 14:49 -0400, Aaron Falk wrote:
> > > The IESG call runs until 5pm UTC which conflicts with Mirja and Magnu=
s.
> > > So,
> > > I=E2=80=99d like to propose we adjust the time to fit. Also, the time=
s I pasted
> > > into
> > > the Doodle are messed up because of daylight savings in the US. To ge=
t it
> > > right, I consulted this site. Bottom line: If you cannot attend on Ap=
ril
> > > 17 if
> > > we run the call from the times below please speak up.
> > > UTC	EDT	PDT
> > > 5:00p - 7:00p	1:00p - 3:00p	10:00a - 12:00p
> > > Webex link: https://ietf.webex.com/meet/taps
> > > Sorry for the confusion!
> > > --aaron
> > > On 19 Mar 2020, at 15:26, Aaron Falk wrote:
> > > > Looks like everyone responding can make April 17, 11am - 1pm EDT / =
8am -
> > > > 10am PDT / 4pm - 6pm UTC. If you cannot, please complete the doodle=
 poll
> > > > ASAP.
> > > > Thanks,
> > > > --aaron
> > > > On 17 Mar 2020, at 10:59, Aaron Falk wrote:
> > > > > Doodle to select meeting date for April interim. We=E2=80=99ve ha=
d good luck
> > > > > with
> > > > > Fridays 11am EDT so please vote. (Preference given to authors.) D=
ate
> > > > > will
> > > > > be selected at the end of this week.
> > > > > https://doodle.com/poll/7b6p6a9twgrtf7ib
> > > > > --aaron
> >=20
> > --=20
> > Cheers
> >=20
> > Magnus Westerlund
> >=20
> >=20
> > ----------------------------------------------------------------------
> > Networks, Ericsson Research
> > ----------------------------------------------------------------------
> > Ericsson AB | Phone +46 10 7148287
> > Torshamnsgatan 23 | Mobile +46 73 0949079
> > SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> > ----------------------------------------------------------------------
--=20
Cheers

Magnus Westerlund=20


----------------------------------------------------------------------
Networks, Ericsson Research
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Torshamnsgatan 23           | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------



--=-ghOuTrUYuw70WnDwyyhh
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCCEtww
ggYHMIID76ADAgECAhALRm3NcHtuMGWutmt5cXntMA0GCSqGSIb3DQEBCwUAMEcxCzAJBgNVBAYT
AlNFMREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBD
QSB2MzAeFw0xNzEyMTUwNzIyMjNaFw0yMDEyMTUwNzIyMjJaMHAxETAPBgNVBAoMCEVyaWNzc29u
MRowGAYDVQQDDBFNYWdudXMgV2VzdGVybHVuZDEtMCsGCSqGSIb3DQEJARYebWFnbnVzLndlc3Rl
cmx1bmRAZXJpY3Nzb24uY29tMRAwDgYDVQQFEwdlcmFtc3dkMIIBIjANBgkqhkiG9w0BAQEFAAOC
AQ8AMIIBCgKCAQEAsKlHZvB3TsmLEDtPSiFFKAh73S2wApt+laqg5eXTqonqnzT9ykEGL2dx9mBT
+2WZiIKxo4w2sisVl3EEYTqXTkctpur7cN29gLC8F3tJHGI2sUVpO9AwpVrN+UuHEVetHt7hdxW9
uYd0LJJ8TP6/wGkIfAFaZxlZUn79O2eHElfih1iVIiTZXLcEe1rBJtzhUNRHWgOm2vQlDJ4sCpig
GFq5w+XSRviEQMkQZRvw1CQmb35QS/C/T36ogzIRHDuAdkoSaiUOY/S2dLp4HkwvOOg+tADpaHkr
bdmdnjKGrYSnJigmxw14pJugxL/Vb2EeVcgpAfVVst7Lm4POPRI8+wIDAQABo4IBxDCCAcAwSAYD
VR0fBEEwPzA9oDugOYY3aHR0cDovL2NybC50cnVzdC50ZWxpYS5jb20vZXJpY3Nzb25ubGluZGl2
aWR1YWxjYXYzLmNybDCBggYIKwYBBQUHAQEEdjB0MCgGCCsGAQUFBzABhhxodHRwOi8vb2NzcDIu
dHJ1c3QudGVsaWEuY29tMEgGCCsGAQUFBzAChjxodHRwOi8vY2EudHJ1c3QudGVsaWFzb25lcmEu
Y29tL2VyaWNzc29ubmxpbmRpdmlkdWFsY2F2My5jZXIwKQYDVR0RBCIwIIEebWFnbnVzLndlc3Rl
cmx1bmRAZXJpY3Nzb24uY29tMFUGA1UdIAROMEwwSgYMKwYBBAGCDwIDAQESMDowOAYIKwYBBQUH
AgEWLGh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYXNvbmVyYS5jb20vQ1BTMB0GA1UdJQQW
MBQGCCsGAQUFBwMEBggrBgEFBQcDAjAdBgNVHQ4EFgQU5ivuhpU51W4UhBDBWwf8XsU837YwHwYD
VR0jBBgwFoAUHHsZnpecdqwgPdjc45Fq49stplMwDgYDVR0PAQH/BAQDAgWgMA0GCSqGSIb3DQEB
CwUAA4ICAQBn0FKukg00UN/c/ESpxSIaYTrsd8liHHMu5rLpOBNOacpGNBMGNgUDDt4QihhoQR3c
vhYXCrAM59NTvw0HNlgqHZoEeVY7YnJJYnJXDCLUfkK5Dn28E3QrzykkF6giUOXDyF9mhWYbSAkJ
yx0Yj0Xc8en3wYNyoFYEqjlKtZrdV0pcgFzEeXVLS8DWrzSy7+KfUtDOEiM6H3zO3nsq++KBmsOi
SKkWn4oYERZg5KElEAHis9av+3KIaEPnOAt8QRWRpFfGZ4d89F16qFvElup5n7l864FqxnC2friD
o4hLQY6ENaOaYIihXhbl2UYxAGDk89aJm/S5pYyq7wzm+KK3IcUl60rmc8SJlt6QXKw0wXEOE1Mu
bauYKMsad2s8jD+rEkXp+agTRl+sezWaRxHBpxuUKDd6MhwDig3SZi1qP7D/Ds4V+JLIjjUJc25l
9tvMGC9+lqI0P+vMI3Zyrou0NNfb55uLQaq18O+7BZ8Kv7jvFdxYyUgbxQ0SPEiyhylcLHAmJeLC
QaiZHmCREBkCLKSf0O4lE2TrVzdOD38wjzuQ27U3UddVCD9EQ3tF7o6EVhpxJJUlB6xe/2UWwy4Z
la71dKLUhakdVrN5abzxqFWvzOAT9nBa2HzYVBtpbcu6KGh72YJ+M79fa9iIkcQCgUnw3gIAeWd/
/n4YbY2QhDCCBgcwggPvoAMCAQICEAtGbc1we24wZa62a3lxee0wDQYJKoZIhvcNAQELBQAwRzEL
MAkGA1UEBhMCU0UxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQDDBxFcmljc3NvbiBOTCBJbmRp
dmlkdWFsIENBIHYzMB4XDTE3MTIxNTA3MjIyM1oXDTIwMTIxNTA3MjIyMlowcDERMA8GA1UECgwI
RXJpY3Nzb24xGjAYBgNVBAMMEU1hZ251cyBXZXN0ZXJsdW5kMS0wKwYJKoZIhvcNAQkBFh5tYWdu
dXMud2VzdGVybHVuZEBlcmljc3Nvbi5jb20xEDAOBgNVBAUTB2VyYW1zd2QwggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQCwqUdm8HdOyYsQO09KIUUoCHvdLbACm36VqqDl5dOqieqfNP3K
QQYvZ3H2YFP7ZZmIgrGjjDayKxWXcQRhOpdORy2m6vtw3b2AsLwXe0kcYjaxRWk70DClWs35S4cR
V60e3uF3Fb25h3QsknxM/r/AaQh8AVpnGVlSfv07Z4cSV+KHWJUiJNlctwR7WsEm3OFQ1EdaA6ba
9CUMniwKmKAYWrnD5dJG+IRAyRBlG/DUJCZvflBL8L9PfqiDMhEcO4B2ShJqJQ5j9LZ0ungeTC84
6D60AOloeStt2Z2eMoathKcmKCbHDXikm6DEv9VvYR5VyCkB9VWy3subg849Ejz7AgMBAAGjggHE
MIIBwDBIBgNVHR8EQTA/MD2gO6A5hjdodHRwOi8vY3JsLnRydXN0LnRlbGlhLmNvbS9lcmljc3Nv
bm5saW5kaXZpZHVhbGNhdjMuY3JsMIGCBggrBgEFBQcBAQR2MHQwKAYIKwYBBQUHMAGGHGh0dHA6
Ly9vY3NwMi50cnVzdC50ZWxpYS5jb20wSAYIKwYBBQUHMAKGPGh0dHA6Ly9jYS50cnVzdC50ZWxp
YXNvbmVyYS5jb20vZXJpY3Nzb25ubGluZGl2aWR1YWxjYXYzLmNlcjApBgNVHREEIjAggR5tYWdu
dXMud2VzdGVybHVuZEBlcmljc3Nvbi5jb20wVQYDVR0gBE4wTDBKBgwrBgEEAYIPAgMBARIwOjA4
BggrBgEFBQcCARYsaHR0cHM6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhc29uZXJhLmNvbS9DUFMw
HQYDVR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMCMB0GA1UdDgQWBBTmK+6GlTnVbhSEEMFbB/xe
xTzftjAfBgNVHSMEGDAWgBQcexmel5x2rCA92NzjkWrj2y2mUzAOBgNVHQ8BAf8EBAMCBaAwDQYJ
KoZIhvcNAQELBQADggIBAGfQUq6SDTRQ39z8RKnFIhphOux3yWIccy7msuk4E05pykY0EwY2BQMO
3hCKGGhBHdy+FhcKsAzn01O/DQc2WCodmgR5VjtickliclcMItR+QrkOfbwTdCvPKSQXqCJQ5cPI
X2aFZhtICQnLHRiPRdzx6ffBg3KgVgSqOUq1mt1XSlyAXMR5dUtLwNavNLLv4p9S0M4SIzoffM7e
eyr74oGaw6JIqRafihgRFmDkoSUQAeKz1q/7cohoQ+c4C3xBFZGkV8Znh3z0XXqoW8SW6nmfuXzr
gWrGcLZ+uIOjiEtBjoQ1o5pgiKFeFuXZRjEAYOTz1omb9LmljKrvDOb4orchxSXrSuZzxImW3pBc
rDTBcQ4TUy5tq5goyxp3azyMP6sSRen5qBNGX6x7NZpHEcGnG5QoN3oyHAOKDdJmLWo/sP8OzhX4
ksiONQlzbmX228wYL36WojQ/68wjdnKui7Q019vnm4tBqrXw77sFnwq/uO8V3FjJSBvFDRI8SLKH
KVwscCYl4sJBqJkeYJEQGQIspJ/Q7iUTZOtXN04PfzCPO5DbtTdR11UIP0RDe0XujoRWGnEklSUH
rF7/ZRbDLhmVrvV0otSFqR1Ws3lpvPGoVa/M4BP2cFrYfNhUG2lty7ooaHvZgn4zv19r2IiRxAKB
SfDeAgB5Z3/+fhhtjZCEMIIGwjCCBKqgAwIBAgIQU7h+g+GcmSiTsJtJHOy46zANBgkqhkiG9w0B
AQsFADA3MRQwEgYDVQQKDAtUZWxpYVNvbmVyYTEfMB0GA1UEAwwWVGVsaWFTb25lcmEgUm9vdCBD
QSB2MTAeFw0xNTEwMjcxMjE2NDZaFw0yNTEwMjcxMjE2NDZaMEcxCzAJBgNVBAYTAlNFMREwDwYD
VQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MzCCAiIw
DQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBAOzy3wAAuFDyp7vYVLfGk/fjwao71MNGNLSzzl5D
tjQtMtl2ZLPZyX6ViqzTN9JOb7uZ6KxuGSpReQvt8XOh7iIhkKH9W5hRpbjTsJmUMJd6zifhOpNK
6iSU3q44+FjsQL1lVtcguUuFG6aZN0N3GFVbgt6jRrASF8t/3wy9bHPAIfMyPybpg6Y2PH5/1Nwk
TepoDSmK69LGV+lV2IK6U9OWayZXZFIFIDCoGyFlhFxAEgN+qZ2+Rqg/0TM0oCHvKO2ELSGmAdnJ
kwizR42ji/Y9SYTSuG75mzSe6OfCGWM8Db/xvy/20aLEPXNu1PvOgzY63WZ6cmkWnjMlVJ90pWC2
haqDm3Yf8TRdjUvAl7Pz1bTuexwShzIGakL7MkCYrEqHMRaojI/VStloQgW76E76zQ2byw5QxrhO
UbisBSKRzlTlOZQgYFFAbG6ViF8DOpJh/ygtQwuTLUM5r15G7eynQV1AMTNCWcX+HUvgArUw6RfW
9L58uA68GjktFTV8s9RlDsUqsNcLqeXaV28S2WMday0YGaq/bloS8AD7KuumUKH+Ri9IGO9mJvP0
5tvDHjKpLvv80c3WLJnJU/aznYHYEt2+jjKHOTqdGTxL/zMdpRSQFSuu+KM8NoYrkU1VJqKga+QL
sgqKghMp99gu1P1e6KsqseWHdXORrMbjqkBXAgMBAAGjggG4MIIBtDCBigYIKwYBBQUHAQEEfjB8
MC0GCCsGAQUFBzABhiFodHRwOi8vb2NzcC50cnVzdC50ZWxpYXNvbmVyYS5jb20wSwYIKwYBBQUH
MAKGP2h0dHA6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhc29uZXJhLmNvbS90ZWxpYXNvbmVyYXJv
b3RjYXYxLmNlcjASBgNVHRMBAf8ECDAGAQH/AgEAMFUGA1UdIAROMEwwSgYMKwYBBAGCDwIDAQEC
MDowOAYIKwYBBQUHAgEWLGh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYXNvbmVyYS5jb20v
Q1BTMEsGA1UdHwREMEIwQKA+oDyGOmh0dHA6Ly9jcmwtMy50cnVzdC50ZWxpYXNvbmVyYS5jb20v
dGVsaWFzb25lcmFyb290Y2F2MS5jcmwwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMA4G
A1UdDwEB/wQEAwIBBjAdBgNVHQ4EFgQUHHsZnpecdqwgPdjc45Fq49stplMwHwYDVR0jBBgwFoAU
8I9ZOACz9Y+algzV6/p7qhfoExIwDQYJKoZIhvcNAQELBQADggIBAFBYa/HVjDu0LqtXQ8iMp8PL
Fpqchf41ksQY6R1AsoZbaBUu0NQlAQ9GzlC1pmI5s0cJnuaZI0xV6TiWS3/R2p9UgW61XD9CTIUb
AL31mY3BdJf3P46gzKgQEca/DlFjq9GVmuPS4q90BLNgvgoxoHubc3C6s0OaY1sbnay5EhnvrAE4
Q511FlxmJPLnRmQGpieeXa3cPegFfY1kJDKyyFRypF1RuRLXcdMIgKEy5NX1bS3M9dQ4mgmUmVT2
d33UiKSEYQ6s/B+LFaaz4LywXSv2o3W4kbHoQs86IWst821ww0wxsCpEfClIvF7fBw2QkbG/1Pwu
zAuLVStEhDzkAqOrMGctKyNEaBsyAn7Eq2eCa8QDXnkmagp9QPsNFs/oqnXj9j1cVtH9a4OPzhtg
0pd7gd0NzU/5QxibXqbYvouQgihGXHQDmaL4ruN7C4arMUqRo82YnREsKL7h3j/jtmzcMLc9Q07F
04QQd/iSR1Y5pIi6PdNBiE2/4uyAXS6KOIGZrPbNQUNrZtwiQpqQNl8AUzgegfPwrYFlFocpaF3d
1m5r+2VKKqiRQVfYPGYeZnWfkcz06JoAhc/9mjbHXSP9hvWYzeLRuoZqHGUdjOX9DIQb926OneV7
C5WMIjSY8ORkamG/HKqngmjypL3gSc6oG/E6B+1i6Ds5j0Qpj5aQMYICzTCCAskCAQEwWzBHMQsw
CQYDVQQGEwJTRTERMA8GA1UECgwIRXJpY3Nzb24xJTAjBgNVBAMMHEVyaWNzc29uIE5MIEluZGl2
aWR1YWwgQ0EgdjMCEAtGbc1we24wZa62a3lxee0wDQYJYIZIAWUDBAIBBQCgggFDMBgGCSqGSIb3
DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTIwMDMyNDE0MzkyMVowLwYJKoZIhvcN
AQkEMSIEICn17gGhYfjVWB7S85gjzOLOUUzND5ecubEaDXM4CxAOMGoGCSsGAQQBgjcQBDFdMFsw
RzELMAkGA1UEBhMCU0UxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQDDBxFcmljc3NvbiBOTCBJ
bmRpdmlkdWFsIENBIHYzAhALRm3NcHtuMGWutmt5cXntMGwGCyqGSIb3DQEJEAILMV2gWzBHMQsw
CQYDVQQGEwJTRTERMA8GA1UECgwIRXJpY3Nzb24xJTAjBgNVBAMMHEVyaWNzc29uIE5MIEluZGl2
aWR1YWwgQ0EgdjMCEAtGbc1we24wZa62a3lxee0wDQYJKoZIhvcNAQEBBQAEggEAd+EK0jECNvDd
4RiPKQ3cPUNoSbFNNSvzEnmxYOXXmnXz8XR1TTpGuriOOhJ/KBpHXNoW9oFZ/GT7CKLmg7V0oiiE
SmTPQOdk7tI81LNo+dpx0yASEl4W1vPo6SMhcbnHx7oT+8BW93bcteiB5NqrdBwONjt/GnlNNQ+5
GEv9MaMk5lXpcDqhSISTeZWQkHPXO/2uefxQtvyReX2NI78RrnrjYP2o7m6fd0cgak7Sn7ZeJLOn
UJ5GuT4Tz9qf2bneEjEbKEn0VXDNw0ucTm7xAOkiG8Q0Y0pu2Zq6EOUauU4rETKVg10KgKj61VDa
OZkkyKnfwAMRvnRflmnG3VCLNwAAAAAAAA==


--=-ghOuTrUYuw70WnDwyyhh--


From nobody Tue Mar 24 08:33:30 2020
Return-Path: <aaron.falk@gmail.com>
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 677943A0871 for <taps@ietfa.amsl.com>; Tue, 24 Mar 2020 08:33:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 j4P6znm0Gybq for <taps@ietfa.amsl.com>; Tue, 24 Mar 2020 08:33:24 -0700 (PDT)
Received: from mail-pj1-x1033.google.com (mail-pj1-x1033.google.com [IPv6:2607:f8b0:4864:20::1033]) (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 1085D3A08B5 for <taps@ietf.org>; Tue, 24 Mar 2020 08:33:23 -0700 (PDT)
Received: by mail-pj1-x1033.google.com with SMTP id kx8so1586411pjb.5 for <taps@ietf.org>; Tue, 24 Mar 2020 08:33:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=RYQS0ksTtuUS6YtnhE4SP884b8dJnwsYlXDFzH/hTgw=; b=SxGPts8VAesvG4oLgDKSNQKOXKV2rfs++zn/BtZElQ2aLjbVZPDMUcmKf7cGN90S4Z O7gL0GDaRgSiQQG7dYC8FK9fFyKYERCpfoD4fU07KhoUSKvDLELMZhlcpPCMwb9HKYUF iLmpBzMbNA3YlO0jv4TPKvfG51Yf+PDZ4Lcvjv7ArfU0jdtbBNd/Lk+STzqA2e4kax07 KBetNE3wjy72fUi+xyIYlXuV7dPxEAD7Ao6Iun27YeH0nWJ/R2zeTy7wmZHUA7K4i2+6 zKXyqKm6nWWzH06/QPQ20/0H/iU5heRjOABapC5IknEjq56GocRI1owb1+E8Y17AEu5N vXYA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=RYQS0ksTtuUS6YtnhE4SP884b8dJnwsYlXDFzH/hTgw=; b=pt5V48/3cVtrd9Q3W/D+iD2Azg9XlMQG3BVSU1QHphqZLgiKNBznmCBnmXLgV8xbx5 cnfcEBaNTjqHU6K6P3SZTupz7YbDD2acWepItQdqcE9mMA4qtPABc1fCBMZQST3EtnoU kHT27z+QXQbnORWpzy5UtaUfZHVPkH02MF+wHGTi7it0JEPvTXPiZVT9SPIfWd027oHw lbnsHHE12wyXyl1A7Cdu0FTGtzYmbg9PbPo4QFovIyFuc5OYE5lmjhQd4exlMhK8Q/Tb uZNKib0pTHgN0jm53IHLw1Cua0RQj++Ohk3Bgko6GgVkhu10xKE1BnM1l005Af0WTQUm CehA==
X-Gm-Message-State: ANhLgQ3ABRpWry2EOBms/1HgN9sV1iJP8QSEysPzRH4YU3XtSK0B+VzS lk3tqywhm/OdJTVYfM9aMb4XcdJX20QVGDPZtLqg7NE3
X-Google-Smtp-Source: ADFU+vvK/nUnu+oiMW4N5fSZL2xa4/r+7RuQXmzrtUCjSEA0z5+Rh1tPvcXblBg117qqeVzZ8OYC5Uq2lU13IruMsO0=
X-Received: by 2002:a17:90a:bb92:: with SMTP id v18mr5962382pjr.171.1585064002821;  Tue, 24 Mar 2020 08:33:22 -0700 (PDT)
MIME-Version: 1.0
References: <18805F34-42FE-42D8-AE3D-5D9AE2111A9A@gmail.com> <E4EBDD29-A18D-4B07-BA1A-F4D563A5EC08@gmail.com> <81D5CFCB-634F-41E0-AC22-D7BAFCC34D33@gmail.com> <7cfeb3b3682826b7cbc0033d4bf691808f8e9bd2.camel@ericsson.com> <350953BF-B45A-49EF-9AAD-369A6347A04B@gmail.com> <a6b425f24c488ac240f7bebb17eae8d07427778b.camel@ericsson.com>
In-Reply-To: <a6b425f24c488ac240f7bebb17eae8d07427778b.camel@ericsson.com>
From: Aaron Falk <aaron.falk@gmail.com>
Date: Tue, 24 Mar 2020 11:33:11 -0400
Message-ID: <CAD62q9VLRo=obZFDKWGsPNeRqyXZ+Bjs6Fp7SN9MegjHzSe8JQ@mail.gmail.com>
To: "taps@ietf.org" <taps@ietf.org>
Cc: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>,  Magnus Westerlund <magnus.westerlund@ericsson.com>
Content-Type: multipart/mixed; boundary="000000000000d5c30a05a19b783f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/ZubYKSMnX6VVIbmCqaSE9J5mDgE>
Subject: Re: [Taps] TAPS April Interim Scheduling
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, 24 Mar 2020 15:33:28 -0000

--000000000000d5c30a05a19b783f
Content-Type: multipart/alternative; boundary="000000000000d5c30805a19b783d"

--000000000000d5c30805a19b783d
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

OK, let=E2=80=99s do the meeting at the time described below (April 17, 160=
0 UTC).
I=E2=80=99m attaching an .ics file for those with fancy calendars. :)  Agen=
da to
come.

--aaron

On Tue, Mar 24, 2020 at 10:39 AM Magnus Westerlund <
magnus.westerlund@ericsson.com> wrote:

> Hi,
>
> Yes, that will not collide with the IESG meeting.
>
> /Magnus
>
> On Mon, 2020-03-23 at 11:15 -0400, Aaron Falk wrote:
> > Thanks, Magnus. Just to confirm (since I=E2=80=99ve been mistaken in th=
e past):
> will
> > the timing below work without conflicting with the IESG meeting?
> > --aaron
> > CEST/CET, Central European Summer
> > 6:00p Fri, Apr 17 2020
> > 8:00p Fri, Apr 17 2020
> > UTC, Coordinated Universal Time
> > 4:00p Fri, Apr 17 2020
> > 6:00p Fri, Apr 17 2020
> > EDT/EST, Eastern Daylight Time (US)
> > 12:00p Fri, Apr 17 2020
> > 2:00p Fri, Apr 17 2020
> > PDT/PST, Pacific Daylight Time (US)
> > 9:00a Fri, Apr 17 2020
> > 11:00a Fri, Apr 17 2020
> > On 23 Mar 2020, at 10:54, Magnus Westerlund wrote:
> > > Hi,
> > >
> > > Actually the IESG meeting will have end at 16:00 UTC on the 17th of
> April,
> > > it is
> > > 16:00-18:00 CEST. The TAPS meeting scheduled is 19:00-21:00 CEST. It
> would
> > > work
> > > for me, but so you have the right information.
> > >
> > > Cheers
> > >
> > > Magnus
> > >
> > > On Fri, 2020-03-20 at 14:49 -0400, Aaron Falk wrote:
> > > > The IESG call runs until 5pm UTC which conflicts with Mirja and
> Magnus.
> > > > So,
> > > > I=E2=80=99d like to propose we adjust the time to fit. Also, the ti=
mes I
> pasted
> > > > into
> > > > the Doodle are messed up because of daylight savings in the US. To
> get it
> > > > right, I consulted this site. Bottom line: If you cannot attend on
> April
> > > > 17 if
> > > > we run the call from the times below please speak up.
> > > > UTC       EDT     PDT
> > > > 5:00p - 7:00p     1:00p - 3:00p   10:00a - 12:00p
> > > > Webex link: https://ietf.webex.com/meet/taps
> > > > Sorry for the confusion!
> > > > --aaron
> > > > On 19 Mar 2020, at 15:26, Aaron Falk wrote:
> > > > > Looks like everyone responding can make April 17, 11am - 1pm EDT =
/
> 8am -
> > > > > 10am PDT / 4pm - 6pm UTC. If you cannot, please complete the
> doodle poll
> > > > > ASAP.
> > > > > Thanks,
> > > > > --aaron
> > > > > On 17 Mar 2020, at 10:59, Aaron Falk wrote:
> > > > > > Doodle to select meeting date for April interim. We=E2=80=99ve =
had good
> luck
> > > > > > with
> > > > > > Fridays 11am EDT so please vote. (Preference given to authors.)
> Date
> > > > > > will
> > > > > > be selected at the end of this week.
> > > > > > https://doodle.com/poll/7b6p6a9twgrtf7ib
> > > > > > --aaron
> > >
> > > --
> > > Cheers
> > >
> > > Magnus Westerlund
> > >
> > >
> > > ---------------------------------------------------------------------=
-
> > > Networks, Ericsson Research
> > > ---------------------------------------------------------------------=
-
> > > Ericsson AB | Phone +46 10 7148287
> > > Torshamnsgatan 23 | Mobile +46 73 0949079
> > > SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> > > ---------------------------------------------------------------------=
-
> --
> Cheers
>
> Magnus Westerlund
>
>
> ----------------------------------------------------------------------
> Networks, Ericsson Research
> ----------------------------------------------------------------------
> Ericsson AB                 | Phone  +46 10 7148287
> Torshamnsgatan 23           | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>
>
>

--000000000000d5c30805a19b783d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">OK, let=E2=80=99s do the meeting at the time described bel=
ow (April 17, 1600 UTC).=C2=A0 I=E2=80=99m attaching an .ics file for those=
 with fancy calendars. :) =C2=A0Agenda to come.<br><br>--aaron<br></div><br=
><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, M=
ar 24, 2020 at 10:39 AM Magnus Westerlund &lt;<a href=3D"mailto:magnus.west=
erlund@ericsson.com">magnus.westerlund@ericsson.com</a>&gt; wrote:<br></div=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
Yes, that will not collide with the IESG meeting. <br>
<br>
/Magnus<br>
<br>
On Mon, 2020-03-23 at 11:15 -0400, Aaron Falk wrote:<br>
&gt; Thanks, Magnus. Just to confirm (since I=E2=80=99ve been mistaken in t=
he past): will<br>
&gt; the timing below work without conflicting with the IESG meeting?<br>
&gt; --aaron<br>
&gt; CEST/CET, Central European Summer<br>
&gt; 6:00p Fri, Apr 17 2020<br>
&gt; 8:00p Fri, Apr 17 2020<br>
&gt; UTC, Coordinated Universal Time<br>
&gt; 4:00p Fri, Apr 17 2020<br>
&gt; 6:00p Fri, Apr 17 2020<br>
&gt; EDT/EST, Eastern Daylight Time (US)<br>
&gt; 12:00p Fri, Apr 17 2020<br>
&gt; 2:00p Fri, Apr 17 2020<br>
&gt; PDT/PST, Pacific Daylight Time (US)<br>
&gt; 9:00a Fri, Apr 17 2020<br>
&gt; 11:00a Fri, Apr 17 2020<br>
&gt; On 23 Mar 2020, at 10:54, Magnus Westerlund wrote:<br>
&gt; &gt; Hi,<br>
&gt; &gt; <br>
&gt; &gt; Actually the IESG meeting will have end at 16:00 UTC on the 17th =
of April,<br>
&gt; &gt; it is<br>
&gt; &gt; 16:00-18:00 CEST. The TAPS meeting scheduled is 19:00-21:00 CEST.=
 It would<br>
&gt; &gt; work<br>
&gt; &gt; for me, but so you have the right information.<br>
&gt; &gt; <br>
&gt; &gt; Cheers<br>
&gt; &gt; <br>
&gt; &gt; Magnus<br>
&gt; &gt; <br>
&gt; &gt; On Fri, 2020-03-20 at 14:49 -0400, Aaron Falk wrote:<br>
&gt; &gt; &gt; The IESG call runs until 5pm UTC which conflicts with Mirja =
and Magnus.<br>
&gt; &gt; &gt; So,<br>
&gt; &gt; &gt; I=E2=80=99d like to propose we adjust the time to fit. Also,=
 the times I pasted<br>
&gt; &gt; &gt; into<br>
&gt; &gt; &gt; the Doodle are messed up because of daylight savings in the =
US. To get it<br>
&gt; &gt; &gt; right, I consulted this site. Bottom line: If you cannot att=
end on April<br>
&gt; &gt; &gt; 17 if<br>
&gt; &gt; &gt; we run the call from the times below please speak up.<br>
&gt; &gt; &gt; UTC=C2=A0 =C2=A0 =C2=A0 =C2=A0EDT=C2=A0 =C2=A0 =C2=A0PDT<br>
&gt; &gt; &gt; 5:00p - 7:00p=C2=A0 =C2=A0 =C2=A01:00p - 3:00p=C2=A0 =C2=A01=
0:00a - 12:00p<br>
&gt; &gt; &gt; Webex link: <a href=3D"https://ietf.webex.com/meet/taps" rel=
=3D"noreferrer" target=3D"_blank">https://ietf.webex.com/meet/taps</a><br>
&gt; &gt; &gt; Sorry for the confusion!<br>
&gt; &gt; &gt; --aaron<br>
&gt; &gt; &gt; On 19 Mar 2020, at 15:26, Aaron Falk wrote:<br>
&gt; &gt; &gt; &gt; Looks like everyone responding can make April 17, 11am =
- 1pm EDT / 8am -<br>
&gt; &gt; &gt; &gt; 10am PDT / 4pm - 6pm UTC. If you cannot, please complet=
e the doodle poll<br>
&gt; &gt; &gt; &gt; ASAP.<br>
&gt; &gt; &gt; &gt; Thanks,<br>
&gt; &gt; &gt; &gt; --aaron<br>
&gt; &gt; &gt; &gt; On 17 Mar 2020, at 10:59, Aaron Falk wrote:<br>
&gt; &gt; &gt; &gt; &gt; Doodle to select meeting date for April interim. W=
e=E2=80=99ve had good luck<br>
&gt; &gt; &gt; &gt; &gt; with<br>
&gt; &gt; &gt; &gt; &gt; Fridays 11am EDT so please vote. (Preference given=
 to authors.) Date<br>
&gt; &gt; &gt; &gt; &gt; will<br>
&gt; &gt; &gt; &gt; &gt; be selected at the end of this week.<br>
&gt; &gt; &gt; &gt; &gt; <a href=3D"https://doodle.com/poll/7b6p6a9twgrtf7i=
b" rel=3D"noreferrer" target=3D"_blank">https://doodle.com/poll/7b6p6a9twgr=
tf7ib</a><br>
&gt; &gt; &gt; &gt; &gt; --aaron<br>
&gt; &gt; <br>
&gt; &gt; -- <br>
&gt; &gt; Cheers<br>
&gt; &gt; <br>
&gt; &gt; Magnus Westerlund<br>
&gt; &gt; <br>
&gt; &gt; <br>
&gt; &gt; -----------------------------------------------------------------=
-----<br>
&gt; &gt; Networks, Ericsson Research<br>
&gt; &gt; -----------------------------------------------------------------=
-----<br>
&gt; &gt; Ericsson AB | Phone +46 10 7148287<br>
&gt; &gt; Torshamnsgatan 23 | Mobile +46 73 0949079<br>
&gt; &gt; SE-164 80 Stockholm, Sweden | mailto: <a href=3D"mailto:magnus.we=
sterlund@ericsson.com" target=3D"_blank">magnus.westerlund@ericsson.com</a>=
<br>
&gt; &gt; -----------------------------------------------------------------=
-----<br>
-- <br>
Cheers<br>
<br>
Magnus Westerlund <br>
<br>
<br>
----------------------------------------------------------------------<br>
Networks, Ericsson Research<br>
----------------------------------------------------------------------<br>
Ericsson AB=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| =
Phone=C2=A0 +46 10 7148287<br>
Torshamnsgatan 23=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| Mobile +46 73 0=
949079<br>
SE-164 80 Stockholm, Sweden | mailto: <a href=3D"mailto:magnus.westerlund@e=
ricsson.com" target=3D"_blank">magnus.westerlund@ericsson.com</a><br>
----------------------------------------------------------------------<br>
<br>
<br>
</blockquote></div>

--000000000000d5c30805a19b783d
Content-Type: text/calendar; charset="UTF-8"
Content-Transfer-Encoding: 7bit

BEGIN:VCALENDAR
PRODID:-//Helloka, LLC//World Time Buddy//EN
BEGIN:VEVENT
DESCRIPTION:\nhttps://ietf.webex.com/meet/taps
DTEND:20200417T180000Z
DTSTAMP:20200324T145328Z
DTSTART:20200417T160000Z
LOCATION:
SUMMARY;LANGUAGE=en-us:TAPS April Interim
TRANSP:OPAQUE
UID:5a73af2b-63df-9e14-7148-faf179786e43@worldtimebuddy.com
BEGIN:VALARM
TRIGGER:-PT15M
ACTION:DISPLAY
DESCRIPTION:Reminder
END:VALARM
END:VEVENT
END:VCALENDAR

--000000000000d5c30805a19b783d--

--000000000000d5c30a05a19b783f
Content-Type: text/calendar; charset="US-ASCII"; name="TAPS April interim.ics"
Content-Disposition: attachment; filename="TAPS April interim.ics"
Content-Transfer-Encoding: base64
Content-ID: <f_k8625ff50>
X-Attachment-Id: f_k8625ff50

QkVHSU46VkNBTEVOREFSClBST0RJRDotLy9IZWxsb2thLCBMTEMvL1dvcmxkIFRpbWUgQnVkZHkv
L0VOCkJFR0lOOlZFVkVOVApERVNDUklQVElPTjpcbmh0dHBzOi8vaWV0Zi53ZWJleC5jb20vbWVl
dC90YXBzCkRURU5EOjIwMjAwNDE3VDE4MDAwMFoKRFRTVEFNUDoyMDIwMDMyNFQxNDUzMjhaCkRU
U1RBUlQ6MjAyMDA0MTdUMTYwMDAwWgpMT0NBVElPTjoKU1VNTUFSWTtMQU5HVUFHRT1lbi11czpU
QVBTIEFwcmlsIEludGVyaW0KVFJBTlNQOk9QQVFVRQpVSUQ6NWE3M2FmMmItNjNkZi05ZTE0LTcx
NDgtZmFmMTc5Nzg2ZTQzQHdvcmxkdGltZWJ1ZGR5LmNvbQpCRUdJTjpWQUxBUk0KVFJJR0dFUjot
UFQxNU0KQUNUSU9OOkRJU1BMQVkKREVTQ1JJUFRJT046UmVtaW5kZXIKRU5EOlZBTEFSTQpFTkQ6
VkVWRU5UCkVORDpWQ0FMRU5EQVIK
--000000000000d5c30a05a19b783f--


From nobody Wed Mar 25 05:43:57 2020
Return-Path: <magnus.westerlund@ericsson.com>
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 97B273A0902; Wed, 25 Mar 2020 05:43:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.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 rJ1c7OuHjofb; Wed, 25 Mar 2020 05:43:53 -0700 (PDT)
Received: from EUR05-DB8-obe.outbound.protection.outlook.com (mail-db8eur05on2066.outbound.protection.outlook.com [40.107.20.66]) (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 99FB23A08FE; Wed, 25 Mar 2020 05:43:52 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=RCA4k1KdInovcx7v+jjmHp77Kgqy7jj/9hyy8BOusPjLTzeG84VD2vFo4n5FYzcscrP0VZ/fOIvaxj+u7POGNif+PKE59PJVF1a2vFsYpkm86ENsMRj5lhw2K/K4Qm0a3fdVpftsGaA9ZAbdv06LEO8dwY4zJF1CVnw+J8QxhnJzwGXZl8KkjYtpiY/QfRxrvsPmCw68BscaIy77EUMYuYgv0rl+Q3jm6g2/bQ+gshBAYKPti/0ta3Wz9/nlD/VtDNJwg7lvbaLVlGm9YUv+m/3fajxFh0ZirdGky+ErW89DDNuoh9k45W5tMASI2UPPfeLCYVq8kOVYRaMRZVM7Lg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=yWbz3hFABStNa2MXmBnXxhyzp//PcKAot1WVQ46a7P8=; b=NvudmnR0AvdTCPFKcP61DomLF3/6do0pR0LaA8J1vCZHMa+yNC0+EVTAtRQswEL6TzlbTbzs2XxqGWotyHsLBqesApu5WyXD0xe0mwbX3KdIVFQgpSiDAttwi7ddMGHT5FHBBXu+FJuQRCkyKkYq2Xviz8mEy9Vwk1d8qjskDa0kwZ3ahD3T1UnPHsczq/l/VzuAUhXj0iwM6Kg0dTSgKF0G+2/qkzOduuwzdn/n1hutp08kkvEjLaEKdBqpepReE2tC9nTKzwkj5IsB4XPZ0f3/uPOcqIn2qzEVEITZlOph2zT0AlGlyeqxDUtHQ3MReXdOBOw5BvVa7QXRhwauug==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=yWbz3hFABStNa2MXmBnXxhyzp//PcKAot1WVQ46a7P8=; b=qpoeQi6mK3C+vBj1IEM2pM6KELOcrTE25mIPXVPzir3VYoLKpLhel6SXY+e4rqOV47HPgGtcF1/srAW+yqfwROrTO/OUX7x2uzg6OtBso5u1HvOCIPs8Kaua2/Ekrye1WqG6eM44EaYhvmOA1VjGzF0wN+wjGDv9Ijjy/KOW5Xk=
Received: from HE1PR0702MB3772.eurprd07.prod.outlook.com (52.133.7.14) by HE1PR0702MB3708.eurprd07.prod.outlook.com (52.133.6.17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2856.17; Wed, 25 Mar 2020 12:43:49 +0000
Received: from HE1PR0702MB3772.eurprd07.prod.outlook.com ([fe80::8bd:85b0:d547:9eed]) by HE1PR0702MB3772.eurprd07.prod.outlook.com ([fe80::8bd:85b0:d547:9eed%6]) with mapi id 15.20.2856.018; Wed, 25 Mar 2020 12:43:49 +0000
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
To: "ekr@rtfm.com" <ekr@rtfm.com>, "taps@ietf.org" <taps@ietf.org>, "draft-ietf-taps-transport-security.all@ietf.org" <draft-ietf-taps-transport-security.all@ietf.org>
Thread-Topic: Review of draft-ietf-taps-transport-security-10
Thread-Index: AQHVp+BJsqWU8TwuDkKXs0T50bXXF6hZ9ViA
Date: Wed, 25 Mar 2020 12:43:49 +0000
Message-ID: <HE1PR0702MB377263F6E134DBDE23EC20FC95CE0@HE1PR0702MB3772.eurprd07.prod.outlook.com>
References: <CABcZeBNJCr4cs=Os8sVG6bzk10_8UbdMzYDW7m8Nd8sJKWiYbg@mail.gmail.com>
In-Reply-To: <CABcZeBNJCr4cs=Os8sVG6bzk10_8UbdMzYDW7m8Nd8sJKWiYbg@mail.gmail.com>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=magnus.westerlund@ericsson.com; 
x-originating-ip: [158.174.118.23]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 0809e558-c34e-4dec-3809-08d7d0ba2ae7
x-ms-traffictypediagnostic: HE1PR0702MB3708:
x-microsoft-antispam-prvs: <HE1PR0702MB370867E6FBFED52F316978C595CE0@HE1PR0702MB3708.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:983;
x-forefront-prvs: 0353563E2B
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(366004)(346002)(396003)(376002)(136003)(39860400002)(81166006)(81156014)(478600001)(15650500001)(186003)(26005)(2906002)(8676002)(52536014)(86362001)(5660300002)(33656002)(64756008)(66946007)(76116006)(66446008)(66556008)(66476007)(66616009)(8936002)(110136005)(316002)(6506007)(7696005)(71200400001)(53546011)(55016002)(9686003)(44832011); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR0702MB3708; H:HE1PR0702MB3772.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: Hq0g7/5FZ/UWkLpK+9T29I+wrqopn+ZAXuLSvsMnr7XBOBlKI1ebtlBxDbxy81nBL0aZTlAdSbEy6x6V0bA8skXt+ieyBCOFhdLfdsQvc65QlYd2L4yFeJnIoaws401ZCgPI3Uu1zke8qj2J6ilLqf9v5BZI6cPQ0jsMKpi/tvBWSqmQp2Hh+8TCRoLBNxv+eOGJK/a0wJ7/LygtcoIt9U9DEUlhfZ5Aj/ixgi/YSQHhlYZg87XuUOM+89XGb/3mkVuxBO8YtIRtgu7y6qu5WaFBXKzF8XIshpyJt+GFG3g25+POdLygrfyM/nXUKkQdsLJNr6ngVvTL7e23lQFuJh0PTivbxVk+lFuxINF53g1tq34CTm3bs/0FO+gYvlscwq3qHzMNHV29mZzdJdvI0CUvPU+Lihnj4Q15NSuJXRPbrZmrAdEWGmTt39W5kNb1
x-ms-exchange-antispam-messagedata: /QOSUd4wim1VPK83Xg+dpfqdoyTYo/ka9EAaX1B3toe5aNite6pp/rKAM3vMN1ro6oUi7WtGjCpbVlgYeq7zTs6pVeLfrLDqrge5PDG6rzX0jQcstTRA4KBuxRsRLxaqH7+n8nXUHsxat4ULHLHdMA==
x-ms-exchange-transport-forked: True
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_0028_01D602AB.696295A0"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 0809e558-c34e-4dec-3809-08d7d0ba2ae7
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Mar 2020 12:43:49.7196 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: ViCcUI6CxDSwRLJ0crkzJKimfsY3M5ZzORqEVM7gjy9ot5HhAhMXxRHKVdZyZGNvp/SkMFIfieDD1z+75eBV+ox3I3Ga24ytvLsRpYF/H8M=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0702MB3708
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/ednzGR4Sevl80Zf0sYv9SrC0e9g>
Subject: Re: [Taps] Review of draft-ietf-taps-transport-security-10
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: Wed, 25 Mar 2020 12:43:56 -0000

------=_NextPart_000_0028_01D602AB.696295A0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_0029_01D602AB.696295A0"


------=_NextPart_001_0029_01D602AB.696295A0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 7bit

HI Ekr,



I have looked at the changes in -11 of the draft and they appear to resolve 
your comments below. I would appreciate feedback if you concur with my 
assessment. I will however in the meantime go forward and schedule this 
document for IESG evaluation. It will at the earliest be on the IESG agenda on 
the 9th of April.



Cheers



Magnus Westerlund



From: Eric Rescorla <ekr@rtfm.com>
Sent: den 1 december 2019 01:42
To: taps@ietf.org; draft-ietf-taps-transport-security.all@ietf.org
Subject: Review of draft-ietf-taps-transport-security-10



Document: draft-ietf-taps-transport-security-10.txt

This document is much improved. I appreciate you removing all the fine
detail of each transport protocol. However, I think another pass
is probably required.

At a high level, I think your taxonomy is still problematic,
especially when it comes to TLS/DTLS because they have been so widely
used in coordination with other protocols (SRTP, SCTP, QUIC, EAP,
etc.) So, it's simultaneously a full transport protocol (the original
usage), an external key management protocol (OpenVPN), an embedded key
management protocol (QUIC, and what's effectively a VPN protocol (SCTP
over DTLS and AnyConnect VPN). Part of this can be fixed by just
saying something like this and including DTLS in a few other places
in the doc, but in general, the world is just complicated and so
taxonomies are difficult.

It would probably somewhat help to explain the common design for
channel security protocols. Something like:

    In general, channel security protocols follow a common pattern:

    - A handshake protocol is responsible for negotiating parameters,
      authenticating the endpoints, and establishing shared keys.

    - A record protocol is used to encrypt traffic using keys and
      parameters provided by the handshake protocol.

    In some systems, such as IPsec, these protocols are separate:
    AH and ESP just assume some external source of keys and parameters;
    these are commonly supplied by IKEv2 but can also be supplied
    by some other protocol or manually configured. In other systems,
    these are tightly integrated, as in tcpcrypt. Some protocols can also be 
used in both
    configurations: the base TLS protocol as defined in [RFC8446] has
    an integrated handshake and record protocol, but TLS or DTLS can be
    used to negotiate keys for other protocols, as in DTLS-SRTP,
    or the handshake can be used alone with s separate record layer,
    as in QUIC.


S 3.2.1.
You're going to want to mention DTLS-SRTP here, partly for the reasons
I mentioned above but partly to help understand the situation with
ZRTP. I.e., SRTP, like IPsec, just assumes that it has some external
keying mechanism and DTLS and ZRTP both fill this role.


S 3.3.1.
I would just call this IETF QUIC, because QUICv1 is defined to use
TLS.


S 3.3.5.
   CurveCP [CurveCP] is a UDP-based transport security protocol from
   Daniel J.  Bernstein.  Unlike other security protocols, it is based
   entirely upon highly efficient public key algorithms.  This removes
   many pitfalls associated with nonce reuse and key synchronization.

This text is going to be confusing to people.  Not to say that CurveCP
is bad, and the primitives it uses *are* fast, but they're not any
faster than those used by TLS, QUIC, or tcpcrypt. I think the
consensus here is that it's not currently practical to have a general
purpose transport protocol that doesn't do key establishment and then
use symmetric keys. (This is the same reason why we weren't able
to use public key encryption for QUIC CID encryption).


3.4.3.  OpenVPN

   OpenVPN [OpenVPN] is a commonly used protocol designed as an
   alternative to IPsec.  A major goal of this protocol is to provide a
   VPN that is simple to configure and works over a variety of
   transports.  OpenVPN encapsulates either IP packets or Ethernet
   frames within a secure tunnel and can run over UDP or TCP.

It's probably worth noting that OpenVPN uses SSL/TLS for handshake,
as it illustrates the pattern above.


4.1.  Reliable Byte-Stream Transports

   The following protocols all depend upon running on a transport
   protocol that provides a reliable, in-order stream of bytes.  This is
   typically TCP.

   Application Payload Security Protocols:

   o  TLS

   Transport-Layer Security Protocols:

   o  tcpcrypt

This doesn't seem quite right, as tcpcrypt is run prior to the TCP
reassembly algorithms.


   Packet Security Protocols:

   o  OpenVPN

Well, sort of. OpenVPN needs TCP for its key establishment phase but
not its transport phase. That doesn't seem like that interesting
a point to make here, as if TCP wasn't available, it could just
cut over to DTLS.


5.1.  Pre-Connection Interfaces

   Configuration interfaces are used to configure the security protocols
   before a handshake begins or the keys are negotiated.

This presentation seems pretty hard to follow, in that it's a lot of
work to figure out which in the long list of protocols doesn't have
this property. Maybe a summary table would help?

Also, I'm not sure you want to omit tcpcrypt here, in that it does
have a way to do external authentication by exporting a session ID.
Also ZRTP allows for some sort of fingerprint-based auth.

tcpcrypt (and I believe ZRTP) both have session caches.


  o  Authentication Delegation: The application provides access to a
      separate module that will provide authentication, using EAP for
      example.

You don't list TLS, but what about EAP-TLS?


I'm not following any of the text around import. This direct/explicit
distinction seems arbitrary, and weird for QUIC, because QUIC doesn't
really have explicit import so much as a dependency on a handshake
protocol that must be integrated.

S 5.2.
IKE has source address validation, no?


S 5.3.
   o  Connection Termination: The security protocol may be instructed to
      tear down its connection and session information.  This is needed
      by some protocols to prevent application data truncation attacks.

This seems like kind of a confusing section, I think partly because it
ignores layering.

The way I think of this is that we have an existing family of insecure
protocols that have their own termination mechanisms (e.g., TCP
FIN/RST). A security protocol that is under such a protocol (e.g.,
IPsec) doesn't need a secure termination mechanism because (a) the
existing termination mechanism become secure and (b) it can just stop
transmitting. By contrast, a security protocol that is above (TLS) or
at the level of such a protocol (QUIC, tcpcrypt) needs its own secure
termination mechanism, lest it be at the mercy of the transport.


   o  Mobility Events: The record protocol can be signaled that it is
      being migrated to another transport or interface due to connection
      mobility, which may reset address and state validation and induce
      state changes such as use of a new Connection Identifier (CID).

How does this work in ESP, actually?

DTLS sort of has this, in that it has a CID, but vague migration rules.


------=_NextPart_001_0029_01D602AB.696295A0
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 15 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DSV =
link=3D"#0563C1" vlink=3D"#954F72"><div class=3DWordSection1><p =
class=3DMsoNormal><span style=3D'mso-fareast-language:EN-US'>HI =
Ekr,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:EN-US'>I have looked at the changes in -11 =
of the draft and they appear to resolve your comments below. I would =
appreciate feedback if you concur with my assessment. I will however in =
the meantime go forward and schedule this document for IESG evaluation. =
It will at the earliest be on the IESG agenda on the 9<sup>th</sup> of =
April. <o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:EN-US'>Cheers<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:EN-US'>Magnus =
Westerlund<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #E1E1E1 =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
lang=3DEN-US>From:</span></b><span lang=3DEN-US> Eric Rescorla =
&lt;ekr@rtfm.com&gt; <br><b>Sent:</b> den 1 december 2019 =
01:42<br><b>To:</b> taps@ietf.org; =
draft-ietf-taps-transport-security.all@ietf.org<br><b>Subject:</b> =
Review of =
draft-ietf-taps-transport-security-10<o:p></o:p></span></p></div></div><p=
 class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p =
class=3DMsoNormal>Document: =
draft-ietf-taps-transport-security-10.txt<br><br>This document is much =
improved. I appreciate you removing all the fine<br>detail of each =
transport protocol. However, I think another pass<br>is probably =
required.<br><br>At a high level, I think your taxonomy is still =
problematic,<br>especially when it comes to TLS/DTLS because they have =
been so widely<br>used in coordination with other protocols (SRTP, SCTP, =
QUIC, EAP,<br>etc.) So, it's simultaneously a full transport protocol =
(the original<br>usage), an external key management protocol (OpenVPN), =
an embedded key<br>management protocol (QUIC, and what's effectively a =
VPN protocol (SCTP<br>over DTLS and AnyConnect VPN). Part of this can be =
fixed by just<br>saying something like this and including DTLS in a few =
other places<br>in the doc, but in general, the world is just =
complicated and so<br>taxonomies are difficult.<br><br>It would probably =
somewhat help to explain the common design for<br>channel security =
protocols. Something like:<br><br>&nbsp; &nbsp; In general, channel =
security protocols follow a common pattern:<br>&nbsp; &nbsp; <br>&nbsp; =
&nbsp; - A handshake protocol is responsible for negotiating =
parameters,<br>&nbsp; &nbsp; &nbsp; authenticating the endpoints, and =
establishing shared keys.<br>&nbsp; &nbsp; <br>&nbsp; &nbsp; - A record =
protocol is used to encrypt traffic using keys and<br>&nbsp; &nbsp; =
&nbsp; parameters provided by the handshake protocol.<br>&nbsp; &nbsp; =
<br>&nbsp; &nbsp; In some systems, such as IPsec, these protocols are =
separate:<br>&nbsp; &nbsp; AH and ESP just assume some external source =
of keys and parameters;<br>&nbsp; &nbsp; these are commonly supplied by =
IKEv2 but can also be supplied<br>&nbsp; &nbsp; by some other protocol =
or manually configured. In other systems,<br>&nbsp; &nbsp; these are =
tightly integrated, as in tcpcrypt. Some protocols can also be used in =
both<br>&nbsp; &nbsp; configurations: the base TLS protocol as defined =
in [RFC8446] has<br>&nbsp; &nbsp; an integrated handshake and record =
protocol, but TLS or DTLS can be<br>&nbsp; &nbsp; used to negotiate keys =
for other protocols, as in DTLS-SRTP,<br>&nbsp; &nbsp; or the handshake =
can be used alone with s separate record layer,<br>&nbsp; &nbsp; as in =
QUIC.<br><br><br>S 3.2.1.<br>You're going to want to mention DTLS-SRTP =
here, partly for the reasons<br>I mentioned above but partly to help =
understand the situation with<br>ZRTP. I.e., SRTP, like IPsec, just =
assumes that it has some external<br>keying mechanism and DTLS and ZRTP =
both fill this role.<br><br><br>S 3.3.1.<br>I would just call this IETF =
QUIC, because QUICv1 is defined to use<br>TLS.<br><br><br>S =
3.3.5.<br>&nbsp; &nbsp;CurveCP [CurveCP] is a UDP-based transport =
security protocol from<br>&nbsp; &nbsp;Daniel J.&nbsp; Bernstein.&nbsp; =
Unlike other security protocols, it is based<br>&nbsp; &nbsp;entirely =
upon highly efficient public key algorithms.&nbsp; This =
removes<br>&nbsp; &nbsp;many pitfalls associated with nonce reuse and =
key synchronization.<br><br>This text is going to be confusing to =
people.&nbsp; Not to say that CurveCP<br>is bad, and the primitives it =
uses *are* fast, but they're not any<br>faster than those used by TLS, =
QUIC, or tcpcrypt. I think the<br>consensus here is that it's not =
currently practical to have a general<br>purpose transport protocol that =
doesn't do key establishment and then<br>use symmetric keys. (This is =
the same reason why we weren't able<br>to use public key encryption for =
QUIC CID encryption).<br><br><br>3.4.3.&nbsp; OpenVPN<br><br>&nbsp; =
&nbsp;OpenVPN [OpenVPN] is a commonly used protocol designed as =
an<br>&nbsp; &nbsp;alternative to IPsec.&nbsp; A major goal of this =
protocol is to provide a<br>&nbsp; &nbsp;VPN that is simple to configure =
and works over a variety of<br>&nbsp; &nbsp;transports.&nbsp; OpenVPN =
encapsulates either IP packets or Ethernet<br>&nbsp; &nbsp;frames within =
a secure tunnel and can run over UDP or TCP.<br><br>It's probably worth =
noting that OpenVPN uses SSL/TLS for handshake,<br>as it illustrates the =
pattern above.<br><br><br>4.1.&nbsp; Reliable Byte-Stream =
Transports<br><br>&nbsp; &nbsp;The following protocols all depend upon =
running on a transport<br>&nbsp; &nbsp;protocol that provides a =
reliable, in-order stream of bytes.&nbsp; This is<br>&nbsp; =
&nbsp;typically TCP.<br><br>&nbsp; &nbsp;Application Payload Security =
Protocols:<br><br>&nbsp; &nbsp;o &nbsp;TLS<br><br>&nbsp; =
&nbsp;Transport-Layer Security Protocols:<br><br>&nbsp; &nbsp;o =
&nbsp;tcpcrypt<br><br>This doesn't seem quite right, as tcpcrypt is run =
prior to the TCP<br>reassembly algorithms.<br><br><br>&nbsp; =
&nbsp;Packet Security Protocols:<br><br>&nbsp; &nbsp;o =
&nbsp;OpenVPN<br><br>Well, sort of. OpenVPN needs TCP for its key =
establishment phase but<br>not its transport phase. That doesn't seem =
like that interesting<br>a point to make here, as if TCP wasn't =
available, it could just<br>cut over to DTLS.<br><br><br>5.1.&nbsp; =
Pre-Connection Interfaces<br><br>&nbsp; &nbsp;Configuration interfaces =
are used to configure the security protocols<br>&nbsp; &nbsp;before a =
handshake begins or the keys are negotiated.<br><br>This presentation =
seems pretty hard to follow, in that it's a lot of<br>work to figure out =
which in the long list of protocols doesn't have<br>this property. Maybe =
a summary table would help?<br><br>Also, I'm not sure you want to omit =
tcpcrypt here, in that it does<br>have a way to do external =
authentication by exporting a session ID.<br>Also ZRTP allows for some =
sort of fingerprint-based auth.<br><br>tcpcrypt (and I believe ZRTP) =
both have session caches.<br><br><br>&nbsp; o &nbsp;Authentication =
Delegation: The application provides access to a<br>&nbsp; &nbsp; &nbsp; =
separate module that will provide authentication, using EAP =
for<br>&nbsp; &nbsp; &nbsp; example.<br><br>You don't list TLS, but what =
about EAP-TLS?<br><br><br>I'm not following any of the text around =
import. This direct/explicit<br>distinction seems arbitrary, and weird =
for QUIC, because QUIC doesn't<br>really have explicit import so much as =
a dependency on a handshake<br>protocol that must be =
integrated.<br><br>S 5.2.<br>IKE has source address validation, =
no?<br><br><br>S 5.3.<br>&nbsp; &nbsp;o &nbsp;Connection Termination: =
The security protocol may be instructed to<br>&nbsp; &nbsp; &nbsp; tear =
down its connection and session information.&nbsp; This is =
needed<br>&nbsp; &nbsp; &nbsp; by some protocols to prevent application =
data truncation attacks.<br><br>This seems like kind of a confusing =
section, I think partly because it<br>ignores layering.<br><br>The way I =
think of this is that we have an existing family of =
insecure<br>protocols that have their own termination mechanisms (e.g., =
TCP<br>FIN/RST). A security protocol that is under such a protocol =
(e.g.,<br>IPsec) doesn't need a secure termination mechanism because (a) =
the<br>existing termination mechanism become secure and (b) it can just =
stop<br>transmitting. By contrast, a security protocol that is above =
(TLS) or<br>at the level of such a protocol (QUIC, tcpcrypt) needs its =
own secure<br>termination mechanism, lest it be at the mercy of the =
transport.<br><br><br>&nbsp; &nbsp;o &nbsp;Mobility Events: The record =
protocol can be signaled that it is<br>&nbsp; &nbsp; &nbsp; being =
migrated to another transport or interface due to connection<br>&nbsp; =
&nbsp; &nbsp; mobility, which may reset address and state validation and =
induce<br>&nbsp; &nbsp; &nbsp; state changes such as use of a new =
Connection Identifier (CID).<br><br>How does this work in ESP, =
actually?<br><br>DTLS sort of has this, in that it has a CID, but vague =
migration rules.<o:p></o:p></p></div></div></div></body></html>
------=_NextPart_001_0029_01D602AB.696295A0--

------=_NextPart_000_0028_01D602AB.696295A0
Content-Type: application/pkcs7-signature;
	name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="smime.p7s"

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIVdjCCAyAw
ggIIoAMCAQICAR0wDQYJKoZIhvcNAQEFBQAwOTELMAkGA1UEBhMCRkkxDzANBgNVBAoTBlNvbmVy
YTEZMBcGA1UEAxMQU29uZXJhIENsYXNzMiBDQTAeFw0wMTA0MDYwNzI5NDBaFw0yMTA0MDYwNzI5
NDBaMDkxCzAJBgNVBAYTAkZJMQ8wDQYDVQQKEwZTb25lcmExGTAXBgNVBAMTEFNvbmVyYSBDbGFz
czIgQ0EwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCQF0o1ncrwDZbHRPoWN/xIvb1/
gC01O+FvqGepvwMcTYxvMkfVQWikEwTBNQyahEP8XB3/ibPoFxjNkV/7iePqv05dfBsm03V57eaE
41flrSnE9Doo56V7hDZps/1edr2jLZnTkE4jKH0YY/FUOyaddluXQrL/rvBO7N05lU6DBn/nSUDI
xQGyVFpmHT38+ek8Cp6BuHDwAYvkI1R8yK74kB4AlnLUVM9hI7zq+50CldG2uXE6aQg/D7ThQseI
9T+YqKe6HOBxce9YV4FQelxrdEYOgwOYw46obvJ2Mm4ng8Jz89wY6LST6nVEawRgIHFXh53zvqCQ
Iz2KJOHaIdvDAgMBAAGjMzAxMA8GA1UdEwEB/wQFMAMBAf8wEQYDVR0OBAoECEqgqliE0148MAsG
A1UdDwQEAwIBBjANBgkqhkiG9w0BAQUFAAOCAQEAWs6H+RZyFVdLHdmb56ImMOyTZ9/WLdI0r/c4
pc6rFrmrL3w1y6zQD7RMK/yA72uMkV82dvfbsxsZ6vSyEf1hcUS/KLM6Hb+zQ+ifv9wxCHGwnY3W
NEcykMZlJPegSnwEc485bxeMcrW9S8h6+HuDwyhOnAnqZz+yZwQbwxTa+OdJJJHQHWr6YTnva+ch
dQYH2BK0ISBwQnGB2jyaNr6mWw1qbJofkXv5+e9Cuk5OnswMjZTc2UWcXuxCUGOu9F3EsRLcyjuo
Lp0UWgV1t+zXY+K6NbYECJHo2p2c9ma1GKwKplQmNDPSG8HUfxo6jguqMm7b/E8ln9kyx5ZacKzf
TDCCBX0wggRloAMCAQICEQCH7S4aKCZKxRmqOuu5DaLLMA0GCSqGSIb3DQEBCwUAMDkxCzAJBgNV
BAYTAkZJMQ8wDQYDVQQKEwZTb25lcmExGTAXBgNVBAMTEFNvbmVyYSBDbGFzczIgQ0EwHhcNMTQx
MjA1MDgxOTE1WhcNMjEwNDA1MTAyOTAwWjA3MRQwEgYDVQQKDAtUZWxpYVNvbmVyYTEfMB0GA1UE
AwwWVGVsaWFTb25lcmEgUm9vdCBDQSB2MTCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIB
AMK+6yfwIaPzaSZVfp3FVRaRXP3vIb9TgHot0pGMYzHw7CTww6XScnwQbfQ3t+XmfHnqjLWCi65I
tqwA3GV17CpNX8GH9SBlK4GoRz6JI5UwFpB/6FcHSOcZrr9FZ7E3GwYq/t75rH2D+1665I+XZ75L
jo1kB1c4VWk0Nj0TSO9P4tNmHqTPGrdeNjPUtAa9GAH9d4RQAEX1jF3oI7x+/jXh7VB7qTCNGdMJ
jmhnXb88lxhTuylixcpecsHHltTbLaC0H2kD7OriUPEMPPCs81Mt8Bz17Ww5OXOAFshSsCPN4D7c
3TxHoLs1iuKYaIu+5b9y7tL6pe0S7fyYGKkmdtwoSxAgHNN/Fnct7W+A90m7UwW7XWjH1Mh1Fj+J
Wov3F0fUTPHSiXk+TT2YqGHeOh7S+F4D4MHJHIzTjU3TlTazN19jY5szFPAtJmtTfImMMsJu7D0h
ADnJoWjiUIMusDor8zagrC/kb2HCUQk5PotTubtn2txTuXZZNp1D5SDgPTJghSJRt8czu90VL6R4
pgd7gUY2BIbdeTXHlSw7sKMXNeVzH7RcWe/a6hBle3rQf5+ztCo3O3CLm1u5K7fsslESl1MpWtTw
EhDcTwK7EpIvYtQ/aUN8Ddb8WHUBiJ1YFkveupD/RwGJBmr2X7KQarMCpgKIv7NHfirZ1fpoeDVN
AgMBAAGjggGAMIIBfDBOBggrBgEFBQcBAQRCMEAwPgYIKwYBBQUHMAKGMmh0dHA6Ly9jYS50cnVz
dC50ZWxpYXNvbmVyYS5jb20vc29uZXJhY2xhc3MyY2EuY2VyMA8GA1UdEwEB/wQFMAMBAf8wGQYD
VR0gBBIwEDAOBgwrBgEEAYIPAgMBAQIwDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBTwj1k4ALP1
j5qWDNXr+nuqF+gTEjCBuQYDVR0fBIGxMIGuMG+gbaBrhmlsZGFwOi8vY3JsLTEudHJ1c3QudGVs
aWFzb25lcmEuY29tL2NuPVNvbmVyYSUyMENsYXNzMiUyMENBLG89U29uZXJhLGM9Rkk/Y2VydGlm
aWNhdGVyZXZvY2F0aW9ubGlzdDtiaW5hcnkwO6A5oDeGNWh0dHA6Ly9jcmwtMi50cnVzdC50ZWxp
YXNvbmVyYS5jb20vc29uZXJhY2xhc3MyY2EuY3JsMBMGA1UdIwQMMAqACEqgqliE0148MA0GCSqG
SIb3DQEBCwUAA4IBAQAQ1elFTM6fGkQ/aRKdkUZicO3Cb9uzBJOpOtFctw+1El0/17lsjoVvJkZB
D3KnUobnrriFdAa+7FAN55KLmZeB/3Y2bG0bB4toSyaVHjOQnQY9M0dv8U852w0Q7GwchKfebLUI
bh9TMt2hI3Xc6j4knFTBUo7C1WAfO51K4bn1irmX6/Ej2VTgiOFsvOAny28W6enFSEQpSHw60VhN
fSttSqTOxyrRR/7kW7Y8yb/3DZDZ/dH6ZCfx/y+BNIv2NuSd85M9HXUzplXXohti4Ql/qeaMn6by
Ius6XlMWZZfkdVRvTuk2PkeC7UmAJ2+/DUWOPpawaytMXVfF4Hvxk34NMIIGBzCCA++gAwIBAgIQ
C0ZtzXB7bjBlrrZreXF57TANBgkqhkiG9w0BAQsFADBHMQswCQYDVQQGEwJTRTERMA8GA1UECgwI
RXJpY3Nzb24xJTAjBgNVBAMMHEVyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EgdjMwHhcNMTcxMjE1
MDcyMjIzWhcNMjAxMjE1MDcyMjIyWjBwMREwDwYDVQQKDAhFcmljc3NvbjEaMBgGA1UEAwwRTWFn
bnVzIFdlc3Rlcmx1bmQxLTArBgkqhkiG9w0BCQEWHm1hZ251cy53ZXN0ZXJsdW5kQGVyaWNzc29u
LmNvbTEQMA4GA1UEBRMHZXJhbXN3ZDCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALCp
R2bwd07JixA7T0ohRSgIe90tsAKbfpWqoOXl06qJ6p80/cpBBi9ncfZgU/tlmYiCsaOMNrIrFZdx
BGE6l05HLabq+3DdvYCwvBd7SRxiNrFFaTvQMKVazflLhxFXrR7e4XcVvbmHdCySfEz+v8BpCHwB
WmcZWVJ+/TtnhxJX4odYlSIk2Vy3BHtawSbc4VDUR1oDptr0JQyeLAqYoBhaucPl0kb4hEDJEGUb
8NQkJm9+UEvwv09+qIMyERw7gHZKEmolDmP0tnS6eB5MLzjoPrQA6Wh5K23ZnZ4yhq2EpyYoJscN
eKSboMS/1W9hHlXIKQH1VbLey5uDzj0SPPsCAwEAAaOCAcQwggHAMEgGA1UdHwRBMD8wPaA7oDmG
N2h0dHA6Ly9jcmwudHJ1c3QudGVsaWEuY29tL2VyaWNzc29ubmxpbmRpdmlkdWFsY2F2My5jcmww
gYIGCCsGAQUFBwEBBHYwdDAoBggrBgEFBQcwAYYcaHR0cDovL29jc3AyLnRydXN0LnRlbGlhLmNv
bTBIBggrBgEFBQcwAoY8aHR0cDovL2NhLnRydXN0LnRlbGlhc29uZXJhLmNvbS9lcmljc3Nvbm5s
aW5kaXZpZHVhbGNhdjMuY2VyMCkGA1UdEQQiMCCBHm1hZ251cy53ZXN0ZXJsdW5kQGVyaWNzc29u
LmNvbTBVBgNVHSAETjBMMEoGDCsGAQQBgg8CAwEBEjA6MDgGCCsGAQUFBwIBFixodHRwczovL3Jl
cG9zaXRvcnkudHJ1c3QudGVsaWFzb25lcmEuY29tL0NQUzAdBgNVHSUEFjAUBggrBgEFBQcDBAYI
KwYBBQUHAwIwHQYDVR0OBBYEFOYr7oaVOdVuFIQQwVsH/F7FPN+2MB8GA1UdIwQYMBaAFBx7GZ6X
nHasID3Y3OORauPbLaZTMA4GA1UdDwEB/wQEAwIFoDANBgkqhkiG9w0BAQsFAAOCAgEAZ9BSrpIN
NFDf3PxEqcUiGmE67HfJYhxzLuay6TgTTmnKRjQTBjYFAw7eEIoYaEEd3L4WFwqwDOfTU78NBzZY
Kh2aBHlWO2JySWJyVwwi1H5CuQ59vBN0K88pJBeoIlDlw8hfZoVmG0gJCcsdGI9F3PHp98GDcqBW
BKo5SrWa3VdKXIBcxHl1S0vA1q80su/in1LQzhIjOh98zt57KvvigZrDokipFp+KGBEWYOShJRAB
4rPWr/tyiGhD5zgLfEEVkaRXxmeHfPRdeqhbxJbqeZ+5fOuBasZwtn64g6OIS0GOhDWjmmCIoV4W
5dlGMQBg5PPWiZv0uaWMqu8M5viityHFJetK5nPEiZbekFysNMFxDhNTLm2rmCjLGndrPIw/qxJF
6fmoE0ZfrHs1mkcRwacblCg3ejIcA4oN0mYtaj+w/w7OFfiSyI41CXNuZfbbzBgvfpaiND/rzCN2
cq6LtDTX2+ebi0GqtfDvuwWfCr+47xXcWMlIG8UNEjxIsocpXCxwJiXiwkGomR5gkRAZAiykn9Du
JRNk61c3Tg9/MI87kNu1N1HXVQg/REN7Re6OhFYacSSVJQesXv9lFsMuGZWu9XSi1IWpHVazeWm8
8ahVr8zgE/ZwWth82FQbaW3Luihoe9mCfjO/X2vYiJHEAoFJ8N4CAHlnf/5+GG2NkIQwggbCMIIE
qqADAgECAhBTuH6D4ZyZKJOwm0kc7LjrMA0GCSqGSIb3DQEBCwUAMDcxFDASBgNVBAoMC1RlbGlh
U29uZXJhMR8wHQYDVQQDDBZUZWxpYVNvbmVyYSBSb290IENBIHYxMB4XDTE1MTAyNzEyMTY0NloX
DTI1MTAyNzEyMTY0NlowRzELMAkGA1UEBhMCU0UxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQD
DBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYzMIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIIC
CgKCAgEA7PLfAAC4UPKnu9hUt8aT9+PBqjvUw0Y0tLPOXkO2NC0y2XZks9nJfpWKrNM30k5vu5no
rG4ZKlF5C+3xc6HuIiGQof1bmFGluNOwmZQwl3rOJ+E6k0rqJJTerjj4WOxAvWVW1yC5S4Ubppk3
Q3cYVVuC3qNGsBIXy3/fDL1sc8Ah8zI/JumDpjY8fn/U3CRN6mgNKYrr0sZX6VXYgrpT05ZrJldk
UgUgMKgbIWWEXEASA36pnb5GqD/RMzSgIe8o7YQtIaYB2cmTCLNHjaOL9j1JhNK4bvmbNJ7o58IZ
YzwNv/G/L/bRosQ9c27U+86DNjrdZnpyaRaeMyVUn3SlYLaFqoObdh/xNF2NS8CXs/PVtO57HBKH
MgZqQvsyQJisSocxFqiMj9VK2WhCBbvoTvrNDZvLDlDGuE5RuKwFIpHOVOU5lCBgUUBsbpWIXwM6
kmH/KC1DC5MtQzmvXkbt7KdBXUAxM0JZxf4dS+ACtTDpF9b0vny4DrwaOS0VNXyz1GUOxSqw1wup
5dpXbxLZYx1rLRgZqr9uWhLwAPsq66ZQof5GL0gY72Ym8/Tm28MeMqku+/zRzdYsmclT9rOdgdgS
3b6OMoc5Op0ZPEv/Mx2lFJAVK674ozw2hiuRTVUmoqBr5AuyCoqCEyn32C7U/V7oqyqx5Yd1c5Gs
xuOqQFcCAwEAAaOCAbgwggG0MIGKBggrBgEFBQcBAQR+MHwwLQYIKwYBBQUHMAGGIWh0dHA6Ly9v
Y3NwLnRydXN0LnRlbGlhc29uZXJhLmNvbTBLBggrBgEFBQcwAoY/aHR0cDovL3JlcG9zaXRvcnku
dHJ1c3QudGVsaWFzb25lcmEuY29tL3RlbGlhc29uZXJhcm9vdGNhdjEuY2VyMBIGA1UdEwEB/wQI
MAYBAf8CAQAwVQYDVR0gBE4wTDBKBgwrBgEEAYIPAgMBAQIwOjA4BggrBgEFBQcCARYsaHR0cHM6
Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhc29uZXJhLmNvbS9DUFMwSwYDVR0fBEQwQjBAoD6gPIY6
aHR0cDovL2NybC0zLnRydXN0LnRlbGlhc29uZXJhLmNvbS90ZWxpYXNvbmVyYXJvb3RjYXYxLmNy
bDAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQW
BBQcexmel5x2rCA92NzjkWrj2y2mUzAfBgNVHSMEGDAWgBTwj1k4ALP1j5qWDNXr+nuqF+gTEjAN
BgkqhkiG9w0BAQsFAAOCAgEAUFhr8dWMO7Quq1dDyIynw8sWmpyF/jWSxBjpHUCyhltoFS7Q1CUB
D0bOULWmYjmzRwme5pkjTFXpOJZLf9Han1SBbrVcP0JMhRsAvfWZjcF0l/c/jqDMqBARxr8OUWOr
0ZWa49Lir3QEs2C+CjGge5tzcLqzQ5pjWxudrLkSGe+sAThDnXUWXGYk8udGZAamJ55drdw96AV9
jWQkMrLIVHKkXVG5Etdx0wiAoTLk1fVtLcz11DiaCZSZVPZ3fdSIpIRhDqz8H4sVprPgvLBdK/aj
dbiRsehCzzohay3zbXDDTDGwKkR8KUi8Xt8HDZCRsb/U/C7MC4tVK0SEPOQCo6swZy0rI0RoGzIC
fsSrZ4JrxANeeSZqCn1A+w0Wz+iqdeP2PVxW0f1rg4/OG2DSl3uB3Q3NT/lDGJtepti+i5CCKEZc
dAOZoviu43sLhqsxSpGjzZidESwovuHeP+O2bNwwtz1DTsXThBB3+JJHVjmkiLo900GITb/i7IBd
Loo4gZms9s1BQ2tm3CJCmpA2XwBTOB6B8/CtgWUWhyloXd3Wbmv7ZUoqqJFBV9g8Zh5mdZ+RzPTo
mgCFz/2aNsddI/2G9ZjN4tG6hmocZR2M5f0MhBv3bo6d5XsLlYwiNJjw5GRqYb8cqqeCaPKkveBJ
zqgb8ToH7WLoOzmPRCmPlpAxggMCMIIC/gIBATBbMEcxCzAJBgNVBAYTAlNFMREwDwYDVQQKDAhF
cmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MwIQC0ZtzXB7bjBl
rrZreXF57TAJBgUrDgMCGgUAoIIBfDAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3
DQEJBTEPFw0yMDAzMjUxMjQzNDhaMCMGCSqGSIb3DQEJBDEWBBQ3iMDcWRFXPwQvNhYUEIM3OXu+
YjBDBgkqhkiG9w0BCQ8xNjA0MAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0D
AgIBQDAHBgUrDgMCGjBqBgkrBgEEAYI3EAQxXTBbMEcxCzAJBgNVBAYTAlNFMREwDwYDVQQKDAhF
cmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MwIQC0ZtzXB7bjBl
rrZreXF57TBsBgsqhkiG9w0BCRACCzFdoFswRzELMAkGA1UEBhMCU0UxETAPBgNVBAoMCEVyaWNz
c29uMSUwIwYDVQQDDBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYzAhALRm3NcHtuMGWutmt5
cXntMA0GCSqGSIb3DQEBAQUABIIBAC74IGS0NLZoX9Z91ON6g0dYSmxhIRDCUDYiesYZvOCpSYaW
tQWeqp7O2kZWPtTTkaDt7DPaPimiSMte5OGpZsHdLWG/RX+3ellyFVgXu3+CDBngqTn/5dyrYFKV
+tffROlxpBxCipbxs35Af1ahSF8fj5lns8Pb8Kp7WlLFxHxJlskrTd75ouj8MwCeCgEXqMkZ3RT3
6qPLQnv8wetgJRHWR6sCNMFrKfBMM9sZBGElSqu1iJsoMloWMRe2fY3U9GrAoswL3NAIy9mmD0qx
+QRyyJOYsqsGry7JBn5v/4inOINbY1JdEbtlDzkSqGYGQZA6jNewOwPjlDs42kTmyvYAAAAAAAA=

------=_NextPart_000_0028_01D602AB.696295A0--


From nobody Wed Mar 25 07:25:08 2020
Return-Path: <aaron.falk@gmail.com>
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 4F38F3A0814 for <taps@ietfa.amsl.com>; Wed, 25 Mar 2020 07:25:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.078
X-Spam-Level: 
X-Spam-Status: No, score=-2.078 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, T_SPF_HELO_TEMPERROR=0.01, T_SPF_TEMPERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 7Kh3w1ue-AuF for <taps@ietfa.amsl.com>; Wed, 25 Mar 2020 07:24:58 -0700 (PDT)
Received: from mail-qv1-xf2d.google.com (mail-qv1-xf2d.google.com [IPv6:2607:f8b0:4864:20::f2d]) (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 9D4683A073D for <taps@ietf.org>; Wed, 25 Mar 2020 07:24:48 -0700 (PDT)
Received: by mail-qv1-xf2d.google.com with SMTP id z13so1114109qvw.3 for <taps@ietf.org>; Wed, 25 Mar 2020 07:24:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:subject:date:message-id:mime-version :content-transfer-encoding; bh=PKo2EaUVf02HtAZ2n883/8nX+8qFjmZJm7cn+5E3iuo=; b=mJVwnn0/cqwFAo1ZarPUlimVjuSM0BTWPs2pttB3pHZw639bDypf9TgLFWdP/P0y2E F8byipuz3ivUE8Rt96tPkfyi7fk82q9fD7XoE1brsCv4sbgegrZ80ZQQGC+zEKF/fKW6 vlx3f021XjzO3lkMQruBzH/j2ncWXnOz6GTS4tN2cF9Y3ndFlVkKp32IeD6hNvJOfzIA 5+t1fZ4OCjVHJ6VDfdaUvRv+b9M4oQ3rLZ/qggwUzaOYmuXUV+N2oL5dmciaAGY56qtW 2VnMwowwCUCJKQVZBQvXrXFCx9fvlXTq6yNI+bl48SOHhMigVUSMFrTAeM87QC0QOA2j OWhg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:mime-version :content-transfer-encoding; bh=PKo2EaUVf02HtAZ2n883/8nX+8qFjmZJm7cn+5E3iuo=; b=burWjXdr/jyFy09706lZOFnDvMmg8sNIWc2SeBGJQitI3fVB2zkpR91bQyInKNRboR 2bl9NXsq1bOptSD3zWXjhefmThW6DyddyXGtP7HE6hDV7QAP4cMvuc3qhL9axxfSonqF U3cGVTIva9wo8xBy47Ei0GaIDXb+INGGB7Z9g1ngzzF5Foky8HxLn/M0jocrlrLwF7dj IoHOeGgljHuwDwU+yUM30x9igmtukIu4snLP4ScXNrmjfKTbIqti8jTaPAsoGfL2qM5Y YftAYXFRItFJhG+oOKZ2evlkL9k1EUSvMLurDOryGH6tTcrm1ua5U61W9/vBV8jvaxX0 YHEA==
X-Gm-Message-State: ANhLgQ0G/qU71TCqCGBPgbc7Yp6AZDuEo6pqUUzNuYMDuxswZynA77mi LLAJIPw/WRN5m1T77h1ymTbEMPLf
X-Google-Smtp-Source: ADFU+vs1fjBhJaJ+4XTD+FkOjhGTzQVve5IcumZskbOOS5x7+5TaXeFXQc3fAyFZKoef0TXie/4wRw==
X-Received: by 2002:ad4:5429:: with SMTP id g9mr3282274qvt.134.1585146285071;  Wed, 25 Mar 2020 07:24:45 -0700 (PDT)
Received: from [172.19.115.248] ([2601:184:4881:2420:1c13:9bc0:8566:8bc4]) by smtp.gmail.com with ESMTPSA id 68sm15394308qkh.75.2020.03.25.07.24.43 for <taps@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 25 Mar 2020 07:24:43 -0700 (PDT)
From: "Aaron Falk" <aaron.falk@gmail.com>
To: "taps WG" <taps@ietf.org>
Date: Wed, 25 Mar 2020 10:24:42 -0400
X-Mailer: MailMate (1.13.1r5671)
Message-ID: <FE3EA31A-3F39-4A2F-BCC7-12D80C53768B@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_4818A9D7-6D41-4B19-AB4F-4A82C3422D4A_="
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/8a5NjzVJSkcvF7hZtWfRRJ_LbFc>
Subject: [Taps] April interim: call for agenda items
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: Wed, 25 Mar 2020 14:25:07 -0000

--=_MailMate_4818A9D7-6D41-4B19-AB4F-4A82C3422D4A_=
Content-Type: text/plain; charset="UTF-8"; markup=markdown
Content-Transfer-Encoding: 8bit

What shall we discuss in April?  How about:

* Normative language in -arch
* Issue review

Some questions:

Is it timely to seek a deep review of -implementation?
Are there open issues to discuss from Kyle’s review of -interface?
What else?

--aaron
--=_MailMate_4818A9D7-6D41-4B19-AB4F-4A82C3422D4A_=
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: 8bit

<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
</head>
<body>
<div style="font-family:sans-serif"><div style="white-space:normal">
<p dir="auto">What shall we discuss in April?  How about:</p>

<ul>
<li>Normative language in -arch</li>
<li>Issue review</li>
</ul>

<p dir="auto">Some questions:</p>

<p dir="auto">Is it timely to seek a deep review of -implementation?<br>
Are there open issues to discuss from Kyle’s review of -interface?<br>
What else?</p>

<p dir="auto">--aaron</p>
</div>
</div>
</body>
</html>

--=_MailMate_4818A9D7-6D41-4B19-AB4F-4A82C3422D4A_=--


From nobody Wed Mar 25 09:03:19 2020
Return-Path: <gorry@erg.abdn.ac.uk>
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 10F233A0BB0 for <taps@ietfa.amsl.com>; Wed, 25 Mar 2020 09:03:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham 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 QQnfzWV1F0PL for <taps@ietfa.amsl.com>; Wed, 25 Mar 2020 09:03:02 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [IPv6:2001:630:42:150::2]) by ietfa.amsl.com (Postfix) with ESMTP id D5C923A09A4 for <taps@ietf.org>; Wed, 25 Mar 2020 09:02:57 -0700 (PDT)
Received: from GF-MacBook-Pro.local (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id 44E9B1B00158; Wed, 25 Mar 2020 16:02:54 +0000 (GMT)
To: Aaron Falk <aaron.falk@gmail.com>, taps WG <taps@ietf.org>
References: <FE3EA31A-3F39-4A2F-BCC7-12D80C53768B@gmail.com>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Message-ID: <7b6f1f49-5594-da76-bbc0-c1352323889e@erg.abdn.ac.uk>
Date: Wed, 25 Mar 2020 16:02:52 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:68.0) Gecko/20100101 Thunderbird/68.6.0
MIME-Version: 1.0
In-Reply-To: <FE3EA31A-3F39-4A2F-BCC7-12D80C53768B@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/BqDJKJHaMc1TNxjlZM39AmKCrWQ>
Subject: Re: [Taps] April interim: - My promised review of normative arch language (derived from github).
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: Wed, 25 Mar 2020 16:03:11 -0000

As promised,

I did a review of the arch draft and the PR that was recently done. 
There were comments that requested to remove some normative language 
that has been implemented in the current draft - where my review agreed, 
I have not commented further below. However, the latest revision, also 
did not retain the discussion of what I suggested should be normative. I 
have worked through the various comments in github and summarise them 
here (since these comments are now burried in the git, see 502 et al).

So here goes:

Overall review: I think we need to keep the normative language for the 
key features that differentiate the API. I'd really like to use 
REQUIRED, RECOMMENDED, rather MUST and SHOULD - because these are not 
protocol operation requirements, but are implementation requirements to 
conform. This includes requirements based on Minset - where the WG 
dervied this API: This is after all why the WG worked on Minset as the 
basis of the API.

----

The following are key requirements, that define the TAPS architecture:

* It is RECOMMENDED that functionality that is common across multiple 
transport protocols is made accessible through a unified set of TAPS 
interface calls. As a baseline, a Transport Services API is 
RECOMMENDED/REQUIRED to allow access to the minimal set of features 
offered by transport protocols {{?I-D.ietf-taps-minset}}.

* TAPS automates the selection of protocols and features, based on a set 
of Properties supplied through the TAPS interface. It is RECOMMENDED 
that a TAPS system offers Properties that are common to multiple 
transport protocols. Specifying common Properties enables a system to 
appropriately select between protocols that offer equivalent features. 
This design permits evolution of the transport protocols and functions 
without affecting the programs using the system.

* Applications using the TAPS API are REQUIRED to be robust to the 
automated selection provided by TAPS, including the possibility to 
express requirements and preferences that constrain the choices that can 
be made by the system.  In normal use, TAPS Systems are RECOMMENDED to 
be designed so that all selection decisions result in consistent choices 
for the same network conditions when they have the same set of 
preferences. This is intended to provide predictable outcomes to the 
application using the transport service.

* Applications using TAPS MAY explicitly require or prevent the use of 
specific transport features (and transport protocols) using the 
"REQUIRED" and "PROHIBIT" preferences. This allows an application to 
constrain the set of protocols and features that will be selected for 
the transport service. It is RECOMMENDED that the default usage by 
applications does not unecessarily restrict this selection, so that the 
system can make informed choices (e.g., based on the availability of 
interfaces or set of transport protocols available for the specified 
remote endpoint).


---

After thought, here is my specific poposal of what to do next:

(a) I suggest we group all the requirements on architecture as short one 
or two sentence blocks (preferably as a bullet or definition list) 
collected into a single subsection, so they are easy to find and read 
and we say that these are the key architectural requirements. I suggest 
we insert this new requirements text either their own section, or in 
section 1.3 (although I am open to other places where we can call-out 
the architectural requirements).

(b) We need to decide if these are architectural requirements and if 
there are more or less in total. I am of course open to more refined 
wording:-).

(c) We could also explicitly say there are additional requirements in 
racing  in section XX.

(d) If this plan seems appropriate, I would then suggest to use lower 
case within the remainder of document (we could refer to the 
requirements subsection, if we thought necessary).

Thoughts please, but review now completed!

Gorry


---


Additional Language NiT:

I think the word /assumes/ is not a good choice of word.

OLD:

and it assumes an implementation that can use multiple IP addresses, 
multiple protocols, multiple paths, and provide multiple application streams

NEW:

and it can provide benefit when an implementation can use multiple IP 
addresses, multiple protocols, multiple paths, and provide multiple 
application streams.


From nobody Wed Mar 25 09:30:40 2020
Return-Path: <mirja.kuehlewind@ericsson.com>
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 AFFD23A0C10 for <taps@ietfa.amsl.com>; Wed, 25 Mar 2020 09:30:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.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 IZuX4r94FYG8 for <taps@ietfa.amsl.com>; Wed, 25 Mar 2020 09:30:35 -0700 (PDT)
Received: from EUR04-DB3-obe.outbound.protection.outlook.com (mail-eopbgr60074.outbound.protection.outlook.com [40.107.6.74]) (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 14AC53A0BF4 for <taps@ietf.org>; Wed, 25 Mar 2020 09:30:34 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=nA9xXzsHcrd66bnKjO5ADC3zabeie98FHTCSS8eu2e8gUNpT73jHIO6+dKqTqo7zsWp+Z7ErcVzx3wAHtX4j11j9loP1iZmzBiFqpmoHXSolqVuGs1hhCCDsHSJjddX8BwU700apnwX5Cer2a3cz056v6ZgO2U0Ua0OAneMtoEx4C12Jpw0+8o1PFv9j7q+gvlEBrOHfme54WRs5vhl7q23gi0MYVNvS6dFTbJpXaS24HMuy29zRLZGISZ97eUxIzDIF+inn173w+IZlnW7bQKdocNTKzvs4kpNW30MrEwtqjA9eh3nB/Dk7luVc2IjFtWpNPxwMOOQuAInWo7KmSg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=H6hNHDQIr7vN1QVWMhQS5LDhVdZldh2XpUwtlZAEXhc=; b=Y/OtNSkYsmqS3P+MCheULmFBVaNKaHlrO7Y6Uxy8aNjvRYC7MrxOJvrIeHXTOIqIWEZEIvuPKl1VT819V0//X3Yj0bddwilaSx+sie7KcE/u3fWxgx4lPcmbDPTyCQaMUxm0kVSAR6f9BPCdKMnXEcL0VO3Ex4j+NAbpdWr1uH1jXepJU3aMcv42cifQdkM0tH9E5bgXgZe8f71s7MQrGnNgPcN1vl35HrzjostclSkrGgQC8CNXeuguOZqdA6CpkdbW67kSPct0fNmcLBPXzVdjl+Kt9b81xoSEmRdSVFwI6LUZy3qvM4odL5rsQbmVQfb4VQcLSy5qr2SZ01dVpQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=H6hNHDQIr7vN1QVWMhQS5LDhVdZldh2XpUwtlZAEXhc=; b=fITJLDg0uJu9bF4haEJZbUi1hErL/bwQIf0epN2auZHLKHw0JAr6HzQNQEK2HLUbr3W6xYSUmd0OZJV3bIARndhMNdV/vmFAydFoMpHMDBhvuuqeNYl+mCqIn+I1PAIKlqD7uHFh8OsWc5sQV3ZEKe40GAepXJ6IV/okvyYpbYs=
Received: from AM0PR07MB4691.eurprd07.prod.outlook.com (52.135.149.158) by AM0PR07MB4627.eurprd07.prod.outlook.com (52.135.152.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2856.9; Wed, 25 Mar 2020 16:30:32 +0000
Received: from AM0PR07MB4691.eurprd07.prod.outlook.com ([fe80::298a:36c6:fff4:f8f8]) by AM0PR07MB4691.eurprd07.prod.outlook.com ([fe80::298a:36c6:fff4:f8f8%3]) with mapi id 15.20.2856.015; Wed, 25 Mar 2020 16:30:32 +0000
From: Mirja Kuehlewind <mirja.kuehlewind@ericsson.com>
To: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, Aaron Falk <aaron.falk@gmail.com>,  taps WG <taps@ietf.org>
Thread-Topic: [Taps] April interim: - My promised review of normative arch language (derived from github).
Thread-Index: AQHWAr7tebDbtG1g0EaQd8Kmn1JR7ahZkKyA
Date: Wed, 25 Mar 2020 16:30:31 +0000
Message-ID: <42C7E843-F7FC-46E3-8A46-60A4EC75F37C@ericsson.com>
References: <FE3EA31A-3F39-4A2F-BCC7-12D80C53768B@gmail.com> <7b6f1f49-5594-da76-bbc0-c1352323889e@erg.abdn.ac.uk>
In-Reply-To: <7b6f1f49-5594-da76-bbc0-c1352323889e@erg.abdn.ac.uk>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=mirja.kuehlewind@ericsson.com; 
x-originating-ip: [2003:de:e723:9a00:e5aa:d554:528d:65c0]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 275478ef-5837-49ea-af9d-08d7d0d9d672
x-ms-traffictypediagnostic: AM0PR07MB4627:
x-microsoft-antispam-prvs: <AM0PR07MB4627EE6CF9F6E4F6F242976EF4CE0@AM0PR07MB4627.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0353563E2B
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(376002)(39860400002)(396003)(366004)(136003)(346002)(966005)(186003)(8676002)(44832011)(81166006)(8936002)(81156014)(2616005)(33656002)(478600001)(6486002)(6512007)(296002)(36756003)(6506007)(86362001)(2906002)(316002)(66446008)(66556008)(66476007)(64756008)(66946007)(76116006)(71200400001)(110136005)(5660300002); DIR:OUT; SFP:1101; SCL:1; SRVR:AM0PR07MB4627; H:AM0PR07MB4691.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: xireypgJ6qCTwL37y8CJLVvkMfkPwJqNDDANYEcIqDvXxiUCcvYR05amgREGSJYFgMOepVhJGUIPc+9D9ZPllhpOfjkBOF57qo6AnDeQAqvjnEyxDuejQm3pSvg0s0oknw06c6Lu1qpxvcN/gVM95cWGui3+f6VhQkUF/J8QHnGYovw3DObflTmCZKhScqT9s0XNwis6Me+Q5++1C8Cn9Ey0zcGg2ATYNYEpfViGuonU0G8Bibu1NTPUVoG3v8m1+/CyHznlaa+Ufh2tWiw3NADP/ZyHK3PWXCwXNeZTYel3HBcOlsvQa4zU9+T3f/Bx8eqv26Z8AZ7o+FhqGe5UNZfHTvAnugv2rFl/c5tQXUemRiVH0xnI/XDGhxngnAdifhFdznkZJGqnVRIzKHQB8yYXDbvIA8KH2SAe5eIp6O1ThdmatJpdBCi5KK02phO1YvXyYR9uXWAabxadd5GUJzkhq6PjWVn/QkN5t/Sz7YaNDBUo9Ch0rXc7tD4hYq9ewFRmdskjzIblRwmc/4xF0g==
x-ms-exchange-antispam-messagedata: x3VecWWySMqUWYeo4eUieNIf6zD9QHd4eX6oX8VBfH4/Zr4n3iqiYsTIKetW/qUKheHScDkdfCLAiK9LwmZTmtXTyjIUD1xUSKRvj/xqtluw+gNm7P+bVxIawjAsLPvhKkygOkornF1qICAovueHhdTrlCHG5Nwd4zzThdAIJ7aohPJVIv1gVpK1X5d40tLuvd4OfvVBsQcIZv0CgyepNA==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <1E4777A1A32E524C88238601237C6E6A@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 275478ef-5837-49ea-af9d-08d7d0d9d672
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Mar 2020 16:30:32.0125 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: Nlf3Vi5+/1dv9FQPWkBHRC1tc54m7te9bSJqCKyvNKMFYwJONVM3uYpnpCB/ifWlJ+ckWH/W4vvj0HMScs4k13k6AG2Fs7GQrLxdU0qvqhU=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR07MB4627
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/jH5ham0SkJAUw8dl3-eT5pIbOgs>
Subject: Re: [Taps] April interim: - My promised review of normative arch language (derived from github).
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: Wed, 25 Mar 2020 16:30:39 -0000

VGhhbmtzLCBHb3JyeSwgZm9yIHRoaXMhIEkgc3VwcG9ydCB0aGUgaWRlYSBvZiBoYXZpbmcgb25l
IHNlY3Rpb24gd2l0aCBub3JtYXRpdmUgcmVxdWlyZW1lbnQgYXQgdGhlIGJlZ2lubmluZy4gV291
bGQgYmUgbmljZSBpZiBzb21lb25lIGNvdWxkIHB1dCB0aGlzIGluIGEgUFIuIEkgZ3Vlc3Mgd2Ug
bmVlZCB0byBhZGQgYXQgbGVhc3Qgb25lIG1vcmUgcmVxdWlyZW1lbnQgb24gdXNlIG9mIHNlY3Vy
aXR5IHByb3RvY29scyBhdCBsZWFzdC4NCg0KTWlyamENCg0KDQrvu79PbiAyNS4wMy4yMCwgMTc6
MDMsICJUYXBzIG9uIGJlaGFsZiBvZiBHb3JyeSBGYWlyaHVyc3QiIDx0YXBzLWJvdW5jZXNAaWV0
Zi5vcmcgb24gYmVoYWxmIG9mIGdvcnJ5QGVyZy5hYmRuLmFjLnVrPiB3cm90ZToNCg0KICAgIEFz
IHByb21pc2VkLA0KICAgIA0KICAgIEkgZGlkIGEgcmV2aWV3IG9mIHRoZSBhcmNoIGRyYWZ0IGFu
ZCB0aGUgUFIgdGhhdCB3YXMgcmVjZW50bHkgZG9uZS4gDQogICAgVGhlcmUgd2VyZSBjb21tZW50
cyB0aGF0IHJlcXVlc3RlZCB0byByZW1vdmUgc29tZSBub3JtYXRpdmUgbGFuZ3VhZ2UgDQogICAg
dGhhdCBoYXMgYmVlbiBpbXBsZW1lbnRlZCBpbiB0aGUgY3VycmVudCBkcmFmdCAtIHdoZXJlIG15
IHJldmlldyBhZ3JlZWQsIA0KICAgIEkgaGF2ZSBub3QgY29tbWVudGVkIGZ1cnRoZXIgYmVsb3cu
IEhvd2V2ZXIsIHRoZSBsYXRlc3QgcmV2aXNpb24sIGFsc28gDQogICAgZGlkIG5vdCByZXRhaW4g
dGhlIGRpc2N1c3Npb24gb2Ygd2hhdCBJIHN1Z2dlc3RlZCBzaG91bGQgYmUgbm9ybWF0aXZlLiBJ
IA0KICAgIGhhdmUgd29ya2VkIHRocm91Z2ggdGhlIHZhcmlvdXMgY29tbWVudHMgaW4gZ2l0aHVi
IGFuZCBzdW1tYXJpc2UgdGhlbSANCiAgICBoZXJlIChzaW5jZSB0aGVzZSBjb21tZW50cyBhcmUg
bm93IGJ1cnJpZWQgaW4gdGhlIGdpdCwgc2VlIDUwMiBldCBhbCkuDQogICAgDQogICAgU28gaGVy
ZSBnb2VzOg0KICAgIA0KICAgIE92ZXJhbGwgcmV2aWV3OiBJIHRoaW5rIHdlIG5lZWQgdG8ga2Vl
cCB0aGUgbm9ybWF0aXZlIGxhbmd1YWdlIGZvciB0aGUgDQogICAga2V5IGZlYXR1cmVzIHRoYXQg
ZGlmZmVyZW50aWF0ZSB0aGUgQVBJLiBJJ2QgcmVhbGx5IGxpa2UgdG8gdXNlIA0KICAgIFJFUVVJ
UkVELCBSRUNPTU1FTkRFRCwgcmF0aGVyIE1VU1QgYW5kIFNIT1VMRCAtIGJlY2F1c2UgdGhlc2Ug
YXJlIG5vdCANCiAgICBwcm90b2NvbCBvcGVyYXRpb24gcmVxdWlyZW1lbnRzLCBidXQgYXJlIGlt
cGxlbWVudGF0aW9uIHJlcXVpcmVtZW50cyB0byANCiAgICBjb25mb3JtLiBUaGlzIGluY2x1ZGVz
IHJlcXVpcmVtZW50cyBiYXNlZCBvbiBNaW5zZXQgLSB3aGVyZSB0aGUgV0cgDQogICAgZGVydmll
ZCB0aGlzIEFQSTogVGhpcyBpcyBhZnRlciBhbGwgd2h5IHRoZSBXRyB3b3JrZWQgb24gTWluc2V0
IGFzIHRoZSANCiAgICBiYXNpcyBvZiB0aGUgQVBJLg0KICAgIA0KICAgIC0tLS0NCiAgICANCiAg
ICBUaGUgZm9sbG93aW5nIGFyZSBrZXkgcmVxdWlyZW1lbnRzLCB0aGF0IGRlZmluZSB0aGUgVEFQ
UyBhcmNoaXRlY3R1cmU6DQogICAgDQogICAgKiBJdCBpcyBSRUNPTU1FTkRFRCB0aGF0IGZ1bmN0
aW9uYWxpdHkgdGhhdCBpcyBjb21tb24gYWNyb3NzIG11bHRpcGxlIA0KICAgIHRyYW5zcG9ydCBw
cm90b2NvbHMgaXMgbWFkZSBhY2Nlc3NpYmxlIHRocm91Z2ggYSB1bmlmaWVkIHNldCBvZiBUQVBT
IA0KICAgIGludGVyZmFjZSBjYWxscy4gQXMgYSBiYXNlbGluZSwgYSBUcmFuc3BvcnQgU2Vydmlj
ZXMgQVBJIGlzIA0KICAgIFJFQ09NTUVOREVEL1JFUVVJUkVEIHRvIGFsbG93IGFjY2VzcyB0byB0
aGUgbWluaW1hbCBzZXQgb2YgZmVhdHVyZXMgDQogICAgb2ZmZXJlZCBieSB0cmFuc3BvcnQgcHJv
dG9jb2xzIHt7P0ktRC5pZXRmLXRhcHMtbWluc2V0fX0uDQogICAgDQogICAgKiBUQVBTIGF1dG9t
YXRlcyB0aGUgc2VsZWN0aW9uIG9mIHByb3RvY29scyBhbmQgZmVhdHVyZXMsIGJhc2VkIG9uIGEg
c2V0IA0KICAgIG9mIFByb3BlcnRpZXMgc3VwcGxpZWQgdGhyb3VnaCB0aGUgVEFQUyBpbnRlcmZh
Y2UuIEl0IGlzIFJFQ09NTUVOREVEIA0KICAgIHRoYXQgYSBUQVBTIHN5c3RlbSBvZmZlcnMgUHJv
cGVydGllcyB0aGF0IGFyZSBjb21tb24gdG8gbXVsdGlwbGUgDQogICAgdHJhbnNwb3J0IHByb3Rv
Y29scy4gU3BlY2lmeWluZyBjb21tb24gUHJvcGVydGllcyBlbmFibGVzIGEgc3lzdGVtIHRvIA0K
ICAgIGFwcHJvcHJpYXRlbHkgc2VsZWN0IGJldHdlZW4gcHJvdG9jb2xzIHRoYXQgb2ZmZXIgZXF1
aXZhbGVudCBmZWF0dXJlcy4gDQogICAgVGhpcyBkZXNpZ24gcGVybWl0cyBldm9sdXRpb24gb2Yg
dGhlIHRyYW5zcG9ydCBwcm90b2NvbHMgYW5kIGZ1bmN0aW9ucyANCiAgICB3aXRob3V0IGFmZmVj
dGluZyB0aGUgcHJvZ3JhbXMgdXNpbmcgdGhlIHN5c3RlbS4NCiAgICANCiAgICAqIEFwcGxpY2F0
aW9ucyB1c2luZyB0aGUgVEFQUyBBUEkgYXJlIFJFUVVJUkVEIHRvIGJlIHJvYnVzdCB0byB0aGUg
DQogICAgYXV0b21hdGVkIHNlbGVjdGlvbiBwcm92aWRlZCBieSBUQVBTLCBpbmNsdWRpbmcgdGhl
IHBvc3NpYmlsaXR5IHRvIA0KICAgIGV4cHJlc3MgcmVxdWlyZW1lbnRzIGFuZCBwcmVmZXJlbmNl
cyB0aGF0IGNvbnN0cmFpbiB0aGUgY2hvaWNlcyB0aGF0IGNhbiANCiAgICBiZSBtYWRlIGJ5IHRo
ZSBzeXN0ZW0uICBJbiBub3JtYWwgdXNlLCBUQVBTIFN5c3RlbXMgYXJlIFJFQ09NTUVOREVEIHRv
IA0KICAgIGJlIGRlc2lnbmVkIHNvIHRoYXQgYWxsIHNlbGVjdGlvbiBkZWNpc2lvbnMgcmVzdWx0
IGluIGNvbnNpc3RlbnQgY2hvaWNlcyANCiAgICBmb3IgdGhlIHNhbWUgbmV0d29yayBjb25kaXRp
b25zIHdoZW4gdGhleSBoYXZlIHRoZSBzYW1lIHNldCBvZiANCiAgICBwcmVmZXJlbmNlcy4gVGhp
cyBpcyBpbnRlbmRlZCB0byBwcm92aWRlIHByZWRpY3RhYmxlIG91dGNvbWVzIHRvIHRoZSANCiAg
ICBhcHBsaWNhdGlvbiB1c2luZyB0aGUgdHJhbnNwb3J0IHNlcnZpY2UuDQogICAgDQogICAgKiBB
cHBsaWNhdGlvbnMgdXNpbmcgVEFQUyBNQVkgZXhwbGljaXRseSByZXF1aXJlIG9yIHByZXZlbnQg
dGhlIHVzZSBvZiANCiAgICBzcGVjaWZpYyB0cmFuc3BvcnQgZmVhdHVyZXMgKGFuZCB0cmFuc3Bv
cnQgcHJvdG9jb2xzKSB1c2luZyB0aGUgDQogICAgIlJFUVVJUkVEIiBhbmQgIlBST0hJQklUIiBw
cmVmZXJlbmNlcy4gVGhpcyBhbGxvd3MgYW4gYXBwbGljYXRpb24gdG8gDQogICAgY29uc3RyYWlu
IHRoZSBzZXQgb2YgcHJvdG9jb2xzIGFuZCBmZWF0dXJlcyB0aGF0IHdpbGwgYmUgc2VsZWN0ZWQg
Zm9yIA0KICAgIHRoZSB0cmFuc3BvcnQgc2VydmljZS4gSXQgaXMgUkVDT01NRU5ERUQgdGhhdCB0
aGUgZGVmYXVsdCB1c2FnZSBieSANCiAgICBhcHBsaWNhdGlvbnMgZG9lcyBub3QgdW5lY2Vzc2Fy
aWx5IHJlc3RyaWN0IHRoaXMgc2VsZWN0aW9uLCBzbyB0aGF0IHRoZSANCiAgICBzeXN0ZW0gY2Fu
IG1ha2UgaW5mb3JtZWQgY2hvaWNlcyAoZS5nLiwgYmFzZWQgb24gdGhlIGF2YWlsYWJpbGl0eSBv
ZiANCiAgICBpbnRlcmZhY2VzIG9yIHNldCBvZiB0cmFuc3BvcnQgcHJvdG9jb2xzIGF2YWlsYWJs
ZSBmb3IgdGhlIHNwZWNpZmllZCANCiAgICByZW1vdGUgZW5kcG9pbnQpLg0KICAgIA0KICAgIA0K
ICAgIC0tLQ0KICAgIA0KICAgIEFmdGVyIHRob3VnaHQsIGhlcmUgaXMgbXkgc3BlY2lmaWMgcG9w
b3NhbCBvZiB3aGF0IHRvIGRvIG5leHQ6DQogICAgDQogICAgKGEpIEkgc3VnZ2VzdCB3ZSBncm91
cCBhbGwgdGhlIHJlcXVpcmVtZW50cyBvbiBhcmNoaXRlY3R1cmUgYXMgc2hvcnQgb25lIA0KICAg
IG9yIHR3byBzZW50ZW5jZSBibG9ja3MgKHByZWZlcmFibHkgYXMgYSBidWxsZXQgb3IgZGVmaW5p
dGlvbiBsaXN0KSANCiAgICBjb2xsZWN0ZWQgaW50byBhIHNpbmdsZSBzdWJzZWN0aW9uLCBzbyB0
aGV5IGFyZSBlYXN5IHRvIGZpbmQgYW5kIHJlYWQgDQogICAgYW5kIHdlIHNheSB0aGF0IHRoZXNl
IGFyZSB0aGUga2V5IGFyY2hpdGVjdHVyYWwgcmVxdWlyZW1lbnRzLiBJIHN1Z2dlc3QgDQogICAg
d2UgaW5zZXJ0IHRoaXMgbmV3IHJlcXVpcmVtZW50cyB0ZXh0IGVpdGhlciB0aGVpciBvd24gc2Vj
dGlvbiwgb3IgaW4gDQogICAgc2VjdGlvbiAxLjMgKGFsdGhvdWdoIEkgYW0gb3BlbiB0byBvdGhl
ciBwbGFjZXMgd2hlcmUgd2UgY2FuIGNhbGwtb3V0IA0KICAgIHRoZSBhcmNoaXRlY3R1cmFsIHJl
cXVpcmVtZW50cykuDQogICAgDQogICAgKGIpIFdlIG5lZWQgdG8gZGVjaWRlIGlmIHRoZXNlIGFy
ZSBhcmNoaXRlY3R1cmFsIHJlcXVpcmVtZW50cyBhbmQgaWYgDQogICAgdGhlcmUgYXJlIG1vcmUg
b3IgbGVzcyBpbiB0b3RhbC4gSSBhbSBvZiBjb3Vyc2Ugb3BlbiB0byBtb3JlIHJlZmluZWQgDQog
ICAgd29yZGluZzotKS4NCiAgICANCiAgICAoYykgV2UgY291bGQgYWxzbyBleHBsaWNpdGx5IHNh
eSB0aGVyZSBhcmUgYWRkaXRpb25hbCByZXF1aXJlbWVudHMgaW4gDQogICAgcmFjaW5nICBpbiBz
ZWN0aW9uIFhYLg0KICAgIA0KICAgIChkKSBJZiB0aGlzIHBsYW4gc2VlbXMgYXBwcm9wcmlhdGUs
IEkgd291bGQgdGhlbiBzdWdnZXN0IHRvIHVzZSBsb3dlciANCiAgICBjYXNlIHdpdGhpbiB0aGUg
cmVtYWluZGVyIG9mIGRvY3VtZW50ICh3ZSBjb3VsZCByZWZlciB0byB0aGUgDQogICAgcmVxdWly
ZW1lbnRzIHN1YnNlY3Rpb24sIGlmIHdlIHRob3VnaHQgbmVjZXNzYXJ5KS4NCiAgICANCiAgICBU
aG91Z2h0cyBwbGVhc2UsIGJ1dCByZXZpZXcgbm93IGNvbXBsZXRlZCENCiAgICANCiAgICBHb3Jy
eQ0KICAgIA0KICAgIA0KICAgIC0tLQ0KICAgIA0KICAgIA0KICAgIEFkZGl0aW9uYWwgTGFuZ3Vh
Z2UgTmlUOg0KICAgIA0KICAgIEkgdGhpbmsgdGhlIHdvcmQgL2Fzc3VtZXMvIGlzIG5vdCBhIGdv
b2QgY2hvaWNlIG9mIHdvcmQuDQogICAgDQogICAgT0xEOg0KICAgIA0KICAgIGFuZCBpdCBhc3N1
bWVzIGFuIGltcGxlbWVudGF0aW9uIHRoYXQgY2FuIHVzZSBtdWx0aXBsZSBJUCBhZGRyZXNzZXMs
IA0KICAgIG11bHRpcGxlIHByb3RvY29scywgbXVsdGlwbGUgcGF0aHMsIGFuZCBwcm92aWRlIG11
bHRpcGxlIGFwcGxpY2F0aW9uIHN0cmVhbXMNCiAgICANCiAgICBORVc6DQogICAgDQogICAgYW5k
IGl0IGNhbiBwcm92aWRlIGJlbmVmaXQgd2hlbiBhbiBpbXBsZW1lbnRhdGlvbiBjYW4gdXNlIG11
bHRpcGxlIElQIA0KICAgIGFkZHJlc3NlcywgbXVsdGlwbGUgcHJvdG9jb2xzLCBtdWx0aXBsZSBw
YXRocywgYW5kIHByb3ZpZGUgbXVsdGlwbGUgDQogICAgYXBwbGljYXRpb24gc3RyZWFtcy4NCiAg
ICANCiAgICBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0K
ICAgIFRhcHMgbWFpbGluZyBsaXN0DQogICAgVGFwc0BpZXRmLm9yZw0KICAgIGh0dHBzOi8vd3d3
LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdGFwcw0KICAgIA0KDQo=


From nobody Wed Mar 25 09:40:30 2020
Return-Path: <gorry@erg.abdn.ac.uk>
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 0EA5E3A0D80 for <taps@ietfa.amsl.com>; Wed, 25 Mar 2020 09:40:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 jmLrBGdl6fNZ for <taps@ietfa.amsl.com>; Wed, 25 Mar 2020 09:40:15 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [IPv6:2001:630:42:150::2]) by ietfa.amsl.com (Postfix) with ESMTP id 3F2A53A0D74 for <taps@ietf.org>; Wed, 25 Mar 2020 09:40:14 -0700 (PDT)
Received: from GF-MacBook-Pro.local (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id 27C5F1B001FC; Wed, 25 Mar 2020 16:40:11 +0000 (GMT)
To: Mirja Kuehlewind <mirja.kuehlewind@ericsson.com>, taps WG <taps@ietf.org>
References: <FE3EA31A-3F39-4A2F-BCC7-12D80C53768B@gmail.com> <7b6f1f49-5594-da76-bbc0-c1352323889e@erg.abdn.ac.uk> <42C7E843-F7FC-46E3-8A46-60A4EC75F37C@ericsson.com>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Message-ID: <b5717f82-19eb-5bc6-e4bf-8b6f897f3ed3@erg.abdn.ac.uk>
Date: Wed, 25 Mar 2020 16:40:10 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:68.0) Gecko/20100101 Thunderbird/68.6.0
MIME-Version: 1.0
In-Reply-To: <42C7E843-F7FC-46E3-8A46-60A4EC75F37C@ericsson.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/97UvXuNXA7xFFFt5m0mHWktVGTw>
Subject: Re: [Taps] April interim: - My promised review of normative arch language (derived from github).
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: Wed, 25 Mar 2020 16:40:28 -0000

On 25/03/2020 16:30, Mirja Kuehlewind wrote:
> Thanks, Gorry, for this! I support the idea of having one section with normative requirement at the beginning. Would be nice if someone could put this in a PR. I guess we need to add at least one more requirement on use of security protocols at least.

Sure - have you an idea for a "placeholder bullet" we can add to my list 
below... so we don't loose the thought...

Gorry

> Mirja
>
>
> ﻿On 25.03.20, 17:03, "Taps on behalf of Gorry Fairhurst" <taps-bounces@ietf.org on behalf of gorry@erg.abdn.ac.uk> wrote:
>
>      As promised,
>      
>      I did a review of the arch draft and the PR that was recently done.
>      There were comments that requested to remove some normative language
>      that has been implemented in the current draft - where my review agreed,
>      I have not commented further below. However, the latest revision, also
>      did not retain the discussion of what I suggested should be normative. I
>      have worked through the various comments in github and summarise them
>      here (since these comments are now burried in the git, see 502 et al).
>      
>      So here goes:
>      
>      Overall review: I think we need to keep the normative language for the
>      key features that differentiate the API. I'd really like to use
>      REQUIRED, RECOMMENDED, rather MUST and SHOULD - because these are not
>      protocol operation requirements, but are implementation requirements to
>      conform. This includes requirements based on Minset - where the WG
>      dervied this API: This is after all why the WG worked on Minset as the
>      basis of the API.
>      
>      ----
>      
>      The following are key requirements, that define the TAPS architecture:
>      
>      * It is RECOMMENDED that functionality that is common across multiple
>      transport protocols is made accessible through a unified set of TAPS
>      interface calls. As a baseline, a Transport Services API is
>      RECOMMENDED/REQUIRED to allow access to the minimal set of features
>      offered by transport protocols {{?I-D.ietf-taps-minset}}.
>      
>      * TAPS automates the selection of protocols and features, based on a set
>      of Properties supplied through the TAPS interface. It is RECOMMENDED
>      that a TAPS system offers Properties that are common to multiple
>      transport protocols. Specifying common Properties enables a system to
>      appropriately select between protocols that offer equivalent features.
>      This design permits evolution of the transport protocols and functions
>      without affecting the programs using the system.
>      
>      * Applications using the TAPS API are REQUIRED to be robust to the
>      automated selection provided by TAPS, including the possibility to
>      express requirements and preferences that constrain the choices that can
>      be made by the system.  In normal use, TAPS Systems are RECOMMENDED to
>      be designed so that all selection decisions result in consistent choices
>      for the same network conditions when they have the same set of
>      preferences. This is intended to provide predictable outcomes to the
>      application using the transport service.
>      
>      * Applications using TAPS MAY explicitly require or prevent the use of
>      specific transport features (and transport protocols) using the
>      "REQUIRED" and "PROHIBIT" preferences. This allows an application to
>      constrain the set of protocols and features that will be selected for
>      the transport service. It is RECOMMENDED that the default usage by
>      applications does not unecessarily restrict this selection, so that the
>      system can make informed choices (e.g., based on the availability of
>      interfaces or set of transport protocols available for the specified
>      remote endpoint).
>      
>      
>      ---
>      
>      After thought, here is my specific poposal of what to do next:
>      
>      (a) I suggest we group all the requirements on architecture as short one
>      or two sentence blocks (preferably as a bullet or definition list)
>      collected into a single subsection, so they are easy to find and read
>      and we say that these are the key architectural requirements. I suggest
>      we insert this new requirements text either their own section, or in
>      section 1.3 (although I am open to other places where we can call-out
>      the architectural requirements).
>      
>      (b) We need to decide if these are architectural requirements and if
>      there are more or less in total. I am of course open to more refined
>      wording:-).
>      
>      (c) We could also explicitly say there are additional requirements in
>      racing  in section XX.
>      
>      (d) If this plan seems appropriate, I would then suggest to use lower
>      case within the remainder of document (we could refer to the
>      requirements subsection, if we thought necessary).
>      
>      Thoughts please, but review now completed!
>      
>      Gorry
>      
>      
>      ---
>      
>      
>      Additional Language NiT:
>      
>      I think the word /assumes/ is not a good choice of word.
>      
>      OLD:
>      
>      and it assumes an implementation that can use multiple IP addresses,
>      multiple protocols, multiple paths, and provide multiple application streams
>      
>      NEW:
>      
>      and it can provide benefit when an implementation can use multiple IP
>      addresses, multiple protocols, multiple paths, and provide multiple
>      application streams.
>      
>      _______________________________________________
>      Taps mailing list
>      Taps@ietf.org
>      https://www.ietf.org/mailman/listinfo/taps
>      
>


From nobody Thu Mar 26 01:11:16 2020
Return-Path: <michawe@ifi.uio.no>
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 7EE4E3A041C for <taps@ietfa.amsl.com>; Thu, 26 Mar 2020 01:11:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 IvYydLBWfw0R for <taps@ietfa.amsl.com>; Thu, 26 Mar 2020 01:11:12 -0700 (PDT)
Received: from mail-out01.uio.no (mail-out01.uio.no [IPv6:2001:700:100:10::50]) (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 0816B3A0415 for <taps@ietf.org>; Thu, 26 Mar 2020 01:11:11 -0700 (PDT)
Received: from mail-mx12.uio.no ([129.240.10.84]) by mail-out01.uio.no with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93.0.4) (envelope-from <michawe@ifi.uio.no>) id 1jHNbZ-00068L-9D; Thu, 26 Mar 2020 09:11:09 +0100
Received: from ti0182q160-4479.bb.online.no ([84.202.168.179] helo=[192.168.1.4]) by mail-mx12.uio.no with esmtpsa (TLS1.2:ECDHE-RSA-AES256-GCM-SHA384:256) user michawe (Exim 4.93.0.4) (envelope-from <michawe@ifi.uio.no>) id 1jHNbY-0004WC-Ek; Thu, 26 Mar 2020 09:11:09 +0100
From: Michael Welzl <michawe@ifi.uio.no>
Message-Id: <82089A1F-9365-46B6-8AB2-A55DD8D9276E@ifi.uio.no>
Content-Type: multipart/alternative; boundary="Apple-Mail=_90DDF4E9-A170-40ED-ADE9-A749F0DC5F0F"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Thu, 26 Mar 2020 09:11:06 +0100
In-Reply-To: <FE3EA31A-3F39-4A2F-BCC7-12D80C53768B@gmail.com>
Cc: "taps@ietf.org" <taps@ietf.org>
To: Aaron Falk <aaron.falk@gmail.com>
References: <FE3EA31A-3F39-4A2F-BCC7-12D80C53768B@gmail.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-UiO-SPF-Received: Received-SPF: neutral (mail-mx12.uio.no: 84.202.168.179 is neither permitted nor denied by domain of ifi.uio.no) client-ip=84.202.168.179; envelope-from=michawe@ifi.uio.no; helo=[192.168.1.4];
X-UiO-Spam-info: not spam, SpamAssassin (score=-5.0, required=5.0, autolearn=disabled, HTML_MESSAGE=0.001, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO)
X-UiO-Scanned: C8724D1787BE0087EC1C4A860B9812AB390BEB06
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/uYDlnY0ps1ItNY0uXAFa0hhc9pY>
Subject: Re: [Taps] April interim: call for agenda items
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: Thu, 26 Mar 2020 08:11:15 -0000

--Apple-Mail=_90DDF4E9-A170-40ED-ADE9-A749F0DC5F0F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi,

Regarding Kyle=E2=80=99s review, I think this should fall under the =
heading of =E2=80=9Cissue review=E2=80=9D. I=E2=80=99m planning to look =
at these again soon, addressing easy ones in a PR, removing points of =
agreement=E2=80=A6 and whatever remains, unless some bigger things =
warrant a list discussion, I thought I'd post as issues. Clearly, =
=E2=80=9CIssue review=E2=80=9D is an important agenda item and it could =
take long. It=E2=80=99s a good, structured way to discuss things IMHO.

Cheers,
Michael


> On Mar 25, 2020, at 3:24 PM, Aaron Falk <aaron.falk@gmail.com> wrote:
>=20
> What shall we discuss in April? How about:
>=20
> Normative language in -arch
> Issue review
> Some questions:
>=20
> Is it timely to seek a deep review of -implementation?
> Are there open issues to discuss from Kyle=E2=80=99s review of =
-interface?
> What else?
>=20
> --aaron
>=20
> _______________________________________________
> Taps mailing list
> Taps@ietf.org
> https://www.ietf.org/mailman/listinfo/taps


--Apple-Mail=_90DDF4E9-A170-40ED-ADE9-A749F0DC5F0F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D"">Hi,<div class=3D""><br class=3D""></div><div =
class=3D"">Regarding Kyle=E2=80=99s review, I think this should fall =
under the heading of =E2=80=9Cissue review=E2=80=9D. I=E2=80=99m =
planning to look at these again soon, addressing easy ones in a PR, =
removing points of agreement=E2=80=A6 and whatever remains, unless some =
bigger things warrant a list discussion, I thought I'd post as issues. =
Clearly, =E2=80=9CIssue review=E2=80=9D is an important agenda item and =
it could take long. It=E2=80=99s a good, structured way to discuss =
things IMHO.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Cheers,</div><div class=3D"">Michael</div><div class=3D""><br =
class=3D""></div><div class=3D""><div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D"">On Mar 25, 2020, at 3:24 PM, =
Aaron Falk &lt;<a href=3D"mailto:aaron.falk@gmail.com" =
class=3D"">aaron.falk@gmail.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D"">


<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8" =
class=3D"">

<div class=3D"">
<div style=3D"font-family:sans-serif" class=3D""><div =
style=3D"white-space:normal" class=3D""><p dir=3D"auto" class=3D"">What =
shall we discuss in April?  How about:</p>

<ul class=3D"">
<li class=3D"">Normative language in -arch</li>
<li class=3D"">Issue review</li>
</ul><p dir=3D"auto" class=3D"">Some questions:</p><p dir=3D"auto" =
class=3D"">Is it timely to seek a deep review of -implementation?<br =
class=3D"">
Are there open issues to discuss from Kyle=E2=80=99s review of =
-interface?<br class=3D"">
What else?</p><p dir=3D"auto" class=3D"">--aaron</p>
</div>
</div>
</div>

_______________________________________________<br class=3D"">Taps =
mailing list<br class=3D""><a href=3D"mailto:Taps@ietf.org" =
class=3D"">Taps@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/taps<br =
class=3D""></div></blockquote></div><br class=3D""></div></body></html>=

--Apple-Mail=_90DDF4E9-A170-40ED-ADE9-A749F0DC5F0F--


From nobody Thu Mar 26 06:42:32 2020
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 4F36C3A07AD for <taps@ietfa.amsl.com>; Thu, 26 Mar 2020 06:42:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 QomBo1GZdYid for <taps@ietfa.amsl.com>; Thu, 26 Mar 2020 06:42:28 -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 A7E443A0405 for <taps@ietf.org>; Thu, 26 Mar 2020 06:42:26 -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 02QDgCH8014596 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 26 Mar 2020 14:42:12 +0100
Received: from p200300ed5f028800b13c44d75d364b5f.dip0.t-ipconnect.de ([2003:ed:5f02:8800:b13c:44d7:5d36:4b5f]) 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 1jHSjE-0001M5-86; Thu, 26 Mar 2020 14:39:24 +0100
From: "Philipp S. Tiesel" <philipp@tiesel.net>
Message-Id: <C5FC45A0-9AB0-464F-AF2B-099FBD43DDD5@tiesel.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_53F324BB-F7F2-48AC-B6F7-40223CEAC3E6"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Date: Thu, 26 Mar 2020 14:42:12 +0100
In-Reply-To: <7b6f1f49-5594-da76-bbc0-c1352323889e@erg.abdn.ac.uk>
Cc: Aaron Falk <aaron.falk@gmail.com>, taps WG <taps@ietf.org>
To: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
References: <FE3EA31A-3F39-4A2F-BCC7-12D80C53768B@gmail.com> <7b6f1f49-5594-da76-bbc0-c1352323889e@erg.abdn.ac.uk>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/S9nvczOsfDABQpb2IQVs4ZfqAoM>
Subject: Re: [Taps] April interim: - My promised review of normative arch language (derived from github).
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: Thu, 26 Mar 2020 13:42:30 -0000

--Apple-Mail=_53F324BB-F7F2-48AC-B6F7-40223CEAC3E6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi Gorry,

I am much in favour with you proposal, though we can clearly define what =
a TAPS system is.

AVE!
   Philipp=20

> On 25. Mar 2020, at 17:02, Gorry Fairhurst <gorry@erg.abdn.ac.uk> =
wrote:
>=20
> As promised,
>=20
> I did a review of the arch draft and the PR that was recently done. =
There were comments that requested to remove some normative language =
that has been implemented in the current draft - where my review agreed, =
I have not commented further below. However, the latest revision, also =
did not retain the discussion of what I suggested should be normative. I =
have worked through the various comments in github and summarise them =
here (since these comments are now burried in the git, see 502 et al).
>=20
> So here goes:
>=20
> Overall review: I think we need to keep the normative language for the =
key features that differentiate the API. I'd really like to use =
REQUIRED, RECOMMENDED, rather MUST and SHOULD - because these are not =
protocol operation requirements, but are implementation requirements to =
conform. This includes requirements based on Minset - where the WG =
dervied this API: This is after all why the WG worked on Minset as the =
basis of the API.
>=20
> ----
>=20
> The following are key requirements, that define the TAPS architecture:
>=20
> * It is RECOMMENDED that functionality that is common across multiple =
transport protocols is made accessible through a unified set of TAPS =
interface calls. As a baseline, a Transport Services API is =
RECOMMENDED/REQUIRED to allow access to the minimal set of features =
offered by transport protocols {{?I-D.ietf-taps-minset}}.
>=20
> * TAPS automates the selection of protocols and features, based on a =
set of Properties supplied through the TAPS interface. It is RECOMMENDED =
that a TAPS system offers Properties that are common to multiple =
transport protocols. Specifying common Properties enables a system to =
appropriately select between protocols that offer equivalent features. =
This design permits evolution of the transport protocols and functions =
without affecting the programs using the system.
>=20
> * Applications using the TAPS API are REQUIRED to be robust to the =
automated selection provided by TAPS, including the possibility to =
express requirements and preferences that constrain the choices that can =
be made by the system.  In normal use, TAPS Systems are RECOMMENDED to =
be designed so that all selection decisions result in consistent choices =
for the same network conditions when they have the same set of =
preferences. This is intended to provide predictable outcomes to the =
application using the transport service.
>=20
> * Applications using TAPS MAY explicitly require or prevent the use of =
specific transport features (and transport protocols) using the =
"REQUIRED" and "PROHIBIT" preferences. This allows an application to =
constrain the set of protocols and features that will be selected for =
the transport service. It is RECOMMENDED that the default usage by =
applications does not unecessarily restrict this selection, so that the =
system can make informed choices (e.g., based on the availability of =
interfaces or set of transport protocols available for the specified =
remote endpoint).
>=20
>=20
> ---
>=20
> After thought, here is my specific poposal of what to do next:
>=20
> (a) I suggest we group all the requirements on architecture as short =
one or two sentence blocks (preferably as a bullet or definition list) =
collected into a single subsection, so they are easy to find and read =
and we say that these are the key architectural requirements. I suggest =
we insert this new requirements text either their own section, or in =
section 1.3 (although I am open to other places where we can call-out =
the architectural requirements).
>=20
> (b) We need to decide if these are architectural requirements and if =
there are more or less in total. I am of course open to more refined =
wording:-).
>=20
> (c) We could also explicitly say there are additional requirements in =
racing  in section XX.
>=20
> (d) If this plan seems appropriate, I would then suggest to use lower =
case within the remainder of document (we could refer to the =
requirements subsection, if we thought necessary).
>=20
> Thoughts please, but review now completed!
>=20
> Gorry
>=20
>=20
> ---
>=20
>=20
> Additional Language NiT:
>=20
> I think the word /assumes/ is not a good choice of word.
>=20
> OLD:
>=20
> and it assumes an implementation that can use multiple IP addresses, =
multiple protocols, multiple paths, and provide multiple application =
streams
>=20
> NEW:
>=20
> and it can provide benefit when an implementation can use multiple IP =
addresses, multiple protocols, multiple paths, and provide multiple =
application streams.
>=20
> _______________________________________________
> Taps mailing list
> Taps@ietf.org
> https://www.ietf.org/mailman/listinfo/taps

AVE!
   Philipp S. Tiesel

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


--Apple-Mail=_53F324BB-F7F2-48AC-B6F7-40223CEAC3E6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">Hi =
Gorry,<div class=3D""><br class=3D""></div><div class=3D"">I am much in =
favour with you proposal, though we can clearly define what a TAPS =
system is.</div><div class=3D""><br class=3D""></div><div =
class=3D"">AVE!</div><div class=3D"">&nbsp; &nbsp;Philipp&nbsp;<br =
class=3D""><div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On 25. Mar 2020, at 17:02, Gorry Fairhurst &lt;<a =
href=3D"mailto:gorry@erg.abdn.ac.uk" =
class=3D"">gorry@erg.abdn.ac.uk</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div class=3D"">As =
promised,<br class=3D""><br class=3D"">I did a review of the arch draft =
and the PR that was recently done. There were comments that requested to =
remove some normative language that has been implemented in the current =
draft - where my review agreed, I have not commented further below. =
However, the latest revision, also did not retain the discussion of what =
I suggested should be normative. I have worked through the various =
comments in github and summarise them here (since these comments are now =
burried in the git, see 502 et al).<br class=3D""><br class=3D"">So here =
goes:<br class=3D""><br class=3D"">Overall review: I think we need to =
keep the normative language for the key features that differentiate the =
API. I'd really like to use REQUIRED, RECOMMENDED, rather MUST and =
SHOULD - because these are not protocol operation requirements, but are =
implementation requirements to conform. This includes requirements based =
on Minset - where the WG dervied this API: This is after all why the WG =
worked on Minset as the basis of the API.<br class=3D""><br =
class=3D"">----<br class=3D""><br class=3D"">The following are key =
requirements, that define the TAPS architecture:<br class=3D""><br =
class=3D"">* It is RECOMMENDED that functionality that is common across =
multiple transport protocols is made accessible through a unified set of =
TAPS interface calls. As a baseline, a Transport Services API is =
RECOMMENDED/REQUIRED to allow access to the minimal set of features =
offered by transport protocols {{?I-D.ietf-taps-minset}}.<br =
class=3D""><br class=3D"">* TAPS automates the selection of protocols =
and features, based on a set of Properties supplied through the TAPS =
interface. It is RECOMMENDED that a TAPS system offers Properties that =
are common to multiple transport protocols. Specifying common Properties =
enables a system to appropriately select between protocols that offer =
equivalent features. This design permits evolution of the transport =
protocols and functions without affecting the programs using the =
system.<br class=3D""><br class=3D"">* Applications using the TAPS API =
are REQUIRED to be robust to the automated selection provided by TAPS, =
including the possibility to express requirements and preferences that =
constrain the choices that can be made by the system.&nbsp; In normal =
use, TAPS Systems are RECOMMENDED to be designed so that all selection =
decisions result in consistent choices for the same network conditions =
when they have the same set of preferences. This is intended to provide =
predictable outcomes to the application using the transport service.<br =
class=3D""><br class=3D"">* Applications using TAPS MAY explicitly =
require or prevent the use of specific transport features (and transport =
protocols) using the "REQUIRED" and "PROHIBIT" preferences. This allows =
an application to constrain the set of protocols and features that will =
be selected for the transport service. It is RECOMMENDED that the =
default usage by applications does not unecessarily restrict this =
selection, so that the system can make informed choices (e.g., based on =
the availability of interfaces or set of transport protocols available =
for the specified remote endpoint).<br class=3D""><br class=3D""><br =
class=3D"">---<br class=3D""><br class=3D"">After thought, here is my =
specific poposal of what to do next:<br class=3D""><br class=3D"">(a) I =
suggest we group all the requirements on architecture as short one or =
two sentence blocks (preferably as a bullet or definition list) =
collected into a single subsection, so they are easy to find and read =
and we say that these are the key architectural requirements. I suggest =
we insert this new requirements text either their own section, or in =
section 1.3 (although I am open to other places where we can call-out =
the architectural requirements).<br class=3D""><br class=3D"">(b) We =
need to decide if these are architectural requirements and if there are =
more or less in total. I am of course open to more refined =
wording:-).<br class=3D""><br class=3D"">(c) We could also explicitly =
say there are additional requirements in racing&nbsp; in section XX.<br =
class=3D""><br class=3D"">(d) If this plan seems appropriate, I would =
then suggest to use lower case within the remainder of document (we =
could refer to the requirements subsection, if we thought necessary).<br =
class=3D""><br class=3D"">Thoughts please, but review now completed!<br =
class=3D""><br class=3D"">Gorry<br class=3D""><br class=3D""><br =
class=3D"">---<br class=3D""><br class=3D""><br class=3D"">Additional =
Language NiT:<br class=3D""><br class=3D"">I think the word /assumes/ is =
not a good choice of word.<br class=3D""><br class=3D"">OLD:<br =
class=3D""><br class=3D"">and it assumes an implementation that can use =
multiple IP addresses, multiple protocols, multiple paths, and provide =
multiple application streams<br class=3D""><br class=3D"">NEW:<br =
class=3D""><br class=3D"">and it can provide benefit when an =
implementation can use multiple IP addresses, multiple protocols, =
multiple paths, and provide multiple application streams.<br =
class=3D""><br =
class=3D"">_______________________________________________<br =
class=3D"">Taps mailing list<br class=3D""><a =
href=3D"mailto:Taps@ietf.org" class=3D"">Taps@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/taps<br =
class=3D""></div></div></blockquote></div><br class=3D""><div class=3D"">
<div dir=3D"auto" style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, =
0); letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div>AVE!</div><div>&nbsp; &nbsp;Philipp S. =
Tiesel</div><div><br class=3D""></div><div>--&nbsp;&nbsp;<br =
class=3D"">Philipp S. Tiesel<br class=3D""><a =
href=3D"https://philipp.tiesel.net/" =
class=3D"">https://philipp.tiesel.net/</a></div></div>
</div>


<br class=3D""></div></body></html>=

--Apple-Mail=_53F324BB-F7F2-48AC-B6F7-40223CEAC3E6--


From nobody Thu Mar 26 09:19:02 2020
Return-Path: <session-request@ietf.org>
X-Original-To: taps@ietf.org
Delivered-To: taps@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 09D253A08EB; Thu, 26 Mar 2020 09:18:48 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Meeting Session Request Tool <session-request@ietf.org>
To: <session-request@ietf.org>
Cc: magnus.westerlund@ericsson.com, taps@ietf.org, aaron.falk@gmail.com, taps-chairs@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.123.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <158523952800.4425.12807933272220126809@ietfa.amsl.com>
Date: Thu, 26 Mar 2020 09:18:48 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/gxORbheNnNootScWVv1_UYmmQlA>
Subject: [Taps] taps - New Interim Meeting Request
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 26 Mar 2020 16:19:00 -0000

A new interim meeting request has just been submitted by Aaron Falk.

This request requires approval by the Area Director of the Transport Area

The meeting can be approved here: 
https://datatracker.ietf.org/meeting/interim/request/interim-2020-taps-01



---------------------------------------------------------
Working Group Name: Transport Services
Area Name: Transport Area
Session Requester: Aaron Falk

Meeting Type: Virtual Meeting

Session 1:

Date: 2020-04-17
Start Time: 12:00 America/New_York
Duration: 02:00
Remote Participation Information: https://ietf.webex.com/meet/taps
Agenda Note: Meeting Notes: http://etherpad.tools.ietf.org:9000/p/notes-taps-interim-2020-apr

---------------------------------------------------------



From nobody Thu Mar 26 15:12:39 2020
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: taps@ietf.org
Delivered-To: taps@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DB0EF3A0CC0; Thu, 26 Mar 2020 15:12:14 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IESG Secretary <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Cc: taps@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.123.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <158526073481.4541.254991955072064214@ietfa.amsl.com>
Date: Thu, 26 Mar 2020 15:12:14 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/Z8Rw-Gy3ZSqS2v8GORuctmyT8Z8>
Subject: [Taps] Transport Services (taps) WG Virtual Meeting: 2020-04-17
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 26 Mar 2020 22:12:32 -0000

The Transport Services (taps) Working Group will hold
a virtual interim meeting on 2020-04-17 from 12:00 to 14:00 America/New_York (16:00 to 18:00 UTC).

Agenda:
Draft Agenda

1. Normative language in -arch
2. Issue review

Information about remote participation:
https://ietf.webex.com/meet/taps

Meeting Notes: http://etherpad.tools.ietf.org:9000/p/notes-taps-interim-2020-apr


From nobody Fri Mar 27 01:02:18 2020
Return-Path: <tapsbot@magpie.corvid.ch>
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 1F6B03A0F0F for <taps@ietfa.amsl.com>; Fri, 27 Mar 2020 01:02:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham 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 Xnhb9BDzzHB2 for <taps@ietfa.amsl.com>; Fri, 27 Mar 2020 01:02:16 -0700 (PDT)
Received: from magpie.corvid.ch (magpie.corvid.ch [46.101.110.207]) (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 CF9993A0DC5 for <taps@ietf.org>; Fri, 27 Mar 2020 01:02:15 -0700 (PDT)
Received: from [127.0.0.1] (helo=magpie.corvid.ch) by magpie.corvid.ch with esmtp (Exim 4.92) (envelope-from <tapsbot@magpie.corvid.ch>) id 1jHjuN-0002lW-Cs for taps@ietf.org; Fri, 27 Mar 2020 08:00:03 +0000
Content-Type: multipart/alternative; boundary="===============6376658890027567817=="
MIME-Version: 1.0
From: TAPS WG status robot <tapsbot@magpie.corvid.ch>
To: taps@ietf.org
Message-Id: <E1jHjuN-0002lW-Cs@magpie.corvid.ch>
Date: Fri, 27 Mar 2020 08:00:03 +0000
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/K6UFxhvkSKY0pt5fe_OABtXS29A>
Subject: [Taps] Weekly github digest (TAPS GitHub Activity Digest)
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: Fri, 27 Mar 2020 08:02:17 -0000

--===============6376658890027567817==
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"; format="flowed"




Issues
------
* ietf-tapswg/api-drafts (+2/-0/=F0=9F=92=AC0)
  2 issues created:
  - Architecture: normative arch language (by gorryfair)
    https://github.com/ietf-tapswg/api-drafts/issues/519 [Architecture] =

  - Architecture NiT: /assumes/ (by gorryfair)
    https://github.com/ietf-tapswg/api-drafts/issues/518 =





Repositories tracked by this digest:
-----------------------------------
* https://github.com/ietf-tapswg/api-drafts

--===============6376658890027567817==
Content-Type: text/html; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

<!doctype html>
<html lang=3D"en">
<head>
<meta charset=3D"utf-8">
<title>Weekly github digest (TAPS GitHub Activity Digest)</title>
<style>
body { font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;=
 font-size: 14px; }
h2 { margin-top: 3em; color: #A52A2A; font-style: italic; font-weight: norm=
al; }
h3 { margin-bottom:0; margin-top: 2em; font-size: 1.2em; }
h1+h2 { margin-top: 1em; }
a { color: #bb6219; text-decoration: none; }
li { margin-bottom: .35em; }
.repos { margin-bottom: 0; margin-top:0; line-height: 1.2; }
.new { color: red; }
.label { display: inline;
	padding: .2em .6em .3em;
	font-size: 75%;
	font-weight: 700;
	line-height: 1;
	color: #fff;
	text-align: center;
	white-space: nowrap;
	vertical-align: baseline;
	border-radius: .25em;
}
</style>
</head>

<body>
<h1>Friday March 27, 2020</h1>


<h2>Issues</h2>

<h3>ietf-tapswg/api-drafts (+2/-0/=F0=9F=92=AC0)</h3>
  <p class=3D"new">2 issues created:</p>
  <ul>
  <li>#519 <a href=3D"https://github.com/ietf-tapswg/api-drafts/issues/519"=
>Architecture: normative arch language</a> (by gorryfair) <span class=3D"la=
bel" style=3D"background-color: #fbca04; color: #000000">Architecture</span=
> </li>
  =

  <li>#518 <a href=3D"https://github.com/ietf-tapswg/api-drafts/issues/518"=
>Architecture NiT: /assumes/</a> (by gorryfair) </li>
  </ul>






<h2>Repositories tracked by this digest:</h2>
<ul class=3D"repos">
  <li><a href=3D"https://github.com/ietf-tapswg/api-drafts">https://github.=
com/ietf-tapswg/api-drafts</a></li>
  </ul>
</body>
</html>

--===============6376658890027567817==--


From nobody Sat Mar 28 15:55:16 2020
Return-Path: <noreply@ietf.org>
X-Original-To: taps@ietf.org
Delivered-To: taps@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EEF5A3A07B3; Sat, 28 Mar 2020 15:55:10 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Murray Kucherawy via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-taps-transport-security@ietf.org, taps-chairs@ietf.org, taps@ietf.org, Philipp Tiesel <philipp@tiesel.net>, caw@heapingbits.net
X-Test-IDTracker: no
X-IETF-IDTracker: 6.123.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Murray Kucherawy <superuser@gmail.com>
Message-ID: <158543611048.7466.9233997230237897172@ietfa.amsl.com>
Date: Sat, 28 Mar 2020 15:55:10 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/0704s-yIovPvsJwDjwbUSJ_L12I>
Subject: [Taps] Murray Kucherawy's Yes on draft-ietf-taps-transport-security-11: (with COMMENT)
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 28 Mar 2020 22:55:11 -0000

Murray Kucherawy has entered the following ballot position for
draft-ietf-taps-transport-security-11: Yes

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-taps-transport-security/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

This is a really useful summary, especially for people without deep background
in transport security.  It'll make a great reference document.

Section 4.3:
* "Specific" should be "Specifically"
* "They have a dependencies on" -- should be "dependency"



