IETF Logo Mail Archive

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

"Rajiv Asati (rajiva)" <rajiva@cisco.com> Tue, 29 October 2019 12:39 UTC

Return-Path: <rajiva@cisco.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 97039120074 for <v6ops@ietfa.amsl.com>; Tue, 29 Oct 2019 05:39:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=NM1CE6uG; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=LQNloD8Z
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 FMj1Fqwkr0DE for <v6ops@ietfa.amsl.com>; Tue, 29 Oct 2019 05:39:00 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E95F12004A for <v6ops@ietf.org>; Tue, 29 Oct 2019 05:39:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7305; q=dns/txt; s=iport; t=1572352740; x=1573562340; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=/Kyjo4Y25NkclXCWTWedPjM9kMJbMtBUzxYJ3mGDgXE=; b=NM1CE6uGjvnDJMfmGMQHArokxzu/K+QKfCkcnidFvZEQ7IglnPG0J2ir nG67K8FhjBdrfDVJDbw5S/fEs9OTaJUJVBp4wGiPO4Nc3Q+DRiavRtYkU GUjJUAtcNiRdOysp07W+UmyR7eqA/a8+/bKfOipvDaT/Sfj9P8hwGojA7 Y=;
IronPort-PHdr: 9a23:mueyCRQIYzCn/3pQle6GjhOdMtpsv++ubAcI9poqja5Pea2//pPkeVbS/uhpkESUDNfA8/wRje3QvuigQmEG7Zub+FE6OJ1XH15g640NmhA4RsuMCEn1NvnvOjYzHsVcXXdu/mqwNg5eH8OtL1A=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0APAAAmMrhd/4kNJK1lGgEBAQEBAQEBAQMBAQEBEQEBAQICAQEBAYFpBQEBAQELAYEbL1AFbFggBAsqhChRgnUDhFqGE4wziTWEYYEugSQDVAkBAQEMAQEYAQoKAgEBhEACF4NAJDQJDgIDCQEBBAEBAQIBBQRthTcMhVICBAEBEBEdAQEsCwEPAgEIDjEDAgICHwYLFBECBA4FIoMAAYF5TQMuAQIMpzMCgTiIYHWBMoJ+AQEFgTQBgRSCRQ0LghcDBoE2AYwOGIFAP4E4H4JMPoIbRwEBAgGCC4JjMoIsj3mFPJd2QQqCJIcQihKEDBQHgjyXII9/hmqCEY8OAgQCBAUCDgEBBYFSOYFYcBU7KgGCQVAQFIMGg3OFFIU/dAGBJ45eAQE
X-IronPort-AV: E=Sophos;i="5.68,243,1569283200"; d="scan'208,217";a="653470489"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 29 Oct 2019 12:38:59 +0000
Received: from XCH-ALN-019.cisco.com (xch-aln-019.cisco.com [173.36.7.29]) by alln-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id x9TCcxNj022605 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 29 Oct 2019 12:38:59 GMT
Received: from xhs-aln-003.cisco.com (173.37.135.120) by XCH-ALN-019.cisco.com (173.36.7.29) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 29 Oct 2019 07:38:58 -0500
Received: from xhs-aln-003.cisco.com (173.37.135.120) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 29 Oct 2019 07:38:58 -0500
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Tue, 29 Oct 2019 07:38:58 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=aCdkxhCplBAo32Ilfgo5UVAAwwNSKRzLnc6yW1G4Uf8bzbf0IXW5h84FaqBpPzXLutrQK8epUu5uyK2AyxeYtmfuLS9wUWKlVcf3zSFU6P7zOc2z/OFKe9Z5fXhMPSK+DKRK6HGNyAU5tBuc5gA6O4P5RPjRjDH2Dg0raEGwCp5hQDT6a0QHQlQlftUH/LhrQznwp0sFkL7XUvbzf2CefRqQgwtOU0cvT3LSM64EZvV0QH6UEmUVfUmfIAutUAoYJfXKwd6qaeOU/o0o2xYgeweng3yA2cY219VuzZvtFy5ga6bid17V95mDtQHxpGjslB48Dwr5yWMGhe544CdepA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=/Kyjo4Y25NkclXCWTWedPjM9kMJbMtBUzxYJ3mGDgXE=; b=mYUep6Wkve80BGKazsMG4W26au7f0tYqRxhHp2LWrzjT9zQLs1zH+AYg2J/xLZOSYoF31gQDCh6z/hlak4n+xv6G6Nd3PXrGTZ3nQAf9ObCGCKVwC3tQHrTGilTQRuMlh5zAdBlqdyKV515DTnq94aQBiLcY3u346t6KpMEmZBmlE4hBUqCzLyEkXmcvt5WWsi3pihu6dthQwmV7OqvFntYA5ZilTbrXvBSKcKqVZUSqW35q2cK0zB+s82klxUnSolXjmXszqxfin5ciBFDrs3RG+NTMR6VeYLIRsFDEtPYCPBSkYZaj1kE2oFyP4GrVAzAPNep4Sb3IhPDEGUcMGA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=/Kyjo4Y25NkclXCWTWedPjM9kMJbMtBUzxYJ3mGDgXE=; b=LQNloD8ZE5AZlfr2hdBtMxG5YpYGHkiJXLSj1OLsl+st/91woXn2wZZj05tRUO2jpHYmnvhVMDZ9g64tlgLEHTZyuLR59kcgPUa6hugChpkqKfRBhmbrub9hL226wVJUVVQf3bcilzv4Htft8cL8K9qUBxjgGs52PBBstm/u3T4=
Received: from MN2PR11MB4319.namprd11.prod.outlook.com (52.135.39.155) by MN2PR11MB3791.namprd11.prod.outlook.com (20.178.254.78) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2408.17; Tue, 29 Oct 2019 12:38:57 +0000
Received: from MN2PR11MB4319.namprd11.prod.outlook.com ([fe80::a5e4:8223:5e72:6181]) by MN2PR11MB4319.namprd11.prod.outlook.com ([fe80::a5e4:8223:5e72:6181%7]) with mapi id 15.20.2387.027; Tue, 29 Oct 2019 12:38:57 +0000
From: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
To: Ted Lemon <mellon@fugue.com>
CC: Alexandre Petrescu <alexandre.petrescu@gmail.com>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] out-of-focus: why DHCPv6 breaks Android computers?
Thread-Index: AQHVjXSxmpGXsWk+qkKRidIrKoxyNqdwwdcAgACs44CAAAyTgIAAFXCA
Date: Tue, 29 Oct 2019 12:38:57 +0000
Message-ID: <EA825926-BD88-4B10-84F8-91E25C1BBA6D@cisco.com>
References: <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:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=rajiva@cisco.com;
x-originating-ip: [2600:387:2:803::81]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: dd5a1e1e-6bd7-47f2-74b1-08d75c6cf77f
x-ms-traffictypediagnostic: MN2PR11MB3791:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <MN2PR11MB3791500CF4BBDFBE3BF21F26C7610@MN2PR11MB3791.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:2887;
x-forefront-prvs: 0205EDCD76
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(39860400002)(366004)(346002)(136003)(396003)(376002)(199004)(189003)(54896002)(53546011)(6506007)(606006)(102836004)(229853002)(14454004)(25786009)(476003)(2906002)(6486002)(478600001)(8676002)(186003)(54906003)(66574012)(486006)(81156014)(6512007)(966005)(36756003)(256004)(14444005)(6116002)(7736002)(76176011)(6306002)(66446008)(64756008)(66556008)(66476007)(236005)(6436002)(76116006)(86362001)(4326008)(4744005)(6246003)(33656002)(316002)(5660300002)(66946007)(81166006)(6916009)(8936002)(99286004)(11346002)(71190400001)(446003)(46003)(71200400001)(2616005); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3791; H:MN2PR11MB4319.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: kFAMrJoXIqhChrVhPXjHeWmkfUxO/k4Da394zYL+VIb8B4nf/zvF1fO3PnSPcd6366n2MUGzaHT4giOiTCAYGkoBlaf+CdyL2tx6AvAUh7YjU+NTsVSWyX/MIA0jKBLpm1I/Mr8CuaUTk1hZfa8ZWWgJNPnr68M8LA3+XhlDEU+aGTRBn5jzFt/tcCb2dLD6jmdFNrhrYazx+i0z3LY5mqunIhzB/c9TrF2BjVn+ESN9Dn5CmwcBlNBBWzKLtrjY23qnKo0pfdGADqWcn/+LMwMVJlHhNnFtzdcp+Ye4vNhvjc2ZTvA+itOdArJzYvZz53JfvdXLLCIx5/7hA7+yEVlxdHV+AMzP03a1JS2teRe+IJr66ECHJn9K5bwjxOxN70Q1MLmgIBkwoaWauPNXnNnQ0NGn34OwdJ8beyVK7u+jm/TGBVPLyjPZZGeeKPLtDLxG8FBTSbuKuRpJWLtLH9CWK6BbiiH8TBxW+jYu8Gs=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_EA825926BD884B1084F891E25C1BBA6Dciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: dd5a1e1e-6bd7-47f2-74b1-08d75c6cf77f
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Oct 2019 12:38:57.1774 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: iprJT0rLSNkMkEw7SraFm5GHk0sLqGZ1gQEcf4+AFxyHFSTcvgKxQVRkssObEJ49+luTzxafFoCL/rQUt4VbPw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3791
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.29, xch-aln-019.cisco.com
X-Outbound-Node: alln-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/lkfeT7PJGm0hQl-PV2HhiEh8MhI>
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 12:39:03 -0000

Indeed. CPE router should allow keeping both M and A flags, to allow simultaneous usage of DHCPv6 and SLAAC by the hosts.

About time to update RFC7084 -
https://tools.ietf.org/html/rfc7084#section-4.3



Cheers,
Rajiv


On Oct 29, 2019, at 7:22 AM, Ted Lemon <mellon@fugue.com> wrote:

 On Oct 29, 2019, at 6:37 AM, Alexandre Petrescu <alexandre.petrescu@gmail.com<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.

_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops

v2.23.0 | Report a Bug | By Email