IETF Logo Mail Archive

Re: [Idr] Slot request in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00.txt

Robert Raszuk <robert@raszuk.net> Mon, 11 July 2016 20:48 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 A124D12D0FC for <idr@ietfa.amsl.com>; Mon, 11 Jul 2016 13:48:00 -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 XTvR1M9nVQ9Y for <idr@ietfa.amsl.com>; Mon, 11 Jul 2016 13:47:58 -0700 (PDT)
Received: from mail-lf0-x22f.google.com (mail-lf0-x22f.google.com [IPv6:2a00:1450:4010:c07::22f]) (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 4496912D0FA for <idr@ietf.org>; Mon, 11 Jul 2016 13:47:58 -0700 (PDT)
Received: by mail-lf0-x22f.google.com with SMTP id f93so31069010lfi.2 for <idr@ietf.org>; Mon, 11 Jul 2016 13:47:58 -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=8wMwbJlvz7gIdBOyCTg3zCHS3euCd4bUoXqjvgOJ9e0=; b=Ax/dWT15YoBRHRJXVDQJiSJv+fDUKv1KUsrneDamz6XfD9kwnRiEB4ANqmJV7mTNlQ PfFRpY5pWOZwy+HhzqJRha1SCfUMU9d72QTI/rMj2hFgEakCGkZ+RMRLp86GMFqEj1ez 2VI1vrzrQ0V0mNEuDGU8kaj90wzbs2Z25u85/OEKnNwi7OQf1sNdBhsDL7criSJEDdsc hUmPVQRiL2+02CO/inl8FPt+XOsNhF528XrQVU1oi7biG5k0MW7ACMAToc5ZG8iPr/gV Cdu4qsYx2SNRbCNymBOEECbxjI8VCsdmtoKToMDd8Nc2y6h6oCST5jciq0PGkg8QNaHN D1bA==
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=8wMwbJlvz7gIdBOyCTg3zCHS3euCd4bUoXqjvgOJ9e0=; b=POcRnTVqsPfN4koVHKU1opzhS5gwvGnNJccOVwexZSujWuesf3iPmlLVufHodc7fpi vnmiX7Sr5TAC7YJKkiK/zVugqivf5rLj9MWqsEz/ht0fO6wbtPQjBbFCZ4UJYKRLB9Yd p8b1cT8N0FrtD0R4cAHT2mvbNKTjPO98yRnzgAB7y3l1QWvUUDPuhgqQxQoLl2PPhjJa m2YEURJgxmjV0t+2pRZsZLemfZBqZNhQG4JKf26jlh6ia26S1Wum/TMf1uO/1U4pCr/t KItKb7jpYmnSHk+TTTFzFHtIihGnVwZpP1R1z1kFJTdDGU4L9Fqe8nQUUsvWuHrkFirS 5mNQ==
X-Gm-Message-State: ALyK8tKa3gbRMHLmL2i5XBleTNFz2buUPMg7PFiI0m0v9qLRzXWeJSPTR6aF95U9Sb8ffdoww5Ih9dGcVPD8aA==
X-Received: by 10.25.84.65 with SMTP id i62mr7332620lfb.88.1468270076453; Mon, 11 Jul 2016 13:47:56 -0700 (PDT)
MIME-Version: 1.0
Sender: rraszuk@gmail.com
Received: by 10.25.10.131 with HTTP; Mon, 11 Jul 2016 13:47:55 -0700 (PDT)
In-Reply-To: <CA+wi2hM+y_K+_50Q_QRS64VBdzgBWtx8hL-6iepsVqed+NtqTw@mail.gmail.com>
References: <CA+wi2hM+y_K+_50Q_QRS64VBdzgBWtx8hL-6iepsVqed+NtqTw@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Mon, 11 Jul 2016 22:47:55 +0200
X-Google-Sender-Auth: 0yk6dvRVkGQCJPT8h7u0UG32OEU
Message-ID: <CA+b+ERm2AnRAYeJRDdsAh=hLX81aQUTVd7Pe5PYLpWmHNvbgtQ@mail.gmail.com>
To: Tony Przygienda <tonysietf@gmail.com>
Content-Type: multipart/alternative; boundary="001a11411f2857697a053762449d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/lZ8TUnQkbVO3fqDuhCDteZkYmVE>
Cc: idr wg <idr@ietf.org>
Subject: Re: [Idr] Slot request in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00.txt
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: Mon, 11 Jul 2016 20:48:01 -0000

Hi Tony,

Can you clarify what is the expected behaviour as far as per peer
filter-list when you negotiate both Refresh with options, ORF and RTC ?
Note that ORF also includes recent extension as described in RFC7543 -
would all of those be always a logical AND towards a peer which pushed
those ?

Would you always carry ORF with separate Refresh_ID value ?

If one requests full Adj_RIB_Out in the new model and sends refresh message
with new refresh_id and no options however there are ORF entries already
installed in the past would he get just the subset of routes against all
ORF entries ? In other words I think the draft should state that
Refresh_IDs have no impact to ORF ADDs or REMOVE actions - don't you think
?

As far as current types why not add regular/extended community ?

Thx,
Robert.











On Sun, Jul 10, 2016 at 7:18 AM, Tony Przygienda <tonysietf@gmail.com>
wrote:

> John, Sue, may I request a slot on IDR agenda in Berlin (10 mins should be
> enough) to present
> https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00.txt
>  ?
>
> thanks
>
> -- tony
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>
>

v2.23.0 | Report a Bug | By Email