Hi Brian.
Changes look mostly good. Some specific comments.
Brian E Carpenter brian.e.carpen...@gmail.com writes:
Traditionally, flow classifiers have been based on the 5-tuple of the
source and destination addresses, ports, and the transport
protocol
add flow classifiers
On 2011-04-06 05:40, Thomas Narten wrote:
Here are my detailed comments on the document. I did chat with Brian
directly in Prague about these points as well. Overall, I support this
document. But I think the wording in places needs another round of
revision.
A flow is a sequence of
Thomas,
Finally catching up on email after IETF.
On Apr 5, 2011, at 10:40 AM, Thomas Narten wrote:
Here are my detailed comments on the document. I did chat with Brian
directly in Prague about these points as well. Overall, I support this
document. But I think the wording in places needs
On 2011-04-07 08:22, Scott Brim wrote:
On Wed, Apr 6, 2011 at 14:49, Thomas Narten nar...@us.ibm.com wrote:
Scott Brim scott.b...@gmail.com writes:
A Flow is a sequence of packets originating from a particular
application that should be treated the same by the network as
they are
Thomas,
Thanks for your three sets of comments. The authors will work on
new versions to respond to them. That will take two or three
weeks, I think.
Regards
Brian
On 2011-04-06 05:40, Thomas Narten wrote:
Here are my detailed comments on the document.
...
On Tue, Apr 5, 2011 at 13:40, Thomas Narten nar...@us.ibm.com wrote:
Here are my detailed comments on the document. I did chat with Brian
directly in Prague about these points as well. Overall, I support this
document. But I think the wording in places needs another round of
revision.
A
Hi Scott.
Scott Brim scott.b...@gmail.com writes:
A Flow is a sequence of packets originating from a particular
application that should be treated the same by the network as
they are forwarded along to their ultimate destination. Packets
within a flow should not be reordered,
On Wed, Apr 6, 2011 at 14:49, Thomas Narten nar...@us.ibm.com wrote:
Scott Brim scott.b...@gmail.com writes:
A Flow is a sequence of packets originating from a particular
application that should be treated the same by the network as
they are forwarded along to their ultimate
Here are my detailed comments on the document. I did chat with Brian
directly in Prague about these points as well. Overall, I support this
document. But I think the wording in places needs another round of
revision.
A flow is a sequence of packets sent from a particular source to a
All,
This message starts a 6MAN Working Group Last Call on advancing:
Title : IPv6 Flow Label Specification
Author(s) : S. Amante, et al.
Filename: draft-ietf-6man-flow-3697bis-02.txt
Pages : 13
Date:
10 matches
Mail list logo