> > Is this growth primarily in the via list? If that is the case, then it > seems possible to solve this using a combination of the fragment > field and the via list. If the fragment field's high order two bits > indicate that this is a fragment, you could replace the via list > with a null list for any fragment after the first complete rendering > of the via list. That requires one more state in the fragment field > (via list not yet complete;via list complete). It also requires you > to presume that the via list can be split across fragments and > and that fragments with "via list not yet complete" set are > going to have no real data--just segments of the via list--in them. >
Maybe I'm missing something basic here. How would the sending node even know that the via list was rendered completely at any time? Regards, Vidya > The same things can be done when other headers grow, obviously; > it is just a bit easiert to do when it is only one header that has to > be tracked in this way. > regards, > Ted > > _______________________________________________ > P2PSIP mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/p2psip _______________________________________________ P2PSIP mailing list [email protected] https://www.ietf.org/mailman/listinfo/p2psip
