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

Kent Watsen <kwatsen@juniper.net> Fri, 29 June 2018 14:38 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 74AB712D949 for <netconf@ietfa.amsl.com>; Fri, 29 Jun 2018 07:38:26 -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 QbS8K_J8dAyx for <netconf@ietfa.amsl.com>; Fri, 29 Jun 2018 07:38:24 -0700 (PDT)
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 075BB130E1C for <netconf@ietf.org>; Fri, 29 Jun 2018 07:38:24 -0700 (PDT)
Received: from pps.filterd (m0108158.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w5TDnHoM009494; Fri, 29 Jun 2018 06:58:59 -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=hvq7CpkyjVMOoEJwfVnusWxsqAXhRvVtSKM57HrVBCg=; b=cTkzHY+wSWpvhkJ7xXhMbllv69gXS0/ls2eAPDDpxWaSk25W9nvlY7pwZXFA47yGo8jv sqReiP2YWjD3yFujkbs5e8/PEt0LAJXbVU0M0UXRSNk+icvJkFL+KFKJtQXmTIzWzz9o QQ3SRrL+9YwMCurLdbvVBWSZ4NC7+kIbEIPMmPGfEuxqKUnbV9QeYs62qsUjWyrRo1MB Dm94jN8TkrvNPwR/lvwUjZAp9JOs/f31sMQ8P99yVRcdfzy8FJs88KPVt6a55ds0+eh/ /vzQQu2b2Yx+9LKtIew2cvGoOO2mkx4p8cmUokk5gDxyGYeJ39Qh/oihNoutkRD718Tx /g==
Received: from nam04-bn3-obe.outbound.protection.outlook.com (mail-bn3nam04lp0113.outbound.protection.outlook.com [216.32.180.113]) by mx0a-00273201.pphosted.com with ESMTP id 2jwnugg0vd-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Fri, 29 Jun 2018 06:58:59 -0700
Received: from BYAPR05MB4230.namprd05.prod.outlook.com (52.135.200.153) by BYAPR05MB4359.namprd05.prod.outlook.com (52.135.202.140) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.930.10; Fri, 29 Jun 2018 13:58:56 +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.0906.018; Fri, 29 Jun 2018 13:58:56 +0000
From: Kent Watsen <kwatsen@juniper.net>
To: Martin Bjorklund <mbj@tail-f.com>
CC: "evoit@cisco.com" <evoit@cisco.com>, "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: [Netconf] IETF 101 SN Question 1: Proper designation of receiver
Thread-Index: AQHT7qXx6AR0hwD/VEqFVDxs31zp6aQ1kroAgAAEGoCAAA8IgIAAYuSAgCWiwACAAZ7SAIAK57IAgAEbxgD//+unAIAAbY0AgAEjt4CAAFpqAIABijQAgABnB4CABEKyAIAAYEAAgAGXzICAAGAlAIACiM+AgADqEoCAAB4rAA==
Date: Fri, 29 Jun 2018 13:58:56 +0000
Message-ID: <3B877486-7E9E-490B-8EA8-3E8715033C32@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>
In-Reply-To: <20180629.101057.1590202307624767148.mbj@tail-f.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.10]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BYAPR05MB4359; 7:A+S150HUGemivxDE8V52+rAthR83awKT2hMvbsnGcl+5pMcQYF8xYWAoiSP3K2sF1UxidsaKJ3XerzT/T3Qn7LBdA23F3uBy6pNkdwC60MMn6RaU3vHf5c2uBv5rteEJiYtCnX4enprtc99AiX7w9AeaJgrS4+/UMJG3FDIZNE8dZ1veRXVw6TYGZP5Y54QSJijljcKg+E6lV4zPvURML8GRszLm3V+KIZ35d1HE9IJx2UWGyG3XSLc/9zxQT1oc
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: dfa9b0ba-e331-4384-2fa0-08d5ddc874d9
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989117)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(5600026)(711020)(48565401081)(2017052603328)(7153060)(7193020); SRVR:BYAPR05MB4359;
x-ms-traffictypediagnostic: BYAPR05MB4359:
x-microsoft-antispam-prvs: <BYAPR05MB4359D0BE77838015931FF1B5A54E0@BYAPR05MB4359.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)(5005006)(8121501046)(3231254)(944501410)(52105095)(93006095)(93001095)(10201501046)(3002001)(6055026)(149027)(150027)(6041310)(20161123562045)(20161123558120)(20161123564045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(6072148)(201708071742011)(7699016); SRVR:BYAPR05MB4359; BCL:0; PCL:0; RULEID:; SRVR:BYAPR05MB4359;
x-forefront-prvs: 0718908305
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(376002)(346002)(366004)(136003)(39860400002)(189003)(199004)(229853002)(446003)(11346002)(105586002)(106356001)(486006)(316002)(2906002)(5660300001)(2900100001)(2616005)(476003)(186003)(93886005)(256004)(6506007)(53936002)(3846002)(6116002)(33656002)(36756003)(6436002)(14454004)(82746002)(6512007)(8676002)(81156014)(81166006)(66066001)(478600001)(54906003)(4326008)(58126008)(86362001)(8936002)(6486002)(68736007)(99286004)(305945005)(76176011)(83716003)(5250100002)(6916009)(25786009)(7736002)(102836004)(97736004)(26005)(6246003); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR05MB4359; H:BYAPR05MB4230.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:3; A:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-microsoft-antispam-message-info: PDasXMphWbMvCjXpRWDdf9nBWlRN8DTXmVR+hdXtT24yaYxVUnMIR/UAWczAXXqZSjIk/rbfN/YaEIDy7RxLb9BBoDPxPcnE/34dwyqR0QndDbv+ZQS8y88VHvrUQdTzycA+p3QM6za2wjAYhh34dlNB17gHL2ee1rF4i3NqJlDz5kjwWnxFPhXnMODWFcafpsFsHggV2yBChgikqwvOanQiu6Qnp30YBoD/+nwGGWVuHde47RE4QlLkzSFKvtjaacc1k8VhmnKTDGtgUEpt4EUrTzWqB5BI1qigeLrFjGn7j0ehJ3ypMI0kRRpxwAAfYIAGUD0pLiItB8LPZX47t/Ph82Ec/pFPGy+vGnS9tBs=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <3985FE8C6EDDFD43B632218BDFC3DF37@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: dfa9b0ba-e331-4384-2fa0-08d5ddc874d9
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Jun 2018 13:58:56.5210 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR05MB4359
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-06-29_05:, , 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=715 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1806210000 definitions=main-1806290149
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/ggG-HpWZ7gf56WAOPucKzCj8QHY>
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: Fri, 29 Jun 2018 14:38:27 -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).


The rpcs are in ietf-subscribed-notifications, from the SN draft.  

* For servers that only support dynamic subscriptions:

  - ietf-subscribed-notifications:
      - implemented, but "configured" feature not supported

  - ietf-netconf-subscribed-notifications:
      - listed in yang-library as not implemented


* For servers that support both, both modules are implemented, and
  the "configured" feature is supported.


* For servers that only support configured subscriptions.  
  If this pans out, then I assume:

  - ietf-subscribed-notifications:
      - implemented, but "dynamic" feature not supported
        (note: this entails adding new feature "dynamic")

  - ietf-netconf-subscribed-notifications:
      - implemented




> /martin

Kent