Re: [spring] WGLC - draft-ietf-spring-srv6-network-programming

Fernando Gont <fgont@si6networks.com> Tue, 03 March 2020 22:59 UTC

Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE4503A07B8; Tue, 3 Mar 2020 14:59:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 6sqzN8qoY2O2; Tue, 3 Mar 2020 14:59:04 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ADC463A078B; Tue, 3 Mar 2020 14:59:03 -0800 (PST)
Received: from [192.168.0.10] (unknown [181.45.84.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 1DB6180236; Tue, 3 Mar 2020 23:58:59 +0100 (CET)
Subject: Re: [spring] WGLC - draft-ietf-spring-srv6-network-programming
To: bruno.decraene@orange.com, Fernando Gont <fernando@gont.com.ar>, Martin Vigoureux <martin.vigoureux@nokia.com>, "spring@ietf.org" <spring@ietf.org>
Cc: "6man@ietf.org" <6man@ietf.org>, "'ietf@ietf.org'" <ietf@ietf.org>, draft-ietf-spring-srv6-network-programming <draft-ietf-spring-srv6-network-programming@ietf.org>
References: <17421_1575566127_5DE93B2F_17421_93_1_53C29892C857584299CBF5D05346208A48D1A3DA@OPEXCAUBM43.corporate.adroot.infra.ftgroup> <3e2da3a5-5d1b-10a0-aeb4-320c57584241@nokia.com> <8259d37e-b460-5f76-1ce6-b0d026bccf6b@gont.com.ar> <20143_1583250558_5E5E7C7E_20143_390_3_53C29892C857584299CBF5D05346208A48DD80E6@OPEXCAUBM43.corporate.adroot.infra.ftgroup>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <82ea2fb2-59d9-1b94-81d4-7c994af14389@si6networks.com>
Date: Tue, 03 Mar 2020 19:58:52 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <20143_1583250558_5E5E7C7E_20143_390_3_53C29892C857584299CBF5D05346208A48DD80E6@OPEXCAUBM43.corporate.adroot.infra.ftgroup>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/iH7KZiRoiK7_FuPpQjXnFEfADL8>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Mar 2020 22:59:13 -0000

On 3/3/20 12:49, bruno.decraene@orange.com wrote:
> Fernando
> 
>> From: spring [mailto:spring-bounces@ietf.org] On Behalf Of Fernando Gont
>> Sent: Monday, March 2, 2020 9:23 PM
>> To: Martin Vigoureux; spring@ietf.org
>> Cc: 6man@ietf.org; 'ietf@ietf.org'; draft-ietf-spring-srv6-network-programming
>> Subject: Re: [spring] WGLC - draft-ietf-spring-srv6-network-programming
>>
>> Martin,
>>
>> As an Area Director, what are your thoughts regarding Bruno's claim that
>> this working group (Spring) doesn't have the necessary skills for
>> evaluating the need of a functionality (PSP) that this wg is including
>> in draft-ietf-spring-srv6-network-programming?
>>
>> Specifically, Bruno has noted (in
>> https://mailarchive.ietf.org/arch/msg/spring/or8086G4iYfee5_Icw4PnhkPLBo/):
>>
>> ---- cut here ----
>> Independently of RFC 8200, the question has been raised with regards to
>> the benefit of PSP.
>> My take is that PSP is an optional data plane optimization. Judging its
>> level of usefulness is very hardware and implementation dependent. It
>> may range anywhere from "not needed" to "required for my platform"
>> (deployed if you are network operator, or been sold if you are a
>> vendor), with possible intermediate points along "n% packet processing
>> gain", or "required when combined with a specific other feature". I
>> don't think that the SPRING WG can really evaluate this point (lack of
>> hardware knowledge, lack of detailed information on the hardwares).
>> ---- cut here ----
>>
>>
>> Doesn't this sound a bit like a group is shipping something that it
>> cannot really understand?
> 
> 
> There have been replied and statement from the WG. E.g. From Dan (network operator) & Jingrong (vendor).
> https://mailarchive.ietf.org/arch/msg/spring/ErcErN39RIlzkL5SKNVAeEWpnAI/

The motivation should be in the draft, not in the mail archive. And you 
declared consensus on a document that does not include such motivation.


> 
> My comment is that a statement such as "(1) reduce the load of final destination.", while true in general, is difficult to evaluate, e.g. in term of packet processing gain, or NPU processing resource gain.
> One can say "not on my hardware", but nobody can say "not in your hardware".
> 
> And I think that this is along Joel reply (although I would not want to speak for Joel)
> "Do you have any comments on what appears to be the significant increase
> in complexity on the device performing PSP?  The question I am trying to
> get at is about the tradeoff, which needs one to evaluate both sides."
> https://mailarchive.ietf.org/arch/msg/spring/CMSX7ijacRdG8qHlla61ylJNggo/

You have to justify the included behavior, not the other way around:

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492