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

ma yc <ycma610103@gmail.com> Tue, 17 March 2009 11:01 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 AC7063A6B26 for <mif@core3.amsl.com>; Tue, 17 Mar 2009 04:01:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.479
X-Spam-Level:
X-Spam-Status: No, score=-2.479 tagged_above=-999 required=5 tests=[AWL=0.120, 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 lR51gubC+7lf for <mif@core3.amsl.com>; Tue, 17 Mar 2009 04:01:17 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.171]) by core3.amsl.com (Postfix) with ESMTP id BA2433A6A94 for <mif@ietf.org>; Tue, 17 Mar 2009 04:01:17 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 27so3733212wfd.31 for <mif@ietf.org>; Tue, 17 Mar 2009 04:02:00 -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:cc:content-type :content-transfer-encoding; bh=2yftLaSaYV5LbCD7lyJpqZmnSHpdWJhvR+cdVp0wycI=; b=PMtgDmQlZMwP2LYmppiltCPqPdf+5JtqjRo8SH+rsPNB1kUFNzf4D852JDZN04ozEx Z1c7rENGN7AgqF1xCeS/dxUZmqq0xneoQ+wnPaJylCGAjjFziqaNWun7wlBs+u/TDOi4 Gt4GjK0KmqN8oNCOnAWoTYqnCbOxOTG/1c8Vg=
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:content-transfer-encoding; b=QQb8CHB/9uHhrxCYo+vr+0a2L42dLsLyAzTr44xzQfwVcrzTv1rTrsVHL6nZzQ5Aw2 S/tTvK6Mq06/V/dzGElMCYip0HNCBqEOVkRtNJMzY8vbqHGGpLm4/XWtrOwBbz6FdgPP afRc18GNT8P2U19mKs5Sgmag3kl4fotLbHi6M=
MIME-Version: 1.0
Received: by 10.142.238.4 with SMTP id l4mr2717782wfh.242.1237287720875; Tue, 17 Mar 2009 04:02:00 -0700 (PDT)
In-Reply-To: <5dca10d30903170225s332bc12bkae4da4281d5aaf30@mail.gmail.com>
References: <mailman.25.1237230002.1293.mif@ietf.org> <e360024e0903162241n245af6e0v5877d86cedc35ef3@mail.gmail.com> <5dca10d30903170225s332bc12bkae4da4281d5aaf30@mail.gmail.com>
Date: Tue, 17 Mar 2009 19:02:00 +0800
Message-ID: <e360024e0903170402u4450129by7f93774fad42e528@mail.gmail.com>
From: ma yc <ycma610103@gmail.com>
To: Min Hui <huimin.cmcc@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: mif@ietf.org
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 11:01:18 -0000

Hi Min

Thank you for your reply. Please check inline.

Yuanchen

2009/3/17 Min Hui <huimin.cmcc@gmail.com>:
> Hi, Yuanchen
>
> For the first question, there are two situations.
>
> 1. the host sends data using one of its interfaces, and the correspond
> node reply to the address of this interface. it's has no problem, the
> host will receive the reply by the same interface.
> 2. the network side initiate the communication, the host name will be
> used in the DNS query to get a list of addresses, which one should be
> choosed depends on the network side policy.
yuanchen> i agree with this scenario that the DNS query may result
in a list of addresses. But i still don't understand what "network
side initiated"
means. IP flow is end-to-end and the other end node should
make the DNS query and make the decision. Do you mean that the other end
node should get some information from somewhere in the network to help the
decision making? I think the requirement should be clarified.

>
> For the second question, the element would be the gateway which in
> charge of all the interfaces, e.g. PDN GW in 3GPP architecture, LMA in
> PMIP domain.
yuanchen> I do not think LMA is a good example for MIF, since the LMA is for
mobility management. PND GW in 3GPP also has the function of LMA.
Such scenario sounds more like extension to PMIP for multiple interface node
support. Netlmm may be better place for such topic.

>
> Thanks for your comments.
>
> - Hui Min
>
> 2009/3/17 ma yc <ycma610103@gmail.com>:
>> 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
>>> >
>> _______________________________________________
>> mif mailing list
>> mif@ietf.org
>> https://www.ietf.org/mailman/listinfo/mif
>>
>