Hi, Martin,
On 6/1/2015 10:44 PM, Martin Stiemerling wrote:
> 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.
I really wish there were. My point is that "transport" is more than
"congestion and flow control".
To say the above in a more generic format:
- connection state coordination
- interaction with path properties
- interaction of with router data plane
- error detection and recovery
- data boundary coordination
The current list states the same concept too many different ways and can
be condensed:
WAS:
- congestion, control loops and hysteresis,
flow control, queuing and latency
MAYBE:
- congestion and flow control
WAS:
- transport connection and reliability issues
IMO SHOULD BE:
- connection state coordination
- error detection and recovery
WAS:
- interactions with the network layer,
the application layer, and middleboxes.
(IMO OK)
The full list, IMO, should be (in no particular order):
- connection state coordination
- interaction with path properties
- interaction of with router data plane
- error detection and recovery
- data boundary coordination
- congestion and flow control
- interactions with the network layer,
the application layer, and middleboxes
IMO that should appear in one paragraph, not split across two paragraphs
that are not adjacent.
Finally, the last paragraph should compress down the congestion/flow
control issues to one item (not 4) and should also specifically list MTU
interactions and ICMP interactions.
Joe
