Re: [apps-discuss] service configuration

"Songhaibin (A)" <haibin.song@huawei.com> Mon, 29 July 2013 12:21 UTC

Return-Path: <haibin.song@huawei.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C7D021F9BD0 for <apps-discuss@ietfa.amsl.com>; Mon, 29 Jul 2013 05:21:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Okx0tqv11B5x for <apps-discuss@ietfa.amsl.com>; Mon, 29 Jul 2013 05:21:29 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4536E21F9C37 for <apps-discuss@ietf.org>; Mon, 29 Jul 2013 05:21:17 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AVN40409; Mon, 29 Jul 2013 12:21:16 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Mon, 29 Jul 2013 13:21:08 +0100
Received: from nkgeml405-hub.china.huawei.com (10.98.56.36) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.1.323.7; Mon, 29 Jul 2013 13:21:13 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.43]) by nkgeml405-hub.china.huawei.com ([10.98.56.36]) with mapi id 14.01.0323.007; Mon, 29 Jul 2013 20:21:10 +0800
From: "Songhaibin (A)" <haibin.song@huawei.com>
To: Peter Saint-Andre <stpeter@stpeter.im>
Thread-Topic: service configuration
Thread-Index: AQHOjDW/wZDETQ16ikKym0w+C3YhuZl7KLkw
Date: Mon, 29 Jul 2013 12:21:09 +0000
Message-ID: <E33E01DFD5BEA24B9F3F18671078951F2471AB12@nkgeml501-mbs.china.huawei.com>
References: <CAL0qLwbCgzTEnL4-jaCLWvvVUK1vWoS3RUEMQ9zKHgD3hUsMYA@mail.gmail.com> <E33E01DFD5BEA24B9F3F18671078951F24716FE4@nkgeml501-mbs.china.huawei.com> <51F6185C.5050101@stpeter.im> <E33E01DFD5BEA24B9F3F18671078951F2471A846@nkgeml501-mbs.china.huawei.com> <51F627E3.9030004@stpeter.im>
In-Reply-To: <51F627E3.9030004@stpeter.im>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.216.44.211]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] service configuration
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Jul 2013 12:21:36 -0000

I'm reading this document.

>From the description below:
" This specification defines a single protocol which will allow for retrieval of a variety of service configuration information in a single call, allowing developers to simplify the coding and user interface in client software, and in particular in multi-function client software such as a combined e-mail and calendar clients. Configuration is retrieved from a single document on a server, improving performance over per-service configuration mechanisms that require multiple network operations."

I think this document is very interesting and useful for client side configuration to communicate with different service providers. But it seems that it is a total different story from what I talked about this morning, especially for the software installation part, where for example, a home user installs a virtual home gateway in the provider's network, and chooses the features(software components) that he wants to install on that virtual gateway. 

For the service configuration part (we both call them service configuration, but we focus on different things), Cyrus's document could be complementary, if the software we moved to the provider's network has requirements to configure it for communication with other service provider servers. But it is also very common the configuration is for other purpose, for example, an enterprise user installs a virtual firewall in the provider's network, then it has to configure it for handling the traffic from/to the enterprise.

BR,
-Haibin

-----Original Message-----
From: Peter Saint-Andre [mailto:stpeter@stpeter.im] 
Sent: Monday, July 29, 2013 4:29 PM
To: Songhaibin (A)
Cc: apps-discuss@ietf.org
Subject: Re: service configuration

On 7/29/13 10:03 AM, Songhaibin (A) wrote:
> Hi Peter,
> 
> Many thanks for the reference. I will look into the related documents 
> to see whether there are overlaps. I do not want to do duplicate work 
> either.

If you have a chance to review the document from Cyrus this week, you could probably chat with him in person (or with others -- I have been tracking this work and I know several other people who have.

Peter