From nobody Mon Jul 4 05:18:20 2016 Return-Path: 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 448F512D0CA; Mon, 4 Jul 2016 05:18:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 4.439 X-Spam-Level: **** X-Spam-Status: No, score=4.439 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, RDNS_NONE=0.793] autolearn=no 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 kVcVbwg1lfv8; Mon, 4 Jul 2016 05:18:17 -0700 (PDT) Received: from hickoryhill-consulting.com (unknown [50.245.122.97]) (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 8D12012B018; Mon, 4 Jul 2016 05:18:17 -0700 (PDT) X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=174.124.202.159; From: "Susan Hares" To: Date: Mon, 4 Jul 2016 08:17:34 -0400 Message-ID: <152e01d1d5ee$0c4c1320$24e43960$@ndzh.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_152F_01D1D5CC.853B0F60" X-Mailer: Microsoft Outlook 14.0 Thread-Index: AdHV7eYFSQENVz2zSUi66Ycsd1UdXA== Content-Language: en-us X-Authenticated-User: skh@ndzh.com Archived-At: Cc: 'idr chairs' , "'John G. Scudder'" Subject: [Idr] Presentation slot X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jul 2016 12:18:19 -0000 This is a multipart message in MIME format. ------=_NextPart_000_152F_01D1D5CC.853B0F60 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit IETF 96 is drawing near. For those who would like to present at IETF 96, please reply to this message (making sure to keep both chairs), and request a slot. Sue and John ------=_NextPart_000_152F_01D1D5CC.853B0F60 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

 

IETF 96 is = drawing near.  For those who would like to present at IETF 96, = please reply to this message (making sure to keep both chairs), and = request a slot. 

 

Sue and John =

------=_NextPart_000_152F_01D1D5CC.853B0F60-- From nobody Tue Jul 5 12:25:30 2016 Return-Path: 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 C1E4F12D0E8 for ; Tue, 5 Jul 2016 12:25:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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 v3Mlc5KT87Md for ; Tue, 5 Jul 2016 12:25:28 -0700 (PDT) Received: from mail-qk0-x232.google.com (mail-qk0-x232.google.com [IPv6:2607:f8b0:400d:c09::232]) (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 6F52612D507 for ; Tue, 5 Jul 2016 12:25:26 -0700 (PDT) Received: by mail-qk0-x232.google.com with SMTP id s126so13222878qkh.2 for ; Tue, 05 Jul 2016 12:25:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=O0EPSug6KtI9Uj2vs0xUkm4HWXrrJfWu3ZviD+8IF7k=; b=fjU0+w7LIV5PhERKEekW82AAri2IjW5ogq48lzkbelR4y9KDsGENGRpGMrugl9x8fU GEV6FMGBhy/bgFL8kJHQJiHvtRpxyi5hX4664CRgVyioaC4U5uPuyx0rnIgQPYeiRVk3 CYXg7i289jRmcaksTCshzQwUPxIov038kQN9h0DaMZfp9rnLuC9wWhDppuxEs/FDXKTl 4dhELQn8mkL3EVzDhycUYH9xpmcdI/yu0uEkoEpYbSwESVVy3Sy1pVh0JleY9b5t/aBT Xh92u1RaYbx+3s7pw699C+DJJR3uQasizz252OLrdpbJp7vcKrDoSfnUXUJp1nDUiuK7 BELg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=O0EPSug6KtI9Uj2vs0xUkm4HWXrrJfWu3ZviD+8IF7k=; b=ARDRKMSzHR7GS6pNye7bvqsVJpwTtwCIyboh0TzwGrf3kaXZ3YZ09/xEYfnY1Z4Cgb hfuifspve+vOZY6EHnh/bZNiUnGqxqscxF2I/pV8KTPZdj+cAdbpados9RbeRXb4vrwQ T138xvRCAzcvErFriRPqc7aaK4if0iktbgHsFeA+p696FazW/7gewt7LKnVfyq7847XI Rg0VMeBBxqO2As8kxykmFLMSc0L7tpi7EbEwvVEguu4KQqVPD2sJvW1WD9gpb69VfI1W /WEcvi/HILeN2AWdl2MDd6ynu9LkJjQ3E3AS2YjYs7GBowLaSQ9fcE70PyK3/O20MiAx /3FQ== X-Gm-Message-State: ALyK8tJ1GgdWUhMYdEn9g9C0RPiv5kgP+rfSCtlLnWX5cZx1yRGgL0jVtEV/l3qAVKva+vaRn+FADYzxD2LPrA== X-Received: by 10.55.73.148 with SMTP id w142mr25653980qka.77.1467746726044; Tue, 05 Jul 2016 12:25:26 -0700 (PDT) MIME-Version: 1.0 Received: by 10.55.43.232 with HTTP; Tue, 5 Jul 2016 12:25:25 -0700 (PDT) From: amit bhagat Date: Tue, 5 Jul 2016 12:25:25 -0700 Message-ID: To: idr@ietf.org Content-Type: multipart/alternative; boundary=001a114a880839e9920536e86ae4 Archived-At: Subject: [Idr] Review Request for draft BGP Overload X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jul 2016 19:25:30 -0000 --001a114a880839e9920536e86ae4 Content-Type: text/plain; charset=UTF-8 Hey All, We are looking for your comments on the new draft https://datatracker.ietf.org/doc/draft-bhagat-bgp-overload/ We would really appreciate any comments and questions about the document. Best Regards, Amit Bhagat --001a114a880839e9920536e86ae4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hey Al= l,

We ar= e looking for your comments on the new draft https://datatracker.ietf.org/doc/= draft-bhagat-bgp-overload/

We would really appreciate any comments and questions=
 about the document.
=20
Best Regards,
Amit Bhagat

--001a114a880839e9920536e86ae4-- From nobody Tue Jul 5 12:46:13 2016 Return-Path: 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 A3C2012D107 for ; Tue, 5 Jul 2016 12:46:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.4 X-Spam-Level: X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.198, 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=unavailable 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 scuqMbS9Ie7i for ; Tue, 5 Jul 2016 12:46:09 -0700 (PDT) Received: from mail-lf0-x234.google.com (mail-lf0-x234.google.com [IPv6:2a00:1450:4010:c07::234]) (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 57D6812D1AF for ; Tue, 5 Jul 2016 12:39:12 -0700 (PDT) Received: by mail-lf0-x234.google.com with SMTP id h129so141549809lfh.1 for ; Tue, 05 Jul 2016 12:39:12 -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=0Y2Gh5liNsnJaT3APEC8rudnnim3kDSFAj++V5+N6Rs=; b=V+pcuEXVBx2gpK14gAaeFLOoIQqGqffiR+LubaAFinwhU1i82MEUVgjT4IgDxLAAb4 jhZY9vPvmZaVvZL+/bgSsEutjooF9xuPK5biTVC0MezIzMKzKgmvMAfI2xgPgT9ES5JU s8Qjgx7jQA07N6i+KsnCNwHQjm68CpDhrYesn9Kw8yVAEsDSDXTjjA1zcA+na0DeUYGh hEaeLOej2hO0IhMVJp1VOEXhmgkPuG3wJgbCVbv5vWK70AEy2KZ3Tijomd1qCArctpNM l96csU9jc9JTJzyTi6Xfk88DdmZM8+RPSLLE6rYn6D6+JoYl3WWLSsbVSdziqc8Fdhkk XrUA== 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=0Y2Gh5liNsnJaT3APEC8rudnnim3kDSFAj++V5+N6Rs=; b=NAS5jMerxFALecPWx2QOxjNoQkoqroeIqewX5uZUV/4elHbZ7mlLEjFg9/6ZHJYkpN h/f0RhAoHDnkgJq3Bm9FRqoGeXsdS/kKSQB5qT5Mk+4L4T9sMunDdt8Mq5hZVu63wiXB sqp1wXlNeG1GfG6DybDVxc8paxJPKP/MfTSplogOB+04xeez97S5rIO+egtGIsaWMeLc qqoREqSr4TiRzRrBFGGPRxZ1MZxFqkJ87XP2TTlRxEPK+AvmtnPtlJ8WLbNAqnEB1HZZ dEUbTgPQIuL1x2PJ1P4D9xKlr56iCb883/eMRlIc81h2+P+YlHNhJnZ89UXqlD/HVmVW MuFw== X-Gm-Message-State: ALyK8tII0oP3ZeFDHuCKgVXt+uPLMXptFc9KjRwkc/vPWxNAOLO7OuSdwIt9ex8nzMtDdIi3yQNjBpeqv/7I/g== X-Received: by 10.46.5.138 with SMTP id 132mr4795533ljf.9.1467747550501; Tue, 05 Jul 2016 12:39:10 -0700 (PDT) MIME-Version: 1.0 Sender: rraszuk@gmail.com Received: by 10.25.21.30 with HTTP; Tue, 5 Jul 2016 12:39:09 -0700 (PDT) In-Reply-To: References: From: Robert Raszuk Date: Tue, 5 Jul 2016 21:39:09 +0200 X-Google-Sender-Auth: z2jwfNl8LIiVjKx5EGf9ew3WOus Message-ID: To: amit bhagat Content-Type: multipart/alternative; boundary=001a114a733c5e20d00536e89bc5 Archived-At: Cc: idr wg Subject: Re: [Idr] Review Request for draft BGP Overload X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jul 2016 19:46:11 -0000 --001a114a733c5e20d00536e89bc5 Content-Type: text/plain; charset=UTF-8 Hi Amit, In an essence it seems that your proposal is just a subset of "Graceful BGP session shutdown" https://tools.ietf.org/html/draft-ietf-grow-bgp-gshut-06. Can you clarify how your encoding is any better then proposed by Pierre's, et al. G-Shut community? Why do you need a new SAFI for it ? Would it be easier to use community or attribute and send it over existing SAFIs ? How in your encoding one can distinguish IBGP sessions from EBGP sessions (case of core or edge line card replacement) ? What is the use case to not use "global" mode .. ie. when do you envision need to signal overload for only subset of AFI/SAFIs carried by given BGP speaker ? Many Thx, Robert. On Tue, Jul 5, 2016 at 9:25 PM, amit bhagat wrote: > Hey All, > > We are looking for your comments on the new draft > https://datatracker.ietf.org/doc/draft-bhagat-bgp-overload/ > > We would really appreciate any comments and questions about the document. > > Best Regards, > > Amit Bhagat > > > > _______________________________________________ > Idr mailing list > Idr@ietf.org > https://www.ietf.org/mailman/listinfo/idr > > --001a114a733c5e20d00536e89bc5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Amit,

In an essence it seems that your proposal is just a = subset of "Graceful BGP session shutdown"= =C2=A0https://tools.ietf.org/html/draft-ietf-grow-bgp-gshut-06.=C2=A0<= /div>

Can you clarify how yo= ur encoding is any better then proposed by Pierre's, et al. G-Shut comm= unity?=C2=A0

Why do yo= u need a new SAFI for it ? Would it be easier to use community or attribute= and send it over existing SAFIs ?=C2=A0

=
How in your encoding one can distinguish IBGP sessions f= rom EBGP sessions (case of core or edge line card replacement) ?=C2=A0

What is the use case to no= t use "global" mode .. ie. when do you envision need to signal ov= erload for only subset of AFI/SAFIs carried by given BGP speaker ?

Many Thx,
Robert.


On Tue, Jul 5, 2016 at 9:25 PM, amit bhagat <scet.amit@gma= il.com> wrote:
Hey All,

We are looking fo= r your comments on the new draft https://datatracker.ietf.or= g/doc/draft-bhagat-bgp-overload/

We would really appreciate any comments and que=
stions about the document.
=20
Best Regards,
Amit Bhagat


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


--001a114a733c5e20d00536e89bc5-- From nobody Tue Jul 5 15:12:55 2016 Return-Path: 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 B2D3212D0FC for ; Tue, 5 Jul 2016 15:12:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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 YMzqj1JctlnB for ; Tue, 5 Jul 2016 15:12:50 -0700 (PDT) Received: from mail-qt0-x236.google.com (mail-qt0-x236.google.com [IPv6:2607:f8b0:400d:c0d::236]) (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 2905D12B05B for ; Tue, 5 Jul 2016 15:12:50 -0700 (PDT) Received: by mail-qt0-x236.google.com with SMTP id w59so108386329qtd.3 for ; Tue, 05 Jul 2016 15:12:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=N+RRo9COZe1xK5SDynWyJPu3iU63gWSJb2AgjNa5YFU=; b=IpReQ+aReWn0tRAYXk1vlphS6bt5pObCfm9YDw4IQ1lUzCtbHF7i884ijLcn9ysOyV SAGBLlmRfmuvXxYvIZDK9ioOXa0vAYk0BrDycM/5RYz5LvSLouIuf3fxQ/b/uK3S2BTd 8+2Zv0tnREkhUzzpPjWzo/lMIeUYGAXnmBve6SqSnZ2/CoJ7ctQsXDnBwOQunkE68f2A uMMm4+aEjd/hlPE5yGMk9Hf6F+mMpoEgflCmYDtjMl4p9fWW7r65mjieNWb+CI1ZdfcX I7tYJJ3z0PmGsSE0vlEJMRMN3b/jTtWK2W2ylQ4bX2GcPfrT8MSZ/BUZgD9+g/BY8huX cLhA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=N+RRo9COZe1xK5SDynWyJPu3iU63gWSJb2AgjNa5YFU=; b=l2RMc1CpKIxWDCKS1joUEF0GPCXXvAGJvXkz+rqu81QXQQxGSpsm9DIObgjOpBUWYh 2FQAJ/snw29LOFLyEraReLwJT8sm0I07ntMMora3hvPyzgeNzKjsMYHYmiUhDNxOA0Qx ViQ0CBoM5raAhb3AowzGYKRh298G39uDI5xVJECjoPM3ZRNQDSDTGJAMHBoN9x3eVCNy Gukv24jJyTfzCkMGVLRCEenWnc1ip04Dnlt/cL4zROewjP6i/Cb0CyLvQWdR6fhZ3Lbn +iK/X9mhXncsGW3Z3iSyA2BIZ96WTQk28s2EOXzgQdINTpreGakFpTRyeP3b4K1qDWLg g2Xw== X-Gm-Message-State: ALyK8tI3clP29H7RRbQcIzXhkLjSAE/Gx6mfAC4CYRlvMem3BbQVP8hGAj3EUbfZrj1U+Qg8N2bu0JcB81szgg== X-Received: by 10.200.49.165 with SMTP id h34mr31129188qte.43.1467756769325; Tue, 05 Jul 2016 15:12:49 -0700 (PDT) MIME-Version: 1.0 Received: by 10.55.43.232 with HTTP; Tue, 5 Jul 2016 15:12:48 -0700 (PDT) In-Reply-To: References: From: amit bhagat Date: Tue, 5 Jul 2016 15:12:48 -0700 Message-ID: To: Robert Raszuk Content-Type: multipart/alternative; boundary=001a11c10850da391e0536eac0c7 Archived-At: Cc: idr wg Subject: Re: [Idr] Review Request for draft BGP Overload X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jul 2016 22:12:53 -0000 --001a11c10850da391e0536eac0c7 Content-Type: text/plain; charset=UTF-8 Hi Robert, Many thanks for your comments. Initially, I thought about using a community but that would mean putting all NLRIs in the Update message. This could also mean a different Update per-neighbor/per-peergroup. re: G-shut community - Reading through G-shut draft, it seems to be targeting a single use case - maintenance. Additionally, it requires manual configuration of route-policies. The way I envision this is a simple Update that is applicable to all peers; no need to worry about manipulating any BGP attributes. re: new SAFI - The reason for requesting a new SAFI is so that a new NLRI encoding can be defined to keep it simple. The existing SAFI would require adding NLRIs to the Update message. re: BGP session distinction - Is there a need to identify IBGP or EBGP session? Perhaps I am missing something. re: Global mode - the use case would be if a BGP speaker has multiple links to different peers and running different AFI/SAFI pairs per links, it might be just easy to drain a particular type of traffic rather than ALL traffic. Additionally, one of the other use cases I am thinking of is when a BGP speaker drops its Established neighbor-count below a threshold, it can advertise itself as "Overloaded". This can help avoid congestion. Agreed, this can also be the cause of network outage, but within a CLOS fabric, it should not be a problem due to multiple paths. Again, thanks for reviewing. Amit. On Tue, Jul 5, 2016 at 12:39 PM, Robert Raszuk wrote: > Hi Amit, > > In an essence it seems that your proposal is just a subset of "Graceful > BGP session shutdown" > https://tools.ietf.org/html/draft-ietf-grow-bgp-gshut-06. > > Can you clarify how your encoding is any better then proposed by Pierre's, > et al. G-Shut community? > > Why do you need a new SAFI for it ? Would it be easier to use community or > attribute and send it over existing SAFIs ? > > How in your encoding one can distinguish IBGP sessions from EBGP sessions > (case of core or edge line card replacement) ? > > What is the use case to not use "global" mode .. ie. when do you envision > need to signal overload for only subset of AFI/SAFIs carried by given BGP > speaker ? > > Many Thx, > Robert. > > > On Tue, Jul 5, 2016 at 9:25 PM, amit bhagat wrote: > >> Hey All, >> >> We are looking for your comments on the new draft >> https://datatracker.ietf.org/doc/draft-bhagat-bgp-overload/ >> >> We would really appreciate any comments and questions about the document. >> >> Best Regards, >> >> Amit Bhagat >> >> >> >> _______________________________________________ >> Idr mailing list >> Idr@ietf.org >> https://www.ietf.org/mailman/listinfo/idr >> >> > --001a11c10850da391e0536eac0c7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Robert,

Many than= ks for your comments.

Initially, I thought about using a commu= nity but that would mean putting all NLRIs in the Update message. This coul= d also mean a different Update per-neighbor/per-peergroup.

re:= G-shut community - Reading through G-shut draft, it seems to be targeting = a=20 single use case - maintenance. Additionally, it requires manual=20 configuration of route-policies. The way I envision this is a simple Update= that is applicable to all peers; no need to worry about manipulating any B= GP attributes.

re: new SAFI - The reason for reques= ting a new SAFI is so that a new NLRI encoding can be defined to keep it si= mple. The existing SAFI would require adding NLRIs to the Update message.
re: BGP session distinction - Is there a need to identify = IBGP or EBGP session? Perhaps I am missing something.

re:= Global mode - the use case would be if a BGP speaker has multiple links to= different peers and running different AFI/SAFI pairs per links, it might b= e just easy to drain a particular type of traffic rather than ALL traffic. =

Additionally, one of the other use cases I am= thinking of is when a BGP speaker drops=20 its Established neighbor-count below a threshold, it can advertise=20 itself as "Overloaded". This can help avoid congestion. Agreed, t= his can also be the cause of network outage, but within a CLOS fabric, it=20 should not be a problem due to multiple paths.

Again, thanks for reviewing.

Amit.

On Tue, Jul 5, 2016 at = 12:39 PM, Robert Raszuk <robert@raszuk.net> wrote:
Hi Amit,
=

In an essence it seems that= your proposal is just a subset of "Graceful BGP session shutdown"= ;=C2=A0https://tools.ietf.org/ht= ml/draft-ietf-grow-bgp-gshut-06.=C2=A0

Can you clarify how your encoding is any better then p= roposed by Pierre's, et al. G-Shut community?=C2=A0

Why do you need a new SAFI for it ? Would= it be easier to use community or attribute and send it over existing SAFIs= ?=C2=A0

How in your e= ncoding one can distinguish IBGP sessions from EBGP sessions (case of core = or edge line card replacement) ?=C2=A0

What is the use case to not use "global" mode ..= ie. when do you envision need to signal overload for only subset of AFI/SA= FIs carried by given BGP speaker ?

Many Thx,
Robert.


On Tue, Jul 5, 2016 at 9:25 PM, amit bhagat <<= a href=3D"mailto:scet.amit@gmail.com" target=3D"_blank">scet.amit@gmail.com= > wrote:
<= div class=3D"h5">
Hey All,

We are looking for your comments on the new draft https://datatracker.ietf.org/doc/draft-bhagat-bgp-overload/

We would really ap=
preciate any comments and questions about the document.
=20
Best Regards,
Amit Bhagat


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



--001a11c10850da391e0536eac0c7-- From nobody Tue Jul 5 15:36:52 2016 Return-Path: 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 A421612D0FD for ; Tue, 5 Jul 2016 15:36:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.4 X-Spam-Level: X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.198, 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 dchM7IXx1WkG for ; Tue, 5 Jul 2016 15:36:47 -0700 (PDT) Received: from mail-lf0-x22c.google.com (mail-lf0-x22c.google.com [IPv6:2a00:1450:4010:c07::22c]) (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 474AE12B022 for ; Tue, 5 Jul 2016 15:36:47 -0700 (PDT) Received: by mail-lf0-x22c.google.com with SMTP id l188so143787716lfe.2 for ; Tue, 05 Jul 2016 15:36:46 -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=G8KYTAWYRKVHksgDs07ObZ/8OdqoH2nP2FmfezUI8LU=; b=QhxDiig/VEKUEHl8spb/lMrkulfPPsSwYK791wK7gNZOgI4hOVOz33WxMWefrrkofH 0JjXnpXIMoQZfpt2qCw3LqwTjvYVoAdGaFuua3NZhu5GQ3npRgTIxKBoRUhLWWSVwr2E UOisXLxj6mSXjSqSIbMvaGy9JCqLQ4Z1WJxGyd15CRoDFhVwwmn3It71dRiYprKz1ZsO CppYNHpeEeRCXPjiXlZ6RSnZhZQHcnPWfrUJdKNthaJkiwl3lmMn/u3xlzUpu3x48yXN RFkUxeYTniIZYvb2EC+c8FowGxqDiUmYApOer28RlF6uOwlH+9I4W5Fbjhq65Yl41KR4 u1mA== 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=G8KYTAWYRKVHksgDs07ObZ/8OdqoH2nP2FmfezUI8LU=; b=eU4wbm/SP/D34+U3D4K3EVXbPWJOtXhEDwlt3I0ogQ3DLUIsfMLttnMilX80cufW5W xU8VfA0YKmc0ocjVtKHUeWGvgT74fhjkBXDJ59bvUJKLToYr/CQKsaOYvEMvKSOdTevl sjBstSUTKH4ZesMH8j0YtFndyiFhZ/Jt4MR/LGd6QZMSBUFpAaP4N2hG/Cqc/B6ooJ3/ xq4/7DwfPXARWY+Fe1qb3515aHHvMKI2nQji6vu7R6kOU9LicILug54RPRqQSOyZjsW/ IwqnHhfjUSuB2ffuYxGSYCroLN5m1E1WiY88IWSh/utf4lPtRrExY0VJHAdsJlAtZTzB nKlQ== X-Gm-Message-State: ALyK8tJSr9RPIFUgDHEXuaJjmk9bwiyaUlkZz0atUPOl3vM0h1sDFbJL1774S747OeQJxjTfWmrMShfoT0zwhA== X-Received: by 10.25.18.35 with SMTP id h35mr4118387lfi.82.1467758205139; Tue, 05 Jul 2016 15:36:45 -0700 (PDT) MIME-Version: 1.0 Sender: rraszuk@gmail.com Received: by 10.25.21.30 with HTTP; Tue, 5 Jul 2016 15:36:44 -0700 (PDT) In-Reply-To: References: From: Robert Raszuk Date: Wed, 6 Jul 2016 00:36:44 +0200 X-Google-Sender-Auth: XOU7ZRx2RCJxgJz6wSh0Y1yHVuM Message-ID: To: amit bhagat Content-Type: multipart/alternative; boundary=001a113fbed26f00670536eb168e Archived-At: Cc: idr wg Subject: Re: [Idr] Review Request for draft BGP Overload X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jul 2016 22:36:50 -0000 --001a113fbed26f00670536eb168e Content-Type: text/plain; charset=UTF-8 Hi Amit, Thank you for follow-up. One thing which perhaps needs to be addressed is how this (and few other recent proposals) is relates to Internet BGP vs L3 Clos DC fabric BGP. If your problem description is limited just to the latter due to inherent ECMP such message needs to only go one hop - so even a simple ORF extension will do just fine. Few years back BGP was stretched in one direction to accommodate carrying VPN information in WANs. Now I see it being more and more stretched in the opposite direction to accommodate various use case for DC underlay routing. And I think we all can realize what happens when you take even best material and stretch it with sufficient force in opposite directions :). As far as this draft to me what would be the best envelope for the information is really a new BGP message type .. BGP Operational Message. The work on that started few years back but were a bit put on hold. Defining new SAFI and making spagetti of SAFI-X to SAFI-Y operational inter-dependency kills the ability to separate SAFI dependent code from AF generic processing. Now if your use case is just about Clos topology in a given DC why not to use MED or LocalPref depending if your fabric is eBGP or iBGP based ? Is really re-advertisement of underlay routes such an issue ? Best regards, R. On Wed, Jul 6, 2016 at 12:12 AM, amit bhagat wrote: > Hi Robert, > > Many thanks for your comments. > > Initially, I thought about using a community but that would mean putting > all NLRIs in the Update message. This could also mean a different Update > per-neighbor/per-peergroup. > > re: G-shut community - Reading through G-shut draft, it seems to be > targeting a single use case - maintenance. Additionally, it requires manual > configuration of route-policies. The way I envision this is a simple Update > that is applicable to all peers; no need to worry about manipulating any > BGP attributes. > > re: new SAFI - The reason for requesting a new SAFI is so that a new NLRI > encoding can be defined to keep it simple. The existing SAFI would require > adding NLRIs to the Update message. > > re: BGP session distinction - Is there a need to identify IBGP or EBGP > session? Perhaps I am missing something. > > re: Global mode - the use case would be if a BGP speaker has multiple > links to different peers and running different AFI/SAFI pairs per links, it > might be just easy to drain a particular type of traffic rather than ALL > traffic. > > Additionally, one of the other use cases I am thinking of is when a BGP > speaker drops its Established neighbor-count below a threshold, it can > advertise itself as "Overloaded". This can help avoid congestion. Agreed, > this can also be the cause of network outage, but within a CLOS fabric, it > should not be a problem due to multiple paths. > > Again, thanks for reviewing. > > Amit. > > On Tue, Jul 5, 2016 at 12:39 PM, Robert Raszuk wrote: > >> Hi Amit, >> >> In an essence it seems that your proposal is just a subset of "Graceful >> BGP session shutdown" >> https://tools.ietf.org/html/draft-ietf-grow-bgp-gshut-06. >> >> Can you clarify how your encoding is any better then proposed by >> Pierre's, et al. G-Shut community? >> >> Why do you need a new SAFI for it ? Would it be easier to use community >> or attribute and send it over existing SAFIs ? >> >> How in your encoding one can distinguish IBGP sessions from EBGP sessions >> (case of core or edge line card replacement) ? >> >> What is the use case to not use "global" mode .. ie. when do you envision >> need to signal overload for only subset of AFI/SAFIs carried by given BGP >> speaker ? >> >> Many Thx, >> Robert. >> >> >> On Tue, Jul 5, 2016 at 9:25 PM, amit bhagat wrote: >> >>> Hey All, >>> >>> We are looking for your comments on the new draft >>> https://datatracker.ietf.org/doc/draft-bhagat-bgp-overload/ >>> >>> We would really appreciate any comments and questions about the document. >>> >>> Best Regards, >>> >>> Amit Bhagat >>> >>> >>> >>> _______________________________________________ >>> Idr mailing list >>> Idr@ietf.org >>> https://www.ietf.org/mailman/listinfo/idr >>> >>> >> > --001a113fbed26f00670536eb168e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Amit,

Thank you for follow-up.=C2=A0

One thing which perhaps needs to be address= ed is how this (and few other recent proposals) is relates to Internet BGP = vs L3 Clos DC fabric BGP. If your problem description is limited just to th= e latter due to inherent ECMP such message needs to only go one hop - so ev= en a simple ORF extension will do just fine.=C2=A0
=
Few years back BGP was stretched in one direct= ion to accommodate carrying VPN information in WANs. Now I see it being mor= e and more stretched in the opposite direction to accommodate various use c= ase for DC underlay routing.=C2=A0

And I think we all can realize what happens when you take eve= n best material and stretch it with sufficient force in opposite directions= :).=C2=A0

As far as t= his draft to me what would be the best envelope for the information is real= ly a new BGP message type .. BGP Operational Message. The work on that star= ted few years back but were a bit put on hold.=C2=A0

Defining new SAFI and making spagetti of SAF= I-X to SAFI-Y operational inter-dependency kills the ability to separate SA= FI dependent code from AF generic processing.=C2=A0

Now if your use case is just about Clos topol= ogy in a given DC why not to use MED or LocalPref depending if your fabric = is eBGP or iBGP based ? Is really re-advertisement of underlay routes such = an issue ?=C2=A0

Best = regards,
R.



=C2=A0

=
On Wed, Jul 6, 2016 at 12:12 AM, amit bhagat <scet.amit@gmail.com> wrote:
Hi Robert,

Many th= anks for your comments.

Initially, I thought about using a com= munity but that would mean putting all NLRIs in the Update message. This co= uld also mean a different Update per-neighbor/per-peergroup.

r= e: G-shut community - Reading through G-shut draft, it seems to be targetin= g a=20 single use case - maintenance. Additionally, it requires manual=20 configuration of route-policies. The way I envision this is a simple Update= that is applicable to all peers; no need to worry about manipulating any B= GP attributes.

re: new SAFI - The reason for reques= ting a new SAFI is so that a new NLRI encoding can be defined to keep it si= mple. The existing SAFI would require adding NLRIs to the Update message.
re: BGP session distinction - Is there a need to identify = IBGP or EBGP session? Perhaps I am missing something.

re:= Global mode - the use case would be if a BGP speaker has multiple links to= different peers and running different AFI/SAFI pairs per links, it might b= e just easy to drain a particular type of traffic rather than ALL traffic. =

Additionally, one of the other use cases I am= thinking of is when a BGP speaker drops=20 its Established neighbor-count below a threshold, it can advertise=20 itself as "Overloaded". This can help avoid congestion. Agreed, t= his can also be the cause of network outage, but within a CLOS fabric, it=20 should not be a problem due to multiple paths.

Again, thanks for reviewing.

Amit.

On Tue, J= ul 5, 2016 at 12:39 PM, Robert Raszuk <robert@raszuk.net> wr= ote:
= Hi Amit,

In an essence= it seems that your proposal is just a subset of "Graceful BGP session= shutdown"=C2=A0https://too= ls.ietf.org/html/draft-ietf-grow-bgp-gshut-06.=C2=A0

Can you clarify how your encoding is any= better then proposed by Pierre's, et al. G-Shut community?=C2=A0
=

Why do you need a new SAFI = for it ? Would it be easier to use community or attribute and send it over = existing SAFIs ?=C2=A0

How in your encoding one can distinguish IBGP sessions from EBGP sessions = (case of core or edge line card replacement) ?=C2=A0

What is the use case to not use "global= " mode .. ie. when do you envision need to signal overload for only su= bset of AFI/SAFIs carried by given BGP speaker ?
Many Thx,
Robert.

On Tue, Jul 5, 2016 at 9:25 PM, amit bhagat <scet.amit@gmail.com> wrote:
Hey = All,

We = are looking for your comments on the new draft
https://datat= racker.ietf.org/doc/draft-bhagat-bgp-overload/

We would really appreciate any co=
mments and questions about the document.
=20
Best Regards,
Amit Bhagat


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




--001a113fbed26f00670536eb168e-- From nobody Tue Jul 5 16:08:11 2016 Return-Path: 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 D8CC912D115 for ; Tue, 5 Jul 2016 16:08:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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 D3bTLFkORt5b for ; Tue, 5 Jul 2016 16:08:07 -0700 (PDT) Received: from mail-qk0-x22e.google.com (mail-qk0-x22e.google.com [IPv6:2607:f8b0:400d:c09::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 2A26B12B02F for ; Tue, 5 Jul 2016 16:08:07 -0700 (PDT) Received: by mail-qk0-x22e.google.com with SMTP id s126so17893125qkh.2 for ; Tue, 05 Jul 2016 16:08:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=L8MTHQeuxV9mqIhKBA1+UJjz60fBS6bRh3GDiVoEj6E=; b=RMRhyuTNPtZ+FEA/RmVDatUZQbuMZZQpHugsg2UYOIrkMcdWYsGluPc7UYcL8Q9ejD 3sWkeN+zOvNpJqUaJHcV+zLb0a96h2+68HTTSD85NOklZVDtPslPCXe/0OAxd6iGyxaX 6URTzlQbcCDherS6ZvmXdpGuEcMcbzoiT9sCxE4IDAIPoB5LjXfn+SbqWpFZrGfq8piG AHek7ARdQ/F/3NQvbbimzeBQmPeDCDVlu1AiNxkjraPu68HLWQ/oCYRjPsX5IDIHbQzA dBCsk5Lcp/0Cr7OVtMFB9gwiYviIc/EYH5v8I53P5SuskgkXoodvxTdRUNesT0mv6iKq W4bg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=L8MTHQeuxV9mqIhKBA1+UJjz60fBS6bRh3GDiVoEj6E=; b=iDdP4s+CGwAupS70AfNjGMzFpZ9sjgOFaU41d+B6pBqlm3n+jqeMqAcd5J3iZU2WIW PIf1Lp2TMsxonWrLqrZEoWiPGWnq0IjDwkQFbUjG7GvcCnOCk7/vft/IMaDxaM2cki2i IXGWmc8TPraMOjzleo8bFXkEEAuX+ZZvsD2CTJRYoE+QAuV3ff16No57sD6SYQd4NdbE vqPHh0oydoYkS3RGrbAumITukiV1sKpvRzu7DAFRIFJkgHSaqJZp7yBtrHNXhPxaiLKw R5j4fRWmqAJBcTMKCZ28f24Y9Zj5yvpXyJghpVTUXiGh08mg/EFRTq7DMVKMbmckPTs4 rv3Q== X-Gm-Message-State: ALyK8tLppkcqE5xBcd1w4skAY4pau2tlqRQMbVxJAbNfCLcYquJyg8p579iZ1mq7OCghzsEg9z+olZaEMgh4ig== X-Received: by 10.55.188.198 with SMTP id m189mr25514605qkf.205.1467760086357; Tue, 05 Jul 2016 16:08:06 -0700 (PDT) MIME-Version: 1.0 Received: by 10.55.43.232 with HTTP; Tue, 5 Jul 2016 16:08:05 -0700 (PDT) In-Reply-To: References: From: amit bhagat Date: Tue, 5 Jul 2016 16:08:05 -0700 Message-ID: To: Robert Raszuk Content-Type: multipart/alternative; boundary=94eb2c048d24901dd40536eb86c8 Archived-At: Cc: idr wg Subject: Re: [Idr] Review Request for draft BGP Overload X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jul 2016 23:08:10 -0000 --94eb2c048d24901dd40536eb86c8 Content-Type: text/plain; charset=UTF-8 Hi Robert, I agree that recently BGP is being stretched towards DC-fabric side to encompass various use cases. However, the way I see this draft, it can be useful for both, Internet and DC-fabrics. The main reason is to keep traffic drain procedure BGP topology agnostic, exactly same as ISIS Overload-bit. Agree, BGP has a bigger blast radius in Internet compared to ISIS but appropriate implementation of the feature can provide good benefits. Thanks. Amit On Tue, Jul 5, 2016 at 3:36 PM, Robert Raszuk wrote: > Hi Amit, > > Thank you for follow-up. > > One thing which perhaps needs to be addressed is how this (and few other > recent proposals) is relates to Internet BGP vs L3 Clos DC fabric BGP. If > your problem description is limited just to the latter due to inherent ECMP > such message needs to only go one hop - so even a simple ORF extension will > do just fine. > > Few years back BGP was stretched in one direction to accommodate carrying > VPN information in WANs. Now I see it being more and more stretched in the > opposite direction to accommodate various use case for DC underlay routing. > > And I think we all can realize what happens when you take even best > material and stretch it with sufficient force in opposite directions :). > > As far as this draft to me what would be the best envelope for the > information is really a new BGP message type .. BGP Operational Message. > The work on that started few years back but were a bit put on hold. > > Defining new SAFI and making spagetti of SAFI-X to SAFI-Y operational > inter-dependency kills the ability to separate SAFI dependent code from AF > generic processing. > > Now if your use case is just about Clos topology in a given DC why not to > use MED or LocalPref depending if your fabric is eBGP or iBGP based ? Is > really re-advertisement of underlay routes such an issue ? > > Best regards, > R. > > > > > > > On Wed, Jul 6, 2016 at 12:12 AM, amit bhagat wrote: > >> Hi Robert, >> >> Many thanks for your comments. >> >> Initially, I thought about using a community but that would mean putting >> all NLRIs in the Update message. This could also mean a different Update >> per-neighbor/per-peergroup. >> >> re: G-shut community - Reading through G-shut draft, it seems to be >> targeting a single use case - maintenance. Additionally, it requires manual >> configuration of route-policies. The way I envision this is a simple Update >> that is applicable to all peers; no need to worry about manipulating any >> BGP attributes. >> >> re: new SAFI - The reason for requesting a new SAFI is so that a new NLRI >> encoding can be defined to keep it simple. The existing SAFI would require >> adding NLRIs to the Update message. >> >> re: BGP session distinction - Is there a need to identify IBGP or EBGP >> session? Perhaps I am missing something. >> >> re: Global mode - the use case would be if a BGP speaker has multiple >> links to different peers and running different AFI/SAFI pairs per links, it >> might be just easy to drain a particular type of traffic rather than ALL >> traffic. >> >> Additionally, one of the other use cases I am thinking of is when a BGP >> speaker drops its Established neighbor-count below a threshold, it can >> advertise itself as "Overloaded". This can help avoid congestion. Agreed, >> this can also be the cause of network outage, but within a CLOS fabric, it >> should not be a problem due to multiple paths. >> >> Again, thanks for reviewing. >> >> Amit. >> >> On Tue, Jul 5, 2016 at 12:39 PM, Robert Raszuk wrote: >> >>> Hi Amit, >>> >>> In an essence it seems that your proposal is just a subset of "Graceful >>> BGP session shutdown" >>> https://tools.ietf.org/html/draft-ietf-grow-bgp-gshut-06. >>> >>> Can you clarify how your encoding is any better then proposed by >>> Pierre's, et al. G-Shut community? >>> >>> Why do you need a new SAFI for it ? Would it be easier to use community >>> or attribute and send it over existing SAFIs ? >>> >>> How in your encoding one can distinguish IBGP sessions from EBGP >>> sessions (case of core or edge line card replacement) ? >>> >>> What is the use case to not use "global" mode .. ie. when do you >>> envision need to signal overload for only subset of AFI/SAFIs carried by >>> given BGP speaker ? >>> >>> Many Thx, >>> Robert. >>> >>> >>> On Tue, Jul 5, 2016 at 9:25 PM, amit bhagat wrote: >>> >>>> Hey All, >>>> >>>> We are looking for your comments on the new draft >>>> https://datatracker.ietf.org/doc/draft-bhagat-bgp-overload/ >>>> >>>> We would really appreciate any comments and questions about the document. >>>> >>>> Best Regards, >>>> >>>> Amit Bhagat >>>> >>>> >>>> >>>> _______________________________________________ >>>> Idr mailing list >>>> Idr@ietf.org >>>> https://www.ietf.org/mailman/listinfo/idr >>>> >>>> >>> >> > --94eb2c048d24901dd40536eb86c8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Robert,

I agree that r= ecently BGP is being stretched towards DC-fabric side to encompass various = use cases.

However, the way I see this draft, it can be useful= for both, Internet and DC-fabrics. The main reason is to keep traffic drai= n procedure BGP topology agnostic, exactly same as ISIS Overload-bit. Agree= , BGP has a bigger blast radius in Internet compared to ISIS but appropriat= e implementation of the feature can provide good benefits.

Tha= nks.
Amit

On Tue, Jul 5, 2016 at 3:36 PM, Robert Raszuk = <robert@raszuk.ne= t> wrote:
=
Hi Amit,

Thank you for follow-up.=C2=A0

One thing which perhaps needs to be addressed is how this (a= nd few other recent proposals) is relates to Internet BGP vs L3 Clos DC fab= ric BGP. If your problem description is limited just to the latter due to i= nherent ECMP such message needs to only go one hop - so even a simple ORF e= xtension will do just fine.=C2=A0

Few years back BGP was stretched in one direction to accommod= ate carrying VPN information in WANs. Now I see it being more and more stre= tched in the opposite direction to accommodate various use case for DC unde= rlay routing.=C2=A0

An= d I think we all can realize what happens when you take even best material = and stretch it with sufficient force in opposite directions :).=C2=A0
=

As far as this draft to me = what would be the best envelope for the information is really a new BGP mes= sage type .. BGP Operational Message. The work on that started few years ba= ck but were a bit put on hold.=C2=A0

Defining new SAFI and making spagetti of SAFI-X to SAFI-Y op= erational inter-dependency kills the ability to separate SAFI dependent cod= e from AF generic processing.=C2=A0

Now if your use case is just about Clos topology in a given D= C why not to use MED or LocalPref depending if your fabric is eBGP or iBGP = based ? Is really re-advertisement of underlay routes such an issue ?=C2=A0=

Best regards,
R.



=C2=A0

On Wed, Jul 6, 2016 at 1= 2:12 AM, amit bhagat <scet.amit@gmail.com> wrote:
Hi Robe= rt,

Many thanks for your comments.

Initially, I t= hought about using a community but that would mean putting all NLRIs in the= Update message. This could also mean a different Update per-neighbor/per-p= eergroup.

re: G-shut community - Reading through G-shut draft,= it seems to be targeting a=20 single use case - maintenance. Additionally, it requires manual=20 configuration of route-policies. The way I envision this is a simple Update= that is applicable to all peers; no need to worry about manipulating any B= GP attributes.

re: new SAFI - The reason for reques= ting a new SAFI is so that a new NLRI encoding can be defined to keep it si= mple. The existing SAFI would require adding NLRIs to the Update message.
re: BGP session distinction - Is there a need to identify = IBGP or EBGP session? Perhaps I am missing something.

re:= Global mode - the use case would be if a BGP speaker has multiple links to= different peers and running different AFI/SAFI pairs per links, it might b= e just easy to drain a particular type of traffic rather than ALL traffic. =

Additionally, one of the other use cases I am= thinking of is when a BGP speaker drops=20 its Established neighbor-count below a threshold, it can advertise=20 itself as "Overloaded". This can help avoid congestion. Agreed, t= his can also be the cause of network outage, but within a CLOS fabric, it=20 should not be a problem due to multiple paths.

Again, thanks for reviewing.

<= /span>
Amit.

= On Tue, Jul 5, 2016 at 12:39 PM, Robert Raszuk <robert@raszuk.net><= /span> wrote:
Hi Amit,

In a= n essence it seems that your proposal is just a subset of "Graceful BG= P session shutdown"=C2=A0ht= tps://tools.ietf.org/html/draft-ietf-grow-bgp-gshut-06.=C2=A0

Can you clarify how your encodi= ng is any better then proposed by Pierre's, et al. G-Shut community?=C2= =A0

Why do you need a = new SAFI for it ? Would it be easier to use community or attribute and send= it over existing SAFIs ?=C2=A0

How in your encoding one can distinguish IBGP sessions from EBGP = sessions (case of core or edge line card replacement) ?=C2=A0

What is the use case to not use &qu= ot;global" mode .. ie. when do you envision need to signal overload fo= r only subset of AFI/SAFIs carried by given BGP speaker ?

Many Thx,
Robert.


On Tue, Jul 5, 2016 at 9:25 PM, amit bhagat <scet.amit= @gmail.com> wrote:
Hey All,

We are looking for your comments on the new draft h= ttps://datatracker.ietf.org/doc/draft-bhagat-bgp-overload/

We would really appre=
ciate any comments and questions about the document.
=20
Best Regards,
Amit Bhagat


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





--94eb2c048d24901dd40536eb86c8-- From nobody Tue Jul 5 16:10:20 2016 Return-Path: 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 9556F12D15E for ; Tue, 5 Jul 2016 16:10:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -15.947 X-Spam-Level: X-Spam-Status: No, score=-15.947 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 JYeZnoKI9q39 for ; Tue, 5 Jul 2016 16:10:16 -0700 (PDT) Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C113D12D158 for ; Tue, 5 Jul 2016 16:10:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1648; q=dns/txt; s=iport; t=1467760216; x=1468969816; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=L3R4POy15dPWPVkNNZxxk0EKd6vfOd/KsFnrrnwmB4U=; b=T6UsspAyaldff8vwfXdFe0xzSkYaHqXx0FhBb/bdeWeTX+zhdPjUuO74 Gx2MXssPnuTT45RAt4DkP5IBXlC9j/kzceoZbGYpZ1n65e2GCiy80bxIk Gdz+dbjNkNMOUrx6Nkl2RwKKVs2dXPh6yxHkXMtk+p9Ps+0hnPEBWn4BR g=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AjAgD7PXxX/40NJK1cgz5WfAatMowQg?= =?us-ascii?q?XckhXQCHIEUOBQBAQEBAQEBZRwLhEwBAQUjEUMOBAIBCBoCJgICAh8RFQYBBgM?= =?us-ascii?q?CBBMIDIgCAxcOq2iLQA2EMQEBAQEBAQEBAQEBAQEBAQEBAQEBARcFgQGFJoRNg?= =?us-ascii?q?kOEfoJaBY4EhVWFBjQBhgiGLoIJjzGIF4dyAR42g3BuAYdUAX4BAQE?= X-IronPort-AV: E=Sophos;i="5.28,315,1464652800"; d="scan'208";a="293854662" Received: from alln-core-8.cisco.com ([173.36.13.141]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 05 Jul 2016 23:10:16 +0000 Received: from XCH-RCD-013.cisco.com (xch-rcd-013.cisco.com [173.37.102.23]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id u65NAF0Z000483 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for ; Tue, 5 Jul 2016 23:10:15 GMT Received: from xch-aln-014.cisco.com (173.36.7.24) by XCH-RCD-013.cisco.com (173.37.102.23) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 5 Jul 2016 18:10:15 -0500 Received: from xch-aln-014.cisco.com ([173.36.7.24]) by XCH-ALN-014.cisco.com ([173.36.7.24]) with mapi id 15.00.1210.000; Tue, 5 Jul 2016 18:10:15 -0500 From: "Jakob Heitz (jheitz)" To: "idr@ietf.org" Thread-Topic: New Version Notification for draft-heitz-idr-large-community-00.txt Thread-Index: AQHR1wxN7gRrWu0/MEuLSZwDv2jjd6AKbpHw Date: Tue, 5 Jul 2016 23:10:15 +0000 Message-ID: References: <20160705222638.22322.81874.idtracker@ietfa.amsl.com> In-Reply-To: <20160705222638.22322.81874.idtracker@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [128.107.147.26] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 Archived-At: Subject: [Idr] FW: New Version Notification for draft-heitz-idr-large-community-00.txt X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jul 2016 23:10:18 -0000 QSBsYXJnZXIgZXh0ZW5kZWQgY29tbXVuaXR5IGlzIHByb3Bvc2VkLg0KVGhlIGludGVudCBpcyBu b3QgdG8gcHJvdmlkZSBhIGZsZXhpYmxlIGFuZCBwb3dlcmZ1bA0KY29udGFpbmVyIGZvciBpbmZv cm1hdGlvbiwgYnV0IHNpbXBseSBhbiBpbmNyZWFzZSBpbg0Kc2l6ZSB3aXRob3V0IGltcGFjdGlu ZyB0aGUgcm91dGluZyBwb2xpY2llcyB0aGF0IG9wZXJhdG9ycw0KY3VycmVudGx5IHVzZS4NCg0K Q29tbWVudHMgYXJlIHdlbGNvbWUuDQoNClRoYW5rcywNCkpha29iIEhlaXR6LA0KSm9iIFNuaWpk ZXJzLg0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KVG86IEpha29iIEhlaXR6IChqaGVp dHopIDxqaGVpdHpAY2lzY28uY29tPjsgSWduYXMgQmFnZG9uYXMgPGliYWdkb25hLmlldGZAZ21h aWwuY29tPjsgSm9iIFNuaWpkZXJzIDxqb2JAbnR0Lm5ldD47IEtleXVyIFBhdGVsIChrZXl1cGF0 ZSkgPGtleXVwYXRlQGNpc2NvLmNvbT4NCg0KDQpBIG5ldyB2ZXJzaW9uIG9mIEktRCwgZHJhZnQt aGVpdHotaWRyLWxhcmdlLWNvbW11bml0eS0wMC50eHQNCmhhcyBiZWVuIHN1Y2Nlc3NmdWxseSBz dWJtaXR0ZWQgYnkgSmFrb2IgSGVpdHogYW5kIHBvc3RlZCB0byB0aGUNCklFVEYgcmVwb3NpdG9y eS4NCg0KTmFtZToJCWRyYWZ0LWhlaXR6LWlkci1sYXJnZS1jb21tdW5pdHkNClJldmlzaW9uOgkw MA0KVGl0bGU6CQlMYXJnZSBCR1AgQ29tbXVuaXR5DQpEb2N1bWVudCBkYXRlOgkyMDE2LTA3LTA1 DQpHcm91cDoJCUluZGl2aWR1YWwgU3VibWlzc2lvbg0KUGFnZXM6CQk5DQpVUkw6ICAgICAgICAg ICAgaHR0cHM6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWhlaXR6LWlkci1s YXJnZS1jb21tdW5pdHktMDAudHh0DQpTdGF0dXM6ICAgICAgICAgaHR0cHM6Ly9kYXRhdHJhY2tl ci5pZXRmLm9yZy9kb2MvZHJhZnQtaGVpdHotaWRyLWxhcmdlLWNvbW11bml0eS8NCkh0bWxpemVk OiAgICAgICBodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaGVpdHotaWRyLWxhcmdl LWNvbW11bml0eS0wMA0KDQoNCkFic3RyYWN0Og0KICAgQSBuZXcgdHlwZSBvZiBCR1AgY29tbXVu aXR5IGF0dHJpYnV0ZSB0aGF0IGNvbnRhaW5zIGNvbW11bml0aWVzIHRoYXQNCiAgIGVhY2ggaG9s ZCBhIDQtb2N0ZXQgQVMgbnVtYmVyIGFuZCBhIDYtb2N0ZXQgb3BhcXVlIGZpZWxkIGlzIGRlZmlu ZWQuDQo= From nobody Tue Jul 5 16:28:02 2016 Return-Path: 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 586A312D137 for ; Tue, 5 Jul 2016 16:27:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 3.638 X-Spam-Level: *** X-Spam-Status: No, score=3.638 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, RDNS_NONE=0.793] autolearn=no 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 JRrSdQttu1p3 for ; Tue, 5 Jul 2016 16:27:54 -0700 (PDT) Received: from hickoryhill-consulting.com (unknown [50.245.122.97]) (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 C758B12D520 for ; Tue, 5 Jul 2016 16:27:52 -0700 (PDT) X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=174.124.185.200; From: "Susan Hares" To: , "'Keyur Patel \(keyupate\)'" , , "'Bruno Decraene'" , "'Henderickx, Wim \(Nokia - BE\)'" , Date: Tue, 5 Jul 2016 19:27:12 -0400 Message-ID: <068e01d1d714$c3002760$49007620$@ndzh.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_068F_01D1D6F3.3BEEFC90" X-Mailer: Microsoft Outlook 14.0 Content-Language: en-us Thread-Index: AdHXFCd9QgWs5X1ZTnmBFEDm50qIHg== X-Authenticated-User: skh@ndzh.com Archived-At: Subject: Re: [Idr] WG Adoption of draft-keyupate-idr-bgp-attribute-announcement - 2 week WG Adoption call (6/6 to 6/20) X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jul 2016 23:27:55 -0000 This is a multipart message in MIME format. ------=_NextPart_000_068F_01D1D6F3.3BEEFC90 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit This ends the 2 week WG Adoption call for draft-keyupate-idr-bgp-attribute-announcement. The WG has adopted this draft. The Co-chairs forgot to do an IPR call on this draft. The authors should indicate whether they know of IPR on this draft. After we receive all the IPR statements, the authors will be able to upload this as draft-ietf-idr-bgp-attribute-announcement-00.txt. Sue Hares and John Scudder. ------=_NextPart_000_068F_01D1D6F3.3BEEFC90 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

This ends the 2 week WG Adoption call for = draft-keyupate-idr-bgp-attribute-announcement.  The WG has adopted = this draft. 

The Co-chairs forgot to do an IPR call on this = draft.   The authors should indicate whether they know of IPR = on this draft.   After we receive all the IPR statements, the = authors will be able to upload this as = draft-ietf-idr-bgp-attribute-announcement-00.txt.  =

Sue Hares and John Scudder. =

------=_NextPart_000_068F_01D1D6F3.3BEEFC90-- From nobody Tue Jul 5 17:05:49 2016 Return-Path: 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 4984712D0CA for ; Tue, 5 Jul 2016 17:05:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -15.946 X-Spam-Level: X-Spam-Status: No, score=-15.946 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 PeVOlVtdO0RK for ; Tue, 5 Jul 2016 17:05:41 -0700 (PDT) Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE62D12D1AF for ; Tue, 5 Jul 2016 17:05:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6196; q=dns/txt; s=iport; t=1467763538; x=1468973138; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=BwO88np8Ne8BWEdb8qGQnzl2k4J7kneJXVtjzEWdqQM=; b=dwasXEpq3qswVTRr/y9TkVHQKHb/J35O++zceMDQIHS6Ul61gf5Emgws 3WjwnR/xTPCA5RHkaaKX+L7OrToC4DUe3lkgYP5MGWXreSAgLL1PpxERW sksEDLTWK3PHKKjdJCprDFyjwRyOODag7ziAGWD/SVvhCgcL49/bQOlJJ U=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BCAgClSnxX/5ldJa1cgnBOVnwGtEOFA?= =?us-ascii?q?YF3hhgCgTA4FAEBAQEBAQFlJ4RMAQEFHRBMEAIBCA4DAwECJAQHMhQJCAIEAQ0?= =?us-ascii?q?FiDC7fAEBAQEBAQEBAQEBAQEBAQEBAQEBARyGJ4RNhGCFOwWTWYU6AY5GjyqQC?= =?us-ascii?q?QEeNoI7gTVuh1V/AQEB?= X-IronPort-AV: E=Sophos;i="5.28,316,1464652800"; d="scan'208,217";a="294051608" Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Jul 2016 00:05:37 +0000 Received: from XCH-RTP-016.cisco.com (xch-rtp-016.cisco.com [64.101.220.156]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id u6605bSu018462 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 6 Jul 2016 00:05:37 GMT Received: from xch-rtp-017.cisco.com (64.101.220.157) by XCH-RTP-016.cisco.com (64.101.220.156) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 5 Jul 2016 20:05:36 -0400 Received: from xch-rtp-017.cisco.com ([64.101.220.157]) by XCH-RTP-017.cisco.com ([64.101.220.157]) with mapi id 15.00.1210.000; Tue, 5 Jul 2016 20:05:36 -0400 From: "Keyur Patel (keyupate)" To: Susan Hares , "idr@ietf.org" , "uttaro@att.com" , "'Bruno Decraene'" , "'Henderickx, Wim (Nokia - BE)'" , "jhaas@pfrc.org" Thread-Topic: [Idr] WG Adoption of draft-keyupate-idr-bgp-attribute-announcement - 2 week WG Adoption call (6/6 to 6/20) Thread-Index: AQHR1xofQA6BrIY5ZEmYcC2sVJZtqw== Date: Wed, 6 Jul 2016 00:05:36 +0000 Message-ID: References: <068e01d1d714$c3002760$49007620$@ndzh.com> In-Reply-To: <068e01d1d714$c3002760$49007620$@ndzh.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.4.9.150325 x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.154.162.162] Content-Type: multipart/alternative; boundary="_000_D3A1993345D98keyupateciscocom_" MIME-Version: 1.0 Archived-At: Subject: Re: [Idr] WG Adoption of draft-keyupate-idr-bgp-attribute-announcement - 2 week WG Adoption call (6/6 to 6/20) X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jul 2016 00:05:44 -0000 --_000_D3A1993345D98keyupateciscocom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I am not aware of any IPR related to this document. Regards, Keyur From: Susan Hares > Date: Wednesday, July 6, 2016 at 1:27 AM To: "idr@ietf.org" >= , Keyur Patel >, "uttaro@att.= com" >, 'Bruno= Decraene' >, "= 'Henderickx, Wim (Nokia - BE)'" >, "jhaas@pfrc.org" > Cc: "'John G. Scudder'" > Subject: RE: [Idr] WG Adoption of draft-keyupate-idr-bgp-attribute-announce= ment - 2 week WG Adoption call (6/6 to 6/20) This ends the 2 week WG Adoption call for draft-keyupate-idr-bgp-attribute-= announcement. The WG has adopted this draft. The Co-chairs forgot to do an IPR call on this draft. The authors should = indicate whether they know of IPR on this draft. After we receive all the= IPR statements, the authors will be able to upload this as draft-ietf-idr-= bgp-attribute-announcement-00.txt. Sue Hares and John Scudder. --_000_D3A1993345D98keyupateciscocom_ Content-Type: text/html; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable
I am not aware of any IPR related to this document.

Regards,
Keyur

From: Susan Hares <shares@ndzh.com>
Date: Wednesday, July 6, 2016 at 1:= 27 AM
To: "idr@ietf.org" <idr@ietf.= org>, Keyur Patel <keyupate= @cisco.com>, "uttaro@att.com<= /a>" <uttaro@att.com>, 'Bruno Decra= ene' <bruno.decraene@orange= .com>, "'Henderickx, Wim (Nokia - BE)'" <wim.henderickx@nokia.com>, "jhaas@pfrc.org" <jhaas@pfrc.org>
Cc: "'John G. Scudder'" &= lt;jgs@juniper.net>
Subject: RE: [Idr] WG Adoption of d= raft-keyupate-idr-bgp-attribute-announcement - 2 week WG Adoption call (6/6= to 6/20)

This ends the 2 week WG Adoption call = for draft-keyupate-idr-bgp-attribute-announcement.  The WG has adopted= this draft. 

The Co-chairs forgot to do an IPR call= on this draft.   The authors should indicate whether they know o= f IPR on this draft.   After we receive all the IPR statements, the authors will be able to upload this as draft-ietf-idr-= bgp-attribute-announcement-00.txt. 

Sue Hares and John Scudder.

--_000_D3A1993345D98keyupateciscocom_-- From nobody Tue Jul 5 23:18:35 2016 Return-Path: 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 393D512B05C for ; Tue, 5 Jul 2016 23:18:33 -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 LEyz_ygICCHG for ; Tue, 5 Jul 2016 23:18:30 -0700 (PDT) Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (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 37AEB12B03D for ; Tue, 5 Jul 2016 23:18:30 -0700 (PDT) Received: from fr712umx4.dmz.alcatel-lucent.com (unknown [135.245.210.45]) by Websense Email Security Gateway with ESMTPS id 57832C9B2E0A3; Wed, 6 Jul 2016 06:18:25 +0000 (GMT) Received: from fr712usmtp2.zeu.alcatel-lucent.com (fr712usmtp2.zeu.alcatel-lucent.com [135.239.2.42]) by fr712umx4.dmz.alcatel-lucent.com (GMO-o) with ESMTP id u666IPrU001207 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 6 Jul 2016 06:18:26 GMT Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id u666IOaY002705 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 6 Jul 2016 08:18:25 +0200 Received: from FR711WXCHMBA07.zeu.alcatel-lucent.com ([169.254.3.160]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.03.0195.001; Wed, 6 Jul 2016 08:18:24 +0200 From: "Henderickx, Wim (Nokia - BE)" To: "Keyur Patel (keyupate)" , Susan Hares , "idr@ietf.org" , "uttaro@att.com" , "'Bruno Decraene'" , "jhaas@pfrc.org" Thread-Topic: [Idr] WG Adoption of draft-keyupate-idr-bgp-attribute-announcement - 2 week WG Adoption call (6/6 to 6/20) Thread-Index: AQHR1xouBGjuO1kQsE2xQtFsweKRXqAK7jGA Date: Wed, 6 Jul 2016 06:18:23 +0000 Message-ID: <6A4039E1-71DE-440A-B5E8-9EEF0A0448E7@alcatel-lucent.com> References: <068e01d1d714$c3002760$49007620$@ndzh.com> In-Reply-To: Accept-Language: nl-BE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/0.0.0.151008 x-originating-ip: [135.239.27.41] Content-Type: multipart/alternative; boundary="_000_6A4039E171DE440AB5E89EEF0A0448E7alcatellucentcom_" MIME-Version: 1.0 Archived-At: Subject: Re: [Idr] WG Adoption of draft-keyupate-idr-bgp-attribute-announcement - 2 week WG Adoption call (6/6 to 6/20) X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jul 2016 06:18:33 -0000 --_000_6A4039E171DE440AB5E89EEF0A0448E7alcatellucentcom_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 SSBhbSBOb3QgYXdhcmUgb2YgYW55IElQUiByZWxhdGVkIHRvIHRoaXMgZG9jDQoNCkZyb206IEtl eXVyIFBhdGVsIDxrZXl1cGF0ZUBjaXNjby5jb208bWFpbHRvOmtleXVwYXRlQGNpc2NvLmNvbT4+ DQpEYXRlOiBXZWRuZXNkYXkgNiBKdWx5IDIwMTYgYXQgMDI6MDUNClRvOiBTdXNhbiBIYXJlcyA8 c2hhcmVzQG5kemguY29tPG1haWx0bzpzaGFyZXNAbmR6aC5jb20+PiwgImlkckBpZXRmLm9yZzxt YWlsdG86aWRyQGlldGYub3JnPiIgPGlkckBpZXRmLm9yZzxtYWlsdG86aWRyQGlldGYub3JnPj4s IEppbSBVdHRhcm8gPHV0dGFyb0BhdHQuY29tPG1haWx0bzp1dHRhcm9AYXR0LmNvbT4+LCBCcnVu byBEZWNyYWVuZSA8YnJ1bm8uZGVjcmFlbmVAb3JhbmdlLmNvbTxtYWlsdG86YnJ1bm8uZGVjcmFl bmVAb3JhbmdlLmNvbT4+LCBXaW0gSGVuZGVyaWNreCA8d2ltLmhlbmRlcmlja3hAbm9raWEuY29t PG1haWx0bzp3aW0uaGVuZGVyaWNreEBub2tpYS5jb20+PiwgImpoYWFzQHBmcmMub3JnPG1haWx0 bzpqaGFhc0BwZnJjLm9yZz4iIDxqaGFhc0BwZnJjLm9yZzxtYWlsdG86amhhYXNAcGZyYy5vcmc+ Pg0KQ2M6ICInSm9obiBHLiBTY3VkZGVyJyIgPGpnc0BqdW5pcGVyLm5ldDxtYWlsdG86amdzQGp1 bmlwZXIubmV0Pj4NClN1YmplY3Q6IFJlOiBbSWRyXSBXRyBBZG9wdGlvbiBvZiBkcmFmdC1rZXl1 cGF0ZS1pZHItYmdwLWF0dHJpYnV0ZS1hbm5vdW5jZW1lbnQgLSAyIHdlZWsgV0cgQWRvcHRpb24g Y2FsbCAoNi82IHRvIDYvMjApDQoNCkkgYW0gbm90IGF3YXJlIG9mIGFueSBJUFIgcmVsYXRlZCB0 byB0aGlzIGRvY3VtZW50Lg0KDQpSZWdhcmRzLA0KS2V5dXINCg0KRnJvbTogU3VzYW4gSGFyZXMg PHNoYXJlc0BuZHpoLmNvbTxtYWlsdG86c2hhcmVzQG5kemguY29tPj4NCkRhdGU6IFdlZG5lc2Rh eSwgSnVseSA2LCAyMDE2IGF0IDE6MjcgQU0NClRvOiAiaWRyQGlldGYub3JnPG1haWx0bzppZHJA aWV0Zi5vcmc+IiA8aWRyQGlldGYub3JnPG1haWx0bzppZHJAaWV0Zi5vcmc+PiwgS2V5dXIgUGF0 ZWwgPGtleXVwYXRlQGNpc2NvLmNvbTxtYWlsdG86a2V5dXBhdGVAY2lzY28uY29tPj4sICJ1dHRh cm9AYXR0LmNvbTxtYWlsdG86dXR0YXJvQGF0dC5jb20+IiA8dXR0YXJvQGF0dC5jb208bWFpbHRv OnV0dGFyb0BhdHQuY29tPj4sICdCcnVubyBEZWNyYWVuZScgPGJydW5vLmRlY3JhZW5lQG9yYW5n ZS5jb208bWFpbHRvOmJydW5vLmRlY3JhZW5lQG9yYW5nZS5jb20+PiwgIidIZW5kZXJpY2t4LCBX aW0gKE5va2lhIC0gQkUpJyIgPHdpbS5oZW5kZXJpY2t4QG5va2lhLmNvbTxtYWlsdG86d2ltLmhl bmRlcmlja3hAbm9raWEuY29tPj4sICJqaGFhc0BwZnJjLm9yZzxtYWlsdG86amhhYXNAcGZyYy5v cmc+IiA8amhhYXNAcGZyYy5vcmc8bWFpbHRvOmpoYWFzQHBmcmMub3JnPj4NCkNjOiAiJ0pvaG4g Ry4gU2N1ZGRlciciIDxqZ3NAanVuaXBlci5uZXQ8bWFpbHRvOmpnc0BqdW5pcGVyLm5ldD4+DQpT dWJqZWN0OiBSRTogW0lkcl0gV0cgQWRvcHRpb24gb2YgZHJhZnQta2V5dXBhdGUtaWRyLWJncC1h dHRyaWJ1dGUtYW5ub3VuY2VtZW50IC0gMiB3ZWVrIFdHIEFkb3B0aW9uIGNhbGwgKDYvNiB0byA2 LzIwKQ0KDQpUaGlzIGVuZHMgdGhlIDIgd2VlayBXRyBBZG9wdGlvbiBjYWxsIGZvciBkcmFmdC1r ZXl1cGF0ZS1pZHItYmdwLWF0dHJpYnV0ZS1hbm5vdW5jZW1lbnQuICBUaGUgV0cgaGFzIGFkb3B0 ZWQgdGhpcyBkcmFmdC4NClRoZSBDby1jaGFpcnMgZm9yZ290IHRvIGRvIGFuIElQUiBjYWxsIG9u IHRoaXMgZHJhZnQuICAgVGhlIGF1dGhvcnMgc2hvdWxkIGluZGljYXRlIHdoZXRoZXIgdGhleSBr bm93IG9mIElQUiBvbiB0aGlzIGRyYWZ0LiAgIEFmdGVyIHdlIHJlY2VpdmUgYWxsIHRoZSBJUFIg c3RhdGVtZW50cywgdGhlIGF1dGhvcnMgd2lsbCBiZSBhYmxlIHRvIHVwbG9hZCB0aGlzIGFzIGRy YWZ0LWlldGYtaWRyLWJncC1hdHRyaWJ1dGUtYW5ub3VuY2VtZW50LTAwLnR4dC4NClN1ZSBIYXJl cyBhbmQgSm9obiBTY3VkZGVyLg0K --_000_6A4039E171DE440AB5E89EEF0A0448E7alcatellucentcom_ Content-Type: text/html; charset="utf-8" Content-ID: <9F075CB85C20BD4A949A216A0AF21CAB@exchange.lucent.com> Content-Transfer-Encoding: base64 PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsgY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1zaXplOiAx NHB4OyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsiPg0KPGRpdj4NCjxkaXY+DQo8 ZGl2PkkgYW0gTm90IGF3YXJlIG9mIGFueSBJUFIgcmVsYXRlZCB0byB0aGlzIGRvYzwvZGl2Pg0K PGRpdj4NCjxkaXYgaWQ9Ik1BQ19PVVRMT09LX1NJR05BVFVSRSI+PC9kaXY+DQo8L2Rpdj4NCjwv ZGl2Pg0KPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPHNwYW4gaWQ9Ik9MS19TUkNfQk9EWV9T RUNUSU9OIj4NCjxkaXYgc3R5bGU9ImZvbnQtZmFtaWx5OkNhbGlicmk7IGZvbnQtc2l6ZToxMnB0 OyB0ZXh0LWFsaWduOmxlZnQ7IGNvbG9yOmJsYWNrOyBCT1JERVItQk9UVE9NOiBtZWRpdW0gbm9u ZTsgQk9SREVSLUxFRlQ6IG1lZGl1bSBub25lOyBQQURESU5HLUJPVFRPTTogMGluOyBQQURESU5H LUxFRlQ6IDBpbjsgUEFERElORy1SSUdIVDogMGluOyBCT1JERVItVE9QOiAjYjVjNGRmIDFwdCBz b2xpZDsgQk9SREVSLVJJR0hUOiBtZWRpdW0gbm9uZTsgUEFERElORy1UT1A6IDNwdCI+DQo8c3Bh biBzdHlsZT0iZm9udC13ZWlnaHQ6Ym9sZCI+RnJvbTogPC9zcGFuPktleXVyIFBhdGVsICZsdDs8 YSBocmVmPSJtYWlsdG86a2V5dXBhdGVAY2lzY28uY29tIj5rZXl1cGF0ZUBjaXNjby5jb208L2E+ Jmd0Ozxicj4NCjxzcGFuIHN0eWxlPSJmb250LXdlaWdodDpib2xkIj5EYXRlOiA8L3NwYW4+V2Vk bmVzZGF5IDYgSnVseSAyMDE2IGF0IDAyOjA1PGJyPg0KPHNwYW4gc3R5bGU9ImZvbnQtd2VpZ2h0 OmJvbGQiPlRvOiA8L3NwYW4+U3VzYW4gSGFyZXMgJmx0OzxhIGhyZWY9Im1haWx0bzpzaGFyZXNA bmR6aC5jb20iPnNoYXJlc0BuZHpoLmNvbTwvYT4mZ3Q7LCAmcXVvdDs8YSBocmVmPSJtYWlsdG86 aWRyQGlldGYub3JnIj5pZHJAaWV0Zi5vcmc8L2E+JnF1b3Q7ICZsdDs8YSBocmVmPSJtYWlsdG86 aWRyQGlldGYub3JnIj5pZHJAaWV0Zi5vcmc8L2E+Jmd0OywgSmltIFV0dGFybyAmbHQ7PGEgaHJl Zj0ibWFpbHRvOnV0dGFyb0BhdHQuY29tIj51dHRhcm9AYXR0LmNvbTwvYT4mZ3Q7LA0KIEJydW5v IERlY3JhZW5lICZsdDs8YSBocmVmPSJtYWlsdG86YnJ1bm8uZGVjcmFlbmVAb3JhbmdlLmNvbSI+ YnJ1bm8uZGVjcmFlbmVAb3JhbmdlLmNvbTwvYT4mZ3Q7LCBXaW0gSGVuZGVyaWNreCAmbHQ7PGEg aHJlZj0ibWFpbHRvOndpbS5oZW5kZXJpY2t4QG5va2lhLmNvbSI+d2ltLmhlbmRlcmlja3hAbm9r aWEuY29tPC9hPiZndDssICZxdW90OzxhIGhyZWY9Im1haWx0bzpqaGFhc0BwZnJjLm9yZyI+amhh YXNAcGZyYy5vcmc8L2E+JnF1b3Q7ICZsdDs8YSBocmVmPSJtYWlsdG86amhhYXNAcGZyYy5vcmci PmpoYWFzQHBmcmMub3JnPC9hPiZndDs8YnI+DQo8c3BhbiBzdHlsZT0iZm9udC13ZWlnaHQ6Ym9s ZCI+Q2M6IDwvc3Bhbj4mcXVvdDsnSm9obiBHLiBTY3VkZGVyJyZxdW90OyAmbHQ7PGEgaHJlZj0i bWFpbHRvOmpnc0BqdW5pcGVyLm5ldCI+amdzQGp1bmlwZXIubmV0PC9hPiZndDs8YnI+DQo8c3Bh biBzdHlsZT0iZm9udC13ZWlnaHQ6Ym9sZCI+U3ViamVjdDogPC9zcGFuPlJlOiBbSWRyXSBXRyBB ZG9wdGlvbiBvZiBkcmFmdC1rZXl1cGF0ZS1pZHItYmdwLWF0dHJpYnV0ZS1hbm5vdW5jZW1lbnQg LSAyIHdlZWsgV0cgQWRvcHRpb24gY2FsbCAoNi82IHRvIDYvMjApPGJyPg0KPC9kaXY+DQo8ZGl2 Pjxicj4NCjwvZGl2Pg0KPGRpdj4NCjxkaXYgc3R5bGU9IndvcmQtd3JhcDogYnJlYWstd29yZDsg LXdlYmtpdC1uYnNwLW1vZGU6IHNwYWNlOyAtd2Via2l0LWxpbmUtYnJlYWs6IGFmdGVyLXdoaXRl LXNwYWNlOyBjb2xvcjogcmdiKDAsIDAsIDApOyBmb250LXNpemU6IDE0cHg7IGZvbnQtZmFtaWx5 OiBDYWxpYnJpLCBzYW5zLXNlcmlmOyI+DQo8ZGl2PkkgYW0gbm90IGF3YXJlIG9mIGFueSBJUFIg cmVsYXRlZCB0byB0aGlzIGRvY3VtZW50LjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+ UmVnYXJkcyw8L2Rpdj4NCjxkaXY+S2V5dXI8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8c3Bh biBpZD0iT0xLX1NSQ19CT0RZX1NFQ1RJT04iPg0KPGRpdiBzdHlsZT0iZm9udC1mYW1pbHk6Q2Fs aWJyaTsgZm9udC1zaXplOjExcHQ7IHRleHQtYWxpZ246bGVmdDsgY29sb3I6YmxhY2s7IEJPUkRF Ui1CT1RUT006IG1lZGl1bSBub25lOyBCT1JERVItTEVGVDogbWVkaXVtIG5vbmU7IFBBRERJTkct Qk9UVE9NOiAwaW47IFBBRERJTkctTEVGVDogMGluOyBQQURESU5HLVJJR0hUOiAwaW47IEJPUkRF Ui1UT1A6ICNiNWM0ZGYgMXB0IHNvbGlkOyBCT1JERVItUklHSFQ6IG1lZGl1bSBub25lOyBQQURE SU5HLVRPUDogM3B0Ij4NCjxzcGFuIHN0eWxlPSJmb250LXdlaWdodDpib2xkIj5Gcm9tOiA8L3Nw YW4+U3VzYW4gSGFyZXMgJmx0OzxhIGhyZWY9Im1haWx0bzpzaGFyZXNAbmR6aC5jb20iPnNoYXJl c0BuZHpoLmNvbTwvYT4mZ3Q7PGJyPg0KPHNwYW4gc3R5bGU9ImZvbnQtd2VpZ2h0OmJvbGQiPkRh dGU6IDwvc3Bhbj5XZWRuZXNkYXksIEp1bHkgNiwgMjAxNiBhdCAxOjI3IEFNPGJyPg0KPHNwYW4g c3R5bGU9ImZvbnQtd2VpZ2h0OmJvbGQiPlRvOiA8L3NwYW4+JnF1b3Q7PGEgaHJlZj0ibWFpbHRv OmlkckBpZXRmLm9yZyI+aWRyQGlldGYub3JnPC9hPiZxdW90OyAmbHQ7PGEgaHJlZj0ibWFpbHRv OmlkckBpZXRmLm9yZyI+aWRyQGlldGYub3JnPC9hPiZndDssIEtleXVyIFBhdGVsICZsdDs8YSBo cmVmPSJtYWlsdG86a2V5dXBhdGVAY2lzY28uY29tIj5rZXl1cGF0ZUBjaXNjby5jb208L2E+Jmd0 OywgJnF1b3Q7PGEgaHJlZj0ibWFpbHRvOnV0dGFyb0BhdHQuY29tIj51dHRhcm9AYXR0LmNvbTwv YT4mcXVvdDsNCiAmbHQ7PGEgaHJlZj0ibWFpbHRvOnV0dGFyb0BhdHQuY29tIj51dHRhcm9AYXR0 LmNvbTwvYT4mZ3Q7LCAnQnJ1bm8gRGVjcmFlbmUnICZsdDs8YSBocmVmPSJtYWlsdG86YnJ1bm8u ZGVjcmFlbmVAb3JhbmdlLmNvbSI+YnJ1bm8uZGVjcmFlbmVAb3JhbmdlLmNvbTwvYT4mZ3Q7LCAm cXVvdDsnSGVuZGVyaWNreCwgV2ltIChOb2tpYSAtIEJFKScmcXVvdDsgJmx0OzxhIGhyZWY9Im1h aWx0bzp3aW0uaGVuZGVyaWNreEBub2tpYS5jb20iPndpbS5oZW5kZXJpY2t4QG5va2lhLmNvbTwv YT4mZ3Q7LCAmcXVvdDs8YSBocmVmPSJtYWlsdG86amhhYXNAcGZyYy5vcmciPmpoYWFzQHBmcmMu b3JnPC9hPiZxdW90Ow0KICZsdDs8YSBocmVmPSJtYWlsdG86amhhYXNAcGZyYy5vcmciPmpoYWFz QHBmcmMub3JnPC9hPiZndDs8YnI+DQo8c3BhbiBzdHlsZT0iZm9udC13ZWlnaHQ6Ym9sZCI+Q2M6 IDwvc3Bhbj4mcXVvdDsnSm9obiBHLiBTY3VkZGVyJyZxdW90OyAmbHQ7PGEgaHJlZj0ibWFpbHRv Ompnc0BqdW5pcGVyLm5ldCI+amdzQGp1bmlwZXIubmV0PC9hPiZndDs8YnI+DQo8c3BhbiBzdHls ZT0iZm9udC13ZWlnaHQ6Ym9sZCI+U3ViamVjdDogPC9zcGFuPlJFOiBbSWRyXSBXRyBBZG9wdGlv biBvZiBkcmFmdC1rZXl1cGF0ZS1pZHItYmdwLWF0dHJpYnV0ZS1hbm5vdW5jZW1lbnQgLSAyIHdl ZWsgV0cgQWRvcHRpb24gY2FsbCAoNi82IHRvIDYvMjApDQo8YnI+DQo8L2Rpdj4NCjxkaXY+PGJy Pg0KPC9kaXY+DQo8ZGl2IHhtbG5zOnY9InVybjpzY2hlbWFzLW1pY3Jvc29mdC1jb206dm1sIiB4 bWxuczpvPSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTpvZmZpY2UiIHhtbG5zOnc9 InVybjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOndvcmQiIHhtbG5zOm09Imh0dHA6Ly9z Y2hlbWFzLm1pY3Jvc29mdC5jb20vb2ZmaWNlLzIwMDQvMTIvb21tbCIgeG1sbnM9Imh0dHA6Ly93 d3cudzMub3JnL1RSL1JFQy1odG1sNDAiPg0KPG1ldGEgbmFtZT0iR2VuZXJhdG9yIiBjb250ZW50 PSJNaWNyb3NvZnQgV29yZCAxNCAoZmlsdGVyZWQgbWVkaXVtKSI+DQo8c3R5bGU+PCEtLQ0KLyog Rm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseToiQ2FtYnJpYSBN YXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9u dC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBT dHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05v cm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6 MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7fQ0KYTpsaW5rLCBz cGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsN Cgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxp bmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRl eHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTcNCgl7bXNvLXN0eWxl LXR5cGU6cGVyc29uYWwtY29tcG9zZTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2Vy aWYiOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5 cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjt9DQpA cGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEuMGluIDEu MGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7 fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMg djpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lm IGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFw IHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlm XS0tPg0KPGRpdiBsYW5nPSJFTi1VUyIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2 IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1t YXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBzdHls ZT0iY29sb3I6YmxhY2siPlRoaXMgZW5kcyB0aGUgMiB3ZWVrIFdHIEFkb3B0aW9uIGNhbGwgZm9y IGRyYWZ0LWtleXVwYXRlLWlkci1iZ3AtYXR0cmlidXRlLWFubm91bmNlbWVudC4mbmJzcDsgVGhl IFdHIGhhcyBhZG9wdGVkIHRoaXMgZHJhZnQuJm5ic3A7DQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+ DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNv LW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+VGhlIENv LWNoYWlycyBmb3Jnb3QgdG8gZG8gYW4gSVBSIGNhbGwgb24gdGhpcyBkcmFmdC4gJm5ic3A7Jm5i c3A7VGhlIGF1dGhvcnMgc2hvdWxkIGluZGljYXRlIHdoZXRoZXIgdGhleSBrbm93IG9mIElQUiBv biB0aGlzIGRyYWZ0LiAmbmJzcDsmbmJzcDtBZnRlciB3ZSByZWNlaXZlIGFsbCB0aGUNCiBJUFIg c3RhdGVtZW50cywgdGhlIGF1dGhvcnMgd2lsbCBiZSBhYmxlIHRvIHVwbG9hZCB0aGlzIGFzIGRy YWZ0LWlldGYtaWRyLWJncC1hdHRyaWJ1dGUtYW5ub3VuY2VtZW50LTAwLnR4dC4mbmJzcDsNCjxv OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFy Z2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9 ImNvbG9yOmJsYWNrIj5TdWUgSGFyZXMgYW5kIEpvaG4gU2N1ZGRlci4NCjxvOnA+PC9vOnA+PC9z cGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvc3Bhbj48L2Rpdj4NCjwvZGl2Pg0K PC9zcGFuPg0KPC9ib2R5Pg0KPC9odG1sPg0K --_000_6A4039E171DE440AB5E89EEF0A0448E7alcatellucentcom_-- From nobody Wed Jul 6 00:17:41 2016 Return-Path: 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 7F1A812D692 for ; Wed, 6 Jul 2016 00:17:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.344 X-Spam-Level: X-Spam-Status: No, score=-3.344 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 5p97gxdqFAbq for ; Wed, 6 Jul 2016 00:17:36 -0700 (PDT) Received: from relais-inet.orange.com (relais-nor36.orange.com [80.12.70.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29FB512D68A for ; Wed, 6 Jul 2016 00:17:36 -0700 (PDT) Received: from opfednr05.francetelecom.fr (unknown [xx.xx.xx.69]) by opfednr24.francetelecom.fr (ESMTP service) with ESMTP id 8EB65401DD; Wed, 6 Jul 2016 09:17:34 +0200 (CEST) Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.31]) by opfednr05.francetelecom.fr (ESMTP service) with ESMTP id 58B8D2010F; Wed, 6 Jul 2016 09:17:34 +0200 (CEST) Received: from OPEXCLILM21.corporate.adroot.infra.ftgroup ([fe80::e92a:c932:907e:8f06]) by OPEXCLILM22.corporate.adroot.infra.ftgroup ([fe80::8c90:f4e9:be28:2a1%19]) with mapi id 14.03.0294.000; Wed, 6 Jul 2016 09:17:34 +0200 From: To: Susan Hares , "'John G. Scudder'" Thread-Topic: [Idr] WG Adoption of draft-keyupate-idr-bgp-attribute-announcement - 2 week WG Adoption call (6/6 to 6/20) Thread-Index: AdHXFCd9QgWs5X1ZTnmBFEDm50qIHgAQi4hw Date: Wed, 6 Jul 2016 07:17:33 +0000 Message-ID: <12045_1467789454_577CB08E_12045_1818_1_53C29892C857584299CBF5D05346208A0F92D34C@OPEXCLILM21.corporate.adroot.infra.ftgroup> References: <068e01d1d714$c3002760$49007620$@ndzh.com> In-Reply-To: <068e01d1d714$c3002760$49007620$@ndzh.com> Accept-Language: fr-FR, en-US Content-Language: fr-FR X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.168.234.3] Content-Type: multipart/alternative; boundary="_000_53C29892C857584299CBF5D05346208A0F92D34COPEXCLILM21corp_" MIME-Version: 1.0 Archived-At: Cc: "'Keyur Patel \(keyupate\)'" , "idr@ietf.org" Subject: Re: [Idr] WG Adoption of draft-keyupate-idr-bgp-attribute-announcement - 2 week WG Adoption call (6/6 to 6/20) X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jul 2016 07:17:38 -0000 --_000_53C29892C857584299CBF5D05346208A0F92D34COPEXCLILM21corp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Sue, John, I'm not aware of IPR related to this draft. Regards, -- Bruno From: Susan Hares [mailto:shares@ndzh.com] Sent: Wednesday, July 06, 2016 1:27 AM To: idr@ietf.org; 'Keyur Patel (keyupate)'; uttaro@att.com; DECRAENE Bruno = IMT/OLN; 'Henderickx, Wim (Nokia - BE)'; jhaas@pfrc.org Cc: 'John G. Scudder' Subject: RE: [Idr] WG Adoption of draft-keyupate-idr-bgp-attribute-announce= ment - 2 week WG Adoption call (6/6 to 6/20) This ends the 2 week WG Adoption call for draft-keyupate-idr-bgp-attribute-= announcement. The WG has adopted this draft. The Co-chairs forgot to do an IPR call on this draft. The authors should = indicate whether they know of IPR on this draft. After we receive all the= IPR statements, the authors will be able to upload this as draft-ietf-idr-= bgp-attribute-announcement-00.txt. Sue Hares and John Scudder. ___________________________________________________________________________= ______________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confiden= tielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu= ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el= ectroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou = falsifie. Merci. This message and its attachments may contain confidential or privileged inf= ormation that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and dele= te this message and its attachments. As emails may be altered, Orange is not liable for messages that have been = modified, changed or falsified. Thank you. --_000_53C29892C857584299CBF5D05346208A0F92D34COPEXCLILM21corp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi Sue,= John,

&n= bsp;

I’= ;m not aware of IPR related to this draft.

&n= bsp;

Regards= ,

-- Brun= o

&n= bsp;

From: Susan Ha= res [mailto:shares@ndzh.com]
Sent: Wednesday, July 06, 2016 1:27 AM
To: idr@ietf.org; 'Keyur Patel (keyupate)'; uttaro@att.com; DECRAENE= Bruno IMT/OLN; 'Henderickx, Wim (Nokia - BE)'; jhaas@pfrc.org
Cc: 'John G. Scudder'
Subject: RE: [Idr] WG Adoption of draft-keyupate-idr-bgp-attribute-a= nnouncement - 2 week WG Adoption call (6/6 to 6/20)

 

This ends the 2 week WG= Adoption call for draft-keyupate-idr-bgp-attribute-announcement.  The= WG has adopted this draft. 

The Co-chairs forgot to= do an IPR call on this draft.   The authors should indicate whet= her they know of IPR on this draft.   After we receive all the IPR statements, the authors will be able to upload this as draft-i= etf-idr-bgp-attribute-announcement-00.txt. 

Sue Hares and John Scud= der.

______________________________________________________________________=
___________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.
--_000_53C29892C857584299CBF5D05346208A0F92D34COPEXCLILM21corp_-- From nobody Wed Jul 6 00:35:10 2016 Return-Path: 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 B348412D6AE for ; Wed, 6 Jul 2016 00:34:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.4 X-Spam-Level: X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.198, 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 X_YsxXcllR1Q for ; Wed, 6 Jul 2016 00:34:57 -0700 (PDT) Received: from mail-lf0-x229.google.com (mail-lf0-x229.google.com [IPv6:2a00:1450:4010:c07::229]) (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 0175A12D6A1 for ; Wed, 6 Jul 2016 00:34:56 -0700 (PDT) Received: by mail-lf0-x229.google.com with SMTP id f6so149074429lfg.0 for ; Wed, 06 Jul 2016 00:34:56 -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=aGNT42wL8LNBYDUF1abStR/WnTLa6MBlKsDAnHFGCT8=; b=RPR/P6XLP68qR39sQawm84EOcdwxtvWEc43uOPvtdAyJI//XDrBri4suE/OOGFUTEL KYLjY3nEw8IHbJpMMjYZWkZky4i2YJw2mXvUj9R+qh8llUcQxs+Dd4ogqxKfHvIZ2Hcl umNugQrtcz4osWtN0JBWlWs3XC+h0D+35VXzJkKH7dTsqbC21rRlSXLsMZSxeFF3Aij1 eeu1aTnCAIBVusT6Imq5f4LVpjDQJ7rzwitMzPga5oXlAv9ijYZ8UQg97DhzZM2s1LDH kS6mz+jqZreKpPKgr/WJiSeGCJoF1XR1NBZcIZg6VPlU1goJOLOyhpSX83fZu9oT5Yxm jOQA== 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=aGNT42wL8LNBYDUF1abStR/WnTLa6MBlKsDAnHFGCT8=; b=lnc7y/i6KGnVpjKR3wEACnWRvGYK3cEVqqe5wuDSFjKJAka6cjDdff9cV3GR73hBRV NY06repvp+BCvm3zmfL2Dubw7yYCfdMOTZ4L8pS0jjLGo9ktfMFgj6HC7SIyPoyYPRoD /l1XuFAgOgqGaGTtDqjMX5c0xYgovlpNPTRC2IPbdg+qvN+W+YTo+bht+4YNzHuwYFoN Bkg1dujB+Zh657qURdHaADqxdC8MEkhMKWPtfToWrZ9HC0WQ/5QLe0gtXUzB8wQ/fhPp 5kTi6x0khY4TzyDYUxzm2dfffvT0AsNtAwukzWxbbVRP5V959eWOknxASRScL0BewtmQ T+dA== X-Gm-Message-State: ALyK8tJiIA+IWm6LVEDOD2Nwjc7zMgWoCUe1LLyl9fmtctm5/nZ8qmqjbvAsgi/t0LFFVuJKSwV1S4MhODpqcQ== X-Received: by 10.25.18.35 with SMTP id h35mr4494316lfi.82.1467790494888; Wed, 06 Jul 2016 00:34:54 -0700 (PDT) MIME-Version: 1.0 Sender: rraszuk@gmail.com Received: by 10.25.21.30 with HTTP; Wed, 6 Jul 2016 00:34:54 -0700 (PDT) In-Reply-To: References: From: Robert Raszuk Date: Wed, 6 Jul 2016 09:34:54 +0200 X-Google-Sender-Auth: rKutAckwRy2Risr48d3wYqYOL7o Message-ID: To: amit bhagat Content-Type: multipart/alternative; boundary=001a113fbed20d775e0536f29b78 Archived-At: Cc: idr wg Subject: Re: [Idr] Review Request for draft BGP Overload X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jul 2016 07:35:00 -0000 --001a113fbed20d775e0536f29b78 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Amit, I agree that recently BGP is being stretched towards DC-fabric side to > encompass various use cases. > > However, the way I see this draft, it can be useful for both, Internet an= d > DC-fabrics. The main reason is to keep traffic drain procedure BGP topolo= gy > agnostic, exactly same as ISIS Overload-bit. Agree, BGP has a bigger blas= t > radius in Internet compared to ISIS but appropriate implementation of the > feature can provide good benefits. > =E2=80=8BI don't think =E2=80=8Bthis is about "blast radius". ISIS or OSPF = are link state protocols and each node in the given flooding scope computes its independent SPF hence flooding such information is a necessity for consistent forwarding. Contrary to the above BGP is path/distance-vector where each BGP speaker recomputes its bRIB and re-advertises it. Therefor for the use case you have in mind all what is required is to signal in some way to a bgp peer(s) that you may not want or want again to be in forwarding for a given SAFI. You defined a new SAFI as well as new NLRI format to use for point to point signalling .. I am not convinced this is the right level of signalling choice for this purpose. How do you stop propagation of such NLRIs around ? It would be pretty harmful if one router in Clos fabric will leak it and it breaks entire fabric - wouldn't you agree ? You at very min MUST enforce the NO-EXPORT/NO-ADVERTISE semantics for such SAFI which currently your draft seems to be missing. There are couple of alternatives to accomplish the same though: - using flag in dynamic capabilities - local poisoning of next hops - use of local pref/med (same as OSPF max metric:) - use of G-shut community or simply shutting the SAFIs. When you shut SAFI in one shot all paths learned are removed and best path (or multipath) recomputed. The potential "hit" would be on re-enabling it such that you need readvertise your underlay again. It is gracefull (no packet drops) as local forwarding can continue till everyone around stops sending you packets in a given table_id (corresponding to SAFI which has been shut down). Many thx, R. --001a113fbed20d775e0536f29b78 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Amit,

I agree that recently BGP is = being stretched towards DC-fabric side to encompass various use cases.
<= br>
However, the way I see this draft, it can be useful for both, Inte= rnet and DC-fabrics. The main reason is to keep traffic drain procedure BGP= topology agnostic, exactly same as ISIS Overload-bit. Agree, BGP has a big= ger blast radius in Internet compared to ISIS but appropriate implementatio= n of the feature can provide good benefits.


=E2= =80=8BI don't think =E2=80=8Bthis is about "blast radius". IS= IS or OSPF are link state protocols and each node in the given flooding sco= pe computes its independent SPF hence flooding such information is a necess= ity for consistent forwarding.=C2=A0

Contrary to the above BGP is path/distance-vector where each= BGP speaker recomputes its bRIB and re-advertises it. Therefor for the use= case you have in mind all what is required is to signal in some way to a b= gp peer(s) that you may not want or want again to be in forwarding for a gi= ven SAFI.=C2=A0

You de= fined a new SAFI as well as new NLRI format to use for point to point signa= lling .. I am not convinced this is the right level of signalling choice fo= r this purpose. How do you stop propagation of such NLRIs around ? It would= be pretty harmful if one router in Clos fabric will leak it and it breaks = entire fabric - wouldn't you agree ? You at very min MUST enforce the N= O-EXPORT/NO-ADVERTISE semantics for such SAFI which currently your draft se= ems to be missing.=C2=A0

There are couple of alternatives to accomplish the same though:=C2=A0

- using flag in dynamic = capabilities=C2=A0
- local poisoning of next hops= =C2=A0
- use of local pref/med (same as OSPF max me= tric:)
- use of G-shut community=C2=A0
=C2=A0
or simply shutting the SAFIs. Wh= en you shut SAFI in one shot all paths learned are removed and best path (o= r multipath) recomputed. The potential "hit" would be on re-enabl= ing it such that you need readvertise your underlay again.=C2=A0

It is gracefull (no packet drops= ) as local forwarding can continue till everyone around stops sending you p= ackets in a given table_id (corresponding to SAFI which has been shut down)= .=C2=A0

Many thx,
R= .

--001a113fbed20d775e0536f29b78-- From nobody Wed Jul 6 00:48:21 2016 Return-Path: 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 866F512D731 for ; Wed, 6 Jul 2016 00:48:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.739 X-Spam-Level: * X-Spam-Status: No, score=1.739 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, RDNS_NONE=0.793] autolearn=no 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 dlv5OFniYbhI for ; Wed, 6 Jul 2016 00:48:17 -0700 (PDT) Received: from hickoryhill-consulting.com (unknown [50.245.122.97]) (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 48BA612D6B3 for ; Wed, 6 Jul 2016 00:48:17 -0700 (PDT) X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=184.157.81.45; From: "Susan Hares" To: , "'John G. Scudder'" References: <068e01d1d714$c3002760$49007620$@ndzh.com> <12045_1467789454_577CB08E_12045_1818_1_53C29892C857584299CBF5D05346208A0F92D34C@OPEXCLILM21.corporate.adroot.infra.ftgroup> In-Reply-To: <12045_1467789454_577CB08E_12045_1818_1_53C29892C857584299CBF5D05346208A0F92D34C@OPEXCLILM21.corporate.adroot.infra.ftgroup> Date: Wed, 6 Jul 2016 03:47:36 -0400 Message-ID: <046301d1d75a$a9dbae30$fd930a90$@ndzh.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0464_01D1D739.22CC7F30" X-Mailer: Microsoft Outlook 14.0 Content-Language: en-us Thread-Index: AQHKadK0KmVQ1y9U9ekYqI9scaqLPQJGaXzzoAetQcA= X-Authenticated-User: skh@ndzh.com Archived-At: Cc: "'Keyur Patel \(keyupate\)'" , idr@ietf.org Subject: Re: [Idr] WG Adoption of draft-keyupate-idr-bgp-attribute-announcement - 2 week WG Adoption call (6/6 to 6/20) X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jul 2016 07:48:19 -0000 This is a multipart message in MIME format. ------=_NextPart_000_0464_01D1D739.22CC7F30 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Bruno, Keyur, and Wim: Thank you for your IPR Statements. We simply need the Jim Uttaro and Jeff Haas to respond to this email. Sue From: bruno.decraene@orange.com [mailto:bruno.decraene@orange.com] Sent: Wednesday, July 6, 2016 3:18 AM To: Susan Hares; 'John G. Scudder' Cc: idr@ietf.org; 'Keyur Patel (keyupate)'; uttaro@att.com; 'Henderickx, Wim (Nokia - BE)'; jhaas@pfrc.org Subject: RE: [Idr] WG Adoption of draft-keyupate-idr-bgp-attribute-announcement - 2 week WG Adoption call (6/6 to 6/20) Hi Sue, John, I'm not aware of IPR related to this draft. Regards, -- Bruno From: Susan Hares [mailto:shares@ndzh.com] Sent: Wednesday, July 06, 2016 1:27 AM To: idr@ietf.org; 'Keyur Patel (keyupate)'; uttaro@att.com; DECRAENE Bruno IMT/OLN; 'Henderickx, Wim (Nokia - BE)'; jhaas@pfrc.org Cc: 'John G. Scudder' Subject: RE: [Idr] WG Adoption of draft-keyupate-idr-bgp-attribute-announcement - 2 week WG Adoption call (6/6 to 6/20) This ends the 2 week WG Adoption call for draft-keyupate-idr-bgp-attribute-announcement. The WG has adopted this draft. The Co-chairs forgot to do an IPR call on this draft. The authors should indicate whether they know of IPR on this draft. After we receive all the IPR statements, the authors will be able to upload this as draft-ietf-idr-bgp-attribute-announcement-00.txt. Sue Hares and John Scudder. ____________________________________________________________________________ _____________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. ------=_NextPart_000_0464_01D1D739.22CC7F30 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Bruno, Keyur, and Wim:

 

Thank you for your IPR = Statements.  We simply need the Jim Uttaro and Jeff Haas to respond = to this email.

 

Sue =

 

From:= = bruno.decraene@orange.com [mailto:bruno.decraene@orange.com] =
Sent: Wednesday, July 6, 2016 3:18 AM
To: Susan = Hares; 'John G. Scudder'
Cc: idr@ietf.org; 'Keyur Patel = (keyupate)'; uttaro@att.com; 'Henderickx, Wim (Nokia - BE)'; = jhaas@pfrc.org
Subject: RE: [Idr] WG Adoption of = draft-keyupate-idr-bgp-attribute-announcement - 2 week WG Adoption call = (6/6 to 6/20)

 

Hi Sue, John,

 

I’m not aware of = IPR related to this draft.

 

Regards,

-- = Bruno

 

From:= Susan = Hares [mailto:shares@ndzh.com] =
Sent: Wednesday, July 06, 2016 1:27 AM
To: idr@ietf.org; 'Keyur Patel (keyupate)'; = uttaro@att.com; DECRAENE Bruno = IMT/OLN; 'Henderickx, Wim (Nokia - BE)'; jhaas@pfrc.org
Cc: 'John G. = Scudder'
Subject: RE: [Idr] WG Adoption of = draft-keyupate-idr-bgp-attribute-announcement - 2 week WG Adoption call = (6/6 to 6/20)

 

This ends the 2 week WG Adoption call for = draft-keyupate-idr-bgp-attribute-announcement.  The WG has adopted = this draft. 

The Co-chairs forgot to do an IPR call on this = draft.   The authors should indicate whether they know of IPR = on this draft.   After we receive all the IPR statements, the = authors will be able to upload this as = draft-ietf-idr-bgp-attribute-announcement-00.txt.  =

Sue Hares and John Scudder. =

_______________________________________________________________=
__________________________________________________________
 
Ce message et ses pieces jointes peuvent contenir des =
informations confidentielles ou privilegiees et ne doivent =
donc
pas etre diffuses, =
exploites ou copies sans autorisation. Si vous avez recu ce message par =
erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. =
Les messages electroniques etant susceptibles =
d'alteration,
Orange decline =
toute responsabilite si ce message a ete altere, deforme ou falsifie. =
Merci.
 
This =
message and its attachments may contain confidential or privileged =
information that may be protected by =
law;
they should not be =
distributed, used or copied without =
authorisation.
If you have =
received this email in error, please notify the sender and delete this =
message and its attachments.
As emails may be altered, Orange is not liable for messages =
that have been modified, changed or =
falsified.
Thank =
you.
------=_NextPart_000_0464_01D1D739.22CC7F30-- From nobody Wed Jul 6 06:00:28 2016 Return-Path: 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 B551A12D5AB for ; Wed, 6 Jul 2016 06:00:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -15.947 X-Spam-Level: X-Spam-Status: No, score=-15.947 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 0MGwsZQ1DAmP for ; Wed, 6 Jul 2016 06:00:26 -0700 (PDT) Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C663612D1A5 for ; Wed, 6 Jul 2016 06:00:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1693; q=dns/txt; s=iport; t=1467810025; x=1469019625; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=20QyMzDJGnk4dvzTLmYqMajb9qG/ImflQ/2xA/oZ74Y=; b=B2rKQOib+HftI6YDKHYdVqcbHmE4nOrYh0Y3Fu06dDm06pUYn1EJ1ZaP 7HrnkuN46BrJBuBZFCReKN2S6DxJrce++xtG05XVD7wAfGqIGt8JpNvMP mI7PZJbz6aAnOcTsVzZqm7D2yiT1og3V621xADNm1S1tvMwJB4v1JxNWo U=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AOAgBpAH1X/49dJa1dgz5WfAa5K4F3J?= =?us-ascii?q?IV0AoEpOBQBAQEBAQEBZSeETAEBBAE6PQcLAgEIGB4QMiUCBBOIKAgOvBcBAQE?= =?us-ascii?q?BAQEBAQEBAQEBAQEBAQEBAQEchieBeIJVhECDLIIvBY4Eiw8BhgiCeoVEgWpOh?= =?us-ascii?q?AiIapAJAR42gjuBNW4Bh3J/AQEB?= X-IronPort-AV: E=Sophos;i="5.28,318,1464652800"; d="scan'208";a="292766864" Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Jul 2016 13:00:04 +0000 Received: from XCH-RTP-009.cisco.com (xch-rtp-009.cisco.com [64.101.220.149]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id u66D02Bd015259 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for ; Wed, 6 Jul 2016 13:00:04 GMT Received: from xch-rtp-010.cisco.com (64.101.220.150) by XCH-RTP-009.cisco.com (64.101.220.149) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 6 Jul 2016 09:00:01 -0400 Received: from xch-rtp-010.cisco.com ([64.101.220.150]) by XCH-RTP-010.cisco.com ([64.101.220.150]) with mapi id 15.00.1210.000; Wed, 6 Jul 2016 09:00:02 -0400 From: "Stefano Previdi (sprevidi)" To: idr wg Thread-Topic: New Version Notification for draft-gredler-idr-bgp-ls-segment-routing-ext-03.txt Thread-Index: AQHR14X9SjHTejFfy0qhglpkXuxvTKALoJyA Date: Wed, 6 Jul 2016 13:00:02 +0000 Message-ID: <765F2F5B-CF4B-442D-AA87-3364E2E1856B@cisco.com> References: <20160706125729.7910.33892.idtracker@ietfa.amsl.com> In-Reply-To: <20160706125729.7910.33892.idtracker@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.61.175.206] Content-Type: text/plain; charset="us-ascii" Content-ID: <2DB977A7CAA23D459B4A16045F599363@emea.cisco.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Subject: Re: [Idr] New Version Notification for draft-gredler-idr-bgp-ls-segment-routing-ext-03.txt X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jul 2016 13:00:28 -0000 Added extensions for prefix attributes as defined in RFC7794. Also, the authors believe this draft is ready for WG item adoption consider= ation. s. > On Jul 6, 2016, at 2:57 PM, internet-drafts@ietf.org wrote: >=20 >=20 > A new version of I-D, draft-gredler-idr-bgp-ls-segment-routing-ext-03.txt > has been successfully submitted by Stefano Previdi and posted to the > IETF repository. >=20 > Name: draft-gredler-idr-bgp-ls-segment-routing-ext > Revision: 03 > Title: BGP Link-State extensions for Segment Routing > Document date: 2016-07-06 > Group: Individual Submission > Pages: 33 > URL: https://www.ietf.org/internet-drafts/draft-gredler-idr-bg= p-ls-segment-routing-ext-03.txt > Status: https://datatracker.ietf.org/doc/draft-gredler-idr-bgp-ls= -segment-routing-ext/ > Htmlized: https://tools.ietf.org/html/draft-gredler-idr-bgp-ls-segm= ent-routing-ext-03 > Diff: https://www.ietf.org/rfcdiff?url2=3Ddraft-gredler-idr-bgp= -ls-segment-routing-ext-03 >=20 > Abstract: > Segment Routing (SR) allows for a flexible definition of end-to-end > paths within IGP topologies by encoding paths as sequences of > topological sub-paths, called "segments". These segments are > advertised by the link-state routing protocols (IS-IS, OSPF and > OSPFv3). >=20 > This draft defines extensions to the BGP Link-state address-family in > order to carry segment information via BGP. >=20 >=20 >=20 >=20 >=20 > Please note that it may take a couple of minutes from the time of submiss= ion > until the htmlized version and diff are available at tools.ietf.org. >=20 > The IETF Secretariat >=20 From nobody Wed Jul 6 08:38:30 2016 Return-Path: X-Original-To: idr@ietf.org Delivered-To: idr@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1152A12D5B7; Wed, 6 Jul 2016 08:38:29 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.25.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20160706153829.26748.93309.idtracker@ietfa.amsl.com> Date: Wed, 06 Jul 2016 08:38:29 -0700 Archived-At: Cc: idr@ietf.org Subject: [Idr] I-D Action: draft-ietf-idr-te-lsp-distribution-05.txt X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jul 2016 15:38:29 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Inter-Domain Routing of the IETF. Title : Distribution of Traffic Engineering (TE) Policies and State using BGP-LS Authors : Stefano Previdi Jie Dong Mach(Guoyi) Chen Hannes Gredler Jeff Tantsura Filename : draft-ietf-idr-te-lsp-distribution-05.txt Pages : 26 Date : 2016-07-06 Abstract: This document describes a mechanism to collect the Traffic Engineering and Policy information that is locally available in a router and advertise it into BGP-LS updates. Such information can be used by external components for path computation, re-optimization, service placement, network visualization, etc. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-idr-te-lsp-distribution/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-idr-te-lsp-distribution-05 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-te-lsp-distribution-05 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Wed Jul 6 08:41:00 2016 Return-Path: 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 4136112D61B for ; Wed, 6 Jul 2016 08:40:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -15.927 X-Spam-Level: X-Spam-Status: No, score=-15.927 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 crajCg4JenjB for ; Wed, 6 Jul 2016 08:40:55 -0700 (PDT) Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B8FF12D61A for ; Wed, 6 Jul 2016 08:40:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1549; q=dns/txt; s=iport; t=1467819622; x=1469029222; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=ghTEovkauoLrwQOgmIeVK3/Sx/eX/0T+uLxCTf2MM4I=; b=X9fjse/6ubL+iKeWvh7+bzal4XThsdFeY3Pb3MQzNKOtD1xMqu0HErz0 kwMfACSTwWUTxqOtxAl2DthRQwWi4PjLgujnKVuc22qGV54pGgf1GfKbo RWK7mo+Ff8zCT3VDuKnOg5q79O+KVKLscWdks3JHGndfFErFeqW6qsUQg Q=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ABAgAnJn1X/49dJa1dgz5WfAa5EYF3J?= =?us-ascii?q?IV0AoEqOBQBAQEBAQEBZSeETAEBBAE6PQcLAgEIGB4QMiUCBBOIKAgOvCoBAQE?= =?us-ascii?q?BAQEBAQEBAQEBAQEBAQEBAQEchieBeAiCTYRAgyyCLwWOBIsPAYYIiD4KgWBOh?= =?us-ascii?q?AiIapAJAR42g3BuAYdyfwEBAQ?= X-IronPort-AV: E=Sophos;i="5.28,319,1464652800"; d="scan'208";a="125686838" Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Jul 2016 15:40:21 +0000 Received: from XCH-RTP-006.cisco.com (xch-rtp-006.cisco.com [64.101.220.146]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id u66FeLJD004748 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for ; Wed, 6 Jul 2016 15:40:21 GMT Received: from xch-rtp-010.cisco.com (64.101.220.150) by XCH-RTP-006.cisco.com (64.101.220.146) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 6 Jul 2016 11:40:20 -0400 Received: from xch-rtp-010.cisco.com ([64.101.220.150]) by XCH-RTP-010.cisco.com ([64.101.220.150]) with mapi id 15.00.1210.000; Wed, 6 Jul 2016 11:40:20 -0400 From: "Stefano Previdi (sprevidi)" To: idr wg Thread-Topic: New Version Notification for draft-ietf-idr-te-lsp-distribution-05.txt Thread-Index: AQHR15x6aFnBeN0w0ke+xSYil4t7VqALzToA Date: Wed, 6 Jul 2016 15:40:20 +0000 Message-ID: References: <20160706153829.26748.10794.idtracker@ietfa.amsl.com> In-Reply-To: <20160706153829.26748.10794.idtracker@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.61.175.206] Content-Type: text/plain; charset="us-ascii" Content-ID: <32157DCF616C2F4CBBF6665C5C0F3AF3@emea.cisco.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Subject: Re: [Idr] New Version Notification for draft-ietf-idr-te-lsp-distribution-05.txt X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jul 2016 15:40:59 -0000 Hi, added support of SR TE Policies (as defined in draft-previdi-idr-segment-ro= uting-te-policy) and local cross connect state. Thanks. s. > On Jul 6, 2016, at 5:38 PM, internet-drafts@ietf.org wrote: >=20 >=20 > A new version of I-D, draft-ietf-idr-te-lsp-distribution-05.txt > has been successfully submitted by Stefano Previdi and posted to the > IETF repository. >=20 > Name: draft-ietf-idr-te-lsp-distribution > Revision: 05 > Title: Distribution of Traffic Engineering (TE) Policies and State using= BGP-LS > Document date: 2016-07-06 > Group: idr > Pages: 26 > URL: https://www.ietf.org/internet-drafts/draft-ietf-idr-te-ls= p-distribution-05.txt > Status: https://datatracker.ietf.org/doc/draft-ietf-idr-te-lsp-di= stribution/ > Htmlized: https://tools.ietf.org/html/draft-ietf-idr-te-lsp-distrib= ution-05 > Diff: https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-idr-te-lsp= -distribution-05 >=20 > Abstract: > This document describes a mechanism to collect the Traffic > Engineering and Policy information that is locally available in a > router and advertise it into BGP-LS updates. Such information can be > used by external components for path computation, re-optimization, > service placement, network visualization, etc. >=20 >=20 >=20 >=20 >=20 > Please note that it may take a couple of minutes from the time of submiss= ion > until the htmlized version and diff are available at tools.ietf.org. >=20 > The IETF Secretariat >=20 From nobody Wed Jul 6 10:34:23 2016 Return-Path: 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 3420B12D1B7 for ; Wed, 6 Jul 2016 10:34:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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 BTkKhwQoRCQQ for ; Wed, 6 Jul 2016 10:34:19 -0700 (PDT) Received: from mail-qk0-x236.google.com (mail-qk0-x236.google.com [IPv6:2607:f8b0:400d:c09::236]) (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 5770012D0AA for ; Wed, 6 Jul 2016 10:34:19 -0700 (PDT) Received: by mail-qk0-x236.google.com with SMTP id e3so119540731qkd.0 for ; Wed, 06 Jul 2016 10:34:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=zkZdktzpVHU1irEwYEYLDM4Lt0R+u2zismm3etT59qk=; b=gmUsKsM6QdFgY8fZG+DzoWgGWy5W9RsR6uhuwDxT0w1VY04l2y7Zaw8rxFjQz9ZVTn UBGMVv7gTA+kHZZwXPJVwISyFA4jSBmNtvaA3Cv50UwPWwgUi8Da8WfheJHEJrjn8Xyj YiCXAogr2WhJu816RtM93iC+OaWZOiJCOblBL9rFf25rvHneCmOgj+EorgFeLXTnp36E d+ydSBDfM08HzBGIL8ozySRHgxR36Kq50BRDqR1FzulEC5yKzpzIQ2tuVPZv5qdDKUe3 ugjexiJJt45t7Fr2jeAlSfCdMnlNYjlNo8IMhRPwjeKZmI47Vmq1PiUysT+efCfuWElH l+7w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=zkZdktzpVHU1irEwYEYLDM4Lt0R+u2zismm3etT59qk=; b=EoUF1F5Y7XqdH6C1Zuy3WeTEZL5vDnsA6M8waNadeH+vs7oZUVvWO2XBOqI7NTe5+m 04Y6/ggFveaZc0NrRHog7uNd8651Nh5YdvzFse0UJAydoXeGh0zG1dZR6QsMCgfdywXy 5Y8u/8ZOOgJKqHhggWHNehnoUeyVr6WcslcI6cIgTf+BRIqevRdumgyD7jvEFFOOGRTn U2sYaHfRY22TtwCHfC56CC8ag3OpRNF3RvKgMF1eWJkboXdpy9Cg4jErXorh9bCozBvM M+WTf0LuQP4T2GM31KnvrpswIuRk82v8C8/C4l6u6hoshG/gZ9qM5BUVa2a00KOV298a rVrg== X-Gm-Message-State: ALyK8tJBQ8HUR967xTDdOJxzoiA873YI6B3Tr6qKne2gglUinQ3Q03qhN/1YjynL0DbtYgGQZ/yIcgf4HxmObQ== X-Received: by 10.55.160.211 with SMTP id j202mr30956849qke.108.1467826458562; Wed, 06 Jul 2016 10:34:18 -0700 (PDT) MIME-Version: 1.0 Received: by 10.55.43.232 with HTTP; Wed, 6 Jul 2016 10:34:17 -0700 (PDT) In-Reply-To: References: From: amit bhagat Date: Wed, 6 Jul 2016 10:34:17 -0700 Message-ID: To: Robert Raszuk Content-Type: multipart/alternative; boundary=001a114fadeca796eb0536fafadc Archived-At: Cc: idr wg Subject: Re: [Idr] Review Request for draft BGP Overload X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jul 2016 17:34:21 -0000 --001a114fadeca796eb0536fafadc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Robert, There is no risk of leaking as the Capability will be exchanged with peers upon session establishment. What this feature also gives is monitoring Established neighbor-count. Consider a router connected to 10 peers and all 10 peers advertise exactly same prefixes in a CLOS fabric. Now, if 5 peer sessions go down, the capacity is effectively reduced to 50% while this router is still in the transit. This can cause congestion. Instead, the router can declare itself overloaded and the downstream routers then rely on other paths. The update advertisement delay can be an implementation detail. Thanks. Amit On Wed, Jul 6, 2016 at 12:34 AM, Robert Raszuk wrote: > Hi Amit, > > I agree that recently BGP is being stretched towards DC-fabric side to >> encompass various use cases. >> >> However, the way I see this draft, it can be useful for both, Internet >> and DC-fabrics. The main reason is to keep traffic drain procedure BGP >> topology agnostic, exactly same as ISIS Overload-bit. Agree, BGP has a >> bigger blast radius in Internet compared to ISIS but appropriate >> implementation of the feature can provide good benefits. >> > > > =E2=80=8BI don't think =E2=80=8Bthis is about "blast radius". ISIS or OSP= F are link state > protocols and each node in the given flooding scope computes its > independent SPF hence flooding such information is a necessity for > consistent forwarding. > > Contrary to the above BGP is path/distance-vector where each BGP speaker > recomputes its bRIB and re-advertises it. Therefor for the use case you > have in mind all what is required is to signal in some way to a bgp peer(= s) > that you may not want or want again to be in forwarding for a given SAFI. > > You defined a new SAFI as well as new NLRI format to use for point to > point signalling .. I am not convinced this is the right level of > signalling choice for this purpose. How do you stop propagation of such > NLRIs around ? It would be pretty harmful if one router in Clos fabric wi= ll > leak it and it breaks entire fabric - wouldn't you agree ? You at very mi= n > MUST enforce the NO-EXPORT/NO-ADVERTISE semantics for such SAFI which > currently your draft seems to be missing. > > There are couple of alternatives to accomplish the same though: > > - using flag in dynamic capabilities > - local poisoning of next hops > - use of local pref/med (same as OSPF max metric:) > - use of G-shut community > > or simply shutting the SAFIs. When you shut SAFI in one shot all paths > learned are removed and best path (or multipath) recomputed. The potentia= l > "hit" would be on re-enabling it such that you need readvertise your > underlay again. > > It is gracefull (no packet drops) as local forwarding can continue till > everyone around stops sending you packets in a given table_id > (corresponding to SAFI which has been shut down). > > Many thx, > R. > > --001a114fadeca796eb0536fafadc Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Robert,

There is no risk of leak= ing as the Capability will be exchanged with peers upon session establishme= nt.

What this feature also gives is monitoring Establishe= d neighbor-count. Consider a router connected to 10 peers and all 10 peers = advertise exactly same prefixes in a CLOS fabric. Now, if 5 peer sessions g= o down, the capacity is effectively reduced to 50% while this router is sti= ll in the transit. This can cause congestion. Instead, the router can decla= re itself overloaded and the downstream routers then rely on other paths. T= he update advertisement delay can be an implementation detail.

Thanks.
Amit
=
On Wed, Jul 6, 2016 at 12:34 AM, Robert Rasz= uk <robert@raszuk.net> wrote:
Hi Amit,
I agre= e that recently BGP is being stretched towards DC-fabric side to encompass = various use cases.

However, the way I see this draft, it can b= e useful for both, Internet and DC-fabrics. The main reason is to keep traf= fic drain procedure BGP topology agnostic, exactly same as ISIS Overload-bi= t. Agree, BGP has a bigger blast radius in Internet compared to ISIS but ap= propriate implementation of the feature can provide good benefits.

=E2=80=8BI don't think =E2=80=8Bthis is about= "blast radius". ISIS or OSPF are link state protocols and each n= ode in the given flooding scope computes its independent SPF hence flooding= such information is a necessity for consistent forwarding.=C2=A0

Contrary to the above BGP is pa= th/distance-vector where each BGP speaker recomputes its bRIB and re-advert= ises it. Therefor for the use case you have in mind all what is required is= to signal in some way to a bgp peer(s) that you may not want or want again= to be in forwarding for a given SAFI.=C2=A0

You defined a new SAFI as well as new NLRI format to= use for point to point signalling .. I am not convinced this is the right = level of signalling choice for this purpose. How do you stop propagation of= such NLRIs around ? It would be pretty harmful if one router in Clos fabri= c will leak it and it breaks entire fabric - wouldn't you agree ? You a= t very min MUST enforce the NO-EXPORT/NO-ADVERTISE semantics for such SAFI = which currently your draft seems to be missing.=C2=A0

There are couple of alternatives to accompl= ish the same though:=C2=A0

- using flag in dynamic capabilities=C2=A0
- l= ocal poisoning of next hops=C2=A0
- use of local = pref/med (same as OSPF max metric:)
- use of G-shut= community=C2=A0
=C2=A0
or = simply shutting the SAFIs. When you shut SAFI in one shot all paths learned= are removed and best path (or multipath) recomputed. The potential "h= it" would be on re-enabling it such that you need readvertise your und= erlay again.=C2=A0

It = is gracefull (no packet drops) as local forwarding can continue till everyo= ne around stops sending you packets in a given table_id (corresponding to S= AFI which has been shut down).=C2=A0

Many thx,
R.


--001a114fadeca796eb0536fafadc-- From nobody Wed Jul 6 10:41:28 2016 Return-Path: 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 DCC2612D094 for ; Wed, 6 Jul 2016 10:41:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.4 X-Spam-Level: X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.198, 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 aG5EYOTMObua for ; Wed, 6 Jul 2016 10:41:24 -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 13147126B6D for ; Wed, 6 Jul 2016 10:41:24 -0700 (PDT) Received: by mail-lf0-x22f.google.com with SMTP id l188so159310474lfe.2 for ; Wed, 06 Jul 2016 10:41:23 -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=uk5QG+TUmYwHGn2871iO5hSm7/JNLVFhfoc+PY32sHQ=; b=xaM0SdPQXUJSGUMA9LlswdGatoM/RbFt7TwIHeIarRVILPYBHIRbwuCWJXjxciqmbF vaOPX4s3MEqbtnnreTKQ1xTEWmXoFOoAdrDQcC2YksmBqrwY+5ujmZgneAdk9WUz5VxY wYQ5QH31NKGEj6CJMFtEs/MA7pTXg4zYHSg9Ip1LgMBmsNFTiR2kArW5pvfNvI7Yhl3X UdENcA3HRcNht0bmtry7lKjCKxYkHd1bfR6bJf5QjlzJi8hTdnVjahvFEwvD6O82Y0ad jn2OXkIHApDBftUeXcZO8ZHpjrJzWZBu9Ksk0E5oHoE3vMEysrQqZOSklhcuY83LeBUk /jNQ== 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=uk5QG+TUmYwHGn2871iO5hSm7/JNLVFhfoc+PY32sHQ=; b=k1nL4HxD90B2ADiK2gGNEfSYlZjOqeKd2jhmCGV1qr8EnIcBPoU/h8bh6/+e/CkfHo nkKcIa5n9cuK0XOp2tip1VvC5IdoGOh05OXipkZMO7d9Kdyy1IwNQOcXhzSO50YZm97M tz5XegH0n18Fb/sqlgB3H1SRlz5IcqFGl73xsDNg+g+zFwzK8ujatOZgFML9/HX+u+hS aIw64YK6SuDw66Ug6Ycge9ol3PcRMYc4zEyuxRgREmebhUXiWgSxs2zC888Cp7i0kdMU StAmEIChgDjMatKxDFjdJ4DBj5211AZR8ZAgiJnXDIF/5Fmb1iOM8chxIUbvw/teOa2a ntmA== X-Gm-Message-State: ALyK8tJudR1B3ooplfdDgMnPNQGUgMCEQnr241pL2SWxrA7AzPfsYwTKbbEUtPUrYa6yenEKkIpHuuyDjW68Ew== X-Received: by 10.25.84.65 with SMTP id i62mr7127356lfb.88.1467826882161; Wed, 06 Jul 2016 10:41:22 -0700 (PDT) MIME-Version: 1.0 Sender: rraszuk@gmail.com Received: by 10.25.21.30 with HTTP; Wed, 6 Jul 2016 10:41:21 -0700 (PDT) In-Reply-To: References: From: Robert Raszuk Date: Wed, 6 Jul 2016 19:41:21 +0200 X-Google-Sender-Auth: f2r1FZw3BsPrdO9aplMPh77t69U Message-ID: To: amit bhagat Content-Type: multipart/alternative; boundary=001a11411f28e730fd0536fb13fe Archived-At: Cc: idr wg Subject: Re: [Idr] Review Request for draft BGP Overload X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jul 2016 17:41:27 -0000 --001a11411f28e730fd0536fb13fe Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Amit, BGP Capability is completely orthogonal. It only indicates who support this new SAFI. I am talking about the case where as this new SAFI which is needed only between *directly connected* peers will use generic BGP mechanism and will propage NLRIs across entire DC. It would be completely unnecessary yet your draft does not discuss this point. This is what I call "leaking". As far as signalling number of active peers to a peer I do not see how you encode this in the currently posted proposal nor it is clear what action such router should automatically do with that information. Honestly I would rather see the operator action here. Thx, R. On Wed, Jul 6, 2016 at 7:34 PM, amit bhagat wrote: > Hi Robert, > > There is no risk of leaking as the Capability will be exchanged with peer= s > upon session establishment. > > What this feature also gives is monitoring Established neighbor-count. > Consider a router connected to 10 peers and all 10 peers advertise exactl= y > same prefixes in a CLOS fabric. Now, if 5 peer sessions go down, the > capacity is effectively reduced to 50% while this router is still in the > transit. This can cause congestion. Instead, the router can declare itsel= f > overloaded and the downstream routers then rely on other paths. The updat= e > advertisement delay can be an implementation detail. > > Thanks. > Amit > > On Wed, Jul 6, 2016 at 12:34 AM, Robert Raszuk wrote: > >> Hi Amit, >> >> I agree that recently BGP is being stretched towards DC-fabric side to >>> encompass various use cases. >>> >>> However, the way I see this draft, it can be useful for both, Internet >>> and DC-fabrics. The main reason is to keep traffic drain procedure BGP >>> topology agnostic, exactly same as ISIS Overload-bit. Agree, BGP has a >>> bigger blast radius in Internet compared to ISIS but appropriate >>> implementation of the feature can provide good benefits. >>> >> >> >> =E2=80=8BI don't think =E2=80=8Bthis is about "blast radius". ISIS or OS= PF are link state >> protocols and each node in the given flooding scope computes its >> independent SPF hence flooding such information is a necessity for >> consistent forwarding. >> >> Contrary to the above BGP is path/distance-vector where each BGP speaker >> recomputes its bRIB and re-advertises it. Therefor for the use case you >> have in mind all what is required is to signal in some way to a bgp peer= (s) >> that you may not want or want again to be in forwarding for a given SAFI= . >> >> You defined a new SAFI as well as new NLRI format to use for point to >> point signalling .. I am not convinced this is the right level of >> signalling choice for this purpose. How do you stop propagation of such >> NLRIs around ? It would be pretty harmful if one router in Clos fabric w= ill >> leak it and it breaks entire fabric - wouldn't you agree ? You at very m= in >> MUST enforce the NO-EXPORT/NO-ADVERTISE semantics for such SAFI which >> currently your draft seems to be missing. >> >> There are couple of alternatives to accomplish the same though: >> >> - using flag in dynamic capabilities >> - local poisoning of next hops >> - use of local pref/med (same as OSPF max metric:) >> - use of G-shut community >> >> or simply shutting the SAFIs. When you shut SAFI in one shot all paths >> learned are removed and best path (or multipath) recomputed. The potenti= al >> "hit" would be on re-enabling it such that you need readvertise your >> underlay again. >> >> It is gracefull (no packet drops) as local forwarding can continue till >> everyone around stops sending you packets in a given table_id >> (corresponding to SAFI which has been shut down). >> >> Many thx, >> R. >> >> > --001a11411f28e730fd0536fb13fe Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Amit,

BGP Capability is completely orthogonal. It only ind= icates who support this new SAFI. I am talking about the case where =C2=A0a= s this new SAFI which is needed only between *directly connected* peers wil= l use generic BGP mechanism and will propage NLRIs across entire DC. It wou= ld be completely unnecessary yet your draft does not discuss this point. Th= is is what I call "leaking".=C2=A0

As far as signalling number of active peers to a pee= r I do not see how you encode this in the currently posted proposal nor it = is clear what action such router should automatically do with that informat= ion. Honestly I would rather see the operator action here.=C2=A0

Thx,
R.<= /div>



On Wed, Jul 6, 2016 at = 7:34 PM, amit bhagat <scet.amit@gmail.com> wrote:
Hi Robert,

There is no risk of leaking as the Capability will be exchanged with peer= s upon session establishment.

What this feature also give= s is monitoring Established neighbor-count. Consider a router connected to = 10 peers and all 10 peers advertise exactly same prefixes in a CLOS fabric.= Now, if 5 peer sessions go down, the capacity is effectively reduced to 50= % while this router is still in the transit. This can cause congestion. Ins= tead, the router can declare itself overloaded and the downstream routers t= hen rely on other paths. The update advertisement delay can be an implement= ation detail.

Thanks.
Amit

On W= ed, Jul 6, 2016 at 12:34 AM, Robert Raszuk <robert@raszuk.net> wrote:
Hi Amit,

=
I agree that recently BGP is being stretched towards D= C-fabric side to encompass various use cases.

However, the way= I see this draft, it can be useful for both, Internet and DC-fabrics. The = main reason is to keep traffic drain procedure BGP topology agnostic, exact= ly same as ISIS Overload-bit. Agree, BGP has a bigger blast radius in Inter= net compared to ISIS but appropriate implementation of the feature can prov= ide good benefits.

=

=E2=80=8BI don't t= hink =E2=80=8Bthis is about "blast radius". ISIS or OSPF are link= state protocols and each node in the given flooding scope computes its ind= ependent SPF hence flooding such information is a necessity for consistent = forwarding.=C2=A0

Cont= rary to the above BGP is path/distance-vector where each BGP speaker recomp= utes its bRIB and re-advertises it. Therefor for the use case you have in m= ind all what is required is to signal in some way to a bgp peer(s) that you= may not want or want again to be in forwarding for a given SAFI.=C2=A0

You defined a new SAFI as= well as new NLRI format to use for point to point signalling .. I am not c= onvinced this is the right level of signalling choice for this purpose. How= do you stop propagation of such NLRIs around ? It would be pretty harmful = if one router in Clos fabric will leak it and it breaks entire fabric - wou= ldn't you agree ? You at very min MUST enforce the NO-EXPORT/NO-ADVERTI= SE semantics for such SAFI which currently your draft seems to be missing.= =C2=A0

There are coupl= e of alternatives to accomplish the same though:=C2=A0

- using flag in dynamic capabilities=C2=A0=
- local poisoning of next hops=C2=A0
- use of local pref/med (same as OSPF max metric:)
- use of G-shut community=C2=A0
=C2=A0
or simply shutting the SAFIs. When you shut SAFI in = one shot all paths learned are removed and best path (or multipath) recompu= ted. The potential "hit" would be on re-enabling it such that you= need readvertise your underlay again.=C2=A0

It is gracefull (no packet drops) as local forwardin= g can continue till everyone around stops sending you packets in a given ta= ble_id (corresponding to SAFI which has been shut down).=C2=A0

Many thx,
R.


--001a11411f28e730fd0536fb13fe-- From nobody Thu Jul 7 06:53:46 2016 Return-Path: X-Original-To: idr@ietf.org Delivered-To: idr@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 600B512D1DE; Thu, 7 Jul 2016 06:53:43 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.25.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20160707135343.23713.62123.idtracker@ietfa.amsl.com> Date: Thu, 07 Jul 2016 06:53:43 -0700 Archived-At: Cc: idr@ietf.org Subject: [Idr] I-D Action: draft-ietf-idr-reserved-extended-communities-09.txt X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jul 2016 13:53:43 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Inter-Domain Routing of the IETF. Title : Assigned BGP extended communities Authors : Bruno Decraene Pierre Francois Filename : draft-ietf-idr-reserved-extended-communities-09.txt Pages : 6 Date : 2016-07-07 Abstract: This document defines an IANA registry in order to assign non- transitive extended communities from. These are similar to the existing well-known BGP communities defined in RFC 1997 but provide a control over inter-AS community advertisement as, per RFC RFC 4360, they are not transitive across Autonomous System boundaries. For that purpose, this document defines the use of the reserved Autonomous System number 0.65535 in the non-transitive generic four- octet AS specific extended community type. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-idr-reserved-extended-communities/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-idr-reserved-extended-communities-09 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-reserved-extended-communities-09 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Thu Jul 7 06:55:54 2016 Return-Path: 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 50EC312D09F for ; Thu, 7 Jul 2016 06:55:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.345 X-Spam-Level: X-Spam-Status: No, score=-3.345 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 TT3ZSs-BQzRt for ; Thu, 7 Jul 2016 06:55:51 -0700 (PDT) Received: from relais-inet.orange.com (relais-nor34.orange.com [80.12.70.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3CCC612D603 for ; Thu, 7 Jul 2016 06:55:51 -0700 (PDT) Received: from opfednr05.francetelecom.fr (unknown [xx.xx.xx.69]) by opfednr23.francetelecom.fr (ESMTP service) with ESMTP id 157BBC013E for ; Thu, 7 Jul 2016 15:55:50 +0200 (CEST) Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.60]) by opfednr05.francetelecom.fr (ESMTP service) with ESMTP id EA32020057 for ; Thu, 7 Jul 2016 15:55:49 +0200 (CEST) Received: from OPEXCLILM21.corporate.adroot.infra.ftgroup ([fe80::e92a:c932:907e:8f06]) by OPEXCLILM7F.corporate.adroot.infra.ftgroup ([fe80::c1d7:e278:e357:11ad%19]) with mapi id 14.03.0301.000; Thu, 7 Jul 2016 15:55:49 +0200 From: To: "idr@ietf.org" Thread-Topic: [Idr] I-D Action: draft-ietf-idr-reserved-extended-communities-09.txt Thread-Index: AQHR2Fb9EvV7tgRwJk6+NMB0Oq8ngKAM/WZw Date: Thu, 7 Jul 2016 13:55:48 +0000 Message-ID: <5465_1467899750_577E5F65_5465_11655_1_53C29892C857584299CBF5D05346208A0F94131B@OPEXCLILM21.corporate.adroot.infra.ftgroup> References: <20160707135343.23713.62123.idtracker@ietfa.amsl.com> In-Reply-To: <20160707135343.23713.62123.idtracker@ietfa.amsl.com> Accept-Language: fr-FR, en-US Content-Language: fr-FR X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.168.234.1] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Subject: Re: [Idr] I-D Action: draft-ietf-idr-reserved-extended-communities-09.txt X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jul 2016 13:55:53 -0000 Hi all, Just a refresh, following discussions on GROW WG related to non-transitive = well-known communities. -- Bruno > -----Original Message----- > From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of internet-drafts@ietf= .org > Sent: Thursday, July 07, 2016 3:54 PM > To: i-d-announce@ietf.org > Cc: idr@ietf.org > Subject: [Idr] I-D Action: draft-ietf-idr-reserved-extended-communities-0= 9.txt >=20 >=20 > A New Internet-Draft is available from the on-line Internet-Drafts direct= ories. > This draft is a work item of the Inter-Domain Routing of the IETF. >=20 > Title : Assigned BGP extended communities > Authors : Bruno Decraene > Pierre Francois > Filename : draft-ietf-idr-reserved-extended-communities-09.txt > Pages : 6 > Date : 2016-07-07 >=20 > Abstract: > This document defines an IANA registry in order to assign non- > transitive extended communities from. These are similar to the > existing well-known BGP communities defined in RFC 1997 but provide a > control over inter-AS community advertisement as, per RFC RFC 4360, > they are not transitive across Autonomous System boundaries. >=20 > For that purpose, this document defines the use of the reserved > Autonomous System number 0.65535 in the non-transitive generic four- > octet AS specific extended community type. >=20 >=20 >=20 > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-idr-reserved-extended-communi= ties/ >=20 > There's also a htmlized version available at: > https://tools.ietf.org/html/draft-ietf-idr-reserved-extended-communities-= 09 >=20 > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-idr-reserved-extended-comm= unities-09 >=20 >=20 > Please note that it may take a couple of minutes from the time of submiss= ion > until the htmlized version and diff are available at tools.ietf.org. >=20 > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ >=20 > _______________________________________________ > Idr mailing list > Idr@ietf.org > https://www.ietf.org/mailman/listinfo/idr ___________________________________________________________________________= ______________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confiden= tielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu= ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el= ectroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou = falsifie. Merci. This message and its attachments may contain confidential or privileged inf= ormation that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and dele= te this message and its attachments. As emails may be altered, Orange is not liable for messages that have been = modified, changed or falsified. Thank you. From nobody Thu Jul 7 10:17:38 2016 Return-Path: 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 727AE12D0E4 for ; Thu, 7 Jul 2016 10:17:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.328 X-Spam-Level: X-Spam-Status: No, score=-3.328 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.426, 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 7tntUEogjPtQ for ; Thu, 7 Jul 2016 10:17:36 -0700 (PDT) Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 95E4012D590 for ; Thu, 7 Jul 2016 10:17:35 -0700 (PDT) Received: by slice.pfrc.org (Postfix, from userid 1001) id 3178E1E3C3; Thu, 7 Jul 2016 13:17:51 -0400 (EDT) Date: Thu, 7 Jul 2016 13:17:51 -0400 From: Jeffrey Haas To: Susan Hares Message-ID: <20160707171750.GB3711@pfrc.org> References: <068e01d1d714$c3002760$49007620$@ndzh.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <068e01d1d714$c3002760$49007620$@ndzh.com> User-Agent: Mutt/1.5.21 (2010-09-15) Archived-At: Cc: idr@ietf.org, "'Keyur Patel \(keyupate\)'" , 'Bruno Decraene' Subject: Re: [Idr] WG Adoption of draft-keyupate-idr-bgp-attribute-announcement - 2 week WG Adoption call (6/6 to 6/20) X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jul 2016 17:17:37 -0000 On Tue, Jul 05, 2016 at 07:27:12PM -0400, Susan Hares wrote: > This ends the 2 week WG Adoption call for > draft-keyupate-idr-bgp-attribute-announcement. The WG has adopted this > draft. > > The Co-chairs forgot to do an IPR call on this draft. The authors should > indicate whether they know of IPR on this draft. After we receive all the > IPR statements, the authors will be able to upload this as > draft-ietf-idr-bgp-attribute-announcement-00.txt. I am unaware of any IPR on this document. -- Jeff From nobody Thu Jul 7 10:24:57 2016 Return-Path: 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 98FF312D60B for ; Thu, 7 Jul 2016 10:24:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.328 X-Spam-Level: X-Spam-Status: No, score=-3.328 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.426, 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 7mkWjudKq3fp for ; Thu, 7 Jul 2016 10:24:54 -0700 (PDT) Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id D3D1B12D0E4 for ; Thu, 7 Jul 2016 10:24:54 -0700 (PDT) Received: by slice.pfrc.org (Postfix, from userid 1001) id 7A8471E3C3; Thu, 7 Jul 2016 13:25:10 -0400 (EDT) Date: Thu, 7 Jul 2016 13:25:10 -0400 From: Jeffrey Haas To: idr@ietf.org Message-ID: <20160707172510.GC3711@pfrc.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Archived-At: Subject: [Idr] Early allocation for ext-opt-param [internet-drafts@ietf.org: I-D Action: draft-ietf-idr-ext-opt-param-05.txt] X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jul 2016 17:24:56 -0000 A brief note as I'm catching up in my email: It does not appear that IANA has an early allocation request for the 255 code point for this draft. Given that the feature is deployed, that seems problematic. If the authors and our AD believe this will pass through IESG fast enough, we can probably skip such a request. -- Jeff ----- Forwarded message from internet-drafts@ietf.org ----- Date: Tue, 28 Jun 2016 19:10:49 -0700 From: internet-drafts@ietf.org To: i-d-announce@ietf.org Cc: idr@ietf.org Subject: [Idr] I-D Action: draft-ietf-idr-ext-opt-param-05.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Inter-Domain Routing of the IETF. Title : Extended Optional Parameters Length for BGP OPEN Message Authors : Enke Chen John Scudder Filename : draft-ietf-idr-ext-opt-param-05.txt Pages : 6 Date : 2016-06-28 Abstract: The Optional Parameters in the BGP OPEN message as defined in the base BGP specification are limited to 255 octets due to a one-octet length field. BGP Capabilities are carried in this field and may foreseeably exceed 255 octets in the future, leading to concern about this limitation. In this document we update RFC 4271 by extending the BGP OPEN length field in a backward-compatible manner. The Parameter Length field of individual Optional Parameters is similarly extended. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-idr-ext-opt-param/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-idr-ext-opt-param-05 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-ext-opt-param-05 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ Idr mailing list Idr@ietf.org https://www.ietf.org/mailman/listinfo/idr ----- End forwarded message ----- From nobody Thu Jul 7 10:33:38 2016 Return-Path: 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 D4E8512D1A7 for ; Thu, 7 Jul 2016 10:33:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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 evKzRPfJzQdy for ; Thu, 7 Jul 2016 10:33:29 -0700 (PDT) Received: from mail-qt0-x235.google.com (mail-qt0-x235.google.com [IPv6:2607:f8b0:400d:c0d::235]) (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 4158212D572 for ; Thu, 7 Jul 2016 10:33:29 -0700 (PDT) Received: by mail-qt0-x235.google.com with SMTP id m2so12008609qtd.1 for ; Thu, 07 Jul 2016 10:33:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=swkEyJaX/0JPwy+Up/9VXQgaBV6Of8McrjS29zRIdzk=; b=p06SxB5V71Y26MOsW0fgsKO7Ep3bxeX/prSDwhVW4Y7A/GzHLPjW8DKjTdNgyQpah4 S0JXzGoxsWxqohBw/EKkD1ZvGLr7Cs5rZhzeXx49q5K7Umhpfs5mkzyLiqummGwzIVhS R4XBVQgvwIBCAwnIT/9uS5fWlcalqsyE3wk4CToHnQ5JEW1aFrzVjninWOeiJufhH4zt 26owKDNMaTuFSBGIRf0FIxONnCnxnH67QMjcQEcziGEOoEkC446ATwRRUnSde1DdSYR4 rOVdRSVyPNkhiKMnrUkvfuphrM81neHVng5WDqUFvEPOW3qCCgoheELw6qMiCVx3m1n5 F1/g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=swkEyJaX/0JPwy+Up/9VXQgaBV6Of8McrjS29zRIdzk=; b=Db8egqA/WoPQSWMhK+rDQxtvAXXazJO0ZEe7F0Fsa3kRcc3AeslhT2w9j95+WJksyl 1bq2inQhh+iM2t9EQu5ef5z2YoLc10qO03jILW9uJZ7wii4g0SK0ghN7M/ibmMfYR2Yl uyv1as1ciuHv+Yi1LYWc0yUvYWjrf0MfqG48aO4DgKv2vjNhqLaYNhGPGQA8MPJOt/A7 /5Zb+lvvfW1kLydUa4c3zQRx7TrknEFarEVxNXFNPdvGTtoyMwAUtYXJzZJ5wHr5d47B xqA9todd/wEGeiJG0z2g4MuEQW3OUhgRlZxJB3/Us/2XMERTbetqf15sDPD5BguBvjja jG7A== X-Gm-Message-State: ALyK8tJlXOvsBlvjW98elKYzVJXCr9FK8F1KZPTF+xzULcBeOxwEH5UlcQbN0A7d7spMgdRc1h9AwjCgdbssoQ== X-Received: by 10.200.37.150 with SMTP id e22mr2003543qte.37.1467912808399; Thu, 07 Jul 2016 10:33:28 -0700 (PDT) MIME-Version: 1.0 Received: by 10.55.43.232 with HTTP; Thu, 7 Jul 2016 10:33:27 -0700 (PDT) In-Reply-To: References: From: amit bhagat Date: Thu, 7 Jul 2016 10:33:27 -0700 Message-ID: To: Robert Raszuk Content-Type: multipart/alternative; boundary=001a11c04ca881896205370f154f Archived-At: Cc: idr wg Subject: Re: [Idr] Review Request for draft BGP Overload X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jul 2016 17:33:36 -0000 --001a11c04ca881896205370f154f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Robert, I uploaded v01 of the draft to address some of your concerns. Sorry, I misunderstood what you meant by leaking. Agreed, even though MP_(UN)REACH_NLRI are non-transitive, they will be advertised to neighboring AS. To stop this flooding, I have added that the UPDATE message must be sent with NO_ADVERTISE community. Not sure if this is "hacky". It also includes the usecase I am referring to - neighbor-count threshold. I appreciate your feedback. Thanks. Amit On Wed, Jul 6, 2016 at 10:41 AM, Robert Raszuk wrote: > Hi Amit, > > BGP Capability is completely orthogonal. It only indicates who support > this new SAFI. I am talking about the case where as this new SAFI which = is > needed only between *directly connected* peers will use generic BGP > mechanism and will propage NLRIs across entire DC. It would be completely > unnecessary yet your draft does not discuss this point. This is what I ca= ll > "leaking". > > As far as signalling number of active peers to a peer I do not see how yo= u > encode this in the currently posted proposal nor it is clear what action > such router should automatically do with that information. Honestly I wou= ld > rather see the operator action here. > > Thx, > R. > > > > On Wed, Jul 6, 2016 at 7:34 PM, amit bhagat wrote: > >> Hi Robert, >> >> There is no risk of leaking as the Capability will be exchanged with >> peers upon session establishment. >> >> What this feature also gives is monitoring Established neighbor-count. >> Consider a router connected to 10 peers and all 10 peers advertise exact= ly >> same prefixes in a CLOS fabric. Now, if 5 peer sessions go down, the >> capacity is effectively reduced to 50% while this router is still in the >> transit. This can cause congestion. Instead, the router can declare itse= lf >> overloaded and the downstream routers then rely on other paths. The upda= te >> advertisement delay can be an implementation detail. >> >> Thanks. >> Amit >> >> On Wed, Jul 6, 2016 at 12:34 AM, Robert Raszuk wrote= : >> >>> Hi Amit, >>> >>> I agree that recently BGP is being stretched towards DC-fabric side to >>>> encompass various use cases. >>>> >>>> However, the way I see this draft, it can be useful for both, Internet >>>> and DC-fabrics. The main reason is to keep traffic drain procedure BGP >>>> topology agnostic, exactly same as ISIS Overload-bit. Agree, BGP has a >>>> bigger blast radius in Internet compared to ISIS but appropriate >>>> implementation of the feature can provide good benefits. >>>> >>> >>> >>> =E2=80=8BI don't think =E2=80=8Bthis is about "blast radius". ISIS or O= SPF are link >>> state protocols and each node in the given flooding scope computes its >>> independent SPF hence flooding such information is a necessity for >>> consistent forwarding. >>> >>> Contrary to the above BGP is path/distance-vector where each BGP speake= r >>> recomputes its bRIB and re-advertises it. Therefor for the use case you >>> have in mind all what is required is to signal in some way to a bgp pee= r(s) >>> that you may not want or want again to be in forwarding for a given SAF= I. >>> >>> You defined a new SAFI as well as new NLRI format to use for point to >>> point signalling .. I am not convinced this is the right level of >>> signalling choice for this purpose. How do you stop propagation of such >>> NLRIs around ? It would be pretty harmful if one router in Clos fabric = will >>> leak it and it breaks entire fabric - wouldn't you agree ? You at very = min >>> MUST enforce the NO-EXPORT/NO-ADVERTISE semantics for such SAFI which >>> currently your draft seems to be missing. >>> >>> There are couple of alternatives to accomplish the same though: >>> >>> - using flag in dynamic capabilities >>> - local poisoning of next hops >>> - use of local pref/med (same as OSPF max metric:) >>> - use of G-shut community >>> >>> or simply shutting the SAFIs. When you shut SAFI in one shot all paths >>> learned are removed and best path (or multipath) recomputed. The potent= ial >>> "hit" would be on re-enabling it such that you need readvertise your >>> underlay again. >>> >>> It is gracefull (no packet drops) as local forwarding can continue till >>> everyone around stops sending you packets in a given table_id >>> (corresponding to SAFI which has been shut down). >>> >>> Many thx, >>> R. >>> >>> >> > --001a11c04ca881896205370f154f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Robert,

I uploaded v01= of the draft to address some of your concerns. Sorry, I misunderstood what= you meant by leaking. Agreed, even though MP_(UN)REACH_NLRI are non-transi= tive, they will be advertised to neighboring AS. To stop this flooding, I h= ave added that the UPDATE message must be sent with NO_ADVERTISE community.= Not sure if this is "hacky".

It al= so includes the usecase I am referring to - neighbor-count threshold.

I appreciate your feedback.

Thanks.
Amit

O= n Wed, Jul 6, 2016 at 10:41 AM, Robert Raszuk <robert@raszuk.net> wrote:
Hi Amit,

BGP = Capability is completely orthogonal. It only indicates who support this new= SAFI. I am talking about the case where =C2=A0as this new SAFI which is ne= eded only between *directly connected* peers will use generic BGP mechanism= and will propage NLRIs across entire DC. It would be completely unnecessar= y yet your draft does not discuss this point. This is what I call "lea= king".=C2=A0

As f= ar as signalling number of active peers to a peer I do not see how you enco= de this in the currently posted proposal nor it is clear what action such r= outer should automatically do with that information. Honestly I would rathe= r see the operator action here.=C2=A0

Thx,
R.


On Wed, J= ul 6, 2016 at 7:34 PM, amit bhagat <scet.amit@gmail.com> w= rote:
Hi Rober= t,

There is no risk of leaking as the Capability will be excha= nged with peers upon session establishment.

What this fea= ture also gives is monitoring Established neighbor-count. Consider a router= connected to 10 peers and all 10 peers advertise exactly same prefixes in = a CLOS fabric. Now, if 5 peer sessions go down, the capacity is effectively= reduced to 50% while this router is still in the transit. This can cause c= ongestion. Instead, the router can declare itself overloaded and the downst= ream routers then rely on other paths. The update advertisement delay can b= e an implementation detail.

Thanks.
Amit
=

On Wed, Jul 6, 2016 at 12:34 AM, Robert Raszuk <robert@= raszuk.net> wrote:
Hi Amit,

I agree that recently BGP is = being stretched towards DC-fabric side to encompass various use cases.
<= br>
However, the way I see this draft, it can be useful for both, Inte= rnet and DC-fabrics. The main reason is to keep traffic drain procedure BGP= topology agnostic, exactly same as ISIS Overload-bit. Agree, BGP has a big= ger blast radius in Internet compared to ISIS but appropriate implementatio= n of the feature can provide good benefits.


=E2=80=8BI don't think =E2=80=8Bthis is about "blast radius&quo= t;. ISIS or OSPF are link state protocols and each node in the given floodi= ng scope computes its independent SPF hence flooding such information is a = necessity for consistent forwarding.=C2=A0

Contrary to the above BGP is path/distance-vector wher= e each BGP speaker recomputes its bRIB and re-advertises it. Therefor for t= he use case you have in mind all what is required is to signal in some way = to a bgp peer(s) that you may not want or want again to be in forwarding fo= r a given SAFI.=C2=A0

= You defined a new SAFI as well as new NLRI format to use for point to point= signalling .. I am not convinced this is the right level of signalling cho= ice for this purpose. How do you stop propagation of such NLRIs around ? It= would be pretty harmful if one router in Clos fabric will leak it and it b= reaks entire fabric - wouldn't you agree ? You at very min MUST enforce= the NO-EXPORT/NO-ADVERTISE semantics for such SAFI which currently your dr= aft seems to be missing.=C2=A0

There are couple of alternatives to accomplish the same though:=C2= =A0

- using flag in dy= namic capabilities=C2=A0
- local poisoning of next = hops=C2=A0
- use of local pref/med (same as OSPF ma= x metric:)
- use of G-shut community=C2=A0
=C2=A0
or simply shutting the SAFIs= . When you shut SAFI in one shot all paths learned are removed and best pat= h (or multipath) recomputed. The potential "hit" would be on re-e= nabling it such that you need readvertise your underlay again.=C2=A0
<= div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif= ;font-size:small">
It is gracefull (no packet d= rops) as local forwarding can continue till everyone around stops sending y= ou packets in a given table_id (corresponding to SAFI which has been shut d= own).=C2=A0

Many thx,<= br>R.




--001a11c04ca881896205370f154f-- From nobody Fri Jul 8 03:29:34 2016 Return-Path: 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 75B2F12D665 for ; Fri, 8 Jul 2016 03:29:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.738 X-Spam-Level: * X-Spam-Status: No, score=1.738 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, RDNS_NONE=0.793] autolearn=no 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 CTLRWALYM40Z for ; Fri, 8 Jul 2016 03:29:32 -0700 (PDT) Received: from hickoryhill-consulting.com (unknown [50.245.122.97]) (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 A7FBC12D63C for ; Fri, 8 Jul 2016 03:29:31 -0700 (PDT) X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=74.43.47.72; From: "Susan Hares" To: References: <20160708102740.32127.50534.idtracker@ietfa.amsl.com> In-Reply-To: <20160708102740.32127.50534.idtracker@ietfa.amsl.com> Date: Fri, 8 Jul 2016 06:28:54 -0400 Message-ID: <008001d1d903$87a6a630$96f3f290$@ndzh.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQHaWnduqGUJ7AohcqThQyqhgB8nHp/9UbJw Content-Language: en-us X-Authenticated-User: skh@ndzh.com Archived-At: Subject: [Idr] FW: New Version Notification for draft-liang-idr-flowspec-v1-time-00.txt X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jul 2016 10:29:33 -0000 This time filter that combines with the other RFC5575bis filters. The = authors welcome comments on this draft.=20 Sue, Jianjie, and LIang -----Original Message----- From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]=20 Sent: Friday, July 8, 2016 6:28 AM To: Jianjie You; Qiandeng Liang; liangqiandeng; Susan Hares Subject: New Version Notification for = draft-liang-idr-flowspec-v1-time-00.txt A new version of I-D, draft-liang-idr-flowspec-v1-time-00.txt has been successfully submitted by Susan Hares and posted to the IETF = repository. Name: draft-liang-idr-flowspec-v1-time Revision: 00 Title: BGP Flow Specification Filter Component for Time Constraints Document date: 2016-07-08 Group: Individual Submission Pages: 6 URL: = https://www.ietf.org/internet-drafts/draft-liang-idr-flowspec-v1-time-00.= txt Status: = https://datatracker.ietf.org/doc/draft-liang-idr-flowspec-v1-time/ Htmlized: = https://tools.ietf.org/html/draft-liang-idr-flowspec-v1-time-00 Abstract: BGP flow specification version 1 (RFC5575) describes the distribution of traffic filter policy (traffic filters and actions) which are distributed via BGP to BGP peers to support the following 3 applications: (1) mitigation of Denial of Service (DoS), (2) traffic filtering in BGP/MPLS VPNs, and (3) centralized traffic control for networks with SDN or NFV controllers. A BGP Flow Filter that combines packet filter with time may provide an ability to for these three applications to have a flow filter operate for only a specific time. This document proposes a new BGP Flow specification filter based on time. = =20 Please note that it may take a couple of minutes from the time of = submission until the htmlized version and diff are available at = tools.ietf.org. The IETF Secretariat From nobody Fri Jul 8 03:36:42 2016 Return-Path: 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 92AAC12D739 for ; Fri, 8 Jul 2016 03:36:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 4.439 X-Spam-Level: **** X-Spam-Status: No, score=4.439 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, RDNS_NONE=0.793] autolearn=no 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 1XNg8lxqlS_y for ; Fri, 8 Jul 2016 03:36:39 -0700 (PDT) Received: from hickoryhill-consulting.com (unknown [50.245.122.97]) (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 4187F12D5DE for ; Fri, 8 Jul 2016 03:36:39 -0700 (PDT) X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=74.43.47.72; From: "Susan Hares" To: "'John G. Scudder'" , Date: Fri, 8 Jul 2016 06:36:07 -0400 Message-ID: <008201d1d904$89530130$9bf90390$@ndzh.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0083_01D1D8E3.0243F940" X-Mailer: Microsoft Outlook 14.0 Thread-Index: AdHZBGDb1bLvCih+QbGfyXVlJNljLg== Content-Language: en-us X-Authenticated-User: skh@ndzh.com Archived-At: Subject: [Idr] IDR presentaton slot X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jul 2016 10:36:40 -0000 This is a multipart message in MIME format. ------=_NextPart_000_0083_01D1D8E3.0243F940 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit John: May I please have time for 4 flow specification drafts presentations: 1) Flow specification v2 [3 slides, title, 2 text] 2) RFC5575bis - 2 variants: draft-hares-rfc5575bis, draft-hr-rfc5575bis [4 slides: title: 3 text] 3) Flow Specification Time filter - draft-liang-idr-flowspec-v1-time and draft-liang-idr-flowspec-v3 [3 slides, title, 2 text, 1 QA] Total: slides: 10 slides, total time 15 minutes (less if need to) . Sue Hares ------=_NextPart_000_0083_01D1D8E3.0243F940 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

John: =

 

May I please have time for 4 flow specification drafts = presentations:  

 

1)      = Flow specification v2  [3 slides, title, 2 = text]  

2)      = RFC5575bis – 2 variants: = draft-hares-rfc5575bis, draft-hr-rfc5575bis  [4 slides: title: 3 = text]  

3)      = Flow Specification Time filter - = draft-liang-idr-flowspec-v1-time and = draft-liang-idr-flowspec-v3

[3 = slides, title, 2 text, 1 QA]  

 

Total: =  slides: 10 slides, total time 15 minutes (less if need to) .  =   

 

Sue Hares

 

 

------=_NextPart_000_0083_01D1D8E3.0243F940-- From nobody Fri Jul 8 08:02:59 2016 Return-Path: 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 0C48C12B047 for ; Fri, 8 Jul 2016 08:02:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -15.947 X-Spam-Level: X-Spam-Status: No, score=-15.947 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 tMirpktgh9GE for ; Fri, 8 Jul 2016 08:02:56 -0700 (PDT) Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1423E12D769 for ; Fri, 8 Jul 2016 08:02:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=218; q=dns/txt; s=iport; t=1467990170; x=1469199770; h=from:to:cc:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=/F/+zUzPRtd7bIts2aBHDG+Rcmh0Z5jU7YSOY6cKG38=; b=RqE6dtjr8FTWE0KgIhDnMxZC8NBIWI2D+pQWZVACqei1EIZxNx6S3Uu2 QPVs/HHKdVaEFM6fzroy0SgmnV4ulmrECCkTpkVTV8Q+JnK4zcKam1Neq nn/zbFNHSlAQb1xeHe4XmyG2buw7bLWpSnDrsGfVYnTcYO0I2OyjzrhtI 4=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BVBgCCv39X/4MNJK1bgz5WgQK5DoF7I?= =?us-ascii?q?oV2HoELOhIBAQEBAQEBZSeEUyMRRRIBFgwCJgIEMBUSBAENiDUOrkGPPQEBAQE?= =?us-ascii?q?BAQEDAQEBAQEBAQEaBYEBixWGIIJaBZkUAYYLiEOBVAGNV2+PHgElBCuDcYkhf?= =?us-ascii?q?wEBAQ?= X-IronPort-AV: E=Sophos;i="5.28,330,1464652800"; d="scan'208";a="295285027" Received: from alln-core-1.cisco.com ([173.36.13.131]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 08 Jul 2016 15:02:50 +0000 Received: from XCH-RTP-012.cisco.com (xch-rtp-012.cisco.com [64.101.220.152]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id u68F2o99004064 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 8 Jul 2016 15:02:50 GMT Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-012.cisco.com (64.101.220.152) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 8 Jul 2016 11:02:49 -0400 Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1210.000; Fri, 8 Jul 2016 11:02:49 -0400 From: "Acee Lindem (acee)" To: Susan Hares , John Scudder Thread-Topic: IDR Session Slot Request Thread-Index: AQHR2SnKHHa63GQ4GEuJn2prDiOnng== Date: Fri, 8 Jul 2016 15:02:49 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.116.152.196] Content-Type: text/plain; charset="utf-8" Content-ID: Content-Transfer-Encoding: base64 MIME-Version: 1.0 Archived-At: Cc: IDR List Subject: [Idr] IDR Session Slot Request X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jul 2016 15:02:58 -0000 SGkgU3VlLCBKb2huLA0KDQpJIHdvdWxkIGxpa2UgYSAxMCBtaW51dGUgc2xvdCB0byBwcmVzZW50 IG91ciBuZXcgZHJhZnQ6DQoNCmh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0 LWtleXVwYXRlLWlkci1iZ3Atc3BmLw0KDQpUaGFua3MsDQpBY2VlIA0KDQo= From nobody Fri Jul 8 08:48:19 2016 Return-Path: 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 C3B5112D0B5 for ; Fri, 8 Jul 2016 08:48:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.738 X-Spam-Level: * X-Spam-Status: No, score=1.738 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, RDNS_NONE=0.793] autolearn=no 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 cF0ftpP9eUxT for ; Fri, 8 Jul 2016 08:48:16 -0700 (PDT) Received: from hickoryhill-consulting.com (unknown [50.245.122.97]) (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 A6C6812D549 for ; Fri, 8 Jul 2016 08:48:16 -0700 (PDT) X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=74.43.47.72; From: "Susan Hares" To: "'Acee Lindem \(acee\)'" , "'John Scudder'" References: In-Reply-To: Date: Fri, 8 Jul 2016 11:47:43 -0400 Message-ID: <01a201d1d930$1189dbc0$349d9340$@ndzh.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQLZUY3p7vHktXOl/lY0p4GxW46HOp3/vPkA Content-Language: en-us X-Authenticated-User: skh@ndzh.com Archived-At: Cc: 'IDR List' Subject: Re: [Idr] IDR Session Slot Request X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jul 2016 15:48:17 -0000 Acee: I will add you to the list. Sue -----Original Message----- From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Acee Lindem (acee) Sent: Friday, July 8, 2016 11:03 AM To: Susan Hares; John Scudder Cc: IDR List Subject: [Idr] IDR Session Slot Request Hi Sue, John, I would like a 10 minute slot to present our new draft: https://datatracker.ietf.org/doc/draft-keyupate-idr-bgp-spf/ Thanks, Acee _______________________________________________ Idr mailing list Idr@ietf.org https://www.ietf.org/mailman/listinfo/idr From nobody Fri Jul 8 08:52:30 2016 Return-Path: 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 6FE8212D7D2 for ; Fri, 8 Jul 2016 08:52:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.4 X-Spam-Level: X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.198, 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 Hw8kbZC51LYa for ; Fri, 8 Jul 2016 08:52:13 -0700 (PDT) Received: from mail-lf0-x243.google.com (mail-lf0-x243.google.com [IPv6:2a00:1450:4010:c07::243]) (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 0195812D7D6 for ; Fri, 8 Jul 2016 08:51:58 -0700 (PDT) Received: by mail-lf0-x243.google.com with SMTP id a2so7997959lfe.3 for ; Fri, 08 Jul 2016 08:51:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:from:date:message-id:subject:to:cc; bh=Ia/KcfbRRLyG/U3c5JcHAUJYcvQGIOVkLG+/COt2QOM=; b=dpTVe8Ik+czS2ZgoCQTz/Uuo4nZ5EWIV5K4WYk4t9IdlZYA3zopuFqzGG9xaoFWgiX yTRBozUXii2XrIRMV4dWM/19SqCRPsAEFlaJlZv+mgolzz++DLSqU9MmJ/YahL6PoVXg t67awBaqe9nhZLs8DvFuS07/ucaV2QX49m7CSDuOWuslMs2ZRX+ZqUCKQ3hkqefJ9Ap6 awPghu+BgTBf2n7EskNfTJVCwUx2MWshJA+YXFsJobo/1mZrBUYUw/Bvz+St52zwNHBH YI7gQyPpmC4CuHeoFGkb5vrK8Z1bNwZhN+5/oBIGrHoaDtcbkk2QiH056g38io65byev QBHw== 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:from:date:message-id:subject :to:cc; bh=Ia/KcfbRRLyG/U3c5JcHAUJYcvQGIOVkLG+/COt2QOM=; b=HugfF+jW1816SHlrZ5zGmdSWjISR2QaXD2EKlNV6IudNyeHsMwyqoK3QrV2FCBd21Z aoPtWzPXHUUjhEPlxFVf5xJ1RT2DzNxdMs22WmjzO0Hea1RD4LQywS4RXXRicx0oL4QV emJVju1y4CXJ1zp4x0qdFzgXg6sdkSytEYBPmm0YLKZJL5ZBsnBFi+rAMzRrtfZvjuH7 v4jTe1iqgfPJWi6OtpDFqEZSxlDs7xO6841/rp++o7GVvNJs3rGY09nU1c4f1dUGCb9F fdIH1GYOom1ZIISi5x53v2+kT2bVfmo5vM67VMdwKXgIyQml0gOkYhwF5mbTJG5YfVVW i2+Q== X-Gm-Message-State: ALyK8tJ9m1mY4O7mjmqKFKvaM6xCleubdJ6VmouDU9VjO5p5Rr41I9QvpZWFChp/6lJacCKCIbLF/EDykC1kzg== X-Received: by 10.46.33.80 with SMTP id h77mr1666535ljh.29.1467993117101; Fri, 08 Jul 2016 08:51:57 -0700 (PDT) MIME-Version: 1.0 Sender: rraszuk@gmail.com Received: by 10.25.18.225 with HTTP; Fri, 8 Jul 2016 08:51:56 -0700 (PDT) From: Robert Raszuk Date: Fri, 8 Jul 2016 17:51:56 +0200 X-Google-Sender-Auth: qUiayxR_DCszy7xVT6kvZqHWfnw Message-ID: To: "Keyur Patel (keyupate)" , "Acee Lindem (acee)" , Abhay Roy , "Derek Man-Kit Yeung (myeung)" , "Venu Venugopal (venuv)" Content-Type: multipart/alternative; boundary=001a1142c9b24714ca053721c8dc Archived-At: Cc: idr wg Subject: [Idr] Shortest Path Routing Extensions for BGP Protocol X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jul 2016 15:52:15 -0000 --001a1142c9b24714ca053721c8dc Content-Type: text/plain; charset=UTF-8 Hi, I have reviewed your proposal. Turning path vector or distance vector protocol into link state carrier is no doubt a bold idea :). Effectively what you are proposing is to use BGP TCP sessions to propagate link state database creating first "link vector protocol" ! For start I have few questions: Q1: RFC7752 has gone via lot of efforts (especially sections 3.2 and up) to include number of OSPF or ISIS specific encodings. In your proposal you mentioned OSPF twice and not even once ISIS. Does it mean that you are not going to use all encoding for specific IGPs as defined in RFC7752 ? Q2: Who creates and maintains LSDB in each BGP speaker ? Are you planning to run OSPF and or ISIS except disable it to establish any adjaciencies ? Q3: Currently there are already to models to build DCs with BGP ... one uses BGP to create only lean underlay the other is to use BGP for both underlay and tenants (example project Calico for the latter). With that scale wise I think your proposal will work great for the former. However I do have concerns about using your model for the latter where say 10,000 or 100,000 /32s or /128s from each VMs are injected and you need to construct SPT with all of those. Q4: Related to Q3 in your model and say flat DC routing each compute node other then just injecting 10s of /32s and being "done" now becomes an IGP node. Since your document explicitely targets Massively Scaled Data Centers (MSDCs) I am concerned that having 100,000+ IGP nodes and in many case much more is not the best idea. Q5: Have you considered just proposing an OSPF route reflector instead without stuffing BGP into the mix ? As some of you perhaps remember the work on this started around year 2000 to optimize PE-CE CSC deployments :) It seems to me very reusable for this goal. Best regards, Robert. --001a1142c9b24714ca053721c8dc Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

<= div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif= ;font-size:small">I have reviewed your proposal.=C2=A0

Turning path vector or distance vector pro= tocol into link state carrier is no doubt a bold idea :).

Effectively what you are proposing is= to use BGP TCP sessions to propagate link state database creating first &q= uot;link vector protocol" !

For start I have few questions:

Q1:=C2=A0

RFC7752 has gone via lot of efforts (especially sections 3.2 and u= p) to include number of OSPF or ISIS specific encodings. In your proposal y= ou mentioned OSPF twice and not even once ISIS. Does it mean that you are n= ot going to use all encoding for specific IGPs as defined in RFC7752 ?=C2= =A0

Q2:=C2=A0

Who creates and maintains LSDB= in each BGP speaker ? Are you planning to run OSPF and or ISIS except disa= ble it to establish any adjaciencies ?=C2=A0

Q3:=C2=A0

Currently there are already to models to build DCs with BGP ... = one uses BGP to create only lean underlay the other is to use BGP for both = underlay and tenants (example project Calico for the latter). With that sca= le wise I think your proposal will work great for the former. However I do = have concerns about using your model for the latter where say 10,000 or 100= ,000 /32s or /128s from each VMs are injected and you need to construct SPT= with all of those.=C2=A0

Q4:=C2=A0

Rela= ted to Q3 in your model and say flat DC routing each compute node other the= n just injecting 10s of /32s and being "done" now becomes an IGP = node. Since your document explicitely targets=C2=A0Massively Scaled Data Ce= nters (MSDCs) I am concerned that having 100,000+ IGP nodes and in many cas= e much more is not the best idea.=C2=A0

<= div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif= ;font-size:small">Q5:=C2=A0

Have you considered just proposing an OSPF route reflector instead wi= thout stuffing BGP into the mix ? As some of you perhaps remember the work = on this started around year 2000 to optimize PE-CE CSC deployments :) It se= ems to me very reusable for this goal.

Best regards,
Robert.

--001a1142c9b24714ca053721c8dc-- From nobody Fri Jul 8 09:08:39 2016 Return-Path: X-Original-To: idr@ietf.org Delivered-To: idr@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B4FC512B02E; Fri, 8 Jul 2016 09:08:34 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.25.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20160708160834.32176.49579.idtracker@ietfa.amsl.com> Date: Fri, 08 Jul 2016 09:08:34 -0700 Archived-At: Cc: idr@ietf.org Subject: [Idr] I-D Action: draft-vandevelde-idr-flowspec-path-redirect-03.txt X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jul 2016 16:08:35 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Inter-Domain Routing of the IETF. Title : Flowspec Indirection-id Redirect Authors : Gunter Van de Velde Wim Henderickx Keyur Patel Arjun Sreekantiah Zhenbin Li Shunwan Zhuang Nan Wu Filename : draft-vandevelde-idr-flowspec-path-redirect-03.txt Pages : 12 Date : 2016-07-08 Abstract: Flowspec is an extension to BGP that allows for the dissemination of traffic flow specification rules. This has many possible applications but the primary one for many network operators is the distribution of traffic filtering actions for DDoS mitigation. The flow-spec standard RFC5575 [2] defines a redirect-to-VRF action for policy-based forwarding but this mechanism is not always sufficient, particularly if the redirected traffic needs to be steered into an engineered path or into a service plane. This document defines a new extended community known as redirect-to- indirection-id (32-bit) flowspec action to provide advanced redirection capabilities on flowspec clients. When activated, the flowspec extended community is used by a flowspec client to find the correct next-hop entry within a localised indirection-id mapping table. The functionality present in this draft allows a network controller to decouple flowspec functionality from the creation and maintainance of the network's service plane itself including the setup of tunnels and other service constructs that could be managed by other network devices. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-vandevelde-idr-flowspec-path-redirect/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-vandevelde-idr-flowspec-path-redirect-03 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-vandevelde-idr-flowspec-path-redirect-03 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Fri Jul 8 09:13:26 2016 Return-Path: X-Original-To: idr@ietf.org Delivered-To: idr@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A33A12D504; Fri, 8 Jul 2016 09:13:24 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.25.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20160708161324.32205.25819.idtracker@ietfa.amsl.com> Date: Fri, 08 Jul 2016 09:13:24 -0700 Archived-At: Cc: idr@ietf.org Subject: [Idr] I-D Action: draft-ietf-idr-bgp-optimal-route-reflection-12.txt X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jul 2016 16:13:24 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Inter-Domain Routing of the IETF. Title : BGP Optimal Route Reflection (BGP-ORR) Authors : Robert Raszuk Christian Cassar Erik Aman Bruno Decraene Stephane Litkowski Kevin Wang Filename : draft-ietf-idr-bgp-optimal-route-reflection-12.txt Pages : 12 Date : 2016-07-08 Abstract: This document proposes a solution for BGP route reflectors to allow them to choose the best path their clients would have chosen under the same conditions, without requiring further state or any new features to be placed on the clients. This facilitates, for example, best exit point policy (hot potato routing). This solution is primarily applicable in deployments using centralized route reflectors. The solution relies upon all route reflectors learning all paths which are eligible for consideration. Best path selection is performed in each route reflector based on a configured virtual location in the IGP. The location can be the same for all clients or different per peer/update group or per peer. Best path selection can also be performed based on user configured policies in each route reflector. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-optimal-route-reflection/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-idr-bgp-optimal-route-reflection-12 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-bgp-optimal-route-reflection-12 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Fri Jul 8 09:21:32 2016 Return-Path: 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 160B712D0C9; Fri, 8 Jul 2016 09:21:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.702 X-Spam-Level: X-Spam-Status: No, score=-2.702 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=icloud.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 LGlFVwBRL_W1; Fri, 8 Jul 2016 09:21:29 -0700 (PDT) Received: from st13p11im-asmtp003.me.com (st13p11im-asmtp003.me.com [17.164.40.218]) (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 C6B6D12D0A4; Fri, 8 Jul 2016 09:21:28 -0700 (PDT) Received: from process-dkim-sign-daemon.st13p11im-asmtp003.me.com by st13p11im-asmtp003.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) id <0OA0006007HEP000@st13p11im-asmtp003.me.com>; Fri, 08 Jul 2016 16:21:09 +0000 (GMT) Received: from 174-16-209-161.hlrn.qwest.net (unknown [128.127.164.82]) by st13p11im-asmtp003.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) with ESMTPSA id <0OA000CLT82YDS00@st13p11im-asmtp003.me.com>; Fri, 08 Jul 2016 16:21:07 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2016-07-08_09:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1011 suspectscore=3 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1510270003 definitions=main-1607080152 Content-type: text/plain; charset=us-ascii MIME-version: 1.0 (Mac OS X Mail 9.3 \(3124\)) From: Gunter Van De Velde In-reply-to: <152e01d1d5ee$0c4c1320$24e43960$@ndzh.com> Date: Fri, 08 Jul 2016 18:20:57 +0200 Content-transfer-encoding: quoted-printable Message-id: References: <152e01d1d5ee$0c4c1320$24e43960$@ndzh.com> To: Susan Hares X-Mailer: Apple Mail (2.3124) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=icloud.com; s=4d515a; t=1467994869; bh=eZ7uVLxxdzlllwjRhBdF/WLzXzqiG3ZDrFSqzQvo6ck=; h=Content-type:MIME-version:Subject:From:Date:Message-id:To; b=oXIn6UnNLJGmtV4o8iHTv31Tfjyjut8Kpct5iSG+8d0MgJFnmjt2dn5KDS8Aep4KQ 2qVYPhCwZp8Zigk/pIs9ygnvFkOkhWWfIXR/rRtWCAz/EmdP2E216FQumU6m6vJ23q ZhCr7NoQvIneovSoOouXErKUGl2u90HASEIKq1ioSQCTt3FP8HaR9CGsB+HS1ugmFS IjkS6VRFPCS4F9F4JpRX7X7MVy9kQEutRdaS1/O6n/r/igzDrcr50FyKOGLKnosdA9 CxwSZX8lHk/uE9TNvcGICVcJCQJ6UTTWVC5gGo54+eK/SxumXxWBxQk1XcDhaT/788 SFOUI9IjLz4ug== Archived-At: Cc: idr@ietf.org, "John G. Scudder" , idr chairs Subject: Re: [Idr] Presentation slot X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jul 2016 16:21:31 -0000 Hi Sue, John, As discussed the draft-vandevelde-idr-flowspec-path-redirect-03 has been = posted and is now the merged document=20 draft-vandevelde-idr-flowspec-path-redirect-02 and = draft-li-idr-flowspec-redirect-generalized-sid-00 . Maybe a 5 minute slot to discuss the current state could be helpful for = the WG. Brgds, G/ > On 04 Jul 2016, at 14:17, Susan Hares wrote: >=20 > =20 > IETF 96 is drawing near. For those who would like to present at IETF = 96, please reply to this message (making sure to keep both chairs), and = request a slot. =20 > =20 > Sue and John=20 > _______________________________________________ > Idr mailing list > Idr@ietf.org > https://www.ietf.org/mailman/listinfo/idr From nobody Fri Jul 8 09:22:36 2016 Return-Path: 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 2F58412D0C9 for ; Fri, 8 Jul 2016 09:22:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -15.946 X-Spam-Level: X-Spam-Status: No, score=-15.946 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 2vZKxlX6IRxX for ; Fri, 8 Jul 2016 09:22:32 -0700 (PDT) Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A09012D0A8 for ; Fri, 8 Jul 2016 09:22:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=20889; q=dns/txt; s=iport; t=1467994952; x=1469204552; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=0PMCpYYQ5fEWD2ok48+A47JvdnnGh9GbYX6aX9/5xOg=; b=fMNbTva700JgvtVnBuBpbfxAzyiNgUp1eFoUkGQzj/GV9uDCTG2gWi9M 9n17BNrXIewRie18rwj2QclYDnwzqeyDmS5dZfK78IDTkRSX2qBWNr88K CN5QK56pU6LSDDHAt1uKnd/79ULyJ4YNdLKUHPKQUM6unzp0sxaFmrpGC Q=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0B5AgCL0n9X/4sNJK1bgnBOgVIGrHmHE?= =?us-ascii?q?YUEgXuGGAIcgQw4FAEBAQEBAQFlJ4RMAQEFI0QSEAIBCBEDAQIoAwICAh8RFAk?= =?us-ascii?q?IAgQBDQWIFgMXrm6LBQ2EGwEBAQEBAQEBAQEBAQEBAQEBAQEBARyJcYEDgkOBW?= =?us-ascii?q?kSCYYJaBZNahQY0AYw6ghSBaoRYiGqIGodzAR42g3Fuh25FfwEBAQ?= X-IronPort-AV: E=Sophos;i="5.28,330,1464652800"; d="scan'208,217";a="294704602" Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 08 Jul 2016 16:22:31 +0000 Received: from XCH-RTP-015.cisco.com (xch-rtp-015.cisco.com [64.101.220.155]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id u68GMUYo012265 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 8 Jul 2016 16:22:31 GMT Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-015.cisco.com (64.101.220.155) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 8 Jul 2016 12:22:29 -0400 Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1210.000; Fri, 8 Jul 2016 12:22:29 -0400 From: "Acee Lindem (acee)" To: Robert Raszuk , "Keyur Patel (keyupate)" , "Abhay Roy (akr)" , "Derek Man-Kit Yeung (myeung)" , "Venu Venugopal (venuv)" Thread-Topic: Shortest Path Routing Extensions for BGP Protocol Thread-Index: AQHR2TCrYqWhF/FuxECJ8BfBQYUWB6AOt3SA Date: Fri, 8 Jul 2016 16:22:29 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.116.152.196] Content-Type: multipart/alternative; boundary="_000_D3A547856931Eaceeciscocom_" MIME-Version: 1.0 Archived-At: Cc: idr wg Subject: Re: [Idr] Shortest Path Routing Extensions for BGP Protocol X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jul 2016 16:22:34 -0000 --_000_D3A547856931Eaceeciscocom_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 SGkgUm9iZXJ0LA0KDQpUaGFua3MgZm9yIGVuZ2FnaW5n4oCmDQoNCkZyb206IDxycmFzenVrQGdt YWlsLmNvbTxtYWlsdG86cnJhc3p1a0BnbWFpbC5jb20+PiBvbiBiZWhhbGYgb2YgUm9iZXJ0IFJh c3p1ayA8cm9iZXJ0QHJhc3p1ay5uZXQ8bWFpbHRvOnJvYmVydEByYXN6dWsubmV0Pj4NCkRhdGU6 IEZyaWRheSwgSnVseSA4LCAyMDE2IGF0IDExOjUxIEFNDQpUbzogIktleXVyIFBhdGVsIChrZXl1 cGF0ZSkiIDxrZXl1cGF0ZUBjaXNjby5jb208bWFpbHRvOmtleXVwYXRlQGNpc2NvLmNvbT4+LCBB Y2VlIExpbmRlbSA8YWNlZUBjaXNjby5jb208bWFpbHRvOmFjZWVAY2lzY28uY29tPj4sICJBYmhh eSBSb3kgKGFrcikiIDxha3JAY2lzY28uY29tPG1haWx0bzpha3JAY2lzY28uY29tPj4sICJEZXJl ayBNYW4tS2l0IFlldW5nIChteWV1bmcpIiA8bXlldW5nQGNpc2NvLmNvbTxtYWlsdG86bXlldW5n QGNpc2NvLmNvbT4+LCAiVmVudSBWZW51Z29wYWwgKHZlbnV2KSIgPHZlbnV2QGNpc2NvLmNvbTxt YWlsdG86dmVudXZAY2lzY28uY29tPj4NCkNjOiBJRFIgTGlzdCA8aWRyQGlldGYub3JnPG1haWx0 bzppZHJAaWV0Zi5vcmc+Pg0KU3ViamVjdDogU2hvcnRlc3QgUGF0aCBSb3V0aW5nIEV4dGVuc2lv bnMgZm9yIEJHUCBQcm90b2NvbA0KDQpIaSwNCg0KSSBoYXZlIHJldmlld2VkIHlvdXIgcHJvcG9z YWwuDQoNClR1cm5pbmcgcGF0aCB2ZWN0b3Igb3IgZGlzdGFuY2UgdmVjdG9yIHByb3RvY29sIGlu dG8gbGluayBzdGF0ZSBjYXJyaWVyIGlzIG5vIGRvdWJ0IGEgYm9sZCBpZGVhIDopLg0KDQrigJxG b3J0dW5lIGJlZnJpZW5kcyB0aGUgYm9sZC7igJ0gLUVtaWx5IERpY2tpbnNvbg0KDQoNCkVmZmVj dGl2ZWx5IHdoYXQgeW91IGFyZSBwcm9wb3NpbmcgaXMgdG8gdXNlIEJHUCBUQ1Agc2Vzc2lvbnMg dG8gcHJvcGFnYXRlIGxpbmsgc3RhdGUgZGF0YWJhc2UgY3JlYXRpbmcgZmlyc3QgImxpbmsgdmVj dG9yIHByb3RvY29sIiAhDQoNCkZvciBzdGFydCBJIGhhdmUgZmV3IHF1ZXN0aW9uczoNCg0KUTE6 DQoNClJGQzc3NTIgaGFzIGdvbmUgdmlhIGxvdCBvZiBlZmZvcnRzIChlc3BlY2lhbGx5IHNlY3Rp b25zIDMuMiBhbmQgdXApIHRvIGluY2x1ZGUgbnVtYmVyIG9mIE9TUEYgb3IgSVNJUyBzcGVjaWZp YyBlbmNvZGluZ3MuIEluIHlvdXIgcHJvcG9zYWwgeW91IG1lbnRpb25lZCBPU1BGIHR3aWNlIGFu ZCBub3QgZXZlbiBvbmNlIElTSVMuIERvZXMgaXQgbWVhbiB0aGF0IHlvdSBhcmUgbm90IGdvaW5n IHRvIHVzZSBhbGwgZW5jb2RpbmcgZm9yIHNwZWNpZmljIElHUHMgYXMgZGVmaW5lZCBpbiBSRkM3 NzUyID8NCg0KV2UgYXJlIHVzaW5nIHRoZSBCR1AgUHJvdG9jb2wtSUQgZGVmaW5lZCBmb3IgQkdQ LUVQRS4gVGhlIElBTkEgcmVxdWVzdCB3aWxsIGJlIGdlbmVyYWxpemVkIGZyb20g4oCcQkdQLUVQ ReKAnSB0byDigJxCR1DigJ0gaW4gc3VwcG9ydCBvZiBTZWdtZW50IFJvdXRpbmcgYW5kIG90aGVy IGVuaGFuY2VtZW50cy4gVGhlIEJHUC1MUyBOTFJJIGFyZSBzcGVjaWZpYyBCR1AgYW5kIG5vdCBl aXRoZXIgSVMtSVMgb3IgT1NQRi4NCg0KDQpRMjoNCg0KV2hvIGNyZWF0ZXMgYW5kIG1haW50YWlu cyBMU0RCIGluIGVhY2ggQkdQIHNwZWFrZXIgPyBBcmUgeW91IHBsYW5uaW5nIHRvIHJ1biBPU1BG IGFuZCBvciBJU0lTIGV4Y2VwdCBkaXNhYmxlIGl0IHRvIGVzdGFibGlzaCBhbnkgYWRqYWNpZW5j aWVzID8NCg0KSeKAmXZlIHNlZW4gZGVzaWducyBsaWtlIHRoaXMgaW4gbXkgdGltZSBidXQgaGF2 ZSBuZXZlciBiZWVuIG9mIGEgZmFuIG9mIHRoZW0gO14pLiBCR1Agd2lsbCBkbyB0aGUgU1BGIGRp cmVjdGx5IGFuZCBtYWludGFpbiB0aGUgU1BULiBZb3XigJlsbCBub3RlIHRoYXQgYSBzaW1wbGlm aWVkIFNQRiBpcyBhbHJlYWR5IGRvbmUgZm9yIE9SUi4NCg0KDQpRMzoNCg0KQ3VycmVudGx5IHRo ZXJlIGFyZSBhbHJlYWR5IHRvIG1vZGVscyB0byBidWlsZCBEQ3Mgd2l0aCBCR1AgLi4uIG9uZSB1 c2VzIEJHUCB0byBjcmVhdGUgb25seSBsZWFuIHVuZGVybGF5IHRoZSBvdGhlciBpcyB0byB1c2Ug QkdQIGZvciBib3RoIHVuZGVybGF5IGFuZCB0ZW5hbnRzIChleGFtcGxlIHByb2plY3QgQ2FsaWNv IGZvciB0aGUgbGF0dGVyKS4gV2l0aCB0aGF0IHNjYWxlIHdpc2UgSSB0aGluayB5b3VyIHByb3Bv c2FsIHdpbGwgd29yayBncmVhdCBmb3IgdGhlIGZvcm1lci4gSG93ZXZlciBJIGRvIGhhdmUgY29u Y2VybnMgYWJvdXQgdXNpbmcgeW91ciBtb2RlbCBmb3IgdGhlIGxhdHRlciB3aGVyZSBzYXkgMTAs MDAwIG9yIDEwMCwwMDAgLzMycyBvciAvMTI4cyBmcm9tIGVhY2ggVk1zIGFyZSBpbmplY3RlZCBh bmQgeW91IG5lZWQgdG8gY29uc3RydWN0IFNQVCB3aXRoIGFsbCBvZiB0aG9zZS4NCg0KU2ltaWxh ciB0byB0aG9zZSBkZXNpZ25zLCB0aGUgU1BUIGNvdWxkIGJlIGxpbWl0ZWQgdG8gdGhlIHVuZGVy bGF5LiBIb3dldmVyLCBpZiB0aGVyZSBpcyBubyByZXF1aXJlbWVudCBmb3IgdGhlIGJlbmVmaXRz IG9mIEwyIG9yIEwzIFZQTnMsIEkgc2VlIG5vIHJlYXNvbiB3aHkgdGhlc2UgMTAwS3Mgb2YgbGVh ZnMgVk0gcHJlZml4ZXMgaW4gREMgY2VudGVyIGNvdWxkbuKAmXQgYmUgc3VwcG9ydGVkLg0KDQoN ClE0Og0KDQpSZWxhdGVkIHRvIFEzIGluIHlvdXIgbW9kZWwgYW5kIHNheSBmbGF0IERDIHJvdXRp bmcgZWFjaCBjb21wdXRlIG5vZGUgb3RoZXIgdGhlbiBqdXN0IGluamVjdGluZyAxMHMgb2YgLzMy cyBhbmQgYmVpbmcgImRvbmUiIG5vdyBiZWNvbWVzIGFuIElHUCBub2RlLiBTaW5jZSB5b3VyIGRv Y3VtZW50IGV4cGxpY2l0ZWx5IHRhcmdldHMgTWFzc2l2ZWx5IFNjYWxlZCBEYXRhIENlbnRlcnMg KE1TRENzKSBJIGFtIGNvbmNlcm5lZCB0aGF0IGhhdmluZyAxMDAsMDAwKyBJR1Agbm9kZXMgYW5k IGluIG1hbnkgY2FzZSBtdWNoIG1vcmUgaXMgbm90IHRoZSBiZXN0IGlkZWEuDQoNCjEwMEsrIHN3 aXRjaGVzIGluIGEgc2luZ2xlIERDIGZhYnJpYyAoaS5lLiwgQkdQIHJvdXRpbmcgZG9tYWluKT8g SSBoYXZlIHNvbWUgZXhwZXJpZW5jZSBpbiBsaW5rLXN0YXRlIHByb3RvY29scyBhbmQgSSBjYW4g dGVsbCB5b3UgdGhhdCBPU1BGIGlzIEkvTyBib3VuZCBtYWlubHkgZHVlIHRvIHRoZSBmbG9vZGlu Zy4gSWYgZG9uZSByaWdodCwgdGhlIFNQRiBjYWxjdWxhdGlvbiBjYW4gYmUgZG9uZSB3aXRoIG1p bmltYWwgY29tcHV0YXRpb24uIFdoaWxlIEJHUC1MUyBpc27igJl0IHRoZSB3b3JsZCdzIG1vc3Qg Y29tcGFjdCBlbmNvZGluZywgaXQgaXMgY29tcGxldGVseSBpbmNyZW1lbnRhbC4NCg0KDQpRNToN Cg0KSGF2ZSB5b3UgY29uc2lkZXJlZCBqdXN0IHByb3Bvc2luZyBhbiBPU1BGIHJvdXRlIHJlZmxl Y3RvciBpbnN0ZWFkIHdpdGhvdXQgc3R1ZmZpbmcgQkdQIGludG8gdGhlIG1peCA/IEFzIHNvbWUg b2YgeW91IHBlcmhhcHMgcmVtZW1iZXIgdGhlIHdvcmsgb24gdGhpcyBzdGFydGVkIGFyb3VuZCB5 ZWFyIDIwMDAgdG8gb3B0aW1pemUgUEUtQ0UgQ1NDIGRlcGxveW1lbnRzIDopIEl0IHNlZW1zIHRv IG1lIHZlcnkgcmV1c2FibGUgZm9yIHRoaXMgZ29hbC4NCg0KV2UgbG9va2VkIGF0IGxvdHMgb2Yg YWx0ZXJuYXRpdmVzIGFuZCB0aGlzIG9uZSBzZWVtZWQgbGlrZSB0aGUgYmVzdCBvbmUuIFBsZWFz ZSBwYXNzIG1lIGEgcG9pbnRlciB0byB0aGUgd29yayB5b3UgbWVudGlvbi4NCg0KVGhhbmtzLA0K QWNlZQ0KDQoNCg0KQmVzdCByZWdhcmRzLA0KUm9iZXJ0Lg0KDQo= --_000_D3A547856931Eaceeciscocom_ Content-Type: text/html; charset="utf-8" Content-ID: Content-Transfer-Encoding: base64 PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsiPg0KPGRpdiBzdHlsZT0iY29sb3I6IHJnYigwLCAwLCAw KTsgZm9udC1mYW1pbHk6IENhbGlicmksIHNhbnMtc2VyaWY7IGZvbnQtc2l6ZTogMTRweDsiPg0K SGkgUm9iZXJ0LCZuYnNwOzwvZGl2Pg0KPGRpdiBzdHlsZT0iY29sb3I6IHJnYigwLCAwLCAwKTsg Zm9udC1mYW1pbHk6IENhbGlicmksIHNhbnMtc2VyaWY7IGZvbnQtc2l6ZTogMTRweDsiPg0KPGJy Pg0KPC9kaXY+DQo8ZGl2IHN0eWxlPSJjb2xvcjogcmdiKDAsIDAsIDApOyBmb250LWZhbWlseTog Q2FsaWJyaSwgc2Fucy1zZXJpZjsgZm9udC1zaXplOiAxNHB4OyI+DQpUaGFua3MgZm9yIGVuZ2Fn aW5n4oCmPC9kaXY+DQo8ZGl2IHN0eWxlPSJjb2xvcjogcmdiKDAsIDAsIDApOyBmb250LWZhbWls eTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsgZm9udC1zaXplOiAxNHB4OyI+DQo8YnI+DQo8L2Rpdj4N CjxzcGFuIGlkPSJPTEtfU1JDX0JPRFlfU0VDVElPTiIgc3R5bGU9ImNvbG9yOiByZ2IoMCwgMCwg MCk7IGZvbnQtZmFtaWx5OiBDYWxpYnJpLCBzYW5zLXNlcmlmOyBmb250LXNpemU6IDE0cHg7Ij4N CjxkaXYgc3R5bGU9ImZvbnQtZmFtaWx5OkNhbGlicmk7IGZvbnQtc2l6ZToxMXB0OyB0ZXh0LWFs aWduOmxlZnQ7IGNvbG9yOmJsYWNrOyBCT1JERVItQk9UVE9NOiBtZWRpdW0gbm9uZTsgQk9SREVS LUxFRlQ6IG1lZGl1bSBub25lOyBQQURESU5HLUJPVFRPTTogMGluOyBQQURESU5HLUxFRlQ6IDBp bjsgUEFERElORy1SSUdIVDogMGluOyBCT1JERVItVE9QOiAjYjVjNGRmIDFwdCBzb2xpZDsgQk9S REVSLVJJR0hUOiBtZWRpdW0gbm9uZTsgUEFERElORy1UT1A6IDNwdCI+DQo8c3BhbiBzdHlsZT0i Zm9udC13ZWlnaHQ6Ym9sZCI+RnJvbTogPC9zcGFuPiZsdDs8YSBocmVmPSJtYWlsdG86cnJhc3p1 a0BnbWFpbC5jb20iPnJyYXN6dWtAZ21haWwuY29tPC9hPiZndDsgb24gYmVoYWxmIG9mIFJvYmVy dCBSYXN6dWsgJmx0OzxhIGhyZWY9Im1haWx0bzpyb2JlcnRAcmFzenVrLm5ldCI+cm9iZXJ0QHJh c3p1ay5uZXQ8L2E+Jmd0Ozxicj4NCjxzcGFuIHN0eWxlPSJmb250LXdlaWdodDpib2xkIj5EYXRl OiA8L3NwYW4+RnJpZGF5LCBKdWx5IDgsIDIwMTYgYXQgMTE6NTEgQU08YnI+DQo8c3BhbiBzdHls ZT0iZm9udC13ZWlnaHQ6Ym9sZCI+VG86IDwvc3Bhbj4mcXVvdDtLZXl1ciBQYXRlbCAoa2V5dXBh dGUpJnF1b3Q7ICZsdDs8YSBocmVmPSJtYWlsdG86a2V5dXBhdGVAY2lzY28uY29tIj5rZXl1cGF0 ZUBjaXNjby5jb208L2E+Jmd0OywgQWNlZSBMaW5kZW0gJmx0OzxhIGhyZWY9Im1haWx0bzphY2Vl QGNpc2NvLmNvbSI+YWNlZUBjaXNjby5jb208L2E+Jmd0OywgJnF1b3Q7QWJoYXkgUm95IChha3Ip JnF1b3Q7ICZsdDs8YSBocmVmPSJtYWlsdG86YWtyQGNpc2NvLmNvbSI+YWtyQGNpc2NvLmNvbTwv YT4mZ3Q7LA0KICZxdW90O0RlcmVrIE1hbi1LaXQgWWV1bmcgKG15ZXVuZykmcXVvdDsgJmx0Ozxh IGhyZWY9Im1haWx0bzpteWV1bmdAY2lzY28uY29tIj5teWV1bmdAY2lzY28uY29tPC9hPiZndDss ICZxdW90O1ZlbnUgVmVudWdvcGFsICh2ZW51dikmcXVvdDsgJmx0OzxhIGhyZWY9Im1haWx0bzp2 ZW51dkBjaXNjby5jb20iPnZlbnV2QGNpc2NvLmNvbTwvYT4mZ3Q7PGJyPg0KPHNwYW4gc3R5bGU9 ImZvbnQtd2VpZ2h0OmJvbGQiPkNjOiA8L3NwYW4+SURSIExpc3QgJmx0OzxhIGhyZWY9Im1haWx0 bzppZHJAaWV0Zi5vcmciPmlkckBpZXRmLm9yZzwvYT4mZ3Q7PGJyPg0KPHNwYW4gc3R5bGU9ImZv bnQtd2VpZ2h0OmJvbGQiPlN1YmplY3Q6IDwvc3Bhbj5TaG9ydGVzdCBQYXRoIFJvdXRpbmcgRXh0 ZW5zaW9ucyBmb3IgQkdQIFByb3RvY29sPGJyPg0KPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0K PGJsb2NrcXVvdGUgaWQ9Ik1BQ19PVVRMT09LX0FUVFJJQlVUSU9OX0JMT0NLUVVPVEUiIHN0eWxl PSJCT1JERVItTEVGVDogI2I1YzRkZiA1IHNvbGlkOyBQQURESU5HOjAgMCAwIDU7IE1BUkdJTjow IDAgMCA1OyI+DQo8ZGl2Pg0KPGRpdj4NCjxkaXYgZGlyPSJsdHIiPg0KPGRpdiBjbGFzcz0iZ21h aWxfZGVmYXVsdCIgc3R5bGU9ImZvbnQtZmFtaWx5OmFyaWFsLGhlbHZldGljYSxzYW5zLXNlcmlm O2ZvbnQtc2l6ZTpzbWFsbCI+DQpIaSw8L2Rpdj4NCjxkaXYgY2xhc3M9ImdtYWlsX2RlZmF1bHQi IHN0eWxlPSJmb250LWZhbWlseTphcmlhbCxoZWx2ZXRpY2Esc2Fucy1zZXJpZjtmb250LXNpemU6 c21hbGwiPg0KPGJyPg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSJnbWFpbF9kZWZhdWx0IiBzdHlsZT0i Zm9udC1mYW1pbHk6YXJpYWwsaGVsdmV0aWNhLHNhbnMtc2VyaWY7Zm9udC1zaXplOnNtYWxsIj4N CkkgaGF2ZSByZXZpZXdlZCB5b3VyIHByb3Bvc2FsLiZuYnNwOzwvZGl2Pg0KPGRpdiBjbGFzcz0i Z21haWxfZGVmYXVsdCIgc3R5bGU9ImZvbnQtZmFtaWx5OmFyaWFsLGhlbHZldGljYSxzYW5zLXNl cmlmO2ZvbnQtc2l6ZTpzbWFsbCI+DQo8YnI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9ImdtYWlsX2Rl ZmF1bHQiIHN0eWxlPSJmb250LWZhbWlseTphcmlhbCxoZWx2ZXRpY2Esc2Fucy1zZXJpZjtmb250 LXNpemU6c21hbGwiPg0KVHVybmluZyBwYXRoIHZlY3RvciBvciBkaXN0YW5jZSB2ZWN0b3IgcHJv dG9jb2wgaW50byBsaW5rIHN0YXRlIGNhcnJpZXIgaXMgbm8gZG91YnQgYSBib2xkIGlkZWEgOiku PC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L3NwYW4+DQo8 ZGl2IHN0eWxlPSJjb2xvcjogcmdiKDAsIDAsIDApOyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fu cy1zZXJpZjsgZm9udC1zaXplOiAxNHB4OyI+DQo8YnI+DQo8L2Rpdj4NCjxkaXY+PGZvbnQgZmFj ZT0iQ2FsaWJyaSxzYW5zLXNlcmlmIj7igJxGb3J0dW5lIGJlZnJpZW5kcyB0aGUgYm9sZC7igJ0g LUVtaWx5IERpY2tpbnNvbjwvZm9udD48L2Rpdj4NCjxkaXYgc3R5bGU9ImNvbG9yOiByZ2IoMCwg MCwgMCk7IGZvbnQtZmFtaWx5OiBDYWxpYnJpLCBzYW5zLXNlcmlmOyBmb250LXNpemU6IDE0cHg7 Ij4NCjxicj4NCjwvZGl2Pg0KPHNwYW4gaWQ9Ik9MS19TUkNfQk9EWV9TRUNUSU9OIiBzdHlsZT0i Y29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1mYW1pbHk6IENhbGlicmksIHNhbnMtc2VyaWY7IGZv bnQtc2l6ZTogMTRweDsiPg0KPGJsb2NrcXVvdGUgaWQ9Ik1BQ19PVVRMT09LX0FUVFJJQlVUSU9O X0JMT0NLUVVPVEUiIHN0eWxlPSJCT1JERVItTEVGVDogI2I1YzRkZiA1IHNvbGlkOyBQQURESU5H OjAgMCAwIDU7IE1BUkdJTjowIDAgMCA1OyI+DQo8ZGl2Pg0KPGRpdj4NCjxkaXYgZGlyPSJsdHIi Pg0KPGRpdiBjbGFzcz0iZ21haWxfZGVmYXVsdCIgc3R5bGU9ImZvbnQtZmFtaWx5OmFyaWFsLGhl bHZldGljYSxzYW5zLXNlcmlmO2ZvbnQtc2l6ZTpzbWFsbCI+DQo8YnI+DQo8L2Rpdj4NCjxkaXYg Y2xhc3M9ImdtYWlsX2RlZmF1bHQiIHN0eWxlPSJmb250LWZhbWlseTphcmlhbCxoZWx2ZXRpY2Es c2Fucy1zZXJpZjtmb250LXNpemU6c21hbGwiPg0KRWZmZWN0aXZlbHkgd2hhdCB5b3UgYXJlIHBy b3Bvc2luZyBpcyB0byB1c2UgQkdQIFRDUCBzZXNzaW9ucyB0byBwcm9wYWdhdGUgbGluayBzdGF0 ZSBkYXRhYmFzZSBjcmVhdGluZyBmaXJzdCAmcXVvdDtsaW5rIHZlY3RvciBwcm90b2NvbCZxdW90 OyAhPC9kaXY+DQo8ZGl2IGNsYXNzPSJnbWFpbF9kZWZhdWx0IiBzdHlsZT0iZm9udC1mYW1pbHk6 YXJpYWwsaGVsdmV0aWNhLHNhbnMtc2VyaWY7Zm9udC1zaXplOnNtYWxsIj4NCjxicj4NCjwvZGl2 Pg0KPGRpdiBjbGFzcz0iZ21haWxfZGVmYXVsdCIgc3R5bGU9ImZvbnQtZmFtaWx5OmFyaWFsLGhl bHZldGljYSxzYW5zLXNlcmlmO2ZvbnQtc2l6ZTpzbWFsbCI+DQpGb3Igc3RhcnQgSSBoYXZlIGZl dyBxdWVzdGlvbnM6PC9kaXY+DQo8ZGl2IGNsYXNzPSJnbWFpbF9kZWZhdWx0IiBzdHlsZT0iZm9u dC1mYW1pbHk6YXJpYWwsaGVsdmV0aWNhLHNhbnMtc2VyaWY7Zm9udC1zaXplOnNtYWxsIj4NCjxi cj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iZ21haWxfZGVmYXVsdCIgc3R5bGU9ImZvbnQtZmFtaWx5 OmFyaWFsLGhlbHZldGljYSxzYW5zLXNlcmlmO2ZvbnQtc2l6ZTpzbWFsbCI+DQpRMTombmJzcDs8 L2Rpdj4NCjxkaXYgY2xhc3M9ImdtYWlsX2RlZmF1bHQiIHN0eWxlPSJmb250LWZhbWlseTphcmlh bCxoZWx2ZXRpY2Esc2Fucy1zZXJpZjtmb250LXNpemU6c21hbGwiPg0KPGJyPg0KPC9kaXY+DQo8 ZGl2IGNsYXNzPSJnbWFpbF9kZWZhdWx0IiBzdHlsZT0iZm9udC1mYW1pbHk6YXJpYWwsaGVsdmV0 aWNhLHNhbnMtc2VyaWY7Zm9udC1zaXplOnNtYWxsIj4NClJGQzc3NTIgaGFzIGdvbmUgdmlhIGxv dCBvZiBlZmZvcnRzIChlc3BlY2lhbGx5IHNlY3Rpb25zIDMuMiBhbmQgdXApIHRvIGluY2x1ZGUg bnVtYmVyIG9mIE9TUEYgb3IgSVNJUyBzcGVjaWZpYyBlbmNvZGluZ3MuIEluIHlvdXIgcHJvcG9z YWwgeW91IG1lbnRpb25lZCBPU1BGIHR3aWNlIGFuZCBub3QgZXZlbiBvbmNlIElTSVMuIERvZXMg aXQgbWVhbiB0aGF0IHlvdSBhcmUgbm90IGdvaW5nIHRvIHVzZSBhbGwgZW5jb2RpbmcgZm9yIHNw ZWNpZmljDQogSUdQcyBhcyBkZWZpbmVkIGluIFJGQzc3NTIgPyZuYnNwOzwvZGl2Pg0KPC9kaXY+ DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9zcGFuPg0KPGRpdj48YnI+DQo8L2Rp dj4NCjxkaXY+V2UgYXJlIHVzaW5nIHRoZSBCR1AgUHJvdG9jb2wtSUQgZGVmaW5lZCBmb3IgQkdQ LUVQRS4gVGhlIElBTkEgcmVxdWVzdCB3aWxsIGJlIGdlbmVyYWxpemVkIGZyb20g4oCcQkdQLUVQ ReKAnSB0byDigJxCR1DigJ0gaW4gc3VwcG9ydCBvZiBTZWdtZW50IFJvdXRpbmcgYW5kIG90aGVy IGVuaGFuY2VtZW50cy4gVGhlIEJHUC1MUyBOTFJJIGFyZSBzcGVjaWZpYyBCR1AgYW5kIG5vdCBl aXRoZXIgSVMtSVMgb3IgT1NQRi4mbmJzcDs8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8c3Bh biBpZD0iT0xLX1NSQ19CT0RZX1NFQ1RJT04iIHN0eWxlPSJjb2xvcjogcmdiKDAsIDAsIDApOyBm b250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsgZm9udC1zaXplOiAxNHB4OyI+DQo8Ymxv Y2txdW90ZSBpZD0iTUFDX09VVExPT0tfQVRUUklCVVRJT05fQkxPQ0tRVU9URSIgc3R5bGU9IkJP UkRFUi1MRUZUOiAjYjVjNGRmIDUgc29saWQ7IFBBRERJTkc6MCAwIDAgNTsgTUFSR0lOOjAgMCAw IDU7Ij4NCjxkaXY+DQo8ZGl2Pg0KPGRpdiBkaXI9Imx0ciI+DQo8ZGl2IGNsYXNzPSJnbWFpbF9k ZWZhdWx0IiBzdHlsZT0iZm9udC1mYW1pbHk6YXJpYWwsaGVsdmV0aWNhLHNhbnMtc2VyaWY7Zm9u dC1zaXplOnNtYWxsIj4NCjxicj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iZ21haWxfZGVmYXVsdCIg c3R5bGU9ImZvbnQtZmFtaWx5OmFyaWFsLGhlbHZldGljYSxzYW5zLXNlcmlmO2ZvbnQtc2l6ZTpz bWFsbCI+DQpRMjombmJzcDs8L2Rpdj4NCjxkaXYgY2xhc3M9ImdtYWlsX2RlZmF1bHQiIHN0eWxl PSJmb250LWZhbWlseTphcmlhbCxoZWx2ZXRpY2Esc2Fucy1zZXJpZjtmb250LXNpemU6c21hbGwi Pg0KPGJyPg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSJnbWFpbF9kZWZhdWx0IiBzdHlsZT0iZm9udC1m YW1pbHk6YXJpYWwsaGVsdmV0aWNhLHNhbnMtc2VyaWY7Zm9udC1zaXplOnNtYWxsIj4NCldobyBj cmVhdGVzIGFuZCBtYWludGFpbnMgTFNEQiBpbiBlYWNoIEJHUCBzcGVha2VyID8gQXJlIHlvdSBw bGFubmluZyB0byBydW4gT1NQRiBhbmQgb3IgSVNJUyBleGNlcHQgZGlzYWJsZSBpdCB0byBlc3Rh Ymxpc2ggYW55IGFkamFjaWVuY2llcyA/Jm5ic3A7PC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9k aXY+DQo8L2Jsb2NrcXVvdGU+DQo8L3NwYW4+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5J4oCZ dmUgc2VlbiBkZXNpZ25zIGxpa2UgdGhpcyBpbiBteSB0aW1lIGJ1dCBoYXZlIG5ldmVyIGJlZW4g b2YgYSBmYW4gb2YgdGhlbSA7XikuIEJHUCB3aWxsIGRvIHRoZSBTUEYgZGlyZWN0bHkgYW5kIG1h aW50YWluIHRoZSBTUFQuIFlvdeKAmWxsIG5vdGUgdGhhdCBhIHNpbXBsaWZpZWQgU1BGIGlzIGFs cmVhZHkgZG9uZSBmb3IgT1JSLiZuYnNwOzwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxzcGFu IGlkPSJPTEtfU1JDX0JPRFlfU0VDVElPTiIgc3R5bGU9ImNvbG9yOiByZ2IoMCwgMCwgMCk7IGZv bnQtZmFtaWx5OiBDYWxpYnJpLCBzYW5zLXNlcmlmOyBmb250LXNpemU6IDE0cHg7Ij4NCjxibG9j a3F1b3RlIGlkPSJNQUNfT1VUTE9PS19BVFRSSUJVVElPTl9CTE9DS1FVT1RFIiBzdHlsZT0iQk9S REVSLUxFRlQ6ICNiNWM0ZGYgNSBzb2xpZDsgUEFERElORzowIDAgMCA1OyBNQVJHSU46MCAwIDAg NTsiPg0KPGRpdj4NCjxkaXY+DQo8ZGl2IGRpcj0ibHRyIj4NCjxkaXYgY2xhc3M9ImdtYWlsX2Rl ZmF1bHQiIHN0eWxlPSJmb250LWZhbWlseTphcmlhbCxoZWx2ZXRpY2Esc2Fucy1zZXJpZjtmb250 LXNpemU6c21hbGwiPg0KPGJyPg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSJnbWFpbF9kZWZhdWx0IiBz dHlsZT0iZm9udC1mYW1pbHk6YXJpYWwsaGVsdmV0aWNhLHNhbnMtc2VyaWY7Zm9udC1zaXplOnNt YWxsIj4NClEzOiZuYnNwOzwvZGl2Pg0KPGRpdiBjbGFzcz0iZ21haWxfZGVmYXVsdCIgc3R5bGU9 ImZvbnQtZmFtaWx5OmFyaWFsLGhlbHZldGljYSxzYW5zLXNlcmlmO2ZvbnQtc2l6ZTpzbWFsbCI+ DQo8YnI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9ImdtYWlsX2RlZmF1bHQiIHN0eWxlPSJmb250LWZh bWlseTphcmlhbCxoZWx2ZXRpY2Esc2Fucy1zZXJpZjtmb250LXNpemU6c21hbGwiPg0KQ3VycmVu dGx5IHRoZXJlIGFyZSBhbHJlYWR5IHRvIG1vZGVscyB0byBidWlsZCBEQ3Mgd2l0aCBCR1AgLi4u IG9uZSB1c2VzIEJHUCB0byBjcmVhdGUgb25seSBsZWFuIHVuZGVybGF5IHRoZSBvdGhlciBpcyB0 byB1c2UgQkdQIGZvciBib3RoIHVuZGVybGF5IGFuZCB0ZW5hbnRzIChleGFtcGxlIHByb2plY3Qg Q2FsaWNvIGZvciB0aGUgbGF0dGVyKS4gV2l0aCB0aGF0IHNjYWxlIHdpc2UgSSB0aGluayB5b3Vy IHByb3Bvc2FsIHdpbGwgd29yayBncmVhdA0KIGZvciB0aGUgZm9ybWVyLiBIb3dldmVyIEkgZG8g aGF2ZSBjb25jZXJucyBhYm91dCB1c2luZyB5b3VyIG1vZGVsIGZvciB0aGUgbGF0dGVyIHdoZXJl IHNheSAxMCwwMDAgb3IgMTAwLDAwMCAvMzJzIG9yIC8xMjhzIGZyb20gZWFjaCBWTXMgYXJlIGlu amVjdGVkIGFuZCB5b3UgbmVlZCB0byBjb25zdHJ1Y3QgU1BUIHdpdGggYWxsIG9mIHRob3NlLiZu YnNwOzwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9zcGFu Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+U2ltaWxhciB0byB0aG9zZSBkZXNpZ25zLCB0aGUg U1BUIGNvdWxkIGJlIGxpbWl0ZWQgdG8gdGhlIHVuZGVybGF5LiBIb3dldmVyLCBpZiB0aGVyZSBp cyBubyByZXF1aXJlbWVudCBmb3IgdGhlIGJlbmVmaXRzIG9mIEwyIG9yIEwzIFZQTnMsIEkgc2Vl IG5vIHJlYXNvbiB3aHkgdGhlc2UgMTAwS3Mgb2YgbGVhZnMgVk0gcHJlZml4ZXMgaW4gREMgY2Vu dGVyIGNvdWxkbuKAmXQgYmUgc3VwcG9ydGVkLiZuYnNwOzwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rp dj4NCjxzcGFuIGlkPSJPTEtfU1JDX0JPRFlfU0VDVElPTiIgc3R5bGU9ImNvbG9yOiByZ2IoMCwg MCwgMCk7IGZvbnQtZmFtaWx5OiBDYWxpYnJpLCBzYW5zLXNlcmlmOyBmb250LXNpemU6IDE0cHg7 Ij4NCjxibG9ja3F1b3RlIGlkPSJNQUNfT1VUTE9PS19BVFRSSUJVVElPTl9CTE9DS1FVT1RFIiBz dHlsZT0iQk9SREVSLUxFRlQ6ICNiNWM0ZGYgNSBzb2xpZDsgUEFERElORzowIDAgMCA1OyBNQVJH SU46MCAwIDAgNTsiPg0KPGRpdj4NCjxkaXY+DQo8ZGl2IGRpcj0ibHRyIj4NCjxkaXYgY2xhc3M9 ImdtYWlsX2RlZmF1bHQiIHN0eWxlPSJmb250LWZhbWlseTphcmlhbCxoZWx2ZXRpY2Esc2Fucy1z ZXJpZjtmb250LXNpemU6c21hbGwiPg0KPGJyPg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSJnbWFpbF9k ZWZhdWx0IiBzdHlsZT0iZm9udC1mYW1pbHk6YXJpYWwsaGVsdmV0aWNhLHNhbnMtc2VyaWY7Zm9u dC1zaXplOnNtYWxsIj4NClE0OiZuYnNwOzxicj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iZ21haWxf ZGVmYXVsdCIgc3R5bGU9ImZvbnQtZmFtaWx5OmFyaWFsLGhlbHZldGljYSxzYW5zLXNlcmlmO2Zv bnQtc2l6ZTpzbWFsbCI+DQo8YnI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9ImdtYWlsX2RlZmF1bHQi IHN0eWxlPSJmb250LWZhbWlseTphcmlhbCxoZWx2ZXRpY2Esc2Fucy1zZXJpZjtmb250LXNpemU6 c21hbGwiPg0KUmVsYXRlZCB0byBRMyBpbiB5b3VyIG1vZGVsIGFuZCBzYXkgZmxhdCBEQyByb3V0 aW5nIGVhY2ggY29tcHV0ZSBub2RlIG90aGVyIHRoZW4ganVzdCBpbmplY3RpbmcgMTBzIG9mIC8z MnMgYW5kIGJlaW5nICZxdW90O2RvbmUmcXVvdDsgbm93IGJlY29tZXMgYW4gSUdQIG5vZGUuIFNp bmNlIHlvdXIgZG9jdW1lbnQgZXhwbGljaXRlbHkgdGFyZ2V0cyZuYnNwO01hc3NpdmVseSBTY2Fs ZWQgRGF0YSBDZW50ZXJzIChNU0RDcykgSSBhbSBjb25jZXJuZWQgdGhhdCBoYXZpbmcgMTAwLDAw MCYjNDM7DQogSUdQIG5vZGVzIGFuZCBpbiBtYW55IGNhc2UgbXVjaCBtb3JlIGlzIG5vdCB0aGUg YmVzdCBpZGVhLiZuYnNwOzwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1 b3RlPg0KPC9zcGFuPg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+MTAwSyYjNDM7IHN3aXRjaGVz IGluIGEgc2luZ2xlIERDIGZhYnJpYyAoaS5lLiwgQkdQIHJvdXRpbmcgZG9tYWluKT8gSSBoYXZl IHNvbWUgZXhwZXJpZW5jZSBpbiBsaW5rLXN0YXRlIHByb3RvY29scyBhbmQgSSBjYW4gdGVsbCB5 b3UgdGhhdCBPU1BGIGlzIEkvTyBib3VuZCBtYWlubHkgZHVlIHRvIHRoZSBmbG9vZGluZy4gSWYg ZG9uZSByaWdodCwgdGhlIFNQRiBjYWxjdWxhdGlvbiBjYW4gYmUgZG9uZSB3aXRoIG1pbmltYWwg Y29tcHV0YXRpb24uDQogV2hpbGUgQkdQLUxTIGlzbuKAmXQgdGhlIHdvcmxkJ3MgbW9zdCBjb21w YWN0IGVuY29kaW5nLCBpdCBpcyBjb21wbGV0ZWx5IGluY3JlbWVudGFsLiZuYnNwOzwvZGl2Pg0K PGRpdj48YnI+DQo8L2Rpdj4NCjxzcGFuIGlkPSJPTEtfU1JDX0JPRFlfU0VDVElPTiIgc3R5bGU9 ImNvbG9yOiByZ2IoMCwgMCwgMCk7IGZvbnQtZmFtaWx5OiBDYWxpYnJpLCBzYW5zLXNlcmlmOyBm b250LXNpemU6IDE0cHg7Ij4NCjxibG9ja3F1b3RlIGlkPSJNQUNfT1VUTE9PS19BVFRSSUJVVElP Tl9CTE9DS1FVT1RFIiBzdHlsZT0iQk9SREVSLUxFRlQ6ICNiNWM0ZGYgNSBzb2xpZDsgUEFERElO RzowIDAgMCA1OyBNQVJHSU46MCAwIDAgNTsiPg0KPGRpdj4NCjxkaXY+DQo8ZGl2IGRpcj0ibHRy Ij4NCjxkaXYgY2xhc3M9ImdtYWlsX2RlZmF1bHQiIHN0eWxlPSJmb250LWZhbWlseTphcmlhbCxo ZWx2ZXRpY2Esc2Fucy1zZXJpZjtmb250LXNpemU6c21hbGwiPg0KPGJyPg0KPC9kaXY+DQo8ZGl2 IGNsYXNzPSJnbWFpbF9kZWZhdWx0IiBzdHlsZT0iZm9udC1mYW1pbHk6YXJpYWwsaGVsdmV0aWNh LHNhbnMtc2VyaWY7Zm9udC1zaXplOnNtYWxsIj4NClE1OiZuYnNwOzwvZGl2Pg0KPGRpdiBjbGFz cz0iZ21haWxfZGVmYXVsdCIgc3R5bGU9ImZvbnQtZmFtaWx5OmFyaWFsLGhlbHZldGljYSxzYW5z LXNlcmlmO2ZvbnQtc2l6ZTpzbWFsbCI+DQo8YnI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9ImdtYWls X2RlZmF1bHQiIHN0eWxlPSJmb250LWZhbWlseTphcmlhbCxoZWx2ZXRpY2Esc2Fucy1zZXJpZjtm b250LXNpemU6c21hbGwiPg0KSGF2ZSB5b3UgY29uc2lkZXJlZCBqdXN0IHByb3Bvc2luZyBhbiBP U1BGIHJvdXRlIHJlZmxlY3RvciBpbnN0ZWFkIHdpdGhvdXQgc3R1ZmZpbmcgQkdQIGludG8gdGhl IG1peCA/IEFzIHNvbWUgb2YgeW91IHBlcmhhcHMgcmVtZW1iZXIgdGhlIHdvcmsgb24gdGhpcyBz dGFydGVkIGFyb3VuZCB5ZWFyIDIwMDAgdG8gb3B0aW1pemUgUEUtQ0UgQ1NDIGRlcGxveW1lbnRz IDopIEl0IHNlZW1zIHRvIG1lIHZlcnkgcmV1c2FibGUgZm9yIHRoaXMgZ29hbC48L2Rpdj4NCjwv ZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvc3Bhbj4NCjxkaXY+PGJyPg0K PC9kaXY+DQo8ZGl2PldlIGxvb2tlZCBhdCBsb3RzIG9mIGFsdGVybmF0aXZlcyBhbmQgdGhpcyBv bmUgc2VlbWVkIGxpa2UgdGhlIGJlc3Qgb25lLiBQbGVhc2UgcGFzcyBtZSBhIHBvaW50ZXIgdG8g dGhlIHdvcmsgeW91IG1lbnRpb24uJm5ic3A7PC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRp dj5UaGFua3MsPC9kaXY+DQo8ZGl2PkFjZWUmbmJzcDs8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+ DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPHNwYW4gaWQ9Ik9MS19TUkNfQk9EWV9TRUNUSU9OIiBzdHls ZT0iY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1mYW1pbHk6IENhbGlicmksIHNhbnMtc2VyaWY7 IGZvbnQtc2l6ZTogMTRweDsiPg0KPGJsb2NrcXVvdGUgaWQ9Ik1BQ19PVVRMT09LX0FUVFJJQlVU SU9OX0JMT0NLUVVPVEUiIHN0eWxlPSJCT1JERVItTEVGVDogI2I1YzRkZiA1IHNvbGlkOyBQQURE SU5HOjAgMCAwIDU7IE1BUkdJTjowIDAgMCA1OyI+DQo8ZGl2Pg0KPGRpdj4NCjxkaXYgZGlyPSJs dHIiPg0KPGRpdiBjbGFzcz0iZ21haWxfZGVmYXVsdCIgc3R5bGU9ImZvbnQtZmFtaWx5OmFyaWFs LGhlbHZldGljYSxzYW5zLXNlcmlmO2ZvbnQtc2l6ZTpzbWFsbCI+DQo8YnI+DQo8L2Rpdj4NCjxk aXYgY2xhc3M9ImdtYWlsX2RlZmF1bHQiIHN0eWxlPSJmb250LWZhbWlseTphcmlhbCxoZWx2ZXRp Y2Esc2Fucy1zZXJpZjtmb250LXNpemU6c21hbGwiPg0KQmVzdCByZWdhcmRzLDwvZGl2Pg0KPGRp diBjbGFzcz0iZ21haWxfZGVmYXVsdCIgc3R5bGU9ImZvbnQtZmFtaWx5OmFyaWFsLGhlbHZldGlj YSxzYW5zLXNlcmlmO2ZvbnQtc2l6ZTpzbWFsbCI+DQpSb2JlcnQuPC9kaXY+DQo8ZGl2IGNsYXNz PSJnbWFpbF9kZWZhdWx0IiBzdHlsZT0iZm9udC1mYW1pbHk6YXJpYWwsaGVsdmV0aWNhLHNhbnMt c2VyaWY7Zm9udC1zaXplOnNtYWxsIj4NCjxicj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwv ZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9zcGFuPg0KPC9ib2R5Pg0KPC9odG1sPg0K --_000_D3A547856931Eaceeciscocom_-- From nobody Fri Jul 8 10:21:19 2016 Return-Path: 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 B494412D5C4; Fri, 8 Jul 2016 10:21:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.738 X-Spam-Level: * X-Spam-Status: No, score=1.738 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, RDNS_NONE=0.793] autolearn=no 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 1MXwVOtcDkn7; Fri, 8 Jul 2016 10:21:07 -0700 (PDT) Received: from hickoryhill-consulting.com (unknown [50.245.122.97]) (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 5AA5A12D589; Fri, 8 Jul 2016 10:21:06 -0700 (PDT) X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=74.43.47.72; From: "Susan Hares" To: "'Gunter Van De Velde'" References: <152e01d1d5ee$0c4c1320$24e43960$@ndzh.com> In-Reply-To: Date: Fri, 8 Jul 2016 13:20:34 -0400 Message-ID: <021301d1d93d$09ce1bf0$1d6a53d0$@ndzh.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQLN6h0I1kMMkzKOeCmbR8vdTJayoQIun9fSngUwyzA= Content-Language: en-us X-Authenticated-User: skh@ndzh.com Archived-At: Cc: idr@ietf.org, "'John G. Scudder'" , 'idr chairs' Subject: Re: [Idr] Presentation slot X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jul 2016 17:21:11 -0000 Gunter: You have a time slot. Sue -----Original Message----- From: Gunter Van De Velde [mailto:guntervandeveldecc@icloud.com] Sent: Friday, July 8, 2016 12:21 PM To: Susan Hares Cc: idr@ietf.org; idr chairs; John G. Scudder Subject: Re: [Idr] Presentation slot Hi Sue, John, As discussed the draft-vandevelde-idr-flowspec-path-redirect-03 has been posted and is now the merged document draft-vandevelde-idr-flowspec-path-redirect-02 and draft-li-idr-flowspec-redirect-generalized-sid-00 . Maybe a 5 minute slot to discuss the current state could be helpful for the WG. Brgds, G/ > On 04 Jul 2016, at 14:17, Susan Hares wrote: > > > IETF 96 is drawing near. For those who would like to present at IETF 96, please reply to this message (making sure to keep both chairs), and request a slot. > > Sue and John > _______________________________________________ > Idr mailing list > Idr@ietf.org > https://www.ietf.org/mailman/listinfo/idr From nobody Fri Jul 8 10:34:51 2016 Return-Path: X-Original-To: idr@ietf.org Delivered-To: idr@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 21A8F12D787; Fri, 8 Jul 2016 10:34:50 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.25.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20160708173450.32087.66387.idtracker@ietfa.amsl.com> Date: Fri, 08 Jul 2016 10:34:50 -0700 Archived-At: Cc: idr@ietf.org Subject: [Idr] I-D Action: draft-ietf-idr-as4octet-extcomm-generic-subtype-09.txt X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jul 2016 17:34:50 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Inter-Domain Routing of the IETF. Title : Generic Subtype for BGP Four-octet AS specific extended community Authors : Dhananjaya Rao Pradosh Mohapatra Jeffrey Haas Filename : draft-ietf-idr-as4octet-extcomm-generic-subtype-09.txt Pages : 6 Date : 2016-07-08 Abstract: Maintaining the current best practices with communities, ISPs and enterprises that are assigned a 4-octet AS number may want the BGP UPDATE messages they receive from their customers or peers to include a 4-octet AS specific BGP extended community. This document defines a new sub-type within the four-octet AS specific extended community to facilitate this practice. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-idr-as4octet-extcomm-generic-subtype/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-idr-as4octet-extcomm-generic-subtype-09 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-as4octet-extcomm-generic-subtype-09 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Fri Jul 8 12:46:12 2016 Return-Path: X-Original-To: idr@ietf.org Delivered-To: idr@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3446212D90F; Fri, 8 Jul 2016 12:45:50 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.25.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20160708194550.32201.86394.idtracker@ietfa.amsl.com> Date: Fri, 08 Jul 2016 12:45:50 -0700 Archived-At: Cc: idr@ietf.org Subject: [Idr] I-D Action: draft-ietf-idr-bgp-attribute-announcement-00.txt X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jul 2016 19:45:50 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Inter-Domain Routing of the IETF. Title : Constrain Attribute announcement within BGP Authors : Keyur Patel James Uttaro Bruno Decraene Wim Henderickx Jeff Haas Filename : draft-ietf-idr-bgp-attribute-announcement-00.txt Pages : 9 Date : 2016-07-08 Abstract: [RFC4271] defines four different categories of BGP Path attributes. The different Path attribute categories can be identified by the attribute flag values. These flags help identify if an attribute is optional or well-known, Transitive or non-Transitive, Partial, or of an Extended length type. BGP attribute announcement depends on whether an attribute is a well-known or optional, and whether an attribute is a transitive or non-transitive. BGP implementations MUST recognize all well-known attributes. The well-known attributes are always Transitive. It is not required for BGP implementations to recognise all the Optional attributes. The Optional attributes could be Transitive or Non-Transitive. BGP implementations MUST store and forward any Unknown Optional Transitive attributes and ignore and drop any Unknown Optional Non-Transitive attributes. Currently, there is no way to confine the scope of Path attributes within a given Autonomous System (AS) or a given BGP member-AS in Confederation. This draft defines attribute extensions that help confine the scope of Optional attributes within a given AS or a given BGP member-AS in Confederation The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-attribute-announcement/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-idr-bgp-attribute-announcement-00 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Fri Jul 8 14:32:36 2016 Return-Path: X-Original-To: idr@ietf.org Delivered-To: idr@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 670BE12D916; Fri, 8 Jul 2016 14:32:27 -0700 (PDT) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: "IETF-Announce" X-Test-IDTracker: no X-IETF-IDTracker: 6.25.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20160708213227.32135.69537.idtracker@ietfa.amsl.com> Date: Fri, 08 Jul 2016 14:32:27 -0700 Archived-At: Cc: idr@ietf.org, idr-chairs@ietf.org, The IESG , draft-ietf-idr-ix-bgp-route-server@ietf.org, shares@ndzh.com, rfc-editor@rfc-editor.org Subject: [Idr] Protocol Action: 'Internet Exchange BGP Route Server' to Proposed Standard (draft-ietf-idr-ix-bgp-route-server-12.txt) X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jul 2016 21:32:27 -0000 The IESG has approved the following document: - 'Internet Exchange BGP Route Server' (draft-ietf-idr-ix-bgp-route-server-12.txt) as Proposed Standard This document is the product of the Inter-Domain Routing Working Group. The IESG contact persons are Alvaro Retana, Alia Atlas and Deborah Brungard. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-idr-ix-bgp-route-server/ Technical Summary This document outlines a specification for multilateral interconnections at Internet exchange points (IXPs). Multilateral interconnection is a method of exchanging routing information between three or more external BGP speakers using a single intermediate broker system, referred to as a route server. Route servers are typically used on shared access media networks, such as Internet exchange points (IXPs), to facilitate simplified interconnection between multiple Internet routers. Working Group Summary The document has been discussed for 2-3 years in the IDR and the GROW working group. There is a "companion" document from the grow WG: draft-ietf-grow-ix-bgp-route-server-operations. Document Quality Yes, implementations from cisco, BIRD and Quaga exist. The details of an implementation report are here: http://trac.tools.ietf.org/wg/idr/trac/wiki/draft-ietf-idr-ix-bgp-route-server%20implementations Personnel Document Shepherd: Susan Hares Responsible AD: Alvaro Retana From nobody Fri Jul 8 14:35:35 2016 Return-Path: X-Original-To: idr@ietf.org Delivered-To: idr@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E85E12D928; Fri, 8 Jul 2016 14:35:34 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.25.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20160708213534.32176.47384.idtracker@ietfa.amsl.com> Date: Fri, 08 Jul 2016 14:35:34 -0700 Archived-At: Cc: idr@ietf.org Subject: [Idr] I-D Action: draft-ietf-idr-route-leak-detection-mitigation-04.txt X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jul 2016 21:35:34 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Inter-Domain Routing of the IETF. Title : Methods for Detection and Mitigation of BGP Route Leaks Authors : Kotikalapudi Sriram Doug Montgomery Brian Dickson Keyur Patel Andrei Robachevsky Filename : draft-ietf-idr-route-leak-detection-mitigation-04.txt Pages : 22 Date : 2016-07-08 Abstract: [I-D.ietf-grow-route-leak-problem-definition] provides a definition of the route leak problem, and also enumerates several types of route leaks. This document first examines which of those route-leak types are detected and mitigated by the existing origin validation (OV) [RFC 6811]. It is recognized that OV offers a limited detection and mitigation capability against route leaks. This document specifies enhancements that significantly extend the route-leak prevention, detection, and mitigation capabilities of BGP. One solution component involves carrying a per-hop route-leak protection (RLP) field in BGP updates. The RLP field is proposed be carried in a new optional transitive attribute, called BGP RLP attribute. The solution is meant to be initially implemented as an enhancement of BGP without requiring BGPsec [I-D.ietf-sidr-bgpsec-protocol]. However, when BGPsec is deployed in the future, the solution can be incorporated in BGPsec, enabling cryptographic protection for the RLP field. That would be one way of implementing the proposed solution in a secure way. The document also includes a stopgap method for detection and mitigation of route leaks for an intermediate phase when OV is deployed but BGP protocol on the wire is unchanged. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-idr-route-leak-detection-mitigation/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-idr-route-leak-detection-mitigation-04 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-route-leak-detection-mitigation-04 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Fri Jul 8 15:57:15 2016 Return-Path: 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 82AAD12D0A3; Fri, 8 Jul 2016 15:57:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -15.947 X-Spam-Level: X-Spam-Status: No, score=-15.947 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 WPGWWoVNfjhB; Fri, 8 Jul 2016 15:57:12 -0700 (PDT) Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E053C12B028; Fri, 8 Jul 2016 15:57:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=572; q=dns/txt; s=iport; t=1468018631; x=1469228231; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=rR366fFmPiyS57HnghpNGBag+cuE5JURlbV55mOZH10=; b=OnRZbPZDmf+6jWprq/Wz9/ppEnSifsu5KRBgRf9CwCvX70OX1Ikma/GD F3IucIo45RIMFw/P9Ux2DveEoVNwxus0BJ+lcdMIdPxIVmWoNyChmwBE7 t48XFa5ymUvOOchD1Gs1AJlNN8b5jY1b37PjyAB+fdOnXE2I8gxm8mz1S g=; X-IronPort-AV: E=Sophos;i="5.28,332,1464652800"; d="scan'208";a="293660187" Received: from alln-core-9.cisco.com ([173.36.13.129]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 08 Jul 2016 22:57:11 +0000 Received: from [10.41.57.152] ([10.41.57.152]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id u68MvAgv015794; Fri, 8 Jul 2016 22:57:10 GMT To: Susan Hares , "'John G. Scudder'" References: <152e01d1d5ee$0c4c1320$24e43960$@ndzh.com> From: Enke Chen Message-ID: <33a8ae6f-1498-f6bb-0135-7215eb7842be@cisco.com> Date: Fri, 8 Jul 2016 15:57:10 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: <152e01d1d5ee$0c4c1320$24e43960$@ndzh.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Archived-At: Cc: idr@ietf.org, Robert Raszuk , 'idr chairs' Subject: Re: [Idr] Presentation slot X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jul 2016 22:57:13 -0000 Hi, Sue and John: I would like to ask for 15-minutes to present the following draft at the upcoming IETF in Berlin: draft-chen-idr-geo-coordinates-01 Thanks. -- Enke On 7/4/16 5:17 AM, Susan Hares wrote: > > > IETF 96 is drawing near. For those who would like to present at IETF 96, please reply to this message (making sure to keep both chairs), and request a slot. > > > > Sue and John > > > > _______________________________________________ > Idr mailing list > Idr@ietf.org > https://www.ietf.org/mailman/listinfo/idr > From nobody Fri Jul 8 16:48:56 2016 Return-Path: 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 CC77D12D87C; Fri, 8 Jul 2016 16:48:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.738 X-Spam-Level: * X-Spam-Status: No, score=1.738 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, RDNS_NONE=0.793] autolearn=no 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 cHyA2DzW75BC; Fri, 8 Jul 2016 16:48:52 -0700 (PDT) Received: from hickoryhill-consulting.com (unknown [50.245.122.97]) (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 0EFDA12D896; Fri, 8 Jul 2016 16:48:51 -0700 (PDT) X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=74.43.47.20; From: "Susan Hares" To: "'Enke Chen'" , "'John G. Scudder'" References: <152e01d1d5ee$0c4c1320$24e43960$@ndzh.com> <33a8ae6f-1498-f6bb-0135-7215eb7842be@cisco.com> In-Reply-To: <33a8ae6f-1498-f6bb-0135-7215eb7842be@cisco.com> Date: Fri, 8 Jul 2016 19:48:17 -0400 Message-ID: <004d01d1d973$342ac660$9c805320$@ndzh.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQLN6h0I1kMMkzKOeCmbR8vdTJayoQKV8PvNngJiZcA= Content-Language: en-us X-Authenticated-User: skh@ndzh.com Archived-At: Cc: idr@ietf.org, 'Robert Raszuk' , 'idr chairs' Subject: Re: [Idr] Presentation slot X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jul 2016 23:48:54 -0000 Enke: I'm thrilled to have you presenting at IDR once again. Your slot will be between 10-15 minutes (depending on how crowded the agenda is). Sue -----Original Message----- From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Enke Chen Sent: Friday, July 8, 2016 6:57 PM To: Susan Hares; 'John G. Scudder' Cc: idr@ietf.org; Robert Raszuk; 'idr chairs' Subject: Re: [Idr] Presentation slot Hi, Sue and John: I would like to ask for 15-minutes to present the following draft at the upcoming IETF in Berlin: draft-chen-idr-geo-coordinates-01 Thanks. -- Enke On 7/4/16 5:17 AM, Susan Hares wrote: > > > IETF 96 is drawing near. For those who would like to present at IETF 96, please reply to this message (making sure to keep both chairs), and request a slot. > > > > Sue and John > > > > _______________________________________________ > Idr mailing list > Idr@ietf.org > https://www.ietf.org/mailman/listinfo/idr > _______________________________________________ Idr mailing list Idr@ietf.org https://www.ietf.org/mailman/listinfo/idr From nobody Fri Jul 8 17:45:57 2016 Return-Path: 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 14B1F12B051 for ; Fri, 8 Jul 2016 17:45:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.902 X-Spam-Level: X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nistgov.onmicrosoft.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 8qck49sWumFK for ; Fri, 8 Jul 2016 17:45:53 -0700 (PDT) Received: from gcc01-CY1-obe.outbound.protection.outlook.com (mail-cy1gcc01on0126.outbound.protection.outlook.com [23.103.200.126]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 64D6912B040 for ; Fri, 8 Jul 2016 17:45:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nistgov.onmicrosoft.com; s=selector1-nist-gov; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=lihC5fZyBNWSRjhst7u8ifuulVg3fZf956vfS+R3Q1Y=; b=qIuQfzDUYoDpr70dRHd+xC195Icoo0F1DsIjEISRRzQzFzwg7ZseGVv9R7t23KsTWDRLZ6qWeBiawKh/Rf0QwdxqG+h2oQkfF3I96ca0XeTwMNhTi1N4gnx5ApF/w3FCvLCheTv+0Xwq/hSYkJrs7JJOrRzkpeZ/NARdVZ/GC9s= Received: from DM2PR09MB0446.namprd09.prod.outlook.com (10.161.252.145) by DM2PR09MB0446.namprd09.prod.outlook.com (10.161.252.145) with Microsoft SMTP Server (TLS) id 15.1.534.14; Sat, 9 Jul 2016 00:45:51 +0000 Received: from DM2PR09MB0446.namprd09.prod.outlook.com ([10.161.252.145]) by DM2PR09MB0446.namprd09.prod.outlook.com ([10.161.252.145]) with mapi id 15.01.0534.020; Sat, 9 Jul 2016 00:45:51 +0000 From: "Sriram, Kotikalapudi (Fed)" To: "idr@ietf.org" Thread-Topic: New Version Notification for draft-ietf-idr-route-leak-detection-mitigation-04.txt Thread-Index: AQHR2WCrrrbulJtx4EiHTxiW5uF0mKAO+eVj Date: Sat, 9 Jul 2016 00:45:51 +0000 Message-ID: References: <20160708213534.32176.45760.idtracker@ietfa.amsl.com> In-Reply-To: <20160708213534.32176.45760.idtracker@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=kotikalapudi.sriram@nist.gov; x-originating-ip: [129.6.219.4] x-ms-office365-filtering-correlation-id: 21e7e9d2-4b68-4b0c-2565-08d3a79260b9 x-microsoft-exchange-diagnostics: 1; DM2PR09MB0446; 6:Ufnw5J/4L5/9GEH2Dqyku/9rG+jvDX6JlO4VlKK1gl1+RaezBMTSEybOIiWb4LL7m9MVVDDLfceikZsLlReZEgq4dW/fDO9ZOySjThA+nIK8tTlH8faJjpHmYLwNccMTXj4mJEvjq7UjaYdCVYYJQqNUc3ta2KQN2NgIz/ZfpYi+heUYA2r2vdSwwRPNvWUY7f5aloxhAGKV9nbw2q+7ZP8k3NFFUJfEqjSkul4+0LrnBqrMcr3TodNhBlxSn46rsM8cdDr7Z40gdteWWu43bdFXTm9EiDChJKENMu5SyNRLSvVOLyIPmFeSO6Am7mRLmOD//5rmrC6EhOgsQ3tB+g==; 5:ppy7ONDYJoYBA0Du29kyxWASktI9t1vyLdpV3olCNAZkNLnhwIAL2v2EFN9KmnEDdRoGiQjI0o4Pxt7BUS2hk0Q9ojlNov5gUKIQE7V/qLiBJQKfYDa5BW35W0YZBHBxW2aECENJIxh6PhBrWMjzPg==; 24:ZbNT7fOq0n1bf0CWbZ2j9U7jx9Dj03iyiJLtaEC/1DoAiSwQJ0c5cWldPagkntIhEsLT1VUcMnS2ffNzcz+vFht+cXgMZhlE2YBvgQ6TCDE=; 7:kzO7TjfwXgXvizA1oKCuRviYXkXDnBmP2WVRoSITABepx4HAQ63f6x8pRQBZscdElhaqwsX8ZUih8mE/r1WeqRL3z/Tufyrxi7VnuGnrA6k8XBTKCO0pRk/7JZpwrGN6QIT7QPCrzgQEvLpdIJ9JcQedRev3fj0EyYfnwhclX+Sb+TnODg5ahegZV6uh5ggbazw3AYHcN0mJGDMU1A/VHlUBPlkBA2WCOFtWfm5IhROKkwbP+UnPeUjXl6tEUZyS x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DM2PR09MB0446; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(120809045254105); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6055026); SRVR:DM2PR09MB0446; BCL:0; PCL:0; RULEID:; SRVR:DM2PR09MB0446; x-forefront-prvs: 0998671D02 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(377454003)(189002)(199003)(377424004)(106356001)(10400500002)(106116001)(97736004)(15650500001)(76576001)(2900100001)(3280700002)(189998001)(66066001)(105586002)(86362001)(9686002)(8936002)(33656002)(2351001)(7736002)(7696003)(3846002)(99286002)(87936001)(50986999)(3660700001)(101416001)(305945005)(2906002)(6116002)(102836003)(7846002)(68736007)(5003600100003)(54356999)(586003)(5002640100001)(92566002)(450100001)(74316002)(122556002)(76176999)(15975445007)(19580405001)(77096005)(19580395003)(230783001)(2501003)(1730700003)(107886002)(3900700001)(110136002)(81166006)(5640700001)(8676002)(2950100001)(11100500001)(81156014); DIR:OUT; SFP:1102; SCL:1; SRVR:DM2PR09MB0446; H:DM2PR09MB0446.namprd09.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; received-spf: None (protection.outlook.com: nist.gov does not designate permitted sender hosts) spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: nist.gov X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Jul 2016 00:45:51.4338 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 2ab5d82f-d8fa-4797-a93e-054655c61dec X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR09MB0446 Archived-At: Subject: [Idr] Fw: New Version Notification for draft-ietf-idr-route-leak-detection-mitigation-04.txt X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Jul 2016 00:45:56 -0000 Minor updates done in this new version: 1. Added a reference to the discussions from the NANOG list in June 2016 which provide support for the material on "Intra-AS Messaging for Route Le= ak Prevention" in Section 3.2. 2. The last paragraph in Section 4 is new.=20 This paragraph actually belongs more suitably at the end of Section 5.4. W= ill make that move in the next revision. Sriram ________________________________________ From: internet-drafts@ietf.org Sent: Friday, July 8, 2016 5:35 PM To: Brian Dickson; Montgomery, Douglas (Fed); Keyur Patel; Andrei Robachevs= ky; Sriram, Kotikalapudi (Fed) Subject: New Version Notification for draft-ietf-idr-route-leak-detection-m= itigation-04.txt A new version of I-D, draft-ietf-idr-route-leak-detection-mitigation-04.txt has been successfully submitted by Kotikalapudi Sriram and posted to the IETF repository. Name: draft-ietf-idr-route-leak-detection-mitigation Revision: 04 Title: Methods for Detection and Mitigation of BGP Route Leaks Document date: 2016-07-08 Group: idr Pages: 22 URL: https://www.ietf.org/internet-drafts/draft-ietf-idr-route-l= eak-detection-mitigation-04.txt Status: https://datatracker.ietf.org/doc/draft-ietf-idr-route-leak-= detection-mitigation/ Htmlized: https://tools.ietf.org/html/draft-ietf-idr-route-leak-detec= tion-mitigation-04 Diff: https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-idr-route-le= ak-detection-mitigation-04 Abstract: [I-D.ietf-grow-route-leak-problem-definition] provides a definition of the route leak problem, and also enumerates several types of route leaks. This document first examines which of those route-leak types are detected and mitigated by the existing origin validation (OV) [RFC 6811]. It is recognized that OV offers a limited detection and mitigation capability against route leaks. This document specifies enhancements that significantly extend the route-leak prevention, detection, and mitigation capabilities of BGP. One solution component involves carrying a per-hop route-leak protection (RLP) field in BGP updates. The RLP field is proposed be carried in a new optional transitive attribute, called BGP RLP attribute. The solution is meant to be initially implemented as an enhancement of BGP without requiring BGPsec [I-D.ietf-sidr-bgpsec-protocol]. However, when BGPsec is deployed in the future, the solution can be incorporated in BGPsec, enabling cryptographic protection for the RLP field. That would be one way of implementing the proposed solution in a secure way. The document also includes a stopgap method for detection and mitigation of route leaks for an intermediate phase when OV is deployed but BGP protocol on the wire is unchanged. From nobody Sat Jul 9 12:49:19 2016 Return-Path: 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 CC52812D0D3 for ; Sat, 9 Jul 2016 12:49:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.697 X-Spam-Level: X-Spam-Status: No, score=-0.697 tagged_above=-999 required=5 tests=[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 RQ_eJrHVeOQ8 for ; Sat, 9 Jul 2016 12:49:15 -0700 (PDT) Received: from mail-lf0-x235.google.com (mail-lf0-x235.google.com [IPv6:2a00:1450:4010:c07::235]) (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 5383E12B05A for ; Sat, 9 Jul 2016 12:49:15 -0700 (PDT) Received: by mail-lf0-x235.google.com with SMTP id h129so47033116lfh.1 for ; Sat, 09 Jul 2016 12:49:15 -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=WeheELEK4ZxgzNo6e9/yblrwmZtSnLBXJAvg8JjZPTI=; b=H9XyhEufWNcwX54DfgRSwY5tssrvsmbYWOCYUwvzcl0z/FcOc+Y6ktfvy27mOWQ1vm bg7b1iU6t6Nvy0d6D1si4HemT+7xbi022n3ljP9aU2fv+IY+z4yWCd+owcXbT6388UbF hFISByZ/5eyNJT1o/sWZl7T1EgmHKR+4w2ZMT9TzpcHmOSnfYdozlzUrgz5tWbP1cVOp Q2kmtEC6jJjKvMcvs/+GZy/jgs2H3PYvz1Dvz0SpJs1yd2y7aGVuMEL2BaMnC98bwbRc +wS7T8v6Q9rxTalTWdjWwqG2DZEwhM/l163OaTBy5yy/rkRo2zDjiq8nnP4lzKL9qYy7 yzwA== 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=WeheELEK4ZxgzNo6e9/yblrwmZtSnLBXJAvg8JjZPTI=; b=Jlp7mGFWFWmbUGlcpxzZ4Tp99joBJodMkYjW+62MmitF2hpNEFFwi7R2G5zl3+wutf vZmp7DnSW4lnlZ327+K2FXKdt/K2ohSm8tOn7BUtIzEHOostYhvuomItTDTojZV/eipI e3T2JUbM3sCSsJ6VRu2JOneAqyBfiVXaPhYNtZiHQrgYDOERjCX2ay15XAQF2BbvFs/G UrbAC1bvLOdU8TGPDLkVTLQL62odNAJ+vbCjoBnemLslZjeyegjoSKX8PoFAwOazFH1A 4bOglkdaR/fb2GdaY0IOzZ5vSmpW39HSACx3mu1korvsBdaaEckxFKhpyUok0MjVzHmQ JIvg== X-Gm-Message-State: ALyK8tIwFH7UfYZBanhvzL1ICNb9Pek25yiWzXO4RuEmxdJUAUhmX1EoemmiBakQvijX+JKiVi4fFXmzMaqBBQ== X-Received: by 10.25.214.97 with SMTP id n94mr3217246lfg.105.1468093753286; Sat, 09 Jul 2016 12:49:13 -0700 (PDT) MIME-Version: 1.0 Sender: rraszuk@gmail.com Received: by 10.25.18.225 with HTTP; Sat, 9 Jul 2016 12:49:12 -0700 (PDT) In-Reply-To: References: From: Robert Raszuk Date: Sat, 9 Jul 2016 21:49:12 +0200 X-Google-Sender-Auth: nKwMP1NapIVFFq-cqu0nBme_-fc Message-ID: To: "Acee Lindem (acee)" Content-Type: multipart/alternative; boundary=001a1140ef7aa9662a05373936ac Archived-At: Cc: "Keyur Patel \(keyupate\)" , "Derek Man-Kit Yeung \(myeung\)" , idr wg Subject: Re: [Idr] Shortest Path Routing Extensions for BGP Protocol X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Jul 2016 19:49:18 -0000 --001a1140ef7aa9662a05373936ac Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi AC, Many thx for responding. As far as your question 100K+ was about number of compute nodes, virtual compute nodes in flat routing (enabled via SR-IOV) & switches together as in your proposal each of them is a node in the SPT. Unless you are planning to introduce analogy to ospf areas here :) In any case the most powerful property of BGP is hierarchy and (multi-level) indirection via next hop. In normal BGP deployments next hops which are carried in BGP are resolved in IGP. In DC cases where eBGP is used between all fabric stages next hops resolves to connected routes. In your case in flat routing you no longer have such recursion. However I assume your proposal can coexist with other SAFIs and say external to the DC desitnations will be still carried in 1/1 or 2/1 and their next hops will be resolved by routes inserted into RIB by running SPF correct? Last .. LFA is a great technology however I am not sure if enabling it in topologies where you have 10s of ECMP active paths and where you are ready by design for a failure handling is a right thing to do. What are other real use cases for giving up on pure BGP best path selection and normal BGP multipath ? Best regards, R. On Fri, Jul 8, 2016 at 6:22 PM, Acee Lindem (acee) wrote: > Hi Robert, > > Thanks for engaging=E2=80=A6 > > From: on behalf of Robert Raszuk > Date: Friday, July 8, 2016 at 11:51 AM > To: "Keyur Patel (keyupate)" , Acee Lindem < > acee@cisco.com>, "Abhay Roy (akr)" , "Derek Man-Kit Yeung > (myeung)" , "Venu Venugopal (venuv)" > Cc: IDR List > Subject: Shortest Path Routing Extensions for BGP Protocol > > Hi, > > I have reviewed your proposal. > > Turning path vector or distance vector protocol into link state carrier i= s > no doubt a bold idea :). > > > =E2=80=9CFortune befriends the bold.=E2=80=9D -Emily Dickinson > > > Effectively what you are proposing is to use BGP TCP sessions to propagat= e > link state database creating first "link vector protocol" ! > > For start I have few questions: > > Q1: > > RFC7752 has gone via lot of efforts (especially sections 3.2 and up) to > include number of OSPF or ISIS specific encodings. In your proposal you > mentioned OSPF twice and not even once ISIS. Does it mean that you are no= t > going to use all encoding for specific IGPs as defined in RFC7752 ? > > > We are using the BGP Protocol-ID defined for BGP-EPE. The IANA request > will be generalized from =E2=80=9CBGP-EPE=E2=80=9D to =E2=80=9CBGP=E2=80= =9D in support of Segment Routing > and other enhancements. The BGP-LS NLRI are specific BGP and not either > IS-IS or OSPF. > > > Q2: > > Who creates and maintains LSDB in each BGP speaker ? Are you planning to > run OSPF and or ISIS except disable it to establish any adjaciencies ? > > > I=E2=80=99ve seen designs like this in my time but have never been of a f= an of > them ;^). BGP will do the SPF directly and maintain the SPT. You=E2=80=99= ll note > that a simplified SPF is already done for ORR. > > > Q3: > > Currently there are already to models to build DCs with BGP ... one uses > BGP to create only lean underlay the other is to use BGP for both underla= y > and tenants (example project Calico for the latter). With that scale wise= I > think your proposal will work great for the former. However I do have > concerns about using your model for the latter where say 10,000 or 100,00= 0 > /32s or /128s from each VMs are injected and you need to construct SPT wi= th > all of those. > > > Similar to those designs, the SPT could be limited to the underlay. > However, if there is no requirement for the benefits of L2 or L3 VPNs, I > see no reason why these 100Ks of leafs VM prefixes in DC center couldn=E2= =80=99t be > supported. > > > Q4: > > Related to Q3 in your model and say flat DC routing each compute node > other then just injecting 10s of /32s and being "done" now becomes an IGP > node. Since your document explicitely targets Massively Scaled Data Cente= rs > (MSDCs) I am concerned that having 100,000+ IGP nodes and in many case mu= ch > more is not the best idea. > > > 100K+ switches in a single DC fabric (i.e., BGP routing domain)? I have > some experience in link-state protocols and I can tell you that OSPF is I= /O > bound mainly due to the flooding. If done right, the SPF calculation can = be > done with minimal computation. While BGP-LS isn=E2=80=99t the world's mos= t compact > encoding, it is completely incremental. > > > Q5: > > Have you considered just proposing an OSPF route reflector instead withou= t > stuffing BGP into the mix ? As some of you perhaps remember the work on > this started around year 2000 to optimize PE-CE CSC deployments :) It see= ms > to me very reusable for this goal. > > > We looked at lots of alternatives and this one seemed like the best one. > Please pass me a pointer to the work you mention. > > Thanks, > Acee > > > > Best regards, > Robert. > > --001a1140ef7aa9662a05373936ac Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi AC,

Many thx for responding.=C2=A0

As far as your question 100K+ was about numbe= r of compute nodes, virtual compute nodes in flat routing (enabled via SR-I= OV) & switches together as in your proposal each of them is a node in t= he SPT. Unless you are planning to introduce analogy to ospf areas here :)<= /div>

In any case the most p= owerful property of BGP is hierarchy and (multi-level) indirection via next= hop. In normal BGP deployments next hops which are carried in BGP are reso= lved in IGP. In DC cases where eBGP is used between all fabric stages next = hops resolves to connected routes.=C2=A0

=
In your case in flat routing you no longer have such rec= ursion.=C2=A0

However = I assume your proposal can coexist with other SAFIs and say external to the= DC desitnations will be still carried in 1/1 or 2/1 and their next hops wi= ll be resolved by routes inserted into RIB by running SPF correct?

Last .. LFA is a great technol= ogy however I am not sure if enabling it in topologies where you have 10s o= f ECMP active paths and where you are ready by design for a failure handlin= g is a right thing to do. What are other real use cases for giving up on pu= re BGP best path selection and normal BGP multipath ?=C2=A0

Best regards,
R.


On Fri, Jul 8, 2016 at 6:22 PM, Acee Lindem (acee) <acee@cisco.com> wrote:
Hi Robert,=C2=A0

Thanks for engaging=E2=80=A6

From: <rraszuk@gmail.com> on behalf of Robert= Raszuk <robert@r= aszuk.net>
Date: Friday, July 8, 2016 at 11:51= AM
To: "Keyur Patel (keyupate)&qu= ot; <keyupate@ci= sco.com>, Acee Lindem <acee@cisco.com>, "Abhay Roy (akr)" <akr@cisco.com>, "Derek Man-Kit Yeung (myeung)" <myeung@cisco.com>, "Venu Venugopal (ve= nuv)" <venuv@c= isco.com>
Cc: IDR List <idr@ietf.org>
Subject: Shortest Path Routing Exte= nsions for BGP Protocol

Hi,

I have reviewed your proposal.=C2=A0

Turning path vector or distance vector protocol into link state carrier is = no doubt a bold idea :).

=E2=80=9CFortune befriends the bold.= =E2=80=9D -Emily Dickinson


Effectively what you are proposing is to use BGP TCP sessions to propagate = link state database creating first "link vector protocol" !

For start I have few questions:

Q1:=C2=A0

RFC7752 has gone via lot of efforts (especially sections 3.2 and up) to inc= lude number of OSPF or ISIS specific encodings. In your proposal you mentio= ned OSPF twice and not even once ISIS. Does it mean that you are not going = to use all encoding for specific IGPs as defined in RFC7752 ?=C2=A0

We are using the BGP Protocol-ID defined for BGP-EPE. The IANA = request will be generalized from =E2=80=9CBGP-EPE=E2=80=9D to =E2=80=9CBGP= =E2=80=9D in support of Segment Routing and other enhancements. The BGP-LS = NLRI are specific BGP and not either IS-IS or OSPF.=C2=A0


Q2:=C2=A0

Who creates and maintains LSDB in each BGP speaker ? Are you planning to ru= n OSPF and or ISIS except disable it to establish any adjaciencies ?=C2=A0<= /div>

I=E2=80=99ve seen designs like this in my time but have never b= een of a fan of them ;^). BGP will do the SPF directly and maintain the SPT= . You=E2=80=99ll note that a simplified SPF is already done for ORR.=C2=A0<= /div>


Q3:=C2=A0

Currently there are already to models to build DCs with BGP ... one uses BG= P to create only lean underlay the other is to use BGP for both underlay an= d tenants (example project Calico for the latter). With that scale wise I t= hink your proposal will work great for the former. However I do have concerns about using your model for the = latter where say 10,000 or 100,000 /32s or /128s from each VMs are injected= and you need to construct SPT with all of those.=C2=A0

Similar to those designs, the SPT could be limited to the under= lay. However, if there is no requirement for the benefits of L2 or L3 VPNs,= I see no reason why these 100Ks of leafs VM prefixes in DC center couldn= =E2=80=99t be supported.=C2=A0


Q4:=C2=A0

Related to Q3 in your model and say flat DC routing each compute node other= then just injecting 10s of /32s and being "done" now becomes an = IGP node. Since your document explicitely targets=C2=A0Massively Scaled Dat= a Centers (MSDCs) I am concerned that having 100,000+ IGP nodes and in many case much more is not the best idea.=C2=A0

100K+ switches in a single DC fabric (i.e., BGP routing domain)= ? I have some experience in link-state protocols and I can tell you that OS= PF is I/O bound mainly due to the flooding. If done right, the SPF calculat= ion can be done with minimal computation. While BGP-LS isn=E2=80=99t the world's most compact encoding, it is co= mpletely incremental.=C2=A0


Q5:=C2=A0

Have you considered just proposing an OSPF route reflector instead without = stuffing BGP into the mix ? As some of you perhaps remember the work on thi= s started around year 2000 to optimize PE-CE CSC deployments :) It seems to= me very reusable for this goal.

We looked at lots of alternatives and this one seemed like the = best one. Please pass me a pointer to the work you mention.=C2=A0

Thanks,
Acee=C2=A0



Best regards,
Robert.


--001a1140ef7aa9662a05373936ac-- From nobody Sat Jul 9 22:19:00 2016 Return-Path: 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 04BCD12B013 for ; Sat, 9 Jul 2016 22:19:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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 YUArS6iRBGJd for ; Sat, 9 Jul 2016 22:18:58 -0700 (PDT) Received: from mail-it0-x236.google.com (mail-it0-x236.google.com [IPv6:2607:f8b0:4001:c0b::236]) (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 7D5E0126B6D for ; Sat, 9 Jul 2016 22:18:58 -0700 (PDT) Received: by mail-it0-x236.google.com with SMTP id f6so33093442ith.0 for ; Sat, 09 Jul 2016 22:18:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:cc; bh=DWByiSgT94eC16ICZWGif4lKfmI58rBWMO9sT+0F6F8=; b=vgMIAgzW2g4b5m3xE0Sy0d4J6wL7hCk1vZ1fexlE9Gm8N4LcuEDTHuHEI9ClNC7gWG ONWhr3+3ueSAQ4wU0t0E4K9I/ZKMrn6QfVDmIyMXSsu9qU4mB4Cc2RzMBCakEJDgnK9+ 5wrd12YG/a0MaWTR2Ff+5URhh0W3BhDATLmz+WXtwuAbO6lgRYqPVeXOS40wF1Y36Hm9 SvBAqhTJ0PIxJsn+fs6FNOhz1mDSM1gj5Vp7yX7cbVJrGoc/F1ue2IFtUPVtG/VImQDz OKw504d1UfnZuUnjfyJKc1MXbldFJdnkK8my21ciMAyWwygMMD/6MU3qxX0b4qA14hB0 lvMg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=DWByiSgT94eC16ICZWGif4lKfmI58rBWMO9sT+0F6F8=; b=a+PDW6ppzcjX+s4C2Wmqvd35efwrWVW5UKrU+dXmQpmfpnb1CRpyqD3ARMx9rJ7Lzn YCldtOA85JJD+Sss2xnAMjUOnHkt8ufoyISeMY8sIdfnDafZ7CLE5bGWgcEIewOBDcpf WnurZCHhSay9r0xz3W5qeu6cCc/AW7O5nvMSv1qW/s8TS6yXT9hCNyPK+0aVxPnJzEd0 HaIGQJOXfefSjmsquf9etlzfXBRgQKeqonM6DkssRxrGB0TRL01SxAIR+MpOeQFKMm4x p1gTJxdA1Iv/otqQNKVQBEaPSwg/ZA3eq8wz1HkOOIIC9JMTHiCP4dRnDTNfBSJta2cG HnpQ== X-Gm-Message-State: ALyK8tLiDG7L0yDOBVHnWA3aEVPKaD/+qbCqFuULU5tNfUv9zvgzhlH3Cu2tiQibWQL6nInkloWfefBgrSvNgw== X-Received: by 10.36.131.194 with SMTP id d185mr134856ite.38.1468127937748; Sat, 09 Jul 2016 22:18:57 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.138.85 with HTTP; Sat, 9 Jul 2016 22:18:18 -0700 (PDT) From: Tony Przygienda Date: Sat, 9 Jul 2016 22:18:18 -0700 Message-ID: To: "John G. Scudder" , Sue Hares Content-Type: multipart/alternative; boundary=94eb2c04965236e37a0537412cbf Archived-At: Cc: idr@ietf.org Subject: [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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Jul 2016 05:19:00 -0000 --94eb2c04965236e37a0537412cbf Content-Type: text/plain; charset=UTF-8 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 --94eb2c04965236e37a0537412cbf Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
John, Sue, may I reque= st a slot on IDR agenda in Berlin (10 mins should be enough) to present=C2= =A0https://www.ietf.org/internet-drafts/draft-idr-bgp-rout= e-refresh-options-00.txt=C2=A0?=C2=A0

tha= nks=C2=A0

<= /div>
-- tony=C2=A0
--94eb2c04965236e37a0537412cbf-- From nobody Sun Jul 10 11:33:00 2016 Return-Path: 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 290B512D0C2; Sun, 10 Jul 2016 11:32:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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 XSKAdyD7FDmr; Sun, 10 Jul 2016 11:32:57 -0700 (PDT) Received: from mail-it0-x234.google.com (mail-it0-x234.google.com [IPv6:2607:f8b0:4001:c0b::234]) (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 ACF5312D0B0; Sun, 10 Jul 2016 11:32:57 -0700 (PDT) Received: by mail-it0-x234.google.com with SMTP id f6so40103092ith.0; Sun, 10 Jul 2016 11:32:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=oUQ+EN8kwepAyt1bGm83r+x4NODQeHbCrUQpQ1xvc4s=; b=Hb+FxJg6R5eY7P+s7F1mM32tJAVgQ3Jqhj+Le+Zwtd8vbiU3tBxNDgYZ6xvLr2KcQ5 Udn/6/HYAEgl3W8V3OcpQxXS9wZd9c/LyJz4Dny/97KtYnvcgUkowU296BaE2xYGixoi 181ZER6XHRY+Gti6n18rTzbX6lBdUpxpBXSS5SkLNbwg7F8gD9S0ac0Rc8cow0LSSRg3 yLKGxKOLLxW5ysqOUbEJUrIS6InoUIYBGbRkCh8cRvc8RssD4uhWPdyiOPyf6vvqgz3g S1BksxBRXnDqCm04O0v1b37qknc8c+dlrM2UAbIxMWLtR5UG64gfzlp9+A9lXvH3xeJ+ eCTA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=oUQ+EN8kwepAyt1bGm83r+x4NODQeHbCrUQpQ1xvc4s=; b=DWf1eNZwsyTLKw//nsp4Hjp5qRRqVSbpVVon5bU87SSp+JvQ0EOicCDSNrrBJLvYq3 01ceRpdwOFNfpbJiAyDkCqI1aXl2HrgjIKSex+StqPNrzHRfQctFJf3V3akC3w2uXwmc S9RYHFFTg0jxjzIpCWeIvwR2xagsU51s81BcqYoHqt3neCKlteOvPOeiS0N+fRzpjopT CAWdfXwWe11K67DtWOZKk72sdcYht4hajZZteIXowvwAMvwQiMa6ocz4WRgtrTDId3ww on1yu8tgXmU1uJ1CV+0SCPR2ZtwJ+4wrItxb33WUt80NtjvaqiRloXgt2UsgSVEWkSGu +LsQ== X-Gm-Message-State: ALyK8tJaZk2YQ5/VQeooWh8tZThg2m3DOX5zoxR2Wb5cAZ9F2dVJaNp7+arOdvbMotMdKjzBdM1/0oFxqWCFzQ== X-Received: by 10.36.16.197 with SMTP id 188mr12067989ity.88.1468175577007; Sun, 10 Jul 2016 11:32:57 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.10.218 with HTTP; Sun, 10 Jul 2016 11:32:17 -0700 (PDT) In-Reply-To: <004d01d1d973$342ac660$9c805320$@ndzh.com> References: <152e01d1d5ee$0c4c1320$24e43960$@ndzh.com> <33a8ae6f-1498-f6bb-0135-7215eb7842be@cisco.com> <004d01d1d973$342ac660$9c805320$@ndzh.com> From: Tony Przygienda Date: Sun, 10 Jul 2016 11:32:17 -0700 Message-ID: To: Susan Hares Content-Type: multipart/alternative; boundary=001a1144405abc4d6b05374c4340 Archived-At: Cc: idr@ietf.org, Robert Raszuk , "John G. Scudder" , idr chairs Subject: Re: [Idr] Presentation slot X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Jul 2016 18:32:59 -0000 --001a1144405abc4d6b05374c4340 Content-Type: text/plain; charset=UTF-8 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 --001a1144405abc4d6b05374c4340 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
John, Sue, may I request a slot on IDR agenda in Berlin (10 mins should = be enough) to present=C2=A0https://www.i= etf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00.txt=C2= =A0?=C2=A0

thanks=C2=A0

-- tony=C2=A0

<= div class=3D"gmail_extra">
--001a1144405abc4d6b05374c4340-- From nobody Sun Jul 10 21:26:57 2016 Return-Path: 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 19F9A12B036; Sun, 10 Jul 2016 21:26:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.739 X-Spam-Level: * X-Spam-Status: No, score=1.739 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, RDNS_NONE=0.793] autolearn=no 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 c7O9jB_eNJVM; Sun, 10 Jul 2016 21:26:54 -0700 (PDT) Received: from hickoryhill-consulting.com (unknown [50.245.122.97]) (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 A171912B028; Sun, 10 Jul 2016 21:26:54 -0700 (PDT) X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=74.43.47.20; From: "Susan Hares" To: "'Tony Przygienda'" References: <152e01d1d5ee$0c4c1320$24e43960$@ndzh.com> <33a8ae6f-1498-f6bb-0135-7215eb7842be@cisco.com> <004d01d1d973$342ac660$9c805320$@ndzh.com> In-Reply-To: Date: Mon, 11 Jul 2016 00:26:11 -0400 Message-ID: <013a01d1db2c$5b3b1e20$11b15a60$@ndzh.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_013B_01D1DB0A.D42ADDB0" X-Mailer: Microsoft Outlook 14.0 Content-Language: en-us Thread-Index: AQLN6h0I1kMMkzKOeCmbR8vdTJayoQKV8PvNAd7HohkB9E52453nO24g X-Authenticated-User: skh@ndzh.com Archived-At: Cc: idr@ietf.org, 'Robert Raszuk' , "'John G. Scudder'" , 'idr chairs' Subject: Re: [Idr] Presentation slot X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jul 2016 04:26:56 -0000 This is a multipart message in MIME format. ------=_NextPart_000_013B_01D1DB0A.D42ADDB0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Tony:=20 =20 What a delight to have you present this draft. I will add you to the = agenda in its next revision.=20 =20 Sue=20 =20 From: Tony Przygienda [mailto:tonysietf@gmail.com]=20 Sent: Sunday, July 10, 2016 2:32 PM To: Susan Hares Cc: Enke Chen; John G. Scudder; idr@ietf.org; Robert Raszuk; idr chairs Subject: Re: [Idr] Presentation slot =20 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 ?=20 =20 thanks=20 =20 -- tony=20 =20 =20 ------=_NextPart_000_013B_01D1DB0A.D42ADDB0 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable

Tony:

 

What a delight to have you present this draft.=C2=A0=C2=A0 I will add = you to the agenda in its next revision.

 

Sue

 

From:= = Tony Przygienda [mailto:tonysietf@gmail.com]
Sent: Sunday, = July 10, 2016 2:32 PM
To: Susan Hares
Cc: Enke Chen; = John G. Scudder; idr@ietf.org; Robert Raszuk; idr = chairs
Subject: Re: [Idr] Presentation = slot

 

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-rout= e-refresh-options-00.txt ? 

 

thanks 

 

-- tony 

 

 

------=_NextPart_000_013B_01D1DB0A.D42ADDB0-- From nobody Mon Jul 11 11:24:23 2016 Return-Path: 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 3482D12D642 for ; Mon, 11 Jul 2016 11:24:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -15.807 X-Spam-Level: X-Spam-Status: No, score=-15.807 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 9g0o-tm3-LJ5 for ; Mon, 11 Jul 2016 11:24:20 -0700 (PDT) Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4569A12D641 for ; Mon, 11 Jul 2016 11:24:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=23174; q=dns/txt; s=iport; t=1468261460; x=1469471060; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=e7EuwPYypynLoPFa9y1040m09F2TgG3A7nPPPBBH8Xk=; b=QopL0l62UnNuLE4ABXtOygbh7Im/FVYGULRuE+BBRic5gi+pnBM1FRmo GFlNUG1xDfPcE5DjxkMkP4yToZHd1ffLn8gimHBMAK0YPgN55D34MYsHl gtkWTRqvPD9QyixaklwSaQjDTp8CfNpANCuJrSCdu5+MSDvoBhsRKP2YV U=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0COAgAo44NX/4cNJK1dgnBOgVIGrGeMF?= =?us-ascii?q?oF6hhgCgSo4FAEBAQEBAQFlJ4RcAQEFZw0FEAIBCBEDAQIhBwchERQJCAIEAQ0?= =?us-ascii?q?FiBYDF7s9DYN+AQEBAQEBAQMBAQEBAQEBAQEBARyGJ4NKgQOCQ4FaRIU7BZNch?= =?us-ascii?q?Qg0AYw7ghaBaoRYiGqIG4dzAR42g3Fuh3tFfwEBAQ?= X-IronPort-AV: E=Sophos;i="5.28,347,1464652800"; d="scan'208,217";a="296416333" Received: from alln-core-2.cisco.com ([173.36.13.135]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 11 Jul 2016 18:24:19 +0000 Received: from XCH-RTP-003.cisco.com (xch-rtp-003.cisco.com [64.101.220.143]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id u6BIOIAm014417 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 11 Jul 2016 18:24:19 GMT Received: from xch-rtp-017.cisco.com (64.101.220.157) by XCH-RTP-003.cisco.com (64.101.220.143) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 11 Jul 2016 14:24:18 -0400 Received: from xch-rtp-017.cisco.com ([64.101.220.157]) by XCH-RTP-017.cisco.com ([64.101.220.157]) with mapi id 15.00.1210.000; Mon, 11 Jul 2016 14:24:18 -0400 From: "Keyur Patel (keyupate)" To: Robert Raszuk , "Acee Lindem (acee)" Thread-Topic: Shortest Path Routing Extensions for BGP Protocol Thread-Index: AQHR26FvxIpLOkGbSUaecUKuYrsBFg== Date: Mon, 11 Jul 2016 18:24:17 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.4.9.150325 x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.154.161.180] Content-Type: multipart/alternative; boundary="_000_D3A931B4465B6keyupateciscocom_" MIME-Version: 1.0 Archived-At: Cc: "Derek Man-Kit Yeung \(myeung\)" , idr wg Subject: Re: [Idr] Shortest Path Routing Extensions for BGP Protocol X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jul 2016 18:24:22 -0000 --_000_D3A931B4465B6keyupateciscocom_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hi Robert, Comment inlined #Keyur. From: Robert Raszuk > Date: Saturday, July 9, 2016 at 12:49 PM To: "Acee Lindem (acee)" > Cc: Keyur Patel >, "Abhay Roy= (akr)" >, "Derek Man-Kit Yeung (myeung= )" >, "Venu Venugopal (venuv)" >, idr wg > Subject: Re: Shortest Path Routing Extensions for BGP Protocol Hi AC, Many thx for responding. As far as your question 100K+ was about number of compute nodes, virtual co= mpute nodes in flat routing (enabled via SR-IOV) & switches together as in = your proposal each of them is a node in the SPT. Unless you are planning to= introduce analogy to ospf areas here :) In any case the most powerful property of BGP is hierarchy and (multi-level= ) indirection via next hop. In normal BGP deployments next hops which are c= arried in BGP are resolved in IGP. In DC cases where eBGP is used between a= ll fabric stages next hops resolves to connected routes. In your case in flat routing you no longer have such recursion. However I assume your proposal can coexist with other SAFIs and say externa= l to the DC desitnations will be still carried in 1/1 or 2/1 and their next= hops will be resolved by routes inserted into RIB by running SPF correct? #Keyur: Yep. Other SAFIs can totally use the draft extensions to recurse th= eir next hops. Regards, Keyur Last .. LFA is a great technology however I am not sure if enabling it in t= opologies where you have 10s of ECMP active paths and where you are ready b= y design for a failure handling is a right thing to do. What are other real= use cases for giving up on pure BGP best path selection and normal BGP mul= tipath ? Best regards, R. On Fri, Jul 8, 2016 at 6:22 PM, Acee Lindem (acee) > wrote: Hi Robert, Thanks for engaging=85 From: > on behalf of Robert Ras= zuk > Date: Friday, July 8, 2016 at 11:51 AM To: "Keyur Patel (keyupate)" = >, Acee Lindem >, "Abhay Roy (akr)" <= akr@cisco.com>, "Derek Man-Kit Yeung (myeung)" >, "Venu Venugopal (venuv)" > Cc: IDR List > Subject: Shortest Path Routing Extensions for BGP Protocol Hi, I have reviewed your proposal. Turning path vector or distance vector protocol into link state carrier is = no doubt a bold idea :). =93Fortune befriends the bold.=94 -Emily Dickinson Effectively what you are proposing is to use BGP TCP sessions to propagate = link state database creating first "link vector protocol" ! For start I have few questions: Q1: RFC7752 has gone via lot of efforts (especially sections 3.2 and up) to inc= lude number of OSPF or ISIS specific encodings. In your proposal you mentio= ned OSPF twice and not even once ISIS. Does it mean that you are not going = to use all encoding for specific IGPs as defined in RFC7752 ? We are using the BGP Protocol-ID defined for BGP-EPE. The IANA request will= be generalized from =93BGP-EPE=94 to =93BGP=94 in support of Segment Routi= ng and other enhancements. The BGP-LS NLRI are specific BGP and not either = IS-IS or OSPF. Q2: Who creates and maintains LSDB in each BGP speaker ? Are you planning to ru= n OSPF and or ISIS except disable it to establish any adjaciencies ? I=92ve seen designs like this in my time but have never been of a fan of th= em ;^). BGP will do the SPF directly and maintain the SPT. You=92ll note th= at a simplified SPF is already done for ORR. Q3: Currently there are already to models to build DCs with BGP ... one uses BG= P to create only lean underlay the other is to use BGP for both underlay an= d tenants (example project Calico for the latter). With that scale wise I t= hink your proposal will work great for the former. However I do have concer= ns about using your model for the latter where say 10,000 or 100,000 /32s o= r /128s from each VMs are injected and you need to construct SPT with all o= f those. Similar to those designs, the SPT could be limited to the underlay. However= , if there is no requirement for the benefits of L2 or L3 VPNs, I see no re= ason why these 100Ks of leafs VM prefixes in DC center couldn=92t be suppor= ted. Q4: Related to Q3 in your model and say flat DC routing each compute node other= then just injecting 10s of /32s and being "done" now becomes an IGP node. = Since your document explicitely targets Massively Scaled Data Centers (MSDC= s) I am concerned that having 100,000+ IGP nodes and in many case much more= is not the best idea. 100K+ switches in a single DC fabric (i.e., BGP routing domain)? I have som= e experience in link-state protocols and I can tell you that OSPF is I/O bo= und mainly due to the flooding. If done right, the SPF calculation can be d= one with minimal computation. While BGP-LS isn=92t the world's most compact= encoding, it is completely incremental. Q5: Have you considered just proposing an OSPF route reflector instead without = stuffing BGP into the mix ? As some of you perhaps remember the work on thi= s started around year 2000 to optimize PE-CE CSC deployments :) It seems to= me very reusable for this goal. We looked at lots of alternatives and this one seemed like the best one. Pl= ease pass me a pointer to the work you mention. Thanks, Acee Best regards, Robert. --_000_D3A931B4465B6keyupateciscocom_ Content-Type: text/html; charset="Windows-1252" Content-ID: <5CB50B4DBA7D2442B0351E287146C45A@emea.cisco.com> Content-Transfer-Encoding: quoted-printable
Hi Robert,

Comment inlined #Keyur.

From: Robert Raszuk <robert@raszuk.net>
Date: Saturday, July 9, 2016 at 12:= 49 PM
To: "Acee Lindem (acee)" = <acee@cisco.com>
Cc: Keyur Patel <keyupate@cisco.com>, "Abhay Roy (akr)&qu= ot; <akr@cisco.com>, "Derek= Man-Kit Yeung (myeung)" <myeun= g@cisco.com>, "Venu Venugopal (venuv)" <= venuv@cisco.com>, idr wg <idr@iet= f.org>
Subject: Re: Shortest Path Routing = Extensions for BGP Protocol

Hi AC,

Many thx for responding. 

As far as your question 100K+ was about number of compute nodes, virtua= l compute nodes in flat routing (enabled via SR-IOV) & switches togethe= r as in your proposal each of them is a node in the SPT. Unless you are pla= nning to introduce analogy to ospf areas here :)

In any case the most powerful property of BGP is hierarchy and (multi-level= ) indirection via next hop. In normal BGP deployments next hops which are c= arried in BGP are resolved in IGP. In DC cases where eBGP is used between a= ll fabric stages next hops resolves to connected routes. 

In your case in flat routing you no longer have such recursion. 

However I assume your proposal can coexist with other SAFIs and say externa= l to the DC desitnations will be still carried in 1/1 or 2/1 and their next= hops will be resolved by routes inserted into RIB by running SPF correct?<= /div>

#Keyur: Yep. Other SAFIs can totally use the draft extensions to recur= se their next hops.

Regards,
Keyur

Last .. LFA is a great technology however I am not sure if enabling it in t= opologies where you have 10s of ECMP active paths and where you are ready b= y design for a failure handling is a right thing to do. What are other real= use cases for giving up on pure BGP best path selection and normal BGP multipath ? 

Best regards,
R.


On Fri, Jul 8, 2016 at 6:22 PM, Acee Lindem (ace= e) <acee@cisco.com&= gt; wrote:
Hi Robert, 

Thanks for engaging=85

From: <rraszuk@gmail.com> on behalf of Robert= Raszuk <robert@r= aszuk.net>
Date: Friday, July 8, 2016 at 11:51= AM
To: "Keyur Patel (keyupate)&qu= ot; <keyupate@ci= sco.com>, Acee Lindem <acee@cisco.com>, "Abhay Roy (akr)" <akr@cisco.com>, "Derek Man-Kit Yeung (myeung)" <myeung@cisco.com>, "Venu Venugopal (ve= nuv)" <venuv@c= isco.com>
Cc: IDR List <idr@ietf.org>
Subject: Shortest Path Routing Exte= nsions for BGP Protocol

Hi,

I have reviewed your proposal. 

Turning path vector or distance vector protocol into link state carrier is = no doubt a bold idea :).

=93Fortune befriends the bold.=94 -E= mily Dickinson


Effectively what you are proposing is to use BGP TCP sessions to propagate = link state database creating first "link vector protocol" !

For start I have few questions:

Q1: 

RFC7752 has gone via lot of efforts (especially sections 3.2 and up) to inc= lude number of OSPF or ISIS specific encodings. In your proposal you mentio= ned OSPF twice and not even once ISIS. Does it mean that you are not going = to use all encoding for specific IGPs as defined in RFC7752 ? 

We are using the BGP Protocol-ID defined for BGP-EPE. The IANA request= will be generalized from =93BGP-EPE=94 to =93BGP=94 in support of Segment = Routing and other enhancements. The BGP-LS NLRI are specific BGP and not ei= ther IS-IS or OSPF. 


Q2: 

Who creates and maintains LSDB in each BGP speaker ? Are you planning to ru= n OSPF and or ISIS except disable it to establish any adjaciencies ? <= /div>

I=92ve seen designs like this in my time but have never been of a fan = of them ;^). BGP will do the SPF directly and maintain the SPT. You=92ll no= te that a simplified SPF is already done for ORR. 


Q3: 

Currently there are already to models to build DCs with BGP ... one uses BG= P to create only lean underlay the other is to use BGP for both underlay an= d tenants (example project Calico for the latter). With that scale wise I t= hink your proposal will work great for the former. However I do have concerns about using your model for the = latter where say 10,000 or 100,000 /32s or /128s from each VMs are injected= and you need to construct SPT with all of those. 

Similar to those designs, the SPT could be limited to the underlay. Ho= wever, if there is no requirement for the benefits of L2 or L3 VPNs, I see = no reason why these 100Ks of leafs VM prefixes in DC center couldn=92t be s= upported. 


Q4: 

Related to Q3 in your model and say flat DC routing each compute node other= then just injecting 10s of /32s and being "done" now becomes an = IGP node. Since your document explicitely targets Massively Scaled Dat= a Centers (MSDCs) I am concerned that having 100,000+ IGP nodes and in many case much more is not the best idea. 

100K+ switches in a single DC fabric (i.e., BGP routing domain)? I= have some experience in link-state protocols and I can tell you that OSPF = is I/O bound mainly due to the flooding. If done right, the SPF calculation= can be done with minimal computation. While BGP-LS isn=92t the world's most compact encoding, it is completely i= ncremental. 


Q5: 

Have you considered just proposing an OSPF route reflector instead without = stuffing BGP into the mix ? As some of you perhaps remember the work on thi= s started around year 2000 to optimize PE-CE CSC deployments :) It seems to= me very reusable for this goal.

We looked at lots of alternatives and this one seemed like the best on= e. Please pass me a pointer to the work you mention. 

Thanks,
Acee 



Best regards,
Robert.


--_000_D3A931B4465B6keyupateciscocom_-- From nobody Mon Jul 11 13:48:01 2016 Return-Path: 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 ; 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 ; 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 ; Mon, 11 Jul 2016 13:47:58 -0700 (PDT) Received: by mail-lf0-x22f.google.com with SMTP id f93so31069010lfi.2 for ; 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: References: From: Robert Raszuk Date: Mon, 11 Jul 2016 22:47:55 +0200 X-Google-Sender-Auth: 0yk6dvRVkGQCJPT8h7u0UG32OEU Message-ID: To: Tony Przygienda Content-Type: multipart/alternative; boundary=001a11411f2857697a053762449d Archived-At: Cc: idr wg 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jul 2016 20:48:01 -0000 --001a11411f2857697a053762449d Content-Type: text/plain; charset=UTF-8 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 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 > > --001a11411f2857697a053762449d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Tony,

Can you clarify what is the expected behaviour as fa= r 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 RFC= 7543 - would all of those be always a logical AND towards a peer which push= ed those ?=C2=A0

Would= you always carry ORF with separate Refresh_ID value ?=C2=A0

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 ju= st the subset of routes against all ORF entries ? In other words I think th= e draft should state that Refresh_IDs have no impact to ORF ADDs or REMOVE = actions - don't you think ?=C2=A0

As far as current types why not add regular/extended commun= ity ?

Thx,
Robert.

=








On Sun, Jul 10, 2016 at 7:18 AM, Tony Przygienda = <tonysietf@gmai= l.com> wrote:
John, Sue, may I request a slot on = IDR agenda in Berlin (10 mins should be enough) to present=C2=A0https://www.ietf.org/internet-drafts/draft-idr-bgp-= route-refresh-options-00.txt=C2=A0?=C2=A0

thanks=C2=A0

-- tony=C2=A0

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


--001a11411f2857697a053762449d-- From nobody Mon Jul 11 15:05:15 2016 Return-Path: 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 2C16012D0B7 for ; Mon, 11 Jul 2016 15:05:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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 WetWov7Ju3Ab for ; Mon, 11 Jul 2016 15:05:13 -0700 (PDT) Received: from mail-io0-x22e.google.com (mail-io0-x22e.google.com [IPv6:2607:f8b0:4001:c06::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 59E7212B03B for ; Mon, 11 Jul 2016 15:05:13 -0700 (PDT) Received: by mail-io0-x22e.google.com with SMTP id b62so438495iod.3 for ; Mon, 11 Jul 2016 15:05:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ZiXxRbZW0DKyLz1/WUWGiZpHHUJ3dFxI492t9rt5bec=; b=CltC1o3YzX0ZByz9NcpoQ7oyRIcV5aK709JR+zSdrGUUIQka2SGGqzcSr6HG/ZU7sB 6zY++pyQVa/K5hxYbIZET1ar5XBIt4xnXfMhE1li2wawD18dW9vu5HEEJa3pBYm/49Hy dG123s/kys+87OGBAAh/xEB+cIdJL34D1kxOr1Hh5E1CnJFSpnkkuxyKE0X0btyLXSqx +Dg5C9MMo2YGyxpVyrKvOzBwP7NPPG/qOiAZXlXoiOgG71aT7qPZwtSpdZmDlIjscOy3 R3L25QI9cKFGCn9PvQ2TrcE16sH6XhgJ2gST0caN3olmVdeQvjPtUy1jeLByCI5+3lYo 5UyA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ZiXxRbZW0DKyLz1/WUWGiZpHHUJ3dFxI492t9rt5bec=; b=Z9Kp+wEjnu3JjK8VLb/xpHu8qCVAZFy1Vu3ld/FO3AWyqzcnmP5iEdZEx9zeai0w2Z ubqez9muzAmi68mtr7F1OFBXREgPEnLIV9MTL2L4ZF+ui+K3SWqe5KK7Gud/uLL3h9Lk Ak/YtF3xVIb6OGuhJctuT6IMy1R6m1+7BX5RxOCpUt+q70gkSF+ptxNMd87ArOIN637F GKGZwX2hiQyLsMZ9GzosQI9Qjys8mZXBlsZbNg8fN5NHSEi0upstgKDkuqvW0CxBoRJp RpfWjguUQX8zHJKMfEt6eNJ0rrRlLVujpLNBE+n0QsGd6B22dIAtvamfY7traTiSbYf4 H+RA== X-Gm-Message-State: ALyK8tLFwo+Vv7tfVFQgjcGp0tWkM/qlXtilzCDr8Zrttf4fFdHYl34ZzvI3D/YwukqcE3zg0urBs5PRbHVEaw== X-Received: by 10.107.29.142 with SMTP id d136mr22360623iod.50.1468274712613; Mon, 11 Jul 2016 15:05:12 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.138.85 with HTTP; Mon, 11 Jul 2016 15:04:33 -0700 (PDT) In-Reply-To: References: From: Tony Przygienda Date: Mon, 11 Jul 2016 15:04:33 -0700 Message-ID: To: Robert Raszuk Content-Type: multipart/alternative; boundary=001a11409584ad982d0537635815 Archived-At: Cc: idr wg 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jul 2016 22:05:15 -0000 --001a11409584ad982d0537635815 Content-Type: text/plain; charset=UTF-8 On Mon, Jul 11, 2016 at 1:47 PM, Robert Raszuk wrote: > Hi Tony, > Hey Robert, thanks for chiming in. Good questions. I speak here for myself, other authors of the draft may have differing opinions. > > 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 ? > We didn't discuss that one through but the only logical conclusion for me is that the ORF/CP-ORF installed are respected (i.e. it's an implicit AND). I see ORF as statefull, remote-pushed policy on the peer that is not being flipped around all the time (albeit AFAIR there were some attempts @ non-persistent, one shot ORF but that ended up expiring?) The motivation for this work were scenarios where a single-shot refresh is needed, actually concurrent bunch of those based on configuration changes, peer having dropped received routes based on specs (A-D), in policy changes, joining VPNs, EVIs and so on. Putting ORF on a peer, refresh and remove ORFs is significantly heavier process that may interfere on top with normal update process going on and needs to be done one-by-one (since you have to wait for single BoRR/EoRR pair) unless one is very smart about combining ORF possibly & playing with the DEFER/IMMEDIATEs. As we indicated, if the AFI/SAFI is covered by RTC and RTC is supported & one is willing to configure RTs for each subset of routes that may need refreshing, RT will be doing the same job just fine. > > Would you always carry ORF with separate Refresh_ID value ? > Yes, Refresh-ID# is strictly monotonic so there is never a misunderstanding WHAT the BoRR belongs to. Observe that the draft does NOT mandate that a request MUST be followed by according BoRR, only that BoRRs must follow same sequence as requests (i.e. are also strictly monotonic). However, we should probably specify that options _and_ ORF can NOT be mixed in the same type #3 message but it's either one or the other (and anything else is error). This will allow ORF operations like today + benefit of the Refresh ID# on the BoRR so the IMMEDIATE can go on @ the same time as another request with higher Refresh ID# (de facto we allow multiple parallel refreshes as you see). In case of DEFER there will be simply no BoRR for it. > > 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 ? > I agree. Yes, ORF is kind of "permanent filter" on the peer while the intent of this draft is to have bunch of "small refreshes" going on @ same time possibly (if you request the refreshes from a good implementation while low-end implementations may serialize the requests to simplify internal logic ;-). > > As far as current types why not add regular/extended community ? > Discussion came up. Feeling was it's an immediate encroach on RT territory. I argued for it ;-) Ultimately, taking a more relaxed view, we chose to wait and see what the response is and most pressing use cases people bring to it and then we start to define bits and bytes of the options supported, possibly borrowing to an extent from the ORF specs ;-) As in "most sincere form of flattery" and such ... ;-) -- tony --001a11409584ad982d0537635815 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Mon, Jul 11, 2016 at 1:47 PM, Robert Raszuk <robert@raszuk.net&= gt; wrote:
Hi Tony,

Hey Robert, thanks for chiming in= . Good questions. I speak here for myself, other authors of the draft may h= ave differing opinions.=C2=A0
=C2=A0

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

We didn'= t discuss that one through but the only logical conclusion for me is that t= he ORF/CP-ORF installed are respected (i.e. it's an implicit AND). I se= e ORF as statefull, remote-pushed policy on the peer that is not being flip= ped around all the time (albeit AFAIR there were some attempts @ non-persis= tent, one shot ORF but that ended up expiring?)

Th= e motivation for this work were scenarios where a single-shot refresh is ne= eded, actually concurrent bunch of those based on configuration changes, pe= er having dropped received routes based on specs (A-D), in policy changes, = joining VPNs, EVIs and so on. Putting ORF on a peer, refresh and remove ORF= s is significantly heavier process that may interfere on top with normal up= date process going on and needs to be done one-by-one (since you have to wa= it for single BoRR/EoRR pair) unless one is very smart about combining ORF = possibly & playing with the DEFER/IMMEDIATEs. As we indicated, if the A= FI/SAFI is covered by RTC and RTC is supported & one is willing to conf= igure RTs for each subset of routes that may need refreshing, RT will be do= ing the same job just fine.=C2=A0
=C2=A0

Would you always carry ORF with separate Ref= resh_ID value ?=C2=A0

Yes, Refr= esh-ID# is strictly monotonic so there is never a misunderstanding WHAT the= BoRR belongs to. Observe that the draft does NOT mandate that a request MU= ST be followed by according BoRR, only that BoRRs must follow same sequence= as requests (i.e. are also strictly monotonic). However, we should probabl= y specify that options _and_ ORF can NOT be mixed in the same type #3 messa= ge but it's either one or the other (and anything else is error). This = will allow ORF operations like today + benefit of the Refresh ID# =C2=A0on = the BoRR so the IMMEDIATE can go on @ the same time as another request with= higher Refresh ID# (de facto we allow multiple parallel refreshes as you s= ee).=C2=A0 In case of DEFER there will be simply no BoRR for it.=C2=A0
=C2=A0

If one re= quests 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 im= pact to ORF ADDs or REMOVE actions - don't you think ?=C2=A0

I agree. Yes, ORF is kind of =C2=A0"= permanent filter" on the peer while the intent of this draft is to hav= e bunch of "small refreshes" going on @ same time possibly (if yo= u request the refreshes from a good implementation while low-end implementa= tions may serialize the requests to simplify internal logic ;-).=C2=A0
=C2=A0

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

Discussion came up. Feeling was it's an immedi= ate encroach on RT territory. I argued for it ;-) =C2=A0Ultimately, taking = a more relaxed view, we chose to wait and see what the response is and most= pressing use cases people bring to it and then we start to define bits and= bytes of the options supported, possibly borrowing to an extent from the O= RF specs ;-) =C2=A0As in "most sincere form of flattery" and such= ... ;-)=C2=A0

-- tony=C2=A0
=C2=A0
--001a11409584ad982d0537635815-- From nobody Mon Jul 11 15:59:14 2016 Return-Path: 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 80FF612D596 for ; Mon, 11 Jul 2016 15:59:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -15.807 X-Spam-Level: X-Spam-Status: No, score=-15.807 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 Z50ggFWWkcAU for ; Mon, 11 Jul 2016 15:59:11 -0700 (PDT) Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2131312D0AE for ; Mon, 11 Jul 2016 15:59:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=33443; q=dns/txt; s=iport; t=1468277951; x=1469487551; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=hME1svnKWzIRV7hOYVcwNBpBjliJXVZIWFDfN0DEaHs=; b=O08xr6fJLg+vEbnz7Dbm0vRm74vNQLh3hZKlwlz8NjQypxEPyhECsTtL Wo7cVZQXdcbfGf+Je99npHBNSaj59XzATTr/0/eFesZFnOtuC7gBrjjU/ VF3yJvFECAgRQrmUpUSt/7tV5lG8u/MJh7Mx0wQm2c3xxWMyvkfCERSAO w=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BLAgDQI4RX/51dJa1cgnBOgVIGrGuMF?= =?us-ascii?q?oF6hhgCHIEQOBQBAQEBAQEBZSeEXAEBBSNEDQUQAgEIEQMBAiEHAwICAh8RFAk?= =?us-ascii?q?IAgQOBYgWAxewP4pcDYN+AQEBAQEBAQMBAQEBAQEBAQEeiXGBA4JDgVpEgmGCW?= =?us-ascii?q?gWTXIUINAGMO4IWgWqEWIhqiBuHcwEeNoNxbod7RX8BAQE?= X-IronPort-AV: E=Sophos;i="5.28,348,1464652800"; d="scan'208,217";a="295890512" Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 11 Jul 2016 22:59:10 +0000 Received: from XCH-RTP-019.cisco.com (xch-rtp-019.cisco.com [64.101.220.159]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id u6BMx9Td001195 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 11 Jul 2016 22:59:09 GMT Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-019.cisco.com (64.101.220.159) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 11 Jul 2016 18:59:08 -0400 Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1210.000; Mon, 11 Jul 2016 18:59:08 -0400 From: "Acee Lindem (acee)" To: Robert Raszuk Thread-Topic: Shortest Path Routing Extensions for BGP Protocol Thread-Index: AQHR2TCrYqWhF/FuxECJ8BfBQYUWB6AOt3SAgAIPJgCAAxangA== Date: Mon, 11 Jul 2016 22:59:08 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.116.152.196] Content-Type: multipart/alternative; boundary="_000_D3A980476A7C5aceeciscocom_" MIME-Version: 1.0 Archived-At: Cc: "Keyur Patel \(keyupate\)" , "Derek Man-Kit Yeung \(myeung\)" , idr wg Subject: Re: [Idr] Shortest Path Routing Extensions for BGP Protocol X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jul 2016 22:59:13 -0000 --_000_D3A980476A7C5aceeciscocom_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 SGkgUm9iZXJ0LA0KU2VlIGlubGluZS4NCg0KRnJvbTogPHJyYXN6dWtAZ21haWwuY29tPG1haWx0 bzpycmFzenVrQGdtYWlsLmNvbT4+IG9uIGJlaGFsZiBvZiBSb2JlcnQgUmFzenVrIDxyb2JlcnRA cmFzenVrLm5ldDxtYWlsdG86cm9iZXJ0QHJhc3p1ay5uZXQ+Pg0KRGF0ZTogU2F0dXJkYXksIEp1 bHkgOSwgMjAxNiBhdCAzOjQ5IFBNDQpUbzogQWNlZSBMaW5kZW0gPGFjZWVAY2lzY28uY29tPG1h aWx0bzphY2VlQGNpc2NvLmNvbT4+DQpDYzogIktleXVyIFBhdGVsIChrZXl1cGF0ZSkiIDxrZXl1 cGF0ZUBjaXNjby5jb208bWFpbHRvOmtleXVwYXRlQGNpc2NvLmNvbT4+LCAiQWJoYXkgUm95IChh a3IpIiA8YWtyQGNpc2NvLmNvbTxtYWlsdG86YWtyQGNpc2NvLmNvbT4+LCAiRGVyZWsgTWFuLUtp dCBZZXVuZyAobXlldW5nKSIgPG15ZXVuZ0BjaXNjby5jb208bWFpbHRvOm15ZXVuZ0BjaXNjby5j b20+PiwgIlZlbnUgVmVudWdvcGFsICh2ZW51dikiIDx2ZW51dkBjaXNjby5jb208bWFpbHRvOnZl bnV2QGNpc2NvLmNvbT4+LCBJRFIgTGlzdCA8aWRyQGlldGYub3JnPG1haWx0bzppZHJAaWV0Zi5v cmc+Pg0KU3ViamVjdDogUmU6IFNob3J0ZXN0IFBhdGggUm91dGluZyBFeHRlbnNpb25zIGZvciBC R1AgUHJvdG9jb2wNCg0KSGkgQUMsDQoNCk1hbnkgdGh4IGZvciByZXNwb25kaW5nLg0KDQpBcyBm YXIgYXMgeW91ciBxdWVzdGlvbiAxMDBLKyB3YXMgYWJvdXQgbnVtYmVyIG9mIGNvbXB1dGUgbm9k ZXMsIHZpcnR1YWwgY29tcHV0ZSBub2RlcyBpbiBmbGF0IHJvdXRpbmcgKGVuYWJsZWQgdmlhIFNS LUlPVikgJiBzd2l0Y2hlcyB0b2dldGhlciBhcyBpbiB5b3VyIHByb3Bvc2FsIGVhY2ggb2YgdGhl bSBpcyBhIG5vZGUgaW4gdGhlIFNQVC4gVW5sZXNzIHlvdSBhcmUgcGxhbm5pbmcgdG8gaW50cm9k dWNlIGFuYWxvZ3kgdG8gb3NwZiBhcmVhcyBoZXJlIDopDQoNCk5vIGFyZWFzIGhlcmXigKYgSWYg eW91IGFyZSBydW5uaW5nIEJHUCBvbiB0aGUgMTAwSysgY29tcHV0ZSBub2RlcyBhcyBJIGJlbGll dmUgeW91IGFyZSBzdWdnZXN0aW5nIHdpdGggdGhlIHJlZmVyZW5jZSB0byBTUi1JT1YsIHlvdSB3 b3VsZCBwcm9iYWJseSBub3Qgd2FudCBmbGF0IHJvdXRpbmcuIEluIG1hbnkgb2YgdG9kYXkgRENz LCB0aGUgY29tcHV0ZSBub2RlcyBhcmUgbWVyZWx5IGhvc3RzIG9uIFRvUiBzdWJuZXRzIGFuZCB0 aGVzZSBwcmVmaXhlcyBjYW4gYmUgZWFzaWx5IGNvbXB1dGVkIHVzaW5nIFNQRiBvcHRpbWl6YXRp b25zLg0KDQoNCkluIGFueSBjYXNlIHRoZSBtb3N0IHBvd2VyZnVsIHByb3BlcnR5IG9mIEJHUCBp cyBoaWVyYXJjaHkgYW5kIChtdWx0aS1sZXZlbCkgaW5kaXJlY3Rpb24gdmlhIG5leHQgaG9wLiBJ biBub3JtYWwgQkdQIGRlcGxveW1lbnRzIG5leHQgaG9wcyB3aGljaCBhcmUgY2FycmllZCBpbiBC R1AgYXJlIHJlc29sdmVkIGluIElHUC4gSW4gREMgY2FzZXMgd2hlcmUgZUJHUCBpcyB1c2VkIGJl dHdlZW4gYWxsIGZhYnJpYyBzdGFnZXMgbmV4dCBob3BzIHJlc29sdmVzIHRvIGNvbm5lY3RlZCBy b3V0ZXMuDQoNCkluIHlvdXIgY2FzZSBpbiBmbGF0IHJvdXRpbmcgeW91IG5vIGxvbmdlciBoYXZl IHN1Y2ggcmVjdXJzaW9uLg0KDQpIb3dldmVyIEkgYXNzdW1lIHlvdXIgcHJvcG9zYWwgY2FuIGNv ZXhpc3Qgd2l0aCBvdGhlciBTQUZJcyBhbmQgc2F5IGV4dGVybmFsIHRvIHRoZSBEQyBkZXNpdG5h dGlvbnMgd2lsbCBiZSBzdGlsbCBjYXJyaWVkIGluIDEvMSBvciAyLzEgYW5kIHRoZWlyIG5leHQg aG9wcyB3aWxsIGJlIHJlc29sdmVkIGJ5IHJvdXRlcyBpbnNlcnRlZCBpbnRvIFJJQiBieSBydW5u aW5nIFNQRiBjb3JyZWN0Pw0KDQpBcyBLZXl1ciByZXNwb25kZWQsIFNQRiByb3V0ZXMgY291bGQg YmUgdXNlZCBmb3IgcmVzb2x1dGlvbiBvZiBvdGhlciBTQUZJcy4NCg0KDQpMYXN0IC4uIExGQSBp cyBhIGdyZWF0IHRlY2hub2xvZ3kgaG93ZXZlciBJIGFtIG5vdCBzdXJlIGlmIGVuYWJsaW5nIGl0 IGluIHRvcG9sb2dpZXMgd2hlcmUgeW91IGhhdmUgMTBzIG9mIEVDTVAgYWN0aXZlIHBhdGhzIGFu ZCB3aGVyZSB5b3UgYXJlIHJlYWR5IGJ5IGRlc2lnbiBmb3IgYSBmYWlsdXJlIGhhbmRsaW5nIGlz IGEgcmlnaHQgdGhpbmcgdG8gZG8uIFdoYXQgYXJlIG90aGVyIHJlYWwgdXNlIGNhc2VzIGZvciBn aXZpbmcgdXAgb24gcHVyZSBCR1AgYmVzdCBwYXRoIHNlbGVjdGlvbiBhbmQgbm9ybWFsIEJHUCBt dWx0aXBhdGggPw0KDQpJIGFncmVlIHRoYXQgdGhlIHZhbHVlIG9mIExGQSBpcyBsaW1pdGVkIGlm IHlvdSBoYXZlIHByZXZhbGVudCBFQ01QIGFuZCBhIGRhdGEgcGxhbmUgdGhhdCBkb2VzIGZhc3Qg RUNNUCByZWhhc2hpbmcgaW4gdGhlIGV2ZW50IG9mIGZhaWx1cmUuIFRoZSBvdGhlciBpbmhlcmVu dCBhZHZhbnRhZ2Ugb2YgU1BGLWJhc2VkIGNvbXB1dGF0aW9uIGlzIHRoYXQgYSBzaW5nbGUgZmFp bHVyZSBvbmx5IHJlc3VsdHMgaW4gdGhlIGRpcmVjdGx5IGltcGFjdGVkIE5MUkkgYmVpbmcgYWR2 ZXJ0aXNlZCBhcyBvcHBvc2VkIHRvIGFsbCB0aGUgaW1wYWN0ZWQgcHJlZml4ZXMgaGF2aW5nIHRv IHByb3BhZ2F0ZSBob3AtYnktaG9wLiBUaGlzIHNob3VsZCBpbXByb3ZlIGNvbnZlcmdlbmNlIGFu ZCBldmVuIHNjYWxpbmcuDQoNClRoYW5rcywNCkFjZWUNCg0KDQoNCkJlc3QgcmVnYXJkcywNClIu DQoNCg0KT24gRnJpLCBKdWwgOCwgMjAxNiBhdCA2OjIyIFBNLCBBY2VlIExpbmRlbSAoYWNlZSkg PGFjZWVAY2lzY28uY29tPG1haWx0bzphY2VlQGNpc2NvLmNvbT4+IHdyb3RlOg0KSGkgUm9iZXJ0 LA0KDQpUaGFua3MgZm9yIGVuZ2FnaW5n4oCmDQoNCkZyb206IDxycmFzenVrQGdtYWlsLmNvbTxt YWlsdG86cnJhc3p1a0BnbWFpbC5jb20+PiBvbiBiZWhhbGYgb2YgUm9iZXJ0IFJhc3p1ayA8cm9i ZXJ0QHJhc3p1ay5uZXQ8bWFpbHRvOnJvYmVydEByYXN6dWsubmV0Pj4NCkRhdGU6IEZyaWRheSwg SnVseSA4LCAyMDE2IGF0IDExOjUxIEFNDQpUbzogIktleXVyIFBhdGVsIChrZXl1cGF0ZSkiIDxr ZXl1cGF0ZUBjaXNjby5jb208bWFpbHRvOmtleXVwYXRlQGNpc2NvLmNvbT4+LCBBY2VlIExpbmRl bSA8YWNlZUBjaXNjby5jb208bWFpbHRvOmFjZWVAY2lzY28uY29tPj4sICJBYmhheSBSb3kgKGFr cikiIDxha3JAY2lzY28uY29tPG1haWx0bzpha3JAY2lzY28uY29tPj4sICJEZXJlayBNYW4tS2l0 IFlldW5nIChteWV1bmcpIiA8bXlldW5nQGNpc2NvLmNvbTxtYWlsdG86bXlldW5nQGNpc2NvLmNv bT4+LCAiVmVudSBWZW51Z29wYWwgKHZlbnV2KSIgPHZlbnV2QGNpc2NvLmNvbTxtYWlsdG86dmVu dXZAY2lzY28uY29tPj4NCkNjOiBJRFIgTGlzdCA8aWRyQGlldGYub3JnPG1haWx0bzppZHJAaWV0 Zi5vcmc+Pg0KU3ViamVjdDogU2hvcnRlc3QgUGF0aCBSb3V0aW5nIEV4dGVuc2lvbnMgZm9yIEJH UCBQcm90b2NvbA0KDQpIaSwNCg0KSSBoYXZlIHJldmlld2VkIHlvdXIgcHJvcG9zYWwuDQoNClR1 cm5pbmcgcGF0aCB2ZWN0b3Igb3IgZGlzdGFuY2UgdmVjdG9yIHByb3RvY29sIGludG8gbGluayBz dGF0ZSBjYXJyaWVyIGlzIG5vIGRvdWJ0IGEgYm9sZCBpZGVhIDopLg0KDQrigJxGb3J0dW5lIGJl ZnJpZW5kcyB0aGUgYm9sZC7igJ0gLUVtaWx5IERpY2tpbnNvbg0KDQoNCkVmZmVjdGl2ZWx5IHdo YXQgeW91IGFyZSBwcm9wb3NpbmcgaXMgdG8gdXNlIEJHUCBUQ1Agc2Vzc2lvbnMgdG8gcHJvcGFn YXRlIGxpbmsgc3RhdGUgZGF0YWJhc2UgY3JlYXRpbmcgZmlyc3QgImxpbmsgdmVjdG9yIHByb3Rv Y29sIiAhDQoNCkZvciBzdGFydCBJIGhhdmUgZmV3IHF1ZXN0aW9uczoNCg0KUTE6DQoNClJGQzc3 NTIgaGFzIGdvbmUgdmlhIGxvdCBvZiBlZmZvcnRzIChlc3BlY2lhbGx5IHNlY3Rpb25zIDMuMiBh bmQgdXApIHRvIGluY2x1ZGUgbnVtYmVyIG9mIE9TUEYgb3IgSVNJUyBzcGVjaWZpYyBlbmNvZGlu Z3MuIEluIHlvdXIgcHJvcG9zYWwgeW91IG1lbnRpb25lZCBPU1BGIHR3aWNlIGFuZCBub3QgZXZl biBvbmNlIElTSVMuIERvZXMgaXQgbWVhbiB0aGF0IHlvdSBhcmUgbm90IGdvaW5nIHRvIHVzZSBh bGwgZW5jb2RpbmcgZm9yIHNwZWNpZmljIElHUHMgYXMgZGVmaW5lZCBpbiBSRkM3NzUyID8NCg0K V2UgYXJlIHVzaW5nIHRoZSBCR1AgUHJvdG9jb2wtSUQgZGVmaW5lZCBmb3IgQkdQLUVQRS4gVGhl IElBTkEgcmVxdWVzdCB3aWxsIGJlIGdlbmVyYWxpemVkIGZyb20g4oCcQkdQLUVQReKAnSB0byDi gJxCR1DigJ0gaW4gc3VwcG9ydCBvZiBTZWdtZW50IFJvdXRpbmcgYW5kIG90aGVyIGVuaGFuY2Vt ZW50cy4gVGhlIEJHUC1MUyBOTFJJIGFyZSBzcGVjaWZpYyBCR1AgYW5kIG5vdCBlaXRoZXIgSVMt SVMgb3IgT1NQRi4NCg0KDQpRMjoNCg0KV2hvIGNyZWF0ZXMgYW5kIG1haW50YWlucyBMU0RCIGlu IGVhY2ggQkdQIHNwZWFrZXIgPyBBcmUgeW91IHBsYW5uaW5nIHRvIHJ1biBPU1BGIGFuZCBvciBJ U0lTIGV4Y2VwdCBkaXNhYmxlIGl0IHRvIGVzdGFibGlzaCBhbnkgYWRqYWNpZW5jaWVzID8NCg0K SeKAmXZlIHNlZW4gZGVzaWducyBsaWtlIHRoaXMgaW4gbXkgdGltZSBidXQgaGF2ZSBuZXZlciBi ZWVuIG9mIGEgZmFuIG9mIHRoZW0gO14pLiBCR1Agd2lsbCBkbyB0aGUgU1BGIGRpcmVjdGx5IGFu ZCBtYWludGFpbiB0aGUgU1BULiBZb3XigJlsbCBub3RlIHRoYXQgYSBzaW1wbGlmaWVkIFNQRiBp cyBhbHJlYWR5IGRvbmUgZm9yIE9SUi4NCg0KDQpRMzoNCg0KQ3VycmVudGx5IHRoZXJlIGFyZSBh bHJlYWR5IHRvIG1vZGVscyB0byBidWlsZCBEQ3Mgd2l0aCBCR1AgLi4uIG9uZSB1c2VzIEJHUCB0 byBjcmVhdGUgb25seSBsZWFuIHVuZGVybGF5IHRoZSBvdGhlciBpcyB0byB1c2UgQkdQIGZvciBi b3RoIHVuZGVybGF5IGFuZCB0ZW5hbnRzIChleGFtcGxlIHByb2plY3QgQ2FsaWNvIGZvciB0aGUg bGF0dGVyKS4gV2l0aCB0aGF0IHNjYWxlIHdpc2UgSSB0aGluayB5b3VyIHByb3Bvc2FsIHdpbGwg d29yayBncmVhdCBmb3IgdGhlIGZvcm1lci4gSG93ZXZlciBJIGRvIGhhdmUgY29uY2VybnMgYWJv dXQgdXNpbmcgeW91ciBtb2RlbCBmb3IgdGhlIGxhdHRlciB3aGVyZSBzYXkgMTAsMDAwIG9yIDEw MCwwMDAgLzMycyBvciAvMTI4cyBmcm9tIGVhY2ggVk1zIGFyZSBpbmplY3RlZCBhbmQgeW91IG5l ZWQgdG8gY29uc3RydWN0IFNQVCB3aXRoIGFsbCBvZiB0aG9zZS4NCg0KU2ltaWxhciB0byB0aG9z ZSBkZXNpZ25zLCB0aGUgU1BUIGNvdWxkIGJlIGxpbWl0ZWQgdG8gdGhlIHVuZGVybGF5LiBIb3dl dmVyLCBpZiB0aGVyZSBpcyBubyByZXF1aXJlbWVudCBmb3IgdGhlIGJlbmVmaXRzIG9mIEwyIG9y IEwzIFZQTnMsIEkgc2VlIG5vIHJlYXNvbiB3aHkgdGhlc2UgMTAwS3Mgb2YgbGVhZnMgVk0gcHJl Zml4ZXMgaW4gREMgY2VudGVyIGNvdWxkbuKAmXQgYmUgc3VwcG9ydGVkLg0KDQoNClE0Og0KDQpS ZWxhdGVkIHRvIFEzIGluIHlvdXIgbW9kZWwgYW5kIHNheSBmbGF0IERDIHJvdXRpbmcgZWFjaCBj b21wdXRlIG5vZGUgb3RoZXIgdGhlbiBqdXN0IGluamVjdGluZyAxMHMgb2YgLzMycyBhbmQgYmVp bmcgImRvbmUiIG5vdyBiZWNvbWVzIGFuIElHUCBub2RlLiBTaW5jZSB5b3VyIGRvY3VtZW50IGV4 cGxpY2l0ZWx5IHRhcmdldHMgTWFzc2l2ZWx5IFNjYWxlZCBEYXRhIENlbnRlcnMgKE1TRENzKSBJ IGFtIGNvbmNlcm5lZCB0aGF0IGhhdmluZyAxMDAsMDAwKyBJR1Agbm9kZXMgYW5kIGluIG1hbnkg Y2FzZSBtdWNoIG1vcmUgaXMgbm90IHRoZSBiZXN0IGlkZWEuDQoNCjEwMEsrIHN3aXRjaGVzIGlu IGEgc2luZ2xlIERDIGZhYnJpYyAoaS5lLiwgQkdQIHJvdXRpbmcgZG9tYWluKT8gSSBoYXZlIHNv bWUgZXhwZXJpZW5jZSBpbiBsaW5rLXN0YXRlIHByb3RvY29scyBhbmQgSSBjYW4gdGVsbCB5b3Ug dGhhdCBPU1BGIGlzIEkvTyBib3VuZCBtYWlubHkgZHVlIHRvIHRoZSBmbG9vZGluZy4gSWYgZG9u ZSByaWdodCwgdGhlIFNQRiBjYWxjdWxhdGlvbiBjYW4gYmUgZG9uZSB3aXRoIG1pbmltYWwgY29t cHV0YXRpb24uIFdoaWxlIEJHUC1MUyBpc27igJl0IHRoZSB3b3JsZCdzIG1vc3QgY29tcGFjdCBl bmNvZGluZywgaXQgaXMgY29tcGxldGVseSBpbmNyZW1lbnRhbC4NCg0KDQpRNToNCg0KSGF2ZSB5 b3UgY29uc2lkZXJlZCBqdXN0IHByb3Bvc2luZyBhbiBPU1BGIHJvdXRlIHJlZmxlY3RvciBpbnN0 ZWFkIHdpdGhvdXQgc3R1ZmZpbmcgQkdQIGludG8gdGhlIG1peCA/IEFzIHNvbWUgb2YgeW91IHBl cmhhcHMgcmVtZW1iZXIgdGhlIHdvcmsgb24gdGhpcyBzdGFydGVkIGFyb3VuZCB5ZWFyIDIwMDAg dG8gb3B0aW1pemUgUEUtQ0UgQ1NDIGRlcGxveW1lbnRzIDopIEl0IHNlZW1zIHRvIG1lIHZlcnkg cmV1c2FibGUgZm9yIHRoaXMgZ29hbC4NCg0KV2UgbG9va2VkIGF0IGxvdHMgb2YgYWx0ZXJuYXRp dmVzIGFuZCB0aGlzIG9uZSBzZWVtZWQgbGlrZSB0aGUgYmVzdCBvbmUuIFBsZWFzZSBwYXNzIG1l IGEgcG9pbnRlciB0byB0aGUgd29yayB5b3UgbWVudGlvbi4NCg0KVGhhbmtzLA0KQWNlZQ0KDQoN Cg0KQmVzdCByZWdhcmRzLA0KUm9iZXJ0Lg0KDQoNCg== --_000_D3A980476A7C5aceeciscocom_ Content-Type: text/html; charset="utf-8" Content-ID: Content-Transfer-Encoding: base64 PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsgY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1zaXplOiAx NHB4OyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsiPg0KPGRpdj5IaSBSb2JlcnQs Jm5ic3A7PC9kaXY+DQo8ZGl2PlNlZSBpbmxpbmUuJm5ic3A7PC9kaXY+DQo8ZGl2Pjxicj4NCjwv ZGl2Pg0KPHNwYW4gaWQ9Ik9MS19TUkNfQk9EWV9TRUNUSU9OIj4NCjxkaXYgc3R5bGU9ImZvbnQt ZmFtaWx5OkNhbGlicmk7IGZvbnQtc2l6ZToxMXB0OyB0ZXh0LWFsaWduOmxlZnQ7IGNvbG9yOmJs YWNrOyBCT1JERVItQk9UVE9NOiBtZWRpdW0gbm9uZTsgQk9SREVSLUxFRlQ6IG1lZGl1bSBub25l OyBQQURESU5HLUJPVFRPTTogMGluOyBQQURESU5HLUxFRlQ6IDBpbjsgUEFERElORy1SSUdIVDog MGluOyBCT1JERVItVE9QOiAjYjVjNGRmIDFwdCBzb2xpZDsgQk9SREVSLVJJR0hUOiBtZWRpdW0g bm9uZTsgUEFERElORy1UT1A6IDNwdCI+DQo8c3BhbiBzdHlsZT0iZm9udC13ZWlnaHQ6Ym9sZCI+ RnJvbTogPC9zcGFuPiZsdDs8YSBocmVmPSJtYWlsdG86cnJhc3p1a0BnbWFpbC5jb20iPnJyYXN6 dWtAZ21haWwuY29tPC9hPiZndDsgb24gYmVoYWxmIG9mIFJvYmVydCBSYXN6dWsgJmx0OzxhIGhy ZWY9Im1haWx0bzpyb2JlcnRAcmFzenVrLm5ldCI+cm9iZXJ0QHJhc3p1ay5uZXQ8L2E+Jmd0Ozxi cj4NCjxzcGFuIHN0eWxlPSJmb250LXdlaWdodDpib2xkIj5EYXRlOiA8L3NwYW4+U2F0dXJkYXks IEp1bHkgOSwgMjAxNiBhdCAzOjQ5IFBNPGJyPg0KPHNwYW4gc3R5bGU9ImZvbnQtd2VpZ2h0OmJv bGQiPlRvOiA8L3NwYW4+QWNlZSBMaW5kZW0gJmx0OzxhIGhyZWY9Im1haWx0bzphY2VlQGNpc2Nv LmNvbSI+YWNlZUBjaXNjby5jb208L2E+Jmd0Ozxicj4NCjxzcGFuIHN0eWxlPSJmb250LXdlaWdo dDpib2xkIj5DYzogPC9zcGFuPiZxdW90O0tleXVyIFBhdGVsIChrZXl1cGF0ZSkmcXVvdDsgJmx0 OzxhIGhyZWY9Im1haWx0bzprZXl1cGF0ZUBjaXNjby5jb20iPmtleXVwYXRlQGNpc2NvLmNvbTwv YT4mZ3Q7LCAmcXVvdDtBYmhheSBSb3kgKGFrcikmcXVvdDsgJmx0OzxhIGhyZWY9Im1haWx0bzph a3JAY2lzY28uY29tIj5ha3JAY2lzY28uY29tPC9hPiZndDssICZxdW90O0RlcmVrIE1hbi1LaXQg WWV1bmcgKG15ZXVuZykmcXVvdDsgJmx0OzxhIGhyZWY9Im1haWx0bzpteWV1bmdAY2lzY28uY29t Ij5teWV1bmdAY2lzY28uY29tPC9hPiZndDssDQogJnF1b3Q7VmVudSBWZW51Z29wYWwgKHZlbnV2 KSZxdW90OyAmbHQ7PGEgaHJlZj0ibWFpbHRvOnZlbnV2QGNpc2NvLmNvbSI+dmVudXZAY2lzY28u Y29tPC9hPiZndDssIElEUiBMaXN0ICZsdDs8YSBocmVmPSJtYWlsdG86aWRyQGlldGYub3JnIj5p ZHJAaWV0Zi5vcmc8L2E+Jmd0Ozxicj4NCjxzcGFuIHN0eWxlPSJmb250LXdlaWdodDpib2xkIj5T dWJqZWN0OiA8L3NwYW4+UmU6IFNob3J0ZXN0IFBhdGggUm91dGluZyBFeHRlbnNpb25zIGZvciBC R1AgUHJvdG9jb2w8YnI+DQo8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBp ZD0iTUFDX09VVExPT0tfQVRUUklCVVRJT05fQkxPQ0tRVU9URSIgc3R5bGU9IkJPUkRFUi1MRUZU OiAjYjVjNGRmIDUgc29saWQ7IFBBRERJTkc6MCAwIDAgNTsgTUFSR0lOOjAgMCAwIDU7Ij4NCjxk aXY+DQo8ZGl2Pg0KPGRpdiBkaXI9Imx0ciI+DQo8ZGl2IGNsYXNzPSJnbWFpbF9kZWZhdWx0IiBz dHlsZT0iZm9udC1mYW1pbHk6YXJpYWwsaGVsdmV0aWNhLHNhbnMtc2VyaWY7Zm9udC1zaXplOnNt YWxsIj4NCkhpIEFDLDwvZGl2Pg0KPGRpdiBjbGFzcz0iZ21haWxfZGVmYXVsdCIgc3R5bGU9ImZv bnQtZmFtaWx5OmFyaWFsLGhlbHZldGljYSxzYW5zLXNlcmlmO2ZvbnQtc2l6ZTpzbWFsbCI+DQo8 YnI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9ImdtYWlsX2RlZmF1bHQiIHN0eWxlPSJmb250LWZhbWls eTphcmlhbCxoZWx2ZXRpY2Esc2Fucy1zZXJpZjtmb250LXNpemU6c21hbGwiPg0KTWFueSB0aHgg Zm9yIHJlc3BvbmRpbmcuJm5ic3A7PC9kaXY+DQo8ZGl2IGNsYXNzPSJnbWFpbF9kZWZhdWx0IiBz dHlsZT0iZm9udC1mYW1pbHk6YXJpYWwsaGVsdmV0aWNhLHNhbnMtc2VyaWY7Zm9udC1zaXplOnNt YWxsIj4NCjxicj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iZ21haWxfZGVmYXVsdCIgc3R5bGU9ImZv bnQtZmFtaWx5OmFyaWFsLGhlbHZldGljYSxzYW5zLXNlcmlmO2ZvbnQtc2l6ZTpzbWFsbCI+DQpB cyBmYXIgYXMgeW91ciBxdWVzdGlvbiAxMDBLJiM0Mzsgd2FzIGFib3V0IG51bWJlciBvZiBjb21w dXRlIG5vZGVzLCB2aXJ0dWFsIGNvbXB1dGUgbm9kZXMgaW4gZmxhdCByb3V0aW5nIChlbmFibGVk IHZpYSBTUi1JT1YpICZhbXA7IHN3aXRjaGVzIHRvZ2V0aGVyIGFzIGluIHlvdXIgcHJvcG9zYWwg ZWFjaCBvZiB0aGVtIGlzIGEgbm9kZSBpbiB0aGUgU1BULiBVbmxlc3MgeW91IGFyZSBwbGFubmlu ZyB0byBpbnRyb2R1Y2UgYW5hbG9neSB0byBvc3BmIGFyZWFzDQogaGVyZSA6KTwvZGl2Pg0KPC9k aXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9zcGFuPg0KPGRpdj48YnI+DQo8 L2Rpdj4NCjxkaXY+Tm8gYXJlYXMgaGVyZeKApiBJZiB5b3UgYXJlIHJ1bm5pbmcgQkdQIG9uIHRo ZSAxMDBLJiM0MzsgY29tcHV0ZSBub2RlcyBhcyBJIGJlbGlldmUgeW91IGFyZSBzdWdnZXN0aW5n IHdpdGggdGhlIHJlZmVyZW5jZSB0byBTUi1JT1YsIHlvdSB3b3VsZCBwcm9iYWJseSBub3Qgd2Fu dCBmbGF0IHJvdXRpbmcuIEluIG1hbnkgb2YgdG9kYXkgRENzLCB0aGUgY29tcHV0ZSBub2RlcyBh cmUgbWVyZWx5IGhvc3RzIG9uIFRvUiBzdWJuZXRzIGFuZCB0aGVzZSBwcmVmaXhlcw0KIGNhbiBi ZSBlYXNpbHkgY29tcHV0ZWQgdXNpbmcgU1BGIG9wdGltaXphdGlvbnMuJm5ic3A7PC9kaXY+DQo8 ZGl2Pjxicj4NCjwvZGl2Pg0KPHNwYW4gaWQ9Ik9MS19TUkNfQk9EWV9TRUNUSU9OIj4NCjxibG9j a3F1b3RlIGlkPSJNQUNfT1VUTE9PS19BVFRSSUJVVElPTl9CTE9DS1FVT1RFIiBzdHlsZT0iQk9S REVSLUxFRlQ6ICNiNWM0ZGYgNSBzb2xpZDsgUEFERElORzowIDAgMCA1OyBNQVJHSU46MCAwIDAg NTsiPg0KPGRpdj4NCjxkaXY+DQo8ZGl2IGRpcj0ibHRyIj4NCjxkaXYgY2xhc3M9ImdtYWlsX2Rl ZmF1bHQiIHN0eWxlPSJmb250LWZhbWlseTphcmlhbCxoZWx2ZXRpY2Esc2Fucy1zZXJpZjtmb250 LXNpemU6c21hbGwiPg0KPGJyPg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSJnbWFpbF9kZWZhdWx0IiBz dHlsZT0iZm9udC1mYW1pbHk6YXJpYWwsaGVsdmV0aWNhLHNhbnMtc2VyaWY7Zm9udC1zaXplOnNt YWxsIj4NCkluIGFueSBjYXNlIHRoZSBtb3N0IHBvd2VyZnVsIHByb3BlcnR5IG9mIEJHUCBpcyBo aWVyYXJjaHkgYW5kIChtdWx0aS1sZXZlbCkgaW5kaXJlY3Rpb24gdmlhIG5leHQgaG9wLiBJbiBu b3JtYWwgQkdQIGRlcGxveW1lbnRzIG5leHQgaG9wcyB3aGljaCBhcmUgY2FycmllZCBpbiBCR1Ag YXJlIHJlc29sdmVkIGluIElHUC4gSW4gREMgY2FzZXMgd2hlcmUgZUJHUCBpcyB1c2VkIGJldHdl ZW4gYWxsIGZhYnJpYyBzdGFnZXMgbmV4dCBob3BzIHJlc29sdmVzDQogdG8gY29ubmVjdGVkIHJv dXRlcy4mbmJzcDs8L2Rpdj4NCjxkaXYgY2xhc3M9ImdtYWlsX2RlZmF1bHQiIHN0eWxlPSJmb250 LWZhbWlseTphcmlhbCxoZWx2ZXRpY2Esc2Fucy1zZXJpZjtmb250LXNpemU6c21hbGwiPg0KPGJy Pg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSJnbWFpbF9kZWZhdWx0IiBzdHlsZT0iZm9udC1mYW1pbHk6 YXJpYWwsaGVsdmV0aWNhLHNhbnMtc2VyaWY7Zm9udC1zaXplOnNtYWxsIj4NCkluIHlvdXIgY2Fz ZSBpbiBmbGF0IHJvdXRpbmcgeW91IG5vIGxvbmdlciBoYXZlIHN1Y2ggcmVjdXJzaW9uLiZuYnNw OzwvZGl2Pg0KPGRpdiBjbGFzcz0iZ21haWxfZGVmYXVsdCIgc3R5bGU9ImZvbnQtZmFtaWx5OmFy aWFsLGhlbHZldGljYSxzYW5zLXNlcmlmO2ZvbnQtc2l6ZTpzbWFsbCI+DQo8YnI+DQo8L2Rpdj4N CjxkaXYgY2xhc3M9ImdtYWlsX2RlZmF1bHQiIHN0eWxlPSJmb250LWZhbWlseTphcmlhbCxoZWx2 ZXRpY2Esc2Fucy1zZXJpZjtmb250LXNpemU6c21hbGwiPg0KSG93ZXZlciBJIGFzc3VtZSB5b3Vy IHByb3Bvc2FsIGNhbiBjb2V4aXN0IHdpdGggb3RoZXIgU0FGSXMgYW5kIHNheSBleHRlcm5hbCB0 byB0aGUgREMgZGVzaXRuYXRpb25zIHdpbGwgYmUgc3RpbGwgY2FycmllZCBpbiAxLzEgb3IgMi8x IGFuZCB0aGVpciBuZXh0IGhvcHMgd2lsbCBiZSByZXNvbHZlZCBieSByb3V0ZXMgaW5zZXJ0ZWQg aW50byBSSUIgYnkgcnVubmluZyBTUEYgY29ycmVjdD88L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8 L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvc3Bhbj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2PkFz IEtleXVyIHJlc3BvbmRlZCwgU1BGIHJvdXRlcyBjb3VsZCBiZSB1c2VkIGZvciByZXNvbHV0aW9u IG9mIG90aGVyIFNBRklzLiZuYnNwOzwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxzcGFuIGlk PSJPTEtfU1JDX0JPRFlfU0VDVElPTiI+DQo8YmxvY2txdW90ZSBpZD0iTUFDX09VVExPT0tfQVRU UklCVVRJT05fQkxPQ0tRVU9URSIgc3R5bGU9IkJPUkRFUi1MRUZUOiAjYjVjNGRmIDUgc29saWQ7 IFBBRERJTkc6MCAwIDAgNTsgTUFSR0lOOjAgMCAwIDU7Ij4NCjxkaXY+DQo8ZGl2Pg0KPGRpdiBk aXI9Imx0ciI+DQo8ZGl2IGNsYXNzPSJnbWFpbF9kZWZhdWx0IiBzdHlsZT0iZm9udC1mYW1pbHk6 YXJpYWwsaGVsdmV0aWNhLHNhbnMtc2VyaWY7Zm9udC1zaXplOnNtYWxsIj4NCjxicj4NCjwvZGl2 Pg0KPGRpdiBjbGFzcz0iZ21haWxfZGVmYXVsdCIgc3R5bGU9ImZvbnQtZmFtaWx5OmFyaWFsLGhl bHZldGljYSxzYW5zLXNlcmlmO2ZvbnQtc2l6ZTpzbWFsbCI+DQpMYXN0IC4uIExGQSBpcyBhIGdy ZWF0IHRlY2hub2xvZ3kgaG93ZXZlciBJIGFtIG5vdCBzdXJlIGlmIGVuYWJsaW5nIGl0IGluIHRv cG9sb2dpZXMgd2hlcmUgeW91IGhhdmUgMTBzIG9mIEVDTVAgYWN0aXZlIHBhdGhzIGFuZCB3aGVy ZSB5b3UgYXJlIHJlYWR5IGJ5IGRlc2lnbiBmb3IgYSBmYWlsdXJlIGhhbmRsaW5nIGlzIGEgcmln aHQgdGhpbmcgdG8gZG8uIFdoYXQgYXJlIG90aGVyIHJlYWwgdXNlIGNhc2VzIGZvciBnaXZpbmcg dXAgb24gcHVyZQ0KIEJHUCBiZXN0IHBhdGggc2VsZWN0aW9uIGFuZCBub3JtYWwgQkdQIG11bHRp cGF0aCA/Jm5ic3A7PC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+ DQo8L3NwYW4+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5JIGFncmVlIHRoYXQgdGhlIHZhbHVl IG9mIExGQSBpcyBsaW1pdGVkIGlmIHlvdSBoYXZlIHByZXZhbGVudCBFQ01QIGFuZCBhIGRhdGEg cGxhbmUgdGhhdCBkb2VzIGZhc3QgRUNNUCByZWhhc2hpbmcgaW4gdGhlIGV2ZW50IG9mIGZhaWx1 cmUuIFRoZSBvdGhlciBpbmhlcmVudCBhZHZhbnRhZ2Ugb2YgU1BGLWJhc2VkIGNvbXB1dGF0aW9u IGlzIHRoYXQgYSBzaW5nbGUgZmFpbHVyZSBvbmx5IHJlc3VsdHMgaW4gdGhlIGRpcmVjdGx5IGlt cGFjdGVkDQogTkxSSSBiZWluZyBhZHZlcnRpc2VkIGFzIG9wcG9zZWQgdG8gYWxsIHRoZSBpbXBh Y3RlZCBwcmVmaXhlcyBoYXZpbmcgdG8gcHJvcGFnYXRlIGhvcC1ieS1ob3AuIFRoaXMgc2hvdWxk IGltcHJvdmUgY29udmVyZ2VuY2UgYW5kIGV2ZW4gc2NhbGluZy4mbmJzcDs8L2Rpdj4NCjxkaXY+ PGJyPg0KPC9kaXY+DQo8ZGl2PlRoYW5rcyw8L2Rpdj4NCjxkaXY+QWNlZSZuYnNwOzwvZGl2Pg0K PGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8c3BhbiBpZD0iT0xLX1NSQ19C T0RZX1NFQ1RJT04iPg0KPGJsb2NrcXVvdGUgaWQ9Ik1BQ19PVVRMT09LX0FUVFJJQlVUSU9OX0JM T0NLUVVPVEUiIHN0eWxlPSJCT1JERVItTEVGVDogI2I1YzRkZiA1IHNvbGlkOyBQQURESU5HOjAg MCAwIDU7IE1BUkdJTjowIDAgMCA1OyI+DQo8ZGl2Pg0KPGRpdj4NCjxkaXYgZGlyPSJsdHIiPg0K PGRpdiBjbGFzcz0iZ21haWxfZGVmYXVsdCIgc3R5bGU9ImZvbnQtZmFtaWx5OmFyaWFsLGhlbHZl dGljYSxzYW5zLXNlcmlmO2ZvbnQtc2l6ZTpzbWFsbCI+DQo8YnI+DQo8L2Rpdj4NCjxkaXYgY2xh c3M9ImdtYWlsX2RlZmF1bHQiIHN0eWxlPSJmb250LWZhbWlseTphcmlhbCxoZWx2ZXRpY2Esc2Fu cy1zZXJpZjtmb250LXNpemU6c21hbGwiPg0KQmVzdCByZWdhcmRzLDxicj4NClIuPC9kaXY+DQo8 ZGl2IGNsYXNzPSJnbWFpbF9kZWZhdWx0IiBzdHlsZT0iZm9udC1mYW1pbHk6YXJpYWwsaGVsdmV0 aWNhLHNhbnMtc2VyaWY7Zm9udC1zaXplOnNtYWxsIj4NCjxicj4NCjwvZGl2Pg0KPC9kaXY+DQo8 ZGl2IGNsYXNzPSJnbWFpbF9leHRyYSI+PGJyPg0KPGRpdiBjbGFzcz0iZ21haWxfcXVvdGUiPk9u IEZyaSwgSnVsIDgsIDIwMTYgYXQgNjoyMiBQTSwgQWNlZSBMaW5kZW0gKGFjZWUpIDxzcGFuIGRp cj0ibHRyIj4NCiZsdDs8YSBocmVmPSJtYWlsdG86YWNlZUBjaXNjby5jb20iIHRhcmdldD0iX2Js YW5rIj5hY2VlQGNpc2NvLmNvbTwvYT4mZ3Q7PC9zcGFuPiB3cm90ZTo8YnI+DQo8YmxvY2txdW90 ZSBjbGFzcz0iZ21haWxfcXVvdGUiIHN0eWxlPSJtYXJnaW46MCAwIDAgLjhleDtib3JkZXItbGVm dDoxcHggI2NjYyBzb2xpZDtwYWRkaW5nLWxlZnQ6MWV4Ij4NCjxkaXYgc3R5bGU9IndvcmQtd3Jh cDpicmVhay13b3JkIj4NCjxkaXYgc3R5bGU9ImNvbG9yOnJnYigwLDAsMCk7Zm9udC1mYW1pbHk6 Q2FsaWJyaSxzYW5zLXNlcmlmO2ZvbnQtc2l6ZToxNHB4Ij5IaSBSb2JlcnQsJm5ic3A7PC9kaXY+ DQo8ZGl2IHN0eWxlPSJjb2xvcjpyZ2IoMCwwLDApO2ZvbnQtZmFtaWx5OkNhbGlicmksc2Fucy1z ZXJpZjtmb250LXNpemU6MTRweCI+PGJyPg0KPC9kaXY+DQo8ZGl2IHN0eWxlPSJjb2xvcjpyZ2Io MCwwLDApO2ZvbnQtZmFtaWx5OkNhbGlicmksc2Fucy1zZXJpZjtmb250LXNpemU6MTRweCI+VGhh bmtzIGZvciBlbmdhZ2luZ+KApjwvZGl2Pg0KPGRpdiBzdHlsZT0iY29sb3I6cmdiKDAsMCwwKTtm b250LWZhbWlseTpDYWxpYnJpLHNhbnMtc2VyaWY7Zm9udC1zaXplOjE0cHgiPjxicj4NCjwvZGl2 Pg0KPHNwYW4gc3R5bGU9ImNvbG9yOnJnYigwLDAsMCk7Zm9udC1mYW1pbHk6Q2FsaWJyaSxzYW5z LXNlcmlmO2ZvbnQtc2l6ZToxNHB4Ij4NCjxkaXYgc3R5bGU9ImZvbnQtZmFtaWx5OkNhbGlicmk7 Zm9udC1zaXplOjExcHQ7dGV4dC1hbGlnbjpsZWZ0O2NvbG9yOmJsYWNrO0JPUkRFUi1CT1RUT006 bWVkaXVtIG5vbmU7Qk9SREVSLUxFRlQ6bWVkaXVtIG5vbmU7UEFERElORy1CT1RUT006MGluO1BB RERJTkctTEVGVDowaW47UEFERElORy1SSUdIVDowaW47Qk9SREVSLVRPUDojYjVjNGRmIDFwdCBz b2xpZDtCT1JERVItUklHSFQ6bWVkaXVtIG5vbmU7UEFERElORy1UT1A6M3B0Ij4NCjxzcGFuIHN0 eWxlPSJmb250LXdlaWdodDpib2xkIj5Gcm9tOiA8L3NwYW4+Jmx0OzxhIGhyZWY9Im1haWx0bzpy cmFzenVrQGdtYWlsLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPnJyYXN6dWtAZ21haWwuY29tPC9hPiZn dDsgb24gYmVoYWxmIG9mIFJvYmVydCBSYXN6dWsgJmx0OzxhIGhyZWY9Im1haWx0bzpyb2JlcnRA cmFzenVrLm5ldCIgdGFyZ2V0PSJfYmxhbmsiPnJvYmVydEByYXN6dWsubmV0PC9hPiZndDs8YnI+ DQo8c3BhbiBzdHlsZT0iZm9udC13ZWlnaHQ6Ym9sZCI+RGF0ZTogPC9zcGFuPkZyaWRheSwgSnVs eSA4LCAyMDE2IGF0IDExOjUxIEFNPGJyPg0KPHNwYW4gc3R5bGU9ImZvbnQtd2VpZ2h0OmJvbGQi PlRvOiA8L3NwYW4+JnF1b3Q7S2V5dXIgUGF0ZWwgKGtleXVwYXRlKSZxdW90OyAmbHQ7PGEgaHJl Zj0ibWFpbHRvOmtleXVwYXRlQGNpc2NvLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPmtleXVwYXRlQGNp c2NvLmNvbTwvYT4mZ3Q7LCBBY2VlIExpbmRlbSAmbHQ7PGEgaHJlZj0ibWFpbHRvOmFjZWVAY2lz Y28uY29tIiB0YXJnZXQ9Il9ibGFuayI+YWNlZUBjaXNjby5jb208L2E+Jmd0OywgJnF1b3Q7QWJo YXkgUm95IChha3IpJnF1b3Q7ICZsdDs8YSBocmVmPSJtYWlsdG86YWtyQGNpc2NvLmNvbSIgdGFy Z2V0PSJfYmxhbmsiPmFrckBjaXNjby5jb208L2E+Jmd0OywNCiAmcXVvdDtEZXJlayBNYW4tS2l0 IFlldW5nIChteWV1bmcpJnF1b3Q7ICZsdDs8YSBocmVmPSJtYWlsdG86bXlldW5nQGNpc2NvLmNv bSIgdGFyZ2V0PSJfYmxhbmsiPm15ZXVuZ0BjaXNjby5jb208L2E+Jmd0OywgJnF1b3Q7VmVudSBW ZW51Z29wYWwgKHZlbnV2KSZxdW90OyAmbHQ7PGEgaHJlZj0ibWFpbHRvOnZlbnV2QGNpc2NvLmNv bSIgdGFyZ2V0PSJfYmxhbmsiPnZlbnV2QGNpc2NvLmNvbTwvYT4mZ3Q7PGJyPg0KPHNwYW4gc3R5 bGU9ImZvbnQtd2VpZ2h0OmJvbGQiPkNjOiA8L3NwYW4+SURSIExpc3QgJmx0OzxhIGhyZWY9Im1h aWx0bzppZHJAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5pZHJAaWV0Zi5vcmc8L2E+Jmd0Ozxi cj4NCjxzcGFuIHN0eWxlPSJmb250LXdlaWdodDpib2xkIj5TdWJqZWN0OiA8L3NwYW4+U2hvcnRl c3QgUGF0aCBSb3V0aW5nIEV4dGVuc2lvbnMgZm9yIEJHUCBQcm90b2NvbDxicj4NCjwvZGl2Pg0K PHNwYW4gY2xhc3M9IiI+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9IkJP UkRFUi1MRUZUOiNiNWM0ZGYgNSBzb2xpZDtQQURESU5HOjAgMCAwIDU7TUFSR0lOOjAgMCAwIDUi Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2IGRpcj0ibHRyIj4NCjxkaXYgY2xhc3M9ImdtYWlsX2RlZmF1 bHQiIHN0eWxlPSJmb250LWZhbWlseTphcmlhbCxoZWx2ZXRpY2Esc2Fucy1zZXJpZjtmb250LXNp emU6c21hbGwiPg0KSGksPC9kaXY+DQo8ZGl2IGNsYXNzPSJnbWFpbF9kZWZhdWx0IiBzdHlsZT0i Zm9udC1mYW1pbHk6YXJpYWwsaGVsdmV0aWNhLHNhbnMtc2VyaWY7Zm9udC1zaXplOnNtYWxsIj4N Cjxicj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iZ21haWxfZGVmYXVsdCIgc3R5bGU9ImZvbnQtZmFt aWx5OmFyaWFsLGhlbHZldGljYSxzYW5zLXNlcmlmO2ZvbnQtc2l6ZTpzbWFsbCI+DQpJIGhhdmUg cmV2aWV3ZWQgeW91ciBwcm9wb3NhbC4mbmJzcDs8L2Rpdj4NCjxkaXYgY2xhc3M9ImdtYWlsX2Rl ZmF1bHQiIHN0eWxlPSJmb250LWZhbWlseTphcmlhbCxoZWx2ZXRpY2Esc2Fucy1zZXJpZjtmb250 LXNpemU6c21hbGwiPg0KPGJyPg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSJnbWFpbF9kZWZhdWx0IiBz dHlsZT0iZm9udC1mYW1pbHk6YXJpYWwsaGVsdmV0aWNhLHNhbnMtc2VyaWY7Zm9udC1zaXplOnNt YWxsIj4NClR1cm5pbmcgcGF0aCB2ZWN0b3Igb3IgZGlzdGFuY2UgdmVjdG9yIHByb3RvY29sIGlu dG8gbGluayBzdGF0ZSBjYXJyaWVyIGlzIG5vIGRvdWJ0IGEgYm9sZCBpZGVhIDopLjwvZGl2Pg0K PC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9zcGFuPjwvc3Bhbj4NCjxk aXYgc3R5bGU9ImNvbG9yOnJnYigwLDAsMCk7Zm9udC1mYW1pbHk6Q2FsaWJyaSxzYW5zLXNlcmlm O2ZvbnQtc2l6ZToxNHB4Ij48YnI+DQo8L2Rpdj4NCjxkaXY+PGZvbnQgZmFjZT0iQ2FsaWJyaSxz YW5zLXNlcmlmIj7igJxGb3J0dW5lIGJlZnJpZW5kcyB0aGUgYm9sZC7igJ0gLUVtaWx5IERpY2tp bnNvbjwvZm9udD48L2Rpdj4NCjxzcGFuIGNsYXNzPSIiPg0KPGRpdiBzdHlsZT0iY29sb3I6cmdi KDAsMCwwKTtmb250LWZhbWlseTpDYWxpYnJpLHNhbnMtc2VyaWY7Zm9udC1zaXplOjE0cHgiPjxi cj4NCjwvZGl2Pg0KPHNwYW4gc3R5bGU9ImNvbG9yOnJnYigwLDAsMCk7Zm9udC1mYW1pbHk6Q2Fs aWJyaSxzYW5zLXNlcmlmO2ZvbnQtc2l6ZToxNHB4Ij4NCjxibG9ja3F1b3RlIHN0eWxlPSJCT1JE RVItTEVGVDojYjVjNGRmIDUgc29saWQ7UEFERElORzowIDAgMCA1O01BUkdJTjowIDAgMCA1Ij4N CjxkaXY+DQo8ZGl2Pg0KPGRpdiBkaXI9Imx0ciI+DQo8ZGl2IGNsYXNzPSJnbWFpbF9kZWZhdWx0 IiBzdHlsZT0iZm9udC1mYW1pbHk6YXJpYWwsaGVsdmV0aWNhLHNhbnMtc2VyaWY7Zm9udC1zaXpl OnNtYWxsIj4NCjxicj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iZ21haWxfZGVmYXVsdCIgc3R5bGU9 ImZvbnQtZmFtaWx5OmFyaWFsLGhlbHZldGljYSxzYW5zLXNlcmlmO2ZvbnQtc2l6ZTpzbWFsbCI+ DQpFZmZlY3RpdmVseSB3aGF0IHlvdSBhcmUgcHJvcG9zaW5nIGlzIHRvIHVzZSBCR1AgVENQIHNl c3Npb25zIHRvIHByb3BhZ2F0ZSBsaW5rIHN0YXRlIGRhdGFiYXNlIGNyZWF0aW5nIGZpcnN0ICZx dW90O2xpbmsgdmVjdG9yIHByb3RvY29sJnF1b3Q7ICE8L2Rpdj4NCjxkaXYgY2xhc3M9ImdtYWls X2RlZmF1bHQiIHN0eWxlPSJmb250LWZhbWlseTphcmlhbCxoZWx2ZXRpY2Esc2Fucy1zZXJpZjtm b250LXNpemU6c21hbGwiPg0KPGJyPg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSJnbWFpbF9kZWZhdWx0 IiBzdHlsZT0iZm9udC1mYW1pbHk6YXJpYWwsaGVsdmV0aWNhLHNhbnMtc2VyaWY7Zm9udC1zaXpl OnNtYWxsIj4NCkZvciBzdGFydCBJIGhhdmUgZmV3IHF1ZXN0aW9uczo8L2Rpdj4NCjxkaXYgY2xh c3M9ImdtYWlsX2RlZmF1bHQiIHN0eWxlPSJmb250LWZhbWlseTphcmlhbCxoZWx2ZXRpY2Esc2Fu cy1zZXJpZjtmb250LXNpemU6c21hbGwiPg0KPGJyPg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSJnbWFp bF9kZWZhdWx0IiBzdHlsZT0iZm9udC1mYW1pbHk6YXJpYWwsaGVsdmV0aWNhLHNhbnMtc2VyaWY7 Zm9udC1zaXplOnNtYWxsIj4NClExOiZuYnNwOzwvZGl2Pg0KPGRpdiBjbGFzcz0iZ21haWxfZGVm YXVsdCIgc3R5bGU9ImZvbnQtZmFtaWx5OmFyaWFsLGhlbHZldGljYSxzYW5zLXNlcmlmO2ZvbnQt c2l6ZTpzbWFsbCI+DQo8YnI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9ImdtYWlsX2RlZmF1bHQiIHN0 eWxlPSJmb250LWZhbWlseTphcmlhbCxoZWx2ZXRpY2Esc2Fucy1zZXJpZjtmb250LXNpemU6c21h bGwiPg0KUkZDNzc1MiBoYXMgZ29uZSB2aWEgbG90IG9mIGVmZm9ydHMgKGVzcGVjaWFsbHkgc2Vj dGlvbnMgMy4yIGFuZCB1cCkgdG8gaW5jbHVkZSBudW1iZXIgb2YgT1NQRiBvciBJU0lTIHNwZWNp ZmljIGVuY29kaW5ncy4gSW4geW91ciBwcm9wb3NhbCB5b3UgbWVudGlvbmVkIE9TUEYgdHdpY2Ug YW5kIG5vdCBldmVuIG9uY2UgSVNJUy4gRG9lcyBpdCBtZWFuIHRoYXQgeW91IGFyZSBub3QgZ29p bmcgdG8gdXNlIGFsbCBlbmNvZGluZyBmb3Igc3BlY2lmaWMNCiBJR1BzIGFzIGRlZmluZWQgaW4g UkZDNzc1MiA/Jm5ic3A7PC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVv dGU+DQo8L3NwYW4+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPC9zcGFuPg0KPGRpdj5XZSBhcmUgdXNp bmcgdGhlIEJHUCBQcm90b2NvbC1JRCBkZWZpbmVkIGZvciBCR1AtRVBFLiBUaGUgSUFOQSByZXF1 ZXN0IHdpbGwgYmUgZ2VuZXJhbGl6ZWQgZnJvbSDigJxCR1AtRVBF4oCdIHRvIOKAnEJHUOKAnSBp biBzdXBwb3J0IG9mIFNlZ21lbnQgUm91dGluZyBhbmQgb3RoZXIgZW5oYW5jZW1lbnRzLiBUaGUg QkdQLUxTIE5MUkkgYXJlIHNwZWNpZmljIEJHUCBhbmQgbm90IGVpdGhlciBJUy1JUyBvciBPU1BG LiZuYnNwOzwvZGl2Pg0KPHNwYW4gY2xhc3M9IiI+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPHNwYW4g c3R5bGU9ImNvbG9yOnJnYigwLDAsMCk7Zm9udC1mYW1pbHk6Q2FsaWJyaSxzYW5zLXNlcmlmO2Zv bnQtc2l6ZToxNHB4Ij4NCjxibG9ja3F1b3RlIHN0eWxlPSJCT1JERVItTEVGVDojYjVjNGRmIDUg c29saWQ7UEFERElORzowIDAgMCA1O01BUkdJTjowIDAgMCA1Ij4NCjxkaXY+DQo8ZGl2Pg0KPGRp diBkaXI9Imx0ciI+DQo8ZGl2IGNsYXNzPSJnbWFpbF9kZWZhdWx0IiBzdHlsZT0iZm9udC1mYW1p bHk6YXJpYWwsaGVsdmV0aWNhLHNhbnMtc2VyaWY7Zm9udC1zaXplOnNtYWxsIj4NCjxicj4NCjwv ZGl2Pg0KPGRpdiBjbGFzcz0iZ21haWxfZGVmYXVsdCIgc3R5bGU9ImZvbnQtZmFtaWx5OmFyaWFs LGhlbHZldGljYSxzYW5zLXNlcmlmO2ZvbnQtc2l6ZTpzbWFsbCI+DQpRMjombmJzcDs8L2Rpdj4N CjxkaXYgY2xhc3M9ImdtYWlsX2RlZmF1bHQiIHN0eWxlPSJmb250LWZhbWlseTphcmlhbCxoZWx2 ZXRpY2Esc2Fucy1zZXJpZjtmb250LXNpemU6c21hbGwiPg0KPGJyPg0KPC9kaXY+DQo8ZGl2IGNs YXNzPSJnbWFpbF9kZWZhdWx0IiBzdHlsZT0iZm9udC1mYW1pbHk6YXJpYWwsaGVsdmV0aWNhLHNh bnMtc2VyaWY7Zm9udC1zaXplOnNtYWxsIj4NCldobyBjcmVhdGVzIGFuZCBtYWludGFpbnMgTFNE QiBpbiBlYWNoIEJHUCBzcGVha2VyID8gQXJlIHlvdSBwbGFubmluZyB0byBydW4gT1NQRiBhbmQg b3IgSVNJUyBleGNlcHQgZGlzYWJsZSBpdCB0byBlc3RhYmxpc2ggYW55IGFkamFjaWVuY2llcyA/ Jm5ic3A7PC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L3Nw YW4+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPC9zcGFuPg0KPGRpdj5J4oCZdmUgc2VlbiBkZXNpZ25z IGxpa2UgdGhpcyBpbiBteSB0aW1lIGJ1dCBoYXZlIG5ldmVyIGJlZW4gb2YgYSBmYW4gb2YgdGhl bSA7XikuIEJHUCB3aWxsIGRvIHRoZSBTUEYgZGlyZWN0bHkgYW5kIG1haW50YWluIHRoZSBTUFQu IFlvdeKAmWxsIG5vdGUgdGhhdCBhIHNpbXBsaWZpZWQgU1BGIGlzIGFscmVhZHkgZG9uZSBmb3Ig T1JSLiZuYnNwOzwvZGl2Pg0KPHNwYW4gY2xhc3M9IiI+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPHNw YW4gc3R5bGU9ImNvbG9yOnJnYigwLDAsMCk7Zm9udC1mYW1pbHk6Q2FsaWJyaSxzYW5zLXNlcmlm O2ZvbnQtc2l6ZToxNHB4Ij4NCjxibG9ja3F1b3RlIHN0eWxlPSJCT1JERVItTEVGVDojYjVjNGRm IDUgc29saWQ7UEFERElORzowIDAgMCA1O01BUkdJTjowIDAgMCA1Ij4NCjxkaXY+DQo8ZGl2Pg0K PGRpdiBkaXI9Imx0ciI+DQo8ZGl2IGNsYXNzPSJnbWFpbF9kZWZhdWx0IiBzdHlsZT0iZm9udC1m YW1pbHk6YXJpYWwsaGVsdmV0aWNhLHNhbnMtc2VyaWY7Zm9udC1zaXplOnNtYWxsIj4NCjxicj4N CjwvZGl2Pg0KPGRpdiBjbGFzcz0iZ21haWxfZGVmYXVsdCIgc3R5bGU9ImZvbnQtZmFtaWx5OmFy aWFsLGhlbHZldGljYSxzYW5zLXNlcmlmO2ZvbnQtc2l6ZTpzbWFsbCI+DQpRMzombmJzcDs8L2Rp dj4NCjxkaXYgY2xhc3M9ImdtYWlsX2RlZmF1bHQiIHN0eWxlPSJmb250LWZhbWlseTphcmlhbCxo ZWx2ZXRpY2Esc2Fucy1zZXJpZjtmb250LXNpemU6c21hbGwiPg0KPGJyPg0KPC9kaXY+DQo8ZGl2 IGNsYXNzPSJnbWFpbF9kZWZhdWx0IiBzdHlsZT0iZm9udC1mYW1pbHk6YXJpYWwsaGVsdmV0aWNh LHNhbnMtc2VyaWY7Zm9udC1zaXplOnNtYWxsIj4NCkN1cnJlbnRseSB0aGVyZSBhcmUgYWxyZWFk eSB0byBtb2RlbHMgdG8gYnVpbGQgRENzIHdpdGggQkdQIC4uLiBvbmUgdXNlcyBCR1AgdG8gY3Jl YXRlIG9ubHkgbGVhbiB1bmRlcmxheSB0aGUgb3RoZXIgaXMgdG8gdXNlIEJHUCBmb3IgYm90aCB1 bmRlcmxheSBhbmQgdGVuYW50cyAoZXhhbXBsZSBwcm9qZWN0IENhbGljbyBmb3IgdGhlIGxhdHRl cikuIFdpdGggdGhhdCBzY2FsZSB3aXNlIEkgdGhpbmsgeW91ciBwcm9wb3NhbCB3aWxsIHdvcmsg Z3JlYXQNCiBmb3IgdGhlIGZvcm1lci4gSG93ZXZlciBJIGRvIGhhdmUgY29uY2VybnMgYWJvdXQg dXNpbmcgeW91ciBtb2RlbCBmb3IgdGhlIGxhdHRlciB3aGVyZSBzYXkgMTAsMDAwIG9yIDEwMCww MDAgLzMycyBvciAvMTI4cyBmcm9tIGVhY2ggVk1zIGFyZSBpbmplY3RlZCBhbmQgeW91IG5lZWQg dG8gY29uc3RydWN0IFNQVCB3aXRoIGFsbCBvZiB0aG9zZS4mbmJzcDs8L2Rpdj4NCjwvZGl2Pg0K PC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvc3Bhbj4NCjxkaXY+PGJyPg0KPC9kaXY+ DQo8L3NwYW4+DQo8ZGl2PlNpbWlsYXIgdG8gdGhvc2UgZGVzaWducywgdGhlIFNQVCBjb3VsZCBi ZSBsaW1pdGVkIHRvIHRoZSB1bmRlcmxheS4gSG93ZXZlciwgaWYgdGhlcmUgaXMgbm8gcmVxdWly ZW1lbnQgZm9yIHRoZSBiZW5lZml0cyBvZiBMMiBvciBMMyBWUE5zLCBJIHNlZSBubyByZWFzb24g d2h5IHRoZXNlIDEwMEtzIG9mIGxlYWZzIFZNIHByZWZpeGVzIGluIERDIGNlbnRlciBjb3VsZG7i gJl0IGJlIHN1cHBvcnRlZC4mbmJzcDs8L2Rpdj4NCjxzcGFuIGNsYXNzPSIiPg0KPGRpdj48YnI+ DQo8L2Rpdj4NCjxzcGFuIHN0eWxlPSJjb2xvcjpyZ2IoMCwwLDApO2ZvbnQtZmFtaWx5OkNhbGli cmksc2Fucy1zZXJpZjtmb250LXNpemU6MTRweCI+DQo8YmxvY2txdW90ZSBzdHlsZT0iQk9SREVS LUxFRlQ6I2I1YzRkZiA1IHNvbGlkO1BBRERJTkc6MCAwIDAgNTtNQVJHSU46MCAwIDAgNSI+DQo8 ZGl2Pg0KPGRpdj4NCjxkaXYgZGlyPSJsdHIiPg0KPGRpdiBjbGFzcz0iZ21haWxfZGVmYXVsdCIg c3R5bGU9ImZvbnQtZmFtaWx5OmFyaWFsLGhlbHZldGljYSxzYW5zLXNlcmlmO2ZvbnQtc2l6ZTpz bWFsbCI+DQo8YnI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9ImdtYWlsX2RlZmF1bHQiIHN0eWxlPSJm b250LWZhbWlseTphcmlhbCxoZWx2ZXRpY2Esc2Fucy1zZXJpZjtmb250LXNpemU6c21hbGwiPg0K UTQ6Jm5ic3A7PGJyPg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSJnbWFpbF9kZWZhdWx0IiBzdHlsZT0i Zm9udC1mYW1pbHk6YXJpYWwsaGVsdmV0aWNhLHNhbnMtc2VyaWY7Zm9udC1zaXplOnNtYWxsIj4N Cjxicj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iZ21haWxfZGVmYXVsdCIgc3R5bGU9ImZvbnQtZmFt aWx5OmFyaWFsLGhlbHZldGljYSxzYW5zLXNlcmlmO2ZvbnQtc2l6ZTpzbWFsbCI+DQpSZWxhdGVk IHRvIFEzIGluIHlvdXIgbW9kZWwgYW5kIHNheSBmbGF0IERDIHJvdXRpbmcgZWFjaCBjb21wdXRl IG5vZGUgb3RoZXIgdGhlbiBqdXN0IGluamVjdGluZyAxMHMgb2YgLzMycyBhbmQgYmVpbmcgJnF1 b3Q7ZG9uZSZxdW90OyBub3cgYmVjb21lcyBhbiBJR1Agbm9kZS4gU2luY2UgeW91ciBkb2N1bWVu dCBleHBsaWNpdGVseSB0YXJnZXRzJm5ic3A7TWFzc2l2ZWx5IFNjYWxlZCBEYXRhIENlbnRlcnMg KE1TRENzKSBJIGFtIGNvbmNlcm5lZCB0aGF0IGhhdmluZyAxMDAsMDAwJiM0MzsNCiBJR1Agbm9k ZXMgYW5kIGluIG1hbnkgY2FzZSBtdWNoIG1vcmUgaXMgbm90IHRoZSBiZXN0IGlkZWEuJm5ic3A7 PC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L3NwYW4+DQo8 ZGl2Pjxicj4NCjwvZGl2Pg0KPC9zcGFuPg0KPGRpdj4xMDBLJiM0Mzsgc3dpdGNoZXMgaW4gYSBz aW5nbGUgREMgZmFicmljIChpLmUuLCBCR1Agcm91dGluZyBkb21haW4pPyBJIGhhdmUgc29tZSBl eHBlcmllbmNlIGluIGxpbmstc3RhdGUgcHJvdG9jb2xzIGFuZCBJIGNhbiB0ZWxsIHlvdSB0aGF0 IE9TUEYgaXMgSS9PIGJvdW5kIG1haW5seSBkdWUgdG8gdGhlIGZsb29kaW5nLiBJZiBkb25lIHJp Z2h0LCB0aGUgU1BGIGNhbGN1bGF0aW9uIGNhbiBiZSBkb25lIHdpdGggbWluaW1hbCBjb21wdXRh dGlvbi4NCiBXaGlsZSBCR1AtTFMgaXNu4oCZdCB0aGUgd29ybGQncyBtb3N0IGNvbXBhY3QgZW5j b2RpbmcsIGl0IGlzIGNvbXBsZXRlbHkgaW5jcmVtZW50YWwuJm5ic3A7PC9kaXY+DQo8c3BhbiBj bGFzcz0iIj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8c3BhbiBzdHlsZT0iY29sb3I6cmdiKDAsMCww KTtmb250LWZhbWlseTpDYWxpYnJpLHNhbnMtc2VyaWY7Zm9udC1zaXplOjE0cHgiPg0KPGJsb2Nr cXVvdGUgc3R5bGU9IkJPUkRFUi1MRUZUOiNiNWM0ZGYgNSBzb2xpZDtQQURESU5HOjAgMCAwIDU7 TUFSR0lOOjAgMCAwIDUiPg0KPGRpdj4NCjxkaXY+DQo8ZGl2IGRpcj0ibHRyIj4NCjxkaXYgY2xh c3M9ImdtYWlsX2RlZmF1bHQiIHN0eWxlPSJmb250LWZhbWlseTphcmlhbCxoZWx2ZXRpY2Esc2Fu cy1zZXJpZjtmb250LXNpemU6c21hbGwiPg0KPGJyPg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSJnbWFp bF9kZWZhdWx0IiBzdHlsZT0iZm9udC1mYW1pbHk6YXJpYWwsaGVsdmV0aWNhLHNhbnMtc2VyaWY7 Zm9udC1zaXplOnNtYWxsIj4NClE1OiZuYnNwOzwvZGl2Pg0KPGRpdiBjbGFzcz0iZ21haWxfZGVm YXVsdCIgc3R5bGU9ImZvbnQtZmFtaWx5OmFyaWFsLGhlbHZldGljYSxzYW5zLXNlcmlmO2ZvbnQt c2l6ZTpzbWFsbCI+DQo8YnI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9ImdtYWlsX2RlZmF1bHQiIHN0 eWxlPSJmb250LWZhbWlseTphcmlhbCxoZWx2ZXRpY2Esc2Fucy1zZXJpZjtmb250LXNpemU6c21h bGwiPg0KSGF2ZSB5b3UgY29uc2lkZXJlZCBqdXN0IHByb3Bvc2luZyBhbiBPU1BGIHJvdXRlIHJl ZmxlY3RvciBpbnN0ZWFkIHdpdGhvdXQgc3R1ZmZpbmcgQkdQIGludG8gdGhlIG1peCA/IEFzIHNv bWUgb2YgeW91IHBlcmhhcHMgcmVtZW1iZXIgdGhlIHdvcmsgb24gdGhpcyBzdGFydGVkIGFyb3Vu ZCB5ZWFyIDIwMDAgdG8gb3B0aW1pemUgUEUtQ0UgQ1NDIGRlcGxveW1lbnRzIDopIEl0IHNlZW1z IHRvIG1lIHZlcnkgcmV1c2FibGUgZm9yIHRoaXMgZ29hbC48L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+ DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvc3Bhbj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8L3Nw YW4+DQo8ZGl2PldlIGxvb2tlZCBhdCBsb3RzIG9mIGFsdGVybmF0aXZlcyBhbmQgdGhpcyBvbmUg c2VlbWVkIGxpa2UgdGhlIGJlc3Qgb25lLiBQbGVhc2UgcGFzcyBtZSBhIHBvaW50ZXIgdG8gdGhl IHdvcmsgeW91IG1lbnRpb24uJm5ic3A7PC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5U aGFua3MsPC9kaXY+DQo8ZGl2PkFjZWUmbmJzcDs8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8 ZGl2Pjxicj4NCjwvZGl2Pg0KPHNwYW4gc3R5bGU9ImNvbG9yOnJnYigwLDAsMCk7Zm9udC1mYW1p bHk6Q2FsaWJyaSxzYW5zLXNlcmlmO2ZvbnQtc2l6ZToxNHB4Ij4NCjxibG9ja3F1b3RlIHN0eWxl PSJCT1JERVItTEVGVDojYjVjNGRmIDUgc29saWQ7UEFERElORzowIDAgMCA1O01BUkdJTjowIDAg MCA1Ij4NCjxkaXY+DQo8ZGl2Pg0KPGRpdiBkaXI9Imx0ciI+DQo8ZGl2IGNsYXNzPSJnbWFpbF9k ZWZhdWx0IiBzdHlsZT0iZm9udC1mYW1pbHk6YXJpYWwsaGVsdmV0aWNhLHNhbnMtc2VyaWY7Zm9u dC1zaXplOnNtYWxsIj4NCjxicj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iZ21haWxfZGVmYXVsdCIg c3R5bGU9ImZvbnQtZmFtaWx5OmFyaWFsLGhlbHZldGljYSxzYW5zLXNlcmlmO2ZvbnQtc2l6ZTpz bWFsbCI+DQpCZXN0IHJlZ2FyZHMsPC9kaXY+DQo8ZGl2IGNsYXNzPSJnbWFpbF9kZWZhdWx0IiBz dHlsZT0iZm9udC1mYW1pbHk6YXJpYWwsaGVsdmV0aWNhLHNhbnMtc2VyaWY7Zm9udC1zaXplOnNt YWxsIj4NClJvYmVydC48L2Rpdj4NCjxkaXYgY2xhc3M9ImdtYWlsX2RlZmF1bHQiIHN0eWxlPSJm b250LWZhbWlseTphcmlhbCxoZWx2ZXRpY2Esc2Fucy1zZXJpZjtmb250LXNpemU6c21hbGwiPg0K PGJyPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L3Nw YW4+PC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjxicj4NCjwvZGl2Pg0KPC9kaXY+DQo8 L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvc3Bhbj4NCjwvYm9keT4NCjwvaHRtbD4NCg== --_000_D3A980476A7C5aceeciscocom_-- From nobody Mon Jul 11 16:14:05 2016 Return-Path: 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 A714812D0AE; Mon, 11 Jul 2016 16:13:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.889 X-Spam-Level: X-Spam-Status: No, score=-103.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.287, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 wDHsixVGOcoD; Mon, 11 Jul 2016 16:13:58 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 03B5512B02A; Mon, 11 Jul 2016 16:13:58 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id E7E21B80A21; Mon, 11 Jul 2016 16:13:57 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20160711231357.E7E21B80A21@rfc-editor.org> Date: Mon, 11 Jul 2016 16:13:57 -0700 (PDT) Archived-At: Cc: drafts-update-ref@iana.org, idr@ietf.org, rfc-editor@rfc-editor.org Subject: [Idr] RFC 7911 on Advertisement of Multiple Paths in BGP X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jul 2016 23:14:00 -0000 A new Request for Comments is now available in online RFC libraries. RFC 7911 Title: Advertisement of Multiple Paths in BGP Author: D. Walton, A. Retana, E. Chen, J. Scudder Status: Standards Track Stream: IETF Date: July 2016 Mailbox: dwalton@cumulusnetworks.com, aretana@cisco.com, enkechen@cisco.com, jgs@juniper.net Pages: 8 Characters: 17537 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-idr-add-paths-15.txt URL: https://www.rfc-editor.org/info/rfc7911 DOI: http://dx.doi.org/10.17487/RFC7911 This document defines a BGP extension that allows the advertisement of multiple paths for the same address prefix without the new paths implicitly replacing any previous ones. The essence of the extension is that each path is identified by a Path Identifier in addition to the address prefix. This document is a product of the Inter-Domain Routing Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC From nobody Thu Jul 14 05:45:45 2016 Return-Path: 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 3D98B12D7CB; Thu, 14 Jul 2016 05:45:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.889 X-Spam-Level: X-Spam-Status: No, score=-103.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.287, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 6as3DLUC7W33; Thu, 14 Jul 2016 05:45:35 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B506412B040; Thu, 14 Jul 2016 05:45:35 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id A6A38B80676; Thu, 14 Jul 2016 05:45:35 -0700 (PDT) To: bruno.decraene@orange.com, yakov@juniper.net, tony.li@tony.li, skh@nexthop.com X-PHP-Originating-Script: 30:errata_mail_lib.php From: RFC Errata System Message-Id: <20160714124535.A6A38B80676@rfc-editor.org> Date: Thu, 14 Jul 2016 05:45:35 -0700 (PDT) Archived-At: Cc: rfc-editor@rfc-editor.org, iesg@ietf.org, idr@ietf.org Subject: [Idr] [Errata Verified] RFC4271 (4493) X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jul 2016 12:45:37 -0000 The following errata report has been verified for RFC4271, "A Border Gateway Protocol 4 (BGP-4)". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=4271&eid=4493 -------------------------------------- Status: Verified Type: Technical Reported by: Bruno Decraene Date Reported: 2015-10-06 Verified by: Alvaro Retana (IESG) Section: 4.5 Original Text ------------- Message Header Error subcodes: 1 - Connection Not Synchronized. 2 - Bad Message Length. 3 - Bad Message Type. OPEN Message Error subcodes: 1 - Unsupported Version Number. 2 - Bad Peer AS. 3 - Bad BGP Identifier. 4 - Unsupported Optional Parameter. 5 - [Deprecated - see Appendix A]. 6 - Unacceptable Hold Time. UPDATE Message Error subcodes: 1 - Malformed Attribute List. 2 - Unrecognized Well-known Attribute. 3 - Missing Well-known Attribute. 4 - Attribute Flags Error. 5 - Attribute Length Error. 6 - Invalid ORIGIN Attribute. 7 - [Deprecated - see Appendix A]. 8 - Invalid NEXT_HOP Attribute. 9 - Optional Attribute Error. 10 - Invalid Network Field. 11 - Malformed AS_PATH. Corrected Text -------------- Message Header Error subcodes: 0 - Unspecific. 1 - Connection Not Synchronized. 2 - Bad Message Length. 3 - Bad Message Type. OPEN Message Error subcodes: 0 - Unspecific. 1 - Unsupported Version Number. 2 - Bad Peer AS. 3 - Bad BGP Identifier. 4 - Unsupported Optional Parameter. 5 - [Deprecated - see Appendix A]. 6 - Unacceptable Hold Time. UPDATE Message Error subcodes: 0 - Unspecific. 1 - Malformed Attribute List. 2 - Unrecognized Well-known Attribute. 3 - Missing Well-known Attribute. 4 - Attribute Flags Error. 5 - Attribute Length Error. 6 - Invalid ORIGIN Attribute. 7 - [Deprecated - see Appendix A]. 8 - Invalid NEXT_HOP Attribute. 9 - Optional Attribute Error. 10 - Invalid Network Field. 11 - Malformed AS_PATH. Notes ----- RFC 4271 defines a use and a name for Error subcode 0: - §4.5 (any error code): If no appropriate Error Subcode is defined, then a zero (Unspecific) value is used for the Error Subcode field. - §6.2 (OPEN error code): If one of the Optional Parameters in the OPEN message is recognized, but is malformed, then the Error Subcode MUST be set to 0 (Unspecific). If verified, the "IANA Considerations" section and the IANA registry would also need to be updated accordingly (currently says "0 Reserved") http://www.iana.org/assignments/bgp-parameters/bgp-parameters.xhtml#bgp-parameters-4 -------------------------------------- RFC4271 (draft-ietf-idr-bgp4-26) -------------------------------------- Title : A Border Gateway Protocol 4 (BGP-4) Publication Date : January 2006 Author(s) : Y. Rekhter, Ed., T. Li, Ed., S. Hares, Ed. Category : DRAFT STANDARD Source : Inter-Domain Routing Area : Routing Stream : IETF Verifying Party : IESG From nobody Thu Jul 14 20:19:32 2016 Return-Path: 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 14B0612B01A; Thu, 14 Jul 2016 20:19:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.908 X-Spam-Level: X-Spam-Status: No, score=-3.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, 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 la9zqdECho43; Thu, 14 Jul 2016 20:19:28 -0700 (PDT) Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A164612B005; Thu, 14 Jul 2016 20:19:28 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 14BE61E5D61; Thu, 14 Jul 2016 20:17:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fCR8jJK8D4db; Thu, 14 Jul 2016 20:17:42 -0700 (PDT) Received: from [192.168.0.5] (cpe-76-174-176-44.socal.res.rr.com [76.174.176.44]) by c8a.amsl.com (Postfix) with ESMTPA id B45E71E5D5D; Thu, 14 Jul 2016 20:17:42 -0700 (PDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Megan Ferguson In-Reply-To: <20160714124535.A6A38B80676@rfc-editor.org> Date: Thu, 14 Jul 2016 20:19:27 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20160714124535.A6A38B80676@rfc-editor.org> To: bruno.decraene@orange.com, skh@nexthop.com, Yakov Rekhter , tony.li@tony.li, "Alvaro Retana (aretana)" X-Mailer: Apple Mail (2.1878.6) Archived-At: Cc: idr@ietf.org, The IESG , RFC System Subject: Re: [Idr] [Errata Verified] RFC4271 (4493) X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jul 2016 03:19:30 -0000 All, FYI - we forwarded this errata report to IANA and received confirmation = that the requested updates have been made (please see = http://www.iana.org/assignments/bgp-parameters). We have updated the Notes field of this report as follows: Old: If verified, the "IANA Considerations" section and the IANA registry = would also need to be updated accordingly (currently says "0 Reserved") = http://www.iana.org/assignments/bgp-parameters/bgp-parameters.xhtml#bgp-pa= rameters-4 New: The "IANA Considerations" section would also need to be updated = accordingly (says "0 Reserved=94). However, IANA has corrected the = corresponding registry at = http://www.iana.org/assignments/bgp-parameters. Thank you. RFC Editor/mf On Jul 14, 2016, at 5:45 AM, RFC Errata System = wrote: > The following errata report has been verified for RFC4271, > "A Border Gateway Protocol 4 (BGP-4)".=20 >=20 > -------------------------------------- > You may review the report below and at: > http://www.rfc-editor.org/errata_search.php?rfc=3D4271&eid=3D4493 >=20 > -------------------------------------- > Status: Verified > Type: Technical >=20 > Reported by: Bruno Decraene > Date Reported: 2015-10-06 > Verified by: Alvaro Retana (IESG) >=20 > Section: 4.5 >=20 > Original Text > ------------- > Message Header Error subcodes: >=20 > 1 - Connection Not Synchronized. > 2 - Bad Message Length. > 3 - Bad Message Type. >=20 > OPEN Message Error subcodes: >=20 > 1 - Unsupported Version Number. > 2 - Bad Peer AS. > 3 - Bad BGP Identifier. > 4 - Unsupported Optional Parameter. > 5 - [Deprecated - see Appendix A]. > 6 - Unacceptable Hold Time. >=20 > UPDATE Message Error subcodes: >=20 > 1 - Malformed Attribute List. > 2 - Unrecognized Well-known Attribute. > 3 - Missing Well-known Attribute. > 4 - Attribute Flags Error. > 5 - Attribute Length Error. > 6 - Invalid ORIGIN Attribute. > 7 - [Deprecated - see Appendix A]. > 8 - Invalid NEXT_HOP Attribute. > 9 - Optional Attribute Error. > 10 - Invalid Network Field. > 11 - Malformed AS_PATH. >=20 > Corrected Text > -------------- > Message Header Error subcodes: >=20 > 0 - Unspecific. > 1 - Connection Not Synchronized. > 2 - Bad Message Length. > 3 - Bad Message Type. >=20 > OPEN Message Error subcodes: >=20 > 0 - Unspecific. > 1 - Unsupported Version Number. > 2 - Bad Peer AS. > 3 - Bad BGP Identifier. > 4 - Unsupported Optional Parameter. > 5 - [Deprecated - see Appendix A]. > 6 - Unacceptable Hold Time. >=20 > UPDATE Message Error subcodes: >=20 > 0 - Unspecific. > 1 - Malformed Attribute List. > 2 - Unrecognized Well-known Attribute. > 3 - Missing Well-known Attribute. > 4 - Attribute Flags Error. > 5 - Attribute Length Error. > 6 - Invalid ORIGIN Attribute. > 7 - [Deprecated - see Appendix A]. > 8 - Invalid NEXT_HOP Attribute. > 9 - Optional Attribute Error. > 10 - Invalid Network Field. > 11 - Malformed AS_PATH. >=20 > Notes > ----- > RFC 4271 defines a use and a name for Error subcode 0: > - =A74.5 (any error code):=20 > If no appropriate Error Subcode is defined, then a zero > (Unspecific) value is used for the Error Subcode field. >=20 > - =A76.2 (OPEN error code):=20 > If one of the Optional Parameters in the OPEN message is recognized, > but is malformed, then the Error Subcode MUST be set to 0 > (Unspecific). >=20 > If verified, the "IANA Considerations" section and the IANA registry = would also need to be updated accordingly (currently says "0 Reserved") > = http://www.iana.org/assignments/bgp-parameters/bgp-parameters.xhtml#bgp-pa= rameters-4 >=20 > -------------------------------------- > RFC4271 (draft-ietf-idr-bgp4-26) > -------------------------------------- > Title : A Border Gateway Protocol 4 (BGP-4) > Publication Date : January 2006 > Author(s) : Y. Rekhter, Ed., T. Li, Ed., S. Hares, Ed. > Category : DRAFT STANDARD > Source : Inter-Domain Routing > Area : Routing > Stream : IETF > Verifying Party : IESG >=20 From nobody Fri Jul 15 02:29:28 2016 Return-Path: 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 39C7212DC52; Fri, 15 Jul 2016 02:29:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.187 X-Spam-Level: X-Spam-Status: No, score=-3.187 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.287] 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 yW9LuGfIEObH; Fri, 15 Jul 2016 02:29:25 -0700 (PDT) Received: from mail.crfreenet.org (gateway.crfreenet.org [81.92.146.254]) by ietfa.amsl.com (Postfix) with ESMTP id 2F58912DB52; Fri, 15 Jul 2016 02:29:21 -0700 (PDT) Received: from feanor (unknown [164.215.121.182]) by mail.crfreenet.org (Postfix) with ESMTP id AB368FCCD; Fri, 15 Jul 2016 11:29:19 +0200 (CEST) Date: Fri, 15 Jul 2016 11:29:18 +0200 From: Ondrej Zajicek To: idr@ietf.org, draft-ietf-idr-add-paths@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: Debian GNU/Linux User-Agent: Mutt/1.5.23 (2014-03-12) Message-Id: <20160715092919.AB368FCCD@mail.crfreenet.org> Archived-At: Subject: [Idr] Unspecified handling of multiple ADD-PATH capabilities X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jul 2016 09:29:27 -0000 Hi draft-ietf-idr-add-paths-15 does not specify how multiple ADD-PATH capability instances received in one OPEN message should be handled. There are at least three incompatible possibilities: 1) Ignore all but first/last (like RFC 4724). 2) Merge on per-AF basis, use first/last per AF. 3) Merge on per-(AF+direction) basis Note that RFC 5492 requires handling of multiple instances to be specified: BGP speakers MAY include more than one instance of a capability (as identified by the Capability Code) with non-zero Capability Length field, but with different Capability Value and either the same or different Capability Length. Processing of these capability instances is specific to the Capability Code and MUST be described in the document introducing the new capability. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so." From nobody Fri Jul 15 09:49:27 2016 Return-Path: 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 0EEFA12D81D; Fri, 15 Jul 2016 09:49:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.439 X-Spam-Level: X-Spam-Status: No, score=-2.439 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.26, 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 qqlddO3djhBB; Fri, 15 Jul 2016 09:49:24 -0700 (PDT) Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (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 19ADB12D78F; Fri, 15 Jul 2016 09:49:12 -0700 (PDT) Received: by mail-wm0-x233.google.com with SMTP id f126so32998413wma.1; Fri, 15 Jul 2016 09:49:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=to:subject:from:message-id:date:user-agent:mime-version; bh=8j8e4XTugvzpwgQv4n434DzI2h6oyAn39YIuBaqYvFE=; b=kSlEVCC+X0Cw0KHoPSMsZwgkrRnZnw8vB/cqESRF2evfRlHJfJWLPiSIW+cSTWlhUk cRFeKELrfM8FlIMVNNrr1eLLH8k+3f0bGkHYKYYvl6Qo7wF9SleenufeoFuDsQNgg1Cq +qh6ZQt8ITVAV151V/Kx9p6AjsJEw3qGkByHgFw7WChiJy4h/1WmWGVMY8jvdIU1rHcZ CVrtkByGJLlYHq0BsqZJv3bP3XhWqlx4cwseZuB1latOyDLzRjKhP5kInnjkF9z51SFG gibcqVdUr/B+vDNVAJi5PrvldIWJ9ImID74Ki2W4CeA+F7gfQpWU2DiezY2TaK3rbrNw kxDg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:subject:from:message-id:date:user-agent :mime-version; bh=8j8e4XTugvzpwgQv4n434DzI2h6oyAn39YIuBaqYvFE=; b=lhynGSQ/GcxHAob/J1G7Zp3eE3oTC8n5XPe5wSOcdp+QHhfag5X6bQypEWMAnwPB04 G2NE5s7hmNqGdBigSFDvnIKjs97COem+yAFR7LOMLCr1BoY3JfAZzmWTbERAAEI2n6wQ CoA/rp/sFim1x3IRxlHLRtqU/1U66xVCDrp/+0tkfgMFBPaEtiBw1jNlquxPwwhbJP7h k1Jh+rmFcFjwsAIBBTgJjZyPIUvoRPqtF+1ohejqqRt9RoxdoSKqc5yxWGJBoj3+fvCz 9RWWl7NytBjpiNmmlsZd074L3gieREwtGzts/rVZk7T4SA9c02u8ESo6+FqQyXTOp/gw J8cg== X-Gm-Message-State: ALyK8tLeyxwzyK/ilgLfFDalGQpGI8bwDdQWIGYXxnJWZddjk3/EZplt6pV/S7mH7FXSEA== X-Received: by 10.28.30.1 with SMTP id e1mr12815842wme.77.1468601350199; Fri, 15 Jul 2016 09:49:10 -0700 (PDT) Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id a203sm170024wma.0.2016.07.15.09.49.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 15 Jul 2016 09:49:09 -0700 (PDT) To: draft-liang-idr-flowspec-v1-time@ietf.org, idr@ietf.org From: Stewart Bryant Message-ID: Date: Fri, 15 Jul 2016 17:49:05 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------D0581DF5FE27F643A8778DC3" Archived-At: Subject: [Idr] Mail regarding draft-liang-idr-flowspec-v1-time X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jul 2016 16:49:26 -0000 This is a multi-part message in MIME format. --------------D0581DF5FE27F643A8778DC3 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hi You seem to have specified this using 32bit Unix time. To quote that well known reference Wikipedia: * At 03:14:08 UTC on Tuesday, 19 January 2038,32-bit versions of the Unix time stamp will cease to work , as it will overflow the largest value that can be held in a signed 32-bit number (7FFFFFFF_16 or2,147,483,647 ). Before this moment, software using 32-bit time stamps will need to adopt a new convention for time stamps,^[20] and file formats using 32-bit time stamps will need to be changed to support larger time stamps or a different epoch. If unchanged, the next second will be incorrectly interpreted as 20:45:52 Friday 13 December 1901 UTC. 2038 is not actually that far away, and looks like it will need a protocol re-spin to fix. It would seem to be a good idea to avoid this at design time by using a larger field for seconds, or an epoch that is less than 46 years old, or include an epoch for the BGP session (which allows compact representation and no practical end date)? Regards Stewart --------------D0581DF5FE27F643A8778DC3 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit Hi

You seem to have specified this using 32bit Unix time.

To quote that well known reference Wikipedia:

  • At 03:14:08 UTC on Tuesday, 19 January 2038, 32-bit versions of the Unix time stamp will cease to work, as it will overflow the largest value that can be held in a signed 32-bit number (7FFFFFFF16 or 2,147,483,647). Before this moment, software using 32-bit time stamps will need to adopt a new convention for time stamps,[20] and file formats using 32-bit time stamps will need to be changed to support larger time stamps or a different epoch. If unchanged, the next second will be incorrectly interpreted as 20:45:52 Friday 13 December 1901 UTC.

2038 is not actually that far away, and looks like it will need a protocol re-spin to fix.  It would seem to be a good idea to avoid this at design time by using a larger field for seconds, or an epoch that is less than  46 years old, or include an epoch for the BGP session (which allows compact representation and no practical end date)?

Regards

Stewart
--------------D0581DF5FE27F643A8778DC3-- From nobody Sun Jul 17 21:37:02 2016 Return-Path: X-Original-To: idr@ietf.org Delivered-To: idr@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C60C12B037; Sun, 17 Jul 2016 21:36:57 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.28.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20160718043657.30624.52782.idtracker@ietfa.amsl.com> Date: Sun, 17 Jul 2016 21:36:57 -0700 Archived-At: Cc: idr@ietf.org Subject: [Idr] I-D Action: draft-ietf-idr-bgp-model-02.txt X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jul 2016 04:36:57 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Inter-Domain Routing of the IETF. Title : BGP Model for Service Provider Networks Authors : Anees Shaikh Rob Shakir Keyur Patel Susan Hares Kevin D'Souza Deepak Bansal Alexander Clemm Aleksandr Zhdankin Mahesh Jethanandani Xyfeng Liu Filename : draft-ietf-idr-bgp-model-02.txt Pages : 98 Date : 2016-07-17 Abstract: This document defines a YANG data model for configuring and managing BGP, including protocol, policy, and operational aspects based on data center, carrier and content provider operational requirements. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-model/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-idr-bgp-model-02 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-bgp-model-02 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Mon Jul 18 08:02:05 2016 Return-Path: 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 D277012B042; Sun, 10 Jul 2016 17:59:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.507 X-Spam-Level: X-Spam-Status: No, score=-5.507 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, 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 qpM-28Pj2Osa; Sun, 10 Jul 2016 17:59:15 -0700 (PDT) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3159812B074; Sun, 10 Jul 2016 17:59:12 -0700 (PDT) Received: from 172.18.7.190 (EHLO lhreml706-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CSI75082; Mon, 11 Jul 2016 00:59:09 +0000 (GMT) Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by lhreml706-cah.china.huawei.com (10.201.5.182) with Microsoft SMTP Server (TLS) id 14.3.235.1; Mon, 11 Jul 2016 01:59:08 +0100 Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.179]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0235.001; Mon, 11 Jul 2016 08:58:57 +0800 From: Haoweiguo To: Ross Callon , Donald Eastlake , Susan Hares , "sujay.gupta@ipinfusion.com" , "mdurrani@cisco.com" , Liyizhou , John Scudder Thread-Topic: routing directorate QA review of draft-ietf-idr-ls-trill-01.txt Thread-Index: AdHLZIDwzATvmHF5Tgi9n3A+2f5ymwPqTC/i Date: Mon, 11 Jul 2016 00:58:57 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US, zh-CN Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.135.23.94] Content-Type: multipart/alternative; boundary="_000_DD5FC8DE455C3348B94340C0AB55173350D676F3nkgeml513mbxchi_" MIME-Version: 1.0 X-CFilter-Loop: Reflected X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090201.5782EF5E.001B, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.1.179, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32 X-Mirapoint-Loop-Id: c75b8f2171d22673bc985619c9bfba68 Archived-At: X-Mailman-Approved-At: Mon, 18 Jul 2016 08:02:00 -0700 Cc: "idr@ietf.org" , "rtg-dir@ietf.org" , "trill@ietf.org" Subject: Re: [Idr] routing directorate QA review of draft-ietf-idr-ls-trill-01.txt X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jul 2016 00:59:18 -0000 --_000_DD5FC8DE455C3348B94340C0AB55173350D676F3nkgeml513mbxchi_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hi Ross, Sorry for late response. Thanks for your great comments. Pls see inline. weiguo ________________________________ From: Ross Callon [rcallon@juniper.net] Sent: Tuesday, June 21, 2016 10:27 To: Haoweiguo; Donald Eastlake; Susan Hares; sujay.gupta@ipinfusion.com; md= urrani@cisco.com; Liyizhou; John Scudder Cc: idr@ietf.org; trill@ietf.org; rtg-dir@ietf.org; Ross Callon Subject: routing directorate QA review of draft-ietf-idr-ls-trill-01.txt I have been selected as the QA reviewer for draft-ietf-idr-ls-trill-01.txt.= For more information about the Routing Directorate, please see http://trac= .tools.ietf.org/area/rtg/trac/wiki/RtgDir Summary: I think that this draft is straightforward and well written. I have only a = couple of questions and some very minor nits. I can see situations in which putting TRILL information into BGP may make s= ense, particularly in the case of providing TRILL information to a SDN cont= roller as pointed out in the draft. Due to the close relationship of this d= raft to the work in TRILL I have CC=92d the TRILL working group on this rev= iew and I assume that the TRILL working group will similarly be informed wh= en the document goes to WGLC. Questions: Section 1, second to last paragraph states: If ESADI (End Station Address Distribution Information) protocol [RFC7357] is used for control plane MAC learning in each data center, BGP LS also can be used for MAC address reachability information synchronization across multiple TRILL domains. End-to-end unicast forwarding paths can be calculated based on the synchronized information. Would this be limited to the case where routes are computed by SDN controll= ers? I am thinking that if instead the MAC reachability from one data cente= r is passed via BGP and fed back into TRILL in a different data center then= this would lead to significant issues which have not been discussed in thi= s document. [weiguo]: Yes, the routes are consumed and computed by SDN controllers is t= he main case. However, i don't know why the MAC reachability passing from o= ne data center and feeding back into another data center will cause signifi= cant problems, can you explain further about this? Section 5 (security considerations) states: Procedures and protocol extensions defined in this document do not affect the BGP security model. See [RFC6952] for details. I am not a TRILL expert and therefore might not fully understand all cases = in which TRILL is used. I am however wondering if there are TRILL-specific = issues in that the TRILL information must only be passed to TRILL capable d= evices. I am also wondering whether there is any valid use of =93TRILL in B= GP=94 other than passing TRILL information to SDN controllers. Passing TRIL= L information from one TRILL domain to another TRILL domain and then redist= ributing the information back into normal TRILL packets seems like a bad id= ea at first glance. I am wondering if this section should say something lik= e =93this protocol MUST be used ONLY for passing TRILL information from TRI= LL devices to SDN controllers, and for passing TRILL information between SD= N controllers. [weiguo]: BGP LS provides a mechanism for passing TRILL information from on= e domain to another domain, it also can be used for passing TRILL informati= on from TRILL devices to SDN controllers and between SDN controllers. Can y= ou explain further about why BGP LS can't be used for passing TRILL informa= tion from one domain to another domain? Very minor nits: Section 2 defines the RFC2119 terms and abbreviations used in this document= in the same section with no subsections. I think that it is more normal to= have a subsection for RFC 2119 terms and a different subsection for abbrev= iations used in this document. [weiguo]: OK, will change it in next version. Section 3, first paragraph, last sentence: =93=85multicast group address, a= nd etc.=94 should be =93=85multicast group address, etc.=94. [weiguo]: OK, will change it in next version. Section 3.1, =93iS-IS=94 should be =93IS-IS=94. [weiguo]: OK, will change it in next version. Section 4, second paragraph, I thought that it was a bit odd for a document= to reference itself, as in =93An implementation of this specification[idr-= ls-trill], MUST do=85=94. Would this be a bit less awkward as: =93Any imple= mentation of the protocol in this specification (ie that distributes TRILL = Link-State information using BGP), MUST do=85=94. [weiguo]: OK, will change it in next version. That is all that I found in a couple of readings of this document, Thanks, Ross --_000_DD5FC8DE455C3348B94340C0AB55173350D676F3nkgeml513mbxchi_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable

Hi Ross,

Sorry for late response.

Thanks for your great comments. Pls se= e inline.

weiguo


From: Ross Callon [rcallon@juniper.net] Sent: Tuesday, June 21, 2016 10:27
To: Haoweiguo; Donald Eastlake; Susan Hares; sujay.gupta@ipinfusion.= com; mdurrani@cisco.com; Liyizhou; John Scudder
Cc: idr@ietf.org; trill@ietf.org; rtg-dir@ietf.org; Ross Callon
Subject: routing directorate QA review of draft-ietf-idr-ls-trill-01= .txt

I have been selected as the QA reviewer for draft-ietf-idr-ls-trill-01= .txt. For more information about the Routing Directorate, please see http://trac.tools.ietf.org/area/rtg/trac/wi= ki/RtgDir
 
Summary:
 
I think that this draft is straightforward and well written. I have on= ly a couple of questions and some very minor nits.
 
I can see situations in which putting TRILL information into BGP may m= ake sense, particularly in the case of providing TRILL information to a SDN= controller as pointed out in the draft. Due to the close relationship of t= his draft to the work in TRILL I have CC=92d the TRILL working group on this review and I assume that the T= RILL working group will similarly be informed when the document goes to WGL= C.
 
 
Questions:
 
Section 1, second to last paragraph states:
 
   If ESADI (End Station Address Distribution Information) p= rotocol
   [RFC7357] is used for control plane MAC learning in each = data center,
   BGP LS also can be used for MAC address reachability info= rmation
   synchronization across multiple TRILL domains.  End-= to-end unicast
   forwarding paths can be calculated based on the synchroni= zed
   information.
 
Would this be limited to the case where routes are computed by SDN con= trollers? I am thinking that if instead the MAC reachability from one data = center is passed via BGP and fed back into TRILL in a different data center= then this would lead to significant issues which have not been discussed in this document.
[weiguo]: Yes, the routes are consumed and computed by SDN controllers= is the main case. However, i don't know why the MAC reachability passing f= rom one data center and feeding back into another data center will cause si= gnificant problems, can you explain further about this?
 
Section 5 (security considerations) states:
 
   Procedures and protocol extensions defined in this docume= nt do not
   affect the BGP security model.  See [RFC6952] for de= tails.
 
I am not a TRILL expert and therefore might not fully understand all c= ases in which TRILL is used. I am however wondering if there are TRILL-spec= ific issues in that the TRILL information must only be passed to TRILL capa= ble devices. I am also wondering whether there is any valid use of =93TRILL in BGP=94 other than passing TR= ILL information to SDN controllers. Passing TRILL information from one TRIL= L domain to another TRILL domain and then redistributing the information ba= ck into normal TRILL packets seems like a bad idea at first glance. I am wondering if this section should say some= thing like =93this protocol MUST be used ONLY for passing TRILL information= from TRILL devices to SDN controllers, and for passing TRILL information b= etween SDN controllers.
[weiguo]: BGP LS provides a mechanism for passing TRILL information fr= om one domain to another domain, it also can be used for passing TRILL info= rmation from TRILL devices to SDN controllers and between SDN controllers. = Can you explain further about why BGP LS can't be used for passing TRILL information from one domain to anot= her domain?
 
Very minor nits:
 
Section 2 defines the RFC2119 terms and abbreviations used in this doc= ument in the same section with no subsections. I think that it is more norm= al to have a subsection for RFC 2119 terms and a different subsection for a= bbreviations used in this document.
[weiguo]: OK, will change it in next version.
Section 3, first paragraph, last sentence: =93=85multicast group addre= ss, and  etc.=94 should be =93=85multicast group address, etc.=94.
[weiguo]: OK, will change it in next version.
Section 3.1, =93iS-IS=94 should be =93IS-IS=94.
[weiguo]: OK, will change it in next version.
Section 4, second paragraph, I thought that it was a bit odd for a doc= ument to reference itself, as in =93An implementation of this specification= [idr-ls-trill], MUST do=85=94. Would this be a bit less awkward as: =93Any = implementation of the protocol in this specification (ie that distributes TRILL Link-State information using BGP), MUST do=85= =94.
[weiguo]: OK, will change it in next version.
 
That is all that I found in a couple of readings of this document,
Thanks, Ross
 
--_000_DD5FC8DE455C3348B94340C0AB55173350D676F3nkgeml513mbxchi_-- From nobody Tue Jul 19 03:06:53 2016 Return-Path: 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 AC60D12D1A2 for ; Tue, 19 Jul 2016 03:06:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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 xYvoxDpE72hO for ; Tue, 19 Jul 2016 03:06:46 -0700 (PDT) Received: from mail-it0-x236.google.com (mail-it0-x236.google.com [IPv6:2607:f8b0:4001:c0b::236]) (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 6DEC712D5CC for ; Tue, 19 Jul 2016 03:04:36 -0700 (PDT) Received: by mail-it0-x236.google.com with SMTP id f6so87815159ith.1 for ; Tue, 19 Jul 2016 03:04:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=e6/n7BFaDV0yf1jek5+qkX/a5MWCbQ/nz6oHlfwkRto=; b=N5AzpkFVN3K/m/3JRn+E22osJlXBTVOolYbgt+7hgfbTgyr/tMBbITTnYkMJm+qDk7 E9B2DsEpFYt78rW7eqQoVuCXwna6NsWUVXlV78+iRwHWVML2utbuKwiPpa+hfVrTyZFu hzV6QnaVKpYMlB2DzLb+VQZW3MJzPOHqD4F3yRkCF0uzwDxbe4JbH0jKtx+eXzyQk0pO +m9JJVGfgZIblblMp4mzZtRirGz8Ktym1spe0FGjgHfQqdHP45BdFnn8+niXBSDLaa4+ BPukCSAVzKehiiUzpb5E9yJvyXwV+sM86kIpcLoR9cvZ8QBvy2nay9jSAk1cfvmDp5fb Lcaw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=e6/n7BFaDV0yf1jek5+qkX/a5MWCbQ/nz6oHlfwkRto=; b=R8HLa/hO3lYZZIDfAforAcfgNrXKgdVC1yX0zTJJyIimP4INdH0Ouvn7Whd3cvav2A OKfjd+IfvkjwYWtCMmgRDbQmun7G2AT48vDRYz2g71WsWRgLT9WbjBTFljEMq5ojQgPL wyMDFO9K9ANYOLwQ/DzffAAMmOq6UKU6I4LAY1EvpTUtrGcuyX+fxu7bLMLSuqriJl7q aYKpLcgcrNRhKXgeqf5Ehq56jNMT+6pMNrpQk9brorNBAKZPt4jegExjL61IMOCm8chZ wOjb1DS4RzGQwn7nG0mJCkQ2vfHokuILufbuv9a+LlrLY5bkbRTX+2RxU/ohbt45idv/ N3zw== X-Gm-Message-State: ALyK8tL9yns8TuhI5r8iqBXfoC8E87gLRn3gJpxR6kuCXtN4T5dFrXA9ZKc1Nrxeml+0RS2BCPU4zHcU3am8SQ== X-Received: by 10.36.19.75 with SMTP id 72mr2777388itz.83.1468922675756; Tue, 19 Jul 2016 03:04:35 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.158.82 with HTTP; Tue, 19 Jul 2016 03:03:56 -0700 (PDT) In-Reply-To: References: From: Tony Przygienda Date: Tue, 19 Jul 2016 03:03:56 -0700 Message-ID: To: Robert Raszuk , idr wg Content-Type: multipart/alternative; boundary=001a1145180a4a88170537fa36db Archived-At: Subject: [Idr] Fwd: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jul 2016 10:06:50 -0000 --001a1145180a4a88170537fa36db Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Resending ... ---------- Forwarded message ---------- From: Tony Przygienda Date: Mon, Jul 11, 2016 at 3:04 PM Subject: Re: [Idr] Slot request in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00= .txt To: Robert Raszuk Cc: idr wg On Mon, Jul 11, 2016 at 1:47 PM, Robert Raszuk wrote: > Hi Tony, > Hey Robert, thanks for chiming in. Good questions. I speak here for myself, other authors of the draft may have differing opinions. > > 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 ? > We didn't discuss that one through but the only logical conclusion for me is that the ORF/CP-ORF installed are respected (i.e. it's an implicit AND). I see ORF as statefull, remote-pushed policy on the peer that is not being flipped around all the time (albeit AFAIR there were some attempts @ non-persistent, one shot ORF but that ended up expiring?) The motivation for this work were scenarios where a single-shot refresh is needed, actually concurrent bunch of those based on configuration changes, peer having dropped received routes based on specs (A-D), in policy changes, joining VPNs, EVIs and so on. Putting ORF on a peer, refresh and remove ORFs is significantly heavier process that may interfere on top with normal update process going on and needs to be done one-by-one (since you have to wait for single BoRR/EoRR pair) unless one is very smart about combining ORF possibly & playing with the DEFER/IMMEDIATEs. As we indicated, if the AFI/SAFI is covered by RTC and RTC is supported & one is willing to configure RTs for each subset of routes that may need refreshing, RT will be doing the same job just fine. > > Would you always carry ORF with separate Refresh_ID value ? > Yes, Refresh-ID# is strictly monotonic so there is never a misunderstanding WHAT the BoRR belongs to. Observe that the draft does NOT mandate that a request MUST be followed by according BoRR, only that BoRRs must follow same sequence as requests (i.e. are also strictly monotonic). However, we should probably specify that options _and_ ORF can NOT be mixed in the same type #3 message but it's either one or the other (and anything else is error). This will allow ORF operations like today + benefit of the Refresh ID# on the BoRR so the IMMEDIATE can go on @ the same time as another request with higher Refresh ID# (de facto we allow multiple parallel refreshes as you see). In case of DEFER there will be simply no BoRR for it. > > 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 ? > I agree. Yes, ORF is kind of "permanent filter" on the peer while the intent of this draft is to have bunch of "small refreshes" going on @ same time possibly (if you request the refreshes from a good implementation while low-end implementations may serialize the requests to simplify internal logic ;-). > > As far as current types why not add regular/extended community ? > Discussion came up. Feeling was it's an immediate encroach on RT territory. I argued for it ;-) Ultimately, taking a more relaxed view, we chose to wait and see what the response is and most pressing use cases people bring to it and then we start to define bits and bytes of the options supported, possibly borrowing to an extent from the ORF specs ;-) As in "most sincere form of flattery" and such ... ;-) -- tony --=20 *We=E2=80=99ve heard that a million monkeys at a million keyboards could pr= oduce the complete works of Shakespeare; now, thanks to the Internet, we know that is not true.* =E2=80=94Robert Wilensky --001a1145180a4a88170537fa36db Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Resending ...=C2=A0

---= ------- Forwarded message ----------
From: Tony Przygienda <tonysietf@gmail.com>
Date: Mon, Jul 11, 2016 at 3:0= 4 PM
Subject: Re: [Idr] Slot request in IDR to present = https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00= .txt
To: Robert Raszuk <robe= rt@raszuk.net>
Cc: idr wg <idr= @ietf.org>




On Mon, Jul 11, 2016 at 1:47 PM, Robert Ra= szuk <robert@raszuk.net> wrote:
Hi Tony,

Hey = Robert, thanks for chiming in. Good questions. I speak here for myself, oth= er authors of the draft may have differing opinions.=C2=A0
=C2=A0

Can = you clarify what is the expected behaviour as far as per peer filter-list w= hen you negotiate both Refresh with options, ORF and RTC ? Note that ORF al= so includes recent extension as described in RFC7543 - would all of those b= e always a logical AND towards a peer which pushed those ?=C2=A0

We didn't discuss that one thr= ough but the only logical conclusion for me is that the ORF/CP-ORF installe= d are respected (i.e. it's an implicit AND). I see ORF as statefull, re= mote-pushed policy on the peer that is not being flipped around all the tim= e (albeit AFAIR there were some attempts @ non-persistent, one shot ORF but= that ended up expiring?)

The motivation for this = work were scenarios where a single-shot refresh is needed, actually concurr= ent bunch of those based on configuration changes, peer having dropped rece= ived routes based on specs (A-D), in policy changes, joining VPNs, EVIs and= so on. Putting ORF on a peer, refresh and remove ORFs is significantly hea= vier process that may interfere on top with normal update process going on = and needs to be done one-by-one (since you have to wait for single BoRR/EoR= R pair) unless one is very smart about combining ORF possibly & playing= with the DEFER/IMMEDIATEs. As we indicated, if the AFI/SAFI is covered by = RTC and RTC is supported & one is willing to configure RTs for each sub= set of routes that may need refreshing, RT will be doing the same job just = fine.=C2=A0
=C2=A0

Would you always carry ORF with separate Refresh_ID= value ?=C2=A0

Yes, Refr= esh-ID# is strictly monotonic so there is never a misunderstanding WHAT the= BoRR belongs to. Observe that the draft does NOT mandate that a request MU= ST be followed by according BoRR, only that BoRRs must follow same sequence= as requests (i.e. are also strictly monotonic). However, we should probabl= y specify that options _and_ ORF can NOT be mixed in the same type #3 messa= ge but it's either one or the other (and anything else is error). This = will allow ORF operations like today + benefit of the Refresh ID# =C2=A0on = the BoRR so the IMMEDIATE can go on @ the same time as another request with= higher Refresh ID# (de facto we allow multiple parallel refreshes as you s= ee).=C2=A0 In case of DEFER there will be simply no BoRR for it.=C2=A0
=C2=A0

If one requests full Adj_RIB_Out in the new model and sends refres= h 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 agains= t all ORF entries ? In other words I think the draft should state that Refr= esh_IDs have no impact to ORF ADDs or REMOVE actions - don't you think = ?=C2=A0

I agree. Yes, OR= F is kind of =C2=A0"permanent filter" on the peer while the inten= t of this draft is to have bunch of "small refreshes" going on @ = same time possibly (if you request the refreshes from a good implementation= while low-end implementations may serialize the requests to simplify inter= nal logic ;-).=C2=A0
=C2=A0

As far as current types why not add regula= r/extended community ?

D= iscussion came up. Feeling was it's an immediate encroach on RT territo= ry. I argued for it ;-) =C2=A0Ultimately, taking a more relaxed view, we ch= ose to wait and see what the response is and most pressing use cases people= bring to it and then we start to define bits and bytes of the options supp= orted, possibly borrowing to an extent from the ORF specs ;-) =C2=A0As in &= quot;most sincere form of flattery" and such ... ;-)=C2=A0

-- tony=C2=A0<= /div>
=C2=A0



--
We=E2=80= =99ve heard that a million monkeys at a million keyboards could produce the= complete works of Shakespeare; now, thanks to the Internet, we know that i= s not true.
<= /i>
=E2=80=94Robert Wilensky
--001a1145180a4a88170537fa36db-- From nobody Tue Jul 19 04:44:42 2016 Return-Path: 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 8372712D187 for ; Tue, 19 Jul 2016 04:44:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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 bubhT9TBE4EW for ; Tue, 19 Jul 2016 04:44:37 -0700 (PDT) Received: from mail-it0-x230.google.com (mail-it0-x230.google.com [IPv6:2607:f8b0:4001:c0b::230]) (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 60DF112D180 for ; Tue, 19 Jul 2016 04:44:37 -0700 (PDT) Received: by mail-it0-x230.google.com with SMTP id j124so17229715ith.1 for ; Tue, 19 Jul 2016 04:44:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=0ZFHd7d6XaZMW3E0SeF4jN+fm6ZEbEyTSe705Iy2ykI=; b=MPapd1TAs3Rhwqfxaxbq0Eh+YG8sjaccZZZl/uRo9a9xaRul6rj9Ou9tvDWgu1HLe8 sVYgwJoKdq9oYOiF68rUzGxrQX7nxUztEl9x9oKtffp8ZLAYerWXu31RVaQtbS/2w3hu vzwjYYICVpIKdx69U0U6UURyCyltBFNxxpAIHllqiCOy0NVlUDEm1pgLM94tIurss7xt 1CsTDs2Hetb4Ky63BpKe4CGE8gW0pRi5Ib7sHxEHskmLb7tHDcdcmiPefhvCTVBfDqVi msezN6CO68qfbrZugIyatKv8s4ermiuKPtkfMTlOcR2+WQfIlRQlsZK5tA7sriIn33ZB 4TCw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=0ZFHd7d6XaZMW3E0SeF4jN+fm6ZEbEyTSe705Iy2ykI=; b=iN9o7Vk4egKlUK+kfISEZSHGjhyRD+KH0TX250MnZmUEr5xbF9YnyNFTwmis3UV6I1 W8Eox/ZCO/qaJ6aWS00Fc6GACcrqyyTY0qD0CRmtKu78iG1ViIo4s+i9TeEWviLf9m55 lPeMeeXBD4Zkxnb3hhcihV08+OqtjhoyzO8AXnZQaVBZ3NR+24HX5nprhw7R15pFex+t qqlib6D6GkKN7jwru1XsnCR65Q1GAmeUj1znVTTjg4lFHP18reVm7GaPgD9jWy1M2U0e BwjPiy6Z9MnmSdAyTZ/1u2OZWdVmazsC0FWc+65zXvhWNPozhq72mWeOD+adVI4uhaWz pGXQ== X-Gm-Message-State: ALyK8tLo4uQkOP9WyxGtDdPWkRDQRjZ6Wc1EwztVxtfIPH2k8DQxKqEaWgSDGyEdnn4syFrZfp8Kuv9lEfx9uQ== X-Received: by 10.36.87.140 with SMTP id u134mr2063790ita.38.1468928676743; Tue, 19 Jul 2016 04:44:36 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.158.82 with HTTP; Tue, 19 Jul 2016 04:43:57 -0700 (PDT) In-Reply-To: References: From: Tony Przygienda Date: Tue, 19 Jul 2016 04:43:57 -0700 Message-ID: To: Robert Raszuk , idr wg Content-Type: multipart/alternative; boundary=001a1135018cfa5af00537fb9b52 Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jul 2016 11:44:40 -0000 --001a1135018cfa5af00537fb9b52 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable yep, sorry, I missed that I only answered ORF and not RTC As example look at 7432 section 7.9. Box of Pandora has been opened a while ago, route type being the other one ... On Tue, Jul 19, 2016 at 3:03 AM, Tony Przygienda wrote: > Resending ... > > ---------- Forwarded message ---------- > From: Tony Przygienda > Date: Mon, Jul 11, 2016 at 3:04 PM > Subject: Re: [Idr] Slot request in IDR to present > https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-= 00.txt > To: Robert Raszuk > Cc: idr wg > > > > > On Mon, Jul 11, 2016 at 1:47 PM, Robert Raszuk wrote: > >> Hi Tony, >> > > Hey Robert, thanks for chiming in. Good questions. I speak here for > myself, other authors of the draft may have differing opinions. > > >> >> 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 ? >> > > We didn't discuss that one through but the only logical conclusion for me > is that the ORF/CP-ORF installed are respected (i.e. it's an implicit AND= ). > I see ORF as statefull, remote-pushed policy on the peer that is not bein= g > flipped around all the time (albeit AFAIR there were some attempts @ > non-persistent, one shot ORF but that ended up expiring?) > > The motivation for this work were scenarios where a single-shot refresh i= s > needed, actually concurrent bunch of those based on configuration changes= , > peer having dropped received routes based on specs (A-D), in policy > changes, joining VPNs, EVIs and so on. Putting ORF on a peer, refresh and > remove ORFs is significantly heavier process that may interfere on top wi= th > normal update process going on and needs to be done one-by-one (since you > have to wait for single BoRR/EoRR pair) unless one is very smart about > combining ORF possibly & playing with the DEFER/IMMEDIATEs. As we > indicated, if the AFI/SAFI is covered by RTC and RTC is supported & one i= s > willing to configure RTs for each subset of routes that may need > refreshing, RT will be doing the same job just fine. > > >> >> Would you always carry ORF with separate Refresh_ID value ? >> > > Yes, Refresh-ID# is strictly monotonic so there is never a > misunderstanding WHAT the BoRR belongs to. Observe that the draft does NO= T > mandate that a request MUST be followed by according BoRR, only that BoRR= s > must follow same sequence as requests (i.e. are also strictly monotonic). > However, we should probably specify that options _and_ ORF can NOT be mix= ed > in the same type #3 message but it's either one or the other (and anythin= g > else is error). This will allow ORF operations like today + benefit of th= e > Refresh ID# on the BoRR so the IMMEDIATE can go on @ the same time as > another request with higher Refresh ID# (de facto we allow multiple > parallel refreshes as you see). In case of DEFER there will be simply no > BoRR for it. > > >> >> 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 yo= u >> think ? >> > > I agree. Yes, ORF is kind of "permanent filter" on the peer while the > intent of this draft is to have bunch of "small refreshes" going on @ sam= e > time possibly (if you request the refreshes from a good implementation > while low-end implementations may serialize the requests to simplify > internal logic ;-). > > >> >> As far as current types why not add regular/extended community ? >> > > Discussion came up. Feeling was it's an immediate encroach on RT > territory. I argued for it ;-) Ultimately, taking a more relaxed view, w= e > chose to wait and see what the response is and most pressing use cases > people bring to it and then we start to define bits and bytes of the > options supported, possibly borrowing to an extent from the ORF specs ;-) > As in "most sincere form of flattery" and such ... ;-) > > -- tony > > > > > -- > *We=E2=80=99ve heard that a million monkeys at a million keyboards could = produce > the complete works of Shakespeare; now, thanks to the Internet, we know > that is not true.* > =E2=80=94Robert Wilensky > --=20 *We=E2=80=99ve heard that a million monkeys at a million keyboards could pr= oduce the complete works of Shakespeare; now, thanks to the Internet, we know that is not true.* =E2=80=94Robert Wilensky --001a1135018cfa5af00537fb9b52 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
yep, sorry, I missed that I only answered ORF and not RTC= =C2=A0

As example look at 7432 section 7.9. Box of Pando= ra has been opened a while ago, route type being the other one ...=C2=A0

On Tue, = Jul 19, 2016 at 3:03 AM, Tony Przygienda <tonysietf@gmail.com> wrote:
Resending ..= .=C2=A0

---------= - Forwarded message ----------
From: Tony = Przygienda <tonysietf@gmail.com>
Date: Mon, Jul 11,= 2016 at 3:04 PM
Subject: Re: [Idr] Slot request in IDR to present https://www.ietf.org/internet-drafts/draft-id= r-bgp-route-refresh-options-00.txt
To: Robert Raszuk <robert@raszuk.net>
Cc= : idr wg <idr@ietf.org= >




On Mon, Jul 11, 2016 at 1:47 PM, Robert Raszuk <ro= bert@raszuk.net> wrote:
Hi Tony,

Hey Robert, t= hanks for chiming in. Good questions. I speak here for myself, other author= s of the draft may have differing opinions.=C2=A0
=C2=A0

Can you clarify what is = the expected behaviour as far as per peer filter-list when you negotiate bo= th Refresh with options, ORF and RTC ? Note that ORF also includes recent e= xtension as described in RFC7543 - would all of those be always a logical A= ND towards a peer which pushed those ?=C2=A0
<= br>
We didn't discuss that one through but the only lo= gical conclusion for me is that the ORF/CP-ORF installed are respected (i.e= . it's an implicit AND). I see ORF as statefull, remote-pushed policy o= n the peer that is not being flipped around all the time (albeit AFAIR ther= e were some attempts @ non-persistent, one shot ORF but that ended up expir= ing?)

The motivation for this work were scenarios = where a single-shot refresh is needed, actually concurrent bunch of those b= ased on configuration changes, peer having dropped received routes based on= specs (A-D), in policy changes, joining VPNs, EVIs and so on. Putting ORF = on a peer, refresh and remove ORFs is significantly heavier process that ma= y interfere on top with normal update process going on and needs to be done= one-by-one (since you have to wait for single BoRR/EoRR pair) unless one i= s very smart about combining ORF possibly & playing with the DEFER/IMME= DIATEs. As we indicated, if the AFI/SAFI is covered by RTC and RTC is suppo= rted & one is willing to configure RTs for each subset of routes that m= ay need refreshing, RT will be doing the same job just fine.=C2=A0
=C2=A0

Would y= ou always carry ORF with separate Refresh_ID value ?=C2=A0

Yes, Refresh-ID# is strictly monotonic s= o there is never a misunderstanding WHAT the BoRR belongs to. Observe that = the draft does NOT mandate that a request MUST be followed by according BoR= R, only that BoRRs must follow same sequence as requests (i.e. are also str= ictly monotonic). However, we should probably specify that options _and_ OR= F can NOT be mixed in the same type #3 message but it's either one or t= he other (and anything else is error). This will allow ORF operations like = today + benefit of the Refresh ID# =C2=A0on the BoRR so the IMMEDIATE can g= o on @ the same time as another request with higher Refresh ID# (de facto w= e allow multiple parallel refreshes as you see).=C2=A0 In case of DEFER the= re will be simply no BoRR for it.=C2=A0
=C2=A0

If one requests full Adj_RIB_Out i= n the new model and sends refresh message with new refresh_id and no option= s 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 REMOV= E actions - don't you think ?=C2=A0

I agree. Yes, ORF is kind of =C2=A0"permanent filter&q= uot; on the peer while the intent of this draft is to have bunch of "s= mall refreshes" going on @ same time possibly (if you request the refr= eshes from a good implementation while low-end implementations may serializ= e the requests to simplify internal logic ;-).=C2=A0
=C2=A0=

As far as current typ= es why not add regular/extended community ?
Discussion came up. Feeling was it's an immediate e= ncroach on RT territory. I argued for it ;-) =C2=A0Ultimately, taking a mor= e relaxed view, we chose to wait and see what the response is and most pres= sing use cases people bring to it and then we start to define bits and byte= s of the options supported, possibly borrowing to an extent from the ORF sp= ecs ;-) =C2=A0As in "most sincere form of flattery" and such ... = ;-)=C2=A0

-- tony=C2= =A0
=C2=A0



--
<= div dir=3D"ltr">
We=E2=80=99ve heard that a million monkeys at a mil= lion keyboards could produce the complete works of Shakespeare; now, thanks= to the Internet, we know that is not true.
=E2=80=94Robert Wile= nsky



--
We=E2=80=99ve heard that a million monkeys at a million keyboards cou= ld produce the complete works of Shakespeare; now, thanks to the Internet, = we know that is not true.=E2=80=94Robert Wilensky<= br>
--001a1135018cfa5af00537fb9b52-- From nobody Tue Jul 19 05:24:48 2016 Return-Path: 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 4EFF212D591 for ; Tue, 19 Jul 2016 05:24:46 -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 F9bFJrGb7Cmp for ; Tue, 19 Jul 2016 05:24:44 -0700 (PDT) Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com [IPv6:2607:f8b0:400d:c09::233]) (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 E9F5112D626 for ; Tue, 19 Jul 2016 05:24:41 -0700 (PDT) Received: by mail-qk0-x233.google.com with SMTP id x1so13615627qkb.3 for ; Tue, 19 Jul 2016 05:24:41 -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:date:message-id:subject :from:to:cc; bh=omHFBfCxegTjICaMJHFppLquP3ejhsICktDCxCA+IY4=; b=FI9TUsQeMO3a2nweOD9S4VU8KcpmUTNAduavejWPby+E0gZ98R+avsfl+Rdok5M/aE 28TK4r3sennEXqm/9cE4Pwc/TO74uQFUDUVYpS/+srh2rNB42JcFL87aBIwoZnIXe25d YnwuGZbT5ttfLIMEemPcsWlc+TaIKjDc3+0oOSOztG3QY6IMS8Z1APJi1mRHIv0gtbkn wrnUadlyJG8P+bF5Lg7EfJLRllNjoDMDI3GkwOwBC+EsqI5tpcBnzzfcA+OV+MiA4uyO +K4FdGQNQ8UcoqESEmyNJh4ifKhruZRLojUZ9+e2lmIqVvlscjXz26Mq6rtTsLHHynu/ R0YA== 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:date :message-id:subject:from:to:cc; bh=omHFBfCxegTjICaMJHFppLquP3ejhsICktDCxCA+IY4=; b=SHOjGeZ7H5pzDT+/iQjkgXA/Nm2mbGVRN5QIKxmQYGjMVZ6Mor2mRkRrbY7QZ3IObX jXN1uhh35zQFhcCiQ3/rpaf9dIgv1YR7S8khA1C794y5xYgGo1lttYTmMlDQTBUen6Cg I1YREUl6/2mt8k7cL4+Gcqyc4tCJoQJZ2+dUQBTSQoTCPhnjJaaeWjXAier88Ln8tygK Cyu68yhmwvdYoMhECWoMxEuhF4x4uWDylsS5dQuMVJKQ7a0og3Q7A3zilqMwQMX3/YPZ 4VXiCISI6Wq/Ngk4AdSwWXCwotyRD9WDs2GwoI5Ukohj5th2t+I5t02ng3SdTA2hxnBB Dn9Q== X-Gm-Message-State: ALyK8tI3Jl2wZtlw2d8dv0/YnVViGOjjavliW0Tti34a8eB6Ux6IcFEI5Ndfk8ip1UiR5L1WIsPQMqZAp5wyoA== MIME-Version: 1.0 X-Received: by 10.55.16.27 with SMTP id a27mr53777438qkh.34.1468931081054; Tue, 19 Jul 2016 05:24:41 -0700 (PDT) Sender: rraszuk@gmail.com Received: by 10.237.36.90 with HTTP; Tue, 19 Jul 2016 05:24:40 -0700 (PDT) Received: by 10.237.36.90 with HTTP; Tue, 19 Jul 2016 05:24:40 -0700 (PDT) In-Reply-To: References: Date: Tue, 19 Jul 2016 14:24:40 +0200 X-Google-Sender-Auth: kwcEnCwYh1vyG_bZBRNKGUJcXiE Message-ID: From: Robert Raszuk To: Tony Przygienda Content-Type: multipart/alternative; boundary=001a11476366492fd70537fc2b5f Archived-At: Cc: idr wg 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jul 2016 12:24:46 -0000 --001a11476366492fd70537fc2b5f Content-Type: text/plain; charset=UTF-8 Tony, Section 7.9 only mentions that RD *MAY BE* structured to include VLAN ID but equally well it says that it may be locally generated. As someone pointed at this IETF term "MAY" = "MAY NOT" hence any actions based on that is likely to fail. Said this while perhaps someone can use your RD type to manually query the peer for subset of routes then for any automated action .. which is what is really need say when you modify RT import list it will fail. Bottom line I think we should not add elements to protocols which are not guaranteed to work if for nothing else then to reduce operational issues in multi vendor environments. Thx R. --001a11476366492fd70537fc2b5f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Tony,

Section 7.9 only mentions that RD *MAY BE* structured to inc= lude VLAN ID but equally well it says=C2=A0 that it may be locally generate= d.

As someone pointed at this IETF term "MAY" =3D &qu= ot;MAY NOT" hence any actions based on that is likely to fail.

Said this while perhaps someone can use your RD type to manu= ally query the peer for subset of routes then for any automated action .. w= hich is what is really need say when you modify RT import list it will fail= .

Bottom line I think we should not add elements to protocols = which are not guaranteed to work if for nothing else then to reduce operati= onal issues in multi vendor environments.

Thx
R.

--001a11476366492fd70537fc2b5f-- From nobody Tue Jul 19 05:59:30 2016 Return-Path: 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 C483512D792 for ; Tue, 19 Jul 2016 05:59:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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 QwpxwcANBMkC for ; Tue, 19 Jul 2016 05:59:26 -0700 (PDT) Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::231]) (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 9ED6D12D7FF for ; Tue, 19 Jul 2016 05:56:42 -0700 (PDT) Received: by mail-io0-x231.google.com with SMTP id q83so17965202iod.1 for ; Tue, 19 Jul 2016 05:56:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=DbE8Ktl79nI1AkYF5qcnbYKiGU/WzDvmkoK/I+eiWzI=; b=jAt+uHRRHfDR+pb/4x8ijMyVShmqQpIBh1xHyiaXivfJ8x6omQX+FMh5qeocI38GD5 pYFo0mUOybSzTHPD7pA6zUng5szEzLyuDQkRO0qMo+QREKDm5SYMMFh7R4zTvLBFMOVq UtBUg70CwMflsF6YeMP3rZEWjO44DiYq/5XZiSwO1L/zaghNUvcq/W4Vd1KJLMx5YsqD sMYwy5GpV5/LbaXDtIuLqq7dkhuPyf0z+m+NyvMTAbPPRk3fsTpRa0k2tqNxwgbM6wsO HDsloNOc50TiVBB5sxhcqI/vZBbr/mpKnfnktdZXhbzqYzY0ytylTxDerSChIljtuq2j J87g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=DbE8Ktl79nI1AkYF5qcnbYKiGU/WzDvmkoK/I+eiWzI=; b=Ofnk4P+UX5HcrVXVBRbX9+1vOSn/0gSgJWSMAEqxYzF0d/SI3WVNRzxiGsu9ICpOYP e6GUB6sLn2nriPPoAdbiaSipG4e2ZaI9dPMipvVocxV0Kn//XVRqBYb2sc4RXKFtw26B i/n24r2b6FeY8uho3rWasamzPs+zsEj6YaYC0RA28255HXA+p2vEccXA0GJ6nnljz+eo LEE2xm3Aj66s+oZ3W17wCd8e34638H7LtxYuSD1+v+uDHH6j3B77WIKw/ssMCJ9zWiWQ c5WCLx6mZGPrX2WSc59+McLJqLQvcQnA2qeorYDWq1MiHE895faNH7WYhxcRnLlylHBS XRnQ== X-Gm-Message-State: ALyK8tIwitFMXtmdvpF/ZLsA9rtZeUGvamD1it/gdsyhHqaJXfY3QpfClTrHraPA+Ice8S+iCiD4LyMcpndYBA== X-Received: by 10.107.29.142 with SMTP id d136mr39328387iod.50.1468933001358; Tue, 19 Jul 2016 05:56:41 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.158.82 with HTTP; Tue, 19 Jul 2016 05:56:02 -0700 (PDT) In-Reply-To: References: From: Tony Przygienda Date: Tue, 19 Jul 2016 05:56:02 -0700 Message-ID: To: Robert Raszuk Content-Type: multipart/alternative; boundary=001a11409584beb5e80537fc9d97 Archived-At: Cc: idr wg 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jul 2016 12:59:29 -0000 --001a11409584beb5e80537fc9d97 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable OK, agreed in principle on 7.9. In fact, we were oscillating between RD (with or without prefix length) filter + address prefix filter and just 'NLRI filter' but given NLRI we need to add RD anyway in there. The RD filter allows you to wildcard the RD, i.e. you can e.g. request prefix/address update from your peer without. We can start to split hair as well that section 8.2.1 does NOT give you the flexibility to do anything else but structure the RD ... Overall, I think the Pandora's box is open and it's better to allow an RD filter to at least wildcard RDs ... --- tony On Tue, Jul 19, 2016 at 5:24 AM, Robert Raszuk wrote: > Tony, > > Section 7.9 only mentions that RD *MAY BE* structured to include VLAN ID > but equally well it says that it may be locally generated. > > As someone pointed at this IETF term "MAY" =3D "MAY NOT" hence any action= s > based on that is likely to fail. > > Said this while perhaps someone can use your RD type to manually query th= e > peer for subset of routes then for any automated action .. which is what = is > really need say when you modify RT import list it will fail. > > Bottom line I think we should not add elements to protocols which are not > guaranteed to work if for nothing else then to reduce operational issues = in > multi vendor environments. > > Thx > R. > --=20 *We=E2=80=99ve heard that a million monkeys at a million keyboards could pr= oduce the complete works of Shakespeare; now, thanks to the Internet, we know that is not true.* =E2=80=94Robert Wilensky --001a11409584beb5e80537fc9d97 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
OK, agreed in principle on 7.9.=C2=A0

I= n fact, we were oscillating between RD (with or without prefix length) filt= er + address prefix filter and just 'NLRI filter' but given NLRI we= need to add RD anyway in there. The RD filter allows you to wildcard the R= D, i.e. you can e.g. request prefix/address update from your peer without.= =C2=A0

We can start to split hair as well that section 8= .2.1 does NOT give you the flexibility to do anything else but structure th= e RD ...=C2=A0

Overall, I think the Pandora's bo= x is open and it's better to allow an RD filter to at least wildcard RD= s ...=C2=A0

--- tony=C2=A0
=

On Tue, Jul 19, 2= 016 at 5:24 AM, Robert Raszuk <robert@raszuk.net> wrote:
=

Tony,

Section 7.9 only mentions that RD *MAY BE* structured to inc= lude VLAN ID but equally well it says=C2=A0 that it may be locally generate= d.

As someone pointed at this IETF term "MAY" =3D &qu= ot;MAY NOT" hence any actions based on that is likely to fail.

Said this while perhaps someone can use your RD type to manu= ally query the peer for subset of routes then for any automated action .. w= hich is what is really need say when you modify RT import list it will fail= .

Bottom line I think we should not add elements to protocols = which are not guaranteed to work if for nothing else then to reduce operati= onal issues in multi vendor environments.

Thx
R.




--
We=E2=80=99ve heard that a million monkeys at a million keyboards cou= ld produce the complete works of Shakespeare; now, thanks to the Internet, = we know that is not true.=E2=80=94Robert Wilensky<= br>
--001a11409584beb5e80537fc9d97-- From nobody Tue Jul 19 06:15:12 2016 Return-Path: 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 418D512DFCD for ; Tue, 19 Jul 2016 06:15:11 -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 Wogkcxi4uxCu for ; Tue, 19 Jul 2016 06:15:06 -0700 (PDT) Received: from mail-qk0-x232.google.com (mail-qk0-x232.google.com [IPv6:2607:f8b0:400d:c09::232]) (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 586DA12D869 for ; Tue, 19 Jul 2016 06:06:29 -0700 (PDT) Received: by mail-qk0-x232.google.com with SMTP id p74so14801260qka.0 for ; Tue, 19 Jul 2016 06:06:29 -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:date:message-id:subject :from:to:cc; bh=YYogL94De3CYxKdAV47IEcmV7WxTm1cfj84AmX5MXI0=; b=kOlPRFXYxd+uG5bXCtQTdMHHlI1L9IxQ+wdzWE1Q8xHEobFb5f/l7N8tjKoxHoXaRW NMk+F62wNBwBcK+w/mUb6t0PeSTMtrjNQllFpwT5bLIUS1bdC55uJtfAxiUTpCJyubkt pxP/c3SszhdXTh9DessuDWyr5I3wjTRplJvQxRcK4byCv/ZG3d9q78Hx0e3igloWzqfY gMie9LeKIP15YJgigG1iX/+Gm7XXqVzbVHw53xTkOrQis22Z95Kv6nUFfTKe9Bzj3XIe Cz3itBVkl7KbCEKEKwwqRTQ3POKmTE2VMd0/sO3YhnfAkvtj0k8PfRK45PxDv86l6a1c uH/A== 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:date :message-id:subject:from:to:cc; bh=YYogL94De3CYxKdAV47IEcmV7WxTm1cfj84AmX5MXI0=; b=Saw9EH2Z2L+iQXLDCFcxFS/9SO4iW4DoABGbJUxOde/bgWKWFoGEOCy+FhGHVfYkQ8 0B6w+nXps70YG9hA0cQ1/0ZWl3FPfj87d1Q31SgGpYvIA4a0vpilZrBvtTCGakTwC8u6 0IX9Befmf2O+EJIym4Ew8AjbJ1328Pf/pURtAcTKn+P/jWLSzZEEgQbjKJdXtG01TRWd FyiJxFZXdtCCSZo2/FX8wwiZTKtC6cf4/sNKciE9/rEPDSrcwHL4gS6xFkpOz3TGD+cr otLc87q6cPm/t00SChJkoRtxc3yOS0SJGdO2BSm6WAmwv4mvZoteFll7VkqUnjT9/ger EudQ== X-Gm-Message-State: ALyK8tK7WNQEArjW/PtKIW+jloEgA+a8BKcnwCaRFuKiPd5jKDGXSY8BzCj/bbuhlwtYiPMiksg1DxXVcBysaQ== MIME-Version: 1.0 X-Received: by 10.55.129.71 with SMTP id c68mr49921818qkd.174.1468933588427; Tue, 19 Jul 2016 06:06:28 -0700 (PDT) Sender: rraszuk@gmail.com Received: by 10.237.36.90 with HTTP; Tue, 19 Jul 2016 06:06:27 -0700 (PDT) Received: by 10.237.36.90 with HTTP; Tue, 19 Jul 2016 06:06:27 -0700 (PDT) In-Reply-To: References: Date: Tue, 19 Jul 2016 15:06:27 +0200 X-Google-Sender-Auth: zf5EWXofE-BPGCQvsQSHswDdBKE Message-ID: From: Robert Raszuk To: Tony Przygienda Content-Type: multipart/alternative; boundary=94eb2c06266abcae320537fcc0c2 Archived-At: Cc: idr wg 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jul 2016 13:15:11 -0000 --94eb2c06266abcae320537fcc0c2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Tony Yes you have RD *prefix* not RD fixed value there which is a good progress ;). But you just can not use RD to even query prefixes (of those SAFIS which use it) in any automated way simply as your PE does not know it. Human could use it but this is I hope not the main motivation of your draft. So if you want to query say VPN safi you need RT + NLRI not RD. In those query you would define and use the notion of ANY_RD flag implicitely or explicitely. Till someone at next ietf proposes new safi to auto discover all RDs in the network which I hope will never happen use of RD for filtering or query should be removed. Best, R. On Jul 19, 2016 2:56 PM, "Tony Przygienda" wrote: > OK, agreed in principle on 7.9. > > In fact, we were oscillating between RD (with or without prefix length) > filter + address prefix filter and just 'NLRI filter' but given NLRI we > need to add RD anyway in there. The RD filter allows you to wildcard the > RD, i.e. you can e.g. request prefix/address update from your peer withou= t. > > We can start to split hair as well that section 8.2.1 does NOT give you > the flexibility to do anything else but structure the RD ... > > Overall, I think the Pandora's box is open and it's better to allow an RD > filter to at least wildcard RDs ... > > --- tony > > On Tue, Jul 19, 2016 at 5:24 AM, Robert Raszuk wrote: > >> Tony, >> >> Section 7.9 only mentions that RD *MAY BE* structured to include VLAN ID >> but equally well it says that it may be locally generated. >> >> As someone pointed at this IETF term "MAY" =3D "MAY NOT" hence any actio= ns >> based on that is likely to fail. >> >> Said this while perhaps someone can use your RD type to manually query >> the peer for subset of routes then for any automated action .. which is >> what is really need say when you modify RT import list it will fail. >> >> Bottom line I think we should not add elements to protocols which are no= t >> guaranteed to work if for nothing else then to reduce operational issues= in >> multi vendor environments. >> >> Thx >> R. >> > > > > -- > *We=E2=80=99ve heard that a million monkeys at a million keyboards could = produce > the complete works of Shakespeare; now, thanks to the Internet, we know > that is not true.* > =E2=80=94Robert Wilensky > --94eb2c06266abcae320537fcc0c2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Tony

Yes you have RD *prefix* not RD fixed value there which is a= good progress ;).

But you just can not use RD to even query prefixes (of those= SAFIS which use it) in any automated way simply as your PE does not know i= t. Human could use it but this is I hope not the main motivation of your dr= aft.

So if you want to query say VPN safi you need RT + NLRI not = RD. In those query you would define and use the notion of ANY_RD flag impli= citely or explicitely.

Till someone at next ietf proposes new safi to auto discover= all RDs in the network which I hope will never happen use of RD for filter= ing or query should be removed.

Best,
R.


On Jul 19, 2016 2= :56 PM, "Tony Przygienda" <tonysietf@gmail.com> wrote:
OK, agreed in principle on 7.9.=C2=A0
In fact, we were oscillating between RD (with or without = prefix length) filter + address prefix filter and just 'NLRI filter'= ; but given NLRI we need to add RD anyway in there. The RD filter allows yo= u to wildcard the RD, i.e. you can e.g. request prefix/address update from = your peer without.=C2=A0

We can start to split hair as w= ell that section 8.2.1 does NOT give you the flexibility to do anything els= e but structure the RD ...=C2=A0

Overall, I think th= e Pandora's box is open and it's better to allow an RD filter to at= least wildcard RDs ...=C2=A0

--- tony=C2=A0=

On Tue, Jul 19, 2016 at 5:24 AM, Robert Raszuk <robert@raszuk.net>= wrote:

Tony,

Section 7.9 only mentions that RD *MAY BE* structured to inc= lude VLAN ID but equally well it says=C2=A0 that it may be locally generate= d.

As someone pointed at this IETF term "MAY" =3D &qu= ot;MAY NOT" hence any actions based on that is likely to fail.

Said this while perhaps someone can use your RD type to manu= ally query the peer for subset of routes then for any automated action .. w= hich is what is really need say when you modify RT import list it will fail= .

Bottom line I think we should not add elements to protocols = which are not guaranteed to work if for nothing else then to reduce operati= onal issues in multi vendor environments.

Thx
R.




--
We=E2=80=99ve heard th= at a million monkeys at a million keyboards could produce the complete work= s of Shakespeare; now, thanks to the Internet, we know that is not true.
= =E2=80=94Robert Wilensky
--94eb2c06266abcae320537fcc0c2-- From nobody Tue Jul 19 07:10:58 2016 Return-Path: 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 BE2CA12DFD1 for ; Tue, 19 Jul 2016 07:10:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.507 X-Spam-Level: X-Spam-Status: No, score=-5.507 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, 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 9fnEGMNdCFlh for ; Tue, 19 Jul 2016 07:10:55 -0700 (PDT) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2511912E0C9 for ; Tue, 19 Jul 2016 06:20:57 -0700 (PDT) Received: from 172.18.7.190 (EHLO lhreml708-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CSV63298; Tue, 19 Jul 2016 13:20:50 +0000 (GMT) Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by lhreml708-cah.china.huawei.com (10.201.5.202) with Microsoft SMTP Server (TLS) id 14.3.235.1; Tue, 19 Jul 2016 14:20:49 +0100 Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0235.001; Tue, 19 Jul 2016 21:20:45 +0800 From: Xuxiaohu To: Robert Raszuk , Tony Przygienda Thread-Topic: [Idr] Slot request in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00.txt Thread-Index: AQHR4bL5/Or89VLM1kKahAYDnVqIxaAfJ4gAgAAIxACAAALpgIAAiS7d Date: Tue, 19 Jul 2016 13:20:45 +0000 Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D57661E@NKGEML515-MBX.china.huawei.com> References: , In-Reply-To: Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.200.217.24] Content-Type: multipart/alternative; boundary="_000_1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D57661ENKGEML515MBXchi_" MIME-Version: 1.0 X-CFilter-Loop: Reflected X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A010201.578E2933.019F, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32 X-Mirapoint-Loop-Id: 1d49f1868d34f798a8a4c3223c51495c Archived-At: Cc: idr wg 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jul 2016 14:10:57 -0000 --_000_1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D57661ENKGEML515MBXchi_ Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 DQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQq3orz+yMs6IElkciBbaWRyLWJv dW5jZXNAaWV0Zi5vcmddILT6se0gUm9iZXJ0IFJhc3p1ayBbcm9iZXJ0QHJhc3p1ay5uZXRdDQq3 osvNyrG85DogMjAxNsTqN9TCMTnI1SAyMTowNg0KytW8/sjLOiBUb255IFByenlnaWVuZGENCrOt y806IGlkciB3Zw0K1vfM4jogUmU6IFtJZHJdIFNsb3QgcmVxdWVzdCBpbiBJRFIgdG8gcHJlc2Vu dCBodHRwczovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtaWRyLWJncC1yb3V0 ZS1yZWZyZXNoLW9wdGlvbnMtMDAudHh0DQoNCg0KVG9ueQ0KDQpZZXMgeW91IGhhdmUgUkQgKnBy ZWZpeCogbm90IFJEIGZpeGVkIHZhbHVlIHRoZXJlIHdoaWNoIGlzIGEgZ29vZCBwcm9ncmVzcyA7 KS4NCg0KQnV0IHlvdSBqdXN0IGNhbiBub3QgdXNlIFJEIHRvIGV2ZW4gcXVlcnkgcHJlZml4ZXMg KG9mIHRob3NlIFNBRklTIHdoaWNoIHVzZSBpdCkgaW4gYW55IGF1dG9tYXRlZCB3YXkgc2ltcGx5 IGFzIHlvdXIgUEUgZG9lcyBub3Qga25vdyBpdC4gSHVtYW4gY291bGQgdXNlIGl0IGJ1dCB0aGlz IGlzIEkgaG9wZSBub3QgdGhlIG1haW4gbW90aXZhdGlvbiBvZiB5b3VyIGRyYWZ0Lg0KDQpTbyBp ZiB5b3Ugd2FudCB0byBxdWVyeSBzYXkgVlBOIHNhZmkgeW91IG5lZWQgUlQgKyBOTFJJIG5vdCBS RC4gSW4gdGhvc2UgcXVlcnkgeW91IHdvdWxkIGRlZmluZSBhbmQgdXNlIHRoZSBub3Rpb24gb2Yg QU5ZX1JEIGZsYWcgaW1wbGljaXRlbHkgb3IgZXhwbGljaXRlbHkuDQoNCg0KDQpbWGlhb2h1XSBJ biBmYWN0LCB0aGlzIGRyYWZ0IChodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQteHUt YmVzcy1sM3Zwbi1wcmVmaXgtb3JmLTAyKSBpcyBqdXN0IGludGVuZGVkIHRvIGFjaGlldmUgdGhl IGFib3ZlIGdvYWwgKGkuZS4sIHJlcXVlc3RpbmcgcGFydGlhbCByb3V0ZXMgb2YgYSBnaXZlbiBW UE4pIC4NCg0KDQoNCkJlc3QgcmVnYXJkcywNCg0KWGlhb2h1DQoNCg0KDQpUaWxsIHNvbWVvbmUg YXQgbmV4dCBpZXRmIHByb3Bvc2VzIG5ldyBzYWZpIHRvIGF1dG8gZGlzY292ZXIgYWxsIFJEcyBp biB0aGUgbmV0d29yayB3aGljaCBJIGhvcGUgd2lsbCBuZXZlciBoYXBwZW4gdXNlIG9mIFJEIGZv ciBmaWx0ZXJpbmcgb3IgcXVlcnkgc2hvdWxkIGJlIHJlbW92ZWQuDQoNCkJlc3QsDQpSLg0KDQpP biBKdWwgMTksIDIwMTYgMjo1NiBQTSwgIlRvbnkgUHJ6eWdpZW5kYSIgPHRvbnlzaWV0ZkBnbWFp bC5jb208bWFpbHRvOnRvbnlzaWV0ZkBnbWFpbC5jb20+PiB3cm90ZToNCk9LLCBhZ3JlZWQgaW4g cHJpbmNpcGxlIG9uIDcuOS4NCg0KSW4gZmFjdCwgd2Ugd2VyZSBvc2NpbGxhdGluZyBiZXR3ZWVu IFJEICh3aXRoIG9yIHdpdGhvdXQgcHJlZml4IGxlbmd0aCkgZmlsdGVyICsgYWRkcmVzcyBwcmVm aXggZmlsdGVyIGFuZCBqdXN0ICdOTFJJIGZpbHRlcicgYnV0IGdpdmVuIE5MUkkgd2UgbmVlZCB0 byBhZGQgUkQgYW55d2F5IGluIHRoZXJlLiBUaGUgUkQgZmlsdGVyIGFsbG93cyB5b3UgdG8gd2ls ZGNhcmQgdGhlIFJELCBpLmUuIHlvdSBjYW4gZS5nLiByZXF1ZXN0IHByZWZpeC9hZGRyZXNzIHVw ZGF0ZSBmcm9tIHlvdXIgcGVlciB3aXRob3V0Lg0KDQpXZSBjYW4gc3RhcnQgdG8gc3BsaXQgaGFp ciBhcyB3ZWxsIHRoYXQgc2VjdGlvbiA4LjIuMSBkb2VzIE5PVCBnaXZlIHlvdSB0aGUgZmxleGli aWxpdHkgdG8gZG8gYW55dGhpbmcgZWxzZSBidXQgc3RydWN0dXJlIHRoZSBSRCAuLi4NCg0KT3Zl cmFsbCwgSSB0aGluayB0aGUgUGFuZG9yYSdzIGJveCBpcyBvcGVuIGFuZCBpdCdzIGJldHRlciB0 byBhbGxvdyBhbiBSRCBmaWx0ZXIgdG8gYXQgbGVhc3Qgd2lsZGNhcmQgUkRzIC4uLg0KDQotLS0g dG9ueQ0KDQpPbiBUdWUsIEp1bCAxOSwgMjAxNiBhdCA1OjI0IEFNLCBSb2JlcnQgUmFzenVrIDxy b2JlcnRAcmFzenVrLm5ldDxtYWlsdG86cm9iZXJ0QHJhc3p1ay5uZXQ+PiB3cm90ZToNCg0KVG9u eSwNCg0KU2VjdGlvbiA3Ljkgb25seSBtZW50aW9ucyB0aGF0IFJEICpNQVkgQkUqIHN0cnVjdHVy ZWQgdG8gaW5jbHVkZSBWTEFOIElEIGJ1dCBlcXVhbGx5IHdlbGwgaXQgc2F5cyAgdGhhdCBpdCBt YXkgYmUgbG9jYWxseSBnZW5lcmF0ZWQuDQoNCkFzIHNvbWVvbmUgcG9pbnRlZCBhdCB0aGlzIElF VEYgdGVybSAiTUFZIiA9ICJNQVkgTk9UIiBoZW5jZSBhbnkgYWN0aW9ucyBiYXNlZCBvbiB0aGF0 IGlzIGxpa2VseSB0byBmYWlsLg0KDQpTYWlkIHRoaXMgd2hpbGUgcGVyaGFwcyBzb21lb25lIGNh biB1c2UgeW91ciBSRCB0eXBlIHRvIG1hbnVhbGx5IHF1ZXJ5IHRoZSBwZWVyIGZvciBzdWJzZXQg b2Ygcm91dGVzIHRoZW4gZm9yIGFueSBhdXRvbWF0ZWQgYWN0aW9uIC4uIHdoaWNoIGlzIHdoYXQg aXMgcmVhbGx5IG5lZWQgc2F5IHdoZW4geW91IG1vZGlmeSBSVCBpbXBvcnQgbGlzdCBpdCB3aWxs IGZhaWwuDQoNCkJvdHRvbSBsaW5lIEkgdGhpbmsgd2Ugc2hvdWxkIG5vdCBhZGQgZWxlbWVudHMg dG8gcHJvdG9jb2xzIHdoaWNoIGFyZSBub3QgZ3VhcmFudGVlZCB0byB3b3JrIGlmIGZvciBub3Ro aW5nIGVsc2UgdGhlbiB0byByZWR1Y2Ugb3BlcmF0aW9uYWwgaXNzdWVzIGluIG11bHRpIHZlbmRv ciBlbnZpcm9ubWVudHMuDQoNClRoeA0KUi4NCg0KDQoNCi0tDQpXZaGvdmUgaGVhcmQgdGhhdCBh IG1pbGxpb24gbW9ua2V5cyBhdCBhIG1pbGxpb24ga2V5Ym9hcmRzIGNvdWxkIHByb2R1Y2UgdGhl IGNvbXBsZXRlIHdvcmtzIG9mIFNoYWtlc3BlYXJlOyBub3csIHRoYW5rcyB0byB0aGUgSW50ZXJu ZXQsIHdlIGtub3cgdGhhdCBpcyBub3QgdHJ1ZS4NCqGqUm9iZXJ0IFdpbGVuc2t5DQo= --_000_1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D57661ENKGEML515MBXchi_ Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: quoted-printable

 

=B7=A2=BC=FE=C8=CB: Idr [idr-bounces@ietf.= org] =B4=FA=B1=ED Robert Raszuk [robert@raszuk.net]
=B7=A2=CB=CD=CA=B1=BC=E4: 2016=C4=EA7=D4=C219=C8=D5 21:06
=CA=D5=BC=FE=C8=CB: Tony Przygienda
=B3=AD=CB=CD: idr wg
=D6=F7=CC=E2: Re: [Idr] Slot request in IDR to present https://www.i= etf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00.txt

Tony

Yes you have RD *prefix* not RD fixed value there which is a= good progress ;).

But you just can not use RD to even query prefixes (of those= SAFIS which use it) in any automated way simply as your PE does not know i= t. Human could use it but this is I hope not the main motivation of your dr= aft.

So if you want to query say VPN safi you need RT + NLRI = not RD. In those query you would define and use the notion of ANY_RD flag i= mplicitely or explicitely.

 

[Xiaohu] In fact, this draft (https://tools.ietf.org/htm= l/draft-xu-bess-l3vpn-prefix-orf-02) is just intended to achieve t= he above goal (i.e., requesting partial routes of a given VPN) .

 

Best regards,

Xiaohu

 

Till someone at next ietf proposes new safi to auto discover= all RDs in the network which I hope will never happen use of RD for filter= ing or query should be removed.

Best,
R.


On Jul 19, 2016 2:56 PM, "Tony Przygienda&q= uot; <tonysietf= @gmail.com> wrote:
OK, agreed in principle on 7.9. 

In fact, we were oscillating between RD (with or without prefix length= ) filter + address prefix filter and just 'NLRI filter' but given NLRI = we need to add RD anyway in there. The RD filter allows you to wildcard the= RD, i.e. you can e.g. request prefix/address update from your peer without. 

We can start to split hair as well that section 8.2.1 does NOT give yo= u the flexibility to do anything else but structure the RD ... 

Overall, I think the Pandora's box is open and it's better to allow an= RD filter to at least wildcard RDs ... 

--- tony 

On Tue, Jul 19, 2016 at 5:24 AM, Robert Raszuk <= span dir=3D"ltr"> <robert@raszuk.ne= t> wrote:

Tony,

Section 7.9 only mentions that RD *MAY BE* structured to inc= lude VLAN ID but equally well it says  that it may be locally generate= d.

As someone pointed at this IETF term "MAY" =3D &qu= ot;MAY NOT" hence any actions based on that is likely to fail.

Said this while perhaps someone can use your RD type to manu= ally query the peer for subset of routes then for any automated action .. w= hich is what is really need say when you modify RT import list it will fail= .

Bottom line I think we should not add elements to protocols = which are not guaranteed to work if for nothing else then to reduce operati= onal issues in multi vendor environments.

Thx
R.




--
We=A1= =AFve heard that a million monkeys at a million keyboards could produce the= complete works of Shakespeare; now, thanks to the Internet, we know that i= s not true.
= =A1=AARobert Wilensky
--_000_1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D57661ENKGEML515MBXchi_-- From nobody Tue Jul 19 14:47:54 2016 Return-Path: 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 64D5412D13F for ; Tue, 19 Jul 2016 14:47:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.507 X-Spam-Level: X-Spam-Status: No, score=-5.507 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, 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 4UHKasdMAObh for ; Tue, 19 Jul 2016 14:47:48 -0700 (PDT) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69D8B12B025 for ; Tue, 19 Jul 2016 14:47:47 -0700 (PDT) Received: from 172.18.7.190 (EHLO lhreml707-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CNY60987; Tue, 19 Jul 2016 21:47:44 +0000 (GMT) Received: from NKGEML414-HUB.china.huawei.com (10.98.56.75) by lhreml707-cah.china.huawei.com (10.201.5.199) with Microsoft SMTP Server (TLS) id 14.3.235.1; Tue, 19 Jul 2016 22:47:41 +0100 Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml414-hub.china.huawei.com ([10.98.56.75]) with mapi id 14.03.0235.001; Wed, 20 Jul 2016 05:47:35 +0800 From: "Dongjie (Jimmy)" To: Tony Przygienda , Robert Raszuk , idr wg Thread-Topic: [Idr] Fwd: Slot request in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00.txt Thread-Index: AQHR4aVU83cQxXd4nUuy17dJqjAuSaAgQJlw Date: Tue, 19 Jul 2016 21:47:34 +0000 Message-ID: <76CD132C3ADEF848BD84D028D243C92774EEF7CF@NKGEML515-MBX.china.huawei.com> References: In-Reply-To: Accept-Language: en-US, zh-CN Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.200.216.14] Content-Type: multipart/alternative; boundary="_000_76CD132C3ADEF848BD84D028D243C92774EEF7CFNKGEML515MBXchi_" MIME-Version: 1.0 X-CFilter-Loop: Reflected X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090204.578EA001.0112, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32 X-Mirapoint-Loop-Id: 30fd6b1a07a3ac00d82fc45c67e61a7b Archived-At: Subject: Re: [Idr] Fwd: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jul 2016 21:47:51 -0000 --_000_76CD132C3ADEF848BD84D028D243C92774EEF7CFNKGEML515MBXchi_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 SGkgVG9ueSwNCg0KUGxlYXNlIHNlZSBzb21lIGNvbW1lbnRzIGlubGluZSB3aXRoIFtKaWVdOg0K DQpGcm9tOiBJZHIgW21haWx0bzppZHItYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIFRv bnkgUHJ6eWdpZW5kYQ0KU2VudDogVHVlc2RheSwgSnVseSAxOSwgMjAxNiA2OjA0IFBNDQpUbzog Um9iZXJ0IFJhc3p1azsgaWRyIHdnDQpTdWJqZWN0OiBbSWRyXSBGd2Q6IFNsb3QgcmVxdWVzdCBp biBJRFIgdG8gcHJlc2VudCBodHRwczovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJh ZnQtaWRyLWJncC1yb3V0ZS1yZWZyZXNoLW9wdGlvbnMtMDAudHh0DQoNClJlc2VuZGluZyAuLi4N Cg0KLS0tLS0tLS0tLSBGb3J3YXJkZWQgbWVzc2FnZSAtLS0tLS0tLS0tDQpGcm9tOiBUb255IFBy enlnaWVuZGEgPHRvbnlzaWV0ZkBnbWFpbC5jb208bWFpbHRvOnRvbnlzaWV0ZkBnbWFpbC5jb20+ Pg0KRGF0ZTogTW9uLCBKdWwgMTEsIDIwMTYgYXQgMzowNCBQTQ0KU3ViamVjdDogUmU6IFtJZHJd IFNsb3QgcmVxdWVzdCBpbiBJRFIgdG8gcHJlc2VudCBodHRwczovL3d3dy5pZXRmLm9yZy9pbnRl cm5ldC1kcmFmdHMvZHJhZnQtaWRyLWJncC1yb3V0ZS1yZWZyZXNoLW9wdGlvbnMtMDAudHh0DQpU bzogUm9iZXJ0IFJhc3p1ayA8cm9iZXJ0QHJhc3p1ay5uZXQ8bWFpbHRvOnJvYmVydEByYXN6dWsu bmV0Pj4NCkNjOiBpZHIgd2cgPGlkckBpZXRmLm9yZzxtYWlsdG86aWRyQGlldGYub3JnPj4NCg0K DQoNCk9uIE1vbiwgSnVsIDExLCAyMDE2IGF0IDE6NDcgUE0sIFJvYmVydCBSYXN6dWsgPHJvYmVy dEByYXN6dWsubmV0PG1haWx0bzpyb2JlcnRAcmFzenVrLm5ldD4+IHdyb3RlOg0KSGkgVG9ueSwN Cg0KSGV5IFJvYmVydCwgdGhhbmtzIGZvciBjaGltaW5nIGluLiBHb29kIHF1ZXN0aW9ucy4gSSBz cGVhayBoZXJlIGZvciBteXNlbGYsIG90aGVyIGF1dGhvcnMgb2YgdGhlIGRyYWZ0IG1heSBoYXZl IGRpZmZlcmluZyBvcGluaW9ucy4NCg0KDQpDYW4geW91IGNsYXJpZnkgd2hhdCBpcyB0aGUgZXhw ZWN0ZWQgYmVoYXZpb3VyIGFzIGZhciBhcyBwZXIgcGVlciBmaWx0ZXItbGlzdCB3aGVuIHlvdSBu ZWdvdGlhdGUgYm90aCBSZWZyZXNoIHdpdGggb3B0aW9ucywgT1JGIGFuZCBSVEMgPyBOb3RlIHRo YXQgT1JGIGFsc28gaW5jbHVkZXMgcmVjZW50IGV4dGVuc2lvbiBhcyBkZXNjcmliZWQgaW4gUkZD NzU0MyAtIHdvdWxkIGFsbCBvZiB0aG9zZSBiZSBhbHdheXMgYSBsb2dpY2FsIEFORCB0b3dhcmRz IGEgcGVlciB3aGljaCBwdXNoZWQgdGhvc2UgPw0KDQpXZSBkaWRuJ3QgZGlzY3VzcyB0aGF0IG9u ZSB0aHJvdWdoIGJ1dCB0aGUgb25seSBsb2dpY2FsIGNvbmNsdXNpb24gZm9yIG1lIGlzIHRoYXQg dGhlIE9SRi9DUC1PUkYgaW5zdGFsbGVkIGFyZSByZXNwZWN0ZWQgKGkuZS4gaXQncyBhbiBpbXBs aWNpdCBBTkQpLiBJIHNlZSBPUkYgYXMgc3RhdGVmdWxsLCByZW1vdGUtcHVzaGVkIHBvbGljeSBv biB0aGUgcGVlciB0aGF0IGlzIG5vdCBiZWluZyBmbGlwcGVkIGFyb3VuZCBhbGwgdGhlIHRpbWUg KGFsYmVpdCBBRkFJUiB0aGVyZSB3ZXJlIHNvbWUgYXR0ZW1wdHMgQCBub24tcGVyc2lzdGVudCwg b25lIHNob3QgT1JGIGJ1dCB0aGF0IGVuZGVkIHVwIGV4cGlyaW5nPykNCg0KW0ppZV0gSSB0aGlu ayB0aGUgYXR0ZW1wdHMgeW91IG1lbnRpb25lZCBoZXJlIGFyZSB0aGUgb25lLXRpbWUgT1JGIGRy YWZ0czogZHJhZnQtemVuZy1pZHItb25lLXRpbWUtcHJlZml4LW9yZiAgYW5kIGRyYWZ0LWRvbmct aWRyLW9uZS10aW1lLWV4dC1jb21tdW5pdHktb3JmLiBBZnRlciBzZXZlcmFsIHJldmlzaW9ucywg dGhlc2UgZHJhZnRzIGdvdCBleHBpcmVkIGR1ZSB0byBsYWNrIG9mIHJlcXVpcmVtZW50cyBhdCB0 aGF0IHRpbWUuIElmIHBlb3BsZSBmb3VuZCBzb21lIG5ldyB1c2UgY2FzZXMgb2YgdGhlc2Uga2lu ZHMgb2YgbWVjaGFuaXNtcywgdGhlIGF1dGhvcnMgd291bGQgYmUgaGFwcHkgdG8gYnJpbmcgdGhl bSBiYWNrIHRvIGRpc2N1c3Npb24uDQoNClRoZSBtb3RpdmF0aW9uIGZvciB0aGlzIHdvcmsgd2Vy ZSBzY2VuYXJpb3Mgd2hlcmUgYSBzaW5nbGUtc2hvdCByZWZyZXNoIGlzIG5lZWRlZCwgYWN0dWFs bHkgY29uY3VycmVudCBidW5jaCBvZiB0aG9zZSBiYXNlZCBvbiBjb25maWd1cmF0aW9uIGNoYW5n ZXMsIHBlZXIgaGF2aW5nIGRyb3BwZWQgcmVjZWl2ZWQgcm91dGVzIGJhc2VkIG9uIHNwZWNzIChB LUQpLCBpbiBwb2xpY3kgY2hhbmdlcywgam9pbmluZyBWUE5zLCBFVklzIGFuZCBzbyBvbi4gUHV0 dGluZyBPUkYgb24gYSBwZWVyLCByZWZyZXNoIGFuZCByZW1vdmUgT1JGcyBpcyBzaWduaWZpY2Fu dGx5IGhlYXZpZXIgcHJvY2VzcyB0aGF0IG1heSBpbnRlcmZlcmUgb24gdG9wIHdpdGggbm9ybWFs IHVwZGF0ZSBwcm9jZXNzIGdvaW5nIG9uIGFuZCBuZWVkcyB0byBiZSBkb25lIG9uZS1ieS1vbmUg KHNpbmNlIHlvdSBoYXZlIHRvIHdhaXQgZm9yIHNpbmdsZSBCb1JSL0VvUlIgcGFpcikgdW5sZXNz IG9uZSBpcyB2ZXJ5IHNtYXJ0IGFib3V0IGNvbWJpbmluZyBPUkYgcG9zc2libHkgJiBwbGF5aW5n IHdpdGggdGhlIERFRkVSL0lNTUVESUFURXMuIEFzIHdlIGluZGljYXRlZCwgaWYgdGhlIEFGSS9T QUZJIGlzIGNvdmVyZWQgYnkgUlRDIGFuZCBSVEMgaXMgc3VwcG9ydGVkICYgb25lIGlzIHdpbGxp bmcgdG8gY29uZmlndXJlIFJUcyBmb3IgZWFjaCBzdWJzZXQgb2Ygcm91dGVzIHRoYXQgbWF5IG5l ZWQgcmVmcmVzaGluZywgUlQgd2lsbCBiZSBkb2luZyB0aGUgc2FtZSBqb2IganVzdCBmaW5lLg0K DQpbSmllXSBUaGUgbW90aXZhdGlvbnMgbG9vayBzaW1pbGFyIHRvIHdoYXQgd2UgZGVzY3JpYmVk IGZvciB0aGUgb25lLXRpbWUgT1JGIGRyYWZ0cy4NCg0KDQpXb3VsZCB5b3UgYWx3YXlzIGNhcnJ5 IE9SRiB3aXRoIHNlcGFyYXRlIFJlZnJlc2hfSUQgdmFsdWUgPw0KDQpZZXMsIFJlZnJlc2gtSUQj IGlzIHN0cmljdGx5IG1vbm90b25pYyBzbyB0aGVyZSBpcyBuZXZlciBhIG1pc3VuZGVyc3RhbmRp bmcgV0hBVCB0aGUgQm9SUiBiZWxvbmdzIHRvLiBPYnNlcnZlIHRoYXQgdGhlIGRyYWZ0IGRvZXMg Tk9UIG1hbmRhdGUgdGhhdCBhIHJlcXVlc3QgTVVTVCBiZSBmb2xsb3dlZCBieSBhY2NvcmRpbmcg Qm9SUiwgb25seSB0aGF0IEJvUlJzIG11c3QgZm9sbG93IHNhbWUgc2VxdWVuY2UgYXMgcmVxdWVz dHMgKGkuZS4gYXJlIGFsc28gc3RyaWN0bHkgbW9ub3RvbmljKS4gSG93ZXZlciwgd2Ugc2hvdWxk IHByb2JhYmx5IHNwZWNpZnkgdGhhdCBvcHRpb25zIF9hbmRfIE9SRiBjYW4gTk9UIGJlIG1peGVk IGluIHRoZSBzYW1lIHR5cGUgIzMgbWVzc2FnZSBidXQgaXQncyBlaXRoZXIgb25lIG9yIHRoZSBv dGhlciAoYW5kIGFueXRoaW5nIGVsc2UgaXMgZXJyb3IpLiBUaGlzIHdpbGwgYWxsb3cgT1JGIG9w ZXJhdGlvbnMgbGlrZSB0b2RheSArIGJlbmVmaXQgb2YgdGhlIFJlZnJlc2ggSUQjICBvbiB0aGUg Qm9SUiBzbyB0aGUgSU1NRURJQVRFIGNhbiBnbyBvbiBAIHRoZSBzYW1lIHRpbWUgYXMgYW5vdGhl ciByZXF1ZXN0IHdpdGggaGlnaGVyIFJlZnJlc2ggSUQjIChkZSBmYWN0byB3ZSBhbGxvdyBtdWx0 aXBsZSBwYXJhbGxlbCByZWZyZXNoZXMgYXMgeW91IHNlZSkuICBJbiBjYXNlIG9mIERFRkVSIHRo ZXJlIHdpbGwgYmUgc2ltcGx5IG5vIEJvUlIgZm9yIGl0Lg0KDQoNCklmIG9uZSByZXF1ZXN0cyBm dWxsIEFkal9SSUJfT3V0IGluIHRoZSBuZXcgbW9kZWwgYW5kIHNlbmRzIHJlZnJlc2ggbWVzc2Fn ZSB3aXRoIG5ldyByZWZyZXNoX2lkIGFuZCBubyBvcHRpb25zIGhvd2V2ZXIgdGhlcmUgYXJlIE9S RiBlbnRyaWVzIGFscmVhZHkgaW5zdGFsbGVkIGluIHRoZSBwYXN0IHdvdWxkIGhlIGdldCBqdXN0 IHRoZSBzdWJzZXQgb2Ygcm91dGVzIGFnYWluc3QgYWxsIE9SRiBlbnRyaWVzID8gSW4gb3RoZXIg d29yZHMgSSB0aGluayB0aGUgZHJhZnQgc2hvdWxkIHN0YXRlIHRoYXQgUmVmcmVzaF9JRHMgaGF2 ZSBubyBpbXBhY3QgdG8gT1JGIEFERHMgb3IgUkVNT1ZFIGFjdGlvbnMgLSBkb24ndCB5b3UgdGhp bmsgPw0KDQpJIGFncmVlLiBZZXMsIE9SRiBpcyBraW5kIG9mICAicGVybWFuZW50IGZpbHRlciIg b24gdGhlIHBlZXIgd2hpbGUgdGhlIGludGVudCBvZiB0aGlzIGRyYWZ0IGlzIHRvIGhhdmUgYnVu Y2ggb2YgInNtYWxsIHJlZnJlc2hlcyIgZ29pbmcgb24gQCBzYW1lIHRpbWUgcG9zc2libHkgKGlm IHlvdSByZXF1ZXN0IHRoZSByZWZyZXNoZXMgZnJvbSBhIGdvb2QgaW1wbGVtZW50YXRpb24gd2hp bGUgbG93LWVuZCBpbXBsZW1lbnRhdGlvbnMgbWF5IHNlcmlhbGl6ZSB0aGUgcmVxdWVzdHMgdG8g c2ltcGxpZnkgaW50ZXJuYWwgbG9naWMgOy0pLg0KDQoNCkFzIGZhciBhcyBjdXJyZW50IHR5cGVz IHdoeSBub3QgYWRkIHJlZ3VsYXIvZXh0ZW5kZWQgY29tbXVuaXR5ID8NCg0KRGlzY3Vzc2lvbiBj YW1lIHVwLiBGZWVsaW5nIHdhcyBpdCdzIGFuIGltbWVkaWF0ZSBlbmNyb2FjaCBvbiBSVCB0ZXJy aXRvcnkuIEkgYXJndWVkIGZvciBpdCA7LSkgIFVsdGltYXRlbHksIHRha2luZyBhIG1vcmUgcmVs YXhlZCB2aWV3LCB3ZSBjaG9zZSB0byB3YWl0IGFuZCBzZWUgd2hhdCB0aGUgcmVzcG9uc2UgaXMg YW5kIG1vc3QgcHJlc3NpbmcgdXNlIGNhc2VzIHBlb3BsZSBicmluZyB0byBpdCBhbmQgdGhlbiB3 ZSBzdGFydCB0byBkZWZpbmUgYml0cyBhbmQgYnl0ZXMgb2YgdGhlIG9wdGlvbnMgc3VwcG9ydGVk LCBwb3NzaWJseSBib3Jyb3dpbmcgdG8gYW4gZXh0ZW50IGZyb20gdGhlIE9SRiBzcGVjcyA7LSkg IEFzIGluICJtb3N0IHNpbmNlcmUgZm9ybSBvZiBmbGF0dGVyeSIgYW5kIHN1Y2ggLi4uIDstKQ0K DQpbSmllXSBBY3R1YWxseSBiZWZvcmUgdGhlIG9uZS10aW1lIE9SRiBkcmFmdHMgd2VyZSBzdWJt aXR0ZWQsIHdlIGluaXRpYWxseSBjb25zaWRlcmVkIHRvIG1ha2UgaXQgYSDigJxzZWxlY3RpdmUg cm91dGUgcmVmcmVzaOKAnSBtZWNoYW5pc20uIFRoZW4gd2UgcmVhbGl6ZWQgdGhhdCB0aGUgZmls dGVycyB3aWxsIGJlIHF1aXRlIHNpbWlsYXIgdG8gdGhlIG9uZXMgYWxyZWFkeSBkZWZpbmVkIGZv ciBPUkYuIEluIG9yZGVyIHRvIHJldXNlIHRoZSBPUkYgZmlsdGVycywgd2UgdGhlbiBkZWNpZGVk IHRvIGRlZmluZSB0aGlzIG1lY2hhbmlzbSBhcyBuZXcg4oCcb25lLXRpbWXigJ0gT1JGIHR5cGVz LiAgSnVzdCB0byBwcm92aWRlIHNvbWUgYmFja2dyb3VuZCBpbmZvcm1hdGlvbiBzaW5jZSB5b3Ug YWxzbyBwbGFuIHRvIHJldXNlIHRoZSBmb3JtYXQgb2YgdGhlIGV4aXN0aW5nIE9SRiB0eXBlcy4N Cg0KQmVzdCByZWdhcmRzLA0KSmllDQoNCi0tIHRvbnkNCg0KDQoNCg0KLS0NCldl4oCZdmUgaGVh cmQgdGhhdCBhIG1pbGxpb24gbW9ua2V5cyBhdCBhIG1pbGxpb24ga2V5Ym9hcmRzIGNvdWxkIHBy b2R1Y2UgdGhlIGNvbXBsZXRlIHdvcmtzIG9mIFNoYWtlc3BlYXJlOyBub3csIHRoYW5rcyB0byB0 aGUgSW50ZXJuZXQsIHdlIGtub3cgdGhhdCBpcyBub3QgdHJ1ZS4NCuKAlFJvYmVydCBXaWxlbnNr eQ0K --_000_76CD132C3ADEF848BD84D028D243C92774EEF7CFNKGEML515MBXchi_ Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: base64 PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTIgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6 5a6L5L2TOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtm b250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMgMiA0 O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUg MiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJcQOWui+S9kyI7DQoJ cGFub3NlLTE6MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5 OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQpAZm9udC1mYWNlDQoJ e2ZvbnQtZmFtaWx5Okdlb3JnaWE7DQoJcGFub3NlLTE6MiA0IDUgMiA1IDQgNSAyIDMgMzt9DQov KiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1z b05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNp emU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OuWui+S9kzt9DQphOmxpbmssIHNwYW4uTXNvSHlwZXJs aW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpibHVlOw0KCXRleHQtZGVjb3Jh dGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJ e21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9u OnVuZGVybGluZTt9DQpwLk1zb0FjZXRhdGUsIGxpLk1zb0FjZXRhdGUsIGRpdi5Nc29BY2V0YXRl DQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoi5om55rOo5qGG5paH 5pysIENoYXIiOw0KCW1hcmdpbjowY207DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQt c2l6ZTo5LjBwdDsNCglmb250LWZhbWlseTrlrovkvZM7fQ0Kc3Bhbi5ob2VuemINCgl7bXNvLXN0 eWxlLW5hbWU6aG9lbnpiO30NCnNwYW4uQ2hhcg0KCXttc28tc3R5bGUtbmFtZToi5om55rOo5qGG 5paH5pysIENoYXIiOw0KCW1zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazrm ibnms6jmoYbmlofmnKw7DQoJZm9udC1mYW1pbHk65a6L5L2TO30NCnNwYW4uRW1haWxTdHlsZTIw DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJp Iiwic2Fucy1zZXJpZiI7DQoJY29sb3I6IzFGNDk3RDt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28t c3R5bGUtdHlwZTpleHBvcnQtb25seTt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo2MTIu MHB0IDc5Mi4wcHQ7DQoJbWFyZ2luOjcyLjBwdCA5MC4wcHQgNzIuMHB0IDkwLjBwdDt9DQpkaXYu V29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBn dGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIx MDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpz aGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIg Lz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGxh bmc9IlpILUNOIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xhc3M9IldvcmRT ZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9 ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtz YW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPkhpIFRvbnksDQo8bzpwPjwvbzpwPjwvc3Bh bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZv bnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5z LXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4N CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXpl OjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYm cXVvdDs7Y29sb3I6IzFGNDk3RCI+UGxlYXNlIHNlZSBzb21lIGNvbW1lbnRzIGlubGluZSB3aXRo IFtKaWVdOjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu IGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtD YWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4m bmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRv cDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6My4wcHQgMGNtIDBjbSAwY20iPg0KPHAgY2xh c3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAu MHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7 Ij5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAu MHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7 Ij4gSWRyIFttYWlsdG86aWRyLWJvdW5jZXNAaWV0Zi5vcmddDQo8Yj5PbiBCZWhhbGYgT2YgPC9i PlRvbnkgUHJ6eWdpZW5kYTxicj4NCjxiPlNlbnQ6PC9iPiBUdWVzZGF5LCBKdWx5IDE5LCAyMDE2 IDY6MDQgUE08YnI+DQo8Yj5Ubzo8L2I+IFJvYmVydCBSYXN6dWs7IGlkciB3Zzxicj4NCjxiPlN1 YmplY3Q6PC9iPiBbSWRyXSBGd2Q6IFNsb3QgcmVxdWVzdCBpbiBJRFIgdG8gcHJlc2VudCBodHRw czovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtaWRyLWJncC1yb3V0ZS1yZWZy ZXNoLW9wdGlvbnMtMDAudHh0PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFz cz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+ PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj5SZXNl bmRpbmcgLi4uJm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJN c29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+ DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0 Ij48c3BhbiBsYW5nPSJFTi1VUyI+LS0tLS0tLS0tLSBGb3J3YXJkZWQgbWVzc2FnZSAtLS0tLS0t LS0tPGJyPg0KRnJvbTogPGI+VG9ueSBQcnp5Z2llbmRhPC9iPiAmbHQ7PGEgaHJlZj0ibWFpbHRv OnRvbnlzaWV0ZkBnbWFpbC5jb20iPnRvbnlzaWV0ZkBnbWFpbC5jb208L2E+Jmd0Ozxicj4NCkRh dGU6IE1vbiwgSnVsIDExLCAyMDE2IGF0IDM6MDQgUE08YnI+DQpTdWJqZWN0OiBSZTogW0lkcl0g U2xvdCByZXF1ZXN0IGluIElEUiB0byBwcmVzZW50IDxhIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYu b3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1pZHItYmdwLXJvdXRlLXJlZnJlc2gtb3B0aW9ucy0w MC50eHQiPg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWlkci1i Z3Atcm91dGUtcmVmcmVzaC1vcHRpb25zLTAwLnR4dDwvYT48YnI+DQpUbzogUm9iZXJ0IFJhc3p1 ayAmbHQ7PGEgaHJlZj0ibWFpbHRvOnJvYmVydEByYXN6dWsubmV0Ij5yb2JlcnRAcmFzenVrLm5l dDwvYT4mZ3Q7PGJyPg0KQ2M6IGlkciB3ZyAmbHQ7PGEgaHJlZj0ibWFpbHRvOmlkckBpZXRmLm9y ZyI+aWRyQGlldGYub3JnPC9hPiZndDs8YnI+DQo8YnI+DQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+ DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5i c3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBs YW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNz PSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj5PbiBNb24sIEp1bCAxMSwgMjAxNiBhdCAx OjQ3IFBNLCBSb2JlcnQgUmFzenVrICZsdDs8YSBocmVmPSJtYWlsdG86cm9iZXJ0QHJhc3p1ay5u ZXQiIHRhcmdldD0iX2JsYW5rIj5yb2JlcnRAcmFzenVrLm5ldDwvYT4mZ3Q7IHdyb3RlOjxvOnA+ PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw YW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVv dDtzYW5zLXNlcmlmJnF1b3Q7Ij5IaSBUb255LDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2 Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMi PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN c29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj5IZXkgUm9iZXJ0LCB0aGFua3MgZm9yIGNoaW1p bmcgaW4uIEdvb2QgcXVlc3Rpb25zLiBJIHNwZWFrIGhlcmUgZm9yIG15c2VsZiwgb3RoZXIgYXV0 aG9ycyBvZiB0aGUgZHJhZnQgbWF5IGhhdmUgZGlmZmVyaW5nIG9waW5pb25zLiZuYnNwOzxvOnA+ PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz cGFuIGxhbmc9IkVOLVVTIj4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxi bG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEu MHB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJp Z2h0OjBjbSI+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9 IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1z ZXJpZiZxdW90OyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWls eTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5DYW4geW91IGNsYXJp Znkgd2hhdCBpcyB0aGUgZXhwZWN0ZWQgYmVoYXZpb3VyIGFzIGZhciBhcyBwZXIgcGVlciBmaWx0 ZXItbGlzdCB3aGVuIHlvdSBuZWdvdGlhdGUgYm90aCBSZWZyZXNoIHdpdGggb3B0aW9ucywgT1JG IGFuZCBSVEMgPyBOb3RlIHRoYXQgT1JGIGFsc28gaW5jbHVkZXMgcmVjZW50IGV4dGVuc2lvbg0K IGFzIGRlc2NyaWJlZCBpbiBSRkM3NTQzIC0gd291bGQgYWxsIG9mIHRob3NlIGJlIGFsd2F5cyBh IGxvZ2ljYWwgQU5EIHRvd2FyZHMgYSBwZWVyIHdoaWNoIHB1c2hlZCB0aG9zZSA/Jm5ic3A7PG86 cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxkaXY+ DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286 cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g bGFuZz0iRU4tVVMiPldlIGRpZG4ndCBkaXNjdXNzIHRoYXQgb25lIHRocm91Z2ggYnV0IHRoZSBv bmx5IGxvZ2ljYWwgY29uY2x1c2lvbiBmb3IgbWUgaXMgdGhhdCB0aGUgT1JGL0NQLU9SRiBpbnN0 YWxsZWQgYXJlIHJlc3BlY3RlZCAoaS5lLiBpdCdzIGFuIGltcGxpY2l0IEFORCkuIEkgc2VlIE9S RiBhcyBzdGF0ZWZ1bGwsIHJlbW90ZS1wdXNoZWQgcG9saWN5IG9uIHRoZSBwZWVyIHRoYXQgaXMg bm90DQogYmVpbmcgZmxpcHBlZCBhcm91bmQgYWxsIHRoZSB0aW1lIChhbGJlaXQgQUZBSVIgdGhl cmUgd2VyZSBzb21lIGF0dGVtcHRzIEAgbm9uLXBlcnNpc3RlbnQsIG9uZSBzaG90IE9SRiBidXQg dGhhdCBlbmRlZCB1cCBleHBpcmluZz8pPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9 Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2Zv bnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xv cjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y bWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1p bHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5 N0QiPltKaWVdIEkgdGhpbmsgdGhlIGF0dGVtcHRzIHlvdSBtZW50aW9uZWQgaGVyZSBhcmUgdGhl IG9uZS10aW1lIE9SRiBkcmFmdHM6IGRyYWZ0LXplbmctaWRyLW9uZS10aW1lLXByZWZpeC1vcmYg Jm5ic3A7YW5kIGRyYWZ0LWRvbmctaWRyLW9uZS10aW1lLWV4dC1jb21tdW5pdHktb3JmLg0KIEFm dGVyIHNldmVyYWwgcmV2aXNpb25zLCB0aGVzZSBkcmFmdHMgZ290IGV4cGlyZWQgZHVlIHRvIGxh Y2sgb2YgcmVxdWlyZW1lbnRzIGF0IHRoYXQgdGltZS4gSWYgcGVvcGxlIGZvdW5kIHNvbWUgbmV3 IHVzZSBjYXNlcyBvZiB0aGVzZSBraW5kcyBvZiBtZWNoYW5pc21zLCB0aGUgYXV0aG9ycyB3b3Vs ZCBiZSBoYXBweSB0byBicmluZyB0aGVtIGJhY2sgdG8gZGlzY3Vzc2lvbi48bzpwPjwvbzpwPjwv c3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5n PSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPlRoZSBtb3RpdmF0aW9uIGZvciB0 aGlzIHdvcmsgd2VyZSBzY2VuYXJpb3Mgd2hlcmUgYSBzaW5nbGUtc2hvdCByZWZyZXNoIGlzIG5l ZWRlZCwgYWN0dWFsbHkgY29uY3VycmVudCBidW5jaCBvZiB0aG9zZSBiYXNlZCBvbiBjb25maWd1 cmF0aW9uIGNoYW5nZXMsIHBlZXIgaGF2aW5nIGRyb3BwZWQgcmVjZWl2ZWQgcm91dGVzIGJhc2Vk IG9uIHNwZWNzIChBLUQpLCBpbiBwb2xpY3kNCiBjaGFuZ2VzLCBqb2luaW5nIFZQTnMsIEVWSXMg YW5kIHNvIG9uLiBQdXR0aW5nIE9SRiBvbiBhIHBlZXIsIHJlZnJlc2ggYW5kIHJlbW92ZSBPUkZz IGlzIHNpZ25pZmljYW50bHkgaGVhdmllciBwcm9jZXNzIHRoYXQgbWF5IGludGVyZmVyZSBvbiB0 b3Agd2l0aCBub3JtYWwgdXBkYXRlIHByb2Nlc3MgZ29pbmcgb24gYW5kIG5lZWRzIHRvIGJlIGRv bmUgb25lLWJ5LW9uZSAoc2luY2UgeW91IGhhdmUgdG8gd2FpdCBmb3Igc2luZ2xlIEJvUlIvRW9S Ug0KIHBhaXIpIHVubGVzcyBvbmUgaXMgdmVyeSBzbWFydCBhYm91dCBjb21iaW5pbmcgT1JGIHBv c3NpYmx5ICZhbXA7IHBsYXlpbmcgd2l0aCB0aGUgREVGRVIvSU1NRURJQVRFcy4gQXMgd2UgaW5k aWNhdGVkLCBpZiB0aGUgQUZJL1NBRkkgaXMgY292ZXJlZCBieSBSVEMgYW5kIFJUQyBpcyBzdXBw b3J0ZWQgJmFtcDsgb25lIGlzIHdpbGxpbmcgdG8gY29uZmlndXJlIFJUcyBmb3IgZWFjaCBzdWJz ZXQgb2Ygcm91dGVzIHRoYXQgbWF5IG5lZWQgcmVmcmVzaGluZywgUlQNCiB3aWxsIGJlIGRvaW5n IHRoZSBzYW1lIGpvYiBqdXN0IGZpbmUuJm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAu NXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90 Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i TXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9u dC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9y OiMxRjQ5N0QiPltKaWVdIFRoZSBtb3RpdmF0aW9ucyBsb29rIHNpbWlsYXIgdG8gd2hhdCB3ZSBk ZXNjcmliZWQgZm9yIHRoZSBvbmUtdGltZSBPUkYgZHJhZnRzLjxvOnA+PC9vOnA+PC9zcGFuPjwv cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVT Ij4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxl PSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGNt IDBjbSAwY20gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBjbSI+DQo8ZGl2 Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0i Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PG86 cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v cm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZx dW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5Xb3VsZCB5b3UgYWx3YXlzIGNhcnJ5IE9SRiB3 aXRoIHNlcGFyYXRlIFJlZnJlc2hfSUQgdmFsdWUgPyZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwv cD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v cm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwv ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj5ZZXMs IFJlZnJlc2gtSUQjIGlzIHN0cmljdGx5IG1vbm90b25pYyBzbyB0aGVyZSBpcyBuZXZlciBhIG1p c3VuZGVyc3RhbmRpbmcgV0hBVCB0aGUgQm9SUiBiZWxvbmdzIHRvLiBPYnNlcnZlIHRoYXQgdGhl IGRyYWZ0IGRvZXMgTk9UIG1hbmRhdGUgdGhhdCBhIHJlcXVlc3QgTVVTVCBiZSBmb2xsb3dlZCBi eSBhY2NvcmRpbmcgQm9SUiwgb25seSB0aGF0IEJvUlJzIG11c3QgZm9sbG93DQogc2FtZSBzZXF1 ZW5jZSBhcyByZXF1ZXN0cyAoaS5lLiBhcmUgYWxzbyBzdHJpY3RseSBtb25vdG9uaWMpLiBIb3dl dmVyLCB3ZSBzaG91bGQgcHJvYmFibHkgc3BlY2lmeSB0aGF0IG9wdGlvbnMgX2FuZF8gT1JGIGNh biBOT1QgYmUgbWl4ZWQgaW4gdGhlIHNhbWUgdHlwZSAjMyBtZXNzYWdlIGJ1dCBpdCdzIGVpdGhl ciBvbmUgb3IgdGhlIG90aGVyIChhbmQgYW55dGhpbmcgZWxzZSBpcyBlcnJvcikuIFRoaXMgd2ls bCBhbGxvdyBPUkYgb3BlcmF0aW9ucw0KIGxpa2UgdG9kYXkgJiM0MzsgYmVuZWZpdCBvZiB0aGUg UmVmcmVzaCBJRCMgJm5ic3A7b24gdGhlIEJvUlIgc28gdGhlIElNTUVESUFURSBjYW4gZ28gb24g QCB0aGUgc2FtZSB0aW1lIGFzIGFub3RoZXIgcmVxdWVzdCB3aXRoIGhpZ2hlciBSZWZyZXNoIElE IyAoZGUgZmFjdG8gd2UgYWxsb3cgbXVsdGlwbGUgcGFyYWxsZWwgcmVmcmVzaGVzIGFzIHlvdSBz ZWUpLiZuYnNwOyBJbiBjYXNlIG9mIERFRkVSIHRoZXJlIHdpbGwgYmUgc2ltcGx5IG5vIEJvUlIg Zm9yIGl0LiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs YXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bh bj48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVm dDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNi4wcHQ7bWFyZ2luLWxl ZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBjbSI+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O b3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwm cXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMi IHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1 b3Q7Ij5JZiBvbmUgcmVxdWVzdHMgZnVsbCBBZGpfUklCX091dCBpbiB0aGUgbmV3IG1vZGVsIGFu ZCBzZW5kcyByZWZyZXNoIG1lc3NhZ2Ugd2l0aCBuZXcgcmVmcmVzaF9pZCBhbmQgbm8gb3B0aW9u cyBob3dldmVyIHRoZXJlIGFyZSBPUkYgZW50cmllcyBhbHJlYWR5IGluc3RhbGxlZCBpbiB0aGUg cGFzdCB3b3VsZA0KIGhlIGdldCBqdXN0IHRoZSBzdWJzZXQgb2Ygcm91dGVzIGFnYWluc3QgYWxs IE9SRiBlbnRyaWVzID8gSW4gb3RoZXIgd29yZHMgSSB0aGluayB0aGUgZHJhZnQgc2hvdWxkIHN0 YXRlIHRoYXQgUmVmcmVzaF9JRHMgaGF2ZSBubyBpbXBhY3QgdG8gT1JGIEFERHMgb3IgUkVNT1ZF IGFjdGlvbnMgLSBkb24ndCB5b3UgdGhpbmsgPyZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N CjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h bCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2 Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj5JIGFncmVl LiBZZXMsIE9SRiBpcyBraW5kIG9mICZuYnNwOyZxdW90O3Blcm1hbmVudCBmaWx0ZXImcXVvdDsg b24gdGhlIHBlZXIgd2hpbGUgdGhlIGludGVudCBvZiB0aGlzIGRyYWZ0IGlzIHRvIGhhdmUgYnVu Y2ggb2YgJnF1b3Q7c21hbGwgcmVmcmVzaGVzJnF1b3Q7IGdvaW5nIG9uIEAgc2FtZSB0aW1lIHBv c3NpYmx5IChpZiB5b3UgcmVxdWVzdCB0aGUgcmVmcmVzaGVzIGZyb20gYSBnb29kIGltcGxlbWVu dGF0aW9uDQogd2hpbGUgbG93LWVuZCBpbXBsZW1lbnRhdGlvbnMgbWF5IHNlcmlhbGl6ZSB0aGUg cmVxdWVzdHMgdG8gc2ltcGxpZnkgaW50ZXJuYWwgbG9naWMgOy0pLiZuYnNwOzxvOnA+PC9vOnA+ PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxh bmc9IkVOLVVTIj4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxibG9ja3F1 b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3Bh ZGRpbmc6MGNtIDBjbSAwY20gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBj bSI+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVT IiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZx dW90OyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh c3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVv dDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5BcyBmYXIgYXMgY3VycmVudCB0 eXBlcyB3aHkgbm90IGFkZCByZWd1bGFyL2V4dGVuZGVkIGNvbW11bml0eSA/PG86cD48L286cD48 L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxkaXY+DQo8cCBjbGFz cz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+ PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4t VVMiPkRpc2N1c3Npb24gY2FtZSB1cC4gRmVlbGluZyB3YXMgaXQncyBhbiBpbW1lZGlhdGUgZW5j cm9hY2ggb24gUlQgdGVycml0b3J5LiBJIGFyZ3VlZCBmb3IgaXQgOy0pICZuYnNwO1VsdGltYXRl bHksIHRha2luZyBhIG1vcmUgcmVsYXhlZCB2aWV3LCB3ZSBjaG9zZSB0byB3YWl0IGFuZCBzZWUg d2hhdCB0aGUgcmVzcG9uc2UgaXMgYW5kIG1vc3QgcHJlc3NpbmcgdXNlIGNhc2VzIHBlb3BsZQ0K IGJyaW5nIHRvIGl0IGFuZCB0aGVuIHdlIHN0YXJ0IHRvIGRlZmluZSBiaXRzIGFuZCBieXRlcyBv ZiB0aGUgb3B0aW9ucyBzdXBwb3J0ZWQsIHBvc3NpYmx5IGJvcnJvd2luZyB0byBhbiBleHRlbnQg ZnJvbSB0aGUgT1JGIHNwZWNzIDstKSAmbmJzcDtBcyBpbiAmcXVvdDttb3N0IHNpbmNlcmUgZm9y bSBvZiBmbGF0dGVyeSZxdW90OyBhbmQgc3VjaCAuLi4gOy0pJm5ic3A7PG86cD48L286cD48L3Nw YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJm b250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fu cy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+ DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6 ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlm JnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPltKaWVdIEFjdHVhbGx5IGJlZm9yZSB0aGUgb25lLXRpbWUg T1JGIGRyYWZ0cyB3ZXJlIHN1Ym1pdHRlZCwgd2UgaW5pdGlhbGx5IGNvbnNpZGVyZWQgdG8gbWFr ZSBpdCBhIOKAnHNlbGVjdGl2ZSByb3V0ZSByZWZyZXNo4oCdIG1lY2hhbmlzbS4gVGhlbiB3ZQ0K IHJlYWxpemVkIHRoYXQgdGhlIGZpbHRlcnMgd2lsbCBiZSBxdWl0ZSBzaW1pbGFyIHRvIHRoZSBv bmVzIGFscmVhZHkgZGVmaW5lZCBmb3IgT1JGLiBJbiBvcmRlciB0byByZXVzZSB0aGUgT1JGIGZp bHRlcnMsIHdlIHRoZW4gZGVjaWRlZCB0byBkZWZpbmUgdGhpcyBtZWNoYW5pc20gYXMgbmV3IOKA nG9uZS10aW1l4oCdIE9SRiB0eXBlcy4gJm5ic3A7SnVzdCB0byBwcm92aWRlIHNvbWUgYmFja2dy b3VuZCBpbmZvcm1hdGlvbiBzaW5jZSB5b3UgYWxzbyBwbGFuIHRvDQogcmV1c2UgdGhlIGZvcm1h dCBvZiB0aGUgZXhpc3RpbmcgT1JGIHR5cGVzLiA8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41 cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7 O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN c29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250 LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6 IzFGNDk3RCI+QmVzdCByZWdhcmRzLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN c29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250 LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6 IzFGNDk3RCI+SmllPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh c3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJjb2xvcjojODg4ODg4Ij48 bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv Tm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9yOiM4ODg4ODgiPi0tIHRvbnkm bmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv Tm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9yOiM4ODg4ODgiPiZuYnNwOzxv OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9k aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+PGJyPg0KPGJyIGNs ZWFyPSJhbGwiPg0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O b3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8 L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj4tLSA8bzpwPjwv bzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs Ij48aT48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZTo5LjVwdDtmb250LWZhbWls eTomcXVvdDtHZW9yZ2lhJnF1b3Q7LCZxdW90O3NlcmlmJnF1b3Q7Ij5XZeKAmXZlIGhlYXJkIHRo YXQgYSBtaWxsaW9uIG1vbmtleXMgYXQgYSBtaWxsaW9uIGtleWJvYXJkcyBjb3VsZCBwcm9kdWNl IHRoZSBjb21wbGV0ZSB3b3JrcyBvZiBTaGFrZXNwZWFyZTsgbm93LCB0aGFua3MgdG8gdGhlIElu dGVybmV0LCB3ZSBrbm93IHRoYXQgaXMgbm90IHRydWUuPC9zcGFuPjwvaT48c3BhbiBsYW5nPSJF Ti1VUyI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z b05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6OS41cHQ7Zm9udC1m YW1pbHk6JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7LCZxdW90O3NlcmlmJnF1b3Q7Ij7igJRS b2JlcnQgV2lsZW5za3k8L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+PC9vOnA+PC9zcGFu PjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwv Ym9keT4NCjwvaHRtbD4NCg== --_000_76CD132C3ADEF848BD84D028D243C92774EEF7CFNKGEML515MBXchi_-- From nobody Tue Jul 19 14:52:23 2016 Return-Path: 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 23D7D12B025 for ; Tue, 19 Jul 2016 14:52:21 -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 k4sI4BHSqCCa for ; Tue, 19 Jul 2016 14:52:18 -0700 (PDT) Received: from mail-qk0-x22a.google.com (mail-qk0-x22a.google.com [IPv6:2607:f8b0:400d:c09::22a]) (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 EA09612D5AE for ; Tue, 19 Jul 2016 14:52:17 -0700 (PDT) Received: by mail-qk0-x22a.google.com with SMTP id x1so28919125qkb.3 for ; Tue, 19 Jul 2016 14:52:17 -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=SIGnszavm1LIbp6MMNvz5TbjFLJdR3Qfj+MWE8NcOKQ=; b=uzolku07owCf5m6UIyFz/SmsDeabHlwg6kznpzvIkoWtoM1YdQpsZ6lsrUw3hcNE+V PzvwB4OWu0R5I0HcHbE5eqJS0eBd2gXA6/rLShxHGIcJfw5doWNQFAAWtPgmNLxtDxzc 0h49YiA0XlYu1M6EmyF0caXLjCkLCcs5wLKQ5lU7wmuSsngaNo2qADOFvhPQFPYj9qna v8o9lcTJaK7BskDaghRVi9Al+raMUhcr8PabM+/UZE74Z+ixmXGb1/nGKFpXrn8PkRGf xNUaYoWhjlibz3Lj5TR/LhL+IRHVfLqHZGjV2CO1dDuOtd1T8W/sjQFZKA1GEsaDRXro 0WRQ== 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=SIGnszavm1LIbp6MMNvz5TbjFLJdR3Qfj+MWE8NcOKQ=; b=ZHbvswAAF7OB/YfL8ES/1mVNQ5pfZroynbB8E1gHvJrFns2Eo49LTEJwHVFjrF/hzx ZzT1m5UwdgWLL8M/q/odgs8mSfDGRaui2jQhkHIy5mziw/Ovy+KrqwZ/YU+l9MIQfEXO DHBqdmh+jA+HepySBCVJ/5IYzT2FbymETEpzkn/QLzVw+n/2SbJYyy7K84nPKUiYKr3c O68kssLkcxv+QMl5jEw20gsWkjcIHy1HXxjJg4WBGEeLho7PKv0/F0x3EXfe6RStaVES 4qYfwSDpC6tqttPjG1nAy0MMVoap7YvglNf2QAFAYo30HbNWCrrjAX1KyoXtVFedrkvY czdQ== X-Gm-Message-State: ALyK8tKGgescyRv/Nh4pYEmrvGjFzF9WBiRmN4iefXliZtI2qEylsPpxLbW0myNbzK7HZHyrlbASMBw/gXynqQ== X-Received: by 10.55.71.6 with SMTP id u6mr56824824qka.188.1468965137069; Tue, 19 Jul 2016 14:52:17 -0700 (PDT) MIME-Version: 1.0 Sender: rraszuk@gmail.com Received: by 10.237.36.90 with HTTP; Tue, 19 Jul 2016 14:52:16 -0700 (PDT) In-Reply-To: <76CD132C3ADEF848BD84D028D243C92774EEF7CF@NKGEML515-MBX.china.huawei.com> References: <76CD132C3ADEF848BD84D028D243C92774EEF7CF@NKGEML515-MBX.china.huawei.com> From: Robert Raszuk Date: Tue, 19 Jul 2016 23:52:16 +0200 X-Google-Sender-Auth: OCRZUDjQ5-5lffW2qORkkvErMfQ Message-ID: To: "Dongjie (Jimmy)" Content-Type: multipart/alternative; boundary=001a114a72ae2ec394053804193b Archived-At: Cc: idr wg Subject: Re: [Idr] Fwd: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jul 2016 21:52:21 -0000 --001a114a72ae2ec394053804193b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Jie, To me what is perhaps missing is just a new draft to define *Route Type* ORF to address some of those EVPN new NLRI encodings. I am not that much convinced if one time ORF is needed as you are free to INSTALL and REMOVE ORF effectively producing one time behavior. Also existing Enhanced Route Refresh should work with ORF too. Many thx, R. On Tue, Jul 19, 2016 at 11:47 PM, Dongjie (Jimmy) wrote: > Hi Tony, > > > > Please see some comments inline with [Jie]: > > > > *From:* Idr [mailto:idr-bounces@ietf.org] *On Behalf Of *Tony Przygienda > *Sent:* Tuesday, July 19, 2016 6:04 PM > *To:* Robert Raszuk; idr wg > *Subject:* [Idr] Fwd: Slot request in IDR to present > https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-= 00.txt > > > > Resending ... > > > > ---------- Forwarded message ---------- > From: *Tony Przygienda* > Date: Mon, Jul 11, 2016 at 3:04 PM > Subject: Re: [Idr] Slot request in IDR to present > https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-= 00.txt > To: Robert Raszuk > Cc: idr wg > > > > > > On Mon, Jul 11, 2016 at 1:47 PM, Robert Raszuk wrote: > > Hi Tony, > > > > Hey Robert, thanks for chiming in. Good questions. I speak here for > myself, other authors of the draft may have differing opinions. > > > > > > 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 ? > > > > We didn't discuss that one through but the only logical conclusion for me > is that the ORF/CP-ORF installed are respected (i.e. it's an implicit AND= ). > I see ORF as statefull, remote-pushed policy on the peer that is not bein= g > flipped around all the time (albeit AFAIR there were some attempts @ > non-persistent, one shot ORF but that ended up expiring?) > > > > [Jie] I think the attempts you mentioned here are the one-time ORF drafts= : > draft-zeng-idr-one-time-prefix-orf and > draft-dong-idr-one-time-ext-community-orf. After several revisions, these > drafts got expired due to lack of requirements at that time. If people > found some new use cases of these kinds of mechanisms, the authors would = be > happy to bring them back to discussion. > > > > The motivation for this work were scenarios where a single-shot refresh i= s > needed, actually concurrent bunch of those based on configuration changes= , > peer having dropped received routes based on specs (A-D), in policy > changes, joining VPNs, EVIs and so on. Putting ORF on a peer, refresh and > remove ORFs is significantly heavier process that may interfere on top wi= th > normal update process going on and needs to be done one-by-one (since you > have to wait for single BoRR/EoRR pair) unless one is very smart about > combining ORF possibly & playing with the DEFER/IMMEDIATEs. As we > indicated, if the AFI/SAFI is covered by RTC and RTC is supported & one i= s > willing to configure RTs for each subset of routes that may need > refreshing, RT will be doing the same job just fine. > > > > [Jie] The motivations look similar to what we described for the one-time > ORF drafts. > > > > > > Would you always carry ORF with separate Refresh_ID value ? > > > > Yes, Refresh-ID# is strictly monotonic so there is never a > misunderstanding WHAT the BoRR belongs to. Observe that the draft does NO= T > mandate that a request MUST be followed by according BoRR, only that BoRR= s > must follow same sequence as requests (i.e. are also strictly monotonic). > However, we should probably specify that options _and_ ORF can NOT be mix= ed > in the same type #3 message but it's either one or the other (and anythin= g > else is error). This will allow ORF operations like today + benefit of th= e > Refresh ID# on the BoRR so the IMMEDIATE can go on @ the same time as > another request with higher Refresh ID# (de facto we allow multiple > parallel refreshes as you see). In case of DEFER there will be simply no > BoRR for it. > > > > > > 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 ? > > > > I agree. Yes, ORF is kind of "permanent filter" on the peer while the > intent of this draft is to have bunch of "small refreshes" going on @ sam= e > time possibly (if you request the refreshes from a good implementation > while low-end implementations may serialize the requests to simplify > internal logic ;-). > > > > > > As far as current types why not add regular/extended community ? > > > > Discussion came up. Feeling was it's an immediate encroach on RT > territory. I argued for it ;-) Ultimately, taking a more relaxed view, w= e > chose to wait and see what the response is and most pressing use cases > people bring to it and then we start to define bits and bytes of the > options supported, possibly borrowing to an extent from the ORF specs ;-) > As in "most sincere form of flattery" and such ... ;-) > > > > [Jie] Actually before the one-time ORF drafts were submitted, we initiall= y > considered to make it a =E2=80=9Cselective route refresh=E2=80=9D mechani= sm. Then we > realized that the filters will be quite similar to the ones already defin= ed > for ORF. In order to reuse the ORF filters, we then decided to define thi= s > mechanism as new =E2=80=9Cone-time=E2=80=9D ORF types. Just to provide s= ome background > information since you also plan to reuse the format of the existing ORF > types. > > > > Best regards, > > Jie > > > > -- tony > > > > > > > > -- > > *We=E2=80=99ve heard that a million monkeys at a million keyboards could = produce > the complete works of Shakespeare; now, thanks to the Internet, we know > that is not true.* > > =E2=80=94Robert Wilensky > --001a114a72ae2ec394053804193b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Jie,

To me what is perhaps missing is just a new draft to = define *Route Type* ORF to address some of those EVPN new NLRI encodings.

I am not that much conv= inced if one time ORF is needed as you are free to INSTALL and REMOVE ORF e= ffectively producing one time behavior. Also existing Enhanced Route Refres= h should work with ORF too.=C2=A0

Many thx,
R.
=



On Tue, Jul 19, = 2016 at 11:47 PM, Dongjie (Jimmy) <jie.dong@huawei.com> wr= ote:

Hi Tony,

=C2= =A0

Please see= some comments inline with [Jie]:

=C2= =A0

From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Tony Przygienda
Sent: Tuesday, July 19, 2016 6:04 PM
To: Robert Raszuk; idr wg
Subject: [Idr] Fwd: Slot request in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-= refresh-options-00.txt

=C2=A0

Resending ...=C2=A0

=C2=A0

= ---------- Forwarded message ----------
From: Tony Przygienda <tonysietf@gmail.com>
Date: Mon, Jul 11, 2016 at 3:04 PM
Subject: Re: [Idr] Slot request in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00= .txt
To: Robert Raszuk <robert@raszuk.net>
Cc: idr wg <idr@ietf.o= rg>

=C2=A0

=C2=A0

On Mon, Jul 11, 2016 at 1:47 PM= , Robert Raszuk <= robert@raszuk.net> wrote:

Hi Tony,

=C2=A0

Hey Robert, thanks for chiming = in. Good questions. I speak here for myself, other authors of the draft may= have differing opinions.=C2=A0

=C2=A0

=C2=A0

Can you clarify what is the expected behavi= our as far as per peer filter-list when you negotiate both Refresh with opt= ions, ORF and RTC ? Note that ORF also includes recent extension as described in RFC7543 - would all of those be always a logical AND towar= ds a peer which pushed those ?=C2=A0

=C2=A0

We didn't discuss that one = through but the only logical conclusion for me is that the ORF/CP-ORF insta= lled are respected (i.e. it's an implicit AND). I see ORF as statefull,= remote-pushed policy on the peer that is not being flipped around all the time (albeit AFAIR there were some attempts @= non-persistent, one shot ORF but that ended up expiring?)

=C2= =A0

[Ji= e] I think the attempts you mentioned here are the one-time ORF drafts: dra= ft-zeng-idr-one-time-prefix-orf =C2=A0and draft-dong-idr-one-time-ext-commu= nity-orf. After several revisions, these drafts got expired due to lack of requireme= nts at that time. If people found some new use cases of these kinds of mech= anisms, the authors would be happy to bring them back to discussion.=

=C2=A0

The motivation for this work we= re scenarios where a single-shot refresh is needed, actually concurrent bun= ch of those based on configuration changes, peer having dropped received ro= utes based on specs (A-D), in policy changes, joining VPNs, EVIs and so on. Putting ORF on a peer, refresh and = remove ORFs is significantly heavier process that may interfere on top with= normal update process going on and needs to be done one-by-one (since you = have to wait for single BoRR/EoRR pair) unless one is very smart about combining ORF possibly & playing = with the DEFER/IMMEDIATEs. As we indicated, if the AFI/SAFI is covered by R= TC and RTC is supported & one is willing to configure RTs for each subs= et of routes that may need refreshing, RT will be doing the same job just fine.=C2=A0

=C2= =A0

[Ji= e] The motivations look similar to what we described for the one-time ORF d= rafts.

=C2=A0

=C2=A0

Would you always carry ORF with separate Re= fresh_ID value ?=C2=A0

=C2=A0

Yes, Refresh-ID# is strictly mo= notonic so there is never a misunderstanding WHAT the BoRR belongs to. Obse= rve that the draft does NOT mandate that a request MUST be followed by acco= rding BoRR, only that BoRRs must follow same sequence as requests (i.e. are also strictly monotonic). However, we = should probably specify that options _and_ ORF can NOT be mixed in the same= type #3 message but it's either one or the other (and anything else is= error). This will allow ORF operations like today + benefit of the Refresh ID# =C2=A0on the BoRR so the IMMEDIATE= can go on @ the same time as another request with higher Refresh ID# (de f= acto we allow multiple parallel refreshes as you see).=C2=A0 In case of DEF= ER there will be simply no BoRR for it.=C2=A0

=C2=A0

=C2=A0

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 ?=C2=A0

=C2=A0

I agree. Yes, ORF is kind of = =C2=A0"permanent filter" on the peer while the intent of this dra= ft is to have bunch of "small refreshes" going on @ same time pos= sibly (if you request the refreshes from a good implementation while low-end implementations may serialize the requests to simplify inter= nal logic ;-).=C2=A0

=C2=A0

=C2=A0

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

=C2=A0

Discussion came up. Feeling was= it's an immediate encroach on RT territory. I argued for it ;-) =C2=A0= Ultimately, taking a more relaxed view, we chose to wait and see what the r= esponse is and most pressing use cases people bring to it and then we start to define bits and bytes of the options supp= orted, possibly borrowing to an extent from the ORF specs ;-) =C2=A0As in &= quot;most sincere form of flattery" and such ... ;-)=C2=A0

=C2= =A0

[Ji= e] Actually before the one-time ORF drafts were submitted, we initially con= sidered to make it a =E2=80=9Cselective route refresh=E2=80=9D mechanism. T= hen we realized that the filters will be quite similar to the ones already define= d for ORF. In order to reuse the ORF filters, we then decided to define thi= s mechanism as new =E2=80=9Cone-time=E2=80=9D ORF types.=C2=A0 Just to prov= ide some background information since you also plan to reuse the format of the existing ORF types.

=C2= =A0

Best regar= ds,

Jie=

= =C2=A0

-- tony= =C2=A0

=C2=A0<= u>



=C2=A0

--

We=E2=80=99ve heard that a = million monkeys at a million keyboards could produce the complete works of = Shakespeare; now, thanks to the Internet, we know that is not true.<= /i>

=E2=80=94Robert Wilens= ky


--001a114a72ae2ec394053804193b-- From nobody Tue Jul 19 15:18:34 2016 Return-Path: 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 661B912B025 for ; Tue, 19 Jul 2016 15:18:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -15.807 X-Spam-Level: X-Spam-Status: No, score=-15.807 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 c0qcsihIydya for ; Tue, 19 Jul 2016 15:18:28 -0700 (PDT) Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0812012D0A6 for ; Tue, 19 Jul 2016 15:18:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=26307; q=dns/txt; s=iport; t=1468966707; x=1470176307; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Z4O0nRl83z/xMRmSQOU4CLnWYiwwKpilEg5ez3fA6Uo=; b=jxnOAoBCdlrUHaEqNdrI2Jo9EgoKffbmp9h1pOyQJ7XdLs8lR/n7ojjF tKK14ko/ug+9QlNisnSO4hLVL0V2m+Lq5j32kGw1H/VJfUrNRVpkI3b1m 79TpyGVVo8EJZc0PDfFZ2OjcStfA5BHbC8Kt7pEodkKFJldBrXhRwwq/B 8=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ARAgAepo5X/4oNJK1dgnFOVnwGrE6MG?= =?us-ascii?q?oF6JIV2AoEzOBQBAQEBAQEBZSeEXAEBBXMGEAIBCBEDAQEBIQMEByERFAkIAgQ?= =?us-ascii?q?BDQUUB4d7AxcOuGwNhAgBAQEBAQEBAQEBAQEBAQEBAQEBAQEXBYYqhE2BIoEhg?= =?us-ascii?q?h0WhSUFiBcIhiV7iTE0AYkNgzaCHoFrhFmIc4ZfgUaHeAEeNoIIHxeBNW4BhyV?= =?us-ascii?q?/AQEB?= X-IronPort-AV: E=Sophos;i="5.28,391,1464652800"; d="scan'208,217";a="125913431" Received: from alln-core-5.cisco.com ([173.36.13.138]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 19 Jul 2016 22:18:26 +0000 Received: from XCH-RTP-019.cisco.com (xch-rtp-019.cisco.com [64.101.220.159]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id u6JMIPsI020143 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 19 Jul 2016 22:18:26 GMT Received: from xch-rtp-017.cisco.com (64.101.220.157) by XCH-RTP-019.cisco.com (64.101.220.159) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 19 Jul 2016 18:18:24 -0400 Received: from xch-rtp-017.cisco.com ([64.101.220.157]) by XCH-RTP-017.cisco.com ([64.101.220.157]) with mapi id 15.00.1210.000; Tue, 19 Jul 2016 18:18:25 -0400 From: "Keyur Patel (keyupate)" To: Robert Raszuk , "Dongjie (Jimmy)" Thread-Topic: [Idr] Fwd: Slot request in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00.txt Thread-Index: AQHR4gt3jXzNsYcN6ECcWcNExZ/YjA== Date: Tue, 19 Jul 2016 22:18:24 +0000 Message-ID: References: <76CD132C3ADEF848BD84D028D243C92774EEF7CF@NKGEML515-MBX.china.huawei.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.4.9.150325 x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.154.162.233] Content-Type: multipart/alternative; boundary="_000_D3B3F3D947283keyupateciscocom_" MIME-Version: 1.0 Archived-At: Cc: idr wg Subject: Re: [Idr] Fwd: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jul 2016 22:18:31 -0000 --_000_D3B3F3D947283keyupateciscocom_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Robert, Dongjie, Comments inlined #Keyur From: Robert Raszuk > Date: Tuesday, July 19, 2016 at 2:52 PM To: "Dongjie (Jimmy)" > Cc: idr wg > Subject: Re: [Idr] Fwd: Slot request in IDR to present https://www.ietf.org= /internet-drafts/draft-idr-bgp-route-refresh-options-00.txt Hi Jie, To me what is perhaps missing is just a new draft to define *Route Type* OR= F to address some of those EVPN new NLRI encodings. #Keyur: ORFs are permanent filters. We wanted to decouple the transaction b= ased filters (one time per refresh) from the permanent filters and hence ch= ose to modify refresh message as opposed to an ORF. I am not that much convinced if one time ORF is needed as you are free to I= NSTALL and REMOVE ORF effectively producing one time behavior. #Keyur: Ack. Also existing Enhanced Route Refresh should work with ORF too. #Keyur: There are modifications needed if the refresh is going to be for se= lective prefixes only. Furthermore, if we want to support multiple concurre= nt selective refreshes then the changes needed are very much along the line= s of the solution suggested in the draft. Regards, Keyur Many thx, R. On Tue, Jul 19, 2016 at 11:47 PM, Dongjie (Jimmy) > wrote: Hi Tony, Please see some comments inline with [Jie]: From: Idr [mailto:idr-bounces@ietf.org] On Beh= alf Of Tony Przygienda Sent: Tuesday, July 19, 2016 6:04 PM To: Robert Raszuk; idr wg Subject: [Idr] Fwd: Slot request in IDR to present https://www.ietf.org/int= ernet-drafts/draft-idr-bgp-route-refresh-options-00.txt Resending ... ---------- Forwarded message ---------- From: Tony Przygienda > Date: Mon, Jul 11, 2016 at 3:04 PM Subject: Re: [Idr] Slot request in IDR to present https://www.ietf.org/inte= rnet-drafts/draft-idr-bgp-route-refresh-options-00.txt To: Robert Raszuk > Cc: idr wg > On Mon, Jul 11, 2016 at 1:47 PM, Robert Raszuk > wrote: Hi Tony, Hey Robert, thanks for chiming in. Good questions. I speak here for myself,= other authors of the draft may have differing opinions. Can you clarify what is the expected behaviour as far as per peer filter-li= st when you negotiate both Refresh with options, ORF and RTC ? Note that OR= F also includes recent extension as described in RFC7543 - would all of tho= se be always a logical AND towards a peer which pushed those ? We didn't discuss that one through but the only logical conclusion for me i= s that the ORF/CP-ORF installed are respected (i.e. it's an implicit AND). = I see ORF as statefull, remote-pushed policy on the peer that is not being = flipped around all the time (albeit AFAIR there were some attempts @ non-pe= rsistent, one shot ORF but that ended up expiring?) [Jie] I think the attempts you mentioned here are the one-time ORF drafts: = draft-zeng-idr-one-time-prefix-orf and draft-dong-idr-one-time-ext-communi= ty-orf. After several revisions, these drafts got expired due to lack of re= quirements at that time. If people found some new use cases of these kinds = of mechanisms, the authors would be happy to bring them back to discussion. The motivation for this work were scenarios where a single-shot refresh is = needed, actually concurrent bunch of those based on configuration changes, = peer having dropped received routes based on specs (A-D), in policy changes= , joining VPNs, EVIs and so on. Putting ORF on a peer, refresh and remove O= RFs is significantly heavier process that may interfere on top with normal = update process going on and needs to be done one-by-one (since you have to = wait for single BoRR/EoRR pair) unless one is very smart about combining OR= F possibly & playing with the DEFER/IMMEDIATEs. As we indicated, if the AFI= /SAFI is covered by RTC and RTC is supported & one is willing to configure = RTs for each subset of routes that may need refreshing, RT will be doing th= e same job just fine. [Jie] The motivations look similar to what we described for the one-time OR= F drafts. Would you always carry ORF with separate Refresh_ID value ? Yes, Refresh-ID# is strictly monotonic so there is never a misunderstanding= WHAT the BoRR belongs to. Observe that the draft does NOT mandate that a r= equest MUST be followed by according BoRR, only that BoRRs must follow same= sequence as requests (i.e. are also strictly monotonic). However, we shoul= d probably specify that options _and_ ORF can NOT be mixed in the same type= #3 message but it's either one or the other (and anything else is error). = This will allow ORF operations like today + benefit of the Refresh ID# on = the BoRR so the IMMEDIATE can go on @ the same time as another request with= higher Refresh ID# (de facto we allow multiple parallel refreshes as you s= ee). In case of DEFER there will be simply no BoRR for it. 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 i= nstalled 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 h= ave no impact to ORF ADDs or REMOVE actions - don't you think ? I agree. Yes, ORF is kind of "permanent filter" on the peer while the inte= nt of this draft is to have bunch of "small refreshes" going on @ same time= possibly (if you request the refreshes from a good implementation while lo= w-end implementations may serialize the requests to simplify internal logic= ;-). As far as current types why not add regular/extended community ? Discussion came up. Feeling was it's an immediate encroach on RT territory.= I argued for it ;-) Ultimately, taking a more relaxed view, we chose to w= ait and see what the response is and most pressing use cases people bring t= o it and then we start to define bits and bytes of the options supported, p= ossibly borrowing to an extent from the ORF specs ;-) As in "most sincere = form of flattery" and such ... ;-) [Jie] Actually before the one-time ORF drafts were submitted, we initially = considered to make it a "selective route refresh" mechanism. Then we realiz= ed that the filters will be quite similar to the ones already defined for O= RF. In order to reuse the ORF filters, we then decided to define this mecha= nism as new "one-time" ORF types. Just to provide some background informat= ion since you also plan to reuse the format of the existing ORF types. Best regards, Jie -- tony -- We've heard that a million monkeys at a million keyboards could produce the= complete works of Shakespeare; now, thanks to the Internet, we know that i= s not true. -Robert Wilensky --_000_D3B3F3D947283keyupateciscocom_ Content-Type: text/html; charset="iso-8859-1" Content-ID: <1F0A355623AE2C4D8D6C5A17FC493AA0@emea.cisco.com> Content-Transfer-Encoding: quoted-printable
Robert, Dongjie,

Comments inlined #Keyur

From: Robert Raszuk <robert@raszuk.net>
Date: Tuesday, July 19, 2016 at 2:5= 2 PM
To: "Dongjie (Jimmy)" <= ;jie.dong@huawei.com>
Cc: idr wg <idr@ietf.org>
Subject: Re: [Idr] Fwd: Slot reques= t in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00= .txt

Hi Jie,

To me what is perhaps missing is just a new draft to define *Route Type* OR= F to address some of those EVPN new NLRI encodings.

#Keyur: ORFs are permanent filters. We wanted to decouple the transact= ion based filters (one time per refresh) from the permanent filters and hen= ce chose to modify refresh message as opposed to an ORF. 

I am not that much convinced if one time ORF is needed as you are free to I= NSTALL and REMOVE ORF effectively producing one time behavior.

#Keyur: Ack. 

Also existing Enhanced Route Refresh should work with ORF too. 

#Keyur: There are modifications needed if the refresh is going to be f= or selective prefixes only. Furthermore, if we want to support multiple con= current selective refreshes then the changes needed are very much along the= lines of the solution suggested in the draft.

Regards,
Keyur 



Many thx,
R.




On Tue, Jul 19, 2016 at 11:47 PM, Dongjie (Jimmy= ) <jie.dong@huawe= i.com> wrote:

Hi Tony,

 

Please see some co= mments inline with [Jie]:

 

From: Idr [mailto:idr-bounces@ietf.org= ] On Behalf Of Tony Przygienda
Sent: Tuesday, July 19, 2016 6:04 PM
To: Robert Raszuk; idr wg
Subject: [Idr] Fwd: Slot request in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00= .txt

 

Resending ... 

 

= ---------- Forwarded message ----------
From: Tony Przygienda <tonysietf@gmail.com>
Date: Mon, Jul 11, 2016 at 3:04 PM
Subject: Re: [Idr] Slot request in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00= .txt
To: Robert Raszuk <robert@raszuk.net>
Cc: idr wg <idr@ietf.o= rg>

 

 

On Mon, Jul 11, 2016 at 1:47 PM= , Robert Raszuk <= robert@raszuk.net> wrote:

Hi Tony,

 

Hey Robert, thanks for chiming = in. Good questions. I speak here for myself, other authors of the draft may= have differing opinions. 

 

 

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

 

We didn't discuss that one thro= ugh but the only logical conclusion for me is that the ORF/CP-ORF installed= are respected (i.e. it's an implicit AND). I see ORF as statefull, remote-= pushed policy on the peer that is not being flipped around all the time (albeit AFAIR there were some attempts @= non-persistent, one shot ORF but that ended up expiring?)

 

[Jie] I think the = attempts you mentioned here are the one-time ORF drafts: draft-zeng-idr-one= -time-prefix-orf  and draft-dong-idr-one-time-ext-community-orf. After several revisions, these drafts got expired due to lack of requireme= nts at that time. If people found some new use cases of these kinds of mech= anisms, the authors would be happy to bring them back to discussion.=

 

The motivation for this work we= re scenarios where a single-shot refresh is needed, actually concurrent bun= ch of those based on configuration changes, peer having dropped received ro= utes based on specs (A-D), in policy changes, joining VPNs, EVIs and so on. Putting ORF on a peer, refresh and = remove ORFs is significantly heavier process that may interfere on top with= normal update process going on and needs to be done one-by-one (since you = have to wait for single BoRR/EoRR pair) unless one is very smart about combining ORF possibly & playing = with the DEFER/IMMEDIATEs. As we indicated, if the AFI/SAFI is covered by R= TC and RTC is supported & one is willing to configure RTs for each subs= et of routes that may need refreshing, RT will be doing the same job just fine. 

 

[Jie] The motivati= ons look similar to what we described for the one-time ORF drafts.

 

 

Would you always carry ORF with separate Refresh_ID value ? = ;

 

Yes, Refresh-ID# is strictly mo= notonic so there is never a misunderstanding WHAT the BoRR belongs to. Obse= rve that the draft does NOT mandate that a request MUST be followed by acco= rding BoRR, only that BoRRs must follow same sequence as requests (i.e. are also strictly monotonic). However, we = should probably specify that options _and_ ORF can NOT be mixed in the same= type #3 message but it's either one or the other (and anything else is err= or). This will allow ORF operations like today + benefit of the Refresh ID#  on the BoRR so the IMMED= IATE can go on @ the same time as another request with higher Refresh ID# (= de facto we allow multiple parallel refreshes as you see).  In case of= DEFER there will be simply no BoRR for it. 

 

 

If one requests full Adj_RIB_Out in the new model and sends refr= esh message with new refresh_id and no options however there are ORF entrie= s 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 ? 

 

I agree. Yes, ORF is kind of &n= bsp;"permanent filter" on the peer while the intent of this draft= is to have bunch of "small refreshes" going on @ same time possi= bly (if you request the refreshes from a good implementation while low-end implementations may serialize the requests to simplify inter= nal logic ;-). 

 

 

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

 

Discussion came up. Feeling was= it's an immediate encroach on RT territory. I argued for it ;-)  Ulti= mately, taking a more relaxed view, we chose to wait and see what the respo= nse is and most pressing use cases people bring to it and then we start to define bits and bytes of the options supp= orted, possibly borrowing to an extent from the ORF specs ;-)  As in &= quot;most sincere form of flattery" and such ... ;-) 

 

[Jie] Actually bef= ore the one-time ORF drafts were submitted, we initially considered to make= it a “selective route refresh” mechanism. Then we realized that the filters will be quite similar to the ones alread= y defined for ORF. In order to reuse the ORF filters, we then decided to de= fine this mechanism as new “one-time” ORF types.  Just to = provide some background information since you also plan to reuse the format of the existing ORF types. <= /p>

 

Best regards,

Jie<= /span>

=  

-- tony=  

 <= u>



 

--

We’ve heard that a million monkeys at a = million keyboards could produce the complete works of Shakespeare; now, tha= nks to the Internet, we know that is not true.

—Robert Wilensky


--_000_D3B3F3D947283keyupateciscocom_-- From nobody Tue Jul 19 15:29:52 2016 Return-Path: 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 E591D12D936 for ; Tue, 19 Jul 2016 15:29:50 -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 iIIEcCUeDxed for ; Tue, 19 Jul 2016 15:29:47 -0700 (PDT) Received: from mail-qk0-x231.google.com (mail-qk0-x231.google.com [IPv6:2607:f8b0:400d:c09::231]) (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 59C5512D1A5 for ; Tue, 19 Jul 2016 15:29:47 -0700 (PDT) Received: by mail-qk0-x231.google.com with SMTP id p74so29752700qka.0 for ; Tue, 19 Jul 2016 15:29:47 -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=LHu9teD1sAWi4/Ylve5KP3ZrWlOZ9zDMGFmP2KXLEW4=; b=TCfidarNWdeBfPuai4A03xxNQF8AldvMT13cj6gZtR1Wdw+zSS+w/RDIzO/bxOJvEn /bMdAkVs3fVA+7Q8O86FZxe+DjTbk05PjM6uF/ch7AVOiyjQBjcPLoSUq11beGm42B3F EmNam9+S+SyeZtpvStuiRcJoEAyvJZUhZ/N+xsNdwzUII/VC5UH1X99ZjvkWDfyRwQYa IqIMnUQsvsyVYd1PR6iFD2XHAFIlhp9II94x8H4AAbuOVFy7aKaovcefUyw7+vXMBFMX Qix+sHAua9FJrxFVMxj53lDDl4f066PZq2Nb7lufTpnhOzTW7Wy5cSrfqR7/F1fkqmJK WU1A== 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=LHu9teD1sAWi4/Ylve5KP3ZrWlOZ9zDMGFmP2KXLEW4=; b=PITRIfoApKi+xleeEZBP4pQdafgkPVHJAJ2sCZqthVCRSZ/YbDXgzgLz34mYgAZT1Z Sz4ll/ni86dtjkfW8qxQgFbkdOC1N4CanwnqYNg5EANy8xzsgxaVXFqfUgDZn/LjFt/1 auU4EVevjbOpIfj4S8eyv+W/NC4JQDuh+EGt8Vs9EpTGXOWhuZIpc88WVOnofVS4cUGK P5iw507Bzh+j3bZappBJuUjl8dHa9XV/fVfqCa/VC7wHzS8Ez5Z4+uMDbRE++bUl7Fgu Gs55KUhZrNpXUlP770fjJStqCbOp60sgzD0Xw4BIBjUco4/VdFqxDnsZLWBeNz8tElpX 2KKg== X-Gm-Message-State: ALyK8tKITtevD8HhWaVDfUh3zZRWSLDcis29shhit5RIuiuYLm9AludN+pZDv85tbj0ubIjntBvd/vsOZZr3ng== X-Received: by 10.55.16.27 with SMTP id a27mr57547385qkh.34.1468967386361; Tue, 19 Jul 2016 15:29:46 -0700 (PDT) MIME-Version: 1.0 Sender: rraszuk@gmail.com Received: by 10.237.36.90 with HTTP; Tue, 19 Jul 2016 15:29:45 -0700 (PDT) In-Reply-To: References: <76CD132C3ADEF848BD84D028D243C92774EEF7CF@NKGEML515-MBX.china.huawei.com> From: Robert Raszuk Date: Wed, 20 Jul 2016 00:29:45 +0200 X-Google-Sender-Auth: A_xO6hde_EH8qhm6dzMfEBh_i3c Message-ID: To: "Keyur Patel (keyupate)" Content-Type: multipart/alternative; boundary=001a114763664034a30538049f82 Archived-At: Cc: idr wg Subject: Re: [Idr] Fwd: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jul 2016 22:29:51 -0000 --001a114763664034a30538049f82 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Keyur, The missing part seems to be justification if we really need "transaction based filters" as opposed to simply having permanent ones. What real problem "transaction based filters" solve ? IMO the draft needs to state it clearly. The other point is that "permanent" are not really permanent anyway .. they are installed from update to withdraw of a given filter - regardless what filtering mechanism you choose (ORF, RTC, XYZ ...). And if you go with the notion that permanent are sufficient the entire aparatus allowing you to have concurrent route refresh requests in flight goes away :) Thx, r. On Wed, Jul 20, 2016 at 12:18 AM, Keyur Patel (keyupate) wrote: > Robert, Dongjie, > > Comments inlined #Keyur > > From: Robert Raszuk > Date: Tuesday, July 19, 2016 at 2:52 PM > To: "Dongjie (Jimmy)" > Cc: idr wg > Subject: Re: [Idr] Fwd: Slot request in IDR to present > https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-= 00.txt > > Hi Jie, > > To me what is perhaps missing is just a new draft to define *Route Type* > ORF to address some of those EVPN new NLRI encodings. > > #Keyur: ORFs are permanent filters. We wanted to decouple the transaction > based filters (one time per refresh) from the permanent filters and hence > chose to modify refresh message as opposed to an ORF. > > I am not that much convinced if one time ORF is needed as you are free to > INSTALL and REMOVE ORF effectively producing one time behavior. > > #Keyur: Ack. > > Also existing Enhanced Route Refresh should work with ORF too. > > #Keyur: There are modifications needed if the refresh is going to be for > selective prefixes only. Furthermore, if we want to support multiple > concurrent selective refreshes then the changes needed are very much alon= g > the lines of the solution suggested in the draft. > > Regards, > Keyur > > > > Many thx, > R. > > > > > On Tue, Jul 19, 2016 at 11:47 PM, Dongjie (Jimmy) > wrote: > >> Hi Tony, >> >> >> >> Please see some comments inline with [Jie]: >> >> >> >> *From:* Idr [mailto:idr-bounces@ietf.org] *On Behalf Of *Tony Przygienda >> *Sent:* Tuesday, July 19, 2016 6:04 PM >> *To:* Robert Raszuk; idr wg >> *Subject:* [Idr] Fwd: Slot request in IDR to present >> https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options= -00.txt >> >> >> >> Resending ... >> >> >> >> ---------- Forwarded message ---------- >> From: *Tony Przygienda* >> Date: Mon, Jul 11, 2016 at 3:04 PM >> Subject: Re: [Idr] Slot request in IDR to present >> https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options= -00.txt >> To: Robert Raszuk >> Cc: idr wg >> >> >> >> >> >> On Mon, Jul 11, 2016 at 1:47 PM, Robert Raszuk wrote= : >> >> Hi Tony, >> >> >> >> Hey Robert, thanks for chiming in. Good questions. I speak here for >> myself, other authors of the draft may have differing opinions. >> >> >> >> >> >> 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 ? >> >> >> >> We didn't discuss that one through but the only logical conclusion for m= e >> is that the ORF/CP-ORF installed are respected (i.e. it's an implicit AN= D). >> I see ORF as statefull, remote-pushed policy on the peer that is not bei= ng >> flipped around all the time (albeit AFAIR there were some attempts @ >> non-persistent, one shot ORF but that ended up expiring?) >> >> >> >> [Jie] I think the attempts you mentioned here are the one-time ORF >> drafts: draft-zeng-idr-one-time-prefix-orf and >> draft-dong-idr-one-time-ext-community-orf. After several revisions, thes= e >> drafts got expired due to lack of requirements at that time. If people >> found some new use cases of these kinds of mechanisms, the authors would= be >> happy to bring them back to discussion. >> >> >> >> The motivation for this work were scenarios where a single-shot refresh >> is needed, actually concurrent bunch of those based on configuration >> changes, peer having dropped received routes based on specs (A-D), in >> policy changes, joining VPNs, EVIs and so on. Putting ORF on a peer, >> refresh and remove ORFs is significantly heavier process that may interf= ere >> on top with normal update process going on and needs to be done one-by-o= ne >> (since you have to wait for single BoRR/EoRR pair) unless one is very sm= art >> about combining ORF possibly & playing with the DEFER/IMMEDIATEs. As we >> indicated, if the AFI/SAFI is covered by RTC and RTC is supported & one = is >> willing to configure RTs for each subset of routes that may need >> refreshing, RT will be doing the same job just fine. >> >> >> >> [Jie] The motivations look similar to what we described for the one-time >> ORF drafts. >> >> >> >> >> >> Would you always carry ORF with separate Refresh_ID value ? >> >> >> >> Yes, Refresh-ID# is strictly monotonic so there is never a >> misunderstanding WHAT the BoRR belongs to. Observe that the draft does N= OT >> mandate that a request MUST be followed by according BoRR, only that BoR= Rs >> must follow same sequence as requests (i.e. are also strictly monotonic)= . >> However, we should probably specify that options _and_ ORF can NOT be mi= xed >> in the same type #3 message but it's either one or the other (and anythi= ng >> else is error). This will allow ORF operations like today + benefit of t= he >> Refresh ID# on the BoRR so the IMMEDIATE can go on @ the same time as >> another request with higher Refresh ID# (de facto we allow multiple >> parallel refreshes as you see). In case of DEFER there will be simply n= o >> BoRR for it. >> >> >> >> >> >> 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 yo= u >> think ? >> >> >> >> I agree. Yes, ORF is kind of "permanent filter" on the peer while the >> intent of this draft is to have bunch of "small refreshes" going on @ sa= me >> time possibly (if you request the refreshes from a good implementation >> while low-end implementations may serialize the requests to simplify >> internal logic ;-). >> >> >> >> >> >> As far as current types why not add regular/extended community ? >> >> >> >> Discussion came up. Feeling was it's an immediate encroach on RT >> territory. I argued for it ;-) Ultimately, taking a more relaxed view, = we >> chose to wait and see what the response is and most pressing use cases >> people bring to it and then we start to define bits and bytes of the >> options supported, possibly borrowing to an extent from the ORF specs ;-= ) >> As in "most sincere form of flattery" and such ... ;-) >> >> >> >> [Jie] Actually before the one-time ORF drafts were submitted, we >> initially considered to make it a =E2=80=9Cselective route refresh=E2=80= =9D mechanism. Then >> we realized that the filters will be quite similar to the ones already >> defined for ORF. In order to reuse the ORF filters, we then decided to >> define this mechanism as new =E2=80=9Cone-time=E2=80=9D ORF types. Just= to provide some >> background information since you also plan to reuse the format of the >> existing ORF types. >> >> >> >> Best regards, >> >> Jie >> >> >> >> -- tony >> >> >> >> >> >> >> >> -- >> >> *We=E2=80=99ve heard that a million monkeys at a million keyboards could= produce >> the complete works of Shakespeare; now, thanks to the Internet, we know >> that is not true.* >> >> =E2=80=94Robert Wilensky >> > > --001a114763664034a30538049f82 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Keyur,

<= /div>
The missing part seems to be justification if we re= ally need "transaction based filters" as opposed to simply having= permanent ones.=C2=A0

What real problem "transaction based filters" solve ? IMO the dr= aft needs to state it clearly.=C2=A0

The other point is that "permanent" are not really= permanent anyway .. they are installed from update to withdraw of a given = filter - regardless what filtering mechanism you choose (ORF, RTC, XYZ ...)= . And if you go with the notion that permanent are sufficient the entire ap= aratus allowing you to have concurrent route refresh requests in flight goe= s away :)

Thx,
r.


On Wed, Jul 20, 2016 at 12:18 AM= , Keyur Patel (keyupate) <keyupate@cisco.com> wrote:
Robert, Dongjie,

Comments inlined #Keyur

From: Robert Raszuk <robert@raszuk.net>
Date: Tuesday, July 19, 2016 at 2:5= 2 PM
To: "Dongjie (Jimmy)" <= ;jie.dong@huawei.c= om>
Cc: idr wg <idr@ietf.org>
Subject: Re: [Idr] Fwd: Slot reques= t in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00= .txt

Hi Jie,

To me what is perhaps missing is just a new draft to define *Route Type* OR= F to address some of those EVPN new NLRI encodings.

#Keyur: ORFs are permanent filters. We wanted to decouple the transact= ion based filters (one time per refresh) from the permanent filters and hen= ce chose to modify refresh message as opposed to an ORF.=C2=A0

I am not that much convinced if one time ORF is needed as you are free to I= NSTALL and REMOVE ORF effectively producing one time behavior.

#Keyur: Ack.=C2=A0

Also existing Enhanced Route Refresh should work with ORF too.=C2=A0

#Keyur: There are modifications needed if the refresh is going = to be for selective prefixes only. Furthermore, if we want to support multi= ple concurrent selective refreshes then the changes needed are very much al= ong the lines of the solution suggested in the draft.

Regards,
Keyur=C2=A0



Many thx,
R.




On Tue, Jul 19, 2016 at 11:47 PM, Dongjie (Jimmy= ) <jie.dong@huawe= i.com> wrote:

Hi Tony,

=C2=A0=

Please see some comments in= line with [Jie]:

=C2=A0=

From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Tony Przygienda
Sent: Tuesday, July 19, 2016 6:04 PM
To: Robert Raszuk; idr wg
Subject: [Idr] Fwd: Slot request in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00= .txt

=C2=A0

Resending ...=C2=A0

=C2=A0

= ---------- Forwarded message ----------
From: Tony Przygienda <tonysietf@gmail.com>
Date: Mon, Jul 11, 2016 at 3:04 PM
Subject: Re: [Idr] Slot request in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00= .txt
To: Robert Raszuk <robert@raszuk.net>
Cc: idr wg <idr@ietf.o= rg>

=C2=A0

=C2=A0

On Mon, Jul 11, 2016 at 1:47 PM= , Robert Raszuk <= robert@raszuk.net> wrote:

Hi Tony,

=C2=A0

Hey Robert, thanks for chiming = in. Good questions. I speak here for myself, other authors of the draft may= have differing opinions.=C2=A0

=C2=A0

=C2=A0

Can you clarify what is the expected behaviour as far as per peer f= ilter-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 towar= ds a peer which pushed those ?=C2=A0

=C2=A0

We didn't discuss that one = through but the only logical conclusion for me is that the ORF/CP-ORF insta= lled are respected (i.e. it's an implicit AND). I see ORF as statefull,= remote-pushed policy on the peer that is not being flipped around all the time (albeit AFAIR there were some attempts @= non-persistent, one shot ORF but that ended up expiring?)

=C2=A0=

[Jie] I think the attempts = you mentioned here are the one-time ORF drafts: draft-zeng-idr-one-time-pre= fix-orf =C2=A0and draft-dong-idr-one-time-ext-community-orf. After several revisions, these drafts got expired due to lack of requireme= nts at that time. If people found some new use cases of these kinds of mech= anisms, the authors would be happy to bring them back to discussion.=

=C2=A0

The motivation for this work we= re scenarios where a single-shot refresh is needed, actually concurrent bun= ch of those based on configuration changes, peer having dropped received ro= utes based on specs (A-D), in policy changes, joining VPNs, EVIs and so on. Putting ORF on a peer, refresh and = remove ORFs is significantly heavier process that may interfere on top with= normal update process going on and needs to be done one-by-one (since you = have to wait for single BoRR/EoRR pair) unless one is very smart about combining ORF possibly & playing = with the DEFER/IMMEDIATEs. As we indicated, if the AFI/SAFI is covered by R= TC and RTC is supported & one is willing to configure RTs for each subs= et of routes that may need refreshing, RT will be doing the same job just fine.=C2=A0

=C2=A0=

[Jie] The motivations look = similar to what we described for the one-time ORF drafts.

=C2=A0

=C2=A0

Would you always carry ORF with separate Refresh_ID value ?=C2=A0

=C2=A0

Yes, Refresh-ID# is strictly mo= notonic so there is never a misunderstanding WHAT the BoRR belongs to. Obse= rve that the draft does NOT mandate that a request MUST be followed by acco= rding BoRR, only that BoRRs must follow same sequence as requests (i.e. are also strictly monotonic). However, we = should probably specify that options _and_ ORF can NOT be mixed in the same= type #3 message but it's either one or the other (and anything else is= error). This will allow ORF operations like today + benefit of the Refresh ID# =C2=A0on the BoRR so the IMMEDIATE= can go on @ the same time as another request with higher Refresh ID# (de f= acto we allow multiple parallel refreshes as you see).=C2=A0 In case of DEF= ER there will be simply no BoRR for it.=C2=A0

=C2=A0

=C2=A0

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 a= lready 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 ?=C2=A0

=C2=A0

I agree. Yes, ORF is kind of = =C2=A0"permanent filter" on the peer while the intent of this dra= ft is to have bunch of "small refreshes" going on @ same time pos= sibly (if you request the refreshes from a good implementation while low-end implementations may serialize the requests to simplify inter= nal logic ;-).=C2=A0

=C2=A0

=C2=A0

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

=C2=A0

Discussion came up. Feeling was= it's an immediate encroach on RT territory. I argued for it ;-) =C2=A0= Ultimately, taking a more relaxed view, we chose to wait and see what the r= esponse is and most pressing use cases people bring to it and then we start to define bits and bytes of the options supp= orted, possibly borrowing to an extent from the ORF specs ;-) =C2=A0As in &= quot;most sincere form of flattery" and such ... ;-)=C2=A0

=C2=A0=

[Jie] Actually before the o= ne-time ORF drafts were submitted, we initially considered to make it a =E2= =80=9Cselective route refresh=E2=80=9D mechanism. Then we realized that the filters will be quite similar to the ones alread= y defined for ORF. In order to reuse the ORF filters, we then decided to de= fine this mechanism as new =E2=80=9Cone-time=E2=80=9D ORF types.=C2=A0 Just= to provide some background information since you also plan to reuse the format of the existing ORF types. <= /p>

=C2=A0=

Best regards,=

Jie

= =C2=A0

-- tony= =C2=A0

=C2=A0<= u>



=C2=A0

--

We=E2=80=99ve heard that a million monkeys at a mil= lion keyboards could produce the complete works of Shakespeare; now, thanks= to the Internet, we know that is not true.=

=E2=80=94Robert Wilensky



--001a114763664034a30538049f82-- From nobody Wed Jul 20 00:27:55 2016 Return-Path: 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 5EF6012B02A for ; Wed, 20 Jul 2016 00:27:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.507 X-Spam-Level: X-Spam-Status: No, score=-5.507 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, 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 QAtEOR5J5IWo for ; Wed, 20 Jul 2016 00:27:49 -0700 (PDT) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5369612B01A for ; Wed, 20 Jul 2016 00:27:48 -0700 (PDT) Received: from 172.18.7.190 (EHLO lhreml704-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CSW67657; Wed, 20 Jul 2016 07:27:44 +0000 (GMT) Received: from NKGEML414-HUB.china.huawei.com (10.98.56.75) by lhreml704-cah.china.huawei.com (10.201.5.130) with Microsoft SMTP Server (TLS) id 14.3.235.1; Wed, 20 Jul 2016 08:27:43 +0100 Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml414-hub.china.huawei.com ([10.98.56.75]) with mapi id 14.03.0235.001; Wed, 20 Jul 2016 15:27:37 +0800 From: "Dongjie (Jimmy)" To: Robert Raszuk Thread-Topic: [Idr] Fwd: Slot request in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00.txt Thread-Index: AQHR4aVU83cQxXd4nUuy17dJqjAuSaAgQJlw//+FoACAASOekA== Date: Wed, 20 Jul 2016 07:27:36 +0000 Message-ID: <76CD132C3ADEF848BD84D028D243C92774EEFBE8@NKGEML515-MBX.china.huawei.com> References: <76CD132C3ADEF848BD84D028D243C92774EEF7CF@NKGEML515-MBX.china.huawei.com> In-Reply-To: Accept-Language: en-US, zh-CN Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.200.218.207] Content-Type: multipart/alternative; boundary="_000_76CD132C3ADEF848BD84D028D243C92774EEFBE8NKGEML515MBXchi_" MIME-Version: 1.0 X-CFilter-Loop: Reflected X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090201.578F27F2.003C, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32 X-Mirapoint-Loop-Id: 3f24c9cc87920f73bd6b0f48beffe65d Archived-At: Cc: idr wg Subject: Re: [Idr] Fwd: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jul 2016 07:27:52 -0000 --_000_76CD132C3ADEF848BD84D028D243C92774EEFBE8NKGEML515MBXchi_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 SGkgUm9iZXJ0LA0KDQpJIGFncmVlIHRoYXQg4oCcUm91dGUgVHlwZeKAnSBiYXNlZCBmaWx0ZXJp bmcgbWF5IGJlIG5lZWRlZCBpbiBzb21lIGNhc2VzLiBEbyB5b3UgdGhpbmsgaXQgc2hvdWxkIGJl aGF2ZSBhcyBvbmUtdGltZSBmaWx0ZXIgb3IgYSBwZXJtYW5lbnQgZmlsdGVyLCBvciBtYXliZSBi b3RoIGFyZSBuZWVkZWQ/DQoNCkFzIGZvciB0aGUgb25lLXRpbWUgYmVoYXZpb3IsIElNTyBpdCBk ZXNlcnZlcyBhIGRlZGljYXRlZCBPUkYgdHlwZSAob3IgcmVmcmVzaCBvcHRpb24pLCBhcyB1c2lu ZyBjb25zZWN1dGl2ZSBtZXNzYWdlcyB0byBpbnN0YWxsIGFuZCByZW1vdmUgdGhlIE9SRiBmaWx0 ZXIgY291bGQgaW50cm9kdWNlIHVubmVjZXNzYXJ5IGNvc3QgaW4gYm90aCBtZXNzYWdlIGV4Y2hh bmdlIGFuZCB0aGUgcHJvY2Vzc2luZyBvbiB0aGUgZGV2aWNlLg0KDQpCZXN0IHJlZ2FyZHMsDQpK aWUNCg0KRnJvbTogcnJhc3p1a0BnbWFpbC5jb20gW21haWx0bzpycmFzenVrQGdtYWlsLmNvbV0g T24gQmVoYWxmIE9mIFJvYmVydCBSYXN6dWsNClNlbnQ6IFdlZG5lc2RheSwgSnVseSAyMCwgMjAx NiA1OjUyIEFNDQpUbzogRG9uZ2ppZSAoSmltbXkpDQpDYzogVG9ueSBQcnp5Z2llbmRhOyBpZHIg d2cNClN1YmplY3Q6IFJlOiBbSWRyXSBGd2Q6IFNsb3QgcmVxdWVzdCBpbiBJRFIgdG8gcHJlc2Vu dCBodHRwczovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtaWRyLWJncC1yb3V0 ZS1yZWZyZXNoLW9wdGlvbnMtMDAudHh0DQoNCkhpIEppZSwNCg0KVG8gbWUgd2hhdCBpcyBwZXJo YXBzIG1pc3NpbmcgaXMganVzdCBhIG5ldyBkcmFmdCB0byBkZWZpbmUgKlJvdXRlIFR5cGUqIE9S RiB0byBhZGRyZXNzIHNvbWUgb2YgdGhvc2UgRVZQTiBuZXcgTkxSSSBlbmNvZGluZ3MuDQoNCkkg YW0gbm90IHRoYXQgbXVjaCBjb252aW5jZWQgaWYgb25lIHRpbWUgT1JGIGlzIG5lZWRlZCBhcyB5 b3UgYXJlIGZyZWUgdG8gSU5TVEFMTCBhbmQgUkVNT1ZFIE9SRiBlZmZlY3RpdmVseSBwcm9kdWNp bmcgb25lIHRpbWUgYmVoYXZpb3IuIEFsc28gZXhpc3RpbmcgRW5oYW5jZWQgUm91dGUgUmVmcmVz aCBzaG91bGQgd29yayB3aXRoIE9SRiB0b28uDQoNCk1hbnkgdGh4LA0KUi4NCg0KDQoNCg0KT24g VHVlLCBKdWwgMTksIDIwMTYgYXQgMTE6NDcgUE0sIERvbmdqaWUgKEppbW15KSA8amllLmRvbmdA aHVhd2VpLmNvbTxtYWlsdG86amllLmRvbmdAaHVhd2VpLmNvbT4+IHdyb3RlOg0KSGkgVG9ueSwN Cg0KUGxlYXNlIHNlZSBzb21lIGNvbW1lbnRzIGlubGluZSB3aXRoIFtKaWVdOg0KDQpGcm9tOiBJ ZHIgW21haWx0bzppZHItYm91bmNlc0BpZXRmLm9yZzxtYWlsdG86aWRyLWJvdW5jZXNAaWV0Zi5v cmc+XSBPbiBCZWhhbGYgT2YgVG9ueSBQcnp5Z2llbmRhDQpTZW50OiBUdWVzZGF5LCBKdWx5IDE5 LCAyMDE2IDY6MDQgUE0NClRvOiBSb2JlcnQgUmFzenVrOyBpZHIgd2cNClN1YmplY3Q6IFtJZHJd IEZ3ZDogU2xvdCByZXF1ZXN0IGluIElEUiB0byBwcmVzZW50IGh0dHBzOi8vd3d3LmlldGYub3Jn L2ludGVybmV0LWRyYWZ0cy9kcmFmdC1pZHItYmdwLXJvdXRlLXJlZnJlc2gtb3B0aW9ucy0wMC50 eHQNCg0KUmVzZW5kaW5nIC4uLg0KDQotLS0tLS0tLS0tIEZvcndhcmRlZCBtZXNzYWdlIC0tLS0t LS0tLS0NCkZyb206IFRvbnkgUHJ6eWdpZW5kYSA8dG9ueXNpZXRmQGdtYWlsLmNvbTxtYWlsdG86 dG9ueXNpZXRmQGdtYWlsLmNvbT4+DQpEYXRlOiBNb24sIEp1bCAxMSwgMjAxNiBhdCAzOjA0IFBN DQpTdWJqZWN0OiBSZTogW0lkcl0gU2xvdCByZXF1ZXN0IGluIElEUiB0byBwcmVzZW50IGh0dHBz Oi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1pZHItYmdwLXJvdXRlLXJlZnJl c2gtb3B0aW9ucy0wMC50eHQNClRvOiBSb2JlcnQgUmFzenVrIDxyb2JlcnRAcmFzenVrLm5ldDxt YWlsdG86cm9iZXJ0QHJhc3p1ay5uZXQ+Pg0KQ2M6IGlkciB3ZyA8aWRyQGlldGYub3JnPG1haWx0 bzppZHJAaWV0Zi5vcmc+Pg0KDQoNCk9uIE1vbiwgSnVsIDExLCAyMDE2IGF0IDE6NDcgUE0sIFJv YmVydCBSYXN6dWsgPHJvYmVydEByYXN6dWsubmV0PG1haWx0bzpyb2JlcnRAcmFzenVrLm5ldD4+ IHdyb3RlOg0KSGkgVG9ueSwNCg0KSGV5IFJvYmVydCwgdGhhbmtzIGZvciBjaGltaW5nIGluLiBH b29kIHF1ZXN0aW9ucy4gSSBzcGVhayBoZXJlIGZvciBteXNlbGYsIG90aGVyIGF1dGhvcnMgb2Yg dGhlIGRyYWZ0IG1heSBoYXZlIGRpZmZlcmluZyBvcGluaW9ucy4NCg0KDQpDYW4geW91IGNsYXJp Znkgd2hhdCBpcyB0aGUgZXhwZWN0ZWQgYmVoYXZpb3VyIGFzIGZhciBhcyBwZXIgcGVlciBmaWx0 ZXItbGlzdCB3aGVuIHlvdSBuZWdvdGlhdGUgYm90aCBSZWZyZXNoIHdpdGggb3B0aW9ucywgT1JG IGFuZCBSVEMgPyBOb3RlIHRoYXQgT1JGIGFsc28gaW5jbHVkZXMgcmVjZW50IGV4dGVuc2lvbiBh cyBkZXNjcmliZWQgaW4gUkZDNzU0MyAtIHdvdWxkIGFsbCBvZiB0aG9zZSBiZSBhbHdheXMgYSBs b2dpY2FsIEFORCB0b3dhcmRzIGEgcGVlciB3aGljaCBwdXNoZWQgdGhvc2UgPw0KDQpXZSBkaWRu J3QgZGlzY3VzcyB0aGF0IG9uZSB0aHJvdWdoIGJ1dCB0aGUgb25seSBsb2dpY2FsIGNvbmNsdXNp b24gZm9yIG1lIGlzIHRoYXQgdGhlIE9SRi9DUC1PUkYgaW5zdGFsbGVkIGFyZSByZXNwZWN0ZWQg KGkuZS4gaXQncyBhbiBpbXBsaWNpdCBBTkQpLiBJIHNlZSBPUkYgYXMgc3RhdGVmdWxsLCByZW1v dGUtcHVzaGVkIHBvbGljeSBvbiB0aGUgcGVlciB0aGF0IGlzIG5vdCBiZWluZyBmbGlwcGVkIGFy b3VuZCBhbGwgdGhlIHRpbWUgKGFsYmVpdCBBRkFJUiB0aGVyZSB3ZXJlIHNvbWUgYXR0ZW1wdHMg QCBub24tcGVyc2lzdGVudCwgb25lIHNob3QgT1JGIGJ1dCB0aGF0IGVuZGVkIHVwIGV4cGlyaW5n PykNCg0KW0ppZV0gSSB0aGluayB0aGUgYXR0ZW1wdHMgeW91IG1lbnRpb25lZCBoZXJlIGFyZSB0 aGUgb25lLXRpbWUgT1JGIGRyYWZ0czogZHJhZnQtemVuZy1pZHItb25lLXRpbWUtcHJlZml4LW9y ZiAgYW5kIGRyYWZ0LWRvbmctaWRyLW9uZS10aW1lLWV4dC1jb21tdW5pdHktb3JmLiBBZnRlciBz ZXZlcmFsIHJldmlzaW9ucywgdGhlc2UgZHJhZnRzIGdvdCBleHBpcmVkIGR1ZSB0byBsYWNrIG9m IHJlcXVpcmVtZW50cyBhdCB0aGF0IHRpbWUuIElmIHBlb3BsZSBmb3VuZCBzb21lIG5ldyB1c2Ug Y2FzZXMgb2YgdGhlc2Uga2luZHMgb2YgbWVjaGFuaXNtcywgdGhlIGF1dGhvcnMgd291bGQgYmUg aGFwcHkgdG8gYnJpbmcgdGhlbSBiYWNrIHRvIGRpc2N1c3Npb24uDQoNClRoZSBtb3RpdmF0aW9u IGZvciB0aGlzIHdvcmsgd2VyZSBzY2VuYXJpb3Mgd2hlcmUgYSBzaW5nbGUtc2hvdCByZWZyZXNo IGlzIG5lZWRlZCwgYWN0dWFsbHkgY29uY3VycmVudCBidW5jaCBvZiB0aG9zZSBiYXNlZCBvbiBj b25maWd1cmF0aW9uIGNoYW5nZXMsIHBlZXIgaGF2aW5nIGRyb3BwZWQgcmVjZWl2ZWQgcm91dGVz IGJhc2VkIG9uIHNwZWNzIChBLUQpLCBpbiBwb2xpY3kgY2hhbmdlcywgam9pbmluZyBWUE5zLCBF VklzIGFuZCBzbyBvbi4gUHV0dGluZyBPUkYgb24gYSBwZWVyLCByZWZyZXNoIGFuZCByZW1vdmUg T1JGcyBpcyBzaWduaWZpY2FudGx5IGhlYXZpZXIgcHJvY2VzcyB0aGF0IG1heSBpbnRlcmZlcmUg b24gdG9wIHdpdGggbm9ybWFsIHVwZGF0ZSBwcm9jZXNzIGdvaW5nIG9uIGFuZCBuZWVkcyB0byBi ZSBkb25lIG9uZS1ieS1vbmUgKHNpbmNlIHlvdSBoYXZlIHRvIHdhaXQgZm9yIHNpbmdsZSBCb1JS L0VvUlIgcGFpcikgdW5sZXNzIG9uZSBpcyB2ZXJ5IHNtYXJ0IGFib3V0IGNvbWJpbmluZyBPUkYg cG9zc2libHkgJiBwbGF5aW5nIHdpdGggdGhlIERFRkVSL0lNTUVESUFURXMuIEFzIHdlIGluZGlj YXRlZCwgaWYgdGhlIEFGSS9TQUZJIGlzIGNvdmVyZWQgYnkgUlRDIGFuZCBSVEMgaXMgc3VwcG9y dGVkICYgb25lIGlzIHdpbGxpbmcgdG8gY29uZmlndXJlIFJUcyBmb3IgZWFjaCBzdWJzZXQgb2Yg cm91dGVzIHRoYXQgbWF5IG5lZWQgcmVmcmVzaGluZywgUlQgd2lsbCBiZSBkb2luZyB0aGUgc2Ft ZSBqb2IganVzdCBmaW5lLg0KDQpbSmllXSBUaGUgbW90aXZhdGlvbnMgbG9vayBzaW1pbGFyIHRv IHdoYXQgd2UgZGVzY3JpYmVkIGZvciB0aGUgb25lLXRpbWUgT1JGIGRyYWZ0cy4NCg0KDQpXb3Vs ZCB5b3UgYWx3YXlzIGNhcnJ5IE9SRiB3aXRoIHNlcGFyYXRlIFJlZnJlc2hfSUQgdmFsdWUgPw0K DQpZZXMsIFJlZnJlc2gtSUQjIGlzIHN0cmljdGx5IG1vbm90b25pYyBzbyB0aGVyZSBpcyBuZXZl ciBhIG1pc3VuZGVyc3RhbmRpbmcgV0hBVCB0aGUgQm9SUiBiZWxvbmdzIHRvLiBPYnNlcnZlIHRo YXQgdGhlIGRyYWZ0IGRvZXMgTk9UIG1hbmRhdGUgdGhhdCBhIHJlcXVlc3QgTVVTVCBiZSBmb2xs b3dlZCBieSBhY2NvcmRpbmcgQm9SUiwgb25seSB0aGF0IEJvUlJzIG11c3QgZm9sbG93IHNhbWUg c2VxdWVuY2UgYXMgcmVxdWVzdHMgKGkuZS4gYXJlIGFsc28gc3RyaWN0bHkgbW9ub3RvbmljKS4g SG93ZXZlciwgd2Ugc2hvdWxkIHByb2JhYmx5IHNwZWNpZnkgdGhhdCBvcHRpb25zIF9hbmRfIE9S RiBjYW4gTk9UIGJlIG1peGVkIGluIHRoZSBzYW1lIHR5cGUgIzMgbWVzc2FnZSBidXQgaXQncyBl aXRoZXIgb25lIG9yIHRoZSBvdGhlciAoYW5kIGFueXRoaW5nIGVsc2UgaXMgZXJyb3IpLiBUaGlz IHdpbGwgYWxsb3cgT1JGIG9wZXJhdGlvbnMgbGlrZSB0b2RheSArIGJlbmVmaXQgb2YgdGhlIFJl ZnJlc2ggSUQjICBvbiB0aGUgQm9SUiBzbyB0aGUgSU1NRURJQVRFIGNhbiBnbyBvbiBAIHRoZSBz YW1lIHRpbWUgYXMgYW5vdGhlciByZXF1ZXN0IHdpdGggaGlnaGVyIFJlZnJlc2ggSUQjIChkZSBm YWN0byB3ZSBhbGxvdyBtdWx0aXBsZSBwYXJhbGxlbCByZWZyZXNoZXMgYXMgeW91IHNlZSkuICBJ biBjYXNlIG9mIERFRkVSIHRoZXJlIHdpbGwgYmUgc2ltcGx5IG5vIEJvUlIgZm9yIGl0Lg0KDQoN CklmIG9uZSByZXF1ZXN0cyBmdWxsIEFkal9SSUJfT3V0IGluIHRoZSBuZXcgbW9kZWwgYW5kIHNl bmRzIHJlZnJlc2ggbWVzc2FnZSB3aXRoIG5ldyByZWZyZXNoX2lkIGFuZCBubyBvcHRpb25zIGhv d2V2ZXIgdGhlcmUgYXJlIE9SRiBlbnRyaWVzIGFscmVhZHkgaW5zdGFsbGVkIGluIHRoZSBwYXN0 IHdvdWxkIGhlIGdldCBqdXN0IHRoZSBzdWJzZXQgb2Ygcm91dGVzIGFnYWluc3QgYWxsIE9SRiBl bnRyaWVzID8gSW4gb3RoZXIgd29yZHMgSSB0aGluayB0aGUgZHJhZnQgc2hvdWxkIHN0YXRlIHRo YXQgUmVmcmVzaF9JRHMgaGF2ZSBubyBpbXBhY3QgdG8gT1JGIEFERHMgb3IgUkVNT1ZFIGFjdGlv bnMgLSBkb24ndCB5b3UgdGhpbmsgPw0KDQpJIGFncmVlLiBZZXMsIE9SRiBpcyBraW5kIG9mICAi cGVybWFuZW50IGZpbHRlciIgb24gdGhlIHBlZXIgd2hpbGUgdGhlIGludGVudCBvZiB0aGlzIGRy YWZ0IGlzIHRvIGhhdmUgYnVuY2ggb2YgInNtYWxsIHJlZnJlc2hlcyIgZ29pbmcgb24gQCBzYW1l IHRpbWUgcG9zc2libHkgKGlmIHlvdSByZXF1ZXN0IHRoZSByZWZyZXNoZXMgZnJvbSBhIGdvb2Qg aW1wbGVtZW50YXRpb24gd2hpbGUgbG93LWVuZCBpbXBsZW1lbnRhdGlvbnMgbWF5IHNlcmlhbGl6 ZSB0aGUgcmVxdWVzdHMgdG8gc2ltcGxpZnkgaW50ZXJuYWwgbG9naWMgOy0pLg0KDQoNCkFzIGZh ciBhcyBjdXJyZW50IHR5cGVzIHdoeSBub3QgYWRkIHJlZ3VsYXIvZXh0ZW5kZWQgY29tbXVuaXR5 ID8NCg0KRGlzY3Vzc2lvbiBjYW1lIHVwLiBGZWVsaW5nIHdhcyBpdCdzIGFuIGltbWVkaWF0ZSBl bmNyb2FjaCBvbiBSVCB0ZXJyaXRvcnkuIEkgYXJndWVkIGZvciBpdCA7LSkgIFVsdGltYXRlbHks IHRha2luZyBhIG1vcmUgcmVsYXhlZCB2aWV3LCB3ZSBjaG9zZSB0byB3YWl0IGFuZCBzZWUgd2hh dCB0aGUgcmVzcG9uc2UgaXMgYW5kIG1vc3QgcHJlc3NpbmcgdXNlIGNhc2VzIHBlb3BsZSBicmlu ZyB0byBpdCBhbmQgdGhlbiB3ZSBzdGFydCB0byBkZWZpbmUgYml0cyBhbmQgYnl0ZXMgb2YgdGhl IG9wdGlvbnMgc3VwcG9ydGVkLCBwb3NzaWJseSBib3Jyb3dpbmcgdG8gYW4gZXh0ZW50IGZyb20g dGhlIE9SRiBzcGVjcyA7LSkgIEFzIGluICJtb3N0IHNpbmNlcmUgZm9ybSBvZiBmbGF0dGVyeSIg YW5kIHN1Y2ggLi4uIDstKQ0KDQpbSmllXSBBY3R1YWxseSBiZWZvcmUgdGhlIG9uZS10aW1lIE9S RiBkcmFmdHMgd2VyZSBzdWJtaXR0ZWQsIHdlIGluaXRpYWxseSBjb25zaWRlcmVkIHRvIG1ha2Ug aXQgYSDigJxzZWxlY3RpdmUgcm91dGUgcmVmcmVzaOKAnSBtZWNoYW5pc20uIFRoZW4gd2UgcmVh bGl6ZWQgdGhhdCB0aGUgZmlsdGVycyB3aWxsIGJlIHF1aXRlIHNpbWlsYXIgdG8gdGhlIG9uZXMg YWxyZWFkeSBkZWZpbmVkIGZvciBPUkYuIEluIG9yZGVyIHRvIHJldXNlIHRoZSBPUkYgZmlsdGVy cywgd2UgdGhlbiBkZWNpZGVkIHRvIGRlZmluZSB0aGlzIG1lY2hhbmlzbSBhcyBuZXcg4oCcb25l LXRpbWXigJ0gT1JGIHR5cGVzLiAgSnVzdCB0byBwcm92aWRlIHNvbWUgYmFja2dyb3VuZCBpbmZv cm1hdGlvbiBzaW5jZSB5b3UgYWxzbyBwbGFuIHRvIHJldXNlIHRoZSBmb3JtYXQgb2YgdGhlIGV4 aXN0aW5nIE9SRiB0eXBlcy4NCg0KQmVzdCByZWdhcmRzLA0KSmllDQoNCi0tIHRvbnkNCg0KDQoN Cg0KLS0NCldl4oCZdmUgaGVhcmQgdGhhdCBhIG1pbGxpb24gbW9ua2V5cyBhdCBhIG1pbGxpb24g a2V5Ym9hcmRzIGNvdWxkIHByb2R1Y2UgdGhlIGNvbXBsZXRlIHdvcmtzIG9mIFNoYWtlc3BlYXJl OyBub3csIHRoYW5rcyB0byB0aGUgSW50ZXJuZXQsIHdlIGtub3cgdGhhdCBpcyBub3QgdHJ1ZS4N CuKAlFJvYmVydCBXaWxlbnNreQ0KDQo= --_000_76CD132C3ADEF848BD84D028D243C92774EEFBE8NKGEML515MBXchi_ Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: base64 PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTIgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6 5a6L5L2TOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtm b250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMgMiA0 O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUg MiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5v c2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJc QOWui+S9kyI7DQoJcGFub3NlLTE6MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQpAZm9udC1mYWNlDQoJ e2ZvbnQtZmFtaWx5Okdlb3JnaWE7DQoJcGFub3NlLTE6MiA0IDUgMiA1IDQgNSAyIDMgMzt9DQov KiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1z b05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNp emU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OuWui+S9kzt9DQphOmxpbmssIHNwYW4uTXNvSHlwZXJs aW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpibHVlOw0KCXRleHQtZGVjb3Jh dGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJ e21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9u OnVuZGVybGluZTt9DQpwLk1zb0FjZXRhdGUsIGxpLk1zb0FjZXRhdGUsIGRpdi5Nc29BY2V0YXRl DQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoi5om55rOo5qGG5paH 5pysIENoYXIiOw0KCW1hcmdpbjowY207DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQt c2l6ZTo5LjBwdDsNCglmb250LWZhbWlseTrlrovkvZM7fQ0Kc3Bhbi5DaGFyDQoJe21zby1zdHls ZS1uYW1lOiLmibnms6jmoYbmlofmnKwgQ2hhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0K CW1zby1zdHlsZS1saW5rOuaJueazqOahhuaWh+acrDsNCglmb250LWZhbWlseTrlrovkvZM7fQ0K c3Bhbi5FbWFpbFN0eWxlMTkNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9u dC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgljb2xvcjojMUY0OTdEO30NCi5Nc29D aHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5O30NCkBwYWdlIFdvcmRTZWN0 aW9uMQ0KCXtzaXplOjYxMi4wcHQgNzkyLjBwdDsNCgltYXJnaW46NzIuMHB0IDkwLjBwdCA3Mi4w cHQgOTAuMHB0O30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+ PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9 ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBt c28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0 PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0K PC9oZWFkPg0KPGJvZHkgbGFuZz0iWkgtQ04iIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0K PGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxh bmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxp YnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+SGkgUm9iZXJ0 LA0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFu Zz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGli cmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNw OzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1V UyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90 OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPkkgYWdyZWUgdGhhdCDigJxS b3V0ZSBUeXBl4oCdIGJhc2VkIGZpbHRlcmluZyBtYXkgYmUgbmVlZGVkIGluIHNvbWUgY2FzZXMu IERvIHlvdSB0aGluayBpdCBzaG91bGQgYmVoYXZlIGFzIG9uZS10aW1lIGZpbHRlciBvciBhIHBl cm1hbmVudCBmaWx0ZXIsDQogb3IgbWF5YmUgYm90aCBhcmUgbmVlZGVkPzxvOnA+PC9vOnA+PC9z cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0i Zm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3Nh bnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNp emU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJp ZiZxdW90Oztjb2xvcjojMUY0OTdEIj5BcyBmb3IgdGhlIG9uZS10aW1lIGJlaGF2aW9yLCBJTU8g aXQgZGVzZXJ2ZXMgYSBkZWRpY2F0ZWQgT1JGIHR5cGUgKG9yIHJlZnJlc2ggb3B0aW9uKSwgYXMg dXNpbmcgY29uc2VjdXRpdmUgbWVzc2FnZXMgdG8gaW5zdGFsbCBhbmQgcmVtb3ZlIHRoZQ0KIE9S RiBmaWx0ZXIgY291bGQgaW50cm9kdWNlIHVubmVjZXNzYXJ5IGNvc3QgaW4gYm90aCBtZXNzYWdl IGV4Y2hhbmdlIGFuZCB0aGUgcHJvY2Vzc2luZyBvbiB0aGUgZGV2aWNlLjxvOnA+PC9vOnA+PC9z cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0i Zm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3Nh bnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNp emU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJp ZiZxdW90Oztjb2xvcjojMUY0OTdEIj5CZXN0IHJlZ2FyZHMsPG86cD48L286cD48L3NwYW4+PC9w Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNp emU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJp ZiZxdW90Oztjb2xvcjojMUY0OTdEIj5KaWU8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz cz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7 Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2Nv bG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXYgc3R5bGU9ImJv cmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0I1QzRERiAxLjBwdDtwYWRkaW5nOjMuMHB0IDBj bSAwY20gMGNtIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIGxhbmc9IkVOLVVTIiBz dHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1 b3Q7c2Fucy1zZXJpZiZxdW90OyI+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIGxhbmc9IkVOLVVTIiBz dHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1 b3Q7c2Fucy1zZXJpZiZxdW90OyI+IHJyYXN6dWtAZ21haWwuY29tIFttYWlsdG86cnJhc3p1a0Bn bWFpbC5jb21dDQo8Yj5PbiBCZWhhbGYgT2YgPC9iPlJvYmVydCBSYXN6dWs8YnI+DQo8Yj5TZW50 OjwvYj4gV2VkbmVzZGF5LCBKdWx5IDIwLCAyMDE2IDU6NTIgQU08YnI+DQo8Yj5Ubzo8L2I+IERv bmdqaWUgKEppbW15KTxicj4NCjxiPkNjOjwvYj4gVG9ueSBQcnp5Z2llbmRhOyBpZHIgd2c8YnI+ DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IFtJZHJdIEZ3ZDogU2xvdCByZXF1ZXN0IGluIElEUiB0byBw cmVzZW50IGh0dHBzOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1pZHItYmdw LXJvdXRlLXJlZnJlc2gtb3B0aW9ucy0wMC50eHQ8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rp dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwv bzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu IGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7 c2Fucy1zZXJpZiZxdW90OyI+SGkgSmllLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0K PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9u dC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PG86cD4m bmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h bCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90 OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5UbyBtZSB3aGF0IGlzIHBlcmhhcHMgbWlzc2luZyBp cyBqdXN0IGEgbmV3IGRyYWZ0IHRvIGRlZmluZSAqUm91dGUgVHlwZSogT1JGIHRvIGFkZHJlc3Mg c29tZSBvZiB0aG9zZSBFVlBOIG5ldyBOTFJJIGVuY29kaW5ncy48bzpwPjwvbzpwPjwvc3Bhbj48 L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1V UyIgc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYm cXVvdDsiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs YXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1 b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+SSBhbSBub3QgdGhhdCBtdWNo IGNvbnZpbmNlZCBpZiBvbmUgdGltZSBPUkYgaXMgbmVlZGVkIGFzIHlvdSBhcmUgZnJlZSB0byBJ TlNUQUxMIGFuZCBSRU1PVkUgT1JGIGVmZmVjdGl2ZWx5IHByb2R1Y2luZyBvbmUgdGltZSBiZWhh dmlvci4gQWxzbyBleGlzdGluZyBFbmhhbmNlZCBSb3V0ZSBSZWZyZXNoIHNob3VsZA0KIHdvcmsg d2l0aCBPUkYgdG9vLiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4N CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1p bHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PG86cD4mbmJzcDs8 L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw YW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVv dDtzYW5zLXNlcmlmJnF1b3Q7Ij5NYW55IHRoeCw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rp dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9 ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPlIu PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h bCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90 OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8 L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5 bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsi PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN c29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJp YWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+ PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBs YW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNz PSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj5PbiBUdWUsIEp1bCAxOSwgMjAxNiBhdCAx MTo0NyBQTSwgRG9uZ2ppZSAoSmltbXkpICZsdDs8YSBocmVmPSJtYWlsdG86amllLmRvbmdAaHVh d2VpLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPmppZS5kb25nQGh1YXdlaS5jb208L2E+Jmd0OyB3cm90 ZTo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt YWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6 YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFt aWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0 OTdEIj5IaSBUb255LA0KPC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPjwvbzpwPjwvc3Bh bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1 dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0i Zm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3Nh bnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+Jm5ic3A7PC9zcGFuPjxzcGFuIGxhbmc9IkVO LVVTIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0i bXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFu IGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtD YWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+UGxlYXNl IHNlZSBzb21lIGNvbW1lbnRzIGlubGluZSB3aXRoIFtKaWVdOjwvc3Bhbj48c3BhbiBsYW5nPSJF Ti1VUyI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9 Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3Bh biBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7 Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPiZuYnNw Ozwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPGRpdiBz dHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6 My4wcHQgMGNtIDBjbSAwY20iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJn aW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48Yj48c3BhbiBsYW5n PSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21h JnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPkZyb206PC9zcGFuPjwvYj48c3BhbiBsYW5n PSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21h JnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPiBJZHINCiBbbWFpbHRvOjxhIGhyZWY9Im1h aWx0bzppZHItYm91bmNlc0BpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPmlkci1ib3VuY2VzQGll dGYub3JnPC9hPl0NCjxiPk9uIEJlaGFsZiBPZiA8L2I+VG9ueSBQcnp5Z2llbmRhPGJyPg0KPGI+ U2VudDo8L2I+IFR1ZXNkYXksIEp1bHkgMTksIDIwMTYgNjowNCBQTTxicj4NCjxiPlRvOjwvYj4g Um9iZXJ0IFJhc3p1azsgaWRyIHdnPGJyPg0KPGI+U3ViamVjdDo8L2I+IFtJZHJdIEZ3ZDogU2xv dCByZXF1ZXN0IGluIElEUiB0byBwcmVzZW50IDxhIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3Jn L2ludGVybmV0LWRyYWZ0cy9kcmFmdC1pZHItYmdwLXJvdXRlLXJlZnJlc2gtb3B0aW9ucy0wMC50 eHQiIHRhcmdldD0iX2JsYW5rIj4NCmh0dHBzOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0 cy9kcmFmdC1pZHItYmdwLXJvdXRlLXJlZnJlc2gtb3B0aW9ucy0wMC50eHQ8L2E+PC9zcGFuPjxz cGFuIGxhbmc9IkVOLVVTIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNz PSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJv dHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiPiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFu PjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3At YWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIj5S ZXNlbmRpbmcgLi4uJm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNz PSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJv dHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiPiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFu PjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3At YWx0OmF1dG87bWFyZ2luLWJvdHRvbToxMi4wcHQiPjxzcGFuIGxhbmc9IkVOLVVTIj4tLS0tLS0t LS0tIEZvcndhcmRlZCBtZXNzYWdlIC0tLS0tLS0tLS08YnI+DQpGcm9tOiA8Yj5Ub255IFByenln aWVuZGE8L2I+ICZsdDs8YSBocmVmPSJtYWlsdG86dG9ueXNpZXRmQGdtYWlsLmNvbSIgdGFyZ2V0 PSJfYmxhbmsiPnRvbnlzaWV0ZkBnbWFpbC5jb208L2E+Jmd0Ozxicj4NCkRhdGU6IE1vbiwgSnVs IDExLCAyMDE2IGF0IDM6MDQgUE08YnI+DQpTdWJqZWN0OiBSZTogW0lkcl0gU2xvdCByZXF1ZXN0 IGluIElEUiB0byBwcmVzZW50IDxhIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3JnL2ludGVybmV0 LWRyYWZ0cy9kcmFmdC1pZHItYmdwLXJvdXRlLXJlZnJlc2gtb3B0aW9ucy0wMC50eHQiIHRhcmdl dD0iX2JsYW5rIj4NCmh0dHBzOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1p ZHItYmdwLXJvdXRlLXJlZnJlc2gtb3B0aW9ucy0wMC50eHQ8L2E+PGJyPg0KVG86IFJvYmVydCBS YXN6dWsgJmx0OzxhIGhyZWY9Im1haWx0bzpyb2JlcnRAcmFzenVrLm5ldCIgdGFyZ2V0PSJfYmxh bmsiPnJvYmVydEByYXN6dWsubmV0PC9hPiZndDs8YnI+DQpDYzogaWRyIHdnICZsdDs8YSBocmVm PSJtYWlsdG86aWRyQGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+aWRyQGlldGYub3JnPC9hPiZn dDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5 bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48 c3BhbiBsYW5nPSJFTi1VUyI+Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxw IGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFy Z2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiPiZuYnNwOzxvOnA+PC9vOnA+ PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdp bi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVO LVVTIj5PbiBNb24sIEp1bCAxMSwgMjAxNiBhdCAxOjQ3IFBNLCBSb2JlcnQgUmFzenVrICZsdDs8 YSBocmVmPSJtYWlsdG86cm9iZXJ0QHJhc3p1ay5uZXQiIHRhcmdldD0iX2JsYW5rIj5yb2JlcnRA cmFzenVrLm5ldDwvYT4mZ3Q7IHdyb3RlOjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8 ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRv O21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZv bnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPkhpIFRv bnksPC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rp dj4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2lu LXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4t VVMiPiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz PSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJv dHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiPkhleSBSb2JlcnQsIHRoYW5rcyBmb3Ig Y2hpbWluZyBpbi4gR29vZCBxdWVzdGlvbnMuIEkgc3BlYWsgaGVyZSBmb3IgbXlzZWxmLCBvdGhl ciBhdXRob3JzIG9mIHRoZSBkcmFmdCBtYXkgaGF2ZSBkaWZmZXJpbmcgb3BpbmlvbnMuJm5ic3A7 PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h bCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDph dXRvIj48c3BhbiBsYW5nPSJFTi1VUyI+Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9k aXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0ND Q0NDQyAxLjBwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21h cmdpbi10b3A6NS4wcHQ7bWFyZ2luLXJpZ2h0OjBjbTttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxk aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFs dDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5 bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsi PiZuYnNwOzwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD48L286cD48L3NwYW4+PC9wPg0K PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9w LWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIg c3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVv dDsiPkNhbiB5b3UgY2xhcmlmeSB3aGF0IGlzIHRoZSBleHBlY3RlZCBiZWhhdmlvdXIgYXMgZmFy IGFzIHBlciBwZWVyIGZpbHRlci1saXN0IHdoZW4geW91IG5lZ290aWF0ZSBib3RoIFJlZnJlc2gg d2l0aCBvcHRpb25zLA0KIE9SRiBhbmQgUlRDID8gTm90ZSB0aGF0IE9SRiBhbHNvIGluY2x1ZGVz IHJlY2VudCBleHRlbnNpb24gYXMgZGVzY3JpYmVkIGluIFJGQzc1NDMgLSB3b3VsZCBhbGwgb2Yg dGhvc2UgYmUgYWx3YXlzIGEgbG9naWNhbCBBTkQgdG93YXJkcyBhIHBlZXIgd2hpY2ggcHVzaGVk IHRob3NlID8mbmJzcDs8L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+PC9vOnA+PC9zcGFu PjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z b05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9t LWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyI+Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9w Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4t dG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1V UyI+V2UgZGlkbid0IGRpc2N1c3MgdGhhdCBvbmUgdGhyb3VnaCBidXQgdGhlIG9ubHkgbG9naWNh bCBjb25jbHVzaW9uIGZvciBtZSBpcyB0aGF0IHRoZSBPUkYvQ1AtT1JGIGluc3RhbGxlZCBhcmUg cmVzcGVjdGVkIChpLmUuIGl0J3MgYW4gaW1wbGljaXQgQU5EKS4gSSBzZWUgT1JGDQogYXMgc3Rh dGVmdWxsLCByZW1vdGUtcHVzaGVkIHBvbGljeSBvbiB0aGUgcGVlciB0aGF0IGlzIG5vdCBiZWlu ZyBmbGlwcGVkIGFyb3VuZCBhbGwgdGhlIHRpbWUgKGFsYmVpdCBBRkFJUiB0aGVyZSB3ZXJlIHNv bWUgYXR0ZW1wdHMgQCBub24tcGVyc2lzdGVudCwgb25lIHNob3QgT1JGIGJ1dCB0aGF0IGVuZGVk IHVwIGV4cGlyaW5nPyk8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs IiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1 dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWls eTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3 RCI+Jm5ic3A7PC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+ DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNv LW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1z aXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2Vy aWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+W0ppZV0gSSB0aGluayB0aGUgYXR0ZW1wdHMgeW91IG1l bnRpb25lZCBoZXJlIGFyZSB0aGUgb25lLXRpbWUgT1JGIGRyYWZ0czogZHJhZnQtemVuZy1pZHIt b25lLXRpbWUtcHJlZml4LW9yZg0KICZuYnNwO2FuZCBkcmFmdC1kb25nLWlkci1vbmUtdGltZS1l eHQtY29tbXVuaXR5LW9yZi4gQWZ0ZXIgc2V2ZXJhbCByZXZpc2lvbnMsIHRoZXNlIGRyYWZ0cyBn b3QgZXhwaXJlZCBkdWUgdG8gbGFjayBvZiByZXF1aXJlbWVudHMgYXQgdGhhdCB0aW1lLiBJZiBw ZW9wbGUgZm91bmQgc29tZSBuZXcgdXNlIGNhc2VzIG9mIHRoZXNlIGtpbmRzIG9mIG1lY2hhbmlz bXMsIHRoZSBhdXRob3JzIHdvdWxkIGJlIGhhcHB5IHRvIGJyaW5nIHRoZW0gYmFjayB0byBkaXNj dXNzaW9uLjwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD48L286cD48L3NwYW4+PC9wPg0K PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9w LWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyI+ Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z b05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9t LWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyI+VGhlIG1vdGl2YXRpb24gZm9yIHRoaXMgd29y ayB3ZXJlIHNjZW5hcmlvcyB3aGVyZSBhIHNpbmdsZS1zaG90IHJlZnJlc2ggaXMgbmVlZGVkLCBh Y3R1YWxseSBjb25jdXJyZW50IGJ1bmNoIG9mIHRob3NlIGJhc2VkIG9uIGNvbmZpZ3VyYXRpb24g Y2hhbmdlcywgcGVlciBoYXZpbmcNCiBkcm9wcGVkIHJlY2VpdmVkIHJvdXRlcyBiYXNlZCBvbiBz cGVjcyAoQS1EKSwgaW4gcG9saWN5IGNoYW5nZXMsIGpvaW5pbmcgVlBOcywgRVZJcyBhbmQgc28g b24uIFB1dHRpbmcgT1JGIG9uIGEgcGVlciwgcmVmcmVzaCBhbmQgcmVtb3ZlIE9SRnMgaXMgc2ln bmlmaWNhbnRseSBoZWF2aWVyIHByb2Nlc3MgdGhhdCBtYXkgaW50ZXJmZXJlIG9uIHRvcCB3aXRo IG5vcm1hbCB1cGRhdGUgcHJvY2VzcyBnb2luZyBvbiBhbmQgbmVlZHMgdG8gYmUgZG9uZQ0KIG9u ZS1ieS1vbmUgKHNpbmNlIHlvdSBoYXZlIHRvIHdhaXQgZm9yIHNpbmdsZSBCb1JSL0VvUlIgcGFp cikgdW5sZXNzIG9uZSBpcyB2ZXJ5IHNtYXJ0IGFib3V0IGNvbWJpbmluZyBPUkYgcG9zc2libHkg JmFtcDsgcGxheWluZyB3aXRoIHRoZSBERUZFUi9JTU1FRElBVEVzLiBBcyB3ZSBpbmRpY2F0ZWQs IGlmIHRoZSBBRkkvU0FGSSBpcyBjb3ZlcmVkIGJ5IFJUQyBhbmQgUlRDIGlzIHN1cHBvcnRlZCAm YW1wOyBvbmUgaXMgd2lsbGluZyB0byBjb25maWd1cmUgUlRzDQogZm9yIGVhY2ggc3Vic2V0IG9m IHJvdXRlcyB0aGF0IG1heSBuZWVkIHJlZnJlc2hpbmcsIFJUIHdpbGwgYmUgZG9pbmcgdGhlIHNh bWUgam9iIGp1c3QgZmluZS4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i TXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0 b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtm b250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29s b3I6IzFGNDk3RCI+Jm5ic3A7PC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPjwvbzpwPjwv c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0 OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHls ZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90 O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+W0ppZV0gVGhlIG1vdGl2YXRpb25zIGxv b2sgc2ltaWxhciB0byB3aGF0IHdlIGRlc2NyaWJlZCBmb3IgdGhlIG9uZS10aW1lIE9SRiBkcmFm dHMuPC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rp dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0 OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIj4mbmJz cDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3Jk ZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGNtIDBjbSAw Y20gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tcmlnaHQ6 MGNtO21hcmdpbi1ib3R0b206NS4wcHQiPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y bWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0 OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwm cXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+Jm5ic3A7PC9zcGFuPjxzcGFuIGxhbmc9IkVO LVVTIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv Tm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20t YWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJp YWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+V291bGQgeW91IGFsd2F5cyBjYXJyeSBP UkYgd2l0aCBzZXBhcmF0ZSBSZWZyZXNoX0lEIHZhbHVlID8mbmJzcDs8L3NwYW4+PHNwYW4gbGFu Zz0iRU4tVVMiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2Nr cXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9w LWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyI+ Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z b05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9t LWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyI+WWVzLCBSZWZyZXNoLUlEIyBpcyBzdHJpY3Rs eSBtb25vdG9uaWMgc28gdGhlcmUgaXMgbmV2ZXIgYSBtaXN1bmRlcnN0YW5kaW5nIFdIQVQgdGhl IEJvUlIgYmVsb25ncyB0by4gT2JzZXJ2ZSB0aGF0IHRoZSBkcmFmdCBkb2VzIE5PVCBtYW5kYXRl IHRoYXQgYSByZXF1ZXN0IE1VU1QNCiBiZSBmb2xsb3dlZCBieSBhY2NvcmRpbmcgQm9SUiwgb25s eSB0aGF0IEJvUlJzIG11c3QgZm9sbG93IHNhbWUgc2VxdWVuY2UgYXMgcmVxdWVzdHMgKGkuZS4g YXJlIGFsc28gc3RyaWN0bHkgbW9ub3RvbmljKS4gSG93ZXZlciwgd2Ugc2hvdWxkIHByb2JhYmx5 IHNwZWNpZnkgdGhhdCBvcHRpb25zIF9hbmRfIE9SRiBjYW4gTk9UIGJlIG1peGVkIGluIHRoZSBz YW1lIHR5cGUgIzMgbWVzc2FnZSBidXQgaXQncyBlaXRoZXIgb25lIG9yIHRoZSBvdGhlcg0KIChh bmQgYW55dGhpbmcgZWxzZSBpcyBlcnJvcikuIFRoaXMgd2lsbCBhbGxvdyBPUkYgb3BlcmF0aW9u cyBsaWtlIHRvZGF5ICYjNDM7IGJlbmVmaXQgb2YgdGhlIFJlZnJlc2ggSUQjICZuYnNwO29uIHRo ZSBCb1JSIHNvIHRoZSBJTU1FRElBVEUgY2FuIGdvIG9uIEAgdGhlIHNhbWUgdGltZSBhcyBhbm90 aGVyIHJlcXVlc3Qgd2l0aCBoaWdoZXIgUmVmcmVzaCBJRCMgKGRlIGZhY3RvIHdlIGFsbG93IG11 bHRpcGxlIHBhcmFsbGVsIHJlZnJlc2hlcyBhcyB5b3Ugc2VlKS4mbmJzcDsNCiBJbiBjYXNlIG9m IERFRkVSIHRoZXJlIHdpbGwgYmUgc2ltcGx5IG5vIEJvUlIgZm9yIGl0LiZuYnNwOzxvOnA+PC9v OnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl PSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNw YW4gbGFuZz0iRU4tVVMiPiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGJs b2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4w cHQ7cGFkZGluZzowY20gMGNtIDBjbSA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tdG9w OjUuMHB0O21hcmdpbi1yaWdodDowY207bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8ZGl2Pg0KPGRp dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bztt c28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250 LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4mbmJzcDs8 L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0K PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0 bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJm b250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5JZiBv bmUgcmVxdWVzdHMgZnVsbCBBZGpfUklCX091dCBpbiB0aGUgbmV3IG1vZGVsIGFuZCBzZW5kcyBy ZWZyZXNoIG1lc3NhZ2Ugd2l0aCBuZXcgcmVmcmVzaF9pZCBhbmQgbm8gb3B0aW9ucyBob3dldmVy DQogdGhlcmUgYXJlIE9SRiBlbnRyaWVzIGFscmVhZHkgaW5zdGFsbGVkIGluIHRoZSBwYXN0IHdv dWxkIGhlIGdldCBqdXN0IHRoZSBzdWJzZXQgb2Ygcm91dGVzIGFnYWluc3QgYWxsIE9SRiBlbnRy aWVzID8gSW4gb3RoZXIgd29yZHMgSSB0aGluayB0aGUgZHJhZnQgc2hvdWxkIHN0YXRlIHRoYXQg UmVmcmVzaF9JRHMgaGF2ZSBubyBpbXBhY3QgdG8gT1JGIEFERHMgb3IgUkVNT1ZFIGFjdGlvbnMg LSBkb24ndCB5b3UgdGhpbmsgPyZuYnNwOzwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD48 L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxkaXY+DQo8 cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1h cmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIj4mbmJzcDs8bzpwPjwvbzpw Pjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0i bXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFu IGxhbmc9IkVOLVVTIj5JIGFncmVlLiBZZXMsIE9SRiBpcyBraW5kIG9mICZuYnNwOyZxdW90O3Bl cm1hbmVudCBmaWx0ZXImcXVvdDsgb24gdGhlIHBlZXIgd2hpbGUgdGhlIGludGVudCBvZiB0aGlz IGRyYWZ0IGlzIHRvIGhhdmUgYnVuY2ggb2YgJnF1b3Q7c21hbGwgcmVmcmVzaGVzJnF1b3Q7IGdv aW5nIG9uIEAgc2FtZSB0aW1lIHBvc3NpYmx5DQogKGlmIHlvdSByZXF1ZXN0IHRoZSByZWZyZXNo ZXMgZnJvbSBhIGdvb2QgaW1wbGVtZW50YXRpb24gd2hpbGUgbG93LWVuZCBpbXBsZW1lbnRhdGlv bnMgbWF5IHNlcmlhbGl6ZSB0aGUgcmVxdWVzdHMgdG8gc2ltcGxpZnkgaW50ZXJuYWwgbG9naWMg Oy0pLiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz PSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJv dHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiPiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFu PjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0 OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowY20gMGNtIDBjbSA2LjBwdDttYXJnaW4tbGVm dDo0LjhwdDttYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1yaWdodDowY207bWFyZ2luLWJvdHRvbTo1 LjBwdCI+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFy Z2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0i RU4tVVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNl cmlmJnF1b3Q7Ij4mbmJzcDs8L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+PC9vOnA+PC9z cGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28t bWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFu Zz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5z LXNlcmlmJnF1b3Q7Ij5BcyBmYXIgYXMgY3VycmVudCB0eXBlcyB3aHkgbm90IGFkZCByZWd1bGFy L2V4dGVuZGVkIGNvbW11bml0eSA/PC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPjwvbzpw Pjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPGRpdj4NCjxwIGNs YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2lu LWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiPiZuYnNwOzxvOnA+PC9vOnA+PC9z cGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28t bWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFu Zz0iRU4tVVMiPkRpc2N1c3Npb24gY2FtZSB1cC4gRmVlbGluZyB3YXMgaXQncyBhbiBpbW1lZGlh dGUgZW5jcm9hY2ggb24gUlQgdGVycml0b3J5LiBJIGFyZ3VlZCBmb3IgaXQgOy0pICZuYnNwO1Vs dGltYXRlbHksIHRha2luZyBhIG1vcmUgcmVsYXhlZCB2aWV3LCB3ZSBjaG9zZSB0byB3YWl0IGFu ZA0KIHNlZSB3aGF0IHRoZSByZXNwb25zZSBpcyBhbmQgbW9zdCBwcmVzc2luZyB1c2UgY2FzZXMg cGVvcGxlIGJyaW5nIHRvIGl0IGFuZCB0aGVuIHdlIHN0YXJ0IHRvIGRlZmluZSBiaXRzIGFuZCBi eXRlcyBvZiB0aGUgb3B0aW9ucyBzdXBwb3J0ZWQsIHBvc3NpYmx5IGJvcnJvd2luZyB0byBhbiBl eHRlbnQgZnJvbSB0aGUgT1JGIHNwZWNzIDstKSAmbmJzcDtBcyBpbiAmcXVvdDttb3N0IHNpbmNl cmUgZm9ybSBvZiBmbGF0dGVyeSZxdW90OyBhbmQgc3VjaCAuLi4gOy0pJm5ic3A7PG86cD48L286 cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9w LWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIg c3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90Oywm cXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPiZuYnNwOzwvc3Bhbj48c3BhbiBs YW5nPSJFTi1VUyI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIg c3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRv Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6 JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0Qi PltKaWVdIEFjdHVhbGx5IGJlZm9yZSB0aGUgb25lLXRpbWUgT1JGIGRyYWZ0cyB3ZXJlIHN1Ym1p dHRlZCwgd2UgaW5pdGlhbGx5IGNvbnNpZGVyZWQNCiB0byBtYWtlIGl0IGEg4oCcc2VsZWN0aXZl IHJvdXRlIHJlZnJlc2jigJ0gbWVjaGFuaXNtLiBUaGVuIHdlIHJlYWxpemVkIHRoYXQgdGhlIGZp bHRlcnMgd2lsbCBiZSBxdWl0ZSBzaW1pbGFyIHRvIHRoZSBvbmVzIGFscmVhZHkgZGVmaW5lZCBm b3IgT1JGLiBJbiBvcmRlciB0byByZXVzZSB0aGUgT1JGIGZpbHRlcnMsIHdlIHRoZW4gZGVjaWRl ZCB0byBkZWZpbmUgdGhpcyBtZWNoYW5pc20gYXMgbmV3IOKAnG9uZS10aW1l4oCdIE9SRiB0eXBl cy4mbmJzcDsgSnVzdCB0bw0KIHByb3ZpZGUgc29tZSBiYWNrZ3JvdW5kIGluZm9ybWF0aW9uIHNp bmNlIHlvdSBhbHNvIHBsYW4gdG8gcmV1c2UgdGhlIGZvcm1hdCBvZiB0aGUgZXhpc3RpbmcgT1JG IHR5cGVzLg0KPC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+ DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNv LW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1z aXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2Vy aWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+Jm5ic3A7PC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIj48 bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1h cmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9 IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp JnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+QmVzdCByZWdhcmRz LDwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4t Ym90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41 cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7 O2NvbG9yOiMxRjQ5N0QiPkppZTwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD48L286cD48 L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1z by1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBs YW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9yOiM4ODg4ODgiPiZuYnNwOzwvc3Bhbj48c3BhbiBsYW5n PSJFTi1VUyI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9 Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90 dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9yOiM4ODg4ODgiPi0t IHRvbnkmbmJzcDs8L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+PC9vOnA+PC9zcGFuPjwv cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2lu LXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4t VVMiIHN0eWxlPSJjb2xvcjojODg4ODg4Ij4mbmJzcDs8L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMi PjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0K PC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1 dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIj48YnI+DQo8 YnIgY2xlYXI9ImFsbCI+DQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9 Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90 dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyI+Jm5ic3A7PG86cD48L286cD48L3NwYW4+ PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3At YWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIj4t LQ0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9 Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90 dG9tLWFsdDphdXRvIj48aT48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZTo5LjVw dDtmb250LWZhbWlseTomcXVvdDtHZW9yZ2lhJnF1b3Q7LCZxdW90O3NlcmlmJnF1b3Q7Ij5XZeKA mXZlIGhlYXJkIHRoYXQgYSBtaWxsaW9uIG1vbmtleXMgYXQgYSBtaWxsaW9uIGtleWJvYXJkcyBj b3VsZCBwcm9kdWNlIHRoZSBjb21wbGV0ZSB3b3JrcyBvZiBTaGFrZXNwZWFyZTsNCiBub3csIHRo YW5rcyB0byB0aGUgSW50ZXJuZXQsIHdlIGtub3cgdGhhdCBpcyBub3QgdHJ1ZS48L3NwYW4+PC9p PjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+ DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNv LW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1z aXplOjkuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90OywmcXVvdDtz ZXJpZiZxdW90OyI+4oCUUm9iZXJ0IFdpbGVuc2t5PC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIj48 bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwv ZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g bGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+ DQo8L2JvZHk+DQo8L2h0bWw+DQo= --_000_76CD132C3ADEF848BD84D028D243C92774EEFBE8NKGEML515MBXchi_-- From nobody Wed Jul 20 00:46:24 2016 Return-Path: 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 3B70C12D9B9 for ; Wed, 20 Jul 2016 00:46:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.507 X-Spam-Level: X-Spam-Status: No, score=-5.507 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, 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 T_IXM9TwTZzz for ; Wed, 20 Jul 2016 00:46:17 -0700 (PDT) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 357EC12D17A for ; Wed, 20 Jul 2016 00:46:16 -0700 (PDT) Received: from 172.18.7.190 (EHLO lhreml701-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CNZ17804; Wed, 20 Jul 2016 07:46:13 +0000 (GMT) Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml701-cah.china.huawei.com (10.201.5.93) with Microsoft SMTP Server (TLS) id 14.3.235.1; Wed, 20 Jul 2016 08:46:03 +0100 Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0235.001; Wed, 20 Jul 2016 15:45:57 +0800 From: "Dongjie (Jimmy)" To: "Keyur Patel (keyupate)" , Robert Raszuk Thread-Topic: [Idr] Fwd: Slot request in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00.txt Thread-Index: AQHR4aVU83cQxXd4nUuy17dJqjAuSaAgQJlw//+FoACAAAdOAIABIFDQ Date: Wed, 20 Jul 2016 07:45:57 +0000 Message-ID: <76CD132C3ADEF848BD84D028D243C92774EEFC10@NKGEML515-MBX.china.huawei.com> References: <76CD132C3ADEF848BD84D028D243C92774EEF7CF@NKGEML515-MBX.china.huawei.com> In-Reply-To: Accept-Language: en-US, zh-CN Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.200.218.207] Content-Type: multipart/alternative; boundary="_000_76CD132C3ADEF848BD84D028D243C92774EEFC10NKGEML515MBXchi_" MIME-Version: 1.0 X-CFilter-Loop: Reflected X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020204.578F2C46.0073, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32 X-Mirapoint-Loop-Id: 30fd6b1a07a3ac00d82fc45c67e61a7b Archived-At: Cc: idr wg Subject: Re: [Idr] Fwd: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jul 2016 07:46:22 -0000 --_000_76CD132C3ADEF848BD84D028D243C92774EEFC10NKGEML515MBXchi_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Keyur, Please see my comments inline with [Jie2]: From: Keyur Patel (keyupate) [mailto:keyupate@cisco.com] Sent: Wednesday, July 20, 2016 6:18 AM To: Robert Raszuk; Dongjie (Jimmy) Cc: idr wg Subject: Re: [Idr] Fwd: Slot request in IDR to present https://www.ietf.org= /internet-drafts/draft-idr-bgp-route-refresh-options-00.txt Robert, Dongjie, Comments inlined #Keyur From: Robert Raszuk > Date: Tuesday, July 19, 2016 at 2:52 PM To: "Dongjie (Jimmy)" > Cc: idr wg > Subject: Re: [Idr] Fwd: Slot request in IDR to present https://www.ietf.org= /internet-drafts/draft-idr-bgp-route-refresh-options-00.txt Hi Jie, To me what is perhaps missing is just a new draft to define *Route Type* OR= F to address some of those EVPN new NLRI encodings. #Keyur: ORFs are permanent filters. We wanted to decouple the transaction b= ased filters (one time per refresh) from the permanent filters and hence ch= ose to modify refresh message as opposed to an ORF. [Jie2]: This was also my understanding in the beginning of writing the one-= time orf drafts. However since you need traffic filters for this "selective= refresh", you will find out it is already there with ORF, then you will wa= nt to reuse the filters. Actually it is something between the traditional r= efresh and the traditional ORF, IMO the name does not really matter, the i= mportant thing is we can reuse what already exists. I am not that much convinced if one time ORF is needed as you are free to I= NSTALL and REMOVE ORF effectively producing one time behavior. #Keyur: Ack. Also existing Enhanced Route Refresh should work with ORF too. #Keyur: There are modifications needed if the refresh is going to be for se= lective prefixes only. Furthermore, if we want to support multiple concurre= nt selective refreshes then the changes needed are very much along the line= s of the solution suggested in the draft. [Jie2] For the concurrent refresh part, could you elaborate in which case i= t will be needed? The draft says "The BGP speaker responding to the route = refresh requests MAY perform the refreshes in parallel", do you mean the ro= ute updates for different selective refresh requests may be interleaved? Best regards Jie Regards, Keyur Many thx, R. On Tue, Jul 19, 2016 at 11:47 PM, Dongjie (Jimmy) > wrote: Hi Tony, Please see some comments inline with [Jie]: From: Idr [mailto:idr-bounces@ietf.org] On Beh= alf Of Tony Przygienda Sent: Tuesday, July 19, 2016 6:04 PM To: Robert Raszuk; idr wg Subject: [Idr] Fwd: Slot request in IDR to present https://www.ietf.org/int= ernet-drafts/draft-idr-bgp-route-refresh-options-00.txt Resending ... ---------- Forwarded message ---------- From: Tony Przygienda > Date: Mon, Jul 11, 2016 at 3:04 PM Subject: Re: [Idr] Slot request in IDR to present https://www.ietf.org/inte= rnet-drafts/draft-idr-bgp-route-refresh-options-00.txt To: Robert Raszuk > Cc: idr wg > On Mon, Jul 11, 2016 at 1:47 PM, Robert Raszuk > wrote: Hi Tony, Hey Robert, thanks for chiming in. Good questions. I speak here for myself,= other authors of the draft may have differing opinions. Can you clarify what is the expected behaviour as far as per peer filter-li= st when you negotiate both Refresh with options, ORF and RTC ? Note that OR= F also includes recent extension as described in RFC7543 - would all of tho= se be always a logical AND towards a peer which pushed those ? We didn't discuss that one through but the only logical conclusion for me i= s that the ORF/CP-ORF installed are respected (i.e. it's an implicit AND). = I see ORF as statefull, remote-pushed policy on the peer that is not being = flipped around all the time (albeit AFAIR there were some attempts @ non-pe= rsistent, one shot ORF but that ended up expiring?) [Jie] I think the attempts you mentioned here are the one-time ORF drafts: = draft-zeng-idr-one-time-prefix-orf and draft-dong-idr-one-time-ext-communi= ty-orf. After several revisions, these drafts got expired due to lack of re= quirements at that time. If people found some new use cases of these kinds = of mechanisms, the authors would be happy to bring them back to discussion. The motivation for this work were scenarios where a single-shot refresh is = needed, actually concurrent bunch of those based on configuration changes, = peer having dropped received routes based on specs (A-D), in policy changes= , joining VPNs, EVIs and so on. Putting ORF on a peer, refresh and remove O= RFs is significantly heavier process that may interfere on top with normal = update process going on and needs to be done one-by-one (since you have to = wait for single BoRR/EoRR pair) unless one is very smart about combining OR= F possibly & playing with the DEFER/IMMEDIATEs. As we indicated, if the AFI= /SAFI is covered by RTC and RTC is supported & one is willing to configure = RTs for each subset of routes that may need refreshing, RT will be doing th= e same job just fine. [Jie] The motivations look similar to what we described for the one-time OR= F drafts. Would you always carry ORF with separate Refresh_ID value ? Yes, Refresh-ID# is strictly monotonic so there is never a misunderstanding= WHAT the BoRR belongs to. Observe that the draft does NOT mandate that a r= equest MUST be followed by according BoRR, only that BoRRs must follow same= sequence as requests (i.e. are also strictly monotonic). However, we shoul= d probably specify that options _and_ ORF can NOT be mixed in the same type= #3 message but it's either one or the other (and anything else is error). = This will allow ORF operations like today + benefit of the Refresh ID# on = the BoRR so the IMMEDIATE can go on @ the same time as another request with= higher Refresh ID# (de facto we allow multiple parallel refreshes as you s= ee). In case of DEFER there will be simply no BoRR for it. 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 i= nstalled 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 h= ave no impact to ORF ADDs or REMOVE actions - don't you think ? I agree. Yes, ORF is kind of "permanent filter" on the peer while the inte= nt of this draft is to have bunch of "small refreshes" going on @ same time= possibly (if you request the refreshes from a good implementation while lo= w-end implementations may serialize the requests to simplify internal logic= ;-). As far as current types why not add regular/extended community ? Discussion came up. Feeling was it's an immediate encroach on RT territory.= I argued for it ;-) Ultimately, taking a more relaxed view, we chose to w= ait and see what the response is and most pressing use cases people bring t= o it and then we start to define bits and bytes of the options supported, p= ossibly borrowing to an extent from the ORF specs ;-) As in "most sincere = form of flattery" and such ... ;-) [Jie] Actually before the one-time ORF drafts were submitted, we initially = considered to make it a "selective route refresh" mechanism. Then we realiz= ed that the filters will be quite similar to the ones already defined for O= RF. In order to reuse the ORF filters, we then decided to define this mecha= nism as new "one-time" ORF types. Just to provide some background informat= ion since you also plan to reuse the format of the existing ORF types. Best regards, Jie -- tony -- We've heard that a million monkeys at a million keyboards could produce the= complete works of Shakespeare; now, thanks to the Internet, we know that i= s not true. -Robert Wilensky --_000_76CD132C3ADEF848BD84D028D243C92774EEFC10NKGEML515MBXchi_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi Keyur,

 = ;

Please see= my comments inline with [Jie2]:

 = ;

From: Keyur Patel (keyupate) [mailto:keyupate@cisco.com]
Sent: Wednesday, July 20, 2016 6:18 AM
To: Robert Raszuk; Dongjie (Jimmy)
Cc: idr wg
Subject: Re: [Idr] Fwd: Slot request in IDR to present https://www.i= etf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00.txt

 

Robert, Dong= jie,

 <= /o:p>

Comments inl= ined #Keyur

 <= /o:p>

From: Robert Raszuk <robert@raszuk.net>
Date: Tuesday, July 19, 2016 at 2:52 PM
To: "Dongjie (Jimmy)" <jie.dong@huawei.com>
Cc: idr wg <idr@ietf.org><= br> Subject: Re: [Idr] Fwd: Slot request in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00= .txt

 <= /o:p>

Hi Jie,

 

To me what is perhaps missing i= s just a new draft to define *Route Type* ORF to address some of those EVPN= new NLRI encodings.

 <= /o:p>

#Keyur: ORFs= are permanent filters. We wanted to decouple the transaction based filters= (one time per refresh) from the permanent filters and hence chose to modify refresh message as opposed to an ORF. 

 = ;

[Jie2]: Th= is was also my understanding in the beginning of writing the one-time orf d= rafts. However since you need traffic filters for this “selective refresh”, you will find out it is already there with ORF, then you w= ill want to reuse the filters. Actually it is something between the traditi= onal refresh and the traditional ORF,  IMO the name does not really ma= tter, the important thing is we can reuse what already exists.

 

I am not that much convinced if= one time ORF is needed as you are free to INSTALL and REMOVE ORF effective= ly producing one time behavior.

 <= /o:p>

#Keyur: Ack.=  

 <= /o:p>

Also existing Enhanced Route Re= fresh should work with ORF too. 

 <= /o:p>

#Keyur: Ther= e are modifications needed if the refresh is going to be for selective pref= ixes only. Furthermore, if we want to support multiple concurrent selective refreshes then the changes needed are very much along the lines = of the solution suggested in the draft.

 = ;

[Jie2] For= the concurrent refresh part, could you elaborate in which case it will be = needed? The draft says “The BGP speaker responding to  the route refresh requests MAY perform the refreshes in parallel”, do yo= u mean the route updates for different selective refresh requests may be in= terleaved?

 = ;

Best regar= ds

Jie

 <= /o:p>

Regards,

Keyur <= o:p>

 <= /o:p>

 <= /o:p>

 

Many thx,

R.

 

 

 

 <= /o:p>

On Tue, Jul = 19, 2016 at 11:47 PM, Dongjie (Jimmy) <jie.dong@huawei.com> wrote:

Hi Tony,

 

Please see some comments= inline with [Jie]:<= /o:p>

 

From: Idr [mailto:idr-= bounces@ietf.org] On Behalf Of Tony Przygienda
Sent: Tuesday, July 19, 2016 6:04 PM
To: Robert Raszuk; idr wg
Subject: [Idr] Fwd: Slot request in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00= .txt

 

Resending ... 

 

---------- Forwarded message = ----------
From: Tony Przygienda <tonysietf@gmail.com>
Date: Mon, Jul 11, 2016 at 3:04 PM
Subject: Re: [Idr] Slot request in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00= .txt
To: Robert Raszuk <robert@raszuk.net>
Cc: idr wg <idr@ietf.o= rg>

 

 

On Mon, Jul 11, 2016 at= 1:47 PM, Robert Raszuk <robert@raszuk.net> wrote:

Hi Tony,

 

Hey Robert, thanks for = chiming in. Good questions. I speak here for myself, other authors of the d= raft may have differing opinions. 

 

 

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

 

We didn't discuss that = one through but the only logical conclusion for me is that the ORF/CP-ORF i= nstalled are respected (i.e. it's an implicit AND). I see ORF as statefull, remote-pushed policy on the peer that is not= being flipped around all the time (albeit AFAIR there were some attempts @= non-persistent, one shot ORF but that ended up expiring?)

 

[Jie] I think the attemp= ts you mentioned here are the one-time ORF drafts: draft-zeng-idr-one-time-= prefix-orf  and draft-dong-idr-one-time-ext-community-orf. After several revisio= ns, these drafts got expired due to lack of requirements at that time. If p= eople found some new use cases of these kinds of mechanisms, the authors wo= uld be happy to bring them back to discussion.

 

The motivation for this= work were scenarios where a single-shot refresh is needed, actually concur= rent bunch of those based on configuration changes, peer having dropped received routes based on specs (A-D), in poli= cy changes, joining VPNs, EVIs and so on. Putting ORF on a peer, refresh an= d remove ORFs is significantly heavier process that may interfere on top wi= th normal update process going on and needs to be done one-by-one (since you have to wait for single BoRR/Eo= RR pair) unless one is very smart about combining ORF possibly & playin= g with the DEFER/IMMEDIATEs. As we indicated, if the AFI/SAFI is covered by= RTC and RTC is supported & one is willing to configure RTs for each subset of routes that may need refreshing, RT wi= ll be doing the same job just fine. 

 

[Jie] The motivations lo= ok similar to what we described for the one-time ORF drafts.

 

 

Would you always carry ORF with separate Refr= esh_ID value ? =

 

Yes, Refresh-ID# is str= ictly monotonic so there is never a misunderstanding WHAT the BoRR belongs = to. Observe that the draft does NOT mandate that a request MUST be followed by according BoRR, only that BoRRs must fo= llow same sequence as requests (i.e. are also strictly monotonic). However,= we should probably specify that options _and_ ORF can NOT be mixed in the = same type #3 message but it's either one or the other (and anything else is error). This will allow ORF operati= ons like today + benefit of the Refresh ID#  on the BoRR so the IM= MEDIATE can go on @ the same time as another request with higher Refresh ID= # (de facto we allow multiple parallel refreshes as you see).  In case of DEFER there will be simply no BoRR for it.&n= bsp;

 

 

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

 

I agree. Yes, ORF is ki= nd of  "permanent filter" on the peer while the intent of th= is draft is to have bunch of "small refreshes" going on @ same time possibly (if you request the refreshes from a good implementat= ion while low-end implementations may serialize the requests to simplify in= ternal logic ;-). 

 

 

As far as current types why not add regular/e= xtended community ?<= /o:p>

 

Discussion came up. Fee= ling was it's an immediate encroach on RT territory. I argued for it ;-) &n= bsp;Ultimately, taking a more relaxed view, we chose to wait and see what the response is and most pressing use cases peo= ple bring to it and then we start to define bits and bytes of the options s= upported, possibly borrowing to an extent from the ORF specs ;-)  As i= n "most sincere form of flattery" and such ... ;-) 

 

[Jie] Actually before th= e one-time ORF drafts were submitted, we initially considered to make it a “selective route refresh” mechanism. Then we real= ized that the filters will be quite similar to the ones already defined for= ORF. In order to reuse the ORF filters, we then decided to define this mec= hanism as new “one-time” ORF types.  Just to provide some background information since you also plan to reuse the forma= t of the existing ORF types.

 

Best regards,

Jie

 

-- tony <= span lang=3D"EN-US" style=3D"color:black">

 



 

--

We’ve heard that a mill= ion monkeys at a million keyboards could produce the complete works of Shakespeare; now, thanks to the Internet, we know that is not true.

—= Robert Wilensky

 <= /o:p>

--_000_76CD132C3ADEF848BD84D028D243C92774EEFC10NKGEML515MBXchi_-- From nobody Wed Jul 20 14:05:44 2016 Return-Path: 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 D05F912D848 for ; Wed, 20 Jul 2016 14:05:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -15.807 X-Spam-Level: X-Spam-Status: No, score=-15.807 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 kBdudPHmDEqs for ; Wed, 20 Jul 2016 14:05:40 -0700 (PDT) Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0063A12D805 for ; Wed, 20 Jul 2016 14:05:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=32747; q=dns/txt; s=iport; t=1469048739; x=1470258339; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=4fGakmnwthm3X1n50bLrbx7+cTyov24JmRo8xYJqGno=; b=iF9jPkV/82pQmX0tx7KqQ3DJGd0KzqAs6TY76YVpKQ0yfZZSJsyRECHN sYUhv6VLH5cV00JW+i/2FD6uDNfQ8/Qbx6OuXnDLVrOBHeuy94XRj5NYy A1Kex+vWBdWL+OlAEAQLA3ctoHP85ML8ceCj5DkH6ty/QB5peUZxRXol4 o=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AlAgDg5o9X/4UNJK1dgnFOVnwGrD6MG?= =?us-ascii?q?4F7JIV2AoE1OBQBAQEBAQEBZSeEXAEBBXMGEAIBCBEDAQEBIQECBAchERQJCAI?= =?us-ascii?q?EDgUUBQKHewMXDrkIDYQJAQEBAQEBAQEBAQEBAQEBAQEBAQEBFwWGKoRNgSKBI?= =?us-ascii?q?YIdFoUlBYgXCIYle4kzNAGJDYM2gh6BbIRZiHSGX4FGh3oBHjaCCB8XgTVuAYY?= =?us-ascii?q?nfwEBAQ?= X-IronPort-AV: E=Sophos;i="5.28,396,1464652800"; d="scan'208,217";a="300380105" Received: from alln-core-11.cisco.com ([173.36.13.133]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 20 Jul 2016 21:05:38 +0000 Received: from XCH-RTP-019.cisco.com (xch-rtp-019.cisco.com [64.101.220.159]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id u6KL5bwZ031825 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 20 Jul 2016 21:05:38 GMT Received: from xch-rtp-017.cisco.com (64.101.220.157) by XCH-RTP-019.cisco.com (64.101.220.159) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 20 Jul 2016 17:05:37 -0400 Received: from xch-rtp-017.cisco.com ([64.101.220.157]) by XCH-RTP-017.cisco.com ([64.101.220.157]) with mapi id 15.00.1210.000; Wed, 20 Jul 2016 17:05:37 -0400 From: "Keyur Patel (keyupate)" To: Robert Raszuk Thread-Topic: [Idr] Fwd: Slot request in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00.txt Thread-Index: AQHR4gt3jXzNsYcN6ECcWcNExZ/YjA== Date: Wed, 20 Jul 2016 21:05:37 +0000 Message-ID: References: <76CD132C3ADEF848BD84D028D243C92774EEF7CF@NKGEML515-MBX.china.huawei.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.4.9.150325 x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.154.161.115] Content-Type: multipart/alternative; boundary="_000_D3B5343D474BDkeyupateciscocom_" MIME-Version: 1.0 Archived-At: Cc: idr wg Subject: Re: [Idr] Fwd: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jul 2016 21:05:43 -0000 --_000_D3B5343D474BDkeyupateciscocom_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Robert, One interesting use case is with EVPN address family where a new route-type= is introduced without a capability. A PE may have had safi enabled but no= t have accepted its route-type (or set of route-types) all mapping to a sam= e RT. A transactional filter attempts to solve it. We can clarify in the next revision of the draft. One more comment inlined #Keyur From: Robert Raszuk > Date: Tuesday, July 19, 2016 at 3:29 PM To: Keyur Patel > Cc: "Dongjie (Jimmy)" >, id= r wg > Subject: Re: [Idr] Fwd: Slot request in IDR to present https://www.ietf.org= /internet-drafts/draft-idr-bgp-route-refresh-options-00.txt Hi Keyur, The missing part seems to be justification if we really need "transaction b= ased filters" as opposed to simply having permanent ones. What real problem "transaction based filters" solve ? IMO the draft needs t= o state it clearly. The other point is that "permanent" are not really permanent anyway .. they= are installed from update to withdraw of a given filter - regardless what = filtering mechanism you choose (ORF, RTC, XYZ ...). And if you go with the = notion that permanent are sufficient the entire aparatus allowing you to ha= ve concurrent route refresh requests in flight goes away :) #Keyur: Ack your right. My reference to a permanent filter was in context o= f a session life time and I agree with you that it could be modified or wit= hdrawn at any given time. I was trying to differentiate it from transaction= al filters. Regards, Keyur Thx, r. On Wed, Jul 20, 2016 at 12:18 AM, Keyur Patel (keyupate) > wrote: Robert, Dongjie, Comments inlined #Keyur From: Robert Raszuk > Date: Tuesday, July 19, 2016 at 2:52 PM To: "Dongjie (Jimmy)" > Cc: idr wg > Subject: Re: [Idr] Fwd: Slot request in IDR to present https://www.ietf.org= /internet-drafts/draft-idr-bgp-route-refresh-options-00.txt Hi Jie, To me what is perhaps missing is just a new draft to define *Route Type* OR= F to address some of those EVPN new NLRI encodings. #Keyur: ORFs are permanent filters. We wanted to decouple the transaction b= ased filters (one time per refresh) from the permanent filters and hence ch= ose to modify refresh message as opposed to an ORF. I am not that much convinced if one time ORF is needed as you are free to I= NSTALL and REMOVE ORF effectively producing one time behavior. #Keyur: Ack. Also existing Enhanced Route Refresh should work with ORF too. #Keyur: There are modifications needed if the refresh is going to be for se= lective prefixes only. Furthermore, if we want to support multiple concurre= nt selective refreshes then the changes needed are very much along the line= s of the solution suggested in the draft. Regards, Keyur Many thx, R. On Tue, Jul 19, 2016 at 11:47 PM, Dongjie (Jimmy) > wrote: Hi Tony, Please see some comments inline with [Jie]: From: Idr [mailto:idr-bounces@ietf.org] On Beh= alf Of Tony Przygienda Sent: Tuesday, July 19, 2016 6:04 PM To: Robert Raszuk; idr wg Subject: [Idr] Fwd: Slot request in IDR to present https://www.ietf.org/int= ernet-drafts/draft-idr-bgp-route-refresh-options-00.txt Resending ... ---------- Forwarded message ---------- From: Tony Przygienda > Date: Mon, Jul 11, 2016 at 3:04 PM Subject: Re: [Idr] Slot request in IDR to present https://www.ietf.org/inte= rnet-drafts/draft-idr-bgp-route-refresh-options-00.txt To: Robert Raszuk > Cc: idr wg > On Mon, Jul 11, 2016 at 1:47 PM, Robert Raszuk > wrote: Hi Tony, Hey Robert, thanks for chiming in. Good questions. I speak here for myself,= other authors of the draft may have differing opinions. Can you clarify what is the expected behaviour as far as per peer filter-li= st when you negotiate both Refresh with options, ORF and RTC ? Note that OR= F also includes recent extension as described in RFC7543 - would all of tho= se be always a logical AND towards a peer which pushed those ? We didn't discuss that one through but the only logical conclusion for me i= s that the ORF/CP-ORF installed are respected (i.e. it's an implicit AND). = I see ORF as statefull, remote-pushed policy on the peer that is not being = flipped around all the time (albeit AFAIR there were some attempts @ non-pe= rsistent, one shot ORF but that ended up expiring?) [Jie] I think the attempts you mentioned here are the one-time ORF drafts: = draft-zeng-idr-one-time-prefix-orf and draft-dong-idr-one-time-ext-communi= ty-orf. After several revisions, these drafts got expired due to lack of re= quirements at that time. If people found some new use cases of these kinds = of mechanisms, the authors would be happy to bring them back to discussion. The motivation for this work were scenarios where a single-shot refresh is = needed, actually concurrent bunch of those based on configuration changes, = peer having dropped received routes based on specs (A-D), in policy changes= , joining VPNs, EVIs and so on. Putting ORF on a peer, refresh and remove O= RFs is significantly heavier process that may interfere on top with normal = update process going on and needs to be done one-by-one (since you have to = wait for single BoRR/EoRR pair) unless one is very smart about combining OR= F possibly & playing with the DEFER/IMMEDIATEs. As we indicated, if the AFI= /SAFI is covered by RTC and RTC is supported & one is willing to configure = RTs for each subset of routes that may need refreshing, RT will be doing th= e same job just fine. [Jie] The motivations look similar to what we described for the one-time OR= F drafts. Would you always carry ORF with separate Refresh_ID value ? Yes, Refresh-ID# is strictly monotonic so there is never a misunderstanding= WHAT the BoRR belongs to. Observe that the draft does NOT mandate that a r= equest MUST be followed by according BoRR, only that BoRRs must follow same= sequence as requests (i.e. are also strictly monotonic). However, we shoul= d probably specify that options _and_ ORF can NOT be mixed in the same type= #3 message but it's either one or the other (and anything else is error). = This will allow ORF operations like today + benefit of the Refresh ID# on = the BoRR so the IMMEDIATE can go on @ the same time as another request with= higher Refresh ID# (de facto we allow multiple parallel refreshes as you s= ee). In case of DEFER there will be simply no BoRR for it. 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 i= nstalled 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 h= ave no impact to ORF ADDs or REMOVE actions - don't you think ? I agree. Yes, ORF is kind of "permanent filter" on the peer while the inte= nt of this draft is to have bunch of "small refreshes" going on @ same time= possibly (if you request the refreshes from a good implementation while lo= w-end implementations may serialize the requests to simplify internal logic= ;-). As far as current types why not add regular/extended community ? Discussion came up. Feeling was it's an immediate encroach on RT territory.= I argued for it ;-) Ultimately, taking a more relaxed view, we chose to w= ait and see what the response is and most pressing use cases people bring t= o it and then we start to define bits and bytes of the options supported, p= ossibly borrowing to an extent from the ORF specs ;-) As in "most sincere = form of flattery" and such ... ;-) [Jie] Actually before the one-time ORF drafts were submitted, we initially = considered to make it a "selective route refresh" mechanism. Then we realiz= ed that the filters will be quite similar to the ones already defined for O= RF. In order to reuse the ORF filters, we then decided to define this mecha= nism as new "one-time" ORF types. Just to provide some background informat= ion since you also plan to reuse the format of the existing ORF types. Best regards, Jie -- tony -- We've heard that a million monkeys at a million keyboards could produce the= complete works of Shakespeare; now, thanks to the Internet, we know that i= s not true. -Robert Wilensky --_000_D3B5343D474BDkeyupateciscocom_ Content-Type: text/html; charset="iso-8859-1" Content-ID: <7E388603B23C46448291FF55CDD43A30@emea.cisco.com> Content-Transfer-Encoding: quoted-printable
Hi Robert,

One interesting use case is with EVPN address family where a new route= -type is introduced without a capability.  A PE may have had safi enab= led but not have accepted its route-type (or set of route-types) all mappin= g to a same RT. A transactional filter attempts to solve it.

We can clarify in the next revision of the draft.

One more comment inlined #Keyur

From: Robert Raszuk <robert@raszuk.net>
Date: Tuesday, July 19, 2016 at 3:2= 9 PM
To: Keyur Patel <keyupate@cisco.com>
Cc: "Dongjie (Jimmy)" <= ;jie.dong@huawei.com>, idr wg= <idr@ietf.org>
Subject: Re: [Idr] Fwd: Slot reques= t in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00= .txt

Hi Keyur,

The missing part seems to be justification if we really need "transact= ion based filters" as opposed to simply having permanent ones. 

What real problem "transaction based filters" solve ? IMO the dra= ft needs to state it clearly. 

The other point is that "permanent" are not really permanent anyw= ay .. they are installed from update to withdraw of a given filter - regard= less what filtering mechanism you choose (ORF, RTC, XYZ ...). And if you go= with the notion that permanent are sufficient the entire aparatus allowing you to have concurrent route refresh requests= in flight goes away :)

#Keyur: Ack your right. My reference to a permanent filter was in cont= ext of a session life time and I agree with you that it could be modified o= r withdrawn at any given time. I was trying to differentiate it from transa= ctional filters.

Regards,
Keyur

Thx,
r.


On Wed, Jul 20, 2016 at 12:18 AM, Keyur Patel (k= eyupate) <keyupate@cisco.com> wrote:
Robert, Dongjie,

Comments inlined #Keyur

From: Robert Raszuk <robert@raszuk.net>
Date: Tuesday, July 19, 2016 at 2:5= 2 PM
To: "Dongjie (Jimmy)" <= ;jie.dong@huawei.c= om>
Cc: idr wg <idr@ietf.org>
Subject: Re: [Idr] Fwd: Slot reques= t in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00= .txt

Hi Jie,

To me what is perhaps missing is just a new draft to define *Route Type* OR= F to address some of those EVPN new NLRI encodings.

#Keyur: ORFs are permanent filters. We wanted to decouple the transact= ion based filters (one time per refresh) from the permanent filters and hen= ce chose to modify refresh message as opposed to an ORF. 

I am not that much convinced if one time ORF is needed as you are free to I= NSTALL and REMOVE ORF effectively producing one time behavior.

#Keyur: Ack. 

Also existing Enhanced Route Refresh should work with ORF too. 

#Keyur: There are modifications needed if the refresh is going to be f= or selective prefixes only. Furthermore, if we want to support multiple con= current selective refreshes then the changes needed are very much along the= lines of the solution suggested in the draft.

Regards,
Keyur 



Many thx,
R.




On Tue, Jul 19, 2016 at 11:47 PM, Dongjie (Jimmy= ) <jie.dong@huawe= i.com> wrote:

Hi Tony,

 

Please see some co= mments inline with [Jie]:

 

From: Idr [mailto:idr-bounces@ietf.org= ] On Behalf Of Tony Przygienda
Sent: Tuesday, July 19, 2016 6:04 PM
To: Robert Raszuk; idr wg
Subject: [Idr] Fwd: Slot request in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00= .txt

 

Resending ... 

 

= ---------- Forwarded message ----------
From: Tony Przygienda <tonysietf@gmail.com>
Date: Mon, Jul 11, 2016 at 3:04 PM
Subject: Re: [Idr] Slot request in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00= .txt
To: Robert Raszuk <robert@raszuk.net>
Cc: idr wg <idr@ietf.o= rg>

 

 

On Mon, Jul 11, 2016 at 1:47 PM= , Robert Raszuk <= robert@raszuk.net> wrote:

Hi Tony,

 

Hey Robert, thanks for chiming = in. Good questions. I speak here for myself, other authors of the draft may= have differing opinions. 

 

 

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

 

We didn't discuss that one thro= ugh but the only logical conclusion for me is that the ORF/CP-ORF installed= are respected (i.e. it's an implicit AND). I see ORF as statefull, remote-= pushed policy on the peer that is not being flipped around all the time (albeit AFAIR there were some attempts @= non-persistent, one shot ORF but that ended up expiring?)

 

[Jie] I think the = attempts you mentioned here are the one-time ORF drafts: draft-zeng-idr-one= -time-prefix-orf  and draft-dong-idr-one-time-ext-community-orf. After several revisions, these drafts got expired due to lack of requireme= nts at that time. If people found some new use cases of these kinds of mech= anisms, the authors would be happy to bring them back to discussion.=

 

The motivation for this work we= re scenarios where a single-shot refresh is needed, actually concurrent bun= ch of those based on configuration changes, peer having dropped received ro= utes based on specs (A-D), in policy changes, joining VPNs, EVIs and so on. Putting ORF on a peer, refresh and = remove ORFs is significantly heavier process that may interfere on top with= normal update process going on and needs to be done one-by-one (since you = have to wait for single BoRR/EoRR pair) unless one is very smart about combining ORF possibly & playing = with the DEFER/IMMEDIATEs. As we indicated, if the AFI/SAFI is covered by R= TC and RTC is supported & one is willing to configure RTs for each subs= et of routes that may need refreshing, RT will be doing the same job just fine. 

 

[Jie] The motivati= ons look similar to what we described for the one-time ORF drafts.

 

 

Would you always carry ORF with separate Refresh_ID value ? = ;

 

Yes, Refresh-ID# is strictly mo= notonic so there is never a misunderstanding WHAT the BoRR belongs to. Obse= rve that the draft does NOT mandate that a request MUST be followed by acco= rding BoRR, only that BoRRs must follow same sequence as requests (i.e. are also strictly monotonic). However, we = should probably specify that options _and_ ORF can NOT be mixed in the same= type #3 message but it's either one or the other (and anything else is err= or). This will allow ORF operations like today + benefit of the Refresh ID#  on the BoRR so the IMMED= IATE can go on @ the same time as another request with higher Refresh ID# (= de facto we allow multiple parallel refreshes as you see).  In case of= DEFER there will be simply no BoRR for it. 

 

 

If one requests full Adj_RIB_Out in the new model and sends refr= esh message with new refresh_id and no options however there are ORF entrie= s 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 ? 

 

I agree. Yes, ORF is kind of &n= bsp;"permanent filter" on the peer while the intent of this draft= is to have bunch of "small refreshes" going on @ same time possi= bly (if you request the refreshes from a good implementation while low-end implementations may serialize the requests to simplify inter= nal logic ;-). 

 

 

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

 

Discussion came up. Feeling was= it's an immediate encroach on RT territory. I argued for it ;-)  Ulti= mately, taking a more relaxed view, we chose to wait and see what the respo= nse is and most pressing use cases people bring to it and then we start to define bits and bytes of the options supp= orted, possibly borrowing to an extent from the ORF specs ;-)  As in &= quot;most sincere form of flattery" and such ... ;-) 

 

[Jie] Actually bef= ore the one-time ORF drafts were submitted, we initially considered to make= it a “selective route refresh” mechanism. Then we realized that the filters will be quite similar to the ones alread= y defined for ORF. In order to reuse the ORF filters, we then decided to de= fine this mechanism as new “one-time” ORF types.  Just to = provide some background information since you also plan to reuse the format of the existing ORF types. <= /p>

 

Best regards,

Jie<= /span>

=  

-- tony=  

 <= u>



 

--

We’ve heard that a million monkeys at a = million keyboards could produce the complete works of Shakespeare; now, tha= nks to the Internet, we know that is not true.

—Robert Wilensky



--_000_D3B5343D474BDkeyupateciscocom_-- From nobody Wed Jul 20 14:11:52 2016 Return-Path: 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 95F6012D1B3 for ; Wed, 20 Jul 2016 14:11:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -15.807 X-Spam-Level: X-Spam-Status: No, score=-15.807 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 6oNRVjUiPe_5 for ; Wed, 20 Jul 2016 14:11:47 -0700 (PDT) Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A9EC812D7CD for ; Wed, 20 Jul 2016 14:11:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=45341; q=dns/txt; s=iport; t=1469049107; x=1470258707; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=J3126QlCeoK/DJ+ELyh54x/gAxgP63D//SzRvchzRuc=; b=HQXCpu7sju2WPBxc55dybi6Mx05/6UWlRYXDDK48uQktteHCiy8RlODA yNNN1C1nCn5x3RTbYcM1nsLPbxNEZvMW5ZDS1svK+5PxouphGY4VCTUsq qI5JpWQCNL4h4NfJugXVeiEjXOoLQVPQBQkYcLPuvEUlrYDGGYTfog3cA s=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AlAgCi549X/40NJK1dgnFOVnwGrD6MG?= =?us-ascii?q?4F7JIV2AoE1OBQBAQEBAQEBZSeEXAEBBS1GBhACAQgRAwEBASEBAgQHIREUCQg?= =?us-ascii?q?CBAENBRQHh3sDFw65EQ2ECQEBAQEBAQEBAQEBAQEBAQEBAQEBARcFhiqETYEig?= =?us-ascii?q?SGCHRaFJQWIFwiFbIE0iTM0AYkNgzaCHoFshFmIdIZfgUaHegEeNoIIHxeBNW4?= =?us-ascii?q?Bhid/AQEB?= X-IronPort-AV: E=Sophos;i="5.28,396,1464652800"; d="scan'208,217";a="131799610" Received: from alln-core-8.cisco.com ([173.36.13.141]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 20 Jul 2016 21:11:46 +0000 Received: from XCH-RTP-019.cisco.com (xch-rtp-019.cisco.com [64.101.220.159]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id u6KLBjFm009319 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 20 Jul 2016 21:11:45 GMT Received: from xch-rtp-017.cisco.com (64.101.220.157) by XCH-RTP-019.cisco.com (64.101.220.159) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 20 Jul 2016 17:11:44 -0400 Received: from xch-rtp-017.cisco.com ([64.101.220.157]) by XCH-RTP-017.cisco.com ([64.101.220.157]) with mapi id 15.00.1210.000; Wed, 20 Jul 2016 17:11:44 -0400 From: "Keyur Patel (keyupate)" To: "Dongjie (Jimmy)" , Robert Raszuk Thread-Topic: [Idr] Fwd: Slot request in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00.txt Thread-Index: AQHR4gt3jXzNsYcN6ECcWcNExZ/YjA== Date: Wed, 20 Jul 2016 21:11:44 +0000 Message-ID: References: <76CD132C3ADEF848BD84D028D243C92774EEF7CF@NKGEML515-MBX.china.huawei.com> <76CD132C3ADEF848BD84D028D243C92774EEFC10@NKGEML515-MBX.china.huawei.com> In-Reply-To: <76CD132C3ADEF848BD84D028D243C92774EEFC10@NKGEML515-MBX.china.huawei.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.4.9.150325 x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.154.161.115] Content-Type: multipart/alternative; boundary="_000_D3B535AC474D9keyupateciscocom_" MIME-Version: 1.0 Archived-At: Cc: idr wg Subject: Re: [Idr] Fwd: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jul 2016 21:11:50 -0000 --_000_D3B535AC474D9keyupateciscocom_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hi Jie, Comments inlined #Keyur1 From: "Dongjie (Jimmy)" > Date: Wednesday, July 20, 2016 at 12:45 AM To: Keyur Patel >, Robert Ras= zuk > Cc: idr wg > Subject: Re: [Idr] Fwd: Slot request in IDR to present https://www.ietf.org= /internet-drafts/draft-idr-bgp-route-refresh-options-00.txt Hi Keyur, Please see my comments inline with [Jie2]: From: Keyur Patel (keyupate) [mailto:keyupate@cisco.com] Sent: Wednesday, July 20, 2016 6:18 AM To: Robert Raszuk; Dongjie (Jimmy) Cc: idr wg Subject: Re: [Idr] Fwd: Slot request in IDR to present https://www.ietf.org= /internet-drafts/draft-idr-bgp-route-refresh-options-00.txt Robert, Dongjie, Comments inlined #Keyur From: Robert Raszuk > Date: Tuesday, July 19, 2016 at 2:52 PM To: "Dongjie (Jimmy)" > Cc: idr wg > Subject: Re: [Idr] Fwd: Slot request in IDR to present https://www.ietf.org= /internet-drafts/draft-idr-bgp-route-refresh-options-00.txt Hi Jie, To me what is perhaps missing is just a new draft to define *Route Type* OR= F to address some of those EVPN new NLRI encodings. #Keyur: ORFs are permanent filters. We wanted to decouple the transaction b= ased filters (one time per refresh) from the permanent filters and hence ch= ose to modify refresh message as opposed to an ORF. [Jie2]: This was also my understanding in the beginning of writing the one-= time orf drafts. However since you need traffic filters for this =93selecti= ve refresh=94, you will find out it is already there with ORF, then you wil= l want to reuse the filters. Actually it is something between the tradition= al refresh and the traditional ORF, IMO the name does not really matter, t= he important thing is we can reuse what already exists. #Keyur1: We could definitely work towards reusing what is there or merging = some of the work. :) I am not that much convinced if one time ORF is needed as you are free to I= NSTALL and REMOVE ORF effectively producing one time behavior. #Keyur: Ack. Also existing Enhanced Route Refresh should work with ORF too. #Keyur: There are modifications needed if the refresh is going to be for se= lective prefixes only. Furthermore, if we want to support multiple concurre= nt selective refreshes then the changes needed are very much along the line= s of the solution suggested in the draft. [Jie2] For the concurrent refresh part, could you elaborate in which case i= t will be needed? The draft says =93The BGP speaker responding to the rout= e refresh requests MAY perform the refreshes in parallel=94, do you mean th= e route updates for different selective refresh requests may be interleaved= ? #Keyur1: Exactly! More specifically a bgp speaker may be re-announcing rout= e updates as part of multiple different refresh requests (same or with over= lapping filters)). Best Regards, Keyur Best regards Jie Regards, Keyur Many thx, R. On Tue, Jul 19, 2016 at 11:47 PM, Dongjie (Jimmy) > wrote: Hi Tony, Please see some comments inline with [Jie]: From: Idr [mailto:idr-bounces@ietf.org] On Beh= alf Of Tony Przygienda Sent: Tuesday, July 19, 2016 6:04 PM To: Robert Raszuk; idr wg Subject: [Idr] Fwd: Slot request in IDR to present https://www.ietf.org/int= ernet-drafts/draft-idr-bgp-route-refresh-options-00.txt Resending ... ---------- Forwarded message ---------- From: Tony Przygienda > Date: Mon, Jul 11, 2016 at 3:04 PM Subject: Re: [Idr] Slot request in IDR to present https://www.ietf.org/inte= rnet-drafts/draft-idr-bgp-route-refresh-options-00.txt To: Robert Raszuk > Cc: idr wg > On Mon, Jul 11, 2016 at 1:47 PM, Robert Raszuk > wrote: Hi Tony, Hey Robert, thanks for chiming in. Good questions. I speak here for myself,= other authors of the draft may have differing opinions. Can you clarify what is the expected behaviour as far as per peer filter-li= st when you negotiate both Refresh with options, ORF and RTC ? Note that OR= F also includes recent extension as described in RFC7543 - would all of tho= se be always a logical AND towards a peer which pushed those ? We didn't discuss that one through but the only logical conclusion for me i= s that the ORF/CP-ORF installed are respected (i.e. it's an implicit AND). = I see ORF as statefull, remote-pushed policy on the peer that is not being = flipped around all the time (albeit AFAIR there were some attempts @ non-pe= rsistent, one shot ORF but that ended up expiring?) [Jie] I think the attempts you mentioned here are the one-time ORF drafts: = draft-zeng-idr-one-time-prefix-orf and draft-dong-idr-one-time-ext-communi= ty-orf. After several revisions, these drafts got expired due to lack of re= quirements at that time. If people found some new use cases of these kinds = of mechanisms, the authors would be happy to bring them back to discussion. The motivation for this work were scenarios where a single-shot refresh is = needed, actually concurrent bunch of those based on configuration changes, = peer having dropped received routes based on specs (A-D), in policy changes= , joining VPNs, EVIs and so on. Putting ORF on a peer, refresh and remove O= RFs is significantly heavier process that may interfere on top with normal = update process going on and needs to be done one-by-one (since you have to = wait for single BoRR/EoRR pair) unless one is very smart about combining OR= F possibly & playing with the DEFER/IMMEDIATEs. As we indicated, if the AFI= /SAFI is covered by RTC and RTC is supported & one is willing to configure = RTs for each subset of routes that may need refreshing, RT will be doing th= e same job just fine. [Jie] The motivations look similar to what we described for the one-time OR= F drafts. Would you always carry ORF with separate Refresh_ID value ? Yes, Refresh-ID# is strictly monotonic so there is never a misunderstanding= WHAT the BoRR belongs to. Observe that the draft does NOT mandate that a r= equest MUST be followed by according BoRR, only that BoRRs must follow same= sequence as requests (i.e. are also strictly monotonic). However, we shoul= d probably specify that options _and_ ORF can NOT be mixed in the same type= #3 message but it's either one or the other (and anything else is error). = This will allow ORF operations like today + benefit of the Refresh ID# on = the BoRR so the IMMEDIATE can go on @ the same time as another request with= higher Refresh ID# (de facto we allow multiple parallel refreshes as you s= ee). In case of DEFER there will be simply no BoRR for it. 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 i= nstalled 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 h= ave no impact to ORF ADDs or REMOVE actions - don't you think ? I agree. Yes, ORF is kind of "permanent filter" on the peer while the inte= nt of this draft is to have bunch of "small refreshes" going on @ same time= possibly (if you request the refreshes from a good implementation while lo= w-end implementations may serialize the requests to simplify internal logic= ;-). As far as current types why not add regular/extended community ? Discussion came up. Feeling was it's an immediate encroach on RT territory.= I argued for it ;-) Ultimately, taking a more relaxed view, we chose to w= ait and see what the response is and most pressing use cases people bring t= o it and then we start to define bits and bytes of the options supported, p= ossibly borrowing to an extent from the ORF specs ;-) As in "most sincere = form of flattery" and such ... ;-) [Jie] Actually before the one-time ORF drafts were submitted, we initially = considered to make it a =93selective route refresh=94 mechanism. Then we re= alized that the filters will be quite similar to the ones already defined f= or ORF. In order to reuse the ORF filters, we then decided to define this m= echanism as new =93one-time=94 ORF types. Just to provide some background = information since you also plan to reuse the format of the existing ORF typ= es. Best regards, Jie -- tony -- We=92ve heard that a million monkeys at a million keyboards could produce t= he complete works of Shakespeare; now, thanks to the Internet, we know that= is not true. =97Robert Wilensky --_000_D3B535AC474D9keyupateciscocom_ Content-Type: text/html; charset="Windows-1252" Content-ID: Content-Transfer-Encoding: quoted-printable
Hi Jie,

Comments inlined #Keyur1

From: "Dongjie (Jimmy)" &= lt;jie.dong@huawei.com>
Date: Wednesday, July 20, 2016 at 1= 2:45 AM
To: Keyur Patel <keyupate@cisco.com>, Robert Raszuk <robert@raszuk.net>
Cc: idr wg <idr@ietf.org>
Subject: Re: [Idr] Fwd: Slot reques= t in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00= .txt

Hi Keyur,

 <= /span>

Please see my comm= ents inline with [Jie2]:

 <= /span>

From: Keyur Patel (keyupa= te) [mailto:keyupate@cisco.com]
Sent: Wednesday, July 20, 2016 6:18 AM
To: Robert Raszuk; Dongjie (Jimmy)
Cc: idr wg
Subject: Re: [Idr] Fwd: Slot request in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00= .txt

 

Robert, Dongjie,

 

Comments inlined #Keyur<= /o:p>

 

From: Robert Raszuk <robert@raszuk.net>
Date: Tuesday, July 19, 2016 at 2:52 PM
To: "Dongjie (Jimmy)" <jie.dong@huawei.com>
Cc: idr wg <idr@ietf.org><= br> Subject: Re: [Idr] Fwd: Slot request in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00= .txt

 

Hi Jie,

 

To me what is perhaps missing is just a new draft = to define *Route Type* ORF to address some of those EVPN new NLRI encodings= .

 

#Keyur: ORFs are permanent fi= lters. We wanted to decouple the transaction based filters (one time per re= fresh) from the permanent filters and hence chose to modify refresh message as opposed to an ORF. 

 <= /span>

[Jie2]: This was a= lso my understanding in the beginning of writing the one-time orf drafts. H= owever since you need traffic filters for this =93selective refresh=94, you will find out it is already there wi= th ORF, then you will want to reuse the filters. Actually it is something b= etween the traditional refresh and the traditional ORF,  IMO the name = does not really matter, the important thing is we can reuse what already exists.


#Keyur1: We could definitely work towards reusing what is there or mer= ging some of the work. :)

=

 

I am not that much convinced if one time ORF is ne= eded as you are free to INSTALL and REMOVE ORF effectively producing one ti= me behavior.

 

#Keyur: Ack. =

 

Also existing Enhanced Route Refresh should work w= ith ORF too. 

 

#Keyur: There are modificatio= ns needed if the refresh is going to be for selective prefixes only. Furthe= rmore, if we want to support multiple concurrent selective refreshes then the changes needed are very much along= the lines of the solution suggested in the draft.

 <= /span>

[Jie2] For the con= current refresh part, could you elaborate in which case it will be needed? = The draft says =93The BGP speaker responding to  the route refresh requests MAY perform the refreshes in parallel= =94, do you mean the route updates for different selective refresh requests= may be interleaved?


#Keyur1: Exactly! More specifically a bgp speaker may be re-announcing= route updates as part of multiple different refresh requests (same or with= overlapping filters)). 

Best Regards,
Keyur



=

 <= /span>

Best regards<= /o:p>

Jie

 

Regards,

Keyur =

 

 

 

Many thx,

R.

 

 

 

 

On Tue, Jul 19, 2016 at 11:47= PM, Dongjie (Jimmy) <jie.dong@huawei.com> wrote:

Hi Tony,

 

Please see some comments inline = with [Jie]:

 

From: Idr [mailto:idr-= bounces@ietf.org] On Behalf Of Tony Przygienda
Sent: Tuesday, July 19, 2016 6:04 PM
To: Robert Raszuk; idr wg
Subject: [Idr] Fwd: Slot request in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00= .txt

 

Resending ... 

 

---------- Forwarded message = ----------
From: Tony Przygienda <tonysietf@gmail.com>
Date: Mon, Jul 11, 2016 at 3:04 PM
Subject: Re: [Idr] Slot request in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00= .txt
To: Robert Raszuk <robert@raszuk.net>
Cc: idr wg <idr@ietf.o= rg>

 

 

On Mon, Jul 11, 2016 at= 1:47 PM, Robert Raszuk <robert@raszuk.net> wrote:

Hi Tony,<= /o:p>

 

Hey Robert, thanks for = chiming in. Good questions. I speak here for myself, other authors of the d= raft may have differing opinions. 

 

 

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

 

We didn't discuss that = one through but the only logical conclusion for me is that the ORF/CP-ORF i= nstalled are respected (i.e. it's an implicit AND). I see ORF as statefull, remote-pushed policy on the peer that is not= being flipped around all the time (albeit AFAIR there were some attempts @= non-persistent, one shot ORF but that ended up expiring?)

 

[Jie] I think the attempts you m= entioned here are the one-time ORF drafts: draft-zeng-idr-one-time-prefix-orf  and draft-dong-idr-one-time-ext-c= ommunity-orf. After several revisions, these drafts got expired due to lack= of requirements at that time. If people found some new use cases of these = kinds of mechanisms, the authors would be happy to bring them back to discussion.

 

The motivation for this= work were scenarios where a single-shot refresh is needed, actually concur= rent bunch of those based on configuration changes, peer having dropped received routes based on specs (A-D), in poli= cy changes, joining VPNs, EVIs and so on. Putting ORF on a peer, refresh an= d remove ORFs is significantly heavier process that may interfere on top wi= th normal update process going on and needs to be done one-by-one (since you have to wait for single BoRR/Eo= RR pair) unless one is very smart about combining ORF possibly & playin= g with the DEFER/IMMEDIATEs. As we indicated, if the AFI/SAFI is covered by= RTC and RTC is supported & one is willing to configure RTs for each subset of routes that may need refreshing, RT wi= ll be doing the same job just fine. 

 

[Jie] The motivations look simil= ar to what we described for the one-time ORF drafts.

 

 

Would you always carry ORF with separate Refresh_ID value ? = ;

 

Yes, Refresh-ID# is str= ictly monotonic so there is never a misunderstanding WHAT the BoRR belongs = to. Observe that the draft does NOT mandate that a request MUST be followed by according BoRR, only that BoRRs must fo= llow same sequence as requests (i.e. are also strictly monotonic). However,= we should probably specify that options _and_ ORF can NOT be mixed in the = same type #3 message but it's either one or the other (and anything else is error). This will allow ORF operati= ons like today + benefit of the Refresh ID#  on the BoRR so the IM= MEDIATE can go on @ the same time as another request with higher Refresh ID= # (de facto we allow multiple parallel refreshes as you see).  In case of DEFER there will be simply no BoRR for it.&n= bsp;

 

 

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

 

I agree. Yes, ORF is ki= nd of  "permanent filter" on the peer while the intent of th= is draft is to have bunch of "small refreshes" going on @ same time possibly (if you request the refreshes from a good implementat= ion while low-end implementations may serialize the requests to simplify in= ternal logic ;-). 

 

 

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

 

Discussion came up. Fee= ling was it's an immediate encroach on RT territory. I argued for it ;-) &n= bsp;Ultimately, taking a more relaxed view, we chose to wait and see what the response is and most pressing use cases peo= ple bring to it and then we start to define bits and bytes of the options s= upported, possibly borrowing to an extent from the ORF specs ;-)  As i= n "most sincere form of flattery" and such ... ;-) 

 

[Jie] Actually before the one-ti= me ORF drafts were submitted, we initially considered to make it a =93selective route refresh=94 mechanism. Then we r= ealized that the filters will be quite similar to the ones already defined = for ORF. In order to reuse the ORF filters, we then decided to define this = mechanism as new =93one-time=94 ORF types.  Just to provide some background information since you also plan to reuse t= he format of the existing ORF types.

 

Best regards,

Jie

 

-- tony <= span lang=3D"EN-US" style=3D"color:black">

 



 

--

We=92ve heard that a million monkeys at a mill= ion keyboards could produce the complete works of Shakespeare; now, thanks to the Internet, we know that is not true.

=97Robe= rt Wilensky

 

--_000_D3B535AC474D9keyupateciscocom_-- From nobody Wed Jul 20 15:14:47 2016 Return-Path: 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 5FF5E12D1C1 for ; Wed, 20 Jul 2016 15:14:45 -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 nvIPnqdgzX4G for ; Wed, 20 Jul 2016 15:14:43 -0700 (PDT) Received: from mail-qt0-x22d.google.com (mail-qt0-x22d.google.com [IPv6:2607:f8b0:400d:c0d::22d]) (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 9E6A312B00F for ; Wed, 20 Jul 2016 15:14:42 -0700 (PDT) Received: by mail-qt0-x22d.google.com with SMTP id w38so34319551qtb.0 for ; Wed, 20 Jul 2016 15:14:42 -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=QV/3gSoMW9LoJPG0wphgPx9lQP5iPfbxILY3pzGAlSs=; b=CNwU+aMNqd1mjKGUloFlRmN5nkkxiFKKv/8CeDzLmsKcxBHON9pu2le8j94xsuMuif LuMe9d12n2F5HX9NLkSR8Z0QWTu7y/IHXtbapvV0G1nVBPc2YJBggldf255to1gzUZSC On3cuH993vhmkNqccgHJ7PoKvKK40D+bnzgtIkpYZmyNtl5MzGNcy0bJtjAfThfiN4XA istC4gWsxIIpVo+ta+0qYb7oJlNc3JEXri83K3G1Gq6YXy28rooPma3XGIOkR1qUhN/J lr813BUMWhJdaPO8mBiDjvuPB7UN1XdMKke9O6t/rHkOS5ldYGGx8NwVI1uIDQ1FRgKk FFow== 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=QV/3gSoMW9LoJPG0wphgPx9lQP5iPfbxILY3pzGAlSs=; b=c3bMcNLf8WNbzGstX9hwVlLXBLtA1w03mHES/LhN58zX5l7Mdx1dfkTx23eSamunD0 tCTMlPaLif6fJNtslTAlyapfXSyUadL5CLIjdOObPtXklCAOcB424HgP+1DDsqCS07kP MxG6pNIgJRQ+g4rzfBxL2S5cJDnWNwlrGkdcArZuzkmzcE9gBEanW+yE5MUBfDOCkn9m VtqETAgSx178c+zInUpVGKKaVJRx6Whxs5C1Mug4OuxUuSSZdAIiSYVIJoNdHK9CM+ls wLRZVPjyewghUrbW0zOT1yCW7dcYBNZ7W1Y/31N8/2ODXN4VnFM9l1d0pKg6MX3F6Bee jF0Q== X-Gm-Message-State: ALyK8tKpPwuD5hf9J2piOo21KsPxgiAjYjZp2wESq8d2og+emDEvbwNmLCbes5VIvHrD4+gllm9CYf1sxsLDqg== X-Received: by 10.237.38.35 with SMTP id z32mr70687324qtc.69.1469052881689; Wed, 20 Jul 2016 15:14:41 -0700 (PDT) MIME-Version: 1.0 Sender: rraszuk@gmail.com Received: by 10.237.36.90 with HTTP; Wed, 20 Jul 2016 15:14:40 -0700 (PDT) In-Reply-To: References: <76CD132C3ADEF848BD84D028D243C92774EEF7CF@NKGEML515-MBX.china.huawei.com> From: Robert Raszuk Date: Thu, 21 Jul 2016 00:14:40 +0200 X-Google-Sender-Auth: SY6GMa9y6rhhIRb56iZ9AkL8ieA Message-ID: To: "Keyur Patel (keyupate)" Content-Type: multipart/alternative; boundary=94eb2c123a102b63bc053818877b Archived-At: Cc: idr wg Subject: Re: [Idr] Fwd: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jul 2016 22:14:45 -0000 --94eb2c123a102b63bc053818877b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Keyur, On the EVPN topic which defines BGP protocol extensions without any IDR WG review the more I hear about cases like you bring below (and this is not the first one btw) the more I think it is really quite badly designed. And such bad protocol extensions should not be a justification to introduce even more questionable knobs in BGP. In this specific case just get all SAFI refreshed modulo to RTC or ORF filters and you are done. Case solved :). Best, R. On Wed, Jul 20, 2016 at 11:05 PM, Keyur Patel (keyupate) wrote: > Hi Robert, > > One interesting use case is with EVPN address family where a new > route-type is introduced without a capability. A PE may have had safi > enabled but not have accepted its route-type (or set of route-types) all > mapping to a same RT. A transactional filter attempts to solve it. > > We can clarify in the next revision of the draft. > > One more comment inlined #Keyur > > From: Robert Raszuk > Date: Tuesday, July 19, 2016 at 3:29 PM > To: Keyur Patel > Cc: "Dongjie (Jimmy)" , idr wg > Subject: Re: [Idr] Fwd: Slot request in IDR to present > https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-= 00.txt > > Hi Keyur, > > The missing part seems to be justification if we really need "transaction > based filters" as opposed to simply having permanent ones. > > What real problem "transaction based filters" solve ? IMO the draft needs > to state it clearly. > > The other point is that "permanent" are not really permanent anyway .. > they are installed from update to withdraw of a given filter - regardless > what filtering mechanism you choose (ORF, RTC, XYZ ...). And if you go wi= th > the notion that permanent are sufficient the entire aparatus allowing you > to have concurrent route refresh requests in flight goes away :) > > #Keyur: Ack your right. My reference to a permanent filter was in context > of a session life time and I agree with you that it could be modified or > withdrawn at any given time. I was trying to differentiate it from > transactional filters. > > Regards, > Keyur > > Thx, > r. > > > On Wed, Jul 20, 2016 at 12:18 AM, Keyur Patel (keyupate) < > keyupate@cisco.com> wrote: > >> Robert, Dongjie, >> >> Comments inlined #Keyur >> >> From: Robert Raszuk >> Date: Tuesday, July 19, 2016 at 2:52 PM >> To: "Dongjie (Jimmy)" >> Cc: idr wg >> Subject: Re: [Idr] Fwd: Slot request in IDR to present >> https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options= -00.txt >> >> Hi Jie, >> >> To me what is perhaps missing is just a new draft to define *Route Type* >> ORF to address some of those EVPN new NLRI encodings. >> >> #Keyur: ORFs are permanent filters. We wanted to decouple the transactio= n >> based filters (one time per refresh) from the permanent filters and henc= e >> chose to modify refresh message as opposed to an ORF. >> >> I am not that much convinced if one time ORF is needed as you are free t= o >> INSTALL and REMOVE ORF effectively producing one time behavior. >> >> #Keyur: Ack. >> >> Also existing Enhanced Route Refresh should work with ORF too. >> >> #Keyur: There are modifications needed if the refresh is going to be for >> selective prefixes only. Furthermore, if we want to support multiple >> concurrent selective refreshes then the changes needed are very much alo= ng >> the lines of the solution suggested in the draft. >> >> Regards, >> Keyur >> >> >> >> Many thx, >> R. >> >> >> >> >> On Tue, Jul 19, 2016 at 11:47 PM, Dongjie (Jimmy) >> wrote: >> >>> Hi Tony, >>> >>> >>> >>> Please see some comments inline with [Jie]: >>> >>> >>> >>> *From:* Idr [mailto:idr-bounces@ietf.org] *On Behalf Of *Tony Przygiend= a >>> *Sent:* Tuesday, July 19, 2016 6:04 PM >>> *To:* Robert Raszuk; idr wg >>> *Subject:* [Idr] Fwd: Slot request in IDR to present >>> https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-option= s-00.txt >>> >>> >>> >>> Resending ... >>> >>> >>> >>> ---------- Forwarded message ---------- >>> From: *Tony Przygienda* >>> Date: Mon, Jul 11, 2016 at 3:04 PM >>> Subject: Re: [Idr] Slot request in IDR to present >>> https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-option= s-00.txt >>> To: Robert Raszuk >>> Cc: idr wg >>> >>> >>> >>> >>> >>> On Mon, Jul 11, 2016 at 1:47 PM, Robert Raszuk >>> wrote: >>> >>> Hi Tony, >>> >>> >>> >>> Hey Robert, thanks for chiming in. Good questions. I speak here for >>> myself, other authors of the draft may have differing opinions. >>> >>> >>> >>> >>> >>> 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 ? >>> >>> >>> >>> We didn't discuss that one through but the only logical conclusion for >>> me is that the ORF/CP-ORF installed are respected (i.e. it's an implici= t >>> AND). I see ORF as statefull, remote-pushed policy on the peer that is = not >>> being flipped around all the time (albeit AFAIR there were some attempt= s @ >>> non-persistent, one shot ORF but that ended up expiring?) >>> >>> >>> >>> [Jie] I think the attempts you mentioned here are the one-time ORF >>> drafts: draft-zeng-idr-one-time-prefix-orf and >>> draft-dong-idr-one-time-ext-community-orf. After several revisions, the= se >>> drafts got expired due to lack of requirements at that time. If people >>> found some new use cases of these kinds of mechanisms, the authors woul= d be >>> happy to bring them back to discussion. >>> >>> >>> >>> The motivation for this work were scenarios where a single-shot refresh >>> is needed, actually concurrent bunch of those based on configuration >>> changes, peer having dropped received routes based on specs (A-D), in >>> policy changes, joining VPNs, EVIs and so on. Putting ORF on a peer, >>> refresh and remove ORFs is significantly heavier process that may inter= fere >>> on top with normal update process going on and needs to be done one-by-= one >>> (since you have to wait for single BoRR/EoRR pair) unless one is very s= mart >>> about combining ORF possibly & playing with the DEFER/IMMEDIATEs. As we >>> indicated, if the AFI/SAFI is covered by RTC and RTC is supported & one= is >>> willing to configure RTs for each subset of routes that may need >>> refreshing, RT will be doing the same job just fine. >>> >>> >>> >>> [Jie] The motivations look similar to what we described for the one-tim= e >>> ORF drafts. >>> >>> >>> >>> >>> >>> Would you always carry ORF with separate Refresh_ID value ? >>> >>> >>> >>> Yes, Refresh-ID# is strictly monotonic so there is never a >>> misunderstanding WHAT the BoRR belongs to. Observe that the draft does = NOT >>> mandate that a request MUST be followed by according BoRR, only that Bo= RRs >>> must follow same sequence as requests (i.e. are also strictly monotonic= ). >>> However, we should probably specify that options _and_ ORF can NOT be m= ixed >>> in the same type #3 message but it's either one or the other (and anyth= ing >>> else is error). This will allow ORF operations like today + benefit of = the >>> Refresh ID# on the BoRR so the IMMEDIATE can go on @ the same time as >>> another request with higher Refresh ID# (de facto we allow multiple >>> parallel refreshes as you see). In case of DEFER there will be simply = no >>> BoRR for it. >>> >>> >>> >>> >>> >>> 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 entrie= s >>> 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 y= ou >>> think ? >>> >>> >>> >>> I agree. Yes, ORF is kind of "permanent filter" on the peer while the >>> intent of this draft is to have bunch of "small refreshes" going on @ s= ame >>> time possibly (if you request the refreshes from a good implementation >>> while low-end implementations may serialize the requests to simplify >>> internal logic ;-). >>> >>> >>> >>> >>> >>> As far as current types why not add regular/extended community ? >>> >>> >>> >>> Discussion came up. Feeling was it's an immediate encroach on RT >>> territory. I argued for it ;-) Ultimately, taking a more relaxed view,= we >>> chose to wait and see what the response is and most pressing use cases >>> people bring to it and then we start to define bits and bytes of the >>> options supported, possibly borrowing to an extent from the ORF specs ;= -) >>> As in "most sincere form of flattery" and such ... ;-) >>> >>> >>> >>> [Jie] Actually before the one-time ORF drafts were submitted, we >>> initially considered to make it a =E2=80=9Cselective route refresh=E2= =80=9D mechanism. Then >>> we realized that the filters will be quite similar to the ones already >>> defined for ORF. In order to reuse the ORF filters, we then decided to >>> define this mechanism as new =E2=80=9Cone-time=E2=80=9D ORF types. Jus= t to provide some >>> background information since you also plan to reuse the format of the >>> existing ORF types. >>> >>> >>> >>> Best regards, >>> >>> Jie >>> >>> >>> >>> -- tony >>> >>> >>> >>> >>> >>> >>> >>> -- >>> >>> *We=E2=80=99ve heard that a million monkeys at a million keyboards coul= d produce >>> the complete works of Shakespeare; now, thanks to the Internet, we know >>> that is not true.* >>> >>> =E2=80=94Robert Wilensky >>> >> >> > --94eb2c123a102b63bc053818877b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Keyur,

<= /div>
On the EVPN topic which defines BGP protocol extens= ions without any IDR WG review the more I hear about cases like you bring b= elow (and this is not the first one btw) the more I think it is really quit= e badly designed.=C2=A0

And such bad protocol extensions should not be a justification to introdu= ce even more questionable knobs in BGP.=C2=A0

<= /div>
In this specific case just get all SAFI refreshed m= odulo to RTC or ORF filters and you are done. Case solved :).

Best,
R.


On Wed, Jul 20, 2016 at 11:05 PM, Keyur Patel (keyupate) <= span dir=3D"ltr"><keyupate@cisco.com> wrote:
Hi Robert,

One interesting use case is with EVPN address family where a new route= -type is introduced without a capability.=C2=A0 A PE may have had safi enab= led but not have accepted its route-type (or set of route-types) all mappin= g to a same RT. A transactional filter attempts to solve it.

We can clarify in the next revision of the draft.

One more comment inlined #Keyur

From: Robert Raszuk <robert@raszuk.net>
Date: Tuesday, July 19, 2016 at 3:2= 9 PM
To: Keyur Patel <keyupate@cisco.com>
Cc: "Dongjie (Jimmy)" <= ;jie.dong@huawei.c= om>, idr wg <id= r@ietf.org>
Subject: Re: [Idr] Fwd: Slot reques= t in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00= .txt

Hi Keyur,

The missing part seems to be justification if we really need "transact= ion based filters" as opposed to simply having permanent ones.=C2=A0

What real problem "transaction based filters" solve ? IMO the dra= ft needs to state it clearly.=C2=A0

The other point is that "permanent" are not really permanent anyw= ay .. they are installed from update to withdraw of a given filter - regard= less what filtering mechanism you choose (ORF, RTC, XYZ ...). And if you go= with the notion that permanent are sufficient the entire aparatus allowing you to have concurrent route refresh requests= in flight goes away :)

#Keyur: Ack your right. My reference to a permanent filter was in cont= ext of a session life time and I agree with you that it could be modified o= r withdrawn at any given time. I was trying to differentiate it from transa= ctional filters.

Regards,
Keyur

Thx,
r.


On Wed, Jul 20, 2016 at 12:18 AM, Keyur Patel (k= eyupate) <keyupate@cisco.com> wrote:
Robert, Dongjie,

Comments inlined #Keyur

From: Robert Raszuk <robert@raszuk.net>
Date: Tuesday, July 19, 2016 at 2:5= 2 PM
To: "Dongjie (Jimmy)" <= ;jie.dong@huawei.c= om>
Cc: idr wg <idr@ietf.org>
Subject: Re: [Idr] Fwd: Slot reques= t in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00= .txt

Hi Jie,

To me what is perhaps missing is just a new draft to define *Route Type* OR= F to address some of those EVPN new NLRI encodings.

#Keyur: ORFs are permanent filters. We wanted to decouple the transact= ion based filters (one time per refresh) from the permanent filters and hen= ce chose to modify refresh message as opposed to an ORF.=C2=A0

I am not that much convinced if one time ORF is needed as you are free to I= NSTALL and REMOVE ORF effectively producing one time behavior.

#Keyur: Ack.=C2=A0

Also existing Enhanced Route Refresh should work with ORF too.=C2=A0

#Keyur: There are modifications needed if the refresh is going to be f= or selective prefixes only. Furthermore, if we want to support multiple con= current selective refreshes then the changes needed are very much along the= lines of the solution suggested in the draft.

Regards,
Keyur=C2=A0



Many thx,
R.




On Tue, Jul 19, 2016 at 11:47 PM, Dongjie (Jimmy= ) <jie.dong@huawe= i.com> wrote:

Hi Tony,

=C2=A0=

Please see some comments in= line with [Jie]:

=C2=A0=

From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Tony Przygienda
Sent: Tuesday, July 19, 2016 6:04 PM
To: Robert Raszuk; idr wg
Subject: [Idr] Fwd: Slot request in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00= .txt

=C2=A0

Resending ...=C2=A0

=C2=A0

= ---------- Forwarded message ----------
From: Tony Przygienda <tonysietf@gmail.com>
Date: Mon, Jul 11, 2016 at 3:04 PM
Subject: Re: [Idr] Slot request in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00= .txt
To: Robert Raszuk <robert@raszuk.net>
Cc: idr wg <idr@ietf.o= rg>

=C2=A0

=C2=A0

On Mon, Jul 11, 2016 at 1:47 PM= , Robert Raszuk <= robert@raszuk.net> wrote:

Hi Tony,

=C2=A0

Hey Robert, thanks for chiming = in. Good questions. I speak here for myself, other authors of the draft may= have differing opinions.=C2=A0

=C2=A0

=C2=A0

Can you clarify what is the expected behaviour as far as per peer f= ilter-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 towar= ds a peer which pushed those ?=C2=A0

=C2=A0

We didn't discuss that one = through but the only logical conclusion for me is that the ORF/CP-ORF insta= lled are respected (i.e. it's an implicit AND). I see ORF as statefull,= remote-pushed policy on the peer that is not being flipped around all the time (albeit AFAIR there were some attempts @= non-persistent, one shot ORF but that ended up expiring?)

=C2=A0=

[Jie] I think the attempts = you mentioned here are the one-time ORF drafts: draft-zeng-idr-one-time-pre= fix-orf =C2=A0and draft-dong-idr-one-time-ext-community-orf. After several revisions, these drafts got expired due to lack of requireme= nts at that time. If people found some new use cases of these kinds of mech= anisms, the authors would be happy to bring them back to discussion.=

=C2=A0

The motivation for this work we= re scenarios where a single-shot refresh is needed, actually concurrent bun= ch of those based on configuration changes, peer having dropped received ro= utes based on specs (A-D), in policy changes, joining VPNs, EVIs and so on. Putting ORF on a peer, refresh and = remove ORFs is significantly heavier process that may interfere on top with= normal update process going on and needs to be done one-by-one (since you = have to wait for single BoRR/EoRR pair) unless one is very smart about combining ORF possibly & playing = with the DEFER/IMMEDIATEs. As we indicated, if the AFI/SAFI is covered by R= TC and RTC is supported & one is willing to configure RTs for each subs= et of routes that may need refreshing, RT will be doing the same job just fine.=C2=A0

=C2=A0=

[Jie] The motivations look = similar to what we described for the one-time ORF drafts.

=C2=A0

=C2=A0

Would you always carry ORF with separate Refresh_ID value ?=C2=A0

=C2=A0

Yes, Refresh-ID# is strictly mo= notonic so there is never a misunderstanding WHAT the BoRR belongs to. Obse= rve that the draft does NOT mandate that a request MUST be followed by acco= rding BoRR, only that BoRRs must follow same sequence as requests (i.e. are also strictly monotonic). However, we = should probably specify that options _and_ ORF can NOT be mixed in the same= type #3 message but it's either one or the other (and anything else is= error). This will allow ORF operations like today + benefit of the Refresh ID# =C2=A0on the BoRR so the IMMEDIATE= can go on @ the same time as another request with higher Refresh ID# (de f= acto we allow multiple parallel refreshes as you see).=C2=A0 In case of DEF= ER there will be simply no BoRR for it.=C2=A0

=C2=A0

=C2=A0

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 a= lready 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 ?=C2=A0

=C2=A0

I agree. Yes, ORF is kind of = =C2=A0"permanent filter" on the peer while the intent of this dra= ft is to have bunch of "small refreshes" going on @ same time pos= sibly (if you request the refreshes from a good implementation while low-end implementations may serialize the requests to simplify inter= nal logic ;-).=C2=A0

=C2=A0

=C2=A0

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

=C2=A0

Discussion came up. Feeling was= it's an immediate encroach on RT territory. I argued for it ;-) =C2=A0= Ultimately, taking a more relaxed view, we chose to wait and see what the r= esponse is and most pressing use cases people bring to it and then we start to define bits and bytes of the options supp= orted, possibly borrowing to an extent from the ORF specs ;-) =C2=A0As in &= quot;most sincere form of flattery" and such ... ;-)=C2=A0

=C2=A0=

[Jie] Actually before the o= ne-time ORF drafts were submitted, we initially considered to make it a =E2= =80=9Cselective route refresh=E2=80=9D mechanism. Then we realized that the filters will be quite similar to the ones alread= y defined for ORF. In order to reuse the ORF filters, we then decided to de= fine this mechanism as new =E2=80=9Cone-time=E2=80=9D ORF types.=C2=A0 Just= to provide some background information since you also plan to reuse the format of the existing ORF types. <= /p>

=C2=A0=

Best regards,=

Jie

= =C2=A0

-- tony= =C2=A0

=C2=A0<= u>



=C2=A0

--

We=E2=80=99ve heard that a million monkeys at a mil= lion keyboards could produce the complete works of Shakespeare; now, thanks= to the Internet, we know that is not true.=

=E2=80=94Robert Wilensky




--94eb2c123a102b63bc053818877b-- From nobody Thu Jul 21 08:42:19 2016 Return-Path: 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 8218C12D75E for ; Thu, 21 Jul 2016 08:42:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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 FMTP2syyn9PB for ; Thu, 21 Jul 2016 08:42:14 -0700 (PDT) Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::22b]) (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 814DD12D5A1 for ; Thu, 21 Jul 2016 08:42:14 -0700 (PDT) Received: by mail-io0-x22b.google.com with SMTP id m101so79575245ioi.2 for ; Thu, 21 Jul 2016 08:42:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=PmvsbB06xoY+sHGCkIEuAoxy1lehlqThPtiDTEJBPV8=; b=EjZogTB0j+4rzv7w+NYLim2TUjDJmqckIFBawCwsyT5ZM2xy7k7DF4U6XiPlzM4svj j5TBedhBUZjA3uBjxuRaSVkhi2EW3gUBcZL6QEeh8/x3tOAR0XuuWgVoT4q8IJKPpLMs 5sdk4ymcGVrGKUQ18gbVZ0nCp79uC0L6gstId/avU21qAOUZ51Og0Rasx9GLCjrbAuBH JKR8JNdoXouep37mBDFkne8KBEuIRkPKxABfsnt2N0aiwJpDpoXTd3awn3mOMs9/SEAe +10eC8lH8art7ZUdxu6NXoEVbYtl4sX4GAB2EIjgEWwRXPyvpyYw9XGaFRiocvGJna4K 2HcA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=PmvsbB06xoY+sHGCkIEuAoxy1lehlqThPtiDTEJBPV8=; b=gALH73q6ECl5OBZUCMqsafkmBkJ8kmqUifulbPPcd20WUtLIvJSJo7BJR5Gz7Rh4lx wsgDQDHNMdP0CY4FUgYcRuV8B8txZkq+OY1VvrKS0S1i9qsknvUTJI0erFxnkz3uyqnY 03NuAb2lr95ZspavZgPS19iYCSFqCNvWtgzOyUyuI/bulHCP/WOndD9azrs2DHJ9ww7e rndWm3FJEil6bO9vwiJvRMd/boHbLONooP5tqBFIcNzF8+9XFL/weeo4BaccASdvLm52 nefMS5ijgwtFrpk+3s9UCriWv1aVQ0pgUa3ZpDoufodaEtSHP5bP5PIIR8vbJZKJG8sG HmJw== X-Gm-Message-State: ALyK8tLX5vCmKVKren6S9k8U1+t4R7Ws7q3KmnAuS61tdVBwwUzCaY2lT5AI5A0m3Fw9C4lR8s/KevpKayg2tA== X-Received: by 10.107.27.144 with SMTP id b138mr51221042iob.163.1469115733694; Thu, 21 Jul 2016 08:42:13 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.158.82 with HTTP; Thu, 21 Jul 2016 08:41:34 -0700 (PDT) In-Reply-To: References: <76CD132C3ADEF848BD84D028D243C92774EEF7CF@NKGEML515-MBX.china.huawei.com> From: Tony Przygienda Date: Thu, 21 Jul 2016 08:41:34 -0700 Message-ID: To: Robert Raszuk Content-Type: multipart/alternative; boundary=001a11409f9a70de21053827296a Archived-At: Cc: "Keyur Patel \(keyupate\)" , idr wg Subject: Re: [Idr] Fwd: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jul 2016 15:42:18 -0000 --001a11409f9a70de21053827296a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Read the "longish" thread by now and between all this "let's do filter/let's do pull (refresh)" I try to take a step back to see the forest= : a) To validate Niloo's point: 'f an implementation chooses to drop things based on configuration/policy (multicast EVPN routes) extending ORF will cause a complete refresh of EVPN (including type-2 MACs) unless you go and "install filter type-2, then refresh, then remove-filter-2" and after requesting type-6 (you can't defer remove-filter-2 step, otherwise you won't receive type-2 updates anymore!) floods you with all MACs. Pub-sub with a single "filter-list" is simply NOT a good model to request arbitrary pieces of routes missing (which is where the world is going, BGP database is sharding to the point specs are recommending to "drop when you don't need it" and we have the need to ask for very specific sets @ given points in time [as the use cases describe]). b) A much _bigger_ problem IMO is the fact that ORF language does not seem to be an algebra, it's a program and you can only build a closure of procedural programs by running them normally (not good to restrict sets you process). In less abstract terms a refresh with filters that are OR'ed and AND'ed (first order logic transitive closure) determines the cone you need to walk on the RIB very easily (people implementing heavy-duty BGP will know precisely what that means) whereas any change to the filter will cause a full walk on the RIB possibly (in case of arbitrary mix of accepts and rejects) without a lot of possibly hard logic to write (I didn't think fully through it but I think it may be actually possible to write something delivering closure from a generic ORF filter so it's an interesting discussion). Even if you can build the closure, you can only run one at a time (one ORF filter) unless the peer does some crazy state-ful query optimization language to do wonders to squeeze multiple queries it needs into a single ORFs it's doing (SQL query optimizers are _really_ complex beasts) while the "you can put a filter on something to suppress it on refresh but you can hammered with it anyway the moment you remove it" persists. For that 2 cases my take is that it's better to move towards the model proposed by a "filtered refresh" (independently of being co-author) rather than a 'pub-sub'. As ultimate, wider angle view of the world. BGP will be offered more cycles to run (it already is ) but not in the form of a single faster and faster CPU anymore but in form of multiple cores/machines. A set of filtered refreshes can be parallelized fairly easily when requested. A single ORF filter being manipulated on/off will as described in a) possibly cause huge spurious refreshes and in b) a single threat of execution serializing the synchronization between peers. I hope that all can be parsed ... Very good discussion overall no matter which way it goes ... --- tony On Wed, Jul 20, 2016 at 3:14 PM, Robert Raszuk wrote: > Hi Keyur, > > On the EVPN topic which defines BGP protocol extensions without any IDR W= G > review the more I hear about cases like you bring below (and this is not > the first one btw) the more I think it is really quite badly designed. > > And such bad protocol extensions should not be a justification to > introduce even more questionable knobs in BGP. > > In this specific case just get all SAFI refreshed modulo to RTC or ORF > filters and you are done. Case solved :). > > Best, > R. > > > On Wed, Jul 20, 2016 at 11:05 PM, Keyur Patel (keyupate) < > keyupate@cisco.com> wrote: > >> Hi Robert, >> >> One interesting use case is with EVPN address family where a new >> route-type is introduced without a capability. A PE may have had safi >> enabled but not have accepted its route-type (or set of route-types) all >> mapping to a same RT. A transactional filter attempts to solve it. >> >> We can clarify in the next revision of the draft. >> >> One more comment inlined #Keyur >> >> From: Robert Raszuk >> Date: Tuesday, July 19, 2016 at 3:29 PM >> To: Keyur Patel >> Cc: "Dongjie (Jimmy)" , idr wg >> Subject: Re: [Idr] Fwd: Slot request in IDR to present >> https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options= -00.txt >> >> Hi Keyur, >> >> The missing part seems to be justification if we really need "transactio= n >> based filters" as opposed to simply having permanent ones. >> >> What real problem "transaction based filters" solve ? IMO the draft need= s >> to state it clearly. >> >> The other point is that "permanent" are not really permanent anyway .. >> they are installed from update to withdraw of a given filter - regardles= s >> what filtering mechanism you choose (ORF, RTC, XYZ ...). And if you go w= ith >> the notion that permanent are sufficient the entire aparatus allowing yo= u >> to have concurrent route refresh requests in flight goes away :) >> >> #Keyur: Ack your right. My reference to a permanent filter was in contex= t >> of a session life time and I agree with you that it could be modified or >> withdrawn at any given time. I was trying to differentiate it from >> transactional filters. >> >> Regards, >> Keyur >> >> Thx, >> r. >> >> >> On Wed, Jul 20, 2016 at 12:18 AM, Keyur Patel (keyupate) < >> keyupate@cisco.com> wrote: >> >>> Robert, Dongjie, >>> >>> Comments inlined #Keyur >>> >>> From: Robert Raszuk >>> Date: Tuesday, July 19, 2016 at 2:52 PM >>> To: "Dongjie (Jimmy)" >>> Cc: idr wg >>> Subject: Re: [Idr] Fwd: Slot request in IDR to present >>> https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-option= s-00.txt >>> >>> Hi Jie, >>> >>> To me what is perhaps missing is just a new draft to define *Route Type= * >>> ORF to address some of those EVPN new NLRI encodings. >>> >>> #Keyur: ORFs are permanent filters. We wanted to decouple the >>> transaction based filters (one time per refresh) from the permanent fil= ters >>> and hence chose to modify refresh message as opposed to an ORF. >>> >>> I am not that much convinced if one time ORF is needed as you are free >>> to INSTALL and REMOVE ORF effectively producing one time behavior. >>> >>> #Keyur: Ack. >>> >>> Also existing Enhanced Route Refresh should work with ORF too. >>> >>> #Keyur: There are modifications needed if the refresh is going to be fo= r >>> selective prefixes only. Furthermore, if we want to support multiple >>> concurrent selective refreshes then the changes needed are very much al= ong >>> the lines of the solution suggested in the draft. >>> >>> Regards, >>> Keyur >>> >>> >>> >>> Many thx, >>> R. >>> >>> >>> >>> >>> On Tue, Jul 19, 2016 at 11:47 PM, Dongjie (Jimmy) >>> wrote: >>> >>>> Hi Tony, >>>> >>>> >>>> >>>> Please see some comments inline with [Jie]: >>>> >>>> >>>> >>>> *From:* Idr [mailto:idr-bounces@ietf.org] *On Behalf Of *Tony >>>> Przygienda >>>> *Sent:* Tuesday, July 19, 2016 6:04 PM >>>> *To:* Robert Raszuk; idr wg >>>> *Subject:* [Idr] Fwd: Slot request in IDR to present >>>> https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-optio= ns-00.txt >>>> >>>> >>>> >>>> Resending ... >>>> >>>> >>>> >>>> ---------- Forwarded message ---------- >>>> From: *Tony Przygienda* >>>> Date: Mon, Jul 11, 2016 at 3:04 PM >>>> Subject: Re: [Idr] Slot request in IDR to present >>>> https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-optio= ns-00.txt >>>> To: Robert Raszuk >>>> Cc: idr wg >>>> >>>> >>>> >>>> >>>> >>>> On Mon, Jul 11, 2016 at 1:47 PM, Robert Raszuk >>>> wrote: >>>> >>>> Hi Tony, >>>> >>>> >>>> >>>> Hey Robert, thanks for chiming in. Good questions. I speak here for >>>> myself, other authors of the draft may have differing opinions. >>>> >>>> >>>> >>>> >>>> >>>> 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 ? >>>> >>>> >>>> >>>> We didn't discuss that one through but the only logical conclusion for >>>> me is that the ORF/CP-ORF installed are respected (i.e. it's an implic= it >>>> AND). I see ORF as statefull, remote-pushed policy on the peer that is= not >>>> being flipped around all the time (albeit AFAIR there were some attemp= ts @ >>>> non-persistent, one shot ORF but that ended up expiring?) >>>> >>>> >>>> >>>> [Jie] I think the attempts you mentioned here are the one-time ORF >>>> drafts: draft-zeng-idr-one-time-prefix-orf and >>>> draft-dong-idr-one-time-ext-community-orf. After several revisions, th= ese >>>> drafts got expired due to lack of requirements at that time. If people >>>> found some new use cases of these kinds of mechanisms, the authors wou= ld be >>>> happy to bring them back to discussion. >>>> >>>> >>>> >>>> The motivation for this work were scenarios where a single-shot refres= h >>>> is needed, actually concurrent bunch of those based on configuration >>>> changes, peer having dropped received routes based on specs (A-D), in >>>> policy changes, joining VPNs, EVIs and so on. Putting ORF on a peer, >>>> refresh and remove ORFs is significantly heavier process that may inte= rfere >>>> on top with normal update process going on and needs to be done one-by= -one >>>> (since you have to wait for single BoRR/EoRR pair) unless one is very = smart >>>> about combining ORF possibly & playing with the DEFER/IMMEDIATEs. As w= e >>>> indicated, if the AFI/SAFI is covered by RTC and RTC is supported & on= e is >>>> willing to configure RTs for each subset of routes that may need >>>> refreshing, RT will be doing the same job just fine. >>>> >>>> >>>> >>>> [Jie] The motivations look similar to what we described for the >>>> one-time ORF drafts. >>>> >>>> >>>> >>>> >>>> >>>> Would you always carry ORF with separate Refresh_ID value ? >>>> >>>> >>>> >>>> Yes, Refresh-ID# is strictly monotonic so there is never a >>>> misunderstanding WHAT the BoRR belongs to. Observe that the draft does= NOT >>>> mandate that a request MUST be followed by according BoRR, only that B= oRRs >>>> must follow same sequence as requests (i.e. are also strictly monotoni= c). >>>> However, we should probably specify that options _and_ ORF can NOT be = mixed >>>> in the same type #3 message but it's either one or the other (and anyt= hing >>>> else is error). This will allow ORF operations like today + benefit of= the >>>> Refresh ID# on the BoRR so the IMMEDIATE can go on @ the same time as >>>> another request with higher Refresh ID# (de facto we allow multiple >>>> parallel refreshes as you see). In case of DEFER there will be simply= no >>>> BoRR for it. >>>> >>>> >>>> >>>> >>>> >>>> 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 entri= es >>>> 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 stat= e >>>> that Refresh_IDs have no impact to ORF ADDs or REMOVE actions - don't = you >>>> think ? >>>> >>>> >>>> >>>> I agree. Yes, ORF is kind of "permanent filter" on the peer while the >>>> intent of this draft is to have bunch of "small refreshes" going on @ = same >>>> time possibly (if you request the refreshes from a good implementation >>>> while low-end implementations may serialize the requests to simplify >>>> internal logic ;-). >>>> >>>> >>>> >>>> >>>> >>>> As far as current types why not add regular/extended community ? >>>> >>>> >>>> >>>> Discussion came up. Feeling was it's an immediate encroach on RT >>>> territory. I argued for it ;-) Ultimately, taking a more relaxed view= , we >>>> chose to wait and see what the response is and most pressing use cases >>>> people bring to it and then we start to define bits and bytes of the >>>> options supported, possibly borrowing to an extent from the ORF specs = ;-) >>>> As in "most sincere form of flattery" and such ... ;-) >>>> >>>> >>>> >>>> [Jie] Actually before the one-time ORF drafts were submitted, we >>>> initially considered to make it a =E2=80=9Cselective route refresh=E2= =80=9D mechanism. Then >>>> we realized that the filters will be quite similar to the ones already >>>> defined for ORF. In order to reuse the ORF filters, we then decided to >>>> define this mechanism as new =E2=80=9Cone-time=E2=80=9D ORF types. Ju= st to provide some >>>> background information since you also plan to reuse the format of the >>>> existing ORF types. >>>> >>>> >>>> >>>> Best regards, >>>> >>>> Jie >>>> >>>> >>>> >>>> -- tony >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> -- >>>> >>>> *We=E2=80=99ve heard that a million monkeys at a million keyboards cou= ld >>>> produce the complete works of Shakespeare; now, thanks to the Internet= , we >>>> know that is not true.* >>>> >>>> =E2=80=94Robert Wilensky >>>> >>> >>> >> > > _______________________________________________ > Idr mailing list > Idr@ietf.org > https://www.ietf.org/mailman/listinfo/idr > > --=20 *We=E2=80=99ve heard that a million monkeys at a million keyboards could pr= oduce the complete works of Shakespeare; now, thanks to the Internet, we know that is not true.* =E2=80=94Robert Wilensky --001a11409f9a70de21053827296a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Read the "longish" thread by now and between all= this "let's do filter/let's do pull (refresh)" I try to = take a step back to see the forest:

a) To validate Niloo= 's point: 'f an implementation chooses to drop things based on conf= iguration/policy (multicast EVPN routes) extending ORF will cause a complet= e refresh of EVPN (including type-2 MACs) unless you go and "install f= ilter type-2, then refresh, then remove-filter-2" and after requesting= type-6 =C2=A0(you can't defer remove-filter-2 step, otherwise you won&= #39;t receive type-2 updates anymore!) floods you with all MACs. Pub-sub wi= th a single "filter-list" is simply NOT a good model to request a= rbitrary pieces of routes missing (which is where the world is going, BGP d= atabase is sharding to the point specs are recommending to "drop when = you don't need it" and we have the need to ask for very specific s= ets @ given points in time [as the use cases describe]).=C2=A0
b) A much _bigger_ problem IMO is the fact that ORF language d= oes not seem to be an algebra, it's a program and you can only build a = closure of procedural programs by running them normally (not good to restri= ct sets you process). In less abstract terms a refresh with filters that ar= e OR'ed and AND'ed (first order logic transitive closure) determine= s the cone you need to walk on the RIB very easily (people implementing hea= vy-duty BGP will know precisely what that means) whereas any change to the = filter will cause a full walk on the RIB possibly (in case of arbitrary mix= of accepts and rejects) without a lot of possibly hard logic to write (I d= idn't think fully through it but I think it may be actually possible to= write something delivering closure from a generic ORF filter so it's a= n interesting discussion). Even if you can build the closure, you can only = run one at a time (one ORF filter) unless the peer does some crazy state-fu= l query optimization language to do wonders to squeeze multiple queries it = needs into a single ORFs it's doing (SQL query optimizers are _really_ = complex beasts) while the "you can put a filter on something to suppre= ss it on refresh but you can hammered with it anyway the moment you remove = it" persists.=C2=A0

For that 2 cases my take = =C2=A0is that it's better to move towards the model proposed by a "= ;filtered refresh" (independently of being co-author) rather than a &#= 39;pub-sub'.=C2=A0

As ultimate, wider angle vi= ew of the world.=C2=A0

BGP will be offered more cy= cles to run (it already is ) but not in the form of a single faster and fas= ter CPU anymore but in form of multiple cores/machines. A set of filtered r= efreshes can be parallelized fairly easily when requested. A single ORF fil= ter being manipulated on/off will as described in a) possibly cause huge sp= urious refreshes and in b) a single threat of execution serializing the syn= chronization between peers.=C2=A0

I hope that all = can be parsed ...=C2=A0

Very good discussion overa= ll no matter which way it goes ...=C2=A0

--- tony= =C2=A0


On Wed, Jul 20, 2016 at 3:14 PM, Robert Raszuk <robert@= raszuk.net> wrote:
Hi Keyur,

On the EVPN topic which defines BGP protocol extensions wit= hout any IDR WG review the more I hear about cases like you bring below (an= d this is not the first one btw) the more I think it is really quite badly = designed.=C2=A0

And su= ch bad protocol extensions should not be a justification to introduce even = more questionable knobs in BGP.=C2=A0

In this specific case just get all SAFI refreshed modulo to= RTC or ORF filters and you are done. Case solved :).

Best,
R.
=

<= br>
On Wed, Jul 20, 2016 at 11:05 PM, Keyur Patel= (keyupate) <keyupate@cisco.com> wrote:
Hi Robert,

One interesting use case is with EVPN address family where a new route= -type is introduced without a capability.=C2=A0 A PE may have had safi enab= led but not have accepted its route-type (or set of route-types) all mappin= g to a same RT. A transactional filter attempts to solve it.

We can clarify in the next revision of the draft.

One more comment inlined #Keyur

From: Robert Raszuk <robert@raszuk.net>
Date: Tuesday, July 19, 2016 at 3:2= 9 PM
To: Keyur Patel <keyupate@cisco.com>
Cc: "Dongjie (Jimmy)" <= ;jie.dong@huawei.c= om>, idr wg <id= r@ietf.org>
Subject: Re: [Idr] Fwd: Slot reques= t in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00= .txt

Hi Keyur,

The missing part seems to be justification if we really need "transact= ion based filters" as opposed to simply having permanent ones.=C2=A0

What real problem "transaction based filters" solve ? IMO the dra= ft needs to state it clearly.=C2=A0

The other point is that "permanent" are not really permanent anyw= ay .. they are installed from update to withdraw of a given filter - regard= less what filtering mechanism you choose (ORF, RTC, XYZ ...). And if you go= with the notion that permanent are sufficient the entire aparatus allowing you to have concurrent route refresh requests= in flight goes away :)

#Keyur: Ack your right. My reference to a permanent filter was in cont= ext of a session life time and I agree with you that it could be modified o= r withdrawn at any given time. I was trying to differentiate it from transa= ctional filters.

Regards,
Keyur

Thx,
r.


On Wed, Jul 20, 2016 at 12:18 AM, Keyur Patel (k= eyupate) <keyupate@cisco.com> wrote:
Robert, Dongjie,

Comments inlined #Keyur

From: Robert Raszuk <robert@raszuk.net>
Date: Tuesday, July 19, 2016 at 2:5= 2 PM
To: "Dongjie (Jimmy)" <= ;jie.dong@huawei.c= om>
Cc: idr wg <idr@ietf.org>
Subject: Re: [Idr] Fwd: Slot reques= t in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00= .txt

Hi Jie,

To me what is perhaps missing is just a new draft to define *Route Type* OR= F to address some of those EVPN new NLRI encodings.

#Keyur: ORFs are permanent filters. We wanted to decouple the transact= ion based filters (one time per refresh) from the permanent filters and hen= ce chose to modify refresh message as opposed to an ORF.=C2=A0

I am not that much convinced if one time ORF is needed as you are free to I= NSTALL and REMOVE ORF effectively producing one time behavior.

#Keyur: Ack.=C2=A0

Also existing Enhanced Route Refresh should work with ORF too.=C2=A0

#Keyur: There are modifications needed if the refresh is going to be f= or selective prefixes only. Furthermore, if we want to support multiple con= current selective refreshes then the changes needed are very much along the= lines of the solution suggested in the draft.

Regards,
Keyur=C2=A0



Many thx,
R.




On Tue, Jul 19, 2016 at 11:47 PM, Dongjie (Jimmy= ) <jie.dong@huawe= i.com> wrote:

Hi Tony,

=C2=A0=

Please see some comments in= line with [Jie]:

=C2=A0=

From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Tony Przygienda
Sent: Tuesday, July 19, 2016 6:04 PM
To: Robert Raszuk; idr wg
Subject: [Idr] Fwd: Slot request in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00= .txt

=C2=A0

Resending ...=C2=A0

=C2=A0

= ---------- Forwarded message ----------
From: Tony Przygienda <tonysietf@gmail.com>
Date: Mon, Jul 11, 2016 at 3:04 PM
Subject: Re: [Idr] Slot request in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00= .txt
To: Robert Raszuk <robert@raszuk.net>
Cc: idr wg <idr@ietf.o= rg>

=C2=A0

=C2=A0

On Mon, Jul 11, 2016 at 1:47 PM= , Robert Raszuk <= robert@raszuk.net> wrote:

Hi Tony,

=C2=A0

Hey Robert, thanks for chiming = in. Good questions. I speak here for myself, other authors of the draft may= have differing opinions.=C2=A0

=C2=A0

=C2=A0

Can you clarify what is the expected behaviour as far as per peer f= ilter-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 towar= ds a peer which pushed those ?=C2=A0

=C2=A0

We didn't discuss that one = through but the only logical conclusion for me is that the ORF/CP-ORF insta= lled are respected (i.e. it's an implicit AND). I see ORF as statefull,= remote-pushed policy on the peer that is not being flipped around all the time (albeit AFAIR there were some attempts @= non-persistent, one shot ORF but that ended up expiring?)

=C2=A0=

[Jie] I think the attempts = you mentioned here are the one-time ORF drafts: draft-zeng-idr-one-time-pre= fix-orf =C2=A0and draft-dong-idr-one-time-ext-community-orf. After several revisions, these drafts got expired due to lack of requireme= nts at that time. If people found some new use cases of these kinds of mech= anisms, the authors would be happy to bring them back to discussion.=

=C2=A0

The motivation for this work we= re scenarios where a single-shot refresh is needed, actually concurrent bun= ch of those based on configuration changes, peer having dropped received ro= utes based on specs (A-D), in policy changes, joining VPNs, EVIs and so on. Putting ORF on a peer, refresh and = remove ORFs is significantly heavier process that may interfere on top with= normal update process going on and needs to be done one-by-one (since you = have to wait for single BoRR/EoRR pair) unless one is very smart about combining ORF possibly & playing = with the DEFER/IMMEDIATEs. As we indicated, if the AFI/SAFI is covered by R= TC and RTC is supported & one is willing to configure RTs for each subs= et of routes that may need refreshing, RT will be doing the same job just fine.=C2=A0

=C2=A0=

[Jie] The motivations look = similar to what we described for the one-time ORF drafts.

=C2=A0

=C2=A0

Would you always carry ORF with separate Refresh_ID value ?=C2=A0

=C2=A0

Yes, Refresh-ID# is strictly mo= notonic so there is never a misunderstanding WHAT the BoRR belongs to. Obse= rve that the draft does NOT mandate that a request MUST be followed by acco= rding BoRR, only that BoRRs must follow same sequence as requests (i.e. are also strictly monotonic). However, we = should probably specify that options _and_ ORF can NOT be mixed in the same= type #3 message but it's either one or the other (and anything else is= error). This will allow ORF operations like today + benefit of the Refresh ID# =C2=A0on the BoRR so the IMMEDIATE= can go on @ the same time as another request with higher Refresh ID# (de f= acto we allow multiple parallel refreshes as you see).=C2=A0 In case of DEF= ER there will be simply no BoRR for it.=C2=A0

=C2=A0

=C2=A0

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 a= lready 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 ?=C2=A0

=C2=A0

I agree. Yes, ORF is kind of = =C2=A0"permanent filter" on the peer while the intent of this dra= ft is to have bunch of "small refreshes" going on @ same time pos= sibly (if you request the refreshes from a good implementation while low-end implementations may serialize the requests to simplify inter= nal logic ;-).=C2=A0

=C2=A0

=C2=A0

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

=C2=A0

Discussion came up. Feeling was= it's an immediate encroach on RT territory. I argued for it ;-) =C2=A0= Ultimately, taking a more relaxed view, we chose to wait and see what the r= esponse is and most pressing use cases people bring to it and then we start to define bits and bytes of the options supp= orted, possibly borrowing to an extent from the ORF specs ;-) =C2=A0As in &= quot;most sincere form of flattery" and such ... ;-)=C2=A0

=C2=A0=

[Jie] Actually before the o= ne-time ORF drafts were submitted, we initially considered to make it a =E2= =80=9Cselective route refresh=E2=80=9D mechanism. Then we realized that the filters will be quite similar to the ones alread= y defined for ORF. In order to reuse the ORF filters, we then decided to de= fine this mechanism as new =E2=80=9Cone-time=E2=80=9D ORF types.=C2=A0 Just= to provide some background information since you also plan to reuse the format of the existing ORF types. <= /p>

=C2=A0=

Best regards,=

Jie

= =C2=A0

-- tony= =C2=A0

=C2=A0<= u>



=C2=A0

--

We=E2=80=99ve heard that a million monkeys at a mil= lion keyboards could produce the complete works of Shakespeare; now, thanks= to the Internet, we know that is not true.=

=E2=80=94Robert Wilensky





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




--
=
We=E2=80=99ve heard that a million monkeys at a million keyboards c= ould produce the complete works of Shakespeare; now, thanks to the Internet= , we know that is not true.
= =E2=80=94Robert Wilensky
--001a11409f9a70de21053827296a-- From nobody Thu Jul 21 08:50:11 2016 Return-Path: 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 9A73312B031 for ; Thu, 21 Jul 2016 08:50:09 -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 0e6Y6hLWYdbW for ; Thu, 21 Jul 2016 08:50:06 -0700 (PDT) Received: from mail-qt0-x233.google.com (mail-qt0-x233.google.com [IPv6:2607:f8b0:400d:c0d::233]) (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 C475D12D0B4 for ; Thu, 21 Jul 2016 08:50:05 -0700 (PDT) Received: by mail-qt0-x233.google.com with SMTP id 52so46268297qtq.3 for ; Thu, 21 Jul 2016 08:50:05 -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:date:message-id:subject :from:to:cc; bh=XGlMPIhSEE4P07S+cOz6N2BExa1v59TS8AV1uc8kboU=; b=uZKSdl6CB3W3rZiHTrXid0otzmvvD4KtgYdVBVZnAIehM7x+//OE5vFgZELGAoG9cA OxP1cjAQmvaRFHJ5BjewgLCcJ+uv8wSpc0F14DijUGEKJ6WZiEyb8A5/e240vAfTNZ1S x/+MTBHPEsMkMz2e+oZm3100wXt7iI2mrJb5X0bUdk7NwXeTv9/lIgradfXocUulUUA5 VCA0JW3jx0pmidnL1qihp1ooUS4SAoBJCAu8MuPrSZk1XQvNZ5K4CSqMidzlaw7jcml6 jbiD4pNxCaUgcBeXk8p5VRiuNGGRriXvzgbowRzBcfGBxZy0VJ9RlaqSSU769WQ7zczx Agrw== 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:date :message-id:subject:from:to:cc; bh=XGlMPIhSEE4P07S+cOz6N2BExa1v59TS8AV1uc8kboU=; b=YLb0Px+d3KPgOU18nemcG/+zdTQvR5Rvm3hbStxc9iGh61FG9nFEIoUz2Rudl4cCR6 oBvvOYpBlvlhtGA47EBQrseYHhybnpqRHzyKpyRZ+AniwCwyh3Ujn191YcGIQD7LNS2H mOLMwVdi1Dcuc53bwzKxzN51yz9z+5h/U/ioF8aZpX3QoHW23m+YFg18YcijOdqVXLOI ldB3qDoVgacQF1xzonosLuHntguEFtbd+gaUGFaB3lbjdzHygjZh+w7vWSQvsvUxTF6p sGIVZjeIXodLioE774UBoUck11bo8q1Yr88byxWdr7ZCO1oMt1fTIUH/MftH9+x5Tncd qGmA== X-Gm-Message-State: ALyK8tKowdLOfTHZmKKsrCMlMQOVXvivSr96rp93e4uNiW3l3pvr7bUYtn+88v3Il35p0RIOo1R8gl1jahedRQ== MIME-Version: 1.0 X-Received: by 10.200.56.90 with SMTP id r26mr82599500qtb.37.1469116204796; Thu, 21 Jul 2016 08:50:04 -0700 (PDT) Sender: rraszuk@gmail.com Received: by 10.237.36.90 with HTTP; Thu, 21 Jul 2016 08:50:03 -0700 (PDT) Received: by 10.237.36.90 with HTTP; Thu, 21 Jul 2016 08:50:03 -0700 (PDT) In-Reply-To: References: <76CD132C3ADEF848BD84D028D243C92774EEF7CF@NKGEML515-MBX.china.huawei.com> Date: Thu, 21 Jul 2016 17:50:03 +0200 X-Google-Sender-Auth: mAY19Bz6AYtmcFjWKWTppmq9fO8 Message-ID: From: Robert Raszuk To: Tony Przygienda Content-Type: multipart/alternative; boundary=001a113fe4408554110538274583 Archived-At: Cc: "Keyur Patel \(keyupate\)" , idr wg Subject: Re: [Idr] Fwd: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jul 2016 15:50:09 -0000 --001a113fe4408554110538274583 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Tony, You have nicely summarized various discussed this week sub threads happening bith on and off the list. Except .. you did not list the most important .. to enumerate real protocol level use cases which would justify this addition. If we start with the problem (rather then just starting with "when we need subset of routes") then perhaps it will be easy to adopt this work or we go back and fix protocol encoding which are root cause of the problem you are trying to patch with solutions like selective overlapping route refresh messages. Best, R. On Jul 21, 2016 5:42 PM, "Tony Przygienda" wrote: Read the "longish" thread by now and between all this "let's do filter/let's do pull (refresh)" I try to take a step back to see the forest= : a) To validate Niloo's point: 'f an implementation chooses to drop things based on configuration/policy (multicast EVPN routes) extending ORF will cause a complete refresh of EVPN (including type-2 MACs) unless you go and "install filter type-2, then refresh, then remove-filter-2" and after requesting type-6 (you can't defer remove-filter-2 step, otherwise you won't receive type-2 updates anymore!) floods you with all MACs. Pub-sub with a single "filter-list" is simply NOT a good model to request arbitrary pieces of routes missing (which is where the world is going, BGP database is sharding to the point specs are recommending to "drop when you don't need it" and we have the need to ask for very specific sets @ given points in time [as the use cases describe]). b) A much _bigger_ problem IMO is the fact that ORF language does not seem to be an algebra, it's a program and you can only build a closure of procedural programs by running them normally (not good to restrict sets you process). In less abstract terms a refresh with filters that are OR'ed and AND'ed (first order logic transitive closure) determines the cone you need to walk on the RIB very easily (people implementing heavy-duty BGP will know precisely what that means) whereas any change to the filter will cause a full walk on the RIB possibly (in case of arbitrary mix of accepts and rejects) without a lot of possibly hard logic to write (I didn't think fully through it but I think it may be actually possible to write something delivering closure from a generic ORF filter so it's an interesting discussion). Even if you can build the closure, you can only run one at a time (one ORF filter) unless the peer does some crazy state-ful query optimization language to do wonders to squeeze multiple queries it needs into a single ORFs it's doing (SQL query optimizers are _really_ complex beasts) while the "you can put a filter on something to suppress it on refresh but you can hammered with it anyway the moment you remove it" persists. For that 2 cases my take is that it's better to move towards the model proposed by a "filtered refresh" (independently of being co-author) rather than a 'pub-sub'. As ultimate, wider angle view of the world. BGP will be offered more cycles to run (it already is ) but not in the form of a single faster and faster CPU anymore but in form of multiple cores/machines. A set of filtered refreshes can be parallelized fairly easily when requested. A single ORF filter being manipulated on/off will as described in a) possibly cause huge spurious refreshes and in b) a single threat of execution serializing the synchronization between peers. I hope that all can be parsed ... Very good discussion overall no matter which way it goes ... --- tony On Wed, Jul 20, 2016 at 3:14 PM, Robert Raszuk wrote: > Hi Keyur, > > On the EVPN topic which defines BGP protocol extensions without any IDR W= G > review the more I hear about cases like you bring below (and this is not > the first one btw) the more I think it is really quite badly designed. > > And such bad protocol extensions should not be a justification to > introduce even more questionable knobs in BGP. > > In this specific case just get all SAFI refreshed modulo to RTC or ORF > filters and you are done. Case solved :). > > Best, > R. > > > On Wed, Jul 20, 2016 at 11:05 PM, Keyur Patel (keyupate) < > keyupate@cisco.com> wrote: > >> Hi Robert, >> >> One interesting use case is with EVPN address family where a new >> route-type is introduced without a capability. A PE may have had safi >> enabled but not have accepted its route-type (or set of route-types) all >> mapping to a same RT. A transactional filter attempts to solve it. >> >> We can clarify in the next revision of the draft. >> >> One more comment inlined #Keyur >> >> From: Robert Raszuk >> Date: Tuesday, July 19, 2016 at 3:29 PM >> To: Keyur Patel >> Cc: "Dongjie (Jimmy)" , idr wg >> Subject: Re: [Idr] Fwd: Slot request in IDR to present >> https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options= -00.txt >> >> Hi Keyur, >> >> The missing part seems to be justification if we really need "transactio= n >> based filters" as opposed to simply having permanent ones. >> >> What real problem "transaction based filters" solve ? IMO the draft need= s >> to state it clearly. >> >> The other point is that "permanent" are not really permanent anyway .. >> they are installed from update to withdraw of a given filter - regardles= s >> what filtering mechanism you choose (ORF, RTC, XYZ ...). And if you go w= ith >> the notion that permanent are sufficient the entire aparatus allowing yo= u >> to have concurrent route refresh requests in flight goes away :) >> >> #Keyur: Ack your right. My reference to a permanent filter was in contex= t >> of a session life time and I agree with you that it could be modified or >> withdrawn at any given time. I was trying to differentiate it from >> transactional filters. >> >> Regards, >> Keyur >> >> Thx, >> r. >> >> >> On Wed, Jul 20, 2016 at 12:18 AM, Keyur Patel (keyupate) < >> keyupate@cisco.com> wrote: >> >>> Robert, Dongjie, >>> >>> Comments inlined #Keyur >>> >>> From: Robert Raszuk >>> Date: Tuesday, July 19, 2016 at 2:52 PM >>> To: "Dongjie (Jimmy)" >>> Cc: idr wg >>> Subject: Re: [Idr] Fwd: Slot request in IDR to present >>> https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-option= s-00.txt >>> >>> Hi Jie, >>> >>> To me what is perhaps missing is just a new draft to define *Route Type= * >>> ORF to address some of those EVPN new NLRI encodings. >>> >>> #Keyur: ORFs are permanent filters. We wanted to decouple the >>> transaction based filters (one time per refresh) from the permanent fil= ters >>> and hence chose to modify refresh message as opposed to an ORF. >>> >>> I am not that much convinced if one time ORF is needed as you are free >>> to INSTALL and REMOVE ORF effectively producing one time behavior. >>> >>> #Keyur: Ack. >>> >>> Also existing Enhanced Route Refresh should work with ORF too. >>> >>> #Keyur: There are modifications needed if the refresh is going to be fo= r >>> selective prefixes only. Furthermore, if we want to support multiple >>> concurrent selective refreshes then the changes needed are very much al= ong >>> the lines of the solution suggested in the draft. >>> >>> Regards, >>> Keyur >>> >>> >>> >>> Many thx, >>> R. >>> >>> >>> >>> >>> On Tue, Jul 19, 2016 at 11:47 PM, Dongjie (Jimmy) >>> wrote: >>> >>>> Hi Tony, >>>> >>>> >>>> >>>> Please see some comments inline with [Jie]: >>>> >>>> >>>> >>>> *From:* Idr [mailto:idr-bounces@ietf.org] *On Behalf Of *Tony >>>> Przygienda >>>> *Sent:* Tuesday, July 19, 2016 6:04 PM >>>> *To:* Robert Raszuk; idr wg >>>> *Subject:* [Idr] Fwd: Slot request in IDR to present >>>> https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-optio= ns-00.txt >>>> >>>> >>>> >>>> Resending ... >>>> >>>> >>>> >>>> ---------- Forwarded message ---------- >>>> From: *Tony Przygienda* >>>> Date: Mon, Jul 11, 2016 at 3:04 PM >>>> Subject: Re: [Idr] Slot request in IDR to present >>>> https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-optio= ns-00.txt >>>> To: Robert Raszuk >>>> Cc: idr wg >>>> >>>> >>>> >>>> >>>> >>>> On Mon, Jul 11, 2016 at 1:47 PM, Robert Raszuk >>>> wrote: >>>> >>>> Hi Tony, >>>> >>>> >>>> >>>> Hey Robert, thanks for chiming in. Good questions. I speak here for >>>> myself, other authors of the draft may have differing opinions. >>>> >>>> >>>> >>>> >>>> >>>> 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 ? >>>> >>>> >>>> >>>> We didn't discuss that one through but the only logical conclusion for >>>> me is that the ORF/CP-ORF installed are respected (i.e. it's an implic= it >>>> AND). I see ORF as statefull, remote-pushed policy on the peer that is= not >>>> being flipped around all the time (albeit AFAIR there were some attemp= ts @ >>>> non-persistent, one shot ORF but that ended up expiring?) >>>> >>>> >>>> >>>> [Jie] I think the attempts you mentioned here are the one-time ORF >>>> drafts: draft-zeng-idr-one-time-prefix-orf and >>>> draft-dong-idr-one-time-ext-community-orf. After several revisions, th= ese >>>> drafts got expired due to lack of requirements at that time. If people >>>> found some new use cases of these kinds of mechanisms, the authors wou= ld be >>>> happy to bring them back to discussion. >>>> >>>> >>>> >>>> The motivation for this work were scenarios where a single-shot refres= h >>>> is needed, actually concurrent bunch of those based on configuration >>>> changes, peer having dropped received routes based on specs (A-D), in >>>> policy changes, joining VPNs, EVIs and so on. Putting ORF on a peer, >>>> refresh and remove ORFs is significantly heavier process that may inte= rfere >>>> on top with normal update process going on and needs to be done one-by= -one >>>> (since you have to wait for single BoRR/EoRR pair) unless one is very = smart >>>> about combining ORF possibly & playing with the DEFER/IMMEDIATEs. As w= e >>>> indicated, if the AFI/SAFI is covered by RTC and RTC is supported & on= e is >>>> willing to configure RTs for each subset of routes that may need >>>> refreshing, RT will be doing the same job just fine. >>>> >>>> >>>> >>>> [Jie] The motivations look similar to what we described for the >>>> one-time ORF drafts. >>>> >>>> >>>> >>>> >>>> >>>> Would you always carry ORF with separate Refresh_ID value ? >>>> >>>> >>>> >>>> Yes, Refresh-ID# is strictly monotonic so there is never a >>>> misunderstanding WHAT the BoRR belongs to. Observe that the draft does= NOT >>>> mandate that a request MUST be followed by according BoRR, only that B= oRRs >>>> must follow same sequence as requests (i.e. are also strictly monotoni= c). >>>> However, we should probably specify that options _and_ ORF can NOT be = mixed >>>> in the same type #3 message but it's either one or the other (and anyt= hing >>>> else is error). This will allow ORF operations like today + benefit of= the >>>> Refresh ID# on the BoRR so the IMMEDIATE can go on @ the same time as >>>> another request with higher Refresh ID# (de facto we allow multiple >>>> parallel refreshes as you see). In case of DEFER there will be simply= no >>>> BoRR for it. >>>> >>>> >>>> >>>> >>>> >>>> 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 entri= es >>>> 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 stat= e >>>> that Refresh_IDs have no impact to ORF ADDs or REMOVE actions - don't = you >>>> think ? >>>> >>>> >>>> >>>> I agree. Yes, ORF is kind of "permanent filter" on the peer while the >>>> intent of this draft is to have bunch of "small refreshes" going on @ = same >>>> time possibly (if you request the refreshes from a good implementation >>>> while low-end implementations may serialize the requests to simplify >>>> internal logic ;-). >>>> >>>> >>>> >>>> >>>> >>>> As far as current types why not add regular/extended community ? >>>> >>>> >>>> >>>> Discussion came up. Feeling was it's an immediate encroach on RT >>>> territory. I argued for it ;-) Ultimately, taking a more relaxed view= , we >>>> chose to wait and see what the response is and most pressing use cases >>>> people bring to it and then we start to define bits and bytes of the >>>> options supported, possibly borrowing to an extent from the ORF specs = ;-) >>>> As in "most sincere form of flattery" and such ... ;-) >>>> >>>> >>>> >>>> [Jie] Actually before the one-time ORF drafts were submitted, we >>>> initially considered to make it a =E2=80=9Cselective route refresh=E2= =80=9D mechanism. Then >>>> we realized that the filters will be quite similar to the ones already >>>> defined for ORF. In order to reuse the ORF filters, we then decided to >>>> define this mechanism as new =E2=80=9Cone-time=E2=80=9D ORF types. Ju= st to provide some >>>> background information since you also plan to reuse the format of the >>>> existing ORF types. >>>> >>>> >>>> >>>> Best regards, >>>> >>>> Jie >>>> >>>> >>>> >>>> -- tony >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> -- >>>> >>>> *We=E2=80=99ve heard that a million monkeys at a million keyboards cou= ld >>>> produce the complete works of Shakespeare; now, thanks to the Internet= , we >>>> know that is not true.* >>>> >>>> =E2=80=94Robert Wilensky >>>> >>> >>> >> > > _______________________________________________ > Idr mailing list > Idr@ietf.org > https://www.ietf.org/mailman/listinfo/idr > > --=20 *We=E2=80=99ve heard that a million monkeys at a million keyboards could pr= oduce the complete works of Shakespeare; now, thanks to the Internet, we know that is not true.* =E2=80=94Robert Wilensky --001a113fe4408554110538274583 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Tony,

You have nicely summarized various discussed this week sub t= hreads happening bith on and off the list.

Except .. you did not list the most important .. to enumerat= e real protocol level use cases which would justify this addition.

If we start with the problem (rather then just starting with= "when we need subset of routes") then perhaps it will be easy to= adopt this work or we go back and fix protocol encoding which are root cau= se of the problem you are trying to patch with solutions like selective ove= rlapping route refresh messages.

Best,
R.


On Jul 21, 2016 5= :42 PM, "Tony Przygienda" <tonysietf@gmail.com> wrote:
Read the "longish" thread by now an= d between all this "let's do filter/let's do pull (refresh)&qu= ot; I try to take a step back to see the forest:

a) To v= alidate Niloo's point: 'f an implementation chooses to drop things = based on configuration/policy (multicast EVPN routes) extending ORF will ca= use a complete refresh of EVPN (including type-2 MACs) unless you go and &q= uot;install filter type-2, then refresh, then remove-filter-2" and aft= er requesting type-6 =C2=A0(you can't defer remove-filter-2 step, other= wise you won't receive type-2 updates anymore!) floods you with all MAC= s. Pub-sub with a single "filter-list" is simply NOT a good model= to request arbitrary pieces of routes missing (which is where the world is= going, BGP database is sharding to the point specs are recommending to &qu= ot;drop when you don't need it" and we have the need to ask for ve= ry specific sets @ given points in time [as the use cases describe]).=C2=A0=

b) A much _bigger_ problem IMO is the fact that O= RF language does not seem to be an algebra, it's a program and you can = only build a closure of procedural programs by running them normally (not g= ood to restrict sets you process). In less abstract terms a refresh with fi= lters that are OR'ed and AND'ed (first order logic transitive closu= re) determines the cone you need to walk on the RIB very easily (people imp= lementing heavy-duty BGP will know precisely what that means) whereas any c= hange to the filter will cause a full walk on the RIB possibly (in case of = arbitrary mix of accepts and rejects) without a lot of possibly hard logic = to write (I didn't think fully through it but I think it may be actuall= y possible to write something delivering closure from a generic ORF filter = so it's an interesting discussion). Even if you can build the closure, = you can only run one at a time (one ORF filter) unless the peer does some c= razy state-ful query optimization language to do wonders to squeeze multipl= e queries it needs into a single ORFs it's doing (SQL query optimizers = are _really_ complex beasts) while the "you can put a filter on someth= ing to suppress it on refresh but you can hammered with it anyway the momen= t you remove it" persists.=C2=A0

For that 2 c= ases my take =C2=A0is that it's better to move towards the model propos= ed by a "filtered refresh" (independently of being co-author) rat= her than a 'pub-sub'.=C2=A0

As ultimate, w= ider angle view of the world.=C2=A0

BGP will be of= fered more cycles to run (it already is ) but not in the form of a single f= aster and faster CPU anymore but in form of multiple cores/machines. A set = of filtered refreshes can be parallelized fairly easily when requested. A s= ingle ORF filter being manipulated on/off will as described in a) possibly = cause huge spurious refreshes and in b) a single threat of execution serial= izing the synchronization between peers.=C2=A0

I h= ope that all can be parsed ...=C2=A0

Very good dis= cussion overall no matter which way it goes ...=C2=A0

--- tony=C2=A0


On Wed, Jul 20, 2016 at 3:14 PM, Robert Raszuk <robert@raszuk.n= et> wrote:
Hi Keyur,

On the EVPN topic which defines = BGP protocol extensions without any IDR WG review the more I hear about cas= es like you bring below (and this is not the first one btw) the more I thin= k it is really quite badly designed.=C2=A0

And such bad protocol extensions should not be a justi= fication to introduce even more questionable knobs in BGP.=C2=A0

In this specific case just get a= ll SAFI refreshed modulo to RTC or ORF filters and you are done. Case solve= d :).

Best,
R.


On Wed, Jul 20, 2016 at 11:05 = PM, Keyur Patel (keyupate) <keyupate@cisco.com> wrote:
<= blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px= #ccc solid;padding-left:1ex">
Hi Robert,

One interesting use case is with EVPN address family where a new route= -type is introduced without a capability.=C2=A0 A PE may have had safi enab= led but not have accepted its route-type (or set of route-types) all mappin= g to a same RT. A transactional filter attempts to solve it.

We can clarify in the next revision of the draft.

One more comment inlined #Keyur

From: Robert Raszuk <robert@raszuk.net>
Date: Tuesday, July 19, 2016 at 3:2= 9 PM
To: Keyur Patel <keyupate@cisco.com>
Cc: "Dongjie (Jimmy)" <= ;jie.dong@huawei.c= om>, idr wg <id= r@ietf.org>
Subject: Re: [Idr] Fwd: Slot reques= t in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00= .txt

Hi Keyur,

The missing part seems to be justification if we really need "transact= ion based filters" as opposed to simply having permanent ones.=C2=A0

What real problem "transaction based filters" solve ? IMO the dra= ft needs to state it clearly.=C2=A0

The other point is that "permanent" are not really permanent anyw= ay .. they are installed from update to withdraw of a given filter - regard= less what filtering mechanism you choose (ORF, RTC, XYZ ...). And if you go= with the notion that permanent are sufficient the entire aparatus allowing you to have concurrent route refresh requests= in flight goes away :)

#Keyur: Ack your right. My reference to a permanent filter was in cont= ext of a session life time and I agree with you that it could be modified o= r withdrawn at any given time. I was trying to differentiate it from transa= ctional filters.

Regards,
Keyur

Thx,
r.


On Wed, Jul 20, 2016 at 12:18 AM, Keyur Patel (k= eyupate) <keyupate@cisco.com> wrote:
Robert, Dongjie,

Comments inlined #Keyur

From: Robert Raszuk <robert@raszuk.net>
Date: Tuesday, July 19, 2016 at 2:5= 2 PM
To: "Dongjie (Jimmy)" <= ;jie.dong@huawei.c= om>
Cc: idr wg <idr@ietf.org>
Subject: Re: [Idr] Fwd: Slot reques= t in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00= .txt

Hi Jie,

To me what is perhaps missing is just a new draft to define *Route Type* OR= F to address some of those EVPN new NLRI encodings.

#Keyur: ORFs are permanent filters. We wanted to decouple the transact= ion based filters (one time per refresh) from the permanent filters and hen= ce chose to modify refresh message as opposed to an ORF.=C2=A0

I am not that much convinced if one time ORF is needed as you are free to I= NSTALL and REMOVE ORF effectively producing one time behavior.

#Keyur: Ack.=C2=A0

Also existing Enhanced Route Refresh should work with ORF too.=C2=A0

#Keyur: There are modifications needed if the refresh is going to be f= or selective prefixes only. Furthermore, if we want to support multiple con= current selective refreshes then the changes needed are very much along the= lines of the solution suggested in the draft.

Regards,
Keyur=C2=A0



Many thx,
R.




On Tue, Jul 19, 2016 at 11:47 PM, Dongjie (Jimmy= ) <jie.dong@huawe= i.com> wrote:

Hi Tony,

=C2=A0=

Please see some comments in= line with [Jie]:

=C2=A0=

From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Tony Przygienda
Sent: Tuesday, July 19, 2016 6:04 PM
To: Robert Raszuk; idr wg
Subject: [Idr] Fwd: Slot request in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00= .txt

=C2=A0

Resending ...=C2=A0

=C2=A0

= ---------- Forwarded message ----------
From: Tony Przygienda <tonysietf@gmail.com>
Date: Mon, Jul 11, 2016 at 3:04 PM
Subject: Re: [Idr] Slot request in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00= .txt
To: Robert Raszuk <robert@raszuk.net>
Cc: idr wg <idr@ietf.o= rg>

=C2=A0

=C2=A0

On Mon, Jul 11, 2016 at 1:47 PM= , Robert Raszuk <= robert@raszuk.net> wrote:

Hi Tony,

=C2=A0

Hey Robert, thanks for chiming = in. Good questions. I speak here for myself, other authors of the draft may= have differing opinions.=C2=A0

=C2=A0

=C2=A0

Can you clarify what is the expected behaviour as far as per peer f= ilter-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 towar= ds a peer which pushed those ?=C2=A0

=C2=A0

We didn't discuss that one = through but the only logical conclusion for me is that the ORF/CP-ORF insta= lled are respected (i.e. it's an implicit AND). I see ORF as statefull,= remote-pushed policy on the peer that is not being flipped around all the time (albeit AFAIR there were some attempts @= non-persistent, one shot ORF but that ended up expiring?)

=C2=A0=

[Jie] I think the attempts = you mentioned here are the one-time ORF drafts: draft-zeng-idr-one-time-pre= fix-orf =C2=A0and draft-dong-idr-one-time-ext-community-orf. After several revisions, these drafts got expired due to lack of requireme= nts at that time. If people found some new use cases of these kinds of mech= anisms, the authors would be happy to bring them back to discussion.=

=C2=A0

The motivation for this work we= re scenarios where a single-shot refresh is needed, actually concurrent bun= ch of those based on configuration changes, peer having dropped received ro= utes based on specs (A-D), in policy changes, joining VPNs, EVIs and so on. Putting ORF on a peer, refresh and = remove ORFs is significantly heavier process that may interfere on top with= normal update process going on and needs to be done one-by-one (since you = have to wait for single BoRR/EoRR pair) unless one is very smart about combining ORF possibly & playing = with the DEFER/IMMEDIATEs. As we indicated, if the AFI/SAFI is covered by R= TC and RTC is supported & one is willing to configure RTs for each subs= et of routes that may need refreshing, RT will be doing the same job just fine.=C2=A0

=C2=A0=

[Jie] The motivations look = similar to what we described for the one-time ORF drafts.

=C2=A0

=C2=A0

Would you always carry ORF with separate Refresh_ID value ?=C2=A0

=C2=A0

Yes, Refresh-ID# is strictly mo= notonic so there is never a misunderstanding WHAT the BoRR belongs to. Obse= rve that the draft does NOT mandate that a request MUST be followed by acco= rding BoRR, only that BoRRs must follow same sequence as requests (i.e. are also strictly monotonic). However, we = should probably specify that options _and_ ORF can NOT be mixed in the same= type #3 message but it's either one or the other (and anything else is= error). This will allow ORF operations like today + benefit of the Refresh ID# =C2=A0on the BoRR so the IMMEDIATE= can go on @ the same time as another request with higher Refresh ID# (de f= acto we allow multiple parallel refreshes as you see).=C2=A0 In case of DEF= ER there will be simply no BoRR for it.=C2=A0

=C2=A0

=C2=A0

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 a= lready 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 ?=C2=A0

=C2=A0

I agree. Yes, ORF is kind of = =C2=A0"permanent filter" on the peer while the intent of this dra= ft is to have bunch of "small refreshes" going on @ same time pos= sibly (if you request the refreshes from a good implementation while low-end implementations may serialize the requests to simplify inter= nal logic ;-).=C2=A0

=C2=A0

=C2=A0

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

=C2=A0

Discussion came up. Feeling was= it's an immediate encroach on RT territory. I argued for it ;-) =C2=A0= Ultimately, taking a more relaxed view, we chose to wait and see what the r= esponse is and most pressing use cases people bring to it and then we start to define bits and bytes of the options supp= orted, possibly borrowing to an extent from the ORF specs ;-) =C2=A0As in &= quot;most sincere form of flattery" and such ... ;-)=C2=A0

=C2=A0=

[Jie] Actually before the o= ne-time ORF drafts were submitted, we initially considered to make it a =E2= =80=9Cselective route refresh=E2=80=9D mechanism. Then we realized that the filters will be quite similar to the ones alread= y defined for ORF. In order to reuse the ORF filters, we then decided to de= fine this mechanism as new =E2=80=9Cone-time=E2=80=9D ORF types.=C2=A0 Just= to provide some background information since you also plan to reuse the format of the existing ORF types. <= /p>

=C2=A0=

Best regards,=

Jie

= =C2=A0

-- tony= =C2=A0

=C2=A0<= u>



=C2=A0

--

We=E2=80=99ve heard that a million monkeys at a mil= lion keyboards could produce the complete works of Shakespeare; now, thanks= to the Internet, we know that is not true.=

=E2=80=94Robert Wilensky





______________________________________= _________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr




--
We=E2=80=99ve heard that a million monkeys at a million ke= yboards could produce the complete works of Shakespeare; now, thanks to the= Internet, we know that is not true.
=E2=80=94Robert Wilensky

--001a113fe4408554110538274583-- From nobody Thu Jul 21 09:06:46 2016 Return-Path: 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 CE9DF12D78E for ; Thu, 21 Jul 2016 09:06:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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 4wIMCq6yYJPC for ; Thu, 21 Jul 2016 09:06:31 -0700 (PDT) Received: from mail-it0-x230.google.com (mail-it0-x230.google.com [IPv6:2607:f8b0:4001:c0b::230]) (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 E815D12D754 for ; Thu, 21 Jul 2016 09:06:30 -0700 (PDT) Received: by mail-it0-x230.google.com with SMTP id j124so22303568ith.1 for ; Thu, 21 Jul 2016 09:06:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Zuu5Q7lGuvo4F6O6YS4iMjp4PiMhgCT/pMKY/qdrd6Q=; b=mEGNoeWbUFlnKK9oWIxfO6Jix3BmIdDbZn437Tcf6xlICjfQeXZEaOmsQav1dEQmhe hKa+dLJem7bc9PN7OeWVJkvedgMBrHX6KELjieNZX4hfte2R5zFt+c0bQ+r6KKHS3hYM buxnCLlfNxMWSPYWzeuJM8kHrokXX8QNu8y2CWWdKLqgldllwW8+yJbG7SF8c0KlUJt5 RWDPsKVdecLuxbQUqTsXkHSiVWHxG30JESwfdAb9uZk5uOil0wd3tEoYRoR0xwPHUMrh m/cbw5J6OO8TYuDnntGd+hJCydrbY7Wep06VURKOjz3aVy9MYc70ftCa8jdEmhRX+3gl ZX6Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Zuu5Q7lGuvo4F6O6YS4iMjp4PiMhgCT/pMKY/qdrd6Q=; b=llHqGOLoVyfUSqKyhWtPBI8y2RkNPN59De6gPfxOarsOxgTG7Ij+o+LrmVCOkHmuVs y7QtfA/TPPkTd+Ul/oj6mq67ikpQjEGf417xrYo4I1aiEd/ygSr/709phNul1LDk3Ns1 8W+6Mn5JXOd4Bcv0z3UFPsfmXMK64aMLfN4xqlMa7d9bdjvddPSyvsahcqgUeuEEqf0u LKYEWK+l9EP/SVsIHu9iTp+qDYxJ64zyKrUVII7OUy+VR1bf+HsN7AJ1EMxx0m6lX1Pm WvKomA/4EsMk99epv9vWLSwINTxpaxH9w+B4aU/edMaLxztV8pgB4HbMmlZa0p0zDKOV QZqg== X-Gm-Message-State: ALyK8tI5b9WUErZJQxMX7WKxtUWmsDWsLg8pB7D8Krqloh3RYE8DjT11oa8xBo5QRFRZ532rM8XcargeaGkZHw== X-Received: by 10.36.87.140 with SMTP id u134mr15366683ita.38.1469117189175; Thu, 21 Jul 2016 09:06:29 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.158.82 with HTTP; Thu, 21 Jul 2016 09:05:49 -0700 (PDT) In-Reply-To: References: <76CD132C3ADEF848BD84D028D243C92774EEF7CF@NKGEML515-MBX.china.huawei.com> From: Tony Przygienda Date: Thu, 21 Jul 2016 09:05:49 -0700 Message-ID: To: Robert Raszuk Content-Type: multipart/alternative; boundary=001a1135018c3200fb0538278021 Archived-At: Cc: "Keyur Patel \(keyupate\)" , idr wg Subject: Re: [Idr] Fwd: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jul 2016 16:06:45 -0000 --001a1135018c3200fb0538278021 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Robert, in the draft there are enough of first examples, I repeated several times other ones we were seeing outside the idr room and later and each time it seems it is being dismissed and discussion goes into abstract "let's do publish-subscribe because it's better". So I won't repeat all that again. I suggest we will update the draft with more and more of stuff we saw and justified talking about it. You didn't respond to any of the "what to do with type-6 refresh" or "how will I make one ORF filter update multiple subsets [possibly disjoint] I need to refresh without getting flooded to death with the AFI/SAFI stuff" and "how will I implement ORF except a full walk on any change" which happen to be pretty massive issues if you want decent BGP convergence on more and more AFI/SAFIs, routes, types & other zoo sneaking upon BGP ... sorry if I'm a tad acerbic ... --- tony On Thu, Jul 21, 2016 at 8:50 AM, Robert Raszuk wrote: > Tony, > > You have nicely summarized various discussed this week sub threads > happening bith on and off the list. > > Except .. you did not list the most important .. to enumerate real > protocol level use cases which would justify this addition. > > If we start with the problem (rather then just starting with "when we nee= d > subset of routes") then perhaps it will be easy to adopt this work or we = go > back and fix protocol encoding which are root cause of the problem you ar= e > trying to patch with solutions like selective overlapping route refresh > messages. > > Best, > R. > > On Jul 21, 2016 5:42 PM, "Tony Przygienda" wrote: > > Read the "longish" thread by now and between all this "let's do > filter/let's do pull (refresh)" I try to take a step back to see the fore= st: > > a) To validate Niloo's point: 'f an implementation chooses to drop things > based on configuration/policy (multicast EVPN routes) extending ORF will > cause a complete refresh of EVPN (including type-2 MACs) unless you go an= d > "install filter type-2, then refresh, then remove-filter-2" and after > requesting type-6 (you can't defer remove-filter-2 step, otherwise you > won't receive type-2 updates anymore!) floods you with all MACs. Pub-sub > with a single "filter-list" is simply NOT a good model to request arbitra= ry > pieces of routes missing (which is where the world is going, BGP database > is sharding to the point specs are recommending to "drop when you don't > need it" and we have the need to ask for very specific sets @ given point= s > in time [as the use cases describe]). > > b) A much _bigger_ problem IMO is the fact that ORF language does not see= m > to be an algebra, it's a program and you can only build a closure of > procedural programs by running them normally (not good to restrict sets y= ou > process). In less abstract terms a refresh with filters that are OR'ed an= d > AND'ed (first order logic transitive closure) determines the cone you nee= d > to walk on the RIB very easily (people implementing heavy-duty BGP will > know precisely what that means) whereas any change to the filter will cau= se > a full walk on the RIB possibly (in case of arbitrary mix of accepts and > rejects) without a lot of possibly hard logic to write (I didn't think > fully through it but I think it may be actually possible to write somethi= ng > delivering closure from a generic ORF filter so it's an interesting > discussion). Even if you can build the closure, you can only run one at a > time (one ORF filter) unless the peer does some crazy state-ful query > optimization language to do wonders to squeeze multiple queries it needs > into a single ORFs it's doing (SQL query optimizers are _really_ complex > beasts) while the "you can put a filter on something to suppress it on > refresh but you can hammered with it anyway the moment you remove it" > persists. > > For that 2 cases my take is that it's better to move towards the model > proposed by a "filtered refresh" (independently of being co-author) rathe= r > than a 'pub-sub'. > > As ultimate, wider angle view of the world. > > BGP will be offered more cycles to run (it already is ) but not in the > form of a single faster and faster CPU anymore but in form of multiple > cores/machines. A set of filtered refreshes can be parallelized fairly > easily when requested. A single ORF filter being manipulated on/off will = as > described in a) possibly cause huge spurious refreshes and in b) a single > threat of execution serializing the synchronization between peers. > > I hope that all can be parsed ... > > Very good discussion overall no matter which way it goes ... > > --- tony > > > On Wed, Jul 20, 2016 at 3:14 PM, Robert Raszuk wrote: > >> Hi Keyur, >> >> On the EVPN topic which defines BGP protocol extensions without any IDR >> WG review the more I hear about cases like you bring below (and this is = not >> the first one btw) the more I think it is really quite badly designed. >> >> And such bad protocol extensions should not be a justification to >> introduce even more questionable knobs in BGP. >> >> In this specific case just get all SAFI refreshed modulo to RTC or ORF >> filters and you are done. Case solved :). >> >> Best, >> R. >> >> >> On Wed, Jul 20, 2016 at 11:05 PM, Keyur Patel (keyupate) < >> keyupate@cisco.com> wrote: >> >>> Hi Robert, >>> >>> One interesting use case is with EVPN address family where a new >>> route-type is introduced without a capability. A PE may have had safi >>> enabled but not have accepted its route-type (or set of route-types) al= l >>> mapping to a same RT. A transactional filter attempts to solve it. >>> >>> We can clarify in the next revision of the draft. >>> >>> One more comment inlined #Keyur >>> >>> From: Robert Raszuk >>> Date: Tuesday, July 19, 2016 at 3:29 PM >>> To: Keyur Patel >>> Cc: "Dongjie (Jimmy)" , idr wg >>> Subject: Re: [Idr] Fwd: Slot request in IDR to present >>> https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-option= s-00.txt >>> >>> Hi Keyur, >>> >>> The missing part seems to be justification if we really need >>> "transaction based filters" as opposed to simply having permanent ones. >>> >>> What real problem "transaction based filters" solve ? IMO the draft >>> needs to state it clearly. >>> >>> The other point is that "permanent" are not really permanent anyway .. >>> they are installed from update to withdraw of a given filter - regardle= ss >>> what filtering mechanism you choose (ORF, RTC, XYZ ...). And if you go = with >>> the notion that permanent are sufficient the entire aparatus allowing y= ou >>> to have concurrent route refresh requests in flight goes away :) >>> >>> #Keyur: Ack your right. My reference to a permanent filter was in >>> context of a session life time and I agree with you that it could be >>> modified or withdrawn at any given time. I was trying to differentiate = it >>> from transactional filters. >>> >>> Regards, >>> Keyur >>> >>> Thx, >>> r. >>> >>> >>> On Wed, Jul 20, 2016 at 12:18 AM, Keyur Patel (keyupate) < >>> keyupate@cisco.com> wrote: >>> >>>> Robert, Dongjie, >>>> >>>> Comments inlined #Keyur >>>> >>>> From: Robert Raszuk >>>> Date: Tuesday, July 19, 2016 at 2:52 PM >>>> To: "Dongjie (Jimmy)" >>>> Cc: idr wg >>>> Subject: Re: [Idr] Fwd: Slot request in IDR to present >>>> https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-optio= ns-00.txt >>>> >>>> Hi Jie, >>>> >>>> To me what is perhaps missing is just a new draft to define *Route >>>> Type* ORF to address some of those EVPN new NLRI encodings. >>>> >>>> #Keyur: ORFs are permanent filters. We wanted to decouple the >>>> transaction based filters (one time per refresh) from the permanent fi= lters >>>> and hence chose to modify refresh message as opposed to an ORF. >>>> >>>> I am not that much convinced if one time ORF is needed as you are free >>>> to INSTALL and REMOVE ORF effectively producing one time behavior. >>>> >>>> #Keyur: Ack. >>>> >>>> Also existing Enhanced Route Refresh should work with ORF too. >>>> >>>> #Keyur: There are modifications needed if the refresh is going to be >>>> for selective prefixes only. Furthermore, if we want to support multip= le >>>> concurrent selective refreshes then the changes needed are very much a= long >>>> the lines of the solution suggested in the draft. >>>> >>>> Regards, >>>> Keyur >>>> >>>> >>>> >>>> Many thx, >>>> R. >>>> >>>> >>>> >>>> >>>> On Tue, Jul 19, 2016 at 11:47 PM, Dongjie (Jimmy) >>>> wrote: >>>> >>>>> Hi Tony, >>>>> >>>>> >>>>> >>>>> Please see some comments inline with [Jie]: >>>>> >>>>> >>>>> >>>>> *From:* Idr [mailto:idr-bounces@ietf.org] *On Behalf Of *Tony >>>>> Przygienda >>>>> *Sent:* Tuesday, July 19, 2016 6:04 PM >>>>> *To:* Robert Raszuk; idr wg >>>>> *Subject:* [Idr] Fwd: Slot request in IDR to present >>>>> https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-opti= ons-00.txt >>>>> >>>>> >>>>> >>>>> Resending ... >>>>> >>>>> >>>>> >>>>> ---------- Forwarded message ---------- >>>>> From: *Tony Przygienda* >>>>> Date: Mon, Jul 11, 2016 at 3:04 PM >>>>> Subject: Re: [Idr] Slot request in IDR to present >>>>> https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-opti= ons-00.txt >>>>> To: Robert Raszuk >>>>> Cc: idr wg >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Mon, Jul 11, 2016 at 1:47 PM, Robert Raszuk >>>>> wrote: >>>>> >>>>> Hi Tony, >>>>> >>>>> >>>>> >>>>> Hey Robert, thanks for chiming in. Good questions. I speak here for >>>>> myself, other authors of the draft may have differing opinions. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> 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 pushe= d >>>>> those ? >>>>> >>>>> >>>>> >>>>> We didn't discuss that one through but the only logical conclusion fo= r >>>>> me is that the ORF/CP-ORF installed are respected (i.e. it's an impli= cit >>>>> AND). I see ORF as statefull, remote-pushed policy on the peer that i= s not >>>>> being flipped around all the time (albeit AFAIR there were some attem= pts @ >>>>> non-persistent, one shot ORF but that ended up expiring?) >>>>> >>>>> >>>>> >>>>> [Jie] I think the attempts you mentioned here are the one-time ORF >>>>> drafts: draft-zeng-idr-one-time-prefix-orf and >>>>> draft-dong-idr-one-time-ext-community-orf. After several revisions, t= hese >>>>> drafts got expired due to lack of requirements at that time. If peopl= e >>>>> found some new use cases of these kinds of mechanisms, the authors wo= uld be >>>>> happy to bring them back to discussion. >>>>> >>>>> >>>>> >>>>> The motivation for this work were scenarios where a single-shot >>>>> refresh is needed, actually concurrent bunch of those based on >>>>> configuration changes, peer having dropped received routes based on s= pecs >>>>> (A-D), in policy changes, joining VPNs, EVIs and so on. Putting ORF o= n a >>>>> peer, refresh and remove ORFs is significantly heavier process that m= ay >>>>> interfere on top with normal update process going on and needs to be = done >>>>> one-by-one (since you have to wait for single BoRR/EoRR pair) unless = one is >>>>> very smart about combining ORF possibly & playing with the >>>>> DEFER/IMMEDIATEs. As we indicated, if the AFI/SAFI is covered by RTC = and >>>>> RTC is supported & one is willing to configure RTs for each subset of >>>>> routes that may need refreshing, RT will be doing the same job just f= ine. >>>>> >>>>> >>>>> >>>>> [Jie] The motivations look similar to what we described for the >>>>> one-time ORF drafts. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Would you always carry ORF with separate Refresh_ID value ? >>>>> >>>>> >>>>> >>>>> Yes, Refresh-ID# is strictly monotonic so there is never a >>>>> misunderstanding WHAT the BoRR belongs to. Observe that the draft doe= s NOT >>>>> mandate that a request MUST be followed by according BoRR, only that = BoRRs >>>>> must follow same sequence as requests (i.e. are also strictly monoton= ic). >>>>> However, we should probably specify that options _and_ ORF can NOT be= mixed >>>>> in the same type #3 message but it's either one or the other (and any= thing >>>>> else is error). This will allow ORF operations like today + benefit o= f the >>>>> Refresh ID# on the BoRR so the IMMEDIATE can go on @ the same time a= s >>>>> another request with higher Refresh ID# (de facto we allow multiple >>>>> parallel refreshes as you see). In case of DEFER there will be simpl= y no >>>>> BoRR for it. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> 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 entr= ies >>>>> 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 sta= te >>>>> that Refresh_IDs have no impact to ORF ADDs or REMOVE actions - don't= you >>>>> think ? >>>>> >>>>> >>>>> >>>>> I agree. Yes, ORF is kind of "permanent filter" on the peer while th= e >>>>> intent of this draft is to have bunch of "small refreshes" going on @= same >>>>> time possibly (if you request the refreshes from a good implementatio= n >>>>> while low-end implementations may serialize the requests to simplify >>>>> internal logic ;-). >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> As far as current types why not add regular/extended community ? >>>>> >>>>> >>>>> >>>>> Discussion came up. Feeling was it's an immediate encroach on RT >>>>> territory. I argued for it ;-) Ultimately, taking a more relaxed vie= w, we >>>>> chose to wait and see what the response is and most pressing use case= s >>>>> people bring to it and then we start to define bits and bytes of the >>>>> options supported, possibly borrowing to an extent from the ORF specs= ;-) >>>>> As in "most sincere form of flattery" and such ... ;-) >>>>> >>>>> >>>>> >>>>> [Jie] Actually before the one-time ORF drafts were submitted, we >>>>> initially considered to make it a =E2=80=9Cselective route refresh=E2= =80=9D mechanism. Then >>>>> we realized that the filters will be quite similar to the ones alread= y >>>>> defined for ORF. In order to reuse the ORF filters, we then decided t= o >>>>> define this mechanism as new =E2=80=9Cone-time=E2=80=9D ORF types. J= ust to provide some >>>>> background information since you also plan to reuse the format of the >>>>> existing ORF types. >>>>> >>>>> >>>>> >>>>> Best regards, >>>>> >>>>> Jie >>>>> >>>>> >>>>> >>>>> -- tony >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> *We=E2=80=99ve heard that a million monkeys at a million keyboards co= uld >>>>> produce the complete works of Shakespeare; now, thanks to the Interne= t, we >>>>> know that is not true.* >>>>> >>>>> =E2=80=94Robert Wilensky >>>>> >>>> >>>> >>> >> >> _______________________________________________ >> Idr mailing list >> Idr@ietf.org >> https://www.ietf.org/mailman/listinfo/idr >> >> > > > -- > *We=E2=80=99ve heard that a million monkeys at a million keyboards could = produce > the complete works of Shakespeare; now, thanks to the Internet, we know > that is not true.* > =E2=80=94Robert Wilensky > > > --=20 *We=E2=80=99ve heard that a million monkeys at a million keyboards could pr= oduce the complete works of Shakespeare; now, thanks to the Internet, we know that is not true.* =E2=80=94Robert Wilensky --001a1135018c3200fb0538278021 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Robert, in the draft there are enough of first examples, I= repeated several times other ones we were seeing outside the idr room and = later and each time it seems it is being dismissed and discussion goes into= abstract "let's do publish-subscribe because it's better"= ;. So I won't repeat all that again. I suggest we will update the draft= with more and more of stuff we saw and justified talking about it.=C2=A0
You didn't respond to any of the "what to do wit= h type-6 refresh" or "how will I make one ORF filter update multi= ple subsets [possibly disjoint] I need to refresh without getting flooded t= o death with the AFI/SAFI stuff" and "how will I implement ORF ex= cept a full walk on any change" which happen to be pretty massive issu= es if you want decent BGP convergence on more and more AFI/SAFIs, routes, t= ypes & other zoo sneaking upon BGP ...=C2=A0

s= orry if I'm a tad acerbic ...=C2=A0

--- tony= =C2=A0

On Thu, Jul 21, 2016 at 8:50 AM, Robert Raszuk <robert@raszuk.net>= wrote:

Tony,

You have nicely summarized various discussed this week sub t= hreads happening bith on and off the list.

Except .. you did not list the most important .. to enumerat= e real protocol level use cases which would justify this addition.

If we start with the problem (rather then just starting with= "when we need subset of routes") then perhaps it will be easy to= adopt this work or we go back and fix protocol encoding which are root cau= se of the problem you are trying to patch with solutions like selective ove= rlapping route refresh messages.

Best,
R.


On Jul 21, 2016 5= :42 PM, "Tony Przygienda" <tonysietf@gmail.com> wrote:
Read the "longish" thread by now = and between all this "let's do filter/let's do pull (refresh)&= quot; I try to take a step back to see the forest:

a) To= validate Niloo's point: 'f an implementation chooses to drop thing= s based on configuration/policy (multicast EVPN routes) extending ORF will = cause a complete refresh of EVPN (including type-2 MACs) unless you go and = "install filter type-2, then refresh, then remove-filter-2" and a= fter requesting type-6 =C2=A0(you can't defer remove-filter-2 step, oth= erwise you won't receive type-2 updates anymore!) floods you with all M= ACs. Pub-sub with a single "filter-list" is simply NOT a good mod= el to request arbitrary pieces of routes missing (which is where the world = is going, BGP database is sharding to the point specs are recommending to &= quot;drop when you don't need it" and we have the need to ask for = very specific sets @ given points in time [as the use cases describe]).=C2= =A0

b) A much _bigger_ problem IMO is the fact tha= t ORF language does not seem to be an algebra, it's a program and you c= an only build a closure of procedural programs by running them normally (no= t good to restrict sets you process). In less abstract terms a refresh with= filters that are OR'ed and AND'ed (first order logic transitive cl= osure) determines the cone you need to walk on the RIB very easily (people = implementing heavy-duty BGP will know precisely what that means) whereas an= y change to the filter will cause a full walk on the RIB possibly (in case = of arbitrary mix of accepts and rejects) without a lot of possibly hard log= ic to write (I didn't think fully through it but I think it may be actu= ally possible to write something delivering closure from a generic ORF filt= er so it's an interesting discussion). Even if you can build the closur= e, you can only run one at a time (one ORF filter) unless the peer does som= e crazy state-ful query optimization language to do wonders to squeeze mult= iple queries it needs into a single ORFs it's doing (SQL query optimize= rs are _really_ complex beasts) while the "you can put a filter on som= ething to suppress it on refresh but you can hammered with it anyway the mo= ment you remove it" persists.=C2=A0

For that = 2 cases my take =C2=A0is that it's better to move towards the model pro= posed by a "filtered refresh" (independently of being co-author) = rather than a 'pub-sub'.=C2=A0

As ultimate= , wider angle view of the world.=C2=A0

BGP will be= offered more cycles to run (it already is ) but not in the form of a singl= e faster and faster CPU anymore but in form of multiple cores/machines. A s= et of filtered refreshes can be parallelized fairly easily when requested. = A single ORF filter being manipulated on/off will as described in a) possib= ly cause huge spurious refreshes and in b) a single threat of execution ser= ializing the synchronization between peers.=C2=A0

= I hope that all can be parsed ...=C2=A0

Very good = discussion overall no matter which way it goes ...=C2=A0

--- tony=C2=A0

=

On Wed= , Jul 20, 2016 at 3:14 PM, Robert Raszuk <robert@raszuk.net>= wrote:
Hi Keyur,

On the EVPN topic which defines BGP protocol extensions without any IDR W= G review the more I hear about cases like you bring below (and this is not = the first one btw) the more I think it is really quite badly designed.=C2= =A0

And such bad proto= col extensions should not be a justification to introduce even more questio= nable knobs in BGP.=C2=A0

In this specific case just get all SAFI refreshed modulo to RTC or ORF = filters and you are done. Case solved :).

Best,
R.


On Wed, Jul 20, 2016 at 11:05 PM, Keyur Patel (keyupate) <keyupate@c= isco.com> wrote:
Hi Robert,

One interesting use case is with EVPN address family where a new route= -type is introduced without a capability.=C2=A0 A PE may have had safi enab= led but not have accepted its route-type (or set of route-types) all mappin= g to a same RT. A transactional filter attempts to solve it.

We can clarify in the next revision of the draft.

One more comment inlined #Keyur

From: Robert Raszuk <robert@raszuk.net>
Date: Tuesday, July 19, 2016 at 3:2= 9 PM
To: Keyur Patel <keyupate@cisco.com>
Cc: "Dongjie (Jimmy)" <= ;jie.dong@huawei.c= om>, idr wg <id= r@ietf.org>
Subject: Re: [Idr] Fwd: Slot reques= t in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00= .txt

Hi Keyur,

The missing part seems to be justification if we really need "transact= ion based filters" as opposed to simply having permanent ones.=C2=A0

What real problem "transaction based filters" solve ? IMO the dra= ft needs to state it clearly.=C2=A0

The other point is that "permanent" are not really permanent anyw= ay .. they are installed from update to withdraw of a given filter - regard= less what filtering mechanism you choose (ORF, RTC, XYZ ...). And if you go= with the notion that permanent are sufficient the entire aparatus allowing you to have concurrent route refresh requests= in flight goes away :)

#Keyur: Ack your right. My reference to a permanent filter was in cont= ext of a session life time and I agree with you that it could be modified o= r withdrawn at any given time. I was trying to differentiate it from transa= ctional filters.

Regards,
Keyur

Thx,
r.


On Wed, Jul 20, 2016 at 12:18 AM, Keyur Patel (k= eyupate) <keyupate@cisco.com> wrote:
Robert, Dongjie,

Comments inlined #Keyur

From: Robert Raszuk <robert@raszuk.net>
Date: Tuesday, July 19, 2016 at 2:5= 2 PM
To: "Dongjie (Jimmy)" <= ;jie.dong@huawei.c= om>
Cc: idr wg <idr@ietf.org>
Subject: Re: [Idr] Fwd: Slot reques= t in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00= .txt

Hi Jie,

To me what is perhaps missing is just a new draft to define *Route Type* OR= F to address some of those EVPN new NLRI encodings.

#Keyur: ORFs are permanent filters. We wanted to decouple the transact= ion based filters (one time per refresh) from the permanent filters and hen= ce chose to modify refresh message as opposed to an ORF.=C2=A0

I am not that much convinced if one time ORF is needed as you are free to I= NSTALL and REMOVE ORF effectively producing one time behavior.

#Keyur: Ack.=C2=A0

Also existing Enhanced Route Refresh should work with ORF too.=C2=A0

#Keyur: There are modifications needed if the refresh is going to be f= or selective prefixes only. Furthermore, if we want to support multiple con= current selective refreshes then the changes needed are very much along the= lines of the solution suggested in the draft.

Regards,
Keyur=C2=A0



Many thx,
R.




On Tue, Jul 19, 2016 at 11:47 PM, Dongjie (Jimmy= ) <jie.dong@huawe= i.com> wrote:

Hi Tony,

=C2=A0=

Please see some comments in= line with [Jie]:

=C2=A0=

From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Tony Przygienda
Sent: Tuesday, July 19, 2016 6:04 PM
To: Robert Raszuk; idr wg
Subject: [Idr] Fwd: Slot request in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00= .txt

=C2=A0

Resending ...=C2=A0

=C2=A0

= ---------- Forwarded message ----------
From: Tony Przygienda <tonysietf@gmail.com>
Date: Mon, Jul 11, 2016 at 3:04 PM
Subject: Re: [Idr] Slot request in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00= .txt
To: Robert Raszuk <robert@raszuk.net>
Cc: idr wg <idr@ietf.o= rg>

=C2=A0

=C2=A0

On Mon, Jul 11, 2016 at 1:47 PM= , Robert Raszuk <= robert@raszuk.net> wrote:

Hi Tony,

=C2=A0

Hey Robert, thanks for chiming = in. Good questions. I speak here for myself, other authors of the draft may= have differing opinions.=C2=A0

=C2=A0

=C2=A0

Can you clarify what is the expected behaviour as far as per peer f= ilter-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 towar= ds a peer which pushed those ?=C2=A0

=C2=A0

We didn't discuss that one = through but the only logical conclusion for me is that the ORF/CP-ORF insta= lled are respected (i.e. it's an implicit AND). I see ORF as statefull,= remote-pushed policy on the peer that is not being flipped around all the time (albeit AFAIR there were some attempts @= non-persistent, one shot ORF but that ended up expiring?)

=C2=A0=

[Jie] I think the attempts = you mentioned here are the one-time ORF drafts: draft-zeng-idr-one-time-pre= fix-orf =C2=A0and draft-dong-idr-one-time-ext-community-orf. After several revisions, these drafts got expired due to lack of requireme= nts at that time. If people found some new use cases of these kinds of mech= anisms, the authors would be happy to bring them back to discussion.=

=C2=A0

The motivation for this work we= re scenarios where a single-shot refresh is needed, actually concurrent bun= ch of those based on configuration changes, peer having dropped received ro= utes based on specs (A-D), in policy changes, joining VPNs, EVIs and so on. Putting ORF on a peer, refresh and = remove ORFs is significantly heavier process that may interfere on top with= normal update process going on and needs to be done one-by-one (since you = have to wait for single BoRR/EoRR pair) unless one is very smart about combining ORF possibly & playing = with the DEFER/IMMEDIATEs. As we indicated, if the AFI/SAFI is covered by R= TC and RTC is supported & one is willing to configure RTs for each subs= et of routes that may need refreshing, RT will be doing the same job just fine.=C2=A0

=C2=A0=

[Jie] The motivations look = similar to what we described for the one-time ORF drafts.

=C2=A0

=C2=A0

Would you always carry ORF with separate Refresh_ID value ?=C2=A0

=C2=A0

Yes, Refresh-ID# is strictly mo= notonic so there is never a misunderstanding WHAT the BoRR belongs to. Obse= rve that the draft does NOT mandate that a request MUST be followed by acco= rding BoRR, only that BoRRs must follow same sequence as requests (i.e. are also strictly monotonic). However, we = should probably specify that options _and_ ORF can NOT be mixed in the same= type #3 message but it's either one or the other (and anything else is= error). This will allow ORF operations like today + benefit of the Refresh ID# =C2=A0on the BoRR so the IMMEDIATE= can go on @ the same time as another request with higher Refresh ID# (de f= acto we allow multiple parallel refreshes as you see).=C2=A0 In case of DEF= ER there will be simply no BoRR for it.=C2=A0

=C2=A0

=C2=A0

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 a= lready 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 ?=C2=A0

=C2=A0

I agree. Yes, ORF is kind of = =C2=A0"permanent filter" on the peer while the intent of this dra= ft is to have bunch of "small refreshes" going on @ same time pos= sibly (if you request the refreshes from a good implementation while low-end implementations may serialize the requests to simplify inter= nal logic ;-).=C2=A0

=C2=A0

=C2=A0

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

=C2=A0

Discussion came up. Feeling was= it's an immediate encroach on RT territory. I argued for it ;-) =C2=A0= Ultimately, taking a more relaxed view, we chose to wait and see what the r= esponse is and most pressing use cases people bring to it and then we start to define bits and bytes of the options supp= orted, possibly borrowing to an extent from the ORF specs ;-) =C2=A0As in &= quot;most sincere form of flattery" and such ... ;-)=C2=A0

=C2=A0=

[Jie] Actually before the o= ne-time ORF drafts were submitted, we initially considered to make it a =E2= =80=9Cselective route refresh=E2=80=9D mechanism. Then we realized that the filters will be quite similar to the ones alread= y defined for ORF. In order to reuse the ORF filters, we then decided to de= fine this mechanism as new =E2=80=9Cone-time=E2=80=9D ORF types.=C2=A0 Just= to provide some background information since you also plan to reuse the format of the existing ORF types. <= /p>

=C2=A0=

Best regards,=

Jie

= =C2=A0

-- tony= =C2=A0

=C2=A0<= u>



=C2=A0

--

We=E2=80=99ve heard that a million monkeys at a mil= lion keyboards could produce the complete works of Shakespeare; now, thanks= to the Internet, we know that is not true.=

=E2=80=94Robert Wilensky





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




-- <= br>
We=E2= =80=99ve heard that a million monkeys at a million keyboards could produce = the complete works of Shakespeare; now, thanks to the Internet, we know tha= t is not true.
=E2=80=94Robert Wilensky




--
=
We=E2=80=99ve heard that a million monkeys at a million ke= yboards could produce the complete works of Shakespeare; now, thanks to the= Internet, we know that is not true.
=E2=80=94Robert Wilensky
--001a1135018c3200fb0538278021-- From nobody Thu Jul 21 09:22:50 2016 Return-Path: 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 D525412D0B2 for ; Thu, 21 Jul 2016 09:22:47 -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 K4LuIGA8k7Vh for ; Thu, 21 Jul 2016 09:22:46 -0700 (PDT) Received: from mail-qt0-x233.google.com (mail-qt0-x233.google.com [IPv6:2607:f8b0:400d:c0d::233]) (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 2820C12B028 for ; Thu, 21 Jul 2016 09:22:46 -0700 (PDT) Received: by mail-qt0-x233.google.com with SMTP id 52so46835842qtq.3 for ; Thu, 21 Jul 2016 09:22:46 -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:date:message-id:subject :from:to:cc; bh=u6nZy0qFxFrbmppUnsYKsE3+pC2gZGY4MM+4RG/8sXU=; b=nuQnbJRLy5HslHeOEhTOIt9rLDPK9Kn6ic1FDD0b2swqXMvzNwnXRV9Ilx/cbWZdWN CyWcFUvFu8kLx7F9xwLHcIMWQRjbQJMQzjA4jVs3iZm503CrIjfPASt9K+0Ww8naQY46 PYCaQ1ElElc4QeEi9VBp75O9Qrmcm67fG+2u/sUsbGUs7V2duzfmY9vxbdAe5H9TCAQ5 J4GMNJKdiGQkFK2eFIIeJfQdNikxufaN6KAhi7scUXJ68ad/c2luhcoCQty40xGkS7uw iodFIKWqi6RY0C94qL2RliBSuTpmtWv241NvSEQwATOsUcoCC69Y8pqi3/25CFF4CXL2 bR9Q== 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:date :message-id:subject:from:to:cc; bh=u6nZy0qFxFrbmppUnsYKsE3+pC2gZGY4MM+4RG/8sXU=; b=iRomB2Vc1ni6UDVITzX2EHySHku5ryw4utzIsvg0/Yze9F+0OldauQhr5dv72nkxoD kJHc5atrE5RtjRayYHNw7xG3q8PUhd4TBIoHoCANOMRMLaUyS7Uo35gNmNY0IWGATPCE XM8Zk99QyL+5YoDAfOldp7hx3QLDs3DeH8JOKx7GTJuFZmxHmvw51LGO79TqH7CxBSzn iIGh8ITTZ/b4aTGSpB+/FZ2xoMlV4oQHFxHoJ0hm2EeJb6qOkxvnv3Pgl1Wv1/ENQkWY efZMxjW3ymnFlIQIw2ufEEu4lL9IzuD0OU/1UhvLgRE6BAOFRMtL/cQuiPdKdQZ9q22R dTeg== X-Gm-Message-State: ALyK8tJVzVnQvGAtsSjzM8UIF03xlxNcaNwbSRfB5TUnQLV5FFG3rb5xJrrjws7MhhHl5WbZrOLtLCJqptQPzA== MIME-Version: 1.0 X-Received: by 10.200.35.169 with SMTP id q38mr60453667qtq.4.1469118165258; Thu, 21 Jul 2016 09:22:45 -0700 (PDT) Sender: rraszuk@gmail.com Received: by 10.237.36.90 with HTTP; Thu, 21 Jul 2016 09:22:45 -0700 (PDT) Received: by 10.237.36.90 with HTTP; Thu, 21 Jul 2016 09:22:45 -0700 (PDT) In-Reply-To: References: <76CD132C3ADEF848BD84D028D243C92774EEF7CF@NKGEML515-MBX.china.huawei.com> Date: Thu, 21 Jul 2016 18:22:45 +0200 X-Google-Sender-Auth: 1Iir9PsiJniLQSQAv3lEGS4SQlo Message-ID: From: Robert Raszuk To: Tony Przygienda Content-Type: multipart/alternative; boundary=001a114034305f9a0b053827babd Archived-At: Cc: "Keyur Patel \(keyupate\)" , idr wg Subject: Re: [Idr] Fwd: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jul 2016 16:22:48 -0000 --001a114034305f9a0b053827babd Content-Type: text/plain; charset=UTF-8 Tony, Sorry to be a bit stubborn here but I have not seen any valid reason for this work. Yes you have listed bunch if reasons in the original reply but non of those apply. Quoted below from your mail all below reasons require permanent filter not one time as you must not only get the NLRI once .. you MUST also get all updates to it when something changes supposedly also in subset way - otherwise you get all SAFI (all MACs which is what you are trying to avoid in the first place). That is critical which you seems to be missing. The debug thing is not sufficient justification. Moreover as you confirm this work is not compatible with RTC and as you confirmed you will not get anything over RTC filter in place. So to use one time refresh RTC needs to be effectively disabled. Your reasons: "The motivation for this work were scenarios where a single-shot refresh is needed, actually concurrent bunch of those based on configuration changes, peer having dropped received routes based on specs (A-D), in policy changes, joining VPNs, EVIs and so on. " Thx, R. --001a114034305f9a0b053827babd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Tony,

Sorry to be a bit stubborn here but I have not seen any vali= d reason for this work.

Yes you have listed bunch if reasons in the original reply b= ut non of those apply.

Quoted below from your mail all below reasons require perman= ent filter not one time as you must not only get the NLRI once .. you MUST = also get all updates to it when something changes supposedly also in subset= way - otherwise you get all SAFI (all MACs which is what you are trying to= avoid in the first place).

That is critical which you seems to be missing.

The debug thing is not sufficient justification.

Moreover as you confirm this work is not compatible with RTC= and as you confirmed you will not get anything over RTC filter in place. S= o to use one time refresh RTC needs to be effectively disabled.

Your reasons:

"The motivation for this work were scenarios where a si= ngle-shot refresh is needed, actually concurrent bunch of those based on co= nfiguration changes, peer having dropped received routes based on specs (A-= D), in policy changes, joining VPNs, EVIs and so on. "

Thx,
R.

--001a114034305f9a0b053827babd-- From nobody Fri Jul 22 01:53:08 2016 Return-Path: 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 7C7B012B05D for ; Fri, 22 Jul 2016 01:53:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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 BYzltKXDiKMD for ; Fri, 22 Jul 2016 01:53:05 -0700 (PDT) Received: from mail-it0-x232.google.com (mail-it0-x232.google.com [IPv6:2607:f8b0:4001:c0b::232]) (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 1564312DAAF for ; Fri, 22 Jul 2016 01:53:02 -0700 (PDT) Received: by mail-it0-x232.google.com with SMTP id f6so32422122ith.1 for ; Fri, 22 Jul 2016 01:53:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=+gMjYg2Q5rZ5HcEJn0bdIYKREgiY81OJvmT29sxhOY0=; b=a9YAuV4PhDw7qI2kDOqDhGik9vvBRgk4ixi98jiArX3JX448Jck3FKf9h4SvAC7sk4 /HozUgY061K6yaQ07QyX3jhxdY/KNWIXVJtOCzimBvXcoBV7VDvD8sg6/0uDuFyxXd5b 6JW2ySxfwTLoPx24fqY192neAxwM0PB0IHhK4+OPtaKJCS0mPvQGc1WgTx34qznNxSxx A7DjphlhjfpUpZj/QAvdxbnwB/dJCP9Ljlt6j07XnNjz2gcPLAL3jf+QuqO0XEQH+ckZ xSb+nAqVeJMsPyW4RLtHkHVMfb+Tpkrn3ZpmqMGxdmqEjSyMawSEfIcf4mC68Pqwy4Kv jlww== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=+gMjYg2Q5rZ5HcEJn0bdIYKREgiY81OJvmT29sxhOY0=; b=XTzKdBxFaotBZ3rTdfpG6xDuFWMNlnahxFb6WfJ53ennus3o+uWDycjauqI0oapDbB 8ZNFV41zuf/MXn6VH9VPIa7qfHZ6qnbmhmTM8HnMDJDzWEh8IUJwIV8KsaJU/ZqbHCtD 0QL7WxkLFKdeD6PHpSXTf1xmj+w2bN3tk/Y3KctQiIy3y0hXi7/PnoQTs/ZXUytOvSVs /iosOvH7GNekhvsRFaNDWx42Rp3O+isHFwb8MGZNKCKtsOlnPTlvuF7R9A4HsL5GIyWJ AUmIf0MfIYxORDTX+W+41lTcSAnt5TEJob97LkMeNCndVFJy+hRkH2a5lntzhdaI28rW kw9w== X-Gm-Message-State: ALyK8tJDXWLtLLUnl1mASt9tNWZkq1WK+uE9rJRFjQsUYhRsvyoHfV7nklvgv35yXd6xhNFV6280bhDk92upOg== X-Received: by 10.36.131.194 with SMTP id d185mr67580234ite.38.1469177581460; Fri, 22 Jul 2016 01:53:01 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.158.82 with HTTP; Fri, 22 Jul 2016 01:52:21 -0700 (PDT) In-Reply-To: References: <76CD132C3ADEF848BD84D028D243C92774EEF7CF@NKGEML515-MBX.china.huawei.com> From: Tony Przygienda Date: Fri, 22 Jul 2016 01:52:21 -0700 Message-ID: To: Robert Raszuk Content-Type: multipart/alternative; boundary=94eb2c049652dae1410538358f03 Archived-At: Cc: "Keyur Patel \(keyupate\)" , idr wg Subject: Re: [Idr] Fwd: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jul 2016 08:53:07 -0000 --94eb2c049652dae1410538358f03 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Robert, fine, agreed to disagree. We see over next rev of the draft ... We will extend section 1.1. further and frankly, I think it's sufficient today (otherwise we wouldn't bother wasting our time writing/figuring that out). RD we need wildcard semantics, beside that I agree that there isn't necessary enough justification for RD otherwise without assuming further semantics overload of RDs (bad thing). So maybe not allowing and RD options/filter and saying "RD is implied wildcard" is good enough. My feeling tells me it's not but it can be added later. I cannot parse the RTC comment you're making really. I suggest to distinguish very tightly between "querying", "registering" and "filtering". RTC is a intermixed "registration/filtering" mechanism, refresh is a "querying" mechanism. I think we'll add RTs to the filters for the option refresh and with that you can either "register via/filter RTCs" _or_ specifically request refresh for an RTC (which will be filtered by existing RTCs since RTC is the "overall filtering"). registering is good if you want full refresh of something beside initial open but the filters must be very orthogonal to do it efficiently and decoupled from each other (transactional) while RTC is simply a accept/deny language which is hard to closure compute (sorry, can't save the linear programing vs. transitive closure algebra distinction here and if it's not clear it will become painfully clear in implementation only). filtering is the NOT of registering really and RTC is a ball-of-hair where the deny are really "NOTs" and possibly filters rather then registers. While empty RTC is a "register all" implicitly. Refresh is querying. Something pretty different from "register". Semantics is "I may have registered (implicitly) but I may have filtered on my side for some reason and now I need the information again". Yes, one can play great games with filtering/registering to emulate querying as one can surely use screwdrivers to open tin cans. A very orthogonal algebra of independent RTC filters would have been possibly equivalent to the route refresh options but alas between the accept/reject/defer/immediate I would always chose to have a clean "orthogonal filter transactional query" architecture here ... (sorry, I speak databas'ish here since this is all really a big partitioned/distributed/loosely synchronized database problem and has nothing to do really with BGP carrying the bits). Your answers to "on RTC change you'll get flooded with all the stuff again" and "how do I get type-6 only without causing subsequent flooding when I unwind the RTC filter" are still surepitiously missing. If your point "you never _query_ in BGP, we SHALL only register" then route-refresh was the battle to be fought, this particular Rubicon has been crossed long time ago as you know (and it took good many years until a similar discussion I had a _looong_ time ago about "you need Begin Transaction/End Transaction" and was ignored caused enough real pain to lead to Extended Route Refresh). no, to nastepnej wersi ;-) ;-) --- tony On Thu, Jul 21, 2016 at 9:22 AM, Robert Raszuk wrote: > Tony, > > Sorry to be a bit stubborn here but I have not seen any valid reason for > this work. > > Yes you have listed bunch if reasons in the original reply but non of > those apply. > > Quoted below from your mail all below reasons require permanent filter no= t > one time as you must not only get the NLRI once .. you MUST also get all > updates to it when something changes supposedly also in subset way - > otherwise you get all SAFI (all MACs which is what you are trying to avoi= d > in the first place). > > That is critical which you seems to be missing. > > The debug thing is not sufficient justification. > > Moreover as you confirm this work is not compatible with RTC and as you > confirmed you will not get anything over RTC filter in place. So to use o= ne > time refresh RTC needs to be effectively disabled. > > Your reasons: > > "The motivation for this work were scenarios where a single-shot refresh > is needed, actually concurrent bunch of those based on configuration > changes, peer having dropped received routes based on specs (A-D), in > policy changes, joining VPNs, EVIs and so on. " > > Thx, > R. > --=20 *We=E2=80=99ve heard that a million monkeys at a million keyboards could pr= oduce the complete works of Shakespeare; now, thanks to the Internet, we know that is not true.* =E2=80=94Robert Wilensky --94eb2c049652dae1410538358f03 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Robert, fine, agreed to disagree. We see over next rev of = the draft ...=C2=A0

We will extend section 1.1. further = and frankly, I think it's sufficient today (otherwise we wouldn't b= other wasting our time writing/figuring that out).=C2=A0

RD we need wildcard semantics, beside that I agree that there isn= 9;t necessary enough justification for RD otherwise without assuming furthe= r semantics overload of RDs (bad thing). So maybe not allowing and RD optio= ns/filter and saying "RD is implied wildcard" is good enough. My = feeling tells me it's not but it can be added later.=C2=A0
I cannot parse the RTC comment you're making really. I sug= gest to distinguish very tightly between "querying", "regist= ering" and "filtering".

RTC is a in= termixed "registration/filtering" mechanism, refresh is a "q= uerying" mechanism. I think we'll add RTs to the filters for the o= ption refresh and with that you can either "register via/filter RTCs&q= uot; _or_ specifically request refresh for an RTC (which will be filtered b= y existing RTCs since RTC is the "overall filtering").=C2=A0

registering is good if you want full refresh of someth= ing beside initial open but the filters must be very orthogonal to do it ef= ficiently and decoupled from each other (transactional) while RTC is simply= a accept/deny language which is hard to closure compute (sorry, can't = save the linear programing vs. transitive closure algebra distinction here = and if it's not clear it will become painfully clear in implementation = only).=C2=A0

filtering is the NOT of registering r= eally and RTC is a ball-of-hair where the deny are really "NOTs" = and possibly filters rather then registers. While empty RTC is a "regi= ster all" implicitly.=C2=A0

Refresh is queryi= ng. Something pretty different from "register". Semantics is &quo= t;I may have registered (implicitly) but I may have filtered on my side for= some reason and now I need the information again". Yes, one can play = great games with filtering/registering to emulate querying as one can surel= y use screwdrivers to open tin cans. A very orthogonal algebra of independe= nt RTC filters would have been possibly equivalent to the route refresh opt= ions but alas between the accept/reject/defer/immediate I would always chos= e to have a clean "orthogonal filter transactional query" archite= cture here ... (sorry, I speak databas'ish here since this is all reall= y a big partitioned/distributed/loosely synchronized database problem and h= as nothing to do really with BGP carrying the bits).=C2=A0

Your answers to "on RTC change you'll get flooded with al= l the stuff again" and "how do I get type-6 only without causing = subsequent flooding when I unwind the RTC filter" are still surepitiou= sly missing.

If your =C2=A0point "you never _= query_ in BGP, we SHALL only register" then route-refresh was the batt= le to be fought, this particular Rubicon has been crossed long time ago as = you know (and it took good many years until a similar discussion I had a _l= ooong_ time ago about "you need Begin Transaction/End Transaction"= ; and was ignored caused enough real pain to lead to Extended Route Refresh= ).=C2=A0

no, to nastepnej wersi ;-) ;-)=C2=A0

--- tony=C2=A0
<= br>
On Thu, Jul 21, 2016 at 9:22 AM, Robert Raszu= k <robert@raszuk.net> wrote:

Tony,

Sorry to be a bit stubborn here but I have not seen any vali= d reason for this work.

Yes you have listed bunch if reasons in the original reply b= ut non of those apply.

Quoted below from your mail all below reasons require perman= ent filter not one time as you must not only get the NLRI once .. you MUST = also get all updates to it when something changes supposedly also in subset= way - otherwise you get all SAFI (all MACs which is what you are trying to= avoid in the first place).

That is critical which you seems to be missing.

The debug thing is not sufficient justification.

Moreover as you confirm this work is not compatible with RTC= and as you confirmed you will not get anything over RTC filter in place. S= o to use one time refresh RTC needs to be effectively disabled.

Your reasons:

"The motivation for this work were scenarios where a si= ngle-shot refresh is needed, actually concurrent bunch of those based on co= nfiguration changes, peer having dropped received routes based on specs (A-= D), in policy changes, joining VPNs, EVIs and so on. "

Thx,
R.




--
We=E2=80=99ve heard that a million monkeys at a million keyboards cou= ld produce the complete works of Shakespeare; now, thanks to the Internet, = we know that is not true.=E2=80=94Robert Wilensky<= br>
--94eb2c049652dae1410538358f03-- From nobody Sun Jul 24 07:22:14 2016 Return-Path: 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 E420512D555 for ; Sun, 24 Jul 2016 07:22:12 -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 8RF01CH1Feog for ; Sun, 24 Jul 2016 07:22:11 -0700 (PDT) Received: from mail-qt0-x22b.google.com (mail-qt0-x22b.google.com [IPv6:2607:f8b0:400d:c0d::22b]) (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 1F21512D54D for ; Sun, 24 Jul 2016 07:22:11 -0700 (PDT) Received: by mail-qt0-x22b.google.com with SMTP id x25so85090846qtx.2 for ; Sun, 24 Jul 2016 07:22:11 -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=5o4I20WOaXUfn75v5K+TlFgsmBS/jruCbwpocatwtW0=; b=OHVrUVeEQUKNFIAej0+LCJsxtA/FtVUA7UIenjCu5jSOFclyJDKdsE4xBvdaiSgsEK 1sCx5VASdDaAF2jdW7S3g9FOtD2OR0YxpCyq7uVtsSGdvZS/MyNOF9xECZ1GZ5yC7Xl/ W0C6KOz7vbeodN3XN5QG878tb3F7HbZJc5y6u/HSqghu45z9Wzv5ey4eFhR1yCm8DFbk NJ0zG4pZc1qt1oTO97ezxUxsiCIBaryykGYj35QfX6cvEHyx2tS2qWFLl/EpNL3UKqtc riVSRRvVcItCxRHV9GYCEpOlWHC9KkngGRzqCgGm7Y2spt5/BXSWdpyMx8gr3qxC4suH RzZQ== 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=5o4I20WOaXUfn75v5K+TlFgsmBS/jruCbwpocatwtW0=; b=M1cKE0mn/3xZ0zjGergmimJGiYh/H/DELuV7cSThdVJiEWaVVsQ816fNoMR5pjoUEu cmCM9c2fiXgEvrbs8HBEBEd5yDKwg6Yp9a3zd09bxebL4R2mRbuiH0b3tal8GWYqUsVs bY0WoSrysyhElQErInpkWn9KkJr6rWDfK9EnQq4V8L2Rbp+nH1MwueT99wGqligdEtl+ eCjvEawyBM+S2GpGEoTwxeyIrwlhGe6dmWj1ijs/z9Yh2sipLqZ8mSlZGnc/9xQ6TLlR iGXtQbOzMYEuNWEDo/7NXEjiKEGI69i0/A+Sf3yH2CYpgbNvWyd8CNXPV4ikOI3m1ehX addg== X-Gm-Message-State: AEkooutYH8tzXEQfGs2H/atMY2HjoH5OuEK4MsRYNDc9e9e8XbI60TywxNfTwUxosPAkR/ZmWIuv1jF9BhWHIg== X-Received: by 10.237.37.58 with SMTP id v55mr22651661qtc.9.1469370130098; Sun, 24 Jul 2016 07:22:10 -0700 (PDT) MIME-Version: 1.0 Sender: rraszuk@gmail.com Received: by 10.237.36.90 with HTTP; Sun, 24 Jul 2016 07:22:08 -0700 (PDT) In-Reply-To: References: <76CD132C3ADEF848BD84D028D243C92774EEF7CF@NKGEML515-MBX.china.huawei.com> From: Robert Raszuk Date: Sun, 24 Jul 2016 16:22:08 +0200 X-Google-Sender-Auth: Eesf19_4tg4FEJgG6kDJA-Q4aQc Message-ID: To: Tony Przygienda Content-Type: multipart/alternative; boundary=001a113f42e6a5f01c053862649a Archived-At: Cc: "Keyur Patel \(keyupate\)" , idr wg Subject: Re: [Idr] Fwd: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jul 2016 14:22:13 -0000 --001a113f42e6a5f01c053862649a Content-Type: text/plain; charset=UTF-8 Dear Antoni, The point here is not about the question if query in BGP is good or bad or how easy or difficult it is to implement. The points to discuss are following: #1 What parameters are used to "query" ? #2 How does defined "query" work with existing BGP protocol and extensions ? #3 What protocol state machine change triggers "query" action ? - - - Ad 1 - Cool that we have already accomplished consensus to get rid of RD query. If you do not specify anything the automatic assumptions would be *ANY* RD anyway if you query by anything other then NLRI prefix. Query by NLRI is questionable too (see below Ad 3). Now let's talk about (in)famous EVPN route types you keep bringing as query parameter. Please observe that RFC7432 does not define BGP capability per route type and only negotiates 25/70 implicitly indicating support of all route types. Moreover RFC7432 is very clear that to accomplish filtering of routes on the sender side use of RTC is recommended. Ad 2 - Assume operator is using RTC so list of RT filters is populated by the peer outbound towards querying bgp speaker. Now issuing query for anything needs to be evaluated against already supported Enhanced Route Refresh (RFC7313) which btw you are also obsoleting here where you get full filtered by RTC list of interesting NLRIs for specific AFI/SAFI. On the topic of obsoleting RFC2918 I must say that I hope this is just a huge oversight ... Your current draft says: "When the Route Refresh Options Capability has been negotiated by both sides of a BGP session, both peers MUST use message types 3, 4 and 5." And message type 3 clearly states that I must have at least one refresh option ... quote from the field of the msg: "One or more Route Refresh Options" That means that I no longer can ask for refresh of the entire AFI/SAFI - this is pretty bad. Ad 3 - Now the crux of all of this ... Please enumerate on the list or in the draft what exact protocol state machine transitions will result in automated query for subset of given AFI/SAFI with and without prior use of RTC and ORF filters. In other words I do not buy general justifications explained before, quote: * "now I need the information again" * " The motivation for this work were scenarios where a single-shot refresh is needed, actually concurrent bunch of those based on configuration changes, --> You need per AFI/SAFI or per RT refresh " in policy changes, joining VPNs, EVIs and so on." --> You need per AFI/SAFI or per RT refresh - - - - - - Conclusion: Asking for subset of AFI/SAFI routes based on specific query does not in any way allows to assure that you will get full set of routes which are actually needed for correct operation. BGP standardized use of Route Target Ext Community to filter routes both on inbound as well as optimize it also outbound. If you modify RT import policy say you add one RT I agree that asking for just that one RT may be much better - but here RTC is exactly what comes as solution as generating one update in SAFI 132 will result in getting such delta of routes. It also needs to be stated that there is no overhead to add few RTs (one per NLRI type) for those new address families which bring the concept of NLRI types (EVPN, BGP-LS etc ...) hence the objectives of this work can be easily achieved today with existing specifications. Best regards, Robert. --001a113f42e6a5f01c053862649a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Dear Antoni,
The point here is not about the question if quer= y in BGP is good or bad or how easy or difficult it is to implement.
<= div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif= ;font-size:small">
The points to discuss are fo= llowing:=C2=A0

#1 What= parameters are used to "query" ?=C2=A0
<= br>
#2 How does defined "query" work with= existing BGP protocol and extensions ?

#3 What protocol state machine change triggers "= query" action ?

-= - -=C2=A0

Ad 1 -=C2= =A0

Cool that we have = already accomplished consensus to get rid of RD query. If you do not specif= y anything the automatic assumptions would be *ANY* RD anyway if you query = by anything other then NLRI prefix. Query by NLRI is questionable too (see = below Ad 3).=C2=A0

Now= let's talk about (in)famous EVPN route types you keep bringing as quer= y parameter. Please observe that RFC7432 does not define BGP capability per= route type and only negotiates 25/70 implicitly indicating support of all = route types. Moreover RFC7432 is very clear that to accomplish filtering of= routes on the sender side use of RTC is recommended.=C2=A0


Ad 2 -= =C2=A0

Assume operator= is using RTC so list of RT filters is populated by the peer outbound towar= ds querying bgp speaker. Now issuing query for anything needs to be evaluat= ed against already supported Enhanced Route Refresh (RFC7313) which btw you= are also obsoleting here where you get full filtered by RTC list of intere= sting NLRIs for specific AFI/SAFI.=C2=A0

=
On the topic of obsoleting RFC2918 I must say that I hop= e this is just a huge oversight ... Your current draft says:=C2=A0

"When the Route Refresh O= ptions Capability has been negotiated by both
sides of a BGP sessio= n, both peers MUST use message types 3, 4 and 5."

And message type 3 clearly states that I must have at least one refresh op= tion ... quote from the field of the msg: "One or more Route Re= fresh Options"=C2=A0

= That means that I no longer can ask for refresh of the entire AFI/SAFI - th= is is pretty bad.=C2=A0

=
Ad 3 -=C2=A0

Now the crux of all of this ...=C2=A0
=
Please enumerate on the list or in the draft wha= t exact protocol state machine transitions will result in automated query f= or subset of given AFI/SAFI with and without prior use of RTC and ORF filte= rs.=C2=A0

In other words I= do not buy general justifications explained before,=C2=A0quo= te:=C2=A0

* "<= span style=3D"font-size:12.8px;font-family:arial,sans-serif">now I need the= information again"=C2=A0

* "=C2=A0The motivation fo= r this work were scenarios where a single-shot refresh is needed, actually = concurrent bunch of those based on configuration changes,=C2=A0

--= > You need per AFI/SAFI or per RT refresh

" in policy cha= nges, joining VPNs, EVIs and so on."=C2=A0

--> You need per AFI/SAFI or per RT refresh

- - - - - -=C2=A0

Conclusion: =C2=A0

Asking for subset of AFI/S= AFI routes based on specific query does not in any way allows to assure tha= t you will get full set of routes which are actually needed for correct ope= ration.=C2=A0

BGP stan= dardized use of Route Target Ext Community to filter routes both on inbound= as well as optimize it also outbound. If you modify RT import policy say y= ou add one RT I agree that asking for just that one RT may be much better -= but here RTC is exactly what comes as solution as generating one update in= SAFI 132 will result in getting such delta of routes.=C2=A0

It also needs to be stated that ther= e is no overhead to add few RTs (one per NLRI type) for those new address f= amilies which bring the concept of NLRI types (EVPN, BGP-LS etc ...) hence = the objectives of this work can be easily achieved today with existing spec= ifications.=C2=A0

Best= regards,
Robert.

--001a113f42e6a5f01c053862649a-- From nobody Sun Jul 24 09:11:40 2016 Return-Path: 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 8E3F012D1AE for ; Sun, 24 Jul 2016 09:11:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.922 X-Spam-Level: X-Spam-Status: No, score=-1.922 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=junipernetworks.onmicrosoft.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 eLusaE2N7Nhi for ; Sun, 24 Jul 2016 09:11:36 -0700 (PDT) Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-bl2nam02on0112.outbound.protection.outlook.com [104.47.38.112]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8BC3C12D130 for ; Sun, 24 Jul 2016 09:11:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=junipernetworks.onmicrosoft.com; s=selector1-juniper-net; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=ao0jr127cKpMCtOTg5sTKV1xU5BT9HogNMF8T4G0/LM=; b=JkvixBEbJ0Q8m3B5y6zCaBCfAtup1ZdAv5M/0B1840lqwcVa0D723ETpxg2PpfBsWwWmZaYO8o0FRbLSud3O83zLKkpSCx+U6eHo63LOwxd5+fNax23Y/qI1hnj1yubdmykLHBD29RjEVjEX1GBYzhAIB0rKweiVtGVH6QWTf4k= Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=jgs@juniper.net; Received: from [172.29.64.104] (193.110.55.14) by CO2PR05MB2502.namprd05.prod.outlook.com (10.166.95.148) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.549.5; Sun, 24 Jul 2016 16:11:32 +0000 From: "John G. Scudder" Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message-ID: Date: Sun, 24 Jul 2016 18:11:24 +0200 To: MIME-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) X-Mailer: Apple Mail (2.3124) X-Originating-IP: [193.110.55.14] X-ClientProxiedBy: DM2PR0501CA0037.namprd05.prod.outlook.com (10.162.29.175) To CO2PR05MB2502.namprd05.prod.outlook.com (10.166.95.148) X-MS-Office365-Filtering-Correlation-Id: c3a91580-0ee8-451a-e320-08d3b3dd2e62 X-Microsoft-Exchange-Diagnostics: 1; CO2PR05MB2502; 2:NJ9FwsADkNkpWZrnUuUEZjL9Lp2XkgHUZixvsiVWu9no3mc8++hp/hUTJPSVVGmhGVKAuY9G/Ix+WA+XbwiXcjgeIiOUyPbOrQP4Re0KQS8H7lIgcLU5JYBK2bJQG9gsb/DROPDZJJPbKrEiurpqZG+2glhQdUlv0uC0CcKrFWoyC4zQk8EhFET9OE/oxhEe; 3:X3qICfwOQMCi7sss9s6PXddQkjukuzkSsBkv/4Y1pANtty61G59VDTAvi4c/KOhTzw5n6J+OadH8iIEL2vIXB4WSBEX5I7myvv2xNo/Qa9hPn9ziiCh+Fg9Rm9Yiq0Et X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:CO2PR05MB2502; X-Microsoft-Exchange-Diagnostics: 1; CO2PR05MB2502; 25:hrxcaLzO0PIQi0B9CgKVjrbI1foh2jaigsZZf4oProCTgYv+Ijpk9AmOS7Ivyq8NUkYfQifi0U6aQ/4pvIlJHWlqDZL6jk46hS0QS6RBAa0rIJxL9A34fu2IJzRbWDmmuTfGoAfocYOe+sZ8VQZ24xhxjBCO0B5FD/ycb3X5SNFLLfB39oJw9Wk0holmguU7Dj01/n6eVhL74Hnx2V3kIez+TD4UPygynODF6pWUy8R5Edv3zU+Wh12Bv3rPpsBvQ8CiKHlhcuqIkoUTYuUnH2+5jRj2GOsbsAI617NKeSc4YLtZGpiPoEpYy2DSBuqr6FN6oNxL7WvCG40Ie+8t17cy+2qtQ1/q4AxstXacsdNHP8EfRM0KaeqSb73nSKmjD7no714BzZxVUuImomT9j5rFjUzzlRgiM2T4MwB+8hBE9md+X5Hl9lb088qPaYUdO2rCmhQkApxScKqGokdFFGuA6xOAczEXlvlyg5H5yfTMzBXvcEtt97y2WSpBz/lyIEHyebCYkxLLU5WDHIZTuFbKEW+LE2dOHdyPFt4/ruGZ88T5HmzYjkwpSRNv26uAR1lR8CaOx7MEclMo8ziPcQV6J8Zjn4cwqF7WzjLcxQl4dk4IxsJgHKjRQtHQG7ss386fKoFQjaDv2xZPVJxo5jHEbbyEG0ENnDGykx4p9qJ2X50heNof4/swPw4V0KjrBm3e+5bRZEWpVYZViwP9FfPmrqLkSAaauW0XMOMvEhQOO2LuKCNgix83LTX1uKjPZW6sx1uIulYhsUaurrhGKqgKbOPxzCrbsChYu3vVL8w= X-Microsoft-Exchange-Diagnostics: 1; CO2PR05MB2502; 31:/YW3iTwFSxdyNoUj+hdqHxFn2Nut1fDYtMPVC5JUu9LYeR/JQ9MZLvvooJWHAYYdf05El5Vq1o6PJ9DcpyjUa38AFaQnRXG0nX8EJun7P/eWNdvpJEHSbKlO8//SOTVdyq0oSuiSUHstxXvkyalY9SxLQRXONvvDN3ob8g297qn0+SqWQQQDikzHorxH2drmjZ3+3RuA2rmQWuCF+eSe6w==; 20:ChLe7Hs7yvkBAJ0Uda0p4CsKAHJjweSnzaymlpIhLMOfpOoAUiuteWywCbEPLnni4PrSuAS5IGV/3z5aHoGQrxCY0eMzMhWfbbkz+oVVBCZtu9Pl/dWaO+Mb5G2R+LAHaa5FsKdUeutQPetjLUfJTzf8tMgX/ttCZ3D6To2GVDJUztO6QmICupqwjQKV1ThSeF/NCL16SvO5EU+QO/ns0UDOlcc6leUispF4V20WGa1cJVA5OwWkU7ZXOMmrDAqw5ApQuMRsZOwn04XphUgtXOOquv+PX2ORnU1Z/cUPJNm6AXkQfp7GFJ2LF+sag/MRgKG6vp78iqhPVVzGhKjXgjZ5YD+XGq+yT+hQowdRfaL32Gj+j93RXhVgOEuvpFxVwRxUBoqzgGpr/WGpxaSpPqH7580V54rdFLpXw/B+nJ9EdEBgZhC2kkMg+re9LlghnNvY7H4+DvQ33eWwl9nN0QEdr8lPQ/nvvYfWzS6QIuj4SL6K4CxcX+rJ5/PDFH2c X-Microsoft-Antispam-PRVS: X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6055026); SRVR:CO2PR05MB2502; BCL:0; PCL:0; RULEID:; SRVR:CO2PR05MB2502; X-Microsoft-Exchange-Diagnostics: 1; CO2PR05MB2502; 4:D3Ca8pIJhlRpvrImxa0OEfBCG5ZXtux9P3WxRPUGBN/hhFk8ljXjmL2Lx39Fi5TN8hnTuxoGAE/QXrtrZHF7u04xTaI2XWZukbyaix9YqgMwxaujnZapTcHHNgC+baphP3x44IiIk64u1li0Uo6QHELaTaKhcwx71/35T/gBLW5BNaxIgZ03NGDglEB03bwrRFGDBCswP+GAIySe/ShdJJToj8eNQOwOwP9FqhhRltn+iACaCNeewhYPvZeWD/7JSafVyf86oL8UprY+bMNU8wj4mH6+Z6I1wdZTRSJrfn5PzYq2wE0o/WvchTEHmc48V4YvYsPksUrY8JK10G7pRpmLw9ix/EuIXfw8W8BJGCAH2akGG+zCTlRtcpT8PuLY X-Forefront-PRVS: 0013079544 X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(6049001)(6009001)(7916002)(189002)(53754006)(199003)(86362001)(97756001)(57306001)(19580395003)(8746002)(50466002)(7736002)(7846002)(92566002)(81166006)(106356001)(2351001)(81156014)(229853001)(50226002)(101416001)(305945005)(33656002)(450100001)(50986999)(189998001)(82746002)(8676002)(42186005)(68736007)(83716003)(105586002)(47776003)(15975445007)(23726003)(558084003)(107886002)(3846002)(6116002)(586003)(97736004)(36756003)(110136002)(2906002)(66066001)(77096005)(46406003)(42262002)(104396002); DIR:OUT; SFP:1102; SCL:1; SRVR:CO2PR05MB2502; H:[172.29.64.104]; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; Received-SPF: None (protection.outlook.com: juniper.net does not designate permitted sender hosts) X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; CO2PR05MB2502; 23:m5xeL9q1MbilGMEukhVQTiAbuDcDDLhpC0Gxz0WfY?= =?us-ascii?Q?pddrPhj9Wg6ubHl+uUlVj7GJKO2nA92IrOpuQvgkjKhTbZnKVGe00zNTMI/t?= =?us-ascii?Q?a6bgEXWRmqbQwUyMHNYJoWLteTEjzL9ppNqjuCES6cxlgHfljcArzVQEZRVD?= =?us-ascii?Q?oZaEKgjoXYZ0KfdzGF4SkvdeF/XKMa5L5+EyC+9aV3ZXOLP7Hd1f6Uq9V3ov?= =?us-ascii?Q?mDPjxcUc3eisWVm0y7KJr6ZIS+EM1Il+6mGZiUhIRn5WUHz+IJjNIhSbd2qt?= =?us-ascii?Q?XpOOAl3O4SDNF0OffkDnoaVV/ha2TB08PSX6Z2WuDyjFy+RassiYlqwQWpyw?= =?us-ascii?Q?OGJmqr8EU1Tg6oFfBm0Bi2vZcozfxkfX6Kf4BBXtvUzZoEivRPVFvSBvKGUo?= =?us-ascii?Q?1DxWHlWFO/YGfP/82gwoWgvxTDxslMjUbCcbLtRhUZuJcvAYMfQzRwiFhTyx?= =?us-ascii?Q?htQUqzoi5/khBl0ilmzsR32d8to7Px4Stz5cxoHh0rLZlWwqcUH97yIEVsVx?= =?us-ascii?Q?Uf9t1C8CgPr8tIA/y/9NMPyKu7n1q2S05A39P8uN8pNML6xDrNqD0er9MnKB?= =?us-ascii?Q?+vdl+copcxy5YcVGf+rP6LWBlFUYQLjPoxNaOHSttdvrh/z0fGIGnCwPrfO8?= =?us-ascii?Q?frE3UezS+EzyK4l/rXGjYD+/UPOqlULaeA+pxa4rp/tfGvWcl1yZBRyGkIki?= =?us-ascii?Q?7/DI3jeFWwWVZduBdJoh4fvdqgCJxRHLYzu2U6Y1yF09xRHwYe99XJsRQbMd?= =?us-ascii?Q?8JWB8feFMP31kId6hUEiF13QBhlirk5o23k26okK/PsJZJdVcoXHIRh1+Zlk?= =?us-ascii?Q?IaXgkEgYQwNkX937WwdyQX61/T/g4jjX2m5S4GYAMBG049HxatxDMEsL/q/G?= =?us-ascii?Q?rX6FrbHv95VK8cYp3JkWVzlE3KZ/9llKbPmZa2sRCdwVLC3LYkit5njzTZIL?= =?us-ascii?Q?0gKvaICVoZEIws4trHtZ/HNVBabNPFsOFgdts6xys9x4xAii+aKtLiAdfQLb?= =?us-ascii?Q?rZk/h823MsbsagLDnJvGlxokCA1lYubWRKNR4J0QMwqnSsfjq5YHhwB/crgP?= =?us-ascii?Q?XikN5uk799kQioY7HcOHBX+Ea8x02TXUH5D7X+2Sh43uf7UUKIwH72A+PdLo?= =?us-ascii?Q?YIKSTVI5OFvtjLx2FLrvx/xe2K2qEWiNlhAz0jAxkLAcqE/m+My/H1cwGZHY?= =?us-ascii?Q?zJdf01traPpdcb8tlGVBSsD69h4Xbn5O1DBhMmgURa3bMYAtMwU0Sw1dgt0W?= =?us-ascii?Q?xBRVHf0BIATtvRtl/8=3D?= X-Microsoft-Exchange-Diagnostics: 1; CO2PR05MB2502; 6:3ZBpRILljM1ykhotmAznkMdUclX3vgOp0MsbR9XOvWSgbgpa2xzZ74/an8CO+xB2CuH9vrGUsK37Wtoo2TCycWOlqd0ZNVGSegusiH2PcBghxQXGy9ikUlxVXytVgnjWIYPOxjHwPpL1PrWioM3yssxQj1z0GEoieiPivqQpwkmfKfHDu6dyi50mLZpoe69sUxnuJyQyhZZNFGCtg7o9Beq2S9cx08/ArNqecm3KESUluL38oEU4EITkcKzslGvA25snJzmy/+W2RYSqtR1NG/LWE1NseJPdDtl/uWoS1ix5ED20Yi0JrHK29D2f/r286or391UXmbLitQ+OYefHHQ==; 5:o/SsiRtk+uCDcYiXbbC5kkJeqU5U8kL9BIx/cuLityn7+darn0sArZGrNAaD6mGUcUmRQGAhnOrBTw2FdvWn4KRrEn8Zrr26IjHSbYdsXJsTCT6QaMOjtlnWzH+DbvREki9xEPF58oqwIKUHhWZmfw==; 24:c1eBLyutPrz+SbKgt6tP8KPQCa+/Ykh+DLX+b9MqXi1+RdCLyg6io0M5WgHSTR9jqURtiukp361dyZ0WT6s6zWXir5y3Bs82zbxcQaPlmXw=; 7:FPGcpqpJmS5dVGS61M/5NrC8kVth492WgOtj73hYjgXtQeA7Lc/h9NEEvfF8D9vtpkQtGXI7s6L+0HWHQYxjI7Wrz4ZNOQQMRMrcyghF0JABkvXg7Od2y83zVBUYOAVIiP4qZcCTH1ZYg6E5VWbAL/6/HBz5tf6xpzVDVfg4Jtrqw9glwQs32fJ6al2bE8nJpRcbhp1yNiv1imqmzfX2s4a3OnxyCqYrChGhv9Zjzb590L4F7XNirGwW3LlBTRLz SpamDiagnosticOutput: 1:99 SpamDiagnosticMetadata: NSPM X-OriginatorOrg: juniper.net X-MS-Exchange-CrossTenant-OriginalArrivalTime: 24 Jul 2016 16:11:32.7581 (UTC) X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO2PR05MB2502 Archived-At: Subject: [Idr] Minutes of IETF-96 IDR posted X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jul 2016 16:11:38 -0000 Hi Everyone, Minutes are now available at = https://www.ietf.org/proceedings/96/minutes/minutes-96-idr. Please send = any corrections or comments to the list. Thanks to those who pitched in = to take the notes. --John= From nobody Sun Jul 24 09:21:10 2016 Return-Path: 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 0FC5F12D1B9 for ; Sun, 24 Jul 2016 09:21:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.903 X-Spam-Level: X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=junipernetworks.onmicrosoft.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 ciunoEjljFzC for ; Sun, 24 Jul 2016 09:21:07 -0700 (PDT) Received: from NAM01-BN3-obe.outbound.protection.outlook.com (mail-bn3nam01on0092.outbound.protection.outlook.com [104.47.33.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF1C712D1B2 for ; Sun, 24 Jul 2016 09:21:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=junipernetworks.onmicrosoft.com; s=selector1-juniper-net; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=URqOAPlo2ARk1KSDoLjbjiROmc3c1bIgcpA3jJ3/OAA=; b=hKd1q16p96SntnO8fR8Fh8T2CcnAYW7CGlJN/HV/SalY3ZhLuAcHkmFjlk/xGD7ebLpaMrYN4Qe1GNavU0Ty4zWpExAAYAS90obiE1Rr0JDU6eIGZMS894tqUI8oKJEdlKqjMAwHLQDQT0xMX8Ok+NuksDUAi3404NudtvtSjTg= Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=jgs@juniper.net; Received: from [172.29.64.104] (193.110.55.14) by CY1PR05MB2506.namprd05.prod.outlook.com (10.167.10.27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.549.5; Sun, 24 Jul 2016 16:21:03 +0000 From: John G.Scudder Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message-ID: <3E32D0E4-415B-4DE3-B63A-5013407CD718@juniper.net> Date: Sun, 24 Jul 2016 18:20:58 +0200 To: idr wg MIME-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) X-Mailer: Apple Mail (2.3124) X-Originating-IP: [193.110.55.14] X-ClientProxiedBy: DM2PR0501CA0001.namprd05.prod.outlook.com (10.162.29.139) To CY1PR05MB2506.namprd05.prod.outlook.com (10.167.10.27) X-MS-Office365-Filtering-Correlation-Id: 87a8b971-7832-430e-791e-08d3b3de8251 X-Microsoft-Exchange-Diagnostics: 1; CY1PR05MB2506; 2:4beZ1G/42qo5CPuJuAxtgA+BxF1B1i0l7pefD0sL7q5Z6h64Ed9vJuBLcp41RCx2M11NwkwM4+9JktLm+6DTUPZFfRWBGR4CCZ7/Jinwf/Ebf/oZHyINPvCLmHBJq+e+YFYE1VGsb1K1K9Zo7n1PubOpdC5g5QmlQIOPjnkSU4uhHiqHjtqI9s1QVIZBbmdn; 3:6wAK/RP9L8Tgpzwji6oZxHMdvirecYPvoB3utXW5wPVlQAKl7n+Ncw13DgKIYjsr+dm+3EZyD2ak0PqWIM3bkGh5enaEeoFCcOg+vQ1OIMHfw8KZEQg17VFAx1lpdh7g X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:CY1PR05MB2506; X-Microsoft-Exchange-Diagnostics: 1; CY1PR05MB2506; 25:fujCl+fQa2UgwrvfRz+/G/TDuiJC/EyeykXatAL1wrfpdP4ZxQ6ox246eZ/uj4l5Cxuve/b/nSvhUcv7U5N2S+g9YZLDt4gw4FJqelMtAf8YV/l9/bj1s2uu8Pczyybr29DAIQf99rNRWLyUVRPOy+4I5fsCA46XB/E1KE4P20Pgfo+Y9FzvB7aR/OK/hKhkCnqZCokO/Oi5ieBFS7x0DgB0CNd9fbhoNQ4HXsoR3TZOzqpY4uLWAvhYJ4/AUz5TlIUkAyzTLp47nancXxSE4aErzZowXylP0uXbv28T1SOxOhd0fD5YHUxouf9NVr37w6PwHCoouYSL4t0mBOdt8A6PrZiyHESXBLD6a4LhjsaRyZ7Ul06Bsc+GKiI0R+30sGnpqt1yeNnUxqr4NLkzEVtLsVxVRaLcipjaqn4f3aLhT8IK+bWrX5pLlH7uXX6n8LeGlvLNFw7+RqEXt83L//txIUfQkNJ7Y3ps8zPrCZGpuGfnoCx/iQoTId4CQk5olvImHz2gT/HGrDRHBshK6U2Vu60lu7+H9o5d0ju0VHl59iAWoplz+DvctYMF8VfYbcYsOTM/tPnseEti+v016DBHGUT5nYUbly0WLNdVM5s5ic9VrybN1PcdX3867OWFYa/LIL/8/q/V5Kno+iqxtPxUoBSma0crq3Y/a95VJge2bIr/UHEWLFbJu5yVyeGIf69MqWAkacjsQu2rjPxSoFNFKfHA05xfXC3A9ZYki/rOycKrQLC4k4z+5pWy6uRUQzSW8E+cptyaGUMzclU9LGKt1rStt0t7MvAGt3dMcjs= X-Microsoft-Exchange-Diagnostics: 1; CY1PR05MB2506; 31:Dvbq7JIESWvSXIacvvMvYxw83MPevbqAb07v9VX+3RqpzNIpZFIcFjuspI3boD1xXfAm1Gz/SNd2shcCIwnVLQnjOa1My8H2cJhS2ViMD7czxXGe+XWX9j9OvLPmax+ytETb15n0WVXjRxiBdiKW5qEJDvPI9cxgWeGbNn5d+hnwXEs8P+WOEG8F11b4HDLS1NRgIy16FiJMjmznvqizwQ==; 20:0SsFzCA3UDMUXy053O2hNinTuzCc6EY0loAfgWreXXXub6HsfF7K8iAAFRNWpQZ2PLKcUE4VbO6njYLiQh3cUBvPeX1/MNqgheyqcKTZjAIVkAvrE1/3VE6V2rjpsOF/46411pILUDYAyGOG6MqRA3cjnWUrlDwL/AYjQbfRAfomslfGhw6BExujs3ZEZjVZujyYiASQ/xK+FmEQEGhoFGZip2oBkR5o/US6kqwNzEcQvMA1rZm3R4S3uWUXhxA1Bvvv7wxt+uSUKueaoxMgVgeIXCEb1b9TVXyzFU5jh0Op0ovBDVVAy/6lDCUjWR0LZdLn1uRAri3pjezyPRTTQoY8fvtjijqxSUD6keizRaxRXY3NCIXlXcEEv4louzJdjGkbGx3SziSbc5ItTABA4JiXin206DxWmllHnoJj82dBU8FL156nhiIlMI9DJXovoABrtaax1h5c1p3wQJcFdCv8XNouyopImXLd1lJkov1r+LdUSXiATqNhHFauWKx+ X-Microsoft-Antispam-PRVS: X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001)(6055026); SRVR:CY1PR05MB2506; BCL:0; PCL:0; RULEID:; SRVR:CY1PR05MB2506; X-Microsoft-Exchange-Diagnostics: 1; CY1PR05MB2506; 4:jl/wND6bYo0LKLYm3VR7tV4uxXtMR+l3O+B1uqkM2aED7H7rbyJ5n67jw8rCJbeGWKwk+xphFYDKOciKk76FgOiTpiZsa7J/6PCoBcn6M3JHhqO2IoeIrozlkx67bMmABYBXMy2nRdL79nfUbxAxayIn8iQLEcCYlt1DTEDqJovZYG4h5PhFtOcIBhRQ7EJDCCyWDrKo208N03wXNXPpVy7kaO/pyzP9QChUsRCoW0C8ywujTmrRSXiO/NVJXmJchUG6wzAih8lP0+u4uCnMlO9KZw8Hh1kaYdvt5wV1/M08LcqBhhcXspxyfDj4742aTBbmRP4LWxsJRN9KLrDhy3zNGyhaZ4dPvbRamnI300HSwWZaOKQX/eTO60yfsHiR X-Forefront-PRVS: 0013079544 X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(6049001)(6009001)(7916002)(189002)(53754006)(199003)(36756003)(3846002)(50226002)(101416001)(23726003)(7736002)(15975445007)(77096005)(92566002)(229853001)(6116002)(586003)(97756001)(42186005)(305945005)(105586002)(19580395003)(82746002)(7846002)(106356001)(83716003)(86362001)(97736004)(50466002)(2906002)(450100001)(8746002)(47776003)(189998001)(57306001)(50986999)(107886002)(110136002)(33656002)(66066001)(68736007)(46406003)(8676002)(81156014)(81166006)(558084003)(104396002)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR05MB2506; H:[172.29.64.104]; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; Received-SPF: None (protection.outlook.com: juniper.net does not designate permitted sender hosts) X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; CY1PR05MB2506; 23:8bFXAZOJGblofx84VBFBp+Qwj2qJeKUJHVX/9W9gU?= =?us-ascii?Q?NAIIBHEJT2HEmgG4AZ8oIr2kjSYeJO30LFRzq0MwTrokiufwAZC9nFEhvyly?= =?us-ascii?Q?VBVPO6Tc5dX4iFNESPJQKtGs6sBMNrByYpmWU+deMpPkM+77ANrT2SNUP9ij?= =?us-ascii?Q?ubpLDnthr1vvINlNn+fgOSGij7SPjUG5IYxblIbE9g/4OStZ3KIWBFAUGFAY?= =?us-ascii?Q?6P90ORadMJXeYJeqOy3W/75yWwJGwnq2NNN5TJaVpZ9eocdu/wrGeLhaZ+uQ?= =?us-ascii?Q?WVD4LCyKrMgEJqWDEpN7IbmTba2ypZZLOEYroPLzEZTWyQtHQ8OGBfMo/iyR?= =?us-ascii?Q?rqIvDmk/nHZswG660KlJncFgaJu23/EEVRgotc8j2Wij5hzk3mtUj+HXSLuU?= =?us-ascii?Q?7DfsBzPs7CHUP2xPLmhxnlVt431cir0T7UZ45lZ104NlZhO9KganAlpg+Htl?= =?us-ascii?Q?Y4jEAVGNz846rYMxQYsJsL2cT12f/+pTCFzM7i/+Hr6c5XkUX+xTO0w+NtbN?= =?us-ascii?Q?7dU/LXRvMsMf6sOgSgoFHiWQk/+miCi+YOURDRrJgqXbqQ/X3HWzgZdX/3zh?= =?us-ascii?Q?vFdeDPsJEOmIwOMW0UUm3/+4YTrEoKyvG3hcbkq7uY1q+P70BQurmOb6v0gI?= =?us-ascii?Q?hF4QjZMcaDAHNTJw89gdwvd5dsMFDMWXQLICDGahDld6xXmCLppAYSIvi3Ny?= =?us-ascii?Q?D9lyen9H7tDBDF2TkhOfabjkHwXAokU6m29U/8+H135QPLm1g7M5E8VMqp6x?= =?us-ascii?Q?Q90EGTI1x1vVXAgCzKiKTd17+ZhUM/HtXOJAMfQtqWrZUzXwvDG40cJ1SFPP?= =?us-ascii?Q?sPn4sSBpwJeRb4ScIpdwI41oCBzHqL4ai/27cs4GojurCKQXSdijEc8sX7Kg?= =?us-ascii?Q?dN4SajRucu+yxQcwjayW5mqMIYo5DQbWdeXsx4A7z90A41pwNIiYbwQnHwdz?= =?us-ascii?Q?vXgCjhfsjkfuQq6n6f6hVZmfDgqI2/M79EfqmZi+8LcEXA1zLwl7wGdfMYCf?= =?us-ascii?Q?EA0FP819u4nmStzMHF8dJJ54w+R5/WDSTJEwAYm3+RsZO2piKGT0yMygjFWd?= =?us-ascii?Q?jmNGXXVZ+cYRgcn4DLwZgyInEzLZhmxCUkKFXjhJdPh09i2VzbYUJAz0mXCx?= =?us-ascii?Q?b/kDMMZPVgvAgbUFbDiYfzdhRXaVjGGZ41NFNMkLCxZ4YMmpvwfOBrl8v3jq?= =?us-ascii?Q?TYVaP9Od1nZXhoVLR4gZw3P8VCVk8hbBxtHm4Ee5yFCCEsnpCHEb5lQMw=3D?= =?us-ascii?Q?=3D?= X-Microsoft-Exchange-Diagnostics: 1; CY1PR05MB2506; 6:SpKxfDPFhPj2r6tdAFa5qXO/CLomaLvv4Rtqwu8Ond4ufFOXKipJNRtk14FUqKwLz1xzKHLDEz9+9sC92Stwrr8gmqu1rA/J1KoF5rIXvjXRzdjGYqjb5kszRf3hKRL7UlvQFD62OQ77VCGWKCL6wT7x5AWxEAC3puh2r30WPKQjrvZRIZ3UpAc9dBXAtgQhudFLSrG3mIHaQ2RJOzgMjtFclNfbfJB3JuJdwjj0NhpoFEVvqcvk1CUm1IT0GR+LslLdZ/fFup9ZAa0o3NZWyMHaxnEQNFPfp8LVsYrO0M/tgv+FL3bU3PEl962zNJxvd/FX/zhv+iHe999QbB2kzg==; 5:GSG/XqFOQN9xxbdxwHRMyX5dWS6SsKtBmlRMxPn7GGSPCaQdMIgr/hdXBlGvGwbQHbbJNVYfnQvFviGPHxL6DyBtiinhCKo2lesdjXvh8bf2CQmoaMp9a9JFJGBO0D+00kcN4SLgglzIMdnKrtGLPA==; 24:s5s0fhL2zjm28a/AU9vT26DgFKse9BBTm4PkAc+aVXubrE7Yflh6iSl3IhwGYU0kfEobzfsTdjJwuLqewkZhGMMn50geJPNNQ1NlW+dw7pk=; 7:W7u75m08ewND9ckF8oeL3NItI4EmzQgAe0sEsWN6oPkou1EOCxmkrPz8ibpTPgQ8jEc75lKf1byglpHBiAqienghl/p5Ockq2w6PCZzaRdL6OcarDSnNMjJeice5Jl31pjLW1e6lQ9myj0Y86I3RR5aYG4EBfS3HN+AWSJFTMO//1xsdSBiTlp4YQqoln75eYd2O1jD/iy1DoB+SLx8KmX7dz9HIhR3ZJ/R8Y40EujdnGMhC/8kjlQgW7NB5L4KY SpamDiagnosticOutput: 1:99 SpamDiagnosticMetadata: NSPM X-OriginatorOrg: juniper.net X-MS-Exchange-CrossTenant-OriginalArrivalTime: 24 Jul 2016 16:21:03.1203 (UTC) X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR05MB2506 Archived-At: Subject: [Idr] Minutes of IETF-96 SPRING posted X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jul 2016 16:21:09 -0000 Hi Everyone, Minutes are now available at = https://www.ietf.org/proceedings/96/minutes/minutes-96-spring. Please = send any corrections or comments to the list. Thanks to Wim for the = notes! --John= From nobody Sun Jul 24 14:19:43 2016 Return-Path: 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 8E8C812B00B for ; Sun, 24 Jul 2016 14:19:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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 owd9QeisIZ1h for ; Sun, 24 Jul 2016 14:19:40 -0700 (PDT) Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001:c06::234]) (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 446A412B007 for ; Sun, 24 Jul 2016 14:19:40 -0700 (PDT) Received: by mail-io0-x234.google.com with SMTP id 38so146684461iol.0 for ; Sun, 24 Jul 2016 14:19:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=kCycv22QPXOMlg/juUh0TPJiPbDerHFCgn28oYn5Wok=; b=W3dfBxYXUMX7tASTpWogtSmitsiiKKIw7WHRQqbXZR0HynfxKhLaX1Py4Ctfs9ehpG PfEZ/e/sMnE/7s5WrSNOwrI/j0oAQdIv6h2kYSIwj03QJPMXIWgrnr/HFlDOWeC+5NjD b1X0oec3Otqf4NsWryTzcGNHcRTHb2NZwI6kJqqMDbj5ttXrozr/kZ9C1amFPY3UhW68 +aqoQFwnM+d2iM1AoEAD/fxdMydIC2ajTfNc52YxhN8XvkPIpS3U7KdVjsPGxnxuSzR0 6qqFazuLRk46DaSod+4QNixmKnej6YU2dzN2SwCjLoIZJ7F9dUsc7dhlwXENDeKT4ggl E77Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=kCycv22QPXOMlg/juUh0TPJiPbDerHFCgn28oYn5Wok=; b=OF9G4mRjshQ0uMPM3Y5wQVpn2gUE5uYzlnmwF7/lQ0kK/cBIO0Uv+Ne8efjBBnItBG KakKrkYnPBk4fJoG5XCsuItDLEHUYEj2v8MlOaGXHu7/wUV4qYzEECLzCTEdgrF4ZINc /Rd011nE6hweTXPGFFNxNO0DDQ/pJRZ37dfqjj+1QXZx1Etogy6rBVmFogPqgwjmef0U tgZZlh2NDoxFywzZTuCEzXtMHDNHWiLdfzM/0B1JUgJ5t1X14CGntAHtxrlzXxZLhNGp /5SeWrkXZ0U5ol85QzegpkgYFvw+D/QFSTIhrEKL4oOILDu0Y2TN2llj/PRjOoKPB1CO 0GJw== X-Gm-Message-State: AEkoouvMXgR7IFkY0+EOCVND+PEw+6LRTfQutAbTMmC65o3naTfBRU1SGsBVb/qi0VKDujhRRixwRzfm3HrgNQ== X-Received: by 10.107.25.75 with SMTP id 72mr17158224ioz.50.1469395179402; Sun, 24 Jul 2016 14:19:39 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.158.82 with HTTP; Sun, 24 Jul 2016 14:18:59 -0700 (PDT) In-Reply-To: References: <76CD132C3ADEF848BD84D028D243C92774EEF7CF@NKGEML515-MBX.china.huawei.com> From: Tony Przygienda Date: Sun, 24 Jul 2016 23:18:59 +0200 Message-ID: To: Robert Raszuk Content-Type: multipart/alternative; boundary=001a113fe4deb3fa960538683929 Archived-At: Cc: "Keyur Patel \(keyupate\)" , idr wg Subject: Re: [Idr] Fwd: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jul 2016 21:19:42 -0000 --001a113fe4deb3fa960538683929 Content-Type: text/plain; charset=UTF-8 inline On Sun, Jul 24, 2016 at 4:22 PM, Robert Raszuk wrote: > Dear Antoni, > > The point here is not about the question if query in BGP is good or bad or > how easy or difficult it is to implement. > > The points to discuss are following: > > #1 What parameters are used to "query" ? > > #2 How does defined "query" work with existing BGP protocol and extensions > ? > > #3 What protocol state machine change triggers "query" action ? > > - - - > > Ad 1 - > > Cool that we have already accomplished consensus to get rid of RD query. > If you do not specify anything the automatic assumptions would be *ANY* RD > anyway if you query by anything other then NLRI prefix. Query by NLRI is > questionable too (see below Ad 3). > > Now let's talk about (in)famous EVPN route types you keep bringing as > query parameter. Please observe that RFC7432 does not define BGP capability > per route type and only negotiates 25/70 implicitly indicating support of > all route types. Moreover RFC7432 is very clear that to accomplish > filtering of routes on the sender side use of RTC is recommended. > > I think I admitted that getting rid of RD query is reasonable (as long we understand that any other query means "any RD") If you think asking for a new route-type in EVPN via AFI/SAFI refresh and being swamped with all MAC updates is a reasonable deployment option then we simply disagree and the operational world will tell us what is reasonable. > > Ad 2 - > > Assume operator is using RTC so list of RT filters is populated by the > peer outbound towards querying bgp speaker. Now issuing query for anything > needs to be evaluated against already supported Enhanced Route Refresh > (RFC7313) which btw you are also obsoleting here where you get full > filtered by RTC list of interesting NLRIs for specific AFI/SAFI. > > On the topic of obsoleting RFC2918 I must say that I hope this is just a > huge oversight ... Your current draft says: > > "When the Route Refresh Options Capability has been negotiated by both > sides of a BGP session, both peers MUST use message types 3, 4 and 5." > > And message type 3 clearly states that I must have at least one refresh > option ... quote from the field of the msg: "One or more Route Refresh > Options" > > That means that I no longer can ask for refresh of the entire AFI/SAFI - > this is pretty bad. > Absolutely valid, albeit subtle point. "zero or more route refresh options" should be specified. Obsoleting 70 when 74 is present is simplifying things. We can keep mixture of 70 and 74 but implementation will get pretty hairy when you talk details. We talked that through with Cisco co-authors @ length and actually changed from "you can do both in parallel" to "nah, 74 obsoleting 70 is much better/cleaner/easier". > > > Ad 3 - > > Now the crux of all of this ... > > Please enumerate on the list or in the draft what exact protocol state > machine transitions will result in automated query for subset of given > AFI/SAFI with and without prior use of RTC and ORF filters. > section 1.1. in the draft and to be extended > > In other words I do not buy general justifications explained before, > quote: > > * "now I need the information again" > > * " The motivation for this work were scenarios where a single-shot > refresh is needed, actually concurrent bunch of those based on > configuration changes, > > --> You need per AFI/SAFI or per RT refresh > > " in policy changes, joining VPNs, EVIs and so on." > > --> You need per AFI/SAFI or per RT refresh > ok, then as I said, we agree to disagree and then we don't have currently a really practical solution to the cases mentioned in 1.1 and yes, RTC can be used for that if you're willing to maintain RTs for all possible sets you may need to refresh and the draft very explicitly acknowledges that already. Given you know those sets upfront. If you deploy EVPN today and new route type gets introduced (type-6) you better go and reconfigure all your routers in the networks with this type-6-per-EVI=a new RT knowledge to satisfy the "I need now type-6 routes for the EVIs I configured for multicast" use case. Quite a lot of configuration there since it's combinatorial with every parameter. Extending ORF with new filters will lead due to the accept/reject non-computable language to full walks of which you can have one in parallel in ORF and you chose to not answer any of the "and then you'll get flooded on change of ORF filter anyway" observations which leads overall to an interesting, partial treatment of the subject. Frankly, the arguments we are engaged in are becoming repetitive by now, we should close this discussion and see whether implementation/acceptance by major vendors given the pressure of deployment cases we listed will lead to acceptance or the draft will linger ... --- tony --001a113fe4deb3fa960538683929 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
inline

On Sun, Jul 24, 2016 at 4:22 PM, Robert Raszuk = <robert@raszuk.ne= t> wrote:
=
Dear = Antoni,

The point here is not about the question if query in BGP is go= od or bad or how easy or difficult it is to implement.

The points to d= iscuss are following:=C2=A0

#1 What parameters are used to "query= " ?=C2=A0

#2 How does defined "query" work with existin= g BGP protocol and extensions ?

#3 What protocol state machine cha= nge triggers "query" action ?

- - -=C2=A0

Ad 1 -=C2=A0<= /div>
=
Cool that we have already accomplished consensus to get rid of RD quer= y. If you do not specify anything the automatic assumptions would be *ANY* = RD anyway if you query by anything other then NLRI prefix. Query by NLRI is= questionable too (see below Ad 3).=C2=A0

Now let's talk about (in= )famous EVPN route types you keep bringing as query parameter. Please obser= ve that RFC7432 does not define BGP capability per route type and only nego= tiates 25/70 implicitly indicating support of all route types. Moreover RFC= 7432 is very clear that to accomplish filtering of routes on the sender sid= e use of RTC is recommended.=C2=A0


I think I admitted that getting rid of RD query is reasonable (as = long we understand that any other query means "any RD")=C2=A0

If you think asking for a new route-type in EVPN via = AFI/SAFI refresh and being swamped with all MAC updates is a reasonable dep= loyment option then we simply disagree and the operational world will tell = us what is reasonable.=C2=A0
=C2=A0

Ad 2 -=C2=A0

Assume operator is using RTC so = list of RT filters is populated by the peer outbound towards querying bgp s= peaker. Now issuing query for anything needs to be evaluated against alread= y supported Enhanced Route Refresh (RFC7313) which btw you are also obsolet= ing here where you get full filtered by RTC list of interesting NLRIs for s= pecific AFI/SAFI.=C2=A0

On the topic of obsoleting RFC2918 I must say = that I hope this is just a huge oversight ... Your current draft says:=C2= =A0

"When the Route Refresh Options Capability has been negotiate= d by both
sides = of a BGP session, both peers MUST use message types 3, 4 and 5."
=

And message type 3 clearly stat= es that I must have at least one refresh option ... quote from the field of= the msg: "One or more Route Refresh Options"=C2=A0=

That= means that I no longer can ask for refresh of the entire AFI/SAFI - this i= s pretty bad.=C2=A0

Abso= lutely valid, albeit subtle point. "zero or more route refresh options= " should be specified.=C2=A0

Obsoleting 70 wh= en 74 is present is simplifying things. We can keep mixture of 70 and 74 bu= t implementation will get pretty hairy when you talk details. We talked tha= t through with Cisco co-authors @ length and actually changed from "yo= u can do both in parallel" to "nah, 74 obsoleting 70 is much bett= er/cleaner/easier".
=C2=A0
<= span style=3D"color:rgb(0,0,0);font-size:13.3333px;font-family:arial,sans-s= erif">

Ad 3 -=C2=A0

Now the crux of all of this ...=C2=A0

Please enu= merate on the list or in the draft what exact protocol state machine transi= tions will result in automated query for subset of given AFI/SAFI with and = without prior use of RTC and ORF filters.=C2=A0

section 1.1. in the draft and to be extended
<= div>=C2=A0

In other words I do n= ot buy general justifications explained before,=C2=A0quote:= =C2=A0

* "now I need the information again"=C2=A0

* "=C2=A0The motivation for this work were scenari= os where a single-shot refresh is needed, actually concurrent bunch of thos= e based on configuration changes,=C2=A0

--> You need per AFI/SAFI or per RT refresh

" in policy changes, joining VPNs, EVIs and = so on."=C2=A0

--> You need per AFI/SAFI or per RT refresh

ok, then as I said, we agre= e to disagree and then we don't have currently a really practical solut= ion to the cases mentioned in 1.1 and yes, RTC can be used for that if you&= #39;re willing to maintain RTs for all possible sets you may need to refres= h and the draft very explicitly acknowledges that already. Given you know t= hose sets upfront. If you deploy EVPN today and new route type gets introdu= ced (type-6) you better go and reconfigure all your routers in the networks= with this type-6-per-EVI=3Da new RT knowledge to satisfy the "I need = now type-6 routes for the EVIs I configured for multicast" use case. Q= uite a lot of configuration there since it's combinatorial with every p= arameter.=C2=A0

Extending ORF with new filters wil= l lead due to the accept/reject non-computable language to full walks of wh= ich you can have one in parallel in ORF and you chose to not answer any of = the "and then you'll get flooded on change of ORF filter anyway&qu= ot; observations which leads overall to an interesting, partial treatment o= f the subject.=C2=A0

Frankly, the arguments we are= engaged in are becoming repetitive by now, we should close this discussion= and see whether implementation/acceptance by major vendors given the press= ure of deployment cases we listed will lead to acceptance or the draft will= linger ...=C2=A0
=C2=A0
--- tony=C2=A0
--001a113fe4deb3fa960538683929-- From nobody Sun Jul 24 14:31:55 2016 Return-Path: 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 3E90A12B007 for ; Sun, 24 Jul 2016 14:31:54 -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 d0hXdBUufXsq for ; Sun, 24 Jul 2016 14:31:52 -0700 (PDT) Received: from mail-qk0-x22b.google.com (mail-qk0-x22b.google.com [IPv6:2607:f8b0:400d:c09::22b]) (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 56B3C12D5C5 for ; Sun, 24 Jul 2016 14:31:52 -0700 (PDT) Received: by mail-qk0-x22b.google.com with SMTP id s63so141752975qkb.2 for ; Sun, 24 Jul 2016 14:31:52 -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=9K0cn6HpiGts4eQaqQq+0FJzoXynkHVnAXcF8sZ17TM=; b=zdFhfgnpyVeS3B0AzGgZypCwq+N4seFhOkrUTbRlNCJjP6iz/W8SUexciA/eeCMLVM NP4g7MSbexHd77USIf5f41chpdJiHM50w7tuZcaQFDna91PEx3stvS09R+4Dz/SNOxVz k5Ss5aEgiXCipo+ISiMlAlO+L5Ex/VOREc1qAGa6FL48fpifHPQfZDcIoQHVaHnm1w+a pJagHA4js7l+EwfDN0TU8OTr1Dpqq2s8XsggtSCGrvbYn2GKjH7nZxGpgsEsZS5+23A2 IywXYuse+D4b2LOSyAa/9U0A+diUktENb/cB2AMNu6elJUu6Wik13F4qGaMrsMrora2n ZakA== 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=9K0cn6HpiGts4eQaqQq+0FJzoXynkHVnAXcF8sZ17TM=; b=cOznQnlS30+EXShla72VrZGSmToF+4cygcl3maRZ7MKAdiK2V/GQCXVGYofLPgD/iB W55oVSoOupPJXgwccdqrZewvnv+PZrNZSeUvM0xKBJMDOI9+Frd2goz8LzbRniIoRWql /gjpYnbJwL0r3RTWEHq9aZgRi3pjHSu+Olb3wdA0dPMkBXHmyD7KCdi1PvEao/+TzXAb eHjbq5/flOpQQsDjUHvwa3HIFI13YbryEMIJaTXumY50a93o5lxWKQj+zJB14Jz6+Eou sPjHtW7ECRlh53D1OgYJRGo035oSquKvAA7ApdVubqq1mq/vs9mNnoeZAVCP25uy2bNz XB0A== X-Gm-Message-State: AEkoouuORSspX4N4ve8rwgZxop1fd7OzIp3D+pb4DfWTEDhTgJRWOWdrlhTV3niMJ9dR9CuJL+YH08S5PJl2PQ== X-Received: by 10.55.129.71 with SMTP id c68mr18792726qkd.174.1469395911424; Sun, 24 Jul 2016 14:31:51 -0700 (PDT) MIME-Version: 1.0 Sender: rraszuk@gmail.com Received: by 10.237.36.90 with HTTP; Sun, 24 Jul 2016 14:31:49 -0700 (PDT) In-Reply-To: References: <76CD132C3ADEF848BD84D028D243C92774EEF7CF@NKGEML515-MBX.china.huawei.com> From: Robert Raszuk Date: Sun, 24 Jul 2016 23:31:49 +0200 X-Google-Sender-Auth: iDHg84RA7bId5YLngNP7PRXu_cI Message-ID: To: Tony Przygienda Content-Type: multipart/alternative; boundary=94eb2c06266a55c34a053868653f Archived-At: Cc: "Keyur Patel \(keyupate\)" , idr wg Subject: Re: [Idr] Fwd: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jul 2016 21:31:54 -0000 --94eb2c06266a55c34a053868653f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable =E2=80=8BHey Tony,=E2=80=8B > I think I admitted that getting rid of RD query is reasonable (as long we > understand that any other query means "any RD") > =E2=80=8BDone. Absolutely valid, albeit subtle point. "zero or more route refresh options" > should be specified. > =E2=80=8BGreat.=E2=80=8B Obsoleting 70 when 74 is present is simplifying things. We can keep mixture > of 70 and 74 but implementation will get pretty hairy when you talk > details. We talked that through with Cisco co-authors @ length and actual= ly > changed from "you can do both in parallel" to "nah, 74 obsoleting 70 is > much better/cleaner/easier". > =E2=80=8BYes one =E2=80=8BSAFI =E2=80=8B is much cleaner, but you can't break per AFI/SAFI refresh. =E2=80=8B =E2=80=8BSo now I consider this fixed. =E2=80=8B > ok, then as I said, we agree to disagree and then we don't have currently > a really practical solution to the cases mentioned in 1.1 and yes, RTC ca= n > be used for that if you're willing to maintain RTs for all possible sets > you may need to refresh and the draft very explicitly acknowledges that > already. > =E2=80=8BPossible sets .. hmmm how about this to address route types: 1 RT per route type of a given AFI/SAFI ... not much burden at all - for EVPN you burn 5-6 RTs for entire network. =E2=80=8B > Given you know those sets upfront. If you deploy EVPN today and new route > type gets introduced (type-6) you better go and reconfigure all your > routers in the networks with this type-6-per-EVI=3Da new RT knowledge to > satisfy the "I need now type-6 routes for the EVIs I configured for > multicast" use case. Quite a lot of configuration there since it's > combinatorial with every parameter. > =E2=80=8BNot at all .. forgot that RTs can be applied on RR per route type = of NLRI on inbound. Your colleagues already defined that in the other work :) =E2= =80=8B Minimal configuration, existing protocols and all benefits. Cheers, R. --94eb2c06266a55c34a053868653f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
=E2=80=8BHey Tony,=E2=80=8B
=C2=A0
I think I admitted that getting rid of RD = query is reasonable (as long we understand that any other query means "= ;any RD")=C2=A0

=E2=80=8BDone.=C2=A0

Absolutely valid, a= lbeit subtle point. "zero or more route refresh options" should b= e specified.=C2=A0

=
=E2=80=8BGreat.=E2=80=8B

Obsoleting 70 when 74 is present is simplifying = things. We can keep mixture of 70 and 74 but implementation will get pretty= hairy when you talk details. We talked that through with Cisco co-authors = @ length and actually changed from "you can do both in parallel" = to "nah, 74 obsoleting 70 is much better/cleaner/easier".

=E2=80=8BYes one
=E2=80=8BSAFI =E2=80=8B
is much cleaner, but you can't br= eak per AFI/SAFI refresh. =E2=80=8B
=E2=80= =8BSo now I consider this fixed. =E2=80=8B

=C2= =A0
ok, then as I said, we agree t= o disagree and then we don't have currently a really practical solution= to the cases mentioned in 1.1 and yes, RTC can be used for that if you'= ;re willing to maintain RTs for all possible sets you may need to refresh a= nd the draft very explicitly acknowledges that already.
<= /div>

=E2=80=8BPossible = sets .. hmmm how about this to address route types:=C2=A0

1 RT per route type of a given AFI/SA= FI ... not much burden at all - for EVPN you burn 5-6 RTs for entire networ= k. =E2=80=8B
=C2=A0
Given you know those sets upfront. If you deploy EVPN today and new route= type gets introduced (type-6) you better go and reconfigure all your route= rs in the networks with this type-6-per-EVI=3Da new RT knowledge to satisfy= the "I need now type-6 routes for the EVIs I configured for multicast= " use case. Quite a lot of configuration there since it's combinat= orial with every parameter.=C2=A0
=
=E2=80=8BNot at all .. forgot that RTs ca= n be applied on RR per route type of NLRI on inbound. Your colleagues alrea= dy defined that in the other work :) =E2=80=8B

=
Minimal configuration, existing protocols and all = benefits.=C2=A0

Cheers= ,
R.

--94eb2c06266a55c34a053868653f-- From nobody Mon Jul 25 12:27:02 2016 Return-Path: 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 2F58F12D94E for ; Mon, 25 Jul 2016 12:27:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.189 X-Spam-Level: X-Spam-Status: No, score=-3.189 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.287, 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 UmlXPWjHTELw for ; Mon, 25 Jul 2016 12:26:59 -0700 (PDT) Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 1998012D5F0 for ; Mon, 25 Jul 2016 12:26:59 -0700 (PDT) Received: by slice.pfrc.org (Postfix, from userid 1001) id F206A1E31F; Mon, 25 Jul 2016 15:27:42 -0400 (EDT) Date: Mon, 25 Jul 2016 15:27:42 -0400 From: Jeffrey Haas To: "John G. Scudder" Message-ID: <20160725192742.GA28841@pfrc.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Archived-At: Cc: idr@ietf.org Subject: Re: [Idr] Minutes of IETF-96 IDR posted X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jul 2016 19:27:01 -0000 On Sun, Jul 24, 2016 at 06:11:24PM +0200, John G. Scudder wrote: > Minutes are now available at https://www.ietf.org/proceedings/96/minutes/minutes-96-idr. Please send any corrections or comments to the list. Thanks to those who pitched in to take the notes. Minor correction: : Jeff: You are using the wrong handle. Use the IGPs. Consider going to wrong hammer. I also suggest expanding all of the speaker initials in the minutes. -- Jeff (particular about tools used to beat up stuff) From nobody Tue Jul 26 08:21:33 2016 Return-Path: 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 24D1D12DF25; Tue, 26 Jul 2016 08:21:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.45 X-Spam-Level: X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=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 aqwdkQj06eRm; Tue, 26 Jul 2016 08:21:23 -0700 (PDT) Received: from mail-io0-x232.google.com (mail-io0-x232.google.com [IPv6:2607:f8b0:4001:c06::232]) (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 ABB8312D7C2; Tue, 26 Jul 2016 07:47:01 -0700 (PDT) Received: by mail-io0-x232.google.com with SMTP id m101so23783041ioi.2; Tue, 26 Jul 2016 07:47:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=5Xu5lwSLiZ+j5NGlmFdVzS/QsDqJAo7sck0xtKFyV4c=; b=NlFKStQrvCaiUMXOy9z5/4XcChksAW71c33KXUGmxcSorg1Usa/pJ5wEYQHIIMzplP OC8lImsQqBIgxUvWuA/7D+nd0+UHucej1Au2O27pWNmK6nwk/S2DYkJ/al76FO0gkKcs htKrcijaY3aAmz8LYiWkw/GHW12YA5lvaqAdykB0RHMTzTVJurKkDhU7DmiP0V2MHKbq fB89hPqVoL/FlYZjbV1w2mKfh3rA3xnGrGCPdRO2GmTwUdB2DPqVmxHIw9txckkoHb5z hOsapTaR4MbWGbzzl4o/IJ5oC2Mk6NiRMw3nu4IpDYnPNtucwRzeztGBcXod7d/PMqep WoVw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=5Xu5lwSLiZ+j5NGlmFdVzS/QsDqJAo7sck0xtKFyV4c=; b=ZeI70XWk5oOsJiBhf76iMyqpcaL7DBulnn4XK/5iYlIXJrIVsXNOMWrwgxjthBV3W8 OalM12HfGKvRaBJ2AC9OBoJtFxAQDR5EtXQL1U3kNOe5K44A6+AgjzP3YMwtB/d6YiHA TEJ7uCT6haLS3n4b66PzBadTV1JTEnYC4Ca8+uS/7Y7dwXmeSRVmsCnf1TVdv6JJdzhL pu5YVdhylZyatDQjSITvvX/rC5AJWBTun6+M76F/uNmaw4VDYvWm+d5LdEOY7WJKsugi uTeN+aVcm1SfB4xuxwam8y3baRcm8Dwt2Mvxw8MASDK1S/yl7k8Tr2rffEq3iwUqrHF9 sJmQ== X-Gm-Message-State: AEkoouuq6uSmdtr5OuKkfjlwsmS2act2R/V6nygapmJHX7yTXmTLnQzFozN1J2Mm+BOyf1o4BGg8bTmB/YFT8w== X-Received: by 10.157.39.130 with SMTP id c2mr12150583otb.181.1469544420748; Tue, 26 Jul 2016 07:47:00 -0700 (PDT) MIME-Version: 1.0 Received: by 10.157.40.40 with HTTP; Tue, 26 Jul 2016 07:46:46 -0700 (PDT) In-Reply-To: References: From: Donald Eastlake Date: Tue, 26 Jul 2016 10:46:46 -0400 Message-ID: To: "trill@ietf.org" , idr@ietf.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Archived-At: Subject: [Idr] Fwd: routing directorate QA review of draft-ietf-idr-ls-trill-01.txt X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jul 2016 15:21:27 -0000 Forwarding to addresses that should have been cc'ed below. Thanks, Donald =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D Donald E. Eastlake 3rd +1-508-333-2270 (cell) 155 Beaver Street, Milford, MA 01757 USA d3e3e3@gmail.com ---------- Forwarded message ---------- From: Donald Eastlake Date: Tue, Jul 26, 2016 at 1:47 AM Subject: Re: routing directorate QA review of draft-ietf-idr-ls-trill-01.tx= t To: Ross Callon Cc: Susan Hares , "sujay.gupta@ipinfusion.com" , "mdurrani@cisco.com" , Liyizhou , John Scudder , "rtg-dir@ietf.org" , Haoweiguo , "trill-chairs@ietf.org" Hi Ross, Sorry for the delay in response. Based on discussions with Hao Weiguo, the plan is to make minor changes in the draft so as to indicate that the transported MAC reachability information and the like is for telemetry purposes and for use by SDN controller(s) where the coordination or protocol between the SDN controllers is out of scope. Thanks, Donald =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D Donald E. Eastlake 3rd +1-508-333-2270 (cell) 155 Beaver Street, Milford, MA 01757 USA d3e3e3@gmail.com On Sun, Jul 10, 2016 at 8:58 PM, Haoweiguo wrote: > Hi Ross, > > Sorry for late response. > > Thanks for your great comments. Pls see inline. > > weiguo > > ________________________________ > > From: Ross Callon [rcallon@juniper.net] > Sent: Tuesday, June 21, 2016 10:27 > To: Haoweiguo; Donald Eastlake; Susan Hares; sujay.gupta@ipinfusion.com; > mdurrani@cisco.com; Liyizhou; John Scudder > Cc: idr@ietf.org; trill@ietf.org; rtg-dir@ietf.org; Ross Callon > Subject: routing directorate QA review of draft-ietf-idr-ls-trill-01.txt > > I have been selected as the QA reviewer for draft-ietf-idr-ls-trill-01.tx= t. > For more information about the Routing Directorate, please see > http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir > > Summary: > > I think that this draft is straightforward and well written. I have only = a > couple of questions and some very minor nits. > > I can see situations in which putting TRILL information into BGP may make > sense, particularly in the case of providing TRILL information to a SDN > controller as pointed out in the draft. Due to the close relationship of > this draft to the work in TRILL I have CC=E2=80=99d the TRILL working gro= up on this > review and I assume that the TRILL working group will similarly be inform= ed > when the document goes to WGLC. > > > Questions: > > Section 1, second to last paragraph states: > > If ESADI (End Station Address Distribution Information) protocol > [RFC7357] is used for control plane MAC learning in each data center, > BGP LS also can be used for MAC address reachability information > synchronization across multiple TRILL domains. End-to-end unicast > forwarding paths can be calculated based on the synchronized > information. > > Would this be limited to the case where routes are computed by SDN > controllers? I am thinking that if instead the MAC reachability from one > data center is passed via BGP and fed back into TRILL in a different data > center then this would lead to significant issues which have not been > discussed in this document. > [weiguo]: Yes, the routes are consumed and computed by SDN controllers is > the main case. However, i don't know why the MAC reachability passing fro= m > one data center and feeding back into another data center will cause > significant problems, can you explain further about this? > > Section 5 (security considerations) states: > > Procedures and protocol extensions defined in this document do not > affect the BGP security model. See [RFC6952] for details. > > I am not a TRILL expert and therefore might not fully understand all case= s > in which TRILL is used. I am however wondering if there are TRILL-specifi= c > issues in that the TRILL information must only be passed to TRILL capable > devices. I am also wondering whether there is any valid use of =E2=80=9CT= RILL in > BGP=E2=80=9D other than passing TRILL information to SDN controllers. Pas= sing TRILL > information from one TRILL domain to another TRILL domain and then > redistributing the information back into normal TRILL packets seems like = a > bad idea at first glance. I am wondering if this section should say > something like =E2=80=9Cthis protocol MUST be used ONLY for passing TRILL > information from TRILL devices to SDN controllers, and for passing TRILL > information between SDN controllers. > [weiguo]: BGP LS provides a mechanism for passing TRILL information from = one > domain to another domain, it also can be used for passing TRILL informati= on > from TRILL devices to SDN controllers and between SDN controllers. Can yo= u > explain further about why BGP LS can't be used for passing TRILL informat= ion > from one domain to another domain? > > Very minor nits: > > Section 2 defines the RFC2119 terms and abbreviations used in this docume= nt > in the same section with no subsections. I think that it is more normal t= o > have a subsection for RFC 2119 terms and a different subsection for > abbreviations used in this document. > [weiguo]: OK, will change it in next version. > Section 3, first paragraph, last sentence: =E2=80=9C=E2=80=A6multicast gr= oup address, and > etc.=E2=80=9D should be =E2=80=9C=E2=80=A6multicast group address, etc.= =E2=80=9D. > [weiguo]: OK, will change it in next version. > Section 3.1, =E2=80=9CiS-IS=E2=80=9D should be =E2=80=9CIS-IS=E2=80=9D. > [weiguo]: OK, will change it in next version. > Section 4, second paragraph, I thought that it was a bit odd for a docume= nt > to reference itself, as in =E2=80=9CAn implementation of this > specification[idr-ls-trill], MUST do=E2=80=A6=E2=80=9D. Would this be a b= it less awkward as: > =E2=80=9CAny implementation of the protocol in this specification (ie tha= t > distributes TRILL Link-State information using BGP), MUST do=E2=80=A6=E2= =80=9D. > [weiguo]: OK, will change it in next version. > > That is all that I found in a couple of readings of this document, > Thanks, Ross > From nobody Thu Jul 28 19:18:22 2016 Return-Path: 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 CE9C212D605 for ; Thu, 28 Jul 2016 19:18:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -15.807 X-Spam-Level: X-Spam-Status: No, score=-15.807 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 izURVRnPGsaZ for ; Thu, 28 Jul 2016 19:18:18 -0700 (PDT) Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C2AAD12D5B9 for ; Thu, 28 Jul 2016 19:18:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8280; q=dns/txt; s=iport; t=1469758698; x=1470968298; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=XgUmnT550slAZ6XAQFuRYwPOvMp5tJqL0XULBgHtzlw=; b=ctnMzJR35TuQvc1+MotNdzqFjaTi/JlDx9smTq+LrX5kRjC31H7A5N5X QrZ09CjIw6UdMjTGJjIJsHvN8Uk2GmMArjE81x36tM99zLJK6XMKIUcPH MmDKV4qrA0KEskQV2AG23URZ9A+eacw716ptOPeBhpi73zQasxdovHpBQ M=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DKAgD/u5pX/5NdJa1dgndOVnwGs3WFB?= =?us-ascii?q?YF9JoV3AhyBFjgUAQEBAQEBAV0nhF0BBSMKTBACAQg7BwICAjAlAgQBDQ2IKQ6?= =?us-ascii?q?uIY1vAQEBAQEBAQEBAQEBAQEBAQEBAQEBFwWGKoRNgSKCeoMlgloFiQSKbIVCA?= =?us-ascii?q?Y52j0aQJQEeNoJFgTVuAYZURX8BAQE?= X-IronPort-AV: E=Sophos;i="5.28,437,1464652800"; d="scan'208,217";a="303895023" Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Jul 2016 02:18:17 +0000 Received: from XCH-ALN-019.cisco.com (xch-aln-019.cisco.com [173.36.7.29]) by rcdn-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id u6T2IHDR031475 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 29 Jul 2016 02:18:17 GMT Received: from xch-aln-014.cisco.com (173.36.7.24) by XCH-ALN-019.cisco.com (173.36.7.29) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 28 Jul 2016 21:18:17 -0500 Received: from xch-aln-014.cisco.com ([173.36.7.24]) by XCH-ALN-014.cisco.com ([173.36.7.24]) with mapi id 15.00.1210.000; Thu, 28 Jul 2016 21:18:17 -0500 From: "Jakob Heitz (jheitz)" To: Robert Raszuk , Tony Przygienda Thread-Topic: [Idr] Fwd: Slot request in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00.txt Thread-Index: AQHR4aVazIYBPV/cR0uGH7jm8G+9GqAgntcAgAABUACAAAdOAIAAAyuAgAF604CAABNLAIABJIAA//+uo+aAAFgkgIAABLuAgAEUfoCAA4DNAIAAdHiAgAADloCABkHiEA== Date: Fri, 29 Jul 2016 02:18:17 +0000 Message-ID: <5506bd9120c44493acb735085ead333a@XCH-ALN-014.cisco.com> References: <76CD132C3ADEF848BD84D028D243C92774EEF7CF@NKGEML515-MBX.china.huawei.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.24.69.18] Content-Type: multipart/alternative; boundary="_000_5506bd9120c44493acb735085ead333aXCHALN014ciscocom_" MIME-Version: 1.0 Archived-At: Cc: "Keyur Patel \(keyupate\)" , idr wg Subject: Re: [Idr] Fwd: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jul 2016 02:18:21 -0000 --_000_5506bd9120c44493acb735085ead333aXCHALN014ciscocom_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 SnVzdCByZWFkaW5nIHNvbWUgb2YgdGhpcy4NCkEgbGltaXRlZCByZWZyZXNoIGlzIE5PVCB0aGUg c2FtZSB0aGluZyBhcyAiQXBwbHkgdGhlIE9SRiB0aGVuIHJlbW92ZSBpdCIuDQpTdXBwb3NlIHlv dSB3YW50IHRvIHJlZnJlc2ggYSBzdWJzZXQgb2YgdGhlIHJvdXRlcy4NCllvdSBzZW5kIGFuIE9S RiB0byBwZXJtaXQgb25seSB0aGUgc3Vic2V0Lg0KWW91IHJlY2VpdmUgdGhlIHN1YnNldC4NCk5v dyB5b3UgcmVtb3ZlIHRoZSBPUkYuDQpZb3UgcmVjZWl2ZSB0aGUgd2hvbGUgdGFibGUuDQpOT1Qg d2hhdCB5b3Ugd2FudGVkLg0KDQpBbHNvLCB0aGUgdXNlIGNhc2UgaXMgZ29vZC4NClRoZSByZWNl aXZlciBkcm9wcGVkIHNvbWUgcm91dGVzIGR1ZSB0byBwb2xpY3kuDQpUaGUgcmVjZWl2ZXIgY2hh bmdlZCB0aGUgcG9saWN5Lg0KTm93IGl0IHdhbnRzIGEgcmVwZWF0IG9mIHRoZSBwcmV2aW91c2x5 IGRyb3BwZWQgcm91dGVzLg0KVGhpcyBpcyBub3QgYSB1c2UgY2FzZSBmb3IgT1JGIG9yIFJUQy4N ClRoZSB0aGluZyBpcyB0aGF0IE9SRiBvciBSVEMgd2VyZSBhbHJlYWR5IHBhc3NpbmcgdGhvc2Ug cm91dGVzLCBzbyBjaGFuZ2luZyB0aGVtIGlzIG5vbnNlbnNlLg0KDQpUaGFua3MsDQpKYWtvYi4N Cg0KDQo= --_000_5506bd9120c44493acb735085ead333aXCHALN014ciscocom_ Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: base64 PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6 U2ltU3VuOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtm b250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMgMiA0 O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Ikx1Y2lkYSBDb25zb2xlIjsNCglwYW5vc2Ut MToyIDExIDYgOSA0IDUgNCAyIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJcQFNp bVN1biI7DQoJcGFub3NlLTE6MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQovKiBTdHlsZSBEZWZpbml0 aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJn aW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZv bnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLHNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBl cmxpbmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOiMwNTYzQzE7DQoJdGV4dC1k ZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93 ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOiM5NTRGNzI7DQoJdGV4dC1kZWNv cmF0aW9uOnVuZGVybGluZTt9DQpzcGFuLkVtYWlsU3R5bGUxNw0KCXttc28tc3R5bGUtdHlwZTpw ZXJzb25hbC1yZXBseTsNCglmb250LWZhbWlseToiTHVjaWRhIENvbnNvbGUiOw0KCWNvbG9yOiM3 MDMwQTA7DQoJZm9udC13ZWlnaHQ6bm9ybWFsOw0KCWZvbnQtc3R5bGU6bm9ybWFsOw0KCXRleHQt ZGVjb3JhdGlvbjpub25lIG5vbmU7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6 ZXhwb3J0LW9ubHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0KQHBhZ2Ug V29yZFNlY3Rpb24xDQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAxLjBpbiAx LjBpbiAxLjBpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0t Pjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0 PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUg bXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4 dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4N CjwvaGVhZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5rPSIjMDU2M0MxIiB2bGluaz0iIzk1NEY3 MiI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw YW4gc3R5bGU9ImZvbnQtc2l6ZTo4LjBwdDtmb250LWZhbWlseTomcXVvdDtMdWNpZGEgQ29uc29s ZSZxdW90Oztjb2xvcjojNzAzMEEwIj5KdXN0IHJlYWRpbmcgc29tZSBvZiB0aGlzLjxvOnA+PC9v OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNp emU6OC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7THVjaWRhIENvbnNvbGUmcXVvdDs7Y29sb3I6Izcw MzBBMCI+QSBsaW1pdGVkIHJlZnJlc2ggaXMgTk9UIHRoZSBzYW1lIHRoaW5nIGFzICZxdW90O0Fw cGx5IHRoZSBPUkYgdGhlbiByZW1vdmUgaXQmcXVvdDsuPG86cD48L286cD48L3NwYW4+PC9wPg0K PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo4LjBwdDtmb250LWZh bWlseTomcXVvdDtMdWNpZGEgQ29uc29sZSZxdW90Oztjb2xvcjojNzAzMEEwIj5TdXBwb3NlIHlv dSB3YW50IHRvIHJlZnJlc2ggYSBzdWJzZXQgb2YgdGhlIHJvdXRlcy48bzpwPjwvbzpwPjwvc3Bh bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjguMHB0 O2ZvbnQtZmFtaWx5OiZxdW90O0x1Y2lkYSBDb25zb2xlJnF1b3Q7O2NvbG9yOiM3MDMwQTAiPllv dSBzZW5kIGFuIE9SRiB0byBwZXJtaXQgb25seSB0aGUgc3Vic2V0LjxvOnA+PC9vOnA+PC9zcGFu PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OC4wcHQ7 Zm9udC1mYW1pbHk6JnF1b3Q7THVjaWRhIENvbnNvbGUmcXVvdDs7Y29sb3I6IzcwMzBBMCI+WW91 IHJlY2VpdmUgdGhlIHN1YnNldC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjguMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0x1 Y2lkYSBDb25zb2xlJnF1b3Q7O2NvbG9yOiM3MDMwQTAiPk5vdyB5b3UgcmVtb3ZlIHRoZSBPUkYu PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9 ImZvbnQtc2l6ZTo4LjBwdDtmb250LWZhbWlseTomcXVvdDtMdWNpZGEgQ29uc29sZSZxdW90Oztj b2xvcjojNzAzMEEwIj5Zb3UgcmVjZWl2ZSB0aGUgd2hvbGUgdGFibGUuPG86cD48L286cD48L3Nw YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo4LjBw dDtmb250LWZhbWlseTomcXVvdDtMdWNpZGEgQ29uc29sZSZxdW90Oztjb2xvcjojNzAzMEEwIj5O T1Qgd2hhdCB5b3Ugd2FudGVkLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7THVj aWRhIENvbnNvbGUmcXVvdDs7Y29sb3I6IzcwMzBBMCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+ PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo4LjBwdDtm b250LWZhbWlseTomcXVvdDtMdWNpZGEgQ29uc29sZSZxdW90Oztjb2xvcjojNzAzMEEwIj5BbHNv LCB0aGUgdXNlIGNhc2UgaXMgZ29vZC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjguMHB0O2ZvbnQtZmFtaWx5OiZxdW90 O0x1Y2lkYSBDb25zb2xlJnF1b3Q7O2NvbG9yOiM3MDMwQTAiPlRoZSByZWNlaXZlciBkcm9wcGVk IHNvbWUgcm91dGVzIGR1ZSB0byBwb2xpY3kuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo4LjBwdDtmb250LWZhbWlseTom cXVvdDtMdWNpZGEgQ29uc29sZSZxdW90Oztjb2xvcjojNzAzMEEwIj5UaGUgcmVjZWl2ZXIgY2hh bmdlZCB0aGUgcG9saWN5LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt YWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7THVjaWRh IENvbnNvbGUmcXVvdDs7Y29sb3I6IzcwMzBBMCI+Tm93IGl0IHdhbnRzIGEgcmVwZWF0IG9mIHRo ZSBwcmV2aW91c2x5IGRyb3BwZWQgcm91dGVzLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OC4wcHQ7Zm9udC1mYW1pbHk6 JnF1b3Q7THVjaWRhIENvbnNvbGUmcXVvdDs7Y29sb3I6IzcwMzBBMCI+VGhpcyBpcyBub3QgYSB1 c2UgY2FzZSBmb3IgT1JGIG9yIFJUQy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjguMHB0O2ZvbnQtZmFtaWx5OiZxdW90 O0x1Y2lkYSBDb25zb2xlJnF1b3Q7O2NvbG9yOiM3MDMwQTAiPlRoZSB0aGluZyBpcyB0aGF0IE9S RiBvciBSVEMgd2VyZSBhbHJlYWR5IHBhc3NpbmcgdGhvc2Ugcm91dGVzLCBzbyBjaGFuZ2luZyB0 aGVtIGlzIG5vbnNlbnNlLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt YWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7THVjaWRh IENvbnNvbGUmcXVvdDs7Y29sb3I6IzcwMzBBMCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo4LjBwdDtmb250 LWZhbWlseTomcXVvdDtMdWNpZGEgQ29uc29sZSZxdW90Oztjb2xvcjojNzAzMEEwIj5UaGFua3Ms PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9 ImZvbnQtc2l6ZTo4LjBwdDtmb250LWZhbWlseTomcXVvdDtMdWNpZGEgQ29uc29sZSZxdW90Oztj b2xvcjojNzAzMEEwIj5KYWtvYi48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv Tm9ybWFsIj48YSBuYW1lPSJfTWFpbEVuZENvbXBvc2UiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6 OC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7THVjaWRhIENvbnNvbGUmcXVvdDs7Y29sb3I6IzcwMzBB MCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9hPjwvcD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpu b25lO2JvcmRlci1sZWZ0OnNvbGlkIGJsdWUgMS41cHQ7cGFkZGluZzowaW4gMGluIDBpbiA0LjBw dCI+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw YW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+ Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0K PC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg== --_000_5506bd9120c44493acb735085ead333aXCHALN014ciscocom_-- From nobody Fri Jul 29 00:45:46 2016 Return-Path: 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 3F3EE12D53B for ; Fri, 29 Jul 2016 00:45:45 -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 L2TpC9GaJ74m for ; Fri, 29 Jul 2016 00:45:43 -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 1241B12D504 for ; Fri, 29 Jul 2016 00:45:43 -0700 (PDT) Received: by mail-lf0-x22f.google.com with SMTP id f93so65577663lfi.2 for ; Fri, 29 Jul 2016 00:45:42 -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=19EPQXp/W9zDrJrKmhWEVJOQUjqyLVFcovsVmED0h+Y=; b=vTD0txmQtdpvdEM33KJ7xA/1z2+o0ffnKLYYuHodsKXH2QTV/YBASOCcljSq5GSZlI BjDOSzxXX+9A9VtJar0A7lDusPSLGD9Qh61InlzetvdbBBDwz4A6XkDCfAkkol+NMxPg xOpOr1X6ypK+16tSiY2EFTZC9TVRRQX7JDU+Kr8mQw/y2XfPHteRncQRY0M6fharWoI3 7jdu+2yzQj14qKOKsAvJV+gS8x0JQvh0aT4NNq5rssmf2APM9zsqtcyqcOT21E3P8LyG QEWiPqhvPXfbVCetpBYKuSYDvbshFGRvPfKBI5Ct5vQUcOglwMg2hgI9t9HlI/moXXMI 7hBA== 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=19EPQXp/W9zDrJrKmhWEVJOQUjqyLVFcovsVmED0h+Y=; b=gz6AaRe4+jkXcf53SNSSxJ+yI51NgooB+Y1wPuJV9rAVcEDQj0TOdkWnpu3X0WqJUX CTD76dNnhBKpihZnNDiKnhBzIGu85qWYGgwt4Ig+Lo9gg12nS0wteGHvjq5mjVHkTkNr aC+iZNZDqo90vzWHNhxQLQ3ZLSBPwIcy8YiC6fEZh+pmomeTWFJPJwb5HiUd79XSlUAZ 3CdoXPO9acGOb2lhhnFypVxEqTSrfPqpfZwGJqzPpuwsnJ8GgdC7FW4IoEHNWW5vcz3M b21z3aOcvGGaUvG1Cz2ngY3JIe0Yxl3CKYtqy6TsnFGURTpMSE0aChW0FzXCenqXDZCh v8cw== X-Gm-Message-State: AEkoouveHhAwecNcuFblOeIQu88p+3j8+60SKS79W3dwYfzO+moF187rU5bDq+hGgGedmPdvPemoGltZ8D6SXQ== X-Received: by 10.46.5.196 with SMTP id 187mr14302043ljf.13.1469778341178; Fri, 29 Jul 2016 00:45:41 -0700 (PDT) MIME-Version: 1.0 Sender: rraszuk@gmail.com Received: by 10.25.10.131 with HTTP; Fri, 29 Jul 2016 00:45:39 -0700 (PDT) In-Reply-To: <5506bd9120c44493acb735085ead333a@XCH-ALN-014.cisco.com> References: <76CD132C3ADEF848BD84D028D243C92774EEF7CF@NKGEML515-MBX.china.huawei.com> <5506bd9120c44493acb735085ead333a@XCH-ALN-014.cisco.com> From: Robert Raszuk Date: Fri, 29 Jul 2016 09:45:39 +0200 X-Google-Sender-Auth: hvJ3UpQc11LpaeJRcI9iM6PGT1E Message-ID: To: "Jakob Heitz (jheitz)" Content-Type: multipart/alternative; boundary=001a114a6beaecb3380538c16f87 Archived-At: Cc: "Keyur Patel \(keyupate\)" , idr wg Subject: Re: [Idr] Fwd: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jul 2016 07:45:45 -0000 --001a114a6beaecb3380538c16f87 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Jakob, See inline ... On Fri, Jul 29, 2016 at 4:18 AM, Jakob Heitz (jheitz) wrote: > Just reading some of this. > > A limited refresh is NOT the same thing as "Apply the ORF then remove it"= . > > Suppose you want to refresh a subset of the routes. > > You send an ORF to permit only the subset. > > You receive the subset. > > Now you remove the ORF. > > You receive the whole table. > > NOT what you wanted. > =E2=80=8BIf this is what your implementation does then I recommend you fix = it first. For Match =3D DENY =E2=80=8BREMOVE action should result in *only* advertise= ment of previously filtered entries. For Match =3D PERMIT REMOVE action should result in *only* the delta betwee= n whole table and remaining ORF entries. =E2=80=8BIn no case you get the whole table (other then removal of last ORF= PERMIT entry). =E2=80=8B > Also, the use case is good. > > The receiver dropped some routes due to policy. > > The receiver changed the policy. > > Now it wants a repeat of the previously dropped routes. > > This is not a use case for ORF or RTC. > > The thing is that ORF or RTC were already passing those routes, so > changing them is nonsense. > =E2=80=8BFor this case you use Enhanced Route Refresh. As result you get th= ose NLRIs which pass ORF or RTC the filters on a per AFI/SAFI basis. You have to be able to handle it anyway as when you boot you will get. If you pushed your prefix list with ORF then removing it will get you the delta. If you filtered based on import RT then advertising RT in ORF or RTC will get you the delta. So in what exact protocol cases you envision use case for this scoped one time refresh ? And what exactly in your opinion should be the list of parameters used to perform a query ? Best, R. --001a114a6beaecb3380538c16f87 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Jakob,

<= /div>
See inline ...=C2=A0

On Fri, Jul 29, 2016 at 4:18 AM, Jakob Hei= tz (jheitz) <jheitz@cisco.com> wrote:

Just reading some of this.

A limited refresh is NOT the same thing as= "Apply the ORF then remove it".

Suppose you want to refresh a subset of th= e routes.

You send an ORF to permit only the subset.=

You receive the subset.

Now you remove the ORF.

You receive the whole table.=

NOT what you wanted.



=E2=80= =8BIf this is what your implementation does then I recommend you fix it fir= st.=C2=A0

For Match = =3D DENY =E2=80=8BREMOVE action should result in *only* advertisement of pr= eviously filtered entries.=C2=A0

For Match =3D PERMIT REMOVE action should result in *only* the d= elta between whole table and remaining ORF entries.=C2=A0
<= br>
=E2=80=8BIn no case you get the whole tabl= e (other then removal of last ORF PERMIT entry). =E2=80=8B

<= div>
=C2=A0

=

Also, the use case is good.

The receiver dropped some routes due to po= licy.

The receiver changed the policy.=

Now it wants a repeat of the previously dr= opped routes.

This is not a use case for ORF or RTC.<= /u>

The thing is that ORF or RTC were already = passing those routes, so changing them is nonsense.

<= /blockquote>


=E2=80=8B= For this case you use Enhanced Route Refresh. As result you get those NLRIs= which pass ORF or RTC the filters on a per AFI/SAFI basis.=C2=A0

You have to be able to handle i= t anyway as when you boot you will get.

<= /div>
If you pushed your prefix list with ORF then removi= ng it will get you the delta.=C2=A0

If you filtered based on import RT then advertising RT in ORF= or RTC will get you the delta.=C2=A0

So in what exact protocol cases you envision use case for t= his scoped one time refresh ? And what exactly in your opinion should be th= e list of parameters used to perform a query ?=C2=A0


Best,
R.


=



--001a114a6beaecb3380538c16f87-- From nobody Fri Jul 29 03:14:11 2016 Return-Path: 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 18A4A12DB27 for ; Fri, 29 Jul 2016 03:14:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -15.807 X-Spam-Level: X-Spam-Status: No, score=-15.807 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 UHww3MdKrG_l for ; Fri, 29 Jul 2016 03:14:06 -0700 (PDT) Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB8E812DB68 for ; Fri, 29 Jul 2016 03:13:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11079; q=dns/txt; s=iport; t=1469787180; x=1470996780; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=1NKaYC3/Kl4tiyJPT1mVdicCElAS7KAHHgX9vJH4dDo=; b=VAZyAwdLF1tu4JApHxwvMT6j+edBnbR241RgyzSBsRkO4zK2z+fzWUDA 33uFMO2lgsdHSz4yI5eICwziAQJ5VJOg9lyV5qTK2iS5LTTC2/gWYxJY4 BY+Up9wF4l0BU/ThQCqpvs4ktxq4XW4M5k1MiERYoAzOi/fZwcHmaGyFi U=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CRAwAOK5tX/4YNJK1dgndOVny0AoUFg?= =?us-ascii?q?X0mhXcCgTE4FAEBAQEBAQFdJ4RdAQVnEhACAQg7BAcyFBECBA4FiDEOvBcBAQE?= =?us-ascii?q?BAQEBAQEBAQEBAQEBAQEBAQEXBYYqgXiCVYEignqDUIIvBZNwhUMBjn2PQIwxg?= =?us-ascii?q?3cBHjaCRYE1bgGGTYFEAQEB?= X-IronPort-AV: E=Sophos;i="5.28,438,1464652800"; d="scan'208,217";a="303170707" Received: from alln-core-12.cisco.com ([173.36.13.134]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 29 Jul 2016 10:12:59 +0000 Received: from XCH-RCD-019.cisco.com (xch-rcd-019.cisco.com [173.37.102.29]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id u6TACxgB015133 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 29 Jul 2016 10:12:59 GMT Received: from xch-aln-014.cisco.com (173.36.7.24) by XCH-RCD-019.cisco.com (173.37.102.29) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 29 Jul 2016 05:12:59 -0500 Received: from xch-aln-014.cisco.com ([173.36.7.24]) by XCH-ALN-014.cisco.com ([173.36.7.24]) with mapi id 15.00.1210.000; Fri, 29 Jul 2016 05:12:59 -0500 From: "Jakob Heitz (jheitz)" To: Robert Raszuk Thread-Topic: [Idr] Fwd: Slot request in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00.txt Thread-Index: AQHR4aVazIYBPV/cR0uGH7jm8G+9GqAgntcAgAABUACAAAdOAIAAAyuAgAF604CAABNLAIABJIAA//+uo+aAAFgkgIAABLuAgAEUfoCAA4DNAIAAdHiAgAADloCABkHiEIAAsvKA///VWEw= Date: Fri, 29 Jul 2016 10:12:59 +0000 Message-ID: References: <76CD132C3ADEF848BD84D028D243C92774EEF7CF@NKGEML515-MBX.china.huawei.com> <5506bd9120c44493acb735085ead333a@XCH-ALN-014.cisco.com>, In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted Content-Type: multipart/alternative; boundary="_000_F8A1EED64A40408A99EF46E7F0984B49ciscocom_" MIME-Version: 1.0 Archived-At: Cc: "Keyur Patel \(keyupate\)" , idr wg Subject: Re: [Idr] Fwd: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jul 2016 10:14:09 -0000 --_000_F8A1EED64A40408A99EF46E7F0984B49ciscocom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Wrong. RFC 5291 says: The speaker MUST re-advertise all the routes that have been affected by the ORF entries carried in the message, but MAY also re- advertise the routes that have not been affected by the ORF entries carried in the message. Thanks, Jakob. On Jul 29, 2016, at 12:45 AM, Robert Raszuk > wrote: Hi Jakob, See inline ... On Fri, Jul 29, 2016 at 4:18 AM, Jakob Heitz (jheitz) > wrote: Just reading some of this. A limited refresh is NOT the same thing as "Apply the ORF then remove it". Suppose you want to refresh a subset of the routes. You send an ORF to permit only the subset. You receive the subset. Now you remove the ORF. You receive the whole table. NOT what you wanted. ?If this is what your implementation does then I recommend you fix it first= . For Match =3D DENY ?REMOVE action should result in *only* advertisement of = previously filtered entries. For Match =3D PERMIT REMOVE action should result in *only* the delta betwee= n whole table and remaining ORF entries. ?In no case you get the whole table (other then removal of last ORF PERMIT = entry). ? Also, the use case is good. The receiver dropped some routes due to policy. The receiver changed the policy. Now it wants a repeat of the previously dropped routes. This is not a use case for ORF or RTC. The thing is that ORF or RTC were already passing those routes, so changing= them is nonsense. ?For this case you use Enhanced Route Refresh. As result you get those NLRI= s which pass ORF or RTC the filters on a per AFI/SAFI basis. You have to be able to handle it anyway as when you boot you will get. If you pushed your prefix list with ORF then removing it will get you the d= elta. If you filtered based on import RT then advertising RT in ORF or RTC will g= et you the delta. So in what exact protocol cases you envision use case for this scoped one t= ime refresh ? And what exactly in your opinion should be the list of parame= ters used to perform a query ? Best, R. --_000_F8A1EED64A40408A99EF46E7F0984B49ciscocom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Wrong. RFC 5291 says:
The spe=
aker MUST re-advertise all the routes that have been
   affected by the ORF entries carried in the message, but MAY also re-
   advertise the routes that have not been affected by the ORF entries
   carried in the message.

Thanks,
Jakob.


On Jul 29, 2016, at 12:45 AM, Robert Raszuk <robert@raszuk.net> wrote:

Hi Jakob,

See inline ... 

On Fri, Jul 29, 2016 at 4:18 AM, Jakob Heitz (jh= eitz) <jheitz@cisco.com<= /a>> wrote:

Just reading some of this.

A limited refresh is NOT the same thing as= "Apply the ORF then remove it".

Suppose you want to refresh a subset of th= e routes.

You send an ORF to permit only the subset.=

You receive the subset.

Now you remove the ORF.

You receive the whole table.=

NOT what you wanted.



​If this is what your implementation does then I recommend you fix it= first. 

For Match =3D DENY ​REMOVE action should result in *only* advertiseme= nt of previously filtered entries. 

For Match =3D PERMIT REMOVE action should result in *only* the delta betwee= n whole table and remaining ORF entries. 

​In no case you get the whole table (other then removal of last ORF P= ERMIT entry). ​


 

Also, the use case is good.

The receiver dropped some routes due to po= licy.

The receiver changed the policy.=

Now it wants a repeat of the previously dr= opped routes.

This is not a use case for ORF or RTC.<= /u>

The thing is that ORF or RTC were already = passing those routes, so changing them is nonsense.



​For this case you use Enhanced Route Refresh. As result you get thos= e NLRIs which pass ORF or RTC the filters on a per AFI/SAFI basis. 

You have to be able to handle it anyway as when you boot you will get.

If you pushed your prefix list with ORF then removing it will get you the d= elta. 

If you filtered based on import RT then advertising RT in ORF or RTC will g= et you the delta. 

So in what exact protocol cases you envision use case for this scoped one t= ime refresh ? And what exactly in your opinion should be the list of parame= ters used to perform a query ? 


Best,
R.





--_000_F8A1EED64A40408A99EF46E7F0984B49ciscocom_-- From nobody Fri Jul 29 03:37:33 2016 Return-Path: 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 AA5B912DC45 for ; Fri, 29 Jul 2016 03:37:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -15.807 X-Spam-Level: X-Spam-Status: No, score=-15.807 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 fnrnyTPKnKXe for ; Fri, 29 Jul 2016 03:37:28 -0700 (PDT) Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC9EB12DC3D for ; Fri, 29 Jul 2016 03:37:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12302; q=dns/txt; s=iport; t=1469788647; x=1470998247; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=xkRZM9FEC9z6Fq/1R3+jd6JslGEvzOJNW5y8/RFpGpA=; b=VUwOJYofEp/ujCAQZPV+y5Jx2W/YyhOS0ZW+9niexFZn6jVcxQFCAzLv hApKLXrlh1QYpmMW3aGycHOzc/Di8rDr4PmfkenJkPEj2fw6eLjSHejJ5 Hae/Fn+CXuQWEhXR7wGr4jRChuY5Hemac8Rb7p/tIXSx7PEh+JhPi2k9Q 4=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CRAwDzMJtX/4ENJK1dgndOVny0AoUFg?= =?us-ascii?q?X0mhXcCgTE4FAEBAQEBAQFdJ4RdAQVnEhACAQg7BAcyFBECBA4FiDEOvAQBAQE?= =?us-ascii?q?BAQEBAQEBAQEBAQEBAQEBAQEXBYYqgXgIgk2BIoJ6g1CCLwWTcIVDAY59j0CMM?= =?us-ascii?q?YN3AR42gkWBNW4Bhk2BRAEBAQ?= X-IronPort-AV: E=Sophos;i="5.28,438,1464652800"; d="scan'208,217";a="129638184" Received: from alln-core-9.cisco.com ([173.36.13.129]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 29 Jul 2016 10:37:26 +0000 Received: from XCH-ALN-018.cisco.com (xch-aln-018.cisco.com [173.36.7.28]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id u6TAbQXj014838 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 29 Jul 2016 10:37:26 GMT Received: from xch-aln-014.cisco.com (173.36.7.24) by XCH-ALN-018.cisco.com (173.36.7.28) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 29 Jul 2016 05:37:26 -0500 Received: from xch-aln-014.cisco.com ([173.36.7.24]) by XCH-ALN-014.cisco.com ([173.36.7.24]) with mapi id 15.00.1210.000; Fri, 29 Jul 2016 05:37:26 -0500 From: "Jakob Heitz (jheitz)" To: Robert Raszuk Thread-Topic: [Idr] Fwd: Slot request in IDR to present https://www.ietf.org/internet-drafts/draft-idr-bgp-route-refresh-options-00.txt Thread-Index: AQHR4aVazIYBPV/cR0uGH7jm8G+9GqAgntcAgAABUACAAAdOAIAAAyuAgAF604CAABNLAIABJIAA//+uo+aAAFgkgIAABLuAgAEUfoCAA4DNAIAAdHiAgAADloCABkHiEIAAsvKA///VWEyAAAbVgQ== Date: Fri, 29 Jul 2016 10:37:25 +0000 Message-ID: <0598FA6B-280B-4448-8A95-2AD85C562DF4@cisco.com> References: <76CD132C3ADEF848BD84D028D243C92774EEF7CF@NKGEML515-MBX.china.huawei.com> <5506bd9120c44493acb735085ead333a@XCH-ALN-014.cisco.com>, , In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted Content-Type: multipart/alternative; boundary="_000_0598FA6B280B44488A952AD85C562DF4ciscocom_" MIME-Version: 1.0 Archived-At: Cc: "Keyur Patel \(keyupate\)" , idr wg Subject: Re: [Idr] Fwd: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jul 2016 10:37:32 -0000 --_000_0598FA6B280B44488A952AD85C562DF4ciscocom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable And to clarify, that means all routes permitted after the ORF message is pr= ocessed MUST be re-advertised. It doesn't matter whether the action was add= or remove. Also, when you remove the last permit, you get nothing. It's like after ses= sion establishment: if the ORF capability was negotiated, nothing is sent u= ntil the first permit is received. Thanks, Jakob. On Jul 29, 2016, at 3:12 AM, Jakob Heitz (jheitz) > wrote: Wrong. RFC 5291 says: The speaker MUST re-advertise all the routes that have been affected by the ORF entries carried in the message, but MAY also re- advertise the routes that have not been affected by the ORF entries carried in the message. Thanks, Jakob. On Jul 29, 2016, at 12:45 AM, Robert Raszuk > wrote: Hi Jakob, See inline ... On Fri, Jul 29, 2016 at 4:18 AM, Jakob Heitz (jheitz) > wrote: Just reading some of this. A limited refresh is NOT the same thing as "Apply the ORF then remove it". Suppose you want to refresh a subset of the routes. You send an ORF to permit only the subset. You receive the subset. Now you remove the ORF. You receive the whole table. NOT what you wanted. ?If this is what your implementation does then I recommend you fix it first= . For Match =3D DENY ?REMOVE action should result in *only* advertisement of = previously filtered entries. For Match =3D PERMIT REMOVE action should result in *only* the delta betwee= n whole table and remaining ORF entries. ?In no case you get the whole table (other then removal of last ORF PERMIT = entry). ? Also, the use case is good. The receiver dropped some routes due to policy. The receiver changed the policy. Now it wants a repeat of the previously dropped routes. This is not a use case for ORF or RTC. The thing is that ORF or RTC were already passing those routes, so changing= them is nonsense. ?For this case you use Enhanced Route Refresh. As result you get those NLRI= s which pass ORF or RTC the filters on a per AFI/SAFI basis. You have to be able to handle it anyway as when you boot you will get. If you pushed your prefix list with ORF then removing it will get you the d= elta. If you filtered based on import RT then advertising RT in ORF or RTC will g= et you the delta. So in what exact protocol cases you envision use case for this scoped one t= ime refresh ? And what exactly in your opinion should be the list of parame= ters used to perform a query ? Best, R. --_000_0598FA6B280B44488A952AD85C562DF4ciscocom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
And to clarify, that means all routes permitted after the ORF message = is processed MUST be re-advertised. It doesn't matter whether the action wa= s add or remove.

Also, when you remove the last permit, you g= et nothing. It's like after session establishment: if the ORF capability wa= s negotiated, nothing is sent until the first permit is received.

Thanks,
Jakob.

Wrong. RFC 5291 says:
The spe=
aker MUST re-advertise all the routes that have been
   affected by the ORF entries carried in the message, but MAY also re-
   advertise the routes that have not been affected by the ORF entries
   carried in the message.

Thanks,
Jakob.


On Jul 29, 2016, at 12:45 AM, Robert Raszuk <robert@raszuk.net> wrote:

Hi Jakob,

See inline ... 

On Fri, Jul 29, 2016 at 4:18 AM, Jakob Heitz (jh= eitz) <jheitz@cisco.com<= /a>> wrote:

Just reading some of this.

A limited refresh is NOT the same thing as= "Apply the ORF then remove it".

Suppose you want to refresh a subset of th= e routes.

You send an ORF to permit only the subset.=

You receive the subset.

Now you remove the ORF.

You receive the whole table.=

NOT what you wanted.



​If this is what your implementation does then I recommend you fix it= first. 

For Match =3D DENY ​REMOVE action should result in *only* advertiseme= nt of previously filtered entries. 

For Match =3D PERMIT REMOVE action should result in *only* the delta betwee= n whole table and remaining ORF entries. 

​In no case you get the whole table (other then removal of last ORF P= ERMIT entry). ​


 

Also, the use case is good.

The receiver dropped some routes due to po= licy.

The receiver changed the policy.=

Now it wants a repeat of the previously dr= opped routes.

This is not a use case for ORF or RTC.<= /u>

The thing is that ORF or RTC were already = passing those routes, so changing them is nonsense.



​For this case you use Enhanced Route Refresh. As result you get thos= e NLRIs which pass ORF or RTC the filters on a per AFI/SAFI basis. 

You have to be able to handle it anyway as when you boot you will get.

If you pushed your prefix list with ORF then removing it will get you the d= elta. 

If you filtered based on import RT then advertising RT in ORF or RTC will g= et you the delta. 

So in what exact protocol cases you envision use case for this scoped one t= ime refresh ? And what exactly in your opinion should be the list of parame= ters used to perform a query ? 


Best,
R.





--_000_0598FA6B280B44488A952AD85C562DF4ciscocom_-- From nobody Fri Jul 29 04:30:50 2016 Return-Path: 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 45E4112DDAA for ; Fri, 29 Jul 2016 04:30:48 -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 XVK1djHX8-4N for ; Fri, 29 Jul 2016 04:30:46 -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 95B1412DDA8 for ; Fri, 29 Jul 2016 04:30:45 -0700 (PDT) Received: by mail-lf0-x22f.google.com with SMTP id f93so69271475lfi.2 for ; Fri, 29 Jul 2016 04:30:45 -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=MpvPLySiOHqrn2+PAo12K6tNeshfwpyp5RiS61UFqTE=; b=zBeuQ9/rHOPbJBGReL1yuBXFTpJkTHN359eE59+7Pj9MjUNjMEXkCKa2ss/RFwsXhg 6ouP0Meq8MM7hguSK6uRJ3iGGJivBBCMelocjPpjo5Fn9S8+5EVeD+yT09zD317BBQrv gyGJLwPUHuqilDq2NyTnbjtjgpWyBwuvlxh3HYRy6WdUQYo1Ao2iXg2wVws7p4+KqVtl 7FRoiTTJ/2cFsbKKOzYJQYiCdouXR4zVTTdgoKTqHbp+B/l6rtd1k4K/C+fjii7UgmI6 b0mWpZrydm6Zs50gVz/wRi0cmv9wecM8byc+MwK9u/cIoSjF3o4iO5Uc3TN3iExvg3xz IyiA== 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=MpvPLySiOHqrn2+PAo12K6tNeshfwpyp5RiS61UFqTE=; b=D7sDj+WVmFclCAhv9UQGmOS638Ckkqf3f20euo6pzF8+SClMB/PKrEqV8LE6hb65ti sv/OLFufqkCUm+TCxU+FF6bTk0WoUdIRUxEi2gj7g7rzssjzM7DMsVFvce75IkuHBWvH 3I1wcOJfpYGIHmMD9DNW/gsE7dMorOHvkErgPPsD0AIa565kxp6VcWRSLAgb+zKBgJYq iKYpSjCL8/VUOGH9Po+I3GzQ2sco/ic2TZx071McN1a5Lo6hXXKtc9tQzN6orxOQiovy uFSygLSR1o9NwwMDbEnd9V2kdWWKPAFgNRA7YqTz9VMrZWok2ylN+Ys9QeOYYJTeYhIp HXAw== X-Gm-Message-State: AEkoouu7uMDOPGTtkpQZc6URyBdIcNs2MHdCwQiguPjEzfpx9qjd1KByWhjPne1l3IY8K8hIaI1koB0OgUajOA== X-Received: by 10.25.26.194 with SMTP id a185mr15593566lfa.167.1469791843666; Fri, 29 Jul 2016 04:30:43 -0700 (PDT) MIME-Version: 1.0 Sender: rraszuk@gmail.com Received: by 10.25.10.131 with HTTP; Fri, 29 Jul 2016 04:30:42 -0700 (PDT) In-Reply-To: References: <76CD132C3ADEF848BD84D028D243C92774EEF7CF@NKGEML515-MBX.china.huawei.com> <5506bd9120c44493acb735085ead333a@XCH-ALN-014.cisco.com> From: Robert Raszuk Date: Fri, 29 Jul 2016 13:30:42 +0200 X-Google-Sender-Auth: A5cSWo54uCXrEJ8vYfsbbjdFBJU Message-ID: To: "Jakob Heitz (jheitz)" Content-Type: multipart/alternative; boundary=001a11403bd8bc62970538c494cc Archived-At: Cc: "Keyur Patel \(keyupate\)" , idr wg Subject: Re: [Idr] Fwd: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jul 2016 11:30:48 -0000 --001a11403bd8bc62970538c494cc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Jakob, I did not make any judgement who is right and who is wrong. You did so let me explain where you are missing it. #1 - As someone wisely said at the last IETF MAY =3D MAY NOT hence if spec contains MAY it equally well could be interpreted in the opposite way. Enough to say this is not a base to make any right or wrong judgement. #2 - This entire thread as well as this draft in question is all about optimization. I must repeat that there is no problem in the first place so receiving all routes in a given SAFI modulo ORF or RTC filter is just fine. During policy change you issue Enhanced Route Refresh. However If this is not fine then I recommend to fix those inefficient implementations which are generating excess of messages in the BGP UPDATE rather then putting another layer of questionable band-aid on top of it. Thx, R. On Fri, Jul 29, 2016 at 12:12 PM, Jakob Heitz (jheitz) wrote: > Wrong. RFC 5291 says: > > The speaker MUST re-advertise all the routes that have been > affected by the ORF entries carried in the message, but MAY also re- > advertise the routes that have not been affected by the ORF entries > carried in the message. > > > Thanks, > Jakob. > > > On Jul 29, 2016, at 12:45 AM, Robert Raszuk wrote: > > Hi Jakob, > > See inline ... > > On Fri, Jul 29, 2016 at 4:18 AM, Jakob Heitz (jheitz) > wrote: > >> Just reading some of this. >> >> A limited refresh is NOT the same thing as "Apply the ORF then remove it= ". >> >> Suppose you want to refresh a subset of the routes. >> >> You send an ORF to permit only the subset. >> >> You receive the subset. >> >> Now you remove the ORF. >> >> You receive the whole table. >> >> NOT what you wanted. >> > > > =E2=80=8BIf this is what your implementation does then I recommend you fi= x it > first. > > For Match =3D DENY =E2=80=8BREMOVE action should result in *only* adverti= sement of > previously filtered entries. > > For Match =3D PERMIT REMOVE action should result in *only* the delta betw= een > whole table and remaining ORF entries. > > =E2=80=8BIn no case you get the whole table (other then removal of last O= RF PERMIT > entry). =E2=80=8B > > > > >> Also, the use case is good. >> >> The receiver dropped some routes due to policy. >> >> The receiver changed the policy. >> >> Now it wants a repeat of the previously dropped routes. >> >> This is not a use case for ORF or RTC. >> >> The thing is that ORF or RTC were already passing those routes, so >> changing them is nonsense. >> > > > =E2=80=8BFor this case you use Enhanced Route Refresh. As result you get = those > NLRIs which pass ORF or RTC the filters on a per AFI/SAFI basis. > > You have to be able to handle it anyway as when you boot you will get. > > If you pushed your prefix list with ORF then removing it will get you the > delta. > > If you filtered based on import RT then advertising RT in ORF or RTC will > get you the delta. > > So in what exact protocol cases you envision use case for this scoped one > time refresh ? And what exactly in your opinion should be the list of > parameters used to perform a query ? > > > Best, > R. > > > > > > --001a11403bd8bc62970538c494cc Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Jakob,

I did not make any judgement who is right and who is w= rong. You did so let me explain where you are missing it.=C2=A0

#1 - As someone wisely said at th= e last IETF MAY =3D MAY NOT hence if spec contains MAY it equally well coul= d be interpreted in the opposite way. Enough to say this is not a base to m= ake any right or wrong judgement.=C2=A0

<= div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif= ;font-size:small">#2 - This entire thread as well as this draft in question= is all about optimization. I must repeat that there is no problem in the f= irst place so receiving all routes in a given SAFI modulo ORF or RTC filter= is just fine. During policy change you issue Enhanced Route Refresh.
=

However If this is not fine= then I recommend to fix those inefficient implementations which are genera= ting excess of messages in the BGP UPDATE rather then putting another layer= of questionable band-aid on top of it.=C2=A0

<= /div>
Thx,
R.

On Fri, Jul 29, 2016 at 1= 2:12 PM, Jakob Heitz (jheitz) <jheitz@cisco.com> wrote:
Wrong. RFC 5291 says:
The speaker MUST re-advertise all the routes that have been
   affected by the ORF entries carried in the message, but MAY also re-
   advertise the routes that have not been affected by the ORF entries
   carried in the message.

Thanks,
Jakob.


On Jul 29, 2016, at 12:45 AM, Robert Raszuk <robert@raszuk.net> wrote:

Hi Jakob,

See inline ...=C2=A0

On Fri, Jul 29, 2016 at 4:18 AM, Jakob Heitz (jh= eitz) <jheitz@cisco.com<= /a>> wrote:

Just reading some of this.

A limited refresh is NOT the same thing as= "Apply the ORF then remove it".

Suppose you want to refresh a subset of th= e routes.

You send an ORF to permit only the subset.=

You receive the subset.

Now you remove the ORF.

You receive the whole table.=

NOT what you wanted.



=E2=80=8BIf this is what your implementation does then I recommend you fix = it first.=C2=A0

For Match =3D DENY =E2=80=8BREMOVE action should result in *only* advertise= ment of previously filtered entries.=C2=A0

For Match =3D PERMIT REMOVE action should result in *only* the delta betwee= n whole table and remaining ORF entries.=C2=A0

=E2=80=8BIn no case you get the whole table (other then removal of last ORF= PERMIT entry). =E2=80=8B


=C2=A0

Also, the use case is good.

The receiver dropped some routes due to po= licy.

The receiver changed the policy.=

Now it wants a repeat of the previously dr= opped routes.

This is not a use case for ORF or RTC.<= /u>

The thing is that ORF or RTC were already = passing those routes, so changing them is nonsense.



=E2=80=8BFor this case you use Enhanced Route Refresh. As result you get th= ose NLRIs which pass ORF or RTC the filters on a per AFI/SAFI basis.=C2=A0<= /div>

You have to be able to handle it anyway as when you boot you will get.

If you pushed your prefix list with ORF then removing it will get you the d= elta.=C2=A0

If you filtered based on import RT then advertising RT in ORF or RTC will g= et you the delta.=C2=A0

So in what exact protocol cases you envision use case for this scoped one t= ime refresh ? And what exactly in your opinion should be the list of parame= ters used to perform a query ?=C2=A0


Best,
R.






--001a11403bd8bc62970538c494cc-- From nobody Sun Jul 31 10:58:05 2016 Return-Path: X-Original-To: idr@ietf.org Delivered-To: idr@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AF5012D587; Sun, 31 Jul 2016 10:58:03 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Secretariat To: , , , X-Test-IDTracker: no X-IETF-IDTracker: 6.29.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20160731175803.7926.55155.idtracker@ietfa.amsl.com> Date: Sun, 31 Jul 2016 10:58:03 -0700 Archived-At: Subject: [Idr] The IDR WG has placed draft-gredler-idr-bgp-ls-segment-routing-ext in state "Candidate for WG Adoption" X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.17 List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Jul 2016 17:58:03 -0000 The IDR WG has placed draft-gredler-idr-bgp-ls-segment-routing-ext in state Candidate for WG Adoption (entered by Susan Hares) The document is available at https://datatracker.ietf.org/doc/draft-gredler-idr-bgp-ls-segment-routing-ext/ From nobody Sun Jul 31 23:21:06 2016 Return-Path: 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 D5B9912D501 for ; Sun, 31 Jul 2016 23:21:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.895 X-Spam-Level: X-Spam-Status: No, score=-2.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=yahoo.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 Ff2mD2lPjOtg for ; Sun, 31 Jul 2016 23:21:03 -0700 (PDT) Received: from nm26-vm0.bullet.mail.bf1.yahoo.com (nm26-vm0.bullet.mail.bf1.yahoo.com [98.139.213.74]) (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 9D05512D12D for ; Sun, 31 Jul 2016 23:21:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1470032462; bh=5c4qlc6oc3JK/xhjOIbiuvroy8RrVqfGQPVpdZqSe0Y=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=GJ7U7y1OT5aC1A7utZsekKrkOzynSnSZmgY7YMF9mC/oQdSgFHA1cgXPS3wCR6WLJpQg5091VyrTIVr+z9jkgyxoP0XM+qR6THYuIghxgAPNiM/Ct987ozcFtBO9GpbI1U/yjUGJWU3kaLdlT6uX8o6FUENJYUvYrSzaf7OCW6XwEimEA0ruOwWrYQ9WZC/tzoe3F0euD2/kB7KL+1cMc73ut82jAnodzEyN2eiDHQ5iWLePE4pqQJr/+GNxGUwzwTvoSSXFvKjM/ZewOI/biTB9mXgoBtQ+LahGxo/zcRN7F70m8hOnkVGvbWMfoLehnDmLuDWvtZ8RuA6WI2C0Gg== Received: from [66.196.81.171] by nm26.bullet.mail.bf1.yahoo.com with NNFMP; 01 Aug 2016 06:21:02 -0000 Received: from [98.139.215.254] by tm17.bullet.mail.bf1.yahoo.com with NNFMP; 01 Aug 2016 06:21:02 -0000 Received: from [127.0.0.1] by omp1067.mail.bf1.yahoo.com with NNFMP; 01 Aug 2016 06:21:02 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 683403.87746.bm@omp1067.mail.bf1.yahoo.com X-YMail-OSG: 4AcasDwVM1mpyJflBB4VJ6us91I.ZvN7ve3MwGrgCLjc1K3o0xYKSbjtEoxQVfI y1od5.bBbtUu5FnJlX0eN_.wY3FB0kHdxlNBpAUKXVy6vrheMRRxpXVoIKH88Pp3xr1878O60wP8 U02bbINDABxiYkhQn4j8ZtQlMsQEYR_C7IkGA9WwxoNp3v58Ycjc8gaEwrW13ZwoDqOpdhHZKCvo MJ8278gPpLkEFY5UwyNI74j0dfHzydPxJMJtzLj7r.bvQFSFvsQjnvfbdF5vE3uLzVeAJ147gPDv IVuqX3GjFXq9YBnTY2y.6D3fWQbjfJsMqckz6x_4l6_ON4s.CezjRif0D8Obd_n1Zt2yJ30mNOgM 1DTxua1cHkIlKxVaIgNdky1JziP2juJuDi2.cecn8oDZhqRr.kyuFTXDnIOWIFl5HB7KFDs1DDOd M8JoEk55vUxvOILcBsrnlwPzO2BzYmiLpQtd2Rp6L7H6qlaWelb3J0N_d3yngUw2wRQBZAyqJXIz RgOxyLSWP_8mCXTws0xWQDvbXitv6ZsHZO4dLAQ-- Received: from jws10601.mail.bf1.yahoo.com by sendmailws138.mail.bf1.yahoo.com; Mon, 01 Aug 2016 06:21:02 +0000; 1470032462.293 Date: Mon, 1 Aug 2016 06:19:56 +0000 (UTC) From: Niloofar Fazlollahi To: Robert Raszuk , "Jakob Heitz (jheitz)" Message-ID: <2138159007.9153002.1470032396712.JavaMail.yahoo@mail.yahoo.com> In-Reply-To: References: <76CD132C3ADEF848BD84D028D243C92774EEF7CF@NKGEML515-MBX.china.huawei.com> <5506bd9120c44493acb735085ead333a@XCH-ALN-014.cisco.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_9153001_392289852.1470032396698" Archived-At: Cc: "Keyur Patel \(keyupate\)" , idr wg Subject: Re: [Idr] Fwd: 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 Reply-To: Niloofar Fazlollahi List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Aug 2016 06:21:06 -0000 ------=_Part_9153001_392289852.1470032396698 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Robert,In response to your comment:"If you pushed your prefix list with = ORF then removing it will get you the delta.=C2=A0 If you filtered based on import RT then advertising RT in ORF or RTC will g= et you the delta.=C2=A0 So in what exact protocol cases you envision use case for this scoped one t= ime refresh ? And what exactly in your opinion should be the list of parame= ters used to perform a query ? " There is also the case that policy is enforced locally, nor ORF and neither= RTC, e.g., route-map in with deny prefix-list. Once the policy is removed, with cap 74, speaker can request refresh of onl= y the previously denied prefixes.How to implement this optimization with OR= F?=C2=A0 Based on your previous email:"For Match =3D PERMIT REMOVE action should res= ult in *only* the delta between whole table and remaining ORF entries. " If we send a PERMIT ADD for those prefixes and then PERMIT REMOVE, we will = be refreshed with the whole AFI/SAFI assuming no other ORF is added previou= sly. Regards,Niloofar =20 On Friday, July 29, 2016 4:30 AM, Robert Raszuk wro= te: =20 Jakob, I did not make any judgement who is right and who is wrong. You did so let = me explain where you are missing it.=C2=A0 #1 - As someone wisely said at the last IETF MAY =3D MAY NOT hence if spec = contains MAY it equally well could be interpreted in the opposite way. Enou= gh to say this is not a base to make any right or wrong judgement.=C2=A0 #2 - This entire thread as well as this draft in question is all about opti= mization. I must repeat that there is no problem in the first place so rece= iving all routes in a given SAFI modulo ORF or RTC filter is just fine. Dur= ing policy change you issue Enhanced Route Refresh. However If this is not fine then I recommend to fix those inefficient imple= mentations which are generating excess of messages in the BGP UPDATE rather= then putting another layer of questionable band-aid on top of it.=C2=A0 Thx,R. On Fri, Jul 29, 2016 at 12:12 PM, Jakob Heitz (jheitz) w= rote: Wrong. RFC 5291 says:The speaker MUST re-advertise all the routes that have= been affected by the ORF entries carried in the message, but MAY also re- advertise the routes that have not been affected by the ORF entries carried in the message. Thanks, Jakob. On Jul 29, 2016, at 12:45 AM, Robert Raszuk wrote: Hi Jakob, See inline ...=C2=A0 On Fri, Jul 29, 2016 at 4:18 AM, Jakob Heitz (jheitz) wr= ote: Just reading some of this.A limited refresh is NOT the same thing as "Apply= the ORF then remove it".Suppose you want to refresh a subset of the routes= .You send an ORF to permit only the subset.You receive the subset.Now you r= emove the ORF.You receive the whole table.NOT what you wanted. =E2=80=8BIf this is what your implementation does then I recommend you fix = it first.=C2=A0 For Match =3D DENY =E2=80=8BREMOVE action should result in *only* advertise= ment of previously filtered entries.=C2=A0 For Match =3D PERMIT REMOVE action should result in *only* the delta betwee= n whole table and remaining ORF entries.=C2=A0 =E2=80=8BIn no case you get the whole table (other then removal of last ORF= PERMIT entry). =E2=80=8B =C2=A0 Also, the use case is good. The receiver dropped some routes due to policy.The receiver changed the pol= icy.Now it wants a repeat of the previously dropped routes.This is not a us= e case for ORF or RTC.The thing is that ORF or RTC were already passing tho= se routes, so changing them is nonsense. =E2=80=8BFor this case you use Enhanced Route Refresh. As result you get th= ose NLRIs which pass ORF or RTC the filters on a per AFI/SAFI basis.=C2=A0 You have to be able to handle it anyway as when you boot you will get. If you pushed your prefix list with ORF then removing it will get you the d= elta.=C2=A0 If you filtered based on import RT then advertising RT in ORF or RTC will g= et you the delta.=C2=A0 So in what exact protocol cases you envision use case for this scoped one t= ime refresh ? And what exactly in your opinion should be the list of parame= ters used to perform a query ?=C2=A0 Best,R. _______________________________________________ Idr mailing list Idr@ietf.org https://www.ietf.org/mailman/listinfo/idr ------=_Part_9153001_392289852.1470032396698 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable ------=_Part_9153001_392289852.1470032396698--
Hi Robert,
In response to your comment:
"If you pushed your prefix list with ORF then r= emoving it will get you the delta. 

If you filtered based on import RT then advertising RT in ORF or RTC will= get you the delta. 

So in what exact protocol cases you envision use case for this scope= d one time refresh ? And what exactly in your opinion should be the list of= parameters used to perform a query ? "

There is also the case that poli= cy is enforced locally, nor ORF and neither RTC, e.g., route-map in with de= ny prefix-list.
Once the policy is removed, with cap 74= , speaker can request refresh of only the previously denied prefixes.
How to implement this optimization with ORF? 
<= div style=3D"font-family: arial, helvetica, sans-serif; font-size: small;" = dir=3D"ltr" id=3D"yui_3_16_0_ym19_1_1469982898423_37523">Based on your previou= s email:
"For Match =3D PERMIT REMOVE action should = result in *only* the delta between whole table and remaining ORF entries. "=

If we send a PERMIT ADD= for those prefixes and then PERMIT REMOVE, we will be refreshed with the w= hole AFI/SAFI assuming no other ORF is added previously.
Regards,
Niloofar

=


On Friday, July 29, 2016 4:30 AM, Robert Raszuk <rober= t@raszuk.net> wrote:


Jakob,

I did not make any judgement who is right and wh= o is wrong. You did so let me explain where you are missing it. 
=

#1 - As someone wisely said at the last IETF MAY =3D MAY NOT hence if = spec contains MAY it equally well could be interpreted in the opposite way.= Enough to say this is not a base to make any right or wrong judgement.&nbs= p;

#2 - This entire thread as well as this draft in question is a= ll about optimization. I must repeat that there is no problem in the first = place so receiving all routes in a given SAFI modulo ORF or RTC filter is j= ust fine. During policy change you issue Enhanced Route Refresh.

= However If this is not fine then I recommend to fix those inefficient imple= mentations which are generating excess of messages in the BGP UPDATE rather= then putting another layer of questionable band-aid on top of it. 

Thx,
R.

On Fri, Jul 29, 2016 at 12:12 PM, Jakob Heitz (jheitz) &= lt;jheitz@cisco.com> wrote:
Wrong. RFC 5291 says:
The speaker MUST re-adve=
rtise all the routes that have been
   affected by the ORF entries carried in the message, but MAY also re-
   advertise the routes that have not been affected by the ORF entries
   carried in the message.

Thanks,
Jakob.

Hi Jakob,

See inline ... 

On Fri, Jul 29, 2016 at 4:18 AM, Ja= kob Heitz (jheitz) <jheitz@cisco.com> wrote:<= br>
Just reading some of this.
A limited refresh is NOT the same thing as "Apply the ORF then re= move it".
Suppose you want to refresh a subset of the routes.=
You send an ORF to permit only the subset.
You receive the subset.
Now you remove the ORF.
You receive the whole table.
NOT what you wanted.


=E2=80=8BIf this is what your implementation does then I recommend you fix = it first. 

For Match =3D DENY =E2=80=8BREMOVE action should result in *only* advertise= ment of previously filtered entries. 

For Match =3D PERMIT REMOVE action should result in *only* the delta betwee= n whole table and remaining ORF entries. 

=E2=80=8BIn no case you get the whole table (other then removal of last ORF= PERMIT entry). =E2=80=8B


 
Also, the use case is good.
The receiver dropped some routes due to policy.
The receiver changed the policy.
Now it wants a repeat of the previously dropped routes.=
This is not a use case for ORF or RTC.
The thing is that ORF or RTC were already passing those routes, s= o changing them is nonsense.


=E2=80=8BFor this case you use Enhanced Route Refresh. As result you get th= ose NLRIs which pass ORF or RTC the filters on a per AFI/SAFI basis. <= /div>

You have to be able to handle it anyway as when you boot you will get.

If you pushed your prefix list with ORF then removing it will get you the d= elta. 

If you filtered based on import RT then advertising RT in ORF or RTC will g= et you the delta. 

So in what exact protocol cases you envision use case for this scoped one t= ime refresh ? And what exactly in your opinion should be the list of parame= ters used to perform a query ? 


Best,
R.







____________________________________= ___________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/list= info/idr