Re: [IPFIX] New version of IPFIX configuration draft
Kobayashi Atsushi <akoba@nttv6.net> Sun, 09 March 2008 08:51 UTC
Return-Path: <ipfix-bounces@ietf.org>
X-Original-To: ietfarch-ipfix-archive@core3.amsl.com
Delivered-To: ietfarch-ipfix-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 33F143A6C40; Sun, 9 Mar 2008 00:51:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.09
X-Spam-Level:
X-Spam-Status: No, score=-100.09 tagged_above=-999 required=5 tests=[AWL=0.347, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, 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 MfqjHBYi2uzf; Sun, 9 Mar 2008 00:51:57 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3C10B3A6BD0; Sun, 9 Mar 2008 00:51:57 -0800 (PST)
X-Original-To: ipfix@core3.amsl.com
Delivered-To: ipfix@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6095C3A6B0C for <ipfix@core3.amsl.com>; Sun, 9 Mar 2008 00:51:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 a+05nE4Rdfyf for <ipfix@core3.amsl.com>; Sun, 9 Mar 2008 00:51:54 -0800 (PST)
Received: from mail.nttv6.net (mail.nttv6.net [IPv6:2001:fa8::25]) by core3.amsl.com (Postfix) with ESMTP id 5A55E28C0F6 for <ipfix@ietf.org>; Sun, 9 Mar 2008 00:51:30 -0800 (PST)
Received: from localhost (mail.nttv6.net [192.16.178.5]) by mail.nttv6.net (8.14.2/8.14.1) with ESMTP id m298mxcg064493; Sun, 9 Mar 2008 17:49:00 +0900 (JST) (envelope-from akoba@nttv6.net)
Date: Sun, 09 Mar 2008 17:49:11 +0900
From: Kobayashi Atsushi <akoba@nttv6.net>
To: Kobayashi Atsushi <akoba@nttv6.net>
In-Reply-To: <20080308212938.7A9F.AKOBA@nttv6.net>
References: <47C2F1CD.5020407@informatik.uni-tuebingen.de> <20080308212938.7A9F.AKOBA@nttv6.net>
Message-Id: <20080309173742.5623.AKOBA@nttv6.net>
MIME-Version: 1.0
X-Mailer: Becky! ver. 2.30.02 [ja]
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (mail.nttv6.net [192.16.178.5]); Sun, 09 Mar 2008 17:49:06 +0900 (JST)
Cc: "ipfix@ietf.org" <ipfix@ietf.org>
Subject: Re: [IPFIX] New version of IPFIX configuration draft
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ipfix-bounces@ietf.org
Errors-To: ipfix-bounces@ietf.org
Sorry for sending duplicate same messages. I tryed to send same message until it updates. It took about 30 minutes. On Sat, 08 Mar 2008 21:30:32 +0900 Kobayashi Atsushi <akoba@nttv6.net> wrote: > > Hi Gerhard, Benoit and all, > > This draft is almost complete and great work. > I think that such XML configuration enhances efficiency of the use of > flexibility of IPFIX. > > IMHO, I am afraid that the filtering method is different than current ACL > implemented in several routers. Therefore, the IPFIX XML cfg might not > be implemented, because of the gap between current ACL filter and IPFIX > XML cfg, even if psamp mention "AND" operation only. > > I propose the following XML schema added the ACL elements to -03 draft. > I am not familiar with YANG yet, sorry. > > http://www3.plala.or.jp/akoba/ipfix-cfg-acl.txt > http://www3.plala.or.jp/akoba/ipfix-cfg-acl.html > > The following Complex/Simple type elements are added. > - Complex Type: accessListMatch_type > - Complex Type: sequenceList_type > - SFrom ipfix-bounces@ietf.org Sun Mar 9 00:51:59 2008 Return-Path: <ipfix-bounces@ietf.org> X-Original-To: ietfarch-ipfix-archive@core3.amsl.com Delivered-To: ietfarch-ipfix-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 33F143A6C40; Sun, 9 Mar 2008 00:51:59 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -100.09 X-Spam-Level: X-Spam-Status: No, score=-100.09 tagged_above=-999 required=5 tests=[AWL=0.347, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, 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 MfqjHBYi2uzf; Sun, 9 Mar 2008 00:51:57 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3C10B3A6BD0; Sun, 9 Mar 2008 00:51:57 -0800 (PST) X-Original-To: ipfix@core3.amsl.com Delivered-To: ipfix@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6095C3A6B0C for <ipfix@core3.amsl.com>; Sun, 9 Mar 2008 00:51:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com 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 a+05nE4Rdfyf for <ipfix@core3.amsl.com>; Sun, 9 Mar 2008 00:51:54 -0800 (PST) Received: from mail.nttv6.net (mail.nttv6.net [IPv6:2001:fa8::25]) by core3.amsl.com (Postfix) with ESMTP id 5A55E28C0F6 for <ipfix@ietf.org>; Sun, 9 Mar 2008 00:51:30 -0800 (PST) Received: from localhost (mail.nttv6.net [192.16.178.5]) by mail.nttv6.net (8.14.2/8.14.1) with ESMTP id m298mxcg064493; Sun, 9 Mar 2008 17:49:00 +0900 (JST) (envelope-from akoba@nttv6.net) Date: Sun, 09 Mar 2008 17:49:11 +0900 From: Kobayashi Atsushi <akoba@nttv6.net> To: Kobayashi Atsushi <akoba@nttv6.net> In-Reply-To: <20080308212938.7A9F.AKOBA@nttv6.net> References: <47C2F1CD.5020407@informatik.uni-tuebingen.de> <20080308212938.7A9F.AKOBA@nttv6.net> Message-Id: <20080309173742.5623.AKOBA@nttv6.net> MIME-Version: 1.0 X-Mailer: Becky! ver. 2.30.02 [ja] X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (mail.nttv6.net [192.16.178.5]); Sun, 09 Mar 2008 17:49:06 +0900 (JST) Cc: "ipfix@ietf.org" <ipfix@ietf.org> Subject: Re: [IPFIX] New version of IPFIX configuration draft X-BeenThere: ipfix@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IPFIX WG discussion list <ipfix.ietf.org> List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=unsubscribe> List-Archive: <http://www.ietf.org/pipermail/ipfix> List-Post: <mailto:ipfix@ietf.org> List-Help: <mailto:ipfix-request@ietf.org?subject=help> List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=subscribe> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ipfix-bounces@ietf.org Errors-To: ipfix-bounces@ietf.org Sorry for sending duplicate same messages. I tryed to send same message until it updates. It took about 30 minutes. On Sat, 08 Mar 2008 21:30:32 +0900 Kobayashi Atsushi <akoba@nttv6.net> wrote: > > Hi Gerhard, Benoit and all, > > This draft is almost complete and great work. > I think that such XML configuration enhances efficiency of the use of > flexibility of IPFIX. > > IMHO, I am afraid that the filtering method is different than current ACL > implemented in several routers. Therefore, the IPFIX XML cfg might not > be implemented, because of the gap between current ACL filter and IPFIX > XML cfg, even if psamp mention "AND" operation only. > > I propose the following XML schema added the ACL elements to -03 draft. > I am not familiar with YANG yet, sorry. > > http://www3.plala.or.jp/akoba/ipfix-cfg-acl.txt > http://www3.plala.or.jp/akoba/ipfix-cfg-acl.html > > The following Complex/Simple type elements are added. > - Complex Type: accessListMatch_type > - Complex Type: sequenceList_type > - Simple Type: action_type > > In addition, it allows "selectionProcess_type" to include > "AccessListMatch" element. > > What do you think about that? I think that it enhances flexibility as > optional. > > Regards, > Atsushi KOBAYASHI > > On Mon, 25 Feb 2008 17:50:21 +0100 > Gerhard Muenz <muenz@informatik.uni-tuebingen.de> wrote: > > > > > Dear all, > > > > A new revision of the IPFIX/PSAMP configuration data model has been > > published: > > http://www.ietf.org/internet-drafts/draft-muenz-ipfix-configuration-04.txt > > > > Apart from smaller changes in the model itself, the big change compared > > to the previous version concerns the specification language: instead of > > XML Schema, we now use YANG, a new language for modelling Netconf data > > models. As a consequence, conformance to Netconf can be guaranteed. > > > > We received a lot of valuable feedback and support from Martin Bjorklund > > who is a Netconf expert and author of the YANG draft. We will try to get > > some additional feedback from other Netconf experts as well. > > > > Regards, > > Gerhard > > _______________________________________________ IPFIX mailing list IPFIX@ietf.org https://www.ietf.org/mailman/listinfo/ipfix imple Type: action_type > > In addition, it allows "selectionProcess_type" to include > "AccessListMatch" element. > > What do you think about that? I think that it enhances flexibility as > optional. > > Regards, > Atsushi KOBAYASHI > > On Mon, 25 Feb 2008 17:50:21 +0100 > Gerhard Muenz <muenz@informatik.uni-tuebingen.de> wrote: > > > > > Dear all, > > > > A new revision of the IPFIX/PSAMP configuration data model has been > > published: > > http://www.ietf.org/internet-drafts/draft-muenz-ipfix-configuration-04.txt > > > > Apart from smaller changes in the model itself, the big change compared > > to the previous version concerns the specification language: instead of > > XML Schema, we now use YANG, a new language for modelling Netconf data > > models. As a consequence, conformance to Netconf can be guaranteed. > > > > We received a lot of valuable feedback and support from Martin Bjorklund > > who is a Netconf expert and author of the YANG draft. We will try to get > > some additional feedback from other Netconf experts as well. > > > > Regards, > > Gerhard > > _______________________________________________ IPFIX mailing list IPFIX@ietf.org https://www.ietf.org/mailman/listinfo/ipfix
- [IPFIX] New version of IPFIX configuration draft Gerhard Muenz
- Re: [IPFIX] New version of IPFIX configuration dr… Kobayashi Atsushi
- Re: [IPFIX] New version of IPFIX configuration dr… Kobayashi Atsushi
- Re: [IPFIX] New version of IPFIX configuration dr… Kobayashi Atsushi
- Re: [IPFIX] New version of IPFIX configuration dr… Kobayashi Atsushi
- Re: [IPFIX] New version of IPFIX configuration dr… Kobayashi Atsushi
- Re: [IPFIX] New version of IPFIX configuration dr… Kobayashi Atsushi
- Re: [IPFIX] New version of IPFIX configuration dr… Kobayashi Atsushi
- Re: [IPFIX] New version of IPFIX configuration dr… Gerhard Muenz
- Re: [IPFIX] New version of IPFIX configuration dr… Atsushi Kobayashi
- Re: [IPFIX] New version of IPFIX configuration dr… Gerhard Muenz
- Re: [IPFIX] New version of IPFIX configuration dr… Atsushi Kobayashi
- Re: [IPFIX] New version of IPFIX configuration dr… Gerhard Muenz
- Re: [IPFIX] New version of IPFIX configuration dr… Atsushi Kobayashi
- Re: [IPFIX] New version of IPFIX configuration dr… Andy Bierman