Re: [mif] mif Digest, Vol 5, Issue 18
<pierrick.seite@orange-ftgroup.com> Tue, 17 March 2009 08:54 UTC
Return-Path: <pierrick.seite@orange-ftgroup.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 A51483A6998 for <mif@core3.amsl.com>; Tue, 17 Mar 2009 01:54:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level:
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 kp6bG3fDOszj for <mif@core3.amsl.com>; Tue, 17 Mar 2009 01:54:27 -0700 (PDT)
Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com [195.101.245.15]) by core3.amsl.com (Postfix) with ESMTP id 67B833A6827 for <mif@ietf.org>; Tue, 17 Mar 2009 01:54:27 -0700 (PDT)
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959); Tue, 17 Mar 2009 09:55:09 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 17 Mar 2009 09:55:08 +0100
Message-ID: <DD8B8FEBBFAF9E488F63FF0F1A69EDD10597D786@ftrdmel1>
In-Reply-To: <e360024e0903162241n245af6e0v5877d86cedc35ef3@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [mif] mif Digest, Vol 5, Issue 18
Thread-Index: AcmmwwGKXgngl4vHRuuFyIfYQr/NEgAGc/QA
References: <mailman.25.1237230002.1293.mif@ietf.org> <e360024e0903162241n245af6e0v5877d86cedc35ef3@mail.gmail.com>
From: pierrick.seite@orange-ftgroup.com
To: ycma610103@gmail.com, mif@ietf.org
X-OriginalArrivalTime: 17 Mar 2009 08:55:09.0810 (UTC) FILETIME=[1392AD20:01C9A6DE]
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 08:54:28 -0000
Hi, > -----Message d'origine----- > De : mif-bounces@ietf.org [mailto:mif-bounces@ietf.org] De la part de ma > yc > Envoyé : mardi 17 mars 2009 06:41 > À : mif@ietf.org > Objet : Re: [mif] mif Digest, Vol 5, Issue 18 > > 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? > For instance, an aggregation router can be in charge of distributing the traffic. But, as Marcelo pointed out, there is an issue when the user is connected to different ISPs; "which entity for distributing the traffic" and "how to harmonize network policies" in that case... Regards, Pierrick > 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
- Re: [mif] mif Digest, Vol 5, Issue 18 ma yc
- Re: [mif] mif Digest, Vol 5, Issue 18 pierrick.seite
- Re: [mif] mif Digest, Vol 5, Issue 18 Min Hui
- Re: [mif] mif Digest, Vol 5, Issue 18 ma yc
- Re: [mif] mif Digest, Vol 5, Issue 18 ma yc
- Re: [mif] mif Digest, Vol 5, Issue 18 Min Hui
- Re: [mif] mif Digest, Vol 5, Issue 18 ma yc
- Re: [mif] mif Digest, Vol 5, Issue 18 marcelo bagnulo braun
- Re: [mif] mif Digest, Vol 5, Issue 18 Min Hui
- Re: [mif] mif Digest, Vol 5, Issue 18 marcelo bagnulo braun
- Re: [mif] mif Digest, Vol 5, Issue 18 Scott Brim
- Re: [mif] mif Digest, Vol 5, Issue 18 ma yc
- Re: [mif] mif Digest, Vol 5, Issue 18 Scott Brim
- Re: [mif] mif Digest, Vol 5, Issue 18 ma yc