Re: [ieee-ietf-coord] ITU-T SG13 / FG NET-2030

"Andrew Myles (amyles)" <amyles@cisco.com> Sun, 17 November 2019 20:56 UTC

Return-Path: <amyles@cisco.com>
X-Original-To: ieee-ietf-coord@ietfa.amsl.com
Delivered-To: ieee-ietf-coord@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED5281201EF for <ieee-ietf-coord@ietfa.amsl.com>; Sun, 17 Nov 2019 12:56:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.489
X-Spam-Level:
X-Spam-Status: No, score=-14.489 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, T_KAM_HTML_FONT_INVALID=0.01, 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=KM/WiKLt; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=EV4OOh3P
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 AKs5zoYfiwpq for <ieee-ietf-coord@ietfa.amsl.com>; Sun, 17 Nov 2019 12:55:58 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 221591200B5 for <ieee-ietf-coord@ietf.org>; Sun, 17 Nov 2019 12:55:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=15157; q=dns/txt; s=iport; t=1574024158; x=1575233758; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=NDsEa7X6Y5e00PGTJqEWungOOdKgCVLuTXflL60uE7I=; b=KM/WiKLtw7GldpcgIZyLiiSvuc3QppLszeIIRYyBRMFI4DWRX1lj+w4x qtHziFV0OCHCRLYtTf1cyjoZRd+8h/8IYzpwhJCgFt3aaK3envzpNewkF 2GK3RkTmvLCicUY/7AAzLKz1c3VYs6nZXpAZLVc//wOLvShsj5uy/PX0+ E=;
IronPort-PHdr: =?us-ascii?q?9a23=3AxMQ5eRyiHW810vHXCy+N+z0EezQntrPoPwUc9p?= =?us-ascii?q?sgjfdUf7+++4j5YR2N/u1j2VnOW4iTq+lJjebbqejBYSQB+t7A1RJKa5lQT1?= =?us-ascii?q?kAgMQSkRYnBZuMDFz/IeXCZC0hF8MEX1hgrDm2?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0A/GQC1stFd/4ENJK1lHQEBAQkBEQU?= =?us-ascii?q?FAYF+gRwvUAVsWCAECyqHbwOKcU6CEJMehGKCUgNUCQEBAQwBARgBCgoCAQG?= =?us-ascii?q?EQAKCIyQ4EwIDCwEBBAEBAQIBBQRthTcMhVEBAQEBAwEBEBsTAQElBQIMCwQ?= =?us-ascii?q?CAQgRAQMBASgHJwsUAwYIAgQBEggagwGBeU0DLgECDKIWAoE4iGCCJ4J+AQE?= =?us-ascii?q?FhH8YghcDBoE2jBUYgUA/gRABRoJMPoEEUIEOAQGBYyQHgxWCLJVal3VeCoI?= =?us-ascii?q?qlWqaEY5ImggCBAIEBQIOAQEFgWkigVhwFTuCbFARFJEag3OFFIU/dIEojWU?= =?us-ascii?q?BAQ?=
X-IronPort-AV: E=Sophos;i="5.68,317,1569283200"; d="scan'208,217";a="440727358"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 17 Nov 2019 20:55:56 +0000
Received: from XCH-ALN-006.cisco.com (xch-aln-006.cisco.com [173.36.7.16]) by alln-core-9.cisco.com (8.15.2/8.15.2) with ESMTPS id xAHKtt85021652 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Sun, 17 Nov 2019 20:55:55 GMT
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by XCH-ALN-006.cisco.com (173.36.7.16) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sun, 17 Nov 2019 14:55:55 -0600
Received: from xhs-aln-001.cisco.com (173.37.135.118) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sun, 17 Nov 2019 15:55:54 -0500
Received: from NAM03-DM3-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; Sun, 17 Nov 2019 14:55:53 -0600
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=hTTbhFU8y6G8IMzwDbtKcJkmpeIXTzpU3uTtRjC2qvWwEY2TtU5S40HkLOHOnpzJiRWz4DPXt3LWRxi0NLAcdoJTWHOHXVOBLhHN8B/oTrULNQlk8Wbyn926HLJrUjP5TYX9jNhTT0P+GYf8Va4qGNBPNgik4AKr7vQKDCdpEUuIZ/xeJr7FsFl5cOHhOE29GrRDDX+D9/EdcRiXy9fOoVY3ZGAXmC9b87HWdUmvbohctWmS4vkJO4qBE7VrAqXvodV9jzva2CwIhzOHoDlheJ01UQWUTvSmOBiNmWDOcEzYOKv6Sxe3XyyA5c8KLCYLsXObAvCZFJypU4rnnk+MVQ==
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=nbJTTHxfRaxCB36dK17EpvJ7ZU/eO1B0r8Y91JzEciU=; b=U3m7C4RJxXAcaM9suP144pREbhxYlD20esjj1p5hWB39FADdDX+anIv5O9Umyov/0+e61/BEEe0Ej/ESuFGmsFlQNOXuSWJxFFrD3uOQ2UAFpfQ4txZ36/xcK3L0uvsCbFylmH0EcyFUT59uf2FmBxkCJ7W7k+gLSk/URGLCqE19jjvM2N9QKZ0Eo00xeTyMBzyc+vcQIRuBjaYvBqyd2sI0twIyH4K5kc88vrZ4y9I9YKEwP0X/xQqQxXu/H8GghuawYH3IK71bQCnLLA+A+TNIXPnhW60YO0vi6+ZU9Zz8C6VkTM6f2TseN1iK/UrIBEtFmQtS4I/62BQpNGHXEA==
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=nbJTTHxfRaxCB36dK17EpvJ7ZU/eO1B0r8Y91JzEciU=; b=EV4OOh3PG1bSciJd1MXYAwHxj6uxqedVv3lE0ELh5F+oxPJUSc1pDwvRrZKmMhCVh1SlJzn79/dZMj8oBKkLfDX2ANsEKCncCeON8a5ACSKm5yEa9gY8UQog83vMBv7QI6rYYCPLBzDuC4VH9CF7EVjAtGI0o5y3v17ESPTEvn0=
Received: from MN2PR11MB4461.namprd11.prod.outlook.com (52.135.39.93) by MN2PR11MB3950.namprd11.prod.outlook.com (20.179.150.29) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2451.29; Sun, 17 Nov 2019 20:55:53 +0000
Received: from MN2PR11MB4461.namprd11.prod.outlook.com ([fe80::e924:7c82:baed:a677]) by MN2PR11MB4461.namprd11.prod.outlook.com ([fe80::e924:7c82:baed:a677%7]) with mapi id 15.20.2451.029; Sun, 17 Nov 2019 20:55:53 +0000
From: "Andrew Myles (amyles)" <amyles@cisco.com>
To: Russ Housley <housley@vigilsec.com>, "<ieee-ietf-coord@ietf.org>" <ieee-ietf-coord@ietf.org>
Thread-Topic: [ieee-ietf-coord] ITU-T SG13 / FG NET-2030
Thread-Index: AQHVnCn9J8NDLxCefEaf4wS211GSk6eP1r3g
Date: Sun, 17 Nov 2019 20:55:52 +0000
Message-ID: <MN2PR11MB44618CBD0231468892EF0E6CCF720@MN2PR11MB4461.namprd11.prod.outlook.com>
References: <A1623302-8C4F-4756-A9C9-0AAA34BFA9DB@vigilsec.com>
In-Reply-To: <A1623302-8C4F-4756-A9C9-0AAA34BFA9DB@vigilsec.com>
Accept-Language: en-AU, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=amyles@cisco.com;
x-originating-ip: [2001:420:c0d0:1002::51]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 739b2898-ab79-4249-b7d4-08d76ba088db
x-ms-traffictypediagnostic: MN2PR11MB3950:
x-microsoft-antispam-prvs: <MN2PR11MB3950E83F610E8DF321627F0ACF720@MN2PR11MB3950.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 02243C58C6
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(376002)(366004)(39860400002)(136003)(396003)(346002)(189003)(63294003)(13464003)(199004)(66574012)(5660300002)(2906002)(476003)(55016002)(54896002)(9686003)(236005)(46003)(6246003)(71190400001)(966005)(606006)(256004)(14444005)(6306002)(316002)(14454004)(71200400001)(110136005)(7736002)(6436002)(25786009)(229853002)(6116002)(74316002)(486006)(7696005)(52536014)(81156014)(76176011)(81166006)(8676002)(186003)(790700001)(99286004)(8936002)(86362001)(6506007)(478600001)(53546011)(33656002)(11346002)(446003)(102836004)(66476007)(66556008)(66446008)(64756008)(66946007)(76116006)(491001); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3950; H:MN2PR11MB4461.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: BCL:0;
x-microsoft-antispam-message-info: yzAQBtLjT4Vaj68TdgQ38JJ1vABd+RgE+D2JbwONIWyPZHm46h57Xh85nNKKnTNOaG+Ir+qUKZt77ewRFlmXHzIN5BjucmXf9bFybR2eRdMd79R1q1syn3uAgv4L5sIWxaZlUbXQcA7KhxKIgy1qoUHtQuOOP0XiY3gaDzNaWN7OR0OiJXwlDP0bdBhwy7igpLHqBvGUT6dglFiv3w+q/rqBcEVf1qw2TR6ZslZmmeYvVGdpcvc9tah+Bw7MswC1ZQTvivIZkM1K1kJALpWmX5WjWzT+j5NDxUnzVi2Fz3npmam7GkFjIp8SzwGsUYNt0tk9xrtcKh92oamKz3LUW/7KazptIDfnWaQkymA3azCwM1KARu3DQ7DzbNQn6EAA748SfXeRKSt/tyqFzPcDvtWFU/x4o5npqDEesE5O2w5WSsN3Qpb7R0Yr3pQqQIXg
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MN2PR11MB44618CBD0231468892EF0E6CCF720MN2PR11MB4461namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 739b2898-ab79-4249-b7d4-08d76ba088db
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Nov 2019 20:55:53.0105 (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: 76JWQt88irzI95MC2VydGy0AsQoNoib53fba2BKWBiL4TYeE0EH6C2KRFNFfTWecIr5Oibsg75gzGPC/UnfH1A==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3950
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.16, xch-aln-006.cisco.com
X-Outbound-Node: alln-core-9.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ieee-ietf-coord/NkBTu_sF5hRExeENMSzuDT3Iy70>
Subject: Re: [ieee-ietf-coord] ITU-T SG13 / FG NET-2030
X-BeenThere: ieee-ietf-coord@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Management-level discussions between IEEE and IETF on topics of interest to both SDOs <ieee-ietf-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ieee-ietf-coord>, <mailto:ieee-ietf-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ieee-ietf-coord/>
List-Post: <mailto:ieee-ietf-coord@ietf.org>
List-Help: <mailto:ieee-ietf-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ieee-ietf-coord>, <mailto:ieee-ietf-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Nov 2019 20:56:01 -0000

G'day Russ



You may also be interested in some work in ISO/IEC JTC1/SC6/WG7. This WG is generally planning to replace the entire internet protocol stack. :)



More specifically, in recent times a NP Ballot (ISO/IEC NP 4396) has started  (the ballot closes 1 Feb 2020) to standardise RINA. This is a protocol that I understand John Day proposed in the IETF some time ago, but it was not taken up.



The proposed scope is:

This NP will define the Recursive IPC Network Architecture, an architecture that can meet the requirements set out in ISO/IEC TR 29181-1. It can deliver services beyond the limitations of the current Internet by providing security and guaranteeing QoS while maintaining scalability and ease of configuration. This single NP will consist of multiple specifications as follows:

*       Part 1: Architecture

*       Part 2: Common application connection establishment phase

*       Part 3: Common distributed application protocol

*       Part 4: Flow allocator

*       Part 5: Error and flow control protocol

The work to be carried out in this project requires additional protocol specifications for the future work, which support defined architecture. Current proposed specifications are included in this document as drafts for the work to be undertaken.



The purpose and justification is:

There are significant conundrums present in the current Internet architecture. Multi-homing and mobility of hosts are not easily achievable with a standard TCP/IP stack. APIs are not standardised, making the connection between systems a problem. The Internet also has well known issues related to security, Quality of Service (QoS) and multicast. One of the worst problems is the explosion in complexity by the ever growing Internet protocol suite. These issues illustrate the need for well-defined network architectures that encourage networking engineers to apply a disciplined approach towards solving networking problems. This is the right moment to prepare specifications as different companies and governments are backing the deployment of RINA(Recursive Inter-Network Architecture)-enabled networks.



