> Because this isn't a brand new subject area. This doc is intended (IMHO) > to clarify (lots and lots of) existing practice and nudge it in the right > direction, not start with a clean sheet.
If something "adopts" this as an approach, it then inherits all the practices, and would need to do its own profiling to then limit the options further. I don't see that happening as much as if the "best practice" were already here, so the effect is to leave things pretty much as they are. > People will be looking to this spec to clarify this naming mystery. > Leaving out traditional practice because it's icky just leaves the mystery > to be documented in alleyways instead. Precluding something doesn't necessarily mean leaving it undocumented or unmentioned though. -- Scott _______________________________________________ certid mailing list [email protected] https://www.ietf.org/mailman/listinfo/certid
