- lir-wg - mailman.ripe.net

Re: Tracking stealth portscan/pepsi attacks
by Berislav Todorovic 02 Sep '99

02 Sep '99

>> As a side note, does anybody use anything to prevent address spoofing in >> their network? That would at prevent a lot of attacks completly and make >> tracing the rest much easier. RFC 2267 describes most of the measures that should be taken at the router level. I'm not sure how many ISPs implemented everything recommended in that document. Regards, Beri .-------. | --+-- | Berislav Todorovic, B.Sc.E.E. | E-mail: BERI(a)etf.bg.ac.yu | /|\ Hostmaster of the YU TLD | |-(-+-)-| School of Electrical Engineering | Phone: (+381-11) 3221-419 | \|/ Bulevar Revolucije 73 | 3218-350 | --+-- | 11000 Belgrade SERBIA, YUGOSLAVIA | Fax: (+381-11) 3248-681 `-------' --------------------------------------------------------------------

2 1

Call for agenda items to the RIPE Local Internet Registry Workin Group
by hph＠sys.sol.no 30 Aug '99

30 Aug '99

Dear Working Group, Summer is almost over and there will soon be a RIPE meeting, and at that RIPE meeting a Local Internet Registry Working Group. Since we were extremely efficient at the last meeting we have 0 - zero - open action points, so it will be even harder for me to put together an agenda this time. This is the reason for this message. What do YOU want us to do at the next meeting? Shall we limit the WG to the registry reports or are there other matters that needs to be discussed? Lots of things are happening in our area, a proposal for an address-supporting organisation in ICANN (see http://www.icann.org/comments-mail/comment-aso/maillist.html) has been circulated among the membership and submitted to the ICANN board. Some of the discussion has taken on aso-discuss(a)ripe.net and yet some on comment-aso(a)icann.org which can be viewed at http://www.icann.org/comments-mail/comment-aso/maillist.html . But when the discussion has ended and there is consensus, the real work start, how do we appoint our representatives to the ASO, and who do we want oversee the future of the Internet, both at the ASO and on the ICANN board? Should we discuss this topic in any flavour in the working group or should we leave this for the plenary? In the ICANN process the openness of our policy-making procedures has been repeatedly questioned by external voices. Not very concrete and therefor not very constructive. Maybe we should rise above that and still discuss this. Maybe our policy-making procedures seem closed because nobody knows what they are and how they work? IANA has allocated addresses to the regional registries. What implications does this have? Should this still be a matter for the IPv6 WG only or should some aspects of IPv6 such as evolving the policy document, be included on our agenda. (Or even, do we know enough about IPv6?) Then of course there may be concrete policy issues or other topics you would like on the agenda. Feel free to air your opinions at this list or to me. I plan to circulate a draft agenda early next week, and make one or two updates before the meeting. Hans Petter Holen LIR-WG Chair.

1 0

Final RIR ASO Proposal Submission to ICANN
by Mirjam Kuehne 27 Aug '99

27 Aug '99

Dear Colleagues, Thank you very much for the support received regarding the 'Draft proposal for a MoU-based ASO'. As you know, your support is essential to the process and therefore very much appreciated. Discussions following the announcement of the draft proposal on 8 July 1999, and at the recent open ASO meeting which took place at the IETF in Oslo, modifications to the draft proposal were suggested. Following discussions between the RIR excecutive boards, taking into account the collective interests of our communities, further adjustments were made to the proposal which we believe will enhance the prospect of its adoption by ICANN. A proposal for the formation of an ASO has now been formally submitted to ICANN jointly by the Regional Internet Registries: APNIC, ARIN and RIPE NCC. The 'Proposal for a MoU-based ASO' can be found on the RIPE NCC Web site under the 'Current Issues' section at: http://www.ripe.net/info/ncc/icann.html Below please find the modified sections of the draft text as well as comments supporting the motivation for each of these changes. As the adjustments to this proposal have been made for clarity purposes to ensure fair and open processes in all regions, we hope that we can count on your continued support. Kind Regards, Mirjam Kuehne RIPE NCC 2. The Address Council. a. Members. ----------- [original text:] Each RIR signatory of the MOU will appoint two [2] individuals to the Address Council by means of their own choosing. No individual can serve on the Address Council and be on the staff of a RIR at the same time. [final version:] Each RIR signatory of the MOU will select three [3] individuals to the Address Council using the following process: i Annually the RIR will issue a public call for nominees to the Address Council at least 90 days before the RIR's policy meeting. Any individual can submit a nomination to the RIR. ii The due date for this call shall be 30 days before the meeting. iii The nominees must be individuals. iv A list of all nominees who agree to run for the Address Council must be posted on the RIR's web page at least 15 days before the meeting along with a statement from each nominee who wishes to make one. v Selection of the RIR's members of the Address Council will be made via an open and transparent procedure. The individuals selected for the Address Council must not be staff members of the RIR. COMMENTS: Concerns were raised that having only two [2] Address Council members appointed per region would not allow for sufficient representation. Therefore the number was changed to three [3] per RIR signatory. When additional RIRs sign the MoU this will be revised in order to keep the number of Address Council members at a practical size. Principles for the selection of Address Council members were stated in section 3.b. of the original draft proposal. These methods have been refined and included in this section for further clarification. However, please note that the selection process of the Address Council members will be defined by the regions via an open and transparent procedure. b. Term. -------- [original text:] The term of Address Council members will be 2 years. Removal will be pursuant to procedures established through the MOU. (Initial terms will be 1 and 2 years to provide initial conditions for staggered terms.) [final version:] The term of Address Council members will be 3 years. Removal will be pursuant to procedures established through the MOU. (Initial terms will be 1, 2 and 3 years to provide initial conditions for staggered terms.) COMMENTS: With the increased number of Address Coucil members one additonal term has been defined. c. Powers/Duties of the Address Council. ---------------------------------------- ii Qualifications of ICANN Directors. [original text:] No more than 1 of the ASO-appointed Directors may come from the same geographic region. [final version:] a) No more than 1 ASO-appointed Director may come from the same geographic region. (This proposal assumes the regions defined in the ICANN by-laws.) b) No ASO-appointed Director may serve simultaneously on the Address Council. COMMENTS: The additional sentence under a) is to clarify the word 'region' in this context. Parapraph b) was added as no clear prohibition against Address Council members also serving on the ICANN board was stated. d. Address Policy Development. ------------------------------ [final version:] One paragraph was added to this section: In addition the Address Council may accept, for consideration, proposals for changes to global IP address policy from any interested individual. COMMENT: One may imagine a circumstance where it would be more practical to approach the ASO directly to support the fair and open consideration of a proposal in order to stress equal opportunity for all interested parties. In any case, all proposals received by the ASO will be reviewed by the RIR signaories and the community as described in this section following the above noted addition: In all cases when the Address Council reviews proposals for new global policies or proposed modification to existing policies in this area it will first solicit the opinions of all of the RIR signatories of the MOU and of the public. 3. Annual Open Meeting. (General Assembly) a. Hosting an open meeting. --------------------------- [original text:] The Address Council will periodically host an open meeting ("General Assembly") for promoting discussion and receiving input regarding the work of the ASO. A General Assembly meeting will be held once per year, and will permit open participation by all interested individuals. [final version:] The Address Council will periodically host an open meeting ("General Assembly") for promoting discussion and receiving input regarding the work of the ASO. A General Assembly meeting will be held *at least* once per year, and will permit open participation by all interested individuals. COMMENT: It was felt that the number of meetings should not be restricted in this document. The important point here is that there should be *at least* one meeting per year. b. Selection of Address Council Members. ---------------------------------------- [original text:] Ninety days prior to each General Assembly, ICANN and the Address Council shall make an open call for nominations to any potential vacancies in the Address Council. The results of this call will be forwarded to each RIR signatory to the MOU for their information. Each RIR signatory to the ASO MOU will be entitled to select two [2] members of the Address Council by means of its own choosing. The terms of the appointees will be determined by the appointing RIR. [final version:] Ninety days prior to each annual open meeting, ICANN and the Address Council shall make an open call for nominations to any potential vacancies in the Address Council. The results of this call will be forwarded to each RIR signatory to the MOU for their information. Each RIR signatory to the ASO MOU will be entitled to select three [3] members of the Address Council using the process described in Section 2a. COMMENT: This has been changed in order to make the section consistent with the principles outlined in section 2.a (see above). 4. Open Proceedings and Documents. b. ASO Proceedings ------------------ [original text:] All discussions of ASO business will be conducted on or reported on a publicly-archived mailing list accessible through the ICANN/ASO web site. The schedule for the ASO meetings will be posted 90 days in advance of the meeting date. The agenda for the Address Council and annual open meetings will be posted on the ICANN/ASO web site at least 30 days before the meetings. The minutes from all ASO meetings will be publicly posted on the ICANN/ASO web site within 30 days of the meeting. [final version:] All discussions regarding ASO policy formation will be conducted on or reported on a publicly-archived mailing list accessible through the ASO web site. The schedule for the ASO meetings will be posted 90 days in advance of the meeting date. The agenda for the Address Council and annual open meetings will be posted on the ASO web site at least 30 days before the meetings. The minutes from all ASO meetings will be publicly posted on the ASO web site within 30 days of the meeting. In the unlikely event that the policy formation discussions involve confidential commercial data that was presented in an address allocation process the above disclosures must be done in a way to protect the confidentially of that data. COMMENT: The location of the documentation to be published has been more clearly specified (on the ASO web site). The last sentence has been added in order to explicitly exempt confidential data from publication as defined in the existing RIR operational procedures. 6. Recognition. [original text:] 7) That the introduction of a new RIR must be based on a "Sound Business Plan". The plan must be reviewed by ICANN and by the existing RIRs. The process for creating a new RIR must be included in the MOU. [final version:] 6) That the proposed RIR has clearly defined procedures open to all interested parties regarding ensuring fair representation of constituents within the region of coverage in the policy development process. COMMENT: This paragraph was added in order to ensure open and transparent processes of policy development in all new and existing RIRs. For your information, please note that the order of points in appendix A has slightly changed, resulting in the number change noted above.

3 2

Top 100 Maintainers List - 19990820
by RIPE Database Manager 20 Aug '99

20 Aug '99

1 0

Draft minutes from the LIR-WG at RIPE 33
by hph＠sys.sol.no 18 Aug '99

18 Aug '99

Version 1.0 Chair: Hans Petter Holen <hph(a)sys.sol.no> Scribe: Paul Tate, RIPE NCC Hostmaster Participants: approximately 68 RIPE 33 - Local IR Working Group Final Agenda 1. Admin scribe participant list agenda meet the RIPE NCC hostmasters mailinglists 2. RIPE 32 minutes actions 3. Reports from the Registries RIPE: Paula Caslav APNIC: Paul Wilson ARIN: Micahel O'Neill New Regional R (Africa & S. America) brief status by Daniel Karrenberg 4. Tagging IP addresses for Anti Spam purposes 5. AOB Action Points LIR-WG RIPE 32 Done: NCC: Web interface to RIPE 141. Announce, receive comments, and make source public Done: NCC: Get IPv6 Guidelines in place Done: NCC: write up suggestion on lowering AW from /19 Done: Guy Davies, UUnet: Start discussion on list on max allocation size and internal aggregation needs for large networks Done: NCC: Make pretty address statistics charts Done: NCC: IP adresses to cable networks Document current IANA policy and align practice with other IRRs Everybody: Participate in policies for IPv6 discussion Open: tagging of IP addresses for anti SPAM Tagging IP addresses for anti SPAM measures presentation on how the Dialup User List implemented by Paul Vixie works: maps.vix.com discussion on the usefulness of adding mechanisms to the RIPE database took place. Daniel Karrenberg proposed a more general mechanism that would solve this and other needs Passed on to the db wg Action points lir-wg@RIPE 33 All previous actions DONE Many thanks to the RIPE NCC for the good work ! (And to Paula in particular) NO new actions added

1 0

Somebody else trying to use our NCC-Reg-ID
by registry＠gams.co.at 18 Aug '99

18 Aug '99

Dir LIRs! We received this mail yesterday, that someone sends AS requests with our NCC-Reg-ID. I mailed these guys -> no response ... Did someone experience things like that before ! --lg zen Original Mail starts here: > >Dear at.gams staff, > >We have received the below AS request however it has not been signed >by any of the current registered contact people, therefore I should >like to ask you to please resubmit the request by a registered contact >person. > > > Kind regards and thanks :-) > > from > > Pepa Tejedor Carnicero > > ======== > Ripe NCC > ======== > > > root(a)liberty.bulinfo.net writes: > * X-NCC-RegID: at > * .gams > * > * #[AUT-NUM TEMPLATE]# > * > * aut-num: NEW > * descr: Bulinfo Ltd. Autonomous System > * descr: Internet Services Provider > * descr: > * Sofia, Bulgaria > * as-in: from AS9127 100 accept ANY > * as-in: from AS8262 10 accept ANY > * as-out: to AS9127 announce NEW > * as-out: to AS8262 announce NEW > * default: AS9127 > * admin-c: KS2766-RIPE > * tech-c: KS2766-RIPE > * mnt-by: NEW > * changed: krassi(a)bulinfo.net 19990812 > * source: RIPE > * > * #[MAINTAINER TEMPLATE]# > * > * mntner: NEW > * descr: Bulinfo Ltd. AS Maintainer > * admin-c: KS2766-RIPE > * tech-c: KS2766-RIPE > * upd-to: krassi(a)bulinfo.net > * auth: CRYPT-PW BulinfoNet > * mnt-by: NEW > * changed: krassi(a)bulinfo.net 19990812 > * source: RIPE > * > * #[PERSON TEMPLATE]# > * > * person: Kr > * assimir Slavchev > * address: Bu > * linfo Ltd. > * address: Ca > * rnegie 11a str > * address: So > * fia 1000, Bulgaria > * phone: +3 > * 59 2 963 36 52 > * fax-no: +3 > * 59 2 963 37 64 > * e-mail: kr > * assi(a)bulinfo.net > * nic-hdl: > * KS2766-RIPE > * changed: kr > * assi(a)bulinfo.net 19990809 > * source: RI > * PE > * > * #[TEMPLATE END]#

1 0

Please, ignore "my" posting on local-ir
by Berislav Todorovic 06 Aug '99

06 Aug '99

Hello, The message with subject "RE: .DK domain", that I sent a month ago, appeared on the "local-ir" list today. I don't have any idea on the reason. Please, ignore it and apologies for inconvenience. Regards, Beri .-------. | --+-- | Berislav Todorovic, B.Sc.E.E. | E-mail: BERI(a)etf.bg.ac.yu | /|\ Hostmaster of the YU TLD | |-(-+-)-| School of Electrical Engineering | Phone: (+381-11) 3221-419 | \|/ Bulevar Revolucije 73 | 3218-350 | --+-- | 11000 Belgrade SERBIA, YUGOSLAVIA | Fax: (+381-11) 3248-681 `-------' --------------------------------------------------------------------

1 0

Top 100 Maintainers List
by RIPE Database Manager 04 Aug '99

04 Aug '99

2 1

New ACK ?
by mediaWays Hostmaster 29 Jul '99

29 Jul '99

[ Moderator note: changed ripe-list(a)ripe.net -> lir-wg(a)ripe.net ] Hi, does anyone know the new ACK !!! format for denic KKs ? MfG "hostmaster of the day" ________________________ Stephan Mankopf +49 5241 80 88729 hostmaster(a)mediaways.net

