Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard
Ted Hardie <ted.ietf@gmail.com> Fri, 27 January 2012 02:26 UTC
Return-Path: <ted.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D80C421F86F0 for <ietf@ietfa.amsl.com>; Thu, 26 Jan 2012 18:26:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.434
X-Spam-Level:
X-Spam-Status: No, score=-3.434 tagged_above=-999 required=5 tests=[AWL=0.165, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Uj-mzTqmfhn2 for <ietf@ietfa.amsl.com>; Thu, 26 Jan 2012 18:26:42 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id D3D5A21F86EB for <ietf@ietf.org>; Thu, 26 Jan 2012 18:26:41 -0800 (PST)
Received: by yhnn12 with SMTP id n12so642311yhn.31 for <ietf@ietf.org>; Thu, 26 Jan 2012 18:26:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=T4s0oBX7thyfSJ9VSgvcPrnwPvS8g+kV8et6vtx6DRw=; b=ZZ7ZdJJcpbL7BfcMknuBEwcKU6+0+juLVzTkjSzCGlBZ7DKP5/nlC3cuFrPAPvpWRk 56JtP9UrpHynqNZ/83z1uGBe/Bsv3LL68ijcsOZKeplF3/akVpNa2tZUi9uMQLsiZ24e Mnkevy0tidrz5MjqOPcxrUwbMSgY4Jx13rZxc=
MIME-Version: 1.0
Received: by 10.236.154.232 with SMTP id h68mr7369602yhk.51.1327631201313; Thu, 26 Jan 2012 18:26:41 -0800 (PST)
Received: by 10.236.180.230 with HTTP; Thu, 26 Jan 2012 18:26:41 -0800 (PST)
In-Reply-To: <CAC4RtVBfe5G=eEotH3gceVCm9grc7qxCT1siykbF+cHeNdArxA@mail.gmail.com>
References: <20120125201714.3903.82295.idtracker@ietfa.amsl.com> <4F2075BE.5070201@nostrum.com> <033901ccdbab$6bae0900$430a1b00$@olddog.co.uk> <CD5674C3CD99574EBA7432465FC13C1B226F573BC9@DC-US1MBEX4.global.avaya.com> <4F208AEF.5060406@qualcomm.com> <CD5674C3CD99574EBA7432465FC13C1B226F573BCE@DC-US1MBEX4.global.avaya.com> <4F21ABF2.7040002@qualcomm.com> <6842.1327617385@marajade.sandelman.ca> <F5833273385BB34F99288B3648C4F06F19C9A7D9F5@EXCH-C2.corp.cloudmark.com> <CAC4RtVBfe5G=eEotH3gceVCm9grc7qxCT1siykbF+cHeNdArxA@mail.gmail.com>
Date: Thu, 26 Jan 2012 18:26:41 -0800
Message-ID: <CA+9kkMCR9RFjXg9nszOFSv1yMc3w2C9xzBYJ1zy+rv16uoudTg@mail.gmail.com>
Subject: Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard
From: Ted Hardie <ted.ietf@gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jan 2012 02:26:43 -0000
On Thu, Jan 26, 2012 at 5:50 PM, Barry Leiba <barryleiba@computer.org> wrote: > I am not a lawyer, but I don't think the license terms are at issue > here. As I understand it, the terms that Huawei has been specifying > in its disclosures are defensive, and shouldn't restrict standards > implementations. The issue we're discussing isn't the terms, but that > the disclosures weren't made when they should have been. > While I appreciate the recitation of unfortunate events that led us here, I don't quite share the view that the license terms are not at issue here. The reason that we have an IPR rule that asks us to declare what the terms of a license are is so that the working groups' members can evaluate both the applicability of the potentially encumbering patents and the terms of the license. The later those are made clear, the harder it is for the working group. It may have to abandon a lot of work at a late stage, which is difficult if deadlines are looming or, worse, code has been shipped. A license which was an outright grant would have no impact on that, so the lack of timely disclosure has a smaller overall impact. It's still bad form, but not really more. For a royalty-bearing license, there is an obvious cost; for a defensive license, there is a less obvious, but potentially real, cost. If example.com sues Huawei for any reason, they lose this license and can no longer use the technology the WG agreed to standardize with purchasing a FRAND license on the other (less-specified) terms. I have no advice on this particular case, but the general point seems to me important. regards, Ted
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Adam Roach
- RE: Second Last Call: <draft-ietf-sieve-notify-si… Adrian Farrel
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Peter Saint-Andre
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Thomas Nadeau
- Re: Second Last Call: <draft-ietf-sieve-notify-si… SM
- RE: Second Last Call: <draft-ietf-sieve-notify-si… Worley, Dale R (Dale)
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Peter Saint-Andre
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Pete Resnick
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Pete Resnick
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Adam Roach
- Violation of IETF process (was: Second Last Call:… SM
- RE: Violation of IETF process (was: Second Last C… Adrian Farrel
- Re: [sieve] Second Last Call: <draft-ietf-sieve-n… Dave CROCKER
- RE: Violation of IETF process (was: Second Last C… SM
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Dave Cridland
- Re: Second Last Call: <draft-ietf-sieve-notify-si… John C Klensin
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Harald Alvestrand
- Re: [sieve] Second Last Call: <draft-ietf-sieve-n… Bob Hinden
- Re: Second Last Call: <draft-ietf-sieve-notify-si… John C Klensin
- RE: Second Last Call: <draft-ietf-sieve-notify-si… Murray S. Kucherawy
- RE: Violation of IETF process (was: Second Last C… Murray S. Kucherawy
- RE: Second Last Call: <draft-ietf-sieve-notify-si… Murray S. Kucherawy
- RE: Second Last Call: <draft-ietf-sieve-notify-si… Murray S. Kucherawy
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Pete Resnick
- Re: Second Last Call: <draft-ietf-sieve-notify-si… SM
- Re: Second Last Call: <draft-ietf-sieve-notify-si… John C Klensin
- encouraging compliance with IPR disclosure rules Peter Saint-Andre
- RE: Second Last Call: <draft-ietf-sieve-notify-si… Worley, Dale R (Dale)
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Pete Resnick
- Re: encouraging compliance with IPR disclosure ru… SM
- Re: Violation of IETF process todd glassey
- Re: Second Last Call: <draft-ietf-sieve-notify-si… todd glassey
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Kevin P. Fleming
- Re: Second Last Call: <draft-ietf-sieve-notify-si… SM
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Martin Rex
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Cyrus Daboo
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Cyrus Daboo
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Michael Richardson
- RE: Second Last Call: <draft-ietf-sieve-notify-si… Murray S. Kucherawy
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Hector
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Pete Resnick
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Barry Leiba
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Ted Hardie
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Steven Bellovin
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Barry Leiba
- Re: Second Last Call: <draft-ietf-sieve-notify-si… SM
- RE: Second Last Call: <draft-ietf-sieve-notify-si… Murray S. Kucherawy
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Hector Santos
- Re: Second Last Call: <draft-ietf-sieve-notify-si… t.petch
- Re: [sieve] Second Last Call: <draft-ietf-sieve-n… Arnt Gulbrandsen
- Re: encouraging compliance with IPR disclosure ru… Polk, William T.
- Re: encouraging compliance with IPR disclosure ru… Scott Brim
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Dave CROCKER
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Alexey Melnikov
- Re: encouraging compliance with IPR disclosure ru… todd glassey