Re: [Int-area] [ih] Fwd: Existing use of IP protocol 114 (any 0-hop protocol)

John Gilmore <gnu@toad.com> Fri, 20 September 2019 00:02 UTC

Return-Path: <gnu@toad.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8238120052 for <int-area@ietfa.amsl.com>; Thu, 19 Sep 2019 17:02:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DBiUnoYjh4Qf for <int-area@ietfa.amsl.com>; Thu, 19 Sep 2019 17:02:20 -0700 (PDT)
Received: from hop.toad.com (75-101-100-43.dsl.static.fusionbroadband.com [75.101.100.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1CFBC120043 for <int-area@ietf.org>; Thu, 19 Sep 2019 17:02:17 -0700 (PDT)
Received: from hop.toad.com (localhost [127.0.0.1]) by hop.toad.com (8.12.9/8.12.9) with ESMTP id x8K024Ro000417; Thu, 19 Sep 2019 17:02:04 -0700
To: internet-history@postel.org, Brian E Carpenter <brian.e.carpenter@gmail.com>
cc: int-area@ietf.org, evyncke@cisco.com, gnu@toad.com
In-reply-to: <88ec7bdb-57e7-5966-6deb-b9e9ba8d7b67@gmail.com>
References: <D6BD6D0F-9504-4533-BCFD-A79B2357BC96@cisco.com> <88ec7bdb-57e7-5966-6deb-b9e9ba8d7b67@gmail.com>
Comments: In-reply-to Brian E Carpenter <brian.e.carpenter@gmail.com> message dated "Fri, 20 Sep 2019 09:27:07 +1200."
Date: Thu, 19 Sep 2019 17:02:04 -0700
Message-ID: <416.1568937724@hop.toad.com>
From: John Gilmore <gnu@toad.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/Yl4UemfxS-Nsd3FDYATFN7Et8iY>
Subject: Re: [Int-area] [ih] Fwd: Existing use of IP protocol 114 (any 0-hop protocol)
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Sep 2019 00:02:22 -0000

Protocol 114 was unassigned in RFC 1700 in Oct 1994, which was the last
RFC tabulating protocol assignments.  In January 2002, RFCs ceased being
published for protocol number assignments, according to RFC 3232.
Sometime before Feb 1999, protocol 114 was assigned here:

  https://web.archive.org/web/19990203044112/http://www.isi.edu/in-notes/iana/assignments/protocol-numbers
  
The original IANA, Jon Postel, died on October 16, 1998.  There was some
turmoil in the relevant websites at the time.  The Internet Archive's
Wayback Machine does not appear to have captured the IANA.org or isi.edu
websites during an earlier time when this protocol number was not
assigned.  But, only five assignments in Feb 1999 had followed 114; the
next one was L2TP (protocol 115) by Bernard Aboba (April 1998).  The
preceding one was PGM (protocol 113) by Tony Speakman in January 1998.
So it's a pretty good bet that it was assigned by Postel between January
and April 1998.

(L2TP was documented in RFC 2661 of August 1999, and by that point it was
not using protocol #115; it ran over IP and UDP on port 1701.  A later
2005 evolution of L2TP, L2TPv3, used protocol 115.)

Does anyone have archives of the TCP-IP Distribution List from 1998?
The only copy I have found so far is at
http://securitydigest.org/tcp-ip/ but it ends in 1994 (with no apparent
"we're closing down the list" messages).

A separate issue:

Having read the draft-zhu-intarea-gma-03.txt, and skimmed the 2017
draft-kanugovi-intarea-mams-protocol-03 that it references, I don't see
how this protocol could in any way be seen as a 0-hop protocol.  The
whole design is to provide multiple paths to the Internet, which would
require that the relevant packets traverse routers.  The MAMS draft
explicitly says "MAMS routes user plane data packets at the IP layer".
0-hop protocols only operate on a single LAN and cannot be routed, by
definition.  (ARP, DHCP or its predecessor BOOTP are examples of 0-hop
protocols.)

Therefore, I think this draft should not be using protocol 114.

	John