[BXXPwg] Keep-alive proposal

Keith McCloghrie kzm@cisco.com
Fri, 22 Sep 2000 11:59:39 -0700 (PDT)

I suggest that it depends on what you want to test: 

1) the underlying transport layer's connectivity, or
2) connectivity to the peer application.

It's only #2 which needs something at the application layer.  Below,
you specifically ask for #1, for which it's better to use what the
transport layer already provides, and TCP has a "keep-alive" (see
section of RFC 1122).


> Well, a lot of things that have worked their way into BXXP already are
> unnecessary, so I don't see much harm in adding one more, plus I really
> like the idea of having a ping to test the underlying transport layer.  It
> seems trivial to implement and I can't think of any negative side-effects,
> so why not add it?  Just because the TCP mapping already allows a SEQ
> message to be sent, doesn't mean other mappings will, so adding ping
> capabilities makes things a little bit simpler for those other mappings.
> BXXP is intended to be eXtensible to other transports, and I believe that
> a ping mechanism could prove useful in that, so I fully support its
> inclusion.
> -Wes
> _______________________________________________
> BXXPwg mailing list
> BXXPwg@lists.invisible.net
> http://lists.invisible.net/mailman/listinfo/bxxpwg