Skip to content

Handling malformed/forged _domainconnect RR #180

Open
Open
Handling malformed/forged _domainconnect RR#180
Labels
IETFIssues reported from IETF processIETF Draft: CorePrioIssues with priority to talk about
@pawel-kow

Description

@pawel-kow
pawel-kow
opened on Mar 23, 2026

https://mailarchive.ietf.org/arch/msg/dconn/ZBOHz9sE-y7DbGtaaeTiaLlFFoM

I also realised a more dangerous scenario: malicious domain with _domainconnect record pointing to malformed http resource / oversized file etc. (potential DoS of Service Provider), or internal URL of server infrastructure. I think these are additions to Security Considerations I would take.

Metadata

Metadata

Assignees

No one assigned

    Labels

    IETFIssues reported from IETF processIETF Draft: CorePrioIssues with priority to talk about

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions