[BLISS] draft-ietf-bliss-ach-analysis-02

"Elwell, John" <john.elwell@siemens.com> Wed, 11 June 2008 19:26 UTC

Return-Path: <bliss-bounces@ietf.org>
X-Original-To: bliss-archive@optimus.ietf.org
Delivered-To: ietfarch-bliss-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A37603A6878; Wed, 11 Jun 2008 12:26:36 -0700 (PDT)
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 76CCA3A6813 for <bliss@core3.amsl.com>; Wed, 11 Jun 2008 12:26:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 xCVZIdtACgTC for <bliss@core3.amsl.com>; Wed, 11 Jun 2008 12:26:34 -0700 (PDT)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk [195.171.110.225]) by core3.amsl.com (Postfix) with ESMTP id 45BAA3A69A3 for <bliss@ietf.org>; Wed, 11 Jun 2008 12:26:24 -0700 (PDT)
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235]) by siemenscomms.co.uk (PMDF V6.3-x14 #31430) with ESMTP id <0K2B00G1GCOP5N@siemenscomms.co.uk> for bliss@ietf.org; Wed, 11 Jun 2008 20:26:49 +0100 (BST)
Date: Wed, 11 Jun 2008 20:26:48 +0100
From: "Elwell, John" <john.elwell@siemens.com>
To: bliss@ietf.org
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D0CE409D@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: draft-ietf-bliss-ach-analysis-02
Thread-Index: AcjL+RfpXyXZFvOCTU2P1m7uA9FJ9w==
Content-class: urn:content-classes:message
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Subject: [BLISS] draft-ietf-bliss-ach-analysis-02
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: bliss-bounces@ietf.org
Errors-To: bliss-bounces@ietf.org

http://www.ietf.org/internet-drafts/draft-ietf-bliss-ach-analysis-02.txt

The ACH design team still needs feedback on this (there has been very
little since it was posted about 2-3 weeks ago). From the design team's
point of view it is more or less complete, apart from the question of
how a UA can configure ACH settings at its proxy (other than a normal
web page, which merely gives the user control, not the UA itself). Input
is lacking on this configuration topic. Something based on XCAP might be
one possibility, but also there has been a suggestion this might be too
complex. Any input would be welcome.

John
_______________________________________________
BLISS mailing list
BLISS@ietf.org
https://www.ietf.org/mailman/listinfo/bliss