Re: [Netconf] LC on subscribed-notifications-10

Kent Watsen <kwatsen@juniper.net> Thu, 05 July 2018 22:19 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 BB53D130ED0 for <netconf@ietfa.amsl.com>; Thu, 5 Jul 2018 15:19:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, 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 0xJXHkyM60uy for <netconf@ietfa.amsl.com>; Thu, 5 Jul 2018 15:19:37 -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 AA5E312777C for <netconf@ietf.org>; Thu, 5 Jul 2018 15:19:37 -0700 (PDT)
Received: from pps.filterd (m0108159.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w65MJYGL004405; Thu, 5 Jul 2018 15:19:34 -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 : mime-version; s=PPS1017; bh=saeP82ttU5XPnMFCb+dSfIjzPunpTYLM+bK69i2LqaE=; b=wKUc2FFM/xH4SxASYVYZgUcD058vYokngkFIT0ZC/xR+t6LqPMLwNEgBnzrLDFzr2WgU CefmeLP/Rq8tRRLV/pcflTOig8pkkxA+mRKwo1yamuyemmjo2knkPfeSCRcR3tVKhWPG 9msQXn+wNnudNVP8TT0/cdWnb2Zf6cSNcpu9cL0VmeXmRqEoUzn8En+twBH3ajpoccyU iV80vbMX55eEWTZVZjOKbfGGVhRjlNEPfr6nu+KSrsGnMr71iG9o4YZMw1K+YZ9COTox ZqYQqfzn0NlNHyMk4gStjDOoOgETjwimBGwEpEhO+PykVpkfabqaIrfRVhLV7kT+KFNB Tw==
Received: from nam05-co1-obe.outbound.protection.outlook.com (mail-co1nam05lp0086.outbound.protection.outlook.com [216.32.181.86]) by mx0a-00273201.pphosted.com with ESMTP id 2k1sc4g8aq-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 05 Jul 2018 15:19:34 -0700
Received: from BYAPR05MB4230.namprd05.prod.outlook.com (52.135.200.153) by BYAPR05MB4469.namprd05.prod.outlook.com (52.135.203.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.952.7; Thu, 5 Jul 2018 22:19:15 +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 22:19:15 +0000
From: Kent Watsen <kwatsen@juniper.net>
To: "Eric Voit (evoit)" <evoit@cisco.com>
CC: "netconf@ietf.org" <netconf@ietf.org>, Alexander Clemm <ludwig@clemm.org>
Thread-Topic: [Netconf] LC on subscribed-notifications-10
Thread-Index: AQHTvAAnlMdwSaUGiEGsguuFvEIgr6PTNMYAgAKRSACAHsEbAIAEpeaAgAxV1oCAAIbkgIAIxKuAgAHWLYCAAWPcgIABfIqAgBLPcYCAAfAGAIAHv+mAgAFNpYCADOOSAIABWNGAgArMEgCAAKtggIASeyqAgAHUMQCADcgmAIAA1tCAgAPW54CAAFbTgIAECbMAgAh/NICAAvaHAA==
Date: Thu, 5 Jul 2018 22:19:15 +0000
Message-ID: <BB246B62-0A79-4FAD-9C23-B5EC40AE394D@juniper.net>
References: <17B884BF-0BB8-4B7C-BFBB-0AAFBEA857F6@juniper.net> <aedeb7390d0b4faa9f2bf12c2fe45cd2@XCH-RTP-013.cisco.com> <040a01d3be9f$09700490$1c500db0$@clemm.org> <2089023D-DA09-48E9-8F37-8FE459DC4F49@juniper.net> <dfc78f2b1062498388824b1f6dd97ff6@XCH-RTP-013.cisco.com> <1EC2E732-C524-4552-A3AD-27507239F763@juniper.net> <2b788c22f7ee4af889813b805348d69a@XCH-RTP-013.cisco.com> <9E7F3A66-98B9-4528-882C-43AAD19F0AEC@juniper.net> <96615f0331cd455182901ddf3e6ece23@XCH-RTP-013.cisco.com> <7F8F2AF4-28A5-4016-B727-10CAF6A093AF@juniper.net> <87fbe3cb907a473f816295c4545bd7fa@XCH-RTP-013.cisco.com> <CEE5B81C-31AE-40C6-B2F0-23D93C644D85@juniper.net> <fd172bddff134db6aeda49b7e8bfd3e9@XCH-RTP-013.cisco.com> <B112DC20-D6FC-44BA-AACE-0E641D49C5C3@juniper.net> <3b4744f4e2144ee18b9bfd5225360bf4@XCH-RTP-013.cisco.com> <01486F5E-CEE3-4BDD-9CD2-CA2754981000@juniper.net> <e414fe96c38f4aeba97dd56592748a23@XCH-RTP-013.cisco.com> <49943A03-D229-4084-9947-3065CE58A672@juniper.net> <a18cacd026e046b0a0c08f7a3fc969d2@XCH-RTP-013.cisco.com> <470391DD-9A9E-47EC-9CEC-E8E6BABE3DDF@juniper.net> <b94935c9fbbb4ced8b7393ea42457471@XCH-RTP-013.cisco.com> <38DB151D-81C9-49E4-B6A3-73D083298C53@juniper.net> <fd74cc7419894fec87f5af3e7dc688bd@XCH-RTP-013.cisco.com> <230D4B7A-42E6-4A9E-909B-BE91EE5D2FF3@juniper.net> <bc1b705b88f04d368334b78fbe91b7dd@XCH-RTP-013.cisco.com> <4146A91F-42E3-4C81-A414-C27920CA30C0@juniper.net> <9721a7a06f9543a1b510988b087da6b3@XCH-RTP-013.cisco.com>
In-Reply-To: <9721a7a06f9543a1b510988b087da6b3@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; BYAPR05MB4469; 7:rU316C1fsDLBi1kKG6KcedNP8t+knDSz0iKXfIc+pdKtUTYyGvS0qqW1BihrPCABceLcj7ikbkn0j79KbDj/FdZM8+HWeID4KqwA78RIQ4GZ/oIdIsjWORfXaOiUCos2vjE9/se/zHVlT6uD4nnCjdblgowyC/6tvya/MQApoF5cuueiUicPrI0d36bguYt6bG68+oNVuLj8f+FrCptxrivtRx1CMI1PjMUcsLTZBZLjpGnhis8l5NMM+tAXFTEe
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 4c02cfc5-ac85-4504-afd8-08d5e2c55837
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:BYAPR05MB4469;
x-ms-traffictypediagnostic: BYAPR05MB4469:
x-microsoft-antispam-prvs: <BYAPR05MB44698188C4A25202A24831DAA5400@BYAPR05MB4469.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(21748063052155);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(10201501046)(3002001)(93006095)(93001095)(3231282)(944501410)(52105095)(6055026)(149027)(150027)(6041310)(20161123558120)(20161123564045)(20161123562045)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6072148)(201708071742011)(7699016); SRVR:BYAPR05MB4469; BCL:0; PCL:0; RULEID:; SRVR:BYAPR05MB4469;
x-forefront-prvs: 0724FCD4CD
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(136003)(396003)(39860400002)(376002)(346002)(199004)(189003)(6306002)(82746002)(6512007)(6116002)(2906002)(3846002)(81156014)(7736002)(81166006)(6486002)(5660300001)(8936002)(54896002)(8676002)(97736004)(66066001)(229853002)(2900100001)(33656002)(68736007)(6916009)(6436002)(561944003)(476003)(486006)(102836004)(478600001)(93886005)(316002)(14454004)(186003)(83716003)(446003)(2616005)(11346002)(6246003)(256004)(4326008)(99286004)(54906003)(58126008)(6506007)(106356001)(76176011)(86362001)(5250100002)(53936002)(36756003)(26005)(105586002)(25786009); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR05MB4469; 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: L3YoxrbOkoMLV3FgNJW7Tq6a5kImhb2mniArUEl3MIgfdEDnD1SiafFMkLL/1dJeXz+dfgvo9t31ZeyzX0xyZqG1YlG3zduT1bbsC0fc07WXdO8rVSfsVBfCZzGbOzrDU7mcte6nK1FDRBBD/hhqEcsCNvg0Fxmf4Haep7e3qCkK6doFTS5jO0TOrngYzQrnqW+LP/54PMECgJHx5BX/bMAG2xmoAzvZJtnJ6EjEJic79OxVvM+pJwKcFEKmrBziP39+InOTurmfKFrz8HGcq/qUKSGIkUGHpR0l58MOmZc1gX62qgoTfvKUUsGhaneyAC/DCttz/XFGNApLYF+ySD4cm4xxPcsYqM7MRYvshWk=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_BB246B620A794FAD9C23B5EC40AE394Djunipernet_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 4c02cfc5-ac85-4504-afd8-08d5e2c55837
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Jul 2018 22:19:15.7691 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR05MB4469
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-1807050245
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/DcJYQ3VYVRjHxblkOS2krjBMWFQ>
Subject: Re: [Netconf] LC on subscribed-notifications-10
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 22:19:50 -0000

<Kent13>


<Kent9> it might be typical/common desire, but it's still once in the lifetime of the configured subscription.  It seems like, if the device supports dynamic subscriptions, after receiving subscription-started, the client could a) pause the configured subscription, b) use a dynamic subscript to fetch the missing logs, and then c) resume the flow of logs from the configured subscriptions.



<Eric10> Your proposal still precludes (b)-(d) above.   In addition for your step a), there is no RPC or action which allows the event records from a configured (or dynamic) subscription to be paused.  The solution also adds complexity into the client to recognize that early events might be missing, to issue an establish-subscription, and then to tie the results of the independent subscriptions together.



