Re: [dnssd] Advertising proxy document updated in git

I haven't published the draft yet, so if you want to see a diff you have to download the XML file, upload it to author-tools.ietf.org <http://author-tools.ietf.org/>, format it there, and then compare it with the previous version. This is easy to do on author-tools—it's one click once you've chosen the file to upload.

> On Nov 15, 2023, at 20:58, Tim Wicinski <tjw.ietf@gmail.com> wrote:
> 
> Thanks Ted.  The comparison link https://dnssd-wg.github.io/draft-ietf-dnssd-advertising-proxy/#go.draft-ietf-dnssd-advertising-proxy.diff
> seems out of date still but reading the changes here https://github.com/dnssd-wg/draft-ietf-dnssd-advertising-proxy/commit/cc71668232f6cd8a6a43e0a3e91f0f5a92c7128b  helped.  I'll need to read it formatted a bit better to dig into your conflict proposals.
> 
> tim
> 
> 
> On Wed, Nov 15, 2023 at 8:07 PM Abtin Keshavarzian <abtink=40google.com@dmarc.ietf.org <mailto:40google.com@dmarc.ietf.org>> wrote:
>> Thanks Ted for updating this. I read the new changes. Overall looks good.
>> 
>> 
>> On Wed, Nov 8, 2023 at 6:55 AM Ted Lemon <elemon=40apple.com@dmarc.ietf.org <mailto:40apple.com@dmarc.ietf.org>> wrote:
>>> We had a good discussion about the advertising proxy document in our meeting on Monday (thanks to everyone who attended!). I promised to do a quick update based on the discussion, which wound up being a bit more work than I'd anticipated. However, I've gotten to a point where I think it's probably worth looking at, and so I've committed these changes to the github repo. I have not published a new version of the document yet. Hopefully Jonathan and Abtin can take a look at the document and see what they think.
>>> 
>>> To summarize what's changed:
>>> - The document now talks specifically and only about the advertising proxy function, and not e.g. the SRP server, or the resolver.
>>> - The document has a lot more detail about how to actually implement an advertising proxy
>>> - I mentioned in San Francisco that it might make sense to use naming hierarchy of some sort to prevent conflicts between discrete namespaces when advertising them using mDNS, which would ordinarily flatten the namespace. This document contains two proposals for how to do this, which I think might actually work without requiring any mDNS changes.
>>> 
>>> I probably made other changes, but it's all a blur now, so please give it a read if you have time and let me know what you think.
>>> 
>>> _______________________________________________
>>> dnssd mailing list
>>> dnssd@ietf.org <mailto:dnssd@ietf.org>
>>> https://www.ietf.org/mailman/listinfo/dnssd
>> _______________________________________________
>> dnssd mailing list
>> dnssd@ietf.org <mailto:dnssd@ietf.org>
>> https://www.ietf.org/mailman/listinfo/dnssd