Question 1: Does packet replication work with single access circuit by replicating packet and forwarding in the same path?
Answer:
Packet replication does not work with single access circuit. Packet replication is generally used for lossy links, if we allow packet replication on already congested link then it will not be useful.
Question 2: How is FEC better than packet re-transmission as even in FEC destination FlexVNF regenerates lost packet ?
For UDP traffic (RTP: Audio and Video) there is no re-transmission from sender and any packet lost will be seen as distorted video or audio at receiving end. FEC regeneration help as end host does not see packet loss.
For TCP sender can retransmit packet but packet loss will indicate congestion and window will be reduced which will impact the throughput/performance. With FEC regeneration, sender will not see a loss and congestion will not be detected and hence end host will see better throughput.
3.When a CPE receives packets, how it differentiates between original and replicated packet? Whether sequence number of original and replicated packet remains same?
Original and replicated packets has same sequence number
4.If replication factor is 3 and there are 3 WAN interfaces, then whether all three WANs transmits packet by default? Requirement is to send original packet on one WAN, first duplicate packet on second WAN and second duplicate packet on third WAN. How can we achieve this?
Yes replication factor 3 will send first packet of one WAN and two copies respectively on other two WAN circuits.
5.For 50 Mbps bidirectional traffic with replication factor 2, what CPE model do you suggest.
Replication or FEC should be dependent on traffic conditions whether we are seeing packet loss or not. Based on the available bandwidth we can turn on replication (100% overhead) or FEC (25% overhead with 1 FEC per 4 packets, 50% overhead with duplicate-FEC-packet turn on).
6.For single tenant CPE, what is maximum VRF supported in 16.1R1 S3.1? In earlier discussion we got information that only 15 vrf per tenant is supported. If this limitation is still there in 16.1R1S3.1, in which release there is any plan to increase this number
We support 1016 routing-instances (It can be of type VRF or virtual-router). (Note- 8 are reserved out of 1024 for special purposes)
As of Today there is a limit of 64 VRF per tenant (not 15) because of the MPLS label limitation.