Re: [IPFIX] IPFIX export: SNMP versus physical Interface
Juergen Quittek <Quittek@neclab.eu> Tue, 26 July 2011 15:25 UTC
Return-Path: <Quittek@neclab.eu>
X-Original-To: ipfix@ietfa.amsl.com
Delivered-To: ipfix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79AD111E811C for <ipfix@ietfa.amsl.com>; Tue, 26 Jul 2011 08:25:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.174
X-Spam-Level:
X-Spam-Status: No, score=-102.174 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, HELO_EQ_DE=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vp2YXBG5IVqO for <ipfix@ietfa.amsl.com>; Tue, 26 Jul 2011 08:25:58 -0700 (PDT)
Received: from smtp0.netlab.nec.de (smtp0.netlab.nec.de [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id B974B11E810A for <ipfix@ietf.org>; Tue, 26 Jul 2011 08:25:56 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp0.netlab.nec.de (Postfix) with ESMTP id 0893C2800032C; Tue, 26 Jul 2011 17:25:56 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office.hd)
Received: from smtp0.netlab.nec.de ([127.0.0.1]) by localhost (atlas1.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jxpU60gI-ULp; Tue, 26 Jul 2011 17:25:55 +0200 (CEST)
Received: from METHONE.office.hd (Methone.office.hd [192.168.24.54]) by smtp0.netlab.nec.de (Postfix) with ESMTP id E059128000327; Tue, 26 Jul 2011 17:25:40 +0200 (CEST)
Received: from Polydeuces.office.hd ([169.254.3.125]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0270.001; Tue, 26 Jul 2011 17:25:41 +0200
From: Juergen Quittek <Quittek@neclab.eu>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Andrew Feren <andrewf@plixer.com>
Thread-Topic: [IPFIX] IPFIX export: SNMP versus physical Interface
Thread-Index: AQHMS6hGIQFWk4i+J0edj8aD7cTPqw==
Date: Tue, 26 Jul 2011 15:25:40 +0000
Message-ID: <CA545203.148C1%quittek@neclab.eu>
In-Reply-To: <20110726150219.GA7287@elstar.local>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.12.0.110505
x-originating-ip: [10.7.0.92]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <5323DBFA22CC784BA84D405A95ECE2BB@office.hd>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF IPFIX Working Group <ipfix@ietf.org>
Subject: Re: [IPFIX] IPFIX export: SNMP versus physical Interface
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipfix>, <mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Tue, 26 Jul 2011 15:25:59 -0000
Hi all, [Writing as technical contrionbutor] I agree. In the definition of IEs #10 and #14 we refer to RFC2863 and state that the IE reports the ifIndex value for that interface. This still appears to be a very good choice and I don't think we should change this. It might be helpful using IEs #252 and #253 when reporting the physical interface is needed where a logical one reported by #10 or #14 is located. Juergen On 26.07.11 11:02, "Juergen Schoenwaelder" <j.schoenwaelder@jacobs-university.de> wrote: >On Tue, Jul 26, 2011 at 10:54:52AM -0400, Andrew Feren wrote: > >> From a collection and reporting perspective the important difference for >> me in these two sets of definitions isn't physical vs maybe not >> physical, but that "The value matches the value of managed object >> 'ifIndex' as defined in RFC 2863 ..." and everything that implies for >> elements 10/14. >> >> So I agree with Paul's approach. There are situations where either >> 10/14 or 252/253 could be used, but if RFC 2863 applies to your >> interface use 10/14. >> >> Maybe rather than replacing "IP interface" with "logical or virtual >> interface" it could just be "interface" or "network interface". >> >> On a related not I'm not sure the references for 252/253 need to refer >> readers to "[RFC2863] for the definition of the ifIndex object." > >RFC2863 always applies to an ifIndex object. I fail to see the >problem. I find the definitions of these elements rather clear as they >are written. > >/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/> >_______________________________________________ >IPFIX mailing list >IPFIX@ietf.org >https://www.ietf.org/mailman/listinfo/ipfix
- [IPFIX] IPFIX export: SNMP versus physical Interf… Paul Aitken
- Re: [IPFIX] IPFIX export: SNMP versus physical In… Juergen Schoenwaelder
- Re: [IPFIX] IPFIX export: SNMP versus physical In… Paul Aitken
- Re: [IPFIX] IPFIX export: SNMP versus physical In… Brian Trammell
- Re: [IPFIX] IPFIX export: SNMP versus physical In… Andrew Feren
- Re: [IPFIX] IPFIX export: SNMP versus physical In… Juergen Schoenwaelder
- Re: [IPFIX] IPFIX export: SNMP versus physical In… Juergen Quittek
- Re: [IPFIX] IPFIX export: SNMP versus physical In… Benoit Claise
- Re: [IPFIX] IPFIX export: SNMP versus physical In… Andrew Feren
- Re: [IPFIX] IPFIX export: SNMP versus physical In… Juergen Quittek
- Re: [IPFIX] IPFIX export: SNMP versus physical In… Benoit Claise