- lir-wg - mailman.ripe.net

Re: [db-wg] Re: [lir-wg] Re: ERX of v4 address space proposal
by Jim Fleming 21 Nov '02

21 Nov '02

----- Original Message ----- From: "Kandra Nygårds" <kandra(a)foxette.net> To: "Jim Fleming" <JimFleming(a)Ameritech.Net> Cc: <lir-wg(a)ripe.net> Sent: Thursday, November 21, 2002 12:56 PM Subject: Re: [db-wg] Re: [lir-wg] Re: ERX of v4 address space proposal > From: "Jim Fleming" <JimFleming(a)ameritech.net> > > > From: "Andrei Robachevsky" <andrei(a)ripe.net> > > > Our current data shows that around 753 networks will go to APNIC, 9072 > > > stay with ARIN, 92 will go to LACNIC and 3176 to RIPE NCC. > > > > Note, LACNIC is less than 30 days old, and it will get 92 /8s ? *each* > valued at $1 to $2 billion dollars ? > > No kidding! Not to mention the 9072 /8s that ARIN keeps, and the 3176 /8s > that goes to RIPE. Jim, quick! Buy ARIN stock before it's too late! Or even > better, send your money to me and I'll buy the stock for you! > > When you add the 11 additional bits of addressing to the existing IPv4 header, you get 2,048 32-bit address spaces in both the AM and FM Internets. That is a lot of /8s, but ARIN and RIPE only deal with TOS=0,0x0*,0x*0. http://www.iana.org/assignments/ipv4-address-space 128-bit DNS AAAA Record Flag Day Formats 2002:[IPv4]:[SDLL.OFFF.FFFF.TTTT]:[64-bit IPv8 or IPv16 Persistent Address] [YMDD]:[IPv4]:[SDLL.OFFF.FFFF.TTTT]:[64-bit IPv8 or IPv16 Persistent Address] 1-bit to set the Reserved/Spare ("AM/FM") bit in Fragment Offset [S] 1-bit to set the Don't Fragment (DF) bit [D] 2-bits to select 1 of 4 common TTL values (255, 128, 32, 8) [LL] 1-bit for Options Control [O] 7-bits to set the Identification Field(dst) [FFFFFFF] 4-bits to set the TOS(dst) Field [TTTT] Default SDLL.OFFF.FFFF.TTTT = 0000.0000.0000.0000 FFF.FFFF.TTTT = GGG.SSSS.SSSS http://www.ntia.doc.gov/ntiahome/domainname/130dftmail/unir.txt IPv8 0QQQQGGGSSSSSSSS[32-bits][Port] IPv16 0QQQQGGGSSSSSSSS[32-bits][Port] 1WWWWWWWSSSSSSSS[32-bits][Port] === Jim Fleming 128-bit DNS is closer than you think... IPv16...COM...NET...AM...NZ...AE...FM...NR...SZ...AC...DE...FI...JM...NO...PR...ST...UZ http://ipv8.dyndns.tv http://ipv8.dyns.cx http://ipv8.no-ip.com http://ipv8.no-ip.biz http://ipv8.no-ip.info http://ipv8.myip.us http://ipv8.dyn.ee

1 0

What /8s have been transferred to LACNIC ?
by Jim Fleming 20 Nov '02

20 Nov '02

What /8s have been transferred to LACNIC ? http://www.iana.org/assignments/ipv4-address-space How much did LACNIC pay for them ? http://lacnic.net/en/transition.html http://lacnic.net/cgi-bin/meeting/list.cgi?lang=en Andrew McLaughlin ICANN US IVAN MOURA CAMPOS ICANN BR IVAN MOURA CAMPOS ICANN BR John Crain ICANN US Raymond Plzak ARIN US Paul Wilson APNIC AU Leslie Nobile ARIN US ===== Jim Fleming 128-bit DNS is closer than you think... IPv16...NET...COM...AM...NZ...AE...FM...NR...SZ...AC...DE...FI...JM...NO...PR...ST...UZ http://ipv8.dyndns.tv http://ipv8.dyns.cx http://ipv8.no-ip.com http://ipv8.no-ip.biz http://ipv8.no-ip.info http://ipv8.myip.us http://ipv8.dyn.ee http://ipv8.community.net.au

1 0

Routing Workshop - free places available
by Paul Rendek 19 Nov '02

19 Nov '02

