Re: [Taps] RFC 8095 on Services Provided by IETF Transport Protocols and Congestion Control Mechanisms

"Aaron Falk" <aaron.falk@gmail.com> Tue, 07 March 2017 22:23 UTC

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 39C7A129625 for <taps@ietfa.amsl.com>; Tue, 7 Mar 2017 14:23:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 jq3a5cyUFZSs for <taps@ietfa.amsl.com>; Tue, 7 Mar 2017 14:22:59 -0800 (PST)
Received: from mail-qk0-x22e.google.com (mail-qk0-x22e.google.com [IPv6:2607:f8b0:400d:c09::22e]) (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 44ECB12961C for <taps@ietf.org>; Tue, 7 Mar 2017 14:22:59 -0800 (PST)
Received: by mail-qk0-x22e.google.com with SMTP id 1so29418966qkl.3 for <taps@ietf.org>; Tue, 07 Mar 2017 14:22:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:subject:date:message-id:in-reply-to:references:mime-version :content-transfer-encoding; bh=DbGzVRfoir25qunYwkDLJ4jl0ueV7mD/zkE2hqMOlaE=; b=S4BtnaCaMQ1dgned7Kf3wt2V/cFB08SXD8X4eKsY+GfKY/FyF7bUeHjTTFEKdAuGcp LAMd4Jp33boH+3wsuYM9KfB1GRYNarsa7aklapyKoIoZsp7VSYeSTPujlQro+J6wfA/v iwOYcL0HHm7AuJyYcH44yXvO7sRIgHKzWISY84znb1Ytk14dcSJ+ZmbBJ5mQkJQE929S R+77yJ46HAcxXqrQgAjlN4tNrUIVrVwcQKxuSJOBrWFT73oEH/mI6ORMz14zchFwrLT9 iP4rbvgGr8ulCXHU3rZqSjRivX785F3IqkWeWcPNKv4F4yDKFX0Sa6yzSqdl1R7gzzLd uR5g==
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:in-reply-to :references:mime-version:content-transfer-encoding; bh=DbGzVRfoir25qunYwkDLJ4jl0ueV7mD/zkE2hqMOlaE=; b=UsJ6kTQ9bdnR1QdL8cJwoXDZJL5yAlk2f267XOKsWrFPuxlF4Kno923YcOI4vl7NoO aqqC4QxSZS2dvJ13qXMAdJfXwoAMHaRpdq6PVHQBno9o0kq/SzvT7ds82n9nSMyvRnwB glPFCRAWPkKWjv8U5TQwWJPP/Wnq8JjIiYe3GzvVAiuC1zKjKGV8qDGVa7JRRFSXtwI0 WQDMa93+wEGMU5oL9q+OdalyPgz+s/abp6bdQ8np1FELRSi3voNn0uOtw1WeZsSEXvjU uoLq79V1mKbta+pP8HSeTphBt6Lne+OKE/giOs01hlp/BAfC90myMx3Rj3QtwHc633o6 Y2Jw==
X-Gm-Message-State: AFeK/H0TkHAD3Vy+7cQqj/ON9pLsxkqzT7ehPfVQJCQxPjKx7ghK4nMxX4WR6N78dQkqYw==
X-Received: by 10.55.94.6 with SMTP id s6mr3602213qkb.166.1488925378338; Tue, 07 Mar 2017 14:22:58 -0800 (PST)
Received: from [172.19.33.209] ([2001:4878:8000:60:fda8:c06f:d163:83dd]) by smtp.gmail.com with ESMTPSA id m12sm883402qtm.45.2017.03.07.14.22.57 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 Mar 2017 14:22:57 -0800 (PST)
From: Aaron Falk <aaron.falk@gmail.com>
To: taps WG <taps@ietf.org>, Gorry Fairhurst <gorry@erg.abdn.ac.uk>, Brian Trammell <ietf@trammell.ch>, Mirja Kühlewind <mirja.kuehlewind@tik.ee.ethz.ch>
Date: Tue, 07 Mar 2017 17:22:57 -0500
Message-ID: <E8BD8D6D-E9D3-4744-92FB-0F411830BE4A@gmail.com>
In-Reply-To: <20170307221838.0675EB819B9@rfc-editor.org>
References: <20170307221838.0675EB819B9@rfc-editor.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.6r5356)
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/Wv5rdUuBRSuUQtdiHBHbC3RwrNc>
Subject: Re: [Taps] RFC 8095 on Services Provided by IETF Transport Protocols and Congestion Control Mechanisms
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Discussions on Transport Services <taps.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/taps>, <mailto:taps-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/taps/>
List-Post: <mailto:taps@ietf.org>
List-Help: <mailto:taps-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/taps>, <mailto:taps-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Mar 2017 22:23:01 -0000

TAPS doc 1 published.  Thank you, Brian, Mirja, & Gorry!

—aaron

On 7 Mar 2017, at 17:18, rfc-editor@rfc-editor.org wrote:

> A new Request for Comments is now available in online RFC libraries.
>
>
>         RFC 8095
>
>         Title:      Services Provided by IETF Transport
>                     Protocols and Congestion Control Mechanisms
>         Author:     G. Fairhurst, Ed.,
>                     B. Trammell, Ed.,
>                     M. Kuehlewind, Ed.
>         Status:     Informational
>         Stream:     IETF
>         Date:       March 2017
>         Mailbox:    gorry@erg.abdn.ac.uk,
>                     ietf@trammell.ch,
>                     mirja.kuehlewind@tik.ee.ethz.ch
>         Pages:      54
>         Characters: 126843
>         Updates/Obsoletes/SeeAlso:   None
>
>         I-D Tag:    draft-ietf-taps-transports-14.txt
>
>         URL:        https://www.rfc-editor.org/info/rfc8095
>
>         DOI:        10.17487/RFC8095
>
> This document describes, surveys, and classifies the protocol
> mechanisms provided by existing IETF protocols, as background for
> determining a common set of transport services.  It examines the
> Transmission Control Protocol (TCP), Multipath TCP, the Stream
> Control Transmission Protocol (SCTP), the User Datagram Protocol
> (UDP), UDP-Lite, the Datagram Congestion Control Protocol (DCCP), the
> Internet Control Message Protocol (ICMP), the Real-Time Transport
> Protocol (RTP), File Delivery over Unidirectional Transport /
> Asynchronous Layered Coding (FLUTE/ALC) for Reliable Multicast, NACK-
> Oriented Reliable Multicast (NORM), Transport Layer Security (TLS),
> Datagram TLS (DTLS), and the Hypertext Transport Protocol (HTTP),
> when HTTP is used as a pseudotransport.  This survey provides
> background for the definition of transport services within the TAPS
> working group.
>
> This document is a product of the Transport Services Working Group of 
> the IETF.
>
>
> INFORMATIONAL: This memo provides information for the Internet 
> community.
> It does not specify an Internet standard of any kind. Distribution of
> this memo is unlimited.
>
> This announcement is sent to the IETF-Announce and rfc-dist lists.
> To subscribe or unsubscribe, see
>   https://www.ietf.org/mailman/listinfo/ietf-announce
>   https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
>
> For searching the RFC series, see https://www.rfc-editor.org/search
> For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
>
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to rfc-editor@rfc-editor.org.  
> Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
>
>
> The RFC Editor Team
> Association Management Solutions, LLC
>
>
> _______________________________________________
> Taps mailing list
> Taps@ietf.org
> https://www.ietf.org/mailman/listinfo/taps