- address-policy-wg - mailman.ripe.net

Proposed Open Letter to ICANN and Related Documents
by Axel Pawlik 13 Oct '03

13 Oct '03

Dear Colleagues, The Regional Internet Registries (RIR) have published three (3) documents: a. Proposed Open Letter to ICANN from the Regional Internet Registries b. Proposed Agreement between the RIRs to create the Number Resource Organization c. Proposed Agreement between the RIRs (acting through the NRO) and ICANN concerning the Address Supporting Organization These documents are available on a single web page at: http://www.ripe.net/ripencc/about/regional/draft-public-comment.html In order to ensure that RIR members and address communities in every region have the opportunity to comment, the Board of the RIRs have requested that RIRs post the documents for a period of 30 days. The comment period closes at midnight (UTC) on the 22nd October 2003. Each of the RIR Boards will consider the comments as they are received, and each RIR Board intends to make a decision whether to adopt these documents following this comment period. If these documents are adopted by all the RIR Boards, it is the present intention to formally pass the following open letter to ICANN on the 24th of October. On the same date the Boards of the RIRs currently intend to direct their CEOs to sign the MoU concerning the establishment of the Number Resource Organization. All comments should be addressed to: nro-comments(a)apnic.net. The comments will be passed to all the Boards of the RIRs, and will also be published on the web site http://www.apnic.net/nro-comments. Any dialogue that arises from such comments will also be published on this site. Subscription information for the nro-comments mailing list is available at: http://mailman.apnic.net/mailman/listinfo/nro-comments All postings to this mail address (nro-comments(a)apnic.net) are public, and will be published at the following URL: http://www.apnic.net/nro-comments kind regards, Axel Pawlik Managing Director RIPE NCC

2 1

RIPE NCC Regional Meeting, Middle East, Dubai, 7-9 December 2003
by Membership Liason Officer 08 Oct '03

08 Oct '03

Dear Colleagues, The RIPE NCC is pleased to announce the RIPE NCC Regional Meeting, Middle East, to be held 7-9 December 2003 at the Metropolitan Palace Hotel, Dubai, U.A.E. Registration for the Regional Meeting opens 8 October 2003. Attendance to the RIPE NCC Regional Meeting is open and free of charge. However, attendees are responsible to cover their own travel and accommodation costs. To register, please see: http://www.ripe.net/cgi-bin/dubai-reg The RIPE NCC Regional Meeting will focus on Internet resource allocation and Internet management issues including: - How to participate in and influence IP address management policy-making; - The industry self-regulatory open structures and processes used by the RIPE NCC and the global Internet community; - Are we running out of IPv4 address space? - Root name server operations: who is involved? - Domain Name management on the Internet; - The internationalisation of Domain Names. The Regional Meeting draft agenda can be found at: http://www.ripe.net/ripencc/regional-meetings/dubai-2003/plan.html RIPE and the RIPE NCC will explain their roles in the administration of the Internet infrastructure as well as specific aspects in managing and operating the Internet infrastructure. The discussions will be directly related to the particular needs and concerns surrounding these issues in the Middle East region. The current meeting agenda reflects our intentions. However, it requires active participation from the local community to discuss specific issues of the region. The RIPE NCC has reserved several presentation opportunities for those with local knowledge of Internet management and operational issues affecting the Middle East. If your organisation wishes to provide a presentation or suggest a relevant topic, please send your proposal by e-mail to: <contact(a)ripe.net> The RIPE NCC is one of four Regional Internet Registries (RIRs) that provide Internet resource allocation, registration services and co-ordination activities that support the operation of the Internet globally. The RIPE NCC is an independent, not-for-profit membership organisation that provides services to members in its service region currently covering Europe, the Middle East, Central Asia and African countries located north of the equator. Any further questions about the RIPE NCC Regional Meeting, Middle East can be sent directly to: <contact(a)ripe.net>. Regards, Sabrina Wilmot Membership Liaison Officer RIPE NCC

