Re: [NGO] NETCONF Data Modeling BoF (NDM) proposal

Phil Shafer <phil@juniper.net> Mon, 10 September 2007 13:42 UTC

Return-path: <ngo-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IUjWc-0001w3-KF; Mon, 10 Sep 2007 09:42:02 -0400
Received: from ngo by megatron.ietf.org with local (Exim 4.43) id 1IUjWa-0001oK-Vg for ngo-confirm+ok@megatron.ietf.org; Mon, 10 Sep 2007 09:42:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IUjWa-0001kw-JP for ngo@ietf.org; Mon, 10 Sep 2007 09:42:00 -0400
Received: from smtpb.juniper.net ([207.17.137.119]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IUjWZ-0005VE-BC for ngo@ietf.org; Mon, 10 Sep 2007 09:42:00 -0400
Received: from unknown (HELO magenta.juniper.net) ([172.17.27.123]) by smtpb.juniper.net with ESMTP/TLS/DES-CBC3-SHA; 10 Sep 2007 06:41:58 -0700
Received: from idle.juniper.net (idleski.juniper.net [172.25.4.26]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id l8ADfrI30747; Mon, 10 Sep 2007 06:41:53 -0700 (PDT) (envelope-from phil@juniper.net)
Received: from idle.juniper.net (localhost [127.0.0.1]) by idle.juniper.net (8.12.6/8.11.3) with ESMTP id l8ADfqql043484; Mon, 10 Sep 2007 09:41:52 -0400 (EDT) (envelope-from phil@idle.juniper.net)
Message-Id: <200709101341.l8ADfqql043484@idle.juniper.net>
To: Andy Bierman <ietf@andybierman.com>
Subject: Re: [NGO] NETCONF Data Modeling BoF (NDM) proposal
In-Reply-To: Your message of "Fri, 07 Sep 2007 11:01:26 PDT." <46E191F6.4010103@andybierman.com>
Date: Mon, 10 Sep 2007 09:41:52 -0400
From: Phil Shafer <phil@juniper.net>
X-Spam-Score: 1.2 (+)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Cc: NETCONF Goes On <ngo@ietf.org>
X-BeenThere: ngo@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: NETCONF Goes On - discussions on future work and extensions to NETCONF <ngo.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ngo>, <mailto:ngo-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ngo>
List-Post: <mailto:ngo@ietf.org>
List-Help: <mailto:ngo-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ngo>, <mailto:ngo-request@ietf.org?subject=subscribe>
Errors-To: ngo-bounces@ietf.org

Andy Bierman writes:
>There are tools that help do it for you, just
>like there are C compilers that do the ASM for you.

Which is why we standardize C, not ASM.

>BTW, I have 24 years, and a few of them writing
>device drivers in x86 ASM.

So you grok why only device drivers are written in ASM ;^)
(And gcc asm hooks mean you don't even need to do that)

>If people are not willing or able to learn XSD,
>then no WGs can ever really effectively standardize
>data models that use XSD to define the XML syntax.

Given the number of errors and surprises in the netconf
xsd (where people _were_ willing or able to learn XSD),
how can we inflict this on the rest of the ietf?

>(That's the Requirements Phase -- the
>first 18 months of the 5 year plan.)

Are you just trying to make me cry?

>Why can't max-access be a property of the data, which is realized
>in different ways.  In XSD, it would be an <appinfo> extension.

So you need extensions to your lower-level language to handle
high-level concepts?

>You're right that I don't use XSD to write data models.
>I am trying to refine my DML to optimize tool automation.
>I think it's way easier to use than XSD, but my language
>preference is for a C-like syntax (like SMIng).

Amen.

>Can agreement on a new DML really be reached in the IETF?
>A giant, complicated, "let's do everybody's idea" approach (ala DIFFSERV)
>is not going to work.  I am skeptical the WG result will be
>better and simpler than XSD.

The all-singing-all-dancing approach won't fly, but that doesn't
mean we're stuck w/ XSD.  I favor an incremental approach, starting
with a small number of important things, getting something working,
building trust, and then moving on to other issues.  This approach
works well, if future work builds on the initial work, rather than
recreating it.

>I completely agree that XSD is not the long term solution.

My opinion is that the IETF isn't a good place for short term solutions.

>I am quite frustrated with the progress that we have had using XSD.
>At a previous WG meeting, Simon asked people who did not understand XSD
>to abstain from a straw poll.  The count was 3 for, 3 against, 40+ abstain.

But _all_ the votes where single digit for/against.  My worry is
that this is a sign that folks have completely lost interest.  Which
would be very bad news.

Thanks,
 Phil


_______________________________________________
NGO mailing list
NGO@ietf.org
https://www1.ietf.org/mailman/listinfo/ngo