Hi, Keith,
I reviewed 00/01 of this draft pretty seriously, and have reviewed the 02
and 03 diffs.
It's ready for publication as an Informational RFC.
I have one question, mostly involving future-proofing, and it may not
require any changes to the current draft.
This text was added in 03:
Essential Corrections to SIP: A collection of fixes to SIP that
address important bugs and vulnerabilities. These include a fix
requiring loop detection in any proxy that forks [82] and a
clarification on how record-routing works [110].
This points to two references, but it's likely there will be others in the
future, (my impression from
http://www3.ietf.org/proceedings/07mar/minutes/sip.html and
http://www3.ietf.org/proceedings/07jul/minutes/sip.html is that we have not
identified the last essential correction to SIP).
Is there any convention that the SIP working group can adopt so that
implementers can know that some future "fix to some random thing we all
thought worked, but it doesn't" is ALSO an essential correction?
Thanks,
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
