Re: [netmod] WG adoption poll - instance-data

Martin Bjorklund <mbj@tail-f.com> Tue, 09 October 2018 12:25 UTC

Return-Path: <mbj@tail-f.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA557131308; Tue, 9 Oct 2018 05:25:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 UDSrNrxy7wSI; Tue, 9 Oct 2018 05:25:09 -0700 (PDT)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 76CB5131303; Tue, 9 Oct 2018 05:25:09 -0700 (PDT)
Received: from localhost (unknown [173.38.220.61]) by mail.tail-f.com (Postfix) with ESMTPSA id CF1A01AE0428; Tue, 9 Oct 2018 14:25:07 +0200 (CEST)
Date: Tue, 09 Oct 2018 14:25:06 +0200 (CEST)
Message-Id: <20181009.142506.637283350958767455.mbj@tail-f.com>
To: balazs.lengyel@ericsson.com
Cc: lberger@labn.net, netmod-chairs@ietf.org, netmod@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <58f8baa5-320c-a75e-62ef-e277d488b962@ericsson.com>
References: <b8f163ea-ea33-53a6-3fac-944b8d6c03ec@labn.net> <20181009.125822.1764836266889190398.mbj@tail-f.com> <58f8baa5-320c-a75e-62ef-e277d488b962@ericsson.com>
X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/pE6FC3vZbFh10JIEq-xGE0UgQP8>
Subject: Re: [netmod] WG adoption poll - instance-data
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Oct 2018 12:25:12 -0000

Hi,

Balázs Lengyel <balazs.lengyel@ericsson.com> wrote:
> Hello Martin,
> 
> I agree that this document shall be about defining the file format,
> and server capabilities shall only be a use-case.)
> 
> I already took out a lot of text, that explicitly recommended using
> instance data for documenting capabilities. Server capabilities are
> only mentioned in the introduction chapter.
> As you wrote: There is no _normative_  specification of how a server
> would document its capabilities, because this is
> what the WG requested, so I removed it.

Hmm.  Ok, if this is what the WG wants, then it is fine to just have
server capabilities as an example use case.  (I thought that the WG
wanted a normative description of server capabilities...)

> I see that I forgot to change the title and the introduction can be
> reworded to make
> it more clear that documenting server capabilities is just a use-case.
> (I still see it as the primary use-case for instance data.)

I think all text in 2 Introduction (except the last para) in this case
should be moved to section 2.1, and new text should be written in 2.

(*if* there will be a separate doc for server capabilities, the text
in 2 should be moved to that doc instead.)

>  If I promise to change the title and clarify the introduction can you
> support adoption?

First of all I'd like to ensure that the WG in fact just wants to do
the file format.  Since people have expressed support for adopting the
draft with the current title, I'm not so sure that this is the case.

I think you should make those changes, and I support the adoption of
the modified document.  I don't see any reason not to make these
chanegs before posting as a WG doc.


/martin



> 
> regards Balazs
> 
> On 2018. 10. 09. 12:58, Martin Bjorklund wrote:
> > Hi,
> >
> > I still think that this draft should either be split into two, one for
> > specifiying the generic file format (ok with examples), and one for
> > "Documenting Server Capabilities", or the document should just be
> > about the file format (+ *examples*).
> >
> > [The current document mixes the two; it's a bit as if we had "The
> > YANG language and a model for interfaces" as one doc...]
> >
> > It is clear that the document specifies a file format for YANG
> > instance data, which is good.  But it is not clear if the document
> > intends to specify how a server should document its capabilities.
> >
> > The Introduction mainly talks about why it is important to document
> > server capabilities.  But then AFAICT there is no normative
> > specification of how a server would document its capabilities.
> >
> >
> > /martin
> >
> >
> > Lou Berger <lberger@labn.net> wrote:
> >> All,
> >>
> >> This is start of a two week poll on making
> >> draft-lengyel-netmod-yang-instance-data-04 a working group
> >> document. Please send email to the list indicating "yes/support" or
> >> "no/do not support".  If indicating no, please state your reservations
> >> with the document.  If yes, please also feel free to provide comments
> >> you'd like to see addressed once the document is a WG document.
> >>
> >> The poll ends Oct 22.
> >>
> >> Thanks,
> >>
> >> Lou (and co-chairs)
> >>
> >> _______________________________________________
> >> netmod mailing list
> >> netmod@ietf.org
> >> https://www.ietf.org/mailman/listinfo/netmod
> >>
> > _______________________________________________
> > netmod mailing list
> > netmod@ietf.org
> > https://www.ietf.org/mailman/listinfo/netmod
> >
> -- 
> Balazs Lengyel                       Ericsson Hungary Ltd.
> Senior Specialist
> Mobile: +36-70-330-7909 email: Balazs.Lengyel@ericsson.com
> 
>