IETF Logo Mail Archive

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

"Elwell, John" <john.elwell@siemens-enterprise.com> Fri, 05 February 2010 15:44 UTC

Return-Path: <john.elwell@siemens-enterprise.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 9359C28C160 for <sipping@core3.amsl.com>; Fri, 5 Feb 2010 07:44:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.546
X-Spam-Level:
X-Spam-Status: No, score=-2.546 tagged_above=-999 required=5 tests=[AWL=0.053, 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 0-f9U1QQzbR0 for <sipping@core3.amsl.com>; Fri, 5 Feb 2010 07:44:26 -0800 (PST)
Received: from ms04.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 0536628C141 for <sipping@ietf.org>; Fri, 5 Feb 2010 07:44:25 -0800 (PST)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms04.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-795087; Fri, 5 Feb 2010 16:45:15 +0100
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx11-mx (Server) with ESMTP id B3B4A1EB82AB; Fri, 5 Feb 2010 16:45:15 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Fri, 5 Feb 2010 16:45:15 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "Kevin P. Fleming" <kpfleming@digium.com>
Date: Fri, 05 Feb 2010 16:45:14 +0100
Thread-Topic: [Sipping] Question on draft-ietf-sipping-v6-transition-07
Thread-Index: AcqmdFtiK/hGUxQTQWmAdlzg8x4yfwABc2rw
Message-ID: <A444A0F8084434499206E78C106220CAB92995DE@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> <4B6B2FF0.5030007@bell-labs.com> <A444A0F8084434499206E78C106220CAB9210933@MCHP058A.global-ad.net> <4B6C332E.9080402@digium.com>
In-Reply-To: <4B6C332E.9080402@digium.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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:44:27 -0000

Thanks, that seems to make sense to me.

John 

> -----Original Message-----
> From: Kevin P. Fleming [mailto:kpfleming@digium.com] 
> Sent: 05 February 2010 15:03
> To: Elwell, John
> Cc: Vijay K. Gurbani; sipping@ietf.org
> Subject: Re: [Sipping] Question on draft-ietf-sipping-v6-transition-07
> 
> 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