Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-edns-client-subnet

[Dave Lawrence]

Ted Lemon writes:
> It would be helpful if the authors could explain why the REFUSED
> response is being used here.

Not to be glib, but because that's what Wilmer originally specified.
That's thus what got implemented by the existing implementations (and
there are more than you'd likely imagine, too).  

> Do people think this is the right thing to do

No, I don't.  Thus I'm working on addressing that and several other
protocol issues in a new draft.

>  My preference would be to allocate a new EDNS0 response code, point
>  out that existing implementations do something different, which
>  behavior is actually a bad idea, and recommend against adding such
>  behavior to new implementations. 

This is what I intend to do.

___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop

[DNSOP] RFC 7646 on Definition and Use of DNSSEC Negative Trust Anchors

[rfc-editor]

A new Request for Comments is now available in online RFC libraries.


RFC 7646

Title:  Definition and Use of DNSSEC 
Negative Trust Anchors 
Author: P. Ebersman, W. Kumari,
C. Griffiths, J. Livingood,
R. Weber
Status: Informational
Stream: IETF
Date:   September 2015
Mailbox:ebersman-i...@dragon.net, 
war...@kumari.net, 
cgriffi...@gmail.com, 
jason_living...@cable.comcast.com, 
ralf.we...@nominum.com
Pages:  16
Characters: 36117
Updates/Obsoletes/SeeAlso:   None

I-D Tag:draft-ietf-dnsop-negative-trust-anchors-13.txt

URL:https://www.rfc-editor.org/info/rfc7646

DOI:http://dx.doi.org/10.17487/RFC7646

DNS Security Extensions (DNSSEC) is now entering widespread
deployment.  However, domain signing tools and processes are not yet
as mature and reliable as those for non-DNSSEC-related domain
administration tools and processes.  This document defines Negative
Trust Anchors (NTAs), which can be used to mitigate DNSSEC validation
failures by disabling DNSSEC validation at specified domains.

This document is a product of the Domain Name System Operations Working Group 
of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-edi...@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop