Re: [CCAMP] [OPSAWG] Draft on YANG for state machine

nicola sambo <nicosambo@gmail.com> Thu, 27 July 2017 08:41 UTC

Return-Path: <nicosambo@gmail.com>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 282D1129461; Thu, 27 Jul 2017 01:41:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 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_LOW=-0.7, 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 W0zJf15djDus; Thu, 27 Jul 2017 01:41:47 -0700 (PDT)
Received: from mail-lf0-x236.google.com (mail-lf0-x236.google.com [IPv6:2a00:1450:4010:c07::236]) (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 94569126B7E; Thu, 27 Jul 2017 01:41:46 -0700 (PDT)
Received: by mail-lf0-x236.google.com with SMTP id d17so9707206lfe.0; Thu, 27 Jul 2017 01:41:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Ul5SUGoy0o31h5GUy/MK/9ui/e0winrpMSPeV/GVarU=; b=GtDYX9ACrn6q4YHttIGtMz8wD8Xh212J20ONFHNs66qRDRyTtRMCV82w/lZVg2VKxB dAlPNwchcJY4ejnCtbMbXtHyCnqS27PFc/ENyMbijzrvXRUdbTk3YAOUqk2N1pZ0pqae Cz3oKeXqwPjjFL4jKCMm8qp2cb7V2DKtDOzHtjEKf9UL6SM6BMBqTRl/AuVkhMYs2MfT BA6kPPVQSHW1L14SQGcqhTm6RbHBhJ9Ws81cOlsV0Q+6Fu5g4t8XKVkX04dOU+FyzEhb 4lQFmKsoG9/Kq38FXN1XBgnx9xdqt+HeAzWLc/+2LGOVqHh6iDPWv4VpgxW+qI5RRarh Ic0A==
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=Ul5SUGoy0o31h5GUy/MK/9ui/e0winrpMSPeV/GVarU=; b=CrbpnxU8E84RA15o+EoUKCyfbhZEYvcOFJK7Fvm+n5PxGx5eBA/T4n/Sfh5sYqlW3D Fq9WM1LNkEd3UhRfTgnf38+B+nWwt0pjgFiEp+bGC/aErljIc44fQ/N8lfaIWxAvbDld uEj4PCGK43tlKcIHzvLenmP+xrJh23P+E8GWxaUvmto6rWGCGlaCf/SNgBjtyRxyA1+q 1OiVSxF3kKvxm53ANB7fmyQinhR9ZMDcce0ONDjPOgLzYS5YzR1YtZjKs4yXwG4IAhlF dnDN4htxy8yS8Gq3GkCw62G/tFeCMkvvVgHrZGrc8GJfHxNiVPiCTuS6lztnQsOlD0E0 W+EQ==
X-Gm-Message-State: AIVw112o5hNLdhF8aPLj3SxQ+yJ5+8Pylb83fy8D5DdLS6ytBMuqabrl swbBonqHF0YPbKCU/fYiG/Ajm9oZDQ==
X-Received: by 10.25.151.19 with SMTP id z19mr1376141lfd.134.1501144904602; Thu, 27 Jul 2017 01:41:44 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.56.84 with HTTP; Thu, 27 Jul 2017 01:41:43 -0700 (PDT)
In-Reply-To: <01c801d3062d$d610da40$4001a8c0@gateway.2wire.net>
References: <CADqwGbcDisUAGT+RT9DzAO3aHTLdivc=T+YT3vn+ygP3MgTKBQ@mail.gmail.com> <AM2PR07MB099422F50A32698191D65CC6F0B80@AM2PR07MB0994.eurprd07.prod.outlook.com> <7782c0248fe347d1be1ec824b9364dbf@TELMBXC02BA020.telecomitalia.local> <CADqwGbfA44vWqdTGuq_3VREbzEqJ59ji=1Ybt=3u_7J6gLaSdg@mail.gmail.com> <01c801d3062d$d610da40$4001a8c0@gateway.2wire.net>
From: nicola sambo <nicosambo@gmail.com>
Date: Thu, 27 Jul 2017 10:41:43 +0200
Message-ID: <CADqwGbdtmpDCLoc1Ocfn4qXMR94so1fxHc1xk_mszqp+A28c7w@mail.gmail.com>
To: "t.petch" <ietfc@btconnect.com>
Cc: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>, opsawg@ietf.org, ccamp@ietf.org, n.sambo@sssup.it
Content-Type: multipart/alternative; boundary="001a11402492cb97fc05554888c1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/5twe-elR8bD9tF1mZXm1OEIMbl0>
Subject: Re: [CCAMP] [OPSAWG] Draft on YANG for state machine
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ccamp/>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jul 2017 08:41:50 -0000

Dear Tom,

many thanks for the comments. I reply inline below:

2017-07-26 18:35 GMT+02:00 t.petch <ietfc@btconnect.com>;:

> Nicola
>
> The title of this I-D caught my eye but when I read it, I struggle to
> see the connection between the content and the title.
>
> If you are really extending YANG, then to me it is axiomatic that the
> work should be done in the NETMOD WG.  Reading the I-D, I struggle to
> see what extensions you want to make to YANG.
>
>
We have decided to modify the title (and the content) in the next version
of the draft by removing the word "extension". Indeed, also from a previous
email exchange before the Prague meeting, after a comment from Robert by
Cisco, we noticed that this word can create misunderstanding since we
actually do not use the "extension" keyword supported by YANG.
Regarding the working group we are still discussing among co-authors, also
depending on the use cases we will find.


> Starting from an FSM perspective, I would have thought that a data
> modelling language would not make a good starting point.
>

Within IETF, we have seen proposals for modeling policies with YANG.
Formally, here is something similar.


>
> And the phraseology used in the I-D surprises me e.g.
>
> " First, NETCONF
>    supports both control and management functionalities, thus permits
>    high programmability. "
> Um, NETCONF is an application protocol that can transfer such things as
> chunks of ASN.1 or SQL from A to B using a paradigm of RPC (with events
> tacked on the side).
>
> How this relates to control and management funtionalities I struggle to
> see.
>

We can rephrase that sentence. What we meant is that NETCONF supports
messages for configuration (e.g., <edit-conf>) and others such as the
<notification> message that can be used to implement alarms based on a
notification subscription (<create-subscription>).


>
> Perhaps a non-optical example would make things clearer.
>

We are working on that. Thanks.

Best regards,
Nicola



>
> Tom Petch
>
>
> ----- Original Message -----
> From: "nicola sambo" <nicosambo@gmail.com>;
> To: "Daniele Ceccarelli" <daniele.ceccarelli@ericsson.com>;
> Cc: "Greg Mirsky" <gregimirsky@gmail.com>;; <opsawg@ietf.org>;;
> <ccamp@ietf.org>;; <n.sambo@sssup.it>;
> Sent: Wednesday, July 26, 2017 10:13 AM
>
> Hi Daniele,
>
> thanks for the suggestion. We will generalize it and include further use
> cases as the one anticipated by Giuseppe.
>
> And we are open to include further contributions if any.
>
> Best,
> Nicola
>
> Il martedì 25 luglio 2017, Fioccola Giuseppe <
> giuseppe.fioccola@telecomitalia.it>; ha scritto:
>
> > Hi Daniele and All,
> >
> > As one of the coauthors of this draft, I also agree about the purpose
> to
> > generalize this proposal.
> >
> > And regarding this aspect, we will add a new use case for IP and
> Overlay
> > Network that is inspired by a well-known IPPM methodology
> > (draft-ietf-ippm-alt-mark) and in particular its application in an SDN
> > oriented environment (draft-fioccola-ippm-multipoint-alt-mark).
> >
> > Of course, NETMOD WG could be also taken into consideration.
> >
> >
> >
> > Best Regards,
> >
> >
> >
> > Giuseppe
> >
> >
> >
> > *Da:* Daniele Ceccarelli [mailto:daniele.ceccarelli@ericsson.com
> > <javascript:_e(%7B%7D,'cvml','daniele.ceccarelli@ericsson.com');>]
> > *Inviato:* martedì 25 luglio 2017 18:14
> > *A:* nicola sambo; opsawg@ietf.org
> > <javascript:_e(%7B%7D,'cvml','opsawg@ietf.org');>; ccamp@ietf.org
> > <javascript:_e(%7B%7D,'cvml','ccamp@ietf.org');>
> > *Cc:* Greg Mirsky; Fioccola Giuseppe; n.sambo@sssup.it
> > <javascript:_e(%7B%7D,'cvml','n.sambo@sssup.it');>
> > *Oggetto:* RE: [OPSAWG][CCAMP] Draft on YANG for state machine
> >
> >
> >
> > Hi Nicola,
> >
> >
> >
> > Thanks for bringing this up. As i said during the OPSAWG session
> @IETF99 I
> > believe you should have a generalized version of this document (not
> > starting from an optical use case) and then build on new use cases and
> > possibly technology specific extensions.
> >
> > Personally I believe the work should be done in the OPS area, probably
> in
> > the OPSAWG or even better in NETMOD WG.
> >
> >
> >
> > Cheers
> >
> > Daniele
> >
> >
> >
> > *From:* nicola sambo [mailto:nicosambo@gmail.com
> > <javascript:_e(%7B%7D,'cvml','nicosambo@gmail.com');>]
> > *Sent:* martedì 25 luglio 2017 12:38
> > *To:* opsawg@ietf.org
> <javascript:_e(%7B%7D,'cvml','opsawg@ietf.org');>;
> > ccamp@ietf.org <javascript:_e(%7B%7D,'cvml','ccamp@ietf.org');>
> > *Cc:* Greg Mirsky <gregimirsky@gmail.com
> > <javascript:_e(%7B%7D,'cvml','gregimirsky@gmail.com');>>; Fioccola
> > Giuseppe <giuseppe.fioccola@telecomitalia.it
> > <javascript:_e(%7B%7D,'cvml','giuseppe.fioccola@telecomitalia.it');>>;
> > Daniele Ceccarelli <daniele.ceccarelli@ericsson.com
> > <javascript:_e(%7B%7D,'cvml','daniele.ceccarelli@ericsson.com');>>;
> > n.sambo@sssup.it <javascript:_e(%7B%7D,'cvml','n.sambo@sssup.it');>
> > *Subject:* [OPSAWG][CCAMP] Draft on YANG for state machine
> >
> >
> >
> > Dear all,
> >
> >
> >
> > I'd like to continue the discussion related to the draft:
> >
> >
> >
> > https://datatracker.ietf.org/doc/draft-sambo-opsawg-ccamp-
> > supa-ext-yang-fsm/
> >
> >
> >
> > In particular, please let me know if you have comments about
> >
> >
> >
> > - working group of the draft
> >
> > - use cases of application
> >
> > - other
> >
> >
> >
> > Slides presented at the meeting are available here
> >
> <https://www.dropbox.com/s/qhq2n6bmlp8ifkj/draft-sambo-opsawg-ccamp-supa
> -ext-yang-fsm-00.pptx?dl=0
> <https://www.dropbox.com/s/qhq2n6bmlp8ifkj/draft-sambo-opsawg-ccamp-supa-ext-yang-fsm-00.pptx?dl=0>
> >.
> > Any comment and contribution are welcome.
> >
> >
> >
> > Thanks. Best,
> >
> > Nicola
> > Questo messaggio e i suoi allegati sono indirizzati esclusivamente
> alle
> > persone indicate. La diffusione, copia o qualsiasi altra azione
> derivante
> > dalla conoscenza di queste informazioni sono rigorosamente vietate.
> Qualora
> > abbiate ricevuto questo documento per errore siete cortesemente
> pregati di
> > darne immediata comunicazione al mittente e di provvedere alla sua
> > distruzione, Grazie.
> >
> > * This e-mail and any attachments is confidential and may contain
> > privileged information intended for the addressee(s) only.
> Dissemination,
> > copying, printing or use by anybody else is unauthorised. If you are
> not
> > the intended recipient, please delete this message and any attachments
> and
> > advise the sender by return e-mail, Thanks. *
> >
> > *Rispetta l'ambiente. Non stampare questa mail se non è necessario.*
> >
>
>
>
> ------------------------------------------------------------------------
> --------
>
>
> > _______________________________________________
> > OPSAWG mailing list
> > OPSAWG@ietf.org
> > https://www.ietf.org/mailman/listinfo/opsawg
> >
>
>