At 01:39 PM 8/1/2007, Dean Willis wrote:
So I'd like to ask the group some questions:
1) Should we stop updating Table 2/3 in each draft?
2) If so, do we need an update to RFC 4485 to establish new guidelines?
3) Should we do something instead of updating Table 2/3, such as
coming up with a new representation?
4) If we have a new representation, should it be fully presented in
each draft, or should it establish a new registry that each draft
would update via IANA actions? Or somethinge else?
If we choose #s 3 or 4 - we need to update RFC-4485
Doing #1 also requires an update to RFC-4485
meaning, unless we continue doing the table fill per draft, we need
to update RFC-4485.
What would an alternative to table 2/3 be?
While I agree that supporting text in a particular doc doesn't always
follow the doc's table 2/3 update, which should have been a
requirement in RFC-4485 BTW, having that inconsistency can only cause
inconsistent implementations.
I like the table, but feel we need to update RFC-4485 with consistent
text supporting the table in each doc, if we keep the table (and the
RFC-4485 requirement in Dean's original message).
--
Dean, Duly Appointed Co-Chair and Self-Appointed Pontificous Mediator
_______________________________________________
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
