- lir-wg - mailman.ripe.net

New IPv6 Documents available
by RIPE NCC Document Announcement Service 27 Jun '02

27 Jun '02

New/Revised RIPE Document Announcement, apologies for multiple e-mails. -------------------------------------- Revised/new documents available from the RIPE document store. Ref: ripe-246 Title: IPv6 Address Allocation and Assignment Policy Author: ARIN, APNIC, RIPE NCC Date: 27 June 2002 Format: PS= 812450 TXT=31632 Obsoletes: ripe-196 Ref: ripe-247 Title: Initial IPv6 Allocation Request Form in the RIPE NCC Service Region Author: Leo Vegoda Date: 27 June 2002 Format: PS=16615 TXT=4226 Obsoletes: ripe-195 Ref: ripe-248 Title: Supporting Notes to the Initial IPv6 Allocation Request Form in the RIPE NCC Service Region Author: Leo Vegoda Date: 27 June 2002 Format: PS=28439 TXT=12788 Ref: ripe-249 Title: IPv6 End User Site Assignment Request Form in the RIPE NCC Service Region Author: Leo Vegoda Date: 27 June 2002 Format: PS=16477 TXT=4126 Ref: ripe-250 Title: Supporting Notes for the IPv6 End User Site Assignment Request Form in the RIPE NCC Service Region Author: Leo Vegoda Date: 27 June 2002 Format: PS=34008 TXT=15211 Short content description ------------------------- This set of IPv6 documents define registry policies for the assignment and allocation of globally-unique IPv6 addresses to Internet ServiceProviders (ISPs) and other organisations. The core document: "IPv6 Address Allocation and Assignment Policy" (ripe-246) obsoletes the "Provisional IPv6 assignment and allocation policy document" (ripe-196). It was developed through joint discussions among the APNIC, ARIN and RIPE communities. The other documents support the policy document, and provide Local Internet Registries with request forms for IPv6 address space. Supporting notes for the request forms can be found in the supporting notes documents. Accessing the RIPE document store --------------------------------- You can access the RIPE documents in HTML format via WWW at the following URLs: "IPv6 Address Allocation and Assignment Policy" (ripe-246) is available at: http://www.ripe.net/ripe/docs/ipv6policy.html "Initial IPv6 Allocation Request Form in the RIPE NCC Service Region" (ripe-247) is available at: http://www.ripe.net/ripe/docs/ipv6-initial.html "Supporting Notes for the Initial IPv6 Allocation Request Form in the RIPE NCC Service Region" (ripe-248) is available at: http://www.ripe.net/ripe/docs/ipv6-supp-initial.html "IPv6 End User Site Assignment Request Form in the RIPE NCC Service Region" (ripe-249) is available at: http://www.ripe.net/ripe/docs/ipv6-assignment-request.html "Supporting Notes for the IPv6 End User Site Assignment Request Form in the RIPE NCC Service Region" (ripe-250) is available at: http://www.ripe.net/ripe/docs/ipv6-supp-assignment.html The RIPE document store is also available via anonymous FTP to ftp.ripe.net, in the directory ripe/docs. The URLs for the new documents on the FTP-server are: ftp://ftp.ripe.net/ripe/docs/ripe-246.ps PostScript version ftp://ftp.ripe.net/ripe/docs/ripe-246.txt plain text version ftp://ftp.ripe.net/ripe/docs/ripe-247.ps PostScript version ftp://ftp.ripe.net/ripe/docs/ripe-247.txt plain text version ftp://ftp.ripe.net/ripe/docs/ripe-247.ps PostScript version ftp://ftp.ripe.net/ripe/docs/ripe-247.txt plain text version ftp://ftp.ripe.net/ripe/docs/ripe-247.ps PostScript version ftp://ftp.ripe.net/ripe/docs/ripe-247.txt plain text version ftp://ftp.ripe.net/ripe/docs/ripe-247.ps PostScript version ftp://ftp.ripe.net/ripe/docs/ripe-247.txt plain text version Kind Regards, RIPE NCC Document Announcement Service

1 0

New Draft in-addr.arpa Policy Document - Reminder
by Paul Rendek 20 Jun '02

20 Jun '02

Dear Colleagues, This is a reminder that the deadline for comments and suggestions for the draft in-addr policy document is set for Monday, 24 June 2002. The new draft "Reverse Address Delegation Under 'in-addr.arpa' in the RIPE NCC Service Region" document can be found on our website at: http://www.ripe.net/ripencc/mem-services/registration/policies/draft-docume… All comments and suggestions should be sent to <lir-wg(a)ripe.net>. Regards, Paul Rendek RIPE NCC

3 2

RE: [apnic-talk] Status field for inet6num objects
by Guy Davies 20 Jun '02

20 Jun '02

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > -----Original Message----- > From: Nigel Titley [mailto:nigel@titley.com] > > On Wed, 2002-06-12 at 07:11, Daniel Karrenberg wrote: > > At 06:00 AM 6/12/2002, Geoff Huston wrote: > > >However, the distinction between "ALLOCATED" and > "ASSIGNED" is perhaps a bit subtle. > > > > When these attributes were created, those particular words > were in deemed both descriptive and clear. > > Maybe the language concerned has shifted underneath in the > meantime ;-). > > As a native speaker of one of its dialects, would you make > a suggestion for improvement? > > Well actually as a native speaker of (another) of its dialects, > I've never considered the distinction of ALLOCATED and ASSIGNED to > be other than subtle. I'd much prefer DELEGATED and ASSIGNED or > some such. This may be a matter of taste however. I tend to agree with Nigel, although I'd go for something even plainer like DELEGATED-TO-LIR and ASSIGNED-TO-END-USER (I know they're a bit verbose but they're absolutely clear ;-) It also makes clear that addresses assigned to an LIR in the role of END-USER are exactly that. That way, an individual who is struggling with English as a second language (or even their first language ;-) can be absolutely clear of the status of a range of addresses. Just my two pence... Regards, Guy -----BEGIN PGP SIGNATURE----- Version: PGP 7.0.1 iQA/AwUBPQca4I3dwu/Ss2PCEQJv6ACeMa1ZbnoN3P7r6VaBANGPa1yXN9UAoMLQ cJpgKn6FvDPmyD1X02WLXJF3 =yl1x -----END PGP SIGNATURE----- This e-mail is private and may be confidential and is for the intended recipient only. If misdirected, please notify us by telephone and confirm that it has been deleted from your system and any copies destroyed. If you are not the intended recipient you are strictly prohibited from using, printing, copying, distributing or disseminating this e-mail or any information contained in it. We use reasonable endeavors to virus scan all e-mails leaving the Company but no warranty is given that this e-mail and any attachments are virus free. You should undertake your own virus checking. The right to monitor e-mail communications through our network is reserved by us.

9 11

Wait Queue
by Tanya Hinman 18 Jun '02

18 Jun '02

Why is the wait queue even longer than it was before the last RIPE Meeting? I thought the general consensus was to get the waiting issue resolved??? 24 days for an ASN request is a bit long. Tanya

2 1

New Document available: RIPE-234
by RIPE NCC Document Announcement Service 17 Jun '02

17 Jun '02

New/Revised RIPE Document Announcement -------------------------------------- A set of new documents is available from the RIPE Document Store: IPv4 Address Allocation and Assignment Policies in the RIPE NCC Service Region (ripe-234) IPv4 First Allocation Request Form (ripe-235) Supporting Notes for the IPv4 First Allocation Request Form (ripe-236) New Values of the "status:" Attribute for Inetnum Objects (LIR-PARTITIONED) (ripe-239) IPv4 Additional Allocation Request Form (ripe-240) Mergers, Acquisitions, Takeovers and Closures of Organisations Operating an LIR (ripe-241) Autonomous System (AS) Number Assignment Policies and Procedures (ripe-245) Short content description ------------------------- This set of IPv4 policy documents replaces the now obsolete ripe-185 (European Internet Registry Policies and Procedures). Additionally, we have created specific forms for Local Internet Registries to request a first allocation and additional allocations. Accessing the RIPE document store --------------------------------- All documents are on-line at the following URLs: http://www.ripe.net/ripe/docs/ipv4-policies.html http://www.ripe.net/ripe/docs/first-allocation.html http://www.ripe.net/ripe/docs/first-allocation-support.html http://www.ripe.net/ripe/docs/lir-partitioned.html http://www.ripe.net/ripe/docs/add-allocation.html http://www.ripe.net/ripe/docs/mergers.html http://www.ripe.net/ripe/docs/asn-assignment.html The RIPE document store is also available via anonymous FTP to ftp.ripe.net, in the directory ripe/docs/. The URLs for the new documents on the FTP-server are: ftp://ftp.ripe.net/ripe/docs/ripe-234.ps PostScript version ftp://ftp.ripe.net/ripe/docs/ripe-234.txt plain text version ftp://ftp.ripe.net/ripe/docs/ripe-235.ps PostScript version ftp://ftp.ripe.net/ripe/docs/ripe-235.txt plain text version ftp://ftp.ripe.net/ripe/docs/ripe-236.ps PostScript version ftp://ftp.ripe.net/ripe/docs/ripe-236.txt plain text version ftp://ftp.ripe.net/ripe/docs/ripe-239.ps PostScript version ftp://ftp.ripe.net/ripe/docs/ripe-239.txt plain text version ftp://ftp.ripe.net/ripe/docs/ripe-240.ps PostScript version ftp://ftp.ripe.net/ripe/docs/ripe-240.txt plain text version ftp://ftp.ripe.net/ripe/docs/ripe-241.ps PostScript version ftp://ftp.ripe.net/ripe/docs/ripe-241.txt plain text version ftp://ftp.ripe.net/ripe/docs/ripe-245.ps PostScript version ftp://ftp.ripe.net/ripe/docs/ripe-245.txt plain text version Kind Regards, RIPE NCC Document Announcement Service

