Re: [Idnet] Intelligence-Defined Network Architecture and Call for Interests

David Meyer <dmm@1-4-5.net> Tue, 28 March 2017 18:01 UTC

Return-Path: <dmm@1-4-5.net>
X-Original-To: idnet@ietfa.amsl.com
Delivered-To: idnet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB9B21293E8 for <idnet@ietfa.amsl.com>; Tue, 28 Mar 2017 11:01:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=1-4-5-net.20150623.gappssmtp.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 tx3YWJizmdoh for <idnet@ietfa.amsl.com>; Tue, 28 Mar 2017 11:01:48 -0700 (PDT)
Received: from mail-qt0-x22b.google.com (mail-qt0-x22b.google.com [IPv6:2607:f8b0:400d:c0d::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 82E181294D2 for <idnet@ietf.org>; Tue, 28 Mar 2017 11:01:48 -0700 (PDT)
Received: by mail-qt0-x22b.google.com with SMTP id r45so71013065qte.3 for <idnet@ietf.org>; Tue, 28 Mar 2017 11:01:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1-4-5-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=fmqYPB85VxhO+lvi/V/NE+flwOUvOuCSPyjBbShIWe4=; b=k9IS2usCmE1ydCMxR+HMjghqM6hpwGrPqzzmfdUvrDpguXr41OWvgezVm8eICkfbg6 2K4MXWz5TeM+JgP6AGZtofbHIRniTey3h3+dyTFkPZfC5fGayLLPcAbec19gqZ2xeL9R gB2EuD83O/YaqP5ZRiW5iJsI4SWKzFKi4XFu/SDWP4iRplM9v+DGS8s0v17YJWJQ/cZo tFTITFjdeefyUFkYXAHQrr3nNjRdY1YAQXH/ZPq8XbpID7In98nDxJ5J+fgGEUFtGQeb kYSoAVAZ6qAmNL6OcchYqIqcbd/40Au0BP7jCkV/fpXMggxt2T1Vd2pGAAPreGmqfq+Q 3afQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=fmqYPB85VxhO+lvi/V/NE+flwOUvOuCSPyjBbShIWe4=; b=MiiYRzCCGwbg6a90Pfw2KChtKCkZs2NcwRktmtYPjF2BzyrEO7Ivf3j4jHQvM6ED+3 i/G+3dT6atZk+WDt1YD9F4/ON8jqRsFbuAT/ucQ2ftPPyrsKaCh4de6B+7UYm3dDzZKV j4pSrYS55/KapZrPh9xP5UNRVGB1Fa4bDG4VyRFskDVUh7aThwTu76WG1kS8H16kNcKc ACkHldo8PlGMbEES+mqJDMR/3qxvDfmzxAQFExX9TRPdtM6hfL4vpcKKbKF4cEG3A2Ps 91gMg73e0hDxrDjB5TqfIgIPiOIDnEl1S/BK3HeFuT2fxh1cc5BXNiYEJZ5Gh38Ae7kQ eiaw==
X-Gm-Message-State: AFeK/H2iqG4eXdOQ+uRQ2gY5A3kl68aSvoYBM0yn1n9xtKxNELzNC+GsxdiSb4YIZRT/CkTzVo0qQFv874X6BA==
X-Received: by 10.237.38.229 with SMTP id q92mr27673117qtd.6.1490724107465; Tue, 28 Mar 2017 11:01:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.12.149.34 with HTTP; Tue, 28 Mar 2017 11:01:46 -0700 (PDT)
X-Originating-IP: [128.223.156.253]
In-Reply-To: <CAHiKxWgT3hKr2VwhbfpmR_siHgiY4PbiKy3QgesG7uqUTnedmw@mail.gmail.com>
References: <5D36713D8A4E7348A7E10DF7437A4B927CD15A18@NKGEML515-MBS.china.huawei.com> <CAHiKxWgT3hKr2VwhbfpmR_siHgiY4PbiKy3QgesG7uqUTnedmw@mail.gmail.com>
From: David Meyer <dmm@1-4-5.net>
Date: Tue, 28 Mar 2017 11:01:46 -0700
Message-ID: <CAHiKxWjbAY5uaBw+M+Wxzy8VZYu=epEtWBakLR8TdkqPRt_BAw@mail.gmail.com>
To: Sheng Jiang <jiangsheng@huawei.com>
Cc: "idnet@ietf.org" <idnet@ietf.org>
Content-Type: multipart/alternative; boundary=94eb2c0bb94ee265ff054bce40d3
Archived-At: <https://mailarchive.ietf.org/arch/msg/idnet/a44oryv_lmTQvC5WuHfePZ_MHIU>
Subject: Re: [Idnet] Intelligence-Defined Network Architecture and Call for Interests
X-BeenThere: idnet@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "The IDNet \(Intelligence-Defined Network\) " <idnet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idnet>, <mailto:idnet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idnet/>
List-Post: <mailto:idnet@ietf.org>
List-Help: <mailto:idnet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idnet>, <mailto:idnet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Mar 2017 18:01:51 -0000

s/NMRL/NMLRG/   (sorry about that). Dave

On Tue, Mar 28, 2017 at 10:59 AM, David Meyer <dmm@1-4-5.net> wrote:

> Hey Sheng,
>
> I just wanted to revive my key concern on [0] (same one I made at the
> NMRL): The hard parts of getting Machine Learning intelligence into
> Networking is the Machine Learning part. In addition, successful deployment
> of ML requires knowledge of ML combined with domain knowledge. We
> definitely have the domain knowledge; the problem is that we don't have the
> ML knowledge, and this is one of the big factors holding us back; see e.g.
> Andrew's discussion of talent in [1].  Slides such as [0] seem to imply
> that *someone else* (in particular, not us)  will handle the ML part of all
> of this. I'll just note that in general successful deployments of ML don't
> work this way; the domain experts will have to learn ML (and vice versa)
> for us to be successful (again, see [1] and many others).
>
> Perhaps a useful exercise would be to write an ID that makes your
> assumptions explicit?
>
> Thanks,
>
> Dave
>
>
> [0] https://www.ietf.org/proceedings/97/slides/slides-
> 97-nmlrg-intelligence-defined-network-01.pdf
> [1] https://hbr.org/2016/11/what-artificial-intelligence-can-
> and-cant-do-right-now
>
>
> On Tue, Mar 28, 2017 at 9:29 AM, Sheng Jiang <jiangsheng@huawei.com>
> wrote:
>
>> Hi, all,
>>
>> Although there are many understanding for Intelligence-Defined Network,
>> we are actually using this IDN as a term reference to the SDN-beyond
>> architecture that we presented in IETF97, see the below link. A reference
>> model is presented in page 3, while potential standardization works is
>> presented in page 9.
>>
>> https://www.ietf.org/proceedings/97/slides/slides-97-nmlrg-
>> intelligence-defined-network-01.pdf
>>
>> Although it might be a little bit too early for AI/ML in network giving
>> the recent story of the concluded proposed NMLRG, we still would like to
>> call for interests in IDN. Anybody (on site in Chicago this week) are
>> interested in this or even wider topics regarding to AI/ML in network,
>> please contact me on jiangsheng@huawei.com . Then we may have an
>> informal meeting to discuss some common interests and potential future
>> activities (not any activities in IETF, but also other STO or experimental
>> trails, etc.)  on Thursday morning.
>>
>> FYI, we have already working on a Work Item, called IDN in the ETSI NGP
>> (Next Generation Protocol) ISG, links below.
>>
>> https://portal.etsi.org/tb.aspx?tbid=844&SubTB=844
>> https://portal.etsi.org/webapp/WorkProgram/Report_WorkItem.
>> asp?WKI_ID=51011
>>
>> Meanwhile, please do use this mail list as a forum to discuss any topics
>> that may applying AI/ML into network area.
>>
>> Best regards,
>>
>> Sheng
>> _______________________________________________
>> IDNET mailing list
>> IDNET@ietf.org
>> https://www.ietf.org/mailman/listinfo/idnet
>>
>
>