[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Sip] Sip-199-02: majors and nits from Robert (was: RE: WGLC for draft-ietf-sip-199-02)
> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg at ericsson.com]
> Sent: Monday, November 24, 2008 4:51 PM
>
> So, soon people will have to start deploying SBCs, in order to fix the
> mistakes made by their existing SBCs..... ;)
Well people do upgrade. I think they usually find it easier to upgrade their SBCs than upgrade their customers' PBX's or peer's equipment, or even their own core servers.
> But, I think the correct way to prevent those is to make sure our specs
> are clear enough, and easy to understand - not to start making
> restrictions which may shoot back later.
The thing is with the 199-type of mechanism I actually don't think we should ever allow such a thing tFrom sip-bounces at ietf.org Mon Nov 24 15:17:40 2008
Return-Path: <sip-bounces at ietf.org>
X-Original-To: sip-web-archive at optimus.ietf.org
Delivered-To: ietfarch-sip-web-archive at core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 80DB13A68DC;
Mon, 24 Nov 2008 15:17:40 -0800 (PST)
X-Original-To: sip at core3.amsl.com
Delivered-To: sip at core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id B00A33A68DC
for <sip at core3.amsl.com>; Mon, 24 Nov 2008 15:17:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.525
X-Spam-Level:
X-Spam-Status: No, score=-2.525 tagged_above=-999 required=5 tests=[AWL=0.074,
BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id nUOs8BuBSKgb for <sip at core3.amsl.com>;
Mon, 24 Nov 2008 15:17:38 -0800 (PST)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6])
by core3.amsl.com (Postfix) with ESMTP id 395F73A689E
for <sip at ietf.org>; Mon, 24 Nov 2008 15:17:38 -0800 (PST)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com
(216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.291.1;
Mon, 24 Nov 2008 18:16:08 -0500
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with
mapi; Mon, 24 Nov 2008 18:16:07 -0500
From: Hadriel Kaplan <HKaplan at acmepacket.com>
To: Christer Holmberg <christer.holmberg at ericsson.com>
Date: Mon, 24 Nov 2008 18:17:33 -0500
Thread-Topic: [Sip] Sip-199-02: majors and nits from Robert (was: RE: WGLC
for draft-ietf-sip-199-02)
Thread-Index: AclENT1Jx1/iIji4RxKlbejpCUMInQB6CvXgAZCTmVAAEDSvAAAJHcFgAE4JvxAAEcsjkAAOb7SgAAKo6+A=
Message-ID: <E6C2E8958BA59A4FB960963D475F7AC313747B6403 at mail>
References: <5D1A7985295922448D5550C94DE29180024975DD at DEEXC1U01.de.lucent.com><900DBDFF-96AA-4EF8-96EC-A5DF0D3A7F92 at nostrum.com><58BEC600-AE98-4ADC-A822-DC3FF4B0B398 at nostrum.com>
<CA9998CD4A020D418654FCDEF4E707DF05C0F9B3 at esealmw113.eemea.ericsson.se>
<E6C2E8958BA59A4FB960963D475F7AC313741544FF at mail>
<CA9998CD4A020D418654FCDEF4E707DF05C0F9B8 at esealmw113.eemea.ericsson.se>
<E6C2E8958BA59A4FB960963D475F7AC31374154553 at mail>
<CA9998CD4A020D418654FCDEF4E707DF09387F95 at esealmw113.eemea.ericsson.se>
<E6C2E8958BA59A4FB960963D475F7AC313747B590A at mail>
<CA9998CD4A020D418654FCDEF4E707DF05C0F9C0 at esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF05C0F9C0 at esealmw113.eemea.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
Cc: SIP IETF <sip at ietf.org>
Subject: Re: [Sip] Sip-199-02: majors and nits from Robert (was: RE: WGLC
for draft-ietf-sip-199-02)
X-BeenThere: sip at ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
<mailto:sip-request at ietf.org?subject=unsubscribe>
List-Post: <mailto:sip at ietf.org>
List-Help: <mailto:sip-request at ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
<mailto:sip-request at ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces at ietf.org
Errors-To: sip-bounces at ietf.org
> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg at ericsson.com]
> Sent: Monday, November 24, 2008 4:51 PM
>
> So, soon people will have to start deploying SBCs, in order to fix the
> mistakes made by their existing SBCs..... ;)
Well people do upgrade. I think they usually find it easier to upgrade their SBCs than upgrade their customers' PBX's or peer's equipment, or even their own core servers.
> But, I think the correct way to prevent those is to make sure our specs
> are clear enough, and easy to understand - not to start making
> restrictions which may shoot back later.
The thing is with the 199-type of mechanism I actually don't think we should ever allow such ao be Required, ever.
What you are basically asking for is to create a new 1xx response code some device may require in order to operate correctly, and that I think is a bad idea.
-hadriel
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip
thing to be Required, ever.
What you are basically asking for is to create a new 1xx response code some device may require in order to operate correctly, and that I think is a bad idea.
-hadriel
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip