[BLISS] How are appearance assignments by phones confirmed?
"Worley, Dale R (Dale)" <dworley@avaya.com> Mon, 18 April 2011 21:18 UTC
Return-Path: <dworley@avaya.com>
X-Original-To: bliss@ietfc.amsl.com
Delivered-To: bliss@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id CBECAE06B5 for <bliss@ietfc.amsl.com>; Mon, 18 Apr 2011 14:18:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.541
X-Spam-Level:
X-Spam-Status: No, score=-102.541 tagged_above=-999 required=5 tests=[AWL=0.058, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z-g2ZHZyQk2D for <bliss@ietfc.amsl.com>; Mon, 18 Apr 2011 14:18:36 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfc.amsl.com (Postfix) with ESMTP id 063D7E06F9 for <bliss@ietf.org>; Mon, 18 Apr 2011 14:18:22 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAJgtcU3GmAcF/2dsb2JhbACmZHSkegKZF4VhBJAM
X-IronPort-AV: E=Sophos;i="4.64,234,1301889600"; d="scan'208";a="184929229"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 18 Apr 2011 15:42:14 -0400
X-IronPort-AV: E=Sophos;i="4.64,234,1301889600"; d="scan'208";a="610140428"
Received: from unknown (HELO DC-US1HCEX4.global.avaya.com) ([135.11.52.35]) by co300216-co-erhwest-out.avaya.com with ESMTP; 18 Apr 2011 15:42:14 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.201]) by DC-US1HCEX4.global.avaya.com ([135.11.52.35]) with mapi; Mon, 18 Apr 2011 15:42:14 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "bliss@ietf.org" <bliss@ietf.org>
Date: Mon, 18 Apr 2011 15:39:08 -0400
Thread-Topic: How are appearance assignments by phones confirmed?
Thread-Index: AQHL/gC3BtBJZIcmRU2mlcFrCcpO5w==
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22246BD3E6@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] How are appearance assignments by phones confirmed?
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Mon, 18 Apr 2011 21:18:37 -0000
Regarding draft-ietf-bliss-shared-appearances-07, I mentioned that there wasn't a clear calling-out of the "fundamental operation" whereby a UA assigned an appearance number and the AA confirms the assignment. At that time I thought that it was done by the UA sending a PUBLISH, and watching for the AA to send a NOTIFY containing the assignment. But now I think I was wrong, that the confirmation is done by a success response to the PUBLISH. (Which means that the PUBLISH must be handled directly by the AA.) The fact that I was confused about this operation means that it isn't described specifically in the draft. I think it needs to be described as a separate, fairly high-level section. Dale
- [BLISS] How are appearance assignments by phones … Worley, Dale R (Dale)