Re: Appeal against IESG blocking DISCUSS on draft-klensin-rfc2821bis
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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



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 at munnari.OZ.AU>
To: <debbie at ictmarketing.co.uk>
Cc: <iesg at ietf.org>; <ietf at 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 at ictmarketing.co.uk>
>    Message-ID:  <049b01c8d089$6c901ce0$0a00a8c0 at 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 at ietf.org
> https://www.ietf.org/mailman/listinfo/ietf 

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



Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.