Re: [DNSOP] I-D Action: draft-ietf-dnsop-dns-zone-digest-02.txt

2019-11-18 Thread Wessels, Duane
> On Nov 7, 2019, at 7:56 PM, Vladimír Čunát wrote: > > Hello! > > On 10/28/19 10:32 PM, Wessels, Duane wrote: >> The one defined hash algorithm SHA384 has been renamed to SHA384-STABLE to >> reflect that it designed for use on stable (or small) zones where it is not >> burdensome to recalcu

Re: [DNSOP] Specification of DNSKEY "Private-key-format"

2019-11-18 Thread Mukund Sivaraman
Hi Victor On Thu, Aug 29, 2019 at 07:25:54PM +0530, Mukund Sivaraman wrote: > Hi Viktor > > On Thu, Aug 29, 2019 at 09:48:31AM -0400, Viktor Dukhovni wrote: > > On Thu, Aug 29, 2019 at 06:25:02PM +0530, Mukund Sivaraman wrote: > > > A tool such as BIND's dnssec-keygen generates the following form

Re: [DNSOP] Second Working Group Last Call for draft-ietf-dnsop-extended-error

2019-11-18 Thread Vladimír Čunát
On 11/14/19 12:05 AM, Viktor Dukhovni wrote: > It'd be a shame (though admittedly not frequent) to have a resolver > retry over TCP just to get the same answer with additional information > it does not need and perhaps does not even understand. EDE codes themselves take very little space, so trunc

[DNSOP] I-D Action: draft-ietf-dnsop-server-cookies-02.txt

2019-11-18 Thread internet-drafts
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Domain Name System Operations WG of the IETF. Title : Interoperable Domain Name System (DNS) Server Cookies Authors : Ondrej Sury

Re: [DNSOP] RFC 8482 (the ANY -> HINFO hack) and DNAME

2019-11-18 Thread Viktor Dukhovni
> On Nov 17, 2019, at 8:35 PM, Mark Andrews wrote: > > Just because broken configuration don’t always cause problems doesn’t mean > that they don’t sometimes. MTA’s need to know what names they are known > by to properly remove MX records from consideration when performing store and > forward. E

Re: [DNSOP] RFC 8482 (the ANY -> HINFO hack) and DNAME

2019-11-18 Thread Paul Vixie
a correct implemention of smtp could pick up the a and from additional data without making any additional queries. it could also ignore cname records in the a/ response and declare that the a/ owner was wrong. we can't break working behaviour no matter what the statistics show. a dr

Re: [DNSOP] RFC 8482 (the ANY -> HINFO hack) and DNAME

2019-11-18 Thread Viktor Dukhovni
> On Nov 18, 2019, at 1:00 PM, Paul Vixie wrote: > > A correct implementation of SMTP could pick up the A and from > additional data without making any additional queries. Some resolvers return "minimal" answers and don't include additional records. MTA's can't rely on getting addresses in

Re: [DNSOP] Specification of DNSKEY "Private-key-format"

2019-11-18 Thread Viktor Dukhovni
> On Nov 18, 2019, at 5:31 AM, Mukund Sivaraman wrote: > >> I am initimately familiar with what these fields mean and the code that >> generates it. The question is not about what the meaning of these fields >> are. >> >> I am asking about where this key format is specified - I want to extend >>

Re: [DNSOP] RFC 8482 (the ANY -> HINFO hack) and DNAME

2019-11-18 Thread Paul Vixie
Viktor Dukhovni wrote on 2019-11-18 12:56:> ... At the end of the day, operating outside the RFC carries some risk, and one should not be cavalier in deploying creative deviations from the spec. However, post-MX CNAME indirection is seen to useful by some to stick to the spec, and since MTAs

[DNSOP] Warren Kumari's Recuse on draft-ietf-dnsop-serve-stale-09: (with COMMENT)

2019-11-18 Thread Warren Kumari via Datatracker
Warren Kumari has entered the following ballot position for draft-ietf-dnsop-serve-stale-09: Recuse When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to http