Signaling Trust Anchor Knowledge in DNS Security Extensions (DNSSEC)
RFC 8145

Note: This ballot was opened for revision 03 and is now closed.

(Stephen Farrell) Yes

Comment (2017-02-15 for -04)
- abstract: referring to section 1.1 from here seems wrong,
the abstract ought be readable by itself

- section 5: Is the key tag query only and solely intended to
allow the authoritative to track how clients are paying
attention (or not) to key rollovers? If there's another
purpose I'm not clear about it.

- 5.3: "I believe that to be..." seems like the wrong language
to use with >1 author.

- section 7/8: Is there a missing security/privacy
consideration here, in that an authoritative server here could
arrange to hand out key tags that are specific to (in the
limit) each query, so that when the resolver queries a
sub-domain, and thereafter, the client will be identifiable to
the authoritative server?  One could do this by generating new
keys per querier so that if I ask about I get
given a tag that's unique to me, and then some web content
pushes me to ask about and every time I do
that I emit that user-specific key tag. While that'd be
unlikely for a large zone, it might be feasible as a tracker
if some "bad" domain sets up a specific subdomain for such
purposes. That said, I'm not clear how much better this is for
the attacker compared to simply using a tracking name in the
authority component of the URL for e.g. some 1x1 gif.

(Joel Jaeggli) Yes

(Jari Arkko) No Objection

(Alia Atlas) No Objection

Deborah Brungard No Objection

Ben Campbell No Objection

Comment (2017-02-15 for -04)
It's unfortunate that the working group couldn't agree on one mechanism, but that's not enough to stand in the way of publication.

(Benoit Claise) No Objection

Comment (2017-02-16 for -04)
Discussion engaged between the Mahesh (OPS DIR reviewer) and the author.

Alissa Cooper No Objection

Spencer Dawkins No Objection

Suresh Krishnan No Objection

Mirja K├╝hlewind No Objection

Terry Manderson No Objection

Alexey Melnikov No Objection

Comment (2017-02-15 for -04)
I am doubtful that this will deploy, considering that there are 2 mechanism.

Are there existing or planned implementations of both approaches? I am sorry if I missed that in the shepherding writeup.

(Kathleen Moriarty) No Objection

Alvaro Retana No Objection