Re: [v6ops] new draft: draft-cui-v6ops-lte-lw4over6

Vízdal Aleš <ales.vizdal@t-mobile.cz> Fri, 14 February 2014 08:51 UTC

Return-Path: <ales.vizdal@t-mobile.cz>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44D3C1A0115 for <v6ops@ietfa.amsl.com>; Fri, 14 Feb 2014 00:51:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.8
X-Spam-Level:
X-Spam-Status: No, score=-0.8 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_CZ=0.445, HOST_EQ_CZ=0.904, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kovmtgk6gtyu for <v6ops@ietfa.amsl.com>; Fri, 14 Feb 2014 00:51:37 -0800 (PST)
Received: from ctxmailhub.t-mobile.cz (ctxmailhub.t-mobile.cz [93.153.104.87]) by ietfa.amsl.com (Postfix) with ESMTP id 2AE011A0179 for <v6ops@ietf.org>; Fri, 14 Feb 2014 00:51:36 -0800 (PST)
From: Vízdal Aleš <ales.vizdal@t-mobile.cz>
To: "v6ops@ietf.org" <v6ops@ietf.org>
Date: Fri, 14 Feb 2014 09:51:32 +0100
Thread-Topic: [v6ops] new draft: draft-cui-v6ops-lte-lw4over6
Thread-Index: Ac8owd+2dNL6The/SDe7lo5wLYQoxAAnWaPQ
Message-ID: <1808340F7EC362469DDFFB112B37E2FCDA3256B25D@SRVHKE02.rdm.cz>
References: <201402131345.s1DDj0911080@ftpeng-update.cisco.com>
In-Reply-To: <201402131345.s1DDj0911080@ftpeng-update.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
x-loop: 2
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Forwarded
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/DclLCWjtWNlgLgqYY3C53z9B6xA
Cc: "draft-cui-v6ops-lte-lw4over6@tools.ietf.org" <draft-cui-v6ops-lte-lw4over6@tools.ietf.org>
Subject: Re: [v6ops] new draft: draft-cui-v6ops-lte-lw4over6
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Feb 2014 08:51:39 -0000

> -----Original Message-----
> From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of
> fred@cisco.com
> Sent: Thursday, February 13, 2014 2:45 PM
> To: v6ops@ietf.org
> Cc: draft-cui-v6ops-lte-lw4over6@tools.ietf.org
> Subject: [v6ops] new draft: draft-cui-v6ops-lte-lw4over6
> 
> 
> A new draft has been posted, at
> http://tools.ietf.org/html/draft-cui-v6ops-lte-lw4over6.
> Please take a look at it and comment.

IETF V6OPS is not the right place for such an architectural change. 
A problem statement may fit to start the discussion, but 3GPP SA1/SA2 
is the place to get this kind of change done.

Ales