- ipv6-wg - mailman.ripe.net

New Document available: RIPE-256
by RIPE NCC Document Announcement Service 05 Aug '02

05 Aug '02

New/Revised RIPE Document Announcement -------------------------------------- A revised/new document is available from the RIPE document store: "IPv6 Address Space Policy for Internet Exchange Points" Short content description ------------------------- Internet Exchange Points (IXPs) are used to exchange Internet traffic between different Internet Service Providers (ISPs). Many Exchange Point operators require address space for the peering mesh that is independent from any of the address space in use by member networks. Accessing the RIPE document store --------------------------------- You can access the RIPE documents in HTML format via WWW. "IPv6 Address Space Policy for Internet Exchange Points" is available at the following URL: http://www.ripe.net/docs/ripe-256.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-256.ps PostScript version ftp://ftp.ripe.net/ripe/docs/ripe-256.txt plain text version Kind Reagrds, Jeroen Bet Webmaster RIPE NCC

1 0

New Document available: RIPE-243
by RIPE NCC Document Announcement Service 05 Aug '02

05 Aug '02

New/Revised RIPE Document Announcement -------------------------------------- A revised/new document is available from the RIPE document store: "New Values of the "status:" Attribute for inet6num Objects". Short content description ------------------------- This document describes the new values of the "status:" attribute for inet6num objects and their impact on database operation. Accessing the RIPE document store --------------------------------- You can access the RIPE documents in HTML format via WWW. "New Values of the "status:" Attribute for inet6num Objects" is available from the WWW at the following URL: http://www.ripe.net/docs/new-value-status.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-243.ps PostScript version ftp://ftp.ripe.net/ripe/docs/ripe-243.txt plain text version Kind Regards, Jeroen Bet Webmaster RIPE NCC

1 0

New draft: "New Values of the 'status:' attribute for inet6num Objects"
by leo vegoda 25 Jul '02

25 Jul '02

Dear Colleagues, Thank you for the comments we have received on the draft document "New Values of the 'status:' attribute for inet6num Objects". We have revised it to incorporate the suggestions you have made. The meaning of the labels has been made clearer, in line with the comments received. ALLOCATED-BY-RIR - For allocations made by an RIR to an LIR. ALLOCATED-BY-LIR - For allocations made by an LIR or an LIR's downstream customer to another downstream organisation. ASSIGNED - For assignments made to End User sites The new draft is available from our web site at: <http://www.ripe.net/ripe/draft-documents/new-value-status.html> We would welcome comments on this new draft until Thursday, 1 August 2002. All comments and suggestions should be sent to <lir-wg(a)ripe.net>. Regards, -- leo vegoda RIPE NCC, Registration Services Assistant Manager

1 0

RE: [lir-wg] Discussion Summary: Status field for inet6num object s
by Guy Davies 08 Jul '02

08 Jul '02

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I would prefer RIR-LIR-ALLOCATED, LIR-SUB-ALLOCATED and LIR-USER-ASSIGNED (or similar) if we must keep ALLOCATED and ASSIGNED in the descriptions. I don't think that it is immediately clear from the proposals below whether LIR-ALLOCATED is allocated by an LIR or to an LIR. Regards, Guy > -----Original Message----- > From: Gert Doering [mailto:gert@space.net] > Sent: Monday, July 08, 2002 1:42 PM > To: leo vegoda > Cc: ipv6-wg(a)ripe.net; lir-wg(a)ripe.net; db-wg(a)ripe.net; > sig-db(a)apnic.net; > policy-db(a)apnic.net; apnic-talk(a)apnic.net > Subject: Re: [lir-wg] Discussion Summary: Status field for inet6num > objects > > > Hi, > > On Mon, Jul 01, 2002 at 06:21:24PM +0200, leo vegoda wrote: > > The RIPE NCC needs to implement a new status attribute for the > > inet6num object to reflect the new policy agreed by the RIPE, > > ARIN and APNIC communities. > > > > The RIPE NCC suggested the following new status attributes for > > the inet6num objects: > > > > - RIR-ALLOCATED > > (For allocations made by an RIR to an LIR) > > > > - LIR-ALLOCATED > > (For allocations made by an LIR or an LIR's downstream > > customer > > to another downstream organisation) > > > > - ASSIGNED > > (For assignments made to End User sites) > > I haven't seen any replies to this so far. > > I want to express that I like this proposal. It doesn't introduce > any new and yet-undefined terms, but makes clear what the status of > a given network is. > > Gert Doering > -- NetMaster > -- > Total number of prefixes smaller than registry allocations: > 45809 (45931) > > SpaceNet AG Mail: netmaster(a)Space.Net > Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0 > 80807 Muenchen Fax : +49-89-32356-299 > -----BEGIN PGP SIGNATURE----- Version: PGP 7.0.1 iQA/AwUBPSmLLo3dwu/Ss2PCEQIJdQCeOKDqqTLKCuB+o3pWMj/XJ41QJMQAnROW EWRBiRI4rPpF9DRbhrxYcK0S =Rab7 -----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.

