>> Maybe this discussion could be viewed as a good motivation for >> revisiting the requirements draft. > > don't require what you have no solid idea of how to achieve.
Maybe if someone actually laid out real requirements, someone, someplace, could determine how to achieve most (if not all) of them. The process SIDR has used is backwards --choose a solution, then build the requirements around that solution. When problems arise, just change the requirements so it's no longer a problem. :-) Russ _______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
