Re: [netext] Consensus call: Adopt selective IPv4 offloading feature as specified in I-D draft-gundavelli-netext-pmipv6-sipto-option
liu dapeng <maxpassion@gmail.com> Thu, 18 August 2011 08:41 UTC
Return-Path: <maxpassion@gmail.com>
X-Original-To: netext@ietfa.amsl.com
Delivered-To: netext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 875D821F8AE1 for <netext@ietfa.amsl.com>; Thu, 18 Aug 2011 01:41:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iCEjDs3X8+Gf for <netext@ietfa.amsl.com>; Thu, 18 Aug 2011 01:41:32 -0700 (PDT)
Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by ietfa.amsl.com (Postfix) with ESMTP id EDD8721F8A64 for <netext@ietf.org>; Thu, 18 Aug 2011 01:41:31 -0700 (PDT)
Received: by iye1 with SMTP id 1so3228927iye.27 for <netext@ietf.org>; Thu, 18 Aug 2011 01:42:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=hILIndj9gfAIxbeuSPHLPjcLYpc14OHUYxDOlVa2yqA=; b=QqwQ7a0YH+3ywzaPB2pt0iQLASIB11Ik+Zr0KmfSkez+F+g/Rgc209cBq7GiK/P4Gp 3rTnbw1Qu6eMfYmf9JAcV5mX9S6ESZ2Ju5yzTMG7vFpO00xRNzWtARDDP8wFjnFSXC2/ stFlMuRpGRhTZ6i6O+tn108JHM1T1qc9jKaMI=
MIME-Version: 1.0
Received: by 10.231.85.12 with SMTP id m12mr1046132ibl.60.1313656945302; Thu, 18 Aug 2011 01:42:25 -0700 (PDT)
Received: by 10.231.79.145 with HTTP; Thu, 18 Aug 2011 01:42:24 -0700 (PDT)
In-Reply-To: <CA6867A8.1CF3A%basavaraj.patil@nokia.com>
References: <CA6867A8.1CF3A%basavaraj.patil@nokia.com>
Date: Thu, 18 Aug 2011 16:42:24 +0800
Message-ID: <CAKcc6AfF_2hCWZyg6A2674ZYPSpL6EK6CfEqz1+bO=4zP5GF0Q@mail.gmail.com>
From: liu dapeng <maxpassion@gmail.com>
To: Basavaraj.Patil@nokia.com
Content-Type: text/plain; charset="ISO-8859-1"
Cc: netext@ietf.org
Subject: Re: [netext] Consensus call: Adopt selective IPv4 offloading feature as specified in I-D draft-gundavelli-netext-pmipv6-sipto-option
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Mailing list for discusion of extensions to network mobility protocol, i.e PMIP6. " <netext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netext>, <mailto:netext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netext>
List-Post: <mailto:netext@ietf.org>
List-Help: <mailto:netext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netext>, <mailto:netext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Aug 2011 08:41:32 -0000
1. YES 2. YES BTW, I assume this solution would be more suitable only for S2a interface if considering using it in 3GPP? Regards, Dapeng Liu 2011/8/11, Basavaraj.Patil@nokia.com <Basavaraj.Patil@nokia.com>: > > > At IETF81, the Netext WG discussed the proposal: "IP Traffic Offload > Selector Option for Proxy Mobile IPv6" > <draft-gundavelli-netext-pmipv6-sipto-option-01.txt> > > Abstract > > This specification defines a mechanism and a related mobility option > for carrying IP Offload traffic selectors between a mobile access > gateway and a local mobility anchor in a Proxy Mobile IPv6 domain. > Based on the received offload flow selectors from the local mobility > anchor, a mobile access gateway can enable offload traffic rule on > the selected IP flows. > > Please note that the offloading of traffic from the MAG is limited to > IPv4 flow only using NAT44 functionality. > > The general consensus of the room at the IETF81 WG meeting was that > this is a relevant problem and should be solved by the WG. As per the > minutes: > " > 11 people think we should solve the problem, 4 think we should not. > " > > As per process, the same question is now being asked on the Netext WG > ML before making a decision. > > Questions: > > 1. Is the solution to offloading specific IPv4 flows from a MAG of > interest to the WG? > > Yes [ ] > No [ ] > > 2. Should we adopt as WG I-D: > draft-gundavelli-netext-pmipv6-sipto-option-01.txt which will serve as > the starting point in specifying the solution? > > Yes [ ] > No [ ] > > Please respond to the above questions by August 18, 2011 on the ML. > > -Chairs > > The slides presented at the meeting are available in the IETF81 > proceedings. Minutes have been posted to the ML and are also available > at: http://www.ietf.org/proceedings/81/minutes/netext.txt > > > _______________________________________________ > netext mailing list > netext@ietf.org > https://www.ietf.org/mailman/listinfo/netext > -- ------ Best Regards, Dapeng Liu
- [netext] Consensus call: Adopt selective IPv4 off… Basavaraj.Patil
- Re: [netext] Consensus call: Adopt selective IPv4… Jouni
- Re: [netext] Consensus call: Adopt selective IPv4… Sri Gundavelli
- Re: [netext] Consensus call: Adopt selective IPv4… zhou.xingyue
- Re: [netext] Consensus call: Adopt selective IPv4… Ahmad Muhanna
- Re: [netext] Consensus call: Adopt selective IPv4… pierrick.seite
- Re: [netext] Consensus call: Adopt selective IPv4… zhu.chunhui
- Re: [netext] Consensus call: Adopt selective IPv4… Jiang Dong
- Re: [netext] Consensus call: Adopt selective IPv4… Basavaraj.Patil
- Re: [netext] Consensus call: Adopt selective IPv4… Behcet Sarikaya
- Re: [netext] Consensus call: Adopt selective IPv4… Carl Williams
- Re: [netext] Consensus call: Adopt selective IPv4… Hidetoshi Yokota
- Re: [netext] Consensus call: Adopt selective IPv4… Jinho Kim
- Re: [netext] Consensus call: Adopt selective IPv4… 马骁
- Re: [netext] Consensus call: Adopt selective IPv4… Mohana Jeyatharan
- Re: [netext] Consensus call: Adopt selective IPv4… Mohana Jeyatharan
- Re: [netext] Consensus call: Adopt selective IPv4… liu dapeng
- Re: [netext] Consensus call: Adopt selective IPv4… Hui Deng