Re: draft-kuthan-sip-derive
Hadriel Kaplan <[email protected]>
| Newsgroups | gmane.ietf.sip |
|---|---|
| Message-ID | <E6C2E8958BA59A4FB960963D475F7AC3136C689751@mail> |
> -----Original Message----- > From: Adam Roach [mailto:[email protected]] > Sent: Monday, November 17, 2008 9:12 AM > > On 11/17/08 7:40 AM, Hadriel Kaplan wrote: > > Or you could pick something else to use for verification. > > Such as...? Either a new header or a new parameter. We seem to be getting this requirement a lot lately in various SIP-related WG's: we need some unique per-call identifier thingy that crosses b2bua's without change. I propose we just standardize one, but avoid making it have any property which made changing call-id value's a necessity. (like don't put addressing info in it, and don't make it a dialog match criteria in the state machine, etc.) I was planning to submit a draft to do that before the deadline, but was too busy. It would require the UA's to change to support it if you want to use it for Derive, but somehow I don't really believe a significant market share of deployed UA's support the rfc4235 subscribe dialog-package yet either (despite Sipit's poll). And I think we'd have uses for a logical call-id not in Call-ID. -hadriel _______________________________________________ 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