[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[dccp] milestone updates
Hi,
during the Paris meeting, we proposed to update our milestones as
summarized below. Please send comments to the list. Assuming the WG
agrees, we'll initiate the milestone update process in a few days.
November 2005: complete WGLC draft-ietf-dccp-problem-xx as Informational
November 2005: complete WGLC draft-ietf-dccp-tfrc-media-xx as
Informational
June 2006: complete WGLC draft-ietf-dccp-user-guide-xx as
Informational (or BCP?)
June 2006: complete WGLC draft-ietf-dccp-tfrc-voip-xx as Experimental
June 2006: complete WGLC draft-ietf-dccp-tfrc-faster-restart-xx as
Experimental
Proceedings of the WG meeting will be available soon, here are some
initial notes to go with the milestone update:
draft-ietf-dccp-problem-xx is already in WGLC, which we'll end as
soon as the final revision appears.
draft-ietf-dccp-tfrc-media-xx requires a bit more work to address the
comments brought up during the presentation in Paris.
For draft-ietf-dccp-user-guide-xx, we'd like to update it based on
implementation experience. Implementors should take a look and
coordinate with Tom.
draft-ietf-dccp-tfrc-voip-xx and draft-ietf-dccp-tfrc-faster-restart-
xx are relatively stable. The goal is to make them "Experimental" in
the sense that people have a stable spec to actually experiment with
the mechanisms, being very clear that we (currently) don't feel they
are safe for widespread deployment. It'd be great if implementations
that have otherwise stabilized would start to check if and how they
can implement these variants, to allow researchers to play with them
on the real network.
Comments?
Lars
--
Lars Eggert NEC Network Laboratories
Attachment:
smime.p7s
Description: S/MIME cryptographic signature