IETF Logo Mail Archive

[Sipping-tispan] CCBS/CCNR in Version -02f

"Schmidt, Christian" <christian-schmidt@siemens.com> Fri, 23 September 2005 13:30 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EIndJ-0003kG-AB; Fri, 23 Sep 2005 09:30:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EIndH-0003kB-J8 for sipping-tispan@megatron.ietf.org; Fri, 23 Sep 2005 09:30:31 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14376 for <sipping-tispan@ietf.org>; Fri, 23 Sep 2005 09:30:30 -0400 (EDT)
Received: from david.siemens.de ([192.35.17.14]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EInjh-0006ju-2B for sipping-tispan@ietf.org; Fri, 23 Sep 2005 09:37:11 -0400
Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by david.siemens.de (8.12.6/8.12.6) with ESMTP id j8NDURPQ006689; Fri, 23 Sep 2005 15:30:27 +0200
Received: from mhpahx2c.ww002.siemens.net (mhpahx2c.mch.sbs.de [139.25.165.55]) by mail3.siemens.de (8.12.6/8.12.6) with ESMTP id j8NDURdu031124; Fri, 23 Sep 2005 15:30:27 +0200
Received: from MCHP7R5A.ww002.siemens.net ([139.25.131.163]) by mhpahx2c.ww002.siemens.net with Microsoft SMTPSVC(6.0.3790.0); Fri, 23 Sep 2005 15:30:26 +0200
x-mimeole: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 23 Sep 2005 15:30:26 +0200
Message-ID: <72963DDDF17D7949ABD18DC5DA58E770058419@MCHP7R5A.ww002.siemens.net>
Thread-Topic: CCBS/CCNR in Version -02f
Thread-Index: AcWu4tVCR8+10prpSdmPzRs37GfeiQAA6BjABFaPp0A=
From: "Schmidt, Christian" <christian-schmidt@siemens.com>
To: "Miguel Garcia" <Miguel.An.Garcia@nokia.com>, <sipping-tispan@ietf.org>
X-OriginalArrivalTime: 23 Sep 2005 13:30:26.0946 (UTC) FILETIME=[F5855E20:01C5C042]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: quoted-printable
Cc:
Subject: [Sipping-tispan] CCBS/CCNR in Version -02f
X-BeenThere: sipping-tispan@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion of requirements for SIP introduced by ETSI TISPAN <sipping-tispan.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping-tispan>, <mailto:sipping-tispan-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/sipping-tispan>
List-Post: <mailto:sipping-tispan@ietf.org>
List-Help: <mailto:sipping-tispan-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping-tispan>, <mailto:sipping-tispan-request@ietf.org?subject=subscribe>
Sender: sipping-tispan-bounces@ietf.org
Errors-To: sipping-tispan-bounces@ietf.org

Hi Miguel,

in case CCBS/CCNR, two requirements are still missing:

REQ-CCBS/CCNR-xx: The caller must be able to invoke CCBS / CCNR service.

REQ-CCBS/CCNR-yy: If a CCBS service is invoked for a callee, other
terminating calls should not be offered to this callee.


For the benefit of the reader, I would recommend to structure the
requirements. For example in gathering
requirements arround pending CCBS/CCNR requests in a block.

Regards,
Christian




_______________________________________________
Sipping-tispan mailing list
Sipping-tispan@ietf.org
https://www1.ietf.org/mailman/listinfo/sipping-tispan

v2.8.7 | Report a Bug | By Email