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

David Meyer <> Tue, 28 March 2017 17:59 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 39CBB12778D for <>; Tue, 28 Mar 2017 10:59:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.899
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: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id GeqtiRVSfmFO for <>; Tue, 28 Mar 2017 10:59:39 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:400d:c0d::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 971ED1293E8 for <>; Tue, 28 Mar 2017 10:59:39 -0700 (PDT)
Received: by with SMTP id x35so70914111qtc.2 for <>; Tue, 28 Mar 2017 10:59:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Y+LiQCl57nucHSJUPoacPsgnGUKj7497vw/NrW7qhF4=; b=Pmna0jlaeTmaBCUy/FyhrA9BFVAVaywsolYxWESpqqNfC8hlER5gRmfMBT1nNF7vJu 3+G3AZAln8KNZvm57TnQzdTR0tMXZEvKwTAgVbt/28zpKgev0/W0O/7hChtpdPGYBe4H mZLsGecXWMkwWG2R7wfMw+AfYwvsaT9RGK1krZvOtmBv9Kbbgl2ocEVn190dc6Wykl10 HA3aoSekRYw5jIIF/48e+Wt8YqEbezQnzBL4pM445INlmQ3EwDfzn5vJH975Mm6vTmOv FDgTlE+deM0pyRimGbPx66P8IBYHWeSoL+xXcu2ec+wyIY5fVddeZhOgczmQw49SNO6N GELw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Y+LiQCl57nucHSJUPoacPsgnGUKj7497vw/NrW7qhF4=; b=IvCxF6efYIOlMnEp+kQoQCC8qBqcBMLdGuWyVWPDYLocJF04jLoDJUCXiG/j4ZhnPr bRv3Cvio+1TfLkxwq3PHocz/OCVIn/YlspitQa071Tsa6QqiCbhVti6sVDVNcrFzNP6l cji1igYvQEcn7wQIvirCdKsEi+PyJRuZwnWe+rdEGD1EH9XGren4Z5mgK4r02MlL1Cac 9mgl+3Rl9crHjeffGngIMXCRJO5g6KZv02yYmPkHKGnpdrGig3ceQLR5PjV8c9qByLF6 qQ6Lv6DklwsU1BzqOqMkC3QA/OEZE77wB+pT4A0qCxq+8nqOtIs5RiJodSlMt0S+hZkG NmbA==
X-Gm-Message-State: AFeK/H0e5UmVnYM56zpg3VlqRyTz0aosTVNjNXn4+pL3F+p2L6RVatKJOvXAFwN5KoefVKxNGEqAkcJDG8U0IA==
X-Received: by with SMTP id 16mr26506965qtf.10.1490723978643; Tue, 28 Mar 2017 10:59:38 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Tue, 28 Mar 2017 10:59:38 -0700 (PDT)
X-Originating-IP: []
In-Reply-To: <>
References: <>
From: David Meyer <>
Date: Tue, 28 Mar 2017 10:59:38 -0700
Message-ID: <>
To: Sheng Jiang <>
Cc: "" <>
Content-Type: multipart/alternative; boundary=94eb2c0c995a34a6a6054bce3903
Archived-At: <>
Subject: Re: [Idnet] Intelligence-Defined Network Architecture and Call for Interests
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "The IDNet \(Intelligence-Defined Network\) " <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 28 Mar 2017 17:59:42 -0000

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?




On Tue, Mar 28, 2017 at 9:29 AM, Sheng Jiang <> 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.
> 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 . 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.
> 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