[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: SOI: selector exclusion lists/ranges
Actually, now that I think about it, the ipsec-sctp draft addresses some of
this via the ID_RECURSE (BAD name! Bad name!!) payload. The new SOI Traffic
selector payload used in this manner would be a great benefit.
jan
On Tue, 27 Nov 2001, Ricky Charlet wrote:
> Michael Thomas wrote:
> > Thus I think we should have a requirement which
> > states:
> >
> > "The protocol MUST have the ability to express
> > port ranges for flow selectors, as well as have
> > the ability to selectively enumerate ports which
> > fall outside of the flow selector."
> >
> > Mike
>
>
>
> Ooh, ooh, ooh!! And lists (not restricted to ranges) of subnets bound
> to a single SA too please!
>
>
> --
> "They that can give up essential liberty to obtain a little temporary
> safety deserve neither liberty nor safety." Benjamin Franklin
>
> Ricky Charlet : SonicWall Inc. : usa (510) 497-2103
>
--
Jan Vilhuber vilhuber@cisco.com
Cisco Systems, San Jose (408) 527-0847
References: