- db-wg - mailman.ripe.net

Announcement Routing Registry Training Courses
by RIPE NCC Training 04 Oct '04

04 Oct '04

Dear Colleagues, [apologies for duplicate postings] As a service to its members the RIPE NCC offers the "Routing Registry Training Course". The main objective of the "Routing Registry Training Course" is to familiarise the LIRs with the features of the Routing Registry, while introducing the relevant tools and services of the RIPE NCC. The course also offers practical exercises. OVERVIEW OF TOPICS COVERED IN THE COURSE: - Routing Registry as a part of the RIPE Whois Database and the Internet Routing Registry (IRR) - Specifying routing policies using (RPSL) Routing Policy Specification Language and the RtConfig tool - IRRToolSet - Routing Information Service (RIS) - Routing Registry Consistency Check Project Please note that this is an advanced course. It will: - NOT teach the basics of routing - NOT teach the basics of RIPE Database operations, - NOT describe how to receive Internet resources from the RIPE NCC - NOT describe how to operate a Local Internet Registry (LIR) The target audience of the course are technical staff of LIRs: e.g. network operators, engineers etc. This course is not intended for administrative or management staff (e.g. Hostmasters) . It is assumed that all attendees will be familiar with Border Gateway Protocol routing and with the RIPE Database (i.e. creating/modifying objects). This course is based on interactive exercises in a local network set-up. Please bring your laptops equipped with the following: - A working Ethernet card, - Three meters of Ethernet cable, - A secure connection client, - A web browser. Please be prepared to share your laptop (or at least allow another attendee to "look over your shoulder") if necessary. The Routing Registry Training Course is conducted in the English language and is free of charge, since it is covered by the membership fee. More information about the Routing Registry Training Course can be found at: http://www.ripe.net/training/rr/ REGISTRATION: You can register for a Routing Registry Training Course at the following URL: http://www.ripe.net/cgi-bin/trainingform.pl.cgi Or by completing the registration form at the end of this e-mail and replying to <training(a)ripe.net> . In order to register for a Routing Registry Training Course you must be an employee of an LIR and either: - be an LIR contact - be confirmed by an LIR contact LIR contacts are those employees of an LIR who are registered with RIPE NCC as authoritative contact persons. It is expected that most of those interested in the Routing Registry Training Course will not be an authoritative contact person for their LIR, and therefore will be, refused by the course registration "robot". In order to be admitted to the course, a confirmation e-mail must be sent to <training(a)ripe.net>. Please approach the LIR contacts from your organisation personally, since the identity of LIR contacts is confidential, and the RIPE NCC is unable to divulge contact persons for any given LIR. Kind Regards, Rumy Kanis Training Services Manager RIPE NCC **************************************************************************** COURSE DATES AND VENUES ======================== Date: Tuesday 23 November 2004 Time: 0900 - 1700 Location: Damascus,Syria AND: Date: Friday 14 January 2005 Time: 0900 - 1700 Location: Berlin, Germany AND: Date: Friday 18 March 2005 Time: 0900 - 1700 Location: Barcelona, Spain AND: Date: Friday 15 April 2005 Time: 0900 - 1700 Location: Amsterdam, The Netherlands AND: Date: Friday 22 April 2005 Time: 0900 - 1700 Location: St. Petersburg, Russian Federation ***************************************************************************** REGISTRATION FORM ================= %START PART 1 - Registration 1) Your name Enter First name, Last name in full e.g. John Doe Mary-Beth Walton # NAME [ ] 2) Your Registry ID (format: country-code.<name of registry>) # REG [ ] 3) Your e-mail address # EMAIL [ ] 4) Your NIC handle (optional) # NICHANDLE [ ] 5) The course you plan to attend (date and location) # COURSE [ ] %END

1 0

Fwd: [Apnic-announce] Privacy of customer assignment records - implementation update
by leo vegoda 23 Sep '04

23 Sep '04

