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

Scalability considerations #36

Closed matje closed 5 years ago

matje commented 5 years ago

Scalability is definitely a challenge. The worst case is when you have a very large number of zones sharing the same ANAME target, and that changes address. If ANAME is implemented using existing standard protocol features (i.e. UPDATE, NOTIFY, IXFR) as specified, then the change of address is going to cause a huge volume of modification traffic. But the "as if" clause exists to allow large scale implementations to do clever things to mitigate this.

Add operational considerations section that covers this.

matje commented 5 years ago

Added text on this in the Zone Transfers section and Alternative Setups appendix in #52