> -----Original Message----- > From: Scott Lawrence [mailto:xmlscott@xxxxxxxxx] > Sent: Monday, April 05, 2010 2:30 PM > To: Hadriel Kaplan > > 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 > change notices). Heh... weren't you just arguing about how optional requirements in IETF docs are bad? ;) This form of optional is right up that alley. For example, if I am a service provider who wants to not have Subscription mode, and the only way to do it is through UA config framework itself by setting a config field for "Subscribe-UA-Config="false" or whatever, then clearly the UA's MUST use the config. A MAY statement does nothing. If it's not clear and exact as to what config data a UA is supposed to use, and when, then you really do get "flaky service behavior" as you were worried about in a previous email. -hadriel _______________________________________________ Ietf mailing list Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf