I think there’s something elided from that sentence, since, irrespective of
semantics, “An outcome of that the convention …” isn’t even
grammatically-correct English.
- Kevin
From: DNSOP [mailto:dnsop-boun...@ietf.org] On Behalf Of Bob Harold
Sent: Friday, October 30, 2015 9:34 AM
To: Edward Lewis
Cc: dnsop
Subject: Re: [DNSOP] Draft -domain-names-01
On Fri, Oct 30, 2015 at 7:23 AM, Edward Lewis
<edward.le...@icann.org<mailto:edward.le...@icann.org>> wrote:
A while back I floated a draft across this mail list and got (what I
think) is sufficient (perhaps not the right word) feedback from the WG. I
updated the document and resubmitted. FWIW, this is the document link:
https://tools.ietf.org/html/draft-lewis-domain-names-01
I'm not even asking for comment on the list (but you can if you want).
When I rev'd the document, I didn't mention it on this list (until now).
What I'm asking for is - when in Yokohama, if you have an interest in this
I'm willing to discuss.
The issue in the document is both internal to DNS and external to DNS, I'm
looking for broader input (such as applications area topics).
Ed
I have to disagree with one section:
Section 3.1 includes:
A DNS domain name "192.0.2.1." can be configured and used in the
protocol. The usefulness of this is limited by the concerns
described later on in Interoperability Considerations. An outcome of
that the convention of representing the Domain Name "192.0.2.1." as
"1.2.0.192.in-addr.arpa."
I agree that "192.0.2.1." is a domain name. But it is a totally different
domain name than "1.2.0.192.in-addr.arpa.".
"1.2.0.192.in-addr.arpa." is the typical domain name representation of the IP
address "192.0.2.1", which is a 32 bit number, not a name. There is no 'root'
or trailing dot in an IP address.
--
Bob Harold
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
