[address-policy-wg] Address/ASN certificates and RIPE NCC Transparency Report?, was Legal counsel on 2008-08 (Initial Certification Policy in the RIPE NCC Service Region)

At 10:32 11/05/2011 +0200, Shane Kerr wrote:
>Content-Transfer-Encoding: 7bit
>
>Martin,
>
>On Tue, 2011-05-10 at 08:37 -0400, Martin Millnert wrote:
> > Hi Alex,
> >
> > On Mon, May 9, 2011 at 5:57 PM, Alex Band <alexb at ripe.net> wrote:
> >
> > > Also, you have to realise that we've been working on this since
> > > 2006, by our Community's request. The system is based on open
> > > IETF standards in the SIDR working group which has been active even
> > > longer. All of this has been done in a completely open and
> > > transparent way.
> >
> > Purely out of curiosity here, does the complete openness and
> > transparency of the process so far include the code that the RIPE NCC
> > has developed together with external consultants? I've been looking
> > around at http://www.ripe.net/ but I couldn't find an URL to the
> > subversion repository mentioned in the CPS [1].
> >
> > I do remember hearing from the meeting that some code was planned to
> > be released. Are you going to be releasing all of the code, or will
> > some be kept for obscurity or other reasons?
>
>Speaking of openness... :)
>
>It would be nice if the RIPE NCC could commit to something like the
>Google Transparency Report, where all government requests for legal
>action are published openly:

+1.

-Hank


>http://www.google.com/transparencyreport/
>
>Looking at those numbers makes it pretty clear to me that governments
>will be mucking around with routing policy eventually, whether or not we
>have certificates.
>
>It might be nice to have something like this independent of any eventual
>certification policy.
>
>--
>Shane