[IPP] proposed mods to IPP everywhere spec (per my action item)
Randy Turner
rturner at amalfisystems.com
Mon Apr 9 18:05:03 UTC 2012
Hi Mike,
You're right about multicast DNS not requiring site administration, but dynamic DNS is only designed to update A/AAAA records in a zone. I'm not aware of anyone using dynamic DNS to update TXT, SRV, or other resource records. I haven't seen this done.
Randy
On Apr 9, 2012, at 10:59 AM, Michael Sweet wrote:
> Randy,
>
> Thanks for the text. Comments below.
>
> On Apr 9, 2012, at 10:24 AM, Randy Turner wrote:
>>
>> Hi Guys,
>>
>> Proposed mods for wd-ippeve10-20120201:
>>
>> 4.2.2 Geo-Location (LOC)
>>
>> Site administrators MUST (should this be a "SHOULD" ?) publish LOC records (RFC 1876) to provide the physical location of a printer.
>>
>> 4.2.3 Service Information (TXT)
>> Site administrators MUST publish ("SHOULD" ?)….
>>
>>
>> This document is placing requirements on devices for future compliance with an IPP everywhere standard -- however, DNS requirements are NOT requirements placed on a device, but rather administrative requirements for the site DNS -- so I'm not sure that 4.2.2 and 4.2.3 belong in this document.
>
> Multicast DNS (part of Bonjour, and a perennial draft awaiting love from the IETF DNS WG) is not managed by site administrators and is part of IPP Everywhere.
>
> Also, printers *can* register their own DNS records with traditional DNS infrastructure using dynamic DNS updates (RFC 2136) and many already have support for this...
>
> Anyways, I am happy to note that these are requirements for Multicast DNS and recommendations for traditional DNS.
>
> ________________________________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
>
>
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
More information about the ipp
mailing list