Re: [Anima] RTGWG-chairs: slot for RTGWG@109 to present on GRASP ? (was: Re: draft-li-rtgwg-protocol-assisted-protocol (was: Re: IETF 105 mic comments on draft-li-rtgwg-protocol-assisted-protocol))

Jeff Tantsura <jefftant.ietf@gmail.com> Wed, 11 November 2020 00:13 UTC

Return-Path: <jefftant.ietf@gmail.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 232143A124E; Tue, 10 Nov 2020 16:13:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, 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 082KsDGvZ26e; Tue, 10 Nov 2020 16:13:30 -0800 (PST)
Received: from mail-pg1-x52e.google.com (mail-pg1-x52e.google.com [IPv6:2607:f8b0:4864:20::52e]) (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 EC5B03A127F; Tue, 10 Nov 2020 16:13:27 -0800 (PST)
Received: by mail-pg1-x52e.google.com with SMTP id z24so180896pgk.3; Tue, 10 Nov 2020 16:13:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:message-id:in-reply-to:references:subject :mime-version; bh=LvyUQcVmhaD7XO0Z37EB++0OkEyUFBDZqRSossWr7+w=; b=ar93ccP7d7BYDFm98fymFRkVV85h6UCmFdUsA10JX6Cr8J7ZVSBAATTDuTY95DCnCK 1RDq3b5EI9yhZoGWskjjZDRqeykvsEJQh0eFZ8Hl2I0mUl3FgVguRM7zRDL4YZjpF4fo qne91z6KfUnbtz0kaEzSXdYtaASSuM2Rs3defG0NUj7I44U7tz38OE0SXyTtuGiwdBEz YtINfRgQpkxkvkqlCSqFbikvKnbBlo0Gfs5IzNJV5QNubnJ6cJFqfmYd0KSPBRFM8E+2 gHugqf7F9+KTuzwtgIjIIEoh3CdmRITXNteGh7hh3UZENEIHyEtgSwD0H8N/RsGz8qL5 XVmA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:message-id:in-reply-to :references:subject:mime-version; bh=LvyUQcVmhaD7XO0Z37EB++0OkEyUFBDZqRSossWr7+w=; b=XyF23wFcUJmP7q4gzWkcrdeSHqHOUeB6w5CZze9bWbgnV5pHiskZ5CUYBBVC3bI9TN s5wa4oVUuQv9+HKA6IiBSyA4gGOG0G9sq4ILmtUMvlkcfwr4dDz0cJsQHC9aw/LZOa3i npW74huFNYod8nxPY72Fji9BAPXKtI+9GQ+vl8Xu2hGLEuOuj9J4FdXFqTSekIBdkyg3 uDRdHzggS6bNjY588vTUv5LEs7mLZO5p+amAxSjn3vsKlenUKNYai4uGQ01tItfA1jIC jngCgT53N//nF8nVUIruDyoW38+wzwZKaMz93BB1RrJW7o+saOfuN5Zjd6CTlhl9g70+ bFjA==
X-Gm-Message-State: AOAM533i4Dx3NhQOeJnDzbxSBVC9JqH4NBl7bnQomSA/9rosv13AzpKy jx7DytiTlzS9/4/VgtCj1Yk=
X-Google-Smtp-Source: ABdhPJysV/6kz9a9dg9R18HsvlmLyU4hHG1rkFLQ2s052to7pFGbRfSArJe5JSX+AKzcFAzVT0DPeQ==
X-Received: by 2002:a17:90b:300a:: with SMTP id hg10mr844611pjb.30.1605053607456; Tue, 10 Nov 2020 16:13:27 -0800 (PST)
Received: from [192.168.1.7] (c-73-63-232-212.hsd1.ca.comcast.net. [73.63.232.212]) by smtp.gmail.com with ESMTPSA id ce19sm149244pjb.53.2020.11.10.16.13.25 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 10 Nov 2020 16:13:26 -0800 (PST)
Date: Tue, 10 Nov 2020 16:13:15 -0800
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: Toerless Eckert <tte@cs.fau.de>, rtgwg-chairs@ietf.org, Jeffrey Haas <jhaas@pfrc.org>, Chenshuanglong <chenshuanglong@huawei.com>, "=?utf-8?Q?anima-chairs=40ietf.org?=" <anima-chairs@ietf.org>, Lizhenbin <lizhenbin@huawei.com>, "=?utf-8?Q?anima=40ietf.org?=" <anima@ietf.org>, Guyunan <guyunan@huawei.com>, rwilton@cisco.com, Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: rtgwg@ietf.org
Message-ID: <831c7ecf-8afe-4d49-b213-8277f18d0221@Spark>
In-Reply-To: <311b455e-977a-1c54-0d06-89c779f072c6@gmail.com>
References: <20201110165724.GA42082@faui48f.informatik.uni-erlangen.de> <311b455e-977a-1c54-0d06-89c779f072c6@gmail.com>
X-Readdle-Message-ID: 831c7ecf-8afe-4d49-b213-8277f18d0221@Spark
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="5fab2ca4_7fffca11_6e9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/8ZP5Cx3yogj3Wu1ZJz_G8b4dnLs>
Subject: Re: [Anima] RTGWG-chairs: slot for RTGWG@109 to present on GRASP ? (was: Re: draft-li-rtgwg-protocol-assisted-protocol (was: Re: IETF 105 mic comments on draft-li-rtgwg-protocol-assisted-protocol))
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Nov 2020 00:13:40 -0000

Toerless,

We will provide a slot, most likely during the 2nd meeting.
Please send an email to RTGWG with a short intro so people who might be interested have the time read up.

Thanks!

Cheers,
Jeff
On Nov 10, 2020, 11:48 AM -0800, Brian E Carpenter <brian.e.carpenter@gmail.com>om>, wrote:
> I'd like to underline what Toerless said. I looked at the two use casess
> in the protocol-assisted-protocol draft and they seem very easy to
> map onto GRASP. I don't really have time before the meeting to do
> that but they are certainly use cases we could have included in the
> original use case BOF that led to ANIMA.
>
> Regards
> Brian Carpenter
>
> On 11-Nov-20 05:57, Toerless Eckert wrote:
> > In followup to the discuss on draft-li-rtgwg-protocol-assisted-protocol:
> >
> > Checking RTGWG agenda, it seems you might still have time available,
> > so if you are interested, i would be happy to whip up a few slides
> > to five an overview of GRASP and how we imagine it to be useable
> > to automate operational workflows for various services, including
> > routing protocols.
> >
> > Cheers
> > Toerless
> >
> > In-Reply-To: <20201110165235.GA17445@faui48f.informatik.uni-erlangen.de>
> >
> > On Tue, Nov 10, 2020 at 05:52:35PM +0100, Toerless Eckert wrote:
> > > I see subject draft is again on the agenda of RTGWG'109 and the authors also asked
> > > for a slot to present to ANIMA (which we would be happy to have, time permitting).
> > >
> > > Some thoughts as contributor, maybe ANIMA chair:
> > >
> > > Reading the draft it looks like a reinvention of the ANIMA GRASP protocol
> > > that we finished almost 3 years ago, but without many of the mechanisms
> > > that make GRASP a well reuseable, easily extensible protocol. So i wonder
> > > why we would want to also do another more imited protocol for the same
> > > goals.
> > >
> > > On the mike RTGWG @IETF105, interest was raised to see a more comprehensive
> > > signalling enxchange example. Version 03 of the document seems to have
> > > expanded the BGP example a bit, but still not comprehensive enough for me
> > > to understand if/how this approach would ultimately work.
> > >
> > > I would like to encourage the authors to concentrate on fully specifying
> > > intended use-cases - ideally by simply specifying the use-case as
> > > solution using GRASP (we call this GRASP objectives). I am sure
> > > ANIMA participants (including me) would be happy to help explaining how
> > > to specify such a protocol on top of GRASP once we understand the use-case.
> > >
> > > Cheers
> > > Toerless
> > >
> > > On Mon, Jul 22, 2019 at 11:02:31AM -0400, Jeffrey Haas wrote:
> > > > To repeat my comments from the microphone regarding this draft:
> > > >
> > > > We already have per-protocol operational and configuration state via the
> > > > IETF yang models for a given protocol.
> > > >
> > > > We also have mechanisms to fetch operational state for such protocols; e.g.
> > > > netconf and restconf.
> > > >
> > > > Rather than inventing a new mechanism to do troubleshooting for a protocol,
> > > > I'd suggest it makes better sense to augment existing IETF yang models to
> > > > include RPCs for interacting with troubleshooting for that protocol.
> > > >
> > > > -- Jeff
> > > >
> > > > _______________________________________________
> > > > rtgwg mailing list
> > > > rtgwg@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/rtgwg
> > >
> > > --
> > > ---
> > > tte@cs.fau.de
> >