IETF Logo Mail Archive

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

"Joel M. Halpern" <jmh@joelhalpern.com> Sun, 22 September 2019 16:25 UTC

Return-Path: <jmh@joelhalpern.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 B50631200DB for <int-area@ietfa.amsl.com>; Sun, 22 Sep 2019 09:25:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 xdVCCrg7QQMG for <int-area@ietfa.amsl.com>; Sun, 22 Sep 2019 09:25:41 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 5EFB8120059 for <int-area@ietf.org>; Sun, 22 Sep 2019 09:25:41 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 46bt9K20h2zS292; Sun, 22 Sep 2019 09:25:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1569169541; bh=kiIhGXt4PT7C8tSYn7wGSLw7Ne0KytAAFUwWUi8MDBc=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=F60AlJd6q3bRHZxL3WpJ8U86roRhLs+2nAEGKSyZGGL/XFHyGhkssB3WTWdcWIFW0 o316692UX1r4N+JScLJt1yq9rfc+Xs9PrXWzETL7RAbFvFsHHh0OIg4bve/mg1qVNX cL0PAP4NXcgNH6Pzll5G3kH4wADlNPL2Gpl29SPE=
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from [172.20.7.244] (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 46bt9J3Fc4zS28w; Sun, 22 Sep 2019 09:25:40 -0700 (PDT)
To: adrian@olddog.co.uk
Cc: 'Internet Area' <int-area@ietf.org>
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>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <42ae9f40-5d68-5278-3dfb-f79be299e532@joelhalpern.com>
Date: Sun, 22 Sep 2019 12:25:38 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <032c01d57159$4d11fc30$e735f490$@olddog.co.uk>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/kjCC8UYpURVb1xLApRpLLt9b2nk>
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 16:25:43 -0000

Assuming your interpretation is correct (which seems to match what I 
have seen), that would also seem to indicate that allowing them to 
hijack an existing code point for their use is also not appropriate.

Yours,
Joel

On 9/22/2019 11:20 AM, Adrian Farrel 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.
> 
> Adrian
> 
> 
> 
> 
> 
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area
>

v2.23.0 | Report a Bug | By Email