IETF Logo Mail Archive

Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard

Steven Bellovin <smb@cs.columbia.edu> Fri, 27 January 2012 03:15 UTC

Return-Path: <smb@cs.columbia.edu>
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 CF4E121F864A for <ietf@ietfa.amsl.com>; Thu, 26 Jan 2012 19:15:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.43
X-Spam-Level:
X-Spam-Status: No, score=-5.43 tagged_above=-999 required=5 tests=[AWL=1.169, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 0Uy5KRN9r0nL for <ietf@ietfa.amsl.com>; Thu, 26 Jan 2012 19:15:24 -0800 (PST)
Received: from brinza.cc.columbia.edu (brinza.cc.columbia.edu [128.59.29.8]) by ietfa.amsl.com (Postfix) with ESMTP id B51F321F8646 for <ietf@ietf.org>; Thu, 26 Jan 2012 19:15:24 -0800 (PST)
Received: from [192.168.2.166] (74-92-112-54-Philadelphia.hfc.comcastbusiness.net [74.92.112.54]) (user=smb2132 mech=PLAIN bits=0) by brinza.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id q0R3FLaa020040 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 26 Jan 2012 22:15:21 -0500 (EST)
Subject: Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset="iso-8859-1"
From: Steven Bellovin <smb@cs.columbia.edu>
In-Reply-To: <CA+9kkMCR9RFjXg9nszOFSv1yMc3w2C9xzBYJ1zy+rv16uoudTg@mail.gmail.com>
Date: Thu, 26 Jan 2012 22:15:21 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <66BF157F-0BC3-44ED-8D77-D162C14A3CB3@cs.columbia.edu>
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> <CA+9kkMCR9RFjXg9nszOFSv1yMc3w2C9xzBYJ1zy+rv16uoudTg@mail.gmail.com>
To: Ted Hardie <ted.ietf@gmail.com>
X-Mailer: Apple Mail (2.1251.1)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.8
Cc: Barry Leiba <barryleiba@computer.org>, "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 03:15:25 -0000

On Jan 26, 2012, at 9:26 41PM, Ted Hardie wrote:

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


Yes, precisely.  This is spelled out quite explicitly in Sections 5.2 and 5.3
of RFC 3669, and Section 6.5 of 3979.

		--Steve Bellovin, https://www.cs.columbia.edu/~smb

v2.23.0 | Report a Bug | By Email