RE: Sending ABORT upon receipt of INIT-ACK

"Haresign Lincoln" <[email protected]>
Newsgroups gmane.ietf.sigtran
Message-ID <849535E338E99741B7F7413F73253EDB066180FE@us-nj-mail1.comverse.com>
Brian,

Thanks...I did see this in the rfc4460.  I guess the server really can't
do anything with the ABORT since it doesn't have a TCB.  However, I
guess it might help in debugging in trying to determine why an
association is not coming up.

Regards,
Lincoln 

-----Original Message-----
From: Brian F. G. Bidulock [mailto:[email protected]] 
Sent: Wednesday, May 16, 2007 2:02 PM
To: Haresign Lincoln
Cc: Emmanuel Mavrommatis; [email protected]
Subject: Re: [Sigtran] Sending ABORT upon receipt of INIT-ACK

Lincoln,

Because such an ABORT may be blocked by firewalls for security reasons
(e.g.
port scanning), the 2960bis documents downgrades the MUST to SHOULD in
all cases and permits an implementation to not send the ABORT in the
scenarios described.

--brian

Haresign Lincoln wrote:                       (Wed, 16 May 2007
13:26:53)
> 
>    Emmanuel -
> 
> 
> 
>    If  we  send  an  ABORT  in  response  to an INIT ACK, the server
will
>    receive an ABORT for which it has no TCB.  So it seems unneccessary
to
>    state  this  as  a  MUST  requirement since the server can't really
do
>    anything with the ABORT.
> 
> 
> 
>    Regards,
>    Lincoln


--
Brian F. G. Bidulock
[email protected]
http://www.openss7.org/

_______________________________________________
Sigtran mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/sigtran
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.