Re: [DNSOP] End of Life Notice for ITAR / State of ARPA.

On 2010-12-01, at 10:40, Joe Abley wrote: > I appreciate that there is eagerness amongst the technical community to see a > DS record in the root zone. Operationally, we are ready. I have no > information on the expected time at which the root zone change processing for > ARPA's DS RRSet will

Re: [DNSOP] Neglect for RFC3597 for 128 <= RTYPES < 256. Should such RTYPES be off limits to allocation?

This is the wrong list for this as this is a protocol issue. Redirecting to dns...@ietf.org. In message <50da0744-6dda-446a-b4ae-c897f440d...@icsi.berkeley.edu>, Nicholas W eaver writes: > Much to my embarrassment, our Netalyzr test for RFC3597 (unknown RRTYPE > handling. We used RRTYPE=

[DNSOP] Neglect for RFC3597 for 128 <= RTYPES < 256. Should such RTYPES be off limits to allocation?

Much to my embarrassment, our Netalyzr test for RFC3597 (unknown RRTYPE handling. We used RRTYPE=169 for our testing, as its unassigned yet a convenient mnemonic) was broken for us by the upstream authorities in our path without my realizing it: Bad enough is that all of the a

[DNSOP] Question on recursive resolvers to test against..

One thing we've observed in Netalyzr is that RFC3597 (handling unknown RRTYPEs as opaque binary data) is almost universally ignored. Does anyone have a good set of open recursive resolvers from different vendors that can be queried against for testing? _

Re: [DNSOP] End of Life Notice for ITAR / State of ARPA.

Hi Alfred, On 2010-12-01, at 08:06, Alfred HÎnes wrote: > It is now going to be two weeks since the IANA ITAR has been > factually decommissioned, but still the last entry that has > been removed from the ITAR, the DS record for the ARPA. zone, > has not been placed into the root zone -- as confi

Re: [DNSOP] End of Life Notice for ITAR / State of ARPA.

It is now going to be two weeks since the IANA ITAR has been factually decommissioned, but still the last entry that has been removed from the ITAR, the DS record for the ARPA. zone, has not been placed into the root zone -- as confirmed by today's TLD DNSSEC Report: