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

Suresh Krishnan <suresh.krishnan@ericsson.com> Thu, 29 November 2012 20:28 UTC

Return-Path: <suresh.krishnan@ericsson.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 61B3221F8C14 for <netext@ietfa.amsl.com>; Thu, 29 Nov 2012 12:28:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 34DnWSq5kD6O for <netext@ietfa.amsl.com>; Thu, 29 Nov 2012 12:28:51 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id E104421F8C18 for <netext@ietf.org>; Thu, 29 Nov 2012 12:28:50 -0800 (PST)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id qATKbBvZ015943; Thu, 29 Nov 2012 14:37:13 -0600
Received: from [142.133.112.133] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.181) with Microsoft SMTP Server (TLS) id 8.3.279.1; Thu, 29 Nov 2012 15:28:35 -0500
Message-ID: <50B7C4E3.8030606@ericsson.com>
Date: Thu, 29 Nov 2012 15:26:11 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: netext issue tracker <trac+netext@grenache.tools.ietf.org>
References: <066.92fae5892dd47f6df59125978f3b0285@trac.tools.ietf.org>
In-Reply-To: <066.92fae5892dd47f6df59125978f3b0285@trac.tools.ietf.org>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-netext-pmipv6-flowmob@tools.ietf.org, netext@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
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, 29 Nov 2012 20:28:51 -0000

On 11/21/2012 07:34 AM, netext issue tracker wrote:
> #15: use "update notification" for FMI/FMA
> 
>  If we go for pBU triggered by LMA signaling, the solution should use
>  update notification UPN/UPA from draft-krishnan-netext-update-
>  notifications (If adopted by the WG) instead of FMI/FMA which are
>  functionally similar.

I am supportive of doing this *if* the timelines match. I think it would
be a waste to hold up the flowmob draft just so that it can use the
update notification message (especially since, as Behcet said, it is
still an individual draft).

Thanks
Suresh