2 1

Concerns about billing procedures at RIPE NCC
by Axel Pawlik 14 Jun '02

14 Jun '02

Dear all, regarding today's concern about billing at the RIPE NCC, and the related procedures, I have spent some time this afternoon to look into the matter. What I have found gives not raise to concern about procedures, or the privacy of member's data at the RIPE NCC. It might be possible, though, to remove some slack from the timeline of the payment process. It is our goal to make administrative procedures as efficient and inobtrusive as possible. To assist us in this undertaking, please ensure that your billing data you send is as complete as possible. Should you have any questions or concerns in this aspect, do not hesitate to contact either me, or the RIPE NCC's controller, Jochem de Ruig (jochem(a)ripe.net) directly. kind regards, Axel Pawlik Managing Director, RIPE NCC

1 0

Am I the only one who can't pay their fees ?
by Peter Galbavy 14 Jun '02

14 Jun '02

I have now faxed my credit card payment form to RIPE on three ocassions to two different numbers and today I get my suspension notice. Am I the only one that appears to be at the sharp end of this potential incompetence or are other having problems with financially sensitive data / faxes going missing at RIPE ? I still think that the focus on non-core activities within RIPE is wrong, and these types of administrative problems only help reinforce my view. rgds, -- Peter Galbavy

3 7

RE: Am I the only one who can't pay their fees ?
by Sweeting, John 13 Jun '02

13 Jun '02

We are having the same problems. -----Original Message----- From: Peter Galbavy [mailto:peter.galbavy@knowtion.net] Sent: Thursday, June 13, 2002 11:26 AM To: lir-wg(a)ripe.net Subject: Am I the only one who can't pay their fees ? I have now faxed my credit card payment form to RIPE on three ocassions to two different numbers and today I get my suspension notice. Am I the only one that appears to be at the sharp end of this potential incompetence or are other having problems with financially sensitive data / faxes going missing at RIPE ? I still think that the focus on non-core activities within RIPE is wrong, and these types of administrative problems only help reinforce my view. rgds, -- Peter Galbavy

2 1

RE: [apnic-talk] Status field for inet6num objects
by Michael.Dillon＠radianz.com 13 Jun '02

13 Jun '02

>For me these two phrases, DELEGATED-TO-LIR and >ASSIGNED-TO-END-USER, hit the spot precisely! >excellent suggestion Guy! >Is it appropriate to request consideration of these terms as replacements >for ASSIGNED and ALLOCATED? Wouldn't it be a good idea to standardize the terminology with ARIN and others? In that case, the term LIR would be considered obscure and meaningless. Since all LIRs are service providers of some sort, either ISPs or an internal network service provider, I think that a standard terminology should try to use generic terms. That would mean either DELEGATED-TO-SVC-PROVIDER or DELEGATED-TO-NSP if you like acronyms (Network Service Provider). In any case, because the distinction between "allocated" and "assigned" has been unclear in the past and because there is a significant shift in terminology from "allocated" to "delegated" this change should be incorporated in an informational RFC. This document would help in clarifying that there is indeed a difference between the two states of an address block and would also help in promoting the use of this terminology amongst the community that deal with IP address delegations and assignments. DELEGATED-TO-NSP and ASSIGNED-TO-USER are two terms that would be clear worldwide. Michael Dillon Network Product Engineering Radianz

3 2

Re: [apnic-talk] Status field for inet6num objects
by Geoff Huston 13 Jun '02

13 Jun '02

>To clarify, the values that APNIC would prefer to use are: > >ALLOCATED PORTABLE >ALLOCATED NON-PORTABLE >ASSIGNED PORTABLE >ASSIGNED NON-PORTABLE > >As I mentioned before, these values would be consistent with those in >IPv4 (which take effect in August when the migration to version 3 of the >RIPE database is complete). > >Comments? I would be in favour of this clarity in the field regarding PORTABLE and NON_PORTABLE. However, the distinction between "ALLOCATED" and "ASSIGNED" is perhaps a bit subtle. regards, Geoff

6 5