In message <6fe949c2-18f3-432d-ab75-f66e71570...@hopcount.ca>, Joe Abley writes
:
> Hi all,
>
> The only suggestion I have heard relating to this draft is that if we supplie
> d custom software to synthesise answers we could avoid the overly-broad SOA R
> R returned with the NXDOMAIN.
>
> (My pe
Hi Joe,
At 11:15 27-06-2012, Joe Abley wrote:
- it would be just as good for this document to proceed as an
individual submission, since it will see dns directorate review
anyway and hence all bases will be covered
That's not a good idea.
- this wg already has enough trouble processing the
On Wed, 27 Jun 2012, Joe Abley wrote:
Hi all,
The only suggestion I have heard relating to this draft is that if we supplied
custom software to synthesise answers we could avoid the overly-broad SOA RR
returned with the NXDOMAIN.
(My personal opinion is that this leads us down a path of need
On Jun 27, 2012, at 11:15 AM, Joe Abley wrote:
> Hi all,
>
> The only suggestion I have heard relating to this draft is that if we
> supplied custom software to synthesise answers we could avoid the
> overly-broad SOA RR returned with the NXDOMAIN.
> (My personal opinion is that this leads us
On 6/27/2012 6:15 PM, Joe Abley wrote:
> ...
> Adopt this doc?
yes please.
___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
Hi all,
The only suggestion I have heard relating to this draft is that if we supplied
custom software to synthesise answers we could avoid the overly-broad SOA RR
returned with the NXDOMAIN.
(My personal opinion is that this leads us down a path of needing to develop,
publish and support part
