On Mon, 2010-04-05 at 12:50 -0400, Hadriel Kaplan wrote:
And the way this is written makes the Subscription portion now a
critical/blocking component in getting SIP service up and working
(unless I'm misreading it).
You are misreading it.
The configuration data is obtained via HTTPS before the subscription is
created. Until the subscription is established (whether following the
initial load of the data or on any subsequent UA restart), the status of
that configuration data is that it is of 'unknown validity' (having an
established subscription on which no change notice has been received
changes that to 'known to be valid'). The spec says in section 2.6
(Validity of Stored 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.
So the UA may use the configuration data before any subscription is
established - the subscription does not block anything (except getting
Ietf mailing list