IETF Logo Mail Archive

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

Bob Hinden <bob.hinden@gmail.com> Sun, 22 September 2019 18:16 UTC

Return-Path: <bob.hinden@gmail.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 CE20012002E for <int-area@ietfa.amsl.com>; Sun, 22 Sep 2019 11:16:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 6b-DK7s7Q0ja for <int-area@ietfa.amsl.com>; Sun, 22 Sep 2019 11:16:17 -0700 (PDT)
Received: from mail-wr1-x42e.google.com (mail-wr1-x42e.google.com [IPv6:2a00:1450:4864:20::42e]) (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 EDD2D12000F for <int-area@ietf.org>; Sun, 22 Sep 2019 11:16:16 -0700 (PDT)
Received: by mail-wr1-x42e.google.com with SMTP id y19so11539348wrd.3 for <int-area@ietf.org>; Sun, 22 Sep 2019 11:16:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=2lZdhvlxykn47JJEdYW123tO+mrf/Mmjuutcnqj3ims=; b=WWgAI/kGxcm6IM4LBuF4Hk/FZHGe6e6xyJM2FLUWXylG1Rj7cY6MjAd7/2oLfLvTKr Z0Rp+LE7EtPuorMfnbdbCW/3Y6twDVCtK/xJrNDoNh/8xBL1+P4kqXZ9KyfXmATcmzg2 l6FJTc0WmZqGpek44QeZQE1J+oKiOTeh4eXsdFsxFPxeGviEpOVb30bqnCz+r/HQrZAl zuvZ/I4k48YTcQLl7rrFC+FZ22/T3GsP7oy2kjpkkNyKPfs6HD3GAbFc/AKGgLk602aW E8i7sL+vdfvCxqeWN8AcNrrbAKdFuaZgcTfJlNnCod7TzsAXYLd9hzhg4VL+q9iRPn4K YWig==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=2lZdhvlxykn47JJEdYW123tO+mrf/Mmjuutcnqj3ims=; b=DB6Z/vq1EZmjSgJxsICRF94a6ivbcMHOXTPZZ2NOpCNF3rkzaZHgSVyW7wK9PJp39b X4lh/GabH3xQ2mU5vNP0R6DZeEyWJ8Zeu0kxM85nyRqi0sVg2EyXnm+LOE1i5msLuf8k Tm7PDpSO5D7rhv/mWFAyqrzpiuynppZyhtZ1zyu6/Y5qwMShhw+ocTEKhdwmcQIMeHCa RH2gXb7TJvb3j2ybQhNGpXi5XmxBnC4gC9M8vHpbhPw+To3qLOTQ6N/K535+v1uqGxyH oKauODnaGSv3sf308nCjTPUSZykeLy87bw0xz9dCoBBkgce0EGZ3tXt454aHROJKRT0I 4DHw==
X-Gm-Message-State: APjAAAU0aVZOMSEv6ySIoGLPltf/jWjr8Nk2KnH1UZccuBUGwLc2eTUv e4xSTTM7We3+LM3xUHVMtCQ=
X-Google-Smtp-Source: APXvYqypi4baCFlhVGBsiNlUX6AHOIQ7B+fbfT2lE5F8tjBXAjPBOivsDRgPQq6SPlIff6IElFVwrA==
X-Received: by 2002:adf:e849:: with SMTP id d9mr6537232wrn.358.1569176175483; Sun, 22 Sep 2019 11:16:15 -0700 (PDT)
Received: from ?IPv6:2601:647:5a00:ef0b:e528:d569:df88:7c1b? ([2601:647:5a00:ef0b:e528:d569:df88:7c1b]) by smtp.gmail.com with ESMTPSA id q22sm6972454wmj.5.2019.09.22.11.16.12 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 22 Sep 2019 11:16:14 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <8D55FD31-B2D8-416A-BF36-C57F9EF2B08D@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_D220AF6A-375C-4429-B32D-5A90F4FE81EC"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Sun, 22 Sep 2019 11:16:08 -0700
In-Reply-To: <032c01d57159$4d11fc30$e735f490$@olddog.co.uk>
Cc: Bob Hinden <bob.hinden@gmail.com>, Brian Carpenter <brian.e.carpenter@gmail.com>, Joe Touch <touch@strayalpha.com>, Internet Area <int-area@ietf.org>, Internet History <internet-history@postel.org>
To: adrian@olddog.co.uk
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> <2EA4A012-7FFC-459A-842A-211CAE27F5A6@gmail.com> <032c01d57159$4d11fc30$e735f490$@olddog.co.uk>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/xo-fUDc_eXBXghU50tR-IQsG5fI>
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: Sun, 22 Sep 2019 18:16:19 -0000

Adrian,

> On Sep 22, 2019, at 8:20 AM, Adrian Farrel <adrian@olddog.co.uk> wrote:
> 
> Hi Bob,
> 
>> I think it would be fine for this draft to request a new one that accurately described its usage.
> 
> For what it's worth, the assignment policy for the registry is IESG Approval or Standards Action.
> 
> The draft concerned (draft-zhu-intarea-gma) doesn't seem to have gained much traction in the IETF - at least not enough to be likely to qualify for "Standards Action". Unless the IESG seems likely to grant an assignment, that avenue appears to be closed off.

It is what it is.   I think they should update the draft to request a new code point.   If they can’t meet the requirements then they won’t get one, if they do (for example, convince an AD to ask IANA to assign it), then they get one.

This is much better than deploying something that misuses an exiting code point.

BTW, since I have started doing a little Wireshark development, I think it’s important that new protocols be possible to parse in network debugging tools like Wireshark.   Misusing a code point doesn’t allow for that.

Bob

v2.23.0 | Report a Bug | By Email