Transport protocols and bulk file transfer

[stanislav shalunov <>]

Introductions -- 5 minutes.

Agenda bashing -- 5 minutes.

Tentative work plan -- 5 minutes.

    The time line for building a prototype and the working tool.

Prospective applications -- 15 minutes.

    Do you have an application that could use bulk file transfer?
    What are the sources and consumers of data (other than simple disk
    files) for applications?

Mode of participation -- 15 minutes.

    Can you contribute code?  Ideas?  Advice?  Equipment?  Data
    collection resources?  Testing resources?

Problem factorization -- 15 minutes.

    Can we define the independent problem dimensions?  Would it be
    productive to document them and provide design considerations for
    each dimension?  Examples of largely independent design space
    dimensions: (i) the congestion control algorithm (loss vs delay vs
    packet pair timing, etc.); (ii) kernel-space vs user-space
    implementation strategy; (iii) protocol format and framing;
    (iv) window-based vs rate-based; (v) explicit congestion feedback
    vs implicit; (vi) Reno-friendly vs better-performing; (vii) state
    mostly kept at the sender vs the receiver.

Call-in information

    To join the call, please dial +1-734-531-0125 and use PIN 0111111.

    Or, from a SIP phone, dial 

 or
    visit https://edial.internet2.edu/call/0111111 and enter your SIP URI
    (such as 
sip:).

    Should a tool-free number be necessary, it is +1-800-541-1710.

Talk to you on Friday at 3PM.

-- 
Stanislav Shalunov              http://www.internet2.edu/~shalunov/

This message is designed to be viewed with 0.06479891g of NaCl.