>
> => explain how you can get the position of an extension header in
> the current advanced API. There is a setsockopt per header/position
> defined in RFC 2460 which gives a lot of different setsockopt (not
> a real problem but this is unnecessarily rigid) and of course gives
> no way to code something not described in RFC 2460.
>
The sticky options are quite restrictive at the moment. Making them more
flexible is a little difficult. Ancillary data can be made more flexible
fairly easily.
> If we allow the application,
> via ancillary data, to specify multiple destination options headers and
> place the fragmentation header (and possible AH and ESP) as the application
>
> => how?
>
Please see the archives. We began defining position markers six months ago
and folks lost interest.
> sees fit within the datagram then the only piece of flexability that is
> missing is the ability to add as yet unspecified extension header types.
>
> => or an extension header forgotten in RFC 2460 like IPCOMP?
>
I believe that all that is required is the ability to designate where the
fragmentable part the the datagram begins and where the "terminal" header
should be placed. This would accomodate placement of ESP, AH, IPCOMP or
any other terminal header type.
> - manage headers as a stack with placeholders for some headers like
> fragmentations (the user should not give their contents, only their
> possible positions).
> The second seems the best (not third proposal :-) but details have to be
> written down. This gives enough flexibility too and is closed to the
> conceptual model of extension headers.
>
This can be done within the existing model. So why is a complete redesign
essential except as a full employment program for kernel programmers?
Tim Hartrick
Mentat Inc.
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
