September 2007 - address-policy-wg

1st DRAFT agenda for RIPE 55 APWG meeting
by Gert Doering 16 Oct '07

16 Oct '07

Dear RIPE address policy WG members, here's a proposal for the APWG meeting agenda for the upcoming RIPE meeting (in October in Amsterdam). This time we're early, so there is time to shuffle things around, etc... - please send your suggestions. ----------------------------- snip -------------------------------- Wednesday, October 24, 11:00-12:30: - formal stuff - overview of concluded proposals (whatever those are, in October) - enough time for generic discussion on PI (IPv4, IPv6, contracts, maybe also covering AS numbers) - Leo Vegoda: a proposal for restructuring of the IPv6 policy Thursday, October 25, 09:00-10:30: - discussion of all other currently-open proposals - new proposals that are not yet in the PDP - AOB ----------------------------- snip -------------------------------- Gert Doering -- APWG chair -- Total number of prefixes smaller than registry allocations: 113403 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

1 2

ASO AC: RIPE NCC Call for Nominations for ASO AC Seat
by Paul Rendek 19 Sep '07

19 Sep '07

[Apologies for duplicate e-mails] Dear Colleagues, This is a call for the RIPE community to nominate individuals from the RIPE NCC service region to serve on the Address Supporting Organization (ASO) Address Council (AC). Hans Petter Holen (Visma IT AS) vacates his seat on 31 December, ending his three-year term. Important ---------- The ASO Memorandum of Understanding (MoU) states that the public nomination period should open 90 days in advance of the next open policy meeting (RIPE 55) and close 30 days before the start of this meeting. Due to an oversight in the RIPE NCC's administrative procedure, this public nomination period was not announced to the RIPE community at the scheduled time. We apologise for any inconvenience this may have caused. If there are no objections from the community, we would like to proceed with the nomination process as follows: - 19 September: Nomination period opens - 15 October: Nomination period closes - 15 October: Complete Nomination list posted at: www.ripe.net/info/resource-admin/aso2007/nominations.html - 25 October: Elections take place during the RIPE Address Policy Working Group session at RIPE 55 How to Nominate Candidates ----------------------- Please send your nominations to nominations(a)ripe.net by 23:00 UTC on 15 October 2007. For details of the information that must be included with your nomination please see: www.ripe.net/info/resource-admin/aso2007/index.html More Information ---------------- Information about the ASO AC and the nomination procedure can be found at: http://aso.icann.org/ac/ Information about the election procedure during RIPE 55 can be found at: www.ripe.net/info/resource-admin/aso2007/selection-procedure.html More information about RIPE 55 can be found at: http://www.ripe.net/ripe/meetings/ripe-55/index.html Kind regards, Paul Rendek Head of External Relations & Communications RIPE NCC

1 0

New AS Number Block allocated to the RIPE NCC
by Alex Le Heux 18 Sep '07

18 Sep '07

Dear Colleagues, The RIPE NCC received the AS Number Block 44032 - 45055 from the IANA in September 2007. You may want to update your records accordingly. Best regards, Alex Le Heux RIPE NCC

1 0

Fwd: Re: Re: NCC#2007083003 Fwd: DELIVERY FAILURE:
by BabyMatthew253 13 Sep '07

13 Sep '07

To whoever may read these: I Matthew Brown, would like to request that there be some sort of action, to allow the ripe database managers to contact ISP(s) when someone reports incorrect or outdated information. This would be very helpful in the process of fighting spam and abuse, and when you rely on the whois servers around the world to get the correct email address(es) so you may forward the abuse/spam to the correct department, but only to have if fail because of outdated data, is not useful in the process of reporting it. As an internet user myself, it is a pain to get so much spam and abusive emails. I'm tired of opening my mailbox on a daily basis, to see I've gotten not one, or two, but on average 75 spam messages a day. And simply telling my email provider, in this case it is Yahoo, that an email is spam/abuse, is not enough to stop it from coming into my mailbox. I now take the time to report it to the proper ISP that holds the IP address where the spam/abuse comes from, or sometimes its a potential virus that comes in the form of a URL/Web pages to visit. So, I rely on having correct data. Please look into developing a policy that will allow the ripe database managers the resources to contact ISP(s) when someone reports incorrect information, so that those of us, like me, who are tired of the amount of spam they get can have correct information when they go to look for it, instead of having to make phone contact with each individual ISP who happens to be international for me. I know that the whois database at www.arin.net has the resources to make contact when someone reports incorrect data, so why not follow suit and have the same resources to do the same thing. Sincerely, Matthew Brown RIPE Database Manager <ripe-dbm(a)ripe.net> wrote: To: BabyMatthew253 <babymattb253(a)yahoo.com> Subject: Re: Re: NCC#2007083003 Fwd: DELIVERY FAILURE: From: RIPE Database Manager <ripe-dbm(a)ripe.net> Date: Fri, 24 Aug 2007 10:25:14 +0200 Dear BabyMatthew253, Thank you for your email regarding out of date contact data in the RIPE database. There may be options we could pursue to check the validity of the contact data in the objects in the RIPE Database. Where we have a direct relationship with the owners of these objects we could request that they update this information. But we do not have a mandate from the RIPE community to allocate any resources to this activity. If you feel this should have a higher priority then you may raise the issue on the Database Working Group or Antispam Working Group or Address Policy Working Group mailing lists. You can find information about the mailing lists here http://www.ripe.net/ripe/wg/index.html These are open working groups and views are welcomed from anyone who wishes to discuss relevant issues. Regards, Milena Rakin ____________________________ RIPE Database Administration. --------------------------------- Ready for the edge of your seat? Check out tonight's top picks on Yahoo! TV.

4 3

New Document available: ripe-416
by Filiz Yilmaz 12 Sep '07

12 Sep '07

Dear Colleagues, We previously announced that the policy proposal 2007-04, "IANA Policy for Allocation of ASN Blocks to RIRs" had been accepted by the RIPE community. This policy has now been published as a RIPE Document: ripe-416, "Internet Assigned Numbers Authority (IANA) Policy for Allocation of ASN Blocks to Regional Internet Registries" You can find this document at: http://www.ripe.net/ripe/docs/ripe-416.html Please note that this is a global policy and will therefore come into effect only after it has been accepted as a policy in all other RIR regions and then ratified by ICANN. Kind regards, Filiz Yilmaz RIPE NCC Policy Development Officer

1 0

2007-04 Proposal Accepted (IANA Policy for Allocation of ASN Blocks to RIRs)
by Filiz Yilmaz 05 Sep '07

05 Sep '07

PDP Number: 2007-04 IANA Policy for Allocation of ASN Blocks to RIRs Dear Colleagues Consensus has been reached, and the proposal described in 2007-04 has been accepted by the RIPE community. This proposal is to have a global policy for the Regional Internet Registries (RIRs) to receive blocks of Autonomous System Numbers (ASNs) from the Internet Assigned Numbers Authority (IANA). You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2007-04.html Thank you for your input. Regards Filiz Yilmaz RIPE NCC Policy Development Officer

1 0