Re: [v6ops] new draft: draft-servin-v6ops-monitor-ds-ipv6
Arturo Servin <aservin@lacnic.net> Mon, 15 July 2013 11:44 UTC
Return-Path: <aservin@lacnic.net>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C169521F9E13 for <v6ops@ietfa.amsl.com>; Mon, 15 Jul 2013 04:44:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id damdNYY+Kezw for <v6ops@ietfa.amsl.com>; Mon, 15 Jul 2013 04:44:27 -0700 (PDT)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id 043AB21F9DF0 for <v6ops@ietf.org>; Mon, 15 Jul 2013 04:44:26 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local (unknown [IPv6:2800:af:ba30:ce73:5cbc:d667:d95a:64ad]) by mail.lacnic.net.uy (Postfix) with ESMTP id 58BCD308427; Mon, 15 Jul 2013 08:43:59 -0300 (UYT)
Message-ID: <51E3E093.2000105@lacnic.net>
Date: Mon, 15 Jul 2013 08:44:19 -0300
From: Arturo Servin <aservin@lacnic.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Alejandro Acosta <alejandroacostaalamo@gmail.com>
References: <201307131245.r6DCj0d01032@ftpeng-update.cisco.com> <51E15A35.2090603@lacnic.net> <CAOmxzdz_frL-6jN4N9J_huZ=W3GeY4PyyU8ms4Q5M6Dj9atK5Q@mail.gmail.com>
In-Reply-To: <CAOmxzdz_frL-6jN4N9J_huZ=W3GeY4PyyU8ms4Q5M6Dj9atK5Q@mail.gmail.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck:
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
Cc: v6ops@ietf.org
Subject: Re: [v6ops] new draft: draft-servin-v6ops-monitor-ds-ipv6
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 15 Jul 2013 11:44:27 -0000
Thanks Alejandro for the comments. I have made the edits and I will pushing a revision today with some other recommendations that we have received off-list. Best regards, as On 7/15/13 1:14 AM, Alejandro Acosta wrote: > Hi Arturo, > Great to see there is some working on this. > Just two comments, not big changes: > Both in the introduction section: > > 1) > "A good monitor solution allows to:" > > I think it should be changed for something like this: > > "A good monitor solution -among other things- allows to": > > 2) > : > > Change "Determinate which actions may solve a problem" > by > "Determine which actions may solve a problem" > > > Best regards, > > Alejandro, > > On 7/13/13, Arturo Servin <aservin@lacnic.net> wrote: >> Hi, >> >> We have sent this draft about considerations and recommendations to >> monitor IPv6 and dual-stack networks and services. We have been talking >> with people deploying IPv6 and we have found that not all monitor their >> networks and not many monitor them properly. We also found some >> challenges in monitor implementations that not fully support IPv6 >> monitoring technologies (snmp, netflow, ipfix, ipv6 transport). Even >> though monitoring v6 networks is as critical as doing it in v4, we have >> not found many documents explaining how that has to be done (at least >> guides with free access or up to date). >> >> There are also some misconceptions about monitoring IPv6, for >> example SNMPv3 != SNMP+IPv6, or that you cannot collect IPv6 data and >> send them on IPv4 that we wanted to clarify. >> >> We collected some recommendations from informal conversations with >> people during some training and NOGs meeting during this year but we >> need some more input. We will be sharing this draft with other forums to >> get more inputs but we wanted to share it here first. >> >> Best wishes, >> Arturo and Mariela >> >> On 7/13/13 9:45 AM, fred@cisco.com wrote: >>> A new draft has been posted, at >>> http://tools.ietf.org/html/draft-servin-v6ops-monitor-ds-ipv6. Please take >>> a look at it and comment. >>> _______________________________________________ >>> v6ops mailing list >>> v6ops@ietf.org >>> https://www.ietf.org/mailman/listinfo/v6ops >> _______________________________________________ >> v6ops mailing list >> v6ops@ietf.org >> https://www.ietf.org/mailman/listinfo/v6ops >> >
- Re: [v6ops] new draft: draft-servin-v6ops-monitor… Alejandro Acosta
- Re: [v6ops] new draft: draft-servin-v6ops-monitor… Diego R. Lopez
- [v6ops] new draft: draft-servin-v6ops-monitor-ds-… fred
- Re: [v6ops] new draft: draft-servin-v6ops-monitor… Arturo Servin
- Re: [v6ops] new draft: draft-servin-v6ops-monitor… Arturo Servin
- Re: [v6ops] new draft: draft-servin-v6ops-monitor… Arturo Servin
- Re: [v6ops] new draft: draft-servin-v6ops-monitor… Ariel Weher
- Re: [v6ops] new draft: draft-servin-v6ops-monitor… Arturo Servin
- Re: [v6ops] new draft: draft-servin-v6ops-monitor… Diego R. Lopez
- Re: [v6ops] new draft: draft-servin-v6ops-monitor… George, Wes
- Re: [v6ops] new draft: draft-servin-v6ops-monitor… Arturo Servin
- Re: [v6ops] new draft: draft-servin-v6ops-monitor… Arturo Servin
- Re: [v6ops] new draft: draft-servin-v6ops-monitor… John Mann
- Re: [v6ops] new draft: draft-servin-v6ops-monitor… Arturo Servin