IETF Logo Mail Archive

Re: [v6ops] Windows 10 doesn't honour 'M' flag in RA

"STARK, BARBARA H" <bs7652@att.com> Wed, 13 December 2017 22:08 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 C2EEB1205F0; Wed, 13 Dec 2017 14:08:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.401
X-Spam-Level:
X-Spam-Status: No, score=-5.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, 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 qmeABsHuRs7h; Wed, 13 Dec 2017 14:08:04 -0800 (PST)
Received: from mx0a-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (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 4B60B126D85; Wed, 13 Dec 2017 14:08:04 -0800 (PST)
Received: from pps.filterd (m0049463.ppops.net [127.0.0.1]) by m0049463.ppops.net-00191d01. (8.16.0.21/8.16.0.21) with SMTP id vBDM7bdY040152; Wed, 13 Dec 2017 17:08:01 -0500
Received: from alpi154.enaf.aldc.att.com (sbcsmtp6.sbc.com [144.160.229.23]) by m0049463.ppops.net-00191d01. with ESMTP id 2eubftt5bb-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 13 Dec 2017 17:08:01 -0500
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 vBDM80oB022136; Wed, 13 Dec 2017 17:08:01 -0500
Received: from alpi132.aldc.att.com (alpi132.aldc.att.com [130.8.217.2]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id vBDM7ufx022116 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 13 Dec 2017 17:07:59 -0500
Received: from zlp30484.vci.att.com (zlp30484.vci.att.com [135.47.91.179]) by alpi132.aldc.att.com (RSA Interceptor); Wed, 13 Dec 2017 22:07:37 GMT
Received: from zlp30484.vci.att.com (zlp30484.vci.att.com [127.0.0.1]) by zlp30484.vci.att.com (Service) with ESMTP id 328BE4000341; Wed, 13 Dec 2017 22:07:37 +0000 (GMT)
Received: from GAALPA1MSGHUBAB.ITServices.sbc.com (unknown [130.8.218.151]) by zlp30484.vci.att.com (Service) with ESMTPS id 19A9C40006FB; Wed, 13 Dec 2017 22:07:37 +0000 (GMT)
Received: from GAALPA1MSGUSRBF.ITServices.sbc.com ([169.254.5.227]) by GAALPA1MSGHUBAB.ITServices.sbc.com ([130.8.218.151]) with mapi id 14.03.0361.001; Wed, 13 Dec 2017 17:07:36 -0500
From: "STARK, BARBARA H" <bs7652@att.com>
To: Naveen Kottapalli <naveen.sarma@gmail.com>
CC: v6ops list <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>
Thread-Topic: Windows 10 doesn't honour 'M' flag in RA
Thread-Index: AQHTcxnIMEBQ+YpiC0KlzMNBptkKMaM/UtuWgAKBR0A=
Date: Wed, 13 Dec 2017 22:07:36 +0000
Message-ID: <2D09D61DDFA73D4C884805CC7865E6114DCD4719@GAALPA1MSGUSRBF.ITServices.sbc.com>
References: <CANFmOtnJiKtBH9WuOjfAAaOxmrQ8SanU1ATiEY_zSA9DbAuUAA@mail.gmail.com> <CAAedzxptEK5nZTVHwuzG0aK119Ns61cdfNT3JWPafTGcAxMeeg@mail.gmail.com> <CANFmOtm2SU13o3Wey1XqhQf0WuuTzm80XXPp7Q9UGiV6Kvh5DA@mail.gmail.com>
In-Reply-To: <CANFmOtm2SU13o3Wey1XqhQf0WuuTzm80XXPp7Q9UGiV6Kvh5DA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.70.212.84]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-12-13_13:, , 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=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=359 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1712130304
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/YU_SLCmJvaUg_Jv-1HBkdieFvQA>
Subject: Re: [v6ops] Windows 10 doesn't honour 'M' flag in RA
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 13 Dec 2017 22:08:06 -0000

Hi Naveen (or anyone else who cares to answer),

> In our recent testing, we observed that Windows 10 doesn't honour 'M' flag
> in RA.  It's not just Windows 10, same behaviour is observed with latest Mac
> OS as well.  

I'm curious: What is being harmed by this behavior? I can definitely see advantages in Windows and Mac OS doing it this way; I'm just struggling to understand the disadvantages. Years ago, there was a problem in some ISP networks prior to full launch of IPv6 and prior to support for SOL_MAX_RT (RFC 7083) of DHCPv6 servers being overwhelmed by Solicit messages they were configured not to respond to (because IPv6 wasn't formally supported). But with SOL_MAX_RT, that really shouldn't be an issue. So what is being broken by this behavior now?

Barbara

v2.23.0 | Report a Bug | By Email