Hi Libor, Tom,
Thanks for this, I believe this will be a good extension to the EDNS
specification to help operators hunt down issues. I support its
adoption by the WG. Should the WG disagree, please submit it as an
individual submission.
On Wed, 2022-11-23 at 20:25 +0100, libor.peltan wrote:
>
Hello DNS enthusiasts and other developers,
After three earlier successful and packed DNS devrooms at FOSDEM 2018,
2019, and 2020, we are happy to announce a half-day DNS devroom at
FOSDEM 2023.
As with the previous events, we hope to host talks anywhere from
hardcore protocol stuff, to
Hi Joe,
On 5/10/21 1:42 AM, Joe Abley wrote:
> On May 9, 2021, at 19:27, Paul Hoffman wrote:
>
>> If I'm wrong about this being as good as it can be, there must be an item
>> delimiter that is better than a comma. I am not thinking creatively enough
>> to figure out what might be better than
Hi Dick,
On 5/10/21 1:02 PM, Dick Franks wrote:
> My objection is narrowly focussed on the escape mechanism, nothing
> more. Changing the delimiter is neither necessary nor relevant.
>
> I am happy to contribute the necessary words.
If you have the words to fix this issue that would need to
Hi Dick,
On 5/9/21 2:01 PM, Dick Franks wrote:
> Pre-processing of '\\,' into the RFC1035 standard '\,' is
> superficially attractive, but also fraught with danger.
>
> A parser could have some fun with this one:
>
> $ORIGIN example.com
> @ SVCB 1 foo
>
,bar' that is then parsed to a list of length 1
with value {'foo,bar'}. So nothing changes from the perspective of the
rfc 1035 parser.
I can see how this might be confusing to those writing zone contents and
would support a solution that either prohibits comma's in SVCParam list
values or a differen
s appendix.
I'll try to update the vectors this week, changing the format and adding
some missed cases as well.
Cheers,
Pieter
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
S/pdns/pull/10074/files#diff-1c55ae7b2d1073637c05a035de9ef6688ecffb209e50b3bef8b3d9ea1c5a329dR308-R393
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
is can still be added?
+1000
The PowerDNS unit tests already has a bunch of tests that do the
presentation -> wire -> presentation roundtrip. I could convert those to
using example.com, use some more hex and send a PR to the authors should
they want this.
Cheers,
Pieter
--
Pieter Lex
hint to the end-client that it MUST understand the
keys mentioned in order to use the RR? If that is the case, a few words
to that effect would be good.
I hope the rambling above makes the question clear.
Cheers,
Pieter
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
_
Hi,
On 3/18/21 6:42 PM, Tommy Pauly wrote:
> Personally, I’d prefer to see the name change, and not burn a codepoint,
> as long as we’re not breaking any zone files.
Agree.
> I think the question is: does anyone have a zone that has actually
> deployed the echconfig parameter? I see many
Hi folks,
On 10/15/20 12:05 AM, Benno Overeinder wrote:
> Current versions of the draft are available here:
> https://datatracker.ietf.org/doc/draft-ietf-dnsop-iana-class-type-yang/
>
> The Current Intended Status of this document is: Standards Track
>
> Benno Overeinder will be Document
On 8/5/20 11:13 PM, Mark Andrews wrote:
>> On 6 Aug 2020, at 04:51, Pieter Lexis wrote:
>> On 8/5/20 8:03 PM, Brian Dickson wrote:
>>> (I am not sure of the question/issue of including the SOA, or where that
>>> would go, but I'll defer to anyone who knows or has a
On 8/5/20 8:03 PM, Brian Dickson wrote:
>
>
> On Wed, Aug 5, 2020 at 10:08 AM Ben Schwartz
> <mailto:40google@dmarc.ietf.org>> wrote:
>
> On Wed, Aug 5, 2020 at 12:06 PM Pieter Lexis
> mailto:pieter.le...@powerdns.com>> wrote:
> ...
>
&g
s the case with an in-zone CNAME)
considered an answer and should they go into the ANSWER section?
I find the alias mode semantics (on the DNS-level) unclear and
under-specified in the draft. I look forward to guidance from the authors.
Best regards,
Pieter
--
Pieter Lexis
PowerDNS.COM B
,
The FOSDEM 2020 DNS Devroom organizers
P.S. Apologies to those receiving multiple copies of these emails.
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
ETCONF ecosystem can benefit from this document being
published.
Best regards,
Pieter
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
ikely) a NODATA in that case.
Best regards,
Pieter
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
ve.
> Please also indicate if you are willing to contribute text, review, etc.
As Peter is a direct colleague of mine, I will not supply a review, but am
willing to provide text.
Best regards,
Pieter
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
or a CNAME for a node that only has an ALIAS record should
yield a response indicating that RRType does not exist at that node.
Again, thank you for starting this draft. I support adoption of this draft in
the dnsop WG to facilitate better interop between ALIAS/ANAME/CNAME-flattening
implemento
rds,
Pieter
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
21 matches
Mail list logo