Dear Patrick, Thank you for your careful review of the draft and for pointing out these important details.Regarding the examples:You're absolutely right that WALLET(wip), CERT, and TLSA already exist as RR types. This was actually intentional - we chose existing record types as examples precisely because they represent legitimate real-world use cases with proven value. Our intention was to illustrate how these established RR types might have achieved broader adoption more quickly if they had started with a prefixed TXT transition approach before migrating to their dedicated RR types.We wanted to use concrete, practical examples rather than purely hypothetical ones, but I can see how this might create confusion. We'll revise the draft to make it explicitly clear that we're using these existing RR types as retrospective examples to demonstrate the potential benefits of our proposed transition mechanism.Regarding the RFC numbers:Thank you for flagging this issue. We may consider replace all references to existing unrelated RFC numbers (RFC7777, 8888, etc.) with clearly hypothetical placeholders like RFCNNNN, RFCMMMM, RFCOOOO, and RFCPPPP to avoid any confusion with actual RFCs.We appreciate your feedback and will incorporate these changes in the next revision of the draft. (Sorry your original email <https://mailarchive.ietf.org/arch/msg/dnsop/_wcjiSMB5b7VlRReWWamtA-KTTE/#> didn't go in my inbox and I found it from IETF Mailman Archive, so I am replying here. It may break the thread tree.) Best regards,Victor
Re: (from pmev...@godaddy.com) You might want to choose other examples on things that could exist… as what you list already exists: §3.1 WALLET: already exists as RRtype, see value 262 in IANA registry §3.2 and §3.3 about basically storing public keys and certificates: see record types CERT, OPENPGPKEY, and TLSA. Also not using RFC numbers already existing and unrelated would be better I think. >
_______________________________________________ DNSOP mailing list -- dnsop@ietf.org To unsubscribe send an email to dnsop-le...@ietf.org
