TFRC.bis is a maintainance version of TFRC, to correct the TFRC
specification and will obsolete it when published. The stated milestone
date is July 2007 - my notes show this is currently pending inputs from
implementors (please do contribute to this within the WG).
As such, any current work that will be published after TFRC.bis MUST
refer to TFRC.bis, and it would certainly be wise to consider this as
the basis for all DCCP I-Ds.
However, DCCP CCID currently relies on RFC3448 (TFRC). As I see it,
section 3.1 states how this dependency should be managed. I am not clear
from reading this how an update of the TFRC base spec needs to be
treated, is that what you are asking? I note that there are other issues
that also need to be addressed in CCID-3.
Gorry
Eddie Kohler wrote:
I hope Sally and/or Mark speak up here. I'm not sure whether RFC3448bis
is considered in its early stages, or should be implemented right away,
or what....
Eddie
Arjuna Sathiaseelan wrote:
Eddie:
Ok I get it now..My entire arguments (hence the confusion )were based
on RFC3448-bis and not RFC3448...I was raising points from the
RFC3448-bis draft under the presumption that this draft obsoletes
rfc3448 when it comes to implementing in ns-2..
Arjuna
<snip>
