Hi, Dean,
I was happy with the status-quo. But here's the main problem as I
understand it:
People keep either showing up with INFO uses or just inventing them in
the wild and propagating them until somebody ELSE shows up at IETF with a
"de facto standard" usage of INFO that we have to turn away, thereby
wasting our time and theirs, and hurting many people's delicate feelings
in the process.
If we had an RFC that said "New uses of INFO are not being accepted by
the IETF for the following reasons, please use something else (like an
event package) instead" then people might be less tempted to use INFO, or
at least to bring it to the IETF.
Speaking as co-chair of MEDIACTRL who's currently looking at text in one of
the MEDIACTRL drafts about "why not INFO", that's exactly what I'm hoping
for.
Thanks for the excellent and short summary.
Spencer
_______________________________________________
Sip mailing list https://www1.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
