> > So I think case 3 must not break specification. Do I miss something? >
It might be legal, but it's at least unusual. In this case the IETF guideline "be conservative with what you send" comes into play. Why would you insist in something that might (and obviously does) cause trouble when there is a perfectly fine and wildly used alternative available? Just don't do it! Regards Joerg