1 0

Revised Draft Document for review: "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region"
by Dominic Spratley 05 Oct '03

05 Oct '03

Dear Colleagues, The RIPE NCC is pleased to announce an updated draft of the revised RIPE IPv4 policy document, "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region" (currently ripe-234). The major change from the draft published on 21st July is that the existing "status:" attribute values are kept for inetnum objects with the addition of a new value for sub-allocations. The updated draft can be downloaded from the "Drafts" section in the RIPE Document Store, found at: <http://www.ripe.net/ripe/draft-documents/> The major updates to the current policy text in this draft IPv4 policy document are: - Recent policy changes have been incorporated, including the policy allowing assignments for Internet experiments and the sub-allocation policy. - Wording has been improved to make it easier to read. - The explanation of how to use the database has been removed as a separate "RIPE Database User Manual: Getting Started" was published in September last year. - The document now incorporates the text from "Provider Independent vs Provider Aggregatable Address Space" (ripe-127). If the community accepts this document it will replace the existing IPv4 Policy document (ripe-234) and the "Provider Independent vs Provider Aggregatable Address Space" document (ripe-127). Feedback on this document should be sent to the address-policy-wg@localhost mailing list for a period of two weeks. This review period will end on TWO WEEKS FROM ANNOUNCEMENT. Dominic Spratley Registration Services Manager RIPE NCC

2 1

RIPE 46 Meeting Report
by Nick Hyrka 02 Oct '03

02 Oct '03

(Apologies for duplicate mails.) RIPE 46 Meeting Report Dear Colleagues: The RIPE 46 Meeting was held from 1 - 5 September 2003 at the Grand Hotel Krasnapolsky, Amsterdam, the Netherlands. There were a total of 307 attendees comprised of the RIPE NCC membership, the RIPE community and government representatives. Attendees also included representatives from APNIC, ARIN, AfriNIC, LACNIC and ICANN. HIGHLIGHTS ========== Highlights of RIPE 46 included the open discussion on the services of the RIPE NCC during the first session of the RIPE NCC Services Working Group; a presentation on current RIPE NCC services and plans for 2004 by Axel Pawlik, Managing Director, RIPE NCC; an AfriNIC update; and an update on the changes to Test Traffic Measurement. The European Operators Forum (EOF) featured a full-day tutorial on Voice over Internet Protocol (VoIP) and ENUM that included an overview of current technologies and a focus on practical deployment aspects such as gateways, security, provisioning and use of the new ENUM standards. Geoff Huston, Telstra, gave a presentation on IPv4 Address Lifetime Expectancy. The RIPE NCC would like to thank SURFnet, BIT, FLAG Telecom and KPN EuroRings for the support they provided to the meeting. SUMMARY ======== ADDRESS POLICY ============== - Hans Petter Holen, Chair, requested community involvement to help revise ripe-152 ("Charging by Local Internet Registries") if necessary. - The RIPE NCC will resubmit the IPv4 policy document for community review. - There was a discussion on PI/PA issues and whether the distinction is still valid. - It was agreed that a more formal process was needed for the policy development process. Address Policy Working Group presentations can be viewed at: http://www.ripe.net/ripe/meetings/ripe-46/presentations/#ap DATABASE ======== - Wilfried Woeber, Chair, will co-ordinate with the RIPE NCC to prepare a document summarising the basic assumptions about the use of the RIPE Database. - "status:" attribute values will change. Current efforts aim at consistency between the RIRs and having easy to understand values. - The organisation object proposal received positive feedback from the working group, with suggestions for other features. - The RIPE NCC will implement X.509 authentication before the next RIPE Meeting. Database Working Group presentations can be viewed at: http://www.ripe.net/ripe/meetings/ripe-46/presentations/#db TEST TRAFFIC MEASUREMENTS (TTM) ========================= - As of 1/1/2004 changes will be made to the TTM service contract: Fees will be lowered, all data will be made public with lightweight Acceptable Use Policy (AUP). - Bandwidth measurements: tests showed that results are not conclusive enough so the TTM service will wait before delivering this new product. TTM Working Group presentations can be viewed at: http://www.ripe.net/ripe/meetings/ripe-46/presentations/#tt ANTI-SPAM ========= - Rodney Tillotson, Chair, will post a proposal to the Anti-Spam mailing list regarding methods to improve finding abuse contacts in the RIPE Database. Anti-Spam Working Group presentations can be viewed at: http://www.ripe.net/ripe/meetings/ripe-46/presentations/#anti-spam IPv6 === - The 6BONE phase-out was discussed. The next milestone will be 01/01/2004 when new allocations stop. - Discussion on the separation of the identifier and locater functions of IP addresses in regards to IPv6 multihoming. IPv6 Working Group presentations can be viewed at: http://www.ripe.net/ripe/meetings/ripe-46/presentations/#ipv6 TECHSEC ======== - Community feedback was requested on the requirements needed to secure large scale IP infrastructure especially around CLI interface requirements. - The RIPE NCC presented a report on DNSSec status, DISI achievements since RIPE 45 and the impact of signing on zone size. - George Jones, Mitre, gave a presentation on operational security requirements including the history and current status of the requirements, related work, next steps and milestones. - Baiba Kaskina, TERENA, gave a presentation on Euro CSIRT developments that included details on the CSIRT Task Force, the countries involved, the projects and deliverables. - NLNetLab presented an update on Fonkey and PKI-related developments in IETF. TechSec Working Group presentations can be viewed at: http://www.ripe.net/ripe/meetings/ripe-46/presentations/#techsec EIX == - Support was expressed for aligning and harmonising IPv6 address space policy regarding IXPs with other RIRs and existing IPv4 policies. - Reports were presented by 11 European IXPs in Europe that showed a trend of steady growth, use of GE instead of FE and wide deployment of IPv6. - Discussion of the Inter-Provider Traffic Analyzer that uses past data and statistical calculations to detect anomalies in traffic patterns. - EIX presentations were given on the anycast deployments of the "F" and "K" root servers by ISC and the RIPE NCC. EIX Working Group presentations can be viewed at: http://www.ripe.net/ripe/meetings/ripe-46/presentations/#eix DN* === - From the merging of the former DNS Working Group and DNR Forum it was concluded that one working group is sufficient to deal with everything related to Domain Names. A new name/charter will be discussed on the mailing list. - Jaap Akkerhuis, DN* Co-Chair, will organise a "DNS Related Issues" document. - Peter Koch, DN* Co-Chair, talked about how firewall vendors could make mistakes handling DNS communication issues. DN* Working Group presentations can be viewed at: http://www.ripe.net/ripe/meetings/ripe-46/presentations/#dn RIPE NCC SERVICES ================ - Axel Pawlik noted that the RIPE NCC will present more details in next year's RIPE NCC budget. - There were comments on the current RIPE NCC services, whether they benefit the entire community and whether a 'pay per service' system could be an option. - There was discussion about the need for a more transparent evaluation of RIPE NCC activities and how they benefit the community. RIPE NCC Services Working Group presentations can be viewed at: http://www.ripe.net/ripe/meetings/ripe-46/presentations/#ncc TUTORIALS ========= - The RIPE NCC staff presented the RIPE NCC IP Request Tutorial. It explained address space assignment and allocation procedures in the RIPE NCC region: http://www.ripe.net/ripe/meetings/ripe-46/tutorials/ip-request/ - A full-day tutorial on VoIP and ENUM was presented during the European Operators Forum (EOF). For more information about the EOF at RIPE 46 see: http://www.ripe.net/ripe/meetings/ripe-46/eof.html RIPE MEETING WEBCASTING ======================= - The third phase of RIPE Meeting webcasting trials was held at RIPE 46. Recordings of certain sessions from RIPE 46, including the Plenary, have been archived and can be accessed at: http://www.ripe.net/ripe/meetings/ripe-46/webcast.html HOSTMASTER CONSULTATION CENTRE (HCC) ==================================== - The RIPE NCC Hostmaster Consultation Centre was open at RIPE 46, allowing RIPE NCC Members to discuss issues relating to their business directly with RIPE NCC Hostmasters. Later consultation hours, as introduced at RIPE 44, were continued. "MEET & GREET" =============== - The RIPE NCC's "Meet & Greet" was available for first-time RIPE Meeting attendees at RIPE 46. "Meet & Greet" introduces newcomers to the meetings, to key attendees of the RIPE community and to social events throughout the week. More information can be obtained by contacting the RIPE NCC's Pepa Tejedor Carnicero at <meet-greet(a)ripe.net>. RIPE 46 REFERENCE PAGE ====================== - A complete list of RIPE 46 sessions, tutorials and presentations can be found at: http://www.ripe.net/ripe/meetings/ripe-46/index.html RIPE NCC GENERAL MEETING ======================= - The RIPE NCC General Meeting 2003 was held Friday, 5 September 2003, adjacent to the RIPE 46 Meeting, at the Hotel Krasnapolsky in Amsterdam. For the highlights from the RIPE NCC General Meeting 2003, please see: http://www.ripe.net/ripencc/about/gm/gm2003/highlights.html RIPE 47 ====== - RIPE 47 will be held in Amsterdam, the Netherlands, from 26 - 30 January 2004. Information on RIPE 47 will soon be made available at: http://www.ripe.net/ripe/meetings/ripe-47/ NEW LOCAL INTERNET REGISTRIES (LlRs) - PLEASE NOTE LIRs who signed up after 1 January 2002 are entitled to two (2) free tickets to attend the next RIPE Meeting. The tickets cover the meeting fee only and do not apply to the RIPE dinner, travel or hotel accommodation. More information on the new LIR tickets can be found at: http://www.ripe.net/ripe/meetings/new-lir.html For more information, contact <meeting(a)ripe.net>. END

