IETF Logo Mail Archive

Re: [Netconf] comments on draft-ietf-netconf-subscribed-notifications-12

Kent Watsen <kwatsen@juniper.net> Tue, 19 June 2018 21:58 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 CA252130F6F for <netconf@ietfa.amsl.com>; Tue, 19 Jun 2018 14:58:31 -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=unavailable 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 C_GarNeMCrMh for <netconf@ietfa.amsl.com>; Tue, 19 Jun 2018 14:58:31 -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 0D68A130F55 for <netconf@ietf.org>; Tue, 19 Jun 2018 14:58:30 -0700 (PDT)
Received: from pps.filterd (m0108160.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w5JLsQ4t003706; Tue, 19 Jun 2018 14:58:24 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=PPS1017; bh=MXaKLrGnKoGYb1jwow77tnG42F4Eyja02IM5+ZwWNt8=; b=xX/WsiqH9QAo0x7d8hqeJD+fVYesYvRez9SjXyZ9c6k6PFXjckVmfEWRYqcxG1dg0JwG s6oMLDyQM9iY4oAmoiS5/aFLKPHRfvcuj2MAXeIniL8dGmiRU7KQ0m0TJqxU7ZNjWOHT M2Ya8OglEr75UrQzKlOdM55wDj6xJHqDQP5ncTOBkDqeS4+fjctiirTZhgOuygTIe3Mx mFBY73Ryp1jRzBgbEnzHLJhHAabrVvyU494LAKqbR5A7n/lfnSq5kh5C7Sq5Yn1rjcrt kXuZmJ0v+Bjg2Gkf0jKSsIb0EAdl2iB49LLOjggA9fVMzDbwczScmigHVee6Gwy92fUk Qw==
Received: from nam04-bn3-obe.outbound.protection.outlook.com (mail-bn3nam04lp0118.outbound.protection.outlook.com [216.32.180.118]) by mx0b-00273201.pphosted.com with ESMTP id 2jq7q088p6-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 19 Jun 2018 14:58:24 -0700
Received: from BYAPR05MB4230.namprd05.prod.outlook.com (52.135.200.153) by BYAPR05MB4711.namprd05.prod.outlook.com (52.135.233.89) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.884.15; Tue, 19 Jun 2018 21:58:22 +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.0884.010; Tue, 19 Jun 2018 21:58:22 +0000
From: Kent Watsen <kwatsen@juniper.net>
To: "Eric Voit (evoit)" <evoit=40cisco.com@dmarc.ietf.org>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, "alexander.clemm@huawei.com" <alexander.clemm@huawei.com>, "alex@clemm.org" <alex@clemm.org>, "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: [Netconf] comments on draft-ietf-netconf-subscribed-notifications-12
Thread-Index: AQHT/nS/MUcivqD/HU6aN67dia0Z6aRVWncAgAC3XYCAAEcpAIAAEmGAgAAJoYCABnBmAIAAR1+A///RU4CAAFI2AIAAfEqAgACO9oCAAAdJAIABEdsAgACV3YCAABa6gIAAxcaAgABilgCABqeqgA==
Date: Tue, 19 Jun 2018 21:58:22 +0000
Message-ID: <A0ECF1FF-FF88-4BE3-A722-D681B9CF6F78@juniper.net>
References: <20180613160206.gkutjhxigdxpv2uz@anna.jacobs.jacobs-university.de> <20180614.102216.2199378020340361225.mbj@tail-f.com> <f6f66d0c0a444f2bb0fc770082450037@XCH-RTP-013.cisco.com> <20180614.203959.786029239464099510.mbj@tail-f.com> <20180615062751.obzdeco6oka3ekue@anna.jacobs.jacobs-university.de> <ac1a7a7480da46d4841fcd1bd0ea4ddc@XCH-RTP-013.cisco.com>
In-Reply-To: <ac1a7a7480da46d4841fcd1bd0ea4ddc@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.14]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BYAPR05MB4711; 7:NmghCDqnlgYVqb/8va8w61/C2URFc5jPS22bjqB5pyemni0nNzw7PJzhfRBpGBV57vomcDReayOpz5BH3DNq7JC8MafyOSfWHr0pE8VRstTOdmSGCkZNZ5I6S5M8t3dqbyTe9PkgOpKjWNgQCDkZ2XnzaUPgmXSb97xf37oy6eWPPt4jRTLsNkxCI8eBt72fxEaLt1v0EgW+/SvOb5TZaka9OWCpLfqO17SFoQKn4pbM5cF0OFI043lsgoGh+e5h
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 416e7c40-0e66-4ae7-e9e4-08d5d62fc698
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(4534165)(4627221)(201703031133081)(201702281549075)(5600026)(711020)(48565401081)(2017052603328)(7153060)(7193020); SRVR:BYAPR05MB4711;
x-ms-traffictypediagnostic: BYAPR05MB4711:
x-microsoft-antispam-prvs: <BYAPR05MB47110F8AA947B8963B98753EA5700@BYAPR05MB4711.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(10201501046)(3002001)(3231254)(944501410)(52105095)(93006095)(93001095)(6055026)(149027)(150027)(6041310)(20161123560045)(20161123562045)(20161123558120)(20161123564045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6072148)(201708071742011)(7699016); SRVR:BYAPR05MB4711; BCL:0; PCL:0; RULEID:; SRVR:BYAPR05MB4711;
x-forefront-prvs: 07083FF734
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39380400002)(39860400002)(396003)(346002)(366004)(376002)(189003)(199004)(51444003)(5660300001)(99286004)(93886005)(11346002)(33656002)(476003)(2616005)(106356001)(102836004)(3846002)(105586002)(316002)(110136005)(26005)(6506007)(58126008)(486006)(446003)(186003)(82746002)(59450400001)(6512007)(76176011)(305945005)(6436002)(6246003)(6116002)(25786009)(478600001)(8676002)(6486002)(7736002)(14454004)(2900100001)(8936002)(81156014)(81166006)(68736007)(229853002)(83716003)(5250100002)(36756003)(2501003)(53936002)(3280700002)(3660700001)(2906002)(15650500001)(97736004)(66066001)(86362001)(2201001); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR05MB4711; H:BYAPR05MB4230.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: wDzAPy+aFm9RURzExMjNu8r0uChL7+Yn/b80tiOD7xGutbmlaLuUhCkHwJwa8qPWqDi3EdhliSlGDsLrDYZa1vQQLynNDO5K36YJo1QiGNdKejegYiulHNGQ5MuaHrDLvwgNSngA6ZDfBwcmBmf4bVrl+/RMT9Rpv7jJUKo0yLI3wB7EQpJPd/RZY+oQEgRX1y8NbyTHNNR3hM9wpXIKKAcgsb2Q6/VW4+hun+/h7a6lIcPL7coadrRAUZGVFZ6CwGzqK1R/O0cGfn9AAWZZnf/2a1QW4IPvSzWyCWxDCPriGACdEBuJjgaPfGABrxIg
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <2B654E041831734787BB50468A4DA325@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 416e7c40-0e66-4ae7-e9e4-08d5d62fc698
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Jun 2018 21:58:22.5389 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR05MB4711
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-06-19_11:, , 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-1806190235
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/Gybz8SemzWG55v_OWAAmDpEUoGc>
Subject: Re: [Netconf] comments on draft-ietf-netconf-subscribed-notifications-12
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: Tue, 19 Jun 2018 21:58:32 -0000


> > > > An event record is not necessarily a YANG notification, as the event
> > > > record's payload might not be driven by the result of a YANG
> > > > statement.
> > >
> > > I don't get this.  Can you give an example of when an event record is
> > > not defined as a YANG "notification"?
> > 
> > Why do we care about non-YANG-defined notification messages? How are
> > systems expected to interoperate on such opaque data blobs?
>
> Opaque data blobs is what RFC-5277 can carry.  The WG asked to update 
> RFC-5277 using the improved control plane of YANG-Push.  This is what
> makes up the documents in LC.   
>
> <snip/>
>
> The drafts in LC adds RPC / signaling mechanisms.  The opaque data blobs are not in scope.

RFC 5277 may have allowed opaque data blocks, but I think that we should 
try to bury that support now.  Can this document say that all notifications
MUST be defined by a YANG-defined "notification" statement?  Could this
break in compatibility be advertised somehow?


> It would be helpful to get some comments on draft-ietf-netconf-notification-messages.
> This draft address improvements to the opaque data blobs.

Perhaps tease us with a little more detail?  ;)


Kent

v2.23.0 | Report a Bug | By Email