[OPS-NM] Re: Comments Question about draft-xu-cops-push-00.txt

Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de> Thu, 15 March 2007 14:46 UTC

Return-path: <ops-nm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRrE2-0003tl-1R; Thu, 15 Mar 2007 10:46:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRrE1-0003qy-6s; Thu, 15 Mar 2007 10:46:41 -0400
Received: from hermes.iu-bremen.de ([212.201.44.23]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HRrDz-0002sc-OJ; Thu, 15 Mar 2007 10:46:41 -0400
Received: from localhost (demetrius.iu-bremen.de [212.201.44.32]) by hermes.iu-bremen.de (Postfix) with ESMTP id DAADE6DE29; Thu, 15 Mar 2007 15:46:36 +0100 (CET)
Received: from hermes.iu-bremen.de ([212.201.44.23]) by localhost (demetrius.iu-bremen.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id 14450-05; Thu, 15 Mar 2007 15:46:33 +0100 (CET)
Received: from elstar.iuhb02.iu-bremen.de (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.iu-bremen.de (Postfix) with ESMTP id 8F5A96DAA3; Thu, 15 Mar 2007 15:46:32 +0100 (CET)
Received: by elstar.iuhb02.iu-bremen.de (Postfix, from userid 501) id 6DC3D1DCC0E; Thu, 15 Mar 2007 15:46:31 +0100 (CET)
Date: Thu, 15 Mar 2007 15:46:31 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: xuheyuan <xuheyuan@mail.ritt.com.cn>
Message-ID: <20070315144631.GB17038@elstar.iuhb02.iu-bremen.de>
Mail-Followup-To: xuheyuan <xuheyuan@mail.ritt.com.cn>, Tom-PT Taylor <taylor@nortel.com>, "Romascanu, Dan (Dan)" <dromasca@avaya.com>, ops-nm@ietf.org, dongsun@alcatel-lucent.com, Hexian Huang <huanghexian@mail.ritt.com.cn>, nmrg@ibr.cs.tu-bs.de, ops-area@ietf.org, Tina Tsou <tena@huawei.com>
References: <AAB4B3D3CF0F454F98272CBE187FDE2F0C7A797F@is0004avexu1.global.avaya.com> <45F70371.4010500@nortel.com> <20070315072441.GC15768@elstar.iuhb02.iu-bremen.de> <004c01c7670c$eb8a8220$eb29fea9@xuheyuan>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <004c01c7670c$eb8a8220$eb29fea9@xuheyuan>
User-Agent: Mutt/1.5.14 (2007-02-12)
X-Virus-Scanned: amavisd-new 2.3.3 (20050822) at iu-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: Tina Tsou <tena@huawei.com>, ops-nm@ietf.org, dongsun@alcatel-lucent.com, Hexian Huang <huanghexian@mail.ritt.com.cn>, Tom-PT Taylor <taylor@nortel.com>, nmrg@ibr.cs.tu-bs.de, ops-area@ietf.org
Subject: [OPS-NM] Re: Comments Question about draft-xu-cops-push-00.txt
X-BeenThere: ops-nm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: j.schoenwaelder@iu-bremen.de
List-Id: OPS Area NM e-mail list <ops-nm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>, <mailto:ops-nm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-nm>
List-Post: <mailto:ops-nm@ietf.org>
List-Help: <mailto:ops-nm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>, <mailto:ops-nm-request@ietf.org?subject=subscribe>
Errors-To: ops-nm-bounces@ietf.org

On Thu, Mar 15, 2007 at 10:19:18PM +0800, xuheyuan wrote:

> At that time the Re reference point, merged into Rw reference point
> later, controlled the IP edge, actually an IP-IP gateway. In the
> current network, most existing IP-IP gateways are routers, which
> support COPS already. In reality, using COPS is the quickest way to
> do that as described in approach 2 in this draft.

I have routers that support NETCONF in my lab and no routers
supporting COPS-PR or COPS.  Perhaps this is why our views of the
world are somewhat different.

> COPS-PR by nature does policy control, Rw interface mainly does
> policy control dynamically, not just push configuration
> information. Besides, in 2005,NETCONF was a pretty new protocol, and
> few existing routers supported NETCONF.

I never understood the distinction between configuration and policy
information when it comes to the device interface. The PDP is the
policy engine and what comes out of this engine as provisioning
information is for me not really distinct from configuration data
coming out of other systems (e.g. customer provisioning systems).

I agree that NETCONF was pretty new in 2005 and it still is in 2007.
COPS-PR is older but as far as I can tell not too widely implemented
and the number of people within the IETF who do understand COPS-PR
well is like to be somewhat smaller than the number of people within
the IETF who understand NETCONF and my impression was that COPS-PR
awareness declines.

> As RACF supports both fix and mobile, push and pull modes, in the
> real networking, PD-FE may possibly support both modes, and in pull
> modes, COPS is very effective, so, in push mode, if approach 2 COPS
> could be adopted, it will simplify the implementation.

The implementation simplification is a relative thing (if you have
COPS, using COPS is simple, if you have NETCONF, using NETCONF is
simple). Not sure how to make a decision on this.

Again, I like to see the discussion raised to the technical level to
first understand if NETCONF could do what you need it to do equally
well or whether there is any technical feature that really
distinguishes COPS-PR from NETCONF.

/js

-- 
Juergen Schoenwaelder		 Jacobs University Bremen
<http://www.eecs.iu-bremen.de/>	 P.O. Box 750 561, 28725 Bremen, Germany

_______________________________________________
OPS-NM mailing list
OPS-NM@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-nm