IETF Logo Mail Archive

Re: [sipcore] Last Call: <draft-ietf-sipcore-status-unwanted-04.txt> (A SIP Response Code for Unwanted Calls) to Proposed Standard

worley@ariadne.com (Dale R. Worley) Mon, 27 March 2017 18:15 UTC

Return-Path: <worley@alum.mit.edu>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 145A1129483 for <sipcore@ietfa.amsl.com>; Mon, 27 Mar 2017 11:15:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.934
X-Spam-Level:
X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
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 KdMy4oM51B5W for <sipcore@ietfa.amsl.com>; Mon, 27 Mar 2017 11:15:21 -0700 (PDT)
Received: from resqmta-ch2-08v.sys.comcast.net (resqmta-ch2-08v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E540712947D for <sipcore@ietf.org>; Mon, 27 Mar 2017 11:15:20 -0700 (PDT)
Received: from resomta-ch2-16v.sys.comcast.net ([69.252.207.112]) by resqmta-ch2-08v.sys.comcast.net with SMTP id sZAScAmTqAfZssZAmceV14; Mon, 27 Mar 2017 18:15:20 +0000
Received: from hobgoblin.ariadne.com ([24.60.114.4]) by resomta-ch2-16v.sys.comcast.net with SMTP id sZAkcvHir9isysZAlcEOiA; Mon, 27 Mar 2017 18:15:20 +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 v2RIFI1g024818; Mon, 27 Mar 2017 14:15:18 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id v2RIFH1V024815; Mon, 27 Mar 2017 14:15:17 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: Paul Kyzivat <paul.kyzivat@comcast.net>
Cc: sipcore@ietf.org
In-Reply-To: <8bba04c7-0ea4-5088-813f-b34aeb631e5b@comcast.net> (paul.kyzivat@comcast.net)
Sender: worley@ariadne.com
Date: Mon, 27 Mar 2017 14:15:17 -0400
Message-ID: <87a886lh6y.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfDwQJMUeOR/Iwp+/BwqNGEsHhkCOUC2n8Saj3SSoGF1gIQBMaEx2WdcKCS68Dl7CtkbfyECUfpdnYrEQYuU1sVSUVA6m6FZHRwS5rfMe+x3lL0k9Br/k K8m7e50ZaE8l5LwC5zCCGgo0zFePX6a/L+RJa21rGHdQX92ETD6JmZJyYWKQfuu6hCGHb4QgtAXniXopYli5ITQ6h6vBm8CV3KM=
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/oTcyjqLB8nSzeJrvvXwsuObd5lU>
Subject: Re: [sipcore] Last Call: <draft-ietf-sipcore-status-unwanted-04.txt> (A SIP Response Code for Unwanted Calls) to Proposed Standard
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Mar 2017 18:15:22 -0000

Paul Kyzivat <paul.kyzivat@comcast.net> writes:
> Isn't it assumed that a Reason header is preserved e2e with error responses?

Watching Roland's presentation in the Dispatch WG today prodded me to
think about this again.

As far as I can tell, RFC 3326 envisions that Reason headers can be
included in responses but doesn't specify how they are processed.  OTOH,
it seems to me that the odds are good that most proxies propagate
backward Reason headers in failure responses, so Reason would be a good
choice for carrying additional information.

Dale

v2.23.0 | Report a Bug | By Email