Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard
Barry Leiba <barryleiba@computer.org> Fri, 27 January 2012 03:28 UTC
Return-Path: <barryleiba@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 74A6C21F85DD for <ietf@ietfa.amsl.com>; Thu, 26 Jan 2012 19:28:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.632
X-Spam-Level:
X-Spam-Status: No, score=-102.632 tagged_above=-999 required=5 tests=[AWL=-0.256, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_31=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 XMpzHome7FlF for <ietf@ietfa.amsl.com>; Thu, 26 Jan 2012 19:28:38 -0800 (PST)
Received: from mail-tul01m020-f172.google.com (mail-tul01m020-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 02A9D21F85D8 for <ietf@ietf.org>; Thu, 26 Jan 2012 19:28:37 -0800 (PST)
Received: by obbwc12 with SMTP id wc12so1516791obb.31 for <ietf@ietf.org>; Thu, 26 Jan 2012 19:28:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=6xsqdJ4FnhnPzmn45IWMMFO5S/TzX7NEqZLJ7bVuqFo=; b=jmudYJBnkpiI8yGJ4fa9FGuFpFvcZ/GDDfyAc5LGt2ekrwmSoYlPTPD/5TFXfNEsMI iAd5cGuuBW6MOzoSmGa13qhy7yZipXP4ANorQAXdwIQ6OX5LZXyZpuG7DYY6y/1EFqi7 RGAfjZB3OUrJ7BCSxtFxuULj2U0eLQtN3Ir9s=
MIME-Version: 1.0
Received: by 10.182.121.101 with SMTP id lj5mr4773169obb.39.1327634917674; Thu, 26 Jan 2012 19:28:37 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.60.55.137 with HTTP; Thu, 26 Jan 2012 19:28:37 -0800 (PST)
In-Reply-To: <CA+9kkMCR9RFjXg9nszOFSv1yMc3w2C9xzBYJ1zy+rv16uoudTg@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> <CA+9kkMCR9RFjXg9nszOFSv1yMc3w2C9xzBYJ1zy+rv16uoudTg@mail.gmail.com>
Date: Thu, 26 Jan 2012 22:28:37 -0500
X-Google-Sender-Auth: K2IhPC9AqsvINh9Vu2ipl8Y7NMY
Message-ID: <CALaySJKCe1KFYL-Xu+Ssb-NHgQ8+htWCTtN+wM9Nqnvq9NeBDw@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: Barry Leiba <barryleiba@computer.org>
To: Ted Hardie <ted.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="14dae93998f7a8d07a04b77a17de"
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 03:28:38 -0000
> 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, sorry: I was conflating this thread with the other one(s?) that are specifically looking at how to address the late disclosures (for which the issue really is how to deal with the failure to disclose, regardless of the terms eventually offered). This thread is about the Sieve documents in question, so, yes, you're right that the terms are relevant. I hadn't meant to say we shouldn't think about that with respect to the two Sieve documents. Barry
- 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