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

"James Seng" <james@seng.sg> Thu, 03 July 2008 22:32 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 408F03A699E; Thu, 3 Jul 2008 15:32:06 -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 DC61D3A68DD for <ietf@core3.amsl.com>; Thu, 3 Jul 2008 15:32:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 SGANnonXfTh7 for <ietf@core3.amsl.com>; Thu, 3 Jul 2008 15:32:04 -0700 (PDT)
Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.184]) by core3.amsl.com (Postfix) with ESMTP id C53973A68A1 for <ietf@ietf.org>; Thu, 3 Jul 2008 15:32:03 -0700 (PDT)
Received: by ti-out-0910.google.com with SMTP id a6so37387tib.25 for <ietf@ietf.org>; Thu, 03 Jul 2008 15:32:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=tBNHTtSAQblbVp+cbcBZkOxE0wzfql7UJTJYE1gmBEk=; b=qes5El82GDUWGH8LnkOs6aAuzDvH4qdMKPN1UUkJ5oDHwfdu/TkaFiUzUrsH2/zuTc IokOBzeOPDokIJmIXJ5JmBecvhY5q8fOSZsN5jNgcYYFXR9f5/HNw90a9wDOE1X7Ih24 A1M1CXHSC/oMY8uhnfba21Intsw9z9dlbp38A=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=d0pBGkILJkLgNENVxREGInCERns6bo9HbsxxUtfoZ4c19AbqcW0wddSl9juHijIrCu /e0s5wJkmxvhZB8pJcNvjzeIQMVFG0mRLMVJjNb2uhOZw40Rq5M++FPyjfP46uKdSeGo 8qZLb9SbKV+PaPU8acmAkTDGueXnXpwwuSJGg=
Received: by 10.110.16.13 with SMTP id 13mr1530tip.24.1215124331740; Thu, 03 Jul 2008 15:32:11 -0700 (PDT)
Received: by 10.110.10.7 with HTTP; Thu, 3 Jul 2008 15:32:11 -0700 (PDT)
Message-ID: <558a39a60807031532h3f2a6738t8965565c79a49a26@mail.gmail.com>
Date: Fri, 4 Jul 2008 06:32:11 +0800
From: "James Seng" <james@seng.sg>
To: "Bernard Aboba" <bernard_aboba@hotmail.com>
Subject: Re: Update of RFC 2606 based on the recent ICANN changes ?
In-Reply-To: <558a39a60807031531i246f0790ia2395111567b5795@mail.gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <200807022323.m62NNwVJ034275@drugs.dv.isc.org> <BLU137-W18376D2DBA85C8F712C06F93980@phx.gbl> <8953A1CE-E953-409F-A692-BD12DF4ADE61@acm.org> <BLU137-W11B50878943FB03BF4C33C93980@phx.gbl> <558a39a60807031531i246f0790ia2395111567b5795@mail.gmail.com>
X-Google-Sender-Auth: cb7845c8ff757cf1
Cc: IETF Discussion <ietf@ietf.org>, Lyman Chapin <lyman@acm.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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Oops, ignore my email :P My reading comprehension is bad in the morning.

-James Seng

On Fri, Jul 4, 2008 at 6:31 AM, James Seng <james@seng.sg> wrote:
> RFC 4282 defined
>
>   label       =  let-dig *(ldh-str)
>
> which means a single-label Unicode string would be absolutely fine
> since it translate to xn--gibberish. A shorter gibberish of cos, but
> still longer than a single character.
>
> -James Seng
>
>> Potential problems with global use of single-label names go beyond SMTP.
>> For example,  RFC 4282, which defines the Network Access Identifier
>> (NAI), does not permit the use of single-label names. From Section 2.1:
>>
>>    realm       =  1*( label "." ) label
>>
>> As a result, someone purchasing the "example" TLD and using the NAI
>> bob@example in order to obtain access to the network, might well
>> discover that this would not work.
>>
>>
>>
>>
>> _______________________________________________
>> 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