Hi, APNIC have announced a change in the default behaviour of their Whois server. The change will be made on 30 September. People using their Whois service from this region may be interested in the announcement. Kind regards, -- leo vegoda Registration Services Manager RIPE NCC Begin forwarded message: > From: APNIC Secretariat <secretariat(a)apnic.net> > Date: September 23, 2004 2:02:27 am BST > To: apnic-announce(a)apnic.net > Cc: Subject: [Apnic-announce] Privacy of customer assignment records - > implementation update > Reply-To: apnic-talk(a)apnic.net, secretariat(a)apnic.net > > Dear colleagues, > > This is an important announcement on the implementation of APNIC > approved proposal prop-007-v001 regarding privacy of customer > assignment records. The proposal document, presentation, minutes, and > discussion are available at: > > http://www.apnic.net/docs/policy/proposals/prop-007-v001.html > > The APNIC Secretariat will be implementing this proposal on 30 > September 2004. > > Please note that after this date, customer assignment objects will no > longer be visible in the APNIC Whois Database, unless the APNIC > account holder chooses to make public the customer records for their > allocated address range. > > A set of Frequently Asked Questions about this project is now > available at: > > http://www.apnic.net/info/faq/privacy-faq.html > > If you have any concerns or questions regarding this policy, please > contact the APNIC helpdesk at: > > E-mail: helpdesk(a)apnic.net > Phone: +617 3858 3188 > Fax: +617 3858 3199 > > Regards > > ______________________________________________________________________ > APNIC Secretariat <secretariat(a)apnic.net> > Asia Pacific Network Information Centre (APNIC) Tel: +61-7-3858-3100 > PO Box 2131 Milton, QLD 4064 Australia Fax: +61-7-3858-3199 > ______________________________________________________________________ > _______________________________________________ > Apnic-announce mailing list > Apnic-announce(a)lists.apnic.net > http://mailman.apnic.net/mailman/listinfo/apnic-announce >

2 1

Abuse contacts in RIPE database and whois
by Rodney Tillotson 23 Sep '04

23 Sep '04

In this afternoon's session of the Anti-spam WG we discussed the issue of publishing abuse contacts and I agreed to present this consensus view and request. As time is short this is not yet published in the minutes of the meeting, but it will be! Rodney Tillotson Chair, RIPE anti-spam WG =========================================================== The Anti-spam WG asks the Database WG to take some timely action to improve the availability of abuse contacts for IP addresses allocated through RIPE: 1. to publish an explicit abuse contact address where possible for every address; 2. to lower the profile of other addresses currently in the database and published through whois, which were never intended for the abuse function. While it is for the Database WG to decide the best way to implement such improvements, the Anti-spam WG noted that of the various technical changes which have been proposed or partly implemented, one combination which we would find acceptable is: A. modify the IRT object to include an explicit 'abuse-mail' attribute and to remove the mandatory requirement for PGP or similar authentication (or introduce a similar new object with those properties); and B. modify the default behaviour of the whois interfaces to find and present an abuse address if there is one and to suppress other e-mail addresses. 22nd September 2004. ===========================================================

1 0

Agenda V3
by Titley, Nigel 16 Sep '04

16 Sep '04

Gentlefolk, Following a kind offer by Shane Kerr to give a run down on CRISP please find version 3 of the DB WG agenda. Nigel -- Nigel Titley Peering Coordinator, FLAG Telecom +44 20 7478 9579 ********************************************************************** This e-mail message is confidential and is intended only for the use of the individual or entity named above and contains information which is or may be confidential, non-public or legally privileged. Any dissemination or distribution of this message other than to its intended recipient is strictly prohibited. You should not copy it or use it for any purpose nor disclose the contents to any other person. If you have received this message in error, please notify us by email to postmaster(a)flagtelecom.com immediately and delete the original message and all copies from all locations in your computer systems. This e-mail has been swept by Mailsweeper TM for viruses. However, FLAG Telecom cannot accept liability for any damage which you may sustain as a result of software viruses. ********************************************************************** This message has been scanned for viruses by MailControl - www.mailcontrol.com

1 0

RE: [db-wg] draft agenda (V1) for DB-WG meeting, RIPE 49, Manches ter, UK
by Titley, Nigel 16 Sep '04

16 Sep '04

MarcoH wrote: > Hate to come up with it again, but there are various actions points > open > on the abuse-c stuff. One of them lists the 'implement whatever > concensus there is on the mailinglist'. > > These should already be on the agenda as open action points, but it > might > be worth planning some time for discussion or at least an overview of > what > the outcome of the mail discussion was. Sounds like a good idea. Do we have any volunteers to do a short presentation on where we got to? > It's hard to say there is consensus on this subject, although in they > end there weren't much comments posted and everybody seems to be > happy (or > tired of it). I think it just fizzled out. I'm not sure that we got to any consensus. Nigel -- Nigel Titley Peering Coordinator, FLAG Telecom +44 20 7478 9579 ********************************************************************** This e-mail message is confidential and is intended only for the use of the individual or entity named above and contains information which is or may be confidential, non-public or legally privileged. Any dissemination or distribution of this message other than to its intended recipient is strictly prohibited. You should not copy it or use it for any purpose nor disclose the contents to any other person. If you have received this message in error, please notify us by email to postmaster(a)flagtelecom.com immediately and delete the original message and all copies from all locations in your computer systems. This e-mail has been swept by Mailsweeper TM for viruses. However, FLAG Telecom cannot accept liability for any damage which you may sustain as a result of software viruses. ********************************************************************** This message has been scanned for viruses by MailControl - www.mailcontrol.com

1 0

draft agenda (V1) for DB-WG meeting, RIPE 49, Manchester, UK
by Wilfried Woeber, UniVie/ACOnet 13 Sep '04

13 Sep '04

Dear DB-WG community, attached please find the draft agenda V1 for the DB-WG meeting during RIPE49 in Manchester, UK. As some of us have still been on vacation recently, we may have to update the draft agenda as we get closer to the meeting date. Please feel free to propose additional topics by either replying to the WG mailing list or in private mail to Nigel (who has volunteered to manage the meeting in Manchester - thank you very much!) and myself. Have a nice and successful meeting in Manchester! Wilfried. ++++++++ A. Administrative Matters - scribe - list of participants - agenda - minutes - "remote participation" coordination (if needed) - meeting schedule for 2005 B. DB Operational Update (N.N., RIPE NCC) tbc [~20 min] C. ERX Report [196/8, 198/8] (Leo V., RIPE NCC) [~15 min] D. RAToolSet software maintenance (N.N., RIPE NCC) tbc [~10 min] E. Routing Registry Courses (Vesna M., RIPE NCC) [~05 min] Y. Input from other WGs Z. AOB -------------------------------------------------------------------------------- 7-SEP-2004 12:55:00 UTC

7 12

Re: [db-wg] domain: object normalization
by Wilfried Woeber, UniVie/ACOnet 13 Sep '04

13 Sep '04

I'd like to come back to the *original* question or suggestion: to teach the DB software to accept FQDN notation (trailing ".") for lookup keys that denote domain names. Pro / Con? As a dumb user of the DB I definitely stumble into that one myself, sometimes, so I am in favour of this (hopefully simple?) change. Btw, if this gets implemented, it should also work for the referral domain objects! Wilfried.

2 1

Draft Agenda V2
by Titley, Nigel 13 Sep '04

13 Sep '04

