[i2rs] YANG validation and opstate

Andy Bierman <andy@yumaworks.com> Sun, 05 June 2016 21:42 UTC

Return-Path: <andy@yumaworks.com>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB72E12D636 for <i2rs@ietfa.amsl.com>; Sun, 5 Jun 2016 14:42:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 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] 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 wzweP-zFF4FR for <i2rs@ietfa.amsl.com>; Sun, 5 Jun 2016 14:42:31 -0700 (PDT)
Received: from mail-yw0-x235.google.com (mail-yw0-x235.google.com [IPv6:2607:f8b0:4002:c05::235]) (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 7C03212D626 for <i2rs@ietf.org>; Sun, 5 Jun 2016 14:42:31 -0700 (PDT)
Received: by mail-yw0-x235.google.com with SMTP id c127so125073826ywb.1 for <i2rs@ietf.org>; Sun, 05 Jun 2016 14:42:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks-com.20150623.gappssmtp.com; s=20150623; h=mime-version:date:message-id:subject:from:to; bh=+EVjeFXe/25czphFIDtmFPnbRISq1/oXGvG1OjPSGvI=; b=NYakSRRWTyBP0uYWrmWE0Qwe67cMHbNTX97ySZUPA00kWHdBVlAmh2RamuUh1ZZ5d5 +DMZCwqRmeJzx9pCueZPNVG8iz8r0yM7RFlAvsK7c0QHX2eMMwSkfTzy8ok5XVvbg3hg 5+S7tyjtllsHdwlcPiKi4MhoOxQx6SMG0Em2e45ow+7C1ibyrVClJEaVxTBTOLKjjy3U /jCfSQJ30W6q5uPTT0Do2s89NxVa/pyT2qXPmUSszNdUK3xdJC3dZbvk73KR/2Bh/lP2 PsRZ32EjjinQhjquiLq0YWvRhrvaNodaEfMhBs4zQfwJooT/aoUkO990tspTCa31J/Sh eyAA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=+EVjeFXe/25czphFIDtmFPnbRISq1/oXGvG1OjPSGvI=; b=ZzbAmEcdUvPHneUsKsAMPlxNBTxWFziD/per9jwB0h4jQO2yDjlcfkSC1Bxw3Ib6GK TFqog3sAz5I0cqQMjzTSNq7/YTFyZQe7tXQP4qfkOwwlUf6vBS7ZSCvmD4QXPx+2O4s2 BtNkkeV+57lPyPdx2PnkoSN4AO3c4Ee3as7i7hqLMDwWQBAJTcXfdAhbSTC8iuDzeH67 veFl3aHBP0sP+pTGbU8HEqU5m/9CJlju0mKKUHZEyktklhxRCp3zvEOimPlLeOT6Y1qQ jBNp6YKEUBLF5V87Yiy60VzqkgvvDuuqxBtlvQXPhP9FBVAbW/W+Q0A9qP7OQMGuuDXy w4Tg==
X-Gm-Message-State: ALyK8tKWV2QHA9IRjcAQB10hexEqGSBu1uhiLNfqWccbkJgFLTu2pujwaGaqw7r5+CkTdLaRUuWPgAMi3j0PlQ==
MIME-Version: 1.0
X-Received: by 10.13.202.15 with SMTP id m15mr9172142ywd.259.1465162950741; Sun, 05 Jun 2016 14:42:30 -0700 (PDT)
Received: by 10.37.115.68 with HTTP; Sun, 5 Jun 2016 14:42:30 -0700 (PDT)
Date: Sun, 05 Jun 2016 14:42:30 -0700
Message-ID: <CABCOCHQAuhsngAKXE=-o=wWsv1u6BXDWCJ--0JJ4p5D0f2WY3Q@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
To: "i2rs@ietf.org" <i2rs@ietf.org>
Content-Type: multipart/alternative; boundary="001a11481ab637966005348ed5e3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/tK_n7lFlIEyDOId66Y7BHvrjoOg>
Subject: [i2rs] YANG validation and opstate
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <i2rs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs>, <mailto:i2rs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2rs/>
List-Post: <mailto:i2rs@ietf.org>
List-Help: <mailto:i2rs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs>, <mailto:i2rs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Jun 2016 21:42:33 -0000

Hi,

I don't really agree with idea that I2RS agents pick which
YANG statements they will implement, but I think there is
a way to handle this correctly in the datastore framework.

The proposed enumeration for server validation
capabilities (e.g., full, XPath, leafref) is not really needed.
This enum is too course-grained to be useful.

IMO it is better to say the server MAY do YANG validation
on the ephemeral datastore.  Whether or not the server uses
data from the ephemeral datastore is left as an implementation detail.
The server could use invalid input parameters or ignore them
or reject them in the first place.

The client needs to check operational state to know if/when the
ephemeral data was applied to the system.



Andy