Re: [Netconf] We NEED RESPONSES: WG Last Call ended for:draft-ietf-netconf-4741bis-04.txt

"Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com> Sun, 03 October 2010 19:32 UTC

Return-Path: <mehmet.ersue@nsn.com>
X-Original-To: netconf@core3.amsl.com
Delivered-To: netconf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3C1F23A6D5B for <netconf@core3.amsl.com>; Sun, 3 Oct 2010 12:32:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.372
X-Spam-Level:
X-Spam-Status: No, score=-102.372 tagged_above=-999 required=5 tests=[AWL=0.227, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FcTLmGg9dLXL for <netconf@core3.amsl.com>; Sun, 3 Oct 2010 12:32:25 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by core3.amsl.com (Postfix) with ESMTP id 7C4043A6C4E for <netconf@ietf.org>; Sun, 3 Oct 2010 12:32:25 -0700 (PDT)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id o93JX8rn025433 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 3 Oct 2010 21:33:08 +0200
Received: from demuexc024.nsn-intra.net (demuexc024.nsn-intra.net [10.159.32.11]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id o93JX7uh028095; Sun, 3 Oct 2010 21:33:08 +0200
Received: from DEMUEXC006.nsn-intra.net ([10.150.128.18]) by demuexc024.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675); Sun, 3 Oct 2010 21:33:07 +0200
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 03 Oct 2010 21:33:06 +0200
Message-ID: <80A0822C5E9A4440A5117C2F4CD36A640106533A@DEMUEXC006.nsn-intra.net>
In-Reply-To: <B11AB91666F22D498EEC66410EB3D3C4F412BEC4EA@HQ1-EXCH01.corp.brocade.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Netconf] We NEED RESPONSES: WG Last Call ended for:draft-ietf-netconf-4741bis-04.txt
Thread-Index: ActjH/vGqS0s6DivQVixsu9Yy6MyQgAA4YZgAANuyPA=
References: <CB69B162C87647AE97AB749466633F54@BertLaptop><4C9B3E60.5030000@bwijnen.net><80A0822C5E9A4440A5117C2F4CD36A640106532D@DEMUEXC006.nsn-intra.net> <20101003172455.GA16616@elstar.local> <B11AB91666F22D498EEC66410EB3D3C4F412BEC4EA@HQ1-EXCH01.corp.brocade.com>
From: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
To: ext Andy Bierman <biermana@Brocade.com>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
X-OriginalArrivalTime: 03 Oct 2010 19:33:07.0121 (UTC) FILETIME=[CE059210:01CB6331]
Cc: Netconf <netconf@ietf.org>
Subject: Re: [Netconf] We NEED RESPONSES: WG Last Call ended for:draft-ietf-netconf-4741bis-04.txt
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Network Configuration WG mailing list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sun, 03 Oct 2010 19:32:27 -0000

> I agree with Juergen that we should stick with client/server
> terminology.

This is also what I want. As this is the Terminology section
the description of client (server) could also contain the 
relation to other terms.
 
> Andy

Mehmet

> 
> -----Original Message-----
> From: netconf-bounces@ietf.org [mailto:netconf-bounces@ietf.org] On
> Behalf Of Juergen Schoenwaelder
> Sent: Sunday, October 03, 2010 10:25 AM
> To: Ersue, Mehmet (NSN - DE/Munich)
> Cc: Netconf
> Subject: Re: [Netconf] We NEED RESPONSES: WG Last Call ended
for:draft-
> ietf-netconf-4741bis-04.txt
> 
> On Sun, Oct 03, 2010 at 07:15:52PM +0200, Ersue, Mehmet (NSN -
> DE/Munich) wrote:
> > Section 1.1. Terminology
> >
> > I would suggest to bring the terms client/manager/
> > application vs. agent/server/device as early as
> > possible into relation. The document mainly avoids
> > the usage of the terms manager and agent though
> > there are some leftovers.
> >
> > OLD:
> >    client: A client invokes protocol operations on a server.
> > NEW:
> >    client: A client (manager, application) invokes
> >    protocol operations on a server (agent, device).
> >
> > OLD:
> >    server: A server executes protocol operations invoked by a
client.
> > NEW:
> >    server: A server (agent, device) executes protocol
> >    operations invoked by a client (manager, application).
> 
> I am against this change. The terminology is client and server; if
> there are any leftovers of other terms, we should remove them. There
> is a huge difference between a device and a NETCONF server, same for
> an application and a NETCONF client.
> 
> > Section 9. Security Considerations
> >
> > I would suggest to add a few sentences for the EOM handling
> > and the possible thread concerning section 3. It would be
> > interesting to recommend a possible reaction if this happens
> > frequently, e.g. to drop the NETCONF session.
> 
> 4741bis does not have an EOM marker - so how can we discuss it in
> the security considerations?
> 
> /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/>
> _______________________________________________
> Netconf mailing list
> Netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf