IETF Logo Mail Archive

Re: [sfc] Call for adoption https://datatracker.ietf.org/doc/draft-kumar-sfc-offloads/

Greg Mirsky <gregimirsky@gmail.com> Thu, 23 March 2017 16:17 UTC

Return-Path: <gregimirsky@gmail.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2230012985B for <sfc@ietfa.amsl.com>; Thu, 23 Mar 2017 09:17:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 8oO0BtB7tUvT for <sfc@ietfa.amsl.com>; Thu, 23 Mar 2017 09:17:15 -0700 (PDT)
Received: from mail-oi0-x234.google.com (mail-oi0-x234.google.com [IPv6:2607:f8b0:4003:c06::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C3C111297E1 for <sfc@ietf.org>; Thu, 23 Mar 2017 09:17:15 -0700 (PDT)
Received: by mail-oi0-x234.google.com with SMTP id r203so62867966oib.3 for <sfc@ietf.org>; Thu, 23 Mar 2017 09:17:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=VAUKDAEgKfwq5urT5j3t1MTERaR3uWU+G6HWL5kcrXg=; b=aP/RJZLV1OQSqCUy2i+lrtdRV10WSqpt4ooV5vVvgK/vBrpr4CLX5sX+3sOY9D3YcS xoaz9kGwFo0YsH0RU+7aME6OvFycUresXB1vxJyQFBnwG1lGceaPTJGhqzALeN4f8Ggm +rXpDp9nKjNhmtbMHoutTRc5DWxaRPgwo4/d4p4JnbXs1Sy25g/M2riPF49SCX6YgFbw tc+snSoiiXdLfYr4qJoZES7crSqx9Ft2c/tg8lxyHviLAcweY+uGWMlWjNeTBcgEvsCb JISFHTa9EGEAE3CiNtaKf5CZ+SzBsOsOw/U16E6FI+w0qnDZqD1FP6GFmeL4PkZjKKf8 cYDg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=VAUKDAEgKfwq5urT5j3t1MTERaR3uWU+G6HWL5kcrXg=; b=hoEqI58yscvULwZhIyXGydMeoQVkXvhcHqEEQmD14Rz18hwRyAwrRfgzYDNXzUpRap vpkkQzXWxgGn6kZicPGXZtzYT9sNILe2ZcUaXeirxSP5lsckWFidBcV4u3cgwg0I/z5I RSOH/7/47vZbtysW1g6IJ5qE8mCFc7ZStZ1bSJpf5p358kczwQjfkTcz2aLhKHYeEz5c rJ06wptLbpBcaV1q5dI5mBag6gHQ3Lg+JqO4r1asHRuJafGjrtFPYjStyU9iMYpy4TBO ApZ7H3myIIAr0wbn3tg1xdV0JcvUt+2cfsYaqlVcf2AXI6nwM7Ue9Hd0vzh1SWO1WfZN YhSQ==
X-Gm-Message-State: AFeK/H0HZwymBplGKx7UurL6cwcnpcVbRnT3t2QCo7sCJPZWkKbp9XqxkyM0dyVbUaUuecrV+WemexL8gFotcw==
X-Received: by 10.202.196.79 with SMTP id u76mr2047079oif.44.1490285835226; Thu, 23 Mar 2017 09:17:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.157.21.21 with HTTP; Thu, 23 Mar 2017 09:17:14 -0700 (PDT)
In-Reply-To: <BF1BE6D99B52F84AB9B48B7CF6F17DA3DC0171@SJCEML701-CHM.china.huawei.com>
References: <BF1BE6D99B52F84AB9B48B7CF6F17DA3DC0171@SJCEML701-CHM.china.huawei.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Thu, 23 Mar 2017 11:17:14 -0500
Message-ID: <CA+RyBmWyENuFGPhPAMS6oy9fQ0TugmjKhFm4Jwatxn7gA3iXWg@mail.gmail.com>
To: James N Guichard <james.n.guichard@huawei.com>
Cc: "sfc@ietf.org" <sfc@ietf.org>
Content-Type: multipart/alternative; boundary="001a11c17b32d2960b054b68359a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/1p9KkRfi-ilM73CI5C-4VVqOdvQ>
Subject: Re: [sfc] Call for adoption https://datatracker.ietf.org/doc/draft-kumar-sfc-offloads/
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Network Service Chaining <sfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sfc>, <mailto:sfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sfc/>
List-Post: <mailto:sfc@ietf.org>
List-Help: <mailto:sfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sfc>, <mailto:sfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Mar 2017 16:17:19 -0000

Dear Authors, WG Chairs, et. al,
I've read the draft and think that it addresses practical scenario, offers
viable solution and expresses it all in well-written form. Hence I support
its adoption by SFC WG.
But I find the draft to be in quite unusual, at least in my experience at
IETF, situation in regard to IPR disclosures. It has two disclosures
<https://datatracker.ietf.org/ipr/search/?submit=draft&id=draft-kumar-sfc-offloads>
with different licencing clauses:

   - a covenant not to assert or royalty bearing licensee;
   - RAND with possible royalty/fee to implementers.

I'm not, by far, an IPR expert but, as I recall, IETF is striving to
advance solutions that do not bear imposition of royalty fee on an
implementer. I think that it would be helpful to get clarification, expert
opinion perhaps, on relationship of both IPR claims and the solution
defined in the draft.

Regards,
Greg

On Fri, Mar 10, 2017 at 7:08 PM, James N Guichard <
james.n.guichard@huawei.com> wrote:

> Greetings WG,
>
>
>
> This message begins a two week call for WG adoption of the document
> https://datatracker.ietf.org/doc/draft-kumar-sfc-offloads/ ending 24th
> March 2017.
>
>
>
> Please respond to the SFC mailing list with any statements of approval or
> disapproval.
>
>
>
> Please note:
>
>
>
> 1.        This is not WG last call. The document is not final and the WG
> is expected to modify the content until there is WG consensus that the
> content is solid. Therefore, please don’t oppose adoption just because you
> want to see changes to its content.
>
> 2.        If you have objections to adoption of the document, please
> state your reasons why, and explain what it would take to address your
> concerns.
>
> 3.        If you have issues with the content, by all means raise those
> issues and we can begin a dialog about how best to address them.
>
>
>
> Yours,
>
>
>
> Jim & Joel
>
>
>
>
>
> _______________________________________________
> sfc mailing list
> sfc@ietf.org
> https://www.ietf.org/mailman/listinfo/sfc
>
>

v2.23.0 | Report a Bug | By Email