Beginners Guide to TikTok for Search - Rachel Pearson - We are Tilt __ Bright...
Scaffold
1. Current Internet Architecture Application Socket (local) IP Address MAC Address URL, MAC and IP Point to the same place
2. U X ServiceID p r Socket Identifier Host Address HostID A B MAC Address 1 4 1 3
3. B U ServiceID Socket Identifier r p X A Z Host Address CCC BBB AAA ID = ServiceID:SocketID:HostAdd
4. B U ServiceID Socket Identifier r p 12 11 Node Address X A Z Host Address CCC BBB AAA ID = ServiceID:SocketID:NodeAddr ` Network Layer Network Layer Sub-Network Layer Sub-Network Layer
Notas del editor
Saltzers model
Socket Identifier is a ServiceID instance.
Lets use a multi-homed host as the canonical model. In this case you have multiple POA’sServiceID = Application NameSockID = Application InstanceScaffold maps the application name (ServiceID) to the host addressWhere is the “internetwork definition” if Saltzer defined networks..Routes are sequences of nodesHow do we map the next-hop address to the point of attachment of which there can be more than one.Routing is relative to the layer.. NextHop is the lookup in the successive layer. ServiceID Maps to HostAddr and Host addr maps to what? Host Addr and POA are still the same.Is a host address unambiguous within its layer?In the implementation you are concatenating different layers in the same address. This seems to be very bad.. It is a singe path through the layers as opposed to you independent.Since the POA and the HostAddr are coupled, you need to invalidate the record in both the source and the destination and build a new connection record. The application is transparent to this through the power of the application abstraction (ServiceID) but the dataplane needs to be rewritten. There maybe scalability issues when this is a 1:1000 mapping.
If you have the Node Address, the assumption is that the only invalidation is at the sub-network layer, completely insulating the host stack from an interface transition (i.e. failure)