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

"Dale Worley" <dworley@nortel.com> Wed, 03 March 2010 22: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 25F0828C1EE for <sipping@core3.amsl.com>; Wed, 3 Mar 2010 14:43:40 -0800 (PST)
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 FThyOFbJKneI for <sipping@core3.amsl.com>; Wed, 3 Mar 2010 14:43:39 -0800 (PST)
Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (nj300815-nj-outbound.net.avaya.com [135.11.29.16]) by core3.amsl.com (Postfix) with ESMTP id 233913A8CF0 for <sipping@ietf.org>; Wed, 3 Mar 2010 14:43:39 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.49,576,1262581200"; d="scan'208";a="6086479"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 03 Mar 2010 17:43:39 -0500
X-IronPort-AV: E=Sophos;i="4.49,576,1262581200"; d="scan'208";a="451878675"
Received: from unknown (HELO zcars04f.nortel.com) ([47.129.242.57]) by co300216-co-erhwest-out.avaya.com with ESMTP; 03 Mar 2010 17:43:34 -0500
Received: from zcars04e.nortel.com (zcars04e.nortel.com [47.129.242.56]) by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id o23MhCe27482 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified FAIL); Wed, 3 Mar 2010 22:43:13 GMT
Received: from zrtphxs1.corp.nortel.com (casmtp.ca.nortel.com [47.140.202.46]) by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id o23MhAv29267; Wed, 3 Mar 2010 22:43:10 GMT
Received: from [47.16.90.165] ([47.16.90.165]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 3 Mar 2010 17:43:10 -0500
From: Dale Worley <dworley@nortel.com>
To: "Kevin P. Fleming" <kpfleming@digium.com>
In-Reply-To: <4B6C332E.9080402@digium.com>
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> <4B6B2FF0.5030007@bell-labs.com> <A444A0F8084434499206E78C106220CAB9210933@MCHP058A.global-ad.net> <4B6C332E.9080402@digium.com>
Content-Type: text/plain
Organization: Nortel Networks
Date: Wed, 03 Mar 2010 17:43:09 -0500
Message-Id: <1267656189.3750.50.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: 03 Mar 2010 22:43:10.0324 (UTC) FILETIME=[E675C340:01CABB22]
Cc: "Elwell, John" <john.elwell@siemens-enterprise.com>, "sipping@ietf.org" <sipping@ietf.org>, "Vijay K. Gurbani" <vkg@bell-labs.com>
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: Wed, 03 Mar 2010 22:43:40 -0000

On Fri, 2010-02-05 at 09:03 -0600, Kevin P. Fleming wrote:
> That would in fact be wrong, domain names cannot begin with '.'. In
> addition, I'd recommend against allowing an 'invalid' name that does not
> contain '.', because many systems (including my laptop) are configured
> with default DNS search domains that are searched when names that
> contain only one component are resolved. 'invalid' in my case would
> search in at least two domains for 'invalid.xxx.yyy', which is not
> helpful in the context of this draft.
> 
> Explicitly specifying 'this.is.invalid' or something similar seems to be
> prudent in this case.

That's an interesting point.  As you note, "invalid" is a perfectly
valid DNS name that is reserved.  But it might be subject to bad
resolver behavior.  Indeed, IIRC some popular resolvers will always
search multiple configured domains unless the name given to them is
ended with an extra "." (which seems to be allowed for in the syntax).
But any SIP implementation should use its local resolver in such a way
that such additional searches are never done.

But how many SIP implementations do that correctly?

Dale