IETF Logo Mail Archive

Re: Appeal against IESG blocking DISCUSS on draft-klensin-rfc2821bis

Robert Elz <kre@munnari.OZ.AU> Tue, 17 June 2008 19:00 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 078CE28C19C; Tue, 17 Jun 2008 12:00:10 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4929B28C17E; Tue, 17 Jun 2008 12:00:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.048
X-Spam-Level:
X-Spam-Status: No, score=-1.048 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QXpuoH9LJvDU; Tue, 17 Jun 2008 12:00:06 -0700 (PDT)
Received: from jade.coe.psu.ac.th (unknown [202.28.99.196]) by core3.amsl.com (Postfix) with ESMTP id DD77228C19C; Tue, 17 Jun 2008 12:00:04 -0700 (PDT)
Received: from epsilon.noi.kre.to (localhost [127.0.0.1]) by jade.coe.psu.ac.th with ESMTP id m5HIpDBY001621; Wed, 18 Jun 2008 01:51:15 +0700 (ICT)
Received: from epsilon.noi.kre.to (localhost [127.0.0.1]) by epsilon.noi.kre.to (8.14.2/8.14.2) with ESMTP id m5HIngvV001361; Wed, 18 Jun 2008 01:50:16 +0700 (ICT)
From: Robert Elz <kre@munnari.OZ.AU>
To: debbie@ictmarketing.co.uk
Subject: Re: Appeal against IESG blocking DISCUSS on draft-klensin-rfc2821bis
In-Reply-To: <049b01c8d089$6c901ce0$0a00a8c0@CPQ86763045110>
References: <049b01c8d089$6c901ce0$0a00a8c0@CPQ86763045110> <8832006D4D21836CBE6DB469@klensin-asus.vbn.inter-touch.net><485590E2.3080107@gmail.com><p06250116c47c330c7dd0@[75.145.176.242]> <4856DE3A.3090804@gmail.com>
Mime-Version: 1.0
Date: Wed, 18 Jun 2008 01:49:42 +0700
Message-ID: <1421.1213728582@epsilon.noi.kre.to>
Cc: iesg@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

    Date:        Tue, 17 Jun 2008 15:50:02 +0100
    From:        "Debbie Garside" <debbie@ictmarketing.co.uk>
    Message-ID:  <049b01c8d089$6c901ce0$0a00a8c0@CPQ86763045110>

  | I would also add that to go against an IETF BCP

Huh?   The BCP in question says (in a bit more eloquent form)
"Here are some domain names that are reserved from all normal use,
and so are suitable for use in places where something with the
syntax of a valid domain names is required, but no real domain
name should be used - use them where applicable".

It does not say "you must use these domain names" (for any purpose
at all).

Where's the "go against an IETF BCP" here?

kre



_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email