1 0

Status field for inet6num objects
by Joao Luis Silva Damas 08 Jul '02

08 Jul '02

[** Mail posted to both APNIC and RIPE lists in the hopes of trying to find a solution suitable for all users of RIPE or RIPE-derived software **] Dear all, the inet6num, like the inetnum object, has a field named "status" which stores some information about the nature or position of a block of addresses in the delegation chain, from the RIR through to the end user. Currently, the status field for inet6num object is generated by the Database software based on the size of the address block and its possible values are: o TLA o SubTLA o NLA o SLA This notation has been deprecated and it is time to adapt the database. Discussions on this matter have identified the usefulness of having the capability to distinguish between allocations made by the RIR, allocations made by an LIR or their customers and assignments to end users. As such, we propose to modify the "status" attribute of the inet6num object to be: a) not-generated. This means users must assign a value to the status attribute when creating the object, just as in the inetnum object b) have the following possible values: RIR-allocated LIR-allocated Assigned to be used according to the following set of rules: The RIR-allocated status can only be used in objects representing allocations created directly by the RIR. The LIR-allocated status can be used by LIRs and their customers to represent blocks of addresses that are not assigned to specific end users. There can be several levels of objects with this status. The Assigned status must be used in objects representing assignments to end users (households, companies, enterprises, etc) We hope that with this modification the information in the Database will more accurately describe the registration of IPv6 address space. A possible transition to the new values could be: 1) RIRs modify status fields for allocations 2) Any new objects and modifications to existing ones must have a value for the status field corresponding to the ones described above. Otherwise the update will fail. 3) RIRs contact LIRs to have the status of assignments and sub-allocations updated. Best regards, Joao Damas RIPE NCC

6 8

Reminder: filters have to permit /32s now
by Gert Doering 06 Jul '02

06 Jul '02

Hi, for those of you that are doing strict IPv6 prefix filtering: please adapt your filters to permit /32s and /35s from 2001::/16. RIPE is now allocating /32s, and upgrading existing /35s to /32 - and I am right now observing some IPv6 connectivity issues that could be explained by "our 2001:608::/32 (active since yesterday) is not being accepted by some ASes". Gert Doering -- NetMaster -- Total number of prefixes smaller than registry allocations: 45809 (45931) SpaceNet AG Mail: netmaster(a)Space.Net Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0 80807 Muenchen Fax : +49-89-32356-299

1 0

New IPv6 policy implemented on 1 July 2002
by Paul Rendek 01 Jul '02

01 Jul '02

Dear Colleagues, The RIPE NCC is pleased to announce the implementation of the new IPv6 policy effective 1 July 2002. This IPv6 policy was accepted by consensus at RIPE 42 and is common to all Regional Internet Registry communities - APNIC, ARIN, and the RIPE NCC. The new policy replaces the provisional IPv6 policy launched in 1999. The IPv6 Policy documentation is available from the RIPE document store at: http://www.ripe.net/ripe/docs/internet-registries.html The current set of IPv6 documents are: - IPv6 Address Allocation and Assignment Policy - Initial IPv6 Allocation Request Form in the RIPE NCC Service Region - Supporting Notes for the Initial IPv6 Allocation Request Form in the RIPE NCC Service Region - IPv6 End User Site Assignment Request Form in the RIPE NCC Service Region - Supporting Notes for the IPv6 End User Site Assignment Request Form in the RIPE NCC Service Region Key points of the new IPv6 policy you should be aware of: - The minimum allocation size is /32; - LIRs currently holding a /35 have the option of expanding their allocation to a /32 on request; - In 2002, no additional fees are charged for IPv6 address space in the RIPE NCC service region. The RIPE NCC IPv6 web pages can be found at: http://www.ripe.net/IPv6/ Regards, Paul Rendek Communications Manager RIPE NCC

1 0

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

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.

8 8

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

2 1