[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Sip] INFO Framework - one pakage per INFO
On Dec 10, 2008, at 1:30 AM, Hadriel Kaplan wrote:
I think your point is that we shouldn't explicitly point this out,
for fear of people thinking they need to do it? So that rules out
creating a new specific response code for it, and just letting 415
or 400 cover that case. (that's essentially what all the other SIP
specs do too - don't mention it, leave it implementation specific)
I don't see people having interop issues with it so that's fine,
though it makes troubleshooting a bit more laborious.
I think I agree.
--
Dean
_______________________________________________
Sip mailing list From sip-bounces at ietf.org Wed Dec 10 08:46:06 2008
Return-Path: <sip-bounces at ietf.org>
X-Original-To: sip-archive at optimus.ietf.org
Delivered-To: ietfarch-sip-archive at core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 34E953A68E0;
Wed, 10 Dec 2008 08:46:06 -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 84EE63A68E0
for <sip at core3.amsl.com>; Wed, 10 Dec 2008 08:46:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.585
X-Spam-Level:
X-Spam-Status: No, score=-2.585 tagged_above=-999 required=5 tests=[AWL=0.014,
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 pwnlIe3TJvep for <sip at core3.amsl.com>;
Wed, 10 Dec 2008 08:46:03 -0800 (PST)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
by core3.amsl.com (Postfix) with ESMTP id C8E643A68DD
for <SIP at ietf.org>; Wed, 10 Dec 2008 08:46:03 -0800 (PST)
Received: from [192.168.2.102] (cpe-72-181-150-177.tx.res.rr.com
[72.181.150.177] (may be forged)) (authenticated bits=0)
by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
mBAGjrCP007857
(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
Wed, 10 Dec 2008 10:45:55 -0600
Message-Id: <45981CD6-4440-4967-9705-D7785E1A6810 at softarmor.com>
From: Dean Willis <dean.willis at softarmor.com>
To: Hadriel Kaplan <HKaplan at acmepacket.com>
In-Reply-To: <E6C2E8958BA59A4FB960963D475F7AC3137FAFFE58 at mail>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 10 Dec 2008 10:45:48 -0600
References: 8A6A762007F5D001560B18 at GBNTHT12009MSX.gb002.siemens.net><E6C2E8958BA59A4FB960963D475F7AC3137F290B3C at mail><28B7C3AA2A7ABA4A841F11217ABE78D674743C9B at FRMRSSXCHMBSB3.dc-m.alcatel-lucent.com><E6C2E8958BA59A4FB960963D475F7AC3137FA124A5 at mail>
<CA9998CD4A020D418654FCDEF4E707DF09BBD2A3 at esealmw113.eemea.ericsson.se>
<68367825453443BC9EB23F5C535181C9 at Codalogic>
<CA9998CD4A020D418654FCDEF4E707DF09BBD4EB at esealmw113.eemea.ericsson.se>
<C405813E697143F9845A0DD2DEA1EFFF at Codalogic>
<E6C2E8958BA59A4FB960963D475F7AC3137FA12F18 at mail>
<8F5AA18C-B07C-4AE9-8B2F-6CC8A19E2BDA at softarmor.com>
<E6C2E8958BA59A4FB960963D475F7AC3137FA13467 at mail>
<493F05BD.4060201 at cisco.com>
<64A0A9B8-CE76-4677-8EDF-CABEC788D990 at softarmor.com>
<E6C2E8958BA59A4FB960963D475F7AC3137FAFFE0D at mail>
<52D3B73D-EB78-48E4-BC8A-6ED7316895B0 at softarmor.com>
<E6C2E8958BA59A4FB960963D475F7AC3137FAFFE44 at mail>
<1C88DF15-A365-432E-A375-EE112CA21701 at softarmor.com>
<E6C2E8958BA59A4FB960963D475F7AC3137FAFFE58 at mail>
X-Mailer: Apple Mail (2.929.2)
Cc: SIP List <SIP at ietf.org>
Subject: Re: [Sip] INFO Framework - one pakage per INFO
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces at ietf.org
Errors-To: sip-bounces at ietf.org
On Dec 10, 2008, at 1:30 AM, Hadriel Kaplan wrote:
I think your point is that we shouldn't explicitly point this out,
for fear of people thinking they need to do it? So that rules out
creating a new specific response code for it, and just letting 415
or 400 cover that case. (that's essentially what all the other SIP
specs do too - don't mention it, leave it implementation specific)
I don't see people having interop issues with it so that's fine,
though it makes troubleshooting a bit more laborious.
I think I agree.
--
Dean
_______________________________________________
Sip mailing list https://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
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