Transport protocols and bulk file transfer

[Larry Dunn <>]

Steve,
I'm up for the call - but my notes show it was cancelled by Susan E. in 
3/8/2012 email.
Clearly we can just declare it "back on" - I just want to make sure
that her email did not also kill the phone bridge...

Susan?

Larry
--

On Apr 18, 2012, at 9:11 PM, Steven Senger wrote:

> We will have our monthly call this friday Apr 20 at 1 pm EDT. Call 
> information is below. As we discussed last time we will review the various 
> issue items posted to the mailing list (copied below) with the goal of 
> identifying directions for the working group. 
> 
> - steve
> 
> --------------------
> The dial-in info below will work for all scheduled calls for this group, 
> even when we have to change the date/time.
> 
> To join both the web and audio conference (recommended), click here:
> https://edial.internet2.edu/call/0154927
> If you only want to participate in the audio conference, you may dial in 
> with the following numbers:
> Call: +1-734-615-7474 (PSTN CALL-OUT DOES NOT WORK) or +1-866-411-0013 
> (toll free US/Canada Only)
> Enter access code: 0154927
> -----------------
> 
> On Mar 23, 2012, at 1:14 PM, Scott Brim wrote:
> 
>> Here are some top-of-mind issues.  For my slide I'm mostly interested in
>> the middle level of indentation, not the specific examples.
>> 
>> Enhancing performance:
>> 
>>  We can't have helper nodes like Phoebus everywhere, particularly
>>  when crossing multiple networks.  Should we be considering more
>>  end-to-end approaches?  Examples:
>> 
>>    - TCP tuning (Hamilton Institute, Multipath TCP?)
>>    - Per-flow in-band signaling
>>    - Per-flow in-band signaling with help, e.g. Larry Roberts's
>>      flow-state-aware forwarding.
>>    - SCTP (in endpoints, independent or with GridFTP, but also at the
>>      net edge in Phoebus or Cisco NCE?
>>    - Enhancements to GridFTP in general?
>>    - Other services besides moving files.
>> 
>>    ... but the main question is whether endpoint-based approaches
>>    belong on our agenda, or have they been explored and determined not
>>    to be as productive in any situation.
>> 
>>  Information exchange between functional elements so that they can use
>>  the network better.  Examples:
>> 
>>    - Phoebus does this by exchanging information with peers, right?
>>    - ALTO and ALTO extensions
>>    - Leaking routing information from internal & external routing
>>    - SDN for some value of D
>> 
>> Performance monitoring:
>> 
>>  PerfSonar futures?
>>  Other?
>> 
>> Deployment:
>> 
>>  This group has an operational aspect too, not just making
>>  recommendations.  Once we have research we like, we need to encourage
>>  getting it hardened and production-ready.
>> 
>>    - Phoebus is an obvious one.  Anything else?
>> 
>> Thanks ... Scott
> 
> 
> On Mar 23, 2012, at 4:44 PM, Jason Zurawski wrote:
> 
>> All;
>> 
>> On 3/23/12 2:14 PM, thus spake Scott Brim:
>>> Here are some top-of-mind issues.  For my slide I'm mostly interested in
>>> the middle level of indentation, not the specific examples.
>>> 
>>> Enhancing performance:
>>> 
>>>   We can't have helper nodes like Phoebus everywhere, particularly
>>>   when crossing multiple networks.  Should we be considering more
>>>   end-to-end approaches?  Examples:
>>> 
>>>     - TCP tuning (Hamilton Institute, Multipath TCP?)
>> 
>> Martin may chime in more, but one of the selling points of Phoebus was to 
>> avoid the dark art of TCP tuning.  Its 'easier' on windows/OX, but near 
>> impossible on the latest version of windows.
>> 
>> In any event, this is recommendation #1 for enabling data intensive 
>> science.
>> 
>>>     - Per-flow in-band signaling
>>>     - Per-flow in-band signaling with help, e.g. Larry Roberts's
>>>       flow-state-aware forwarding.
>>>     - SCTP (in endpoints, independent or with GridFTP, but also at the
>>>       net edge in Phoebus or Cisco NCE?
>>>     - Enhancements to GridFTP in general?
>>>     - Other services besides moving files.
>>> 
>>>     ... but the main question is whether endpoint-based approaches
>>>     belong on our agenda, or have they been explored and determined not
>>>     to be as productive in any situation.
>>> 
>>>   Information exchange between functional elements so that they can use
>>>   the network better.  Examples:
>>> 
>>>     - Phoebus does this by exchanging information with peers, right?
>>>     - ALTO and ALTO extensions
>>>     - Leaking routing information from internal&  external routing
>>>     - SDN for some value of D
>>> 
>>> Performance monitoring:
>>> 
>>>   PerfSonar futures?
>> 
>> Periscope - I would welcome the IU/UDel folks to explain the crucial 
>> improvements.
>> 
>>>   Other?
>> 
>> - What can a SDN tell you about its performance, and what do we want to 
>> know about an SDN's performance.
>> 
>>> Deployment:
>>> 
>>>   This group has an operational aspect too, not just making
>>>   recommendations.  Once we have research we like, we need to encourage
>>>   getting it hardened and production-ready.
>>> 
>>>     - Phoebus is an obvious one.  Anything else?
>> 
>> - Monitoring to go w/ Phoebus
>> - The elimination of tools like SCP (or at a bare minimum, getting openssh 
>> to accept the patch from PSC...).
>> 
>> Thats about all I can muster late on a Friday.
>> 
>> Thanks;
>> -jason
>