Re: [netext] #15: use "update notification" for FMI/FMA

Behcet Sarikaya <sarikaya2012@gmail.com> Wed, 13 February 2013 19:58 UTC

Return-Path: <sarikaya2012@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 9044B21E8037 for <netext@ietfa.amsl.com>; Wed, 13 Feb 2013 11:58:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.579
X-Spam-Level:
X-Spam-Status: No, score=-3.579 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SmDclEWW5rP9 for <netext@ietfa.amsl.com>; Wed, 13 Feb 2013 11:58:40 -0800 (PST)
Received: from mail-lb0-f175.google.com (mail-lb0-f175.google.com [209.85.217.175]) by ietfa.amsl.com (Postfix) with ESMTP id 5467021F866E for <netext@ietf.org>; Wed, 13 Feb 2013 11:58:40 -0800 (PST)
Received: by mail-lb0-f175.google.com with SMTP id n3so1209828lbo.6 for <netext@ietf.org>; Wed, 13 Feb 2013 11:58:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:reply-to:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=9QPzPFEk/bpaVGHvMx+SAncfTj8cp5JVSyEOb4eSgN4=; b=XlT0BDTgkwDiNdUuB07Uu+2vBc9dHPovxYz1m9xsiLl9bUw/1/vTsA/Hfxk7334hEI meaqaN6MYZbkcYzCkvNGrdwz9/Nr+kPYTGm1g5znOo4HHs1sTW9AYpNXdgYqU0G7eySj h2P+zxOYN29fnnSECS8IpZJqgDX+pwVn3AIf8PvA25rbVnxINkeO2d2E9VAdfnl74sT7 hAT1tkcHCzEPIUlhx/JpRbXYTXkmLwjIf0XJjs1uNQMvBxXbWhP0o7p1Qu9en2T5GpfQ +apeKW89pb8ByQ8oR+3DeSkcQdBc+HelJniuRWXQ+Nw5Q1Z1faIxl4yJ4kkwHDu0Ccmm Nksw==
MIME-Version: 1.0
X-Received: by 10.152.109.112 with SMTP id hr16mr18275344lab.38.1360785519233; Wed, 13 Feb 2013 11:58:39 -0800 (PST)
Received: by 10.114.28.168 with HTTP; Wed, 13 Feb 2013 11:58:39 -0800 (PST)
In-Reply-To: <1360784743.4099.105.camel@acorde.it.uc3m.es>
References: <066.92fae5892dd47f6df59125978f3b0285@trac.tools.ietf.org> <081.da5e4c25a1a1923379bffc472009f9a0@trac.tools.ietf.org> <CAC8QAcfyubWwvnEn54hEojhWypMFdN-LJyS=ady4pGrzJLU_sQ@mail.gmail.com> <1360784743.4099.105.camel@acorde.it.uc3m.es>
Date: Wed, 13 Feb 2013 13:58:39 -0600
Message-ID: <CAC8QAcdB-Yvs2UYewktVpGeF2HHXu1d4r-bcRCYu8UB2aGqzRw@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: cjbc@it.uc3m.es
Content-Type: multipart/alternative; boundary=bcaec54eea707d48b904d5a09104
Cc: netext@ietf.org, draft-ietf-netext-pmipv6-flowmob@tools.ietf.org
Subject: Re: [netext] #15: use "update notification" for FMI/FMA
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: sarikaya@ieee.org
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: Wed, 13 Feb 2013 19:58:41 -0000

Yes.



On Wed, Feb 13, 2013 at 1:45 PM, Carlos Jesús Bernardos Cano <
cjbc@it.uc3m.es> wrote:

> Hi Behcet,
>
> So you suggest to keep using the FMI?
>
> Carlos
>
> On Wed, 2013-02-13 at 13:26 -0600, Behcet Sarikaya wrote:
> > Hi Carlos,
> >
> > Here is what Suresh wrote on a similar issue:
> >
> > > What are we going to do with LRI/LRA defined in RFC 6705 by Suresh
> himself?
> >
> > Nothing :-). The LRI is not a generic notification message. It cannot be
> > used for other purposes than LR.
> > FMI also is not a generic notification message, it is quite similar to
> > LRI in semantics.
> >
> > Regards,
> >
> > Behcet
> >
> > On Wed, Feb 13, 2013 at 12:49 PM, netext issue tracker <trac
> > +netext@grenache.tools.ietf.org> wrote:
> >         #15: use "update notification" for FMI/FMA
> >
> >
> >
> >         Comment (by cjbc@it.uc3m.es):
> >
> >          (apologies for not addressing this until now)
> >
> >          Since draft-krishnan-netext-update-notifications became
> >         draft-ietf-netext-
> >          update-notifications, I'd be supportive of removing FMI/FMA
> >         and use the
> >          notification message to trigger PBU/PBA for flow mobility
> >         purposes. I
> >          think this would also help to address issue #17 (the MAG
> >         could also
> >          request moving a flow to the LMA, covering the MN initiated
> >         handover
> >          triggers documented there).
> >
> >          I'd like to ask the WG opinions on this: should we keep
> >         FMI/FMA or adopt
> >          the use of update notifications?
> >
> >         --
> >
> -------------------------------------+-------------------------------------
> >          Reporter:                           |       Owner:
> >          draft-ietf-netext-
> >           pierrick.seite@orange.com          |
> >          pmipv6-flowmob@tools.ietf.org
> >              Type:  enhancement              |      Status:  new
> >          Priority:  major                    |   Milestone:
> >         Component:  pmipv6-flowmob           |     Version:
> >
> >          Severity:  -                        |  Resolution:
> >          Keywords:                           |
> >
> -------------------------------------+-------------------------------------
> >
> >         Ticket URL:
> >         <https://trac.tools.ietf.org/wg/netext/trac/ticket/15#comment:1>
> >         netext <http://tools.ietf.org/netext/>
> >
> >         _______________________________________________
> >         netext mailing list
> >         netext@ietf.org
> >         https://www.ietf.org/mailman/listinfo/netext
> >
> >
>
>
>