On 8/2/07, Gerrit Renker <gerrit@xxxxxxxxxxxxxx> wrote: > Omission on my side - I have just checked and found out that the negotiation of the "Send ack vector > feature" is not yet implemented. It is not something which can be done with a hack, since the CCIDs > can also be negotiated, so that enabling Ack Vectors depends on the end result of negotiating the > CCID. > I think at the moment we should add this as a ToDo. If I get some time I'll try to implement the > above, but it is more work than anticipated and so depends on available time. > Well I think the discussion is useful as a future reference. There's no hurry on any of this really. > | The information is not actually needed from an ack vector > | and actually creates more traffic. It seems like > | draft-kohler-dccp-ccid3-drops-01.txt is a replacement for ack vectors > | in CCID3 if you need extra info. > Never figured that one out - doesn't the Data Dropped option do the same thing? > Data Dropped is more when receiver gets it but discards for some reason as I read it. Ian -- Web1: http://wand.net.nz/~iam4/ Web2: http://www.jandi.co.nz Blog: http://iansblog.jandi.co.nz - To unsubscribe from this list: send the line "unsubscribe dccp" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
