Howdy,
I said I would shut up, but I missed one question from Cullen, which was:
This conversation constantly confuses the issue of must implement vs must
deploy. Which one are you objecting to here.
Answer: I am objecting to there not *being* a distinction between must
implement vs. must deploy in this draft. The draft requires the implementation
and DEPLOYMENT of a SIP Subscription service. It is not optional to use. It
is not optional to deploy.
Through some careful analysis of the implementation requirements stipulated in
the draft, one may be able to find an exemption path to avoid deployment by
means of configuration - but the language of the requirements to do so is so
weak that it's meaningless.
You cannot stipulate that a "UA MAY do foo" in a SIP-Forum profile or IETF RFC,
and then expect administrators to rely on that foo for anything useful
whatsoever, because not all UAs are required to do foo. Some will, some won't.
All of them will be compliant. This basically defeats the whole point of
having an "implementation profile", imho.
For example, the following requirements are stipulated:
The User Agent MAY obtain configuration information by any means in
addition to those specified here, and MAY use such information in
preference to any of the steps specified below, but MUST be capable
of using these procedures alone in order to be compliant with this
specification.
...
The UA MAY at any time return to any earlier step in the
process of obtaining configuration data.
...
The UA MAY use configuration data that is of unknown validity, or
configuration data that is known to be no longer valid, while
attempting to revalidate that data or obtain new data. There is no
assurance that such configuration data is still useful, but the UA is
NOT REQUIRED to stop using or delete the data.
These requirements are all completely meaningless, in the sense that they do
not provide any reliable behavior.
-hadriel
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf