Re: [Int-area] FW: New Version Notification for draft-eckert-intarea-flow-metadata-framework-01.txt

Hello Brian,

Thank you for the comments.

As Toerless mentioned the framework covers more than the QoS use case. Other use cases are for example visibility and differentiated routing.

We would definitely like to present this work in TSV as it has definitely some ties there.

Cheers

Amine
On Jul 18, 2013, at 9:58 PM, Brian E Carpenter <brian.e.carpenter@gmail.com>
 wrote:

> On 19/07/2013 00:11, mohamed.boucadair@orange.com wrote:
> ...
>>>> How to trust the data sent by an application? These are examples of
>>>> points which should be further discussed in the document.
>>> 
>>> [RP] I think this depends on the transport. Some transports like PCP or
>>> STUN have some built-in authentication.
>> [Med] The question is not whether a secure transport is used or not but to what extent the flow description is accurate (e.g., send fake flow description, systematically request treatment with higher priority, etc.).
> 
> This of course is why the diffserv model assumes that traffic will
> be reclassified at domain boundaries, since you can't trust what your
> neighbour tells you about QoS requirements. This proposal would be no
> different in the general case; flow metadata needs to be trustworthy.
> If not it will be a recipe for theft of service or DoS.
> 
> Why is this an intarea topic? To my mind it fits in tsvwg, which is
> currently discussing things like QoS for rtcweb.
> 
>   Brian
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area