On Sat, 2011-07-23 at 22:48 +0200, Roland Bless wrote: > The draft was lacking a clear problem statement so that wasn't clear to me.
The proposer has put a fairly clear one into this discussion, hope it ends up in the next draft :-) > Depends on what you want to diagnose. That's always true. No tool will fit all situations. The question about this one, as for all such things, is simply "is it worth having?" > > change in transit (if I read the burbling, ever-changing discussion on > > flow labels correctly, which I may well not have). > > That shouldn't be the case though, see Brian's reply. "Shouldn't be the case" is a far cry from "won't be the case". And the cases where what you expect is not what you get are exactly the cases where a flow-label-independent tool would likely be Very Nice To Have. > My point was referring to the case when the flow label is being used > as intended, not for other purposes. And my point was that "as intended" is very far from clear (and IMO rather unlikely ever to be clear). > My point was that you cannot assume that every end-system has such > debugging tool installed and that you can turn it on remotely. This is true of all end-to-end debugging tools...? I suppose I'm saying that you've not convinced me as to why we should NOT have a diagnostic header. Your arguments all say, in one way or another, that there are situations where it won't be useful. But that is true for all such things. To convince me to be against this proposal, I would need to see - arguments that show how it is a bad thing - arguments that show how it is a useless thing - arguments that show how it will not work - arguments that show how it is not needed "Not needed" is different from "useless". "Not needed" means that while the thing it does is useful, that thing can be done using an existing tool. I think most of your points are well-made, I just don't think they are showstoppers for this proposed new header. Regards, K. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Karl Auer ([email protected]) +61-2-64957160 (h) http://www.biplane.com.au/kauer/ +61-428-957160 (mob) GPG fingerprint: DA41 51B1 1481 16E1 F7E2 B2E9 3007 14ED 5736 F687 Old fingerprint: B386 7819 B227 2961 8301 C5A9 2EBC 754B CD97 0156
signature.asc
Description: This is a digitally signed message part
-------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
