IETF Logo Mail Archive

Re: [Netconf] Fwd: Regarding complete device configuration sync to NMS

Shiva Kumar Pathori <pathori@gmail.com> Sat, 05 September 2015 14:05 UTC

Return-Path: <pathori@gmail.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 178A91B581D; Sat, 5 Sep 2015 07:05:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 6Loec2g6805w; Sat, 5 Sep 2015 07:05:47 -0700 (PDT)
Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA7121B57F9; Sat, 5 Sep 2015 07:04:41 -0700 (PDT)
Received: by oixx17 with SMTP id x17so25572208oix.0; Sat, 05 Sep 2015 07:04:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=SyqXndNEoTk4uF7WMKQtXIR4rJY2/diQvZRBeLJanqE=; b=bTJO/zq9JOHbJHtr2TWsXEVjVjNk6Mxs5mShRwbCgKUyrrsM9tWcGjG6mnNEFP9QMN kxJcBsWFj/hA5pLNommp9W6lLe+aIX9EapcTTJBPyb8wfSqNhtJdnOcxZ7jpkKYyTQ7M y0gnXcFzZgqWTIRcbCrEF1gtdrMp4Wqf2to3Fn/39i12QOj3OwU9lfTWy2q42VPXJJ2J wneEy1oohMZFW5GW4w2hZO1piMpp5Kq6jFpjiC2CjgriymHlaQ5UGC0sBO66mxb5g7dR 5ntWWSqQGeFP+QETEYAfaMGGkcyjpKaq6VqzXCP1GL3lqZTo/XapDZuykkc3GFCS/BtZ +pYg==
MIME-Version: 1.0
X-Received: by 10.202.200.79 with SMTP id y76mr7438104oif.5.1441461881124; Sat, 05 Sep 2015 07:04:41 -0700 (PDT)
Received: by 10.60.46.97 with HTTP; Sat, 5 Sep 2015 07:04:40 -0700 (PDT)
Received: by 10.60.46.97 with HTTP; Sat, 5 Sep 2015 07:04:40 -0700 (PDT)
In-Reply-To: <20150904072319.GA32036@elstar.local>
References: <CABCOCHQE4zGcrLKyb0XEEbBVGbHLAr8LJVFnRzCm1_Xap4MTkQ@mail.gmail.com> <20150903171049.GA30863@elstar.local> <CABCOCHTeSxEVmJ5ZqMohJXb4LFO4J=WiMgH=yMu5QuTt8oqVUg@mail.gmail.com> <20150903.215033.1871297355299522194.mbj@tail-f.com> <CAJtYN8KfBb1OyXvCXO6+Rej+vKx+QA7vQQQXzjSo5mW9E=rtDw@mail.gmail.com> <CAJtYN8LMLZ0N4F9BBcL-UMzpr0YpC9JunjDfq_PT7hkxONNjaA@mail.gmail.com> <CABCOCHS0P2AugRTSB31Gzr3q_ymSWfvnYJzfn0kx9n5MJW-XEA@mail.gmail.com> <20150904072319.GA32036@elstar.local>
Date: Sat, 05 Sep 2015 19:34:40 +0530
Message-ID: <CAJtYN8KTb0wQAt8GdHKzUYFKviXcpmAZnrDkoU67DSF_bt8C2g@mail.gmail.com>
From: Shiva Kumar Pathori <pathori@gmail.com>
To: netconf@ietf.org, Andy Bierman <andy@yumaworks.com>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, netconf-request@ietf.org
Content-Type: multipart/alternative; boundary="001a1134fe1a61be6c051f007f01"
Archived-At: <http://mailarchive.ietf.org/arch/msg/netconf/BC49K708whnewufgJLOXJE--63Q>
Subject: Re: [Netconf] Fwd: Regarding complete device configuration sync to NMS
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.15
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: Sat, 05 Sep 2015 14:05:52 -0000

  This method is similar to the draft
https://datatracker.ietf.org/doc/draft-liu-netconf-multiple-replies/?include_text=1.
Where as Client has to send multiple get-block RPC to get the complete
data. In this method all such replies will be put in multiple files and
zipped. This will reduce the RPC message interaction between client and
server.
On Thu, Sep 03, 2015 at 07:10:46PM -0700, Andy Bierman wrote:
> On Thu, Sep 3, 2015 at 6:43 PM, Shiva Kumar Pathori <pathori@gmail.com>
> wrote:
>
> > I mean the zip file in fact contains proper <rpc-reply> with multiple
> > files. Each file is of one complete XML document.
> >
>
>
> The <rpc-reply> is an XML instance document.
> Why would there be multiple "files" in response to 1 <get> or
<get-config>?
>
> I suggest you implement this and report the memory usage compared to
> streaming
> buffer-at-a-time with SSH, and also compare the number of bytes on the
wire
> for each approach.
>

+1

/js

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

v2.23.0 | Report a Bug | By Email