From ingrid at ripe.net Tue Mar 3 18:03:23 2009 From: ingrid at ripe.net (Ingrid Wijte) Date: Tue, 03 Mar 2009 18:03:23 +0100 Subject: [ncc-services-wg] New Documents available In-Reply-To: <49AD2C32.7060901@ripe.net> References: <49AD2C32.7060901@ripe.net> Message-ID: <49AD62DB.5000101@ripe.net> Dear Colleagues We have published several new RIPE Documents. The publication of these documents follows the implementation by the RIPE NCC of phase one of the previously accepted policy proposal 2007-01: "Direct Internet Resource Assignments to End Users from the RIPE NCC". Policy Documents: - ripe-449, "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region". It replaces ripe-441, "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region". - ripe-448, "Autonomous System (AS) Number Assignment Policies and Procedures". It replaces ripe-389, "Autonomous System (AS) Number Assignment Policies and Procedures". - ripe-450, "IPv6 Address Allocation and Assignment Policy". It replaces ripe-421, "IPv6 Address Allocation and Assignment Policy". - ripe-451, "IPv6 Address Space Policy for Internet Exchange Points". It replaces ripe-256, "IPv6 Address Space Policy for Internet Exchange Points". - ripe-452, "Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region". This is a new RIPE Document. RIPE NCC Organisational Document: - ripe-462, "RIPE NCC End User Assignment Agreement". This is a new RIPE Document. Request Forms and Supporting Notes: - ripe-453, "Provider Independent (PI) Assignment Request Form". It replaces ripe-356, "Provider Independent (PI) Assignment Request Form". - ripe-454, "Supporting Notes for the Provider Independent (PI) Assignment Request Form". It replaces ripe-357, "Supporting Notes for the Provider Independent (PI)Assignment Request Form". - ripe-456, "AS Number Request Form". It replaces ripe-444, "AS Number Request Form". - ripe-457, "Supporting Notes for the Autonomous System Number Request Form". It replaces ripe-445, "Supporting Notes for the Autonomous System Number Request Form". - ripe-458, "Anycast Assignment Request Form". It replaces ripe-390, "Anycast Assignment Request Form". - ripe-459, "Supporting Notes for the Anycast Assignment Request Form". It replaces ripe-391, "Supporting Notes for the Anycast Assignment Request Form". - ripe-460, "IPv6 Internet Exchange Points Assignment Request Form". It replaces ripe-371, "IPv6 Internet Exchange Points Assignment Request Form" - ripe-461, "Supporting Notes for the IPv6 Internet Exchange Points Assignment Request Form". It replaces ripe-372, "Supporting Notes for the IPv6 Internet Exchange Points Assignment Request Form". The new documents are available at: http://www.ripe.net/ripe/docs/titletoc.html Recently Published section available at: http://www.ripe.net/ripe/docs/recent.html Best regards Ingrid Wijte IP Resource Analyst RIPE NCC From Woeber at CC.UniVie.ac.at Wed Mar 4 00:21:08 2009 From: Woeber at CC.UniVie.ac.at (Wilfried Woeber, UniVie/ACOnet) Date: Tue, 03 Mar 2009 23:21:08 +0000 Subject: [ncc-services-wg] 2007-01 Implementation: Model agreement and charging requirements? In-Reply-To: <49A3DC83.7050201@ripe.net> References: <49A30C9A.5000708@CC.UniVie.ac.at> <49A3DC83.7050201@ripe.net> Message-ID: <49ADBB64.60201@CC.UniVie.ac.at> Dear Andrea, NCC Team, thanks for the calrifications! Everything appears to be reasonably under control by now :-) Best regards, Wilfried. _____________________________________________________________________________ Andrea Cima wrote: > Dear Wilfried, > > Wilfried Woeber, UniVie/ACOnet wrote: > >> The announcement about implemntation of 2007-01 was distributed on >> Feb, 12, 2009, pointing to: >> >> http://www.ripe.net/membership/lir-end-user-requirements.html >> >> At the bottom of this page there is the phrase: >> >> "A model agreement and its terms will be provided here shortly." >> >> Can we still expect to see such a model text before March 3, 2009, the >> "effective date" of implementation? >> >> > > > The model agreement will be published before March 3. > This model will be based on the "Contractual Requirements for Provider > Independent Resource Holders in the RIPE NCC Service Region", document > which was created in conjunction with policy proposal 2007-01: > http://www.ripe.net/ripe/draft-documents/ripe-new-draft2007-01-v4.html > >> In particular, I am interested in guidance on: >> >> "End User must pay an annual maintenance fee to the LIR for the >> resources." >> >> > > > The "Contractual Requirements for Provider Independent Resource Holders > in the RIPE NCC Service Region" document, states that all contracts > should include: "Notice that the resource holder is obliged to pay an > annual fee to the LIR for the resources". > http://www.ripe.net/ripe/draft-documents/ripe-new-draft2007-01-v4.html > >> because I wouldn't want to implement a separate charging scheme for our >> customers holding PI resources, and which already do have a contract and >> are charged for our connectivity services on a less granular basis. >> >> Of course, a surcharge of 0,-- would be fine :-) >> >> > > > This is fine, as long as you have specified it in the contract. > > I hope this clarifies the matter for you. If you have any further > questions don't hesitate to let me know. > > Best regards, > > Andrea Cima > RIPE NCC > >> Regards, >> Wilfried. >> >> > > > From denis at ripe.net Tue Mar 10 19:21:38 2009 From: denis at ripe.net (Denis Walker) Date: Tue, 10 Mar 2009 19:21:38 +0100 Subject: [ncc-services-wg] Outage report for the RIPE Database services Message-ID: <49B6AFB2.4000005@ripe.net> [ Apologies for duplicate mails ] Dear colleagues, >From approximately 10:00 (UTC) to 11:30 (UTC) on Tuesday, 10 March 2009, the RIPE Database update services were not available. This was due to a problem with the update servers. During this period it was not possible to connect to the syncupdates or webupdates services. Email updates were also delayed. All the messages received by auto-dbm at ripe.net were stored on our mail server. All the saved update messages have been processed. If you sent an email update to the RIPE Database service during this period, you will have already received an acknowledgment message. There is no need to re-send any update messages. We apologise for any inconvenience that this may have caused. Regards, Denis Walker Business Analyst RIPE NCC Database Group From webmaster at hallmark.org Sat Mar 14 10:17:36 2009 From: webmaster at hallmark.org (webmaster at hallmark.org) Date: Sat, 14 Mar 2009 10:17:36 +0100 (CET) Subject: [ncc-services-wg] You have received a card from a family member! Message-ID: <20090314091736.C5F1317E701F@medoc-server.de> An HTML attachment was scrubbed... URL: From byte_k at romb.net Wed Mar 11 15:07:38 2009 From: byte_k at romb.net (byte_k) Date: Wed, 11 Mar 2009 14:07:38 +0000 Subject: [ncc-services-wg] Reference Number: BMW:2551256003/23 Message-ID: <20090311140618.M58924@romb.net> -- Reference Number: BMW:2551256003/23 This is to notify you in the BMW email lottery which your email won you a BMW 7 Series Sport saloon car and a Lumb Sum of GBP250.000.00. To facilitate your claims, please contact the fiduciary manager. Mr Philips Harper. E- mail; bmwfundclaims at live.co.uk From henk at ripe.net Thu Mar 19 11:59:04 2009 From: henk at ripe.net (Henk Uijterwaal) Date: Thu, 19 Mar 2009 11:59:04 +0100 Subject: [ncc-services-wg] Re: [db-wg] Implementation of ASPLAIN Format In-Reply-To: References: <35FF7202-B217-4BE4-8709-CFC40A6FC14E@ripe.net> Message-ID: <49C22578.7070904@ripe.net> [Apologies for duplicates] Dear Colleagues, With the publication of RFC 5396, the IETF has standardised the representation of all Autonomous System (AS) Numbers in the ASPLAIN format. This covers both 16-bit and 32-bit AS Numbers. The previous ASDOT format is now obsolete. The RIPE NCC plans to start using the ASPLAIN format on March 25, 2009. From that time, any AS Numbers or references must be in the ASPLAIN format. The ASDOT format will no longer be accepted in RIPE NCC services such as the LIR Portal and the RIPE Database. The update of RIPE NCC systems to ASPLAIN will take place on Wednesday, March 25, according to the following schedule (all times are in UTC and are approximations): 7:00 1. Updates to the RIPE Database via webupdates and syncupdates will be disabled. Mail updates will be queued. After the update mechanism has been stopped, all objects containing an AS Number in ASDOT format will be automatically converted to identical objects with the AS Number in ASPLAIN format. Technical details of the conversion process will be published shortly. 2. The LIR Portal will be stopped. 10:00 The RIPE Database will now accept queries in ASPLAIN format; it will no longer accept queries in ASDOT format. 12:00 1. The LIR portal will be restarted. Any reference to an AS Number should be made in ASPLAIN format. 2. Any mail updates to the RIPE Database submitted after 7:00 will be processed. Webupdates and syncupdates will be enabled again. The Routing Information Service (RIS) will not be updated on March 25. If you use AS Numbers internally, or with other tools that have not yet been updated, you may be interested in a conversion tool that has been provided by APNIC. This tool converts ASDOT format AS Numbers to ASPLAIN and back. It can be downloaded from: http://www.apnic.net/cgi-bin/convert-asn.pl If you have any concerns about this matter, please send an email to Kind regards, Henk Uijterwaal Senior Project Manager, RIPE NCC -- ------------------------------------------------------------------------------ Henk Uijterwaal Email: henk.uijterwaal(at)ripe.net RIPE Network Coordination Centre http://www.amsterdamned.org/~henk P.O.Box 10096 Singel 258 Phone: +31.20.5354414 1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445 The Netherlands The Netherlands Mobile: +31.6.55861746 ------------------------------------------------------------------------------ From denis at ripe.net Thu Mar 19 16:58:23 2009 From: denis at ripe.net (Denis Walker) Date: Thu, 19 Mar 2009 16:58:23 +0100 Subject: [ncc-services-wg] ASDOT data conversion in the RIPE Database Message-ID: <49C26B9F.5050009@ripe.net> Dear Colleagues, The RIPE NCC is preparing for the implementation of RFC5396, which defines the representation of all AS Numbers in the ASPLAIN format. The RIPE NCC will start using the ASPLAIN format on 25 March 25 2009. On this day the RIPE NCC will convert any existing ASDOT data in the RIPE Database into ASPLAIN equivalent data. There are two ways we will do this: - If the primary key of the object contains an ASDOT, for example "aut-num: AS8.0", then the object will be deleted and re-created. - If the object contains a reference to an ASDOT, for example "import: from AS8.0", then the object will be modified. All objects altered in any way will have a "remarks:" attribute and an extra "changed:" attribute added. Notifications will be sent to the maintainers of the data for each update. The maintainers of the data do not need to do anything regarding this change. The conversion can only be done as part of the software upgrade. But if you are responsible for any ASDOT data we would ask that you check the data after the conversion is complete. Regards, Denis Walker Business Analyst RIPE NCC From gert at space.net Mon Mar 23 17:28:14 2009 From: gert at space.net (Gert Doering) Date: Mon, 23 Mar 2009 17:28:14 +0100 Subject: [ncc-services-wg] Re: [db-wg] Update to RIPE Database software In-Reply-To: <49C7B55F.5000708@ripe.net> References: <49C7B55F.5000708@ripe.net> Message-ID: <20090323162814.GF61514@Space.Net> Hi, On Mon, Mar 23, 2009 at 05:14:23PM +0100, Agoston Horvath wrote: > The RIPE Database software has been updated. > > The update included the following changes to update notification emails: > - The From: field has changed to unread at ripe.net > - The Reply-to: field has been removed from all notification messages > - The email envelope has been set to 'unread at ripe.net' instead of '<>'. > > The update also improved error reporting. For 'unreferenced object' and > some other errors, the object's primary key is now included. This will > make trouble-shooting easier. I'm not sure if I'm all that happy with this change. If I happen to be the target of such an e-mail: is there anything in there that will enable me to contact someone responsible to explain to me why I am receiving these e-mails and how to stop them? We shouldn't be sending e-mails from purposely-unread sender addresses. Gert Doering -- NetMaster -- Total number of prefixes smaller than registry allocations: 128645 SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (89) 32356-444 USt-IdNr.: DE813185279 From denis at ripe.net Mon Mar 23 18:18:16 2009 From: denis at ripe.net (Denis Walker) Date: Mon, 23 Mar 2009 18:18:16 +0100 Subject: [ncc-services-wg] Re: [db-wg] Update to RIPE Database software In-Reply-To: <20090323162814.GF61514@Space.Net> References: <49C7B55F.5000708@ripe.net> <20090323162814.GF61514@Space.Net> Message-ID: <49C7C458.30407@ripe.net> Hi Gert The reason we did this is to prevent the ticketing mail loop. Previously the From: was set to 'bitbucket at ripe.net' and Reply-To: set to ripe-dbm at ripe.net. These emails are auto-generated by the update software. There are header fields that show it is auto-generated. But many of the notifications are sent to ticketing systems. These don't all recognise the auto-generated headers. So they frequently send an ack message to ripe-dbm. We then create a ticket to say the user has created a ticket. Our Customer Services had to spend time closing hundreds of tickets that were redundant. We have now set the From: to unread that we think is more obvious to users than bitbuket. The message always includes these lines at the end: For assistance or clarification please contact: RIPE Database Administration We have two different types of notification messages generated by our update software. We already made this change on one of them and announced it some time ago. But we then set the Reply-To: to unread. It was pointed out to us at the time that this was not the correct way to compose emails. So that has been corrected with this release. I hope this explains our reasoning behind this change. Regards Denis Walker Business Analyst Database Group RIPE NCC Gert Doering wrote: > Hi, > > On Mon, Mar 23, 2009 at 05:14:23PM +0100, Agoston Horvath wrote: > >> The RIPE Database software has been updated. >> >> The update included the following changes to update notification emails: >> - The From: field has changed to unread at ripe.net >> - The Reply-to: field has been removed from all notification messages >> - The email envelope has been set to 'unread at ripe.net' instead of '<>'. >> >> The update also improved error reporting. For 'unreferenced object' and >> some other errors, the object's primary key is now included. This will >> make trouble-shooting easier. >> > > I'm not sure if I'm all that happy with this change. > > If I happen to be the target of such an e-mail: is there anything in > there that will enable me to contact someone responsible to explain to > me why I am receiving these e-mails and how to stop them? > > We shouldn't be sending e-mails from purposely-unread sender addresses. > > Gert Doering > -- NetMaster > From gert at space.net Mon Mar 23 18:23:56 2009 From: gert at space.net (Gert Doering) Date: Mon, 23 Mar 2009 18:23:56 +0100 Subject: [ncc-services-wg] Re: [db-wg] Update to RIPE Database software In-Reply-To: <49C7C458.30407@ripe.net> References: <49C7B55F.5000708@ripe.net> <20090323162814.GF61514@Space.Net> <49C7C458.30407@ripe.net> Message-ID: <20090323172356.GG61514@Space.Net> Hi, On Mon, Mar 23, 2009 at 06:18:16PM +0100, Denis Walker wrote: > We have now set the From: to unread that we think is more obvious to > users than bitbuket. The message always includes these lines at the end: > > For assistance or clarification please contact: > RIPE Database Administration OK - in that case, I'm fine. I have recently received a mail from your "lame DNS" checking service, which had *NO* indication whom to contact if one had questions about the problems reported - and that one also came from "unread at ripe.net". Which made me quite unhappy, and a bit wary about reading "unread" in a new thread... Thanks for your explanation! Gert Doering -- NetMaster -- Total number of prefixes smaller than registry allocations: 128645 SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (89) 32356-444 USt-IdNr.: DE813185279 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 305 bytes Desc: not available URL: From agoston at ripe.net Mon Mar 23 17:14:23 2009 From: agoston at ripe.net (Agoston Horvath) Date: Mon, 23 Mar 2009 17:14:23 +0100 Subject: [ncc-services-wg] Update to RIPE Database software Message-ID: <49C7B55F.5000708@ripe.net> Dear Colleagues, The RIPE Database software has been updated. The update included the following changes to update notification emails: - The From: field has changed to unread at ripe.net - The Reply-to: field has been removed from all notification messages - The email envelope has been set to 'unread at ripe.net' instead of '<>'. The update also improved error reporting. For 'unreferenced object' and some other errors, the object's primary key is now included. This will make trouble-shooting easier. Kind regards, Agoston Horvath Database Group RIPE NCC From denis at ripe.net Wed Mar 25 13:41:07 2009 From: denis at ripe.net (Denis Walker) Date: Wed, 25 Mar 2009 13:41:07 +0100 Subject: [ncc-services-wg] ASplain deployment Message-ID: <49CA2663.6020300@ripe.net> [Apologies for duplicates] Dear Colleagues, The RIPE NCC has now successfully completed the implementation of ASPLAIN format in the RIPE Database. If you are the maintainer of any routing data in the RIPE Database that is associated with 32-bit Autonomous System (AS) Numbers, please check your data to be sure that it was correctly converted. >From this point, any AS Numbers or references must be in the ASPLAIN format. The ASDOT format will no longer be accepted in RIPE NCC services such as the LIR Portal and the RIPE Database. Please note that the Routing Information Service (RIS) RIS has not been converted to ASPLAIN at this point. Some RIS tools may accept ASPLAIN input, however this is not yet officially supported. If you use AS Numbers internally, or with other tools that have not yet been updated, you may be interested in a conversion tool that has been provided by APNIC. This tool converts ASDOT format AS Numbers to ASPLAIN and back. It can be downloaded from: http://www.apnic.net/cgi-bin/convert-asn.pl If you have any concerns about this matter, please send an email to Kind regards, Denis Walker Business Analyst Database Department RIPE NCC