Re: [clouds] draft-yokota-cloud-service-mobility

Vishwas Manral <vishwas.ietf@gmail.com> Thu, 13 January 2011 17:26 UTC

Return-Path: <vishwas.ietf@gmail.com>
X-Original-To: clouds@core3.amsl.com
Delivered-To: clouds@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C186728C10E for <clouds@core3.amsl.com>; Thu, 13 Jan 2011 09:26:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.47
X-Spam-Level:
X-Spam-Status: No, score=-3.47 tagged_above=-999 required=5 tests=[AWL=0.129, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 JoO6KSJk4aSH for <clouds@core3.amsl.com>; Thu, 13 Jan 2011 09:26:39 -0800 (PST)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 380C328C0F9 for <clouds@ietf.org>; Thu, 13 Jan 2011 09:26:39 -0800 (PST)
Received: by wyf23 with SMTP id 23so2013937wyf.31 for <clouds@ietf.org>; Thu, 13 Jan 2011 09:28:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=cAG+HaLto5LuzbEGdH+WpzXE8SPmub8LU3TybO9xfkA=; b=olM7HYqQR4tKYsSI0oA1hA0RxcPKYhqdt5OTMN3CH3yUuSaE4dztnMW2DlvR7nfbla aghyFPRHBab01M2dt1GTxSoqU/cqtmaWHh0EtyenA1LRGzej5clcgIEkr+loKSgKwK6D 1WBO89sWblyUG1qvxrAmDQiIQcwVueuzsBu3g=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=T9BO8fja1cxEHcfCLVNamBDh4Socn7GELS0DJmM3CXslBVA+ht16KYaLx9fNYXoykd P0Rg5Vsjl0Gm1QSLK3Ay+rMaYYMKOgyQCUlqKbKcyjWwwcLjvUQ3IPEAn0u08JVIYs4s gVZV+gJavLj/vzz9d+xOsaXZp0osF5pVPfp6s=
MIME-Version: 1.0
Received: by 10.216.155.205 with SMTP id j55mr800880wek.90.1294939531580; Thu, 13 Jan 2011 09:25:31 -0800 (PST)
Received: by 10.216.139.219 with HTTP; Thu, 13 Jan 2011 09:25:31 -0800 (PST)
In-Reply-To: <4D2EE067.3010102@kddilabs.jp>
References: <AANLkTimUgYk7FTi-F5kM_wfxmmG68ZCxKWHxKS_QR-Rk@mail.gmail.com> <4D2EE067.3010102@kddilabs.jp>
Date: Thu, 13 Jan 2011 09:25:31 -0800
Message-ID: <AANLkTikCFe=aO_7R=JtpU0E5hNQpi_ViUWGLaRU3oEuq@mail.gmail.com>
From: Vishwas Manral <vishwas.ietf@gmail.com>
To: Hidetoshi Yokota <yokota@kddilabs.jp>
Content-Type: text/plain; charset=ISO-8859-1
Cc: clouds@ietf.org
Subject: Re: [clouds] draft-yokota-cloud-service-mobility
X-BeenThere: clouds@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Clouds pre-BOF discussion list <clouds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/clouds>, <mailto:clouds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clouds>
List-Post: <mailto:clouds@ietf.org>
List-Help: <mailto:clouds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clouds>, <mailto:clouds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jan 2011 17:26:41 -0000

Hi Hidetoshi-san,

>> 2. Scalability issues will occur if keepalives all go to the manager
>> node. In my view there can be a heirarchy of keepalives.
>
> Are you suggesting an intermediate node that collects the keep-alives
> from some group of managed nodes and sends an aggregated message to the
> manager?
Yes I am suggesting one such approach. You have to understand the
number of resources that need to be monitored is very high.

A heirarchical approach will certainly help. Ofcourse there needs to
be redundancy at each layer so that a failure in the intermediate does
not lead to failures that may not necessarily be occuring.

>> 3. There should be a heirarchy of manager nodes too, considering the
>> number of Execution nodes that need to be managed. So there should be
>> a messaging exchange allowed between Manager and Manager node.
>
> I see. Either hierarchical structure (manager of managers) or
> peer-to-peer structure (inter-manager) will be needed when the scale
> becomes larger.
That is correct. Like I mentioned I am trying to come to a PCE model.
It is the same problem with different data. In PCE all the network
nodes and interface properties are kept for Traffic Engineering
purposes.
https://datatracker.ietf.org/wg/pce/

>> 4. All TLV and headers should have length of 16 bits atleast. 8 bits
>> is not scalable at all with the amount of information that is there.
>
> Good suggestion. Will expand the field length.
This is extremely essential and we have seen issues in older protocols
whih have used 8 bit length or type fields.

>> 5. There needs to be authentication in the packets to provide some security.
>
> Ok. Maybe, some option that can carry MAC (Message Authentication Code)
> should be added. Or, do you think the whole message should be encrypted?
> In that case, we should mandate IPSec connection between the Manager
> Node and Execution Node.
It is IPsec not IPSec. Yes we need to add a hash to the packet. If we
are working over TCP we can use the TCP-AO or TCP-MD5 for the same.

>> 6. There needs to be async messaging allowed both from server to
>> client and client to server.
> Ok. I will add something like NOTIFY manage, which is spontaneous and
> can
Great!!!

>>7. There is already a PCE framework that exists. We need to look at
>> it. It is used for simialr purposes in a TE network.
>
> Could you tell me any reference document such as RFC or conference
> paper, please?
Sent the link above.

Thanks,
Vishwas

> Regards,
> --
> Hidetoshi
>
>> Thanks,
>> Vishwas