Murray S. Kucherawy wrote:
Just for the sake of trying to cover all the bases:
This line of discussion is based on some sort of larger 'systems' model in
which
the current specification is only a component. While that's a good thing to
have in mind, the danger is that these discussions will cause folk to believe
they have to specify all the components, or multiple components, before the
current specification can progress.
That would be a mistake.
Most operational environments are fairly simple. They have a well-defined
trust
boundary and they have relatively few components within the boundary. Within
such environments, these other components really aren't needed. Implicit trust
and manual configuration will suffice.
After the current specification is standardized, it will probably be useful to
look for additional components of the intra-ADMD service to specify.
Doing it before that merely makes things messy and delayed.
d/
--
Dave Crocker
Brandenburg InternetWorking
bbiw.net
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html