<Kent10> pausing can be implemented by the receiver not reading any more from the TCP socket, or something else.



<Eric11> There is no mechanism for a receiver to pause a single subscription without pausing other subscriptions on the TCP session (as subscriptions typically would share a common TCP.)



<Kent11> Different "receivers" of different configured subscriptions pointing to the same underlying netconf or restconf call-home connection?



<Eric12> Yes



<Kent12> Ack.  So, *if* we were to do this, the client would either have to pause all the subscriptions, or do a dynamic fetch in parallel.  Hmmm, given that we're talking about the *configured* replay-start-time, which kicks in after a reboot, all the subscriptions would be restarted simultaneously (right?), so maybe this isn't a big issue?



<Eric13> Per this thread, this is now a configured-replay empty object (rather than a start-time).  This empty object simply tells the publisher to push off all events retained from a stream since reboot.  And yes, all configured subscriptions will restart simultaneously.  But without this feature, receivers will not see events from boot to transport establishment.  And without this feature, two different configured receivers might get different initial events as the transport might not be brought up simultaneously.



<Kent13> I'm unsure how this addresses my concern that replaying is unnecessary for configured subscriptions…I somehow thought that it might be related since it's listed here.   Separately, I'm unclear about what this change does, I know you provide some explanation above, but you can say it differently or provide an example or two to illustrate what you mean?   Does this change introduce the problem you mentioned before about duplicates events being sent?  BTW, the description statement on replay-start-time seems incorrect, with the node now being config false, how can it be used to "trigger" anything?





Kent // contributer