Re: [netext] Needs of traffic spec. on MAG?

Behcet Sarikaya <behcetsarikaya@yahoo.com> Fri, 06 August 2010 20:20 UTC

DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=xfYy1JLoIy6x0qYmnJg0PMglVi7Q/y8Hy0yfZwwyOXA3JnXWNF0M418ie3ZYgyVAlzhPTJRvPUt88QmQc5pwfllzspedYiJrci4bnMOHXKIFBdSKsdrQBSNoTgrB6rvIhcEo6TSVwyFFW+ioGZHJDogKh01THZVoIFVr8Q+BHKc=;
Message-ID: <389999.65707.qm@web111402.mail.gq1.yahoo.com>
References: <C87AE9B1.46667%sgundave@cisco.com>
Date: Fri, 06 Aug 2010 13:21:16 -0700
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
To: Sri Gundavelli <sgundave@cisco.com>, cjbc@it.uc3m.es
In-Reply-To: <C87AE9B1.46667%sgundave@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Cc: netext@ietf.org
Subject: Re: [netext] Needs of traffic spec. on MAG?
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>

----- Original Message ----
> From: Sri Gundavelli <sgundave@cisco.com>
> To: Behcet Sarikaya <sarikaya@ieee.org>; cjbc@it.uc3m.es
> Cc: netext@ietf.org
> Sent: Sun, August 1, 2010 11:06:57 AM
> Subject: Re: [netext] Needs of traffic spec. on MAG?
> 
> Hi Behcet,
> 
> You are right, we have to leverage the work done in MEXT. The  Traffic
> Selectors for IPv4 and IPv6 flows can be from the mext binary TS  work. I
> think, Carlos did provide the TS option with a opaque field for  including
> the filter. 

Current definition is only allowing TS like binary TS of George to be used. 
There could be others like language based flow descriptions proposed in the 
past. Is this reusing mext work? 







>So, the semantics of the flow identification are from  MEXT work,
> which took lot of time. Now, how the filters are exchanged in  PMIPv6
> signaling is specific to this draft.

The real flow mobility work in mext was based on Flow Identification Mobility 
Option defined draft-ietf-mext-flow-binding-06.
If we don't reuse it we are missing the whole mext work and trying to reinvent 
the wheel.

 It is not signaling specifics.

Regards,

Behcet

Re: [netext] Needs of traffic spec. on MAG? Carlos Jesús Bernardos Cano
[netext] Needs of traffic spec. on MAG? Youn-Hee Han
Re: [netext] Needs of traffic spec. on MAG? Carlos Jesús Bernardos Cano
Re: [netext] Needs of traffic spec. on MAG? Laganier, Julien
[netext] FW: Needs of traffic spec. on MAG? Youn-Hee Han
[netext] FW: Needs of traffic spec. on MAG? Youn-Hee Han
Re: [netext] Needs of traffic spec. on MAG? Koodli, Rajeev
Re: [netext] FW: Needs of traffic spec. on MAG? Behcet Sarikaya
Re: [netext] Needs of traffic spec. on MAG? Behcet Sarikaya
Re: [netext] Needs of traffic spec. on MAG? Sri Gundavelli
Re: [netext] Needs of traffic spec. on MAG? Laganier, Julien
Re: [netext] Needs of traffic spec. on MAG? Tran Minh Trung
Re: [netext] Needs of traffic spec. on MAG? Koodli, Rajeev
Re: [netext] Needs of traffic spec. on MAG? Tran Minh Trung
Re: [netext] Needs of traffic spec. on MAG? Rajeev Koodli
Re: [netext] Needs of traffic spec. on MAG? Carlos Jesús Bernardos Cano
Re: [netext] Needs of traffic spec. on MAG? Sri Gundavelli
Re: [netext] Needs of traffic spec. on MAG? Sri Gundavelli
Re: [netext] Needs of traffic spec. on MAG? Behcet Sarikaya
Re: [netext] Needs of traffic spec. on MAG? Sri Gundavelli
Re: [netext] Needs of traffic spec. on MAG? Behcet Sarikaya
Re: [netext] Needs of traffic spec. on MAG? Sri Gundavelli
Re: [netext] Needs of traffic spec. on MAG? Carlos Jesús Bernardos Cano
Re: [netext] Needs of traffic spec. on MAG? Sri Gundavelli
Re: [netext] Needs of traffic spec. on MAG? Laganier, Julien
Re: [netext] Needs of traffic spec. on MAG? Laganier, Julien
Re: [netext] Needs of traffic spec. on MAG? Laganier, Julien
Re: [netext] Needs of traffic spec. on MAG? Carlos Jesús Bernardos Cano
Re: [netext] Needs of traffic spec. on MAG? Laganier, Julien
Re: [netext] Needs of traffic spec. on MAG? Laganier, Julien
Re: [netext] Needs of traffic spec. on MAG? Youn-Hee Han