IETF Logo Mail Archive

Re: [Netconf] IETF 101 SN Question 1: Proper designation of receiver

Kent Watsen <kwatsen@juniper.net> Thu, 05 July 2018 21:04 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 0BC12130F80 for <netconf@ietfa.amsl.com>; Thu, 5 Jul 2018 14:04:15 -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 EpthkGyqBMrX for <netconf@ietfa.amsl.com>; Thu, 5 Jul 2018 14:04:12 -0700 (PDT)
Received: from mx0b-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 C18CE130F7C for <netconf@ietf.org>; Thu, 5 Jul 2018 14:04:12 -0700 (PDT)
Received: from pps.filterd (m0108157.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w65L3jM3022010; Thu, 5 Jul 2018 14:04:11 -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=x0tNJSSiNxqRCZPnz8D5i1qSTEL5oDLUYhbn6Q6LQ6Q=; b=KYHnVedTi3ngJ9VnLIlGDODO4yELx3tV7VjoRr5ViENrkispMtw/ThVjXfrKVHPqk9bp S74tB6yJIunM6IsHTfPnOv4xDUM6V7PdFSe3wcr5LNDghlh527pdzeGb/7mZqg1mWlgG O+V3/QJyYrYpoyXwDGK7/b9QLhDwiqMROruGJF1soZst6Brbn4co0W+pNOn2tXrEeqIa uq4k6C7Q0pqU1vZtjk1cwNj3jQCRu6AUrQbi00Yn4CqQ3LWprhXjG5yHXnlRU891ucdO bTskM9iifLq2JQUqfuDZ+nCMNw3aKl3RGLH2MaTl2+4eX8gRMeenmB2h+Si1UpsC20t2 7w==
Received: from nam04-sn1-obe.outbound.protection.outlook.com (mail-sn1nam04lp0087.outbound.protection.outlook.com [216.32.180.87]) by mx0a-00273201.pphosted.com with ESMTP id 2k1pwbghmm-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 05 Jul 2018 14:04:10 -0700
Received: from BYAPR05MB4230.namprd05.prod.outlook.com (52.135.200.153) by BYAPR05MB4056.namprd05.prod.outlook.com (52.135.199.33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.930.17; Thu, 5 Jul 2018 21:04:08 +0000
Received: from BYAPR05MB4230.namprd05.prod.outlook.com ([fe80::959d:9fbe:90e4:3cc]) by BYAPR05MB4230.namprd05.prod.outlook.com ([fe80::959d:9fbe:90e4:3cc%4]) with mapi id 15.20.0930.016; Thu, 5 Jul 2018 21:04:08 +0000
From: Kent Watsen <kwatsen@juniper.net>
To: "Eric Voit (evoit)" <evoit@cisco.com>
CC: "netconf@ietf.org" <netconf@ietf.org>, Martin Bjorklund <mbj@tail-f.com>
Thread-Topic: [Netconf] IETF 101 SN Question 1: Proper designation of receiver
Thread-Index: AQHT7qXx6AR0hwD/VEqFVDxs31zp6aQ1kroAgAAEGoCAAA8IgIAAYuSAgCWiwACAAZ7SAIAK57IAgAEbxgD//+unAIAAbY0AgAEjt4CAAFpqAIABijQAgABnB4CABEKyAIAAYEAAgAGXzICAAGAlAIACiM+AgADqEoCABwS9AIAC/jeA
Date: Thu, 05 Jul 2018 21:04:07 +0000
Message-ID: <3F268B34-FD60-44FB-871E-6A4B403E3CF1@juniper.net>
References: <BD5235E8-596A-40A8-ACDE-3AD947E6D8D9@juniper.net> <89a99290a9ff4addb3d8c537aae89dbf@XCH-RTP-013.cisco.com> <F251AA08-A5FE-4219-BCDC-FAC2F988FE10@juniper.net> <20180629.101057.1590202307624767148.mbj@tail-f.com> <e72d66e05f774908ab15000947b27d66@XCH-RTP-013.cisco.com>
In-Reply-To: <e72d66e05f774908ab15000947b27d66@XCH-RTP-013.cisco.com>
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.11]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BYAPR05MB4056; 7:jKxPBiqS8FCXwwXEzh5qWwVvEoqX3SZZJAeLs0fA7ZIWpFelh1VchxwckqWlDzf70+qFTMqlBTqCwBfUeKsP2dtZCQN+OGVCt2030RuNBGuaOb81xOou7ShTjNwVuJyXjwJgwXAFZs2kVwF3G8DrwSqUevXjYLYqt4j01c196yLLvDWT/80EdDbxY/y7+4Yo+UuN9qD4r9V9c3UJ1OdQRVFe4Fmt+YIZS+u2k+68dnqnxQhTjFOHoLanuYShTRqD
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: f1ecf5a1-7cfd-4020-ade7-08d5e2bad948
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989117)(5600053)(711020)(48565401081)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(2017052603328)(7153060)(7193020); SRVR:BYAPR05MB4056;
x-ms-traffictypediagnostic: BYAPR05MB4056:
x-microsoft-antispam-prvs: <BYAPR05MB40565D25605B0E5F360C62A6A5400@BYAPR05MB4056.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(158342451672863);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(93006095)(93001095)(10201501046)(3002001)(3231254)(944501410)(52105095)(6055026)(149027)(150027)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123562045)(20161123560045)(20161123564045)(20161123558120)(6072148)(201708071742011)(7699016); SRVR:BYAPR05MB4056; BCL:0; PCL:0; RULEID:; SRVR:BYAPR05MB4056;
x-forefront-prvs: 0724FCD4CD
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(366004)(396003)(136003)(346002)(39860400002)(199004)(189003)(316002)(7736002)(66066001)(6306002)(229853002)(6436002)(6512007)(53936002)(68736007)(6116002)(6486002)(5250100002)(82746002)(5660300001)(3846002)(83716003)(2900100001)(966005)(36756003)(25786009)(4326008)(14454004)(6916009)(305945005)(6246003)(2906002)(186003)(478600001)(81166006)(8936002)(8676002)(81156014)(2616005)(476003)(105586002)(97736004)(11346002)(102836004)(26005)(86362001)(106356001)(33656002)(256004)(446003)(6506007)(93886005)(99286004)(54906003)(58126008)(486006)(76176011); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR05MB4056; H:BYAPR05MB4230.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-microsoft-antispam-message-info: nN6yj4U88Olzj1CNB9O6MLWGklyW8qZoMXP8WKd/jJlmz0qnf1/bYNSlNNPJ7roUXa2t1RnyES02K65jlFNEFOBzYnIou3WU/xFDAcXthcOlTCruFzoRMLNaFCNanD2V20I/xApBAH8CcIpAeLFeQeAefNUYIPBVnS4OI93jFgo4nibu2rzxE1KFpU5g7c3453qJKDInoon1iJ6kLPg7ZIO97BwDKm3n7PQgFoOHceFwp3wnZdAuihpxuDn9+yNUXDVxIfZWV+6OzgdHo1ByVfFO8fwk2AqfYsNqwWV1R6pEdLfY4+DWCoQsG3Fcsxt7ZxcEoFJ0G4+xYgApoN2U32zALcpZ+mGseKg4rPq42Ig=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <F1FF16BF4132834D8350ED14331EA796@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: f1ecf5a1-7cfd-4020-ade7-08d5e2bad948
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Jul 2018 21:04:07.8645 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR05MB4056
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-07-05_08:, , 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=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1806210000 definitions=main-1807050232
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/VKCNyjHMcFRJ_sNakFcRIozZCx0>
Subject: Re: [Netconf] IETF 101 SN Question 1: Proper designation of receiver
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.26
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: Thu, 05 Jul 2018 21:04:16 -0000


>>> What this means is, for servers that only want to support
>>> NETCONF-based dynamic subscriptions (no configured subscriptions),
>>> then the ietf-netconf-subscribed-notifications module can be listed in
>>> yang-library as *not implemented*.
>>
>> No, since the server must implement the rpcs, the module must be
>> listed as "implemented" (the feature "configured" would not be 
>> advertised though).

I wrote here [1] that the RPCs are in SN (not netconf-notif), so I
don't believe that Martin's assertion doesn't hold here.

[1] https://mailarchive.ietf.org/arch/msg/netconf/ggG-HpWZ7gf56WAOPucKzCj8QHY


> Beyond this, even for dynamic subscriptions, the module is needed
> for per-subscription operational counters.

Can you help me with this?  I see the config false nodes in the SN
draft, but none of them relate to the identity (which I still have
an issue with) defined in the NN draft...

Thanks,
Kent

v2.23.0 | Report a Bug | By Email