Re: [icnrg] Next steps on the 4G/LTE Draft

"Rahman, Akbar" <Akbar.Rahman@InterDigital.com> Fri, 16 November 2018 03:57 UTC

Return-Path: <Akbar.Rahman@InterDigital.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 52DF6124D68 for <icnrg@ietfa.amsl.com>; Thu, 15 Nov 2018 19:57:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-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=interdigital.onmicrosoft.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 2V01FjtCEOMl for <icnrg@ietfa.amsl.com>; Thu, 15 Nov 2018 19:57:12 -0800 (PST)
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-eopbgr760124.outbound.protection.outlook.com [40.107.76.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 84EB81298C5 for <icnrg@irtf.org>; Thu, 15 Nov 2018 19:57:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=interdigital.onmicrosoft.com; s=selector1-interdigital-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=GQexlKFNHCSaaNtNv3wy7ZXk9IcsuY/91Ubby1AZmn4=; b=p0sz3BBJxkcu4wUQb9XVqQ9dMG5n/8IXnvLJOYFd9Sn6jUXcZuH5sBvhIh3B2U2V9d234TIg8xZZDaj9A9rKWjjFcywqmmq6pKaUBSxY7W5EJWokk8wIP/2OFQoAeV8Abxp4vdkAfZJBsu2e9znAw9Kx0sg7/csJtAI0nSTjycU=
Received: from BN6PR10MB1329.namprd10.prod.outlook.com (10.173.29.143) by BN6PR10MB1475.namprd10.prod.outlook.com (10.173.30.149) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1294.23; Fri, 16 Nov 2018 03:57:09 +0000
Received: from BN6PR10MB1329.namprd10.prod.outlook.com ([fe80::3569:c4fa:2270:9b21]) by BN6PR10MB1329.namprd10.prod.outlook.com ([fe80::3569:c4fa:2270:9b21%5]) with mapi id 15.20.1294.045; Fri, 16 Nov 2018 03:57:09 +0000
From: "Rahman, Akbar" <Akbar.Rahman@InterDigital.com>
To: "Oran, Dave" <daveoran@orandom.net>, icnrg <icnrg@irtf.org>
Thread-Topic: [icnrg] Next steps on the 4G/LTE Draft
Thread-Index: AQHUdmbIZOMaPy78RUuviZ2U5SScsqVRyn+A
Date: Fri, 16 Nov 2018 03:57:09 +0000
Message-ID: <BN6PR10MB13295B8CB97DC732DC72A1D0E7DD0@BN6PR10MB1329.namprd10.prod.outlook.com>
References: <840FA4F4-2A4F-4DC7-AEE8-8EB3C11396B9@orandom.net>
In-Reply-To: <840FA4F4-2A4F-4DC7-AEE8-8EB3C11396B9@orandom.net>
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=Akbar.Rahman@InterDigital.com;
x-originating-ip: [70.30.7.212]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN6PR10MB1475; 6:clJSH/TjKRuVvXfGWXe5rhwOOFZxj5915w5MjAcgL0dNpIY3qcm7zY8LCfhERrdTE2QgOHN1FoXC3pIM5iDGl+KWDlZmWUIU2nMNcoxu0JKmcO5dP2qMU4QVD1iFh6UOA7sOKlplG5flr4WrvK6UNcmMssYYCHMIL6NUi0B7wTi46k8Enik8gGl43lNDSOoPNzc0Eu8MIqn805UVy+OWJwDzUbzD/P2nqH9cBEQy+rP1oFl/xSGqxEa0lazGvQhdL+Igk8HhPm08jIJmtSJRg7vsqg+uEIYN3U/nEzGENlTA9tBzQfTgoNv9E1v5DQjhfBg5Ebbi5D4alJOALqGRm//TvJYcnmE2eyG1u0su/Sk/LGQ3v5burPj8BKFflSm0+30Ldon5NzJ+vOk4ds6VKEo9NralNOUha2EiEy8/pxmB9ymnotXyc+nivBAaGUm21N6Ear8W6WAK2x6wljXHiw==; 5:YgxeO0wUJh8ZjF/RPJ4rzcvc00Gnm9rtk+uPr1RkMuXG7wLgeRdUV2iKbbTJID+PLXqktTg6LvI/UHFH45+zNoMdjcGQ0TmH7IOeGj8UUpESikIpfhMvUdSssfCzO6yHCXDYJdhOhziYVIFUP+hePvg6x1H2CPIsOAUMed22SVM=; 7:Wpz6BnQn0O/8wq6lT/4NwU1kCIrVgtfiWCOIiFvbBetJtCcfC5bXbnGYHc0HiU6jfbqqy6FJNWhlBkZBj8fxRTBriocyToofrKlWoxIXdNXZGjidbVsUMHMV+Jtmws5RKz+HAQBL+wWRoH2InfnZpQ==
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 029f8c2d-3fc8-4960-9c63-08d64b779549
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390098)(7020095)(4652040)(8989299)(5600074)(711020)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7153060)(7193020); SRVR:BN6PR10MB1475;
x-ms-traffictypediagnostic: BN6PR10MB1475:
x-ld-processed: e351b779-f6d5-4e50-8568-80e922d180ae,ExtAddr
x-microsoft-antispam-prvs: <BN6PR10MB14752A54866EF3640BCC74ADE7DD0@BN6PR10MB1475.namprd10.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(120809045254105)(21748063052155)(28532068793085)(190501279198761)(227612066756510);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(3002001)(10201501046)(93006095)(93001095)(3231415)(944501410)(52105112)(148016)(149066)(150057)(6041310)(20161123560045)(20161123558120)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123562045)(20161123564045)(201708071742011)(7699051)(76991095); SRVR:BN6PR10MB1475; BCL:0; PCL:0; RULEID:; SRVR:BN6PR10MB1475;
x-forefront-prvs: 0858FF8026
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(396003)(376002)(346002)(366004)(39840400004)(199004)(189003)(40134004)(66574009)(316002)(110136005)(478600001)(106356001)(33656002)(86362001)(229853002)(97736004)(105586002)(2900100001)(99286004)(76176011)(55016002)(7696005)(25786009)(6436002)(6506007)(5660300001)(236005)(790700001)(9686003)(6306002)(102836004)(53546011)(54896002)(53936002)(74316002)(733005)(6116002)(71190400001)(71200400001)(11346002)(446003)(476003)(186003)(72206003)(8936002)(5024004)(68736007)(7736002)(966005)(256004)(14454004)(81166006)(8676002)(9326002)(26005)(81156014)(14444005)(3846002)(2906002)(6246003)(606006)(486006)(66066001)(85282002); DIR:OUT; SFP:1102; SCL:1; SRVR:BN6PR10MB1475; H:BN6PR10MB1329.namprd10.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: InterDigital.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: vq7fekjxz+fkdH3L1w/n1OhbB2egB7jL5g0Upfv2Lk7quoQZL0wb1p0VJwu1X708fMEyV9OsRsdGu3nPk14XJ9MELRbvT0wDX6jxtHXUjHdSn/yL15GS9AoD6wgDQ7Ub/4zJ10i2JIpFML6OSLTYkwqWHWB/UJbIAhrZGzVJkJ/paBff7txZAM9muTKCHlUE4YE/comUKHJM/n6/CF2mGmcMOxWmCkFNDE17HTiTuUGLjgUKydY0o6WjzhSYY25HkeBjVtA/f10ERgW/qLzZmDnwxIsL57Aykqcc1l9GC2ro1w21mXuVPuAob4MIeP9v7jXzP9XTEYPx80WUDhhlCadOGBLk0J6Q+3AS5LmFo8Y=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_BN6PR10MB13295B8CB97DC732DC72A1D0E7DD0BN6PR10MB1329namp_"
MIME-Version: 1.0
X-OriginatorOrg: interdigital.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 029f8c2d-3fc8-4960-9c63-08d64b779549
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Nov 2018 03:57:09.6473 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: e351b779-f6d5-4e50-8568-80e922d180ae
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR10MB1475
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/xwM4idtIzucfyHrJrNE-ZlttyRQ>
Subject: Re: [icnrg] Next steps on the 4G/LTE Draft
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: Fri, 16 Nov 2018 03:57:16 -0000

Hi Dave,

Following is my feedback to the two questions that you raised:


>1.  Do you think this is ready for an RG last call, and if not, what additions/changes you would like to see to move it forward.

Yes, I think it is ready for an RG last call after update of the self-identified open item in https://tools.ietf.org/html/draft-irtf-icnrg-icn-lte-4g-02#section-6
“We are currently evaluating the ICN deployment options, described in section 4<https://tools.ietf.org/html/draft-irtf-icnrg-icn-lte-4g-02#section-4>, using LTE gateway software and ICN simulator.”

It would be nice to get a quick update of the conclusions of this investigation after which time I think it would be ready for the RG last call.  (I note that we have discussed this draft in multiple IETF meetings as well as having several off line technical reviews).



>2.  Do you think the appropriate target for this particular set of work is the “Informational” or “Experimental RFC track. It seems to fall somewhat in a grey area between the two.
I would vote for Informational track as most of the protocol changes seem 3GPP specific.


Best Regards,

Akbar

From: icnrg [mailto:icnrg-bounces@irtf.org] On Behalf Of Oran, Dave
Sent: Wednesday, November 7, 2018 1:51 AM
To: icnrg <icnrg@irtf.org>
Subject: [icnrg] Next steps on the 4G/LTE Draft


At the ICNRG Interim meeting at IETF 103, we got an update status on https://datatracker.ietf.org/doc/draft-irtf-icnrg-icn-lte-4g/

This document is reaching a mature state and the chairs would like to get a sense from the RG participants on two questions:

  1.  Do you think this is ready for an RG last call, and if not, what additions/changes you would like to see to move it forward.

  1.  Do you think the appropriate target for this particular set of work is the “Informational” or “Experimental RFC track. It seems to fall somewhat in a grey area between the two.

Please reply to the list. We would like to have feedback by the end of next week or so (November 17).

Dave, Dirk, & Börje.

[Banner]
This e-mail is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and/or otherwise protected from disclosure to anyone other than its intended recipient. Unintended transmission shall not constitute waiver of any privilege or confidentiality obligation. If you received this communication in error, please do not review, copy or distribute it, notify me immediately by email, and delete the original message and any attachments. Unless expressly stated in this e-mail, nothing in this message or any attachment should be construed as a digital or electronic signature.