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) Thu, 30 March 2017 20:31 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 C49141294A2 for <sipcore@ietfa.amsl.com>; Thu, 30 Mar 2017 13:31:43 -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 RkQhCx0bTGLE for <sipcore@ietfa.amsl.com>; Thu, 30 Mar 2017 13:31:37 -0700 (PDT)
Received: from resqmta-ch2-03v.sys.comcast.net (resqmta-ch2-03v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:35]) (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 C28A412945E for <sipcore@ietf.org>; Thu, 30 Mar 2017 13:31:32 -0700 (PDT)
Received: from resomta-ch2-03v.sys.comcast.net ([69.252.207.99]) by resqmta-ch2-03v.sys.comcast.net with SMTP id tgifcO8JkfuM3tgjEcPB4P; Thu, 30 Mar 2017 20:31:32 +0000
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-03v.sys.comcast.net with SMTP id tgjCcfvMyVzqStgjDcgqve; Thu, 30 Mar 2017 20:31:31 +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 v2UKVUPB002027 for <sipcore@ietf.org>; Thu, 30 Mar 2017 16:31:30 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id v2UKVTL2002022; Thu, 30 Mar 2017 16:31:29 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: sipcore@ietf.org
In-Reply-To: <87a886lh6y.fsf@hobgoblin.ariadne.com> (worley@ariadne.com)
Sender: worley@ariadne.com
Date: Thu, 30 Mar 2017 16:31:29 -0400
Message-ID: <87efxeh5ge.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfLhSQ+ErpsCUJ2fFcoZr5LiPoB1nKme5wYJWQ5y7yOv//O+MGB/pGo4qRnAF3d03TDdBCH31Kr06QhSaILiiwRt18YDD31twyOAsoQV+oTYo1g/PydvV mRXMsUAKu+QJdyq+U8mxcjqlnqz1n/RkJ38m2hjB//8oVWYhY3waAMOE
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/ZbKde9ccuoG5iQzR3WNgIMyw4tI>
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: Thu, 30 Mar 2017 20:31:44 -0000

worley@ariadne.com (Dale R. Worley) writes:
> 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.

Actually, if/when we define a "protocol" value for Response to be used
with "666" responses, we should just add a normative change to 3261 that
when a proxy chooses as "best response" a response with a Reason header,
it must propagate the Reason header.

Dale

v2.23.0 | Report a Bug | By Email