Re: [sieve] I-D Action: draft-ietf-sieve-notify-sip-message-05.txt
Peter Saint-Andre <stpeter@stpeter.im> Fri, 09 September 2011 22:21 UTC
Return-Path: <stpeter@stpeter.im>
X-Original-To: sieve@ietfa.amsl.com
Delivered-To: sieve@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3973921F888A for <sieve@ietfa.amsl.com>; Fri, 9 Sep 2011 15:21:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.545
X-Spam-Level:
X-Spam-Status: No, score=-102.545 tagged_above=-999 required=5 tests=[AWL=0.054, BAYES_00=-2.599, 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 2Hlo3VwMptaY for <sieve@ietfa.amsl.com>; Fri, 9 Sep 2011 15:21:41 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 58BF721F8564 for <sieve@ietf.org>; Fri, 9 Sep 2011 15:21:37 -0700 (PDT)
Received: from dhcp-64-101-72-178.cisco.com (unknown [64.101.72.178]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 5422A41965 for <sieve@ietf.org>; Fri, 9 Sep 2011 16:26:36 -0600 (MDT)
Message-ID: <4E6A91E4.90402@stpeter.im>
Date: Fri, 09 Sep 2011 16:23:32 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:6.0.2) Gecko/20110902 Thunderbird/6.0.2
MIME-Version: 1.0
To: sieve@ietf.org
References: <20110907162019.5836.10120.idtracker@ietfa.amsl.com>
In-Reply-To: <20110907162019.5836.10120.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.3.1
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Subject: Re: [sieve] I-D Action: draft-ietf-sieve-notify-sip-message-05.txt
X-BeenThere: sieve@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIEVE Working Group <sieve.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sieve>, <mailto:sieve-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sieve>
List-Post: <mailto:sieve@ietf.org>
List-Help: <mailto:sieve-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sieve>, <mailto:sieve-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Sep 2011 22:21:42 -0000
On 9/7/11 10:20 AM, internet-drafts@ietf.org wrote: > Title : Sieve Notification Mechanism: SIP MESSAGE Some quick feedback. Please expand "SIP" on first mention. Section 2.7 states: Because it is impossible to tell in advance whether the notification recipient is online and able to receive a SIP MESSAGE... What about SIP presence (RFC 3856)? Perhaps Because (absent use of SIP extensions such as [RFC3856]) it is impossible to tell in advance whether the notification recipient is online and able to receive a SIP MESSAGE... Section 5 states: User agents that support the SIP MESSAGE request MUST implement end- to-end authentication, body integrity, and body confidentiality mechanisms. As I understand it, that "MUST" actually is specified in RFC 3428, so you might say: As required by [RFC3428], user agents that support the SIP MESSAGE request MUST implement end-to-end authentication, body integrity, and body confidentiality mechanisms. That will make it clear to readers that this specification is not describing a special usage of SIP message. In Section 7, "draft-ietf-sieve-notify-xmpp" is RFC 5437. Peter -- Peter Saint-Andre https://stpeter.im/
- [sieve] I-D Action: draft-ietf-sieve-notify-sip-m… internet-drafts
- Re: [sieve] I-D Action: draft-ietf-sieve-notify-s… Peter Saint-Andre
- Re: [sieve] I-D Action: draft-ietf-sieve-notify-s… Barry Leiba