Re: [Netconf] the name "checksum" in YANG library
Kent Watsen <kwatsen@juniper.net> Fri, 12 October 2018 17:52 UTC
Return-Path: <kwatsen@juniper.net>
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 E72CB130E5B for <netconf@ietfa.amsl.com>; Fri, 12 Oct 2018 10:52:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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=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 IGhc1FWig8RO for <netconf@ietfa.amsl.com>; Fri, 12 Oct 2018 10:52:51 -0700 (PDT)
Received: from mx0b-00273201.pphosted.com (mx0b-00273201.pphosted.com [67.231.152.164]) (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 34096130E5F for <netconf@ietf.org>; Fri, 12 Oct 2018 10:52:51 -0700 (PDT)
Received: from pps.filterd (m0108161.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w9CHiGMr000722; Fri, 12 Oct 2018 10:52:46 -0700
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=x1170wJnCs3UvVDjypkIPo2VwjVqrcwB+aesrpAHiBw=; b=nFfY8qMR2hbTKmR3w1b00bbhKUgdXJ5wT1voA8QAirtWO8rx7STU/oUue744yryzzzFB RS06Z1pMMu0UXhOzg7E9fMXDzN04Mn0v+zEcoINm1sGEZptInVq2WHR1iG88lV0lpSLR gyAiogFbwYpAyGAoKiPBJFvO9QZK8Y0GfQsstb5dP+vQDwzxPVvPr7mK84V/k8nHyLXZ teuch5myTeoeNwbvANiYSaVEAINEsR4zVNpdBb/2Um9yMYTJG9o0OXVsg0f+qcs2u9KF C5Sk0sSjxmIM70XfL1WMusz4xOH3nLceIBlp+LRcQQoPh5ikPtGNP15SP4QEiqnmkYIG Ew==
Received: from nam03-by2-obe.outbound.protection.outlook.com (mail-by2nam03lp0055.outbound.protection.outlook.com [216.32.180.55]) by mx0b-00273201.pphosted.com with ESMTP id 2n2psm0xju-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 12 Oct 2018 10:52:46 -0700
Received: from DM6PR05MB4665.namprd05.prod.outlook.com (20.176.109.202) by DM6PR05MB5307.namprd05.prod.outlook.com (20.176.119.144) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1228.19; Fri, 12 Oct 2018 17:52:43 +0000
Received: from DM6PR05MB4665.namprd05.prod.outlook.com ([fe80::8574:3388:660d:e495]) by DM6PR05MB4665.namprd05.prod.outlook.com ([fe80::8574:3388:660d:e495%5]) with mapi id 15.20.1228.020; Fri, 12 Oct 2018 17:52:43 +0000
From: Kent Watsen <kwatsen@juniper.net>
To: Vladimir Vassilev <vladimir@transpacket.com>, Rohit R Ranade <rohitrranade@huawei.com>, Martin Bjorklund <mbj@tail-f.com>
CC: "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: [Netconf] the name "checksum" in YANG library
Thread-Index: AQHUYU+gQlSnM0ybVE6jc0V6RRgWEqUZ5cCAgAADdYCAATWZgIAAUw0AgAAxUAA=
Date: Fri, 12 Oct 2018 17:52:43 +0000
Message-ID: <46A50778-6BC2-408B-BE9C-E15BAD49C075@juniper.net>
References: <20181011.124600.2085483972062437440.mbj@tail-f.com> <991B70D8B4112A4699D5C00DDBBF878A6BC567C6@dggeml510-mbx.china.huawei.com> <20181011.133113.643945777606446073.mbj@tail-f.com> <991B70D8B4112A4699D5C00DDBBF878A6BC57080@dggeml510-mbx.china.huawei.com> <819ba6e3-89f4-63c4-35a5-c54172cc70cd@transpacket.com>
In-Reply-To: <819ba6e3-89f4-63c4-35a5-c54172cc70cd@transpacket.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.10.2.180910
x-originating-ip: [66.129.241.13]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DM6PR05MB5307; 6:VaHIwLQ/S5A501ZwfYegqHQ4iKT2aMZMmmd3wau+nCxiDSTDCYauiiHVzajNMEGCg66O22fki33BfjAqZ5eXucNWoOBBKNBKiKZFY4nWuWkoGDep5zvTqZfSYtcEw6qcPyHD/10imoKNsBb8SXSf7kQC4qjjc3ObbVfrL2Gx8aTy08Yf7ggXQlqC++UKDaChxaq2yPlYcAFh5SZrVd0SpHzQa0b0PAGI+aKjqx4VWM9kWqlnLCBhw70NZ++6nRFB868gbB7jUyPPVtawveS2NQWhgj357ghah3eslKCdnKxUmp8GbTv4MLhnJmztvf02xe5WDLUYWLw2h5V+vNdLO9biynPb43VyPPXPsXcWAVOG4EQt4Bq9Amtnn8lnZ74w+/1gKs3RrfHvf9WSuEZBzllwHCftmY29zSQ8mj3JnPh/khW0IR6bOsVKUSlZn+wZ938i8B81obL+beoCvMScXQ==; 5:wXcEuwYDPboiwUvTmQOuXmGXF7/3FZp23d1WkggLu8nHAwNM9ZhMu+pEHkkEnbUfMT64g1QBpklqNepQdI3BGV8Uw2TutEePswCfgZe/sbTv5y5+Mu8PYMn24ca0BiGkdNtyX6GsVDmren0oezB9ouEtV2cMkQ42fI5AMwu4xL4=; 7:96d3WwutYYliS6n9zCLo+nXgY7ECm48RN7X6RX14rQWkrcHgnh/ekgHR2gmS/8OVW5SSk84cO7CMnykkpdO0UheBHTwRn7996fdXwvvcmOgXowiaDFcoTB8rT3aJ5lUddYKk+dsknNhDfilM1OKc5J0oafQAiIZrZR4pmvXnpX/4hR0sbGVGhvES7rFaIA4hV2zYi9G+jUj+7HX6iaBXQvd2iiq+ZIo7sbb1V910LhDUQSRcDpQw7HTV2E3+Xnux
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 06c69e8b-7243-4888-9f6a-08d6306b830f
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(4618075)(2017052603328)(7153060)(7193020); SRVR:DM6PR05MB5307;
x-ms-traffictypediagnostic: DM6PR05MB5307:
x-microsoft-antispam-prvs: <DM6PR05MB530785A579065BABF4606D13A5E20@DM6PR05MB5307.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(10436049006162)(50582790962513);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(93006095)(93001095)(10201501046)(3231355)(944501410)(4982022)(52105095)(3002001)(6055026)(149066)(150057)(6041310)(20161123558120)(20161123564045)(20161123560045)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(201708071742011)(7699051)(76991067); SRVR:DM6PR05MB5307; BCL:0; PCL:0; RULEID:; SRVR:DM6PR05MB5307;
x-forefront-prvs: 0823A5777B
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39860400002)(136003)(376002)(366004)(346002)(396003)(13464003)(189003)(199004)(2900100001)(25786009)(6512007)(6436002)(106356001)(33656002)(105586002)(6306002)(305945005)(5660300001)(36756003)(7736002)(229853002)(53546011)(6506007)(99286004)(97736004)(76176011)(102836004)(5250100002)(6346003)(6486002)(71190400001)(14444005)(83716004)(256004)(71200400001)(82746002)(486006)(2616005)(3846002)(26005)(446003)(6116002)(476003)(4326008)(68736007)(186003)(58126008)(11346002)(316002)(110136005)(6246003)(966005)(93886005)(81156014)(81166006)(14454004)(478600001)(8676002)(2906002)(53936002)(8936002)(86362001)(575784001)(66066001); DIR:OUT; SFP:1102; SCL:1; SRVR:DM6PR05MB5307; H:DM6PR05MB4665.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-microsoft-antispam-message-info: SLIr8VmoxDv/GBs+AWOY6EF+FLaz28L93vQtWMCXB63U/YH8flYWUQaVBJ5fB/fxUjWWgo8j+6uGEZRCj5dABXzUho881A6JPnJnZkkHXAHb5Eg5uun/qsWFc0skiMWrr9v55TDoEhMQKfW3Mps+LxNn4fKVkbJ/u7HzMNPQYVPclo9IGGyZY5hAQn4VutwJNesq4w7G0UlH4FSPnucfdgbY47fQbtSANMZOcZvdXHINvbQfBIo7RfVRrPJRokyx0vwSDwsVPjmLyjZPDWfjwhIB8i8TvJ32YFUL1d6KC8QFIhCZ9FmvJ1XHx+w2ZkyMyM4RgGUex9fpferQEyJagjisizgoisqzEphvGliNLgA=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <B40D01E2F8059A49AA91C546EC7BAC7B@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 06c69e8b-7243-4888-9f6a-08d6306b830f
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Oct 2018 17:52:43.7476 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR05MB5307
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-10-12_13:, , 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 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1810120172
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/YPNzZDPwdYUIv1kTwUXUuLR2PF0>
Subject: Re: [Netconf] the name "checksum" in YANG library
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 12 Oct 2018 17:52:54 -0000
We should not try to ensure that two servers having the same response return the same value. That would require the definition of a canonical form that we don't have. We should (IMO) align the checksum value with HTTP Entity-Tag (ETag) [1] and, in particular, using a strong validator [2]. RESTCONF says that ETag SHOULD be available for each resource [3], including {+restconf}/ds/ietf-datastores:operational/ietf-yang-library:yang-library. I know that we don't have to conflate these two things, but it makes sense to do so. PS: just realized that nmda-restconf didn't update [4]. This might be a problem. [1] https://tools.ietf.org/html/rfc7232#section-2.3 [2] https://tools.ietf.org/html/rfc7232#section-2.1 [3] https://tools.ietf.org/html/rfc8040#section-3.5.2 [4] https://tools.ietf.org/html/rfc8040#section-3.4.1.2 Kent // contributor -----Original Message----- From: Netconf <netconf-bounces@ietf.org> on behalf of Vladimir Vassilev <vladimir@transpacket.com> Date: Friday, October 12, 2018 at 6:56 AM To: Rohit R Ranade <rohitrranade@huawei.com>, Martin Bjorklund <mbj@tail-f.com> Cc: "netconf@ietf.org" <netconf@ietf.org> Subject: Re: [Netconf] the name "checksum" in YANG library Hi, On 10/12/18 7:59 AM, Rohit R Ranade wrote: > Hi Martin, > > " The value of this leaf MUST change whenever the > information in the YANG library changes." ==> This statement in Section 3, indicates that the value must change when content changes. > > The draft has also placed a constraint that it is a " unique implementation-specific identifier". When the contents changes, especially if the length of the data which is used for checksum changes, then the resulting checksum values may not be unique. > > So I feel it is simpler, if a counter is used. There is this usecase where a client can compare the checksum against already retrieved checksum or a list of checksums and know that it is connected to a device with schema it was designed to work with or not, or has already retrieved the yang library contents and compiled and cached the schema in case of smarter client etc. I do not think replacing this information with the information how many times the schema has changed (since the last restart?, has it changed and returned back to the same state?) can serve the same purpose as the checksum even if the checksum is calculated with implementation dependent algorithm. That said it is clear that the presented usecase is dependent on what the vendor chose to implement as "checksum" algorithm. How probable it is that two different yang libraries generate identical checksums etc. Vladimir > > With Regards, > Rohit _______________________________________________ Netconf mailing list Netconf@ietf.org https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_netconf&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=9zkP0xnJUvZGJ9EPoOH7Yhqn2gsBYaGTvjISlaJdcZo&m=QwcIVKILbN6JGJBCGujvoCFYDuKfhlWPRNXIUv76Wt0&s=FtBu4_qYCzP67ExA8TL8cw1qhrLD6goeVAQMgbOvFTg&e=
- [Netconf] the name "checksum" in YANG library Martin Bjorklund
- Re: [Netconf] the name "checksum" in YANG library Rohit R Ranade
- Re: [Netconf] the name "checksum" in YANG library Martin Bjorklund
- Re: [Netconf] the name "checksum" in YANG library Rohit R Ranade
- Re: [Netconf] the name "checksum" in YANG library Vladimir Vassilev
- Re: [Netconf] the name "checksum" in YANG library Robert Wilton
- Re: [Netconf] the name "checksum" in YANG library Juergen Schoenwaelder
- Re: [Netconf] the name "checksum" in YANG library Rohit R Ranade
- Re: [Netconf] the name "checksum" in YANG library Robert Wilton
- Re: [Netconf] the name "checksum" in YANG library Kent Watsen
- Re: [Netconf] the name "checksum" in YANG library Vladimir Vassilev
- Re: [Netconf] the name "checksum" in YANG library Rohit R Ranade