Re: [sipcore] Updates to 4244bis-05
"Worley, Dale R (Dale)" <dworley@avaya.com> Mon, 11 July 2011 18:59 UTC
Return-Path: <dworley@avaya.com>
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 13D0921F8ADE for <sipcore@ietfa.amsl.com>; Mon, 11 Jul 2011 11:59:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.263
X-Spam-Level:
X-Spam-Status: No, score=-103.263 tagged_above=-999 required=5 tests=[AWL=0.336, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1dVdtDy0MnCs for <sipcore@ietfa.amsl.com>; Mon, 11 Jul 2011 11:59:05 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id B57D221F86D1 for <sipcore@ietf.org>; Mon, 11 Jul 2011 11:59:04 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAPxGG07GmAcF/2dsb2JhbABTpx93rS4CmzmFW18El2+LSA
X-IronPort-AV: E=Sophos;i="4.65,516,1304308800"; d="scan'208";a="255999329"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 11 Jul 2011 14:59:03 -0400
Received: from dc-us1hcex2.us1.avaya.com (HELO DC-US1HCEX2.global.avaya.com) ([135.11.52.21]) by co300216-co-erhwest-out.avaya.com with ESMTP; 11 Jul 2011 14:57:32 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.172]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Mon, 11 Jul 2011 14:59:02 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Shida Schubert <shida@agnada.com>
Date: Mon, 11 Jul 2011 14:56:30 -0400
Thread-Topic: [sipcore] Updates to 4244bis-05
Thread-Index: Acw+0Dmo/rTm+G6FSOiOnviBISX16wBLAU/v
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B222B1F5765@DC-US1MBEX4.global.avaya.com>
References: <BANLkTi=-rZ1j6RwzMYATeo2WkqksdoV6ZQ@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F56DD@DC-US1MBEX4.global.avaya.com>, <D8F12201-3914-41AD-A257-13BC8A722FB7@agnada.com>
In-Reply-To: <D8F12201-3914-41AD-A257-13BC8A722FB7@agnada.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: SIPCORE Chairs <sipcore-chairs@tools.ietf.org>, SIPCORE <sipcore@ietf.org>
Subject: Re: [sipcore] Updates to 4244bis-05
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 11 Jul 2011 18:59:06 -0000
________________________________________ From: Shida Schubert [shida@agnada.com] It's not for backward compatibility. We couldn't come up with reason why reason should be included in case of 2xx responses. ________________________________________ Of course, there is always the attraction of handling as many cases as possible uniformly. But given that the only case in which the Reason is admitted is 2xx, and all 2xx's are largely created equal, leaving them off has few disadvantages. There might be cases when a 2xx carries a Reason showing a success code from a downstream gateway. Dale
- [sipcore] Updates to 4244bis-05 Mary Barnes
- Re: [sipcore] Updates to 4244bis-05 Worley, Dale R (Dale)
- Re: [sipcore] Updates to 4244bis-05 Shida Schubert
- Re: [sipcore] Updates to 4244bis-05 Worley, Dale R (Dale)