IETF Logo Mail Archive

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

"Kevin P. Fleming" <kpfleming@digium.com> Fri, 05 February 2010 15:02 UTC

Return-Path: <kpfleming@digium.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 57C573A695E for <sipping@core3.amsl.com>; Fri, 5 Feb 2010 07:02:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 0yKOK81nW41G for <sipping@core3.amsl.com>; Fri, 5 Feb 2010 07:02:22 -0800 (PST)
Received: from mail.digium.com (mail.digium.com [216.207.245.2]) by core3.amsl.com (Postfix) with ESMTP id 4EF3D28C159 for <sipping@ietf.org>; Fri, 5 Feb 2010 07:02:22 -0800 (PST)
Received: from zimbra.digium.internal ([10.24.55.203] helo=zimbra.hsv.digium.com) by mail.digium.com with esmtp (Exim 4.69) (envelope-from <kpfleming@digium.com>) id 1NdPiC-00020K-40; Fri, 05 Feb 2010 09:03:12 -0600
Received: from localhost (localhost.localdomain [127.0.0.1]) by zimbra.hsv.digium.com (Postfix) with ESMTP id 1F524D8024; Fri, 5 Feb 2010 09:03:12 -0600 (CST)
Received: from zimbra.hsv.digium.com ([127.0.0.1]) by localhost (zimbra.hsv.digium.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1aKM841MsZqw; Fri, 5 Feb 2010 09:03:11 -0600 (CST)
Received: from [172.19.1.105] (173-24-205-147.client.mchsi.com [173.24.205.147]) by zimbra.hsv.digium.com (Postfix) with ESMTPSA id 782E0D8023; Fri, 5 Feb 2010 09:03:11 -0600 (CST)
Message-ID: <4B6C332E.9080402@digium.com>
Date: Fri, 05 Feb 2010 09:03:10 -0600
From: "Kevin P. Fleming" <kpfleming@digium.com>
Organization: Digium, Inc.
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: "Elwell, John" <john.elwell@siemens-enterprise.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>
In-Reply-To: <A444A0F8084434499206E78C106220CAB9210933@MCHP058A.global-ad.net>
X-Enigmail-Version: 0.95.7
OpenPGP: id=05FB8DB2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: "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: Fri, 05 Feb 2010 15:02:23 -0000

Elwell, John wrote:
> Vijay,
> 
> Thanks, but I was concerned that a domain name beginning with "." might be wrong; Taking the SIP ABNF as an example (SDP ABNF isn't so precise), we have:
> 
> hostname         =  *( domainlabel "." ) toplabel [ "." ] 

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.

-- 
Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
skype: kpfleming | jabber: kpfleming@digium.com
Check us out at www.digium.com & www.asterisk.org

v2.23.0 | Report a Bug | By Email