Re: [Tsvwg] End point and association Address conflict

[Randall Stewart <[e-mail]>]

"Brian F. G. Bidulock" wrote:

> These endpoints are not listening.  When they engage in fully
> formed connections the endpoint is determined from the established
> hashes which requires a match on vtag, source address, source port,
> destination address and destination port.  As long as this set
> uniquely identifies an endpoint (and listen() and connect() will
> make sure that this is true) there is never any problem, just
> as there is never any problem for TCP above.
> 

Vtags have never been defined as part of the identification
of an SCTP association. They are used in place of the
pseudo header and as a defense against blind attacks.. not
as part of association discrimination... Sorry this won't work.
Two associations are not allowed in this case.. just like
your TCP description would return a INUSE error...

One can easily prevent the TCP case.. i.e. at the connect
check the hash.... I guess the ADD-IP case also can
be prevented when one tries to add the IP-C to the second
association you would simply get the same error :>

Thinking about it.. we do this now.. since when you attempt
the sctp_bindx you would get such an error :>

R


-- 
Randall R. Stewart
[e-mail] 815-342-5222 (cell phone)

_______________________________________________
tsvwg mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/tsvwg