Re: scope of derive
Hadriel Kaplan <[email protected]>
| Newsgroups | gmane.ietf.sip |
|---|---|
| Message-ID | <E6C2E8958BA59A4FB960963D475F7AC3137F291109@mail> |
> -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of > Elwell, John > Sent: Friday, December 05, 2008 12:10 PM > > Of course, as with any specs we produce, but until the spec is written > (not necessarily as an RFC) vendors can't implement it and the market > can't therefore decide. All we can do in the IETF is assess whether we > think it worthwhile to devote resources to writing an RFC. Yes exactly. The great thing about a DERIVE concept, or Dan's return-routability draft, is it doesn't require an RFC at all really. There is no interoperability issue to be solved, and no changes to SIP, AFAICT. No? But if they want it to be a WG item then it has to argue its case just as all the others do. -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