- ripe-list - mailman.ripe.net

Fwd: A Direction for IPng
by IESG Secretary 09 Sep '93

09 Sep '93

Folks, Phill Gross asked me to forward this to you all FYI. /jws ------- Forwarded Message Date: Tue, 07 Sep 1993 14:02:30 -0400 From: Phill Gross <pgross(a)ans.net> To: IETF-Announce :; Subject: A Direction for IPng A Direction for IPng At the Amsterdam IETF meeting, we held a BOF, entitled the "IPDecide BOF", on the process and progress of the IPng activities. ("IPng" stands for "IP, the next generation". The IPDecide BOF was chaired by Brian Carpenter. Minutes are available in the IETF directories, with the file name </ietf/93jul/ipdecide-minutes-93jul.txt>.) The IPDecide BOF explored several facets of the IPng process, such as - "What is the basis for choosing the next generation IP (i.e., what are the technical requirements and decision criteria)." - "With the advent of CIDR and new, more stringent address assignment policies, are we comfortable that we truly understand the level of urgency?" - "Should the IETF or the marketplace make the final IPng decision". The BOF was held in a productive atmosphere, but did not achieve what could be called a clear consensus among the assembled attendees. In fact, despite its generally productive spirit, it did more to highlight the lack of a firm direction than to create it. The IPDecide BOF was followed the next evening by the open IESG plenary. During this session, the IESG and the assembled attendees discussed the IPng issues and seemed to arrive at a consensus based on the following set of bullets presented by the IETF chair: - "The IETF needs to move toward closure on IPng." That is, the IETF should take active steps toward a technical decision, rather than waiting for the "marketplace" to decide. - "The IESG has the responsibility for developing an IPng recommendation for the Internet community." That is, the IESG should provide leadership and take specific actions to help move the IETF toward a technical decision. - "The procedures of the recommendation-making process should be open and published well in advance by the IESG." - "As a part of the process, the IPng WGs may be given new milestones and other guidance to aid the IESG." - "There should be ample opportunity for community comment prior to final IESG recommendation (e.g., there will be an extended Last Call)." A Direction For IPng Building on this consensus, I'd like to announce a set of specific directions in the IESG that I hope will move us toward timely resolution of many of the key IPng issues. The IESG will establish a temporary, ad hoc, "area" to deal specifically with IPng issues. The charter for this new IESG area is to develop a recommendation on which, if any, of the current proposals should be adopted as the "next IP". This recommendation will be submitted to the IESG and to the Internet community for review. Following an adequate period of review to surface any community concerns, the IESG will issue a final IPng recommendation. All of the current IPng-related working groups will be moved immediately into this new area. This new area will be headed by two co-Area Directors from within the IESG. I have asked Allison Mankin (NRL), current Transport Services AD, and Scott Bradner (Harvard), current Operational Requirements AD, to serve as co-AD's for this temporary area. I am very pleased to report that they have agreed to take this important assignment. (Because this is expected to be a temporary assignment, Scott and Allison will also continue to serve in their current IESG positions during this period.) All IETF Areas are now expected to have Area Directorates. For the IPng Area, a Directorate will be especially important to bring additional viewpoints into the process. Therefore, I am asking that, as their first action, Scott and Allison form a specific IPng Directorate to act as a direction-setting and preliminary review body. The IPng process will continue to be completely open, and therefore reports and meeting notes from any IPng Directorate meetings will be published in timely fashion. Issues Toward IPng Resolution Two important issues need resolution immediately before we can expect progress toward an IPng recommendation: - What is the scope of the effort? That is, should IPng be limited to solving the well known scaling and address exhaustion issues; or should IPng also include advanced features such as resource reservation for real-time traffic? The argument in favor of considering advanced features is that migration to a new IP is (hopefully, only!) a once-in-a-generation occurance, and therefore all advanced features should at least be considered. Arguments opposed to considering advanced features include the fact that we may not have time for this level of effort before the scaling and address exhaustion problems confront us, and that we may not have the necessary understanding and experience to make all the correct choices at this time. - What is the available timeframe? That is, before we can even begin to make an informed decision about the scope, we need a better understanding of the urgency and time constraints facing us. Factors that affect the available time include the current rate of address assignments (which can give us an estimate of when we are currently projected to run out of addresses), the current policies governing address assignment (which can give us an understanding of how policies affect the assignment and utilization rates), the impact of CIDR aggregation, the development time for IPng, and the time needed to field and migrate to the new IPng. Therefore, I am asking the new AD's and the Directorate to start immediately the following specific activities to help guide their ultimate IPng recommendation: 1. Develop an understanding of the available timeframe, covering at least the following issues: - Review Internet growth metrics, such as the current address assignment and utilization rates. Develop an understanding of how the new address assignment policies impact the assignment and utilization rates. - Review the expected impact of CIDR address aggregation. Develop an understanding of the expected savings due to CIDR aggregation. - Develop new technical guidelines for classless Internet addressing. Specific examples include guidelines for how to utilize variable length subnet masks, and how to utilize currently unused Class A and B addresses in a classless fashion in hosts and routers. - Develop a strong understanding of the time required for the development, fielding, and migration for a new IP. - Based on all the above issues, (a) develop an estimate for how long we have to to develop and deploy an IPng. This could be a set of estimates based on best/worst case estimates for how each of the above factors will affect the available timeframe. (b) Consider whether more stringent assignment policies might provide additional time. If so, recommend such policies. (c) make a recommendation on whether it is worthwhile to mount a serious effort to reclaim addresses and/or to renumber significant portions of the Internet. 2. Based on an informed judgement of the time constraints above, make a recommendation regarding the scope for IPng, i.e., should IPng consider scaling issues only or advanced topics also. 3. Based on the scope and time constraints, develop a clear and concise set of technical requirements and decision criteria for IPng. These should include, but not be limited to, the criteria outlined in the IESG statement (RFC1380). 4. Based on the decision criteria, scope, and time constraints, make a recommendation on which of the current IPng candidates to accept, if any. Finally, I am asking Scott and Allison to make a detailed report at the opening plenary of the next IETF meeting in November on the status of setting up their new area, and on their progress toward organizing the above work items. In particular, the status of the work items on timeframe should be fully reported. This will be followed by regular progress reports to the Internet community, at IETF meetings and in other appropriate forums. Please join me in giving Scott and Allison our full cooperation, and in thanking them for accepting this daunting assignment. I feel confident that we will now make significant progress on the important IPng issues facing the Internet community. Phill Gross IETF/IESG Chair P.S. All follow-up discussion of this message should be on the main IETF mailing list ietf(a)cnri.reston.va.us. ------- End of Forwarded Message

1 0

REMINDER for speakers at RIPE 16
by Anne Lord 07 Sep '93

07 Sep '93

Dear All, **REMINDER** **REMINDER** **REMINDER** **REMINDER** **REMINDER** [This reminder is especially aimed at all those attending the RIPE meeting who plan to make presentations in WORKING GROUP/BOF sessions - sorry to all those for whom this message is a repeat reminder] Proposal to simplify taking the minutes at future RIPE meetings In May I circulated a plan to simplify taking the minutes at RIPE meetings. In case you have forgotten about the new arrangements :-) I have summarised below the salient points for you as a speaker at the forthcoming RIPE meeting in one weeks time. Working Group Presentations/BOF's - - - - - - - - - - - - - - - - - Requirements: Summary of your presentation for inclusion in Minutes. Indication whether you would like your summary to be archived in the RIPE document store in the presentations directory. Deadline: one week after the RIPE meeting - Friday 22nd September, 1993 Format: ASCII for the minutes ASCII/ps for the presentations directory (there is no deadline on submission to the document store) Action by WG Chair: Review presentation {optional} Action by NCC: Editing text for spelling and grammar only. Editorial control remains with author. *Help wanted* To be able to carry this out, I am dependent on your help. Please dont leave it too late to mail me your presentation if you would like something included in the minutes. If you would explicitly *not* like anything included in the minutes, please let me know. Many thanks for your cooperation. It is really appreciated! Anne

