Re: IETF#86 TSVAREA draft minutes posted

2013-03-17 Thread Black, David
Hi Joe, The facts of the matter are that none of the Transport ADs have *ever* been storage experts, and nonetheless, the Transport Area has turned out significant work on NFS and iSCSI. What this means is that while it's a bonus if we can find an AD who is an expert in one or both of these st

Re: IETF#86 TSVAREA draft minutes posted

2013-03-17 Thread Joe Touch
Hi, David, I'm confused by your clarification below. Does this mean: a) your ADs have always had sufficient storage expertise already b) your ADs didn't always have sufficient storage expertise, but that wasn't considered an impediment to their work, and as a result didn't necessitate that y

Re: Flow queuing performance (was: Re: [tsvwg] New Version Notification for draft-baker-tsvwg-aqm-recommendation-00.txt)

2013-03-17 Thread Mikael Abrahamsson
On Sun, 17 Mar 2013, Jim Gettys wrote: Secondly, an extremely important factoid about why we got so excited about fq_codel (which is really DRR, in term derived from SFQ, combined with CoDel along with detecting thin vs. thick flows) is its performance: I can imagine! One thought, have tests

RE: IETF#86 TSVAREA draft minutes posted

2013-03-17 Thread Black, David
Minor, but important correction - I'm recorded as saying: also, chairs of storage WGs are grateful that ADs have never had storage expertise Uh, not exactly. What I thought I said is that the storage WG chairs (storm, nfsv4 chairs) are grateful that we've never had to educate the ADs t

Flow queuing performance (was: Re: [tsvwg] New Version Notification for draft-baker-tsvwg-aqm-recommendation-00.txt)

2013-03-17 Thread Jim Gettys
To begin with, I tend to use the term 'flow queuing' to distinguish what we're doing with classic "fair queuing", which is overbound in most people's minds, and some of what we do is "unfair" by some metrics. Secondly, an extremely important factoid about why we got so excited about fq_codel (whic