Re: [netmod] Instance-data-format -additional simplified format to define content schema

"Rob Wilton (rwilton)" <rwilton@cisco.com> Tue, 23 July 2019 21:47 UTC

Return-Path: <rwilton@cisco.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 938ED1202E2 for <netmod@ietfa.amsl.com>; Tue, 23 Jul 2019 14:47:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=dTxPqHBw; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=kHbwPgBL
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 EV5-pqbR_jhb for <netmod@ietfa.amsl.com>; Tue, 23 Jul 2019 14:47:08 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12479120120 for <netmod@ietf.org>; Tue, 23 Jul 2019 14:47:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13376; q=dns/txt; s=iport; t=1563918428; x=1565128028; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=HMUvImiwY3myxYzKt/Ok9NlONnNCdXw0/E5CB+5Zzec=; b=dTxPqHBwIwmTI9sywqCxKg8uUG7/n3Kc8jL1DS9HI14651t5gWYEY/mJ eb0dBHvaS9HfiBOyZLw/ib5ANp9vsHB2joV+Abso8po+rQeI5+KzDrTbM 2uPMAvPai3RlzEzC3vNm0sCTzuviE9Py9Uyp/F6HkXDRw2D3WPXcsM2I/ k=;
IronPort-PHdr: 9a23:cx3V5BwUfYuZTxTXCy+N+z0EezQntrPoPwUc9psgjfdUf7+++4j5YhSN/u1j2VnOW4iTq+lJjebbqejBYSQB+t7A1RJKa5lQT1kAgMQSkRYnBZufFkz/MPnsRyc7B89FElRi+iLzPA==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ClAADdfzdd/4cNJK1mHAEBAQQBAQcEAQGBVQUBAQsBgRQvUANtVSAECyqHZAOOAEyCD5J7hFWBLoEkA1QJAQEBDAEBLQIBAYRAAoJOIzYHDgEDAQEEAQECAQZthR4MhUoBAQEBAxIbEwEBLAwPAgEIEQQBASgHMhQJCAEBBAESCBMHgwGBHU0DHQECoAECgTiIYIIjgnkBAQWBNgMLQ4MDGIITCYE0AYRxhm0XgUA/gVeCTD6CYQSBYTSDB4ImjC+HRyNblXMJAoIZhXmOLoItizGKLI01l1ACBAIEBQIOAQEFgVcBMIFYcBU7gmyCQoNxilNygSmOJAEB
X-IronPort-AV: E=Sophos;i="5.64,300,1559520000"; d="scan'208,217";a="382954958"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 23 Jul 2019 21:47:07 +0000
Received: from XCH-ALN-003.cisco.com (xch-aln-003.cisco.com [173.36.7.13]) by alln-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id x6NLl6lC007535 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 23 Jul 2019 21:47:06 GMT
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by XCH-ALN-003.cisco.com (173.36.7.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 23 Jul 2019 16:47:06 -0500
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 23 Jul 2019 17:47:05 -0400
Received: from NAM03-DM3-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Tue, 23 Jul 2019 17:47:05 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=T32CXOT7qVOsBlqOiEo+VBsufzuDKn4PM1EYrikvWZE1ZA2EwPsLSS3feaXb/POKf598pS7TD4rujWfCTC0JWbag258pqQ317PqnE0K+ulytQYBkCiccXQP82LKYje4kbqbpe4AuptzPP85aYp8gNhUdDN+hFliEebjU2Axyhpbt+/PyIo8WF4lIi4xWds5a1zgGCXuN9CNK1Jna1EkDFpwqfExy804+4dtmvDLtwaN8x2dx/acI4XWxifaXgTvpPyHhF6UvZ31YrVfvQQhdUynMl/x3tfupi9q/X+mReCXYsPHtsoIwylO3nsTKp0AeNV8goiPSQ5x1Ko/6JpZV1w==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=+xZu+vrLe59RnBU3drUcpezirXsJtEkqkGc/WnOBULY=; b=JXP7dBh7r4qK9q8e3jdjVepHS8LjWHSYljwu0GD37XIYcf9EtLq5YR1RHlLT/t8Cnm7yJIhHKKakaYzryD2ys2clKLkWTgvTxGF25/6uY9FU9M+HbMPEkf4H9yqBIG04/kWIZ4U0K6i0Zq/oJOE+e2K7L87a9Om+J3X5undXHttGA+d21XIcuzrp3JpQ5I7B6n2fyIjU2Okq0b8Vw+b4M1DyB8b2vDbJSOXjj3KsQOhhfF1uHgV4LIBnPX56wwSYUedwxGVP5XFa9qTMOQ8b+uFcvmTQlQm+fVDNf+SoKkLPCRul/luDzF5aohzX2GrtHdRYYhf5Gc6PmDHNwDOwQQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1;spf=pass smtp.mailfrom=cisco.com;dmarc=pass action=none header.from=cisco.com;dkim=pass header.d=cisco.com;arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=+xZu+vrLe59RnBU3drUcpezirXsJtEkqkGc/WnOBULY=; b=kHbwPgBLzvkzGaCoE48XGwuhF/2SHhEQed1wrl84iCaYa9nL0+uaOJfloE1Kc4rEhXUnGBDDL8CKTl4m1BXJ6o3HZJgxA2w+XNWsk2vR6Zh1UGi48mhBY+YzfX5WvQVmaCRFpkeKTf3zr9BYdfK9zBSYR0Zg0D0FHKO5btUZ57E=
Received: from BYAPR11MB2631.namprd11.prod.outlook.com (52.135.227.28) by BYAPR11MB2534.namprd11.prod.outlook.com (52.135.226.30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2094.16; Tue, 23 Jul 2019 21:47:04 +0000
Received: from BYAPR11MB2631.namprd11.prod.outlook.com ([fe80::91da:1669:aaf0:d428]) by BYAPR11MB2631.namprd11.prod.outlook.com ([fe80::91da:1669:aaf0:d428%4]) with mapi id 15.20.2094.013; Tue, 23 Jul 2019 21:47:04 +0000
From: "Rob Wilton (rwilton)" <rwilton@cisco.com>
To: Balázs Lengyel <balazs.lengyel@ericsson.com>, "'netmod@ietf.org'" <netmod@ietf.org>
Thread-Topic: Instance-data-format -additional simplified format to define content schema
Thread-Index: AdVAya70t7DO6UXsR/K+POkwpw7dKAA1fHnQ
Date: Tue, 23 Jul 2019 21:47:04 +0000
Message-ID: <BYAPR11MB2631083F050EC52BC32D7270B5C70@BYAPR11MB2631.namprd11.prod.outlook.com>
References: <VI1PR0701MB2286EB7A76261C01996A67CBF0C40@VI1PR0701MB2286.eurprd07.prod.outlook.com>
In-Reply-To: <VI1PR0701MB2286EB7A76261C01996A67CBF0C40@VI1PR0701MB2286.eurprd07.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=rwilton@cisco.com;
x-originating-ip: [2001:420:c0c8:1002::367]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 15534272-4fb6-454b-2f63-08d70fb74d24
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:BYAPR11MB2534;
x-ms-traffictypediagnostic: BYAPR11MB2534:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <BYAPR11MB2534378E10BDF5D6E8986391B5C70@BYAPR11MB2534.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0107098B6C
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(376002)(366004)(396003)(346002)(39860400002)(189003)(199004)(86362001)(55016002)(6436002)(2906002)(81166006)(9686003)(54896002)(790700001)(6246003)(33656002)(6306002)(68736007)(6116002)(81156014)(53936002)(236005)(8936002)(9326002)(66574012)(14444005)(71200400001)(71190400001)(5660300002)(14454004)(229853002)(7696005)(76116006)(110136005)(478600001)(446003)(64756008)(66556008)(66476007)(316002)(76176011)(7736002)(256004)(25786009)(476003)(66946007)(11346002)(52536014)(486006)(102836004)(46003)(8676002)(74316002)(6506007)(53546011)(99286004)(66446008)(186003)(491001); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB2534; H:BYAPR11MB2631.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: JNvTRAUFrLSNs2MteEY3mCpx87wO6gZBpRAxVVjl52eqqbPIGgMdWSJ9/o3IkgYTQsB1XHpjqloSC/BGmS5M9DtysHTXTRBZvQ+AArVyA9pYcnA2HnBmQIyJR5JQ8xuyqj91vbFhAR+H8cYGhHwSG1pJQNxxvEp9AZgygoCgOaeFWpoYaP0xX54dO9sM67/dDPN/F93AlXWk6myjqQW5K7jPrLmshaAy0YayHZL3xCCKKEEp6zXQ8TK98usejDHLtMijT+XoG+JNLC31JcVvx6odukjhapBdBcrCyyIHTuaz3T3hpHF60IurexrokTGnw6LCxn/qVacOd/7098o43pI8bJx/NlSuTRywjs+Qt7fdnxreW/kLrKQxeTeT0z0O/vXRFegPGtxvwy8zCvbWbmQoTApSxxOI76HT5OoVYVQ=
Content-Type: multipart/alternative; boundary="_000_BYAPR11MB2631083F050EC52BC32D7270B5C70BYAPR11MB2631namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 15534272-4fb6-454b-2f63-08d70fb74d24
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Jul 2019 21:47:04.2224 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: rwilton@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB2534
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.13, xch-aln-003.cisco.com
X-Outbound-Node: alln-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/Utho403gZQvf1ZJJMbELER2liJ8>
Subject: Re: [netmod] Instance-data-format -additional simplified format to define content schema
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, 23 Jul 2019 21:47:11 -0000

Hi Balazs,

Yes, I think this looks good to me.

Thanks,
Rob


From: netmod <netmod-bounces@ietf.org> On Behalf Of Balázs Lengyel
Sent: 22 July 2019 16:13
To: 'netmod@ietf.org' <netmod@ietf.org>
Subject: [netmod] Instance-data-format -additional simplified format to define content schema

Hello,
At the IETF 105 Netmod meeting it was stated that the flexible solution to define the context schema inline (requested earlier on the mailing list) is quite complex, so a fourth simpler method to define content schema inline is needed.
The fourth method would add one more choice to "choice content-schema-spec   "

case simplified-inline {
  leaf-list module  {
    type string {
       pattern '.+@\d{4}-\d{2}-\d{2}\.yang';
     }
     description "The list of content defining YANG
       modules including the revision date for each.
       Usage of this leaf-list implies the modules are
       used without any deviations and with all features
       supported.";
  }
}

An example instant data example could be:
<instance-data-set xmlns="urn:...:ietf-yang-instance-data">
  <name>read-only-acm-rules</name>
  <module>ietf-yang-library@2019-01-04.yang</module<mailto:ietf-yang-library@2019-01-04.yang%3c/module>>

  <module>ietf-netconf-acm@2012-02-22.yang</module<mailto:ietf-netconf-acm@2012-02-22.yang%3c/module>>

  <revision>

    <date>1776-07-04</date>

    <description>Initial version</description>

  </revision>

  <description>Access control rules for a read-only role.</description>

  <content-data>...

Do you like it ? Adding this case are you OK with the content-schema-spec definition?
Regards Balazs