Re: [Gen-art] Gen-ART LC review of draft-ietf-sieve-notify-sip-message-05.txt
Barry Leiba <barryleiba@computer.org> Mon, 26 September 2011 13:15 UTC
Return-Path: <barryleiba@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 995B421F8B4E for <gen-art@ietfa.amsl.com>; Mon, 26 Sep 2011 06:15:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.998
X-Spam-Level:
X-Spam-Status: No, score=-102.998 tagged_above=-999 required=5 tests=[AWL=-0.021, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 X6u0HxVIqdRm for <gen-art@ietfa.amsl.com>; Mon, 26 Sep 2011 06:15:08 -0700 (PDT)
Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by ietfa.amsl.com (Postfix) with ESMTP id 077F621F8B40 for <gen-art@ietf.org>; Mon, 26 Sep 2011 06:15:07 -0700 (PDT)
Received: by yic13 with SMTP id 13so5007447yic.31 for <gen-art@ietf.org>; Mon, 26 Sep 2011 06:17:50 -0700 (PDT)
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=Kndk9j11kXRTZxltK/zFfONtG+Fjhw75lS16soHUEts=; b=JJO//RBk8+2iyPaty2zF9J95qU2vjPUETQutnqCkcmSFv8tKLDaWujU+HHT7Z+1qMr vbDAkzXOxNHXO0F4jFcHnOQ5ZJ0FIai45CxpwxYkH2+FBdG3p7RlVFZ2qQ1vZx7WyMlN FtV6mHowGiLKd0Y4QJOPzupix/T6grf2qBffY=
MIME-Version: 1.0
Received: by 10.236.116.66 with SMTP id f42mr2694074yhh.111.1317043070566; Mon, 26 Sep 2011 06:17:50 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.236.42.198 with HTTP; Mon, 26 Sep 2011 06:17:50 -0700 (PDT)
In-Reply-To: <4E7FD84E.50801@gmail.com>
References: <4E7FD84E.50801@gmail.com>
Date: Mon, 26 Sep 2011 09:17:50 -0400
X-Google-Sender-Auth: ejGPLfxqJRhO3WS8Zx_5KzyyICY
Message-ID: <CALaySJLn-xCDD1cD1GX_B7mUzQUqJKyj7mzxg0m7yA6zrf-A-A@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: draft-ietf-sieve-notify-sip-message.all@tools.ietf.org, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-sieve-notify-sip-message-05.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Sep 2011 13:15:08 -0000
Thanks for the review, Brian. > I was briefly confused by Section 2.4. (Notify tag ":importance") > > It only mentions three possible values of "Priority" but RFC 3261 > mentions four (the extra one is "emergency") and states that > "additional values can be defined elsewhere." I think it should be > noted that the :importance tag can only express a subset of the SIP > Priority header semantics, and does not provide a separate category > for "when life, limb, or property are in imminent danger" [RFC3261]. Yes, that's a good point. New text: The ":importance" tag is intended to convey the importance of the SIP MESSAGE notification, not the importance of the email message that generated the notification. The value of the ":importance" tag MAY, therefore, be transformed into SIP "Priority" header field (in addition to or instead of including it in the body of the message). Note that because the Sieve ":importance" tag only has three values, not all SIP "Priority" values can be represented in the transformation. If this transformation is done, the value of the "Priority" header field MUST be "urgent" if the value of the ":importance" tag is "1", "normal" if the value of the ":importance" tag is "2", and "non-urgent" if the value of the ":importance" tag is "3". There is no mapping to the SIP value "emergency", nor to any additional values that might be defined. Does that work? Barry
- [Gen-art] Gen-ART LC review of draft-ietf-sieve-n… Brian E Carpenter
- Re: [Gen-art] Gen-ART LC review of draft-ietf-sie… Barry Leiba
- Re: [Gen-art] Gen-ART LC review of draft-ietf-sie… Brian E Carpenter