Hi Joe,
Am 29.05.15 um 20:11 schrieb Joe Touch:
Hi, all,
I don't disagree with anything in the text, but it seems to omit a few
key areas that I think are also aspects of transports besides
flow/congestion control-ish. These might also be listed among the
topics/examples:
- segmentation, MTU, and message boundary issues
- connection state management
- deep-packet inspection interactions
- interactions with timing and latency
- end-to-end error detection and correction
I fully agree that the set of service TSV ADs must know about this, but
I wonder if this level of detail is needed in the desired expertise
description for the NOMCOM.
The current text aims at keeping the balance between naming a number of
must haves, but is deliberately not going into more details.
Is there a good term that would cover most of the points, i.e., the text
says core transport topics, but indeed lacks an item that covers the
transport 101 points, like MTU issues.
Thanks,
Martin
Joe
On 5/29/2015 1:09 AM, Eggert, Lars wrote:
Looks spot on
On 2015-5-29, at 07:42, Martin Stiemerling <[email protected]> wrote:
Dear all,
Spencer and I have finished editing the draft text for the desired expertise
for the TSV AD in the NOMCOM 2015 cycle.
This is currently under discussion in the IESG and not yet the final text which
will be sent to the NOMCOM
It is available here:
https://trac.tools.ietf.org/group/iesg/trac/wiki/TransportExpertise
Let Spencer and me know your comments about this until June 3rd, 2015, 8pm CEST.
Thanks,
Spencer and Martin
