Re: [netext] Flow Mobility Draft

Rajeev Koodli <rajeev.koodli@gmail.com> Thu, 24 July 2014 14:26 UTC

Return-Path: <rajeev.koodli@gmail.com>
X-Original-To: netext@ietfa.amsl.com
Delivered-To: netext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B00A1A0375 for <netext@ietfa.amsl.com>; Thu, 24 Jul 2014 07:26:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BNDCQzja7nF3 for <netext@ietfa.amsl.com>; Thu, 24 Jul 2014 07:26:36 -0700 (PDT)
Received: from mail-wg0-x234.google.com (mail-wg0-x234.google.com [IPv6:2a00:1450:400c:c00::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B72E1A004E for <netext@ietf.org>; Thu, 24 Jul 2014 07:26:35 -0700 (PDT)
Received: by mail-wg0-f52.google.com with SMTP id a1so2790374wgh.11 for <netext@ietf.org>; Thu, 24 Jul 2014 07:26:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=iJwOgIOkDGaqUOq0I8t82URez2MLF/aK4QL99qmQ79k=; b=nimy/TCU6BVBY5WTS+ZKbstn0OSKnwCZ0/W8A24HFQ11tLRvxLLbSmKXqZZnNulB1X TzAcKBzxaqWFB9VIi9bFnzpx3gweLCIebGANxy8fSzJGtWw7Yc6LgdCfis8jMqjxIaDR kerMcizN/Z/lnxaJ5ynlRMBIryp1k9fHeNy5YSoQDNXWPTrQXDyOGEhIzhcgQg/pW+Cn DSM9b3qqh+zGAeXbp2Y/fJ6sZL2U9xDvSCstNqy+f9fv9PEPzW+pvIDcpo1KEj5x+PBF ODLp6+xUEvMMXG4OK69NboSGP9L6l1yKETwBUTaPx9626Zq9sMphTnoqTVCtQDWr+5LI Sh0A==
MIME-Version: 1.0
X-Received: by 10.180.84.7 with SMTP id u7mr50561603wiy.1.1406211993871; Thu, 24 Jul 2014 07:26:33 -0700 (PDT)
Received: by 10.195.11.132 with HTTP; Thu, 24 Jul 2014 07:26:33 -0700 (PDT)
In-Reply-To: <CAC8QAceOL--ognqZ7hy2rOBDkArFqiHm8s0DOkJtmtEbvUDvMg@mail.gmail.com>
References: <CFF53D90.14FE0B%sgundave@cisco.com> <53CFF515.9040706@innovationslab.net> <CAC8QAcesq5v69n+ajnmU9hJ1bhWX_muBOkYg2Y_MjfQnU7AqPQ@mail.gmail.com> <53D10901.4000103@innovationslab.net> <CAC8QAceOL--ognqZ7hy2rOBDkArFqiHm8s0DOkJtmtEbvUDvMg@mail.gmail.com>
Date: Thu, 24 Jul 2014 07:26:33 -0700
Message-ID: <CAB_pk7CkGSzgtn=Q32LUQv1y9otPJ84HB4C=BS8dBTwOXNddeg@mail.gmail.com>
From: Rajeev Koodli <rajeev.koodli@gmail.com>
To: sarikaya@ieee.org
Content-Type: multipart/alternative; boundary=f46d0418255c5fac7d04fef13ea3
Archived-At: http://mailarchive.ietf.org/arch/msg/netext/UiawWE8uW-tfslnVM5c3uxZDDEw
Cc: "netext@ietf.org" <netext@ietf.org>
Subject: Re: [netext] Flow Mobility Draft
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.15
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, 24 Jul 2014 14:26:38 -0000

Hi Behcet,

let us not use this ML/WG for personal issues.

Just to be clear: Carlos is the Editor of this ID, and he has chairs
support.

At this point, my sense is that the WG is ready to move ahead with the ID.
Will talk during the meeting.

Regards,

-Rajeev




On Thu, Jul 24, 2014 at 7:10 AM, Behcet Sarikaya <sarikaya2012@gmail.com>
wrote:

> Another issue with the editor has been his attuitude. He has always
> been stubborn he never said things like why don't you provide some
> text? or let's edit the document together.
>
> This document has not originated from his own document, it has come
> out of a design team so the editor's rigid approach was not warranted.
>
> Regards,
>
> Behcet
>
> On Thu, Jul 24, 2014 at 8:24 AM, Brian Haberman
> <brian@innovationslab.net> wrote:
> >
> >
> > On 7/24/14 9:20 AM, Behcet Sarikaya wrote:
> >
> >>> The WG has an issue tracker set up for this document.  It appears that
> >>> the document editor and chairs are using it to track issues raised.
>  Why
> >>> should these concerns be handled any differently.
> >>
> >> Please refer to the Issue Tracker page:
> >> http://trac.tools.ietf.org/wg/netext/trac/report/1
> >>
> >> I did have several issues there.
> >> The editor replied some of them but I was not happy with them.
> >
> > Has anyone expressed support for those concerns?
> >
> >>
> >>>
> >>> Perusal of the mailing list archives and the minutes of previous netext
> >>> meetings reveals no support within the WG for these perceived defects.
> >>> That could be a result of a disagreement with the concerns raised or
> >>> could a result of people not understanding the concerns.
> >>>
> >>
> >> There at least two common concerns that I believe several people share:
> >
> > You believe or know?  Why have they not expressed those concerns on the
> > mailing list?  If they have, can you provide a pointer?
> >
> >>
> >> where is the flow mobility protocol in the draft?
> >>
> >> Why is LMA prefix allocation policy a use case for flow mobility
> protocol?
> >>
> >>
> >> If the Editor does not understand these issues then he needs to read
> >> the revision I mentioned.
> >
> > No.  As I said, that is not an appropriate way to express concerns.  You
> > have several concise questions listed above.  Why not expound on those
> > with the WG?
> >
> > Regards,
> > Brian
> >
>
> _______________________________________________
> netext mailing list
> netext@ietf.org
> https://www.ietf.org/mailman/listinfo/netext
>