> Date: 2005-03-02 09:49 > From: Paul Vixie <paul@xxxxxxx> > > The IAB is ready to ask the RFC-Editor to publish > > > > Â Â Â Â Â What's in a Name: False Assumptions about DNS Names > > Â Â Â Â Â Â Â Â Â Â Â draft-iab-dns-assumptions-02 > > > > as an Informational RFC. ÂThis document reviews the potential > > assumptions that may be made based on domain names, as well as the > > potential implications (and pitfalls) of those assumptions. > > > > The IAB solicits comments by March 29, 2005. Please send > > comments to the IAB (iab@xxxxxxx), or to ietf@xxxxxxxxx > > i think this document is just silly. Âand highly subjective. Âthere is > no way to edit it to correct its problems -- it should just quietly die. Could you be more specific about the alleged problems? The document does identify several ongoing, real, objective problems (e.g. SMTP clients that assume that pipelining is supported even when not offered in response to EHLO, or -- worse -- when HELO is used to initiate a session). Now one might point out that not all of the issues discussed are specific to DNS names (the example above s not), but that could be addressed by splitting the document or reformulating its title and scope. The draft almost contains a workable definition of backwards compatibility, something which would be quite useful. _______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf