Jasdip, My recommendation is to include them to identify all known forms of EPP extensibility that could be considered in RPP upfront. We can tag them as being RIR-based for clarity. The analysis does not include inspecting every element of the extensions, but the extensibility forms, features, and patterns.
-- JG [cid87442*[email protected]] 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/> From: Jasdip Singh <[email protected]> Date: Friday, December 13, 2024 at 2:07 PM To: Rubens Kuhl <[email protected]>, James Gould <[email protected]> Cc: "[email protected]" <[email protected]>, "[email protected]" <[email protected]> Subject: [EXTERNAL] Re: [rpp] Re: [regext] EPP Extensibility and Extensions Analysis 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. Hi Rubens, Since couple of these involve number resource provisioning, curious if it is desired from the NIC BR perspective that these use cases be considered upfront for RPP? Thanks, Jasdip From: Rubens Kuhl <[email protected]> Date: Friday, December 13, 2024 at 1:20 PM To: Gould, James <[email protected]> Cc: [email protected] <[email protected]>, [email protected] <[email protected]> Subject: [rpp] Re: [regext] EPP Extensibility and Extensions Analysis James, Follows links to extensions in active use although not in the IANA registry, from use cases in the RIR/NIR system and ccTLDs: https://ftp.registro.br/pub/libepp-nicbr/draft-neves-epp-asn-02.txt<https://secure-web.cisco.com/1PV4RY_ejPw-1VDVHyygD6STQ7FYfikx17K0yKdLS3wOINgodSUgsrnTCBXH2qEBvRs137WwAF69P51WKLERUq5SwsyFvekTihaWZ7N0XC4F1gLvgrlDtY7u-zQJgpLEBobveISxrXczje5Ty8Y-oWcZCn7hPGxYtTPqgSD9kzebFwxKZTi3xIjASX-lY6qj-mN1Fb9qiDixa1wId7-iWMYi0vENNwQeRK6fzpX8qTE_BXyGxNSB7sobWyvycSjyIgJJDuK-TwsnVJEPo8URIYnB5nSbI1J-dAc3bnmy_a9k/https%3A%2F%2Fftp.registro.br%2Fpub%2Flibepp-nicbr%2Fdraft-neves-epp-asn-02.txt> https://ftp.registro.br/pub/libepp-nicbr/draft-neves-epp-brdomain-05.txt<https://secure-web.cisco.com/1W_XGQfAkGpgBNvEWAaJkivbpohO-5Ylxj1DNwbKFqYrQXMd9wUn3H4E5KYVTiYTI6NBQb_yCORcDGOo_bbsCBRZ940UeMEVKy4K9ADFvEBSFFD1oPr-DiIWkG3lnJLZ1VLMqkotK79DHJES84j2aLwbfYbiyjUm2k5DtWuS7YxBFoD_Zj0MeYNzhmLOXGqKzc4nw2D0bkNDOlKd5Gi97cjXjF2DrkDO00sKDnxjvQFdLEOAPTXutuAe1ZfFObNiGjhQdcM6ALGHWo5u1gw1TLXo-e3umjbyPisgxo5n6uZA/https%3A%2F%2Fftp.registro.br%2Fpub%2Flibepp-nicbr%2Fdraft-neves-epp-brdomain-05.txt> https://ftp.registro.br/pub/libepp-nicbr/draft-neves-epp-brorg-06.txt<https://secure-web.cisco.com/1AogCs5nrcqP2h6wn6Fm0gsl1inleeXTf3mZeI2zJiXpBKErK2C9lCiLOCamEoA2h_xtF-zMkQVI2GsgoxGRbjDh4UDcGjhyVSZZi69B8KCJ5LumAdf2TJPhS8GnPN9j6YgDVhlHUNO83D556Ck60GHlA0V_G-BtLXjFDfg4UHaq34bOy1dh7OBUmVXD2rEoko0B5faIzoMRSzOB4ulguTNc4Y-6i8ziuIUsh7Yr5S_9i1SKlex-nja7CZQ0Nhdr83gVVPsPCVu2H3QKCgiimIpB_IL6SG4UnaF9W3cI9SMc/https%3A%2F%2Fftp.registro.br%2Fpub%2Flibepp-nicbr%2Fdraft-neves-epp-brorg-06.txt> https://ftp.registro.br/pub/libepp-nicbr/draft-neves-epp-ipnetwork-02.txt<https://secure-web.cisco.com/1RTGo39OCHfEIferT7bSM4DM0k_Avrql4wjQURYRgBmRKMe60q6d0FWojWHhlVa82xYLvKK-yUaRUKUpxSclU-heeg5O-fw6GuoYOhXT0TYQpEHFdvwJBW0udHVLn4gpIK9-0el000cpmDyis1ndgG-gSM3ODsM1evCRzdgTiVD3kSpT2sZOm2qrSd7pbPejlikD-Key2KYuZ45oZCUfBPEXntwWcAnF6xZqZEP273-GXoa9_UmfMXz0iDXg-h_yEzT-2_4Dq-bdQNXpqLULR4QG38lhUHlKme_OE7ZRqPsE/https%3A%2F%2Fftp.registro.br%2Fpub%2Flibepp-nicbr%2Fdraft-neves-epp-ipnetwork-02.txt> Rubens > Em 13 de dez. de 2024, à(s) 13:46, Gould, James > <[email protected]> escreveu: > > Hi, In support of the RESTful Provisioning Protocol (RPP), a Tiger Team has > been formed to analyze the EPP extensibility and extensions. The starting > source for the EPP extensions is the EPP extensions IANA registry > (https://www.iana.org/assignments/epp-extensions<https://secure-web.cisco.com/1XIAqVSu_S1mom2JbH4v6hObcf1_imQ4gJX8XgZjR6BQWYgvzF69JMvPK1FeP_YTR7U6pU0Ooih0q4E5Zt-rUPXd4oXfbAs5QA1M99YRAuVsyU8ndnuLuwq6vb3Lic6oyzjSezFwhv1int9TaVvMNEmXubxPW1bLvpp8XNbjkdV6xDBWU8NpRXbly1cEcvuSiz6Sf974B3dlC4jQnoVp2VQ0f7OhpHZbj_1nWZRTbQB9Ovmaam-4OrxxdFjy5t_96uo8HldNDj_6R-N53Dmz4tkYei-MaXB8QT-amBudGXx8/https%3A%2F%2Fwww.iana.org%2Fassignments%2Fepp-extensions>). > I encourage registering and/or updating the EPP extensions in the EPP > extensions IANA registry so that the extensions are included in the analysis. > Please let me know if there are additional EPP extensions that need to be > considered for the analysis. The Tiger Team includes: > > • Jim Gould from Verisign > • Jody Kolker from GoDaddy > • Pawel Kowalik from DENIC > • Eric Skoglund from Internet Infrastructure Foundation > • Maarten Wullink from SIDN > Thanks, > -- > JG > > <image001.png> > > James Gould > Fellow Engineer > [email protected] > > 703-948-3271 > 12061 Bluemont Way > Reston, VA 20190 > > Verisign.com > _______________________________________________ > regext mailing list -- [email protected] > To unsubscribe send an email to [email protected] _______________________________________________ rpp mailing list -- [email protected] To unsubscribe send an email to [email protected]
_______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
