[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
IPv6 Destination options extension header position.
I have some question about position of IPv6 Destination options
extension header.
In draft-ietf-ipsec-{auth-header-01,esp-v2-00}.txt, IPv6 Destination
options extension header may appear before ah/esp, after ah/esp or
both position. When it appears before ah/esp, it's position is after
hop-by-hop, routing and fragment header.
But in rfc1883 or draft-ietf-ipngwg-ipv6-spec-v2-00.txt, destination
option can appear between hop-by-hop option and routing header or
after ah/esp.
What is the right description?
In both document, Destination options header can appear after ah/esp
header. This is not ambiguous. But how about position before ah/esp?
If there is not routing/fragment header, it has almost same
meaning. it will be processed by final destination only.
But if there is routing header, it is different.
According to rfc1883 or draft-ietf-ipngwg-ipv6-spec-v2-00.txt,
destination options header before routing header must be processed by
nodes which appear IPv6 destination address field(each node which
appear in routing header).
In the other hand, destination options header before ah/esp and after
hop-by-hop options, (destination options, )routing header and fragment
header(in draft-ietf-ipsec-*.txt) will be processed by final
destination only.
I think both are reasonable(destination options header may be appear
3 times). Because ah/esp related options must be processed before
ah/esp processing and only by node which must process ah/esp(final
destination for common cases).
So it should be noted in both draft or rfc.
Any comments?
--
Koji Imada - je4owb/2
koji@math.human.nagoya-u.ac.jp
Follow-Ups: