Re: [Dime] Ben Campbell's No Objection on draft-ietf-dime-4over6-provisioning-04: (with COMMENT)
"Ben Campbell" <ben@nostrum.com> Thu, 06 August 2015 20:56 UTC
Return-Path: <ben@nostrum.com>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B775C1B3320; Thu, 6 Aug 2015 13:56:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b-EZrZVF6moF; Thu, 6 Aug 2015 13:56:13 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A5211B3319; Thu, 6 Aug 2015 13:56:13 -0700 (PDT)
Received: from [10.0.1.23] (cpe-70-119-203-4.tx.res.rr.com [70.119.203.4]) (authenticated bits=0) by nostrum.com (8.15.2/8.14.9) with ESMTPSA id t76KtW5J029134 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 6 Aug 2015 15:55:42 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-119-203-4.tx.res.rr.com [70.119.203.4] claimed to be [10.0.1.23]
From: Ben Campbell <ben@nostrum.com>
To: Zhouqian <cathy.zhou@huawei.com>
Date: Thu, 06 Aug 2015 15:55:31 -0500
Message-ID: <80DD195E-CC55-4187-A925-2B198E2A792B@nostrum.com>
In-Reply-To: <A6A061BEE5DDC94A9692D9D81AF776DF409EE785@SZXEMA512-MBX.china.huawei.com>
References: <20150805195831.24117.11508.idtracker@ietfa.amsl.com> <A6A061BEE5DDC94A9692D9D81AF776DF409EE785@SZXEMA512-MBX.china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
X-Mailer: MailMate (1.9.2r5107)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dime/x1OPu0Phx8m-i34POO3DbRUG_Ck>
Cc: draft-ietf-dime-4over6-provisioning.shepherd@ietf.org, draft-ietf-dime-4over6-provisioning@ietf.org, dime-chairs@ietf.org, dime@ietf.org, draft-ietf-dime-4over6-provisioning.ad@ietf.org, The IESG <iesg@ietf.org>
Subject: Re: [Dime] Ben Campbell's No Objection on draft-ietf-dime-4over6-provisioning-04: (with COMMENT)
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dime/>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Aug 2015 20:56:13 -0000
Hi, one final comment, inline: On 6 Aug 2015, at 2:34, Zhouqian (Cathy) wrote: >> -- 3.2: >> Is it possible (or reasonable) for the FQDN to include an >> internationalized >> domain name? That is, is there a need for a idn or precis dependency? >> (I'm not >> saying there _is_ such a need; I'm just >> asking.) > I think it is possible for the FQDN to include an IDN. But this > document does not define the FQDN encoding. > It just follows the definition in RFC1035, RFC1123 and RFC2181. It might not hurt to mention that if IDNs are used, they should be encoded as RFC 5891 A-labels. (But I'm okay with it if you don't.) [...]
- [Dime] Ben Campbell's No Objection on draft-ietf-… Ben Campbell
- Re: [Dime] Ben Campbell's No Objection on draft-i… Zhouqian (Cathy)
- Re: [Dime] Ben Campbell's No Objection on draft-i… mohamed.boucadair
- Re: [Dime] Ben Campbell's No Objection on draft-i… Ben Campbell
- Re: [Dime] Ben Campbell's No Objection on draft-i… Zhouqian (Cathy)