1 0

Re: [address-policy-wg] Re: [ncc-services-wg] Request Forms: upda ted and available on LIR Portal
by Kinder, Klaus 02 Oct '03

02 Oct '03

Hi, Ludger Bornhorst is on vacation but we have discussed this matter before he send this mail. Here two notes from my point of view: you wrote: The RIR->LIR level has the AW to express a given level of trust. I quite agree with you: You could use policies in a narrow interpretation or in a scope of interpretation in addition with your know how in cases of ip-address management, both is possible and essential. But you couldn't find this scope in ripe-283 e.g. #[EQUIPMENT DESCRIPTION]#, I think that's the problem. Or is this scope in addition to your AW an unwritten policy? you wrote: please don't feed the buerocracy. I can assure you that's not our target. From our point of view policies should give all parties, here the LIR's, a general Framework and not a straitjacket. mit freundlichen Grüßen/with best regards Klaus Kinder _________________________________________ Deutsche Telekom T-Com Headquarters Network Information Center Local Internet Registry Ammerländer Heerstr. 138, D-26129 Oldenburg +49 441 234 - 4530 (phone) +49 441 234 - 4589 (fax) E-Mail: Klaus.Kinder(a)telekom.de

1 0

RE: [address-policy-wg] Re: [ncc-services-wg] Request Forms: upda ted and available on LIR Portal
by Bornhorst, Ludger 25 Sep '03

25 Sep '03

