Re: [mpls] Last call on tidying up Expired MPLS WG I-Ds

[Stewart Bryant <[e-mail]>]

> 
> 
> https://datatracker.ietf.org/doc/draft-ietf-mpls-opportunistic-encrypt-03 
> Opportunistic Security in MPLS Networks

This draft has been referenced a number of times number of times in MPLS security discussions.

Maybe making it historic would be more appropriate.

========
> 
> 
> 
> 
> https://datatracker.ietf.org/doc/draft-ietf-mpls-tp-ach-tlv-02 
> Definition of ACH TLV Structure

There is an irony in the MNA work with this one. 

In the TP work we depreciated the ACH TLVso the draft can be made dead, however I wonder if the MNA work will hake us back here?

Maybe leave it in code storage for a bit longer.

=========

> 
> https://datatracker.ietf.org/doc/draft-ietf-mpls-tp-process-05 
> IETF Multi-Protocol Label Switching (MPLS) Transport Profile (MPLS-TP)
> Document Process

I am sure that that one is dead an can be buried.

==========

> 
> 
> https://datatracker.ietf.org/doc/draft-ietf-mpls-framework-05 
> A Framework for MPLS

I would argue that this draft needs to be completed. One thing that is missing in many 
MPLS discussions is an understanding of the foundations of the protocol and a thorough 
Understanding of the consequences of change.

I was trying to capture some of this in draft-bryant-mpls-dev-primer-02 written in the early days of the MNA project.

I am taken by this text extract in the light of SR.

1.5.1.2 Efficient Explicit Routing

Explicit routing (aka Source Routing) is a very powerful technique
which potentially can be useful for a variety of purposes.
However, with pure datagram routing the overhead of carrying a
complete explicit route with each packet is prohibitive. However,
MPLS allows the explicit route to be carried only at the time that
the label switched path is set up, and not with each packet. This
implies that MPLS makes explicit routing practical. This in turn
implies that MPLS can make possible a number of advanced routing
features which depend upon explicit routing.

- Stewart