IETF Logo Mail Archive

Re: Fw: Impending publication: draft-iab-dns-assumptions-02.txt

Bruce Lilly <blilly@erols.com> Wed, 02 March 2005 19:10 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15476; Wed, 2 Mar 2005 14:10:55 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D6ZGU-0008Q9-Hm; Wed, 02 Mar 2005 14:12:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D6ZBd-0006MN-Hz; Wed, 02 Mar 2005 14:07:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D6ZBc-0006MI-9F for ietf@megatron.ietf.org; Wed, 02 Mar 2005 14:07:08 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14968 for <ietf@ietf.org>; Wed, 2 Mar 2005 14:07:06 -0500 (EST)
Received: from ns3a.townisp.com ([216.195.0.136] helo=ns3.townisp.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D6ZCo-0008Hz-Ix for ietf@ietf.org; Wed, 02 Mar 2005 14:08:23 -0500
Received: from mail.blilly.com (dhcp-0-8-a1-c-fa-f7.cpe.townisp.com [216.49.158.220]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ns3.townisp.com (Postfix) with ESMTP id 4309D29923 for <ietf@ietf.org>; Wed, 2 Mar 2005 14:07:06 -0500 (EST)
Received: from marty.blilly.com (localhost [127.0.0.1]) by mail.blilly.com with ESMTP id j22J6xfQ003235(8.13.1/8.13.1/mail.blilly.com sendmail.mc.mail 1.18 2004/05/15 07:23:45) ; Wed, 2 Mar 2005 14:07:00 -0500
Received: from localhost (localhost [127.0.0.1]) by marty.blilly.com with ESMTP id j22J6rb6003231(8.13.1/8.13.1/blilly.com submit.mc 1.1 2003/08/26 22:21:33) ; Wed, 2 Mar 2005 14:06:54 -0500
From: Bruce Lilly <blilly@erols.com>
Organization: Bruce Lilly
To: ietf@ietf.org
Date: Wed, 02 Mar 2005 14:06:52 -0500
User-Agent: KMail/1.7.2
References: <E1D6XOo-0007ex-00@mx18.mrf.mail.rcn.net>
In-Reply-To: <E1D6XOo-0007ex-00@mx18.mrf.mail.rcn.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200503021406.52890.blilly@erols.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: quoted-printable
Subject: Re: Fw: Impending publication: draft-iab-dns-assumptions-02.txt
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: quoted-printable

>  Date: 2005-03-02 09:49
>  From: Paul Vixie <paul@vix.com>

> > 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@iab.org), or to ietf@ietf.org.
> 
> 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 mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email