Hi Christian, > The question is how complex an evaluation must be? The facts needed to > evaluate a normal IP requests are simply the number of nodes needing a > public IP address. In case one or more nodes needs more than 1 IP address > then documentation is needed to explain why to exceed the normal rules, also > in case the expected growth pr. year exceeds 100%. Yes, but I don't have any problem to ask endusers about their (planned) hardware and to document their needs in the way we've done it since several years now, like "We have 20 PC's, 5 routers, 200 dial-in-ports and so on..." This general information will (in most cases) be sufficient to evaluate IP requests. > It would of course be easier to falsify the number of nodes than to falsify > the documentation, but in case an end user intends to falsify information in > order to get more IP addresses than justifyable, then I don't see any easy > way to prevent this. Right, but there are still enduser who don't know about classless addressing. That means they are asking for "Class-C" nets just because they think its hip. So I think it's responsibility of the LIR's to tell this endusers about CIDR and its outcomes. And, yes I agree: If an enduser wants to cheat at you, I can't see a way to prevent this. > I would find it reasonable if larger requests still required some form of > documentation, for example /24 and above. But it would of course still be > very important for all LIRs to stress that the information received from the > enduser must be correct. ACK! This way it would be possible to serve the main part of the customers at a simple level and only ask reasonable questions (hardware documentation) if the request exceeds a certain level. I would like to stress that the /24 border should be the maximum limit of "freedom" given here. Maybe it's better to decrease this "HW-documentation-border" down to /25 or /26 ? What do you think? mit freundlichen Gruessen/with best regards Ludger Bornhorst ______________________________________________________________________ Deutsche Telekom AG T-Com Headquarters Network Information Center Ammerlander Heerstr. 138, D-26129 Oldenburg Hotline +49 441 234 4581 (phone) +49 800 3301180 +49 441 234 4589 (fax) +49 800 3301179 ludger.bornhorst(a)telekom.de (mail) dk.call-center(a)telekom.de

2 1

Re: [address-policy-wg] Re: [ncc-services-wg] IPv6 applications (was: Request Forms: updated and available on LIR Portal)
by Gert Doering 02 Sep '03

02 Sep '03

Hi, On Tue, Aug 26, 2003 at 12:57:13PM +0200, Dominic Spratley wrote: > You both made several points and I hope I can explain our thinking on them > for you. We think these new forms represent a change in the way we provide > services to LIRs so we've addressed this answer to the NCC Services WG list. > We don't think they represent a change to the RIPE community's policy. Actually, I tend to disagree, at least for some parts. Which is why I've put the APWG list back into the CC: (sorry for duplicates). Some of the criticism voiced is that the NCC is asking questions and enforcing rules that are more strict than what the policy demands - and this is certainly relating to policy. [..] > You asked about the requirement for a network diagram to be supplied when > requesting an IPv6 allocation. There are two reasons for this. Firstly, the > RIPE NCC has not yet made yet 250 IPv6 allocations. Our experience with IPv6 > networks is limited and we need network operators to show us how they intend > to use IPv6 address space in their networks. I agree with the assessment that "more experience for the NCC is a good thing". On the other hand, many startup IPv6 deployments are extremely trivial ("one access server with 1000 DSL circuits, serving /48s to DSL end users" would certainly qualify for the policy requirements). So I don't think it's appropriate to enforce this "you send us an interesting picture, otherwise you won't get an IPv6 allocation" approach. Make it optional. > Secondly, the current IPv6 > policy does not allow stockpiling of IPv6 address space. One way of > distinguishing a genuine request from one that is intended for stockpiling > reasons is to request a diagram showing how the address space will be used. > It doesn't have to be a a fancy diagram. It's also fine to fax a hand-drawn > diagram instead of sending one by e-mail. When we have more experience with > IPv6 I expect we will make the diagram optional. This is "conservationism striking again", and this is BAD. The idea behind the current policy is "make IPv6 address blocks available to anybody who is asking for them" (and can reasonably claim 200 future IPv6 customers). For that, you don't *need* a fancy network, so why do you have to demonstrate it at all? What are you worrying about? Address wastage is really not a problem right now. Obstacles on the way to IPv6 deployments are a problem, and we don't want the NCC to be an obstacle. Now come and flame me :-) Gert Doering -- NetMaster -- Total number of prefixes smaller than registry allocations: 55575 (56535) SpaceNet AG Mail: netmaster(a)Space.Net Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0 80807 Muenchen Fax : +49-89-32356-299

2 1

Re: [ncc-services-wg] Request Forms: updated and available on LIR Portal
by Sascha Lenz 02 Sep '03

02 Sep '03

Hay, On Thu, Aug 21, 2003 at 04:02:16PM +0200, Dominic Spratley wrote: > Hi Daniel, > > I hope I can clarify some of your points below: actually i didn't really want to get into this discussion, but it looks like _noone_ else has anything to say about the issues Daniel raised? Than can't be since he is right in most points. > At 03:37 AM 8/21/2003 +0200, Daniel Roesen wrote: [...] most points have been more-or-less clearified by Dominic's answer, but: > >- [EQUIPMENT DESCRIPTION] > > > > This requirement _can't_ be meant serious. We're not on April 1st, > > are we? The silliness of such information requirement was already > > recognized within the IPv6 allocation realm, so why introducing it > > now again for IPv4? > > This is a difficult one as it does require the LIR to do more preparation on > their side. The less time a Hostmaster spends sending E-mails asking > for additional information, the sooner the LIR gets their requested resource. > Asking for the type of equipment used really helps the Hostmaster > understand what and why IP addresses are being requested. ... i still have a problem here if that should be a "must provide this information". I have no much problems with questions like "why-pi" or "routing-reasons" because they can obviously be answered with standard phrases (which renders them useless again, but if RIPE NCC sees that many "bad" requests from many LIRs (aren't they trained?), it's OK for me, no much work, no stupid questions). BUT... information like the equipment being used or a network plan or so _must_ be optional information, not _required_ information. It can't be that a company is _required_ to make statements about their network and equipment if they want to have IP-Adresses! (and no, RIPE doesn't always qualify for receiving such information). Besides that it's way too much work to fill that in seriously for big requests, and doesn't really make sense for small requests. This should be _optional_ information in cases where it's needed to explain an unusual request, whatever, "we have only one machine but it has 500 IP Adresses due to this and that special purpose which can't be handled otherwise due to these and those hardware and software limitations". Is it really only me who is of that opinion, or noone recognized this problem or doesn't think it's a problem? Or isn't it meant as _required_ information anyways and a "N/A" is enough in most cases as answer to this part of the request? ...curious. The reason i noticed that this might get a problem was due to the unholy [...] #[REQUIRED INFORMATION]# [...] % % 2. Please provide a network diagram in PostScript or JPEG % format showing your IPv6 network. Submission instructions % can be found in the RIPE document "Supporting Notes for the % Initial IPv6 Allocation Request Form in the RIPE NCC Service % Region" found at: % % http://www.ripe.net/ripe/docs/ipv6-support-initial.html % % The diagram should indicate expected completion dates of % construction as well as how much IPv6 address space is % expected to be used in each subnet. % % [...] in the (old and new) IPv6 Initial Allocation request form. Since it says "required information" there, i already assumed that it might get a problem to get the IPv6 Allocation for us without providing this one. But i didn't see the point in doing so if i can make our network plans clear in text form, and explain the reasons why a network diagram for an IPv6 network is _completely_useless_ in general at the moment and especially in our case. Though, even on my 2nd mail on that request i just got the reply from some RIPE Hostmistress that "the inability to provide this network topology map calls into question the need for the IPv6 addresses being requested.". At the moment i'm really mad about this. We are currently prevented from deploying IPv6 addresses immediately because i don't have any Windows PC with Viso or something at hand, let alone the time to paint a very useless topology of our IPv6 overlay network, though i explained it in detail in text. (Not to mention that the statement that an active LIR which assigns IPv4 addresses for years is questioned that it will assign IPv6 addresses just because it doesn't like to waste time on painting network maps of some routers and tunnels is VERY doubiously to me.) Why the hell is such information _required_? Information about what equipment being used and a network topology map on a picture might be additional information at best. I fear that IP(v4) request will be denied or at least delayed in future if the RIPE Hostmasters are gonna complain about missing or unsatisfying information about the equipment in the future, too. That's not acceptable i think. But i might be wrong, we're realatively small and don't have that many requests in general, i just wonder why noone of the "big LIRs" sees this problem? You all have AWs that big that you don't care about filling in RIPE forms anyways and have payed managers to paint network diagrams all day? *hint* :) > >Further, the term "peer" is used in a very unclear way in the ASN > >request form and the supporting notes. > > > >Formerly, one uplink and one peer (commercial term) were enough to > >justify an ASN, as this constitutes a "unique routing policy". The > >ASN request form allows this interpretation of "peering partners" > >with "peering" in the technical sense. BUT the supporting notes > >specifically mention the requirement for two peers to "ensure that the > >organisation is multihomed". For me, multihoming means to have at least > >two _upstreams_. This would be a more stricter policy than before. > >What was the real intention behind these phrases? These documents > >should be very specific in the usage of "peer". It might be interpreted > >technically or commercially, each implying different constraints. > >I suggest changing the wording from "peer" to "upstream" in order to > >avoid ambiguities. > > Again this is a good point. However I don't think that either term is > appropriate for all situations. When writing these documents we used > the word peer as we wanted to emphasise it was the routing policy which > was important. So, the policy didn't change to "you have to have two _upstreams_ to get an ASN" but it's only a language-confusion here? P.S.: I think this discussion belongs to the address-policy-wg, not ncc-services-wg? Sorry for crossposting, remove the latter in any replies if i'm right. -- ========================================================================== = Sascha 'master' Lenz SLZ-RIPE slz(a)baycix.de = = NOC BayCIX GmbH = = http://www.noc.baycix.de/ * PGP public Key on demand * = ==========================================================================

4 7

Re: [address-policy-wg] WG Charter
by Hans Petter Holen 01 Sep '03

01 Sep '03

> Hans Petter, > > I would also mention the role of the working group in > - co-ordinating policies with other RIRs > - address policy issues that have to do with IANA/ICANN What about: The Address Policy WG develops policies relating to the management and registration of Internet resources (currently IPv4, IPv6 and AS Numbers) by the RIPE NCC and its LIRs within the RIPE NCC service region. It also co-ordinates policies with the other RIR communities and liaises with the IANA and ICANN on address policy issues. The Address Policy WG meets three times a year at RIPE meetings and has an open (publicly archived) mailing list. Anyone with an interest in Internet numbering issues is welcome to observe, participate and contribute to the WG. -hph

4 4

Fwd: selling ip:s? (kf)
by Katri 28 Aug '03

28 Aug '03

>Hello, I would like rise the question about selling ip-addresses... > >Let me present two exampled: >1. ISP A has offeres adls that includes static 1 ip-address, but if the >customer needs more ip:s > they will apply for this and pay a sum of X krona per ip-adress they > receive. > ISP B also offeres adsl that inclued 1 ip-address, and when the > customer needs more ip:s > they will have to change the service in order to receive more ip:s, > since the adsl service is > only offered with 1 ip-address and approved from RIPE NCC to be done > in this way. > How should ISP B compare and offer the same amount of ip-addresses > without "getting > into trouble"? > >2. ISP A has a customer who has received /24 from which they share out >addresses > and their customers can receive more addresses for a sum of X krona. > > I understand that we are not allowed to sel our ip-addresses but what > about > our customers customer? Is there anything preventing this from > happening and > is there something documented? > >Regards Katri >Tele2/Swipnet IP Registry >Local Internet Registry >__________________________________________________________ > >Tele2/SWIPnet Tel: 08 5626 40 08 >Box 62 Fax: 08 5626 42 10 >164 94 Kista Email: ip(a)swip.net >SWIP-RIPE SWIPNET-LIR-MNT >__________________________________________________________

2 1