Hello Julian,
First of all, I need to apologize for this very late answer.
Many of your comments have already been addressed end of Feb. However
here are the few remaining open points. I wanted to let you know before updating
the document.
Section 3:
File name (usually, this can be
Hello Julian,
I note that draft-ietf-rmt-flute-revised is on the agenda. Just wanted
to note that I haven't seen any feedback to my LC comments on the
ietf-discuss mailing list...
I didn't see you initial email (I'm not not on the ietf@ietf.org mailing list),
which explains
why you didn't
At 07:53 29-02-2012, Vincent Roca wrote:
I didn't see you initial email (I'm not not on the ietf@ietf.org
mailing list), which explains why you didn't receive any feedback.
That explains why the authors did not respond to the comments. It
does not explain why the working group asked the IETF
On 2012-02-29 16:53, Vincent Roca wrote:
Hello Julian,
I note that draft-ietf-rmt-flute-revised is on the agenda. Just wanted
to note that I haven't seen any feedback to my LC comments on the
ietf-discuss mailing list...
I didn't see you initial email (I'm not not on the ietf@ietf.org
On 2012-02-11 01:48, The IESG wrote:
The IESG has received a request from the Reliable Multicast Transport WG
(rmt) to consider the following document:
- 'FLUTE - File Delivery over Unidirectional Transport'
draft-ietf-rmt-flute-revised-13.txt as a Proposed Standard
The IESG plans to make
