On Wed, Oct 9, 2019 at 12:04 AM wrote:
> Dear dnsop WG,
>
> Please review draft-fujiwara-dnsop-avoid-fragmentation-01.
> https://tools.ietf.org/html/draft-fujiwara-dnsop-avoid-fragmentation-01
>
> Main differences are:
> - New Co-author
> - Refer RFC 8085 UDP Usage Guidelines
> - SHOULD send DN
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 : Moving DNSSEC Lookaside Validation (DLV) to Historic
Status
Authors : Matthijs Mekking
On Tue, 8 Oct 2019, Ladislav Lhotka wrote:
(added IESG to CC:)
We don't want to have to update the RFC every time the registry is updated.
Could the RFC just describe exactly how to to convert the registry to YANG?
Then it won't need updates.
Only the initial version of the YANG module will
On Tue, 8 Oct 2019, Ladislav Lhotka wrote:
Speaking for myself, as long as we are not populating RFCs with
obsoleted DNS data or just create RFC with copies of IANA registries,
I'm fine with helping on a document. But not if it is a blind copy
and paste from IANA (whether at DNSOP or OPSAWG)
I
There's an interesting (web-only) effort looking at a similar problem:
https://github.com/krgovind/first-party-sets There, the goal is to establish
commonality for the purposes of sharing state (and fate).
A great counter-example in that case is the relationship between github.com and
github.i
