IETF Logo Mail Archive

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

"TSG" <tglassey@earthlink.net> Tue, 17 June 2008 20:28 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 B7F8C28C17E; Tue, 17 Jun 2008 13:28:35 -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 1013328C1A1; Tue, 17 Jun 2008 13:28:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.996
X-Spam-Level:
X-Spam-Status: No, score=-2.996 tagged_above=-999 required=5 tests=[AWL=-0.398, BAYES_00=-2.599, STOX_REPLY_TYPE=0.001]
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 rBAWggXzBIFn; Tue, 17 Jun 2008 13:28:33 -0700 (PDT)
Received: from elasmtp-kukur.atl.sa.earthlink.net (elasmtp-kukur.atl.sa.earthlink.net [209.86.89.65]) by core3.amsl.com (Postfix) with ESMTP id 8A1AE3A68B4; Tue, 17 Jun 2008 13:28:33 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=lAl0QZa4EGTuZnPDeuSTHT/ACmdgOfxUxW2AyjyIVYEqt38uEvG7M32YGG6SXair; h=Received:Message-ID:From:To:Cc:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [64.125.79.23] (helo=tsg1) by elasmtp-kukur.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1K8hnm-0006ji-57; Tue, 17 Jun 2008 16:29:14 -0400
Message-ID: <00b501c8d0c1$2ee22fe0$0200a8c0@tsg1>
From: TSG <tglassey@earthlink.net>
To: Robert Elz <kre@munnari.OZ.AU>, debbie@ictmarketing.co.uk
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> <1421.1213728582@epsilon.noi.kre.to>
Subject: Re: Appeal against IESG blocking DISCUSS on draft-klensin-rfc2821bis
Date: Tue, 17 Jun 2008 13:29:05 -0800
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec7981ec18d453770e971d887b90f9183a05350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 64.125.79.23
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

Uh, Folks
DOMAIN NAMES cannot be reserved in that manner and this lawsuit from the US 
District Court says so.
http://www.domainnamenews.com/wp-content/uploads/2008/06/express-media-express-corp-nd-ca.pdf

That's not going to fly. DOMAIN NAMES are IP and need to be registered as 
TM's to protect them. If you want these domains to be protected and reserved 
then register them and pay the filing and maintenance fees on them.

Todd Glassey
----- Original Message ----- 
From: "Robert Elz" <kre@munnari.OZ.AU>
To: <debbie@ictmarketing.co.uk>
Cc: <iesg@ietf.org>; <ietf@ietf.org>
Sent: Tuesday, June 17, 2008 10:49 AM
Subject: Re: Appeal against IESG blocking DISCUSS on 
draft-klensin-rfc2821bis


>    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 

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

v2.23.0 | Report a Bug | By Email