@kitz
Those numbers started to do my head in! I couldn't work out how they could manage B=0 ... because that would imply that the entire frame was overhead.
If I try to read them logically, it seems to be saying
B=0 -> zero bytes in MUX data frame
M=2 -> two MUX data frames in RS codeword
R=16 -> sixteen bytes of parity overhead in RS codeword
N=32 -> thirty two bytes in an RS codeword
Would this be
a) N = R + (M*B)
or
b) N = M * (R+B)
Using the English language, I'd assume (a) was more correct. But (b) appears to pan out in real use. I guess these framing parameters are from Bearer 1. Perhaps the rules are slightly different there.
But back in bearer 0, with N=B+R+1, I couldn't honestly figure out why the "+1" should be there.
More thinking needed. I suspect I'll feel the need to dig out the spec again. I recall from last time that G.INP tied the base VDSL2 spec down to using more limited framing options.
Although I have this information listed on the linestat errors page, because of the alphabetical layout, it perhaps doesnt make it quite so clear the relationship between those particular figures.
On reflection and after seeing wombats post, it may be a good idea for me to also add this on the interleaving page, where its not lost amongst other things like LoF or LoS.
I can see that it would be useful to see that relationship, at least for those wanting to dive into the depths.