Re: [netmod] Adoption poll for draft-wu-netmod-factory-default-02

tom petch <ietfc@btconnect.com> Fri, 10 May 2019 10:50 UTC

Return-Path: <ietfc@btconnect.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 9EF22120072 for <netmod@ietfa.amsl.com>; Fri, 10 May 2019 03:50:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.248
X-Spam-Level:
X-Spam-Status: No, score=0.248 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RATWARE_MS_HASH=2.148, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.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 bIQDInBiT8PT for <netmod@ietfa.amsl.com>; Fri, 10 May 2019 03:50:49 -0700 (PDT)
Received: from EUR04-VI1-obe.outbound.protection.outlook.com (mail-eopbgr80094.outbound.protection.outlook.com [40.107.8.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3611B120026 for <netmod@ietf.org>; Fri, 10 May 2019 03:50:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=tDEViCWLcaIqnvsMQZx7aXlyIG5XpBDYMIjPc9puk+U=; b=iqF1ybHM02rO6yKGJ1jN5C9V7jxNe2TEoGEGYU3eZEzYS0Jh1QzzBakKsLHmhTSjT/4pHDEiiPwp21wAk2SfQv2tWasptNsQ0e0p29B3jkAkMgpfA9H90j/ODs3RgEXPDARfFJxKj2kH4t1uMK/oQ8x75utD2fnhrXKBvkAhHdk=
Received: from VI1PR07MB3118.eurprd07.prod.outlook.com (10.175.242.156) by VI1PR07MB4192.eurprd07.prod.outlook.com (20.176.6.29) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1900.7; Fri, 10 May 2019 10:50:46 +0000
Received: from VI1PR07MB3118.eurprd07.prod.outlook.com ([fe80::41a4:68a9:d620:d42b]) by VI1PR07MB3118.eurprd07.prod.outlook.com ([fe80::41a4:68a9:d620:d42b%3]) with mapi id 15.20.1900.006; Fri, 10 May 2019 10:50:46 +0000
From: tom petch <ietfc@btconnect.com>
To: "Joe Clarke (jclarke)" <jclarke@cisco.com>
CC: Qin Wu <bill.wu@huawei.com>, "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: [netmod] Adoption poll for draft-wu-netmod-factory-default-02
Thread-Index: AQHVBZGYZ1YLmj+D6UqmZXjpVYKlQw==
Date: Fri, 10 May 2019 10:50:46 +0000
Message-ID: <02b901d5071d$b61d09a0$4001a8c0@gateway.2wire.net>
References: <B8F9A780D330094D99AF023C5877DABAA4909DE4@nkgeml513-mbx.china.huawei.com> <EB363D33-307A-48E7-B886-08395356BA86@cisco.com> <065d01d50591$173d7c80$4001a8c0@gateway.2wire.net> <64FF5C9D-8BA4-4E36-92AA-EECD8B3BE035@cisco.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: LO2P265CA0029.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:61::17) To VI1PR07MB3118.eurprd07.prod.outlook.com (2603:10a6:802:20::28)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ietfc@btconnect.com;
x-ms-exchange-messagesentrepresentingtype: 1
x-mailer: Microsoft Outlook Express 6.00.2800.1106
x-originating-ip: [86.139.215.234]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 7216f800-1b5c-4009-8f07-08d6d5355b4a
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(2017052603328)(7193020); SRVR:VI1PR07MB4192;
x-ms-traffictypediagnostic: VI1PR07MB4192:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <VI1PR07MB419245B8AE57B79A6FF69895A00C0@VI1PR07MB4192.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0033AAD26D
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(39860400002)(346002)(136003)(376002)(396003)(13464003)(199004)(189003)(52314003)(6436002)(6486002)(446003)(14496001)(14454004)(7736002)(66066001)(71200400001)(81686011)(81816011)(229853002)(44736005)(66446008)(64756008)(66556008)(66476007)(316002)(73956011)(66946007)(71190400001)(256004)(14444005)(1556002)(76176011)(5660300002)(25786009)(486006)(86362001)(476003)(478600001)(44716002)(186003)(62236002)(66574012)(26005)(50226002)(386003)(6506007)(8936002)(53546011)(99286004)(8676002)(81166006)(81156014)(966005)(305945005)(86152003)(61296003)(6916009)(102836004)(6246003)(84392002)(3846002)(52116002)(68736007)(6116002)(6306002)(53936002)(4720700003)(6512007)(9686003)(4326008)(2906002)(54906003)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:VI1PR07MB4192; H:VI1PR07MB3118.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:0; MX:1;
received-spf: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: MSSbcd19NzKlzXQWNbOoDlFKR/v4/fsGGhjJt8sTV5VyAIKfLz3UxCUp6jRDNoKGMk9bGWHrYM5U47RU/fQtTQh0ekKXjQnbqkoePD/883gfu8tamaByiQcQNPnSvraZmhcyguUsuklUns64fc62QO0RatWAbGf6FeoF13CEQupizHWpax0M87OubTuPfJ52ChIf9pGkXiWq5hKm/gyPN4vIF08M2KOoKGy49898Ue0sKs4cFB1mVaZPV6XRSrnSLKbnp/WrauegUl40ZH34aYge3uMSMN5UHbbS09/q+SBYNllBPK7TZqA0iap51TjPL7ZLAVuEr5avry4ZXxCmF15aKMCpqm4qFnfo03DDEf3mei6Ko2BV+nbieNFlPs+gnHHKgWcK/plb8uyPds+C7gaCGi4sE/dJdaHcCa1Bfiw=
Content-Type: text/plain; charset="utf-8"
Content-ID: <C3B78A658DE44C4B9C4E30C8E01AF7DB@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 7216f800-1b5c-4009-8f07-08d6d5355b4a
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 May 2019 10:50:46.2978 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB4192
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/G1o4UP8b9suWvAcfj2xrA4aBAe0>
Subject: Re: [netmod] Adoption poll for draft-wu-netmod-factory-default-02
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: Fri, 10 May 2019 10:50:52 -0000

----- Original Message -----
From: "Joe Clarke (jclarke)" <jclarke@cisco.com>;
Sent: Thursday, May 09, 2019 3:28 PM

>
> > On May 8, 2019, at 07:31, tom petch <ietfc@btconnect.com>; wrote:
> >
> > ----- Original Message -----
> > From: "Joe Clarke (jclarke)" <jclarke@cisco.com>;
> > Sent: Monday, May 06, 2019 4:11 PM
> >>
> >> On May 6, 2019, at 08:06, Qin Wu
> > <bill.wu@huawei.com<mailto:bill.wu@huawei.com>> wrote:
> >>
> >> Hi, Chairs:
> >> Sorry for late follow up, thanks Jurgen, Andy,Joe, Joel and all
others
> > for good comments, here is the update based on discussion and
suggestion
> > on the mailing list
> >> The diff is:
> >>
https://www.ietf.org/rfcdiff?url2=draft-wu-netmod-factory-default-03
> >>
> >> Hey, Qin.  I read through the changes, and I have a couple of
> > additional comments.
> >>
> >> First, the term “YANG server” sounds odd to me.  I know what you
mean,
> > but I haven’t seen this defined before.  Maybe just saying a device
or
> > host is sufficient?
> >
> > Joe
> >
> > If you look at the various RFC - YANG, Netconf, NMDA - they all
define
> > the terms 'client' and 'server'; in the context, 'YANG server' seems
> > appropriate.
>
> It was the combination of the two words as “YANG server” which throws
me.  You’re serving data modeled using YANG.  Anyway, it sounds like
there’s a good referential solution to this from Jürgen and Martin, so
that should sort this out.

Joe,

yes, I can see what you mean.  I was objecting to the use of 'host',
'device' or such like having just read
draft-dai-quic-netconf-00.txt
which wants to reserve client and server for the transport and go to
manager and agent for netconf.

We have been down this road before, with SNMP and NETCONF, and the
confusion it creates is considerable.  If authors cannot cope with
well-established terminology, then they should not be writing I-Ds - if
that I-D comes up for adoption in its present form, I will resolutely
oppose, all the way to IETF Last Call.

</rant>

Tom Petch

> Joe
>
>