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

Erik Kline <ek@loon.com> Sat, 21 September 2019 04:03 UTC

Return-Path: <ek@google.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 21EA812004F for <int-area@ietfa.amsl.com>; Fri, 20 Sep 2019 21:03:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.498
X-Spam-Level:
X-Spam-Status: No, score=-9.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=loon.com
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 FWEnP34Sg7D9 for <int-area@ietfa.amsl.com>; Fri, 20 Sep 2019 21:03:44 -0700 (PDT)
Received: from mail-wr1-x432.google.com (mail-wr1-x432.google.com [IPv6:2a00:1450:4864:20::432]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 556B012003E for <int-area@ietf.org>; Fri, 20 Sep 2019 21:03:44 -0700 (PDT)
Received: by mail-wr1-x432.google.com with SMTP id i1so8625650wro.4 for <int-area@ietf.org>; Fri, 20 Sep 2019 21:03:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=loon.com; s=google; h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc; bh=oEUO24X93b5X4h7Of7zuS8+0pdvL1oyxazXpoLHACv4=; b=EcjyoUN/AUc2zgG1IPgkvfng2spzncGbBK/LzPCwn0ONj7abPva9+F/p7ZwGAvxiJZ +DlMC/uMMzzHMo5JaGZnnz0pIOhSUARfns9JVXseiijgqgGvvE9027N3hWlEDPFPejd0 n1Dw9DhPmW3/eDYlO6g/ilen10+y3iIrNzKZo=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to:cc; bh=oEUO24X93b5X4h7Of7zuS8+0pdvL1oyxazXpoLHACv4=; b=FIcFXUT8TpAU6aavWRPCs8FAAXiK31ww7jHfuSDHMBF9WsS0MV7nCqj6MwjUa8V6au C9R7JxE8Mv1CTghDGHeZfws+9a8e2hY+AEuEwz6yP5p7iSF5tM2djq9zoiTyltyL36+u gPZcn9n+me3ImvXGmbkoIYQLKNhsPskerfI0bbGGcAiW1sAjOEPHhjZelNPPyvisdMbA dF+R6gTN0VQSQNDWacrDqmXTG//oKFYgbjyVF7RwjMdb8+LdBmuu1dsNhtg7ApyE/Sg1 /ebxFDkTJrWp0deYxt+20YA25vyd9Go0k8680AVDokWRUZb2SJNsS26UrJoLQv3Dq/VR RU4g==
X-Gm-Message-State: APjAAAXkaO8EFUwMNEq1djkGOFySioqoApd+D9hxD/tWz/tEmnVvwg+P 9pSWoEJyl4QV5Fb+Qadbf5FqXCDA4GAAdgfti2yfgg==
X-Google-Smtp-Source: APXvYqzkWBg+k9Xs8OYaD95cFae4s5PmUtVW8TTNalg2blBrhZqIqef1N0lSYPZ/PnTT4Xc82AlK+oW312cma1qt/0A=
X-Received: by 2002:adf:dc41:: with SMTP id m1mr13131902wrj.46.1569038622322; Fri, 20 Sep 2019 21:03:42 -0700 (PDT)
MIME-Version: 1.0
References: <D6BD6D0F-9504-4533-BCFD-A79B2357BC96@cisco.com> <88ec7bdb-57e7-5966-6deb-b9e9ba8d7b67@gmail.com> <416.1568937724@hop.toad.com> <CAC8QAcfQd-n1bVWOhXRQEMW_Z=DPNzrYPUEdZrAHCL-MuXYXyQ@mail.gmail.com> <CAA=duU0x8+jPWwHu1qTc-40zjrySKjAdVpSnMBWaTwPJ2nrJvg@mail.gmail.com> <9C35B8B2-B5CC-4BB5-AC4E-2F3C77AD1A7C@gmail.com> <E9F59590-C661-471A-82E4-00D82EC7CBC9@strayalpha.com> <2e48543a-b4f6-f136-3b0f-751dc7473e72@gmail.com>
In-Reply-To: <2e48543a-b4f6-f136-3b0f-751dc7473e72@gmail.com>
Reply-To: ek@loon.com
From: Erik Kline <ek@loon.com>
Date: Fri, 20 Sep 2019 21:03:30 -0700
Message-ID: <CAAedzxpuoBRNohf9hW5PhEwopXRb+VPxaZpWR_3JNeBsR_j4_g@mail.gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Joe Touch <touch@strayalpha.com>, Bob Hinden <bob.hinden@gmail.com>, Internet Area <int-area@ietf.org>, Internet History <internet-history@postel.org>
Content-Type: multipart/alternative; boundary="000000000000b98eef0593084579"
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/gyBIRk-nqT0iFgWvM3ia-oL6a6k>
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: Sat, 21 Sep 2019 04:03:47 -0000

There's also the matter of whether allocating 114 for this doc would
establish a precedent.

On Fri, 20 Sep 2019 at 20:24, Brian E Carpenter <brian.e.carpenter@gmail.com>
wrote:

> On 21-Sep-19 14:11, Joe Touch wrote:
> > FWIW, there are many registries with such “dead” entries.
>
> 114 is a bit special. By definition, all our normal traffic monitoring
> techniques will *never* see protocol 114 unless by chance they are
> installed on a layer 2 segment where it is in use. So even if no traces
> anywhere include it for ten years, we still can't assert that it is out of
> use. It seems harder to prove than most negatives :-).
>
> > RFC6335 talks about the issue in trying to recover such entries.
> >
> > In general, it recommends that even if they are recovered, at best they
> would be marked as “RESERVED” until other values have been assigned and the
> space requires reuse of those dead entries.
> >
> > So the net effect is:
> > a) the list will never actually reflect what is deployed (as Bob notes
> below)
> > b) garbage-collecting will at best mark some subset as dead
> > c) but the available entries won’t be reused until we run out anyway
> >
> > Given the number of remaining entries, the task of garbage collection
> seems of little value.
>
> Until the day when it seems urgent...
>
>     Brian
>
> >
> > Joe
> >
> >> On Sep 20, 2019, at 1:31 PM, Bob Hinden <bob.hinden@gmail.com> wrote:
> >>
> >> Andy,
> >>
> >>> On Sep 20, 2019, at 10:37 AM, Andrew G. Malis <agmalis@gmail.com>
> wrote:
> >>>
> >>> Behcet,
> >>>
> >>> That was a historical list. The current assignments are in
> https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml
> . If you want to go garbage collecting, that's the place to start.
> >>
> >> It's difficult to tell which are no longer used.  For example, I was
> recently asked about the Reliable Data Protocol, it’s IANA assignment:
> >>
> >> 27   RDP     Reliable Data Protocol          [RFC908][Bob_Hinden]
> >>
> >> I assumed it was no longer used.   Later by happenstance, I learned it
> is specified by ETSI as mandatory to implement in eSIMs.  I had no idea.
> >>
> >> Bob
> >>
> >>
> >> _______
> >> internet-history mailing list
> >> internet-history@mailman.postel.org
> >> http://mailman.postel.org/mailman/listinfo/internet-history
> >> Contact list-owner@mailman.postel.org for assistance.
> >
> > _______
> > internet-history mailing list
> > internet-history@mailman.postel.org
> > http://mailman.postel.org/mailman/listinfo/internet-history
> > Contact list-owner@mailman.postel.org for assistance.
> >
>
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area
>