speaking as a regular ol’ member: > On Sep 8, 2016, at 11:57 AM, Carlos M. Martinez <[email protected]> wrote: > > Hi Rob, > > I’ll let each RIR answer for themselves. In our case (LACNIC), we don’t > support up/down. We’ve had a very rough implementation of a ‘parent’ CA for a > while, but since there is essentially no demand for it from our members, the > project always gets down-prioritized. > > If the GTA was to gain any traction, we’d commit resources accordingly in > order to support it from the ‘child’ side. > > In short: it’s not the availability of up-down what has stalled the GTA.
If you had a client side implementation, then if a GTA did get established, you would be able to interact with the GTA for certification of your resources -- immediately. That may also be why Rob asked his question, I dunno. It’s why I was interested in the answers. I think you have said “not yet, but we would 'commit resources accordingly’ ", which is reassuring. It could mean “make this our highest priority, bar none”. Good to know. Of course, it might mean something quite different. —Sandy, speaking as regular ol’ member > > tks! > > Carlos > > On 8 Sep 2016, at 12:37, Rob Austein wrote: > >> Hi, Carlos. Technical question: >> >> Do the current RIR CA implementations support the client role of the >> "up-down" provisioning protocol, and, if so, has there been any recent >> interop testing of this, either against other RIR CA implementations >> or against mine? >> >> APNIC's original implementation did support it. I think RIPE's >> implementation sort of supported it at one point but they did not >> consider it production-ready. Dunno about the others, and all of this >> was a while ago, haven't heard much about it recently. >> >> _______________________________________________ >> sidr mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/sidr > > _______________________________________________ > sidr mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/sidr
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
