Re: [v6ops] management and ipv6

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 16 December 2010 22:48 UTC

Return-Path: <brian.e.carpenter@gmail.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 70D463A6979 for <v6ops@core3.amsl.com>; Thu, 16 Dec 2010 14:48:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.042
X-Spam-Level:
X-Spam-Status: No, score=-103.042 tagged_above=-999 required=5 tests=[AWL=-0.043, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-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 ESzq2PsYGAwE for <v6ops@core3.amsl.com>; Thu, 16 Dec 2010 14:48:56 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 8F82C3A6919 for <v6ops@ietf.org>; Thu, 16 Dec 2010 14:48:56 -0800 (PST)
Received: by vws7 with SMTP id 7so24773vws.31 for <v6ops@ietf.org>; Thu, 16 Dec 2010 14:50:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=kQNuRXWI2nTBC72c5BpDa3SCodGaYQpX/mOaqp0L+34=; b=kpemgYfqmwBy5Iee0BMM9MirURPaWdQ9RO5efRR/6hFvTYnbLFRke/kmsdfwnQjHAk EN2gCKPfglwZfWv4mFditI5uNdN76BecbXSGQcOgQx/6BdFtMsVJd+qT7VlcQcW9YO6R 1Eo/T1pnY1wrxl94nLHY4d21w8s1XZCXf7dDo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=uSx17Ym7WP8RQ3rcyduHYYcStHrvQS7Zg8mURWg6eKC1F7EHJr4qa1NWmqWOqEGtYJ tgxpC3c2OMmMSNmNaCnjaHT+nsU98Dmdnss01N9KwfYTG3Z8VCRV5BHlbqHaYWklYHhm NkCbi1eyj+9yXYnOkc/qYcnB0XuJ/mAJX3VyA=
Received: by 10.220.177.133 with SMTP id bi5mr2084567vcb.260.1292539840519; Thu, 16 Dec 2010 14:50:40 -0800 (PST)
Received: from [10.1.1.4] ([121.98.190.33]) by mx.google.com with ESMTPS id bq5sm210619vcb.8.2010.12.16.14.50.37 (version=SSLv3 cipher=RC4-MD5); Thu, 16 Dec 2010 14:50:39 -0800 (PST)
Message-ID: <4D0A97B9.6090607@gmail.com>
Date: Fri, 17 Dec 2010 11:50:33 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
References: <4D0A5F29.1050502@piuha.net>
In-Reply-To: <4D0A5F29.1050502@piuha.net>
Content-Type: text/plain; charset="UTF-8"
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: Thu, 16 Dec 2010 22:48:57 -0000

Hi Jari,

Some gaps in management tools were reported in the survey that led to
RFC6036, although we didn't really split them out in the analysis.
However, I do emphasise *tools*. It isn't obvious that there's a gap
in IETF specifications. So I'd be interested in seeing more details
about the proposed scope of such a document.

Regards
   Brian

On 2010-12-17 07:49, 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. 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?
> 
> Jari
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>