Issues
--
* ietf-wg-dnsop/draft-ietf-dnsop-domain-verification-techniques (+1/-0/💬3)
1 issues created:
- Re-org discussion (Jan 29) (by ShivanKaul)
https://github.com/ietf-wg-dnsop/draft-ietf-dnsop-domain-verification-techniques/issues/167
2 issues received 3 new comments:
- #167
Paul Hoffman wrote:
> On Feb 1, 2025, at 15:49, Robert Edmonds wrote:
> > If comments aren't allowed, what about parens, embedded newlines, \DDD
> > and \X escapes, etc.?
>
> None of that; I'll add more prohibitions. Thanks again for asking good
> questions!
OK, so does this imply only names an
On Feb 1, 2025, at 15:49, Robert Edmonds wrote:
>
> Paul Hoffman wrote:
>>> So does a DUJ encode the display format of record data,
>>> or does it encode a zone file fragment that embeds the display format of
>>> record data?
>>
>> It encodes the display format. The draft says "The strings are e
It appears that Paul Hoffman said:
>> Not all record types are encoded as one or more 's,
>> for instance the SOA RDATA encodes two 's followed by five
>> 32-bit integers. Should that be represented like this?
>>
>>["DUJ", [["add", "yourname.example", "SOA",
>> "ns1.yourname.example", "
Paul Hoffman wrote:
> > So does a DUJ encode the display format of record data,
> > or does it encode a zone file fragment that embeds the display format of
> > record data?
>
> It encodes the display format. The draft says "The strings are expressed in
> the same manner as the display format def
On Sat, 1 Feb 2025, Paul Hoffman wrote:
a TXT foo bar
b TXT "foo bar"
The first one has two strings of three characters each, the second has one
string of seven characters, and they mean different things.
The fact that RFC 1035 didn't define this well has been discussed ad nauseam for
>30 ye
On Feb 1, 2025, at 15:10, John R Levine wrote:
>
>>> ["DUJ", [["add", "yourname.example", "TYPE4321", "\# 4 0A01"]]
>>>
>>> IF you put quotes around it, you'll get the wrong answer.
>>
>> I assumed that software that is updating zone files would know this; the
>> examples in RFC 3597 are p
["DUJ", [["add", "yourname.example", "TYPE4321", "\# 4 0A01"]]
IF you put quotes around it, you'll get the wrong answer.
I assumed that software that is updating zone files would know this; the
examples in RFC 3597 are pretty clear about that. But I"ll add a note
about that because differ
Thanks for the detailed review!
On Feb 1, 2025, at 13:47, Robert Edmonds wrote:
>
> Paul Hoffman wrote:
>> Greetings again. The following is a proposal to help end-users who are told
>> "please enter this record in your zone to prove your existence". It
>> simplifies the process without automa
Paul Hoffman wrote:
> Greetings again. The following is a proposal to help end-users who are told
> "please enter this record in your zone to prove your existence". It
> simplifies the process without automating it; in short, it makes
> copy-and-pasting more likely to work, particularly for the
On Jan 31, 2025, at 00:42, Libor Peltan wrote:
>
> If I understand the background correctly, it might also help to declare that
> the DNS software vendors SHOULD NOT develop tools that automatically convert
> DUJ into DDNS and send it to a nameserver.
I'm not sure why you say that. Automating
On Jan 31, 2025, at 10:25, John Levine wrote:
>
> It appears that Paul Hoffman said:
>> Greetings again. The following is a proposal to help end-users who are told
>> "please enter this record in your zone to prove your existence". It
>> simplifies the process without automating it; in short,
12 matches
Mail list logo
