Narayanan, Vidya skrev:
From RFC2460:
" The Unfragmentable Part consists of the IPv6 header plus any
extension headers that must be processed by nodes en route to the
destination, that is, all headers up to and including the Routing
header if present, else the Hop-by-Hop Options header if present,
else no extension headers.
The Fragmentable Part consists of the rest of the packet, that is,
any extension headers that need be processed only by the final
destination node(s), plus the upper-layer header and data."
The extension header under discussion here is only to be processed by
the final destination node and hence, falls under the Fragmentable Part
- so, size is not an issue.
From a transport perspective I don't like seeing such sweeping
statements that "size is not an issue". If you cause fragmentation of
the packets by adding an extension header then you do effect the packet
loss probabilities for the packet to reach the destination in a complete
form.
Also if you know what the destination is, why not use a real transport
protocol instead of reinventing the transport functionality you need
inside the extension header. As I don't fully understand the
requirements here I will not be to specific. But unless there is some
real hard requirement why you need to place this exchange in the
extension header, I would recommend using a transport protocol for the
transport. It probably also makes the development of the security
solution easier as there are more ready to use options on the transport
layer.
Cheers
Magnus Westerlund
IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB | Phone +46 8 4048287
Torshamsgatan 23 | Fax +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: [EMAIL PROTECTED]
----------------------------------------------------------------------
_______________________________________________
Int-area mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/int-area
