See inline below: -----Original Message-----
> A communication between two end points traverses multiple administrative domains. Yes, but transport protocols don't interact with AD properties per se. > The TSV-Area AD should have the knowledge of BGP, the domain demarcation > across different administrative domains. Can you give an example of a case where this has been useful? [Linda] Some congestion work done or proposed in TSV area assumed nodes in the network actually "see" the data flows between end points and do something about it. But the reality is that most nodes in the core only see the aggregated traffic, don't have visibility of the end point traffic. > -----Original Message----- > From: tsv-area [mailto:[email protected]] On Behalf Of Joe > Touch > Sent: Friday, May 29, 2015 3:42 PM > To: John Leslie > Cc: [email protected] > Subject: Re: FYI draft text desired expertise TSV AD (NOMCOM 2015 > cycle) > > IMO, these are as critical to many transport discussions as knowledge of > congestion control. > > Joe > > > On 5/29/2015 1:38 PM, John Leslie wrote: >> Joe Touch <[email protected]> wrote: >>> >>> 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 >> >> All of these are "nice to have" -- understanding of MTU is >> especially nice-to-have. >> >> But none of them are critical to a TSV AD doing his/her job. >> >> IMHO, of course. >> >> YMMV... >> >> -- >> John Leslie <[email protected]> >> >