1 0

Second Document announcement.
by Tony Bates 07 Sep '93

07 Sep '93

New/Revised RIPE Document Announcement -------------------------------------- A new document below ...is available from the RIPE document store. Ref: ripe-094 Title: Generic Internet Service Specification (GISS) Project Title: Final Report Author: Tony Bates Date: 7 Sep 1993 Format: PS=78654 Obsoletes: Obsoleted by: Updates: Updated by: Short content description ------------------------- This is the Final Report of the GISS project. Unfortunately, this document is only available in postscript as it contains graphics. FTP Access ---------- All RIPE documents and Internet RFC`s are available via anonymous FTP from host ftp.ripe.net. Type "ftp ftp.ripe.net". Login with username "anonymous" supplying your email address as the password. After logging in, type "cd ripe/docs/ripe-docs" followed by the command "get <filename>". For example "get ripe-094.ps". Electronic Mail Retrieval of Documents -------------------------------------- Documents can also be retrieved from the RIPE document store using a mail server program. For more information on how to use the program, send email to: mail-server(a)ripe.net with "send HELP" in the body text. RIPE NCC Interactive Information Server --------------------------------------- Type "telnet host info.ripe.net". This is a menu driven service allows the document store to be browsed. After reading documents you are prompted as to whether you would like to receive an email copy of the document you have just read. If you would, you simply enter your email address and the document will be mailed to you. Below are details of alternative methods of access. Gopher Access ------------- The same documents are available via a "gopher" server at "gopher gopher.ripe.net". WAIS Access ----------- There is also a "WAIS" server at wais.ripe.net, where there is a WAIS index for RIPE documents "ripe-docs.src" WWW Access ---------- For those who wish to add this home page at the RIPE NCC to their own customized home pages, it can be accessed as: http://www.ripe.net MIME Mail Reader ---------------- Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RIPE document. SEND ripe/docs/ripe-docs/ripe-094.ps

1 0

document announcement
by Tony Bates 07 Sep '93

07 Sep '93

New/Revised RIPE Document Announcement -------------------------------------- A new document below ...is available from the RIPE document store. Ref: ripe-093 Title: "Implementation of a Route Server for Policy Based Routing Title: across the GIX Project" -- Final Report Author: Tony Bates Date: 7 Sep 1993 Format: PS=160095 Obsoletes: Obsoleted by: Updates: Updated by: Old: Short content description ------------------------- This is the Final Report of the Route Server project. Unfortunately, this document is only available in postscript as it contains graphics. FTP Access ---------- All RIPE documents and Internet RFC`s are available via anonymous FTP from host ftp.ripe.net. Type "ftp ftp.ripe.net". Login with username "anonymous" supplying your email address as the password. After logging in, type "cd ripe/docs/ripe-docs" followed by the command "get <filename>". For example "get ripe-093.ps". Electronic Mail Retrieval of Documents -------------------------------------- Documents can also be retrieved from the RIPE document store using a mail server program. For more information on how to use the program, send email to: mail-server(a)ripe.net with "send HELP" in the body text. RIPE NCC Interactive Information Server --------------------------------------- Type "telnet host info.ripe.net". This is a menu driven service allows the document store to be browsed. After reading documents you are prompted as to whether you would like to receive an email copy of the document you have just read. If you would, you simply enter your email address and the document will be mailed to you. Below are details of alternative methods of access. Gopher Access ------------- The same documents are available via a "gopher" server at "gopher gopher.ripe.net". WAIS Access ----------- There is also a "WAIS" server at wais.ripe.net, where there is a WAIS index for RIPE documents "ripe-docs.src" WWW Access ---------- For those who wish to add this home page at the RIPE NCC to their own customized home pages, it can be accessed as: http://www.ripe.net MIME Mail Reader ---------------- Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RIPE document. SEND ripe/docs/ripe-docs/ripe-093.ps

1 0

amateur edition of inet'92 on four hours video casette
by turchanyi＠fserv.kfki.hu 06 Sep '93

06 Sep '93

Folks, I prepared an edited version of my video records made in Kobe, last years. (4 hours, PAL, VHS) Please send me a message if you are interested in having your own copy (for the price of the casette). Regards, Geza Turchanyi

1 0

Report available: The First Year of the RIPE NCC
by Daniel Karrenberg 03 Sep '93

03 Sep '93

New RIPE Document Announcement ------------------------------ A new document is available from the RIPE document store. Ref: ripe-092 Title: The First Year of the RIPE NCC Author: Daniel Karrenberg Date: 3 Sep 1993 Format: PS=27959 TXT=4094 Short content description ------------------------- This very short document is the first formal yearly report of the RIPE NCC. It contains an overview of the expenditures during the first year of operations. For detailed information, please consult the Quarterly Reports. FTP Access ---------- All RIPE documents and Internet RFC`s are available via anonymous FTP from host ftp.ripe.net. Type "ftp ftp.ripe.net". Login with username "anonymous" supplying your email address as the password. After logging in, type "cd ripe/docs/ripe-docs" followed by the command "get <filename>". For example "get ripe-092.txt". Electronic Mail Retrieval of Documents -------------------------------------- Documents can also be retrieved from the RIPE document store using a mail server program. For more information on how to use the program, send email to: mail-server(a)ripe.net with "send HELP" in the body text. RIPE NCC Interactive Information Server --------------------------------------- Type "telnet host info.ripe.net". This is a menu driven service allows the document store to be browsed. After reading documents you are prompted as to whether you would like to receive an email copy of the document you have just read. If you would, you simply enter your email address and the document will be mailed to you. Below are details of alternative methods of access. Gopher Access ------------- The same documents are available via a "gopher" server at "gopher gopher.ripe.net". WAIS Access ----------- There is also a "WAIS" server at wais.ripe.net, where there is a WAIS index for RIPE documents "ripe-docs.src" WWW Access ---------- For those who wish to add this home page at the RIPE NCC to their own customized home pages, it can be accessed as: http://www.ripe.net MIME Mail Reader ---------------- Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RIPE document. SEND ripe/docs/ripe-docs/ripe-092.txt

1 0

Document Announcement
by Tony Bates 03 Sep '93

03 Sep '93

Dear All, A new document is available. This is for use when applying for Autonomous System (AS) numbers. It contains some supporting notes to help with the application. New/Revised RIPE Document Announcement -------------------------------------- A <revised><new> document below ...is available from the RIPE document store. Ref: ripe-091 Title: European Autonomous System Number Application Form Title: & Supporting Notes Author: Tony Bates, Anne Lord Date: 3 Sep 1993 Format: PS=41091 TXT=13759 Obsoletes: Obsoleted by: Updates: Updated by: Old: Short content description ------------------------- Ripe-091 is the first version of the "European Autonomous System Number Application Form". It contains a guidance section to help in applying for AS numbers. It is split into two parts; an administrative and a technical section. The technical section includes the RIPE-81 attributes used for registering an AS's routing policy. FTP Access ---------- All RIPE documents and Internet RFC`s are available via anonymous FTP from host ftp.ripe.net. Type "ftp ftp.ripe.net". Login with username "anonymous" supplying your email address as the password. After logging in, type "cd ripe/docs/ripe-docs" followed by the command "get <filename>". For example "get ripe-091.txt". Electronic Mail Retrieval of Documents -------------------------------------- Documents can also be retrieved from the RIPE document store using a mail server program. For more information on how to use the program, send email to: mail-server(a)ripe.net with "send HELP" in the body text. RIPE NCC Interactive Information Server --------------------------------------- Type "telnet host info.ripe.net". This is a menu driven service allows the document store to be browsed. After reading documents you are prompted as to whether you would like to receive an email copy of the document you have just read. If you would, you simply enter your email address and the document will be mailed to you. Below are details of alternative methods of access. Gopher Access ------------- The same documents are available via a "gopher" server at "gopher gopher.ripe.net". WAIS Access ----------- There is also a "WAIS" server at wais.ripe.net, where there is a WAIS index for RIPE documents "ripe-docs.src" WWW Access ---------- For those who wish to add this home page at the RIPE NCC to their own customized home pages, it can be accessed as: http://www.ripe.net MIME Mail Reader ---------------- Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RIPE document. SEND ripe/docs/ripe-docs/ripe-091.txt

1 0

** RIPE 16 - Dinner Announcement **
by Anne Lord 02 Sep '93

02 Sep '93

* ANNOUNCEMENT * * ANNOUNCEMENT * * ANNOUNCEMENT * * ANNOUNCEMENT * * 16th RIPE Meeting Dinnner Thursday September 16th, Amsterdam Time : 8pm Departure Point: Prins Hendrikkade opposite Central Station For the 16th RIPE meeting dinner we thought it might be nice to have dinner afloat. The dinner will be served aboard a canal boat which will cruise through the canals of Amsterdam. There will be a guide on board the boat to give a guided commentary (as much or as little as you want). The menu for the dinner is as follows (vegetarian and/or special diet meals can be arranged on request) : -00- Creamy Chervil Soup -00- Filet of Salmon in a herb sauce Seasons vegetables Potato-dish -00- Fresh fruit and cream -00- Coffee and digestif -00- The meal will be accompanied by a choice of red or white wine. Cost of the dinner and guide will be Hfl. 70,- inc. drinks Please reply to <meeting(a)ripe.net> if would like to have a place reserved for you at the dinner. Payment from us to them will be on Tuesday 14th, so this is the deadline for reserving a place. The money for the meal will be collected on the second day of the RIPE meeting during lunch. Now I am praying for calm weather and sunny skies :-) Anne - - - - - - - - - - - - -- - - - - - - -- - - - - - - -- - - - - - --

2 1

RIPE DNS Hostcount August 1993
by Marten Terpstra 02 Sep '93

02 Sep '93

