RFC3276 respin
Bob Ray <[email protected]>
| Newsgroups | gmane.ietf.adslmib |
|---|---|
| Message-ID | <[email protected]> |
If ("IF") there were another spin on RFC3276, then, would the following
list of changes suffice to support g.shdsl.bis (from Clay's list)?
1. Hdsl2ShdslWirePair TC - add wirePair3(3) and wirePair4(4)
2. hdsl2ShdslSpanConfWireInterface - add sixWire(3) and eightWire(4)
3. hdsl2ShdslStatusMaxAttainableLineRate - remove the range limit
4. hdsl2ShdslStatusActualLineRate - remove the range limit
5. hdsl2ShdslSpanConfMinLineRate - remove the range limit
6. hdsl2ShdslSpanConfMaxLineRate - remove the range limit
Would these do it? Would this be all? Would this break any existing
implementations (at least of embedded agents)? Would the above break
any management apps?
It doesn't look like it would - it sure looks like any new devices
would simply have a "looser" range of values in 5 objects.
--
Bob Ray <[email protected]>