Folks, Following the discussion about abuse, Marco has agreed to give a short round up. This gives us version 2 of the Agenda Nigel +++++++ A. Administrative Matters - scribe - list of participants - agenda - minutes - "remote participation" coordination (if needed) - meeting schedule for 2005 B. DB Operational Update (N.N., RIPE NCC) tbc [~20 min] C. ERX Report [196/8, 198/8] (Leo V., RIPE NCC) [~15 min] D. RAToolSet software maintenance (N.N., RIPE NCC) tbc [~10 min] E. Routing Registry Courses (Vesna M., RIPE NCC) [~05 min] F. IRT/Abuse roundup (MarcoH) [~15 min] Y. Input from other WGs Z. AOB -- Nigel Titley Peering Coordinator, FLAG Telecom +44 20 7478 9579 ********************************************************************** This e-mail message is confidential and is intended only for the use of the individual or entity named above and contains information which is or may be confidential, non-public or legally privileged. Any dissemination or distribution of this message other than to its intended recipient is strictly prohibited. You should not copy it or use it for any purpose nor disclose the contents to any other person. If you have received this message in error, please notify us by email to postmaster(a)flagtelecom.com immediately and delete the original message and all copies from all locations in your computer systems. This e-mail has been swept by Mailsweeper TM for viruses. However, FLAG Telecom cannot accept liability for any damage which you may sustain as a result of software viruses. ********************************************************************** This message has been scanned for viruses by MailControl - www.mailcontrol.com

1 0

Draft Minutes of the DB WG, version 2
by Titley, Nigel 13 Sep '04

13 Sep '04

Folks, This is the second draft of the minutes from the DB-WG RIPE 48. A very minor change has been made to item C. All actions are unchanged. Please check for your actions and try and report back. For reference I have open actions against RIPE NCC Wilfried Woeber Randy Bush + Niall O'Reilly Shane Kerr Nigel Titley Best regards Nigel -- Nigel Titley Peering Coordinator, FLAG Telecom +44 20 7478 9579 ********************************************************************** This e-mail message is confidential and is intended only for the use of the individual or entity named above and contains information which is or may be confidential, non-public or legally privileged. Any dissemination or distribution of this message other than to its intended recipient is strictly prohibited. You should not copy it or use it for any purpose nor disclose the contents to any other person. If you have received this message in error, please notify us by email to postmaster(a)flagtelecom.com immediately and delete the original message and all copies from all locations in your computer systems. This e-mail has been swept by Mailsweeper TM for viruses. However, FLAG Telecom cannot accept liability for any damage which you may sustain as a result of software viruses. ********************************************************************** This message has been scanned for viruses by MailControl - www.mailcontrol.com

1 0

Poetry object
by Titley, Nigel 13 Sep '04

13 Sep '04

In checking through the minutes and actions I note an action [AP48.3] on myself to clarify the issue of tech-c on the proposed poem: object. My proposal is that to be consistent we should have the tech-c attribute on both the Poem: and the Poetic-form: object. I also note Ulrich's suggestion that we should add the mnt-irt attribute to the Poem: object in order to provide a means of reporting abuse of (or by) the poem, and agree that this could be useful. Hopefully its inclusion at this early stage of the proceedings will allow tool-writers to make use of it rather than parsing lists of changed: attributes. I don't think we need the irt-mnt attribute on the Poetic-form object, but I'm willing to be persuaded. Please could I have comments on this, with the hope that we can tie off this action in Manchester, and get the new objects into the database. Best regards Nigel -- Nigel Titley Peering Coordinator, FLAG Telecom +44 20 7478 9579 ********************************************************************** This e-mail message is confidential and is intended only for the use of the individual or entity named above and contains information which is or may be confidential, non-public or legally privileged. Any dissemination or distribution of this message other than to its intended recipient is strictly prohibited. You should not copy it or use it for any purpose nor disclose the contents to any other person. If you have received this message in error, please notify us by email to postmaster(a)flagtelecom.com immediately and delete the original message and all copies from all locations in your computer systems. This e-mail has been swept by Mailsweeper TM for viruses. However, FLAG Telecom cannot accept liability for any damage which you may sustain as a result of software viruses. ********************************************************************** This message has been scanned for viruses by MailControl - www.mailcontrol.com

1 0