Re: Brian Haberman's No Objection on draft-ietf-bfd-rfc5884-clarifications-03: (with COMMENT)

Brian Haberman <brian@innovationslab.net> Wed, 14 October 2015 15:26 UTC

Return-Path: <brian@innovationslab.net>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AD181A916C; Wed, 14 Oct 2015 08:26:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 Ul6eKrEADtQj; Wed, 14 Oct 2015 08:26:39 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12B171A9007; Wed, 14 Oct 2015 08:26:39 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id E6843880F5; Wed, 14 Oct 2015 08:26:38 -0700 (PDT)
Received: from clemson.jhuapl.edu (swifi-nat.jhuapl.edu [128.244.87.133]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id CB3F2328081A; Wed, 14 Oct 2015 08:26:37 -0700 (PDT)
Subject: Re: Brian Haberman's No Objection on draft-ietf-bfd-rfc5884-clarifications-03: (with COMMENT)
To: Jeffrey Haas <jhaas@pfrc.org>
References: <20151014143827.30440.78575.idtracker@ietfa.amsl.com> <20151014144523.GA28921@pfrc.org> <561E6C57.5010709@innovationslab.net> <20151014151703.GC28921@pfrc.org>
From: Brian Haberman <brian@innovationslab.net>
Message-ID: <561E7427.5050307@innovationslab.net>
Date: Wed, 14 Oct 2015 11:26:31 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <20151014151703.GC28921@pfrc.org>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="Uk7WibpX8MaopvkWjM1KtRoOMwTWAsCe9"
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-bfd/MPVt9HwRtuU7TEdRUIz2EsBGecY>
Cc: draft-ietf-bfd-rfc5884-clarifications@ietf.org, The IESG <iesg@ietf.org>, bfd-chairs@ietf.org, rtg-bfd@ietf.org
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-bfd/>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Oct 2015 15:26:40 -0000


On 10/14/15 11:17 AM, Jeffrey Haas wrote:
> On Wed, Oct 14, 2015 at 10:53:11AM -0400, Brian Haberman wrote:
>> On 10/14/15 10:45 AM, Jeffrey Haas wrote:
>>> On Wed, Oct 14, 2015 at 07:38:27AM -0700, Brian Haberman wrote:
>>>> ----------------------------------------------------------------------
>>>> COMMENT:
>>>> ----------------------------------------------------------------------
>>>>
>>>> Just a question on this draft... Given its status as clarifying (and
>>>> updating) RFC 5884, does it also inherit any of the IPR claims levied
>>>> against RFC 5884?
>>>>
>>>
>>> All existing IPR stands.  No new IPR is introduced.
>>
>> Maybe my parser is broken, but does this mean:
>>
>> 1. None of the IPR disclosures filed against 5884 apply to this draft
>>
>> 2. All/some of the IPR disclosures filed against 5884 apply, but
>> disclosures have not (will not?) be filed against this draft?
> 
> Since this document only clarifies 5884, the IPR against 5884 is still
> applicable.  The clarifications do not introduce any new IPR against the
> material covered in 5884.

I wasn't expecting new IPR, I was wondering if any of the old IPR may
have gone away.  I know, wishful thinking.

> 
> A bit more flippantly, just because we publish a clarification document with
> no additional IPR doesn't mean we think we're getting rid of the existing
> IPR considerations. :-)

I have seen it happen before though and was wondering.

Thanks for the quick follow-up!

Brian