Hi Michael, > > right direction and would not have to be revisited quite as soon if > > something more robust were proposed. > > > > Bottom line. Falls short of what I'd like to see but no objection. > > > > Curtis > > I agree with Curis. I'd really like to see the first version > of this spec at > least have the extended sequence number as is being discussed for v2.
I disagree that AT should have a 64 bit sequence space in the base specification primarily because we are not yet sure if the KARP boot count approach is what the WG will finally converge on (in which case we would need an extended sequence space). Also note that the AT provides an "Auth Type" field which can be assigned a new value (similar to how it will be done for OSPFv2) once we decide to move to a different scheme. The same standard that extends the OSPFv2 sequence space can also do it for OSPFv3 AT block - really hardly an overhead. Also note that you could consider this proposal as just bringing OSPFv3 at par with OSPFv2. Once this is done, any proposal that extends OSPFv2 will natively work for OSPFv3 as well. Cheers, Manav _______________________________________________ OSPF mailing list [email protected] https://www.ietf.org/mailman/listinfo/ospf
