IETF Logo Mail Archive

Re: [Sidrops] Multiple origin validation states in draft-ietf-sidrops-validating-bgp-speaker

Daniel Kopp <daniel.kopp@de-cix.net> Tue, 23 July 2019 21:15 UTC

Return-Path: <daniel.kopp@de-cix.net>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA3831209D4; Tue, 23 Jul 2019 14:15:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 iIaC7gmP_t3y; Tue, 23 Jul 2019 14:15:34 -0700 (PDT)
Received: from de-cix.net (relay4.de-cix.net [46.31.121.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A1221209BD; Tue, 23 Jul 2019 14:15:34 -0700 (PDT)
IronPort-SDR: wuRoO7bP1TnWB3c5G5cYGWkbyCLwWP0VXRrDCxro+0IKZm/Tso4PS4nXOJWrYJqGn9x1r3+HBI QBf8/MYQoR2uBMqhnvXEp0ijqdVDjD2KsXQkvHP4tqZvusgRDreXBrPOnQ3uAB0HCTZVjwSMmW Ccs2NuSeXnMOP2h/1osSdIt3JZOJ5b+MDXH2hF9EcFQBr6xdRpJ9nOj15MBhSAaVoECfyC1rAq DpszsK3GkZbHqWKDfAnCdRqASdyhJ84dco+1zCFEhRz8CCKVaFw3p+Fybl5VdvlhqMEt177aT/ Tko=
X-IronPort-AV: E=Sophos;i="5.64,300,1559512800"; d="scan'208";a="8830502"
Received: from unknown (HELO smtp.de-cix.net) ([192.168.65.10]) by mailgw014.de-cix.net with ESMTP; 23 Jul 2019 23:13:13 +0200
Received: from EX02.for-the-inter.net (ex02.for-the-inter.net [192.168.49.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.de-cix.net (Postfix) with ESMTPS id 7AE4DB00B8; Tue, 23 Jul 2019 23:15:32 +0200 (CEST)
Received: from EX02.for-the-inter.net (192.168.49.20) by EX02.for-the-inter.net (192.168.49.20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1779.2; Tue, 23 Jul 2019 23:15:32 +0200
Received: from EX02.for-the-inter.net ([fe80::1cb2:801e:f870:7df9]) by EX02.for-the-inter.net ([fe80::1cb2:801e:f870:7df9%4]) with mapi id 15.01.1779.004; Tue, 23 Jul 2019 23:15:32 +0200
From: Daniel Kopp <daniel.kopp@de-cix.net>
To: John Scudder <jgs=40juniper.net@dmarc.ietf.org>
CC: "draft-ietf-sidrops-validating-bgp-speaker@ietf.org" <draft-ietf-sidrops-validating-bgp-speaker@ietf.org>, "sidrops@ietf.org" <sidrops@ietf.org>
Thread-Topic: [Sidrops] Multiple origin validation states in draft-ietf-sidrops-validating-bgp-speaker
Thread-Index: AQHVQZK7YXV6PGo8cUeBqH/9As28x6bYkteA
Date: Tue, 23 Jul 2019 21:15:32 +0000
Message-ID: <6D891976-1160-4329-8035-51DD954B835F@de-cix.net>
References: <0B8E9A81-31FE-45BC-A01C-0D05E307EE0E@juniper.net>
In-Reply-To: <0B8E9A81-31FE-45BC-A01C-0D05E307EE0E@juniper.net>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-mailer: Apple Mail (2.3445.6.18)
x-originating-ip: [192.168.140.61]
Content-Type: text/plain; charset="utf-8"
Content-ID: <A0100AB5B000954AB8C01DFD80E5A016@for-the-inter.net>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/d0p8dfFteObIGLT1CSWMw67FYJM>
Subject: Re: [Sidrops] Multiple origin validation states in draft-ietf-sidrops-validating-bgp-speaker
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Jul 2019 21:15:45 -0000

Hi John, 

thanks for pointing this out and clarifying your comment.

I’m sorry for the confusion. I was verbally interpreting the section to extensive, I think :)
A talked to the other authors and it seems that 5.4 is meant to be an addition/similar to 5.2.

So even that the route server must strip any Prefix Origin Validation State it receives,
5.4 serves as an extra protection in case things go wrong.

Let me know if you think we should remove 5.4.

Thanks for your comment!
Daniel

> On 23. Jul 2019, at 22:10, John Scudder <jgs=40juniper.net@dmarc.ietf.org> wrote:
> 
> My comment at the mic was based on the verbal description of the slide. What I see in the draft text is different:
> 
> 5.4.  Error Handling at Peers
> 
>   A route sent by a validating BGP speaker SHOULD only contain none or
>   one EBGP Prefix Origin Validation State Large Community.
> 
>   A peer receiving a route from a validating BGP speaker containing
>   more than one EBGP Prefix Origin Validation State Large Community
>   SHOULD only consider the largest value (as described in Table 1) in
>   the validation result field and disregard the other values.  Values
>   larger than two in the validation result field MUST be disregarded.
> 
> This is different from what was described verbally. The written version seems fine to me. So, I would like to withdraw my comment.
> 
> I do suggest changing both SHOULD to MUST unless you can think of a use case for doing differently; if you can I suggest adding a MAY clause to describe the exception case.
> 
> Thanks,
> 
> —John
> _______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org
> https://www.ietf.org/mailman/listinfo/sidrops

v2.23.0 | Report a Bug | By Email