Re: Question on draft-ietf-sipping-v6-transition-07

"Somogyi, Gabor (NSN - HU/Budapest)" <[email protected]>
Newsgroups gmane.ietf.sipping
Message-ID <E384AABE63D1704BA0944D6B9BE57F0C02775D1B@FIESEXC006.nsn-intra.net>
The dot before "invalid" indicates that "invalid" is a TLD. See also
section 2 of RFC 2606.

BTW, 3GPP TS 29.231 (http://3gpp.org/ftp/Specs/html-info/29231.htm)
describes the same for unspecified connection address.

So create whatever domain name you like within ".invalid" TLD. I think
"x.invalid" is a reasonably short one.

BR,
Som

-----Original Message-----
From: [email protected] [mailto:[email protected]] On
Behalf Of ext Dale Worley
Sent: Friday, February 05, 2010 20:30
To: Vijay K. Gurbani
Cc: Elwell, John; [email protected]
Subject: Re: [Sipping] Question on draft-ietf-sipping-v6-transition-07

On Thu, 2010-02-04 at 14:37 -0600, Vijay K. Gurbani wrote:
> On 02/03/2010 10:07 AM, Elwell, John wrote:
> > Presumably just "invalid" (alone, as opposed to "xxxx.invalid" would
be legal?
> 
> John: I think ".invalid" itself suffices, but I will defer to 
> Gonzalo's view on this.

Why have we put a leading "." on "invalid"?  We do not write, e.g.,
".bell-labs.com".  I know of no other place where a domain name is
written with a leading period.

Dale


_______________________________________________
Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP Use
[email protected] for questions on current sip Use
[email protected] for new developments of core SIP
_______________________________________________
Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use [email protected] for questions on current sip
Use [email protected] for new developments of core SIP
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.