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

Alexandru Petrescu <alexandru.petrescu@gmail.com> Mon, 23 February 2015 11:58 UTC

Return-Path: <alexandru.petrescu@gmail.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 4FF711A1A5D for <v6ops@ietfa.amsl.com>; Mon, 23 Feb 2015 03:58:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.983
X-Spam-Level:
X-Spam-Status: No, score=-3.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
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 aZGAH4zfG00W for <v6ops@ietfa.amsl.com>; Mon, 23 Feb 2015 03:58:09 -0800 (PST)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 366D01A1A5A for <v6ops@ietf.org>; Mon, 23 Feb 2015 03:58:09 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t1NBw7Ep026437 for <v6ops@ietf.org>; Mon, 23 Feb 2015 12:58:07 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id E3E31202798 for <v6ops@ietf.org>; Mon, 23 Feb 2015 12:59:17 +0100 (CET)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id DC4EE2032CF for <v6ops@ietf.org>; Mon, 23 Feb 2015 12:59:17 +0100 (CET)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t1NBw5N7028149 for <v6ops@ietf.org>; Mon, 23 Feb 2015 12:58:06 +0100
Message-ID: <54EB15CD.4010706@gmail.com>
Date: Mon, 23 Feb 2015 12:58:05 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: v6ops@ietf.org
References: <8B808F0C-1AA8-4ABE-A06E-80652B9C1498@cisco.com> <alpine.DEB.2.02.1502201513320.4007@uplift.swm.pp.se> <787AE7BB302AE849A7480A190F8B933004912254@OPEXCLILM23.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B933004912254@OPEXCLILM23.corporate.adroot.infra.ftgroup>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/9yo3V9jKOYdeuKZ5mtY8XNCJgLQ>
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 11:58:11 -0000

Le 23/02/2015 08:59, mohamed.boucadair@orange.com a écrit :
[...]

>> C_REC#6:
>>
>> "restarts the ongoing applications". I don't like this wording,
>> "will interrupt existing network connections" or similar text
>> would be better.
>
> [Med] I made this change:
>
> OLD:
>
> Note, a cellular host changing its connection between an
> IPv6-specific APN and an IPv4-specific APN restarts the ongoing
> applications.  This may be considered as a brokenness situation.
>
> 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.
>
> To Alex: Can you please review this text (because you are the one
> who asked to have the OLD version)

Yes, thanks for asking.  It looks good, except it would be better to say 
"by some applications" instead of "for some applications".

And "bound" or "ongoing" or "related" would be better than "associated" 
(because this latter may make think of WiFi).

Alex

>
>>
>> C_REC#7:
>>
>> typo:
>>
>> "The purpose of the of the roaming profile is"
>
> [Med] Fixed. Thank you.
>
>>
>> C_REC#8:
>>
>> I don't understand the reference to 6052. Is this a referral to
>> networks with NAT64 and/or 464XLAT? Then I think this should be
>> clearer.
>
> [Med] This feature is for NAT64 context in general, but without
> requiring any packet translation feature.
>
> OLD: This solves the issue when applications use IPv4 referrals on
> IPv6-only access networks.
>
> NEW:
>
> In the context of NAT64, applications relying on address referrals
> will fail because an IPv6-only client won't be able to make use of
> an IPv4 address received in a referral.  This feature allows to
> solve this referral problem and, also, to distinguish between
> IPv4-converted IPv6 addresses [RFC6052] and native IPv6 addresses.
>
> Better?
>
>>
>> L_REC#4: Isn't this a duplication of one of the C_RECs?
>
> [Med] This one is for IPv4 devices connected via the cellular device
> through an IPv6-only network. The one in C_REC#8 is about local
> applications running on the cellular host.
>
>>
>> Summary:
>>
>> I think this kind of document is valuable. Many operators do not
>> have staff with right skill level to put in the requirements
>> towards equipment manufacturers, and in some markets, the
>> equipment manufacturers are selling directly to consumers without
>> discussing details with operators. I also feel that the vendors of
>> mobile equipment would benefit from having a more unified set of
>> requirements from the operators.
>>
>> Either these requirements can be gathered within the IETF for IP
>> related matters, or operators can try to do it in another venue. I
>> don't see why the IETF can't be the venue for this.
>>
>> -- Mikael Abrahamsson    email: swmike@swm.pp.se
>>
>> _______________________________________________ v6ops mailing list
>>  v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
>
> _______________________________________________ v6ops mailing list
> v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
>