[Tsv-art] Comments requested on DRAFT DRAFT DRAFT Transport AD position description
Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Fri, 01 June 2018 01:25 UTC
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: tsv-art@ietfa.amsl.com
Delivered-To: tsv-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A3221241F5; Thu, 31 May 2018 18:25:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 OPdwjDsnyFy2; Thu, 31 May 2018 18:25:26 -0700 (PDT)
Received: from mail-yb0-x22b.google.com (mail-yb0-x22b.google.com [IPv6:2607:f8b0:4002:c09::22b]) (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 E8F7D1200E5; Thu, 31 May 2018 18:25:25 -0700 (PDT)
Received: by mail-yb0-x22b.google.com with SMTP id o14-v6so8234699ybq.3; Thu, 31 May 2018 18:25:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=GtRc9qldph6eQagfNJaIexLzDFlKusOX8xOcaX/P000=; b=klfJvQjqHvrERin+u9Z0CG7jXpdjrjfwdEgk/J70mDaqHGgRAM3vXpvDt02KHNorUq EoFlgrN0jKmFMKVYG7OBSvK8dFaIOSfU3DQ6WKmT2vwlt2vxZrXYssbGL+QxxB+1GDTT 6XsIun1OJqNwOpIlO96CEKaEmF0qCr59dHrgEUepC21uMBylOHUpuRNjNiaYb60+1sWS S58beJKqrF+co3XAhfg0xLidOKcMJ2stusGkCelIcjVVTjMtXQ1uF56EYgOzzZpT9kzw r+gFWwwdjvSDTIcvYwpXC/RS8If+978rpT+3MSkEnK/GOn455ftneyH8bYPQHf/NQ0nF nUeQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=GtRc9qldph6eQagfNJaIexLzDFlKusOX8xOcaX/P000=; b=Nz0DXwCzKhCKi8FnBYYFzNds57G/k++UUHyqDrxa00wbfzgu/tOjC2X5dSoWCVgzTY v2ak1cZMOvQ/3giUdD1kvyDRIccrdOeVG3SacaWbMdjUoB2uVMXQQbmT56lpDfFTbJY3 hxDJFTrQuq06NamhdIg12YbP1z+WJuacgFfTo9X/K2sn1dbiLj1z0fFeHUxQ75LLQzkm 8HK5W77B/eB+aD6/T52aYSyCLvCMk1zT8zHj6beTKcLdyXaU411cHpK8v+rg1Z8fNsQr G/UMKHvr7X3NEWbfuJqgKec248aSRVf0YV7TzBWb0rr54ZcZRFMwoD+06Fg08T1CqK7l DovA==
X-Gm-Message-State: ALKqPwcgrg9pWGdkhAYQoiQBrt6KI2sJJkePez0h/APFi3mCAVRnPQze oSGi6eXavmCdSa/4Xba90bty8AyXJhpPfdkdcEPOlg==
X-Google-Smtp-Source: ADUXVKK1g87qOqLE4klwUS93CZ+NDbTiQQyp/YF4tIcwb9uq4mLH/3drcl8/KhIih94gbZUEDZ9by35WLttQcV+UZAw=
X-Received: by 2002:a25:4d57:: with SMTP id a84-v6mr5157266ybb.286.1527816324711; Thu, 31 May 2018 18:25:24 -0700 (PDT)
MIME-Version: 1.0
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Thu, 31 May 2018 20:25:13 -0500
Message-ID: <CAKKJt-eC7zQ4_w9FQJbvW5G47cdrejYPJgu2EvrBvS5sK-+CeA@mail.gmail.com>
To: tsvwg-chairs <tsvwg-chairs@ietf.org>, tsv-art@ietf.org, Tsv-triage@ietf.org
Cc: Mirja Kuehlewind <ietf@kuehlewind.net>, Adam Roach <adam@nostrum.com>
Content-Type: multipart/alternative; boundary="000000000000510d3e056d8a754b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsv-art/v6du8H8Snb0gFTCKd6GqJMqZ9-Y>
Subject: [Tsv-art] Comments requested on DRAFT DRAFT DRAFT Transport AD position description
X-BeenThere: tsv-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Transport Area Review Team <tsv-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsv-art/>
List-Post: <mailto:tsv-art@ietf.org>
List-Help: <mailto:tsv-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Jun 2018 01:25:29 -0000
Dear Transport Area Chairs, Area Review Team, and Triage Team (basically, anyone we invite to the TSV dinner on Monday nights) ... Mirja and I are working on an updated Transport AD position description that Nomcom will use to select a candidate to replace me next March. She and I are still typing, but we'd like to get any comments that pop into your mind by next Thursday, June 7, so that Mirja and I can include your thoughts in our input, which we'd like to finalize by next Friday, June 8. Please note that this is the TSV-specific part of the description. The IESG is making minimal changes to the generic AD description from last year, which you can see at https://datatracker.ietf.org/nomcom/2017/expertise/, so if something is in the generic description, it won't be in the TSV-specific description. If you'd like to see what the TSV-specific part of the description looked like last year, it's also at that link, but we've changed too much for diffs to be useful. If you Google Doc, a link for comments is at https://docs.google.com/document/d/17LxDRzMmux0sOztCajSKYBxBB7zXEkijrPItsUF9XOg/edit?usp=sharing . If you don't, the text as of this moment follows. Thanks, Spencer, who thinks he is morally obligated to serve on the TSV Triage team, because that seems to be where all the TSV ADs end up sooner or later ... Transport Together, the Transport Area Directors are expected to effectively charter, manage and review current and new transport work, including congestion signaling and reporting, Quality of Service (QoS, including Differentiated Services and reservation signaling), and congestion control for unresponsive flows, NAT regularization and specification, storage protocols for the Internet, performance metrics for Internet paths, experimentation with congestion control schemes developed in the IRTF, unicast and multipath extensions to existing transport protocols, and congestion control algorithms for interactive real time media. Together, the Transport ADs should have a broad understanding of core end-to-end transport topics and how transport technologies interact with network-layer technologies and protocols, and with various application-layer protocols, but they are not expected to be experts on all or even most of these topics, Rather, they are expected to work well with Transport Area participants who are experts, and to have enough familiarity with the principles involved to exercise their own good judgment about what should be done and why. Together, the Transport ADs are expected to organize their workload, e.g., document review, email discussions as follow-up of document review, IESG emails, WG management, etc, in such a way that the average workload for each AD is about 15 to 20 hours per week. Transport ADs manage and recruit volunteers in order to maintain the Transport Area Document Review Triage Team (“TSV triage team”) and the Transport Area Review Team (TSV-ART).The TSV triage team provides support for the ADs by assigning document reviews to TSV-ART, and TSV-ART provides reviews on request and during Last Call that can be used by the Transport ADs as input for their ballot positions. The Transport ADs may delegate any tasks that can be delegated, but the ADs themselves still have ultimate responsibility to ensure that transport considerations are appropriately taken into account during IESG Evaluation. Based on current discussions about ossification of transport protocols and stack evolution, basic knowledge about security and privacy, encapsulation and tunneling, and higher layer protocols including web technologies as well as having an overall architectural view can be of value. Because Transport Area working groups often have common interests with IRTF research groups, especially ICCRG, MAPRG, and PANRG, familiarity with these research groups is helpful. Having at least one Transport Area AD with some background in the broader research community is also helpful.
- [Tsv-art] Comments requested on DRAFT DRAFT DRAFT… Spencer Dawkins at IETF