This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/db-wg@ripe.net/
[Fwd: [db-wg] RIPE51 DB-WG Draft Agenda V1]
- Previous message (by thread): [Fwd: [db-wg] RIPE51 DB-WG Draft Agenda V1]
- Next message (by thread): [Fwd: Re: [Fwd: [db-wg] RIPE51 DB-WG Draft Agenda V1]]
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Andre Koopal
andre.koopal at nld.mci.com
Tue Oct 11 15:28:57 CEST 2005
On Tue, Oct 11, 2005 at 01:54:27PM +0100, Wilfried Woeber, UniVie/ACOnet wrote: > > Dear DB-WG folks, Chairs, Meeting! > > Here is the 2nd draft of an agenda for the DB-WG next week at RIPE51 > in Amsterdam. > > For time slot allocation please refer to the most up-to-date meeting > plan at http://www.ripe.net/ripe/meetings/ripe-51/meeting-plan.html Hi Wilfried, A while ago I mailed the db working group to request a changed behavour when you lookup inetnum's. In principle what I would like to see is that when an inetnum is returned, that the IRT object that is relevant to this inetnum is returned as well. For example, if you lookup inetnum '193.78.240' you get that inetnum returned, and the irt-object 'IRT-MCI-NL', as that is specified in the inetnum above: '193.78/15'. Note that this is different then the current -c behavour as that would, in this example' return the inetnum for '193.78/15' instead. Can you add this discussion on the agenda as well? Unfortunately I won't be able to visit the WG session myself, I hope the proposal is clear this way. Regards, Andre Koopal > > Best regards, > Wilfried. > ________________________________________________________________________ > > A. Administrative Matters > - scribe > - list of participants > - agenda > - minutes > - "remote participation" coordination (if needed) > > B. DB Update (N.N., RIPE NCC) [~15 min] > > C. Review of security mechanisms in the DB (Peter K., denic.de) [~15 min] > . quality of CRYPT-PW, CRYPT-MD5, X.509 > . level of vulnerabilty in current dataset > > D. State of whois services, developments? (WW144, N.N., RIPE NCC) [~15 min] > > E. IRIS pilot frontend to whois (N.N., RIPE NCC) [~10 min] > > F. Fact finding: RoutingReg facilities at RIRs (Gert D, SpaceNet) [~15 min] > > X. Impact of "PDP" on how the DB-WG operates (WW144) [~15 min] > . ref: https://www.ripe.net/ripe/docs/ripe-350.html > > Y. Input from other WGs > . DNS: secureDNS requirements for the DB > > Z. AOB > > >
- Previous message (by thread): [Fwd: [db-wg] RIPE51 DB-WG Draft Agenda V1]
- Next message (by thread): [Fwd: Re: [Fwd: [db-wg] RIPE51 DB-WG Draft Agenda V1]]
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]