Re: [multipathtcp] New Version of MPTCP Architecture Draft

Hi Alan,

one short remark: Is this correct?

"Packet Scheduling: This function breaks the bytestream received
      from the application layer into segments which are transmitted on
      one of the available lower (subflow) layers..."

Actually, segments can be transmitted on more than one subflow as the next 
paragraph says: "... segments with the same connection-level sequence number 
can be transmitted over multiple paths, i.e. as retransmissions or just to 
increase redundancy..." right?

And, one more question, is the discussion when actually to set up or close a 
subflow out of scope of this document? I was excepting some sentences about 
that in the Path Manager description...?

BR,
Mirja

On Wednesday 03 February 2010 12:03:24 Ford, Alan wrote:
> Hi all,
>
> We have submitted an updated version of the MPTCP architecture draft,
> which can be found at:
> http://www.ietf.org/id/draft-ford-mptcp-architecture-01.txt
>
> This is a significant change from the previous version, concentrating
> now on how core architectural principles will lead to high-level design
> decisions for a MPTCP protocol.
>
> It is intended to present and discuss this draft at the interim audio
> conference next week. In the meantime, we'd be very interested in
> feedback and discussion, so please do send comments to the list.
>
> Cheers,
> Alan
>
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org
> https://www.ietf.org/mailman/listinfo/multipathtcp

-- 
-------------------------------------------------------------------
Dipl.-Ing. Mirja Kühlewind
Institute of Communication Networks and Computer Engineering (IKR)
University of Stuttgart, Germany
Pfaffenwaldring 47, D-70569 Stuttgart

web: www.ikr.uni-stuttgart.de
email: mirja.kuehlewind@ikr.uni-stuttgart.de
tel: +49(0)711/685-67973
-------------------------------------------------------------------