Kerry Lynn <kerlyn@xxxxxxxx> writes: > Thanks for your thorough review of draft-ietf-6lo-6lobac. Sorry that > it has taken so long to get back to you. Can you take a look at the > new version and see if it addresses your concerns? Comments inline... Yes, the -07 cleans up all my concerns. > Section 6 has been reworked to more clearly distinguish between two types > of IIDs: "MAC-address-derived" and "semantically opaque". The first is > recommended for link-local addresses because it enables maximum IPv6 > header compression efficiency. Since MS/TP is used primarily as a field > bus, I expect most installations will only ever involve link-local traffic > between an MS/TP device and a local controller. > > For applications where the MS/TP device is a client or server with routable > addresses, the spec strongly recommends generating a semantically opaque > IID, with 64 bits of entropy, for each global address. Ah, yes, that's the distinction that makes it clear. > ANSI/ASHRAE Standard 135-2016 was published late last year. This > version integrates the changes that were standardized in 135-2012 > Addendum an, so there's no longer any jumping back and forth between > references. And so you simplified the references to Std. 135 . Dale