Re: Update of RFC 2606 based on the recent ICANN changes ?

SM <sm@resistor.net> Fri, 27 June 2008 19:23 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 9AD173A6B5B; Fri, 27 Jun 2008 12:23:47 -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 A995F3A6B51 for <ietf@core3.amsl.com>; Fri, 27 Jun 2008 12:23:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.479
X-Spam-Level:
X-Spam-Status: No, score=-2.479 tagged_above=-999 required=5 tests=[AWL=0.120, BAYES_00=-2.599]
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 ZslUPbXincJC for <ietf@core3.amsl.com>; Fri, 27 Jun 2008 12:23:45 -0700 (PDT)
Received: from ns1.qubic.net (ns1.qubic.net [208.69.177.116]) by core3.amsl.com (Postfix) with ESMTP id 8E6CC3A6B40 for <ietf@ietf.org>; Fri, 27 Jun 2008 12:22:03 -0700 (PDT)
Received: from subman.resistor.net ([10.0.0.1]) (authenticated bits=0) by ns1.qubic.net (8.14.3/8.14.3) with ESMTP id m5RJLxBG023412 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 27 Jun 2008 12:22:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1214594528; x=1214680928; bh=yBd0a75WVVb829e/40e6pMMhGemMe14D7GEw KXaAE0w=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To: References:Mime-Version:Content-Type; b=Hxs2JGa8Ef0DT422gdMWN+5wKr bCM8Xbq3ZTTkjo7Dahg+9HmKVCT6GrUDXLJcaEz9wuJmQYWtZqaMti+g/bAW03OfJWP fNAk+98eIy7mDyw5AfWSrMtGIxRY+BncSR5/z44eJT6qwpuSBvCHqr+FHPHcSfnHdv3 OzSdVCGBfjc=
DomainKey-Signature: a=rsa-sha1; s=mail; d=resistor.net; c=simple; q=dns; b=zcEUzqAgTI0IpARJUhbLQo7pMiWkFycXPIoV09YkQmFhWW45mK+x54aY3JOAJNgph /LAuumHlWiTg9+zXZ27z8TBY99nCLWaQJJB48fQEKQlaNSmWwXOEja/PdGJaeG5kx0H dWh5lXdqODNLaAAPJL7UiiDCGfMqTkiNKswLous=
Message-Id: <6.2.5.6.2.20080627121824.02c55340@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 27 Jun 2008 12:21:46 -0700
To: David Conrad <drc@virtualized.org>
From: SM <sm@resistor.net>
Subject: Re: Update of RFC 2606 based on the recent ICANN changes ?
In-Reply-To: <74E3E26A-FCFB-45C1-989A-DD7EA5752974@virtualized.org>
References: <4C0AE13D-4CA6-4989-A6B0-555A014DE464@multicasttech.com> <74E3E26A-FCFB-45C1-989A-DD7EA5752974@virtualized.org>
Mime-Version: 1.0
Cc: 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-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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Hi David,
At 11:51 27-06-2008, David Conrad wrote:
>I believe an RFC that provides an IETF-defined list of names (beyond
>the 4 in 2606) and/or rules defining names the "Internet technical
>community" feels would be inappropriate as top-level domains would be
>quite helpful.

Do you mean as in RFC 3675?

Regards,
-sm 

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