The following errata report has been submitted for RFC8095,
"Services Provided by IETF Transport Protocols and Congestion Control
Mechanisms".
--
You may review the report below and at:
http://www.rfc-editor.org/errata/eid5285
+1
On Mar 12, 2018, 8:12 AM -0700, Kyle Rose , wrote:
> In the future, can we add TLS as a P1 conflict for TAPS? There are a lot of
> folks who want to be in both, maybe especially now that our charter has
> expanded.
>
> Kyle
>
>
> > On Mon, Mar 12, 2018 at 10:53 AM,
In the future, can we add TLS as a P1 conflict for TAPS? There are a lot of
folks who want to be in both, maybe especially now that our charter has
expanded.
Kyle
On Mon, Mar 12, 2018 at 10:53 AM, Christopher Wood <
christopherwoo...@gmail.com> wrote:
> Hi Zahed, Aaron,
>
> Would it be
The following errata report has been verified for RFC8095,
"Services Provided by IETF Transport Protocols and Congestion Control
Mechanisms".
--
You may review the report below and at:
http://www.rfc-editor.org/errata/eid5285
Ups… I’ll go ahead and verify this one!
> Am 12.03.2018 um 09:04 schrieb Gorry Fairhurst :
>
> This Errata seems valid. Sorry that was not spotted.
>
> Gorry
>
> On 12/03/2018, 03:54, RFC Errata System wrote:
>> The following errata report has been submitted for RFC8095,
Hi Zahed, Aaron,
Would it be possible to move the talk for
draft-pauly-taps-transport-security to the start of Wednesday's
meeting? There are talks in the tail end of the conflicting TLS
session that I need to attend.
Thanks,
Chris
On Tue, Mar 6, 2018 at 8:32 AM, Anna Brunstrom
This Errata seems valid. Sorry that was not spotted.
Gorry
On 12/03/2018, 03:54, RFC Errata System wrote:
The following errata report has been submitted for RFC8095,
"Services Provided by IETF Transport Protocols and Congestion Control
Mechanisms".
--
You