Speaking as one of Geoff's co-authors, and with no intention of offending anyone: I would be ok with minor changes to the current doc that made it possible for others to reuse this work if they so desire, but I am not all that thrilled by the idea of pushing this work into the PKIX WG as a solution in search of additional problems, and I don't want to do anything to the current spec that would complicate RPKI use of it.
I think my last point (not wanting to complicate RPKI use) can be addressed by nailing down the RPKI profile of the mechanism, if we go that way. I am more concerned with why we are attempting to generalize this spec at this point in time: has anybody outside the SIDR WG requested generalization? Who's the customer here, and what are the customer's requirements? Bottom line: I don't want the SIDR work to get bogged down a well-intentioned attempt to save some unspecified party from a problem that party is not aware of having. If there's some trivial change we can make that costs us nothing and makes life easier for hypothetical others fine, but not if it's going to slow us down. _______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
