Re: [v6ops] draft-binet-v6ops-cellular-host-requirements-00.txt

<david.binet@orange.com> Thu, 15 November 2012 16:05 UTC

Return-Path: <david.binet@orange.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCEAA21F845E for <v6ops@ietfa.amsl.com>; Thu, 15 Nov 2012 08:05:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.648
X-Spam-Level:
X-Spam-Status: No, score=-1.648 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6, UNPARSEABLE_RELAY=0.001]
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 WNjt+9o55BSQ for <v6ops@ietfa.amsl.com>; Thu, 15 Nov 2012 08:05:08 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id A5C9321F897C for <v6ops@ietf.org>; Thu, 15 Nov 2012 08:05:07 -0800 (PST)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm14.si.francetelecom.fr (ESMTP service) with ESMTP id E1A1D22C550; Thu, 15 Nov 2012 17:05:06 +0100 (CET)
Received: from puexch91.nanterre.francetelecom.fr (unknown [10.101.44.48]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id C78BD35C065; Thu, 15 Nov 2012 17:05:06 +0100 (CET)
Received: from PUEXCB1A.nanterre.francetelecom.fr ([10.101.44.14]) by puexch91.nanterre.francetelecom.fr ([10.101.44.48]) with mapi; Thu, 15 Nov 2012 17:05:01 +0100
From: <david.binet@orange.com>
To: Tore Anderson <tore.anderson@redpill-linpro.com>, BOUCADAIR Mohamed OLNC/OLN <mohamed.boucadair@orange.com>
Date: Thu, 15 Nov 2012 17:04:59 +0100
Thread-Topic: [v6ops] draft-binet-v6ops-cellular-host-requirements-00.txt
Thread-Index: Ac3DQ6OI3aQDkepgQaSdLjfteMEhpgAAnXuQ
Message-ID: <24584_1352995506_50A512B2_24584_1846_1_1B2E7539FECD9048B261B791B1B24A7C3EF3E0DDBA@PUEXCB1A.nanterre.francetelecom.fr>
References: <94C682931C08B048B7A8645303FDC9F36E947B1328@PUEXCB1B.nanterre.francetelecom.fr> <50A5064A.1070208@redpill-linpro.com>
In-Reply-To: <50A5064A.1070208@redpill-linpro.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2012.10.24.110314
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] draft-binet-v6ops-cellular-host-requirements-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 15 Nov 2012 16:05:13 -0000

Hi,

It seems it is an implementation issue.
REQ#8 mandates the use of Interface Identifier sent by the Gateway to configure the link local address and actually it is consistent with 3GPP specification. 
We have integrated in last version of the draft some other implementation issue we may have on Wi-Fi interface (report to REQ#19).  
Please provide some text if you want to describe some implementation issues you have identified.  

Best Regards
David

> -----Message d'origine-----
> De : v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] 
> De la part de Tore Anderson
> Envoyé : jeudi 15 novembre 2012 16:12
> À : BOUCADAIR Mohamed OLNC/OLN
> Cc : IPv6 Ops WG
> Objet : Re: [v6ops] 
> draft-binet-v6ops-cellular-host-requirements-00.txt
> 
> Hi,
> 
> REQ#8 («the cellular host MUST use the interface identifier 
> sent in PDP Context Accept message to configure its link 
> local address») is rather tricky to implement for a cellular 
> dongle that emulate an Ethernet device (such as an USB CDC 
> Ethernet class device). In that case, the dongle provides an 
> invented Ethernet MAC address from which the host derives an 
> link local address using EUI-64.
> 
> Since this link local address does not have the correct 
> interface identifier, ND may (partially) break. In 
> particular, I've experienced that when sending an RS from 
> such an EUI-64-derived link local address to the network, the 
> GGSN reponds with an RA that is unicasted to the link local 
> address the network expects the hosts to have. The host has 
> no knowledge of this address, and discards the RA.
> 
> I don't have a good answer to how this problem should be solved.
> However, if the document could make some recommendations (or 
> at least describe the problem), that would be good.
> 
> Best regards,
> --
> Tore Anderson
> Redpill Linpro AS - http://www.redpill-linpro.com 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
> 
_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified.
Thank you.