On 22/10/2012 18:30, Michael Thomas wrote:
> On 10/22/2012 09:31 AM, Brian E Carpenter wrote:
>> On 19/10/2012 18:16, Michael Thomas wrote:
>>> On 10/19/2012 09:36 AM, Tim Chown wrote:
>>>>
>>>> We can take comments towards a -06 over the weekend. The most
>>>> substantial changes are in the Naming and Service Discovery section
>>>> (3.7), so if you have limited time please focus your reading there.
>>> One thing that I'm not sure whether it's been discussed or not is
>>> service announcement.
>>> By service announcement, I mean where instead of multicasting out a
>>> message looking
>>> for the canonical printer with all of its nasty properties especially
>>> for things with batteries
>>> and lossy/slow networks, a device would instead announce its presence to
>>> something
>>> that would later serve it up (eg, bind9, say).
>> e.g. an SLP Directory Agent, designed for this purpose some years ago.
>> [RFC2608], [RFC2610], [RFC3059], [RFC3224], [RFC3421], and [RFC3832]
>> This is not exactly a new problem.
>>
>
> I looked this over, and I don't think it's what I'm thinking of. I'm
> thinking of literally having a device do an IXFR to a real DNS server.
> Or something that looks pretty similar to an IXFR, but the key being
> that it's a real DNS server. No multicast required ever.
>
> In any case, even if this isn't new ground maybe the problem was that
> they didn't hitch their wagon to DNS. Deployment of SLP is I'm guessing
> pretty thin.
I'm told that it's widely implemented (at least in printers) but rarely
used. All I'm saying is that it should be on the candidate list.
(And if the WG charter limits the list of candidates, that's a bug in
the charter that will need to be fixed.)
Brian
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
