> It's an informational RfC, so maybe you should try to contact > the authors. You probably know <http://dict.org> to find the > "dict community" if there is a "dict community", I've no idea. I'm not sure what you mean by "Informational RFC". It provides extension to existing functionality. Alas but I couldn't find any dict.org community. And the only contact address that I found in dict.org ftp site was of the original rfc-2229 authoer - Faith. And I'm still waiting a response from him. Luckily, the mail has not bounced from a 7yr old email. :-) > If the dict authors and / or community like your ideas to > update this rather old protocol, you could publish an I-D > (Internet draft), after reading Paul's "IETF Tao" and some > related memos. What if the authors do not respond or community does not exist. No... I don't intened to infuse fire, but just talking about a possibility. Is there any place / forum where I can approach... or can I directly put up an I-D? > use RfC 3986. For that part of the discussion you could use Hmm... that's pretty new one. I'd check it up and use it. I'm not sure right now, but it may break the old URI which is of the form: dict://userinfo@host:port/d:word:database dict://userinfo@host:port/m:word:database:stratey > IIRC dict has UTF-8 as default. If your updates would break > existing implementations you should really discuss it with the No. It will still continue to support UTF-8 encoding. As a matter of fact, and as also Randy pointed out, charset Unicode with UTF-8 encoding is the major support that I want to have. ASCII with UTF-8 remains the default. Other encodings include UTF-7, MIME etc provided there's enough support in the underlying charset (taking a clue from SMTP / MIME RFCs, encoding of mail-messages) -- not sure if I'm making some sense here. -- Cheers, Gaurav Vaish http://www.mastergaurav.org http://mastergaurav.blogspot.com -------------------------------- _______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf