IETF Logo Mail Archive

Re: [Sdn] gRPC

Hariharan Ananthakrishnan <hari@packetdesign.com> Mon, 14 November 2016 08:36 UTC

Return-Path: <hari@packetdesign.com>
X-Original-To: sdn@ietfa.amsl.com
Delivered-To: sdn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30A04129524 for <sdn@ietfa.amsl.com>; Mon, 14 Nov 2016 00:36:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level:
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=packetdesign.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 QQo-51J2Vq2X for <sdn@ietfa.amsl.com>; Mon, 14 Nov 2016 00:36:33 -0800 (PST)
Received: from NAM03-BY2-obe.outbound.protection.outlook.com (mail-by2nam03on0061.outbound.protection.outlook.com [104.47.42.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A440E1293DF for <sdn@irtf.org>; Mon, 14 Nov 2016 00:36:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=packetdesign.onmicrosoft.com; s=selector1-packetdesign-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=GDPX272FBejeJYWU6s1GOFgWjVMhGAnfCwOrNEab/Mg=; b=EeRw8n6MwMKlWFXXUJT1LJE2ukfK28EYaOpO8suRsh9vHfFr6jGpx5BryfJjq1/ACMwlY5rNAv3bkLbC4qN1kzidTMOhd9mbkjZwerqd/BxPIohvRf65GtPT4korzalUeNCrKAzHbx6l3Yw4wk2SIlyCj00/xb2CGjHqv8+BUq0=
Received: from BY2PR04MB2103.namprd04.prod.outlook.com (10.166.111.153) by BY2PR04MB2101.namprd04.prod.outlook.com (10.166.111.151) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.721.10; Mon, 14 Nov 2016 08:36:30 +0000
Received: from BY2PR04MB2103.namprd04.prod.outlook.com ([10.166.111.153]) by BY2PR04MB2103.namprd04.prod.outlook.com ([10.166.111.153]) with mapi id 15.01.0721.015; Mon, 14 Nov 2016 08:36:29 +0000
From: Hariharan Ananthakrishnan <hari@packetdesign.com>
To: Pedro Martinez-Julia <pedro@nict.go.jp>, Hesham ElBakoury <Hesham.ElBakoury@huawei.com>
Thread-Topic: [Sdn] gRPC
Thread-Index: AQHSPk5p/MMlyyPI90qoVX/wzLWpAaDYJn2A//97LAA=
Date: Mon, 14 Nov 2016 08:36:29 +0000
Message-ID: <110E3A7B-C83B-4BCF-AA6F-58FB88C5ACB1@packetdesign.com>
References: <etPan.58275c6d.4b77d2e1.5186@localhost> <C3855D43D6701846AD1151A536E7A05822677293@dfweml501-mbb> <20161114083147.GA9952@spectre>
In-Reply-To: <20161114083147.GA9952@spectre>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=hari@packetdesign.com;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [2001:67c:370:128:cd6c:aea0:1342:396a]
x-microsoft-exchange-diagnostics: 1; BY2PR04MB2101; 7:rKGFPJid7oNr5R/aVMJAuGcjUZgtA0GwZt8PFg9H6sGY1XfM3tl5USFUNh5rR5joqlCes+7agTHZ3VNmP+36LM5rn+ZrBvvC6Bsbn/wcpQlg+pAECeeYV2+pA+1QGyBakdmj9mZeaqPIzQrhI0qAG8zmh+slo+X6GDHdzvXF2B2kXdLyxESvUDiTmBJJ7cm3906/xsNImL806DUmEkB7e40o40Brr9s1s0esH9Gr2+ndpGG90gwgHOEiwz5PVofl56pxQ6LUqrEL3p00Mg+G1/Pgp/kpeizTOppnY8/xgxRMDiiIk1Qc7NHlhua+TZjoU6UqvNAXinLFi5EbZDwkSc57GVzE0Y9e9ROHHr97PkA=
x-ms-office365-filtering-correlation-id: d578b830-4ae7-4c37-920f-08d40c6954ce
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:BY2PR04MB2101;
x-microsoft-antispam-prvs: <BY2PR04MB210161B50B576AB17CF2D96FBDBC0@BY2PR04MB2101.namprd04.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6060326)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(6061321); SRVR:BY2PR04MB2101; BCL:0; PCL:0; RULEID:; SRVR:BY2PR04MB2101;
x-forefront-prvs: 0126A32F74
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(336003)(189002)(377424004)(252514010)(24454002)(199003)(2950100002)(77096005)(5660300001)(83716003)(101416001)(87936001)(2906002)(50986999)(4326007)(82746002)(92566002)(54356999)(76176999)(3660700001)(81156014)(81166006)(86362001)(229853002)(33656002)(102836003)(36756003)(586003)(6116002)(106356001)(105586002)(106116001)(3280700002)(99286002)(122556002)(8936002)(7846002)(189998001)(5001770100001)(97736004)(2900100001)(7736002)(68736007)(305945005)(8676002)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:BY2PR04MB2101; H:BY2PR04MB2103.namprd04.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: packetdesign.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <2D5A74D35FF7B340B3DBA3EAEA7D0E15@namprd04.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: packetdesign.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Nov 2016 08:36:29.8744 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 1df5b6db-3686-4e87-9323-024e5bfe00f0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR04MB2101
Archived-At: <https://mailarchive.ietf.org/arch/msg/sdn/eiJj3gUiyGTQA2aGRF5ryqBXIWw>
Cc: "sdn@irtf.org" <sdn@irtf.org>, "ejona@google.com" <ejona@google.com>
Subject: Re: [Sdn] gRPC
X-BeenThere: sdn@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: List to Discuss SDN Research Group in the IRTF <sdn.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/sdn>, <mailto:sdn-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sdn/>
List-Post: <mailto:sdn@irtf.org>
List-Help: <mailto:sdn-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/sdn>, <mailto:sdn-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2016 08:36:37 -0000

Some router vendors claim to support gRPC in their network devices. So yes, gRPC between SDN Controller to network devices is coming.

- Hari

On 14/11/2016, 17:31, "sdn on behalf of Pedro Martinez-Julia" <sdn-bounces@irtf.org on behalf of pedro@nict.go.jp> wrote:

    On Mon, Nov 14, 2016 at 08:09:24AM +0000, Hesham ElBakoury wrote:
    > Hi Eric,
    > 
    > Do you think we can use gRPC as southbound protocol for SDN controllers.
    
    Hi,
    
    Sorry to interfere but being a general RPC I think there should be no
    problem to use it there. It would be interesting to map OpenFlow and
    even NETCONF/YANG to protobuf/gRPC but, however, I do not see a clear
    benefit as it means more complexity in devices. What is your idea?
    
    > Thanks
    > 
    > Hesham
    
    Regards,
    Pedro
    
    -- 
    Pedro Martinez-Julia
    Network Science and Convergence Device Technology Laboratory
    Network System Research Institute
    National Institute of Information and Communications Technology (NICT)
    4-2-1, Nukui-Kitamachi, Koganei, Tokyo 184-8795, Japan
    Email: pedro@nict.go.jp
    ---------------------------------------------------------
    *** Entia non sunt multiplicanda praeter necessitatem ***
    
    _______________________________________________
    sdn mailing list
    sdn@irtf.org
    https://www.irtf.org/mailman/listinfo/sdn

v2.23.0 | Report a Bug | By Email