[Idr] Should BGP communities be restrictive (Issue #38)?

Mahesh Jethanandani <mjethanandani@gmail.com> Fri, 30 August 2019 20:32 UTC

Return-Path: <mjethanandani@gmail.com>
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 30F2D120903 for <idr@ietfa.amsl.com>; Fri, 30 Aug 2019 13:32:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 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_FONT_FACE_BAD=0.001, 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=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 vxr_Z4_BUaYR for <idr@ietfa.amsl.com>; Fri, 30 Aug 2019 13:32:56 -0700 (PDT)
Received: from mail-pf1-x432.google.com (mail-pf1-x432.google.com [IPv6:2607:f8b0:4864:20::432]) (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 2B140120108 for <idr@ietf.org>; Fri, 30 Aug 2019 13:32:56 -0700 (PDT)
Received: by mail-pf1-x432.google.com with SMTP id o70so5352553pfg.5 for <idr@ietf.org>; Fri, 30 Aug 2019 13:32:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:mime-version:subject:message-id:date:to; bh=T0O09jemTYpunhIf2ZT3JMK7fMssJhUzmigYYyGw1+c=; b=M+Nj6d9KlqMNf88o2A2L+eBm1HObQMRMC4sISEPciExGoQnkkTehzvIE4MpUxQ2qpf WP/25I6ncmZ5+ppqGsxmwYjWLVQGXTNXJS2Y1LcKBd1PhMrO7Bx2ELL1/1rcPDRcGjpy RDcUXUAYCs+6AUZYIMy3wOm16ij8J3iDIzeIn2Z7uBZWpOXSMNBD4XZmDwB7MbqXyYqL Pn+imKsHGgk04CKyjOiqTxrOdKE8h8FusDPWYB+HhH3/TNW5k8ltlJz4bwyNraPsc7es pBgq5BXDPSsOTz3IuVvkRpa+tmz5zf9A74c567koFElziA5zsvFwYJjsLl95RrgFPxrP JETg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:message-id:date:to; bh=T0O09jemTYpunhIf2ZT3JMK7fMssJhUzmigYYyGw1+c=; b=HO3PzpYp3jEpMpCjh5eay1Fc91qz/ND4nd3r0aBfnNhpz8c3cWrkmB8img781SkW5R EwnMGvD29DxpWFzf0swaME/ed2DUKANgIg/bboK1EFzhTfRFZyMpRFidvoz+tOYMpIsF +3XXyuOBfCR4olmUyFUaokqQ4tIM9e6wL0W/6Y+NLisngXdJS/6HWU1h2Gq/HcowI+eB sYFclpJGvCdHhUXr6gBEiqQz929evNS0IWBzMqJRLv0mH/SFF4b4ETyYkAwY95pV5/fb TrO59xB//u9ERHNg6PlhCEqInOqcLLKfUZjHvqvZoJbCf9x5GbRVKu0L7nf/5XzJDD6P C/tw==
X-Gm-Message-State: APjAAAXt/rw7Gr8tXCSGHbYv35YRcElICD5CSjL4glXVfAlv2eT1UCAC scsGjVAyyL4rQl7hsfgP6newUfTj5lc=
X-Google-Smtp-Source: APXvYqzLZ3b/AtD/F6lpjcMEwCfRDH01n/sV+KYMlRkceq1Ei+IdCs7/unL6o5cnfYBVSXMmKY88pg==
X-Received: by 2002:aa7:8bcc:: with SMTP id s12mr5224961pfd.93.1567197175503; Fri, 30 Aug 2019 13:32:55 -0700 (PDT)
Received: from [10.33.122.240] ([66.170.99.1]) by smtp.gmail.com with ESMTPSA id k14sm6180656pgi.20.2019.08.30.13.32.54 for <idr@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 30 Aug 2019 13:32:54 -0700 (PDT)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_D8D1A52C-B8A1-49B3-AAEB-F69ACFAF674D"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Message-Id: <6355C6C6-121C-425E-8AB3-24B151222D15@gmail.com>
Date: Fri, 30 Aug 2019 13:32:53 -0700
To: idr@ietf.org
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/0grIwtRVg0HGgxujb1oJcUiTKhw>
Subject: [Idr] Should BGP communities be restrictive (Issue #38)?
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: Fri, 30 Aug 2019 20:32:59 -0000

The following issue (#38) is documented here <https://github.com/mjethanandani/ietf-bgp-yang/issues/38> for the BGP YANG module.

It reads:

The current community type is defined in a restrictive manner. An example of what that restriction looks like can be seen here <https://github.com/mjethanandani/ietf-bgp-yang/blob/master/src/yang/ietf-bgp-types.yang#L296>. At least one of the observations is that, experience has shown that restricting ranges of communities may have negative impact on things such as policy, which may need to refer to out-of-acceptable-range values. The suggestion is to not restrict these beyond limiting the range to uint32, or what in YANG terms is 0..max.

The question therefore for the WG is, should the YANG model define the community-type in a restrictive manner that will then allow for checking of invalid values, or should it loosen restrictions on the types to allow for an unrestricted range of values to be accepted, knowing that it will fail somewhere deep in the bowels of the system.

An alternative is to define two different types for *-community-type. One that is restrictive and the other that is not. The latter will be used in policy definition, while the former will be used for everything else.

If no strong opinion is heard, the model will maintain the current restrictions on the ranges it has.

Cheers.

Mahesh Jethanandani
mjethanandani@gmail.com