Re: [payload] Stephen Farrell's Discuss on draft-ietf-payload-rtp-h265-14: (with DISCUSS and COMMENT)

"Ben Campbell" <ben@nostrum.com> Sun, 06 September 2015 04:18 UTC

Return-Path: <ben@nostrum.com>
X-Original-To: payload@ietfa.amsl.com
Delivered-To: payload@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C6601B30CC for <payload@ietfa.amsl.com>; Sat, 5 Sep 2015 21:18:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=unavailable
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 ksfc_LRwKNkP for <payload@ietfa.amsl.com>; Sat, 5 Sep 2015 21:18:46 -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 CE38E1B3059 for <payload@ietf.org>; Sat, 5 Sep 2015 21:18:46 -0700 (PDT)
Received: from [10.0.1.23] (cpe-70-119-203-4.tx.res.rr.com [70.119.203.4]) (authenticated bits=0) by nostrum.com (8.15.2/8.14.9) with ESMTPSA id t864IOjN020454 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Sat, 5 Sep 2015 23:18:34 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-119-203-4.tx.res.rr.com [70.119.203.4] claimed to be [10.0.1.23]
From: Ben Campbell <ben@nostrum.com>
To: Roni Even <ron.even.tlv@gmail.com>
Date: Sat, 05 Sep 2015 23:18:23 -0500
Message-ID: <0529D407-785A-42ED-9828-32D25827FECF@nostrum.com>
In-Reply-To: <950B06A2-11B2-43CF-B9F3-CAD52BB4A58F@stewe.org>
References: <20150901124947.6862.19178.idtracker@ietfa.amsl.com> <1E1BD4D7-093D-4F44-81DE-8F9CF0F40572@stewe.org> <9ED14454-CCCC-4132-BC8A-47F3A1C2718A@nostrum.com> <01cc01d0e820$560c5270$0224f750$@gmail.com> <950B06A2-11B2-43CF-B9F3-CAD52BB4A58F@stewe.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.2r5107)
Archived-At: <http://mailarchive.ietf.org/arch/msg/payload/kKx99SCMdZbiZEZ9t6F38SAuJsY>
Cc: draft-ietf-payload-rtp-h265@ietf.org, payload-chairs@ietf.org, payload@ietf.org, The IESG <iesg@ietf.org>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [payload] Stephen Farrell's Discuss on draft-ietf-payload-rtp-h265-14: (with DISCUSS and COMMENT)
X-BeenThere: payload@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Payloads working group discussion list <payload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/payload>, <mailto:payload-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/payload/>
List-Post: <mailto:payload@ietf.org>
List-Help: <mailto:payload-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/payload>, <mailto:payload-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Sep 2015 04:18:48 -0000

Hi Roni,

It may have been buried in tall the emails, but my understanding is the 
Dec 2014 Nokia disclosure was an update of an earlier disclosure made 
against the pre-wg version of the draft. But because the tracker does 
not show payload-rtp-h265 as replacing the older version, it didn't 
apply the earlier discloser to the working group draft.

Ben.

On 5 Sep 2015, at 22:31, Stephan Wenger wrote:

> On 9/5/15, 14:17, "Roni Even" <ron.even.tlv@gmail.com> wrote:
>
>> Hi Stephan,
>> I am trying to remember but this Nokia IPR was submitted December 
>> 2014 after we sent the document to publication and we had two 
>> meetings since (Dallas and Prague). Was it discussed before on 
>> earlier version of the document?
>
> The Nokia IPR was discussed way earlier, probably around the Berlin 
> IETF.  Let me dig a bit...
> Stephan
>
>> Roni
>>
>> -----Original Message-----
>> From: payload [mailto:payload-bounces@ietf.org] On Behalf Of Ben 
>> Campbell
>> Sent: Saturday, September 05, 2015 1:05 AM
>> To: Stephan Wenger
>> Cc: draft-ietf-payload-rtp-h265@ietf.org; payload-chairs@ietf.org; 
>> The IESG; payload@ietf.org; Stephen Farrell
>> Subject: Re: [payload] Stephen Farrell's Discuss on 
>> draft-ietf-payload-rtp-h265-14: (with DISCUSS and COMMENT)
>>
>> On 4 Sep 2015, at 16:07, Stephan Wenger wrote:
>>
>>>> (2) This is just a process nit probably. The shepherd write-up
>>>> doesn't mention the Nokia IPR declaration.  Were the WG also ok 
>>>> with
>>>> that one? The write-up seems to pre-date that latest IPR 
>>>> declaration,
>>>> which is from a company that seems to employ one of the authors. 
>>>> That
>>>> is odd timing really so can someone explain the sequence of events
>>>> and why all is well?
>>>
>>>
>>> I will leave the chairs and Ben to sort this out.  However, I 
>>> remember
>>> quite clearly that I myself pointed out during IETF payload sessions
>>> the Nokia IPR at least once, including my understanding of the scope
>>> of protection and its limitation to certain optional modes of
>>> operation.  I don’t believe that these discussions were minuted, 
>>> but
>>> they probably can be found in audio records.  In other words, yes, 
>>> the
>>> Nokia IPR was raised in the WG, and in a level of detail rather
>>> uncommon for such discussions.  Really, no regular follower of the
>>> payload WG should be surprised of this.
>>
>> There's a separate discussion of the IPR issue (and that has turned 
>> up a QualComm disclosure that was showing in the tracker for the same 
>> reason the Nokia one did not.) My personal opinion is that we need to 
>> follow a higher standard than "people should be aware/not surprised"; 
>> we really explicit WG discussion about whether it wants to progress 
>> the draft in the face of a disclosure.
>>
>> That being said, do you know (or can you guess) which meeting might 
>> have an audio record of the discussion?
>>
>> Thanks!
>>
>> Ben.
>>
>> _______________________________________________
>> payload mailing list
>> payload@ietf.org
>> https://www.ietf.org/mailman/listinfo/payload
>>