[salud] Normative change to proxy behavior

worley@ariadne.com (Dale R. Worley) Fri, 16 May 2014 22:00 UTC

Return-Path: <worley@ariadne.com>
X-Original-To: salud@ietfa.amsl.com
Delivered-To: salud@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76F081A0218 for <salud@ietfa.amsl.com>; Fri, 16 May 2014 15:00:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MJlAoytuIXrB for <salud@ietfa.amsl.com>; Fri, 16 May 2014 15:00:04 -0700 (PDT)
Received: from qmta10.westchester.pa.mail.comcast.net (qmta10.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:17]) by ietfa.amsl.com (Postfix) with ESMTP id 2427C1A0191 for <salud@ietf.org>; Fri, 16 May 2014 15:00:04 -0700 (PDT)
Received: from omta04.westchester.pa.mail.comcast.net ([76.96.62.35]) by qmta10.westchester.pa.mail.comcast.net with comcast id 2loU1o0060ldTLk5Alzwo9; Fri, 16 May 2014 21:59:56 +0000
Received: from hobgoblin.ariadne.com ([24.34.72.61]) by omta04.westchester.pa.mail.comcast.net with comcast id 2lzv1o00k1KKtkw01lzw2k; Fri, 16 May 2014 21:59:56 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id s4GLxtua010779 for <salud@ietf.org>; Fri, 16 May 2014 17:59:55 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id s4GLxt4x010778; Fri, 16 May 2014 17:59:55 -0400
Date: Fri, 16 May 2014 17:59:55 -0400
Message-Id: <201405162159.s4GLxt4x010778@hobgoblin.ariadne.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: salud@ietf.org
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1400277596; bh=X+bPANJHpxrPYf/zMei2CA3z6/yjqkVbv3I+TaZnDGs=; h=Received:Received:Received:Received:Date:Message-Id:From:To: Subject; b=EDkNaa3UAdlAqPD0fDcktM47mGhUgftOxAQ6ykyAuiGw8/C1Okr6idnSAqLp2AaGA TAIcjVdI3HtWiyw/qRVQSDN4ZYIQ8OKNgmN3IQ1du7J7eqDiT//VXRo1Rrb9ZjDmSB Xc1KMn2UUkOx8fwCHoNLwHXHDMmGTN5y37WBBr0WvucYUTvwchcV6rQ98YRANd68Vo 80tcLjA+5Uxwr3Y5WTO7b/kmTLrOU95CRyvi3BVZw4/zsHaIdfUwtdjIqv4GaHdXyP jiEZHZIfODS8KHjWq3T0Fn8/5EUA2F3zORBfPJatvELFLA1toFqM5jBA6rtXBpDyAv wkObFhzbpmF3g==
Archived-At: http://mailarchive.ietf.org/arch/msg/salud/CaR9ussTQQAct8q7nAaOipCFPB4
Subject: [salud] Normative change to proxy behavior
X-BeenThere: salud@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Sip ALerting for User Devices working group discussion list <salud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/salud>, <mailto:salud-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/salud/>
List-Post: <mailto:salud@ietf.org>
List-Help: <mailto:salud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/salud>, <mailto:salud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 May 2014 22:00:06 -0000

Since we're being particular about listing normative changes, I
thought we'd want to be more explicit about the change we're
permitting for proxies:

   14.  Proxy Behaviour

   A A SIP proxy MAY add an Alert-Info header field if none is present,
   and MAY add or remove URNs to an Alert-Info header field in a SIP
   request or a provisional 1xx response (excepting a 100 response) when
   it needs to provide additional information about the call or about
   the provided service.

By 3261, proxies are allowed to append a new header field value to a
header field that allows multiple values.  (This is done by an implied
redirection to an internal UA which provides a 4xx response with
"Contact:  <whatever?Alert-Info=urn:alert:additional:value>".)  But
removing header field values is not generally allowed.  Section 14 of
our draft enables removing values and adding values that are not at
the end of the value list.

We should document this change in the final paragraph of the abstract
and section 4 by adding something like this:

   Abstract

   This document normatively updates the RFC 3261, which defines the
   Session Initiation Protocol (SIP): It changes the usage of the Alert-
   Info header field defined in the RFC 3261 by additionally allowing
   its use in all provisional responses to INVITE (except the 100
   response).
+  This document also permits proxies to add and remove header field
+  values from the Alert-Info header field.

   4.  Update to RFC 3261

+  4.3.  Proxies may alter Alert-Info header fields
+
+  A SIP proxy MAY add or remove URNs to an Alert-Info header field in
+  a SIP request or a provisional 1xx response (excepting a 100
+  response).

Dale