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

"Ben Campbell" <ben@nostrum.com> Wed, 29 June 2016 15:14 UTC

Return-Path: <ben@nostrum.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 E495712D1DA; Wed, 29 Jun 2016 08:14:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.326
X-Spam-Level:
X-Spam-Status: No, score=-3.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.426] 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 uCJ8mK1lRpXd; Wed, 29 Jun 2016 08:14:57 -0700 (PDT)
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 7310D12D11B; Wed, 29 Jun 2016 08:14:57 -0700 (PDT)
Received: from [10.0.1.4] (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 u5TFEhIo033848 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 29 Jun 2016 10:14:43 -0500 (CDT) (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.4]
From: Ben Campbell <ben@nostrum.com>
To: joel jaeggli <joelja@bogus.com>
Date: Wed, 29 Jun 2016 10:14:43 -0500
Message-ID: <7EA2AD9C-AD9C-45B4-AD5A-8FAC42FF4BAB@nostrum.com>
In-Reply-To: <6D691F17-34B0-40F8-8A49-6CE5F8D816E0@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>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
X-Mailer: MailMate (1.9.4r5234)
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/2yFaNBmVRHlB2C4sfTp_BIRwIp8>
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: Wed, 29 Jun 2016 15:15:00 -0000

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...

>
>
> 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
>>>>
>>>>
>>>>>
>>>