Renee Danson wrote:
> IP tunnels are tough to categorize. So far, I think we've assumed the
> following attributes for LLPs and ULPs:
IP tunnel configuration should be in the link/interface
specification before and after the Clearview IP tunnel change.
It belongs to that layer. I think we should be clear on this.
> LLPs
> 1. Contain config info for Layer 3 and below
> 2. Contain attributes that apply to individual interfaces or links
>
> ULPs
> 1. Contain config info for things that operate above Layer 3; or
> more generally, for things that don't care so much about what
> interfaces are there or will be used, but just want to send a
> packet to IP for delivery to a particular destination
> 2. Contain system-wide attributes
> 3. Are selected based on current network availability
>
> The problem is that (as you pointed out) IP tunnels match LLP items 1 and
> 2, but also ULP item 3. We definitely need to do more thinking about how
> they should fit in.
I think an interesting case is that some network service, such
as VPN, in an Env (Environment or ULP) requires the creation
of an IP tunnel. How can this be specified? One way to do it
is when the VPN service is first installed, an IP tunnel is
created in the link/interface specification. And it is conditional
on the VPN service itself. So after the VPN service installation,
a user can see the IP tunnel info in the specification view. But
it is not enabled. It is enabled when the VPN service actually
starts and enables the tunnel.
--
K. Poon.
kacheong.poon at sun.com
