[BLISS] call-completion issue 2004: Failure codes for CC SUBSCRIBE

"WORLEY, Dale R (Dale)" <dworley@avaya.com> Thu, 08 July 2010 02:56 UTC

Return-Path: <dworley@avaya.com>
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2C3503A67B7 for <bliss@core3.amsl.com>; Wed, 7 Jul 2010 19:56:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.968
X-Spam-Level:
X-Spam-Status: No, score=-1.968 tagged_above=-999 required=5 tests=[AWL=0.631, 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 fApHAdrpwkxF for <bliss@core3.amsl.com>; Wed, 7 Jul 2010 19:56:40 -0700 (PDT)
Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (p-us1-iereast-outbound-tmp.us1.avaya.com [135.11.29.16]) by core3.amsl.com (Postfix) with ESMTP id 4ABD13A68E9 for <bliss@ietf.org>; Wed, 7 Jul 2010 19:56:40 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.53,556,1272859200"; d="scan'208";a="24149275"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 07 Jul 2010 22:56:43 -0400
X-IronPort-AV: E=Sophos;i="4.53,556,1272859200"; d="scan'208";a="489805064"
Received: from dc-us1hcex1.us1.avaya.com (HELO DC-US1HCEX1.global.avaya.com) ([135.11.52.20]) by co300216-co-erhwest-out.avaya.com with ESMTP; 07 Jul 2010 22:56:43 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.161]) by DC-US1HCEX1.global.avaya.com ([2002:870b:3414::870b:3414]) with mapi; Wed, 7 Jul 2010 22:56:42 -0400
From: "WORLEY, Dale R (Dale)" <dworley@avaya.com>
To: "bliss@ietf.org" <bliss@ietf.org>
Date: Wed, 07 Jul 2010 22:53:20 -0400
Thread-Topic: call-completion issue 2004: Failure codes for CC SUBSCRIBE
Thread-Index: AQHLHkkxhSBKoiSm20qsBYflCVGilg==
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B21FE98EE82@DC-US1MBEX4.global.avaya.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
Subject: [BLISS] call-completion issue 2004: Failure codes for CC SUBSCRIBE
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Jul 2010 02:56:41 -0000

> > ** Technical
> > 
> > 
> > * 2004 Failure codes for CC SUBSCRIBE
> > 
> > [New for -05.]  The text is inconsistent regarding the 
> > failure code for a CC SUBSCRIBE for a call that the monitor 
> > has no record of:  7.2 says 404, 9.7 says 481.  It seems to 
> > me that 404 should be reserved for SUBSCRIBEs for which the 
> > monitor cannot identify the managed AOR, and 481 used for 
> > SUBSCRIBEs that designate a proper AOR but not a known call 
> > for that AOR.
> 
> I agree with your analysis. My proposal is to solve this inconsistency
> with a clear definition in subclause 9.7, and delete the regarding
> definitions from subclause 7.2, in order to avoid redundant
> specification.

Given that we are giving up on "call correlation", the monitor no longer produces 481 responses to new SUBSCRIBEs.  Removing that case from the two sections eliminates the inconsistency.

However, I think removing the redundancy is a good idea; the titles of the two sections make it clear that they are related, so a reader will have no difficulty finding the specification of response codes.

Dale