IETF Logo Mail Archive

Re: [mpls] [Technical Errata Reported] RFC3107 (4497)

Ross Callon <rcallon@juniper.net> Mon, 19 October 2015 17:52 UTC

Return-Path: <rcallon@juniper.net>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E7BA1A9069 for <mpls@ietfa.amsl.com>; Mon, 19 Oct 2015 10:52:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uVO15QfJFULn for <mpls@ietfa.amsl.com>; Mon, 19 Oct 2015 10:52:53 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0107.outbound.protection.outlook.com [207.46.100.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1BFB1A6FBF for <mpls@ietf.org>; Mon, 19 Oct 2015 10:52:51 -0700 (PDT)
Received: from DM2PR05MB573.namprd05.prod.outlook.com (10.141.159.16) by CY1PR0501MB2010.namprd05.prod.outlook.com (10.164.2.28) with Microsoft SMTP Server (TLS) id 15.1.300.14; Mon, 19 Oct 2015 17:52:49 +0000
Received: from DM2PR05MB573.namprd05.prod.outlook.com ([10.141.159.16]) by DM2PR05MB573.namprd05.prod.outlook.com ([10.141.159.16]) with mapi id 15.01.0300.010; Mon, 19 Oct 2015 17:52:49 +0000
From: Ross Callon <rcallon@juniper.net>
To: Loa Andersson <loa@pi.nu>, Eric Rosen <erosen@juniper.net>, Martin Vigoureux <martin.vigoureux@alcatel-lucent.com>, RFC Errata System <rfc-editor@rfc-editor.org>, "akatlas@gmail.com" <akatlas@gmail.com>, "db3546@att.com" <db3546@att.com>, "aretana@cisco.com" <aretana@cisco.com>, "swallow@cisco.com" <swallow@cisco.com>
Thread-Topic: [mpls] [Technical Errata Reported] RFC3107 (4497)
Thread-Index: AQHRBfsys01n9sNOwUGc8tunRW5RUZ5qtUqAgAAy3ICAA6QyAIAAnUSAgAPz9PA=
Date: Mon, 19 Oct 2015 17:52:49 +0000
Message-ID: <DM2PR05MB573CC1E441903926743E42DA53A0@DM2PR05MB573.namprd05.prod.outlook.com>
References: <20151013210728.27DF9187E28@rfc-editor.org> <561E1CC9.7080600@pi.nu> <561E4773.1090904@alcatel-lucent.com> <5621556E.1000600@juniper.net> <5621D95B.8090209@pi.nu>
In-Reply-To: <5621D95B.8090209@pi.nu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=rcallon@juniper.net;
x-originating-ip: [66.129.241.13]
x-microsoft-exchange-diagnostics: 1; CY1PR0501MB2010; 5:M4cMgwk9lndtgQVDQsLY4Z63Upfb3aJmIwSBkvwz2hyir6vbDMVOlZoeX0qAVDfyggW+N9VP6e6jjtkuXY8FyCjLDTxT1GkGB05LQYyCwhKPUXI9ITM7gE/H9cKNt6qsKSPpZy4xQAU9LWeuLiAktA==; 24:gtY/hMDQNh8zbQ3AoyajQourkTOj2NBb8nPgVWby9/UQS2m4fjAjLQYgu2IxIATjgqj13mfSrwRTgT0xoeo5+PuV0ttw5uvF/xQYQVd0aao=; 20:wac8qDLlB76zUOt98dp3NgJJp7Dt9FXI02z48RLehioMfgbsHECAaeqFP4CwghVqxkRiGaZhK2G2DbFcBoO9Eg==
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:CY1PR0501MB2010;
x-microsoft-antispam-prvs: <CY1PR0501MB2010DA5C7C8C4B71A59DC285A53A0@CY1PR0501MB2010.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(97927398514766)(95692535739014)(202767206196957);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(8121501046)(5005006)(520078)(3002001); SRVR:CY1PR0501MB2010; BCL:0; PCL:0; RULEID:; SRVR:CY1PR0501MB2010;
x-forefront-prvs: 07349BFAD2
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(377454003)(51444003)(189002)(377424004)(199003)(13464003)(479174004)(24454002)(77096005)(2201001)(5002640100001)(5008740100001)(33656002)(1941001)(11100500001)(86362001)(19580395003)(106356001)(76176999)(81156007)(106116001)(99286002)(2501003)(105586002)(10400500002)(50986999)(97736004)(5007970100001)(101416001)(19580405001)(87936001)(54356999)(92566002)(46102003)(93886004)(4001150100001)(5001770100001)(102836002)(189998001)(64706001)(2950100001)(5003600100002)(74316001)(66066001)(76576001)(40100003)(122556002)(2900100001)(5004730100002)(5001960100002); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR0501MB2010; H:DM2PR05MB573.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Oct 2015 17:52:49.6697 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0501MB2010
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/yAvfsmvcz51cFbr4OzWmr7S_DrI>
Cc: "alexander.okonnikov@gmail.com" <alexander.okonnikov@gmail.com>, "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] [Technical Errata Reported] RFC3107 (4497)
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 19 Oct 2015 17:52:54 -0000

Referring to the errata updating the reference: I think that at the time that RFC 3107 was published the reference to 2283 was wrong both because 2283 had already been updated, and because there is no actual reference to 2283 in the references section. The errata is therefore correct. The problem that I have with "hold for document update" is that by now, and therefore by the time (if any) that we update 3107, the errata will also be out of date. 

My inclination is to think that at the time that 3107 was published the errata was correct, and thus we should accept it. 

Ross

-----Original Message-----
From: Loa Andersson [mailto:loa@pi.nu] 
Sent: Saturday, October 17, 2015 1:15 AM
To: Eric Rosen; Martin Vigoureux; RFC Errata System; akatlas@gmail.com; db3546@att.com; aretana@cisco.com; swallow@cisco.com; Ross Callon
Cc: alexander.okonnikov@gmail.com; mpls@ietf.org
Subject: Re: [mpls] [Technical Errata Reported] RFC3107 (4497)

Eric,

On 2015-10-17 03:52, Eric C Rosen wrote:
> On 10/14/2015 8:15 AM, Martin Vigoureux wrote:
>> I think we should stick to changing [RFC 2283] into [BGP-MP]. Otherwise
>> it could open the door to creating erratas for any reference that would
>> have been updated/obsoleted.
>
> Of course, one could also ask whether it is worthwhile to accept an
> erratum that changes one obsolete reference to another.  Whether one
> looks in the RFC index for RFC2283 or for RFC2858, one will eventually
> follow the change of tags to RFC4760.

I take this to mean "Accept - hold for a potential 3107bis", right?

/Loa
>

v2.23.0 | Report a Bug | By Email