IETF Logo Mail Archive

Re: [v6ops] out-of-focus: why DHCPv6 breaks Android computers?

"STARK, BARBARA H" <bs7652@att.com> Tue, 29 October 2019 14:42 UTC

Return-Path: <bs7652@att.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 D353B12091D for <v6ops@ietfa.amsl.com>; Tue, 29 Oct 2019 07:42:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 9ZoSHImQlv7b for <v6ops@ietfa.amsl.com>; Tue, 29 Oct 2019 07:42:50 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0a-00191d01.pphosted.com [67.231.149.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6574E1208DF for <v6ops@ietf.org>; Tue, 29 Oct 2019 07:42:50 -0700 (PDT)
Received: from pps.filterd (m0049295.ppops.net [127.0.0.1]) by m0049295.ppops.net-00191d01. (8.16.0.42/8.16.0.42) with SMTP id x9TESIuM029185; Tue, 29 Oct 2019 10:42:46 -0400
Received: from alpi154.enaf.aldc.att.com (sbcsmtp6.sbc.com [144.160.229.23]) by m0049295.ppops.net-00191d01. with ESMTP id 2vxq22rsr0-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 29 Oct 2019 10:42:45 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id x9TEgh21016494; Tue, 29 Oct 2019 10:42:44 -0400
Received: from zlp30483.vci.att.com (zlp30483.vci.att.com [135.47.91.189]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id x9TEgcvA016396 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 29 Oct 2019 10:42:42 -0400
Received: from zlp30483.vci.att.com (zlp30483.vci.att.com [127.0.0.1]) by zlp30483.vci.att.com (Service) with ESMTP id 76A0B4014663; Tue, 29 Oct 2019 14:42:38 +0000 (GMT)
Received: from GAALPA1MSGHUBAG.ITServices.sbc.com (unknown [130.8.218.156]) by zlp30483.vci.att.com (Service) with ESMTPS id 636974014661; Tue, 29 Oct 2019 14:42:38 +0000 (GMT)
Received: from GAALPA1MSGUSRBF.ITServices.sbc.com ([169.254.5.98]) by GAALPA1MSGHUBAG.ITServices.sbc.com ([130.8.218.156]) with mapi id 14.03.0468.000; Tue, 29 Oct 2019 10:42:38 -0400
From: "STARK, BARBARA H" <bs7652@att.com>
To: 'Ted Lemon' <mellon@fugue.com>, 'Alexandre Petrescu' <alexandre.petrescu@gmail.com>
CC: "'v6ops@ietf.org'" <v6ops@ietf.org>
Thread-Topic: [v6ops] out-of-focus: why DHCPv6 breaks Android computers?
Thread-Index: AQHVjXSnwl4m0JrsUk+Tlv2FJuKF5KdxBOYAgACs4oCAAAyTgP//7gMQ
Date: Tue, 29 Oct 2019 14:42:37 +0000
Message-ID: <2D09D61DDFA73D4C884805CC7865E611536B4B1B@GAALPA1MSGUSRBF.ITServices.sbc.com>
References: <2b617ab1-018a-8f03-4d8b-081c09c9c88a@gmail.com> <CAFU7BATuer=XutH-G0v0cSCqmcULU2UgHe9GGhS0OhUY2brU4A@mail.gmail.com> <b43f56b8-e5d6-b875-c594-656bc6ba0b45@gmail.com> <8DA54CF0-B7D7-4E4B-BA85-EA024401DEAC@fugue.com>
In-Reply-To: <8DA54CF0-B7D7-4E4B-BA85-EA024401DEAC@fugue.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.70.242.121]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-10-29_04:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1031 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1908290000 definitions=main-1910290140
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/XHLsmqfgOCfXyUSbvmdxB1XMcrA>
Subject: Re: [v6ops] out-of-focus: why DHCPv6 breaks Android computers?
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 29 Oct 2019 14:42:53 -0000

> From: Ted Lemon
>> On Oct 29, 2019, at 6:37 AM, Alexandre Petrescu <mailto:alexandre.petrescu@gmail.com> wrote:
>> Well no.  After  activating DHCPv6 on CPE the CPE sent three RAs
>> changing the Lifetime and flipping the M(anaged) and A(utonomous) flags.
>> 
>> Packet dumps available upon request.

> That’s the problem.   It should turn on the managed bit but not turn off the autonomous bit.  The two can validly be on at the same time.

> Of course, since their meanings are deprecated, it’s not too surprising that implementations get this wrong.

Deprecated? Their meanings aren't deprecated at all, AFAIK. Specifically, the Autonomous bit continues to mean "this prefix can be used to generate SLAAC addresses". If there is no prefix with A set, then there is no prefix to use to generate SLAAC addresses. If there is a prefix with A set, hosts are free to create SLAAC addresses from it to their hearts' content. Or not. I agree that based on Alex's description of the A bit being flipped, it suggests there are no prefixes being advertised with A set -- which means SLAAC is being disabled.

And I'm not going to get started with debating the "M" hint. M's meaning is very clear. Problems arise when people try to attribute or (think they can) demand more meaning than it has. It's a beautiful little bit, and I like it very much. It doesn't deserve to be maligned like this. It has served me very well.
Barbara

v2.23.0 | Report a Bug | By Email