Re: [v6ops] management and ipv6

Joel Jaeggli <joelja@bogus.com> Fri, 17 December 2010 06:05 UTC

Return-Path: <joelja@bogus.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 C44C23A6A85 for <v6ops@core3.amsl.com>; Thu, 16 Dec 2010 22:05:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.789
X-Spam-Level:
X-Spam-Status: No, score=-101.789 tagged_above=-999 required=5 tests=[AWL=0.210, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, 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 nvXEYWy49wAl for <v6ops@core3.amsl.com>; Thu, 16 Dec 2010 22:05:18 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by core3.amsl.com (Postfix) with ESMTP id 5150E3A6903 for <v6ops@ietf.org>; Thu, 16 Dec 2010 22:05:18 -0800 (PST)
Received: from joelja-mac.lan (c-98-234-216-143.hsd1.ca.comcast.net [98.234.216.143]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id oBH66rXs084457 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Fri, 17 Dec 2010 06:06:58 GMT (envelope-from joelja@bogus.com)
Message-ID: <4D0AF5BC.2050808@bogus.com>
Date: Thu, 16 Dec 2010 21:31:40 -0800
From: Joel Jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
References: <4D0A5F29.1050502@piuha.net>
In-Reply-To: <4D0A5F29.1050502@piuha.net>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, '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: Fri, 17 Dec 2010 06:05:19 -0000

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.

> They believe that there's quite a bit of work in this
> if you actually dig through all the details such as what MIB versions
> are required.
> 
> Draft-arkko will be moving forward as we close some other last issues,
> but would the V6OPS WG be willing to work on a separate document to talk
> about management of IPv6 networks? Or is there such a document already?

There's a corpus of work expressed as nanog presnetations among others
on how you manage ipv6 networks.

If some kind of gap analysis reveals protocol omissions or usability
issues with the management of ipv6 I could imagine  that fitting within
the v6ops scope.

> Jari
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>