| |
Comment: |
There seems agreement on the above, and the intention.
There seems disagreement on the current practical implementation in syntax.
Note: resource labels are used for two distinct purposes: for identification of channels (sub-Links) in a Link, and for flow forwarding (e.g. "data of
VLAN 42 of interface 1/2 is forwarded to VLAN 18 of interface 0/3").
You can implement source and destination with either of the above in mind. E.g. assume a port at a router. Is that modelled as the possible IP flows
through that port, or as the IP address of that port. Note that a port in a router in fact does not need an IP address to forward traffic (although it
is used by ICMP). How to model a IP Port without an IP address? For this reason, Freek modelled it as the flows through that Port, which can
efficiently be done using a PortGroup.
Freek needs to create a more formal proposal. There are no clear counter proposals.
|
