<<< Chronological Index >>>    <<< Thread Index >>>

RE: Access to RIPE-TT data from third parties (fwd)


Customer feedback...

------------------------------------------------------------------------------
Henk Uijterwaal                    Email: henk.uijterwaal@ripe.net
RIPE Network Coordination Centre     WWW: http://www.ripe.net/home/henk
Singel 258                         Phone: +31.20.535-4414,  Fax -4445
1016 AB Amsterdam                   Home: +31.20.4195305
The Netherlands                   Mobile: +31.6.55861746  
------------------------------------------------------------------------------

A man can take a train and never reach his destination.
                                               (Kerouac, well before RFC2780).

---------- Forwarded message ----------
Date: Thu, 21 Dec 2000 14:00:09 -0000
From: mike.norris@heanet.ie
To: "'Henk Uijterwaal (RIPE-NCC)'" <henk@ripe.net>
Subject: RE: Access to RIPE-TT data from third parties (fwd)


Henk
    many thanks to you and your colleagues for a fine service.

Happy Christmas and best wishes for 2001.

Mike Norris

> -----Original Message-----
> From: owner-tt-wg@ripe.net [mailto:owner-tt-wg@ripe.net]On Behalf Of
> Henk Uijterwaal (RIPE-NCC)
> Sent: Thursday, December 21, 2000 9:36 AM
> To: tt-wg@ripe.net
> Subject: Re: Access to RIPE-TT data from third parties (fwd)
> 
> 
> 
> 
> On Wed, 15 Nov 2000, Henk Uijterwaal (RIPE-NCC) wrote:
> > 
> > > I suggest to do 2 things.  
> > > 
> > > The plots section of the TTM pages will be split into 3 
> sub-sections:
> > > 
> > > A) A general section, explaining what is show in the 
> plots and other
> > >    documentation, but no real data.  This section will 
> not be password
> > >    protected.
> > > 
> > > B) A test-box-host section, containing all data that is currently
> > >    available.  This section will be password protected 
> with a password
> > >    that is made available to the TB-hosts, but may not be 
> passed on.
> > > 
> > > C) N sections for the customers of a specific site, 
> containing only
> > >    plots from and to a certain test-box. This is a subset 
> of (B).  The
> > >    TB-hosts can ask for a reasonable number of password/username
> > >    combinations for their customers.
> > > 
> > > Before a customer gets the password for (C), he will be 
> asked to sign a
> > > data-disclosure agreement.  
>  
>   (D) In the meantime, another site asked for the opposite case: they
> >     don't mind people seeing plots from their site to the 
> rest of the
> >     world, but also like to install a few test boxes to 
> measure on their
> >     own networks only and NOT publish those results.
> > 
> > If we do (C) right, we can deal with all cases with 1 mechanism.  
> > However, before implementing it, I'd like to know if people 
> can imagine
> > more realistic cases that we'd should consider.  Please 
> mail your comments
> > to the list, I'll collect them and come up with a proposal for
> > implementation in a week or two.
> 
> It has been a month and there were no comments on the list, 
> so we'll won't
> add any cases other than (B), (C) or (D).
> 
> >From our side, there is one other requirement: the scheme 
> must still be
> maintainable, we do not want to spend our days adding and resetting
> passwords.  Ana, our new network engineer, is currently looking at the
> best way to implement this.
> 
> Season's greetings,
> 
> Henk
> 
> --------------------------------------------------------------
> ----------------
> Henk Uijterwaal                    Email: henk.uijterwaal@ripe.net
> RIPE Network Coordination Centre     WWW: 
> http://www.ripe.net/home/henk
> Singel 258                         Phone: +31.20.535-4414,  Fax -4445
> 1016 AB Amsterdam                   Home: +31.20.4195305
> The Netherlands                   Mobile: +31.6.55861746  
> --------------------------------------------------------------
> ----------------
> 
> A man can take a train and never reach his destination.
>                                                (Kerouac, well 
> before RFC2780).
> 
> 







<<< Chronological Index >>>    <<< Thread Index >>>