IETF Logo Mail Archive

[Idr] Question about BGP mandatory attribute missing behavior

Ajay L <ajayl.bro@gmail.com> Fri, 29 April 2016 18:32 UTC

Return-Path: <ajayl.bro@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 9728712D519 for <idr@ietfa.amsl.com>; Fri, 29 Apr 2016 11:32:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 Ahp2IGGumtfk for <idr@ietfa.amsl.com>; Fri, 29 Apr 2016 11:32:40 -0700 (PDT)
Received: from mail-oi0-x235.google.com (mail-oi0-x235.google.com [IPv6:2607:f8b0:4003:c06::235]) (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 347EC12D6F8 for <idr@ietf.org>; Fri, 29 Apr 2016 11:32:39 -0700 (PDT)
Received: by mail-oi0-x235.google.com with SMTP id k142so128266212oib.1 for <idr@ietf.org>; Fri, 29 Apr 2016 11:32:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=+sTSh01S90G+OuwOzeekZBG2nvYGphi89/dJKBNDMrM=; b=HiKNG5QgioUdegp1pR/wcVyPgGYwMcA+XAFJqv8q3nMu1zcHkIuUKfjGXwAvqQzpIJ VtC+tJLQYSaVZ9fw6pjn/iGaN+gmtF7F5YwKs0ihIarzhHCCy9MhiOXTADdz6l2Kf8yo Q6XQdiFqcCWn/0PbvWlHIbPHRicDW97MGU6lIDg8HtH1umHgkrY+R4Vh7eEOtIOtRA9/ PBCAb1i5jgBuLPYY6Z/+Db78LlEKNtc8TWqfbQ8BBF9Nbfc/b5iqesIR2NJhCcT0iB60 4d0DzvyVjZXAroHbB27jiElihTrwZmFmSRZkRZfPlRVFwyzk2IjkxddEB/McQCjUCM/G zsMQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=+sTSh01S90G+OuwOzeekZBG2nvYGphi89/dJKBNDMrM=; b=gs8FYAKyUdnW7LnZxkFAO2J409tvAio58Yk840eimCCsOetEDuTwMb8zexX9uf761c rdH117bhW41PV1R9Z64s/0JV7oIdlRCtvwH7xXx4rmcRLWKVEGDyBJuHkn13Upr/Azi/ XW0m7j2MhzdIKiGorb63Aa17MKAiDXGSJur/vI3Lx/OGzz13uTqKaV88LOMvA24yCclH 8wt5y/vKubvFknmzp2UoDPJ4dpsIQuPR2tMX1b5lDzsRDTv07kY9kTOns/jkMGcildBM nMjhwxKLv9sfCXeaJxqFfhh9yRpJQZjOU07AiQ1vo4BnwO77VeOFItd8wJLuvmyKRHlb FJmA==
X-Gm-Message-State: AOPr4FUFgeWi5+4Hv8uKAX3vNKe5JbdWOA4n+4MdDZ1L2gdv8sGVsfPzoBdCSJz6p1gfVUErdj0OnJti92FDfQ==
MIME-Version: 1.0
X-Received: by 10.157.45.198 with SMTP id g64mr10968390otb.132.1461954758523; Fri, 29 Apr 2016 11:32:38 -0700 (PDT)
Received: by 10.157.36.81 with HTTP; Fri, 29 Apr 2016 11:32:38 -0700 (PDT)
Date: Fri, 29 Apr 2016 11:32:38 -0700
Message-ID: <CAHsGAOKFb_McQtFT3XgJs5Ju47=sBS9TERvSFocaOyaJr5g6xg@mail.gmail.com>
From: Ajay L <ajayl.bro@gmail.com>
To: idr@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c11507a0f437c0531a3dedf"
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/srWKMLtPYcRyCaoIGwO4Tq28a2A>
X-Mailman-Approved-At: Fri, 29 Apr 2016 12:06:35 -0700
Subject: [Idr] Question about BGP mandatory attribute missing behavior
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
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, 29 Apr 2016 18:47:34 -0000

Hi Experts,

Had a question about expected behavior about error handling scenario for an
BGP implementation

Per RFC 4271, if mandatory path attribute is not present in the UPDATE
message, NOTIFICATION message with appropriate error code and subcode must
be generated. If multiple mandatory path attributes are missing (e.g.
ORIGIN and AS_PATH), is the expected behavior to generate multiple separate
NOTIFICATION messages one for each missing attribute, or just
one NOTIFICATION message for the first detected missing attribute?

   If any of the well-known mandatory attributes are not present, then
   the Error Subcode MUST be set to Missing Well-known Attribute.  The
   Data field MUST contain the Attribute Type Code of the missing,
   well-known attribute.


Thanks

Ajay

v2.23.0 | Report a Bug | By Email