Just to be clear, two of the extensions I mentioned are from the ccTLD side (brorg and brdomain) and two are for the RIR/NIR side (ipnetwork and asn).
Rubens > Em 13 de dez. de 2024, à(s) 16:49, Jasdip Singh <[email protected]> escreveu: > > Hi Rubens, > > The candidate RPP charter’s scope does include considering use cases for > number resource provisioning but AFAIK, the RIRs as a whole are not presently > thinking of doing so. > > To James’ point, perhaps ok to consider the NIC BR’s EPP use cases for the > EPP/RPP parity analysis but nothing more for now from the RIRs side. :) > > Thanks for pointing to the NIC BR’s EPP extensions. > > Jasdip > > From: Rubens Kuhl <[email protected]> > Date: Friday, December 13, 2024 at 2:29 PM > To: Jasdip Singh <[email protected]> > Cc: Rubens Kuhl <[email protected]>, Gould, James > <[email protected]>, [email protected] <[email protected]>, > [email protected] <[email protected]> > Subject: [regext] Re: [rpp] Re: EPP Extensibility and Extensions Analysis > > > Jasdip, > > I believe that’s more of a overarching question of whether to address number > resource provisioning in RPP. > If RPP indeed encompasses number resources, than the -asn and -ipnetwork > extensions should probably be included. > > > Rubens > > > > > Em 13 de dez. de 2024, à(s) 16:06, Jasdip Singh <[email protected]> escreveu: > > 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://ftp.registro.br/pub/libepp-nicbr/draft-neves-epp-brdomain-05.txt > https://ftp.registro.br/pub/libepp-nicbr/draft-neves-epp-brorg-06.txt > https://ftp.registro.br/pub/libepp-nicbr/draft-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). 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] <mailto:[email protected]> > To unsubscribe send an email to [email protected] > <mailto:[email protected]>
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
