Christer Holmberg writes: > Now, in your example, if OB_1 and REG_2 fail you don't still don't have > redundancy :)
in the very common case that i have described earlier on this mailing list, obx and regx are paired and run on the same host. they are not separate entities that can fail on their own. > I guess this all comes back to Dean's question whether we need some new > text into the draft. > > In order to avoid delaying the Outbound spec even more, I guess it could > also be an extension draft:"Outbound with multiple contacts", or > something like that... huh, once ob is out as rfc, it is way too late to do anything about it. ob i-d must be got right the first shot. another (better) alternative is to publish the component rfcs that we have identified first and once they are out, start working on ob i-d. -- juha _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip
