[OPS-AREA] It needs a new transport layer protocol to promote IPv6

高 军安 <jagao@outlook.com> Tue, 30 October 2018 11:33 UTC

Return-Path: <jagao@outlook.com>
X-Original-To: ops-area@ietfa.amsl.com
Delivered-To: ops-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CEDC12F295 for <ops-area@ietfa.amsl.com>; Tue, 30 Oct 2018 04:33:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.01
X-Spam-Level:
X-Spam-Status: No, score=-1.01 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, FROM_EXCESS_BASE64=0.979, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=outlook.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 yW78giHv7oXi for <ops-area@ietfa.amsl.com>; Tue, 30 Oct 2018 04:33:32 -0700 (PDT)
Received: from APC01-HK2-obe.outbound.protection.outlook.com (mail-oln040092255086.outbound.protection.outlook.com [40.92.255.86]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D3E78128B14 for <ops-area@ietf.org>; Tue, 30 Oct 2018 04:33:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Pv8uebbHd/kpEYKssdfrbAwjQKCnpkNE/NgnWggIXxk=; b=DlS4cIRXO8HwkUVjQ9JCOogPb+57+nb7QQA98MB14J9mo5d+EXHCtNvo2EA9ViL8gX79ohIB4tOTsAqtAD2JacMJ3aNNEYSVadQBoGADEVgGt4Dv3WN8xl0aCYeD1fCE4zF7jxXQbFhttA35sKZnfioR2OpnIw+Dac1evyneIyoKMnAOvnU10lFpQLGPJtzoNLLUwA5Kny0lZc64GB0HyMP5yY+DrZxY6VcZlPebVbfBBYShMx7wbeRRIcjutLpNi9g0SimHcUykl91VDn0UAIFsis1SQEB09iRDWDxf8DbaZtXey0sTplllijWRW3odaJhksf6wrPElT4X4D9dCKg==
Received: from SG2APC01FT025.eop-APC01.prod.protection.outlook.com (10.152.250.57) by SG2APC01HT151.eop-APC01.prod.protection.outlook.com (10.152.251.128) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1294.14; Tue, 30 Oct 2018 11:33:28 +0000
Received: from HK2PR0302MB2628.apcprd03.prod.outlook.com (10.152.250.56) by SG2APC01FT025.mail.protection.outlook.com (10.152.250.187) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1294.14 via Frontend Transport; Tue, 30 Oct 2018 11:33:28 +0000
Received: from HK2PR0302MB2628.apcprd03.prod.outlook.com ([fe80::4969:1c7d:352d:b22e]) by HK2PR0302MB2628.apcprd03.prod.outlook.com ([fe80::4969:1c7d:352d:b22e%7]) with mapi id 15.20.1294.018; Tue, 30 Oct 2018 11:33:28 +0000
From: =?gb2312?B?uN8gvvywsg==?= <jagao@outlook.com>
To: "ops-area@ietf.org" <ops-area@ietf.org>
Thread-Topic: It needs a new transport layer protocol to promote IPv6
Thread-Index: AQHUcD93nWrTajvsj0Wor2of5obttA==
Date: Tue, 30 Oct 2018 11:33:28 +0000
Message-ID: <HK2PR0302MB2628AFFF9C8FAD836F9EB947BECC0@HK2PR0302MB2628.apcprd03.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-incomingtopheadermarker: OriginalChecksum:9F5FE7BEF11B524408B2501A470CBE791A7D943914EEC901AE1EF0E7352D673F; UpperCasedChecksum:D546B9D74328A853BD9FE66DEE87BF0E5C3E50C05C2A76CD49F0C4FAF821D5D5; SizeAsReceived:6931; Count:44
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [RENNzZzGoUQWkgbdiEQJjXsF4DaxS45e]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; SG2APC01HT151; 6:9yTVW744FVyjnZma5hrHbT4UF8O+IE6WpyGG5/EwExyNGtcp127GCwjqlv/ZaAy29YPZ3Y9J3oCQnGTFik9QJXZ3ffwutU4jUAidBtVye0h90SqfNses1W+LZaPxn84lFiu3Ex5sZf0opMklatz9/IwUcrvSscIOSoQPsFe2lfqCz9xHu/gd1OAPrqH9DabsRmLjZ9qmqEQxLdze9oxqO60MJ3r2R9GO2m9zjdkKkPadEGwSRmEQBQLoG7UlkkknqamS21cJODk1axBaG8Jk0PpiTn5qeORtvMorCCDZ2e6F5i92hjLwpjGHk2foR50G4bsu36/DUz09ibueIdjmYh0zd7HunzmktjaUOu1M2D0r0Qb9Al+Y+KzXxkcsbn7qJ70/z8huH7jBj4eIJeWQjdd0+Y8EBrHPJgYbCgiJaBnSqRxXgRzuIgck6URzFYIaV+OmT7k6P8+o31mh5rCCZQ==; 5:B+GgpLHrLdEigUYNodyXbRGlc4W0tzGzE2FL3HPjsbK+QKTN+YH2sSv5ewqHm4AO1KmJBYqMDE5U/RUQdY7Ddqr24OdCJae0Tt17UU3AwfmOX0fWZaHrR2HDBeNYoB1Mjsl/OoX8ObQeyVzrTWZFDpE/KXk2iKF3zh+pwFlRzck=; 7:fm0Lf8mubaU8Ov8wMS9UiDZcaNFFgFLbAbq6QNfDY3+BJykmGNsf1pW8L+No7fadoIDgblMUJYUrHkwx63s8fVMvssL5UkBhwCgi9737ELLEpONrgIQm4XrZUAKcsLBm47TEusT4qYqxbIf0CutnFw==
x-incomingheadercount: 44
x-eopattributedmessage: 0
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(201702061078)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322404)(1603101475)(1601125500)(1701031045); SRVR:SG2APC01HT151;
x-ms-traffictypediagnostic: SG2APC01HT151:
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(4566010)(82015058); SRVR:SG2APC01HT151; BCL:0; PCL:0; RULEID:; SRVR:SG2APC01HT151;
x-microsoft-antispam-message-info: DhU8EOSAUY63tMO5jCzZVvt8Wzi3rISbuF3nW0frK0apN7uk8mEJEOncI8QInzJi
Content-Type: multipart/alternative; boundary="_000_HK2PR0302MB2628AFFF9C8FAD836F9EB947BECC0HK2PR0302MB2628_"
MIME-Version: 1.0
X-OriginatorOrg: outlook.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: f12efbb0-867f-4c93-8261-502eceebfafa
X-MS-Exchange-CrossTenant-Network-Message-Id: d9c60949-5324-46bf-07b9-08d63e5b836a
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: f12efbb0-867f-4c93-8261-502eceebfafa
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Oct 2018 11:33:28.6483 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SG2APC01HT151
Archived-At: <https://mailarchive.ietf.org/arch/msg/ops-area/ht8qN3L6hQX_kUCVesr9sOZc0jU>
Subject: [OPS-AREA] It needs a new transport layer protocol to promote IPv6
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ops-area/>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Oct 2018 11:33:36 -0000

A new transport protocol should help



- to alleviate, if not to eliminate, the routing scalability problem,



-  to phase out NAT to eliminate processing delay caused by unnecessary middleboxes, and



- to make more efficient utilization of abundant IPv6 addresses.


A new transport protocol called FSP is proposed:

https://datatracker.ietf.org/doc/draft-gao-flexible-session-protocol/


Detailed motivations of designing FSP is explained in https://datatracker.ietf.org/doc/draft-gao-fsp-motivations/<https://datatracker.ietf.org/doc/draft-gao-fsp-motivations/>


In short, FSP is a connection-oriented transport layer provides mobility, multi-homing and multi-path support by introducing the concept of 'upper layer thread ID' (ULTID), which was firstly suggested in "Fuzzy-layering and its suggestion" (https://mailarchive.ietf.org/arch/msg/ietf/u-6i-6f-Etuvh80-SUuRbSCDTwg).



An integrity check code (ICC) field associated with the ULTID is designed in the FSP header to protect authenticity and optionally privacy of the FSP packet. An FSP packet is assumed to originate from the same source if the ICC value associated with certain destination ULTID passes validation, regardless of the source or destination address in the underlying layer.



The ULTID is assigned roughly the same semantics with Security Parameter Index (SPI) in MOBIKE [RFC4555]. Either the weak key or the shared secret key is indexed by the source or destination ULTID in the local context of the sender or the receiver, respectively.



FSP facilitates secret key installation by introducing the concept of transmit transaction. Mechanism of transmit transaction also provides the session-connection synchronization service to the upper layer.



FSP effectively separates the identifier role and routing locator role of the IPv6 address. The identifier role is localized while the routing locator role is kept global. By supporting mobility and multihoming at the transport layer it alleviates the routing scalability problem caused by supporting mobility and multihoming at the network layer.


When implemented over IPv6 abundance of IPv6 addresses makes NAT obsolete. However FSP over UDP is still friendly to NAT.


FSP eliminates the concept of 'port number'. Instead it proposes to take use of the lower 32 bits of the 128-bit IPv6 address as the 'upper layer thread ID'. It could considerably enhance allocation efficiency of the IPv6 address space.



Jason (Jun-an), Gao
General Manager,
Information Technology Department
Beijing Static Traffic Investment and Operation Co.,Ltd.