[mpls] Martin Vigoureux's No Objection on draft-ietf-mpls-summary-frr-rsvpte-08: (with COMMENT)

Martin Vigoureux via Datatracker <noreply@ietf.org> Thu, 20 February 2020 01:35 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: mpls@ietf.org
Delivered-To: mpls@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B62E412011F; Wed, 19 Feb 2020 17:35:10 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Martin Vigoureux via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-mpls-summary-frr-rsvpte@ietf.org, Nicolai Leymann <n.leymann@telekom.de>, mpls-chairs@ietf.org, n.leymann@telekom.de, mpls@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.118.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Martin Vigoureux <martin.vigoureux@nokia.com>
Message-ID: <158216251073.17710.2187878116475113514.idtracker@ietfa.amsl.com>
Date: Wed, 19 Feb 2020 17:35:10 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/tSdxQYGJAmULD_KZ4wBzvcZ9Vuk>
Subject: [mpls] Martin Vigoureux's No Objection on draft-ietf-mpls-summary-frr-rsvpte-08: (with COMMENT)
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 20 Feb 2020 01:35:11 -0000

Martin Vigoureux has entered the following ballot position for
draft-ietf-mpls-summary-frr-rsvpte-08: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-mpls-summary-frr-rsvpte/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Hello

it's getting late here so please dismiss any tiredness induced comment.

       3.1.1.  IPv4 B-SFRR-Ready IPv4 Extended ASSOCIATION ID  . . .   7
       3.1.2.  IPv6 B-SFRR-Ready IPv6 Extended ASSOCIATION ID  . . .   8
IPv4 and IPv6 appear twice. Not sure the second is needed.

You leave unspecified how to set the Global Association Source of Extended
ASSOCIATION object. If it is as in 6780 then I suggest to explicitly say it.
Indeed you explicitly refer to 4872 for the three other fields.

It might be a stupid thing to do, but the text is not clear on whether an IPv4
B-SFRR-Ready Extended ASSOCIATION ID can be added as the Extended Association
ID of an IPv6 Extended ASSOCIATION object and vice versa. Text is clear for
B-SFRR-Active however.

Why the MP does the test on the Bypass_Destination_Address:
   When forwarding an RSVP Path message downstream, the MP SHOULD remove
   any/all B-SFRR-Ready Extended ASSOCIATION object(s) whose Association
   ID contains Bypass_Destination_Address matching the MP node address.
while the PLR does it on the association source (and not on the
Bypass_Source_Address):
   Note, when forwarding an RSVP Resv message upstream, the PLR node
   SHOULD remove any/all B-SFRR-Ready Extended ASSOCIATION objects whose
   Association Source matches the PLR node address.

By the way, Bypass_Destination_Address does not exist per se in your spec, only
Bypass_Destination_IPv4_Address and Bypass_Destination_IPv6_Address

   The RSVP_HOP_Object field in the B-SFRR-Active Extended ASSOCIATION
   ID is set to the common RSVP_HOP that was used by the PLR in
   Section 3.3 of this document.
There is no mention of RSVP_HOP in Section 3.3