Border Gateway Protocol
There needs to be a standards compliant scheme to remove duplicate consecutive ASNs in the AS_SEQUENCE attribute, to undo the AS(s) prepended by administrative domains whom elected to manipulate the AS path. - Conversely there is not a need to remove duplicate consecutive ASNs in the AS_CONFED_SEQUENCE because that is within self-control.
More generally there has to be a way to un-mangle anything that a neighbour AS has done.

Referring to an Ethernet as being multiplexed due to the use of non-locally-significant VLAN tags. Multiplexing and demultiplexing does exist in non-DIX Ethernet by way of the 'Destination Service Access Point' and 'Source Service Access Point'.
Treating an Ethernet as if it were a Time Division Multiplexer because of a Bridge having Z interfaces with speed N, and N interfaces with speed Z.
Explaining IP multicast communication as being one-to-many by means of replication [implying that there can only be one transmitter and any number of receivers], when in fact the benefits are much greater, as it is many-to-many with any host able to be the source to the group at any time.
Specifying that a network has a core while the technologies in use do not impose a hierarchy.

Multi-Protocol Label Switching
The motivation for MPLS was as an alternative to IP longest prefix matching for Routers, with influence from the deficiencies of Asynchronous Transfer Mode and to 'show up' The ATM Forum. Since circa 1996 label switching has become a means for an entity to provide private interconnection of another organisation's incongruent network. As of this writing MPLS does not benefit the source or destination host in the administrative domain that has deployed it.
For MPLS to be useful it must be transitive beyond an AS and the label-space needs to be globally unique and without fiscal encumbrance. [Historic recurrence: 'A Framework for Multiprotocol Label Switching' (draft-ietf-mpls-framework-00), May 12, 1997 – Other Label Allocation Methods, paragraph Ⅱ]
To ensure the efficacy of MPLS the hosts would utilise source-based routing originating from the reliable flooding of a label representing the host itself and for each of its interfaces by a TLV from an equivalent of PNNI within the routing domain, for congruence these labels and the SPF graph would be conveyed via the IDRP/BGP between Autonomous Systems.
It is from the padding of IS-IS Hellos that the maximum MTU can be determined per link for the eventual calculation of whether the route is feasible. When the frame is to be populated with a payload the lowest denominator MTU is used.
With my proposal there is not a need for a 'resolution protocol' as each link-label is an EUI-64, for which an IPv6 Global Unicast Address by Stateless Address Autoconfiguration can be resolved to a hardware address and vice versa. The label that the host is to use for itself is equal to the numerically-lowest of its link-labels. - This is the only instance where duplicate labels do not signify a loop in the graph; This also infers that every host along with its numerically-lowest link must appear in the graph.
To future-proof MPLS will require that adequate bit fields are reserved for versioning, capability advertising and further extensibility, prior to any scale of deployment.

If an overlay network is desired at Open Systems Interconnection model pseudo-layer 2 ½ then we could go back to the future and deploy CLNP, with its benefits of ES-IS redirects and the need of a host to have only one address for all of its interfaces, by developing IPinCLNS.

Security Or Insecurity
You are compelled to due process in the jurisdiction that you are present and in the locale of every person, Intermediate System and End System you have an impact upon.
Before intercepting, altering, restricting or logging packets between End Systems, you must have consent from the user of the source address and the user of the destination address for every permutation of source to destination flow. When a user changes at either the source or destination host you must again be granted consent before intercepting, altering, restricting or logging their first packet.
If you do not heed the above, or be a vigilante, then you will suffer the consequences of due process.
When source-based routing or Segment Routing is made available a new paradigm will be possible during path computation, by the creation of an equivalent of the Wireless Regulatory Database containing the legal requirements of each country and jurisdiction, a route can be determined that takes into account bilateral accord with your locale and countries' laws that are conducive to your own.

Virtual Local Area Networks
It must be by volition of the user of an End System whether and which VLANs they participate in.
IEEE 802.1Q does not include a mechanism for an Ethernet Switch to signal to a host for permission to assign a VLAN to the port that the host is attached. In the case that the VLAN tag is transitive, subsequent Switches and hosts need to be permissive of the VLANs they receive by stripping all VLAN tags on ingress and then on egress being courteous to their LAN by transmitting all frames untagged.

All that is old is new again
Segment Routing, in particular SRv6, owes its existence to 'Source Demand Routing' (RFC 1940), May 1996; and 'Explicit Routing Protocol (ERP) for IPv6' (draft-ietf-sdr-erp-00), October 1994. Segment Routing like its ancestor makes the same mistake by not including End Systems and therefore preventing enduser self-determination. - For this omission, a workaround will be possible when Segment Routing is incorporated into Quagga and everyone installs Quagga on their Computers.

Jonathan Ferguson, Ubuntu Wiki, Musings,

JonathanFerguson/Musings (last edited 2018-02-18 08:39:43 by jonathan-ferguson)