Re: [alto] Ben Campbell's No Objection on draft-ietf-alto-deployments-15: (with COMMENT)

joel jaeggli <joelja@bogus.com> Thu, 30 June 2016 04:12 UTC

Return-Path: <joelja@bogus.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E95B12D0A8; Wed, 29 Jun 2016 21:12:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.326
X-Spam-Level:
X-Spam-Status: No, score=-8.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426] 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 ldVGGieAbtiQ; Wed, 29 Jun 2016 21:12:12 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (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 5A11F12B00E; Wed, 29 Jun 2016 21:12:12 -0700 (PDT)
Received: from mb-2.local ([IPv6:2601:647:4201:9e61:599:6d6a:ecc7:18ed]) (authenticated bits=0) by nagasaki.bogus.com (8.15.2/8.15.2) with ESMTPSA id u5U4Bpgw061183 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Thu, 30 Jun 2016 04:11:52 GMT (envelope-from joelja@bogus.com)
X-Authentication-Warning: nagasaki.bogus.com: Host [IPv6:2601:647:4201:9e61:599:6d6a:ecc7:18ed] claimed to be mb-2.local
To: Ben Campbell <ben@nostrum.com>
References: <20160629024848.22461.52600.idtracker@ietfa.amsl.com> <20e0e953-57a1-a340-bcc2-c835541876d0@bogus.com> <77297E9E-4BB9-404E-9AFD-A54A204C366C@nostrum.com> <2d8046d5-84d7-0b13-6c99-f24b73d8a857@bogus.com> <6D691F17-34B0-40F8-8A49-6CE5F8D816E0@nostrum.com> <7EA2AD9C-AD9C-45B4-AD5A-8FAC42FF4BAB@nostrum.com> <e78ed4cd-df74-784f-ec8f-79d3ddadc668@bogus.com> <2686735A-4E63-4631-BD11-7E6D6DF1832F@nostrum.com>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <9a2a93fb-a929-ca4d-031c-f8c3ebb06f4f@bogus.com>
Date: Wed, 29 Jun 2016 21:11:50 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:47.0) Gecko/20100101 Thunderbird/47.0
MIME-Version: 1.0
In-Reply-To: <2686735A-4E63-4631-BD11-7E6D6DF1832F@nostrum.com>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="lBVPJXUM9ImUtdA4CDn5pNlsQVTDepeKj"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/Z3cKU2iTvB5Ni8y86E-5iIpESgM>
Cc: alto@ietf.org, mls.ietf@gmail.com, The IESG <iesg@ietf.org>, draft-ietf-alto-deployments@ietf.org, alto-chairs@ietf.org
Subject: Re: [alto] Ben Campbell's No Objection on draft-ietf-alto-deployments-15: (with COMMENT)
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/alto/>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2016 04:12:14 -0000

On 6/29/16 9:28 AM, Ben Campbell wrote:
> On 29 Jun 2016, at 10:57, joel jaeggli wrote:
> 
>> On 6/29/16 8:14 AM, Ben Campbell wrote:
>>> On 29 Jun 2016, at 10:08, Ben Campbell wrote:
>>>
>>>> On 29 Jun 2016, at 1:22, joel jaeggli wrote:
>>>>
>>>>> On 6/28/16 11:14 PM, Ben Campbell wrote:
>>>>>> On 29 Jun 2016, at 0:59, joel jaeggli wrote:
>>>>>>
>>>>>>> On 6/28/16 7:48 PM, Ben Campbell wrote:
>>>>>>>> Ben Campbell has entered the following ballot position for
>>>>>>>> draft-ietf-alto-deployments-15: No Objection
>>>>>>>>
>>>>>>>> When responding, please keep the subject line intact and reply
>>>>>>>> to all
>>>>>>>> email addresses included in the To and CC lines. (Feel free to cut
>>>>>>>> this
>>>>>>>> introductory paragraph, however.)
>>>>>>>>
>>>>>>>>
>>>>>>>> Please refer to
>>>>>>>> https://www.ietf.org/iesg/statement/discuss-criteria.html
>>>>>>>> for more information about IESG DISCUSS and COMMENT positions.
>>>>>>>>
>>>>>>>>
>>>>>>>> The document, along with other ballot positions, can be found here:
>>>>>>>> https://datatracker.ietf.org/doc/draft-ietf-alto-deployments/
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ----------------------------------------------------------------------
>>>>>>>>
>>>>>>>>
>>>>>>>> COMMENT:
>>>>>>>> ----------------------------------------------------------------------
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> There's a 2 day old (at the time of this writing) IPR
>>>>>>>> disclosure. It
>>>>>>>> seems rather unusual, and I am not sure of the intent.
>>>>>>>
>>>>>>> they are third party ipr declarations and they are in fact the
>>>>>>> product
>>>>>>> of reviewing the document:
>>>>>>>
>>>>>>> from the review of cpignata@cisco.com Carlos Pignataro.
>>>>>>>
>>>>>>> Major:
>>>>>>>
>>>>>>> 1. I came across two patent applications in which the examiners add
>>>>>>> this
>>>>>>> document as a non-patent citation. The document has no IPR
>>>>>>> disclosures,
>>>>>>> and authors seem to have responded to IPR calls.
>>>>>>
>>>>>> There lies my confusion. Why would a patent application that cites
>>>>>> this
>>>>>> document cause an IPR disclosure against this document? Seems
>>>>>> backwards
>>>>>> to me.
>>>>>
>>>>> https://tools.ietf.org/html/rfc3979#page-9
>>>>>
>>>>> 6.1.3.  IPR of Others
>>>>>
>>>>>    If a person has information about IPR that may Cover IETF
>>>>>    Contributions, but the participant is not required to disclose
>>>>>    because they do not meet the criteria in Section 6.6 (e.g., the IPR
>>>>>    is owned by some other company), such person is encouraged to
>>>>> notify
>>>>>    the IETF by sending an email message to ietf-ipr@ietf.org.  Such a
>>>>>    notice should be sent as soon as reasonably possible after the
>>>>> person
>>>>>    realizes the connection.
>>>>>
>>>>>
>>>>
>>>> Sorry, my confusion is not the fact this is a 3rd party disclosure.
>>>> It's more that the fact being disclosed seems to be that a third party
>>>> patent application cites this document. Maybe I am misreading
>>>> something, but based strictly on the information in the disclosure,
>>>> that doesn't seem to imply a third party has IPR that may encumber the
>>>> draft; rather it seem to imply that may build on top of this draft.
>>>
>>> grumble. I can't seem to type this morning.
>>>
>>> s/... imply that may build.../... imply that the IPR may build...
>>
>> It's not our job to judge the validity or applicability of ipr claims on
>> material.
>>
>> You can draw your own conclusions as an individual.
>>
>> I think it's responsible of the person engaging in third party
>> disclosure to have done so. that's about the only conclusion I would
>> draw.
>>
>>
> 
> I wasn't trying to judge the applicability so much as the intent, but I
> take your point. My real concern at this point is that the working group
> has the opportunity to decide how to proceed.

yeah, I think that applies to any form of late breaking change of
significance.

> 
>>>>
>>>>
>>>> That all being said, this disclosure came in after IETF last call. I'd
>>>> be very surprised if the working group was aware of it when they
>>>> progressed the draft.
>>>>
>>>>>
>>>>>>>
>>>>>>> I will submit 3rd party disclosures for these now, there may be
>>>>>>> more:
>>>>>>> http://www.google.com/patents/EP2913979A1#npl-citations
>>>>>>> http://www.google.com/patents/WO2016039798A1#npl-citations
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>
>>>
>