Re: Criteria for selecting IPv7
Jon Crowcroft <J.Crowcroft@cs.ucl.ac.uk> Tue, 27 October 1992 17:48 UTC
Received: from NRI.RESTON.VA.US by IETF.NRI.Reston.VA.US id aa03945; 27 Oct 92 12:48 EST
Received: from munnari.OZ.AU by NRI.Reston.VA.US id aa11351; 27 Oct 92 12:48 EST
Received: by munnari.oz.au (5.83--+1.3.1+0.50) id AA20757; Wed, 28 Oct 1992 03:13:49 +1100 (from owner-Big-Internet)
Received: from mulga.cs.mu.OZ.AU by munnari.oz.au with SMTP (5.83--+1.3.1+0.50) id AA20753; Wed, 28 Oct 1992 03:13:42 +1100 (from J.Crowcroft@cs.ucl.ac.uk)
Received: from bells.cs.ucl.ac.uk by mulga.cs.mu.OZ.AU with SMTP (5.64+1.3.1+0.50); id AA28107 Wed, 28 Oct 1992 03:12:03 +1100 (from J.Crowcroft@cs.ucl.ac.uk)
Message-Id: <9210271612.28107@mulga.cs.mu.OZ.AU>
Received: from waffle.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id <g.21529-0@bells.cs.ucl.ac.uk>; Tue, 27 Oct 1992 16:08:26 +0000
To: Craig Partridge <craig@aland.bbn.com>
Cc: big-internet@munnari.oz.au
Subject: Re: Criteria for selecting IPv7
Date: Tue, 27 Oct 1992 16:08:23 +0000
From: Jon Crowcroft <J.Crowcroft@cs.ucl.ac.uk>
Status: O
craig, io've tried applying your criteria to the current options - this is a quick hack, and people are welcome to disagree, one thing that is clear is you need ease of interworking as well as ease of transition. disclaimer - this _definitely_ reflects my biases and ignorances, just wanted to see if it could be done a bit! ===================> The Solutions judged by the Partridge Criteria ---------------------------------------------- 2TIER RFC 1335 Wang, Z. A Two-Tier Address Structure Crowcroft, J. for the Internet: A Solution to the Problem of Address Space Exhaustion rfc/rfc1335.txt 2TIER dynamically allocates globally unique addrs to hosts when they wish to do non-local communication Essential: 1. EasyTransition yes 2. 10**10 Hosts yes 3. LessthanLinearRouteGrowth 10**9 nets sort of 4. 3bps<LINKSPEEDS<3Tbps irrelevant 5. Datagrams - yes 6. *Cast - yesish 7. Costrecovery - no Desirable: 8. meetQOS - no 9. Mobile - no 10. ?NLSP - no 11. Plug&Play - sort of 12. PolicyRoutes - hard ---------------------------------------------- NAT The IP Network Address Tsuchiya, P. Translator (Nat): Preliminary Design internet-drafts/draft-tsuchiya-addrtrans-00.txt NAT (and unreleased CNAT) are IP address re-writing gatwqay solutions to address space problem - i.e. local addresses saty local, gateways dynamically form maps for internal to esxternal addresses Essential: 1. EasyTransition - yes 2. 10**10 Hosts - yes 3. LessthanLinearRouteGrowth 10**9 nets- yes 4. 3bps<LINKSPEEDS<3Tbps - yes 5. Datagrams = yes 6. *Cast - ? 7. Costrecovery - no Desirable: 8. meetQOS - no 9. Mobile - no 10. ?NLSP - no 11. Plug&Play - sort of 12. PolicyRoutes - maybe (see CNAT?) =============================================================================== IPv7 IP Version 7 IAB internet-drafts/draft-iab-ipversion7-00.txt the IAB CLNP "announcement" see also, ISO 8473, ES-IS and ISIS, at least TUBA RFC 1347 Callon, R. TCP and UDP with Bigger Addresses (TUBA), A Simple Proposal for Internet Addressing and Routing rfc/rfc1347.txt TUBA2 Use of ISO CLNP in TUBA Piscitello, D. Environments internet-drafts/draft-piscitello-clnp-00.txt TUBA & TUBA2 provide TCP and other Internet protocols on CLNP one way or another... NSAP RFC 1237 Colella, R. Guidelines for OSI NSAP Gardner, E. Allocation in the Internet Callon, R. rfc/rfc1237.txt A scheme to go with CLNP and TUBA Essential: 1. EasyTransition - No 2. 10**10 Hosts - Yes 3. LessthanLinearRouteGrowth 10**9 nets - Yes 4. 3bps<LINKSPEEDS<3Tbps - Probably 5. Datagrams - yes 6. *Cast - not yet 7. Costrecovery - maybe Desirable: 8. meetQOS - no more than IP 9. Mobile - no 10. ?NLSP - maybe (see NLSP) 11. Plug&Play - no more than IP 12. PolicyRoutes - yes, see IDRP =============================================================================== EIP The Extended Internet Protocol Wang, Z. a long-term solution to Internet address exhaustion internet-drafts/draft-wang-extended-ip-00.txt An extended address IP migration/replacement In the process of sort of merging with PIP (see below) Essential: 1. EasyTransition - yes 2. 10**10 Hosts - yes 3. LessthanLinearRouteGrowth 10**9 nets - yes 4. 3bps<LINKSPEEDS<3Tbps - yes, modulo option speedup 5. Datagrams - yes 6. *Cast - yes 7. Costrecovery - no Desirable: 8. meetQOS - no 9. Mobile - no 10. ?NLSP - no 11. Plug&Play - yes 12. PolicyRoutes - ? IPAE A Proposal for IP Address Hinden, R. Encapsulation (IPAE): A Crocker, D. Compatible Version of IP with Large Addresses internet-drafts/draft-crocker-ip-encaps-00.txt An Address Encapsulating IP migration/replacement Also in the process sort of merging with SIP (see below) Essential: 1. EasyTransition - yes 2. 10**10 Hosts - yes 3. LessthanLinearRouteGrowth 10**9 nets - yes 4. 3bps<LINKSPEEDS<3Tbps - yes 5. Datagrams - yes 6. *Cast - yes 7. Costrecovery - no Desirable: 8. meetQOS - no 9. Mobile - no 10. ?NLSP - no 11. Plug&Play - no more than IP 12. PolicyRoutes - no more than IP =============================================================================== Uv7 TCP/IP: Internet Version 7 Ullmann, R. internet-drafts/draft-ullmann-ipv7-00.txt another clean and simple scheme for replacement IP Essential: 1. EasyTransition - ok 2. 10**10 Hosts - yes 3. LessthanLinearRouteGrowth 10**9 nets - yes 4. 3bps<LINKSPEEDS<3Tbps - ? 5. Datagrams - yes 6. *Cast - ? 7. Costrecovery - ? Desirable: 8. meetQOS - ? 9. Mobile - ? 10. ?NLSP - ? 11. Plug&Play - ? 12. PolicyRoutes - ? =============================================================================== PIP Pip: The `P' Internet Protocol Tsuchiya, P. internet-drafts/draft-tsuchiya-pip-00.txt PIP2 Pip Overview and Examples Tsuchiya, P. internet-drafts/draft-tsuchiya-pip-overview-01.txt PIP & PIP2 are about brand new IP replacement which incorprates many of the ideas needed for neat policy and other routing... Essential: 1. EasyTransition - no, modulo EIP plans 2. 10**10 Hosts - yes 3. LessthanLinearRouteGrowth 10**9 nets - yes 4. 3bps<LINKSPEEDS<3Tbps - yes 5. Datagrams - yes 6. *Cast - yes 7. Costrecovery - maybe Desirable: 8. meetQOS - yes 9. Mobile - maybe 10. ?NLSP - yes 11. Plug&Play - no 12. PolicyRoutes - yes SIP SIP: A Simple Internet Deering, S. Protocol parcftp.xerox.com:pub/net-research/sip-spec SIP is an enlarged IP - based on optimising for forwarding path Essential: 1. EasyTransition - no, modulo IPAE plans 2. 10**10 Hosts - yes 3. LessthanLinearRouteGrowth 10**9 nets - yes 4. 3bps<LINKSPEEDS<3Tbps - yes 5. Datagrams - yes 6. *Cast - yes 7. Costrecovery - no Desirable: 8. meetQOS - yes 9. Mobile - no 10. ?NLSP - no 11. Plug&Play - no more than IP 12. PolicyRoutes - maybe
- Criteria for selecting IPv7 Craig Partridge
- Re: Criteria for selecting IPv7 Dennis Perry
- Re: Criteria for selecting IPv7 Noel Chiappa
- re: Criteria for selecting IPv7 Craig Partridge
- Re: Criteria for selecting IPv7 leo j mclaughlin iii
- re: Criteria for selecting IPv7 Craig Partridge
- Re: Criteria for selecting IPv7 John Curran
- re: Criteria for selecting IPv7 leo j mclaughlin iii
- Re: Criteria for selecting IPv7 peter
- Re: Criteria for selecting IPv7 Phill Gross
- Re: Criteria for selecting IPv7 Bernhard Stockman
- Re: Criteria for selecting IPv7 Bernhard Stockman
- re: Criteria for selecting IPv7 Brian Carpenter CERN-CN
- Re: Criteria for selecting IPv7 C. Harald Koch
- Re: Criteria for selecting IPv7 Jon Crowcroft
- Re: Criteria for selecting IPv7 Deborah Estrin
- re: Re: Criteria for selecting IPv7 Ross Callon
- Re: Criteria for selecting IPv7 Brian Carpenter CERN-CN
- Re: Criteria for selecting IPv7 Dave Crocker
- Re: Criteria for selecting IPv7 - holy grails & p… Jon Crowcroft
- re: Criteria for selecting IPv7 Craig Partridge
- Re: Criteria for selecting IPv7 Noel Chiappa
- Re: Criteria for selecting IPv7 John Curran
- Re: Criteria for selecting IPv7 Scott_Brim
- Re: Criteria for selecting IPv7 Craig Partridge
- Re: Criteria for selecting IPv7 dave
- Re: Criteria for selecting IPv7 Craig Partridge
- Re: Criteria for selecting IPv7 Scott_Brim
- Re: Criteria for selecting IPv7 Craig Partridge
- Re: Criteria for selecting IPv7 Frank Kastenholz
- Re: Criteria for selecting IPv7 Frank Kastenholz