IETF Logo Mail Archive

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

Dave Crocker <dhc2@dcrocker.net> Fri, 04 July 2008 17:19 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 C67483A6B29; Fri, 4 Jul 2008 10:19: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 E4B8C3A6B29 for <ietf@core3.amsl.com>; Fri, 4 Jul 2008 10:19:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 Vo5LM48rRJOV for <ietf@core3.amsl.com>; Fri, 4 Jul 2008 10:19:46 -0700 (PDT)
Received: from sbh17.songbird.com (unknown [IPv6:2001:470:1:76:0:ffff:4834:7146]) by core3.amsl.com (Postfix) with ESMTP id 52FC23A69C6 for <ietf@ietf.org>; Fri, 4 Jul 2008 10:19:45 -0700 (PDT)
Received: from [192.168.0.3] (adsl-68-122-70-168.dsl.pltn13.pacbell.net [68.122.70.168]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id m64HJjHj002468 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 4 Jul 2008 10:19:50 -0700
Message-ID: <486E5BB1.9010606@dcrocker.net>
Date: Fri, 04 Jul 2008 10:19:45 -0700
From: Dave Crocker <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Update of RFC 2606 based on the recent ICANN changes ?
References: <200807032314.m63NEY56048085@drugs.dv.isc.org>
In-Reply-To: <200807032314.m63NEY56048085@drugs.dv.isc.org>
X-Virus-Scanned: ClamAV 0.92/7638/Fri Jul 4 04:41:46 2008 on sbh17.songbird.com
X-Virus-Status: Clean
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Fri, 04 Jul 2008 10:19:50 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
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



> 	There is a difference between allowing protocol to be used
> 	in a "local" only mode (single label) and a "global" mode
> 	(multi-label) and saying you must support single label in
> 	a global context.


If a protocol is used in a global mode, the problem with trying to use it in a 
tailored, local mode is that the various defaults of the local context are not 
carried with the data that escapes into the global context.

There must be perfect gatewaying between the two contexts and this almost never 
achieved.

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email