On 30/03/2015 22:49, Ronald Bonica wrote:
Lucy,
Would the following text work?
OLD>
Because the IPv6 delivery header does not include a checksum of its
own, it is subject to corruption. However, even if the delivery
header is corrupted, to likelihood of that corruption resulting in
misdelivery of the payload is extremely low.
<OLD
NEW>
Because the IPv6 delivery header does not include a checksum of its
own, the destination address in the delivery header is subject to
corruption. If the destination address in the deliver header is
corrupted,
the following outcomes are possible:
1)The delivery packet is dropped because the new destination address
is unreachable
2)The delivery packet is dropped because the new destination address
is reachable, but that node is not configured to process GRE delivery
packets from the ingress
3)The delivery packet is processed by a GRE egress other than that
which was originally specified by the GRE ingress. Processing options are:
a.The payload packet is dropped because the payload destination is
unreachable from the node that processed the delivery packet
b.The payload packet is delivered to its intended destination because
the payload destination is reachable from the node that processed the
delivery packet
All of these outcomes are acceptable.
<NEW
Ron
Ron, maybe I am missing a caveat, but suppose the payload is a packet
with a non-globally unique address space (for example 10.x.x.x, but not
limited to IP) then there is a case 3 c which is that the packet was
delivered to a node that it was not the intended ultimate destination
and one has to hope that there is sufficient resilency in the system
receiving the packet that this is of no consequence.
Stewart
_______________________________________________
Int-area mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/int-area
