[Idr] draft-litkowski-idr-rtc-interas
Robert Raszuk <robert@raszuk.net> Tue, 22 July 2014 15:14 UTC
Return-Path: <rraszuk@gmail.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 911C21B28E0 for <idr@ietfa.amsl.com>; Tue, 22 Jul 2014 08:14:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level:
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 GwgtszpnI1IG for <idr@ietfa.amsl.com>; Tue, 22 Jul 2014 08:14:34 -0700 (PDT)
Received: from mail-ie0-x235.google.com (mail-ie0-x235.google.com [IPv6:2607:f8b0:4001:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F5791B2960 for <idr@ietf.org>; Tue, 22 Jul 2014 08:14:33 -0700 (PDT)
Received: by mail-ie0-f181.google.com with SMTP id rp18so8198155iec.12 for <idr@ietf.org>; Tue, 22 Jul 2014 08:14:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:cc:content-type; bh=Mf9d57PfkrpvgcSyjnfARoj+xHqEv8XTqTU6hWYKatU=; b=cJl2ux50uCsRDrUHo7QGSEUnImeyB2WlfVRZVQuA+OZMBdHoyAtGJK83NevEO2xHax R6YIcPRGHZgB+zxOsEZwdLNZ42E5uXoy61abdFwg+fJIHaK13tjZrLenATcPUnv0ISBJ n4nTYRpGWINQHj6X15vYyVq+pCoIeQFkFvo/mVT3GlfAAfLwNrDPVUmzj7mavi2EytFR 7ptbH6JTmDcWX5DpGWFXBsBswis8AeZk3aEU86sh+hTw69wTunx6NCvu55u1i+Z7nszs WCXkP0OISurZczlzKYV3SnDJo/BRATBegMMNP5mo0PKx4VKUHV9WAWbqR3O7YIuyP1F7 tirQ==
MIME-Version: 1.0
X-Received: by 10.50.79.135 with SMTP id j7mr17848909igx.9.1406042072947; Tue, 22 Jul 2014 08:14:32 -0700 (PDT)
Sender: rraszuk@gmail.com
Received: by 10.64.128.99 with HTTP; Tue, 22 Jul 2014 08:14:32 -0700 (PDT)
Date: Tue, 22 Jul 2014 17:14:32 +0200
X-Google-Sender-Auth: 9ZSol9no71QPgJh6kxCwgoUeJfE
Message-ID: <CA+b+ERnCubHOvTErSnrqwLTN-TJzqTC8ih+R=A1C8Kv_-Pat8A@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
To: "<stephane.litkowski@orange.com>" <stephane.litkowski@orange.com>, Jeffrey Haas <jhaas@juniper.net>
Content-Type: multipart/alternative; boundary="089e0122a7544c238804fec9ae37"
Archived-At: http://mailarchive.ietf.org/arch/msg/idr/TUAjkUVQQafUV3AtVLEhUuchLD8
Cc: idr wg <idr@ietf.org>
Subject: [Idr] draft-litkowski-idr-rtc-interas
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 22 Jul 2014 15:14:35 -0000
Stephane, I have one fundamental question on this ... You have focused on making sure that BGP control plane works fast and solid etc. That is great and timestamp idea at each BGP hop would help. However let's observe that BGP control plane is NOT congruent with data plane. In other words you may have a case where someone may have slow and overloaded RR but uses 40 GB pipes for data plane while other AS installed super-hyper x86 RRs and has 1 GB links for data plane. Your results may actually in the above case casue more problems then gains unfortunately. The possible simple fix is to mandate that timestamp is ONLY added when your change next hop to self or that you can have a new flag "N" - Next Hop Set which will help a lot to make more use cases for this proposal. Best, R.
- [Idr] draft-litkowski-idr-rtc-interas Robert Raszuk