IETF Logo Mail Archive

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

Robert Raszuk <robert@raszuk.net> Wed, 14 September 2016 13:43 UTC

Return-Path: <rraszuk@gmail.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 C17DA12BA1E for <idr@ietfa.amsl.com>; Wed, 14 Sep 2016 06:43:02 -0700 (PDT)
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=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 JtPbN6GKHDin for <idr@ietfa.amsl.com>; Wed, 14 Sep 2016 06:42:58 -0700 (PDT)
Received: from mail-it0-x22e.google.com (mail-it0-x22e.google.com [IPv6:2607:f8b0:4001:c0b::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 262B112BA2B for <idr@ietf.org>; Wed, 14 Sep 2016 06:07:19 -0700 (PDT)
Received: by mail-it0-x22e.google.com with SMTP id 186so22553735itf.0 for <idr@ietf.org>; Wed, 14 Sep 2016 06:07:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=Fcz9k1uJ3rOi/cKvJ45JwzPJtULQudyG+Vx8opXkCNc=; b=p3x7UXUQIeH7pGQuCOGy1CTtTCc/y9zRv3xxhzA0qzTKyArehDFxWfRAqBtKmiwzwb WFSWoMNbNMNjJt68bj5lSAuszdz4dcsYqDiH3lTz81NGOXB2krXH16k42G14O1eNtKHn 0w947EWn9ul2N7dx29Fxvt/+AVdrsETnd4RC3tavfIQ+XiUJU8ixNR8NHjnflXz0dmiC BqRt5wMYQztQ/cwwsGV/0rxCRN3yl+4djoJU/+4UGvEOGfo7WFQJt8MR1hbkxM7q+UpP /r9txgR0/1gJKDZZXakHK6w08eiBVt05Yn3ocsURNP5+EWWcJGNakw1MhiJM7GTJgIrT p7tw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=Fcz9k1uJ3rOi/cKvJ45JwzPJtULQudyG+Vx8opXkCNc=; b=mUj/7MKuKNL0PGrIWNiK8SUM4U2R6bkpgfp7stKvQ6ygb1T7eurSOyx7LG7Ks6ToJt zRPSPk2CTWPit3TimIbm8SolSn+GtAwBQWXGUY8/VS2ckwqdfVReguW7BFb83bUSgqPa 24WUM7VN+/BCtGAVhi3QoeUhIFywqyOU6g5UEcl4oxCWEOscZzqS7tTNoKJHpKQUy/wY dVjpNpBiT+v/QtoQJrPhEobG3Ptt5b2FdwaGEg0H8GvopiVszLIoDMQ2b2KYtdkk5sgi KxaIJCrGOt8exwbe/Vh9AU0gO8S2DtoK7n4tSLKlJSOL9J8hYG+S2ZfB0Feg9RL2+pWJ vXUg==
X-Gm-Message-State: AE9vXwNc8aPCp1Clw4A63bLBoLptvFqL5AeyhQZkQz1LH+391o2foL1Mm6DsvmBzAElhc2kyu3KLp1vaQrXVtg==
X-Received: by 10.107.159.138 with SMTP id i132mr5898026ioe.177.1473858438309; Wed, 14 Sep 2016 06:07:18 -0700 (PDT)
MIME-Version: 1.0
Sender: rraszuk@gmail.com
Received: by 10.107.37.68 with HTTP; Wed, 14 Sep 2016 06:07:16 -0700 (PDT)
In-Reply-To: <alpine.DEB.2.02.1609141250080.1477@uplift.swm.pp.se>
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>
From: Robert Raszuk <robert@raszuk.net>
Date: Wed, 14 Sep 2016 15:07:16 +0200
X-Google-Sender-Auth: VsWpA5dvYK_d-aoDetesXsF0F6k
Message-ID: <CA+b+ERmYVgnDeJv-H5vxnkvikJBk_7LKfgqsgNTMeAabQ5OTeQ@mail.gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Content-Type: multipart/alternative; boundary="001a11408224aa3c47053c776808"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/KNB37TFTsj0Jy2I3YnUfXpWrtIU>
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 13:43:03 -0000

Mikael,

> So get it out the door now. Not in 6-12 months time. Now. ASAP.

Get what out of the door ? Are you asking IDR to give you code to run in
your network ?

Operators where not sufficiently asking vendors for last few years to
implement solution accepted long time as IETF IDR WG document .. so vendors
never prioritized to implement it.

No one from mobilized *NOG community also provided any feedback to IDR WG
that solution which we have as working group document is too complex or is
missing something ... contrary when we first defined wide community spec I
had a lot of operators contributing to it and providing their requirements
to what communities should be useful.

All of that is publicly available as again IDR WG document.

IDR has no power to tell any vendor to implement anything. It can only try
to issue BGP extensions which are to be in the best interest of the
protocol. And vendors as past experience shows can and do ship pre-standard
features to gain operational experience and win time to market.  Why the
latter in the recent years has been slower then before ... well you need to
ask vendors for that or move to opensource and start implementations
yourself.

Cheers,
R.


On Wed, Sep 14, 2016 at 12:54 PM, Mikael Abrahamsson <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.
>
> --
> Mikael Abrahamsson    email: swmike@swm.pp.se
>
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>

v2.23.0 | Report a Bug | By Email