IETF Logo Mail Archive

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

"Anil Jangam (anjangam)" <anjangam@cisco.com> Fri, 04 October 2019 16:14 UTC

Return-Path: <anjangam@cisco.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 20ED2120086 for <icnrg@ietfa.amsl.com>; Fri, 4 Oct 2019 09:14:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 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, 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=UFoBEFpw; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=taGU44de
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 jEJ8eBZKiAb5 for <icnrg@ietfa.amsl.com>; Fri, 4 Oct 2019 09:14:15 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5FBD0120048 for <icnrg@irtf.org>; Fri, 4 Oct 2019 09:14:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1080; q=dns/txt; s=iport; t=1570205655; x=1571415255; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=jkyBop34+8QXUrjdYrtSTB8hltwu1tAQ4NEqlfKMBIc=; b=UFoBEFpw+75+1PIC6zwFSi00Vac8rSfibRcEr/8O3o/uML6KMQf69RcD 3IjZ9mitAqqCiiW5m2wySWCwmKoGv4RiFs27BvMteGrYs52VqJcwU/tsi O2KDWbbYr8NcqN20DgxTS2Thv/3EAsItQfYzWArFNK5kCLRl2wR8/1YnH c=;
IronPort-PHdr: 9a23:wKOybxQDiEdLgfnGi/Zn7glhqdpsv++ubAcI9poqja5Pea2//pPkeVbS/uhpkESXBNfA8/wRje3QvuigQmEG7Zub+FE6OJ1XH15g640NmhA4RsuMCEn1NvnvOiU8Hs1EW1Zg13q6KkNSXs35Yg6arw==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BxAAAQb5dd/4cNJK1mHAEBAQQBAQwEAQGBUwcBAQsBgUpQA21WIAQLKoQiYoJlA4RYhXBNmgiBLoEkA1QJAQEBDAEBGAsKAgEBhEACF4IwIzQJDgIDCQEBBAEBAQIBBQRthS0MhUwCAQMBARAREQwBASwMDwIBCA4ECAIfBwICAiULFQIOAgQBEiKDAAGBagMdAQIMpBsCgTiIYXWBMoJ9AQEFgUhBgwEYghcDBoEMKAGMDRiBQD+BOB+CTD6CYQEBAwGBXYMNMoImj2udUQqCI4cIjhAbgjqLeosMjiuIIJERAgQCBAUCDgEBBYFSOYFYcBU7KgGCQVAQFIFPOIM7hRSFP3SBKZBGAQE
X-IronPort-AV: E=Sophos;i="5.67,256,1566864000"; d="scan'208";a="343917829"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 04 Oct 2019 16:14:14 +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 x94GEEM5015723 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 4 Oct 2019 16:14:14 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, 4 Oct 2019 11:14:13 -0500
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 4 Oct 2019 11:14:13 -0500
Received: from NAM05-DM3-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Fri, 4 Oct 2019 11:14:13 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=OSun2N8HYxeDLCxnSag7zegVYhWdoumTEocML4fOmYbO2IFM583zwNNgPt8QFuDD+kUdHrgw8MOYg5jlqkd01ssYxrAHFFd6ysSrk7Hq++BG8HymBYlvg8U4jt9R/dldV4rU3BNRqMhwgjOUNAQ1uJsRbOlecha04TfzOceKmRa7Qr4sX6BEBPTnprK/bD2hfV1RUGo+w/fMrf/Uzbopc513ByJnXvz/LYrGOGR16eMSVbRIXyYF7qBRuMm0k69EHN4Wc8gBHvsmFSjz3t76STi89dgiZ9U9iecYYx0CMj5QsCLt0ZfglbkUBRaZwyv7C+sV5gz1Mbd3c6Cl33ZICw==
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=jkyBop34+8QXUrjdYrtSTB8hltwu1tAQ4NEqlfKMBIc=; b=QbXVmwY6O5m1i3/7CMTO4FPQdza7CSPgge5KPrFj+2c0tGZIpSAzucbPXBSVjEUNbhz0DO4g7MlYB8AKMQVJWSGX/tMIUnUiO/f+KFSCVb+NLfuzEA7lbtTBBlvKGtuyWi+bCSJMJgo4luZR8E55EHlSLPq6F4ZS+l+/Zjy64SOwgnOpuwNzG51mfdUE5Kw00AMhFnE4pKWE9TXYkx5jjj6WT/lK2IrUGB8cQiZ3+BFZ2/ctKXe675F/IsexWb+/UXupP6/pd816K2AkIBlSp+vUykWG1bhz1xWPIe0/m+eqAgYzoplPV163oexo+EB6P+u99GV4ZTKsMXn0+ozWOg==
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=jkyBop34+8QXUrjdYrtSTB8hltwu1tAQ4NEqlfKMBIc=; b=taGU44deXjgTEwm3RchxgL6Zi5MXZvjKBpa1A9mlSYJqGlM5AW/L2X9sDA2YDFhrJ/IFCxrGk7iOGCzhubbfItunTZrf5Q80E5UhhED1H8oXqJoG9nt+9A3j8B7vH4DBZlebIR3tJRVCwTAHy87WX4WyJFWzMew60/Y3zVVmcIQ=
Received: from BYAPR11MB3687.namprd11.prod.outlook.com (20.178.237.160) by BYAPR11MB3368.namprd11.prod.outlook.com (20.177.186.77) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2305.20; Fri, 4 Oct 2019 16:14:12 +0000
Received: from BYAPR11MB3687.namprd11.prod.outlook.com ([fe80::5dd4:f4a6:2c33:4102]) by BYAPR11MB3687.namprd11.prod.outlook.com ([fe80::5dd4:f4a6:2c33:4102%3]) with mapi id 15.20.2305.023; Fri, 4 Oct 2019 16:14:12 +0000
From: "Anil Jangam (anjangam)" <anjangam@cisco.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: AQHVbL20+7O0fD877kWNqiv6We/U5adKTrGA
Date: Fri, 04 Oct 2019 16:14:12 +0000
Message-ID: <9E77D049-BC9D-4F08-ABAD-0C2E404FC196@cisco.com>
References: <BD080723-2E02-4C21-AD7C-3D7329ABB9F3@dkutscher.net>
In-Reply-To: <BD080723-2E02-4C21-AD7C-3D7329ABB9F3@dkutscher.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=anjangam@cisco.com;
x-originating-ip: [2001:420:c0c8:1002::658]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 4888573f-dacd-4f54-755d-08d748e5e52b
x-ms-traffictypediagnostic: BYAPR11MB3368:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <BYAPR11MB33682DD2E690DB4B8E6C7C1CC19E0@BYAPR11MB3368.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 018093A9B5
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(366004)(376002)(346002)(39860400002)(396003)(199004)(189003)(7736002)(46003)(446003)(76116006)(86362001)(25786009)(6246003)(102836004)(8936002)(6506007)(2906002)(6116002)(256004)(4744005)(11346002)(66476007)(966005)(186003)(14454004)(478600001)(71190400001)(6306002)(305945005)(476003)(6436002)(71200400001)(64756008)(66946007)(6512007)(66446008)(316002)(486006)(66556008)(2616005)(110136005)(33656002)(36756003)(5660300002)(6486002)(229853002)(8676002)(99286004)(76176011)(81166006)(81156014); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB3368; H:BYAPR11MB3687.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX: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: TGngzZzC3dPgewElyNjTRHYdneIfSk5LIdi4S+2XGOf10At69gul71Ja1D4UsiLhJsS3+PL5vy5VOByMXLlHvGJn0FK7Zk7BI1jdI0tzT2K5u9IsBYCb+6xFB8wXTB6c3jP21umygxEnENjYR0EF0Usv2xp9SChjuroU3DWX2dDI9RvWQW/IXgTiMNieOuryXxzngvawVL/DFgO5pCGdG2IC0UQ5QJYoXIkEO9Yesf99zsMUedJ0cPQumfs691nyXOsT4mUKbi7Ak26Jq5q5SnQ0qUe6mEGaQbQyvdHpf9fDs4ZC4jriaVHwgqmeK9vKp7WkfG0iM6VduAJgYYZxWArxZdykSdhEKa1Suy6dxm7HWTKzwhyggGtD8PguyqFCZrou3YCjntgVg94x99L0NRRic/vllDb4B8qM9Eu6yH7xY1Qr1KGoignaSQfWu+Ut1w3LQp+V/zgDVb1WjzgaqQ==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <0F8A79AEA22F4C4EBA0951948EB5F662@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 4888573f-dacd-4f54-755d-08d748e5e52b
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Oct 2019 16:14:12.3606 (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: 8BiKUcB8unYBygJ1PhmjAFPc7ErJ9khin4lzXzShASSb07lCBKAMzNbutq9Zzf2nhRlUWTs610+a1YAIUSTb3w==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB3368
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/icnrg/jb0TqspfMVAUk2yIcGtjBWH38yE>
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: Fri, 04 Oct 2019 16:14:17 -0000

+1

Thank you,
/anil.
 

    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/ .
    
    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
    https://www.irtf.org/mailman/listinfo/icnrg

v2.23.0 | Report a Bug | By Email