4 4

Re: IPv6 allocation from IANA.
by Paula Caslav 15 Jul '99

15 Jul '99

The URL is actually: http://www.ripe.net/lir/registries/ipv6.html Sorry about that. Paula paula(a)ripe.net writes: * #################################################### * This message was not delivered to * registry(a)broadsystem.com * Sender was informed with a copy of this message * #################################################### * * Hello colleagues, * * The RIPE NCC is pleased to announce that we have received an allocation * of IPv6 address space from the IANA and can start accepting requests * for sub-TLA allocations. If you wish to request a sub-TLA from the RIPE * NCC, please write to hostmaster(a)ripe.net. Please note that you have to * be a Local IR in order to apply. * * Early next week we will publish ripe-195, an IPv6 request form and * ripe-196, the IPv6 policy document. * * A current version of the policy document can already be seen on: * http://www/lir/registries/ipv6.html * * The only change in the ripe-196 document will be the addition of a * section on reverse DNS. * * A draft version of the request form is now available if you write to * hostmaster(a)ripe.net. * * I include the announcement message from the IANA below. * * Kind regards, * * Paula Caslav * RIPE NCC * * ------- Forwarded Message * * From: "IANA" <iana(a)ISI.EDU> * To: <iana-announce(a)ISI.EDU> * Subject: Delegation of IPv6 address space * Date: Wed, 14 Jul 1999 12:32:07 -0700 * * (text/plain) * Internet Community, * * After much discussion concerning the policy guidelines for the * deployment of * IPv6 addresses, in addition to the years of technical development done * throughout the Internet community, the IANA has delegated the initial * IPv6 * address space to the regional registries in order to begin immediate * worldwide deployment of IPv6 addresses. * * We would like to thank the current Regional Internet Registries (RIR) * for * their invaluable work in the construction of the policy guidelines, * which * seem to have general consensus from the Internet community. We would * also * like to thank the efforts of the IETF community and the support of the * IAB * in making this effort a reality. * * If you have further questions concerning this issue, please contact your * RIR, or you may also contact the IANA at iana(a)iana.org. * * The policy guidelines can be found online at one of the Regional * Internet * Registries: * * http://www.apnic.net * http://www.arin.net * http://www.ripe.net * * This is an historic moment in the continued development of the Internet. * * Thank you for your valuable support and participation in the Internet * community. * * Josh Elliott * On Behalf of the IANA Staff * * * ------- End of Forwarded Message * * * * * *

1 0