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

Tore Anderson <> Thu, 15 November 2012 15:12 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 37A1821F8513 for <>; Thu, 15 Nov 2012 07:12:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id BG+WVnNMeSiN for <>; Thu, 15 Nov 2012 07:12:19 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 94A8221F8488 for <>; Thu, 15 Nov 2012 07:12:19 -0800 (PST)
Received: from localhost (localhost.localdomain []) by (Postfix) with ESMTP id E91C5182004B; Thu, 15 Nov 2012 16:12:17 +0100 (CET)
X-Virus-Scanned: amavisd-new at
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id iM6LMq+dd7rv; Thu, 15 Nov 2012 16:12:12 +0100 (CET)
Received: from ( []) by (Postfix) with ESMTPSA id 96D5F1820057; Thu, 15 Nov 2012 16:12:10 +0100 (CET)
Message-ID: <>
Date: Thu, 15 Nov 2012 16:12:10 +0100
From: Tore Anderson <>
Organization: Redpill Linpro AS
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121016 Thunderbird/16.0.1
MIME-Version: 1.0
References: <>
In-Reply-To: <>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: IPv6 Ops WG <>
Subject: Re: [v6ops] draft-binet-v6ops-cellular-host-requirements-00.txt
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: v6ops discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 15 Nov 2012 15:12:26 -0000


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 -