IETF Logo Mail Archive

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

"Rajeev Koodli (rkoodli)" <rkoodli@cisco.com> Thu, 14 February 2013 05:53 UTC

Return-Path: <rkoodli@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 1A4EE21F8778 for <netext@ietfa.amsl.com>; Wed, 13 Feb 2013 21:53:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 wb4WklTSFr7K for <netext@ietfa.amsl.com>; Wed, 13 Feb 2013 21:53:30 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 2B0A721F8611 for <netext@ietf.org>; Wed, 13 Feb 2013 21:53:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1824; q=dns/txt; s=iport; t=1360821210; x=1362030810; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=HU23BDPMTu/HQo8/KXLF14FR146vo+k0AGaqn5mjFSM=; b=AKPoYPM34mXLqianT4xqBpckFyeUU2jZfPX8KZp1EBNPJSkK+OuT2eZw x2Ey6oTn1Djqo8xGIh5vaJzHhRf8nIUKnFyuAM940N3ERMSWhLLGJ14px WkVf97LbK5SOb2QL8stlI2o9iR2/a4bjskvpdmcez2Rh2cQi9mZe1XKPJ 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAHZ7HFGtJV2Z/2dsb2JhbABEwG0Wc4IhAQQBAQE3NAkCEgEIIhQ3CyUCBAENBQiICgzADI06GoNPYQOXQYomhRCDBoFyNQ
X-IronPort-AV: E=Sophos;i="4.84,662,1355097600"; d="scan'208";a="176947204"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-8.cisco.com with ESMTP; 14 Feb 2013 05:53:29 +0000
Received: from xhc-rcd-x02.cisco.com (xhc-rcd-x02.cisco.com [173.37.183.76]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r1E5rT5p027095 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 14 Feb 2013 05:53:29 GMT
Received: from xmb-aln-x04.cisco.com ([169.254.9.127]) by xhc-rcd-x02.cisco.com ([173.37.183.76]) with mapi id 14.02.0318.004; Wed, 13 Feb 2013 23:53:29 -0600
From: "Rajeev Koodli (rkoodli)" <rkoodli@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: AQHOChrp9PVaofNixkaBfN3Pn4qyQ5h4udMA
Date: Thu, 14 Feb 2013 05:53:29 +0000
Message-ID: <7C52FDEBC843C44DBAF2CA6A30662C6D1DE278@xmb-aln-x04.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.1.120420
x-originating-ip: [10.21.75.167]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <C77278558CE6C84D9FD2F17E2B5F3593@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: Thu, 14 Feb 2013 05:53:31 -0000

Carlos,

I am not sure about this.. I would like us to wrap up the the FM draft,
without yet another dependency (cf. Suresh's earlier email on #15). So,
yes, please keep FMI/FMA and finish the doc.

Thanks.

-Rajeev


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