Re: [Idr] community of the day - common header

Jared Mauch <jared@puck.Nether.net> Wed, 14 September 2016 16:15 UTC

Return-Path: <jared@puck.nether.net>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD31C12B149 for <idr@ietfa.amsl.com>; Wed, 14 Sep 2016 09:15:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.71
X-Spam-Level:
X-Spam-Status: No, score=-5.71 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.508, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 MbFV7zdnLl43 for <idr@ietfa.amsl.com>; Wed, 14 Sep 2016 09:15:52 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) by ietfa.amsl.com (Postfix) with ESMTP id A234E12B369 for <idr@ietf.org>; Wed, 14 Sep 2016 09:06:00 -0700 (PDT)
Received: by puck.nether.net (Postfix, from userid 162) id DB017540B4E; Wed, 14 Sep 2016 12:05:59 -0400 (EDT)
Date: Wed, 14 Sep 2016 12:05:59 -0400
From: Jared Mauch <jared@puck.Nether.net>
To: Robert Raszuk <robert@raszuk.net>
Message-ID: <20160914160559.GA17489@puck.nether.net>
References: <20160909153317.GC8370@pfrc.org> <8C072797-55A7-4D1A-87E4-67551953EF22@puck.nether.net> <20160909155952.GE8370@pfrc.org> <20160909164640.GE79185@Space.Net> <20160909170513.GE12105@pfrc.org> <20160909171110.GF79185@Space.Net> <alpine.DEB.2.02.1609141250080.1477@uplift.swm.pp.se> <CA+b+ERmYVgnDeJv-H5vxnkvikJBk_7LKfgqsgNTMeAabQ5OTeQ@mail.gmail.com> <alpine.DEB.2.02.1609141604570.1477@uplift.swm.pp.se> <CA+b+ERm4NbGi0rC1pyNfvjaormZ9N7z1vJ8BSM=O5MbsA7OL1w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CA+b+ERm4NbGi0rC1pyNfvjaormZ9N7z1vJ8BSM=O5MbsA7OL1w@mail.gmail.com>
User-Agent: Mutt/1.7.0 (2016-08-17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/qcKiMnrM0JaY1iM-r72r1g54bho>
Cc: idr wg <idr@ietf.org>
Subject: Re: [Idr] community of the day - common header
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Sep 2016 16:15:55 -0000

On Wed, Sep 14, 2016 at 04:22:12PM +0200, Robert Raszuk wrote:
> Hi Mikael,
> 
> Being nearly 17 year a vendor I can tell you that nothing works better for
> the account team then fear of loosing a customer or at min part of their
> business.
> 
> Introducing a second vendor always raises the alarm even if customers do
> not always see it :)
> 
> Worst case is vendor lock .. in such a case indeed you can't do much.
> 
> - - -
> 
> Bottom line - no one here is trying to delay or deny urgent need for large
> comms. We are just trying (and trust me there is daily a lot of
> conversations about it) to pack it in the proper envelope.
> 
> Considering the speed of standardization process itself and various phases
> current discussion is really in the best interest to make it as fast as
> possible an RFC.
> 
> Imagine that now working group just blindly passes it though then
> directorate review or IESG review will reject it - as not discussed in the
> WG. So it will go back to where we are today and it will not be in any
> interest of the community.

	In my opinion there is some emergening consensus on a few topics.
I'm hoping we can optimize on a minimum set of document(s) that have broad
support.

> As John already said the other day seeing few emails from those who were
> not even subscribed to IDR - IETF WG rough consensus is really not about
> counting "+1s" from folks who never actively participate in the IDR WG work
> or mailing list discussions.

	I think there is danger here we should clearly avoid.  Counting +1's
is valuable for some definition of value, but we must drive for consensus
in the WG.  This means not everyone may be happy, be it Me, Jeff, Job, Jakob,
Keyur, Robert, Bruno, Mikael, Gert or anyone else.

	having watched this pot be stirred, i'm seeing enough people
motivated to do something, which I think will drive the necessary review
of any documentes adopted in the WG.

	- Jared


> 
> Cheers,
> R.
> 
> 
> 
> On Wed, Sep 14, 2016 at 4:09 PM, Mikael Abrahamsson <swmike@swm.pp.se>
> wrote:
> 
> > On Wed, 14 Sep 2016, Robert Raszuk wrote:
> >
> > Get what out of the door ? Are you asking IDR to give you code to run in
> >> your network ?
> >>
> >
> > I'm asking IDR to get the document out the door. We can hit the vendors
> > over the head for implementations after that just fine, thank you.
> >
> > And having worked at operators since 1999, I can tell you that getting
> > through the account teams is designed to be hard. The answer is always
> > "you're the only one asking for this". I've been told this so many times
> > (which usually was a lie) it's very upsetting to read your text about
> > operators not trying hard enough. What should we have done? All camped
> > outside John Chambers office with banners demanding this, or what?
> >
> >
> > --
> > Mikael Abrahamsson    email: swmike@swm.pp.se
> >

> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr


-- 
Jared Mauch  | pgp key available via finger from jared@puck.nether.net
clue++;      | http://puck.nether.net/~jared/  My statements are only mine.