IETF Logo Mail Archive

Re: [Idr] IDR Charter discussion

Robert Raszuk <robert@raszuk.net> Mon, 10 June 2019 22:58 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 1BAE812010F for <idr@ietfa.amsl.com>; Mon, 10 Jun 2019 15:58:37 -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 o8MUT5Ct5pla for <idr@ietfa.amsl.com>; Mon, 10 Jun 2019 15:58:34 -0700 (PDT)
Received: from mail-qt1-x82b.google.com (mail-qt1-x82b.google.com [IPv6:2607:f8b0:4864:20::82b]) (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 5D49B1200FF for <idr@ietf.org>; Mon, 10 Jun 2019 15:58:34 -0700 (PDT)
Received: by mail-qt1-x82b.google.com with SMTP id s15so12304665qtk.9 for <idr@ietf.org>; Mon, 10 Jun 2019 15:58:34 -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=9JdFvbeaPA5BzW8J2D2UUzvqYKEmXHCsdYtqg98xqDM=; b=BbZjhy9ypbWGIF7+ZbH+5iYjr7wmDZ7pqq8IREI8yO1bAt4s3sDJHzzU/fun92krxg WVdy5QH8qRVh9H/4Y5hUJDcziRloC7izlFkVRFUzYaEDq/orpxYYOCrI8oQr7yr4Y1Bz UbPXTgOknCXXKZvR8uP4wDavQMSQ/HfWT7yMgsf7u4k+FJbe+uZXHqJlu6cKYVJDxwQI BeU5NSkv0j1wS2VdKrdYfv41MYRMjqD8+1OBplDFaTxpo3lhFKKFxvUIMayMJaIM6yhv 0I2qaxqchb7AYSPWqLVYJJp8w3qbNkB8ilKwukq9P5f8GtY+B4rF92k8+EQbBm1ZtDec gdug==
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=9JdFvbeaPA5BzW8J2D2UUzvqYKEmXHCsdYtqg98xqDM=; b=FHlamZZZ7huVzCp5D4Pu0zGpmFOyF0vJTxoKyMrBN6Wta0Otsy/ZK3kfZNx3ZyclJF w7u+JyqIy2AQq1Za26MoSnXVsywsOQ41f6gdBz6OBOFEhnYylfLHmalut6GUcW/3CwFy NgjnSpIIv3p1shR9w4kM+ThjG83IvpBcT9s3zeKmObA/jgulr92UldQxyI/TBr+hfUsM MejP/U+142LRElwLpr+gP/5L30nfHwAFmvN19tu5TEKZQ8kNI68SWfLjDl5FiuCNpDp+ zhWiV+jtzlxNFR68FiCUoc2fX8Qjlng9QmazW6TG9kyJjwxtJfwYsAkJmAdL1VvJNSMn v0ww==
X-Gm-Message-State: APjAAAUTeNLcbfOdkQiyRjs1y8266HGEpdCK9YE16kDBuw8n6PVK+aiz zgA7H9p0fe4dur5oitBZS1XEaFFk+htAQ24DsfAecA==
X-Google-Smtp-Source: APXvYqyhlCFKlYqcnQ2EXm3poQ7Zb4iSSH39HOlCJcEry0qgjXjuesQea4wI2S3KU777QLo+xyiGpVfq7hmI3FLRhOY=
X-Received: by 2002:aed:228d:: with SMTP id p13mr2747120qtc.208.1560207513405; Mon, 10 Jun 2019 15:58:33 -0700 (PDT)
MIME-Version: 1.0
References: <022b01d51fc5$d6576dd0$83064970$@ndzh.com>
In-Reply-To: <022b01d51fc5$d6576dd0$83064970$@ndzh.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Tue, 11 Jun 2019 00:58:23 +0200
Message-ID: <CAOj+MMGC4UwmBCuidx-9RjoDS3xHyXZKs=-qvUQ5t3WvXMmy2A@mail.gmail.com>
To: Susan Hares <shares@ndzh.com>
Cc: "idr@ietf. org" <idr@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009ce2a3058b001e15"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/_L9bcKeg4GR2Zc33VEy9vKbyphQ>
Subject: Re: [Idr] IDR Charter discussion
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: Mon, 10 Jun 2019 22:58:37 -0000

Hi Sue,

> Is there anything we missed?

Can we please also consider adding to the new charter:

* *Enhancements to eBGP Path Selection*

Today we see number of proprietary solutions in this space popping left and
right.

I think it would be in the interest of the industry to work on it in the
IDR WG and deliver an IETF specification of the WG product.

Rajiv has started, but his draft - while very useful - just barely
scratches the tip of the ice berg :)

Thx,
Robert.


On Mon, Jun 10, 2019 at 9:51 PM Susan Hares <shares@ndzh.com> wrote:

> The IDR Charter was last revised in March, 2010.
>
>
>
> It’s time to reconsider what needs to go in the charter:
>
>
>
> Somethings we might include are:
>
> ·         BGP Yang modules,
>
> ·         A general BGP Layer 3 auto-configuration or liveness,
>
> ·         Additional  tunnel features for a optional tunnel encapsulation
> (a follow-on to draft-ietf-idr-tunnel-encaps),
>
> ·         Upgrade of the base BGP specification to Full Standard,
>
> ·         Flow specification additions,
>
> ·         BGP-LS basic functions (e.g. draft-ketant-idr-rfc7752bis-00
> <https://datatracker.ietf.org/doc/draft-ketant-idr-rfc7752bis/>) error
> handling
>
> ·         Segment routing additions to BGP,
>
> ·         Wide Communities and other “bigger” communities ,
>
> ·         Revisions to Existing features.
>
>
>
>
>
> Things which will be removed because we are done:
>
> ·         Support for 4-octet AS numbers,
>
> ·         Add path related additions,
>
> ·         Error handling rules for BGP in general,
>
> ·         Revisions to the BGP 'Minimum Route Advertisement Interval',
>
> ·         The definition of an "Accumulated IGP Metric".
>
>
>
> In 2010, IDR started an advancement of BGP to full standard, but stopped.
>
> WG members indicated they wanted us to focus on the feature revisions.
>
>
>
> Is there anything we missed?
>
>
>
> Please use this thread to suggest things we should keep or drop in the
> charter.
>
>
>
> Cheerily, Susan Hares
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>

v2.23.0 | Report a Bug | By Email