Re: [OPSAWG] ??: RE: Rtgdir early review of draft-ietf-opsawg-ipfix-bgp-community-06
heasley <heas@shrubbery.net> Thu, 19 April 2018 19:55 UTC
Return-Path: <heas@shrubbery.net>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFF1C12DA6F for <opsawg@ietfa.amsl.com>; Thu, 19 Apr 2018 12:55:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.714
X-Spam-Level:
X-Spam-Status: No, score=-2.714 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FAKE_REPLY_C=1.486, RCVD_IN_DNSWL_MED=-2.3, 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 pSqt9NyjHsgw for <opsawg@ietfa.amsl.com>; Thu, 19 Apr 2018 12:55:26 -0700 (PDT)
Received: from guelah.shrubbery.net (guelah.shrubbery.net [198.58.5.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64FE912DA6E for <opsawg@ietf.org>; Thu, 19 Apr 2018 12:55:26 -0700 (PDT)
Received: by guelah.shrubbery.net (Postfix, from userid 7053) id 3BDBF3AB3F; Thu, 19 Apr 2018 19:55:25 +0000 (UTC)
Date: Thu, 19 Apr 2018 19:55:25 +0000
From: heasley <heas@shrubbery.net>
To: opsawg@ietf.org
Message-ID: <20180419195524.GA28874@shrubbery.net>
Reply-To: 57512281-f190-916b-60f5-d27ee2cd37a1@gmail.com
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.9.4 (2018-02-28)
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/jtW7lfEdwjrMPCDhvWqCbUW_QZQ>
Subject: Re: [OPSAWG] ??: RE: Rtgdir early review of draft-ietf-opsawg-ipfix-bgp-community-06
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 19 Apr 2018 19:55:29 -0000
> Could you provide any more details on what specifically is being > patented? Given that the document does not define new protocol mechanics > and only adds in codepoints and element encodings, what can be > practically patented there? Indeed. Please just withdraw the IPR. Or, shall we write another without the IPR? * I'd have read the patent application, but the registration form on the CN patent search page does not appear to work. http://www.pss-system.gov.cn/sipopublicsearch/inportal/i18n.shtml?params=902F004CA61084A284089435EAAEA94F59CC921A916ADCEB