Re: [Int-area] [ih] Fwd: Existing use of IP protocol 114 (any 0-hop protocol)
"Eric Vyncke (evyncke)" <evyncke@cisco.com> Fri, 20 September 2019 07:18 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 081511200CE for <int-area@ietfa.amsl.com>; Fri, 20 Sep 2019 00:18:09 -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, 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=SWVHle3F; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=ola0kP+s
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 FizCBmTTY7g4 for <int-area@ietfa.amsl.com>; Fri, 20 Sep 2019 00:18:07 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 22D79120026 for <int-area@ietf.org>; Fri, 20 Sep 2019 00:18:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3828; q=dns/txt; s=iport; t=1568963887; x=1570173487; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=MM9xxbALgojl9f+1GS6LQDzm4D+MNtdEufqEHZvq9ys=; b=SWVHle3FdwHErdzkzQ+k8zcUAgK2Ybv03QzomEexq3p66c8AnfOUsF5l xSlPT9kmBb8uReysLMy0WKeisquFDFObDMeMhwl9ck0FLfPaIu95bGgq7 gcxaxY7RO+eb22ZEAJhf17ZrqD6jddWmOuM9NIwIEhtXMioniDSkau1EW c=;
IronPort-PHdr: 9a23:cH6ASBPzmQc3cN2+cq0l6mtXPHoupqn0MwgJ65Eul7NJdOG58o//OFDEu60/l0fHCIPc7f8My/HbtaztQyQh2d6AqzhDFf4ETBoZkYMTlg0kDtSCDBj2Mu/sZC83NM9DT1RiuXq8NBsdFQ==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0A2AADXfIRd/4cNJK1lGwEBAQEDAQEBBwMBAQGBVQQBAQELAYFEUANtViAECyqEIoNHA4p8gjeIU49GgS6BJANUCQEBAQwBAScGAgEBhD8CF4JuIzYHDgIDCQEBBAEBAQIBBQRthS0MhUsCAQMSEREMAQE3AQ8CAQgODAImAgICMBUQAgQBDQUigwABgWoDHQECDKAdAoE4iGFzgTKCfQEBBYEzAYNWGIIXCYEMKAGLYiYYgUA/gREnDBOCHi4+hB4mF4J0MoImj1qMZZBQCoIihwWOBRuCNnKKfop+jhqIE5ECAgQCBAUCDgEBBYFZAi+BWHAVOyoBgkEJCj0QFIFOg3JqhCqFP3MBAQqBHYswglMBAQ
X-IronPort-AV: E=Sophos;i="5.64,527,1559520000"; d="scan'208";a="637090193"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 20 Sep 2019 07:17:38 +0000
Received: from XCH-RCD-002.cisco.com (xch-rcd-002.cisco.com [173.37.102.12]) by alln-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id x8K7HZ0M027106 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 20 Sep 2019 07:17:35 GMT
Received: from xhs-aln-003.cisco.com (173.37.135.120) by XCH-RCD-002.cisco.com (173.37.102.12) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 20 Sep 2019 02:17:35 -0500
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 20 Sep 2019 02:17:34 -0500
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Fri, 20 Sep 2019 03:17:34 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=nE72QOYwzT/x2PkXeEt5PoEtaToBLfrOVVjBtj/8wwscQHsNu74LHOHIZa7ToACcdm5DlXqycZiDh/cVS5dfgDpaGRYos/Um1apyGCMdBrmbCJqvdFLbsdE4//l0PQQ4N4J4WEknY5j5rN8Dbkms6M9LnP8XecuF+RvqZ1/qYUMTq1yYNR1gOxGSQhkuPjsbjZUCx6i92tH+up6TsSSHJIwWhsTqNIpq885ki5oo5VPgrH4Q8s9tTS6uufFMaV+gbkm8ARCXEOImsOdwIIep9AEtE0cpe77ys4D4oPnSG9l4aOC7YlLmX/8VH0K6yV6fwgubFhpF34e2Ib+AfVV6lw==
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=MM9xxbALgojl9f+1GS6LQDzm4D+MNtdEufqEHZvq9ys=; b=ZPJj8p9c0QDJFV4G20QyLGNl1dyMKTafkM0b4CC1/pJOmqBrcFTLNTIBlqlRv7pgl2/vTk0Agi48KamqHTrQKb1BLQzlmEJ+Lv+yjCbgewJgfwkZQ+H95VENC1k3jdb+yE23lBY8n+rzfgHHGHBBgyQMFfhG5JIOSKHnMgXYXkmvSEbKWrzjNHjbld/0la8lqOeA7XZ5/2tV0+CHXGFEZu4BBZ5ugtq/W9QZq+Kij51Qubqpd3Ix6EJbGuiUo+fjKWkcTKPatlQqszTDO9MrNIgYQJ3619Hc0FRndsWm5qGpRIwUezJc1ffHU/h+oyxmWbt3AyUq8t6Nfbs/TEOGAQ==
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=MM9xxbALgojl9f+1GS6LQDzm4D+MNtdEufqEHZvq9ys=; b=ola0kP+sAIfQ1Z6cMGH52BJjI23K4V+j6mW0lmI6lfDlqNXWEC3JqvQSPebMB8z0a42CIUEdC9B/rqXvscjwmCAIoWUOYAqRUf5xheVoAp1HpDFkX3vVjlHidno2uTsjCq4zMQWIRRKPfNAOvYPL+mXawS50KhwKSb85vdgUrrA=
Received: from MN2PR11MB4144.namprd11.prod.outlook.com (20.179.150.210) by MN2PR11MB3838.namprd11.prod.outlook.com (20.178.252.202) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2284.22; Fri, 20 Sep 2019 07:17:33 +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; Fri, 20 Sep 2019 07:17:33 +0000
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: John Gilmore <gnu@toad.com>, "internet-history@postel.org" <internet-history@postel.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
CC: "int-area@ietf.org" <int-area@ietf.org>
Thread-Topic: [ih] Fwd: Existing use of IP protocol 114 (any 0-hop protocol)
Thread-Index: AQHVbvvB7FAn9x2haU2zfnRUZFqC/aczr2QDgACbGwA=
Date: Fri, 20 Sep 2019 07:17:33 +0000
Message-ID: <2E013658-CA67-4734-8B23-4B987CCD128E@cisco.com>
References: <D6BD6D0F-9504-4533-BCFD-A79B2357BC96@cisco.com> <88ec7bdb-57e7-5966-6deb-b9e9ba8d7b67@gmail.com> <416.1568937724@hop.toad.com>
In-Reply-To: <416.1568937724@hop.toad.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:c0c0:1008::db]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 4a833563-2cec-40ba-e8df-08d73d9a9b54
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600167)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:MN2PR11MB3838;
x-ms-traffictypediagnostic: MN2PR11MB3838:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <MN2PR11MB38380493D879BB0F221D9234A9880@MN2PR11MB3838.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0166B75B74
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(396003)(366004)(346002)(39860400002)(376002)(189003)(199004)(6506007)(64756008)(66446008)(102836004)(186003)(8936002)(46003)(81166006)(81156014)(14454004)(76176011)(316002)(66556008)(99286004)(5660300002)(91956017)(76116006)(33656002)(58126008)(110136005)(66946007)(476003)(4743002)(486006)(66574012)(11346002)(2616005)(446003)(66476007)(36756003)(8676002)(86362001)(6116002)(229853002)(71190400001)(25786009)(6512007)(6306002)(71200400001)(6246003)(4326008)(6436002)(2501003)(6486002)(7736002)(478600001)(305945005)(966005)(14444005)(256004)(2906002); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3838; 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: P5+/tfVYcKpDAcs8McGPvOJyxUkbKZDzFnug3fi+RomuIHzzIt9zvE2ydqdCaY2Do4yFxMWJTluDv62vfBrhpZOeZEUiMrMP4ZDL5wqfPmF2NAxhlZLC4IXE/1ItQfuSEyYOlefOpOmZehKm/fzzhzf/7pqQEQWlLaW2idbzCOYDbqH4uQSEZdUi64fzCugfc4eXqfPCJx7zc1X773LPjg2SVkFOODCFlcd0PtBssNUktVIzXTX5gIGmm7Vuf7O4O6HSwZQrMHumZMuJf081Zx10oHaQnqiiXEkR+50cRmJyS9hhjIYo2CjQli12Zx78fsJyuzf7klI/pdTqx+xqkGTX6aAepZ8BankOKoeBAtIjnfaOqWf1UR7k2zT0caZ9Tr/5YD4Y9Zcy5XYnSU2CKfRTsj+Xt3RnEGzXMHavXQo=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <55DD14BFBDFA6648A6818C4422E3719C@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 4a833563-2cec-40ba-e8df-08d73d9a9b54
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Sep 2019 07:17:33.4246 (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: dXmysvTH+QhGIJveyWc/GQ2Ao5okEypanz8b8lfaD70xbyHDhr3/XVK1i2d60JktVFr1o1HJOtVxVxWSN+qN0g==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3838
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.12, xch-rcd-002.cisco.com
X-Outbound-Node: alln-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/_2afUR8J8JJjEx2KqPmYizkobtY>
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: Fri, 20 Sep 2019 07:18:09 -0000
Thank you John for your 'archeology' work about this protocol number. I appreciate your time and effort. About the draft itself, I will let the authors reply (as they should be part of int-area@) but my understanding is that the "multi-access gateway" is on the same link (3G or wifi) as the client so it is a layer-3 0-hop. And IMHO hop-limit should be 0 to scope the packets to the local-link (even if less secure than using HL=255). Regards -éric On 20/09/2019, 02:02, "John Gilmore" <gnu@toad.com> wrote: Protocol 114 was unassigned in RFC 1700 in Oct 1994, which was the last RFC tabulating protocol assignments. In January 2002, RFCs ceased being published for protocol number assignments, according to RFC 3232. Sometime before Feb 1999, protocol 114 was assigned here: https://web.archive.org/web/19990203044112/http://www.isi.edu/in-notes/iana/assignments/protocol-numbers The original IANA, Jon Postel, died on October 16, 1998. There was some turmoil in the relevant websites at the time. The Internet Archive's Wayback Machine does not appear to have captured the IANA.org or isi.edu websites during an earlier time when this protocol number was not assigned. But, only five assignments in Feb 1999 had followed 114; the next one was L2TP (protocol 115) by Bernard Aboba (April 1998). The preceding one was PGM (protocol 113) by Tony Speakman in January 1998. So it's a pretty good bet that it was assigned by Postel between January and April 1998. (L2TP was documented in RFC 2661 of August 1999, and by that point it was not using protocol #115; it ran over IP and UDP on port 1701. A later 2005 evolution of L2TP, L2TPv3, used protocol 115.) Does anyone have archives of the TCP-IP Distribution List from 1998? The only copy I have found so far is at http://securitydigest.org/tcp-ip/ but it ends in 1994 (with no apparent "we're closing down the list" messages). A separate issue: Having read the draft-zhu-intarea-gma-03.txt, and skimmed the 2017 draft-kanugovi-intarea-mams-protocol-03 that it references, I don't see how this protocol could in any way be seen as a 0-hop protocol. The whole design is to provide multiple paths to the Internet, which would require that the relevant packets traverse routers. The MAMS draft explicitly says "MAMS routes user plane data packets at the IP layer". 0-hop protocols only operate on a single LAN and cannot be routed, by definition. (ARP, DHCP or its predecessor BOOTP are examples of 0-hop protocols.) Therefore, I think this draft should not be using protocol 114. John
- [Int-area] Existing use of IP protocol 114 (any 0… Eric Vyncke (evyncke)
- Re: [Int-area] Existing use of IP protocol 114 (a… Fernando Gont
- Re: [Int-area] Existing use of IP protocol 114 (a… Erik Kline
- Re: [Int-area] Existing use of IP protocol 114 (a… Andrew G. Malis
- Re: [Int-area] [ih] Fwd: Existing use of IP proto… John Gilmore
- Re: [Int-area] [ih] Fwd: Existing use of IP proto… Eric Vyncke (evyncke)
- Re: [Int-area] [ih] Fwd: Existing use of IP proto… Behcet Sarikaya
- Re: [Int-area] [ih] Fwd: Existing use of IP proto… Andrew G. Malis
- Re: [Int-area] [ih] Fwd: Existing use of IP proto… Bob Hinden
- Re: [Int-area] [ih] Fwd: Existing use of IP proto… Andrew G. Malis
- Re: [Int-area] [ih] Fwd: Existing use of IP proto… Joe Touch
- Re: [Int-area] [ih] Fwd: Existing use of IP proto… Brian E Carpenter
- Re: [Int-area] [ih] Fwd: Existing use of IP proto… Erik Kline
- Re: [Int-area] [ih] Fwd: Existing use of IP proto… Joe Touch
- Re: [Int-area] [ih] Fwd: Existing use of IP proto… Brian E Carpenter
- Re: [Int-area] [ih] Fwd: Existing use of IP proto… Joe Touch
- Re: [Int-area] [ih] Fwd: Existing use of IP proto… Bob Hinden
- Re: [Int-area] [ih] Fwd: Existing use of IP proto… Adrian Farrel
- Re: [Int-area] [ih] Fwd: Existing use of IP proto… Joel M. Halpern
- Re: [Int-area] [ih] Fwd: Existing use of IP proto… Bob Hinden
- Re: [Int-area] Existing use of IP protocol 114 (a… Eric Vyncke (evyncke)
- Re: [Int-area] [ih] Existing use of IP protocol f… John Gilmore
- Re: [Int-area] Existing use of IP protocol 114 (a… Joe Touch