Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • BIND BIND
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 532
    • Issues 532
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 101
    • Merge requests 101
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source Projects
  • BINDBIND
  • Issues
  • #2633

Closed
Open
Created Apr 14, 2021 by Everett Fulton@ebfReporter

Allow RPZ filtering based on SVCB/HTTPS RDATA

A support customer has reported that response-policy filtering is not blocking based on the presence of blocked IPs in the RDATA of SVCB and HTTPS records:

https://support.isc.org/Ticket/Display.html?id=18156

Doing so would have been in conflict with section 4.3 of draft-ietf-dnsop-svcb-https, but a change was accepted in Last Call process to relax this:

https://mailarchive.ietf.org/arch/msg/dnsop/9_GXre5UVskG3VVguTVfnDzggN0/

https://github.com/MikeBishop/dns-alt-svc/pull/313

This would close a loophole that would weaken the purpose of response-policy.

Assignee
Assign to
Time tracking