Discussion of explicit congestion notification's impact on the Internet
 help / color / mirror / Atom feed
From: Pete Heist <pete@heistp.net>
To: ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: [Ecn-sane] IPv5
Date: Wed, 31 Mar 2021 09:16:01 +0200	[thread overview]
Message-ID: <880920d70c014664d8bf49d023ebfa1895ead887.camel@heistp.net> (raw)

Since April 1 is upon us, I thought I'd let the list know that the ECN
debate has finally been resolved, pending a few details to work out...

IPv5
====

Codename: IP "Regret"

# Header Format

-----------------------------------------------------------------
|  Ver  |       Reserved        |   Protocol   |   Hop Limit    |
-----------------------------------------------------------------
|         Payload Length        |          Flow Label           |
-----------------------------------------------------------------
|                                                               |
|                        Source Address                         |
|                                                               |
-----------------------------------------------------------------
|                                                               |
|                      Destination Address                      |
|                                                               |
-----------------------------------------------------------------

(Ver)sion (4 bits):
  Protocol version, set to 5

Reserved (12 bits):
  Reserved for fun, MBZ on open Internet

Protocol (1 byte):
  Protocol number as per IANA

Hop Limit (1 byte):
  As per IPv6

Payload Length (16 bits):
  Length of payload- fragmentation not supported

Flow Label (16 bits):
  Flow label- next to addresses for fast hashing

Source Address (8 bytes):
  64-bit source address

Destination Address (8 bytes):
  64-bit destination address

# Rationale

* provides more than adequate address space
* reduces IPv6 complexity
* reduces header size to 24 bytes, down from 40 for IPv6
* leaves 12 bits of header space for experiments and future use
* makes the Internet fun again



             reply	other threads:[~2021-03-31  7:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-31  7:16 Pete Heist [this message]
2021-03-31 10:55 ` Vint Cerf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/ecn-sane.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=880920d70c014664d8bf49d023ebfa1895ead887.camel@heistp.net \
    --to=pete@heistp.net \
    --cc=ecn-sane@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox