Re: [netmod] comment on draft-bierman-netmod-yang-data-ext

Kent Watsen <kwatsen@juniper.net> Tue, 28 November 2017 19:01 UTC

Return-Path: <kwatsen@juniper.net>
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 A011B1270A0; Tue, 28 Nov 2017 11:01:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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=juniper.net
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 14gwpCfB35CK; Tue, 28 Nov 2017 11:01:13 -0800 (PST)
Received: from mx0a-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 91A25126557; Tue, 28 Nov 2017 11:01:13 -0800 (PST)
Received: from pps.filterd (m0108159.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id vASIxVB3023456; Tue, 28 Nov 2017 11:01:13 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=PPS1017; bh=DTzpoSNL0tnA1mwTBlBUdKzFRsdSM+cNRyRtOiJ5Xrc=; b=yxNAz6R/oxsefpNYePZYwW32gO0m8nTAgnZCBQ0Qi9Ngqxne4FklRhYw6/7o7iRs+FFe MBIkIrncXcyAnVRUIcvadigIrT400PHaCEMq9oocukJt3UvjAVASUAdXDxCO+uz1NQKL hWVbIkBNqR14TxRjVZwJgnRXxjBcN+t2pPAUdd/UNKmX4v62EBX6NyIsUsLtXbTmSIkS 0g13DscDlHT1FfwpVLZblvfcL43MfMul3q0skXIbANvHl28Ns47UI5erA08KNFhbTTW9 w4L/PUr4MRAuR7cm3SxQlE5Pi3sD0WtN4P0em6wVxUXbred/Q2Pu1y/Ocet+lXZ3OJnu NA==
Received: from nam03-by2-obe.outbound.protection.outlook.com (mail-by2nam03lp0055.outbound.protection.outlook.com [216.32.180.55]) by mx0a-00273201.pphosted.com with ESMTP id 2ehdhx007n-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 28 Nov 2017 11:01:11 -0800
Received: from BLUPR05MB275.namprd05.prod.outlook.com (10.141.22.149) by BLUPR05MB276.namprd05.prod.outlook.com (10.141.22.151) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.282.3; Tue, 28 Nov 2017 19:01:10 +0000
Received: from BLUPR05MB275.namprd05.prod.outlook.com ([10.141.22.149]) by BLUPR05MB275.namprd05.prod.outlook.com ([10.141.22.149]) with mapi id 15.20.0282.004; Tue, 28 Nov 2017 19:01:10 +0000
From: Kent Watsen <kwatsen@juniper.net>
To: Lou Berger <lberger@labn.net>, Martin Bjorklund <mbj@tail-f.com>
CC: "draft-bierman-netmod-yang-data-ext@ietf.org" <draft-bierman-netmod-yang-data-ext@ietf.org>, "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: [netmod] comment on draft-bierman-netmod-yang-data-ext
Thread-Index: AQHTZ8r67MT+Ws8/z0S8Z2StvrCXRKMpjdOAgAAjb4CAACHXAA==
Date: Tue, 28 Nov 2017 19:01:10 +0000
Message-ID: <07BCAEEA-86FD-4F91-A786-70ACF2A236D9@juniper.net>
References: <a2eb0409-de68-0bcb-31be-c2acf2acb926@labn.net> <20171128.105313.1322848757325572415.mbj@tail-f.com> <160027f91b8.27d3.9b4188e636579690ba6c69f2c8a0f1fd@labn.net>
In-Reply-To: <160027f91b8.27d3.9b4188e636579690ba6c69f2c8a0f1fd@labn.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.20.0.170309
x-originating-ip: [66.129.241.14]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BLUPR05MB276; 6:RM661kEBcHTGUym5KcxxcsC42y2VKARxcYlOJlSSprdyRABL52W89hTHTxbUWLzDB4yd1U+CpoKd6Qq18HiNpERpwB+b8wHriqAPdGTbp26OYQ9oozBwfQkyyHkRkT4v8R3M+KGpaUF5GNy+ZNY4JIuJOHDkU11s8owRHyWm3BbPMl2fJdQi+jpDGCGLpQ/tf+odF6Hud7fvSRmDvFl+vvA4d7NZgJl3iJgsfud28OWEVs3NStNrXdeX6G/voPDDc1zEfPL4Lg0kEmAcHGjTa/xiBkB5EPoFy3eg+EeEw7KshWVrZ90qavQ4/9SegqSUy3eFk2GQJRxFrYarCDd1rPzcGjvGmOBj158L3hzlumw=; 5:YHJttIDNmNHBc6qX3GCd4OgonR2Y7cK10tkYp8FfRVLkFHVnPMzT21tJ1tw0o5mJd4U/u+m+slidNnAPlztmncIYr0VZtM2aBIekyyJF52Gxytwzm1J5y+xwqycgm7S0gy+KKesUvAEPKd4nB1AqLhw1HPLuw8+sSbcdxO1HQFQ=; 24:x/MpN63TxsY8k7DVqBdzBKBrBYku2DBjqfGsFH74Q0rKBhA+G44L0UjYdwX3a5Wm8b0yYHqD9+tM50kVDAS+VSii4Z/sEvl6RKduLRjz9KA=; 7:iP66YKAh27gogiiJSiKZtF7jNkGo8xK4VQQYDOYxbF35ZCYeF5kIA4kqS4ujy2RofVqLZ3uZnTK5UJkIfjeMGRpmssYrvffDiw/VYUfBmszzHnLQxYcakbvDMBuuFRmYDULexzUo6eOTpCMmUql8TmdB7bfS4Vpk6KnevtVXeOhV6R8mFRA09tKdSb0M4uYN0VTsne0B3W+cSoM9Bm5jDc31PuR4cNQvhUKRcXSOhndfwcKOAkKJ59Nyyx/C0huy
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: a36b1161-d2f6-49fc-b970-08d536926363
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(5600026)(4604075)(4534020)(4602075)(4627115)(201703031133081)(201702281549075)(48565401081)(2017052603258); SRVR:BLUPR05MB276;
x-ms-traffictypediagnostic: BLUPR05MB276:
x-microsoft-antispam-prvs: <BLUPR05MB2760C0E2E4818F2A8A2DE44A53A0@BLUPR05MB276.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(788757137089);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(2401047)(5005006)(8121501046)(3002001)(10201501046)(93006095)(93001095)(3231022)(6055026)(6041248)(20161123558100)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123562025)(20161123555025)(20161123564025)(20161123560025)(6072148)(201708071742011); SRVR:BLUPR05MB276; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:BLUPR05MB276;
x-forefront-prvs: 0505147DDB
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(376002)(39860400002)(366004)(346002)(199003)(24454002)(189002)(3660700001)(106356001)(102836003)(105586002)(6116002)(3846002)(83506002)(3280700002)(81166006)(81156014)(2900100001)(14454004)(7736002)(66066001)(478600001)(6246003)(189998001)(2950100002)(54356999)(99286004)(33656002)(76176999)(50986999)(8676002)(101416001)(305945005)(36756003)(229853002)(25786009)(68736007)(6512007)(6436002)(82746002)(77096006)(6486002)(6506006)(54906003)(110136005)(58126008)(53936002)(4326008)(2906002)(316002)(5660300001)(83716003)(86362001)(230783001)(97736004)(8936002); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR05MB276; H:BLUPR05MB275.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-microsoft-antispam-message-info: juak3PsI9+qJhqVfTf3m5zOEoD2KXDn5t4mQnuQ+hx6lxNqss1/s1E4r8lb6y1hCrFGvUWJVynyXdvSwjFXylQ==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <2DF0E4B218D3CF4FA2939E9BB8209F48@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: a36b1161-d2f6-49fc-b970-08d536926363
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Nov 2017 19:01:10.2460 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR05MB276
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-11-28_11:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1709140000 definitions=main-1711280255
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/Z_gfggxcQFBUso8dsqnkKInhs48>
Subject: Re: [netmod] comment on draft-bierman-netmod-yang-data-ext
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
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, 28 Nov 2017 19:01:16 -0000

