danwing
commented
1 year ago Agreed that "*" is clearer to people and code.
-d
On Mar 15, 2023, at 9:11 AM, Benjamin M. Schwartz @.***> wrote:
In draft-08, a claimed subdomain is represented by stripping off the suffix that matches the parent (e.g. "payroll.internal.example.com" - "example.com" = "payroll.internal."). To claim the entire parent zone, the claimed subdomain is "." (or the empty string, in contexts where the terminal "." is omitted, such as PvD JSON). This is sort of logical but also a bit strange, and might require special-case handling in code.
If we need a special case, maybe we should be more explicit and use "*" instead.
— Reply to this email directly, view it on GitHub https://github.com/ietf-wg-add/draft-ietf-add-split-horizon-authority/issues/21, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABNZQVC3TEQNOGFNO2WAT3TW4HS4LANCNFSM6AAAAAAV4B3C2U. You are receiving this because you are subscribed to this thread.
tireddy2
In draft-08, a claimed subdomain is represented by stripping off the suffix that matches the parent (e.g. "payroll.internal.example.com" - "example.com" = "payroll.internal."). To claim the entire parent zone, the claimed subdomain is "." (or the empty string, in contexts where the terminal "." is omitted, such as PvD JSON). This is sort of logical but also a bit strange, and might require special-case handling in code.
If we need a special case, maybe we should be more explicit and use "*" instead.