IETF Logo Mail Archive

Re: [Netconf] Does ietf-yang-library support includes device/nms system or both?

Kent Watsen <kwatsen@juniper.net> Wed, 30 May 2018 18:50 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 7B93212E8CF for <netconf@ietfa.amsl.com>; Wed, 30 May 2018 11:50:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.711
X-Spam-Level:
X-Spam-Status: No, score=-0.711 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, 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 Bk_GoWzE5t5M for <netconf@ietfa.amsl.com>; Wed, 30 May 2018 11:50:21 -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 5C9A712E8A6 for <netconf@ietf.org>; Wed, 30 May 2018 11:50:21 -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 w4UInXvQ031949; Wed, 30 May 2018 11:50:09 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : subject : date : message-id : content-type : mime-version; s=PPS1017; bh=8xh0M/iiK7j+D0EVzwmaXHsKf9SlSPNA4540qp7hnDU=; b=vf9HoC8GAf4LOCLfkPwIuKtw7il2HspBXd7cbQvvPwOZ4vsktXbeq1oVlXDZetWCA9TL TE/0Kav12+NFTbkuu+SIMPzCY8X6sv3VqLsTZkiNIYFw9yjFFuMX8Q4DbEK5pW+Qy7Pp OrDSAkyVpPvCwu8klvNIrLRbFHwCxjE/4E+bYuREuAOgJIMhBS8ZkWIVX+DV6TmGCyEK npc4q7lR7QdEpectoOZYqSN9xXxdZWejbO9+TrTCelwB7PYg3I6dqwuKaMPkE7aCruIJ TNue0bm9pEugQ2cKgVxj7abcZ+ZBIVVFX9/j0NRohH7kizk1gk4kCnbRAN+9wIFHsQUR Ug==
Received: from nam03-dm3-obe.outbound.protection.outlook.com (mail-dm3nam03lp0019.outbound.protection.outlook.com [207.46.163.19]) by mx0a-00273201.pphosted.com with ESMTP id 2j9y0j093x-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 30 May 2018 11:50:08 -0700
Received: from BYAPR05MB4230.namprd05.prod.outlook.com (52.135.200.153) by BYAPR05MB4392.namprd05.prod.outlook.com (52.135.202.153) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.820.5; Wed, 30 May 2018 18:50:05 +0000
Received: from BYAPR05MB4230.namprd05.prod.outlook.com ([fe80::95f0:e564:96c8:7f1c]) by BYAPR05MB4230.namprd05.prod.outlook.com ([fe80::95f0:e564:96c8:7f1c%2]) with mapi id 15.20.0820.010; Wed, 30 May 2018 18:50:05 +0000
From: Kent Watsen <kwatsen@juniper.net>
To: MALLI KOSURI <VENKATAMALLIKARJUNARAO.KOSURI@adtran.com>, "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: [Netconf] Does ietf-yang-library support includes device/nms system or both?
Thread-Index: AQHT+EcGnoSBQv5czUev1/EaPZjH3Q==
Date: Wed, 30 May 2018 18:50:05 +0000
Message-ID: <CD174E68-C5E0-466A-B3E9-CDC2472D1ABC@juniper.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.12]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BYAPR05MB4392; 7:DWBTJyGOpxOG8D4dcZxgcCU2t7EkRxprb8Ggke6MimEfl7Jc+NuWuo+mfMCsvdgLc97xtKo7QNFnjXtp/EndP56lPH/NrQIBCE915DGDY24yH6NXURJtWSN3X5Yb2v5Il1QZkI8xEAWaJAjEqCYDwfT2bC8d4kaaE22L+3zl51v6EXA5i56A8iCLG/rkQsJmKy1i28R6bhi+FPancM5ZhxM9tHQbse21NPc3zm9I8oato71PfPB7IxF29ZZUDQdc
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(48565401081)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:BYAPR05MB4392;
x-ms-traffictypediagnostic: BYAPR05MB4392:
x-microsoft-antispam-prvs: <BYAPR05MB4392105A40A0E5BFEE0DF456A56C0@BYAPR05MB4392.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(158342451672863)(10436049006162)(21748063052155);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(93006095)(93001095)(3002001)(10201501046)(3231254)(944501410)(52105095)(6055026)(149027)(150027)(6041310)(20161123564045)(20161123558120)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(6072148)(201708071742011)(7699016); SRVR:BYAPR05MB4392; BCL:0; PCL:0; RULEID:; SRVR:BYAPR05MB4392;
x-forefront-prvs: 0688BF9B46
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39860400002)(366004)(396003)(39380400002)(376002)(346002)(199004)(189003)(486006)(58126008)(110136005)(99286004)(186003)(25786009)(229853002)(476003)(3846002)(6436002)(6116002)(2616005)(106356001)(2900100001)(36756003)(105586002)(54896002)(316002)(6512007)(26005)(6246003)(6506007)(102836004)(53936002)(236005)(6306002)(81166006)(81156014)(8936002)(8676002)(7736002)(68736007)(3280700002)(5660300001)(3660700001)(82746002)(478600001)(966005)(97736004)(14454004)(33656002)(5250100002)(66066001)(2501003)(606006)(86362001)(6486002)(9326002)(83716003)(2906002); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR05MB4392; 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: f7dTfDD2yQNmjJwqU+olrsLmOIdqnkCqOlecaGsqi7V6iz5UJ87juvkH0/YhTDAk0aKwBgqColKkPhYzsuLPbRMcewCoCa6cnE1RD82kcEmQJ+kOa8mPvob6UMnE7MdBc++T79dyFI4TBiveYJ8xslng91fVX1HEY3jcGhcePbM9dyF8lgY4bFz/7M7+pTp0
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_CD174E68C5E0466AB3E9CDC2472D1ABCjunipernet_"
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: 75cdab10-f74e-499f-f0de-08d5c65e28f6
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 75cdab10-f74e-499f-f0de-08d5c65e28f6
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 May 2018 18:50:05.8390 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR05MB4392
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-30_09:, , 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-1805220000 definitions=main-1805300200
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/TXqQW8zuhHbbFi1N2Si5nJAW6ls>
Subject: Re: [Netconf] Does ietf-yang-library support includes device/nms system or both?
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 30 May 2018 18:50:24 -0000

