[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: IVs, summary of discussion
>Traditionally, IP assigns the id field.
Right. So does my code, although I give the caller of the IP send
routine the option of specifying one. I generate ID fields with a
global variable used as a counter, so another module (e.g. IPSEC)
could conceivably access it. Or IPSEC could maintain a separate ID
counter of its own without worrying about collisions with "regular" IP
datagrams because the protocol field is logically appended to the ID
field for the purpose of reassembling fragments.
The closest RFC-1122 comes to discussing this issue is the subject of
whether retransmitted segments could have the same IP ID. It seems to
be silent on the specific issue of whether IP should give a transport
protocol direct control over the IP ID field, although the example
upper level interface in RFC-791 does show it as one of the
parameters.
So I guess the question is, does the BSD IP send routine allow its
caller to specify its own ID field? If not, can it be easily modified
to do so?
Phil