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

Andrew Lange <andrew.lange@nokia.com> Thu, 15 September 2016 00:15 UTC

Return-Path: <andrew.lange@nokia.com>
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 1E89412B0F8 for <idr@ietfa.amsl.com>; Wed, 14 Sep 2016 17:15:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-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 Ity34eu3eYHd for <idr@ietfa.amsl.com>; Wed, 14 Sep 2016 17:15:10 -0700 (PDT)
Received: from smtp-us.alcatel-lucent.com (us-hpatc-esg-01.alcatel-lucent.com [135.245.18.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D44F12B0F5 for <idr@ietf.org>; Wed, 14 Sep 2016 17:15:10 -0700 (PDT)
Received: from us70tumx1.dmz.alcatel-lucent.com (unknown [135.245.18.13]) by Websense Email Security Gateway with ESMTPS id 07455677313B8; Thu, 15 Sep 2016 00:15:05 +0000 (GMT)
Received: from us70tusmtp1.zam.alcatel-lucent.com (us70tusmtp1.zam.alcatel-lucent.com [135.5.2.63]) by us70tumx1.dmz.alcatel-lucent.com (GMO) with ESMTP id u8F0F8rV010694 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 15 Sep 2016 00:15:08 GMT
Received: from US70TWXCHHUB04.zam.alcatel-lucent.com (us70twxchhub04.zam.alcatel-lucent.com [135.5.2.36]) by us70tusmtp1.zam.alcatel-lucent.com (GMO) with ESMTP id u8F0F7rx021508 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 15 Sep 2016 00:15:07 GMT
Received: from alange.lra.lucent.com (135.5.27.17) by US70TWXCHHUB04.zam.alcatel-lucent.com (135.5.2.36) with Microsoft SMTP Server (TLS) id 14.3.301.0; Wed, 14 Sep 2016 20:15:06 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail=_88A59D5B-A5B8-41A9-B260-5D14C210554F"
MIME-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Andrew Lange <andrew.lange@nokia.com>
In-Reply-To: <CAHw9_iKs=FrmcCpsG=wGhH04J0kO093dBASrFqBVaUq1GKTheQ@mail.gmail.com>
Date: Wed, 14 Sep 2016 17:14:52 -0700
Message-ID: <34509C11-6FE3-44C7-85EE-96BE5ED0A809@alcatel-lucent.com>
References: <20160908214031.GA23544@pfrc.org> <20160908231840.GB16775@puck.nether.net> <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> <CAHw9_iKs=FrmcCpsG=wGhH04J0kO093dBASrFqBVaUq1GKTheQ@mail.gmail.com>
To: Warren Kumari <warren@kumari.net>
X-Mailer: Apple Mail (2.3124)
X-Originating-IP: [135.5.27.17]
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/S6jckAaVWH1ELuyrWdGuYwtIVvg>
Cc: "idr@ietf. org" <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: Thu, 15 Sep 2016 00:15:13 -0000

This assumes that we don’t have perfect (or at least better) already. There are existing idr drafts that do everything large does.  In fact, by using the common header it can behave exactly like large with an opaque payload you can interpret as 4+4 or any other way local policy allows.  The common header is already defined, has been vetted by becoming an IDR draft and being examined over the years.  Existing drafts are farther ahead in the standards process.

If it’s implementations you want, then ask your vendors!

Having been on both sides, there is no magic to the standard PLM process at vendors.  Customers ask for features, the account teams and regions bring this back to PLM where it’s aggregated.  At some interval PLM gets together and decides what the priorities are for the next release (and the release thereafter for big features).  Number of customers, amount of revenue and feature size are the main considerations.  A common header and opaque body for communities is a small feature.  

Andrew 


> On Sep 14, 2016, at 6:28 AM, Warren Kumari <warren@kumari.net> wrote:
> 
> On Wed, Sep 14, 2016 at 6:54 AM, Mikael Abrahamsson <swmike@swm.pp.se <mailto:swmike@swm.pp.se>> wrote:
>> On Fri, 9 Sep 2016, Gert Doering wrote:
>> 
>>> We're not talking about "too early" here.  We're talking about "5 years
>>> too late" vs. "at some future point of perfection, when nobody alive today
>>> cares anymore".
>> 
>> 
>> I have to agree with Gert here. The time to engineer a great, nice
>> future-proof mechanism was 10 years ago, so it would have running code
>> widely deployed 5 years ago.
>> 
>> Since we don't have that, then now is the time to standardize a "does the
>> same as we have today for 16bitAS but for 32bitAS" which involves as small
>> code, operational and standardization changes as possible, so code can get
>> into operator routers ASAP.
>> 
>> So get it out the door now. Not in 6-12 months time. Now. ASAP.
> 
> +1.
> 
> Seeing as pithy French quotes appear to be the hotness this week:
> "Le mieux est l'ennemi du bien." (The perfect is the enemy of the good.)
> - Voltaire
> 
> W
> 
>> 
>> --
>> Mikael Abrahamsson    email: swmike@swm.pp.se <mailto:swmike@swm.pp.se>
>> 
>> 
>> _______________________________________________
>> Idr mailing list
>> Idr@ietf.org <mailto:Idr@ietf.org>
>> https://www.ietf.org/mailman/listinfo/idr <https://www.ietf.org/mailman/listinfo/idr>
> 
> 
> 
> -- 
> I don't think the execution is relevant when it was obviously a bad
> idea in the first place.
> This is like putting rabid weasels in your pants, and later expressing
> regret at having chosen those particular rabid weasels and that pair
> of pants.
>   ---maf
> 
> _______________________________________________
> Idr mailing list
> Idr@ietf.org <mailto:Idr@ietf.org>
> https://www.ietf.org/mailman/listinfo/idr <https://www.ietf.org/mailman/listinfo/idr>