[mpls] Help with Erratum on RFC 3815

Adrian Farrel <Adrian.Farrel@huawei.com> Sat, 21 August 2010 14:15 UTC

Return-Path: <Adrian.Farrel@huawei.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C9AC63A6803 for <mpls@core3.amsl.com>; Sat, 21 Aug 2010 07:15:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.394
X-Spam-Level:
X-Spam-Status: No, score=-102.394 tagged_above=-999 required=5 tests=[AWL=0.204, BAYES_00=-2.599, STOX_REPLY_TYPE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ak9GlXWhF-FC for <mpls@core3.amsl.com>; Sat, 21 Aug 2010 07:15:46 -0700 (PDT)
Received: from usaga01-in.huawei.com (usaga01-in.huawei.com [206.16.17.211]) by core3.amsl.com (Postfix) with ESMTP id 70D9E3A6768 for <mpls@ietf.org>; Sat, 21 Aug 2010 07:15:45 -0700 (PDT)
Received: from huawei.com (usaga01-in [172.18.4.6]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L7I00IM3AB758@usaga01-in.huawei.com> for mpls@ietf.org; Sat, 21 Aug 2010 07:16:19 -0700 (PDT)
Received: from your029b8cecfe (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L7I00NMGAAU1D@usaga01-in.huawei.com> for mpls@ietf.org; Sat, 21 Aug 2010 07:16:19 -0700 (PDT)
Date: Sat, 21 Aug 2010 15:15:51 +0100
From: Adrian Farrel <Adrian.Farrel@huawei.com>
To: mpls@ietf.org
Message-id: <86953191102B4FD69C8894FBFBA76D25@your029b8cecfe>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5931
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="original"
Content-transfer-encoding: 7bit
X-Priority: 3
X-MSMail-priority: Normal
Cc: Hans Sjöstrand <hans@ipunplugged.com>, mibs@ops.ietf.org, james_luciani@mindspring.com
Subject: [mpls] Help with Erratum on RFC 3815
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Adrian Farrel <Adrian.Farrel@huawei.com>
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sat, 21 Aug 2010 14:15:47 -0000

Hi,

Erratum 227 at http://www.rfc-editor.org/errata_search.php?eid=227 points 
out a real issue.

But I am not sure if it needs to be fixed or whether a resolution introduces 
a backwards compatibility issue.

Does it matter that the order of objects in the SEQUENCE do not match the 
order of the OIDs? Is there a need to reorder anything:
- the objects in the SEQUENCE
- the OIDs assigned.

I suspect that, although the current state of the module is "unusual", no 
fix is actually required.

Thanks for any thoughts.

Adrian