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

Kent Watsen <kwatsen@juniper.net> Fri, 06 July 2018 22:10 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 12FD2131062 for <netconf@ietfa.amsl.com>; Fri, 6 Jul 2018 15:10:34 -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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=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 4Be9NnOjSaY8 for <netconf@ietfa.amsl.com>; Fri, 6 Jul 2018 15:10: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 84E6913105D for <netconf@ietf.org>; Fri, 6 Jul 2018 15:10:31 -0700 (PDT)
Received: from pps.filterd (m0108162.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w66L3jgG017947; Fri, 6 Jul 2018 14:04:46 -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=Shje9673/4hpAmScZ7TcqKQw8CoxBfwyw6z2S9auX2g=; b=wKaQb09oHipqeTXBUSR6F9FkNFkYs6hkImYrGv2zyel788Fl5MfWNx/tVXyFwh26HJNH FyzXFi5aJDa/AgNU6KSvrL3V4o/jP+jKpdzcZ2eALJdnMp668khjQ+27yFSTbdvvFfHc Kw1HtlZl7/pUQ7umSYSA7973pSDIflgQzF3FctQWfkIrztWt1bSii9vwpCDk2YZ+1wxA EDQtmdJfjte9FcTr3y/MCEVkFPCrsNa+pFJNa0i2zMclLUcRrPslZWblfOIiZDxWBK35 NNN8jhegbf9PEi9NLB3c4Y2E3EqiPO/aEyVVokdaYsu7bQQITr+0hsMv+zjWRJEBwRlg gA==
Received: from nam03-by2-obe.outbound.protection.outlook.com (mail-by2nam03lp0053.outbound.protection.outlook.com [216.32.180.53]) by mx0b-00273201.pphosted.com with ESMTP id 2k2cex0dt7-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Fri, 06 Jul 2018 14:04:46 -0700
Received: from BYAPR05MB4230.namprd05.prod.outlook.com (52.135.200.153) by BYAPR05MB4134.namprd05.prod.outlook.com (52.135.199.155) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.930.17; Fri, 6 Jul 2018 21:04:43 +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.0952.008; Fri, 6 Jul 2018 21:04:43 +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/NICAAvaHAIAAYSmAgAEcWQA=
Date: Fri, 6 Jul 2018 21:04:42 +0000
Message-ID: <1D57D1E2-EC43-4512-BCBA-40F067AB537F@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> <BB246B62-0A79-4FAD-9C23-B5EC40AE394D@juniper.net> <a7d654fc37284449ba8c1306a9ce3146@XCH-RTP-013.cisco.com>
In-Reply-To: <a7d654fc37284449ba8c1306a9ce3146@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; BYAPR05MB4134; 7:oGzfr41xcsJjYkBEbOlmL1WKW4T++FSdXGMAmQjLcsoVAehkPXzylo1xm4v+hL89xhZgIsatsgcfHxGOwI0ZWJGYSsRudBqZRaNDi8SJxJ6U2Ek4+4Dqcq63Yh8Kdf6ia5QpZ+I5SEKCII6ShbzaPCtg4+b3a9nwXduw7iWMnnzzNoV4haarKhlXsDcs6p0H9CafsMUo+kJ/EKaPOZHIM62cY4aaiI+EoVIFQDY8hd5WN+n6q+LDL8vYmOgp9RAR
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 9f806133-e916-4d72-a1a9-08d5e38418b0
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989117)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(48565401081)(5600053)(711020)(2017052603328)(7153060)(7193020); SRVR:BYAPR05MB4134;
x-ms-traffictypediagnostic: BYAPR05MB4134:
x-microsoft-antispam-prvs: <BYAPR05MB41345DC1013087ADDA0D3BACA5470@BYAPR05MB4134.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(166708455590820);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(3231291)(944501410)(52105095)(93006095)(93001095)(3002001)(10201501046)(6055026)(149027)(150027)(6041310)(20161123558120)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(20161123560045)(20161123562045)(6072148)(201708071742011)(7699016); SRVR:BYAPR05MB4134; BCL:0; PCL:0; RULEID:; SRVR:BYAPR05MB4134;
x-forefront-prvs: 0725D9E8D0
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(366004)(376002)(136003)(346002)(39860400002)(199004)(189003)(4326008)(102836004)(2900100001)(6506007)(6916009)(6486002)(105586002)(305945005)(81166006)(86362001)(6436002)(106356001)(229853002)(2616005)(476003)(6512007)(81156014)(7736002)(76176011)(54906003)(316002)(11346002)(186003)(8676002)(14444005)(93886005)(256004)(6246003)(6306002)(8936002)(82746002)(14454004)(99286004)(966005)(58126008)(66066001)(3846002)(36756003)(6116002)(486006)(83716003)(15650500001)(446003)(68736007)(26005)(53936002)(2906002)(33656002)(25786009)(5250100002)(97736004)(5660300001)(478600001); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR05MB4134; 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: kvi0VsAdZQLQZgLBSvmww4M+8Q07cvd76HcmNTugHeqI67Bm3rFuWqpQBRCVyl5gjSXHcYcvs6erkye4ujWi1PeG4decXt3HwRT2a7UlZRxDzDO/5BUWBA3c6/1QUaERUGnd+Ley9HEiPmq8BNxBKA2pFQBtNZaAxDPgF9u5TfFPtgNMykVBBN6GX2g1i2pNrc/+GhntRD0d4PI5gavAWNu6kFRilQHQ713yzyPLNdui+LYCmyVjL2EVfNMQKfqOX28GfQMwIIWN9ZPf9crfn82CJ8KO9D72io3jk5w1E/McUDGGaclNKVdo/PV9zd9pOuFwlqzU6ODdFc7O4j8JKZbhM0rA6EPELxxKaDRE/8E=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <7701AB7DB85D6F4BB6B88CFCA757AAEA@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 9f806133-e916-4d72-a1a9-08d5e38418b0
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Jul 2018 21:04:43.0629 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR05MB4134
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-07-06_06:, , 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-1807060237
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/j7Ax_BU238bpL0IQypAXvqWJHCk>
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: Fri, 06 Jul 2018 22:10:34 -0000

<Kent14>

<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?  
 
<Eric14>  Here is a link to the slides which I have put together for IETF 102 which hopefully hits your request above:
 
https://github.com/netconf-wg/rfc5277bis/blob/master/draft-configured-replay-slides-ietf102.pdf  
 
 
<Kent14> not really.  The switch to "configured-replay" seems orthogonal, likely due to it being perceived as easier than specifying an exact time.  Separately, as a comment on the slides, perhaps list both Pros and Cons?  I provided 4 perceived benefits in a recent email…




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?  
 
<Eric14>  replay-start-time exists as part of the establish-subscription RPC.   The RPC is where the triggering occurs.

<Kent14> right, and that's fine, but it's not okay for configured subscriptions.   Subscription-policy uses subscription-policy-dynamic, the description needs to be refined, like it was for the subscription-started notification.


Kent // contributer