RE: Concensus Call on Urgent Pointer.

["Douglas Otis" <dotis@sanlight.net>]

Matt,

MUST use the Urgent Pointer Option requirement if requested by the receiver
is based on an assumption that only the receive side will see any negative
effect.  If the send side has a problem with respect to firewalls,
encapsulation, or performance, then allowing the send side to decline this
requested option ensures greatest compatibility.  The vendor will prefer the
greatest performance, so why make the Urgent Pointer option mandatory?  The
way the receiver side handles an "occasional" Urgent Pointer should not be
greatly effected by no Urgent Pointer actually used.  The possible distance
between pointers or a recovered segment should be conditions any receiver
can handle.

Doug

> I think the spec should say:
>
> "During login, if the target requests use of the Urgent Pointer, then the
> initator Must use the Urgent Pointer when
> sending data.  If the target does not request use of the Urgent
> Pointer, then
> the initiator Must Not use the Urgent Pointer when sending data."
>
> and likewise...
>
> "During login, if the initiator requests use of the Urgent
> Pointer, then the
> target Must use the Urgent Pointer when
> sending data.  If the initiator does not request use of the
> Urgent Pointer,
> then the target Must Not use the Urgent Pointer when sending data."
>
> -Matt
>
>