Re: [sidr] Mirja Kühlewind's No Objection on draft-ietf-sidr-bgpsec-algs-16: (with COMMENT)

"Ben Campbell" <ben@nostrum.com> Mon, 12 December 2016 16:15 UTC

Return-Path: <ben@nostrum.com>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A70C81295B5 for <sidr@ietfa.amsl.com>; Mon, 12 Dec 2016 08:15:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.796
X-Spam-Level:
X-Spam-Status: No, score=-4.796 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-2.896] autolearn=unavailable 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 lm_jfUIMLq9g for <sidr@ietfa.amsl.com>; Mon, 12 Dec 2016 08:15:50 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 267D9129CC0 for <sidr@ietf.org>; Mon, 12 Dec 2016 08:15:37 -0800 (PST)
Received: from [10.0.1.21] (cpe-66-25-7-22.tx.res.rr.com [66.25.7.22]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id uBCGFWRL024369 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 12 Dec 2016 10:15:33 -0600 (CST) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.21]
From: Ben Campbell <ben@nostrum.com>
To: Alvaro Retana <aretana@cisco.com>
Date: Mon, 12 Dec 2016 10:15:32 -0600
Message-ID: <94724E1D-5EA3-46A3-80F9-4E4636D1266F@nostrum.com>
In-Reply-To: <7C970123-C954-44D8-B24B-BCA2BA294BBB@cisco.com>
References: <148154966702.22433.12175370874876571095.idtracker@ietfa.amsl.com> <7C970123-C954-44D8-B24B-BCA2BA294BBB@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.6r5310)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/RB7WwEerZdzIJ6T4fANy-qDP_Zo>
Cc: "draft-ietf-sidr-bgpsec-algs@ietf.org" <draft-ietf-sidr-bgpsec-algs@ietf.org>, "sidr@ietf.org" <sidr@ietf.org>, "sidr-chairs@ietf.org" <sidr-chairs@ietf.org>, Mirja Kuehlewind <ietf@kuehlewind.net>, The IESG <iesg@ietf.org>, "Sandra L. Murphy" <sandy@tislabs.com>
Subject: Re: [sidr] Mirja Kühlewind's No Objection on draft-ietf-sidr-bgpsec-algs-16: (with COMMENT)
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidr/>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Dec 2016 16:15:51 -0000

On 12 Dec 2016, at 9:07, Alvaro Retana (aretana) wrote:

> On 12/12/16, 8:34 AM, "Mirja Kuehlewind" <ietf@kuehlewind.net> wrote:
>
> Mirja:
>
> Hi!
>
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>>
>> Just a thought: Would it be useful to add an IESG note saying 
>> something
>> like in the sheperd write-up:
>> "[...] there are published references
>>     that preceded the filing of the patent, especially those 
>>     mentioned in RFC6090.  RFC6090 notes that its descriptions
>>     "may be useful for implementing the fundamental algorithms 
>> without 
>>     using any of the  specialized methods that were developed 
>> in 
>>     following years.""
>> I know we usuall don't do things like this. But I'm wondering how 
>> someone
>> who wants to implement this should figure this out otherwise....?
>
> I think we would be getting too close to taking a stance on the 
> validity, enforceability of the IPR.  The WG has already discussed and 
> chose to go ahead.
>
> RFC6090 is a normative reference for this document, pointing at the 
> signature algorithm to be used.  Any implementer would have to at 
> least check out RFC6090 and would find the text above in the Abstract.

I agree with Alvaro, with the caveat that it would be more than "too 
close"; it would be the same as taking a stance on validity.

It's the implementors problem to consider IPR issues even without a 
disclosure.

Thanks!

Ben.