Hi Malli,

An NMS that presents a NETCONF or RESTCONF based northbound interface is effectively the "server" for those connections, while being the "client" for the connections to devices it manages via its southbound interface.

Kent


On 5/30/18, 2:42 PM, "Netconf on behalf of MALLI KOSURI" <netconf-bounces@ietf.org<mailto:netconf-bounces@ietf.org> on behalf of VENKATAMALLIKARJUNARAO.KOSURI@adtran.com<mailto:VENKATAMALLIKARJUNARAO.KOSURI@adtran.com>> wrote:


Hello,

As per RFC suggested a server advertises ietf-yang-libaray capabilities, does this applies both a Device or a NMS system implemented using YANG/YANG 1.1, is this true? Are there any exceptions included?

https://tools.ietf.org/html/rfc7950#section-1.1<https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_rfc7950-23section-2D1.1&d=DwMF-g&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=9zkP0xnJUvZGJ9EPoOH7Yhqn2gsBYaGTvjISlaJdcZo&m=FeAVwFzFO2xLx9qTCI9azj6ekyllcwiOP3hj1o8s2DI&s=2Jq8OKlIVEMeeWkVW-yc8b2cnXd0wtQxVKIezWSFR28&e=>


A server advertises support for YANG 1.1 modules by using

      ietf-yang-library [RFC7895<https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_rfc7895&d=DwMF-g&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=9zkP0xnJUvZGJ9EPoOH7Yhqn2gsBYaGTvjISlaJdcZo&m=FeAVwFzFO2xLx9qTCI9azj6ekyllcwiOP3hj1o8s2DI&s=fQQiWG3eaZLQJtmE27iDgv9hdo_56hGuEYsuRvh-W3Q&e=>] instead of listing them as

      capabilities in the <hello> message.


Thanks
Malli

This message has been classified General Business by MALLI KOSURI on 31 May 2018 at 00:11:58.

v2.46.0 | Report a Bug | By Email | System Status