I think this should go down the 1) path. This is a recommended use of
mechanisms that exist, not a change of any normative text.
RjS
On Apr 23, 2007, at 1:56 PM, Dean Willis wrote:
In Prague we recorded a consensus on documenting the various fixes
to record-route as described in:
http://www.ietf.org/internet-drafts/draft-froment-sip-record-route-
fix-00.txt
While we agreed to undertake this effort, we left open the
discussion of how to achieve it.
Two proposals were made:
1) Recast the solution as a BCP
2) Move this into the "Essential Corrections" process for RFC 3261
bugfixing.
I currently lean towards number 2, but we should discuss it.
--
Dean
_______________________________________________
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
_______________________________________________
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
