Re: [Sip] On The Essentialness of Corrections

Dean Willis wrote:
> I'd actually like to see us go beyond the batching of "essential 
> corrections" and start maintaining complete and fully-revised
> versions of the normative behaviors as internet drafts, perhaps
> occasionally publishing them as RFCs that replace the older versions.

We are still talking the sip-essential-correction model here, right?
Or is what you propose above a new model?

> So for example with RFC 3261, we'd maintain a
> "draft-ietf-sip-rfc3261-bis" that would start as a copy of RFC 3261
> (with current boilerplate, of course) and then be edited to reflect
> the changes documented in each "essential correction" we agree to.
> Then instead of telling implementors to go read RFC 3261 plus a dozen
> more potentially conflicting revision documents, we could just say
> "see draft-ietf-sip-rfc3261-bis-xx".

Isn't that what we essentially did with rfc2543-bis set of drafts?
Of course, the domain of influence of SIP back then was a bit more
limited than it is now.

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
2701 Lucent Lane, Rm. 9F-546, Lisle, Illinois 60532 (USA)
Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
WWW:   http://www.alcatel-lucent.com/bell-labs

_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip