From nobody Thu Jun 17 03:58:40 2021 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 B07603A19DF; Thu, 17 Jun 2021 03:58:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 qBjX04oSIuKt; Thu, 17 Jun 2021 03:58:33 -0700 (PDT) Received: from mail-ej1-x636.google.com (mail-ej1-x636.google.com [IPv6:2a00:1450:4864:20::636]) (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 7B11C3A1990; Thu, 17 Jun 2021 03:58:32 -0700 (PDT) Received: by mail-ej1-x636.google.com with SMTP id g20so9230699ejt.0; Thu, 17 Jun 2021 03:58:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc:content-transfer-encoding; bh=pwuh7hicawllzTdSa9ioeOfi2dpEYnjNkC4o4nV7KVo=; b=kuRsHwQO4UHwnqoW8QRSzDs526EUZErsoOUIprE7jr9OJkKbCx4Z9sggL6f4vh5oTm akECdK+aDD0Qa1tvDs36TxQrnvfq1Ukwp+MxUvJEWB4qjBA0iZx9hAbQv4iqvPmmr5nj zGyNtZMyMXd9eN58dUfte7/EDoVw1gXR6RAE90aCaxq5lzgKfpSI4wguzoss0YCwC9wY Knee7nXlo3Fj3FwcKOgOtYNpo7QchyITKB6wAs79F9ylIGLrDcHh+bpP7bEWTLUCLwZh TTx/+jTth1N0TFRSY9grUouVEfOV7+NjbumU4BqtDOWYD2DuNBRJ9v8g81kmewxWsJ0e stVg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc:content-transfer-encoding; bh=pwuh7hicawllzTdSa9ioeOfi2dpEYnjNkC4o4nV7KVo=; b=qtn+ppmOEbit13diNnbXk/yaQfv6YG6G2GgCFKZB0IN5p+4Ffc/Y8X32d9CtXb2FI6 10vhlmYN2pqBFPsmgk3TSgf3SQIioRZeqo40dDLjuwqAd3ViZ1b/My9/ka0iMS81oxva WA1uX1WoyGvH1ZYH4m+PcOUqGPP+fj0VufkmKHZN7DW2i63bQIn5etTBHuFwsLyym5eU PkRm7+5Op+4vDEl/Npf06pfYt9ebfRqr1qWwou6Qubft8P4kU4rKZC68b+QFb0uSKlib zu5V6F8QVQQzx8ho78ro//tuE1U6nAzGUdtlhdru6PbWP/33OESsJuXNOHwogQZeO10m PcZA== X-Gm-Message-State: AOAM532dp03Ezf3UuNQHUmE5L9AlXcH966hTFmnyYG5oWn7ruBDjblGW tQ2rv7FYMMbBrvbUw/yynAeqwCiY6694XQ9zm0I= X-Google-Smtp-Source: ABdhPJzS7uL5jmZRZDnBZaHEHcyp6GONqYmK7q4oL60aAJlyMJ2/ks4hW5faPT9i0WBr4HhseHVv6OhTlYGlu7/PFPs= X-Received: by 2002:a17:906:340d:: with SMTP id c13mr4632938ejb.457.1623927505820; Thu, 17 Jun 2021 03:58:25 -0700 (PDT) Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Thu, 17 Jun 2021 03:58:25 -0700 From: Alvaro Retana In-Reply-To: References: <162387309626.26876.9780257787421823003@ietfa.amsl.com> MIME-Version: 1.0 Date: Thu, 17 Jun 2021 03:58:25 -0700 Message-ID: To: Robert Raszuk , Robert Wilton Cc: Susan Hares , idr-chairs , draft-ietf-idr-bgp-optimal-route-reflection@ietf.org, John Scudder , The IESG , "idr@ietf. org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Archived-At: Subject: Re: [Idr] Robert Wilton's No Objection on draft-ietf-idr-bgp-optimal-route-reflection-25: (with COMMENT) X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jun 2021 10:58:36 -0000 On June 16, 2021 at 6:36:43 PM, Robert Raszuk wrote: Just a quick correction: the BGP Model is still in the WG. =C2=A0At this point, and because it has taken so long, the focus should be on moving the model on -- other features can be added, as needed, through augmentation. Alvaro. > > May I please check, is there a YANG data model that covers this > > functionality? > > The original plan was to add this to the main BGP YANG specification > -draft-ietf-idr-bgp-model-10 to keep this part of the main BGP YANG model > document. > > But it seems that this document moved on and now is in IETF LC.