Re: [v6ops] Apple and IPv6, a few clarifications - 64share

"Hemant Singh (shemant)" <> Mon, 22 June 2015 12:13 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 648611A0368 for <>; Mon, 22 Jun 2015 05:13:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -12.612
X-Spam-Status: No, score=-12.612 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id c-umHRdlaQz7 for <>; Mon, 22 Jun 2015 05:13:37 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 425471A0358 for <>; Mon, 22 Jun 2015 05:13:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=1009; q=dns/txt; s=iport; t=1434975217; x=1436184817; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=pnloHy6JDUfaXBpFfn18Dqxiaduwj+dpT1pACGtgidY=; b=JdyOQkIA0ly5ugLU3ZlEUMSetZ4/YCPVgeeExVx37EcuodjlmyL8L9Es TuXLvEh3A4II8F0sk9znEjdmOBRvTT2RQCnx7UAOW0G2Gwjlzp9dknGq8 4eiAo8aqf5dQ4iGEVSS9rCneuT3YWd0vunZmhnGMK/MZDyZoO9Uv8xwOX 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.13,659,1427760000"; d="scan'208";a="161459361"
Received: from ([]) by with ESMTP; 22 Jun 2015 12:13:36 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id t5MCDaJf020192 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 22 Jun 2015 12:13:36 GMT
Received: from ([]) by ([]) with mapi id 14.03.0195.001; Mon, 22 Jun 2015 07:13:36 -0500
From: "Hemant Singh (shemant)" <>
To: Jeremy Visser <>, "" <>
Thread-Topic: [v6ops] Apple and IPv6, a few clarifications - 64share
Thread-Index: AQHQrN24pinb6cqb6Eq6EbqjHCiHuJ24u+QA//+yDjA=
Date: Mon, 22 Jun 2015 12:13:35 +0000
Message-ID: <>
References: <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [v6ops] Apple and IPv6, a few clarifications - 64share
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 22 Jun 2015 12:13:38 -0000

-----Original Message-----
From: v6ops [] On Behalf Of Jeremy Visser
Sent: Monday, June 22, 2015 7:45 AM
Subject: Re: [v6ops] Apple and IPv6, a few clarifications - 64share

>Why stop at /63?

>If you can think of a use for two subnets, I can think of a use for three.  Or four.  Or sixteen.  Or two hundred and fifty-six...

Also, if the phone uses DHCPv6 PD, then the phone's interface is a requesting router as per RFC3633.  Note, the IPv6 CE Router document in RFC7084 and its WPD-2 bullet.  One should round off prefix length to the nearest nibble.  Thus use a /60.    Additionally, since the phone has disparate transport interfaces in cellular and wifi to forward traffic between, it is best to use routing between the two interfaces.  See what subset of rfc7084 can be used in the phone.  Additionally, an IPv6 CE router implementation is available on Linux in OpenWRT for Linksys routers.