For an operator standpoint, it seems this point may not be clear enough in the draft and at the very least would likely benefit from some text to call out the limitation.
Joe From: [email protected] <[email protected]> Date: Thursday, October 13, 2022 at 3:41 AM To: Ben Schwartz <[email protected]>, Alan DeKok <[email protected]> Cc: Joe Clarke (jclarke) <[email protected]>, [email protected] <[email protected]>, [email protected] <[email protected]>, [email protected] <[email protected]> Subject: RE: [Add] [OPSAWG] π WG LC: RADIUS Extensions for Encrypted DNS Hi Ben, all, This specification targets typical broadband services in which the use of ECH is not relevant. It does not make sense for ISPs to be hosting multiple domains on the same IP address as the encrypted DNS resolver. Cheers, Med De : Add <[email protected]> De la part de Ben Schwartz EnvoyΓ© : mercredi 12 octobre 2022 19:54 Γ : Alan DeKok <[email protected]> Cc : Joe Clarke (jclarke) <[email protected]>; [email protected]; [email protected]; [email protected] Objet : Re: [Add] [OPSAWG] π WG LC: RADIUS Extensions for Encrypted DNS A practical limit of around 4000 octets for SvcParams seems likely to be fine. A hard limit of 250 octets has a real chance of becoming a practical problem. I would encourage you to reconsider the format. As a concrete example, SvcParams are used to deliver public keys for ECH. Currently, only elliptic-curve keys are used, but if a future iteration relied on RSA public keys, they would not fit within this limit. On Wed, Oct 12, 2022 at 1:41 PM Alan DeKok <[email protected]<mailto:[email protected]>> wrote: On Oct 12, 2022, at 1:32 PM, Ben Schwartz <[email protected]<mailto:[email protected]>> wrote: > > The Encrypted-DNS-SvcParams TLV seems to be limited to 253 octets. This is a > problem, since it is meant to hold a SvcParams object that is allowed to be > much larger (up to ~65000 octets in principle). The length is less than 253 octets, as it is encapsulated inside of another attribute "wrapper". So the practical limit is probably 250 or less. RADIUS provides for encoding more than 253 octets in an attribute. See https://www.rfc-editor.org/rfc/rfc8044#section-3.16 However, this capability exists only for "top level" attributes, and cannot be used here. Further, RADIUS packets are generally limited to 4K octets total. So even if the limits on this attribute are removed, then there's still a practical limit of around 4000 octets. Alan DeKok. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
_______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
