IETF Logo Mail Archive

Re: [v6ops] management and ipv6

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Mon, 20 December 2010 09:50 UTC

Return-Path: <dromasca@avaya.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8B7703A69C0 for <v6ops@core3.amsl.com>; Mon, 20 Dec 2010 01:50:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.541
X-Spam-Level:
X-Spam-Status: No, score=-102.541 tagged_above=-999 required=5 tests=[AWL=0.058, 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 fZkWj5BM4uZo for <v6ops@core3.amsl.com>; Mon, 20 Dec 2010 01:50:30 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id 52F203A6A2B for <v6ops@ietf.org>; Mon, 20 Dec 2010 01:50:30 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AosFAA+2Dk2HCzI1/2dsb2JhbACYd4sqc6Q+Apg0hUoEjjKCWw
X-IronPort-AV: E=Sophos;i="4.60,201,1291611600"; d="scan'208";a="224023485"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 20 Dec 2010 04:52:22 -0500
X-IronPort-AV: E=Sophos;i="4.60,201,1291611600"; d="scan'208";a="559966968"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 20 Dec 2010 04:52:20 -0500
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: Mon, 20 Dec 2010 10:51:58 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A04029CBC24@307622ANEX5.global.avaya.com>
In-Reply-To: <4D0BB9AD.4050209@gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [v6ops] management and ipv6
Thread-Index: AcueIH7bJ4ciQZIsTpyPpsgTVNT7/gCCuYLA
References: <4D0A5F29.1050502@piuha.net> <4D0AF5BC.2050808@bogus.com> <4D0BB9AD.4050209@gmail.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Joel Jaeggli <joelja@bogus.com>
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] management and ipv6
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Dec 2010 09:50:31 -0000

 

> -----Original Message-----
> From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com] 
> Sent: Friday, December 17, 2010 9:28 PM
> To: Joel Jaeggli
> Cc: Jari Arkko; Romascanu, Dan (Dan); 'IPv6 Operations'
> Subject: Re: [v6ops] management and ipv6
> 
> On 2010-12-17 18:31, Joel Jaeggli wrote:
> > On 12/16/10 10:49 AM, Jari Arkko wrote:
> >> In the course of discussing 
> draft-arkko-ipv6-transition-guidelines in 
> >> the IESG, Dan and other IESG members brought up the need to talk 
> >> about management in IPv6 networks. For instance, in IPv6-only 
> >> networks all your management tools have to be capable of 
> IPv6, both 
> >> in dual stack and IPv6-only you want your data models to support 
> >> IPv6, in dual stack you need to monitor reachability and 
> errors not 
> >> just in IPv4 but also in IPv6, and so on.
> > 
> > what version of netflow you use is also germain for example.
> 
> I think you might mean ipfix, in the IETF context. Making 
> sure that ipfix is 100% ipv6-safe is important.
> 
>     Brian
>

I think it is. If somebody knows any deficiencies on this respect please
bring them to the attention of the IPFIX WG. 

Dan

v2.23.0 | Report a Bug | By Email