Re: [Netconf] WG LC for draft-ietf-netconf-rfc6536bis

Andy Bierman <andy@yumaworks.com> Sun, 28 May 2017 17:17 UTC

Return-Path: <andy@yumaworks.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26183129412 for <netconf@ietfa.amsl.com>; Sun, 28 May 2017 10:17:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=yumaworks-com.20150623.gappssmtp.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 EnC3kWP0GHtQ for <netconf@ietfa.amsl.com>; Sun, 28 May 2017 10:17:02 -0700 (PDT)
Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (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 9A6A412940B for <netconf@ietf.org>; Sun, 28 May 2017 10:17:01 -0700 (PDT)
Received: by mail-wm0-x22c.google.com with SMTP id d127so32186654wmf.0 for <netconf@ietf.org>; Sun, 28 May 2017 10:17:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=A/W4MziB/JU0dsXN9ca6SMC3fgaKKAO2oMi9gOg1FG0=; b=pjOjKUy6hORZTHi31z+/WwhiDLnFc8/jz5FY2Z7rWoZXEZZQlIkeO341FuNEvzwT8Y M+kn1z9gYNL5Zjnf6ACXWbByZx3kukbSRXrTdrGzaM5ijdh50uG1cr6BU8ugRJMSoXl7 0xftazy6eTxMUkXsrlaI52dUGe8vQkTax3fDPlDKB5Uc7gmMPuxdAxRBfBfhltSKYia0 o41jv1jhyzRkhy0sSsyO82A0C47Ug+hsopGrCCc6RdtTjxie7uMjaSX4AfQSgNALf9Uh w3t7YF4ISBXEt93dHYjhLgbV+sSxC41YE0A1h1JJ3gRE2nHdjwaoD29542ztpXmeWOGg mauw==
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=A/W4MziB/JU0dsXN9ca6SMC3fgaKKAO2oMi9gOg1FG0=; b=Zv4qmtMhgbXwX1ygn3j+FcbJq9cTV7s96Ne01NT+UyPrY9lxnmhI38uLL2RlC1OJkQ 5WypzLU8SGco4IsRGUYC5PXhFfvZnNnfuSQYdDVDd+FIGIIdqH8OR5wTblEeGWwYLh+X shcwgX1t/UyyrtKTiYxz8LuDat4mW89zBH/ND68qzpa8zRZ/cvhISHHLH/NtMI3YprMT Exfqsuqp3U4tL4FDa9gfpfUk3Z1ARnXt/z+gqSREQexJbwxhdtR+l+vftcFznglb36Xe Qq1iMuu8MIn8tpkIWT6d0xO6Y3Y65k/yxUT24/KNx5E78G0/h9RHZ7pGVJXVJDDUuVv2 KvAw==
X-Gm-Message-State: AODbwcC2ZIVtyrLMZxgN1eAkf7Rfgh6JFdQBZQIQb56BmlnAPLLvekh9 fWAPRJdZwPnHgznvqkjy/CHFZRjijQFn
X-Received: by 10.223.134.80 with SMTP id 16mr9273491wrw.62.1495991820082; Sun, 28 May 2017 10:17:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.155.2 with HTTP; Sun, 28 May 2017 10:16:59 -0700 (PDT)
In-Reply-To: <02b101d2d6de$6cf44fc0$4001a8c0@gateway.2wire.net>
References: <20170523.091519.1988324449434279102.mbj@tail-f.com> <D13AF5F3-1AE1-4A43-866F-10984114BF2C@gmail.com> <CABCOCHTjLL7bFCVYHwUYEx-gKG=JaiWiftx2wJSce=LjjrbyNQ@mail.gmail.com> <20170524.091650.1982503698804665659.mbj@tail-f.com> <CABCOCHRk05FYXnLDw1eZyXxx=smGoLSPG83vGtUXGWojetugqg@mail.gmail.com> <02b101d2d6de$6cf44fc0$4001a8c0@gateway.2wire.net>
From: Andy Bierman <andy@yumaworks.com>
Date: Sun, 28 May 2017 10:16:59 -0700
Message-ID: <CABCOCHT-Xu5gnrZ2MU1LHq8CTXSEdsweQsf8qCeqqQ-j9=N5Mg@mail.gmail.com>
To: "t.petch" <ietfc@btconnect.com>
Cc: Martin Bjorklund <mbj@tail-f.com>, Netconf <netconf@ietf.org>
Content-Type: multipart/alternative; boundary="001a11491e7e05f558055098bd77"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/ZCa_cKnvHsU3b-L5EI3_cmazU60>
Subject: Re: [Netconf] WG LC for draft-ietf-netconf-rfc6536bis
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Network Configuration WG mailing list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 May 2017 17:17:04 -0000

Hi,

Just be clear -- we will add explicit support for revised datastores, not
just a
normative reference for terminology.  The NACM CRUDX mappings for the
intended, applied, and operational datastores will be in this draft.

Are there any objections to adding revised datastore support to NACM?
This might be an expansion of scope for the charter item.


Andy


On Sat, May 27, 2017 at 4:19 AM, t.petch <ietfc@btconnect.com> wrote:

> ----- Original Message -----
> From: "Andy Bierman" <andy@yumaworks.com>
> Sent: Saturday, May 27, 2017 3:20 AM
>
> On Wed, May 24, 2017 at 12:16 AM, Martin Bjorklund <mbj@tail-f.com>
> wrote:
>
> > Andy Bierman <andy@yumaworks.com> wrote:
> > > On Tue, May 23, 2017 at 12:41 PM, Mahesh Jethanandani <
> > > mjethanandani@gmail.com> wrote:
> > >
> > > >
> > > > > On May 23, 2017, at 12:15 AM, Martin Bjorklund <mbj@tail-f.com>
> > wrote:
> > > > >
> > > > > Andy Bierman <andy@yumaworks.com> wrote:
> > > > >> Hi,
> > > > >>
> > > > >> The update is on github.
> > > > >> http://github.com/netconf-wg/rfc6536bis
> > > > >>
> > > > >> I would like Martin to look it over before it is posted.
> > > > >
> > > > > Done, and the new text looks good.  I moved the new subsection
> to be
> > > > > the first in 3.2, and I also fixed some minor terminology
> issues.
> > > > >
> > > > > But, I wonder if we shouldn't make the document even less
> NETCONF
> > > > > specific, and align the terminology to revised-datastores.  For
> > > > > example, currently the document talks about access to "NETCONF
> > > > > datastores".   With the new less protocol-specific terminology
> this
> > > > > would simply be "datastore”.
> > > >
> > > > I would prefer this.
> > > >
> > >
> > > OK, but the operations are somewhat NETCONF specific.
> > > We will try to make sure we do not create more inconsistencies than
> we
> > > remove ;-)
> >
> > Yes.  But I think what we should do is not any technical changes, just
> > align terminology.
> >
> >
>
> OK -- the term NETCONF datastore was used twice, now just datastore.
> (pushed to github)
>
> The term datastore appears a lot.  There are 3 variants:
>
>     - datastore
>     - configuration datastore
>     - target datastore
>
> With revised datastores these are not all the same anymore.
> We probably need to go through the entire document and check if the
> correct variant is used in each instance.
>
> Are there other terms that are needed for alignment?
>
> Does NACM need to reference the revised-datastores draft to import
> terminology?
>
> <tp>
>
> Yes, Normative Reference please.
>
> Tom Petch
>
> > /martin
>
> Andy
> > >
> > > Andy
>
>