IETF Logo Mail Archive

Re: [Sipping] Question on draft-ietf-sipping-v6-transition-07

"Dale Worley" <dworley@avaya.com> Thu, 04 February 2010 16:43 UTC

Return-Path: <dworley@avaya.com>
X-Original-To: sipping@core3.amsl.com
Delivered-To: sipping@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DAA403A689B for <sipping@core3.amsl.com>; Thu, 4 Feb 2010 08:43:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Level:
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[AWL=0.060, 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 POO8sWQpVWqb for <sipping@core3.amsl.com>; Thu, 4 Feb 2010 08:43:43 -0800 (PST)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id 132923A676A for <sipping@ietf.org>; Thu, 4 Feb 2010 08:43:43 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.49,405,1262581200"; d="scan'208";a="203775964"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 04 Feb 2010 11:44:29 -0500
X-IronPort-AV: E=Sophos;i="4.49,405,1262581200"; d="scan'208";a="442555324"
Received: from unknown (HELO zcars04f.nortel.com) ([47.129.242.57]) by co300216-co-erhwest-out.avaya.com with ESMTP; 04 Feb 2010 11:44:28 -0500
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id o14Gi7V11809; Thu, 4 Feb 2010 16:44:07 GMT
Received: from zrtphxs1.corp.nortel.com (casmtp.ca.nortel.com [47.140.202.46]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id o14Gi5t17011; Thu, 4 Feb 2010 16:44:05 GMT
Received: from [47.16.90.165] ([47.16.90.165]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 4 Feb 2010 11:44:04 -0500
From: Dale Worley <dworley@avaya.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>
In-Reply-To: <A444A0F8084434499206E78C106220CAB920FE16@MCHP058A.global-ad.net>
References: <A444A0F8084434499206E78C106220CAB4EC49D8@MCHP058A.global-ad.net> <4B61E8AE.6090309@alcatel-lucent.com> <A444A0F8084434499206E78C106220CAB4EC49F5@MCHP058A.global-ad.net> <4B61EEFE.3030605@alcatel-lucent.com> <A444A0F8084434499206E78C106220CAB920FE16@MCHP058A.global-ad.net>
Content-Type: text/plain
Organization: Nortel Networks
Date: Thu, 04 Feb 2010 11:44:04 -0500
Message-Id: <1265301844.3758.24.camel@khone.us.nortel.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.3 (2.12.3-5.fc8)
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 04 Feb 2010 16:44:04.0947 (UTC) FILETIME=[4342E230:01CAA5B9]
Cc: "sipping@ietf.org" <sipping@ietf.org>
Subject: Re: [Sipping] Question on draft-ietf-sipping-v6-transition-07
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipping>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2010 16:43:44 -0000

On Wed, 2010-02-03 at 17:07 +0100, Elwell, John wrote:
> A follow-up question on the statement:
> "For this, IPv6 implementations MUST use a domain
>        name within the .invalid DNS top-level domain instead of using
>        the IPv6 unspecified address (i.e., ::)."
> Presumably just "invalid" (alone, as opposed to "xxxx.invalid" would be legal?

That would be the implication of the usual meaning of "within".  Looking
at RFC 1034 (DOMAIN NAMES - CONCEPTS AND FACILITIES), it doesn't appear
that "within" has a special, defined meaning in regard to domain names.

Dale

v2.23.0 | Report a Bug | By Email