IETF Logo Mail Archive

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

"Sri Gundavelli (sgundave)" <sgundave@cisco.com> Wed, 13 February 2013 23:40 UTC

Return-Path: <sgundave@cisco.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 4672421F8B3A for <netext@ietfa.amsl.com>; Wed, 13 Feb 2013 15:40:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 jTQmww4XKZWM for <netext@ietfa.amsl.com>; Wed, 13 Feb 2013 15:40:31 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id B81F721F866D for <netext@ietf.org>; Wed, 13 Feb 2013 15:40:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1640; q=dns/txt; s=iport; t=1360798831; x=1362008431; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=XFBFY5PpbkpX2ZPOmPz3cJrJbnjjLEk1egDce8Ictzo=; b=KaFAfzznnXbDLwh0Q52hFJEM1dnieJl52OA4e1U4niQg6JJV11kFOrxM Yt4F70/tVDCb8Txhc3GiYiBECMMSh+sO8O9R5ZjBcpj401QITpdsw1Dsj m5pVPWihH8YRjIOIvB/1E0DFw0XPmVnyTlYsMGoEIDGZ9JIqOZ3oG81ep g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAOIiHFGtJXG8/2dsb2JhbABFwG4Wc4IhAQQBAQE3NAkCEgEIIhQ3CyUCBAENBQiICgy/bo1Ug09hA5dBiiaFEIMGgic
X-IronPort-AV: E=Sophos;i="4.84,660,1355097600"; d="scan'208";a="176822760"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-2.cisco.com with ESMTP; 13 Feb 2013 23:40:31 +0000
Received: from xhc-aln-x05.cisco.com (xhc-aln-x05.cisco.com [173.36.12.79]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id r1DNeVFl019304 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 13 Feb 2013 23:40:31 GMT
Received: from xmb-aln-x03.cisco.com ([169.254.6.8]) by xhc-aln-x05.cisco.com ([173.36.12.79]) with mapi id 14.02.0318.004; Wed, 13 Feb 2013 17:40:31 -0600
From: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
To: netext issue tracker <trac+netext@trac.tools.ietf.org>, "draft-ietf-netext-pmipv6-flowmob@tools.ietf.org" <draft-ietf-netext-pmipv6-flowmob@tools.ietf.org>, "cjbc@it.uc3m.es" <cjbc@it.uc3m.es>
Thread-Topic: [netext] #15: use "update notification" for FMI/FMA
Thread-Index: AQHOCkOCisndsqzZhEilieC/jKTKGw==
Date: Wed, 13 Feb 2013 23:40:30 +0000
Message-ID: <24C0F3E22276D9438D6F366EB89FAEA81015C1E3@xmb-aln-x03.cisco.com>
In-Reply-To: <081.da5e4c25a1a1923379bffc472009f9a0@trac.tools.ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.2.3.120616
x-originating-ip: [10.154.141.17]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <EBE98E9869A30A4E95EF02E030C22597@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "netext@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: Wed, 13 Feb 2013 23:40:33 -0000

Ack. Agree with this.

Regards
Sri



On 2/13/13 10:49 AM, "netext issue tracker"
<trac+netext@trac.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

v2.23.0 | Report a Bug | By Email