[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: SOI: selector exclusion lists/ranges

To: Michael Thomas <mat@cisco.com>
Subject: Re: SOI: selector exclusion lists/ranges
From: Ricky Charlet <rcharlet@redcreek.com>
Date: Tue, 27 Nov 2001 12:49:42 -0800
CC: ipsec list <ipsec@lists.tislabs.com>
Organization: Redcreek Communications
References: <15363.62186.160914.487198@thomasm-u1.cisco.com>
Sender: owner-ipsec@lists.tislabs.com

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

Follow-Ups:

Re: SOI: selector exclusion lists/ranges

From: Jan Vilhuber <vilhuber@cisco.com>

References:

SOI: selector exclusion lists/ranges

From: Michael Thomas <mat@cisco.com>

Prev by Date: Re: On shared keys (was RE: SOI: identity protection and DOS)
Next by Date: Re: SOI: selector exclusion lists/ranges
Next by thread: Re: Status of ID: IPsec Flow Monitoring MIB
Index(es):
- Main
- Thread