RE: WG adoption poll on draft-nitish-vrrp-bfd-04

"Adrian Farrel" <adrian@olddog.co.uk> Wed, 26 October 2016 14:20 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5B4D129424; Wed, 26 Oct 2016 07:20:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level:
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] 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 5g_xKyPzYdE9; Wed, 26 Oct 2016 07:20:39 -0700 (PDT)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC0D0129408; Wed, 26 Oct 2016 07:20:15 -0700 (PDT)
Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id u9QEKDRd008275; Wed, 26 Oct 2016 15:20:13 +0100
Received: from 950129200 (28.200.114.87.dyn.plus.net [87.114.200.28]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id u9QEKCEq008250 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Wed, 26 Oct 2016 15:20:12 +0100
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Chris Bowers' <cbowers@juniper.net>, rtgwg@ietf.org, rtg-bfd@ietf.org
References: <MWHPR05MB2829CF8AB32089C947BA4214A9D50@MWHPR05MB2829.namprd05.prod.outlook.com>
In-Reply-To: <MWHPR05MB2829CF8AB32089C947BA4214A9D50@MWHPR05MB2829.namprd05.prod.outlook.com>
Subject: RE: WG adoption poll on draft-nitish-vrrp-bfd-04
Date: Wed, 26 Oct 2016 15:20:11 +0100
Message-ID: <060701d22f94$10b924c0$322b6e40$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0608_01D22F9C.7280E820"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGnKxm+PXIVrKQ0rMfiARCN/F3hL6EQyG1g
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.0.0.1202-22660.007
X-TM-AS-Result: No--23.997-10.0-31-10
X-imss-scan-details: No--23.997-10.0-31-10
X-TMASE-MatchedRID: 8HTFlOrbAtHtvMVN/9JMyp21GZGE81yG0nXvwjW2mSUumgtCQEXZ/iNo hHesUr2QAVEk3tTMpwrUe7Xjz/r6oVYpd80WgN/vW7gz/Gbgpl7/47RIpeE+V9hMNz5U8DsXVri cCR5WSm7IGW1PL4tUh1Dd7rA7JoFaqAn9Dm/i+2LCu3097eieeQ0YtI32OoC9tOtpvXS6qufAkt gDJtZ0AlnK4RQsIpEwteG0FggWc3wLW2bI+DYY7HBRIrj8R47FKau5fqTELpP9k2xa9Ahjg9OGj ZUqGWjEJmLqKu2yqdltE63XdtkUOBGRuqAmkM32CFaAixm5eU/YP0VsOD0E/mjliw+xvItd8f7Q ZtEXuwZKwuG29285VRXCSMTtleITT09fC9Tx663N+qWlu2ZxaPT3/K+ej/DoyPRAwD/3abacQzA jFyPGDdFChERArRPnHjXpWy/tu9EIBUYrvxGmwnlMlWV+Ir670vNkFv6xUCNdKWx22BOmiagTPH jMLlQl4FD3otNxTUP5ceH/IIsL8Nq72IXmYAV7qbg9uWhLYLcZO8jjfdepCV+lV1+J0TE3svEAl cZZFUUA10+0811gl0DpZ5A9hUaeaaqmAEPiermdVNZaI2n6/56KYa03LCO2dDwP5ItpCOxLVOP6 Sq/6Gw7G7azt901XixYJ8/oaa/l1tKCSzroCgY9URkDgdlb5/RmmEswf7IeiXe5nNnUYt6BKM62 rmx9p8eoBfgDeEI7gXuUEZiH4rz8G3G/wjVDpcLw8nYQVLsggFyxci4S+VuRnWbJNcqgXKqHlxT J7eJUibp8py4XIryhHQrcMnybC1lfDCm9+EZWeAiCmPx4NwGmRqNBHmBvevqq8s2MNhPDPPeN6H N6d7EPs5Q2GDC4G87FVmBw+ImN/ksjZjIeNENXIIUu7h2kzAU+xImx6jwfNsFAqgvAzug==
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/_Riw4Q7ghAj_L8TOozThTeLrRXg>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Oct 2016 14:20:44 -0000

It might (or might not :-) help if I give some clarification of my position on
this draft.
[I'm not trying to tell the chairs how to do their job!]
 
We are not in a position at the moment to make our own individual assessments of
whether or how the disclosed IPR covers the draft. This is because we cannot yet
see the content of the IPR filed in the disclosed application. That means we can
take one of two approaches:
 
1. Assume that the IPR covers a substantial portion of the draft
2. Wait and see
 
In the first case we have to decide whether we want to go ahead with this work
on that assumption and in the knowledge of the licensing terms. The alternatives
are:
a. Abandon the work
b. Re-invent the solution to avoid the IPR (which necessarily involves waiting
until we can read it)
c. Carry on regardless deciding that we are willing to live with the disclosure
 
In the second case we would delay progression until we can see the IPR and
decide what to do. The alternative would then be exactly the same a, b, and c as
above.
 
It might be pragmatic to continue to work on the current draft. That work could
happen without adoption (lack of adoption is not reason not to work on the
draft, and the unadopted draft can still be "under the care of the WG") or could
include adoption. If the draft is adopted, however, I would be very wary of the
implied momentum: that is, when the WG has been working on the draft for a while
it must not be taken to imply that any consensus was reached with respect to the
IPR and it must be understood that the discussion was deferred not concluded.
Future arguments that "we have invested so much time and effort" will not carry
water!
 
All that considered, I would be OK to see work continue on the document pending
availability of the IPR in the hope that when we can see the IPR we will attempt
to find a solution that avoids the IPR.
 
Cheers,
Adrian
 
 
From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Chris Bowers
Sent: 20 October 2016 16:11
To: rtgwg@ietf.org; rtg-bfd@ietf.org
Subject: RE: WG adoption poll on draft-nitish-vrrp-bfd-04
 
RTGWG,
 
At this point, I don't think that there is a consensus for the working group to
adopt this draft 
without more discussion of the issue raised by Loa Andersson and Adrian Farrel
in the
following two emails.
 
https://www.ietf.org/mail-archive/web/rtgwg/current/msg05712.html
https://www.ietf.org/mail-archive/web/rtgwg/current/msg05718.html
 
The main objection raised in these two emails is that the working group should
work on 
solutions that are either unencumbered by IPR or that are available on
free-to-implementers
terms.   Loa and Adrian also point out that the current lack of visibility to
the patent 
application covered by the IPR disclosure for this draft means that it is
currently not possible to 
evaluate this situation with respect to this draft.
 
The reason for the IPR disclosure process is to allow working groups to take
into consideration
the potential licensing of IPR when evaluating alternative technical solutions.
At this point, 
adopting draft-nitish-vrrp-bfd-04 as the basis for work on standardizing the use
of VRRP 
with BFD without more discussion of this issue would imply that there is
consensus that 
the working group should not take potential licensing of IPR into account for
this work.
I don't think there is currently consensus for this.
 
I encourage further discussion of this issue. I think that there may be the
potential to
reach a consensus if the working group can come to an explicit agreement about
whether
or not potential licensing of IPR should be taken into account when evaluating
alternative 
technologies for this work.
 
Chris
 
_____________________________________________
From: Chris Bowers 
Sent: Thursday, September 29, 2016 10:44 AM
To: 'rtgwg@ietf.org' <rtgwg@ietf.org>; rtg-bfd@ietf.org
Subject: WG adoption poll on draft-nitish-vrrp-bfd-04
 
 
RTGWG,
 
This email starts a two week poll to gauge consensus on adopting
draft-nitish-vrrp-bfd-04
as an RTGWG working group document.
 
The BFD working group is also copied on this adoption poll.  We encourage
participants in 
BFD working group to provide their input on the adoption poll.  And should this
document
be adopted as an RTGWG document, we would plan to copy the BFD WG on emails 
related to this document to benefit from the BFD expertise in that WG in the
development 
of this document.
 
Please send your comments to the RTGWG mailing list ( <mailto:rtgwg@ietf.org>
rtgwg@ietf.org) indicating support 
or opposition to the adoption of this document, along with the reasoning for
that support
or opposition.  
 
If you are listed as a document author or contributor, please respond to this
email stating
whether or not you are aware of any relevant IPR.   The response needs to be
sent to the 
RTGWG mailing list. The document will not advance to the next stage until a
response has
been received from each author and each individual that has contributed to the
document.
 
At this point, the document has the following IPR disclosure associated with it.
 <https://datatracker.ietf.org/ipr/2739/> https://datatracker.ietf.org/ipr/2739/
 
This adoption poll will end on Friday October 14th.
 
Thanks,
Chris and Jeff