Re: [netext] #15: use "update notification" for FMI/FMA
Behcet Sarikaya <sarikaya2012@gmail.com> Thu, 29 November 2012 20:17 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 C4A2B21F8BB8 for <netext@ietfa.amsl.com>; Thu, 29 Nov 2012 12:17:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.579
X-Spam-Level:
X-Spam-Status: No, score=-3.579 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 Sji0LDo1pieM for <netext@ietfa.amsl.com>; Thu, 29 Nov 2012 12:17:21 -0800 (PST)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id C7E1821F8B60 for <netext@ietf.org>; Thu, 29 Nov 2012 12:17:20 -0800 (PST)
Received: by mail-ie0-f172.google.com with SMTP id c13so16553972ieb.31 for <netext@ietf.org>; Thu, 29 Nov 2012 12:17:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=k9D0Yy5uH1wICMG4WGYJuAg2AIJtvCnS3HiNrxlfIPY=; b=CZfDJ3y4QxzCkC6YvFfeHA8aTJQUNTHKd/SQnxE/Ae9oFBGg7FRZSPCPcxYffMEjn3 izaQT8HZtnVdiW/iJmusUlvmiGWr6+JgKLfAQfbJv8E8KeXyNJfVlh3j0dXY99F/kEWO jGvMeSbNx6DgpYQKNejQMKrTSYOhSji78GyBPvdpF4w+DHBbzYu4+C5kNba8P0TG5Bsq sYUwB4QpRQZZ12DM/4SPxSqm/h1Bqb1qyfs6JjL48oJ39GGJmSp7AxuRooMlYg70Wu4E 7SvK0yR69o9Vr9BcPLyWhCpG6A79okRVo5sMAAW06jjOwISUiNjtoAjtOGwbpxzQ5HWW pkpg==
MIME-Version: 1.0
Received: by 10.42.63.4 with SMTP id a4mr21020774ici.40.1354220240294; Thu, 29 Nov 2012 12:17:20 -0800 (PST)
Received: by 10.231.10.204 with HTTP; Thu, 29 Nov 2012 12:17:20 -0800 (PST)
In-Reply-To: <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> <6471_1354210959_50B79E8F_6471_1459_1_81C77F07008CA24F9783A98CFD706F71073A73@PEXCVZYM12.corporate.adroot.infra.ftgroup>
Date: Thu, 29 Nov 2012 14:17:20 -0600
Message-ID: <CAC8QAcdxAZ-L=ZchUjpgu6hwmTr3soVmGp=fN7Of2ibS55eDpg@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: pierrick.seite@orange.com
Content-Type: multipart/alternative; boundary="90e6ba614c305ed4ff04cfa7f8f7"
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
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: Thu, 29 Nov 2012 20:17:21 -0000
Hi Pierrick, On Thu, Nov 29, 2012 at 11:42 AM, <pierrick.seite@orange.com> wrote: > Hi,**** > > ** ** > > Issue #15 is valid if draft-krishnan is adopted.**** > > ** > What are we going to do with LRI/LRA defined in RFC 6705 by Suresh himself? I think you are worried that no one will use the new messages in draft-krishnan. That is a separate issue, we should accept the fact that already there are several messages defined to be initiated by LMA and move on. Regards, Behcet > ** > > 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> 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 | 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 > 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. > >
- [netext] #15: use "update notification" for FMI/F… netext issue tracker
- Re: [netext] #15: use "update notification" for F… Behcet Sarikaya
- Re: [netext] #15: use "update notification" for F… pierrick.seite
- Re: [netext] #15: use "update notification" for F… Behcet Sarikaya
- Re: [netext] #15: use "update notification" for F… Suresh Krishnan
- Re: [netext] #15: use "update notification" for F… Suresh Krishnan
- Re: [netext] #15: use "update notification" for F… netext issue tracker
- Re: [netext] #15: use "update notification" for F… Behcet Sarikaya
- Re: [netext] #15: use "update notification" for F… Carlos Jesús Bernardos Cano
- Re: [netext] #15: use "update notification" for F… Behcet Sarikaya
- Re: [netext] #15: use "update notification" for F… Sri Gundavelli (sgundave)
- Re: [netext] #15: use "update notification" for F… Rajeev Koodli (rkoodli)