Thomas, There should be no issue registering "proprietary" extensions, if they follow the DE review guidelines in section 2.1.1 (e.g., architectural soundness and using the guidelines in RFC 3735). The issue comes into play for IETF draft categories (prior to RFC, active working group, and abandoned). There are implemented EPP extension drafts in all 3 categories. We don't want to encourage the implementation of proprietary extensions to get around a process issue with the implementation of IETF drafts.
Thanks, -- JG James Gould Fellow Engineer [email protected] <applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/[email protected]> 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign.com <http://verisigninc.com/> On 11/3/25, 7:12 AM, "Thomas Corte (TANGO support)" <[email protected] <mailto:[email protected]>> wrote: Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hello, quick question regarding this "IETF drafts in the EPP registry" discussion... should any of this have an impact on IANA registering *proprietary* extensions (i.e., those with registry-specific https:// namespace URIs, not IETF namespace URIs)? It seems that IANA started postponing such registrations until the issue is settled here, but as far as I can tell, this discussion shouldn't prevent proprietary extensions being registered, except maybe in cases where attempts are made of registering a copy of an IETF draft under a non-IETF namespace, correct? Best regards, Thomas -- TANGO REGISTRY SERVICES® is a product of: Knipp Medien und Kommunikation GmbH Technologiepark Phone: +49 231 9703-222 Martin-Schmeisser-Weg 9 Fax: +49 231 9703-200 D-44227 Dortmund E-Mail: [email protected] <mailto:[email protected]> Germany _______________________________________________ regext mailing list -- [email protected] <mailto:[email protected]> To unsubscribe send an email to [email protected] <mailto:[email protected]> _______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
