Re: [PATCH] sctp: Process OOTB ASCONF Chunk at CLOSED state

[Vlad Yasevich <vladislav.yasevich@xxxxxx>]

On 07/23/2010 04:50 AM, Shan Wei wrote:
> RFC5061 said that If the received ASCONF Chunk is not associated with 
> any association, the Chunk should be treated as OOTB. So, process
> this OOTB chunk according to section 8.4 of RFC4960.
> 
> Quote from RFC5061:
> 5.2. Upon Reception of an ASCONF Chunk
>    D3)  If neither D1, D2, nor D2-ext locates the association, treat the
>         chunk as an Out Of The Blue packet as defined in [RFC4960].
> 
> 
> Signed-off-by: Shan Wei <shanwei@xxxxxxxxxxxxxx>
> ---
>  net/sctp/sm_statetable.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/net/sctp/sm_statetable.c b/net/sctp/sm_statetable.c
> index 6d9b3aa..ca300db 100644
> --- a/net/sctp/sm_statetable.c
> +++ b/net/sctp/sm_statetable.c
> @@ -449,7 +449,7 @@ static const sctp_sm_table_entry_t chunk_event_table[SCTP_NUM_BASE_CHUNK_TYPES][
>  	/* SCTP_STATE_EMPTY */ \
>  	TYPE_SCTP_FUNC(sctp_sf_ootb), \
>  	/* SCTP_STATE_CLOSED */ \
> -	TYPE_SCTP_FUNC(sctp_sf_discard_chunk), \
> +	TYPE_SCTP_FUNC(sctp_sf_ootb), \
>  	/* SCTP_STATE_COOKIE_WAIT */ \
>  	TYPE_SCTP_FUNC(sctp_sf_discard_chunk), \
>  	/* SCTP_STATE_COOKIE_ECHOED */ \

Same should probably be done for ASCONF_ACK as well....

-vlad
--
To unsubscribe from this list: send the line "unsubscribe linux-sctp" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html