Folks, Please find below the RIPE DNS hostcount for August 1993. - we are currently analyzing all the DNS output for some statistics on the 2nd and 3rd level domains inside each of the top levels. Once we get some results we will post them as well. - output again on ftp.ripe.net:ripe/hostcount, also available in the gopher server on gopher.ripe.net under "RIPE Archive"/"ripe"/"hostcount" - UK makes a big jump in their race with Germany towards 100,000 - total increase of almost 25,000 to over 451,000. - history again appended, I have included deltas this time, which shows the growth compared to the previous count. I plan to continue doing this. - everyone who uses "host" for similar purposes as this should pick up a new version from either ftp.ripe.net:tools/dns/host.tar.Z or ftp.nikhef.nl:pub/network/host.tar.Z, because some modifications have been made that make the output somewhat more friendly, and the hostcount much faster (thanks to Eric Wassenaar, NIKHEF) Enoy, -Marten ------- RIPE DNS Hostcount Previous Count : Wed Jul 31 1993 This Count : Tue Aug 31 1993 CY SOA COUNTED DUPL REAL CHANGE ============================================================ al 1 0 0 0 0 at 296 12986 94 12892 + 272 be 57 5134 92 5042 + 806 bg 3 21 5 16 + 16 by 0 0 0 0 0 ch 171 32476 712 31764 + 1283 cs 74 2810 57 2753 + 3 cy 5 30 0 30 0 cz 69 3439 85 3354 + 170 de 1395 95375 3355 92020 + 2506 dk 113 6823 93 6730 + 222 dz 0 0 0 0 0 ee 17 210 2 208 + 16 eg 1 0 0 0 0 es 238 10485 127 10358 + 358 fi 271 28244 748 27496 + 1521 fo 1 0 0 0 0 fr 539 44242 604 43638 + 5287 gb 1 15 0 15 + 1 ge 1 0 0 0 0 gr 86 1337 225 1112 + 12 hr 26 419 1 418 + 91 hu 32 1679 7 1672 + 265 ie 44 1937 48 1889 + 222 is 36 1302 10 1292 + 65 it 353 14058 215 13843 - 338 il 84 5671 64 5607 + 152 li 2 17 0 17 0 lt 1 0 0 0 0 lu 11 229 0 229 + 23 lv 1 15 0 15 + 1 mt 1 0 0 0 0 nl 379 36634 400 36234 + 949 no 404 25871 226 25645 + 958 pl 62 1216 9 1207 + 91 pt 85 2692 45 2647 - 75 ro 2 14 0 14 0 se 457 35535 313 35222 + 2873 si 11 468 3 465 + 9 sk 24 469 8 461 + 162 su 143 757 44 713 + 219 tn 1 0 0 0 - 11 tr 18 449 2 447 + 259 ua 34 140 11 129 + 110 uk 654 95794 10274 85520 + 5791 va 0 0 0 0 0 yu 2 2 0 2 0 ============================================================ 6206 468995 17879 451116 +24289 History Count Delta Delta % ----------------------------------------- Oct 1990 31724 Nov 1990 33665 + 1941 + 6.1% Dec 1990 29230 - 4435 - 13.2% Jan 1991 43832 + 14602 + 50.0% Feb 1991 - Mar 1991 44506 + 674 + 1.5% Apr 1991 46948 + 2442 + 5.5% May 1991 - Jun 1991 63267 + 16319 + 34.8% Jul 1991 - Aug 1991 73069 + 9802 + 15.5% Sep 1991 92834 + 19765 + 27.0% Oct 1991 104824 + 11990 + 12.9% Nov 1991 129652 + 24828 + 23.7% Dec 1991 - Jan 1992 141308 + 11656 + 9.0% Feb 1992 161434 + 20126 + 14.2% Mar 1992 167939 + 6505 + 4.0% Apr 1992 170050 + 2111 + 1.3% May 1992 182528 + 12478 + 7.3% Jun 1992 196758 + 14230 + 7.8% Jul 1992 213017 + 16259 + 8.3% Aug 1992 221951 + 8934 + 4.2% Sep 1992 232522 + 10571 + 4.8% Oct 1992 254585 + 22063 + 9.5% Nov 1992 271795 + 17210 + 6.8% Dec 1992 284374 + 12579 + 4.6% Jan 1993 303828 + 19454 + 6.8% Feb 1993 322902 + 19074 + 6.3% Mar 1993 355140 + 32238 + 10.0% Apr 1993 366164 + 11024 + 3.1% May 1993 385522 + 19358 + 5.3% Jun 1993 404930 + 19408 + 5.0% Jul 1993 426827 + 21897 + 5.4% Aug 1993 451116 + 24289 + 5.7%

1 0

Guidelines on how to report on european connectivity
by Milan Sterba 01 Sep '93

01 Sep '93

Dear colleagues, it has been agreed at the last RIPE meeting that a new more general scheme of reporting on european connectivity shall be adopted in RIPE. The reporting scheme will be open for whole Europe and will cease to be restricted only to Central and Eastern European countries. Connectivity issues will not be pulished in form of a periodical report but will rather be maintained in the form of an indexed archive at the RIPE repository. We have agreed that there should be some editing board which would unify the look and style the presentations of different countries. We also agreed on producing guidelines to the contributors on how the connectivity report of a country should be organized. These guidelines are now published as a RIPE draft document ripe/docs/ripe-drafts/connectivity-report-plan.txt and will be proposed to be accepted as a ripe document at the next RIPE meeting in September. Please have a look at this proposal. I will be gratefull for any comments you might have to this proposal in order to work out a viable scheme which would result in improved quality of reporting on european connectivity. Thanks and see you in Amsterdam Best regards Milan Sterba -- BEWARE - MY TELEPHONE NUMBER HAS CHANGED !!!! ====================================================================== Prague University of Economics e-mail : Milan.Sterba(a)vse.cz Computing Center tel : +42 2 24 21 79 00 nam. W. Churchilla 4 home: +42 2 823 78 59 130 67 Praha 3 fax : +42 2 236 46 24 Czech republic =======================================================================

1 0