Re: [homenet] Name service design principles: a proposal

[Kerry Lynn <[e-mail]>]

On Fri, Jun 29, 2012 at 4:09 PM, Ralph Droms <[e-mail]> wrote:

>
> On Jun 29, 2012, at 3:58 PM 6/29/12, james woodyatt wrote:
>
> > On Jun 29, 2012, at 11:27 , Michael Thomas <[e-mail]> wrote:
> >>
> >> Maybe I can add some fuel to Olafur's fire. I'd like to say that the
> homenet name service MUST be DNS.
> >
> > Let's go further.  Let's say that it must be DNS-Based Service Discovery
> [I-D.cheshire-dnsext-dns-sd], which has been in the RFC Editor Queue for
> 199 days at this point, so one imagines that it stands a decent chance of
> being a published RFC by the time HOMENET finishes its first round of major
> work.
>
> Hear, hear!


> Well, DNS-Based Service Discovery addresses just one kind of requirement:
> listing entities that provide a certain kind of service; perhaps
> generalizable to resolution based on a characteristic or set of
> characteristics that might return more than one response to the resolution
> request.  At some point, there needs to be a mechanism for resolving an
> identity to a single IP address.
>
> Actually, a Multicast DNS responder (mDNS is the multicast version of
DNS-SD)
will allow you to resolve A, AAAA records:

Kerrys-MacBook-Pro:6in4 kerlyn$ dig -p 5353 @224.0.0.251 _http._tcp.local
PTR     <<<< We first discover web servers

; <<>> DiG 9.7.3-P3 <<>> -p 5353 @224.0.0.251 _http._tcp.local PTR
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33690
;; flags: qr aa; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 4

;; QUESTION SECTION:
;_http._tcp.local. IN PTR

;; ANSWER SECTION:
_http._tcp.local. 10 IN PTR
Officejet\032Pro\0328500\032A909g\032[4C0EA4]._http._tcp.local.

;; ADDITIONAL SECTION:
Officejet\032Pro\0328500\032A909g\032[4C0EA4]._http._tcp.local. 10 IN SRV 0
0 80 HP4C0EA4.local.
Officejet\032Pro\0328500\032A909g\032[4C0EA4]._http._tcp.local. 10 IN TXT ""
HP4C0EA4.local. 10 IN A 192.168.1.31
HP4C0EA4.local. 10 IN AAAA fe80::dad3:85ff:fe4c:ea4

;; Query time: 20 msec
;; SERVER: 192.168.1.31#5353(224.0.0.251)
;; WHEN: Fri Jun 29 16:13:10 2012
;; MSG SIZE  rcvd: 168



Kerrys-MacBook-Pro:6in4 kerlyn$ dig -p 5353 @224.0.0.251 HP4C0EA4.local A
  <<<< We can also resolve the host record

; <<>> DiG 9.7.3-P3 <<>> -p 5353 @224.0.0.251 HP4C0EA4.local A
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40117
;; flags: qr aa; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;HP4C0EA4.local. IN A

;; ANSWER SECTION:
HP4C0EA4.local. 10 IN A 192.168.1.31

;; Query time: 1 msec
;; SERVER: 192.168.1.31#5353(224.0.0.251)
;; WHEN: Fri Jun 29 16:13:39 2012
;; MSG SIZE  rcvd: 48



Kerrys-MacBook-Pro:6in4 kerlyn$ dig -p 5353 @192.168.1.31 HP4C0EA4.local A
   <<<< We can just as easily unicast the query

; <<>> DiG 9.7.3-P3 <<>> -p 5353 @192.168.1.31 HP4C0EA4.local A
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32090
;; flags: qr aa; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;HP4C0EA4.local. IN A

;; ANSWER SECTION:
HP4C0EA4.local. 10 IN A 192.168.1.31

;; Query time: 2 msec
;; SERVER: 192.168.1.31#5353(192.168.1.31)
;; WHEN: Fri Jun 29 16:17:47 2012
;; MSG SIZE  rcvd: 48



> - Ralph
>
> >
> >
> > --
> > james woodyatt <[e-mail]>
> > member of technical staff, core os networking
> >
> > [*] <http://datatracker.ietf.org/doc/draft-cheshire-dnsext-dns-sd/>
> > _______________________________________________
> > homenet mailing list
> > [e-mail]
> > https://www.ietf.org/mailman/listinfo/homenet
>
> _______________________________________________
> homenet mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/homenet
>