Re: [mif] about draft-hui-ip-multiple-connections-ps-02

Min Hui <huimin.cmcc@gmail.com> Mon, 23 March 2009 01:29 UTC

Return-Path: <huimin.cmcc@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 7677A3A6809 for <mif@core3.amsl.com>; Sun, 22 Mar 2009 18:29:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.422
X-Spam-Level:
X-Spam-Status: No, score=-2.422 tagged_above=-999 required=5 tests=[AWL=0.177, 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 X1b3XNB5Daub for <mif@core3.amsl.com>; Sun, 22 Mar 2009 18:29:16 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.170]) by core3.amsl.com (Postfix) with ESMTP id AA45B3A67A4 for <mif@ietf.org>; Sun, 22 Mar 2009 18:29:16 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 24so2470562wfg.31 for <mif@ietf.org>; Sun, 22 Mar 2009 18:30:06 -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=Mh/i0p2bbA78OnnD3V0DF+qC40Ms3/AaarxNPUDynFc=; b=X++51Hs/ujo6dlHGXXvtglQD6HWGCBPC0sZbOfJKrfG/Ya3c0ZWAUMJ/YXFGg3ej6r LoBsyGHc1u/+3+vZ+R3e16hXRinP+HJEa1l3MyS5mXmJgyjgjCAsa9/dFB9aPcqI+2T6 D7/bIHishjR0J/4GRZpm7EnhlSRZ7Pv7+rWow=
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=uFkzdjgyxK7OiioXqKsKBM0GV9nSMDNbiYJHtVdYbOtKOyhtA5cogQU/gh0Dgje1o7 HDcYLCAAoMdIFiOb6qomgCvet3BEPubmarfOFlvJfej+3Z16OgxhhAWulu1OGbKgjMQo pHOJ6d+CGrVPJenAPmtOYi4rjCnaZqPrPN0zE=
MIME-Version: 1.0
Received: by 10.142.133.19 with SMTP id g19mr2605777wfd.116.1237771806091; Sun, 22 Mar 2009 18:30:06 -0700 (PDT)
In-Reply-To: <318661.85907.qm@web111415.mail.gq1.yahoo.com>
References: <49BD54AD.1080504@it.uc3m.es> <5dca10d30903160249k39f5d8c3ndcd78ad28b461b44@mail.gmail.com> <49BE88B9.6010306@it.uc3m.es> <5dca10d30903170231t6994eabbr397070506486c71c@mail.gmail.com> <49C20C88.7060700@it.uc3m.es> <5dca10d30903200147g3ac5bde0rd9b1990bce3e49ab@mail.gmail.com> <318661.85907.qm@web111415.mail.gq1.yahoo.com>
Date: Mon, 23 Mar 2009 09:30:06 +0800
Message-ID: <5dca10d30903221830w541b5e47v62c7e971c7b9562e@mail.gmail.com>
From: Min Hui <huimin.cmcc@gmail.com>
To: Behcet Sarikaya <sarikaya@ieee.org>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: mif <mif@ietf.org>
Subject: Re: [mif] about draft-hui-ip-multiple-connections-ps-02
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: Mon, 23 Mar 2009 01:29:17 -0000

Hi, Behcet

Pls see my reply below, thx.

2009/3/21, Behcet Sarikaya <behcetsarikaya@yahoo.com>:
>
> Hi Min,
>   Pls see inline, thx.
>
> Behcet
>
> ________________________________
> From: Min Hui <huimin.cmcc@gmail.com>
> To: marcelo bagnulo braun <marcelo@it.uc3m.es>
> Cc: mif <mif@ietf.org>
> Sent: Friday, March 20, 2009 3:47:24 AM
> Subject: Re: [mif] about
> draft-hui-ip-multiple-connections-ps-02
>
> Hi,
>
> pls see inline reply. thx.
>
> 2009/3/19 marcelo bagnulo braun <marcelo@it.uc3m.es>:
> > Min Hui escribió:
> >>
> >>>
> >>>>
> >>>>    2.2.3. TOS consideration
> >>>>
> >>>>  TOS can be a parameter of routing item to indicate which kind of IP
> >>>>  data is suitable to deliver by this routing. The multiple interfaces
> >>>>  will connect to multiple access networks, so that the preference of
> >>>>  TOS need to be merged to have a better performance of data delivery.
> >>>>  For example, the WiFi access could indicate itself has broader
> >>>>  bandwidth comparing with 2G access, and set the TOS as broad
> >>>>  bandwidth. When another interface connects the Ethernet, the TOS is
> >>>>  also set as broad bandwidth preferred. In this situation, it needs
> >>>>  some mechanism to merge and reorder the TOS getting form multiple
> >>>>  interfaces.
> >>>>
> >>>> I am not sure how widely used is this...
> >>>>
> >>>> A: As depicted in RFC1122, TOS is a necessary parameter to choose a
> >>>> suitable routing. And different applications have different
> >>>> requirements of access network, which can be reflected as TOS. So we
> >>>> think TOS will be useful in multiple interface situations.
> >>>>
> >>>>
> >>>>
> >>>
> >>> right, my question was how widely used is this. I mean how much of the
> >>> internet traffic actually sets the TOS?
> >>>
> >>
> >> The 3G network use TOS as one of the QoS parameters, and we suppose to
> >> use it in the multiple interfaces situation.
> >>
> >>
> >
> > ok, but does any other network uses this?
> > I mean, if only 3g networks use this, this is only a problem when
> > simultaneously connecting to multiple 3G networks, so i am not sure how
> > common this is
> There are 3GPP and 3GPP2 mobile network which have been deployed, both
> of them support it.
> Some network use it for Wifi access network as well.
> There are more and more motivation to do different service quality
> categorization,
> such as put the p2p more low level.
> [behcet] I believe you. I think it would be more convincing if you could
> give us which standard, e.g. 23.401 this is mentioned. Without any evidence
> we just need to believe you..
>
3GPP standard 24.008 can be refered to, thx.

>