Re: [v6ops] draft-elkins-6man-ipv6-diagnostic-header (Was: draft minutes ietf 81, 3 meetings...)

Fred Baker <fred@cisco.com> Mon, 15 August 2011 20:56 UTC

Return-Path: <fred@cisco.com>
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 67D2B21F8CF8 for <v6ops@ietfa.amsl.com>; Mon, 15 Aug 2011 13:56:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.838
X-Spam-Level:
X-Spam-Status: No, score=-102.838 tagged_above=-999 required=5 tests=[AWL=-0.239, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 8jGLaBM+mNKJ for <v6ops@ietfa.amsl.com>; Mon, 15 Aug 2011 13:56:45 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id AC10A21F8CEA for <v6ops@ietf.org>; Mon, 15 Aug 2011 13:56:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=2177; q=dns/txt; s=iport; t=1313441852; x=1314651452; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=8Y+3jrQQr8kTr0E74K85r63hjNhUX58wl+RVgAH5JfI=; b=OH2z5Vu/plPKy9DzLa2ophxMdF2FLawbdJs+/pw5jfGxCxrV1Gdfow80 Z2r/mEPjWDcec3IESoRdoKbAoOQ08lpFU8VEFMVnakZ+U3SIZ+0EZ6CsR UO4NjMc+u200ASLVdvSC3vX7vbLDc9MYWbS4B04pBgHV5/GmIJf4HgVCj E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAE6HSU6rRDoG/2dsb2JhbABCqBZ3gUABAQEBAgESASc/BQsLGC5XBi4Hh06aYAGfBYVoXwSHX4szhQyMCQ
X-IronPort-AV: E=Sophos;i="4.67,376,1309737600"; d="scan'208";a="13335075"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by rcdn-iport-4.cisco.com with ESMTP; 15 Aug 2011 20:57:31 +0000
Received: from stealth-10-32-244-221.cisco.com (stealth-10-32-244-221.cisco.com [10.32.244.221]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p7FKvVfv009145; Mon, 15 Aug 2011 20:57:31 GMT
Received: from [127.0.0.1] by stealth-10-32-244-221.cisco.com (PGP Universal service); Mon, 15 Aug 2011 13:57:31 -0700
X-PGP-Universal: processed; by stealth-10-32-244-221.cisco.com on Mon, 15 Aug 2011 13:57:31 -0700
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <C67F9F44-01D9-4094-855B-BC07AD2D6891@castlepoint.net>
Date: Mon, 15 Aug 2011 13:57:04 -0700
Message-Id: <88B750D9-3429-49A3-B283-BA1594406911@cisco.com>
References: <1313420245.20792.YahooMailClassic@web2818.biz.mail.ne1.yahoo.com> <28E09383-C957-485D-8B15-12EE742D9A2F@castlepoint.net> <EB547F6A-90E9-458A-9FBE-956F82656870@cisco.com> <C67F9F44-01D9-4094-855B-BC07AD2D6891@castlepoint.net>
To: Shane Amante <shane@castlepoint.net>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Cc: v6ops@ietf.org
Subject: Re: [v6ops] draft-elkins-6man-ipv6-diagnostic-header (Was: draft minutes ietf 81, 3 meetings...)
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 Aug 2011 20:56:46 -0000

On Aug 15, 2011, at 1:38 PM, Shane Amante wrote:

> 
> On Aug 15, 2011, at 11:15 AM, Fred Baker wrote:
>> On Aug 15, 2011, at 10:02 AM, Shane Amante wrote:
>> 
>>>> 1.  What if BGP is not being used?
>>> 
>>> Turn it on?
>> 
>> I don't think her question relates to how to turn it on. I think her question relates to the fact that it is not universally needed. BGP is used in inter-corporate networks including ISP-ISP and ISP-customer; it is less commonly used within enterprise and especially data center networks. So when it is not in use, ...
> 
> 
> But, in the case of flow-spec, we're talking about it being used as a "policy distribution mechanism" and not as a routing protocol.

We could discuss "it slices, it dices, and it juliennes too." In my experience, the implied exponential complexity is often of questionable value. If she was using the routing protocol, having it also do something else might make sense. If she is using a different routing protocol or doesn't need one, turning on a routing protocol in order to turn off its routing functionality but... 

my head hurts.

> Look, if BGP is too onerous, then deploy/use sFlow/NetFlow/IPFIX.

Now, there's a sensible solution. At least it targets the intended functionality.

IPFIX, however, reports on sessions (in the target case, relatively large sets of packets) after they happen. What she's looking for is packet information while they're happening.

> The only concern with that may be that depending on the scale/size of platform it may only be able to do statistical sampling, (not 1:1 sampling), if you need to use the central RP.

... packet ... while they're happening ...

> If that's a concern, take it up with your favorite vendor, they have the ability to either sell you HW (today) that will do 1:1, or close to it, sampling.

No doubt.

> I still maintain there are existing tools out there, today, that _are_ already being used to trace these types of issues.  Please let's use them and/or improve upon them.

Well, and funny thing, she's building at least in part on wireshark.