The ballot includes relatively complete drafts, which were written by John Day (Boston University), Eduard Grasa (i2CAT Foundation) & Miquel Tarzan (i2CAT Foundation).



The NP was submitted by the Spanish NB but it has support from at least the US NB and the Belgium NB



Andrew



-----Original Message-----
From: ieee-ietf-coord <ieee-ietf-coord-bounces@ietf.org> On Behalf Of Russ Housley
Sent: Saturday, 16 November 2019 2:00 PM
To: <ieee-ietf-coord@ietf.org> <ieee-ietf-coord@ietf.org>
Subject: [ieee-ietf-coord] ITU-T SG13 / FG NET-2030





I was recently told about an effort to take over significant standards work currently being led by the IETF.   The work taking place in ITU-T Study Group 13 / Focus Group on Technologies for Network 2030, lead by Dr. Richard Li as the FG NET-2030 chairman. The group appears to be looking to redesign the layer 3 and 4 protocols to centralize functions that would enable/facilitate data aggregation and surveillance.



Does anyone on this list know if FG NET-2030 is actually gaining ground?



Russ

_______________________________________________

ieee-ietf-coord mailing list

ieee-ietf-coord@ietf.org<mailto:ieee-ietf-coord@ietf.org>

https://www.ietf.org/mailman/listinfo/ieee-ietf-coord