Re: [ieee-ietf-coord] Draft Minutes from the 2019-06-19 IETF-IEEE 802 Coordination Meeting

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Mon, 24 June 2019 14:58 UTC

Return-Path: <pthubert@cisco.com>
X-Original-To: ieee-ietf-coord@ietfa.amsl.com
Delivered-To: ieee-ietf-coord@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AD60120419 for <ieee-ietf-coord@ietfa.amsl.com>; Mon, 24 Jun 2019 07:58:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 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, 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=P2UHzLPA; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=NA7/QFPm
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 1SqeACLeZM-L for <ieee-ietf-coord@ietfa.amsl.com>; Mon, 24 Jun 2019 07:58:37 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 719EC120422 for <ieee-ietf-coord@ietf.org>; Mon, 24 Jun 2019 07:58:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=16080; q=dns/txt; s=iport; t=1561388310; x=1562597910; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=44ShwjPAvdNgwfQh18STN67bNOp9REJKNOqKt3VpNss=; b=P2UHzLPAV2hroltNA2A/34dyaBLxisyTSpZ38E+q52PsWqkoDk3ELDtc eaUzUi+WmY6DXav1bn+bvQ9TDjF7y7cW9juevm4qPYsGeROhkesMpjXVK YE6kPW13ywqM2Gj7OpV0rpXR/7jW8Hw9s7izO9gVoZAkHRopWy/Fkmb1l g=;
IronPort-PHdr: =?us-ascii?q?9a23=3AISDY+hGibVE6KVOf2tvjcp1GYnJ96bzpIg4Y7I?= =?us-ascii?q?YmgLtSc6Oluo7vJ1Hb+e4z1Q3SRYuO7fVChqKWqK3mVWEaqbe5+HEZON0pNV?= =?us-ascii?q?cejNkO2QkpAcqLE0r+eeb2bzEwEd5efFRk5Hq8d0NSHZW2ag=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ACAwCQ5BBd/5JdJa1lGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAQGBZ4EVL1ADalUgBAsoCodTA45hTIIPgzmMLBGCawOCV4F?= =?us-ascii?q?9gUKBEANUCQEBAQwBARgBDAgCAQGEQAKCbSM4EwEDAQEEAQECAQVtijcMhUo?= =?us-ascii?q?BAQEEAQEQGxMBASwMDwIBCBEEAQEoBycLFAkIAgQTCBqDAYEdTQMdAQIMlzw?= =?us-ascii?q?CgTiIX4IignkBAQWEehiCEQMGgTSLXheBQD+BEUaBTlAuPoEEUIENAQECAYE?= =?us-ascii?q?mOisJgwaCJotjC4dZiFWNcQkCghSGTYZog3yCTIIohw2OEo0mhy+MC4NJAgQ?= =?us-ascii?q?CBAUCDgEBBYFnIYFYcBU7gmyCQTeDOYUUhT9yAYEojScBgSABAQ?=
X-IronPort-AV: E=Sophos;i="5.63,412,1557187200"; d="scan'208,217";a="581029904"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 24 Jun 2019 14:57:58 +0000
Received: from XCH-RCD-014.cisco.com (xch-rcd-014.cisco.com [173.37.102.24]) by rcdn-core-10.cisco.com (8.15.2/8.15.2) with ESMTPS id x5OEvwmw002605 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL) for <ieee-ietf-coord@ietf.org>; Mon, 24 Jun 2019 14:57:58 GMT
Received: from xhs-aln-002.cisco.com (173.37.135.119) by XCH-RCD-014.cisco.com (173.37.102.24) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 24 Jun 2019 09:57:57 -0500
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 24 Jun 2019 09:57:57 -0500
Received: from NAM04-CO1-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 24 Jun 2019 10:57:57 -0400
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=vNmBxhy3fRuvNVqZexBAALKzPe3AwIF7Bljnac9I9bo=; b=NA7/QFPmwiK2tzsju/t0knTYBFc7NsXtG3hZRwPqT+KV0D5PJ/HL03PBH4raLyrMe5djiOqztIQ61T5UIKMJS5E3VddtEsrAdYQhRjZZNwy6xrwO2jp6f48OMh+O824aSa8g2HXhS45Gbtr5oYB3c8la+PiKftzil7LOcTuyye0=
Received: from MN2PR11MB3565.namprd11.prod.outlook.com (20.178.250.159) by MN2PR11MB3840.namprd11.prod.outlook.com (20.178.254.147) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2008.16; Mon, 24 Jun 2019 14:57:55 +0000
Received: from MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::1ce9:1582:146c:c50a]) by MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::1ce9:1582:146c:c50a%6]) with mapi id 15.20.2008.014; Mon, 24 Jun 2019 14:57:55 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "<ieee-ietf-coord@ietf.org>" <ieee-ietf-coord@ietf.org>
Thread-Topic: [ieee-ietf-coord] Draft Minutes from the 2019-06-19 IETF-IEEE 802 Coordination Meeting
Thread-Index: AQHVJsQ4I4oEa/C0zkmRaPqqCYTlpqaq6pbA
Date: Mon, 24 Jun 2019 14:56:43 +0000
Deferred-Delivery: Mon, 24 Jun 2019 14:56:24 +0000
Message-ID: <MN2PR11MB35652B566D37F119F8B6505AD8E00@MN2PR11MB3565.namprd11.prod.outlook.com>
References: <2BD0E5EE-1F2C-4FF2-8576-B3131D194360@amsl.com>
In-Reply-To: <2BD0E5EE-1F2C-4FF2-8576-B3131D194360@amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=pthubert@cisco.com;
x-originating-ip: [173.38.220.59]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 1bd83498-b99f-4108-a275-08d6f8b456ff
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:MN2PR11MB3840;
x-ms-traffictypediagnostic: MN2PR11MB3840:
x-ms-exchange-purlcount: 10
x-microsoft-antispam-prvs: <MN2PR11MB3840AE7E4999400111ABF8C0D8E00@MN2PR11MB3840.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 007814487B
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(346002)(376002)(136003)(39860400002)(366004)(189003)(199004)(81166006)(64756008)(66556008)(73956011)(25786009)(2906002)(66476007)(52536014)(102836004)(66066001)(14454004)(74316002)(966005)(8676002)(66446008)(66574012)(606006)(81156014)(6666004)(76116006)(8936002)(6436002)(229853002)(86362001)(6246003)(71200400001)(256004)(54896002)(6306002)(71190400001)(478600001)(9686003)(33656002)(7736002)(99286004)(446003)(66946007)(55016002)(7696005)(5024004)(790700001)(3846002)(486006)(76176011)(6116002)(236005)(53936002)(476003)(26005)(53546011)(6506007)(316002)(68736007)(11346002)(5660300002)(186003)(491001); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3840; H:MN2PR11MB3565.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: tcJIJULf/LJysvH9UTkCe+525067SESrkr5e8zaKZKUks+QqJ0/EVzFj8qUZlYKHWnOp7ZrvzmhmCrErDklamC3b3zmaqW0V4yCmX37n5QBGME9gxXZe6B/X2M+DxOGuHDpwkot6Bzi5NKaSA6jfqdmXH7AccO5oBbQw1AqMACLO0p6l3cfvWE2EzfbUs/CFUbFty+3ikIyyG7289HerCZJ0LTcmt69k4XRdyReE+hCbQV53VIXYSB+yQEn3eAzq3IWEjxPAWX3ls9cxH5eacH6KzwmF8G+WBzyLca3BJAGuWx6tU5/sjjDMvxAbhWPuj2AHMKIRkf8nRnGFlE7NwIOpfi+fb89+OKRL7M3iG8jH/ab8kUV0tz/eY4TgJGwJlSIpOT8Hy8QUBUYsy/WX04ofExtQqrxfJLqWyN1WcMo=
Content-Type: multipart/alternative; boundary="_000_MN2PR11MB35652B566D37F119F8B6505AD8E00MN2PR11MB3565namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 1bd83498-b99f-4108-a275-08d6f8b456ff
X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Jun 2019 14:57:55.5680 (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: pthubert@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3840
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.24, xch-rcd-014.cisco.com
X-Outbound-Node: rcdn-core-10.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ieee-ietf-coord/uE-AmhRn0_NUbRnCxbmQzlOB11U>
Subject: Re: [ieee-ietf-coord] Draft Minutes from the 2019-06-19 IETF-IEEE 802 Coordination Meeting
X-BeenThere: ieee-ietf-coord@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Management-level discussions between IEEE and IETF on topics of interest to both SDOs <ieee-ietf-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ieee-ietf-coord>, <mailto:ieee-ietf-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ieee-ietf-coord/>
List-Post: <mailto:ieee-ietf-coord@ietf.org>
List-Help: <mailto:ieee-ietf-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ieee-ietf-coord>, <mailto:ieee-ietf-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jun 2019 14:58:42 -0000

Dear all:

As a follow up on the discussion of SAVI and IEEE 802.11.

Please note that I published draft-thubert-6man-ipv6-over-wireless<https://tools.ietf.org/html/draft-thubert-6man-ipv6-over-wireless> to explain better the issues with the SAVI draft and how RFC 8505 family solves them.
Please note that as an implementor of SAVI in my company's Wi-Fi gear, I have a first-hand view on these issues. In the introduction you'll find the following:

"
   Discovering peer addresses by snooping the IPV6 ND protocol as
   proposed for SAVI [I-D.bi-savi-wlan<https://tools.ietf.org/html/draft-thubert-6man-ipv6-over-wireless-03#ref-I-D.bi-savi-wlan>;] was found to be unreliable.  An
   IPv6 address may not be discovered immediately due to a packet loss,
   or if a "silent" node is not currently using one of its addresses,
   e.g., a node that waits in wake-on-lan state.  A change of state,
   e.g. due to a movement, may be missed or misordered, leading to
   unreliable connectivity and an incomplete knowledge of the set of
   peers.

   Wireless ND (WiND) introduces a new approach to IPv6 ND that is
   designed to apply to the WLANs and WPANs types of networks.  On the
   one hand, WiND avoids the use of broadcast operation for Address
   Resolution and Duplicate Address Detection, and on the other hand,
   WiND supports use cases where Subnet and MAC-level domains are not
   congruent, which is common in those types of networks unless a
   specific MAC-Level emulation is provided.


   To achieve this, WiND applies routing inside the Subnets, which

   enables MultiLink Subnets.  Hosts register their addresses to their

   serving routers with [RFC8505<https://tools.ietf.org/html/rfc8505>;].  With the registration, routers have

   a complete knowledge of the hosts they serve and in return, hosts

   obtain routing services for their registered addresses.  The

   registration is abstract to the routing protocol, and it can be

   protected to prevent impersonation attacks with [I-D.ietf-6lo-ap-nd<https://tools.ietf.org/html/draft-thubert-6man-ipv6-over-wireless-03#ref-I-D.ietf-6lo-ap-nd>;].

   The routing service can be a simple reflexion in a Hub-and-Spoke
   Subnet that emulates an IEEE Std 802.11 Infrastructure BSS at Layer
   3.  It can also be a full-fledge routing protocol, in particular RPL
   [RFC6550<https://tools.ietf.org/html/rfc6550>;] that was designed to adapt to various LLNs such as WLAN and
   WPAN radio meshes with the concept of Objective Function.  Finally,
   the routing service can also be ND proxy that emulates an IEEE Std
   802.11 Infrastructure ESS at Layer 3.  WiND specifies the IPv6
   Backbone Router for that purpose in [I-D.ietf-6lo-backbone-router<https://tools.ietf.org/html/draft-thubert-6man-ipv6-over-wireless-03#ref-I-D.ietf-6lo-backbone-router>;].

   More details on WiND can be found in Section 4.1<https://tools.ietf.org/html/draft-thubert-6man-ipv6-over-wireless-03#section-4.1>;.

"

I'm happy to discuss the draft on this list but would rather we copy 6MAN since I plan to present the draft there.

All the best,

Pascal

From: ieee-ietf-coord <ieee-ietf-coord-bounces@ietf.org>; On Behalf Of Cindy Morgan
Sent: mercredi 19 juin 2019 19:26
To: <ieee-ietf-coord@ietf.org>; <ieee-ietf-coord@ietf.org>;
Subject: [ieee-ietf-coord] Draft Minutes from the 2019-06-19 IETF-IEEE 802 Coordination Meeting

All,

Attached please find draft minutes from yesterday's coordination meeting. Please let me know if you have any changes or corrections.


Best regards,
Cindy
_______________________________________________
ieee-ietf-coord mailing list
ieee-ietf-coord@ietf.org<mailto:ieee-ietf-coord@ietf.org>
https://www.ietf.org/mailman/listinfo/ieee-ietf-coord