Hi, George, Please find my comments inline....
> draft-blake-ipv6-flow-label-nonce-02 is expired and I haven't heard > much effort to push it forward again. IMO it would be more helpful to > consider security implications and evaluate your solution with > draft-carpenter-6man-flow-update-03, > draft-donley-6man-flowlabel-transport-sig-00, etc in mind. I believe > that it should integrate well, but I'd rather see a draft revision > that takes this explicitly into consideration. The I-D describes a Flow Label generation algorithm that is compliant with the current specifications, and that also integrates well with draft-blake-ipv6-flow-label-nonce and use of the FL for ECMP. My understanding is that draft-carpenter-6man-flow-update describes a possible update of the current specs *if* there's consensus for that. I'm not sure there has been consensus on updating the Flow Label specification, though. Thanks! Kind regards, -- Fernando Gont e-mail: [email protected] || [email protected] PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1 -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
