[mpls] [Errata Rejected] RFC3031 (5643)

RFC Errata System <rfc-editor@rfc-editor.org> Thu, 30 May 2019 21:16 UTC

Return-Path: <wwwrun@rfc-editor.org>
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 75E87120176; Thu, 30 May 2019 14:16:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id g739uEE9x2Po; Thu, 30 May 2019 14:16:38 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8BE71200E3; Thu, 30 May 2019 14:16:37 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id BDFBAB81FD8; Thu, 30 May 2019 14:16:33 -0700 (PDT)
To: markzzzsmith@gmail.com, erosen@cisco.com, arun@force10networks.com, rcallon@juniper.net
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: db3546@att.com, iesg@ietf.org, mpls@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20190530211633.BDFBAB81FD8@rfc-editor.org>
Date: Thu, 30 May 2019 14:16:33 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/wLsGMLdkq4myIQc601LuMIwMniQ>
Subject: [mpls] [Errata Rejected] RFC3031 (5643)
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 30 May 2019 21:16:40 -0000

The following errata report has been rejected for RFC3031,
"Multiprotocol Label Switching Architecture".

You may review the report below and at:

Status: Rejected
Type: Technical

Reported by: Mark Smith <markzzzsmith@gmail.com>
Date Reported: 2019-02-25
Rejected by: Deborah Brungard (IESG)

Section: Terminology

Original Text

Corrected Text
label edge router - a router capable of accepting an unlabelled packet,
and through MPLS processing, may MPLS encapsulate the packet by adding
 a label stack. 

I am doing some MPLS review.

The book I'm using said an LER was an (RFC3031) MPLS edge node. I believed it was any router that could take unlabelled packets and label them, regardless of where the router was within the MPLS domain. (In other words, an MPLS router was not an LER if it would not MPLS label unlabelled packets and forward them.)

I decided to check RFC3031 for a definition, and discovered there isn't a definition at all for "label edge router", or a match on any text that matches "label edge" or "LER".

RFC6178 clarifies LER processing of IPv4 packets, and the general description of processing matches my understanding of what an LER is. 

However, it doesn't formally define an "label edge router" either, and I think an update to RFC3031 should be where "label edge router" is formally defined.
This is not an error with RFC3031. It is inappropriate to use an Errata Report to add a new term to an RFC.

RFC3031 (draft-ietf-mpls-arch-06)
Title               : Multiprotocol Label Switching Architecture
Publication Date    : January 2001
Author(s)           : E. Rosen, A. Viswanathan, R. Callon
Category            : PROPOSED STANDARD
Source              : Multiprotocol Label Switching
Area                : Routing
Stream              : IETF
Verifying Party     : IESG