Hmm. This is an interesting definition of "optional". I think any xkms-type
proposal needs to be optional for the receiver too - which is what Michael's
sample implies. However, the way you're casting it is that the sender could
dictate to the receiver that they *have* to fetch via xkms, is that correct?
Mark is raising a basic point about the effect of creating choices in a
specification.
Development
Is it optional to create the software that supports the option.
Use
Are all participants free to choose not to support the option?
The usual IETF model is to define a core capability that has the minimum
functionality to do something useful. Everyone claiming to write code that
"supports" the specification MUST implement all of that functionality.
Everyone.
Whether operators choose to use all the features is a separate matter, but as
Mark notes, there is a problem if the initiating side uses it but the
receiving side does not.
d/
---
Dave Crocker
Brandenburg InternetWorking
+1.408.246.8253
dcrocker a t ...
WE'VE MOVED to: www.bbiw.net