CALL FOR APPLICATIONS Routing Workshop, Amsterdam, The Netherlands, 3-7 February 2003 Dear Colleagues, Cisco Systems will provide a Routing Workshop for RIPE NCC staff on 3-7 February 2003 in Amsterdam, The Netherlands. This is a call for applications for 12 places still available in the workshop. This workshop will be provided free of charge and includes lunches. PLEASE NOTE: Travel and accommodation are not provided or reimbursed. Who should Attend: The target audience for this course is persons in the ISP community with a basic familiarity of Cisco Systems equipment. This is a technical workshop and most suitable for those persons who are now or will soon be building or operating a wide area TCP/IP base Internet Service Provider (ISP) network or Internet eXchange Point (IXP) with international and/or multi-provider connectivity. Prerequisites: Cisco IOS fundamentals; user level UNIX and possibly some system administration and; some use of network design, preferably TCP/IP based. * Preference for this course will be given to those individuals from the following regions (i.e. Central Europe, Central Asia, Africa and The Middle East) Cisco Systems will select 12 participants to attend the tutorial based on the information provided in the application form enclosed below. The Workshop scope, location and important dates are also enclosed. Regards, Paul Rendek RIPE NCC WORKSHOP SCOPE: --------------- - Techniques for design, set-up, and operation of a metropolitan, regional or national ISP backbone network. This includes advanced OSPF, BGP4 and policy based routing. - IOS Essentials every ISP should be doing. The hidden secrets that all key NSPs have been using for years but not telling anyone (ie: competitive advantage. - Techniques for multiple connections to the Internet (multihoming), including connections to IXPs, NSP and transoceanic Internet links. - Techniques for the design, set-up and operation of a metropolitan, regional or national IXPs - Techniques to achieve optimal performance and configuration from a Cisco backbone router. This includes routing scalability, network design and configuration techniques. - Examples from a case study from successful ISPs who are making use of many of the workshop techniques. COURSE LOCATION: --------------- The course will take place at the RIPE NCC offices in Amsterdam, The Netherlands. The instructor for the Workshop will be Philip Smith. IMPORTANT DATES: --------------- * The deadline for application submissions: 3 December 2002 * Acceptance notification to selected candidates: 11 December 2002 * Routing Workshop: 3-7 February 2003 ====== ROUTING WORKSHOP - APPLICATION FORM * Please submit your application form by email to: <routing-workshop(a)ripe.net> with the following text as the subject: Routing Workshop First Name: Last Name: Nationality: Contact Information: - postal address: - Tel/Fax number: - email address: CV detailing ISP experience [max 200 words]: ======

1 0

0:0 ARPA.AE and IN-ADDR.ARPA.AE
by Jim Fleming 15 Nov '02

15 Nov '02

It is still not clear who operates 0:0 .ARPA. ARIN, RIPE and APNIC appear to want to rotate that. http://www.iana.org/assignments/ipv4-address-space TLDs that begin with the letters A-E can be managed under .AE to balance the server load That would result in ARPA.AE and IN-ADDR.ARPA.AE > > > http://www.uaenic.ae > > > AE > > > http://www.dot.fm > > > FM > > > http://www.cenpac.net.nr/dns/index.html > > > NR > > > http://www.africaonline.co.sz/domreg/ > > > SZ > > > ===== Jim Fleming 128-bit DNS is closer than you think... AE...FM...NR...SZ http://ipv8.dyndns.tv http://ipv8.dyns.cx http://ipv8.no-ip.com http://ipv8.no-ip.biz http://ipv8.no-ip.info http://ipv8.myip.us http://ipv8.dyn.ee http://ipv8.community.net.au

1 0

Re: [ipv6-wg@ripe.net] IPv6 TLAs for mobile operators
by leo vegoda 15 Nov '02

15 Nov '02

[Note: <lir-wg(a)ripe.net> cc'd as this relates to policy] Andreas, On Thu, Oct 31, 2002 at 06:31:06PM +0100, Andreas.Schmid1(a)swisscom.com wrote: Re: RE: [ipv6-wg(a)ripe.net] IPv6 TLAs for mobile operators [...] > RFC3314 says on page 14: > "Because multiple IPv6 hosts may attach through a 3GPP handset, the IPv6 > WG recommends that one or more /64 prefixes should be assigned to each > primary PDP context." > > But I really don't want to concentrate on that discussion. I want to > know if RIPE NCC accepts IPv6 TLA requests from mobile operators only > having GPRS/UMTS/WLAN customers - and therefore not providing > connectivity to organisations with a /48. > -> if anybody can clarify this, I would be very happy! The RIPE NCC implements the RIPE community's policy as described in the IPv6 Address Allocation and Assignment Policy. The policy was agreed at the RIPE 42 meeting in May. An LIR submitting a request for an initial IPv6 allocation will need to meet all four requirements specified in the policy. <http://www.ripe.net/ripe/docs/ipv6policy.html#initial_criteria> Kind regards, -- leo vegoda RIPE NCC Registration Services

6 5

Re: [lir-wg] ERX of v4 address space proposal
by Wilfried Woeber, UniVie/ACOnet 13 Nov '02

13 Nov '02

--On 5. november 2002 10:00 +0100 Berislav Todorovic <beri(a)eurorings.net> wrote: > On Mon, 4 Nov 2002, Andrei Robachevsky wrote: > >>> Please find attached the proposal for the ERX of IPv4 address space for >>> your review. > > Most legacy IPv4 address space was assigned directly by InterNIC. Should > we read that all those addresses will have "PI" status? Given the fact that those address blocks were distributed before the RIR and NIR / LIR structure was devised, those blocks are _administratively_ PI, or maybe "unspecified" which I consider equivalent (much like the very early LIR blocks :-) Technically, and wirth regard to services rendered by LIRs and RIRs to the holders of those blocks, I'd venture to guess that they should be offered a chance to "opt-in" to an existing LIR or ISP environment. > Secondly, who will provide reverse delegation and how can users of these > blocks affect reverse delegation changes? I guess auto-inaddr will not > work since it requires a valid RegID. Actually this is one of the aspects that I would have liked to tackle in the ERX-TF, unfortunately it looks like I might be too late to have those ideas discussed and considered, due to overload on my end for a while. One of the things we should have learned from the ASN relocation is that those parties are not in touch with the most recent administartive procedures imposed by the RIR (and why should they?), and they simply get mixed up when they suddenly receive messages from the NCC :-( Wilfried.

1 0

Fw: Project to Define a cc-IANA...for "substantial ccTLDs"
by Jim Fleming 12 Nov '02

12 Nov '02

Sent: Tuesday, November 12, 2002 2:08 PM Subject: Project to Define a cc-IANA...for "substantial ccTLDs" > http://www.wwtld.org/~shanghai/cc-IANA.html > Project to Define a cc-IANA > ==== > > "Critically, the success of this project will be measured by the number of “substantial” ccTLDs" > ... > > "The US Department of Commerce, from its side, needs to have these same assurances and the firm acceptance of the other respective > governments that they should accept these entries as authoritative." > > === > > http://www.caida.org/analysis/geopolitical/bgp2country/data/source_add_pre_… > > US 704056771 (50.357%) 65945 (58.259%) 5899 (53.317%) > AU 14416063 ( 1.031%) 5894 ( 5.207%) 213 ( 1.925%) > CA 26436124 ( 1.891%) 5313 ( 4.694%) 239 ( 2.160%) > ZA 6533529 ( 0.467%) 2703 ( 2.388%) 35 ( 0.316%) > ?? 306555022 (21.926%) 2547 ( 2.250%) 276 ( 2.495%) <<<<<<<< OZ or NZ ? > DE 51874361 ( 3.710%) 2410 ( 2.129%) 402 ( 3.633%) > JP 36287488 ( 2.595%) 1959 ( 1.731%) 215 ( 1.943%) > KR 18529780 ( 1.325%) 1859 ( 1.642%) 309 ( 2.793%) > UK 40459542 ( 2.894%) 1691 ( 1.494%) 261 ( 2.359%) > SE 9381784 ( 0.671%) 1162 ( 1.027%) 66 ( 0.597%) > FR 28506472 ( 2.039%) 1137 ( 1.004%) 200 ( 1.808%) > HK 2799696 ( 0.200%) 1086 ( 0.959%) 140 ( 1.265%) > MX 4643076 ( 0.332%) 1062 ( 0.938%) 75 ( 0.678%) > ===== > > US...AU...CA...ZA...OZ or NZ...DE...JP...KR...UK...SE...FR...HK...MX > > Will this be capped at 16 ?...if the total TLDs allowed are 64 ?...25% to the so-called ccTLDs ? > > 25% to gTLDs > > 25% to sTLDs (Staff "sponsored" TLDs) > > 25% to iTLDs (I* society) > > > Jim Fleming > 128-bit DNS is closer than you think... > COM...DE...NET...ORG...INFO...BIZ...US...ONLINE > http://ipv8.dyndns.tv > http://ipv8.dyns.cx > http://ipv8.no-ip.com > http://ipv8.no-ip.biz > http://ipv8.no-ip.info > http://ipv8.myip.us > http://ipv8.dyn.ee > http://ipv8.community.net.au > > > Note..... > > OZ came from the old style two-drawer file cabinets with the "top" being A-M and the "bottom" being O-Z > > If the "top" is going to be A-M, then the "bottom" will be N-Z, as in NZ. > > So, we have TLDs and BLDs, Top Level Domains and Bottom Level Domains. > Correction....OZ came from the old style two-drawer file cabinets with the "top" being A-N and the "bottom" being O-Z I know .AN wants to be the "top" and .OZ wants to be the "bottom". http://www.iana.org/root-whois/an.htm Will that be decided in Amsterdam ? AN and OZ or AM and NZ

1 0

Maintenance work on RIPE Whois Server 13.11.2002
by RIPE Database Administration 12 Nov '02

12 Nov '02

[Apologies for duplicate messages] Dear Colleagues, Tomorrow, 13 November 2002 Wednesday, we plan maintenance work for the whois server. As part of the maintenance work the server software will be upgraded to improve server query performance. We plan to start around 06:30 UTC and finish the work till 10:30 UTC. During this maintenance period, - mail updates will be queued and automatically processed after the maintenance work. - webupdates and syncupdates will not be possible. - queries will be answered by our secondary server. We apologise for any inconvenience. Please contact <ripe-dbm(a)ripe.net> for any questions/ comments. Best Regards, Engin Gunduz RIPE NCC Database Group

1 0

Fw: 3:127 EU
by Jim Fleming 08 Nov '02

08 Nov '02

Sent: Friday, November 08, 2002 11:51 AM Subject: 3:127 EU > If the number of "slots" in the 32-bit legacy root servers is going to be so limited, because of bogus claims > about load and attacks and stability and security, then, will all of the TLDs such as DE and FR end up > under .EU or under .INT ? or under .EU.INT ? Will all of the people have to re-register ? > > http://europa.eu.int/index_en.htm > http://europa.eu.int/abc/symbols/index_en.htm > .ES.EU > .DA.EU > .DE.EU > .EL.EU > .EN.EU > .FR.EU > .IT.EU > .NL.EU > .PT.EU > .FI.EU > .SV.EU > === > > > Jim Fleming > 128-bit DNS is closer than you think... > 3:127 EU > COM...DE...NET...ORG...INFO...BIZ...US...ONLINE > http://ipv8.dyndns.tv > http://ipv8.dyns.cx > http://ipv8.no-ip.com > http://ipv8.no-ip.biz > http://ipv8.no-ip.info > http://ipv8.myip.us > http://ipv8.dyn.ee > http://ipv8.community.net.au > >

1 0

New Document available: RIPE-264
by RIPE NCC Document Announcement Service 08 Nov '02

08 Nov '02

New RIPE Document Announcement -------------------------------------- A new document is available from the RIPE document store. Ref: ripe-264 Title: Smallest RIPE NCC Allocation / Assignment Sizes Author: Joao Luis Silva Damas, Leo Vegoda Date: 8 November 2002 Format: PS=10836 TXT=2169 Obsoletes: ripe-222, ripe-242, ripe-259 Obsoleted by: Updates: Updated by: Short content description ------------------------- The "Smallest RIPE NCC Allocation / Assignment Sizes" document contains the size of the minimum and default allocations made by the RIPE NCC to Local Internet Registries (LIRs) and End Users from IPv4 and IPv6 CIDR blocks allocated to the RIPE NCC by the Internet Assigned Numbers Authority (IANA). Accessing the RIPE document store --------------------------------- You can access the RIPE documents in HTML format via our website at the following URL: http://www.ripe.net/ripe/docs/smallest-alloc-sizes.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-264.ps PostScript version ftp://ftp.ripe.net/ripe/docs/ripe-264.txt plain text version

1 0