Re: [ieee-ietf-coord] Please review draft-bi-savi-wlan-15

"Pascal Thubert (pthubert)" <> Sat, 10 November 2018 03:52 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id AAB5D130E07 for <>; Fri, 9 Nov 2018 19:52:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, 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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id s11wpe2MGug4 for <>; Fri, 9 Nov 2018 19:52:52 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 7EDC6130DD5 for <>; Fri, 9 Nov 2018 19:52:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=7852; q=dns/txt; s=iport; t=1541821972; x=1543031572; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=x0j/1r0oeXbFG2eCGeI2JDAXpe5kvY8HwIS7YBQR7pE=; b=jqLJSc5DXL+OP01tg6lxX68zak7SX8Xe5N6fIQ1B/D/2QhAl56lySlq+ nweF02f0MCdzpvCKSu1P0NlvGwLgWAcz8qik8R+/AN4BnGuIdAvRlpMRq b7DGrz/Vtw/UKEnXCcQHvswyqIzL5wmS0e7+rWJZD4nkClS93b8ZmfNGd o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.54,485,1534809600"; d="scan'208,217";a="477519495"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Nov 2018 03:52:51 +0000
Received: from ( []) by (8.15.2/8.15.2) with ESMTPS id wAA3qpT6004465 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 10 Nov 2018 03:52:51 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1395.4; Fri, 9 Nov 2018 21:52:50 -0600
Received: from ([]) by ([]) with mapi id 15.00.1395.000; Fri, 9 Nov 2018 21:52:50 -0600
From: "Pascal Thubert (pthubert)" <>
To: Russ Housley <>, "" <>
CC: "Jerome Henry (jerhenry)" <>
Thread-Topic: [ieee-ietf-coord] Please review draft-bi-savi-wlan-15
Date: Sat, 10 Nov 2018 03:52:47 +0000
Deferred-Delivery: Sat, 10 Nov 2018 03:52:24 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: fr-FR, en-US
Content-Language: en-US
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_ee1377bb05f4499a833f687c3f79d072XCHRCD001ciscocom_"
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [ieee-ietf-coord] Please review draft-bi-savi-wlan-15
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Management-level discussions between IEEE and IETF on topics of interest to both SDOs <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 10 Nov 2018 03:52:55 -0000

Hello Russ

This is all related to the discussion on rfc-to-be 8505. The SAVI draft represents a personal view of what we have to do when RFC 8505 does not exist; as an implementer of it I can tell you that a very close form of that really exists in the products and is what allows us today to scale wireless in conferences the size of this one. OTOH, snooping fails to provide a complete and accurate views of the network and there are tons of tricks to cope with that beyond what the naïve non-implementer could guess. Those hidden operations may very well contradict future changes in the official standards, so there is a hidden mine in all this game. The 802.11 model of an association is a lot preferable to snooping. RFC 8505 will be that association at layer 3.

All the best,


From: ieee-ietf-coord <>; On Behalf Of Russ Housley
Sent: samedi 10 novembre 2018 10:04
Subject: [ieee-ietf-coord] Please review draft-bi-savi-wlan-15

Suresh reports that he has received a request to publish

It involves a source address validation solution for WLAN.

A review from Bernard Aboba brought up some issues that may be of relevance to 802.11. At this stage, comments should be sent to the IETF mail list (<>).