On Thu, 2009-02-05 at 21:40 +0100, Iñaki Baz Castillo wrote: > Unfortunatelly RFC 3966 remains untouchable containing the bug. > I don't understand why a RFC cannot be *fixed*, I really don't understand it.
Because then there would be several "RFC 3966s", and it would never be clear which one was meant by the phrase "RFC 3966". Now, you can say "RFC 3966" or "RFC 3966 as corrected by erratum 203", and is clear exactly what you mean -- for all time. Dale _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
