each / draft-aname

work on a draft to standardize ANAME/ALIAS records to allow CNAME-like records at the zone apex
7 stars 4 forks source link

Relax requirements about sibling address records #38

Closed matje closed 5 years ago

matje commented 5 years ago

What I had in mind for an -03 revision was to remove any requirements about how the sibling address records are populated. The remaining requirement is that the sibling addresses must work the same way as the target addresses, from the point of view of the end user. The sibling addresses can freely be replaced by the target addresses at any time (provided whatever is doing the substitution can sign the records when that is necessary).

matje commented 5 years ago

I believe this is already the case in -03 now. Closing this issue (feel free to reopen @fanf2 if you think otherwise).