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

Behcet Sarikaya <sarikaya2012@gmail.com> Wed, 13 February 2013 19:26 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 4973421F86B3 for <netext@ietfa.amsl.com>; Wed, 13 Feb 2013 11:26:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.397
X-Spam-Level:
X-Spam-Status: No, score=-2.397 tagged_above=-999 required=5 tests=[AWL=0.202, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
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 K7LkVrY9G+yz for <netext@ietfa.amsl.com>; Wed, 13 Feb 2013 11:26:56 -0800 (PST)
Received: from mail-la0-x22e.google.com (mail-la0-x22e.google.com [IPv6:2a00:1450:4010:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 2669021F86B2 for <netext@ietf.org>; Wed, 13 Feb 2013 11:26:55 -0800 (PST)
Received: by mail-la0-f46.google.com with SMTP id fq12so1538378lab.33 for <netext@ietf.org>; Wed, 13 Feb 2013 11:26:55 -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=aK3RDf0Xuxkyj8N7xGouB6m/GqoN3L7wxbwN0Ji0Usc=; b=DmRbP3gKs98LA9lS2oTZCaHuiEnnYqsd7tarSpHiRDk797bfjVbmTqHStmJbaJr/6B sxBcpvdrii0N6MQ0XDwBrl34m7mTFVbKMswGXM6MpI3DC+3f9yJaSsGbge284y570ufe ZOPE1MELx4P2VEeIEWXvHtyeFOqC0d14/pLozifyGuROM6h2R38sMVVzBsvubOka63iM 15d+BRbqO53hl6nigztPUR2QGCgmHjd5kcaDzvT2+s6xWGYTHkzqKmqz1u6uHjZg+PfV /KfzIc/fWusayPvQWSBlhQjuhGBowR4lecQHRjd0JUxNj/j20OYmZTQCCL6m0yV3zkrx +udA==
MIME-Version: 1.0
X-Received: by 10.112.28.102 with SMTP id a6mr9065599lbh.109.1360783614892; Wed, 13 Feb 2013 11:26:54 -0800 (PST)
Received: by 10.114.28.168 with HTTP; Wed, 13 Feb 2013 11:26:54 -0800 (PST)
In-Reply-To: <081.da5e4c25a1a1923379bffc472009f9a0@trac.tools.ietf.org>
References: <066.92fae5892dd47f6df59125978f3b0285@trac.tools.ietf.org> <081.da5e4c25a1a1923379bffc472009f9a0@trac.tools.ietf.org>
Date: Wed, 13 Feb 2013 13:26:54 -0600
Message-ID: <CAC8QAcfyubWwvnEn54hEojhWypMFdN-LJyS=ady4pGrzJLU_sQ@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: netext@ietf.org
Content-Type: multipart/alternative; boundary=f46d040168b3fb5b9904d5a01f60
Cc: 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:26:57 -0000

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
>