From sander at steffann.nl Fri Aug 1 14:30:15 2014 From: sander at steffann.nl (Sander Steffann) Date: Fri, 1 Aug 2014 14:30:15 +0200 Subject: [ncc-services-wg] [members-discuss] [address-policy-wg] Crimea papers In-Reply-To: <53DB877D.7080100@ripe.net> References: <53D65628.6010001@ukraine.su> <53D66B6A.3060002@ripe.net> <53D68EF8.2060103@ukraine.su> <20140728180451.GC51793@Space.Net> <20140729073316.GJ51793@Space.Net> <53D75403.3080902@netassist.ua> <20140729092156.GM51793@Space.Net> <29BD1EF7-5F1A-47BE-9960-2F36DD21C01A@rfc1035.com> <7C28157D-633E-45BC-8855-4B3864CC436A@bondis.org> <53DA22CE.20506@netassist.ua> <2981AC77-7EB0-4C9F-8B16-F1644EBB9E5B@steffann.nl> <53DB877D.7080100@ripe.net> Message-ID: <1BB9448C-60FB-435D-8CB0-9284DE69B83A@steffann.nl> Hi Athina, > So any prohibition is related to key equipment and technology as listed > in Annex III. > > Annex III does not include anything related to the services we provide, > including the registration of Internet number resources. Glad to hear that! Life for people there is difficult enough as it is, and having access to internet resources can only help them. > We will continue to follow the development of any sanctions that affect > the provisioning of services in our region. Thank you Athina, Sander From athina.fragkouli at ripe.net Fri Aug 1 14:26:37 2014 From: athina.fragkouli at ripe.net (Athina Fragkouli) Date: Fri, 01 Aug 2014 14:26:37 +0200 Subject: [ncc-services-wg] [members-discuss] [address-policy-wg] Crimea papers In-Reply-To: <2981AC77-7EB0-4C9F-8B16-F1644EBB9E5B@steffann.nl> References: <53D65628.6010001@ukraine.su> <53D66B6A.3060002@ripe.net> <53D68EF8.2060103@ukraine.su> <20140728180451.GC51793@Space.Net> <20140729073316.GJ51793@Space.Net> <53D75403.3080902@netassist.ua> <20140729092156.GM51793@Space.Net> <29BD1EF7-5F1A-47BE-9960-2F36DD21C01A@rfc1035.com> <7C28157D-633E-45BC-8855-4B3864CC436A@bondis.org> <53DA22CE.20506@netassist.ua> <2981AC77-7EB0-4C9F-8B16-F1644EBB9E5B@steffann.nl> Message-ID: <53DB877D.7080100@ripe.net> Dear all, The RIPE NCC follows the developments regarding sanctions adopted by the European Union (EU) and reviews whether these sanctions restrict us from providing services to network operators in certain regions or from having a contractual relationship with them. Additionally, the RIPE NCC communicates with the Dutch authorities in order to clarify the details of the imposed sanctions and our obligations. So far, the EU sanctions adopted for the Crimea region (including the newest sanctions imposed by the EU by adopting the Council Regulation (EU) No 825/2014 of 30 July 2014) do not restrict us from doing any of the above. http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv:OJ.L_.2014.226.01.0002.01.ENG In response to the concerns raised about this new Regulation, we have the following remarks: According to Article 2c of the Regulation: 1. It shall be prohibited to sell, supply, transfer, export, directly or indirectly, key equipment and technology as listed in _Annex_III_ to any natural or legal person, entity or body in Crimea or Sevastopol or for use in Crimea or Sevastopol. 2. _Annex_III_ shall include key equipment and technology related to the creation, acquisition or development of infrastructure in the following sectors: ... (b) telecommunications; ... 3. It shall be prohibited to: (a) provide, directly or indirectly, technical assistance or brokering services related to the key equipment and technology listed in _Annex_III_, or related to the provision, manufacture, maintenance and use of items listed in _Annex_III_ to any natural or legal person, entity or body in Crimea or Sevastopol or for use in Crimea or Sevastopol; ... So any prohibition is related to key equipment and technology as listed in Annex III. Annex III does not include anything related to the services we provide, including the registration of Internet number resources. We will continue to follow the development of any sanctions that affect the provisioning of services in our region. Kind regards, Athina Fragkouli Legal Counsel RIPE NCC On 31/07/14 14:38, Sander Steffann wrote: > Hi, > > I just got a question about how I meant this sentence: > >> As a networking person 'related to the provision [...] and use of items listed' does seem to include allocating number resources. > > Just so that people don't misunderstand me: what I meant here is that the terminology used in this legal document has some specific meaning in the networking world. The meaning in a legal sense is probably completely different from what I as a networking engineer would read. Which is why I think we need to let a legal specialist comment on this. IANAL and my opinion doesn't mean anything here :) > > Sorry for the confusion! > > Cheers, > Sander > > > ---- > If you don't want to receive emails from the RIPE NCC members-discuss > mailing list, please log in to your LIR Portal account and go to the general page: > https://lirportal.ripe.net/general/ > > Click on "Edit my LIR details", under "Subscribed Mailing Lists". From here, you can add or remove addresses. > From ingrid at ripe.net Tue Aug 5 12:23:25 2014 From: ingrid at ripe.net (Ingrid Wijte) Date: Tue, 05 Aug 2014 12:23:25 +0200 Subject: [ncc-services-wg] Request for Feedback: Phasing Out Text-Based Email Request Forms Message-ID: <53E0B09D.1090507@ripe.net> Dear colleagues, We are currently working to streamline the process around resource requests, which is something that was asked for in the RIPE NCC Survey 2013. As you will be aware, we offer request forms in the LIR Portal in addition to the text-based email forms that are published in the RIPE document store: http://www.ripe.net/ripe/docs/current-ripe-documents/request-forms-supporting-notes Maintaining two different systems for requests is inefficient, as it requires duplicate work every time there is a policy change. More importantly, the text-based email forms use legacy systems that take engineering time from our staff to maintain. We contacted many LIRs who made requests using the text-based email forms and in most cases they were using them out of habit or due to specific workflows they had. Most said they would not mind to change to the LIR Portal request forms, or adjust their workflows to use an API. Today, most requests come via the LIR Portal rather than by email. Since November 2013: - 95% of IPv6 allocations were issued after an LIR Portal form was sent (909 out of 960) - 91% of IPv4 allocations were requested via the LIR Portal (1,051 out of 1,154) - 75% of ASNs were requested via the LIR Portal (727 out of 975) - From the 25% of ASNs requested via email, 50% of these requests needed several iterations to pass the syntax checks Based on this feedback and the fact that a clear majority of members are requesting resources through the LIR Portal, we would like to propose the following: - The text-based email forms would be archived on 1 November 2014. - We would continue to accept email requests until the end of December 2014 to ensure that regular workflows are not disrupted. - The RIPE NCC would offer an API for those members with specific workflows that prevent them from using the request forms in the LIR Portal. - Text-based request forms that may be used by non-members (e.g. ENUM requests) would remain on the website. - To maintain transparency regarding the information needed to obtain resources, the RIPE NCC would publish these procedures on www.ripe.net. We are interested in your feedback on this proposal: - Do you agree with the general idea of phasing out text-based request forms? - What specific requirements would need to be addressed by the API? - Would December 2014 be a suitable deadline to give you time to adjust your systems and workflows? Please share your feedback on the RIPE NCC Services WG mailing list by emailing before 1 October 2014. If you would like to send us your technical requirements and/or concerns confidentially, please email us at We will provide an update with a summary of the feedback received, along with any next steps if the proposal is to go ahead. Looking forward to your input, Best regards, Ingrid Wijte Assistant Manager Registration Services RIPE NCC From david at sargasso.net Tue Aug 5 14:27:16 2014 From: david at sargasso.net (David Croft) Date: Tue, 5 Aug 2014 14:27:16 +0200 Subject: [ncc-services-wg] Request for Feedback: Phasing Out Text-Based Email Request Forms In-Reply-To: <53E0B09D.1090507@ripe.net> References: <53E0B09D.1090507@ripe.net> Message-ID: Hi Ingrid, I disagree with this in general. Even those who aren't using automated systems to generate the forms, such as myself, find it useful to develop a form in a text file over time before submitting it. Also, if it is such a chore to maintain dual systems, then I suggest the NCC develops a mail-to-API converter at their end rather than require each individual LIR to change their systems. I also suggest that the API should be made available far ahead of phasing anything out. You should release that first long before discussing whether to retire the e-mail submission. Three months is not nearly enough time. It would only be possible to judge this once the API is place to gauge the development effort required. Some if not most LIRs do not have full-time developers on staff or do not maintain their own systems. Regards, David Croft On 5 August 2014 12:23, Ingrid Wijte wrote: > Dear colleagues, > > We are currently working to streamline the process around resource > requests, which is something that was asked for in the RIPE NCC Survey > 2013. As you will be aware, we offer request forms in the LIR Portal > in addition to the text-based email forms that are published in the > RIPE document store: > > http://www.ripe.net/ripe/docs/current-ripe-documents/request-forms-supporting-notes > > Maintaining two different systems for requests is inefficient, as it > requires duplicate work every time there is a policy change. More > importantly, the text-based email forms use legacy systems that take > engineering time from our staff to maintain. > > We contacted many LIRs who made requests using the text-based email > forms and in most cases they were using them out of habit or due to > specific workflows they had. Most said they would not mind to change > to the LIR Portal request forms, or adjust their workflows to use an > API. > > Today, most requests come via the LIR Portal rather than by email. > Since November 2013: > > - 95% of IPv6 allocations were issued after an LIR Portal form was > sent (909 out of 960) > - 91% of IPv4 allocations were requested via the LIR Portal (1,051 out > of 1,154) > - 75% of ASNs were requested via the LIR Portal (727 out of 975) > - From the 25% of ASNs requested via email, 50% of these requests > needed several iterations to pass the syntax checks > > Based on this feedback and the fact that a clear majority of members > are requesting resources through the LIR Portal, we would like to > propose the following: > > - The text-based email forms would be archived on 1 November 2014. > - We would continue to accept email requests until the end of December > 2014 to ensure that regular workflows are not disrupted. > - The RIPE NCC would offer an API for those members with specific > workflows that prevent them from using the request forms in the LIR > Portal. > - Text-based request forms that may be used by non-members (e.g. ENUM > requests) would remain on the website. > - To maintain transparency regarding the information needed to obtain > resources, the RIPE NCC would publish these procedures on > www.ripe.net. > > We are interested in your feedback on this proposal: > > - Do you agree with the general idea of phasing out text-based request > forms? > - What specific requirements would need to be addressed by the API? > - Would December 2014 be a suitable deadline to give you time to > adjust your systems and workflows? > > Please share your feedback on the RIPE NCC Services WG mailing list by > emailing before 1 October 2014. If you > would like to send us your technical requirements and/or concerns > confidentially, please email us at > > We will provide an update with a summary of the feedback received, > along with any next steps if the proposal is to go ahead. > > Looking forward to your input, > Best regards, > > Ingrid Wijte > Assistant Manager Registration Services > RIPE NCC > > > > -- David Croft IT - Network Engineering Sargasso Networks http://www.sargasso.net/ For support enquiries please always contact support at sargasso.net and not any named individual. UK: 0845 034 5020 USA: 212-400-1694 From gert at space.net Tue Aug 5 18:17:48 2014 From: gert at space.net (Gert Doering) Date: Tue, 5 Aug 2014 18:17:48 +0200 Subject: [ncc-services-wg] Request for Feedback: Phasing Out Text-Based Email Request Forms In-Reply-To: <53E0B09D.1090507@ripe.net> References: <53E0B09D.1090507@ripe.net> Message-ID: <20140805161748.GA74243@Space.Net> Hi, On Tue, Aug 05, 2014 at 12:23:25PM +0200, Ingrid Wijte wrote: > We contacted many LIRs who made requests using the text-based email > forms and in most cases they were using them out of habit or due to > specific workflows they had. Most said they would not mind to change > to the LIR Portal request forms, or adjust their workflows to use an > API. I'm a heavy mail form user, and I have been bitten by inconsistencies in the robot in the past (requiring bits that are not in the form, or refusing bits that *are* in the form, or lagging behind updated forms, or just refusing to understand me)... The amount of interaction I have with the NCC these days is pretty much "two requests for every new LIR that is set up" (initial-v6, initial-v4), and every now and then, a spurious AS number or IPv6 PI, maybe 5 formal requests in total per year. Given all that I would be fine with going through the LIR portal for these few requests. Even if I still prefer mail to web interfaces :-) Gert Doering -- speaking for two minor LIRs not doing much PI/AS business -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 811 bytes Desc: not available URL: From hank at efes.iucc.ac.il Tue Aug 5 18:45:05 2014 From: hank at efes.iucc.ac.il (Hank Nussbacher) Date: Tue, 05 Aug 2014 19:45:05 +0300 Subject: [ncc-services-wg] Request for Feedback: Phasing Out Text-Based Email Request Forms Message-ID: <20140805164507.1647156128@doar.tau.ac.il> Just as long as auto-dbm at ripe.net continues to function.? :-) Hank On Aug 5, 2014 7:17 PM, Gert Doering wrote: > > Hi, > > On Tue, Aug 05, 2014 at 12:23:25PM +0200, Ingrid Wijte wrote: > > We contacted many LIRs who made requests using the text-based email > > forms and in most cases they were using them out of habit or due to > > specific workflows they had. Most said they would not mind to change > > to the LIR Portal request forms, or adjust their workflows to use an > > API. > > I'm a heavy mail form user, and I have been bitten by inconsistencies > in the robot in the past (requiring bits that are not in the form, or > refusing bits that *are* in the form, or lagging behind updated forms, > or just refusing to understand me)... > > The amount of interaction I have with the NCC these days is pretty > much "two requests for every new LIR that is set up" (initial-v6, > initial-v4), and every now and then, a spurious AS number or IPv6 PI, > maybe 5 formal requests in total per year. > > Given all that I would be fine with going through the LIR portal for > these few requests.? Even if I still prefer mail to web interfaces :-) > > Gert Doering > ??????? -- speaking for two minor LIRs not doing much PI/AS business > -- > have you enabled IPv6 on something today...? > > SpaceNet AG??????????????????????? Vorstand: Sebastian v. Bomhard > Joseph-Dollinger-Bogen 14????????? Aufsichtsratsvors.: A. Grundner-Culemann > D-80807 Muenchen?????????????????? HRB: 136055 (AG Muenchen) > Tel: +49 (0)89/32356-444?????????? USt-IdNr.: DE813185279 From danny at danysek.cz Tue Aug 5 20:08:56 2014 From: danny at danysek.cz (Daniel Suchy) Date: Tue, 05 Aug 2014 20:08:56 +0200 Subject: [ncc-services-wg] Request for Feedback: Phasing Out Text-Based Email Request Forms In-Reply-To: <53E0B09D.1090507@ripe.net> References: <53E0B09D.1090507@ripe.net> Message-ID: <53E11DB8.6060209@danysek.cz> Hello, with each request submited over LIR portal, there's always generated filled form similar to form sent by email directly. So in general, LIR portal should be simple filled form generator (and there're not so many changes in the form in general) and all parsing can be done against form content, source independently. In general I think NCC has enough budged to support multiple input interfaces and keep *everyone* confortable, even some input method seems to be "legacy". And I don't think it's hard in this case. The "minority" using email interface is still large enough to support email requests. Also there should be some operational issues with portal/API interface and then is fine to have another way to submit request (even it's processed later), as traditional email can be easily queued... Even I'm using portal preferably for majority of changes, I would like to have fall-back option. With regards, Daniel On 5.8.2014 12:23, Ingrid Wijte wrote: > Dear colleagues, > > We are currently working to streamline the process around resource > requests, which is something that was asked for in the RIPE NCC Survey > 2013. As you will be aware, we offer request forms in the LIR Portal > in addition to the text-based email forms that are published in the > RIPE document store: > > http://www.ripe.net/ripe/docs/current-ripe-documents/request-forms-supporting-notes > > > Maintaining two different systems for requests is inefficient, as it > requires duplicate work every time there is a policy change. More > importantly, the text-based email forms use legacy systems that take > engineering time from our staff to maintain. > > We contacted many LIRs who made requests using the text-based email > forms and in most cases they were using them out of habit or due to > specific workflows they had. Most said they would not mind to change > to the LIR Portal request forms, or adjust their workflows to use an > API. > > Today, most requests come via the LIR Portal rather than by email. > Since November 2013: > > - 95% of IPv6 allocations were issued after an LIR Portal form was > sent (909 out of 960) > - 91% of IPv4 allocations were requested via the LIR Portal (1,051 out > of 1,154) > - 75% of ASNs were requested via the LIR Portal (727 out of 975) > - From the 25% of ASNs requested via email, 50% of these requests > needed several iterations to pass the syntax checks > > Based on this feedback and the fact that a clear majority of members > are requesting resources through the LIR Portal, we would like to > propose the following: > > - The text-based email forms would be archived on 1 November 2014. > - We would continue to accept email requests until the end of December > 2014 to ensure that regular workflows are not disrupted. > - The RIPE NCC would offer an API for those members with specific > workflows that prevent them from using the request forms in the LIR > Portal. > - Text-based request forms that may be used by non-members (e.g. ENUM > requests) would remain on the website. > - To maintain transparency regarding the information needed to obtain > resources, the RIPE NCC would publish these procedures on > www.ripe.net. > > We are interested in your feedback on this proposal: > > - Do you agree with the general idea of phasing out text-based request > forms? > - What specific requirements would need to be addressed by the API? > - Would December 2014 be a suitable deadline to give you time to > adjust your systems and workflows? > > Please share your feedback on the RIPE NCC Services WG mailing list by > emailing before 1 October 2014. If you > would like to send us your technical requirements and/or concerns > confidentially, please email us at > > We will provide an update with a summary of the feedback received, > along with any next steps if the proposal is to go ahead. > > Looking forward to your input, > Best regards, > > Ingrid Wijte > Assistant Manager Registration Services > RIPE NCC > > > From mgrigore at ripe.net Thu Aug 7 16:01:51 2014 From: mgrigore at ripe.net (Mihnea-Costin Grigore) Date: Thu, 07 Aug 2014 16:01:51 +0200 Subject: [ncc-services-wg] Help us improve navigation on www.ripe.net Message-ID: <53E386CF.1030009@ripe.net> Dear colleagues, We will shortly conclude tree testing on the navigational structure for www.ripe.net. This testing measures the steps that users take to find content on our website and takes approximately five minutes to complete. Before we close testing, we would like to ask RIPE NCC members to participate. Most responses so far are from non-members, and we would like the results to reflect the fact that RIPE NCC members are the core audience for our services and activities. The test is available to take at: http://www.ripe.net/lir-services/survey/navigation-survey Kind regards, -- Mihnea-Costin Grigore RIPE NCC Web Services Team Leader - http://www.ripe.net/ From mschmidt at ripe.net Thu Aug 7 16:17:46 2014 From: mschmidt at ripe.net (Marco Schmidt) Date: Thu, 07 Aug 2014 16:17:46 +0200 Subject: [ncc-services-wg] 2014-06 New Policy Proposal (Publication of Sponsoring LIR for Legacy Internet Resource Holders) Message-ID: Dear colleagues, A proposed change to RIPE Document ripe-605, "RIPE NCC Services to Legacy Internet Resource Holders" is now available for discussion. You can find the full proposal at: https://www.ripe.net/ripe/policies/proposals/2014-06 We encourage you to review this proposal and send your comments to before 5 September 2014. Regards, Marco Schmidt Policy Development Officer RIPE NCC From gert at space.net Thu Aug 7 16:26:18 2014 From: gert at space.net (Gert Doering) Date: Thu, 7 Aug 2014 16:26:18 +0200 Subject: [ncc-services-wg] 2014-06 New Policy Proposal (Publication of Sponsoring LIR for Legacy Internet Resource Holders) In-Reply-To: <20140807142112.64CD3608D8@mobil.space.net> References: <20140807142112.64CD3608D8@mobil.space.net> Message-ID: <20140807142618.GK51793@Space.Net> Hiya, On Thu, Aug 07, 2014 at 04:17:46PM +0200, Marco Schmidt wrote: > A proposed change to RIPE Document ripe-605, "RIPE NCC Services to > Legacy Internet Resource Holders" is now available for discussion. Makes sense to me (less special-case variants in the policies). Support. Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 811 bytes Desc: not available URL: From rhe at nosc.ja.net Thu Aug 7 16:26:25 2014 From: rhe at nosc.ja.net (Rob Evans) Date: Thu, 7 Aug 2014 15:26:25 +0100 Subject: [ncc-services-wg] 2014-06 New Policy Proposal (Publication of Sponsoring LIR for Legacy Internet Resource Holders) Message-ID: <20140807142625.GA15302@nosc.ja.net> > https://www.ripe.net/ripe/policies/proposals/2014-06 I wonder why this is in 3.0 rather than 2.3, but if that's where it fits best (and not wanting to embark on wordsmithing), support. Rob From he at uninett.no Thu Aug 7 16:41:09 2014 From: he at uninett.no (Havard Eidnes) Date: Thu, 07 Aug 2014 16:41:09 +0200 (CEST) Subject: [ncc-services-wg] 2014-06 New Policy Proposal (Publication of Sponsoring LIR for Legacy Internet Resource Holders) In-Reply-To: <20140807142618.GK51793@Space.Net> References: <20140807142112.64CD3608D8@mobil.space.net> <20140807142618.GK51793@Space.Net> Message-ID: <20140807.164109.177932138.he@uninett.no> > On Thu, Aug 07, 2014 at 04:17:46PM +0200, Marco Schmidt wrote: >> A proposed change to RIPE Document ripe-605, "RIPE NCC Services to >> Legacy Internet Resource Holders" is now available for discussion. > > Makes sense to me (less special-case variants in the policies). Support. +1 - H?vard From ak at list.ak.cx Thu Aug 7 16:52:02 2014 From: ak at list.ak.cx (Andre Keller) Date: Thu, 07 Aug 2014 16:52:02 +0200 Subject: [ncc-services-wg] 2014-06 New Policy Proposal (Publication of Sponsoring LIR for Legacy Internet Resource Holders) In-Reply-To: <20140807142116.32F074E0BF@imx002.zrh01.ndnet.ch> References: <20140807142116.32F074E0BF@imx002.zrh01.ndnet.ch> Message-ID: <53E39292.1090707@list.ak.cx> Hi all, On 07.08.2014 16:17, Marco Schmidt wrote: > https://www.ripe.net/ripe/policies/proposals/2014-06 > > We encourage you to review this proposal and send your comments to > before 5 September 2014. I support this proposal. Regards Andr? From ripe-wgs.cs at schiefner.de Thu Aug 7 20:58:24 2014 From: ripe-wgs.cs at schiefner.de (Carsten Schiefner) Date: Thu, 07 Aug 2014 20:58:24 +0200 Subject: [ncc-services-wg] 2014-06 New Policy Proposal (Publication of Sponsoring LIR for Legacy Internet Resource Holders) In-Reply-To: References: Message-ID: <53E3CC50.5000602@schiefner.de> All - On 07.08.2014 16:17, Marco Schmidt wrote: > > A proposed change to RIPE Document ripe-605, "RIPE NCC Services to > Legacy Internet Resource Holders" is now available for discussion. > > > > You can find the full proposal at: > > https://www.ripe.net/ripe/policies/proposals/2014-06 > > We encourage you to review this proposal and send your comments to > before 5 September 2014. full support for the idea and the language. Best, -C. From nick at netability.ie Thu Aug 7 21:33:13 2014 From: nick at netability.ie (Nick Hilliard) Date: Thu, 07 Aug 2014 20:33:13 +0100 Subject: [ncc-services-wg] 2014-06 New Policy Proposal (Publication of Sponsoring LIR for Legacy Internet Resource Holders) In-Reply-To: <20140807142625.GA15302@nosc.ja.net> References: <20140807142625.GA15302@nosc.ja.net> Message-ID: <53E3D479.4010506@netability.ie> On 07/08/2014 15:26, Rob Evans wrote: > I wonder why this is in 3.0 rather than 2.3, but if that's where it > fits best (and not wanting to embark on wordsmithing), support. We put it into section 3.0 because the sponsorship publication policy applies to both LIR sponsorship and direct RIPE sponsorship. It seemed more sensible to add the text to just 3.0 rather than to both 2.3 and 2.4. Nick From Piotr.Strzyzewski at polsl.pl Fri Aug 8 08:15:29 2014 From: Piotr.Strzyzewski at polsl.pl (Piotr Strzyzewski) Date: Fri, 8 Aug 2014 08:15:29 +0200 Subject: [ncc-services-wg] 2014-06 New Policy Proposal (Publication of Sponsoring LIR for Legacy Internet Resource Holders) In-Reply-To: <9ff61fa1-cf05-4142-b6ed-93fb234157fb@REKSIO.polsl.pl> References: <9ff61fa1-cf05-4142-b6ed-93fb234157fb@REKSIO.polsl.pl> Message-ID: <20140808061529.GA18968@hydra.ck.polsl.pl> On Thu, Aug 07, 2014 at 04:17:46PM +0200, Marco Schmidt wrote: > A proposed change to RIPE Document ripe-605, "RIPE NCC Services to > Legacy Internet Resource Holders" is now available for discussion. I support this proposal. Piotr -- gucio -> Piotr Strzy?ewski E-mail: Piotr.Strzyzewski at polsl.pl From zsako at iszt.hu Fri Aug 8 10:22:09 2014 From: zsako at iszt.hu (Janos Zsako) Date: Fri, 08 Aug 2014 10:22:09 +0200 Subject: [ncc-services-wg] 2014-06 New Policy Proposal (Publication of Sponsoring LIR for Legacy Internet Resource Holders) In-Reply-To: <20140807142132.946FC1246726@deneb.iszt.hu> References: <20140807142132.946FC1246726@deneb.iszt.hu> Message-ID: <53E488B1.2010702@iszt.hu> Dear all, I think it is useful to treat Legacy resources in a similar way as PI space from the point of view of the publication of Sponsoring LIR. I support the proposal. Best regards, Janos > A proposed change to RIPE Document ripe-605, "RIPE NCC Services to > Legacy Internet Resource Holders" is now available for discussion. > > > > You can find the full proposal at: > > https://www.ripe.net/ripe/policies/proposals/2014-06 > > We encourage you to review this proposal and send your comments to > before 5 September 2014. > > > Regards, > > Marco Schmidt > Policy Development Officer > RIPE NCC > > From david.freedman at uk.clara.net Fri Aug 8 10:25:40 2014 From: david.freedman at uk.clara.net (David Freedman) Date: Fri, 8 Aug 2014 08:25:40 +0000 Subject: [ncc-services-wg] 2014-06 New Policy Proposal (Publication of Sponsoring LIR for Legacy Internet Resource Holders) In-Reply-To: <53E488B1.2010702@iszt.hu> References: <20140807142132.946FC1246726@deneb.iszt.hu>, <53E488B1.2010702@iszt.hu> Message-ID: <3498FCC4-C8E3-44BC-B397-6C403E23870F@uk.clara.net> agree and support. Dave > On 8 Aug 2014, at 09:23, "Janos Zsako" wrote: > > Dear all, > > I think it is useful to treat Legacy resources in a similar way as > PI space from the point of view of the publication of Sponsoring LIR. > > I support the proposal. > > Best regards, > Janos > >> A proposed change to RIPE Document ripe-605, "RIPE NCC Services to >> Legacy Internet Resource Holders" is now available for discussion. >> >> >> >> You can find the full proposal at: >> >> https://www.ripe.net/ripe/policies/proposals/2014-06 >> >> We encourage you to review this proposal and send your comments to >> before 5 September 2014. >> >> >> Regards, >> >> Marco Schmidt >> Policy Development Officer >> RIPE NCC > From hamed at skydsl.ir Fri Aug 8 11:26:14 2014 From: hamed at skydsl.ir (Hamed Shafaghi) Date: Fri, 8 Aug 2014 13:56:14 +0430 Subject: [ncc-services-wg] 2014-06 New Policy Proposal (Publication of Sponsoring LIR for Legacy Internet Resource Holders) Message-ID: +1 -- -------------------------------------------- I Hamed Shafaghi I I Managing Director I I Skydsl? Telecom I hamed at skydsl.ir I www.skydsl.ir I -------------- next part -------------- An HTML attachment was scrubbed... URL: From modonovan at btireland.net Fri Aug 8 12:53:05 2014 From: modonovan at btireland.net (Mick O'Donovan [BT Ireland]) Date: Fri, 8 Aug 2014 11:53:05 +0100 Subject: [ncc-services-wg] 2014-06 New Policy Proposal (Publication of Sponsoring LIR for Legacy Internet Resource Holders) In-Reply-To: <20140807142112.98D2F177E75D@avas02.mail.esat.net> References: <20140807142112.98D2F177E75D@avas02.mail.esat.net> Message-ID: <20140808105305.GA16693@supporthost.esat.net.esat.net> All, I support and agree. -- Mick O'Donovan AS-BTIRE [AS2110] Network Engineer BT Ireland 27 Willsborough Industrial Estate Clonshaugh Dublin 17 http://www.btireland.net From nick at netability.ie Sun Aug 10 18:51:36 2014 From: nick at netability.ie (Nick Hilliard) Date: Sun, 10 Aug 2014 17:51:36 +0100 Subject: [ncc-services-wg] Request for Feedback: Phasing Out Text-Based Email Request Forms In-Reply-To: <53E11DB8.6060209@danysek.cz> References: <53E0B09D.1090507@ripe.net> <53E11DB8.6060209@danysek.cz> Message-ID: <53E7A318.2020300@netability.ie> On 05/08/2014 19:08, Daniel Suchy wrote: > In general I think NCC has enough budged to support multiple input > interfaces and keep *everyone* confortable, even some input method seems > to be "legacy". The RIPE NCC also needs to keep its admin costs under control. > And I don't think it's hard in this case. I don't have enough information to make a judgement about this, but would note in passing that many of the legacy systems I deal with are troublesome to maintain - much more troublesome than non legacy systems. > The "minority" > using email interface is still large enough to support email requests. > Also there should be some operational issues with portal/API interface > and then is fine to have another way to submit request (even it's > processed later), as traditional email can be easily queued... > > Even I'm using portal preferably for majority of changes, I would like > to have fall-back option. We will continue to have fall back to the LIR portal. I'm in favour of dumping the email based templates in favour of an API based system, but we need the API based system to be in place for a while to allow time for people to migrate over. If the consultation ends on Oct 1, with phaseout planned for end Dec 2014, then that's 3 months for everyone to migrate over, which isn't long enough. Could you support them for at least 6-12 months after the API system is introduced? Nick From Woeber at CC.UniVie.ac.at Tue Aug 12 14:10:17 2014 From: Woeber at CC.UniVie.ac.at (Wilfried Woeber) Date: Tue, 12 Aug 2014 14:10:17 +0200 Subject: [ncc-services-wg] Request for Feedback: Phasing Out Text-Based Email Request Forms In-Reply-To: <53E7A318.2020300@netability.ie> References: <53E0B09D.1090507@ripe.net> <53E11DB8.6060209@danysek.cz> <53E7A318.2020300@netability.ie> Message-ID: <53EA0429.2000006@CC.UniVie.ac.at> I haven't made up my mind yet, although the forms-based approach has some beauty for us, as it provides a standardised framwork for collecting input from our customers/members. And while I certainly see the arguments from the NCC's end, I am wondering if it is really in the interst of the memebers and the RIR-LIR system at large, to save some money at the NCC and have all the members spend money individually to migrate to an API. Food for thought... Wilfried From ebais at a2b-internet.com Tue Aug 12 16:49:39 2014 From: ebais at a2b-internet.com (Erik Bais) Date: Tue, 12 Aug 2014 16:49:39 +0200 Subject: [ncc-services-wg] Request for Feedback: Phasing Out Text-Based Email Request Forms In-Reply-To: <20140805161748.GA74243@Space.Net> References: <53E0B09D.1090507@ripe.net> <20140805161748.GA74243@Space.Net> Message-ID: <00d901cfb63c$a8f168c0$fad43a40$@a2b-internet.com> Hi, On Tue, Aug 05, 2014 at 12:23:25PM +0200, Ingrid Wijte wrote: > We contacted many LIRs who made requests using the text-based email > forms and in most cases they were using them out of habit or due to > specific workflows they had. Most said they would not mind to change > to the LIR Portal request forms, or adjust their workflows to use an > API. As a frequent user of the various services of the NCC we moved to the LIR portal based forms for new allocations a while ago and it works fine. I hope that this isn't a sliding scale and that the auto-dbm at ripe.net will also be put to rest as we still use that a LOT. Yes there is much to say to do everything in the Portal and RIPE DB Webinterface, but for most actions using templated emails is still faster for creating new reverse dns zones or person objects etc. On the topic of providing an API for this in the future, I would suggest a longer period (6 to 9 months) for the change from the email forms to the API based forms. As people might need some time to change their internal systems. Regards, Erik Bais A2B Internet From ebais at a2b-internet.com Tue Aug 12 17:04:19 2014 From: ebais at a2b-internet.com (Erik Bais) Date: Tue, 12 Aug 2014 17:04:19 +0200 Subject: [ncc-services-wg] Help us improve navigation on www.ripe.net In-Reply-To: <53E386CF.1030009@ripe.net> References: <53E386CF.1030009@ripe.net> Message-ID: <00e601cfb63e$b4dfd7f0$1e9f87d0$@a2b-internet.com> Hi, > The test is available to take at: > http://www.ripe.net/lir-services/survey/navigation-survey Having done the linked navigation survey, I think I have found most of the information or the majority of the locations where you guided me to... Having said that, Navigation on the RIPE website is probably done for a lot of members done via Google ... (As the search method on the RIPE website isn't accurate enough for most searches.. ) Also while you are looking at navigation, do include in the testing of the new to implement menu's / drop downs etc.. that a lot of people might also use a tablet these days which .. And it shouldn't be a race to the actual menu item in the dropdown in order to click on the next option... Nothing is more annoying than seeing the option you need and not being able to click the item as the dropdown will already be closed by the time you move to the section.. In case you require a one-to-one on the user experience on the new look and feel, feel free to ask me off-list. Regards, Erik Bais From rhe at nosc.ja.net Wed Aug 13 11:35:48 2014 From: rhe at nosc.ja.net (Rob Evans) Date: Wed, 13 Aug 2014 10:35:48 +0100 Subject: [ncc-services-wg] Request for Feedback: Phasing Out Text-Based Email Request Forms In-Reply-To: <53E0B09D.1090507@ripe.net> References: <53E0B09D.1090507@ripe.net> Message-ID: Hi Ingrid, We are one of the NCC's members that still use the email forms. However, they are generated automatically by our internal systems (as David Croft said he does) using information from our customers, not crafted by hand. Whilst we're not averse to changing the systems, we're at the point where given the size of the AW and low rate of requests that go above that, we'd be likely to just drop to entering them manually into the LIR portal if the email forms weren't available. This would be more work for us, but probably less work than adapting our system to use an as-yet unpublished API. I'd agree with others that if you do need to drop the email forms, there needs to be a longer migration period to the API than initially suggested. Cheers, Rob From gert at space.net Wed Aug 13 11:40:56 2014 From: gert at space.net (Gert Doering) Date: Wed, 13 Aug 2014 11:40:56 +0200 Subject: [ncc-services-wg] Request for Feedback: Phasing Out Text-Based Email Request Forms In-Reply-To: <53EA0429.2000006@CC.UniVie.ac.at> References: <53E0B09D.1090507@ripe.net> <53E11DB8.6060209@danysek.cz> <53E7A318.2020300@netability.ie> <53EA0429.2000006@CC.UniVie.ac.at> Message-ID: <20140813094056.GV51793@Space.Net> Hi, On Tue, Aug 12, 2014 at 02:10:17PM +0200, Wilfried Woeber wrote: > I haven't made up my mind yet, although the forms-based approach has some > beauty for us, as it provides a standardised framwork for collecting input > from our customers/members. > > And while I certainly see the arguments from the NCC's end, I am wondering > if it is really in the interst of the memebers and the RIR-LIR system at large, > to save some money at the NCC and have all the members spend money individually > to migrate to an API. I hear you, but I wonder how many formal requests you send to RS every year? For us, with the end of IPv4, abandonment of IPv4 PI and IPv4 AW, and the non-requirement to get IPv6 assignments approved, the number of formal interactions with the NCC that go through the hostmaster robot (= e-mail forms) has gone down to "a handful per year". So I'm really wondering how many LIRs would be affected in a major way by this change. (Also I see this not only as "saving money", but more as "introducing consistency". I've had more than one fight with the HM robot in the past, due to forms not in sync with the robot, or some fields being declared mandatory by the robot while the docs say 'optional' etc, so I can see really good reasons to junk this 20-year-old piece of software) Gert Doering -- primary RIPE contact for a few LIRs -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 811 bytes Desc: not available URL: From gert at space.net Wed Aug 13 11:42:56 2014 From: gert at space.net (Gert Doering) Date: Wed, 13 Aug 2014 11:42:56 +0200 Subject: [ncc-services-wg] Request for Feedback: Phasing Out Text-Based Email Request Forms In-Reply-To: <00d901cfb63c$a8f168c0$fad43a40$@a2b-internet.com> References: <53E0B09D.1090507@ripe.net> <20140805161748.GA74243@Space.Net> <00d901cfb63c$a8f168c0$fad43a40$@a2b-internet.com> Message-ID: <20140813094256.GW51793@Space.Net> Hi, On Tue, Aug 12, 2014 at 04:49:39PM +0200, Erik Bais wrote: > I hope that this isn't a sliding scale and that the auto-dbm at ripe.net will > also be put to rest as we still use that a LOT. Uh, strongly seconded. Everything I said about "I'm fine going to the portal" was speaking about the HM robot pre-processing mails to hostmaster at ripe.net. auto-dbm at ripe.net is a different thing, and if *that* one was supposed to go away, I'd oppose the proposal :) Gert Doering -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 811 bytes Desc: not available URL: From gert at space.net Wed Aug 13 11:44:28 2014 From: gert at space.net (Gert Doering) Date: Wed, 13 Aug 2014 11:44:28 +0200 Subject: [ncc-services-wg] Request for Feedback: Phasing Out Text-Based Email Request Forms In-Reply-To: References: <53E0B09D.1090507@ripe.net> Message-ID: <20140813094428.GX51793@Space.Net> Hi, On Wed, Aug 13, 2014 at 10:35:48AM +0100, Rob Evans wrote: > Whilst we're not averse to changing the systems, we're at the > point where given the size of the AW and low rate of requests that > go above that I should point out that we got *rid* of the AW earlier this year, so you will never again see a customer request for IPv4 that goes over the AW :-) Just sayin'... Gert Doering -- waving various hats around -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 811 bytes Desc: not available URL: From andrea at ripe.net Wed Aug 13 11:48:18 2014 From: andrea at ripe.net (Andrea Cima) Date: Wed, 13 Aug 2014 11:48:18 +0200 Subject: [ncc-services-wg] Request for Feedback: Phasing Out Text-Based Email Request Forms In-Reply-To: <20140813094256.GW51793@Space.Net> References: <53E0B09D.1090507@ripe.net> <20140805161748.GA74243@Space.Net> <00d901cfb63c$a8f168c0$fad43a40$@a2b-internet.com> <20140813094256.GW51793@Space.Net> Message-ID: <53EB3462.70303@ripe.net> Hi Gert, In order to clarify, the proposal only addresses Internet number resource request forms sent to hostmaster at ripe.net. The proposal does not impact the use of auto-dbm at ripe.net. Best regards, Andrea Cima RIPE NCC On 13/8/14 11:42, Gert Doering wrote: > Hi, > > On Tue, Aug 12, 2014 at 04:49:39PM +0200, Erik Bais wrote: >> I hope that this isn't a sliding scale and that the auto-dbm at ripe.net will >> also be put to rest as we still use that a LOT. > Uh, strongly seconded. > > Everything I said about "I'm fine going to the portal" was speaking about > the HM robot pre-processing mails to hostmaster at ripe.net. > > auto-dbm at ripe.net is a different thing, and if *that* one was supposed > to go away, I'd oppose the proposal :) > > Gert Doering From richih.mailinglist at gmail.com Wed Aug 13 12:26:45 2014 From: richih.mailinglist at gmail.com (Richard Hartmann) Date: Wed, 13 Aug 2014 12:26:45 +0200 Subject: [ncc-services-wg] Request for Feedback: Phasing Out Text-Based Email Request Forms In-Reply-To: <53EB3462.70303@ripe.net> References: <53E0B09D.1090507@ripe.net> <20140805161748.GA74243@Space.Net> <00d901cfb63c$a8f168c0$fad43a40$@a2b-internet.com> <20140813094256.GW51793@Space.Net> <53EB3462.70303@ripe.net> Message-ID: On Wed, Aug 13, 2014 at 11:48 AM, Andrea Cima wrote: > In order to clarify, the proposal only addresses Internet number resource > request forms sent to hostmaster at ripe.net. The proposal does not impact the > use of auto-dbm at ripe.net. Thanks. +1 for this proposal then. End of 2014 might be too quick for some people, but you have better usage data than us. If it does not create too much overhead on your side maybe look at extending it or doing a test switch-off for a week or two. Richard From stolpe at resilans.se Wed Aug 13 13:04:45 2014 From: stolpe at resilans.se (Daniel Stolpe) Date: Wed, 13 Aug 2014 13:04:45 +0200 (CEST) Subject: [ncc-services-wg] 2014-06 New Policy Proposal (Publication of Sponsoring LIR for Legacy Internet Resource Holders) In-Reply-To: <20140807142618.GK51793@Space.Net> References: <20140807142112.64CD3608D8@mobil.space.net> <20140807142618.GK51793@Space.Net> Message-ID: On Thu, 7 Aug 2014, Gert Doering wrote: > Hiya, > > On Thu, Aug 07, 2014 at 04:17:46PM +0200, Marco Schmidt wrote: >> A proposed change to RIPE Document ripe-605, "RIPE NCC Services to >> Legacy Internet Resource Holders" is now available for discussion. > > Makes sense to me (less special-case variants in the policies). Support. +1 Best Regards, Daniel Stolpe _________________________________________________________________________________ Daniel Stolpe Tel: 08 - 688 11 81 stolpe at resilans.se Resilans AB Fax: 08 - 55 00 21 63 http://www.resilans.se/ Box 45 094 556741-1193 104 30 Stockholm From Woeber at CC.UniVie.ac.at Wed Aug 13 15:48:49 2014 From: Woeber at CC.UniVie.ac.at (Wilfried Woeber) Date: Wed, 13 Aug 2014 15:48:49 +0200 Subject: [ncc-services-wg] Request for Feedback: Phasing Out Text-Based Email Request Forms In-Reply-To: <20140813094056.GV51793@Space.Net> References: <53E0B09D.1090507@ripe.net> <53E11DB8.6060209@danysek.cz> <53E7A318.2020300@netability.ie> <53EA0429.2000006@CC.UniVie.ac.at> <20140813094056.GV51793@Space.Net> Message-ID: <53EB6CC1.20308@CC.UniVie.ac.at> Gert Doering wrote: [...] > I hear you, but I wonder how many formal requests you send to RS every > year? For us, with the end of IPv4, abandonment of IPv4 PI and IPv4 AW, > and the non-requirement to get IPv6 assignments approved, the number of > formal interactions with the NCC that go through the hostmaster robot > (= e-mail forms) has gone down to "a handful per year". Agreed, probably a small hand full :-) But this exacly sounds like an agrgument for me to *not* go down the API route, 'cause it is costing time or money. So, this sounds like we'll be pushed to the manual Click-O-Matic stuff in the Portal.... Wilfried From gert at space.net Wed Aug 13 15:55:12 2014 From: gert at space.net (Gert Doering) Date: Wed, 13 Aug 2014 15:55:12 +0200 Subject: [ncc-services-wg] Request for Feedback: Phasing Out Text-Based Email Request Forms In-Reply-To: <53EB6CC1.20308@CC.UniVie.ac.at> References: <53E0B09D.1090507@ripe.net> <53E11DB8.6060209@danysek.cz> <53E7A318.2020300@netability.ie> <53EA0429.2000006@CC.UniVie.ac.at> <20140813094056.GV51793@Space.Net> <53EB6CC1.20308@CC.UniVie.ac.at> Message-ID: <20140813135512.GG51793@Space.Net> Hi, On Wed, Aug 13, 2014 at 03:48:49PM +0200, Wilfried Woeber wrote: > Gert Doering wrote: > [...] > > I hear you, but I wonder how many formal requests you send to RS every > > year? For us, with the end of IPv4, abandonment of IPv4 PI and IPv4 AW, > > and the non-requirement to get IPv6 assignments approved, the number of > > formal interactions with the NCC that go through the hostmaster robot > > (= e-mail forms) has gone down to "a handful per year". > > Agreed, probably a small hand full :-) > > But this exacly sounds like an agrgument for me to *not* go down the API > route, 'cause it is costing time or money. Phrased that way, indeed. (I do not intend to use the API, wo I wasn't truly considering aspects relating to the API at all, but focusing on "would I miss the hostmaster robot"). > So, this sounds like we'll be pushed to the manual Click-O-Matic stuff > in the Portal.... Yep. Works for me, might not work for everyone... so it's definitely appreciated RS is asking :) Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 811 bytes Desc: not available URL: From training at ripe.net Tue Aug 19 12:15:09 2014 From: training at ripe.net (Training Services) Date: Tue, 19 Aug 2014 12:15:09 +0200 Subject: [ncc-services-wg] [training] RIPE NCC Training Courses October-December 2014 Message-ID: <53F323AD.3060808@ripe.net> Dear Colleagues, Our training team travels the RIPE NCC service region to deliver training courses to our members without any additional cost. Over the next few months, we'll be in Ljubljana, Norway, Tbilisi, Berlin, Bratislava, Amman, Lyon, Athens, London, Amsterdam. Visit the following page to register and to check which training courses we are giving in your area: https://lirportal.ripe.net/training/courses The RIPE NCC delivers the following training courses: - LIR Training Course - RIPE Database Training Course - Basic IPv6 Training Course - Advanced IPv6 Training Course - Routing Security Training Course - DNSSEC Training Course For more information visit: http://www.ripe.net/lir-services/training/courses With kind regards, Rumy Spratley-Kanis Training Services Manager From training at ripe.net Tue Aug 26 14:47:55 2014 From: training at ripe.net (Training Services) Date: Tue, 26 Aug 2014 14:47:55 +0200 Subject: [ncc-services-wg] IP Address Space Course this November in London Message-ID: <53FC81FB.2010909@ripe.net> Dear Colleagues, We are happy to announce a new RIPE NCC training course that will take place on the Sunday before the RIPE 69 Meeting in London this November. This new course will focus on how to obtain, transfer, manage and protect your IP address space. The course is free of charge and is open to anyone interested. The course will cover the most frequently asked questions the RIPE NCC receives about IP address space. Course title: RIPE NCC Presents: IP Address Space Basics How to obtain, transfer, manage and protect your IP addresses Goals: By the end of this course, you will be able to: - Manage your IPv4 and IPv6 addresses according to current RIPE Policies - Understand how to obtain IPv4 addresses through transfers - Protect your address space from hijacking Target audience: Anyone interested in the policies and procedures around address space in the RIPE NCC service region, and companies looking at address space transfers, mergers and acquisitions. No prior knowledge of the topic is necessary. Time: Sunday, 2 November, 10:00?16:00 Outline: - Becoming a RIPE NCC member (why and how) - Obtaining IP addresses (IPv4 and IPv6) - IP address space transfers, mergers and acquisitions - IPv6 basics - Address space hijacking - Resource Certification (RPKI) Cost: Free of charge. Coffee and lunch will be provided. The course will be delivered by representatives from the RIPE NCC?s Training Services and Registration Services departments. If you are interested in attending this course, please let us know asap by sending an email to training at ripe.net. Be quick - we only have 40 seats available on a first come, first served basis! If there is enough interest, we will continue to offer courses on different topics of interest alongside future RIPE Meetings. Kind regards, Training Services From stolpe at resilans.se Wed Aug 27 11:17:59 2014 From: stolpe at resilans.se (Daniel Stolpe) Date: Wed, 27 Aug 2014 11:17:59 +0200 (CEST) Subject: [ncc-services-wg] Request for Feedback: Phasing Out Text-Based Email Request Forms In-Reply-To: <20140813135512.GG51793@Space.Net> References: <53E0B09D.1090507@ripe.net> <53E11DB8.6060209@danysek.cz> <53E7A318.2020300@netability.ie> <53EA0429.2000006@CC.UniVie.ac.at> <20140813094056.GV51793@Space.Net> <53EB6CC1.20308@CC.UniVie.ac.at> <20140813135512.GG51793@Space.Net> Message-ID: On Wed, 13 Aug 2014, Gert Doering wrote: > Hi, > > On Wed, Aug 13, 2014 at 03:48:49PM +0200, Wilfried Woeber wrote: >> Gert Doering wrote: >> [...] >>> I hear you, but I wonder how many formal requests you send to RS every >>> year? For us, with the end of IPv4, abandonment of IPv4 PI and IPv4 AW, >>> and the non-requirement to get IPv6 assignments approved, the number of >>> formal interactions with the NCC that go through the hostmaster robot >>> (= e-mail forms) has gone down to "a handful per year". >> >> Agreed, probably a small hand full :-) >> >> But this exacly sounds like an agrgument for me to *not* go down the API >> route, 'cause it is costing time or money. > > Phrased that way, indeed. (I do not intend to use the API, wo I wasn't > truly considering aspects relating to the API at all, but focusing on > "would I miss the hostmaster robot"). We send more than a handful (of text files per year to the hostmaster robot) and would like to see what the new options are before just shutting it down. An API might work for us. >> So, this sounds like we'll be pushed to the manual Click-O-Matic stuff >> in the Portal.... > > Yep. Works for me, might not work for everyone... so it's definitely > appreciated RS is asking :) Yes. Please show us the API before you just take the robot down. Cheers, Daniel _________________________________________________________________________________ Daniel Stolpe Tel: 08 - 688 11 81 stolpe at resilans.se Resilans AB Fax: 08 - 55 00 21 63 http://www.resilans.se/ Box 45 094 556741-1193 104 30 Stockholm