Re: [Teas-ns-dt] Traffic (address?) type information

Eric,

The answer is as usual - it depends.
If the service provided is protocol aware and mapping is 1:1 (L3VPN/EVPN/VPLS/VPWS) then traffic type must be communicated and must match.
Example:
Routed service: L3VPN - CE-PE traffic type must match for a service to work, e.g IPv4 for IPv4 L3VPN and IPv6 for IPv6 L3VPN
Bridged service: L2VPN - same here, a match is mandatory for the service to work, hence we signal end point semantics.

However if the service is protocol unaware (typically would be a low(er) layer),  optical service doesn’t care about what kind of traffic it transports, L2VPN in general doesn’t care whether it is IPv4 or IPv6, etc

Cheers,
Jeff
On Jun 1, 2020, 8:59 AM -0700, Eric Gray <eric.gray=40ericsson.com@dmarc.ietf.org>rg>, wrote:
> On the question of possibly including the traffic types (IPv4, IPv6, Ethernet, unstructured) as an additional parameter of a Transport Slice service:
>
> I guess I really need to ask this question, first:
>
> Under what circumstances would this information not be explicitly known in advance by whatever higher-level entity it is that is making the request (via the TSC NBI) for a transport slice service?
>
> If the higher-level entity does not know what the available capabilities are for making transport slice service requests (i.e. – what connection points are available, how those connection points are to be reached, what PDU format they are capable of handling, etc.), it is likely that this higher-level will need to make arbitrarily many requests before arriving at a combination that works (i.e. – the NBI interaction results in success), as it goes through an iterative “guessing” process.
>
> It may be that there are multiple ways of doing this, but I believe it is likely to be the common case that traffic is expected to arrive at a transport slice service ingress with a specifically defined format and encapsulation that allows that ingress logical device to determine to which transport slice that traffic applies.  Further, I also believe it very likely that the payload (at least) of the received traffic is expected to be delivered via the transport slice service (exactly as is) to the transport slice service egress.
>
> Are these assumption incorrect?
>
> --
> Teas-ns-dt mailing list
> Teas-ns-dt@ietf.org
> https://www.ietf.org/mailman/listinfo/teas-ns-dt