RE: Amsterdam WG query
Al Costanzo <Al@Kean.EDU> Fri, 07 May 1993 13:44 UTC
Received: by world.std.com (5.65c/Spike-2.0) id AA27103; Fri, 7 May 1993 09:44:44 -0400
Errors-To: ipv7-request@world.std.com
Sender: ipv7-request@world.std.com
Reply-To: ipv7@world.std.com
Precedence: bulk
Return-Path: <AL@TURBO.Kean.EDU>
Received: from TURBO.Kean.EDU by world.std.com (5.65c/Spike-2.0) id AA27073; Fri, 7 May 1993 09:44:40 -0400
Message-Id: <199305071344.AA27073@world.std.com>
Received: (from user AL) by TURBO.Kean.EDU; 07 May 93 09:26:32 EST
To: ipv7@world.std.com
From: Al Costanzo <Al@Kean.EDU>
Organization: Kean College of New Jersey
Security: -- none --
Comment: Sender Phone# (908) 527-2061
Comment: Sender Fax# (908) 527-0391
Subject: RE: Amsterdam WG query
Date: Fri, 07 May 1993 09:26:32 -0500
Status: R
I shall be in Amsterdam and will attend the RAP and IPv7 WG meeting(s). -al From tpix-request@world.std.com Thu May 20 16:34:35 1993 Received: by world.std.com (5.65c/Spike-2.0) id AA09104; Thu, 20 May 1993 16:34:32 -0400 Errors-To: tpix-request@world.std.com Sender: tpix-request@world.std.com Reply-To: tpix@world.std.com Precedence: bulk Return-Path: <ariel> Received: by world.std.com (5.65c/Spike-2.0) id AA09087; Thu, 20 May 1993 16:34:28 -0400 Date: Thu, 20 May 1993 16:34:28 -0400 From: ariel (Robert L Ullmann) Message-Id: <199305202034.AA09087@world.std.com> To: tpix Subject: ipv7->tpix Status: R Hi, The list name and the name of the archive on world.std.com have been changed from ipv7 to tpix. The old names work of course. This message is more in the way of a test than something you really needed to know ... Rob From tpix-request@world.std.com Wed May 26 21:42:49 1993 Received: by world.std.com (5.65c/Spike-2.0) id AA18045; Wed, 26 May 1993 21:42:36 -0400 Errors-To: tpix-request@world.std.com Sender: tpix-request@world.std.com Reply-To: tpix@world.std.com Precedence: bulk Return-Path: <ariel> Received: by world.std.com (5.65c/Spike-2.0) id AA18008; Wed, 26 May 1993 21:42:30 -0400 Date: Wed, 26 May 1993 21:42:30 -0400 From: ariel (Robert L Ullmann) Message-Id: <199305270142.AA18008@world.std.com> To: tpix Subject: ADPLAN draft Status: R Hi, The following is the first of several internet drafts to be published detailing aspects of the TP/IX and RAP protocols not covered in the base documents. I am circulating this for initial comments from the group before I put it up on internet-drafts. [and while I am bothering you :-] If you want to test a RAP prototype, *and* you have a public X.25 connection (so we can set up the requisite direct connection to my lab systems), please contact me. Best Regards, Robert (Remember that this mail list is set up for automatic discussion: replies lead to the list, not private reply. Eschew Reply-All :-) TP/IX R. L. Ullmann Internet Draft Process Software Corporation May 26, 1993 Initial AD Assignment Plan 1 Status of this Memo This memo presents an initial plan for the assignments of Administrative Domain numbers (ADs) for version 7 of the Internet. This document is an Internet Draft. Internet Drafts are working documents of the Internet Engineering Task Force (IETF), its Areas, and its Working Groups. (Note that other groups may also distribute working documents as Internet Drafts). Internet Drafts are draft documents valid for a maximum of six months. Internet Drafts may be updated, replaced, or obsoleted by other documents at any time. It is not appropriate to use Internet Drafts as reference material or to cite them other than as a "working draft" or "work in progress." Please check the I-D abstract listing contained in each Internet Draft directory to learn the current status of this or any other Internet Draft. Ullmann DRAFT: expires November 24, 1993 [page 1] Internet draft Initial AD Assignment Plan May 26, 1993 2 Contents 1 Status of this Memo . . . . . . . . . . . . . . . . 1 2 Contents . . . . . . . . . . . . . . . . . . . . . . 2 3 Introduction . . . . . . . . . . . . . . . . . . . . 3 4 Authority for AD assignments . . . . . . . . . . . . 3 4.1 IANA . . . . . . . . . . . . . . . . . . . . . . . 3 4.2 ISO/ITU . . . . . . . . . . . . . . . . . . . . . 3 5 Country blocks . . . . . . . . . . . . . . . . . . . 4 6 Initial IANA block . . . . . . . . . . . . . . . . . 4 6.1 Version 4 Zone . . . . . . . . . . . . . . . . . . 4 7 Novell IPX . . . . . . . . . . . . . . . . . . . . . 5 8 IEEE 802 block . . . . . . . . . . . . . . . . . . . 5 9 Code table . . . . . . . . . . . . . . . . . . . . . 7 10 References . . . . . . . . . . . . . . . . . . . . 12 11 Author's Address . . . . . . . . . . . . . . . . . 12 Ullmann DRAFT: expires November 24, 1993 [page 2] Internet draft Initial AD Assignment Plan May 26, 1993 3 Introduction This memo presents the plan for initial assignments of Administrative Domain numbers for the Version 7 Internet. The objective is to use a very small amount of space in the numbering system, while providing the necessary distribution of authority. This plan defines 5/256ths of the number space, while making initial AD-block assignments covering only 239/65536ths (0.36%) of the code points available in the most significant 16 bits. It is important that future plans be equally conservative; in the next decade no more than 1/25th of the space need be or should be assigned. Besides the always-unanticipated future expansion, this provides the space to re-do the numbering plan entirely if it should become necessary. It is certainly true that in 10 years, or 25 years, we shall know a great deal more about what the numbering plan should look like, and it is prudent to leave as much of the decision as possible to that time. 4 Authority for AD assignments 4.1 IANA The initial authority for AD assignements is IANA, the Internet Assigned Numbers Authority (IANA@ISI.EDU) The IANA will delegate national blocks with initial octets 120 to 123 in the numbering plan to national authority when applied for by an appropriate organization. The initial AD plan also includes specific assignments of blocks with initial octet 126, for interoperation with existing internetworking protocols. Three non-national blocks are delegated in the initial numbering plan, one (back to) IANA, one to Novell/IPX, and one used for IEEE 802 addressing. Individual AD numbers should be assigned only when there is an expectation that the delegated authority will need to assign on the order of a million network numbers (an AD has space for 16 million networks), or where a clear division of authority is required (e.g. a national administration). Note that under the first of those qualifications, the entire present Internet qualifies as only one AD. 4.2 ISO/ITU Authority for assignments of ADs should eventually be vested in the proper international organization, either the ITU and/or the ISO. This is probably an issue that should eventually be taken up by the proper committee of the Joint Technical Committee (JTC). At present, the AD plan borrows an existing numbering plan for countries, IS 3166. This plan provides for two-letter, three-letter, and three-digit codes for countries, where a country is a member of the UN, or a (possibly disputed) territory or other area recognized by the UN. (Note that this includes the idea of the UN simply Ullmann DRAFT: expires November 24, 1993 [page 3] Internet draft Initial AD Assignment Plan May 26, 1993 recognizing that the area is disputed; see the entity coded "NT" in the 1988 two-letter code.) The Internet already uses IS 3166 as the authority for the two-letter top-level names used in the domain naming system to delegate naming to national authority. 5 Country blocks Each country (using the definitions of IS 3166) is assigned a block of 256 AD numbers, i.e. a 16 bit number at the top of the numbering plan. The specific block number is derived from the three digit code (ISO-3) assigned by IS 3166. The first octet has value 120 plus ISO-3 divided by 250. The second octet has the value ISO-3 modulo 250. This assigns AD blocks in the range 120.0 to 123.249. The fact that this assigns "large" blocks in some cases to very small countries is not considered to be important. (Rather, the premise that all countries should have equal "importance" in the numbering system is considered paramount.) This is not a geographical assignment system. The assignments are administrative, delegated to national authority. A network assigned within a country-derived AD may be physically located anywhere. While it is advisable for a country to assign individual ADs, there is nothing to preclude a national plan using the entire country block; that decision is specifically reserved to the national authority. The question as to whether the numbering plan within the ADs or block should be correlated with topology, geography, or other constraints is also reserved to national authority. It should be kept in mind that the DNS architecture requires that major authority delegations be made on octet boundaries. Certain large countries may need additional block assignments eventually. If the ISO or ITU authority is established at that time, assignments will be made by the appropriate procedure within ISO and/or the ITU. If not, the national authority should apply to the IANA, requesting information on where and how to proceed. 6 Initial IANA block The block authority for AD numbers beginning with 126.0 is assigned to IANA for individual AD assignements with international scope. Only one of the ADs in this block, 126.0.0, is presently assigned. 6.1 Version 4 Zone The AD 126.0.0 is assigned to the present Version 4 numbering plan. This AD has a specific plan for assignments within it: the first 24 bits are the AD (126.0.0), the next 8-24 bits are a network number, each assigned to a specific organization, and the remaining 16-40 bits are assigned to subnets and hosts by authority reserved to the specific organization. Ullmann DRAFT: expires November 24, 1993 [page 4] Internet draft Initial AD Assignment Plan May 26, 1993 7 Novell IPX The internetwork protocol (IPX) used by products of Novell Corporation and other vendors making interoperable software have used a 32-bit LAN network number, implicitly concatenated with the 48 bit MAC layer address to form an internet address. The network numbers were not assigned by any central authority, and thus were not useful for inter-organizational traffic without substantial prior arrangement. There is now an authority, established by Novell, to assign unique 32-bit numbers and blocks of numbers, to organizations that desire the ability to do inter-organization networking with the IPX protocol. Novell has also standardized the encapsulation of IPX over the Internet Protocol. [RFC1234] The Novell/IPX numbering plan is assigned the block 126.1 within the Version 7 numbering plan. It has a specific structure for numbering within the block: the first 16 bits are the Novell/IPX block number (126.1), the next 32 bits are the unique network number assigned to the LAN, and the last 16 bits are a host number assigned, probably by a (to be specified) dynamic method within the LAN. The existance of a number within the Novell/IPX block for a host does not imply that the host is Novell protocol capable, the number is equally useful for both IP version 7 and IPX. The dynamic method for local address assignment might be specific to IPX, or it might be the general method used for any IPv7 local network with 16 bits of host number. While the assignment of a block, rather than a single AD number, is exceptional, in view of the very large base of Novell systems it seems reasonable to accomodate the 32-bit IPX network numbers directly. In particular, RAP can be used to route IPv4, IPv7, and IPX/IPv7 traffic in a combined network. 8 IEEE 802 block The IEEE block provides a local address for any host with a LAN interface. The address format is fixed: the first 16 bits are the block number, 126.2, the remaining 48 bits are the address assigned to the host (or interface card, which is more typical). The 802 address is in canonical bit order [ref tbs]. Because addresses in this block do not have any useable struture, the host is unlikely to be able to communicate beyond the local network. The routing protocol may propagate routes to individual hosts a short distance (i.e. into adjacent LANs) but is unlikely to advertise them very widely. Ullmann DRAFT: expires November 24, 1993 [page 5] Internet draft Initial AD Assignment Plan May 26, 1993 The primary use for addresses in this block is to give hosts an immediately useable address, without any prior configuration. This permits the host to then initiate an auto-configuration protocol with a local net manager, authenticate itself, and find out or register its name and/or wide area Internet address. It also provides a permanent address for simple hosts that do not want to communicate off of the LAN, such as a toaster. It does not provide actual security, and MUST NOT be used in an attempt to prevent access except (e.g.) via an application relay: the routing protocol(s) MAY propagate a route to the host an arbitrary distance. Hosts that begin with an 802 derived address and then do autoconfiguration SHOULD continue to recognize the address after the configuration is complete, and MAY originate new traffic from that address. Hosts using an address in this block MUST be capable of replying to ARP requests, and hosts tring to reach such a host MUST use ARP (or other defined ES-IS-like protocol) to resolve the address (and, implicitly, determine which interface to use to reach the other host), they MUST NOT extract the 802 address from the IPv7 address. Digression: note that there is a presumption here that it is reasonable behavior for any host or router to ARP for an address that it has no particular route for. In the presence of general proxy-ARP, this is indeed a reasonable idea, given that someone out there may be able to reply. This means that a TP/IX-IPv7 host need not necessarily give addresses in this block special treatment in the IP layer route resolution. In the future, as "addresses" are pushed more toward the proper role as endpoint-identifiers, and not used to route datagrams, this block may become more useful. Ullmann DRAFT: expires November 24, 1993 [page 6] Internet draft Initial AD Assignment Plan May 26, 1993 9 Code table Admin Domain Block ISO-3 Country 0 to 119 [reserved] 120.004 004 AF Afghanistan 120.008 008 AL Albania 120.010 010 AQ Antarctica 120.012 012 DZ Algeria 120.016 016 AS American Samoa 120.020 020 AD Andorra 120.024 024 AO Angola 120.028 028 AG Antigua And Barbuda 120.031 031 AZ Azerbaijan 120.032 032 AR Argentina 120.036 036 AU Australia 120.040 040 AT Austria 120.044 044 BS Bahamas 120.048 048 BH Bahrain 120.050 050 BD Bangladesh 120.051 051 AM Armenia 120.052 052 BB Barbados 120.056 056 BE Belgium 120.060 060 BM Bermuda 120.064 064 BT Bhutan 120.068 068 BO Bolivia [tba by UN] BA Bosnia Hercegovina 120.072 072 BW Botswana 120.074 074 BV Bouvet Island 120.076 076 BR Brazil 120.084 084 BZ Belize 120.086 086 IO British Indian Ocean Territory 120.090 090 SB Solomon Islands 120.092 092 VG Virgin Islands (British) 120.096 096 BN Brunei Darussalam 120.100 100 BG Bulgaria 120.104 104 MM Myanmar 120.108 108 BI Burundi 120.112 112 BY Belarus 120.112 112 BY Byelorussian Ssr 120.116 116 KH Cambodia 120.120 120 CM Cameroon 120.124 124 CA Canada 120.132 132 CV Cape Verde 120.136 136 KY Cayman Islands 120.140 140 CF Central African Republic 120.144 144 LK Sri Lanka 120.148 148 TD Chad 120.152 152 CL Chile 120.156 156 CN China 120.158 158 TW Taiwan, Province Of China 120.162 162 CX Christmas Island 120.166 166 CC Cocos (Keeling) Islands 120.170 170 CO Colombia Ullmann DRAFT: expires November 24, 1993 [page 7] Internet draft Initial AD Assignment Plan May 26, 1993 120.174 174 KM Comoros 120.178 178 CG Congo 120.180 180 ZR Zaire 120.184 184 CK Cook Islands 120.188 188 CR Costa Rica [tba by UN] HR Croatia (Hrvatska) 120.192 192 CU Cuba 120.196 196 CY Cyprus 120.200 200 CS Czechoslovakia 120.204 204 BJ Benin 120.208 208 DK Denmark 120.212 212 DM Dominica 120.214 214 DO Dominican Republic 120.218 218 EC Ecuador 120.222 222 SV El Salvador 120.226 226 GQ Equatorial Guinea [tba by UN] [tba] Eritrea 120.230 230 ET Ethiopia 120.233 233 EE Estonia 120.234 234 FO Faroe Islands 120.238 238 FK Falkland Islands (Malvinas) 120.242 242 FJ Fiji 120.246 246 FI Finland 121.000 250 FR France 121.004 254 GF French Guiana 121.008 258 PF French Polynesia 121.010 260 TF French Southern Territories 121.012 262 DJ Djibouti 121.016 266 GA Gabon 121.018 268 GE Georgia 121.020 270 GM Gambia 121.026 276 DE Germany 121.038 288 GH Ghana 121.042 292 GI Gibraltar 121.046 296 KI Kiribati 121.050 300 GR Greece 121.054 304 GL Greenland 121.058 308 GD Grenada 121.062 312 GP Guadeloupe 121.066 316 GU Guam 121.070 320 GT Guatemala 121.074 324 GN Guinea 121.078 328 GY Guyana 121.082 332 HT Haiti 121.084 334 HM Heard And Mc Donald Islands 121.086 336 VA Vatican City State (Holy See) 121.090 340 HN Honduras 121.094 344 HK Hong Kong 121.098 348 HU Hungary 121.102 352 IS Iceland 121.106 356 IN India 121.110 360 ID Indonesia 121.114 364 IR Iran (Islamic Republic Of) 121.118 368 IQ Iraq 121.122 372 IE Ireland Ullmann DRAFT: expires November 24, 1993 [page 8] Internet draft Initial AD Assignment Plan May 26, 1993 121.126 376 IL Israel 121.130 380 IT Italy 121.134 384 CI Cote D'Ivoire 121.138 388 JM Jamaica 121.142 392 JP Japan 121.148 398 KZ Kazakhstan 121.150 400 JO Jordan 121.154 404 KE Kenya 121.158 408 KP Korea, Democratic People's Republic Of 121.160 410 KR Korea, Republic Of 121.164 414 KW Kuwait 121.167 417 KG Kyrgyzstan 121.168 418 LA Lao People's Democratic Republic 121.172 422 LB Lebanon 121.176 426 LS Lesotho 121.178 428 LV Latvia 121.180 430 LR Liberia 121.184 434 LY Libyan Arab Jamahiriya 121.188 438 LI Liechtenstein 121.190 440 LT Lithuania 121.192 442 LU Luxembourg 121.196 446 MO Macau 121.200 450 MG Madagascar 121.204 454 MW Malawi 121.208 458 MY Malaysia 121.212 462 MV Maldives 121.216 466 ML Mali 121.220 470 MT Malta 121.224 474 MQ Martinique 121.228 478 MR Mauritania 121.230 480 MU Mauritius 121.234 484 MX Mexico 121.242 492 MC Monaco 121.246 496 MN Mongolia 121.248 498 MD Moldova, Republic Of 122.000 500 MS Montserrat 122.004 504 MA Morocco 122.008 508 MZ Mozambique 122.012 512 OM Oman 122.016 516 NA Namibia 122.020 520 NR Nauru 122.024 524 NP Nepal 122.028 528 NL Netherlands 122.032 532 AN Netherlands Antilles 122.033 533 AW Aruba 122.036 536 NT Neutral Zone 122.040 540 NC New Caledonia 122.048 548 VU Vanuatu 122.054 554 NZ New Zealand 122.058 558 NI Nicaragua 122.062 562 NE Niger 122.066 566 NG Nigeria 122.070 570 NU Niue 122.074 574 NF Norfolk Island 122.078 578 NO Norway Ullmann DRAFT: expires November 24, 1993 [page 9] Internet draft Initial AD Assignment Plan May 26, 1993 122.080 580 MP Northern Mariana Islands 122.081 581 UM United States Minor Outlying Islands 122.083 583 FM Micronesia 122.084 584 MH Marshall Islands 122.085 585 PW Palau 122.086 586 PK Pakistan 122.090 590 PA Panama 122.098 598 PG Papua New Guinea 122.100 600 PY Paraguay 122.104 604 PE Peru 122.108 608 PH Philippines 122.112 612 PN Pitcairn 122.116 616 PL Poland 122.120 620 PT Portugal 122.124 624 GW Guinea-Bissau 122.126 626 TP East Timor 122.130 630 PR Puerto Rico 122.134 634 QA Qatar 122.138 638 RE Reunion 122.142 642 RO Romania 122.143 643 RU Russian Federation 122.146 646 RW Rwanda 122.154 654 SH St. Helena 122.159 659 KN Saint Kitts And Nevis 122.160 660 AI Anguilla 122.162 662 LC Saint Lucia 122.166 666 PM St. Pierre And Miquelon 122.170 670 VC Saint Vincent And The Grenadines 122.174 674 SM San Marino 122.178 678 ST Sao Tome And Principe 122.182 682 SA Saudi Arabia 122.186 686 SN Senegal 122.190 690 SC Seychelles 122.194 694 SL Sierra Leone 122.202 702 SG Singapore [tba by UN] SI Slovenia 122.204 704 VN Viet Nam 122.206 706 SO Somalia 122.210 710 ZA South Africa 122.216 716 ZW Zimbabwe 122.224 724 ES Spain 122.232 732 EH Western Sahara 122.236 736 SD Sudan 122.240 740 SR Suriname 122.244 744 SJ Svalbard And Jan Mayen Islands 122.248 748 SZ Swaziland 123.002 752 SE Sweden 123.006 756 CH Switzerland 123.010 760 SY Syrian Arab Republic 123.012 762 TJ Tajikistan 123.014 764 TH Thailand 123.018 768 TG Togo 123.022 772 TK Tokelau 123.026 776 TO Tonga 123.030 780 TT Trinidad And Tobago Ullmann DRAFT: expires November 24, 1993 [page 10] Internet draft Initial AD Assignment Plan May 26, 1993 123.034 784 AE United Arab Emirates 123.038 788 TN Tunisia 123.042 792 TR Turkey 123.045 795 TM Turkmenistan 123.046 796 TC Turks And Caicos Islands 123.048 798 TV Tuvalu 123.050 800 UG Uganda 123.054 804 UA Ukrainian Ssr 123.060 810 SU Ussr 123.068 818 EG Egypt 123.076 826 GB United Kingdom 123.084 834 TZ Tanzania, United Republic Of 123.090 840 US United States 123.100 850 VI Virgin Islands (U.S.) 123.104 854 BF Burkina Faso 123.108 858 UY Uruguay 123.110 860 UZ Uzbekistan 123.112 862 VE Venezuela 123.126 876 WF Wallis And Futuna Islands 123.132 882 WS Samoa 123.137 887 YE Yemen, Republic Of 123.140 890 YU Yugoslavia 123.144 894 ZM Zambia 126.000 IANA/InterNIC 126.001 Novell IPX 126.002 IEEE 802 127 to 255 [reserved] Ullmann DRAFT: expires November 24, 1993 [page 11] Internet draft Initial AD Assignment Plan May 26, 1993 10 References [IS 3166] International Organization for Standardization. Codes for the Representation of Names of Countries. ISO 3166, ISO, 1988. [RFC1234] D. Provan. Tunneling IPX Traffic through IP Networks. Novell, Inc. June, 1991. [ID-TPIX] Robert Ullmann. TP/IX: The Next Internet. Internet draft: unpublished at this writing. March, 1993. [ID-RAP] Robert Ullmann. RAP: Internet Route Access Protocol. Internet draft: unpublished at this writing. March, 1993. 11 Author's Address Robert Ullmann Process Software Corporation 959 Concord Street Framingham, MA 01701 USA Phone: +1 508 879 6994 x226 Email: Ariel@Process.COM Ullmann DRAFT: expires November 24, 1993 [page 12] From tpix-request@world.std.com Fri May 28 13:07:18 1993 Received: by world.std.com (5.65c/Spike-2.0) id AA18668; Fri, 28 May 1993 13:07:15 -0400 Errors-To: tpix-request@world.std.com Sender: tpix-request@world.std.com Reply-To: tpix@world.std.com Precedence: bulk Return-Path: <gvaudre@CNRI.Reston.VA.US> Received: from IETF.nri.reston.VA.US (ietf.cnri.reston.va.us) by world.std.com (5.65c/Spike-2.0) id AA18656; Fri, 28 May 1993 13:07:13 -0400 Received: from [127.0.0.1] by IETF.CNRI.Reston.VA.US id aa08335; 28 May 93 12:01 EDT X-Org: Corp. for National Research Initiatives X-Phone: (703) 620-8990 ; Fax: (703) 620-0913 To: IETF-Announce:@CNRI.Reston.VA.US ; Cc: tpix@world.std.com Subject: WG ACTION: TP/IX (tpix) Date: Fri, 28 May 93 12:01:48 -0400 From: Greg Vaudreuil <gvaudre@CNRI.Reston.VA.US> Message-Id: <9305281201.aa08335@IETF.CNRI.Reston.VA.US> Status: R A new working group has been formed in the Internet Area of the IETF. Please contact the working group chair or the Internet area directors for more information. Greg Vaudreuil IESG Secretary TP/IX (tpix) ------------ Charter Chair(s): Vladimir Sukonnik <sukonnik@process.com> Internet Area Director(s) Stev Knowles <stev@ftp.com> David Piscitello <dave@mail.bellcore.com> Mailing lists: General Discussion:tpix@world.std.com To Subscribe: tpix-request@world.std.com Archive: world.std.com:~/pub/tpix/* Description of Working Group: TP/IX is a new version of the IP and TCP/UDP protocols, to advance the Internet technology to the scale and performance of the next generation of internetwork technology. TP/IX has been assigned the IP Protocol Identifier 7. The Working Group is chartered to review the TP/IX and RAP protocols, evaluate issues arising during product development and deployment planning, and to document problems and explanations for any parts of the coexistance with IPv4 not covered directly in the TP/IX-IPv4 interoperation design. The WG will also be the initial forum for development of the RAP protocol while it is experimental; this work will need to be moved to the Routing Area when it is to be advanced. Goals and Milestones: Done Present the TP/IX and the RAP protocols to the IETF Plenary. May 93 Post the TP/IX Protocol and the RAP protocol as Experimental RFCs. Jul 93 Hold Working Group meeting to discuss additional definitions. Prepare criteria to be met prior to standardization. Nov 93 Hold Working Group meeting to evaluate the TP/IX and RAP protocols for Proposed Standard. Dec 93 Submit the TP/IX and RAP Protocols to the IESG for consideration as a Proposed Standard. From tpix-request@world.std.com Fri May 28 13:36:04 1993 Received: by world.std.com (5.65c/Spike-2.0) id AA24460; Fri, 28 May 1993 13:35:55 -0400 Errors-To: tpix-request@world.std.com Sender: tpix-request@world.std.com Reply-To: tpix@world.std.com Precedence: bulk Return-Path: <deering@parc.xerox.com> Received: from alpha.Xerox.COM by world.std.com (5.65c/Spike-2.0) id AA24425; Fri, 28 May 1993 13:35:49 -0400 Received: from skylark.parc.xerox.com ([13.2.116.7]) by alpha.xerox.com with SMTP id <11721>; Fri, 28 May 1993 10:31:22 PDT Received: from localhost by skylark.parc.xerox.com with SMTP id <12171>; Fri, 28 May 1993 10:31:15 -0700 To: tpix@world.std.com Subject: Re: WG ACTION: TP/IX (tpix) In-Reply-To: Your message of "Fri, 28 May 93 09:01:48 PDT." <9305281201.aa08335@IETF.CNRI.Reston.VA.US> Date: Fri, 28 May 1993 10:31:05 PDT From: Steve Deering <deering@parc.xerox.com> Message-Id: <93May28.103115pdt.12171@skylark.parc.xerox.com> Status: R > Description of Working Group: > > TP/IX is a new version of the IP and TCP/UDP protocols, to > advance the Internet technology to the scale and performance of > the next generation of internetwork technology. TP/IX has been > assigned the IP Protocol Identifier 7. Shouldn't that be IP Version number 7, not Protocol Identifier 7? IP Protocol numbers identify transport protocols. Steve
- Amsterdam WG query Robert L Ullmann
- Re: Amsterdam WG query Fred Baker
- Amsterdam WG query yakov
- RE: Amsterdam WG query Al Costanzo