Re: [GROW] I-D Action: draft-gu-grow-bmp-vpn-te-00.txt

Robert Raszuk <robert@raszuk.net> Mon, 11 March 2019 14:00 UTC

Return-Path: <robert@raszuk.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33CF8130F4F for <grow@ietfa.amsl.com>; Mon, 11 Mar 2019 07:00:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=raszuk.net
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 zdV9EKRvCPgt for <grow@ietfa.amsl.com>; Mon, 11 Mar 2019 07:00:28 -0700 (PDT)
Received: from mail-qt1-x82c.google.com (mail-qt1-x82c.google.com [IPv6:2607:f8b0:4864:20::82c]) (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 2FA51130E77 for <grow@ietf.org>; Mon, 11 Mar 2019 07:00:28 -0700 (PDT)
Received: by mail-qt1-x82c.google.com with SMTP id b3so5101126qtj.3 for <grow@ietf.org>; Mon, 11 Mar 2019 07:00:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=vMHzpJiVDaXcmz462+1/vPdTlgMQyax4EMJgjJII+9U=; b=YJDXAUXBX3bKbsRsgVHpWIuUYDqB+WZNLTDuyg0v/OHLOx/xWLGVnW1MGidJdOlHZu xLlQSlqzxuYfq0/xGClsTpft62PGmVTRcmo+oLH8kGWa6Ks/0SIOqwJvNARHo2bRHZHj nm7TH9GwW1CZxULa6km+Chjjqn4pNw6yWV6zSXVp5nv5ZEuPABdVek17w+ZE2V3PerU2 8Rk1ZhbY2gWcU9d0ulu4ONmh/go+Y9V6JPcQUM4Ejhs5w4ErtBYdfsjehmcrBeLSvvK4 YcW3xp2Q1IO7yzEDjYsMlMnI7zDRzdsc2sFlrdHtpxXiRcJt4JliMGoEolG1oe6tBeN4 KVsw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=vMHzpJiVDaXcmz462+1/vPdTlgMQyax4EMJgjJII+9U=; b=Ij/OTCstek1LU5xNpNYIvqiCB4iKaEqDoKxSaTzUWvaXUjniZEHX0ueCJ88eGh+ox9 n5ywxH6n39R2avg9Z4GduWV04wmEAJtzDJFBwok7z0V44REGhQcjKjE77CqXkc3HN64c 5IS410Mv51usNJSeTXzQ9+mUbV2ZRJEEHUXjdscPdAZprVCXz4psewfP7pTZeuZIHwOk rAxsI6XsbdIvYMwhF2e0Vz+FqNOXlKKK3dPxsidvlnghJyOn/p20L/YAZfytcl7dQWa4 9kcoqfiFHu7YbJlCbX6aMo8wdSGdRzRvK06jNlEre5Fu4HxByTNVFSdnsQUsMfpOYPve 20ew==
X-Gm-Message-State: APjAAAVTIYGk04hpvOkRAbRTLKNbkpHNbBv+enIs6q9hgkK8fHyLkXe5 k/1Br4iSyQ0+cl1MywI0/p1Mh+ZaC1M9PvrRB30X9Kk2+Ns=
X-Google-Smtp-Source: APXvYqxJLipCRYQmUV5zUnrh1p36Y1vnAuQGEhaKRHIV2+ZhTj2V7ngmCwrtnBxlJxEnXrXg4ABY2wwpe7DsgOui7uY=
X-Received: by 2002:a0c:aee6:: with SMTP id n38mr25458435qvd.69.1552312826991; Mon, 11 Mar 2019 07:00:26 -0700 (PDT)
MIME-Version: 1.0
References: <155230802904.16948.518748917430558140@ietfa.amsl.com>
In-Reply-To: <155230802904.16948.518748917430558140@ietfa.amsl.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Mon, 11 Mar 2019 15:00:15 +0100
Message-ID: <CAOj+MMHYD_HO3_VQDb9AYpCGMuib4VFNFk_eq9-3V_9Th1oJRA@mail.gmail.com>
To: grow@ietf.org
Content-Type: multipart/alternative; boundary="000000000000a22a530583d1fe35"
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/FnxU8nGbPjkE6vXFxl2HNfgwTN0>
Subject: Re: [GROW] I-D Action: draft-gu-grow-bmp-vpn-te-00.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Mar 2019 14:00:44 -0000

Dear authors of this draft,

Please kindly clarify why vpn traffic engineering requires any extensions
to BMP ? The only justification I found in your draft is following:

"   All in all, it's more efficient to collect the MPLS VPN label
   independently than extracting it from VPNv4 routes."

I would challenge if it is indeed more efficient to upgrade 100s of PEs,
add completely new functionality to current bmp code and then split in some
implmentations very limited number of bmp sessions out of those PEs into
multiple controllers/monitoring tools as opposed to simply parse vpnv4
updates on x86 controller.

VPN labels along with routes and next hops can be learned by your traffic
engineering controller  over vpnv4 sessions since it already needs to speak
vpnv4 SAFI anyway to advertise the "engineered" routes back to the network
devices.

It can advertise it with higher local preference to enforce his routes to
be used as alternative reachability information which could be already
present for example via traditional route reflection.

Besides these days to get any information from a router BGP-LS SAFI is
targetted so I am highly puzzled what triggered idea of now start extending
BMP with similar objectives.

Regards,
RR.


On Mon, Mar 11, 2019 at 1:40 PM <internet-drafts@ietf.org> wrote:

>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>
>         Title           : VPN Traffic Engineering Using BMP
>         Authors         : Yunan Gu
>                           Jie Chen
>                           Penghui Mi
>                           Shunwan Zhuang
>                           Zhenbin Li
>         Filename        : draft-gu-grow-bmp-vpn-te-00.txt
>         Pages           : 10
>         Date            : 2019-03-11
>
> Abstract:
>    The BGP Monitoring Protocol (BMP) is designed to monitor BGP running
>    status, such as BGP peer relationship establishment and termination
>    and route updates.  This document provides a traffic engineering (TE)
>    method in the VPN (Virtual Private Network) scenario using BMP.
>
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-gu-grow-bmp-vpn-te/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-gu-grow-bmp-vpn-te-00
> https://datatracker.ietf.org/doc/html/draft-gu-grow-bmp-vpn-te-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/
>
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>