IETF Logo Mail Archive

Re: Call for operator's input on use case that requires Network Management Automation.

Greg Mirsky <gregimirsky@gmail.com> Thu, 28 March 2019 11:04 UTC

Return-Path: <gregimirsky@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 961CE120499; Thu, 28 Mar 2019 04:04:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 gyQ68Z5axCgc; Thu, 28 Mar 2019 04:04:32 -0700 (PDT)
Received: from mail-lf1-x132.google.com (mail-lf1-x132.google.com [IPv6:2a00:1450:4864:20::132]) (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 C3C6612043C; Thu, 28 Mar 2019 04:04:31 -0700 (PDT)
Received: by mail-lf1-x132.google.com with SMTP id 10so13665167lfr.8; Thu, 28 Mar 2019 04:04:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=dFg3DSsgtB16zFrgqnaUerb11RMA4lN4q3XeIbNKN2A=; b=W5S1BSaZHuuf16rpf0Xmh+VePnT3hIFBs9HJos7ZjXzE3tdJe+F85uODRfgkshlbhs dbRWYiZxhK5K6BKcQqL7WhzufXup91hebZI7bKY4XrJBhAFZfk+5R7xCqGBjISd7sZXX +wmWH2Kpa1x5jRWfVJSOsT+Nhj4yjFd3G5zNasCvZrmnozJg6JFEAHiCK//UYnLgJq+I DkOuKU/xeGQ0xgh3QK0fd0yhLZTRLQk9k9r1Go96287q52PZUh9qaC96f3VCj9v79gFd xSx1hZ/JSivYWlTIehmm9b4U+0g5bQSPJXjbAcNb+I/RWNQz0Bkwx6PalXX7iiqhNZ9g YbIQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=dFg3DSsgtB16zFrgqnaUerb11RMA4lN4q3XeIbNKN2A=; b=ONKze8nd91BdJB4bI1mNr9NKYOTgQZDRnPK4RPDjo1y7ui+hiTHrsp+NXbxkCZ/Kxt rd1KXEfuz2B3zbhqfjQH+rvn3Ib2RCZDreek6JFGvmDS4NCLeiaTnjLxfccvilX7I6Ov 7k7fOC7MCX+To4i3sU23TWxFgP9FXOhif+5iBWn7+EvH8PtY1n+BkLpIaxF4Gu8lp4uw swzYpR4NCPS15lvgYXyW3w/4qe/0B+3zEVECnnLR+3TW8OfYtx9slafPPWWZihbacDn6 spAk9BFxivn6Dtr1kdT6Fy1qP3RqrA1L17zv59whwY497MBPQBZcaRjVBMTZsS/6nwFc qhbw==
X-Gm-Message-State: APjAAAVYHpKYzRJqmlPE/mQTmwtOZnqp7KasxSJAkNVohDk6cuY1wAsp oNL6DpuZs5m5dg1OccHl8pMCDCHE/mVkmvAir7c=
X-Google-Smtp-Source: APXvYqzxKVZ9iCFZjSNgI1sE62dQFzLBWksVoihHGUUe9K+Xjp4cT5RxOxx75PHgPqfiMOWHFBW4e7N4WB2hv9Z6ogA=
X-Received: by 2002:ac2:54bc:: with SMTP id w28mr16708798lfk.127.1553771069926; Thu, 28 Mar 2019 04:04:29 -0700 (PDT)
MIME-Version: 1.0
References: <B8F9A780D330094D99AF023C5877DABAA4888913@nkgeml513-mbx.china.huawei.com>
In-Reply-To: <B8F9A780D330094D99AF023C5877DABAA4888913@nkgeml513-mbx.china.huawei.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Thu, 28 Mar 2019 12:03:48 +0100
Message-ID: <CA+RyBmX19p9FjgRF=uF9UTqubn+TAkc+6qnmenz+x7adYB8B=g@mail.gmail.com>
Subject: Re: Call for operator's input on use case that requires Network Management Automation.
To: Qin Wu <bill.wu@huawei.com>
Cc: opsawg@ietf.org, RTGWG <rtgwg@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000af730105852584f5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/P71HXXgOQoeQ1wdSUzrYNv8dZIE>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Mar 2019 11:04:37 -0000

Dear All,
I would propose that IETF send liaison to MEF LSO Committee, and probably
other SDOs, notifying them of the discussion and inviting to share their
comments.

Regards,

On Thu, Mar 28, 2019, 11:24 Qin Wu <bill.wu@huawei.com> wrote:

> Hi, folks:
>
> I would like to draw you attention to IETF YANG automation Framework that
> will be discussed in opsawg WG session 4:10~6:10pm Thursday.
>
> It has already been discussed in rtgwg Tuesday morning session and got a
> few feedback from operators.
>
>
>
> We would like to discuss this work again in opsawg session to further
> solicit feedback on the IETF YANG issues we raised.
>
>
>
> The goal is call for operator’s input on use case that requires network
> management automation and come up approaches or ways to addresses
>
> Challenge issues faced by IETF YANG model standardization.
>
>
>
> The relevant draft is available at:
>
>
> https://datatracker.ietf.org/doc/draft-wu-model-driven-management-virtualization/
>
> The presentation slides is available at:
>
>
> https://datatracker.ietf.org/meeting/104/materials/slides-104-opsawg-draft-wu-model-driven-management-virtualization-00
>
>
>
> Your comments and suggestions are welcome, see you in opsawg session in
> this afternoon.
>
>
>
> -Qin Wu
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>

v2.23.0 | Report a Bug | By Email