Re: [mif] mif Digest, Vol 5, Issue 18

ma yc <ycma610103@gmail.com> Tue, 17 March 2009 05:40 UTC

Return-Path: <ycma610103@gmail.com>
X-Original-To: mif@core3.amsl.com
Delivered-To: mif@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 59AE53A6783 for <mif@core3.amsl.com>; Mon, 16 Mar 2009 22:40:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150, 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 tE6T86Ban-WY for <mif@core3.amsl.com>; Mon, 16 Mar 2009 22:40:30 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.172]) by core3.amsl.com (Postfix) with ESMTP id 945EB3A6452 for <mif@ietf.org>; Mon, 16 Mar 2009 22:40:30 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 27so3604409wfd.31 for <mif@ietf.org>; Mon, 16 Mar 2009 22:41:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=7xgBov1K98Xxdevdjfck/6EQCRYvwYnykIk4z+U54Go=; b=DSktPEgqRE+KWSVAWwBJqa3Nfn58x6H6+YQBNL7Sisnxfnw416seke9DXnoC8mXMwq tJO0q/Oj25t/1Q3m367sOr8BFqK0EGkVuf/XG9SZMIM3EymNfJmeLhq8U66XdFyEGZjU mex1OjdQ48evXxLLK7sx4cauPjQ300zrXojxA=
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 :content-type:content-transfer-encoding; b=VKzA35T+G6gcI7p0O3VKC57tXmUgLgnaks59x3f0O+Xj5DagBI3OES5Pk6ABQfFbYY vyhlwQPo3qQ7yTtKXKclTgMZv4hL1OZL5HsN8vUAcNedwWxsw9EudKjY4Kn7KSog8CpY aqd/vmsnZu2LBk7B/DnY2CxJ5qZlQNxsAST78=
MIME-Version: 1.0
Received: by 10.142.234.16 with SMTP id g16mr2583213wfh.264.1237268473389; Mon, 16 Mar 2009 22:41:13 -0700 (PDT)
In-Reply-To: <mailman.25.1237230002.1293.mif@ietf.org>
References: <mailman.25.1237230002.1293.mif@ietf.org>
Date: Tue, 17 Mar 2009 13:41:13 +0800
Message-ID: <e360024e0903162241n245af6e0v5877d86cedc35ef3@mail.gmail.com>
From: ma yc <ycma610103@gmail.com>
To: mif@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: Re: [mif] mif Digest, Vol 5, Issue 18
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Mar 2009 05:40:31 -0000

Hi, Min Hui,

I an also confused on the requirement 5.

As for the the flow directed to the multiple
interface node, why does the network side need
to decide which interface to forward the data?

The dst address of the packet should be used for routing.
The network just forwards the data according to the routing table.
I do not see the needs for interface selection to route the flow.

Also if you have the use case, i have the same concern
as macelo, which elememt will be in chcarge of
distributing the traffic?

Thank you.
Regards
Yuanchen

> Date: Mon, 16 Mar 2009 18:13:29 +0100
> From: marcelo bagnulo braun <marcelo@it.uc3m.es>
> Subject: Re: [mif] about draft-hui-ip-multiple-connections-ps-02
> To: Min Hui <huimin.cmcc@gmail.com>
> Cc: mif <mif@ietf.org>
> Message-ID: <49BE88B9.6010306@it.uc3m.es>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>

> >  5 Network side should be capable of distributing the IP flow
> >  according to some parameters, such as IP address prefix, network type
> >  and so on.
> >
> > i don't understnad what you mean by this one, could you expand?
> >
> > A: That is the policy in the network side. Corresponding to the policy
> > of sending data mentioned in the fourth bullet, the policy of
> > receiving data is also needed, which can be apply in the network side.
> > The network can determine forward a specific IP flow to which
> > interface of the destination host according to the policy.
> >
> >
>
> right, i see what you mean. I am not sure which element of the network
> would do that... i mean, are you assuming that all interfaces are being
> connected to the same ISP? If not, i am not sure how would you do this...
> > Regards, marcelo
> >