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

"Eric Vyncke (evyncke)" <evyncke@cisco.com> Thu, 19 September 2019 15:06 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 2653712006B; Thu, 19 Sep 2019 08:06:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 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, URIBL_BLOCKED=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=SyUJSjKs; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=QQwm9r/m
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 tPmVK6ch8sCG; Thu, 19 Sep 2019 08:06:10 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9921412002E; Thu, 19 Sep 2019 08:06:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7583; q=dns/txt; s=iport; t=1568905570; x=1570115170; h=from:to:subject:date:message-id:mime-version; bh=5m3PjCZZuBc/rt5pBCiXiAIRY4EYXKtHojpW2A0NrhU=; b=SyUJSjKsaZ4tD67I3v3zGkAMLwE2Qv44IcQZ9p7Pqw60YUo1iI1teQ4f WMAE4yy+dgEMwvDjoaZTLWAaE4Dd9CkJ8c5Mi6ldsLg7djCzkLCaHIzcY F3y1LDmjEMgsiGqwKra8H7MoiEqapo4EiJfO6U58hjfxS+7p2FOwZmmKp 8=;
IronPort-PHdr: =?us-ascii?q?9a23=3An+SrrBSLZmB9Di2zwEty5IpOadpsv++ubAcI9p?= =?us-ascii?q?oqja5Pea2//pPkeVbS/uhpkESXBdfA8/wRje3QvuigQmEG7Zub+FE6OJ1XH1?= =?us-ascii?q?5g640NmhA4RsuMCEn1NvnvOiEkDcJJV1JN9HCgOk8TE8H7NBXf?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DZAQCAmINd/40NJK1lHAEBAQQBAQc?= =?us-ascii?q?EAQGBVQUBAQsBgRUvUANtViAECyqEIoNHA4p7TYFqkzuEXYEugSQDVAkBAQE?= =?us-ascii?q?MAQElCAIBAYQ/GYJsIzYHDgIDCQEBBAEBAQIBBQRthS0MhWMRHQEBLAwRAUc?= =?us-ascii?q?DAgQwFBMEARIUDoMAAYEdTQMdAQIMoioCgTiIYXOBMoJ9AQEFgkiCOxiCFwM?= =?us-ascii?q?GgTQBjAgYgUA/gREnDBOCHoNNAgOBOFOCXjKCJo9YhSmYCQqCIgOHAo4DG4I?= =?us-ascii?q?2h0uPIo4WiBGRAAIEAgQFAg4BAQWBWQongVhwFTsqAYJBUBAUgU6DcoUUhT9?= =?us-ascii?q?zAYEojHqCUwEB?=
X-IronPort-AV: E=Sophos;i="5.64,523,1559520000"; d="scan'208,217";a="632031912"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 19 Sep 2019 15:06:09 +0000
Received: from XCH-ALN-006.cisco.com (xch-aln-006.cisco.com [173.36.7.16]) by alln-core-8.cisco.com (8.15.2/8.15.2) with ESMTPS id x8JF69an030851 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 19 Sep 2019 15:06:09 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-ALN-006.cisco.com (173.36.7.16) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 19 Sep 2019 10:06:08 -0500
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 19 Sep 2019 11:06:06 -0400
Received: from NAM05-BY2-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Thu, 19 Sep 2019 11:06:06 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=atgBMC4iVL6swexWlnAeoWjgAJ5Qh+8mn+RK43vphXd2c3FGIax5nEefulY5FzjAZWeQsN25HTcy+/ATYKLhAoOPWG9a1HPdTjpmZWCLUhgoTYE0XELxZrnE2rluHcXPt69Xsh/yuDXmDB8Oq8+9jxnaS4fWmvJibKrGxBQzfI7CQXfbYCytVFYjK0w0y2QNdjTnOA0ROFhP8d0hMcUgdBqOqgXvayRA+1JnJGgQRtZ44G81ti5cwgaVDMMwPi19ar37zD4gOlrIIOdpBGFKvnHP5OffMoHvnGzpewYhJI3o7SZbbPpESVvmv/MreBFKFcA7neYtAKpRP9mlQ65Teg==
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=5m3PjCZZuBc/rt5pBCiXiAIRY4EYXKtHojpW2A0NrhU=; b=fWJpNn12n0GsfJ9+EMKIxIwrEDuxF9ghuYYOoXDITsLx+n0o6a6EJ5VrF7SFNZihoGaTLCRUQpPvQsmib9A4j1JXaEzcb4sI/RKf0Q9Ht1JF+7PG2qVPIF+JJZOy1fujqQVoo1xAE0ied7++X4mTzVTiMBYw8zdBQXsrCCn24PprKytf4Zq5IseVZG6tYU/v0sdXSEHSZXFNc4dIl5mbIY8+S3wvPMRKtf/rRqBsVv0QoUf9sM8p4Ei/yh2Y8A7HDfgIShiNAxRlOBQUwu8wYJPpbegexFr92/GMvScAGBKaz0cqupbqgXXsienmqyIwPuEjVZffEn2rsLWYph5zRQ==
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=5m3PjCZZuBc/rt5pBCiXiAIRY4EYXKtHojpW2A0NrhU=; b=QQwm9r/mKbjutZEceVroXdFA0x135Du4oMkli3ZcWckapX07b6fBDvHP25lIyA2UWh0QcmjjoL9JGlIBtSglbzm19FM7ytp1TJgUzH4Pg5uSNcnoCfuzzv8M/vSDoV8lVd+Zd6KQWvt417H/O1RaIU7OTKTJlpwuh3MpiLa74p8=
Received: from MN2PR11MB4144.namprd11.prod.outlook.com (20.179.150.210) by MN2PR11MB4367.namprd11.prod.outlook.com (52.135.37.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2284.22; Thu, 19 Sep 2019 15:06:04 +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.009; Thu, 19 Sep 2019 15:06:04 +0000
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: "int-area@ietf.org" <int-area@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Thread-Topic: Existing use of IP protocol 114 (any 0-hop protocol)
Thread-Index: AQHVbvvB7FAn9x2haU2zfnRUZFqC/Q==
Date: Thu, 19 Sep 2019 15:06:04 +0000
Message-ID: <D6BD6D0F-9504-4533-BCFD-A79B2357BC96@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:b8dc:9ee6:8750:2bb9]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 1db6842f-3e23-491b-023c-08d73d12e494
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600167)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:MN2PR11MB4367;
x-ms-traffictypediagnostic: MN2PR11MB4367:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <MN2PR11MB4367BE4D45CB181EBC0BDC0DA9890@MN2PR11MB4367.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 016572D96D
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(39860400002)(396003)(346002)(376002)(136003)(366004)(189003)(199004)(14454004)(6436002)(99286004)(6306002)(54896002)(6512007)(6116002)(966005)(478600001)(6486002)(476003)(486006)(25786009)(81166006)(46003)(2616005)(81156014)(450100002)(8676002)(102836004)(86362001)(256004)(8936002)(6506007)(2906002)(14444005)(186003)(71200400001)(71190400001)(7736002)(2501003)(316002)(58126008)(110136005)(36756003)(76116006)(91956017)(66556008)(66476007)(66946007)(66446008)(64756008)(236005)(5660300002)(33656002)(606006); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB4367; H:MN2PR11MB4144.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A: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: D1KEKt0HxXrcVKBMJXcM6kIILAJR4g6zlY69tEmB5WJyvFuGt8R5IIwzgKHfCUI5uZSk4dNFITBAiTrsJNJN9usvytpFylcRjCXna+9XKBky//S+iBl49QIyq5L0vpjgpdPsG55cpIrZQOM0gCfMyoT9dR8NHjJnmy6e6iburITonkm+gCDjEmuPmv5K8BwTPBW0GgQB50G7QFsT7cMXGMLgh7TgLiZvUHdgWXe1eWlZywcO822ayplWD7Dxd43e7yfxRChmuyoz14AY9YUX+fgOAB1DaOtOohzQoCwXlCEcKPpDr5qhFkqFOAkY3h8hcanCmRaGtOufr0N5yWlo1OMgtDnlh7fBkHHY4snNlNxD7XVTY2duUVDumFNpKOyZKWwZa1rO+VgzRZQLAfacv2uQPC5/dIKyHOoSkstJBvk=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_D6BD6D0F95044533BCFDA79B2357BC96ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 1db6842f-3e23-491b-023c-08d73d12e494
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Sep 2019 15:06:04.8046 (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: 3bX/Xj+B4K+AEGpOQIy44MXCAHH3Oo5LHNBUpV/yOpDphpiMW5HE6OamVkkoD30NRxaRMc4JHXylNnOq5g+8sQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB4367
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.16, xch-aln-006.cisco.com
X-Outbound-Node: alln-core-8.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/00qMj_dMIwIRQ-td5DS4rkDsDpc>
Subject: [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: Thu, 19 Sep 2019 15:06:14 -0000

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