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

<pierrick.seite@orange.com> Thu, 29 November 2012 17:42 UTC

Return-Path: <pierrick.seite@orange.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 5BDD721F8B40 for <netext@ietfa.amsl.com>; Thu, 29 Nov 2012 09:42:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level:
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, UNPARSEABLE_RELAY=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 rpmaOdaHNRrF for <netext@ietfa.amsl.com>; Thu, 29 Nov 2012 09:42:41 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id 3147021F8AFC for <netext@ietf.org>; Thu, 29 Nov 2012 09:42:41 -0800 (PST)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id 0CB393244A2; Thu, 29 Nov 2012 18:42:40 +0100 (CET)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.183]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id E29BE4C015; Thu, 29 Nov 2012 18:42:39 +0100 (CET)
Received: from PEXCVZYM12.corporate.adroot.infra.ftgroup ([fe80::81f:1640:4749:5d13]) by PEXCVZYH02.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0318.004; Thu, 29 Nov 2012 18:42:39 +0100
From: <pierrick.seite@orange.com>
To: "'sarikaya@ieee.org'" <sarikaya@ieee.org>
Thread-Topic: [netext] #15: use "update notification" for FMI/FMA
Thread-Index: AQHNzlSGDOVBlGfFEU6fGRER0Tg/X5gBFEZw
Date: Thu, 29 Nov 2012 17:42:38 +0000
Message-ID: <6471_1354210959_50B79E8F_6471_1459_1_81C77F07008CA24F9783A98CFD706F71073A73@PEXCVZYM12.corporate.adroot.infra.ftgroup>
References: <066.92fae5892dd47f6df59125978f3b0285@trac.tools.ietf.org> <CAC8QAcdUnKriXgUp1=UtUenwHAxwTRTwfwsVeN84QE=7E_=2sg@mail.gmail.com>
In-Reply-To: <CAC8QAcdUnKriXgUp1=UtUenwHAxwTRTwfwsVeN84QE=7E_=2sg@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.197.38.4]
Content-Type: multipart/alternative; boundary="_000_81C77F07008CA24F9783A98CFD706F71073A73PEXCVZYM12corpora_"
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2012.10.24.110314
Cc: "draft-ietf-netext-pmipv6-flowmob@tools.ietf.org" <draft-ietf-netext-pmipv6-flowmob@tools.ietf.org>, "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, 29 Nov 2012 17:42:42 -0000

Hi,

Issue #15 is valid if draft-krishnan is adopted.

Pierrick

De : Behcet Sarikaya [mailto:sarikaya2012@gmail.com]
Envoyé : jeudi 29 novembre 2012 18:11
À : SEITE Pierrick OLNC/OLN
Cc : draft-ietf-netext-pmipv6-flowmob@tools.ietf.org; netext@ietf.org
Objet : Re: [netext] #15: use "update notification" for FMI/FMA

Hi Pierrick,

I don't understand this issue.

Why should a WG draft in its late stages introduce a normative dependency on an individual draft?

draft-krishnan could be good but it could apply only to the future work possibly after it becomes an RFC.
What if during the process the messages names get changed?

Regards,

Behcet
On Wed, Nov 21, 2012 at 6:34 AM, netext issue tracker <trac+netext@grenache.tools.ietf.org<mailto:trac+netext@grenache.tools.ietf.org>> 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.

--
-------------------------------------+-------------------------------------
 Reporter:                           |      Owner:  draft-ietf-netext-
  pierrick.seite@orange.com<mailto:pierrick.seite@orange.com>          |  pmipv6-flowmob@tools.ietf.org<mailto:pmipv6-flowmob@tools.ietf.org>
     Type:  enhancement              |     Status:  new
 Priority:  major                    |  Milestone:
Component:  pmipv6-flowmob           |    Version:
 Severity:  -                        |   Keywords:
-------------------------------------+-------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/netext/trac/ticket/15>
netext <http://tools.ietf.org/netext/>

_______________________________________________
netext mailing list
netext@ietf.org<mailto:netext@ietf.org>
https://www.ietf.org/mailman/listinfo/netext


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified.
Thank you.