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

"Eric Vyncke (evyncke)" <evyncke@cisco.com> Mon, 23 September 2019 08:40 UTC

Return-Path: <evyncke@cisco.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 90840120106; Mon, 23 Sep 2019 01:40:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=c9Yxsvpq; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=fEnFzswU
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 4s6uTbsArec6; Mon, 23 Sep 2019 01:40:43 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE8BA120043; Mon, 23 Sep 2019 01:40:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=17659; q=dns/txt; s=iport; t=1569228042; x=1570437642; h=from:to:cc:subject:date:message-id:mime-version; bh=lCwUI5kkzTEf+KUZtm0Ru5xdei8c+03VSVcyxTlxx4o=; b=c9Yxsvpqjdde4D4oMk4tpez7vww0jA2mV7toeMfXNyECYWKoNn+JvlI4 ApkubUzI3bzbLesuWsHMNGoAZ7ebCWlWAq2rGqH1fMqmjZtwt9Zk3j++9 sN5rwDfs53H9A5k1zZ1S+OeplGNbd2T0zrq+7SAdqRnjXEWc7gF5DkMut w=;
IronPort-PHdr: 9a23:TNT5RxdZJ0soPES10YcmlQtrlGMj4e+mNxMJ6pchl7NFe7ii+JKnJkHE+PFxlwGRD57D5adCjOzb++D7VGoM7IzJkUhKcYcEFnpnwd4TgxRmBceEDUPhK/u/YjIrGs9BWXdu/mqwNg5eH8OtL1A=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BuAABmhIhd/49dJa1kGwEBAQEDAQEBDAMBAQGBVQQBAQELAYEbL1ADbVYgBAsqhCKDRwOKdoJckxeEXYEugSQDVAkBAQEMAQElCAIBAYQ/AheCfCM2Bw4CAwkBAQQBAQECAQUEbYUtDIVKAQIBAw4EER0BASMJCwERAQgRAwECKAMCBDAUCQoEAQ0FFA6DAAGBHU0DHQECDJ8yAoE4iGFzgTKCfQEBBYJIgkAYghcDBoE0AYwIGIFAP4ERJx+CHi4+gmECA4E4Rg0JglUygiaPWoUpmA0KgiKHBY4FG4I2h0uPJI4aiBORAgIEAgQFAg4BAQWBWQwlgVhwFTsqAYJBUBAUgU6DcoUUhT9zAYEoinGCUwEB
X-IronPort-AV: E=Sophos;i="5.64,539,1559520000"; d="scan'208,217";a="632709715"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 23 Sep 2019 08:40:40 +0000
Received: from XCH-ALN-003.cisco.com (xch-aln-003.cisco.com [173.36.7.13]) by rcdn-core-7.cisco.com (8.15.2/8.15.2) with ESMTPS id x8N8eenG021217 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 23 Sep 2019 08:40:40 GMT
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by XCH-ALN-003.cisco.com (173.36.7.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 23 Sep 2019 03:40:40 -0500
Received: from xhs-aln-001.cisco.com (173.37.135.118) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 23 Sep 2019 03:40:39 -0500
Received: from NAM01-BY2-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 23 Sep 2019 03:40:39 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=PBykztfm+RYpySGlOVRUwobMyM/PMfOIPieIgHCqj9ohQjS2Zl5DqzcXtSasQ6Tn4Vsb6H3ZyLImkcL01sSCTPVywBXhh2LpMZeALtnvfGEYo11K9K/09W/lHCQ7pxjpN23Dj0m7ONSbczsVIWdFgEzZXR15003cP2+Q78v4UjPGMQaADec5HEquQT4naoYGxFNryestQAhnV02XqN1qhshRkubXvAKO1L7RDntX0jJ2lEYyUipYGJWe/JByc67DHr7w6m/8ygwGQUAOgGCvzuriojK9CzeO2V+i2vMQcrM8mY0JkwfUCfvbyBofmQyAF9gDrwLT+63lyGIfWV9PFA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=lCwUI5kkzTEf+KUZtm0Ru5xdei8c+03VSVcyxTlxx4o=; b=fPrMk+gKUyeyUknsoukM69NpFVQwE/WfMa9tX7MZc1NDOD3BLaZcjA+miEncQamcEUgfOmxdoDryu2QnT8nHzhtYpNDDc6gl79+SYNVxbpQ4uWG2CNIAb0JeIQvdMcIDs5Q4kMcFp8dEE+9WwCWXdx8pwGUO11BJxDHKRFv+1RFPE5ICcHCB2iKUQadfwQmeTNUToTRHHIbgbBl2De0q9jQpGkEilTtClJAz4Q0/NdT0dQ2BWcOwi37hVhxU/tUpK5Ytxn16FQmmRMEhFi6aDZOOG6hvZ2mW3LgxfskVDKEXjgYwreI6HMl3o7mOx0dgJ6717gSkopikDx82rje5BQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=lCwUI5kkzTEf+KUZtm0Ru5xdei8c+03VSVcyxTlxx4o=; b=fEnFzswUgEhl7+zHZLTo+esdvU3Kju32rkXroS7JSjgb9pxj5hcaDUVARvpfCpXiUDvZcK7JLiy6KP0a99B9T301dVsgUozU/pa0eroNmCJ5sej7G8AVc/KDp+tyDjzqSdRNjqtfITvfWEcBjsB9i1g5RKoSjQ6r85JvxzTCeoc=
Received: from MN2PR11MB4144.namprd11.prod.outlook.com (20.179.150.210) by MN2PR11MB4063.namprd11.prod.outlook.com (20.179.149.217) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2284.26; Mon, 23 Sep 2019 08:40:37 +0000
Received: from MN2PR11MB4144.namprd11.prod.outlook.com ([fe80::a867:28ea:afa3:be5f]) by MN2PR11MB4144.namprd11.prod.outlook.com ([fe80::a867:28ea:afa3:be5f%6]) with mapi id 15.20.2284.023; Mon, 23 Sep 2019 08:40:37 +0000
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: "int-area@ietf.org" <int-area@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
CC: "internet-history@postel.org" <internet-history@postel.org>
Thread-Topic: [Int-area] Existing use of IP protocol 114 (any 0-hop protocol)
Thread-Index: AQHVceqSKx2j4zX1hEGAG2Fz8ReZYQ==
Date: Mon, 23 Sep 2019 08:40:37 +0000
Message-ID: <B09D69AB-B2AA-4FFE-9B31-F9D305A5D5DC@cisco.com>
Accept-Language: fr-BE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1d.0.190908
authentication-results: spf=none (sender IP is ) smtp.mailfrom=evyncke@cisco.com;
x-originating-ip: [2001:420:c0c1:36:74d5:ba9e:6e11:a3eb]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 5aec7334-dc15-481a-4725-08d74001b533
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600167)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:MN2PR11MB4063;
x-ms-traffictypediagnostic: MN2PR11MB4063:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <MN2PR11MB406300011EA1C9C23715B94CA9850@MN2PR11MB4063.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0169092318
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(346002)(376002)(396003)(136003)(366004)(39860400002)(199004)(189003)(66556008)(66446008)(64756008)(8676002)(66574012)(6246003)(54896002)(76116006)(91956017)(7736002)(6306002)(66476007)(33656002)(6486002)(81156014)(4326008)(110136005)(236005)(25786009)(81166006)(66946007)(6512007)(36756003)(8936002)(58126008)(53546011)(6506007)(486006)(476003)(71200400001)(102836004)(2616005)(186003)(71190400001)(2906002)(478600001)(229853002)(14454004)(99286004)(46003)(5660300002)(6436002)(966005)(6116002)(86362001)(14444005)(256004)(606006)(2501003)(316002); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB4063; H:MN2PR11MB4144.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: EGAE6u0Dr6ukwM6DwSwtfz/SfWHRxLsSkGVYnBO7ye+FVIN0V7qnwgE7S/q405FC+b96lyjU+XLlpuE44S/kGWyILu0Rju++qCVI5OOdbqKHauH9N8Ds9635TnZk8LyLfRfMVYfYibjq04tMiLrj7u1BfKO+y3sFKW0VBWyBkHRE+CH5J5zXCxOk7djWAgMuA6lERdAV6Rf5ZqHYJzbdP/8720gXmHSAZB5G21piBZRveIndcrefqggRdFYrUF/KiaUZfU2ymdEcMJKdm/MOYjFJmf5tjGgo5Z0NQbJrBaJHbRbkpVnrMFNytX9hQAt/ZkP5oxlouditGsmALnlLoT2/k3gmYbQjyKPWB8uMfjjEhqf85EL0mSgp58gSFqPtZQXQbnuc8FlTrKJqSgXddV8vxvQntk5zuxKycEnsfDU=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_B09D69ABB2AA4FFE9B31F9D305A5D5DCciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 5aec7334-dc15-481a-4725-08d74001b533
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Sep 2019 08:40:37.3597 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: CGRHSA7QqX5zhvRcAwJNSCIAZ/qEocUgAcRjl3oE5jz3cb79Pr6rUop9zyeI/hnpoV+e3AeCHoBnSRTJl8fmyQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB4063
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.13, xch-aln-003.cisco.com
X-Outbound-Node: rcdn-core-7.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/sjYMJNUehDmVBa7Ler4jGhyizDk>
Subject: Re: [Int-area] 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: Mon, 23 Sep 2019 08:40:46 -0000

Thank you all for your unicast, multicast replies and the educated pieces of information sent. I even went in the Internet history museum ;-)

Based on the provided information, I will recommend to the draft-zhu-intarea-gma authors:

  1.  As it is an informational independent stream with little traction, to keep using the IP protocol 114;
  2.  BUT, the I-D should be revised to specify a hop-limit of 0 for IPv6 (RFC 8200) and time-to-live of 1 for IPv4 (RFC 791). The balance of local-only packet leak prevention (HL=0) and security (HL=255) in this case should be on preventing the leak of the local-only packets outside the ‘local domain’ to the Internet or to another domain which could use this IP protocol.
  3.  Any other standard track IETF stream document (including this one may be in the future) should request a new IP protocol number if required. The last assigned IP protocol number AFAIK was for HIP in 2015 and there are more than 40% remaining.

Now, it would nice to have a volunteer to write a document to finally document those “Any bla” protocol number by putting common sense restrictions/constraints on them (protocols 9/IGP, 61/host internal, 63/local network, 68/distributed FS, 99/private encryption scheme, 114/0-hop).

Regards

-éric


From: Int-area <int-area-bounces@ietf.org> on behalf of Eric Vyncke <evyncke@cisco.com>
Date: Thursday, 19 September 2019 at 17:07
To: "int-area@ietf.org" <int-area@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: [Int-area] Existing use of IP protocol 114 (any 0-hop protocol)

The authors of https://tools.ietf.org/id/draft-zhu-intarea-gma-03.txt would like to use IP protocol 114 as it is described as “Any 0-hop protocol” on the IANA page[1]. Alas, on the IANA page, there is no reference to this “Any 0-hop protocol”.

Obviously, we all understand that this must be a protocol using hop limit = 0 (or TTL=0 for the legacy protocol).

When there is no reference for a IANA number, this means that this number was assigned _before_ IANA, possibly by J. Postel and nobody at IANA and in the IESG know more. Hence, my questions to the community:

Q1) does anyone know about a more formal reference / specification for this protocol 114

Q2) does anyone know about a RFC or a protocol using this protocol 114 ?

Please note that I do not ask for comments/reviews on the draft itself (they are welcome though on the int-area@ietf.org<mailto:int-area@ietf.org> mailing list even if this is not a WG document). And it is also mostly obvious that only one transport layer can exist on the top of this protocol.

Regards,

-éric (INT AD)


[1] https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml