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

Re: Proposed way forward with the transition mechanisms

Karen E. Nielsen (AH/TED) wrote: 
Hi Alain,

I find it difficult to argue based on draft-ietf-v6ops-assisted-tunneling-requirements-00.txt given that this draft so clearly focuses on the full-fledged tunnelling functionality demanded by (perhaps ?) the ISP environment
and not the lightweight tunnelling function requested for the 3GPP environment.
Examples - just to pick a few: NAT traversal, prefix delegation, extensibility requirements of draft-ietf-v6ops-assisted-tunneling-requirements-00.txt. Neither of which can be found in the 3GPP v6ops documents, that is RFC 3574 and draft-ietf-v6ops-3gpp-analysis-10.txt.

I opt for standard track standardization of Isatap as it serves the needs of the 3GPP environment. In particular:

* It is simple and easy to deploy, 

Manual configuration is easy to deploy at 3GPP scale?

From the ISATAP draft:

8.3.2 Potential Router List Initialization

   ISATAP nodes initialize an ISATAP interface's PRL with IPv4 addresses
   discovered via manual configuration, a DNS fully-qualified domain
   name (FQDN) [STD13], a DHCPv4 option, a DHCPv4 vendor-specific
   option, or an unspecified alternate method. FQDNs are established via
   manual configuration or an unspecified alternate method.

* It is lightweight network architecture wise, i.e. it
requests one additional infrastructure element only, namely the Isatap router.


And an extra module in every host stack that wants to use it.

    Brian

* It provides a scalable and simple service discovery mech (DNS)
* Tunnel set-up protocol at client side is simple
* It is stateless and provides the most efficient tunnel-set up protocol there is at the server side (none)
* Ipv6 Address (/128) assignment and configuration is provided using simple and well-understood mech (IPv6 RS/RA)
* Keep-alive is achieved using simple and well-understood mechs (IPv6 RS/RA)
* It is "ready to use". There is no major open issues and it may be readily standardized.
* It is there, both on paper and in running code and it solves a pressing need in 3GPP

Karen



-----Original Message-----
From: owner-v6ops@ops.ietf.org [mailto:owner-v6ops@ops.ietf.org]On
Behalf Of Alain Durand
Sent: Friday, July 30, 2004 7:43 AM
To: Karim El-Malki (AL/EAB)
Cc: 'Soininen Jonne '; 'v6ops@ops.ietf.org '
Subject: Re: Proposed way forward with the transition mechanisms



On Jul 29, 2004, at 3:39 PM, Karim El-Malki (AL/EAB) wrote:


I agree with Jonne. ISATAP is the most promising solution
for 3gpp tunnelling

For the sake of the discussion, could the ISATAP proponents summarize
why they think ISATAP is a better fit than a tunnel broker solution based
on draft-ietf-v6ops-assisted-tunneling-requirements-00.txt. in a 3GPP environment?

	- Alain.