From randy at psg.com Tue Dec 1 00:15:37 2009 From: randy at psg.com (Randy Bush) Date: Tue, 01 Dec 2009 08:15:37 +0900 Subject: [ncc-services-wg] Re: [db-wg] DOMAIN object proposals In-Reply-To: <4B13B6F6.1030300@ripe.net> References: <4B13B6F6.1030300@ripe.net> Message-ID: > Removal of Forward DOMAIN data from the RIPE Database From noreply at ripe.net Thu Dec 10 10:50:40 2009 From: noreply at ripe.net (Nathalie Trenaman) Date: Thu, 10 Dec 2009 10:50:40 +0100 Subject: [ncc-services-wg] 2009-08 Implementation: IPv6 PI Assignments for LIRs Message-ID: <4B20C470.5030808@ripe.net> [Apologies for duplicate emails] Dear Colleagues, We are pleased to announce that RIPE Policy Proposal 2009-08,"IPv6 Provider Independent (PI) Assignments for LIRs", has been implemented. The RIPE NCC is now ready to accept requests for IPv6 address space under the new policy. This proposal can be found at: http://www.ripe.net/ripe/policies/proposals/2009-08.html The updated "IPv6 Address Allocation and Assignment Policy" document is available at: http://www.ripe.net/ripe/docs/ipv6-policies.html The following document has also been updated to reflect this policy implementation: http://ripe.net/ripe/docs/ipv6-pi-support.html Regards, Nathalie Trenaman Registration Services RIPE NCC From pk at DENIC.DE Mon Dec 14 14:54:05 2009 From: pk at DENIC.DE (Peter Koch) Date: Mon, 14 Dec 2009 14:54:05 +0100 Subject: [ncc-services-wg] Re: [dns-wg] DOMAIN object proposals In-Reply-To: <4B13B6F6.1030300@ripe.net> References: <4B13B6F6.1030300@ripe.net> Message-ID: <20091214135405.GB5987@x27.adm.denic.de> Dear WG, On Mon, Nov 30, 2009 at 01:13:42PM +0100, Denis Walker wrote: > The RIPE NCC made two proposals recently concerning DOMAIN objects: > > 22 October > New rules for reverse domain object creation in the RIPE Database > http://www.ripe.net/ripe/maillists/archives/dns-wg/2009/msg00104.html > > 23 November > Removal of Forward DOMAIN data from the RIPE Database > http://www.ripe.net/ripe/maillists/archives/dns-wg/2009/msg00119.html > > There have been no comments for or against either of these proposals on > the mailing lists. They were both discussed at RIPE Meetings, without > any negative comments. We would like to ask for any final comments by > this Friday, 4 December 2009, so the working group chairs can then draw > a consensus. both proposals have been presented at the latest and previous RIPE meetings. The topic of removal of forward domain objects was also coordinated with the CENTR technical working group due to the TLDs affected. Support was broad with no objections raised. Feedback regarding notifications has been incorporated and the NCC has published a preliminary implementation schedule: >From the perspective of the DNS WG, both proposals have found strong consensus and can move forward. -Peter (for the DNS WG co-chairs) From laura at ripe.net Thu Dec 17 17:28:48 2009 From: laura at ripe.net (Laura Cobley) Date: Thu, 17 Dec 2009 17:28:48 +0100 Subject: [ncc-services-wg] New RIPE NCC PGP Key Message-ID: <4B2A5C40.4080908@ripe.net> [Apologies for duplicate e-mails] Dear Colleagues, On Wednesday, 6 January 2010 we will start using our 2010 key to sign e-mail from our ticketing system. The new key has been signed by the old key as described in the key-management policy on our web site: https://www.ripe.net/rs/pgp/index.html The old key remains valid until Wednesday, 10 February 2010. If you have any questions about this, please contact . Kind Regards, Laura Cobley RIPE NCC From cosku at cccmos.com Fri Dec 18 10:39:15 2009 From: cosku at cccmos.com (Cosku Yilmaz) Date: Fri, 18 Dec 2009 12:39:15 +0300 Subject: [ncc-services-wg] FW: [ncc-announce] New RIPE NCC PGP Key Message-ID: To whom it may concern; I received your e-mail below. Unfortunately it is not clear what I am supposed to do? Would you please explain what is need to be done and what the steps are. Best Regards, ___________________________________ Cosku Yilmaz Managing Director CCCMOS Group Microsoft Gold Certified Partner Tel/ Fax : + 7 (495) 727 41 77 (pbx) E-Mail : cosku.yilmaz at cccmos.com URL : http://www.cccmos.com -----Original Message----- From: ncc-announce-admin at ripe.net [mailto:ncc-announce-admin at ripe.net] On Behalf Of Laura Cobley Sent: Thursday, December 17, 2009 7:29 PM To: ncc-services-wg at ripe.net; ncc-announce at ripe.net Subject: [ncc-announce] New RIPE NCC PGP Key [Apologies for duplicate e-mails] Dear Colleagues, On Wednesday, 6 January 2010 we will start using our 2010 key to sign e-mail from our ticketing system. The new key has been signed by the old key as described in the key-management policy on our web site: https://www.ripe.net/rs/pgp/index.html The old key remains valid until Wednesday, 10 February 2010. If you have any questions about this, please contact . Kind Regards, Laura Cobley RIPE NCC From Woeber at CC.UniVie.ac.at Fri Dec 18 12:36:21 2009 From: Woeber at CC.UniVie.ac.at (Wilfried Woeber, UniVie/ACOnet) Date: Fri, 18 Dec 2009 11:36:21 +0000 Subject: [ncc-services-wg] FW: [ncc-announce] New RIPE NCC PGP Key In-Reply-To: References: Message-ID: <4B2B6935.5040809@CC.UniVie.ac.at> Cosku Yilmaz wrote: > To whom it may concern; > > I received your e-mail below. > > Unfortunately it is not clear what I am supposed to do? > > Would you please explain what is need to be done and what the steps are. If you want to check the signature on eMail sent bei the NCC, which were generated with this new key, you will need the NCC's Public Key in your local keyring. You can grab a copy of this new key by scrolling down on the page given in the URL, to the section labelled: "The Next Key". Save the key which is linked to in *this* section and import it with your PGP-implementation's tool(s) or key management commands - done. You may also want to check the signatures on this new key, afterwards, to prove that it is authentic :-) Hth, Wilfried. PS: I got confused for a short while, too, because I thought the link at the top part of the page would already offer the new key. Alas it still points to the key *currently* in use (in 2009). A bit misleading, imho... > Best Regards, > ___________________________________ > Cosku Yilmaz > Managing Director > CCCMOS Group > Microsoft Gold Certified Partner > > Tel/ Fax : + 7 (495) 727 41 77 (pbx) > E-Mail : cosku.yilmaz at cccmos.com > URL : http://www.cccmos.com From thor at anta.net Fri Dec 18 13:04:21 2009 From: thor at anta.net (Thor Kottelin) Date: Fri, 18 Dec 2009 14:04:21 +0200 Subject: [ncc-services-wg] FW: [ncc-announce] New RIPE NCC PGP Key In-Reply-To: <20091218110004.32265.96976.Mailman@postboy.ripe.net> References: <20091218110004.32265.96976.Mailman@postboy.ripe.net> Message-ID: > From: "Cosku Yilmaz" > To: , > > Date: Fri, 18 Dec 2009 12:39:15 +0300 > Would you please explain what is need to be done and what the steps > are. Do you use, or intend to start using, PGP? If not, you do not need to do anything. If you do use PGP, the steps are basically: download the key, check its authenticity, sign it using your copy of PGP and add it to a key ring. Then use the new key (instead of the previous one) to verify the email messages you receive from the RIPE NCC. -- Thor Kottelin http://www.anta.net/ From Woeber at CC.UniVie.ac.at Fri Dec 18 14:23:29 2009 From: Woeber at CC.UniVie.ac.at (Wilfried Woeber, UniVie/ACOnet) Date: Fri, 18 Dec 2009 13:23:29 +0000 Subject: [ncc-services-wg] FW: [ncc-announce] New RIPE NCC PGP Key In-Reply-To: References: <20091218110004.32265.96976.Mailman@postboy.ripe.net> Message-ID: <4B2B8251.80206@CC.UniVie.ac.at> Thor Kottelin wrote: >>From: "Cosku Yilmaz" >>To: , >> >>Date: Fri, 18 Dec 2009 12:39:15 +0300 > > >>Would you please explain what is need to be done and what the steps >>are. > > > Do you use, or intend to start using, PGP? If not, you do not need to do anything. Correct. > If you do use PGP, or alternatively GnuPG, > the steps are basically: download the key, check its authenticity, > sign it using your copy of PGP And that is not necessary (or even useful) in order "to just verify the email..." > and add it to a key ring. Then use the new key (instead of the previous one) > to verify the email messages you receive from the RIPE NCC. -W From thor at anta.net Fri Dec 18 14:40:45 2009 From: thor at anta.net (Thor Kottelin) Date: Fri, 18 Dec 2009 15:40:45 +0200 Subject: [ncc-services-wg] FW: [ncc-announce] New RIPE NCC PGP Key In-Reply-To: <4B2B8251.80206@CC.UniVie.ac.at> References: <20091218110004.32265.96976.Mailman@postboy.ripe.net> <4B2B8251.80206@CC.UniVie.ac.at> Message-ID: > -----Original Message----- > From: Wilfried Woeber, UniVie/ACOnet > [mailto:Woeber at CC.UniVie.ac.at] > Sent: Friday, December 18, 2009 3:23 PM > To: Thor Kottelin > Cc: ncc-services-wg at ripe.net > Thor Kottelin wrote: > > the steps are basically: download the key, check its > authenticity, > > sign it using your copy of PGP > > And that is not necessary (or even useful) in order "to just verify > the email..." If you trust the key, you should sign it. Until you have signed the key, PGP considers it invalid, and rightfully warns you should you try to verify a message signed with such a key. Please see e.g. in "Tom McCune's PGP Questions & Answers". -- Thor Kottelin http://www.anta.net/ From Woeber at CC.UniVie.ac.at Fri Dec 18 15:21:50 2009 From: Woeber at CC.UniVie.ac.at (Wilfried Woeber, UniVie/ACOnet) Date: Fri, 18 Dec 2009 14:21:50 +0000 Subject: [ncc-services-wg] FW: [ncc-announce] New RIPE NCC PGP Key In-Reply-To: References: <20091218110004.32265.96976.Mailman@postboy.ripe.net> <4B2B8251.80206@CC.UniVie.ac.at> Message-ID: <4B2B8FFE.3070002@CC.UniVie.ac.at> Thor Kottelin wrote: >>-----Original Message----- >>From: Wilfried Woeber, UniVie/ACOnet >>[mailto:Woeber at CC.UniVie.ac.at] >>Sent: Friday, December 18, 2009 3:23 PM >>To: Thor Kottelin >>Cc: ncc-services-wg at ripe.net > > >>Thor Kottelin wrote: > > >>>the steps are basically: download the key, check its >> >>authenticity, >> >>>sign it using your copy of PGP >> >>And that is not necessary (or even useful) in order "to just verify >>the email..." > > > If you trust the key, you should sign it. Until you have signed the key, PGP considers it invalid, and rightfully warns you should you try to verify a message signed with such a key. OK, then PGP and GnuPG obviously do behave differently. Sorry for the confusion! > Please see e.g. in "Tom McCune's PGP Questions & Answers". Wilfried. From noreply at ripe.net Wed Dec 30 14:18:55 2009 From: noreply at ripe.net (Arne Kiessling) Date: Wed, 30 Dec 2009 14:18:55 +0100 Subject: [ncc-services-wg] 2007-01 Policy Implementation - Phase Two Deadline Extended Message-ID: <4B3B533F.4090109@ripe.net> Dear Colleagues, We would like to inform you that the RIPE NCC has extended the deadline for phase two of the 2007-01 policy implementation ("Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region") by two months. LIRs now have until 1 March, 2010 to provide the required documentation for the independent resources that they have marked as "My End User". For further information on the documentation required please see: http://ripe.net/rs/pi-existing-assignments.html If you have any comments or questions, please contact . Kind regards, Arne Kiessling IP Resource Analyst RIPE NCC