Re: refocusing: Re: [v6tc] Issue 2: service discovery: automatic or manual?

Florent Parent <Florent.Parent@hexago.com> Mon, 17 January 2005 03:41 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA11294; Sun, 16 Jan 2005 22:41:17 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CqO0W-0000hM-6y; Sun, 16 Jan 2005 22:56:48 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CqNkS-0005mq-DB; Sun, 16 Jan 2005 22:40:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CqNcH-0005Bt-E3 for v6tc@megatron.ietf.org; Sun, 16 Jan 2005 22:31:45 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA10628 for <v6tc@ietf.org>; Sun, 16 Jan 2005 22:31:42 -0500 (EST)
Received: from modemcable006.77-203-24.mc.videotron.ca ([24.203.77.6] helo=rtr6) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CqNrF-0000X7-DQ for v6tc@ietf.org; Sun, 16 Jan 2005 22:47:13 -0500
Received: from [192.168.31.28] ([192.168.31.28]) by rtr6 (8.12.9p1/8.12.9) with ESMTP id j0H3VaOt013797 for <v6tc@ietf.org>; Sun, 16 Jan 2005 22:31:38 -0500 (EST)
Date: Sun, 16 Jan 2005 22:30:45 -0500
From: Florent Parent <Florent.Parent@hexago.com>
To: v6tc@ietf.org
Subject: Re: refocusing: Re: [v6tc] Issue 2: service discovery: automatic or manual?
Message-ID: <DA2B32A2FE92C51C93F98958@[192.168.31.28]>
In-Reply-To: <8457F87A-6632-11D9-A440-00039358A080@sun.com>
References: <A6369F2C-63BD-11D9-A94C-00039358A080@sun.com> <8457F87A-6632-11D9-A440-00039358A080@sun.com>
X-Mailer: Mulberry/3.1.6 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 2.6 (++)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: 7bit
X-BeenThere: v6tc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: v6tc.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/v6tc>, <mailto:v6tc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/v6tc>
List-Post: <mailto:v6tc@ietf.org>
List-Help: <mailto:v6tc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/v6tc>, <mailto:v6tc-request@ietf.org?subject=subscribe>
Sender: v6tc-bounces@ietf.org
Errors-To: v6tc-bounces@ietf.org
X-Spam-Score: 2.6 (++)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: 7bit


-- On Friday, January 14, 2005 05:45:13 -0800, Alain Durand wrote:

> Well, the discussion on this topic has a bit rat-holing into anycast
> deployment issues,
> when the question I intended to discuss was:
>
>> In other words, could we live with a solution where the user will have
>> to manually
>> input on its v6 host or router an address of the form v6TEP.myISP.com
>> in the relevant
>> form? (provided that would be the ONLY thing to input)
>
> ... or do we absolutely require an automatic discovery mechanism?
>
> I would like to invite those who haven't expressed themselves on
> this very point to participate in the debate.
>
> 	- Alain.

Automatic discovery should be focused within an "autonomous system" 
(enterprise/ISP/etc.). For example, if anycast is used, such address should 
be confined to the autonomous system routing system. How it's done 
(anycast, DNS, etc.) is left to be defined.

I think automatic discovery should be done in order to cover the zero-conf. 
tunneling goals.

In the roaming scenario (or getting service across an IPv4 only ISP), some 
manually configured parameter would be required from the user (e.g. tunnel 
service FQDN of your IPv6 provider). This manual configuration isn't alien 
to users and is done in many client software.

Florent


_______________________________________________
v6tc mailing list
v6tc@ietf.org
https://www1.ietf.org/mailman/listinfo/v6tc