Re: [v6ops] Last Call: <draft-ietf-v6ops-3gpp-eps-03.txt> (IPv6 in 3GPP Evolved Packet System) to Informational RFC
Jouni <jounikor@gmail.com> Fri, 05 August 2011 06:55 UTC
Return-Path: <jounikor@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A034A11E8085; Thu, 4 Aug 2011 23:55:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.999
X-Spam-Level:
X-Spam-Status: No, score=-2.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DOXEkHPj1NDu; Thu, 4 Aug 2011 23:55:19 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5BB2311E807F; Thu, 4 Aug 2011 23:55:18 -0700 (PDT)
Received: by fxe6 with SMTP id 6so3134868fxe.31 for <multiple recipients>; Thu, 04 Aug 2011 23:55:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=bo3r2gvEr7T+Yws8RGXqWKGIEA/RdjMIRPUbwJMFF8o=; b=Bhm+GdW3mqpucuLGa+CYy0Yp6jGEIQvh/anehD2ZSWYfD8JM9Dlm5ioTrbUfbvhwy4 SEg1UEd8ZyM6rgiQ+BVBMI+ULXYLawG4mG7RbBFzcPjKVipFUb8+aeV0AqYJiR+q3erY BWRsJQhDVpe//GwIR8RNu4D+7cZGJuQ7SlLhc=
Received: by 10.204.142.143 with SMTP id q15mr589342bku.321.1312527334358; Thu, 04 Aug 2011 23:55:34 -0700 (PDT)
Received: from a88-114-68-66.elisa-laajakaista.fi (a88-114-68-66.elisa-laajakaista.fi [88.114.68.66]) by mx.google.com with ESMTPS id p24sm756251bkw.41.2011.08.04.23.55.32 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 04 Aug 2011 23:55:33 -0700 (PDT)
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-3gpp-eps-03.txt> (IPv6 in 3GPP Evolved Packet System) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset="us-ascii"
From: Jouni <jounikor@gmail.com>
In-Reply-To: <CAM+vMEQ-qsobxrozvzgnRiiHJjRwDPBbGeNe9qKacvQ+0Fj7GA@mail.gmail.com>
Date: Fri, 05 Aug 2011 09:55:30 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <49A19FE6-7B0A-4876-8F1A-308F978CC8FC@gmail.com>
References: <20110801190301.16571.58632.idtracker@ietfa.amsl.com> <CAM+vMEQ-qsobxrozvzgnRiiHJjRwDPBbGeNe9qKacvQ+0Fj7GA@mail.gmail.com>
To: GangChen <phdgang@gmail.com>
X-Mailer: Apple Mail (2.1244.3)
X-Mailman-Approved-At: Fri, 05 Aug 2011 10:11:16 -0700
Cc: v6ops@ietf.org, ietf@ietf.org, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Aug 2011 06:55:19 -0000
Dear Gang, I would be inclined to say that within the 3GPP scope the client is always the "UE" and its form factor or the end usage scenario does not really matter. It does not change the way the UE is expected to behave from the 3GPP system point of view, unless there is a new functional requirement from 3GPP. - Jouni On Aug 5, 2011, at 5:55 AM, GangChen wrote: > Hello Authors, > > I think it is worth adding some texts to describe mobile CPE case, in > which CPEs with wireless modem use 3GPP access as uplink. > > Gang > > > 2011/8/2, The IESG <iesg-secretary@ietf.org>: >> >> The IESG has received a request from the IPv6 Operations WG (v6ops) to >> consider the following document: >> - 'IPv6 in 3GPP Evolved Packet System' >> <draft-ietf-v6ops-3gpp-eps-03.txt> as an Informational RFC >> >> The IESG plans to make a decision in the next few weeks, and solicits >> final comments on this action. Please send substantive comments to the >> ietf@ietf.org mailing lists by 2011-08-15. Exceptionally, comments may be >> sent to iesg@ietf.org instead. In either case, please retain the >> beginning of the Subject line to allow automated sorting. >> >> Abstract >> >> >> Use of data services in smart phones and broadband services via HSPA >> and HSPA+, in particular Internet services, has increased rapidly and >> operators that have deployed networks based on 3GPP network >> architectures are facing IPv4 address shortages at the Internet >> registries and are feeling a pressure to migrate to IPv6. This >> document describes the support for IPv6 in 3GPP network >> architectures. >> >> >> >> >> The file can be obtained via >> http://datatracker.ietf.org/doc/draft-ietf-v6ops-3gpp-eps/ >> >> IESG discussion can be tracked via >> http://datatracker.ietf.org/doc/draft-ietf-v6ops-3gpp-eps/ >> >> >> No IPR declarations have been submitted directly on this I-D. >> >> >> _______________________________________________ >> v6ops mailing list >> v6ops@ietf.org >> https://www.ietf.org/mailman/listinfo/v6ops >> > _______________________________________________ > Ietf mailing list > Ietf@ietf.org > https://www.ietf.org/mailman/listinfo/ietf