[mpls] draft-rosen-mpls-rfc3107bis

<bruno.decraene@orange.com> Wed, 13 April 2016 11:32 UTC

Return-Path: <bruno.decraene@orange.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id BAAFC12DC58; Wed, 13 Apr 2016 04:32:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 551FrufEoGmS; Wed, 13 Apr 2016 04:32:42 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E763812DE39; Wed, 13 Apr 2016 04:32:41 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm14.si.francetelecom.fr (ESMTP service) with ESMTP id B9D0822C2CC; Wed, 13 Apr 2016 13:32:40 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown []) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id 97AB6238062; Wed, 13 Apr 2016 13:32:40 +0200 (CEST)
Received: from OPEXCLILM21.corporate.adroot.infra.ftgroup ([fe80::e92a:c932:907e:8f06]) by OPEXCLILM31.corporate.adroot.infra.ftgroup ([fe80::2cc9:4bac:7b7d:229d%19]) with mapi id 14.03.0279.002; Wed, 13 Apr 2016 13:32:40 +0200
From: bruno.decraene@orange.com
To: Eric C Rosen <erosen@juniper.net>
Thread-Topic: draft-rosen-mpls-rfc3107bis
Thread-Index: AdGVaEaLL3G3O9S6RJ2NuhcTrvYwZA==
Date: Wed, 13 Apr 2016 11:32:40 +0000
Message-ID: <22090_1460547160_570E2E58_22090_19743_1_53C29892C857584299CBF5D05346208A0F86D10D@OPEXCLILM21.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version:, Antispam-Engine:, Antispam-Data: 2016.4.13.110317
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/fOyaLb-tfpgcK5x7Xi84DLgWRNQ>
Cc: "idr@ietf.org" <idr@ietf.org>, BESS <bess@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>
Subject: [mpls] draft-rosen-mpls-rfc3107bis
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Apr 2016 11:32:50 -0000


Could the draft clarifies the BGP Route Reflector behavior when reflecting a route received from a buggy 3107 implementation with S=0?
a) One may argue that the RR should not modify the NLRI and hence reflect the route with S=0
b) One may argue that the RR should reflect the route after setting S=1 in order to be a speaker compliant with 3107bis & 3107.
c) One may argue that this is an error and treat the IP Prefix as withdraw

IMO I think I would prefer b) in order to not propagate the bug.



Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.