Re: [mpls] [Technical Errata Reported] RFC3031 (5643)

Precisely, I was going to say the same thing but I’m sure Adrian said it better.
Acee

From: mpls <mpls-bounces@ietf.org> on behalf of Adrian Farrel <adrian@olddog.co.uk>
Organization: Old Dog Consulting
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
Date: Monday, February 25, 2019 at 12:56 PM
To: "'Andrew G. Malis'" <agmalis@gmail.com>, 'RFC Errata System' <rfc-editor@rfc-editor.org>
Cc: Ross Callon <rcallon@juniper.net>, 'mpls' <mpls@ietf.org>, "erosen@cisco.com" <erosen@cisco.com>, "markzzzsmith@gmail.com" <markzzzsmith@gmail.com>, "arun@force10networks.com" <arun@force10networks.com>
Subject: Re: [mpls] [Technical Errata Reported] RFC3031 (5643)

3031 does define “MPLS edge node”, “MPLS egress node”, and “MPLS ingress node”. Of course, it also defines “LSR”.

As Andy says, the first mention of LER is in 3811 and it looks like the terminology was produced to solidify the definitions in 3031.

I don’t think it is an “error” in 3031 that it doesn’t define LER. Sure, it would be nice to have all the definitions in one place, but adding stuff to documents isn’t what Errata Reports are supposed to be for.

Adrian

From: mpls <mpls-bounces@ietf.org> On Behalf Of Andrew G. Malis
Sent: 25 February 2019 15:36
To: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: mpls <mpls@ietf.org>; markzzzsmith@gmail.com; arun@force10networks.com; Ross Callon <rcallon@juniper.net>; erosen@cisco.com
Subject: Re: [mpls] [Technical Errata Reported] RFC3031 (5643)

The submitter does make a good point, LER should probably be defined in the MPLS architecture. I just did a search and the earliest mention of "Label Edge Router" that I could find is in RFC 3811.

That said, I think I prefer the definition text from RFC 4221:

   An LER is an LSR placed at the edge of an MPLS domain, and it passes

   traffic into and out of the MPLS domain.  An ingress LER is

   responsible for classifying data and assigning it to a suitable LSP

   or tunnel.

   This classification is done using Forwarding Equivalence Classes

   (FECs) that define the common attributes of data (usually packets)

   that will be treated in the same way.  Once data has been classified,

   it can be handed off to an LSP or tunnel through the Next Hop Label

   Forwarding Entry (NHLFE).
Cheers,
Andy

On Sun, Feb 24, 2019 at 8:23 PM RFC Errata System <rfc-editor@rfc-editor.org<mailto:rfc-editor@rfc-editor.org>> wrote:
The following errata report has been submitted for RFC3031,
"Multiprotocol Label Switching Architecture".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata/eid5643

--------------------------------------
Type: Technical
Reported by: Mark Smith <markzzzsmith@gmail.com<mailto:markzzzsmith@gmail.com>>

Section: Terminology

Original Text
-------------
<missing>

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.

Notes
-----
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.

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party
can log in to change the status and edit the report, if necessary.

--------------------------------------
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

_______________________________________________
mpls mailing list
mpls@ietf.org<mailto:mpls@ietf.org>
https://www.ietf.org/mailman/listinfo/mpls