[mpls] draft-rosen-mpls-rfc3107bis-01

<bruno.decraene@orange.com> Wed, 03 August 2016 09:24 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 AEE0112D0CA; Wed, 3 Aug 2016 02:24:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.905
X-Spam-Status: No, score=-3.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, 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 FV2vXw05nlth; Wed, 3 Aug 2016 02:24:54 -0700 (PDT)
Received: from relais-inet.orange.com (relais-nor35.orange.com []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9222412D0A9; Wed, 3 Aug 2016 02:24:54 -0700 (PDT)
Received: from opfednr03.francetelecom.fr (unknown [xx.xx.xx.67]) by opfednr27.francetelecom.fr (ESMTP service) with ESMTP id 21130A03C0; Wed, 3 Aug 2016 11:24:53 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.41]) by opfednr03.francetelecom.fr (ESMTP service) with ESMTP id E5DB61A0083; Wed, 3 Aug 2016 11:24:52 +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.0301.000; Wed, 3 Aug 2016 11:24:52 +0200
From: bruno.decraene@orange.com
To: "mpls@ietf.org" <mpls@ietf.org>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: draft-rosen-mpls-rfc3107bis-01
Thread-Index: AdHtXhKcw/8U4DNRSc6RiIGfzLyKjA==
Date: Wed, 03 Aug 2016 09:24:51 +0000
Message-ID: <5633_1470216293_57A1B865_5633_2905_1_53C29892C857584299CBF5D05346208A0F973F79@OPEXCLILM21.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_53C29892C857584299CBF5D05346208A0F973F79OPEXCLILM21corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/YnuR6Dg5vEURdpWBnjlqx3K6xYQ>
Subject: [mpls] draft-rosen-mpls-rfc3107bis-01
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, 03 Aug 2016 09:24:58 -0000

Hi Eric,

Thanks for the draft.
I may have 2 comments.

1)      Interaction with BGP Graceful Restart

"   [RFC4724] ("Graceful Restart Mechanism for BGP") describes a

   procedure that allows routes learned over a given BGP session to be

   maintained when the session fails and then restarts.  This procedure

   requires the entire RIB to be transmitted when the session restarts.

   If the Multiple Labels Capability for a given AFI/SAFI had been

   exchanged on the failed session, but is not exchanged on the

   restarted session, then any prefixes advertised in that AFI/SAFI with

   multiple labels MUST be explicitly withdrawn.  Similarly, if the

   maximum label count, specified in the Capability for a given AFI/SAFI

   is reduced, an prefixes advertised with more labels than are valid

   for the current session MUST be explicitly withdrawn."

I don't think that the prefix "MUST be explicitly withdrawn." I'd rather say that the prefix "MUST not be re-advertised" (...with a number of labels exceeding the capability of the receiver).  IOW, the new BGP session simply needs to comply with the spec, nothing new. But I'd agree that to be on the safe side, explicitly spelling out this case may be appropriate. But we could also note that rfc6793 (AS 4-octet) has a related problem and does not talk about it.
Under the control of the IDR WG that is in copy.
BTW, IMHO this document looks heavier on the BGP side than on the MPLS side, especially with the new additions in -01 e.g. interaction with GR, Enhanced-GR which are not trivial, even for the IDR WG. Especially since 3107bis mostly fixes BGP related points (e.g. capability, different BGP encoding depending on the capability)

2)      Interop with RFC 3107

   If a BGP implementation, not conformant with the current document,
   encodes multiple labels in the NLRI but has not sent and received the
   "Multiple Labels" Capability, a BGP implementation that does conform
   with the current document will likely reset the BGP session."

I agree, but it's rather usual that a non-conformant implementation creates issues.
In this case, I think that it would be fair to highlight that an implementation compliant with RFC 3107 and supporting the advertisement of multiple labels, is _not_ compliant with rfc3107bis, hence not interoperable, hence will likely reset the BGP session.
I think it would be useful to have a section talking about the interoperability between RFC3107 and rfc3107bis, in particular for network operator to read and be able to perform the appropriate checks before deployments.



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.