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
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-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 th=
at 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 th=
at 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.=
=20

My inclination is to think that at the time that 3107 was published the err=
ata was correct, and thus we should accept it.=20

Ross

-----Original Message-----
From: Loa Andersson [mailto:loa@pi.nu]=20
Sent: Saturday, October 17, 2015 1:15 AM
To: Eric Rosen; Martin Vigoureux; RFC Errata System; akatlas@gmail.com; db3=
546@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
>