>>>>> "Pascal" == Pascal Thubert <(pthubert)" <pthub...@cisco.com>> writes: >> On 2010-08-09 22:17, Pascal Thubert (pthubert) wrote: > Hi >> Michael: >> > >> > With >> http://tools.ietf.org/html/draft-ietf-roll-rpl-07#section-7.2 I > >> tried to stay within the lines of RFC 3697 as you also defend in >> your > mail. >> > >> > I think the question we have now is not whether that proposal >> is > lawful but whether the new law being defined at 6MAN would >> prevent it > in the future. > If the updated rules allow, then >> I'll be glad to work on an FL-based > alternate to the >> IPinIP/HbH. >> >> So I understand that ROLL would definitely need the ability to >> define explicit semantics on the label. Would it also need the >> label to be mutable? >>
Pascal> [Pascal] The FL based proposal for RPL uses 12 mutable bits. Pascal> They are used as an in-band control plane that checks the Pascal> consistency of routing states along a path. Those states can Pascal> easily get out of sync due to the nature of the links, but Pascal> the maintenance can be costly. We want to accelerate the Pascal> repairs on those links that are actually used when an Pascal> inconsistency is detected that will impact the delivery. I don't understand how the FL helps us on this! Probably I missed something important. What you write below was my entire understanding of our need for an in-band tag. Pascal> RPL also builds multiple topologies (virtual networks Pascal> identified by an instanceID) to address various constraints, Pascal> in terms that can be such as metrics but also Pascal> administrative. E.g. a power utility Command & Control Pascal> network at home will have a specific ID that's different Pascal> from the default general purpose one, so the power related Pascal> traffic ends up at the power utility GW along a specific Pascal> graph. Pascal> An opaque instanceID for the topology can be known by the Pascal> end points. The instanceID is not necessarily related to QoS Pascal> and does not map to a per hop behavior, but in our case, to Pascal> acts more like L3 .1Q tag. The Flow Label is the only field Pascal> available for an application to pass such information to the Pascal> network. Thus the non-mutable 8 bits in the proposal. +1 -- ] He who is tired of Weird Al is tired of life! | firewalls [ ] Michael Richardson, Sandelman Software Works, Ottawa, ON |net architect[ ] m...@sandelman.ottawa.on.ca 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 ipv6@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------