IETF Logo Mail Archive

Re: [icnrg] Possible adoption of "Enabling ICN in 3GPP's 5G NextGen Core Architecture" (draft-ravi-icnrg-5gc-icn-04)

Cedric Westphal <cedric.westphal@futurewei.com> Thu, 19 September 2019 18:18 UTC

Return-Path: <cedric.westphal@futurewei.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56B6C1200E0 for <icnrg@ietfa.amsl.com>; Thu, 19 Sep 2019 11:18:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 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, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.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 Ccqfm0ehGSRP for <icnrg@ietfa.amsl.com>; Thu, 19 Sep 2019 11:18:11 -0700 (PDT)
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-eopbgr770122.outbound.protection.outlook.com [40.107.77.122]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6FF081200F8 for <icnrg@irtf.org>; Thu, 19 Sep 2019 11:18:11 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ItM3egEhgMXwmKzPE11eAVTPZyqsX6rxvlRjyA9kNv/AkMIo0Wg+7Yly04lDL216HKbn7rq8cdwK/rBfLHktDPUw8k5CXOe+MJ50Ez+nq9bFDigGQgXZK+QPRQjdFHpmQki2dxBcWzmbWhhIABgXSDrgUYtNd2M9dfDxub1VA5muBwA4RME2yeWX9sJkyGr1P2DRhDnOq5LnisClntVHE1KPRjcNOAwOJwDF7cQhk7E3TvfCJsRvTEBcqiQXA9S+/27y1cgjzvEtBHBTBYcpQz4c2z2dzn+bNlKy2hQDzxd31KzzZ2xjwSBPYlcPLP9WzjCH6q63Er9nFdB+rgDsFg==
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=gLmKEBIereWVQtJsxxT+qysL9BzK8yGc2+3esglTv38=; b=LPWzUu2wxv9gMXdFBZqeby9WOnq5QWzManIj9HWzcLbtDTa/e3MQT2Qqw3lMdqOZ+4PtF08I/22tKYjL4o7QUIn7RwtSo6Zy2X8mHrj8rXzvWSqHEhCwjRdOAB567v3k8tfjKUEhlJCYlWzGIt6A2yU4Cj8MOPaFjRdzCiCXoAnK60niRb0298i6j3SGFqUM73bY0IsoaTNpaYNtO5tTCHdC2vNtyvKF0Hl1muykAPM77JEjN3O5aYeLzp9oJldocIVVW6sUJgVKnNqx3aW71YOrg4Ft6oi9FLe13xFXDZCCgwF8QNC3w659I2UHDf8DHTITp9blO9PaBfDG2UI1LA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=futurewei.com; dmarc=pass action=none header.from=futurewei.com; dkim=pass header.d=futurewei.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=gLmKEBIereWVQtJsxxT+qysL9BzK8yGc2+3esglTv38=; b=Wc7RBY5wOB9apX/+dkh9IlQe40FBczaSvBsYTXXaOYjfCiLt/RKFQVWUd3/h6mEWN0Oj3k/VaM1rEdMQ3WjbqHGoUn05bCJULTLfqyS9w+2DyRO1fb1UrH1jzKoLLqgHjGeJZ5CjgOZKd8jHdF3BKMT6TFFYUuNLpdGdiPEGdVQ=
Received: from CY4PR1301MB1927.namprd13.prod.outlook.com (10.171.223.26) by CY4PR1301MB1925.namprd13.prod.outlook.com (10.171.223.24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2305.10; Thu, 19 Sep 2019 18:18:08 +0000
Received: from CY4PR1301MB1927.namprd13.prod.outlook.com ([fe80::58eb:d899:486b:53c]) by CY4PR1301MB1927.namprd13.prod.outlook.com ([fe80::58eb:d899:486b:53c%7]) with mapi id 15.20.2284.009; Thu, 19 Sep 2019 18:18:08 +0000
From: Cedric Westphal <cedric.westphal@futurewei.com>
To: Dirk Kutscher <ietf@dkutscher.net>, icnrg <icnrg@irtf.org>
Thread-Topic: [icnrg] Possible adoption of "Enabling ICN in 3GPP's 5G NextGen Core Architecture" (draft-ravi-icnrg-5gc-icn-04)
Thread-Index: AQHVbL25IjACglXW9EmSMHSzP7QmJqcxt5EKgAGWybA=
Date: Thu, 19 Sep 2019 18:18:08 +0000
Message-ID: <CY4PR1301MB1927495C1DCC7D766EB5222CFF890@CY4PR1301MB1927.namprd13.prod.outlook.com>
References: <BD080723-2E02-4C21-AD7C-3D7329ABB9F3@dkutscher.net> <CAGhfKzfku+CDW02GZhKYxGKfKAQyOqGBk2Wftj2OvN-3vLZrGA@mail.gmail.com> <CAG9K2Pk1SHz_BEYdf5dACPhxgLZQ6uSkRHqiWr-ctEBkMc__Gw@mail.gmail.com>
In-Reply-To: <CAG9K2Pk1SHz_BEYdf5dACPhxgLZQ6uSkRHqiWr-ctEBkMc__Gw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=cedric.westphal@futurewei.com;
x-originating-ip: [12.111.81.80]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 48038d7a-ebb2-458d-1c80-08d73d2db94c
x-ms-traffictypediagnostic: CY4PR1301MB1925:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <CY4PR1301MB19253F3DC15BA674640CADEDFF890@CY4PR1301MB1925.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 016572D96D
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(346002)(396003)(376002)(39850400004)(136003)(366004)(22974007)(189003)(199004)(256004)(66946007)(66066001)(52536014)(66476007)(66556008)(64756008)(66446008)(76176011)(5660300002)(7696005)(186003)(486006)(26005)(53546011)(476003)(6506007)(76116006)(102836004)(446003)(99286004)(110136005)(11346002)(71200400001)(71190400001)(316002)(44832011)(86362001)(606006)(9686003)(14454004)(54896002)(6306002)(236005)(81166006)(81156014)(55016002)(3846002)(7736002)(790700001)(6116002)(478600001)(8676002)(229853002)(33656002)(6436002)(966005)(6246003)(9326002)(8936002)(74316002)(25786009)(2906002); DIR:OUT; SFP:1102; SCL:1; SRVR:CY4PR1301MB1925; H:CY4PR1301MB1927.namprd13.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: futurewei.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: bP/UmUV7SGtMsHGPOr/NYFNjxeGZlCh3zPQQ0JlGH8X/anDd40V7LrwVEMvXTt4cAHdYiGcndsrmZO2q4RgdvgSJEGlsM/MbiUXyGqi8MeXX8LLn/GlW016lxyx+PW1moXfYBmgXba/ddsEkWfksP3Z0HUtepJoW6goMlLN5Cjj3XkkxlZwwPjYP/fRDox9lxe3KBRbiwelxmnVKJywfJreqrlVl9mj+bc91/uP1Y/DKpfTgDa0DmXUDqQEx8pul04MAsV6rwu+O4OMXzgfHdFtsSX5qJFOu41KFQuecNJ/lNjSlXnUAGLHfWoLIXpHN7woPeho4WuF6k9meeK1hOpGv6IGgSrENqAQesjgszkB8vvbiXqqqjkIlc7B1Q9ucAtQh78ryKZP7ervprWCPLFNzSajhHfzydHEDyLNCo3g=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_CY4PR1301MB1927495C1DCC7D766EB5222CFF890CY4PR1301MB1927_"
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 48038d7a-ebb2-458d-1c80-08d73d2db94c
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Sep 2019 18:18:08.5671 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: ieD1ez9ERxKaA16fz9Rw2mKJ4NVVM9BEWvJcrgYn1ZH4lyWo3IVbS4Ba9J05bxePPl6v1qa3TzqP/UiXHnjv4w==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR1301MB1925
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/aF56aICOfba19oxWN3XXYUoj_Uk>
Subject: Re: [icnrg] Possible adoption of "Enabling ICN in 3GPP's 5G NextGen Core Architecture" (draft-ravi-icnrg-5gc-icn-04)
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/icnrg/>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Sep 2019 18:18:14 -0000

Hi Dirk,

I support adoption of this draft. It is a very interesting discussion on how to enable ICN over the 5G architecture.

A couple editorial comments:

  *   “where 5G technology is considered as one of the promising alternatives.” -> alternative to what?
  *   “realtime” -> real time or real-time
  *   “application- bound identifier and name resolution split principle considered for the ICN is shown to handle host mobility quite efficiently” -> unclear sentence. Maybe: “ICN uses a split between the application identifier and the name resolution that is known to handle host mobility efficiently”
  *   “design principals” -> “design principles”
  *   “utilize API design” -> “an API design”

Best,

C.


---------- Forwarded message ---------
From: Dirk Kutscher <ietf@dkutscher.net<mailto:ietf@dkutscher.net>>
Date: Mon, Sep 16, 2019 at 11:36 AM
Subject: [icnrg] Possible adoption of "Enabling ICN in 3GPP's 5G NextGen Core Architecture" (draft-ravi-icnrg-5gc-icn-04)
To: ICNRG <icnrg@irtf.org<mailto:icnrg@irtf.org>>


Hi ICNRG,

At the ICNRG meeting at IETF-105 in Montreal, we discussed the possible
adoption of https://datatracker.ietf.org/doc/draft-ravi-icnrg-5gc-icn/<https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ravi-icnrg-5gc-icn%2F&data=02%7C01%7Ccedric.westphal%40futurewei.com%7C1278917ce119463ea73a08d73c5fa868%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637044253849499323&sdata=y6MacrSUa056iZsRKSGr5O3t%2BqDRdY31fgGR4ECr0aE%3D&reserved=0> .

During the meeting, no objection was raised, but not many people had
read the latest version of the draft. As usual, we would like to follow
up on the mailing list, so we are looking for statements indicating
support for adoption or concerns against it from people who are 1) not
co-authors and 2) have read the latest version.

Thanks and best regards,

Chairs

_______________________________________________
icnrg mailing list
icnrg@irtf.org<mailto:icnrg@irtf.org>
https://www.irtf.org/mailman/listinfo/icnrg<https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.irtf.org%2Fmailman%2Flistinfo%2Ficnrg&data=02%7C01%7Ccedric.westphal%40futurewei.com%7C1278917ce119463ea73a08d73c5fa868%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637044253849499323&sdata=vaqzel4d%2BDaViQaXlm5LsUCXhcA8HpqUBI3KGzA4IOM%3D&reserved=0>

v2.23.0 | Report a Bug | By Email