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

Re: manual config of UE tunnel [RE: 3gpp-analysis: Recommendation on tunneling in the UE]

To: Pekka Savola <pekkas@netcore.fi>
Subject: Re: manual config of UE tunnel [RE: 3gpp-analysis: Recommendation on tunneling in the UE]
From: Jasminko Mulahusic <jasko@fakat.com>
Date: Wed, 26 Nov 2003 10:11:34 +0100
Cc: Jonne.Soininen@nokia.com, karim.el-malki@ericsson.com, v6ops@ops.ietf.org
In-reply-to: <Pine.LNX.4.44.0311260850240.32703-100000@netcore.fi>
References: <Pine.LNX.4.44.0311260850240.32703-100000@netcore.fi>
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3

pekka,

As for the client side configuration...

No, this does not seem to be the case.  The user just has to find out
the IPv4 address of the tunnel endpoint somehow.  As the tunnel

it must be completely transparent to the user. otherwise, it is a non-starter. the normal user doesn't care about such things.

jasminko

p.s. instead of endlessly repeating same arguments over and over, shouldn't we write a requirements document for UE tunneling, or something?

Follow-Ups:
- Re: manual config of UE tunnel [RE: 3gpp-analysis: Recommendation on tunneling in the UE]
  - From: Pekka Savola <pekkas@netcore.fi>

References:
- RE: manual config of UE tunnel [RE: 3gpp-analysis: Recommendation on tunneling in the UE]
  - From: Pekka Savola <pekkas@netcore.fi>

Prev by Date: RE: manual config of UE tunnel [RE: 3gpp-analysis: Recommendation on tunneling in the UE]
Next by Date: Re: manual config of UE tunnel [RE: 3gpp-analysis: Recommendation on tunneling in the UE]
Previous by thread: RE: manual config of UE tunnel [RE: 3gpp-analysis: Recommendation on tunneling in the UE]
Next by thread: Re: manual config of UE tunnel [RE: 3gpp-analysis: Recommendation on tunneling in the UE]
Index(es):
- Date
- Thread