Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Kea Kea
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 556
    • Issues 556
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 66
    • Merge requests 66
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source ProjectsISC Open Source Projects
  • KeaKea
  • Issues
  • #185
Closed
Open
Issue created Oct 24, 2018 by Thomas Markwalder@tmarkMaintainer

Examine IA_NA prefix length values in our code for consistency and usability

The following support ticket: https://support.isc.org/Ticket/Display.html?id=13645, raises an issue with our inconsistent handling of prefix length for IA_NA leases and reservations within the code base.

While the immediate issue raised by the ticket seems to be mitigated by changes made for Global Host Reservations, we should still spend time analyzing our code for both consistency and usability. Primarily we to decide if, we allow values of both 0 and 128, or only 128.

This may require polling the user community.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking