RE: [nemo] RE: [Mip6] Consensus call on making IDdraft-wakikawa-nemo-v4tunnel a MIP6/NEMO WGs document

Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM> Mon, 04 April 2005 08:11 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 EAA04029 for <mip6-web-archive@ietf.org>; Mon, 4 Apr 2005 04:11:30 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DIMoA-0008DK-AH for mip6-web-archive@ietf.org; Mon, 04 Apr 2005 04:19:42 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DIMfY-000088-0g; Mon, 04 Apr 2005 04:10:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DIMfU-00007m-SX; Mon, 04 Apr 2005 04:10:45 -0400
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 EAA03979; Mon, 4 Apr 2005 04:10:43 -0400 (EDT)
Received: from dns2.tilab.com ([163.162.42.5]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DIMnN-0008CX-Jq; Mon, 04 Apr 2005 04:18:55 -0400
Received: from iowa2k01b.cselt.it ([163.162.242.202]) by dns2.cselt.it (PMDF V6.1 #38895) with ESMTP id <0IEE00689WU450@dns2.cselt.it>; Mon, 04 Apr 2005 09:58:52 +0200 (MEST)
Received: from EXC01B.cselt.it ([163.162.4.199]) by iowa2k01b.cselt.it with Microsoft SMTPSVC(6.0.3790.211); Mon, 04 Apr 2005 10:09:44 +0200
Date: Mon, 04 Apr 2005 10:10:29 +0200
From: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>
Subject: RE: [nemo] RE: [Mip6] Consensus call on making IDdraft-wakikawa-nemo-v4tunnel a MIP6/NEMO WGs document
To: Basavaraj.Patil@nokia.com
Message-id: <DA62A6E0CDD1B34A84557FF1AC850C5769DF67@EXC01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Content-type: text/plain; charset="us-ascii"
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: [nemo] RE: [Mip6] Consensus call on making IDdraft-wakikawa-nemo-v4tunnel a MIP6/NEMO WGs document
Thread-Index: AcU2v5I6v6wC3vU1ROuQO8Y2kW4a4QADu+tQAIfNijA=
Content-class: urn:content-classes:message
X-OriginalArrivalTime: 04 Apr 2005 08:09:44.0953 (UTC) FILETIME=[A9593E90:01C538ED]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Content-Transfer-Encoding: quoted-printable
Cc: nemo@ietf.org, mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>, <mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>, <mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Content-Transfer-Encoding: quoted-printable

> 
> A couple of clarifications regarding the consensus call:
> 
> 1. The intention is to address the following scenario:
> "MIPv6 and NEMO capable Mobile hosts/routers attaching to an IPv4
> access network need the capability to create a tunnel and be connected
> to their MIP6 home agents."
> This is the scenario that is most applicable for MIP6 deployment.
> There are plenty of other scenarios as well. But they are much more
> of academic interest at this time and hence not really in the scope
> of this discussion. So I would suggst that we do not go off 
> on a tangent
> discussing all these other scenarios.
> 
> Do you agree/disagree that the above scenario is the one that needs
> to be solved ASAP?
> (Note: It does not imply that other scenarios are irrelevant. 
> It simply
> means that this is the scenario worth working on and has the most 
> significant priority or value for MIP6 deployment.)
>

I agree on the priority of this scenario.

--Gerardo

 
> 2. ID:  draft-wakikawa-nemo-v4tunnel can be used as the baseline. It
> does not imply that we are ruling out draft-soliman-v4v6-mipv6 or any
> other. The IDs can be combined w.r.t the parts that address 
> this scenario.
> Additionally once it is a WG document, what goes into the ID 
> is decided
> by the WG. So lets not get into arguments of what or whose 
> draft is the
> one that should be made the WG document.
> 
> -Basavaraj
> 
> 


Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia S.p.A.

====================================================================
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to
MailAdmin@tilab.com. Thank you
====================================================================

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