Re: [mpls] Progressing Resolution of Erratum 2533 (RFC 5960)

Alexander Vainshtein <> Wed, 10 November 2010 07:44 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A26303A6824; Tue, 9 Nov 2010 23:44:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 26jzVgbEST5C; Tue, 9 Nov 2010 23:44:58 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 316783A68F8; Tue, 9 Nov 2010 23:44:57 -0800 (PST)
X-AuditID: 93eaf2e7-b7bfeae000006f4e-03-4cda4d953d64
Received: from ( []) by (Symantec Brightmail Gateway) with SMTP id 96.B6.28494.59D4ADC4; Wed, 10 Nov 2010 09:45:25 +0200 (IST)
Received: from ([]) by ([]) with mapi; Wed, 10 Nov 2010 09:46:43 +0200
From: Alexander Vainshtein <>
To: "" <>
Date: Wed, 10 Nov 2010 09:46:38 +0200
Thread-Topic: [mpls] Progressing Resolution of Erratum 2533 (RFC 5960)
Thread-Index: AcuAqkGWWLljIycMSaaDutg2dx6+TwAAQ/KA
Message-ID: <>
References: <0d0301cb80aa$4a9d75a0$dfd860e0$>
In-Reply-To: <0d0301cb80aa$4a9d75a0$dfd860e0$>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: AAAAAA==
Cc: "" <>, "" <>
Subject: Re: [mpls] Progressing Resolution of Erratum 2533 (RFC 5960)
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 10 Nov 2010 07:44:59 -0000

Sounds OK.
Lots of thanks for the clarification of the process.


-----Original Message-----
From: [] On Behalf Of Adrian Farrel
Sent: Wednesday, November 10, 2010 9:39 AM
Subject: [mpls] Progressing Resolution of Erratum 2533 (RFC 5960)


Thank you for your input and suggestions on this topic.

To be clear, we are not attempting to reach consensus on what change to make,
but I am listening to your individual opinions.

In deciding what Erratum to post, I will select a form of words that clarifies
the published RFC text, but which does not make a technical change. I intend to
reflect the consensus of the IETF that was demonstrated by the publication of
this document.

The Erratum process is intended to correct typographic or rendition issues that
produce Editorial or Technical issues in the published text. The process is not
intended to make technical changes or fixes. Such issues should be handled by
revising the work through the IETF consensus process. draft-ietf-mpls-tp-uni-nni
is a good example of how that is done.

Now, with regard to this particular Erratum.

It seems to me that there are two separate concerns.

The first concern is about identification of payloads. This is needed for a
range of reasons, and is a firm requirement in the existing text (and, indeed in
the MPLS architecture). However, it is noted that the identification may be
explicit or implicit. The text also notes that the use of explicit
identification of payload is a facilitator for demultiplexing multiplexed

The second concern is whether there is a requirement to support payload
multiplexing. I do not believe there is any statement about the support for
multiplexing in RFC 5960. The only mention of the subject is in the filed
Erratum. It would be wrong to introduce any statement of requirement or
non-requirement through an Erratum.

So, I'm not hearing anything that persuades me that the Erratum should be
different from what I wrote. If folk want to establish a specific requirement
that multiplexing is not required, then they can go ahead and write  a draft. I
cannot speak for how the WG will greet such a draft.


mpls mailing list