Call for Comment: <draft-iab-path-signals-02> (Transport Protocol Path Signals)
IAB Executive Administrative Manager <execd@iab.org> Wed, 28 November 2018 21:55 UTC
Return-Path: <execd@iab.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 40F1013104D for <ietf-announce@ietf.org>; Wed, 28 Nov 2018 13:55:23 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IAB Executive Administrative Manager <execd@iab.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: Call for Comment: <draft-iab-path-signals-02> (Transport Protocol Path Signals)
X-Test-IDTracker: no
X-IETF-IDTracker: 6.89.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: iab@iab.org, architecture-discuss@ietf.org
Message-ID: <154344212322.13692.8912412627900013388.idtracker@ietfa.amsl.com>
Date: Wed, 28 Nov 2018 13:55:23 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/tnVyDMGgDiM8CUMrKoNhPSKnCEk>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2018 21:55:23 -0000
This is an announcement of an IETF-wide Call for Comment on draft-iab-path-signals-02. The document is being considered for publication as an Informational RFC within the IAB stream, and is available for inspection at: <https://datatracker.ietf.org/doc/draft-iab-path-signals/> The Call for Comment will last until 2018-12-25. Please send comments to architecture-discuss@ietf.org and iab@iab.org. Abstract This document discusses the nature of signals seen by on-path elements examining transport protocols, contrasting implicit and explicit signals. For example, TCP's state mechanics uses a series of well-known messages that are exchanged in the clear. Because these are visible to network elements on the path between the two nodes setting up the transport connection, they are often used as signals by those network elements. In transports that do not exchange these messages in the clear, on-path network elements lack those signals. Often, the removal of those signals is intended by those moving the messages to confidential channels. Where the endpoints desire that network elements along the path receive these signals, this document recommends explicit signals be used.
- Call for Comment: <draft-iab-path-signals-02> (Tr… IAB Executive Administrative Manager