Re: [Anima] 答复: Request for presentation

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 03 November 2020 18:53 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 DC0F03A0D5A for <anima@ietfa.amsl.com>; Tue, 3 Nov 2020 10:53:17 -0800 (PST)
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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 bEDkL5OfR-ry for <anima@ietfa.amsl.com>; Tue, 3 Nov 2020 10:53:16 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0FD163A0CEE for <anima@ietf.org>; Tue, 3 Nov 2020 10:53:15 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id E35BF3897E for <anima@ietf.org>; Tue, 3 Nov 2020 13:53:13 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id PXLKjGrYhSXw for <anima@ietf.org>; Tue, 3 Nov 2020 13:53:13 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id A9DD238983 for <anima@ietf.org>; Tue, 3 Nov 2020 13:53:07 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id EAC29A01 for <anima@ietf.org>; Tue, 3 Nov 2020 11:24:21 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "anima@ietf.org" <anima@ietf.org>
In-Reply-To: <adb28277-1f1b-edb6-7e04-aeaad00a7d88@gmail.com>
References: <e102ab87b92f44b987a0013e9a3b0874@huawei.com> <20201102155453.GR48111@faui48f.informatik.uni-erlangen.de> <7c189c052c6943408e072390d09b2d41@huawei.com> <adb28277-1f1b-edb6-7e04-aeaad00a7d88@gmail.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Tue, 03 Nov 2020 11:24:21 -0500
Message-ID: <8979.1604420661@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/BJpxXTmuoFQlfO3vdIniL1GGT4c>
Subject: Re: [Anima] 答复: Request for presentation
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: Tue, 03 Nov 2020 18:53:18 -0000

I've only very briefly scanned
   https://tools.ietf.org/html/draft-li-rtgwg-protocol-assisted-protocol-03

Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
    > I don't really understand why you might need a new protocol for
    > this. It sounds like a very good application for the ANIMA model, and
    > everything you describe could easily be expressed in GRASP objectives
    > (synchronization or negotiation are both covered). You discuss this in
    > Section 7.

I'd split this up in three points:

1) It seems like a very good use for the ACP.
   If you are debugging a protocol problem, then you likely have some part of
   the network that has reachability issues.

2) I think that the ACP eliminates the need for PAP to be peer to peer, or
   for it to be UDP.
   It should be between the NOC and the router, not between routers.

3) GRASP CLEARLY has a place in discovering the routers which speak this
   protocol, and/or in having the routers discover the PAP collector in the NOC.


Whether or not GRASP is the right way to transfer the data itself, I'm not
sure.  I'm unclear if access to the raw routing protocol frames (OSPF, BGP,
etc.) is desired, or if some higher-level debug is envisioned.

If raw protocol, then it seems like a span/mirror/ functionality using IPFIX
or PCAPNG [over ACP] would be appropriate.

If you want higher-level diagnostics, then I would use RESTCONF and YANG.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide