Skip to Content.
Sympa Menu

transport - [transport] a quick list of issues

Subject: Transport protocols and bulk file transfer

List archive

[transport] a quick list of issues


Chronological Thread 
  • From: Scott Brim <>
  • To: Transport WG <>
  • Subject: [transport] a quick list of issues
  • Date: Fri, 23 Mar 2012 14:14:06 -0400
  • Organization: Internet2

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



Archive powered by MHonArc 2.6.16.

Top of Page