Re: [sunset4] IPR Disclosure Huawei Technologies Co., Ltd's Statement about IPR related to draft-ietf-sunset4-gapanalysis

Mikael Abrahamsson <swmike@swm.pp.se> Wed, 13 September 2017 04:23 UTC

Return-Path: <swmike@swm.pp.se>
X-Original-To: sunset4@ietfa.amsl.com
Delivered-To: sunset4@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C92D3133A69 for <sunset4@ietfa.amsl.com>; Tue, 12 Sep 2017 21:23:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level:
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 lS_5zMlJ-ZfB for <sunset4@ietfa.amsl.com>; Tue, 12 Sep 2017 21:23:53 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5AE06132964 for <sunset4@ietf.org>; Tue, 12 Sep 2017 21:23:52 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 05CDCB2; Wed, 13 Sep 2017 06:23:49 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1505276629; bh=0z75h1Le1pVWTzBFLFChUuUdkVrwzhN4BjTCjRunHiY=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=WVCBwZhXHlUMmTsWo/tnogF93QaYQnG3TT8yRZ+zTlALW1gWK0joc6dw4R9ZTN2p4 l2E7kcRWim7wSAY/4oZtSwitB9C4tyxDRx06dBpkmjvx65kYY03O+si4eJQqjR8pPN soWfUgKfmKBbpChxGuNSLQ2iGEubqRAkcAqmhwW0=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 00C48B1; Wed, 13 Sep 2017 06:23:48 +0200 (CEST)
Date: Wed, 13 Sep 2017 06:23:48 +0200
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Lee Howard <lee@asgard.org>
cc: Ted Lemon <mellon@fugue.com>, sunset4@ietf.org
In-Reply-To: <D5DDB57B.85A33%lee@asgard.org>
Message-ID: <alpine.DEB.2.20.1709130618120.29378@uplift.swm.pp.se>
References: <150523673628.17987.7033238355130325081@ietfa.amsl.com> <D5DDA85B.85A13%lee@asgard.org> <FF82060A-E792-4253-8FBE-FBE2B259C584@fugue.com> <D5DDB57B.85A33%lee@asgard.org>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sunset4/GvK2wJfAG84LUTkVZNPGyU16buk>
Subject: Re: [sunset4] IPR Disclosure Huawei Technologies Co., Ltd's Statement about IPR related to draft-ietf-sunset4-gapanalysis
X-BeenThere: sunset4@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: sunset4 working group discussion list <sunset4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sunset4>, <mailto:sunset4-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sunset4/>
List-Post: <mailto:sunset4@ietf.org>
List-Help: <mailto:sunset4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sunset4>, <mailto:sunset4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Sep 2017 04:23:56 -0000

On Tue, 12 Sep 2017, Lee Howard wrote:

> And now I find that translation is available, 
> https://encrypted.google.com/patents/CN106612196A?cl=en Which suggests 
> that a client may request resources. So I wonder if this is related to 
> on-demand IP provisioning?

A quick read through (I hate "patent code") seems to indicate that this 
patents basically "DHCP but over NETCONF/RESTCONF", where one use-case is 
NFV provisioning (over NETCONF) based on this interaction to provision the 
needed resource.

"NETCONF protocol is the Internet Engineering Task Force (Internet 
Engineering Task Force, IETF) NETCONF working group launched a new network 
configuration protocol (Network Configuration Protocol), NETC0NF in the 
role of network management similar to the simple network management 
protocol (Simple Network Management Protocol, SNMP) for network interface 
and data transmission between devices. In a network environment, the 
resource manager is used to centrally manage multiple resources of network 
devices, such as Internet Protocol (IP) address pools and forwarding 
entries. The NETCONF protocol is used between the resource manager and the 
network device. The resource manager can allocate resources to the network 
device based on the NETCONF protocol. The current allocation of resources 
there is a waste of resources."

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se