Re: [OPSAWG] AD review of draft-ietf-opsawg-large-flow-load-balancing (draft response)
Benoit Claise <bclaise@cisco.com> Mon, 14 April 2014 12:28 UTC
Return-Path: <bclaise@cisco.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CE6B1A01CE for <opsawg@ietfa.amsl.com>; Mon, 14 Apr 2014 05:28:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.772
X-Spam-Level:
X-Spam-Status: No, score=-9.772 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JtA7h-WTMKWx for <opsawg@ietfa.amsl.com>; Mon, 14 Apr 2014 05:28:25 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) by ietfa.amsl.com (Postfix) with ESMTP id 1F13A1A01E6 for <opsawg@ietf.org>; Mon, 14 Apr 2014 05:28:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=16366; q=dns/txt; s=iport; t=1397478503; x=1398688103; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=9jz8DnjXSQSixJfxt2bvHoFl8WZih5UoQAGku48I9/Y=; b=V3x9CcJvaPAp+w9aek90yW9vHrh2eVjmdl46qGk7Sz27rAtUSCBte5gm ADEhYbr3IY8idf+opY8nSy1CBFz1STdhHcMCD6m9yKJ7ZkZKlZVfiM/P1 TDt5lN08kvWgA5l/rGpwwl0T2tR/xrV20nrKiaObRb3c8KnKg/vG16ANX o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Aq8EACXTS1OtJssW/2dsb2JhbABYDoMziUS6MIE7dIIlAQEBBHgBEAsYCRYIBwkDAgECATQRBg0BBQIBAYd4DcsWEwSObgeEOAEDmGGGVItvgnFCOw
X-IronPort-AV: E=Sophos; i="4.97,856,1389744000"; d="scan'208,217"; a="13170235"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP; 14 Apr 2014 12:28:22 +0000
Received: from [10.60.67.86] (ams-bclaise-8915.cisco.com [10.60.67.86]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s3ECSLY6014303; Mon, 14 Apr 2014 12:28:21 GMT
Message-ID: <534BD465.4090503@cisco.com>
Date: Mon, 14 Apr 2014 14:28:21 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Anoop Ghanwani <anoop@alumni.duke.edu>
References: <CA+-tSzxDpD2V7Q15Jjgzz2A+d5Gn_92YQ-1_Zvx2AP=s5AWpxA@mail.gmail.com>
In-Reply-To: <CA+-tSzxDpD2V7Q15Jjgzz2A+d5Gn_92YQ-1_Zvx2AP=s5AWpxA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------010902020207030602080105"
Archived-At: http://mailarchive.ietf.org/arch/msg/opsawg/OiLLP0rIXvfH81gqqWdfTJj9MY4
Cc: "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] AD review of draft-ietf-opsawg-large-flow-load-balancing (draft response)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 12:28:30 -0000
Hi Anoop, Thanks for the new draft version. I removed some of the points > > > On Tue, Feb 18, 2014 at 7:55 AM, Benoit Claise <bclaise@cisco.com > <mailto:bclaise@cisco.com>> wrote: > > - > > A number of routers support sampling techniques such as sFlow [sFlow- > v5, sFlow-LAG], PSAMP [RFC 5475] and NetFlow Sampling [RFC 3954]. > For the purpose of large flow identification, sampling must be > enabled on all of the egress ports in the router where such > measurements are desired. > > I don't understand the second sentence. > One way to read this is: sampling must be _enabled _on all of the > egress ports where such measurements are desired. > Ok, this is an obvious statement. If the measurements are > desired, enable them > > > Yes, > > Or maybe you want to say: _sampling _must be enabled on all of the > egress ports where such measurements are desired. > This is a false statement: if you have the choice between > sampling and non sampling, use non sampling measurements. > Or maybe you want to say: sampling must be enabled on _all _of the > egress ports where such measurements are desired. > This is a false statement: if I have ECMP on 2 links, and only > one of them can't do non sampling, then we should not force > sampling on both links. > You see, I'm confused. > > You miss a couple of key messages: > - if unsampled measurements are available, use those. > - egress means where LAG/ECMP are enabled (this is important for > the paragraph starting with "If egress sampling is not available, > ingress sampling can suffice since the central management entity use") > > > We were not intending to discuss a mix sampling and non-sampling > interfaces in the same router, but this is a reasonable point and it > will be clarified (i.e. we will state that it's possible to mix > sampled and non sampled interfaces as long as the function of large > flow detection/identification can be performed). You're still missing the point that unsampled measurements is better than sampled ones. Is this what you mean by: It is possible that a router may have line cards that support a sampling technique while other line cards support automatic hardware detection of large flows. It's not very clear. > > > > > > > - The indentation in section 2 is not correct > > > Will fix. > > > - "For tunneling protocols like GRE, VXLAN, NVGRE, STT, etc.," > You need to expand and provide references. > > Will provide references. Still to be provided > What do mean by expand -- just expand the acronyms (already in the > acronym section) or something else? Acceptable acronyms are https://www.rfc-editor.org/rfc-style-guide/abbrev.expansion.txt > > - a PBR rule > Expand. > > OK to be done. Regards, Benoit
- Re: [OPSAWG] AD review of draft-ietf-opsawg-large… Benoit Claise
- Re: [OPSAWG] AD review of draft-ietf-opsawg-large… Benoit Claise
- Re: [OPSAWG] AD review of draft-ietf-opsawg-large… Anoop Ghanwani
- Re: [OPSAWG] AD review of draft-ietf-opsawg-large… ramki Krishnan
- Re: [OPSAWG] AD review of draft-ietf-opsawg-large… Benoit Claise
- Re: [OPSAWG] AD review of draft-ietf-opsawg-large… Anoop Ghanwani
- Re: [OPSAWG] AD review of draft-ietf-opsawg-large… Benoit Claise
- Re: [OPSAWG] AD review of draft-ietf-opsawg-large… Anoop Ghanwani
- Re: [OPSAWG] AD review of draft-ietf-opsawg-large… Benoit Claise
- Re: [OPSAWG] AD review of draft-ietf-opsawg-large… Anoop Ghanwani
- Re: [OPSAWG] AD review of draft-ietf-opsawg-large… ramki Krishnan
- Re: [OPSAWG] AD review of draft-ietf-opsawg-large… Benoit Claise