IETF Logo Mail Archive

Re: [Netconf] YangPush now

"Tim Jenkins (timjenki)" <timjenki@cisco.com> Tue, 17 July 2018 20:50 UTC

Return-Path: <timjenki@cisco.com>
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 6706B13104C for <netconf@ietfa.amsl.com>; Tue, 17 Jul 2018 13:50:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 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_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 27hfHamAClAS for <netconf@ietfa.amsl.com>; Tue, 17 Jul 2018 13:50:25 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8495013105F for <netconf@ietf.org>; Tue, 17 Jul 2018 13:50:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3716; q=dns/txt; s=iport; t=1531860607; x=1533070207; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=INW4n3NbAKYIJhSvo7nkExaG6WGIcIdioA6jGaRtLO4=; b=Oqhi5h4i5uSFZgmJdwelfTVKFBU4jzwHD7PkBlGNsChMw9hodOu7NlSw Kg6gCM06itOiV4Vir0sEj0O8iiCU2W/NRqhraS5fdHcW3T4+l3dtJG9AK Cdxg3W0mVVpvainMZgOYLAUjAqkEvcDFKhuyreN6CPF/x4eUqBJu/sGsw 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D+AgBcVU5b/4QNJK1ZAxkBAQEBAQEBAQEBAQEHAQEBAQGDHypjfygKg3OIBIw9ggyDOJIBgXoLGA0HhEACF4JZITQYAQIBAQIBAQJtHAyFNgEBAQECASMRGhgTDgICAQgOAggCAggBHQICAhkWARUQAgQOAQQBGgIEgjRLAYF3CA+rGoEuhFuFTAWBBod3gVc/gREngmqDDgsBAQEBAQEWgTAWFwomgjqCVQKZXAkChgiJHYFDhBGCbYUkijmHNAIRFIEkHTiBUnAVZQGCPgkKghIXg0UzhGGFPm8BAQ6BBYpiAYEZAQE
X-IronPort-AV: E=Sophos;i="5.51,367,1526342400"; d="scan'208";a="428397838"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 17 Jul 2018 20:50:06 +0000
Received: from XCH-RTP-012.cisco.com (xch-rtp-012.cisco.com [64.101.220.152]) by alln-core-10.cisco.com (8.15.2/8.15.2) with ESMTPS id w6HKo6jQ027027 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 17 Jul 2018 20:50:06 GMT
Received: from xch-rtp-011.cisco.com (64.101.220.151) by XCH-RTP-012.cisco.com (64.101.220.152) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Tue, 17 Jul 2018 16:50:05 -0400
Received: from xch-rtp-011.cisco.com ([64.101.220.151]) by XCH-RTP-011.cisco.com ([64.101.220.151]) with mapi id 15.00.1320.000; Tue, 17 Jul 2018 16:50:05 -0400
From: "Tim Jenkins (timjenki)" <timjenki@cisco.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
CC: "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: [Netconf] YangPush now
Thread-Index: AQHUHVo97/1MCRrcckGjuypYd3RC86STLH0AgAA6yQCAAIYGAP//1s0AgABOBgD//9KlAA==
Date: Tue, 17 Jul 2018 20:50:05 +0000
Message-ID: <3F966B11-1ADB-43A8-A611-097306519474@cisco.com>
References: <2E1BAD12-EFF2-4E35-B232-57A4C4490989@cisco.com> <20180717055030.7bmzlychtznf3mso@anna.jacobs.jacobs-university.de> <18622ABD-DB9F-406C-836F-64649F3D8FF6@cisco.com> <20180717172036.hhuoq6fzs7ctblpf@anna.jacobs.jacobs-university.de> <1DDEF716-343F-4DF9-AE2C-CBC7B6E0DBD1@cisco.com> <20180717193224.acctssedwfatgcl5@anna.jacobs.jacobs-university.de>
In-Reply-To: <20180717193224.acctssedwfatgcl5@anna.jacobs.jacobs-university.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [161.44.212.117]
Content-Type: text/plain; charset="utf-8"
Content-ID: <3DBD52D74AA1814082F4694D6C5B30EA@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/lMOH-STajpioSbUSXS6MCeCVpms>
Subject: Re: [Netconf] YangPush now
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.27
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, 17 Jul 2018 20:50:35 -0000


-- 
Cisco Systems Canada Co.
2000 Innovation Drive
Kanata, ON, Canada, K2K 3E8
Preferences <http://www.cisco.com/offer/subscribe/?sid=000478326>
Unsubscribe <http://www.cisco.com/offer/unsubscribe/?sid=000478327>
Privacy <http://www.cisco.com/web/siteassets/legal/privacy.html>



On 2018-07-17, 3:33 PM, "Juergen Schoenwaelder" <j.schoenwaelder@jacobs-university.de> wrote:

    On Tue, Jul 17, 2018 at 06:53:08PM +0000, Tim Jenkins (timjenki) wrote:
    > Please see embedded, with prefix [Tim]. Note some editing of the original to separate the questions.
    > 
    > 
    > On 2018-07-17, 1:21 PM, "Juergen Schoenwaelder" <j.schoenwaelder@jacobs-university.de> wrote:
    > 
    >     I see several pieces but I do not see how the pieces give me a
    >     workable solution nor do I see how such a solution gives me
    >     interoperability.
    > 
    > [Tim] Even with your questions below, it's still not clear to me what would be missing. 
    >     
    >     If I configure a subscription, how does the flow of notifications work
    >     over NC and RC?
    > 
    > [Tim] NETCONF message flows are described in draft-ietf-netconf-subscribed-notifications, Appendix A.3.   RESTCONF is not in WGLC yet, but can be seen at draft-ietf-netconf-restconf-notif, Appendix B.2
    
    There is no A.3 in draft-ietf-netconf-subscribed-notifications. Perhaps
    you mean draft-ietf-netconf-netconf-event-notifications-10. No, this
    example does not help me understand how notification messages flow. It
    only shows how I create a configured subscription.
[Tim2] Correction to what I put above: https://datatracker.ietf.org/doc/html/draft-ietf-netconf-netconf-event-notifications#appendix-A.3.1 
     
    >     How do I configure where the connection goes?
    > 
    > [Tim] Since we don't implement netconf-server.yang, we do vendor specific stuff to link each receiver to our local call home/dial-out configuration.  There are lots of moving parts here, and we don't expect interoperability for quite a while.  This lack of interoperability is not a result of these subscription drafts though, so waiting for or making a model dependency to pending IETF work in this space will only make things more confusing and add further unnecessary delay to the process.
    
    So you agree that the solution is incomplete.
[Tim2] Please re-read what I wrote. At no point did I say "the solution" is incomplete.

...    
    -- 
    Juergen Schoenwaelder           Jacobs University Bremen gGmbH
    Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
    Fax:   +49 421 200 3103         <https://www.jacobs-university.de/>

v2.23.0 | Report a Bug | By Email