I see the CC to [email protected], and none to [email protected]. I'm not on [email protected], so I imagine I'll get moderated.
>>>>> "Pascal" == Pascal Thubert <(pthubert)" <[email protected]>> writes: Pascal> I think that the premise in the discussion was that the Pascal> network egress is incapable of restoring zero. Are you saying that the network egress can remove hop-by-hops, but it can't restore zero to the flow label? Pascal> - flow label is the only field that an application can use Pascal> to place an abstract tag in the packet in order to dialog Pascal> with the network. Removing Pascal> that capability seems really short sighted. My opinion, again, is that we are doing EXACTLY this. RPL is providing a number of RPLinstanceID's, selectable by flow-label to the application, and the application is selecting one. (Unknown flow-labels naturally need to go into some default RPLinstance ID) If the ROLL WG does not feel conformtable with the above, then I think we need to go ask some grandfathers of IPv6... What's the FLOW LABEL FOR then? I think our usage of flow label is completely within the pervue of what was intended. -- ] He who is tired of Weird Al is tired of life! | firewalls [ ] Michael Richardson, Sandelman Software Works, Ottawa, ON |net architect[ ] [email protected] http://www.sandelman.ottawa.on.ca/ |device driver[ Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE> then sign the petition. -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
