IETF Logo Mail Archive

Re: [dispatch] Proposal for a mew SIP 4xx Error code

Christer Holmberg <christer.holmberg@ericsson.com> Tue, 29 October 2019 06:35 UTC

Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D521D120048; Mon, 28 Oct 2019 23:35:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
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 v28Lo9aixS6S; Mon, 28 Oct 2019 23:35:24 -0700 (PDT)
Received: from EUR02-AM5-obe.outbound.protection.outlook.com (mail-eopbgr00061.outbound.protection.outlook.com [40.107.0.61]) (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 0ED1B120020; Mon, 28 Oct 2019 23:35:23 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=kEw2FNFH04EhvXqpcDCgzWVT7xdHk0fcctTJ+7FFTQw0ZCaomYpPqhgAPmd1byVGbS2f7CLOSatPa5pU/CFKrnDCPm7ijlE5Nw38trhhPbt9oHYR0Tqkzimh/wn1CzWkyxQsLiqe2vn9Mw8UVLXFBHhqeA5M2fmDLpL+qSZFaEbdGOmFrJMuXd/fq7GcpRqbHcfPZC9d3WyCDWbWr0+//bXRiyyDhzIfIVSk0TJw3n1CAAu+ap0GLPr9dFYZ8ZkyG/sbmSo1lIvE1mPYZX6PZ33t6JweARxiZGsX2t8vqpuHRUfj834W9QLtfhbv76YgCeqnPcJwhULO4kduPOtSxA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=+ud4ux5q812bXqwgmuzvR5NGG47kx/yxWEZhZT+tbJQ=; b=BIBZrAvNg0xKR4j6y5vQmhTT9Y0tcS1QSMP99ZQEBJ4oiTovDZZRhh8XeCb1unDcVVrJVHD/9ciirWMKAl6/d4xwOkTCuZUqGhOO/JEhwq6GpLqzNZKNsW93D9JqndugQ7zgYhvhOpDO9RezMlfB1ZMWb7+MMD/mx+0MVvCos7RhsAl2LfEbw8ocV5WHLS2TqYKM2fvkBtAQlPlK33BF/vqcqcQ8c5nGuQKSW1ylcxxMwhOogFs19eTcy9XnhGHcI6Eo+ENV5MN8VMZhR8r7g6RJhlgAQCE5zF8jAI9aj6Q+OSL4CKqUxXwNv80v1IDby+/GCyfveCTPVvmMEEh3Hw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=+ud4ux5q812bXqwgmuzvR5NGG47kx/yxWEZhZT+tbJQ=; b=kNassNsieyHGK3YsNjDw1+BrIPsMUouMTUDh82PA8bCthQql26+WO/+1w9+2CfrU0+r83szeA5c4bb5GhCI2a+VWjibquSVWRd20ZWo/x5tWxzednzKxSz4rl9TicLf3V8mMvRv5p0OPyTFw5Q/cbzflsOt2hP0bgeRcsfryzIY=
Received: from HE1PR07MB3161.eurprd07.prod.outlook.com (10.170.245.23) by HE1PR07MB3273.eurprd07.prod.outlook.com (10.170.248.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2408.15; Tue, 29 Oct 2019 06:35:21 +0000
Received: from HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::5499:1231:e707:4cb7]) by HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::5499:1231:e707:4cb7%7]) with mapi id 15.20.2408.016; Tue, 29 Oct 2019 06:35:21 +0000
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Ranjit Avasarala <ranjitkav12@gmail.com>, "sipcore@ietf.org" <sipcore@ietf.org>, "dispatch@ietf.org" <dispatch@ietf.org>, "Sip-implementors@lists.cs.columbia.edu" <Sip-implementors@lists.cs.columbia.edu>
Thread-Topic: [dispatch] Proposal for a mew SIP 4xx Error code
Thread-Index: AQHVjg48nX8QtQl4x0aJ8SlhWJh8TqdxKWtR
Date: Tue, 29 Oct 2019 06:35:21 +0000
Message-ID: <HE1PR07MB316193008872CD421120942993610@HE1PR07MB3161.eurprd07.prod.outlook.com>
References: <CAFXT-ptE=1ZfpqsvfXXsnsRwEe7GB=M1C-0wdKT5p1qFnbFJeg@mail.gmail.com>
In-Reply-To: <CAFXT-ptE=1ZfpqsvfXXsnsRwEe7GB=M1C-0wdKT5p1qFnbFJeg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=christer.holmberg@ericsson.com;
x-originating-ip: [86.50.147.151]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: edbbcbb4-9b06-47ed-1c25-08d75c3a2c58
x-ms-traffictypediagnostic: HE1PR07MB3273:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <HE1PR07MB32734A9A66F508B58169B27493610@HE1PR07MB3273.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0205EDCD76
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(376002)(346002)(366004)(396003)(39860400002)(199004)(189003)(53754006)(2171002)(102836004)(2906002)(186003)(74316002)(606006)(8676002)(236005)(99286004)(9686003)(6306002)(6116002)(54896002)(19627405001)(66066001)(52536014)(316002)(3846002)(229853002)(110136005)(71190400001)(26005)(8936002)(6436002)(14454004)(71200400001)(5660300002)(7696005)(478600001)(33656002)(105004)(76116006)(14444005)(66946007)(86362001)(64756008)(66446008)(76176011)(66556008)(66476007)(55016002)(6246003)(25786009)(256004)(446003)(2501003)(11346002)(81156014)(476003)(81166006)(53546011)(6506007)(486006)(7736002)(561944003)(2201001)(44832011)(66574012); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR07MB3273; H:HE1PR07MB3161.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 9MSemgZwNHnwrEAIu7Emm/3X/EDFV2edbr24WVxqeO5UeWE+oPlyMewbOkwfOCuYcVqQ7Ig1kkhiKj/lFSqmIDGqMCS314JS6uyzqnHXUVjyqzbZKUu5kAAIWo0jsqRfnQy5snBCSckCnFjtDL54QJyplsgBb5CSplrNJTtOyWMRCLgyiyWkfz3xhQyYfELmnyyLKqdOtMFZU01GY5umLRmDuraYJXfqL1M3tqgLZPInWy7vq5Oplyp/1+2dXEMrDXpaT1/OKNXMouKAqYDAmmeVlbbGzqAF9ITEDGeaBOBUD7YjWG8JeN6sEfNNEMI7ecUUimcFAMJKFgC4JthpZajbfekMfnjSVNgoSJ8PfdrE/1FnFDhoFOx/OxJFhHxYKsaVhzpQxP3zixkKtHfoHkgptZS/O+2OfgS0dRsCR4ez7v4oUShj0GetIyBa9xwg
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_HE1PR07MB316193008872CD421120942993610HE1PR07MB3161eurp_"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-Network-Message-Id: edbbcbb4-9b06-47ed-1c25-08d75c3a2c58
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Oct 2019 06:35:21.6995 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: pbelhOzEZaun1m/4oupZvrfo5BsGBx6g8s5mMb3GcXwz7KkKmJUh8a4n+KcNzL1hIIjVa2tO9odIJLXNamwB53wy53JkLtmtLXvjThGRiAE=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB3273
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/fWDEUsoN5TIb3cOLfKE40iCA9So>
Subject: Re: [dispatch] Proposal for a mew SIP 4xx Error code
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Oct 2019 06:35:27 -0000

Hi,

I assume this discussion can be moved to SIPCORE, because I don't think DISPATCH needs to discuss the need for a new SIP response code, and where the work defining such would be done.

Regards,

Christer



________________________________
From: dispatch <dispatch-bounces@ietf.org> on behalf of Ranjit Avasarala <ranjitkav12@gmail.com>
Sent: Tuesday, October 29, 2019 6:05 AM
To: sipcore@ietf.org <sipcore@ietf.org>; dispatch@ietf.org <dispatch@ietf.org>; Sip-implementors@lists.cs.columbia.edu <Sip-implementors@lists.cs.columbia.edu>
Subject: [dispatch] Proposal for a mew SIP 4xx Error code

Hello all

Many times I experienced scenarios where SIP requests (e.g. INVITE, PUBLISH or PRACK or any other) have either invalid parameters in the header or a particular header is missing in the request or the header value is incomplete.  Some e.gs<https://protect2.fireeye.com/v1/url?k=7d7bb417-21f196fe-7d7bf48c-0cc47ad93e2e-34af2a5be94ea08e&q=1&e=c2646b0c-e4da-4248-94ca-d03438b18bb9&u=http%3A%2F%2Fe.gs%2F> are

  *   SIP Route header in INVITE contains additional "lr" parameter. Ideally, "lr" parameter needs to be associated with a particular route - i.e. sip URI
  *   the Accept header is missing in SIP PUBLISH
  *   the Allow header misses UPDATE method
  *   .....  many more

Currently, in all the above cases the SIP Proxy server that receives the request, responds with a 400 Bad Request.
Though 400 Bad Request is acceptable given that there is some issue in the SIP request, a more detailed error would be more useful - as sometimes interpreting 400 Bad Request is harder
E.g.
a  4xx Invalid header/parameter may be more appropriate with reason
E.g. if there is additional "lr" parameter in SIP INVITE, then the proxy can return a 4xx Invalid Header/parameter with Reason:  SIP code=4xx; Text="Invalid lr parameter in Route header"

Let me know your thoughts on if this proposal can be taken forward as an Internet draft.

Thank you
Ranjit

v2.23.0 | Report a Bug | By Email