Re: [mpls] WG consensus check: RFC 7506 (IPv6 Router Alert Option) to historic

[Toerless Eckert <[e-mail]>]

The way the question is asked (without any text about the conditions under which this is done), i can only say "no".

The reason is that i would not want to see something moved to historic without an RFC solution to replace it.

Now i imagine that the current plan is (because thats not mentioned in the consensus call),
to make draft-ietf-mpls-lspping-norao update RFC8029 in a way that it eliminates the need
for router-alert for both IPv4 and IPv6 in the RFC8029 mechanisms. And that draft already
talks about having made RFC7506 historic.

So, if that is the implied plan for making RFC7506 historic, then i will not say No. But not Yes either.

For a Yes, i would really need to see an RFC8029bis that removed the router-alert text as instructed
by draft-ietf-mpls-lspping-norao. draft-ietf-mpls-lspping-norao itself would only need to be changed to
not ask for the update to RFC8029 anymore, but could easer be the process document defining the
retirement of RFC7506.

In other words: I really don't think the job is nicely done as long as future implementers of MPLS OAM
need to read through router-alert text in RFC8029 AND then the "ignore/replace" the router-alert text
in draft-ietf-mpls-lspping-norao, and apply the instructions from that doc themselves correctly - every
implementer by themself.

Cheers
    Toerless

On Tue, Apr 02, 2024 at 10:00:55AM -0700, Tony Li wrote:
> 
> [WG chair hat: on]
> 
> 
> Hi all,
> 
> It has been proposed that we transition RFC 7506, "IPv6 Router Alert Option for MPLS Operations, Administration, and Maintenance (OAM)” to Historic.
> 
> This note starts a two-week consensus check on this change. Please reply-all with: 
> 
> 	“Yes, I support moving RFC 7506 to Historic”
> 
> or
> 
> 	“No, I do not support moving RFC 7506 to Historic”
> 
> This poll will close at 12:01 PM PDT 16 Apr 2024.
> 
> Thanks,
> Tony
> 
> _______________________________________________
> mpls mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/mpls