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 end user self-determination. - For this omission, a workaround will be possible when Segment Routing is incorporated into Quagga and everyone installs Quagga on their Computers.
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.
Wavelength Division Multiplexing provides the benefit of being able to increase the utilisation of an expensive duplex-pair of optical fibres by way of a Multiplexing Splitter, and a Demultiplexing Splitter and Wavelength Filters. - Its advantage is also its disadvantage which is fate-sharing.
- By combining WDM with TRansparent Interconnection of Lots of Links the fate-sharing can be disseminated by the wavelengths reported by the pluggable modules installed into the Bridge, as duplicate wavelengths cannot be connected to the same WDM splitter. At the other end of the link TRILL will be able to determine which interfaces share fate by the RBridge Nickname contained in Protocol Data Units. The gain is in the knowledge of confirming that the interfaces of the TRILL Switches are patched to the intended Multiplexer and Demultiplexer.
The WDM RBridge needs to be available to the mass-market coinciding with the SFP56 reaching economic critical-mass, to take advantage of PAM-4(Pulse-Amplitude Modulation 22) which will enable operating in a coherent spectrum with a denser channel spacing than legacy CWDM. These WDM RBridges could be implemented with such simplicity that it would facilitate the ability of the near-end and far-end WDM RBridges being owned and operated by different entities. — The WDM RBridge could become the customary means by which entities interconnect at various scales of SFP56 and SFP112 occupancy, by the ability of an arbitrary topology and a variable number of multiplexing and filtered-demultiplexing splitter pairs.
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. The success of Ethernet is evidential by it outlasting Plesiochronous Digital Hierarchy and Synchronous Digital Hierarchy which have subrates and tributaries.
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 a source to the group address at any time.
Specifying that a network has a backbone, core, edge or trunk, while the technologies in use do not impose a hierarchy. This nomenclature should not be promulgated as it is a personal construct to abstract a portion of the network.
Referring to a Computer as something other than an End System, such as a Client or Server. End Systems are not architecturally limited to any role.
Using Open Systems Interconnection, especially X.200 the 7 layer model, as a teaching or troubleshooting aid for technologies which were not devised in or with the organisation.
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. Had ATM of been targeted as the Connection Oriented Network Service replacement for Data Circuit-terminating Equipment in X.25 and X.75, ConnectionLess Network Protocol could have supplanted the Internet Protocol. Since circa 1996 label switching has become a means for an entity to provide private interconnection(backhaul in archaic lexicon) 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 – 126.96.36.199 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, the MTU of all links for each End System, 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.
- Datagram service would pop each link-label on ingress and pop each host-label on egress — if the label becomes unknown the PDU is dropped.
A reliable service would keep all labels intact and would indicate whether the label is traversing in the forward or reverse direction — if a succeeding labelled-link is down an indicator bit is flipped so that the label is then delivered to the source host — if during the reverse journey the label cannot return to the preceding label the PDU is dropped. [This theory is too simplistic as there is not a means for the source host to know at which label the PDU could not proceed] The label space would need to include an additional 1 bit field for each label to indicate at which label the PDU could not proceed, alternatively there could be a 10 [sufficiently sized to accommodate the diameter of the future Internet] bit field [the most significant bit is for the direction] akin to a hop limit that is decremented only in the forward direction per label and never incremented. - Both approaches can be the method of signifying that these labels are not a datagram service.
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.
MPLS remains intangible for many and despite 'Encapsulating MPLS in IP or Generic Routing Encapsulation (GRE)' (RFC 4023), March 2005 and 'Encapsulation of MPLS over Layer 2 Tunneling Protocol Version 3' (RFC 4817), March 2007, IPinIP and IPinGRE have instead prevailed.
Regarding Overlay Networks, since the IANA exhaustion of IPv4 there has been a shift from connecting IPv6 islands with IPinIP and IPinGRE, to the connecting of Ethernets by way of L2TPv3 PWE3, and more recently VXLAN, this growth is in part due to the larger host address space of IPv6, and will accelerate coinciding with the availability of TRILL RBridges.
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.
- VLANs are near the end of their useful life, the predominant usage is to facilitate an Ethernet interface to have more than one unicast IP address, in this situation it is one IPv4 address per broadcast domain. With IPv6 being the present Internet and IPv6 allowing more than one unicast address per physical interface, a pseudo-private LAN can be accomplished by using the Unique Local Address fd00::/8 block and dividing it into fd00::/64.
When I transitioned from academia to industry I noticed differences and similarities between Computer Networks and Telecommunications Networks — some are obvious, many were not
Telecommunications Networks use Computer Networking technologies. The major holdout is Dense Wavelength Division Multiplexing requiring in-band management for amplification gain feedback and for regeneration passthrough.
Computer Networks have a single upfront expense [excluding the insourced or outsourced administrative expense and electricity], whereas Telecommunications Networks have a periodic expense [usually monthly] and may have an additional expense for setup.
Computer Networks are deliberately resilient because the users are not notified when a single interconnection is disconnected due to the use of TRansparent Interconnection of Lots of Links, or in antiquated networks the use of Spanning Tree Protocol and Link Aggregation Control Protocol.
Telecommunications Networks advise their customers [Change Management] of when a disconnection is planned, because the connectivity is being paid for and because the connectivity is most likely provided as a stub [spur in Carriers' vernacular] including the rare instances where LACP is used. Carriers are reliant upon the MTBF of their active equipment and the physical diversity of their passive equipment.
When Telecommunications Networks provide an Ethernet as a private interconnection, the carrier disables SNPA(SubNetwork Point of Attatchment) address learning, Spanning Tree Protocol, Link Layer Discovery Protocol and other protocols to make the Ethernet appear transparent to the customer, as no frames are present when the customer's equipment is not connected, to ensure that the customer's equipment is unable to communicate with the carrier's equipment.
Computer Networks do not hobble the speed of network interfaces, whereas Telecommunications Networks can limit the interface throughput to be less than the native speed to facilitate an additional revenue stream and because it is physically and economically infeasible to provide a fat-tree between their customer's locations. One method of an additional revenue stream is to install a piece of equipment [NTD in ISDN parlance] at the customer's premises to deliver different private interconnections from each interface, where one of could be connectivity to the Internet.
The Metro Ethernet Forum exists solely for Telecommunications Networks to be able to outsource to other carriers the provision of private interconnection of their customer's Computer Networks in locations that they are unable to economically serve, in this instance they outsource to another carrier whom they interconnect [Point of Interconnect] with and it is this interconnection method that the Metro Ethernet Forum standardises. It is to be noted that MEF themselves are not a standalone technology standards body. In instances where there is a dominant Carrier in a location, the MEF will be redundant, as it is the preeminent party who will dictate how the private interconnection is to occur. Additionally, do not confuse the Metro Ethernet Forum with Metropolitan Ethernet implementations of ITU-T Automatic Protection Switching G.8032/Y.1344 Ethernet Protection Ring Switching.
In Computer Networks each user sets up their own tunnels by means such as IPsec or WireGuard, whereas Telecommunications Networks provide a method for the administrator of the Computer Network to setup tunnels across the carrier's network using the so called 'SD-WAN' to create such tunnels as pseudowires over L2TPv3 or MPLS. - If the administrator of the Computer Network is proficient, they can obviate SD-WAN by creating tunnels between their disjoint equipment by bridging the physical interfaces and logical tunnel interface of their RBridges by such means as L2TPv3 or VXLAN.