As an author, I prefer having this draft (yang-data-ext) *update* RFC 8040 with text that explains that the rc:yang-data is deprecated and that modules should use the new yang-data definition instead.  

As NETCONF co-chair, I imagine that some future rfc8040bis will remove the rc:yang-data definition, but I don't think it is urgent to do now.

Kent


--

Hi Martin,

See below.


On November 28, 2017 4:55:17 AM Martin Bjorklund <mbj@tail-f.com> wrote:

> Hi,
>
> Lou Berger <lberger@labn.net> wrote:
>> Hi,
>>
>>     I was looking at how yd:yang-data (this draft) relates to
>> rc:yang-data (rfc8040).  The document seems to imply that this draft's
>> extension is a replacement in one place (see abstract) , is supplemental
>> in another (sec 1, plus augment-yang-data example) and perhaps
>> orthogonal in a final (that rc:yang-data is still used/referenced at
>> all).  I think the document should be clear as to it's objective with
>> respect to  rc:yang-data.
>
> Agreed.  It is intended to replace rc:yang-data.  I have fixed the
> example that used rc:yang-data.  Do you think we need any changes to
> section 1 to clarify this?
>

Only that it should also reflect how the update/deprecation discussed below 
is handled.

>> As rc:yang-data is currently defined in a protocol specific way, I (with
>> any/all hats) would prefer to see a definition of yang-data that would
>> work for any protocol that encodes and transports yang.  I also
>> generally think that having two definitions for basically the same
>> mechanism isn't beneficial to implementors of IETF RFCs, so this leads
>> me to suggest that if this document becomes a WG document it should
>> deprecate rc:yang-data.
>
> I assume this would formally mean that this document would "Update"
> RFC 8040,

Yes, this looks right. although it is a bit subject to how the next point 
is addressed

> and then in the document have text that explains that
> rc:yang-data is deprecated?  Or do you suggest that we actually do a
> 8040bis that formally marks the rc:yang-data extension as
> "deprecated", and instead uses yd:yang-data?
>

This is one option. Another is to just update the rc module with 
rc:yang-data as deprecated.

At this point, since the document is still an individual draft, I suggest 
that the authors propose their preference and that the working group weigh 
in during the acceptance and normal WG processing.

Thanks,

Lou

>
> /martin
>