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

Arnt Gulbrandsen <arnt@gulbrandsen.priv.no> Fri, 27 January 2012 08:01 UTC

Return-Path: <arnt@gulbrandsen.priv.no>
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 B212B21F8525; Fri, 27 Jan 2012 00:01:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 n26Aco2nP5vP; Fri, 27 Jan 2012 00:01:28 -0800 (PST)
Received: from strange.aox.org (strange.aox.org [80.244.248.170]) by ietfa.amsl.com (Postfix) with ESMTP id C18A521F8522; Fri, 27 Jan 2012 00:01:28 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (unknown [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 49D96F8C438; Fri, 27 Jan 2012 08:01:26 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.1.4) with esmtpsa id 1327651285-609-608/10/10; Fri, 27 Jan 2012 08:01:25 +0000
Message-Id: <4F2259D5.5010805@gulbrandsen.priv.no>
Date: Fri, 27 Jan 2012 09:01:25 +0100
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0) Gecko/20111229 Thunderbird/9.0
Mime-Version: 1.0
To: ietf@ietf.org, sieve@ietf.org
Subject: Re: [sieve] Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notifica tion Mechanism: SIP MESSAGE) to Proposed Standard
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> <9E8747DFE73501D34065351E@PST.JCK.COM> <4F217A7C.6080908@qualcomm.com>
In-Reply-To: <4F217A7C.6080908@qualcomm.com>
Content-Type: text/plain; charset="iso-8859-1"
X-Mailman-Approved-At: Fri, 27 Jan 2012 08:18:43 -0800
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 08:01:29 -0000

Pete Resnick wrote:
> We were told by the other company employees who facilitated the
> disclosures, at the time of the disclosures, that this was strictly an
> individual's failure to comply with the IETF IPR Policy, that the author
> in question claims not to have understood the IETF IPR Policy, and that
> the company proceeded to make these disclosures as soon as it discovered
> that this IPR existed. I have no information to contradict that claim.

Barry also said that company procedures have been improved to prevent
this particular type of failure in the future.

Speaking as Sieve WG member and sieve developer, I'm in favour of
treating this as a mishap (albeit a bad one), not an attempt at deception.

Arnt