From andrea at ripe.net Thu Feb 12 17:07:27 2009 From: andrea at ripe.net (Andrea Cima) Date: Thu, 12 Feb 2009 17:07:27 +0100 Subject: [ncc-services-wg] 2007-01 Implementation: Direct Internet Resource Assignments to End Users from the RIPE NCC Message-ID: <4994493F.60704@ripe.net> [Apologies for duplicate emails] Dear Colleagues, We are pleased to announce that phase one of policy proposal 2007-01, "Direct Internet Resource Assignments to End Users from the RIPE NCC", will be implemented on 3 March 2009. This change will require that an End User have a contractual relationship with a sponsoring LIR or the RIPE NCC before the End User can receive Internet number resources (Autonomous System (AS) Number, Provider Independent (PI) IPv4 and IPv6, Internet Exchange Point (IXP) and anycasting assignments) directly from the RIPE NCC. The full text of policy proposal 2007-01 can be found at: http://www.ripe.net/ripe/policies/proposals/2007-01.html Phase one addresses the implementation of the new policy in relation to all new requests for independent numbering resource assignments. Please note that from 3 March 2009, End Users requesting independent numbering resources must sign a contract with a sponsoring LIR or with the RIPE NCC in order to receive those resources. Requests for independent numbering resources that do not demonstrate such a contract will not be processed by the RIPE NCC. Information on the required content of contracts between End Users and sponsoring LIRs is available at: http://www.ripe.net/membership/lir-end-user-requirements.html Phase two of policy proposal 2007-01 will address the contractual relationship between End Users who hold previously assigned independent numbering resources and the RIPE NCC or a sponsoring LIR. A plan for implementation of this phase will be presented at the next meeting of the RIPE NCC Services Working Group, which will take place at the RIPE 58 Meeting in Amsterdam from 4-8 May 2009. Kind regards, Andrea Cima RIPE NCC From info at streamservice.nl Thu Feb 12 18:18:55 2009 From: info at streamservice.nl (Stream Service) Date: Thu, 12 Feb 2009 18:18:55 +0100 Subject: [ncc-services-wg] RE: [address-policy-wg] 2007-01 Implementation: Direct Internet Resource Assignments to End Users from the RIPE NCC In-Reply-To: <4994493F.60704@ripe.net> References: <4994493F.60704@ripe.net> Message-ID: <001d01c98d35$fbf2b460$f3d81d20$@nl> Hello, Does this also mean IPv6 PI is possible from 3 March 2009? Because it is possible to request it from that date if I read the e-mail correctly. With kind regards, Mark Scholten Stream Service www.streamservice.nl - Waiting for IPv6 PI -----Original Message----- From: address-policy-wg-admin at ripe.net [mailto:address-policy-wg-admin at ripe.net] On Behalf Of Andrea Cima Sent: donderdag 12 februari 2009 17:07 To: address-policy-wg at ripe.net; ncc-services-wg at ripe.net; ncc-announce at ripe.net Subject: [address-policy-wg] 2007-01 Implementation: Direct Internet Resource Assignments to End Users from the RIPE NCC [Apologies for duplicate emails] Dear Colleagues, We are pleased to announce that phase one of policy proposal 2007-01, "Direct Internet Resource Assignments to End Users from the RIPE NCC", will be implemented on 3 March 2009. This change will require that an End User have a contractual relationship with a sponsoring LIR or the RIPE NCC before the End User can receive Internet number resources (Autonomous System (AS) Number, Provider Independent (PI) IPv4 and IPv6, Internet Exchange Point (IXP) and anycasting assignments) directly from the RIPE NCC. The full text of policy proposal 2007-01 can be found at: http://www.ripe.net/ripe/policies/proposals/2007-01.html Phase one addresses the implementation of the new policy in relation to all new requests for independent numbering resource assignments. Please note that from 3 March 2009, End Users requesting independent numbering resources must sign a contract with a sponsoring LIR or with the RIPE NCC in order to receive those resources. Requests for independent numbering resources that do not demonstrate such a contract will not be processed by the RIPE NCC. Information on the required content of contracts between End Users and sponsoring LIRs is available at: http://www.ripe.net/membership/lir-end-user-requirements.html Phase two of policy proposal 2007-01 will address the contractual relationship between End Users who hold previously assigned independent numbering resources and the RIPE NCC or a sponsoring LIR. A plan for implementation of this phase will be presented at the next meeting of the RIPE NCC Services Working Group, which will take place at the RIPE 58 Meeting in Amsterdam from 4-8 May 2009. Kind regards, Andrea Cima RIPE NCC From sander at steffann.nl Fri Feb 13 00:42:28 2009 From: sander at steffann.nl (Sander Steffann) Date: Fri, 13 Feb 2009 00:42:28 +0100 Subject: [ncc-services-wg] RE: [address-policy-wg] 2007-01 Implementation: Direct Internet Resource Assignments to End Users from the RIPE NCC In-Reply-To: <001d01c98d35$fbf2b460$f3d81d20$@nl> References: <4994493F.60704@ripe.net> <001d01c98d35$fbf2b460$f3d81d20$@nl> Message-ID: <9A1975AB-5D02-4345-B4E0-1AB290D53059@steffann.nl> Hi Mark, > Does this also mean IPv6 PI is possible from 3 March 2009? Because > it is > possible to request it from that date if I read the e-mail correctly. No, this is only about the contractual relationships. The IPv6 PI policy is 2006-01, which is making a lot of progress and getting a lot of support at the moment. - Sander From gert at space.net Fri Feb 13 01:23:42 2009 From: gert at space.net (Gert Doering) Date: Fri, 13 Feb 2009 01:23:42 +0100 Subject: [ncc-services-wg] Re: [address-policy-wg] 2007-01 Implementation: Direct Internet Resource Assignments to End Users from the RIPE NCC In-Reply-To: <001d01c98d35$fbf2b460$f3d81d20$@nl> References: <4994493F.60704@ripe.net> <001d01c98d35$fbf2b460$f3d81d20$@nl> Message-ID: <20090213002342.GQ44476@Space.Net> Hi, On Thu, Feb 12, 2009 at 06:18:55PM +0100, Stream Service wrote: > Does this also mean IPv6 PI is possible from 3 March 2009? Because it is > possible to request it from that date if I read the e-mail correctly. It's the contractual requirements side - *if* there will be IPv6 PI (because we can agree on 2006-01), it will follow the same rules as IPv4 PI. Gert Doering -- APWG chair -- 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 ahmedr at qnetstaff.com Mon Feb 16 08:04:45 2009 From: ahmedr at qnetstaff.com (Ahmed Abdulraheem) Date: Mon, 16 Feb 2009 10:04:45 +0300 Subject: [ncc-services-wg] Re: [ncc-announce] 2007-01 Implementation: Direct Internet Resource Assignments to End Users from the RIPE NCC In-Reply-To: <4994493F.60704@ripe.net> References: <4994493F.60704@ripe.net> Message-ID: Hello, I am still not understanding about some terms in the Policy requirements such as: - End User must specify and establish need for a Provider Independent (PI) assignment. - End User must provide up-to-date registration information to the LIR; some or all data will be published in the RIPE Database. - End User may not sub-assign resources to third parties. I need more explanation about this Regards, Eng.Ahmad Abdul Rahim System Administrator S.A Department Tel.+965-808888-380 Qualitynet Co. -----ncc-announce-admin at ripe.net wrote: ----- To: address-policy-wg at ripe.net, ncc-services-wg at ripe.net, ncc-announce at ripe.net From: Andrea Cima Sent by: ncc-announce-admin at ripe.net Date: 02/12/2009 07:07PM Subject: [ncc-announce] 2007-01 Implementation: Direct Internet Resource Assignments to End Users from the RIPE NCC [Apologies for duplicate emails] Dear Colleagues, We are pleased to announce that phase one of policy proposal 2007-01, "Direct Internet Resource Assignments to End Users from the RIPE NCC", will be implemented on 3 March 2009. This change will require that an End User have a contractual relationship with a sponsoring LIR or the RIPE NCC before the End User can receive Internet number resources (Autonomous System (AS) Number, Provider Independent (PI) IPv4 and IPv6, Internet Exchange Point (IXP) and anycasting assignments) directly from the RIPE NCC. The full text of policy proposal 2007-01 can be found at: http://www.ripe.net/ripe/policies/proposals/2007-01.html Phase one addresses the implementation of the new policy in relation to all new requests for independent numbering resource assignments. Please note that from 3 March 2009, End Users requesting independent numbering resources must sign a contract with a sponsoring LIR or with the RIPE NCC in order to receive those resources. Requests for independent numbering resources that do not demonstrate such a contract will not be processed by the RIPE NCC. Information on the required content of contracts between End Users and sponsoring LIRs is available at: http://www.ripe.net/membership/lir-end-user-requirements.html Phase two of policy proposal 2007-01 will address the contractual relationship between End Users who hold previously assigned independent numbering resources and the RIPE NCC or a sponsoring LIR. A plan for implementation of this phase will be presented at the next meeting of the RIPE NCC Services Working Group, which will take place at the RIPE 58 Meeting in Amsterdam from 4-8 May 2009. Kind regards, Andrea Cima RIPE NCC From andrea at ripe.net Mon Feb 16 14:12:21 2009 From: andrea at ripe.net (Andrea Cima) Date: Mon, 16 Feb 2009 14:12:21 +0100 Subject: [ncc-services-wg] Re: [ncc-announce] 2007-01 Implementation: Direct Internet Resource Assignments to End Users from the RIPE NCC In-Reply-To: References: <4994493F.60704@ripe.net> Message-ID: <49996635.2040903@ripe.net> Dear Ahmed, Thank you for your email. The points that you have raised are not the result of this policy change, but are already part of the current policy. Ahmed Abdulraheem wrote: > Hello, > I am still not understanding about some terms in the Policy requirements > such as: > > - End User must specify and establish need for a Provider Independent (PI) > assignment. > > All users must justify their need for the Internet number resources they request. The RIPE NCC's evaluation of this need is based on the RIPE policy document related to the specific kind of number resource in question. Please find the Address Policy and Address Management related documents online at: http://www.ripe.net/ripe/docs/index.html > - End User must provide up-to-date registration information to the LIR; > some or all data will be published in the RIPE Database. > > Contact information for all assignments and allocations is published in the RIPE Database. The LIR gathers this information from the end-user and enters it into the request form and/or the RIPE Database. > - End User may not sub-assign resources to third parties. > > An assignment is considered to be the final step in the allocation/assignment chain. If an organisation wants to make assignments to its customers, that organisation must obtain a (sub-) allocation. There can be no assignments registered within other assignments, they can only be registered within allocations. Please see further details about this at: http://www.ripe.net/ripe/docs/ripe-441.html If you have any further questions, please contact me. Kind regards, Andrea Cima RIPE NCC > I need more explanation about this > > Regards, > > > Eng.Ahmad Abdul Rahim > System Administrator > S.A Department > Tel.+965-808888-380 > Qualitynet Co. > > -----ncc-announce-admin at ripe.net wrote: ----- > > To: address-policy-wg at ripe.net, ncc-services-wg at ripe.net, > ncc-announce at ripe.net > From: Andrea Cima > Sent by: ncc-announce-admin at ripe.net > Date: 02/12/2009 07:07PM > Subject: [ncc-announce] 2007-01 Implementation: Direct Internet Resource > Assignments to End Users from the RIPE NCC > > [Apologies for duplicate emails] > > Dear Colleagues, > > We are pleased to announce that phase one of policy proposal 2007-01, > "Direct Internet Resource Assignments to End Users from the RIPE NCC", > will be implemented on 3 March 2009. > > This change will require that an End User have a contractual > relationship with a sponsoring LIR or the RIPE NCC before the End User > can receive Internet number resources (Autonomous System (AS) Number, > Provider Independent (PI) IPv4 and IPv6, Internet Exchange Point (IXP) > and anycasting assignments) directly from the RIPE NCC. > > The full text of policy proposal 2007-01 can be found at: > http://www.ripe.net/ripe/policies/proposals/2007-01.html > > Phase one addresses the implementation of the new policy in relation to > all new requests for independent numbering resource assignments. > > Please note that from 3 March 2009, End Users requesting independent > numbering resources must sign a contract with a sponsoring LIR or with > the RIPE NCC in order to receive those resources. Requests for > independent numbering resources that do not demonstrate such a contract > will not be processed by the RIPE NCC. > > Information on the required content of contracts between End Users and > sponsoring LIRs is available at: > http://www.ripe.net/membership/lir-end-user-requirements.html > > Phase two of policy proposal 2007-01 will address the contractual > relationship between End Users who hold previously assigned independent > numbering resources and the RIPE NCC or a sponsoring LIR. A plan for > implementation of this phase will be presented at the next meeting of > the RIPE NCC Services Working Group, which will take place at the RIPE > 58 Meeting in Amsterdam from 4-8 May 2009. > > Kind regards, > > Andrea Cima > RIPE NCC > > > > > From denis at ripe.net Mon Feb 23 17:37:00 2009 From: denis at ripe.net (Denis Walker) Date: Mon, 23 Feb 2009 17:37:00 +0100 Subject: [ncc-services-wg] Test Database for ASPLAIN Implmentation Message-ID: <49A2D0AC.7050709@ripe.net> Dear Colleagues, The RIPE NCC is preparing for the implementation of the IETF RFC 5396. This defines the representation of all AS Numbers in the ASPLAIN format. There is now a test RIPE Database server available using the new software for ASPLAIN. It is a static copy of the NRTM RIPE Database from 19 February 2009, excluding all personal data. All ASDOT objects and references have been converted to ASPLAIN. We did a very simple conversion on this test database which may have broken some referential integrity rules. If you experience any problems please contact . To access this test database: Query: whois-asn32-test.ripe.net (port 43) Mailupdates: asn32-test-dbm at ripe.net Syncupdates: http(s)://syncupdates-asn32-test.db.ripe.net Please test any internal scripts or third party tools you may use for accessing the RIPE Database which involve AS Numbers. Please send any feedback or comments by 13 March 2009 to . Regards, Denis Walker Business Analyst RIPE NCC From Woeber at CC.UniVie.ac.at Mon Feb 23 21:52:42 2009 From: Woeber at CC.UniVie.ac.at (Wilfried Woeber, UniVie/ACOnet) Date: Mon, 23 Feb 2009 20:52:42 +0000 Subject: [ncc-services-wg] 2007-01 Implementation: Model agreement and charging requirements? Message-ID: <49A30C9A.5000708@CC.UniVie.ac.at> 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? In particular, I am interested in guidance on: "End User must pay an annual maintenance fee to the LIR for the resources." 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 :-) Regards, Wilfried. From andrea at ripe.net Tue Feb 24 12:39:47 2009 From: andrea at ripe.net (Andrea Cima) Date: Tue, 24 Feb 2009 12:39:47 +0100 Subject: [ncc-services-wg] 2007-01 Implementation: Model agreement and charging requirements? In-Reply-To: <49A30C9A.5000708@CC.UniVie.ac.at> References: <49A30C9A.5000708@CC.UniVie.ac.at> Message-ID: <49A3DC83.7050201@ripe.net> 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 sergey at devnull.ru Tue Feb 24 22:58:39 2009 From: sergey at devnull.ru (Sergey Myasoedov) Date: Tue, 24 Feb 2009 22:58:39 +0100 Subject: [ncc-services-wg] Test Database for ASPLAIN Implmentation In-Reply-To: <49A2D0AC.7050709@ripe.net> References: <49A2D0AC.7050709@ripe.net> Message-ID: <685084732.20090224225839@devnull.ru> Dear Denis, it seems the server whois-asn32-test.ripe.net is unavailable: $ ping whois-asn32-test.ripe.net PING whois-asn32-test.ripe.net (193.0.19.77): 56 data bytes ^C --- whois-asn32-test.ripe.net ping statistics --- 6 packets transmitted, 0 packets received, 100% packet loss Monday, February 23, 2009, 5:37:00 PM, you wrote: DW> Dear Colleagues, DW> The RIPE NCC is preparing for the implementation of the IETF RFC 5396. DW> This defines the representation of all AS Numbers in the ASPLAIN format. DW> There is now a test RIPE Database server available using the new DW> software for ASPLAIN. It is a static copy of the NRTM RIPE Database DW> from 19 February 2009, excluding all personal data. All ASDOT DW> objects and references have been converted to ASPLAIN. DW> We did a very simple conversion on this test database which may have DW> broken some referential integrity rules. If you experience any problems DW> please contact . DW> To access this test database: DW> Query: whois-asn32-test.ripe.net (port 43) DW> Mailupdates: asn32-test-dbm at ripe.net DW> Syncupdates: http(s)://syncupdates-asn32-test.db.ripe.net DW> Please test any internal scripts or third party tools you may use for DW> accessing the RIPE Database which involve AS Numbers. Please send any DW> feedback or comments by 13 March 2009 to . DW> Regards, DW> Denis Walker DW> Business Analyst DW> RIPE NCC -- Sergey From gert at space.net Wed Feb 25 08:10:56 2009 From: gert at space.net (Gert Doering) Date: Wed, 25 Feb 2009 08:10:56 +0100 Subject: [ncc-services-wg] Test Database for ASPLAIN Implmentation In-Reply-To: <685084732.20090224225839@devnull.ru> References: <49A2D0AC.7050709@ripe.net> <685084732.20090224225839@devnull.ru> Message-ID: <20090225071056.GF44476@Space.Net> Hi, On Tue, Feb 24, 2009 at 10:58:39PM +0100, Sergey Myasoedov wrote: > it seems the server whois-asn32-test.ripe.net is unavailable: ... no wonder, it doesn't even have a real IP address... $ host -t aaaa whois-asn32-test.ripe.net whois-asn32-test.ripe.net has no AAAA record 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 Wed Feb 25 12:09:00 2009 From: denis at ripe.net (Denis Walker) Date: Wed, 25 Feb 2009 12:09:00 +0100 Subject: [ncc-services-wg] Test Database for ASPLAIN Implmentation In-Reply-To: <685084732.20090224225839@devnull.ru> References: <49A2D0AC.7050709@ripe.net> <685084732.20090224225839@devnull.ru> Message-ID: <49A526CC.10406@ripe.net> Dear Sergey Sorry for the problems. We had not enabled access to it through our firewall. The whois queries should work now. But we have not enabled ping access. regards denis Sergey Myasoedov wrote: > Dear Denis, > > it seems the server whois-asn32-test.ripe.net is unavailable: > > $ ping whois-asn32-test.ripe.net > PING whois-asn32-test.ripe.net (193.0.19.77): 56 data bytes > ^C > --- whois-asn32-test.ripe.net ping statistics --- > 6 packets transmitted, 0 packets received, 100% packet loss > > > > Monday, February 23, 2009, 5:37:00 PM, you wrote: > > DW> Dear Colleagues, > > DW> The RIPE NCC is preparing for the implementation of the IETF RFC 5396. > DW> This defines the representation of all AS Numbers in the ASPLAIN format. > > DW> There is now a test RIPE Database server available using the new > DW> software for ASPLAIN. It is a static copy of the NRTM RIPE Database > DW> from 19 February 2009, excluding all personal data. All ASDOT > DW> objects and references have been converted to ASPLAIN. > > DW> We did a very simple conversion on this test database which may have > DW> broken some referential integrity rules. If you experience any problems > DW> please contact . > > DW> To access this test database: > > DW> Query: whois-asn32-test.ripe.net (port 43) > DW> Mailupdates: asn32-test-dbm at ripe.net > DW> Syncupdates: http(s)://syncupdates-asn32-test.db.ripe.net > > DW> Please test any internal scripts or third party tools you may use for > DW> accessing the RIPE Database which involve AS Numbers. Please send any > DW> feedback or comments by 13 March 2009 to . > > DW> Regards, > DW> Denis Walker > DW> Business Analyst > DW> RIPE NCC > > > > > -- > Sergey > > From denis at ripe.net Wed Feb 25 12:11:06 2009 From: denis at ripe.net (Denis Walker) Date: Wed, 25 Feb 2009 12:11:06 +0100 Subject: [ncc-services-wg] Test Database for ASPLAIN Implmentation In-Reply-To: <20090225071056.GF44476@Space.Net> References: <49A2D0AC.7050709@ripe.net> <685084732.20090224225839@devnull.ru> <20090225071056.GF44476@Space.Net> Message-ID: <49A5274A.5000807@ripe.net> Dear Gert This test whois service is available now on IPv4. Do you need access to it with IPv6 in order to test your internal processes and procedures? regards denis Gert Doering wrote: > Hi, > > On Tue, Feb 24, 2009 at 10:58:39PM +0100, Sergey Myasoedov wrote: > >> it seems the server whois-asn32-test.ripe.net is unavailable: >> > > ... no wonder, it doesn't even have a real IP address... > > $ host -t aaaa whois-asn32-test.ripe.net > whois-asn32-test.ripe.net has no AAAA record > > Gert Doering > -- NetMaster > From gert at space.net Wed Feb 25 12:15:19 2009 From: gert at space.net (Gert Doering) Date: Wed, 25 Feb 2009 12:15:19 +0100 Subject: [ncc-services-wg] Test Database for ASPLAIN Implmentation In-Reply-To: <49A5274A.5000807@ripe.net> References: <49A2D0AC.7050709@ripe.net> <685084732.20090224225839@devnull.ru> <20090225071056.GF44476@Space.Net> <49A5274A.5000807@ripe.net> Message-ID: <20090225111519.GI44476@Space.Net> Hi, On Wed, Feb 25, 2009 at 12:11:06PM +0100, Denis Walker wrote: > This test whois service is available now on IPv4. Do you need access to > it with IPv6 in order to test your internal > processes and procedures? I think that *all* services that the RIPE NCC offers should be IP agnostic, read: IPv4 and IPv6 capable. Even test services. Actually, *especially* test services - people's clients might behave differently if the production system has v6, while the test system didn't. 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 ncc at ripe.net Wed Feb 25 17:36:16 2009 From: ncc at ripe.net (Henk Uijterwaal) Date: Wed, 25 Feb 2009 17:36:16 +0100 Subject: [ncc-services-wg] Implementation of ASPLAIN Format References: <35FF7202-B217-4BE4-8709-CFC40A6FC14E@ripe.net> Message-ID: [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 by the end of March 2009. From that time, any AS Numbers or references must be in the ASPLAIN format. The old ASDOT format will no longer be accepted in RIPE NCC services such as the LIR Portal and the RIPE Database. In order to ensure a smooth transition, any data in the RIPE Database containing an ASDOT AS Number will be converted by the RIPE NCC using the one-to-one mapping that exists between the two formats. Exact details of this conversion will be published closer to the actual date. The RIPE NCC has also provided a test database using the converted software and containing a copy of the RIPE Database. The AS Numbers in this copied data have been converted to ASPLAIN. For more details, see the earlier RIPE NCC announcement: http://www.ripe.net/ripe/maillists/archives/ncc-services-wg/2009/msg00014.html If you use AS Numbers internally, or with other tools that have not yet been updated, you may be interested in a conversion tool 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 write to . Kind regards, Henk Uijterwaal Senior Project Manager, RIPE NCC From gert at space.net Thu Feb 26 14:10:31 2009 From: gert at space.net (Gert Doering) Date: Thu, 26 Feb 2009 14:10:31 +0100 Subject: [asn32] Re: [ncc-services-wg] Test Database for ASPLAIN Implmentation In-Reply-To: <49A693AA.3010900@ripe.net> References: <49A2D0AC.7050709@ripe.net> <685084732.20090224225839@devnull.ru> <20090225071056.GF44476@Space.Net> <49A5274A.5000807@ripe.net> <20090225111519.GI44476@Space.Net> <49A693AA.3010900@ripe.net> Message-ID: <20090226131031.GC44476@Space.Net> Hi, On Thu, Feb 26, 2009 at 02:05:46PM +0100, Agoston Horvath wrote: > You are right. All the announced services are now available over ipv6, too. Cool! ... and it works :-) $ telnet whois-asn32-test.ripe.net 43 Trying 2001:610:240:11:43::1... Connected to whois-asn32-test.ripe.net. Escape character is '^]'. % This is the ASN32 Test server. AS196611 % Note: this output has been filtered. % Information related to 'AS196608 - AS197631' as-block: AS196608 - AS197631 descr: RIPE NCC ASN block ... 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 Thu Feb 26 14:05:46 2009 From: agoston at ripe.net (Agoston Horvath) Date: Thu, 26 Feb 2009 14:05:46 +0100 Subject: [asn32] Re: [ncc-services-wg] Test Database for ASPLAIN Implmentation In-Reply-To: <20090225111519.GI44476@Space.Net> References: <49A2D0AC.7050709@ripe.net> <685084732.20090224225839@devnull.ru> <20090225071056.GF44476@Space.Net> <49A5274A.5000807@ripe.net> <20090225111519.GI44476@Space.Net> Message-ID: <49A693AA.3010900@ripe.net> Dear Gert, You are right. All the announced services are now available over ipv6, too. Sorry for the inconvenience. Kind regards, Agoston Horvath Database Group RIPE NCC Gert Doering wrote: > Hi, > > On Wed, Feb 25, 2009 at 12:11:06PM +0100, Denis Walker wrote: >> This test whois service is available now on IPv4. Do you need access to >> it with IPv6 in order to test your internal >> processes and procedures? > > I think that *all* services that the RIPE NCC offers should be IP agnostic, > read: IPv4 and IPv6 capable. Even test services. > > Actually, *especially* test services - people's clients might behave > differently if the production system has v6, while the test system didn't. > > Gert Doering > -- NetMaster From andrea at ripe.net Thu Feb 26 16:04:22 2009 From: andrea at ripe.net (Andrea Cima) Date: Thu, 26 Feb 2009 16:04:22 +0100 Subject: [ncc-services-wg] RIPE NCC Scheduled Maintenance - Tuesday, 3 March 2009 Message-ID: <49A6AF76.4050900@ripe.net> [Apologies for duplicate emails] Dear Colleagues, We will carry out planned maintenance on Tuesday, 3 March 2009 from 15:00 to 19:00 (UTC). During this time, the LIR Portal, the NEW LIR Application software and the RIPE NCC ticketing system will not be available. Emails sent to the RIPE NCC ticketised mailboxes will be queued and then processed normally when service returns. We apologise for any inconvenience this may cause. Kind regards, Andrea Cima Customer Services Manager RIPE NCC