IETF Logo Mail Archive

Re: [v6ops] draft-ietf-v6ops-mobile-device-profile last call

Lorenzo Colitti <lorenzo@google.com> Mon, 23 February 2015 08:10 UTC

Return-Path: <lorenzo@google.com>
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 77E9A1A0277 for <v6ops@ietfa.amsl.com>; Mon, 23 Feb 2015 00:10:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level:
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 aNB-JTKCoY7Z for <v6ops@ietfa.amsl.com>; Mon, 23 Feb 2015 00:09:59 -0800 (PST)
Received: from mail-ie0-x235.google.com (mail-ie0-x235.google.com [IPv6:2607:f8b0:4001:c03::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DAC611A0302 for <v6ops@ietf.org>; Mon, 23 Feb 2015 00:09:51 -0800 (PST)
Received: by iecvy18 with SMTP id vy18so21449757iec.6 for <v6ops@ietf.org>; Mon, 23 Feb 2015 00:09:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=tEyeUngqhJQlofHLznbcfVudN6nvLAdN1sJq16x6/cw=; b=mxajqiVMwhomNa0Oh8nRAouPBzdQ3eYDNr2L24SXelBJ6CKwjbnQRvaE3ydArRk1qY xoz0gciBkvZIJBjzbhPY2i1sw6v26exkixGlaoEYU2Rnf5SRBJNHPg+OqOf20bOQFiLB eENHcnq5NlgLPxu2ZIIlrH0V45lqNBjUS25C7DnCg+ri6cUTkd0pBGdAg797pRGcxpjy eBIYlWPgsvka4yWQ/kuhDVHTlvWJA/bI20hs0TpfgsMcOJCZ9PeGGIuN7ZFehbsohcdN XPfXnapc8XnFgHM/2PzUdLRGHbDX3H0asM7k2KC0TrN6L9jVN4M7d29EIo03aHpNjOZv xbTQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=tEyeUngqhJQlofHLznbcfVudN6nvLAdN1sJq16x6/cw=; b=Iflpv/zLtoSe5JIgXUpjgQJEVkZ7WXEDUThkqc5u86gFDBOBEvGJe24wmgoMj3n+Jv pHEBvwo8JJpGJJUBdXp1DEGXE/zUKNLWDT4WKT+gN7yXUcDzkt+KYPXyHfVnNMHAa8DE SkHnFlWNjFj89xocuKGFfi4ukr/o0zrw0Jz8wuDDmj0C8XEcZ9Bn8AH3QPTkqZoDd4ND r3J9tSR+gqsvju1878GeGjk+YjQYcEO4s6VcMnLQH75OhBM1H3BVDcMo0WbPYbZLsUlA q2tebaXnZoy/UV0NHICxjNnkF3UfRx0fquc9W63ExJA5tECuWMvWaam6db/+7yoVrwGh 7tRQ==
X-Gm-Message-State: ALoCoQnXbY9OUpt88kvoHoxcW9JGNnrizmPyBvNCtluy/DLwH5dK+oR/PSb6aJ1uVQ84c5A1y/Bv
X-Received: by 10.42.138.199 with SMTP id d7mr10074002icu.3.1424678990989; Mon, 23 Feb 2015 00:09:50 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.33.104 with HTTP; Mon, 23 Feb 2015 00:09:29 -0800 (PST)
In-Reply-To: <787AE7BB302AE849A7480A190F8B933004912254@OPEXCLILM23.corporate.adroot.infra.ftgroup>
References: <8B808F0C-1AA8-4ABE-A06E-80652B9C1498@cisco.com> <alpine.DEB.2.02.1502201513320.4007@uplift.swm.pp.se> <787AE7BB302AE849A7480A190F8B933004912254@OPEXCLILM23.corporate.adroot.infra.ftgroup>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Mon, 23 Feb 2015 17:09:29 +0900
Message-ID: <CAKD1Yr3A6fzgTauLz+Yxe-xOLeDLZ5bzKBo-XyWU4i9LBSAM9Q@mail.gmail.com>
To: "<mohamed.boucadair@orange.com>" <mohamed.boucadair@orange.com>
Content-Type: multipart/alternative; boundary="90e6ba1efc122d70f6050fbcedcf"
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/iF_9auq-1AyD_dAJoSz1tZjSnMI>
Cc: V6 Ops List <v6ops@ietf.org>
Subject: Re: [v6ops] draft-ietf-v6ops-mobile-device-profile last call
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: Mon, 23 Feb 2015 08:10:00 -0000

On Mon, Feb 23, 2015 at 4:59 PM, <mohamed.boucadair@orange.com> wrote:

> NEW:
>
>              *  If the requested IPv4v6 PDP-Context is not supported by
>                 the network, but IPv4 and IPv6 PDP types are allowed,
>                 then the cellular host will be configured with an IPv4
>                 address or an IPv6 prefix by the network.  It must
>                 initiate another PDP-Context activation in addition to
>                 the one already activated for a given APN (Access Point
>                 Name).  The purpose of initiating a second PDP-Context
>                 is to achieve dual-stack connectivity by means of two
>                 PDP-Contexts.
>

Operators who have deployed IPv6 report that running dual-stack over two
PDP contexts is a very bad idea because it consumes 2x the network
resources. Please don't recommend this unless you have evidence that this
works well in production (not in testing).


> NEW:
>                 Note, a cellular host changing its connection between an
>                 IPv6-specific APN and an IPv4-specific APN will
>                 interrupt associated network connections.  This may be
>                 considered as a brokenness situation for some
>                 applications.
>

What is the purpose of this text? Mobile nodes change IP addresses all the
time (e.g., when switching from 4G to wifi). How is this different?

v2.23.0 | Report a Bug | By Email