Re: [BLISS] Moving ahead with the ach-analysis draft
Scott Lawrence <xmlscott@gmail.com> Thu, 29 April 2010 11:08 UTC
Return-Path: <xmlscott@gmail.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 965983A6ADC for <bliss@core3.amsl.com>; Thu, 29 Apr 2010 04:08:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.163
X-Spam-Level:
X-Spam-Status: No, score=-1.163 tagged_above=-999 required=5 tests=[AWL=-0.423, BAYES_20=-0.74]
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 eH22XB8f7lXO for <bliss@core3.amsl.com>; Thu, 29 Apr 2010 04:08:13 -0700 (PDT)
Received: from mail-qy0-f181.google.com (mail-qy0-f181.google.com [209.85.221.181]) by core3.amsl.com (Postfix) with ESMTP id 12D5828C23E for <bliss@ietf.org>; Thu, 29 Apr 2010 04:08:02 -0700 (PDT)
Received: by qyk11 with SMTP id 11so19341256qyk.13 for <bliss@ietf.org>; Thu, 29 Apr 2010 04:07:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:cc :in-reply-to:references:content-type:date:message-id:mime-version :x-mailer:content-transfer-encoding; bh=8BVLQuWPTIsWKkTdH/hcs3xk3diwmeu4K5hFppovztg=; b=Gw6CS4kqEkrIj0d37TpwzkhK1pbt1L+N094fqdc2T3O0WYqQ/0yVSDvgZfRApfXNKk 0MbPh7reezqazhWSIK/qm/3Upm5G2m8RVunqSLmAi9XrBSOsVe4++OLO8BXmVHGro1+a pk2g0UPqAdhF1qIbJDm5vTX+TzhLrsF55Rrk8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer:content-transfer-encoding; b=IJ6uYmUUC3Gz0Gy7e66oGycgvc1KXK4Y2KXIOtAE3vlhPmui8ecPLdkeKxdcl8t135 TDUC7Hq+eJqySxFcuLFrN/FW4efMOrkwCSvLSeBA0Z2W8WsfmYrmbDE51foEs5WaAjk4 v6znUO2H3uP3Acs5AL2xmWpm9D3PKlkq9kE1U=
Received: by 10.224.63.77 with SMTP id a13mr2429531qai.267.1272539266362; Thu, 29 Apr 2010 04:07:46 -0700 (PDT)
Received: from [192.168.10.11] (c-98-229-134-198.hsd1.ma.comcast.net [98.229.134.198]) by mx.google.com with ESMTPS id 22sm513892qyk.6.2010.04.29.04.07.42 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 29 Apr 2010 04:07:43 -0700 (PDT)
From: Scott Lawrence <xmlscott@gmail.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>
In-Reply-To: <A444A0F8084434499206E78C106220CADE2C1116@MCHP058A.global-ad.net>
References: <A444A0F8084434499206E78C106220CADE2C1116@MCHP058A.global-ad.net>
Content-Type: text/plain; charset="UTF-8"
Date: Thu, 29 Apr 2010 07:07:41 -0400
Message-ID: <1272539261.3200.31.camel@localhost>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.3 (2.28.3-1.fc12)
Content-Transfer-Encoding: 7bit
Cc: "bliss@ietf.org" <bliss@ietf.org>
Subject: Re: [BLISS] Moving ahead with the ach-analysis draft
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, 29 Apr 2010 11:08:14 -0000
On Thu, 2010-04-15 at 14:47 +0200, Elwell, John wrote: > One of the issues holding up this draft is the need for a reference to > a solution for a UA to query and modify its ACH configuration at a > proxy. There had been an expectation of specifying a RESTful solution > to this, and referencing that. However, it seems that such work is not > progressing, will not get chartered in BLISS, and in the foreseeable > future probably won't get done elsewhere. It is true that the RESTful API document that Theo started will not be a BLISS work item, but Rifaat Shekh-Yusef has (with permission) picked it up and is preparing an updated draft. I believe he'll be posting his first version shortly. The timing is, however, still problematic in terms of being able to finish this document if you have a reference that has to be resolved before this can be published as an RFC.
- [BLISS] Moving ahead with the ach-analysis draft Elwell, John
- Re: [BLISS] Moving ahead with the ach-analysis dr… Scott Lawrence