my bad. I've been re-framed. Contextually, PUSH means (to me at least) 'do this promiscuously' and PULL means (to me at least) 'do this if asked' -which is not what I previously understood.
In that case, I think PULL makes more sense: do this, if the client signals its what it wants. Otherwise, don't do this. Its the POLA behaviour. (thanks for Paul Hoffman's cluestick hit) -G On Tue, Aug 16, 2016 at 10:57 PM, Tim Wicinski <tjw.i...@gmail.com> wrote: > All, > > > In Berlin we had two presentations on different methods of returning > multiple responses: > > https://datatracker.ietf.org/doc/draft-wkumari-dnsop-multiple-responses/ > > https://datatracker.ietf.org/doc/draft-bellis-dnsext-multi-qtypes/ > > and a presentation in Buenos Aires: > > https://datatracker.ietf.org/doc/draft-vavrusa-dnsop-aaaa-for-free/ > > All of these documents are attempting to solve a larger problem in different > ways. > The end result is "Return Associated Answer" to the client. > > The question is starting to coalesce around these two premises: > > - Do we want to Server to PUSH any or all Associated Answers, or > > - Do we want the Client to PULL any or all Associated Answers, or > > - Do we want the Status Quo? > > thanks > tim > > > > (Thanks to Paul Hoffman for assistance) > > _______________________________________________ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
