Re: [Idr] Adoption call for draft-dawra-idr-bgpls-srv6-ext [5/2 - 5/16/2018]

Robert Raszuk <robert@raszuk.net> Tue, 04 June 2019 13:46 UTC

Return-Path: <robert@raszuk.net>
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 328C012004E for <idr@ietfa.amsl.com>; Tue, 4 Jun 2019 06:46:03 -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_HELO_NONE=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=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 IiQOfr502ijm for <idr@ietfa.amsl.com>; Tue, 4 Jun 2019 06:45:59 -0700 (PDT)
Received: from mail-qk1-x72c.google.com (mail-qk1-x72c.google.com [IPv6:2607:f8b0:4864:20::72c]) (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 B31E7120004 for <idr@ietf.org>; Tue, 4 Jun 2019 06:45:59 -0700 (PDT)
Received: by mail-qk1-x72c.google.com with SMTP id w187so2813275qkb.11 for <idr@ietf.org>; Tue, 04 Jun 2019 06:45:59 -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 :cc; bh=LQyYYsGmFM68yIM+Kq/WPJ5Aq1yP1Hru+tXCy8zS2Cc=; b=NJKMM81XTj0uHZEgooAGLzVnR+6QKHyx+RxdGnShQGE/BmzgKwUSuprmMnbUZWK8zz XfHUr1Ov0Xeg3VKFp0yxcBYVDIQQLYXwK0LHLSl3HNV/AdH+ovGDzd/KqCNfk+6MAK2+ kiuoNo1NZM1bDEFfu0v9UTe/pOmqJxkvx8hgmQ3jXXuiD+1PbrzOIqpAUqGt6lvkUrM8 4KSLMMr1yVGq86hyUqfLNlvYsZ8VmxZwwOz+gh6OW3OzIUhOGdQwY2n95Sl9M0+kbHUk HJzUfnLtlFh5LqlH1Zjr7YNuh0nClWJgrcBgPORIUBc7cfG2jBGPjoxYJ4w4SxDhnPDE toRw==
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:cc; bh=LQyYYsGmFM68yIM+Kq/WPJ5Aq1yP1Hru+tXCy8zS2Cc=; b=HlrP1sSFGoqroVTlVmqbrXwEei9kF4jzzWrcMF2YEkMv8YtytaQG0FYI5rQZwIf2UG 1CN5bUgkhkVqZzr2UfsUwl/s0GCKqUjSq795z20Y6E7fi7ibmXhE1uG+KL1LFl3aW9Ck VbmevvfkJ+14KKWos48QdgjSeEV4GoCTVOTKdqgpB2JmGoItYyM6KlmR9DC19J2sm6sA Wwtp/Tbp1KfjZBSHf6qMRV2IbkknULrb3bgwF9T3R4hBgvvjT9XK/WcqGMxObH6CPq0l Wm7hViW7dg44Eoz+vIJR+CeaHqO7hNWskmhym+NjVjdL8/7JFh1x7/V4iSm6t9c2RR8t RW3w==
X-Gm-Message-State: APjAAAXGrSHvtkJ0X8ZOwcA/1Ds39esS0T9FVpb7vfvxehPe+NMkhnFk wD6i+CZvHE+hDTM0kd+qwOr23MZEukzF7cJe1MDXWw==
X-Google-Smtp-Source: APXvYqypKotVKm1M53JHdR5SepvTPmNd2SUfSy3ymNjJSk9FA2rOPu3RU2+AOIXx7JZmnEU+M4fhtEM9/Lmt5dhpCdY=
X-Received: by 2002:a05:620a:1206:: with SMTP id u6mr26671425qkj.88.1559655958602; Tue, 04 Jun 2019 06:45:58 -0700 (PDT)
MIME-Version: 1.0
References: <01ce01d5167f$d263a120$772ae360$@ndzh.com> <DM5PR11MB202720F61953C224DB081498C1140@DM5PR11MB2027.namprd11.prod.outlook.com> <02cf01d51ab1$052bfc80$4001a8c0@gateway.2wire.net> <004201d51abd$498a5000$dc9ef000$@ndzh.com> <CAOj+MMEnyT1sOX9fWbDR4PV4goBZerdF6ykKUbZ2t3YDRyAHfg@mail.gmail.com> <005301d51ac3$4b6e6a90$e24b3fb0$@ndzh.com>
In-Reply-To: <005301d51ac3$4b6e6a90$e24b3fb0$@ndzh.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Tue, 4 Jun 2019 15:45:46 +0200
Message-ID: <CAOj+MMHV0G_O9p7F0UPHXUtzz6HWSiVa5EsLosZu3Q7U_Gr32A@mail.gmail.com>
To: Susan Hares <shares@ndzh.com>
Cc: "idr@ietf. org" <idr@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000627fcd058a7fb3f1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/DCIgodko0DzsuBt93mZmJPJ6ixQ>
Subject: Re: [Idr] Adoption call for draft-dawra-idr-bgpls-srv6-ext [5/2 - 5/16/2018]
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jun 2019 13:46:03 -0000

Hi Sue,


> As to the 99% of BGP-LS,  that’s a question the chairs and ADs tried to
> ask the WG in 2018.   The WG did not engage on that discussion.
>

I reread the IDR charter ,,, https://datatracker.ietf.org/wg/idr/about/

I did not find anything there which would justify any of the work related
to BGP-LS needs in this WG for example - topology or link state information
transport.

IMO AD should recognize the need for various non routing information
transport and steer this towards BOF and new WG creation to define new
protocol for it.. Even if rather from scratch such effort would reuse some
of the BGP features. And while it was not done up front it is not too late
now.

In order to protect the BGP stream,  the ADs/Chairs pushed for
> draft-ketana-rfc7752bis.txt (for improved error handling) and larger BGP
> messages (see raft-ietf-idr-bgp-extended-messages-30.txt).
>

Improving error handling is always good.

But how making the message larger helps to protect the BGP stream ? Its
like opening the window wider when cloud of wild insects approaches ....

Best,
R.