March 2012 doc.: IEEE 802.15-15-12-0109-00-0009 March 2012 Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title:

Slides:



Advertisements
Similar presentations
Doc.: IEEE xxx Submission January 2015 N. Sato and K. Fukui (OKI)Slide 1 Project: IEEE P Working Group for Wireless Personal Area.
Advertisements

<month year> doc.: IEEE s May 2015
Submission Title: [Add name of submission]
<month year> doc.: IEEE <# > <April 2008>
June 2006 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Proposed Scenarios for Usage Model Document.
doc.: IEEE <doc#>
doc.: IEEE <doc#>
<month year> <doc.: IEEE doc> May 2015
doc.: IEEE <doc#>
doc.: IEEE <doc#>
May 2018 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Considerations on general MAC frame] Date Submitted:
doc.: IEEE <doc#>
September Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [ to adaptation.
March 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Toumaz response to TG6 Call for Applications]
<month year> doc.: IEEE < e>
March 2018 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [SG SECN Call for Proposals] Date Submitted:
<May,2009> doc.: IEEE <doc .....> <July 2009>
<doc.: IEEE −doc>
Nov 2013 Robert Moskowitz, Verizon
1/1/2019<month year> doc.: IEEE
Robert Moskowitz, Verizon
Robert Moskowitz, Verizon
Robert Moskowitz, Verizon
1/2/2019<month year> doc.: IEEE Jan 2013
Robert Moskowitz, Verizon
Robert Moskowitz, Verizon
Robert Moskowitz, Verizon
Robert Moskowitz, Verizon
<month year> <doc.: IEEE doc> March 2015
<month year> <doc.: IEEE doc> September 2015
<month year> <doc.: IEEE doc> July 2015
Submission Title: [WG WNG Liaison Report January08]
<month year> <doc.: IEEE doc> December 2015
Submission Title: [One-to-many and many-to-many peering procedures]
Source: [Pat Kinney] Company [Kinney Consulting LLC]
<month year> <doc.: IEEE doc> Julyl 2015
September Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [ to adaptation.
<month year> <doc.: IEEE doc> March 2015
<author>, <company>
doc.: IEEE /XXXr0 Sep 19, 2007 June 2009
doc.: IEEE <doc#>
<month year> <doc.: IEEE doc> May 2015
<month year> doc.: IEEE <030158r0> January 2004
Robert Moskowitz, Verizon
Submission Title: [One-to-many and many-to-many peering procedures]
May 2018 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Considerations on general MAC frame] Date Submitted:
<month year> doc.: IEEE < e>
July 2012 Robert Moskowitz, Verizon
April 19 July 2010 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: WNG Closing Report for San Diego.
<month year> <doc.: IEEE doc> Julyl 2015
<month year> <doc.: IEEE doc> March 2015
<month year> doc.: IEEE August 2014
Submission Title: [Multi-hop Peering for PAC]
Tero Kivinen, AuthenTec
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [TG agreed text for frequency channel.
<month year> <doc.: IEEE doc> July 2015
<author>, <company>
<month year> doc.: IEEE <030158r0> <March 2003>
January 2000 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Study Group Summary and Motion for .15WG.
Tero Kivinen, AuthenTec
September 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Suggested TG3c PAR Changes] Date Submitted:
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [TG agreed text for frequency channel.
Nov Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Report on IEEE PAC Draft Status]
<month year> <doc.: IEEE doc> September 2015
<month year> <doc.: IEEE doc> March 2015
Submission Title: TG9ma Closing Report for July Meeting
Submission Title: TG9ma Agenda for September Meeting
Jan 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: TeraHertz Closing Report Date Submitted: January.
May 2014 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: TG9 Hop Discussion Date Submitted: May 15, 2014.
Submission Title: TG9ma Closing Report for July Meeting
Presentation transcript:

March 2012 doc.: IEEE 802.15-15-12-0109-00-0009 March 2012 Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: PANA over 802.15.9 Proposal (DCN 15-12-0109-00-0009) Date Submitted: March 2, 2012 Source: Yoshihiro Ohba, Toshiba Address 1 Komukai Toshiba-cho, Saiwai-ku, Kawasaki, 212-8582, Japan Voice:+81 (44) 549-2127, FAX: +81 (44) 520 1806, E-Mail:yoshihiro.ohba@toshiba.co.jp Re: IEEE P802.15.9 CFP Abstract: Proposal for PANA over 802.15.9 Purpose: To add PANA KMP support for 802.15.9 Notice: This document has been prepared to assist the IEEE P802.15. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Release: The contributor acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P802.15. Yoshihiro Ohba, Toshiba <author>, <company>

PANA KMP Support for 802.15.9 Yoshihiro Ohba and March 2012 doc.: IEEE 802.15-15-12-0109-00-0009 March 2012 PANA KMP Support for 802.15.9 Yoshihiro Ohba and Yasuyuki Tanaka (Toshiba), Stephen Chasko (Landis+Gyr), Subir Das (ACS) March 2, 2012 Yoshihiro Ohba, Toshiba <author>, <company>

PANA (RFC 5191) [Informative] doc.: IEEE 802.15-15-12-0109-00-0009 March 2012 PANA (RFC 5191) [Informative] PANA carries EAP between PaC (PANA Client) and PAA (PANA Authentication Agent) over UDP PANA message PaC PAA EAP Peer EAP Authenticator PaC PAA Message (when a 4-message EAP authentication method is used)  PCI  PAR[PRF-Algorithm, Integrity-Algorithm, Encryption-Algorithm*, EAP(msg#1)] PAN[PRF-Algorithm, Integrity-Algorithm, Encryption-Algorithm*, EAP(msg#2)] PAR[Nonce, EAP(msg#3)] PAN[Nonce, EAP(msg#4)] PAR[Result-Code, Key-Id, Session-Lifetime, EAP(Success), Encr-Encap*, AUTH] PAN[Key-Id, AUTH] (*) Encryption feature enabled by a PANA encryption extension (draft-yegin-pana-encr-avp) PCI: PANA-Client-Initiation PAR: PANA-Auth-Request PAN: PANA-Auth-Answer Yoshihiro Ohba, Toshiba

PANA Relay (RFC 6345) [Informative] doc.: IEEE 802.15-15-12-0109-00-0009 March 2012 PANA Relay (RFC 6345) [Informative] PANA Relay Element (PRE) is used when PaC and PAA are not able to directly communicate PANA-Relay (PRY) message is used for forwarding a PANA message in between PaC PRE PAA PANA message PRY message PANA message EAP Peer EAP Authenticator PaC PRE PAA Message  PCI PRY[PaC-Info., Relayed-Message{PCI}]  PRY[PaC-Info., Relayed-Message{PAR}] PAR PAN PRY[Pac-Info., Relayed-Message{PAN}] … PCI: PANA-Client-Initiation PAR: PANA-Auth-Request PAN: PANA-Auth-Answer PRY: PANA-Relay Yoshihiro Ohba, Toshiba

doc.: IEEE 802.15-15-12-0109-00-0009 March 2012 PANA over 802.15.9 Overview PANA PDU (w/o IP and UDP headers) is carried in KMP Payload between PaC and its parent node Parent node is PAA (for single hop case) or PRE (for multi-hop case) PANA PDU is carried over UDP/IP between PRE and PAA (out of the scope of 802.15.9) This guideline uses IPv6 due to straightforward mapping between EUI-64 address and IP address PAA performs network access authentication and authorization for PaC PANA serves as a bootstrapping KMP PAA may communicate with AAA server located outside the mesh network using AAA protocol (out of the scope of 802.15.9) Upon successful network access auth/authz, Link-Layer Credentials (LLCs) are securely distributed from PAA to PaC Using PANA payload encryption mech. (draft-yegin-pana-encr-avp) Example of LLCs: Group PSK credentials Short-term public key credentials LLCs are used for establishing link-layer transient session keys (TSKs) between neighboring nodes to protect link-layer frames using a link establishment KMP TSKs: Unicast TSKs and Multicast TSKs Yoshihiro Ohba, Toshiba

Call Flow (w/o Relay) PaC PAA doc.: IEEE 802.15-15-12-0109-00-0009 March 2012 Call Flow (w/o Relay) Joining Node Parent Node PaC PAA PANA over 802.15.9 (bootstrapping KMP) LLCs LLCs (encrypted in PANA payload) (2) Link Establishment KMP over 802.15.9 PaC : PANA Client PAA: PANA Authentication Agent Yoshihiro Ohba, Toshiba

Call Flow (w/ Relay) PaC PRE PAA Out of scope of 802.15.9 doc.: IEEE 802.15-15-12-0109-00-0009 March 2012 Call Flow (w/ Relay) Joining Node Parent Node PaC PRE PAA PANA over 802.15.9 (bootstrapping KMP) (1’) PANA Relay over UDP LLCs LLCs encrypted in PANA payload) Out of scope of 802.15.9 (2)Link Establishment KMP over 802.15.9 PaC : PANA Client PAA: PANA Authentication Agent PRE: PANA Relay Yoshihiro Ohba, Toshiba

Message Format for 802.15.4e doc.: IEEE 802.15-15-12-0109-00-0009 March 2012 Message Format for 802.15.4e ‘device control’ IE 802.15.4e MAC Frame Frame Control (1 octet) + PANA PDU fragment (variable) PANA PDU Yoshihiro Ohba, Toshiba

Message Mapping for PANA-Relay doc.: IEEE 802.15-15-12-0109-00-0009 March 2012 Message Mapping for PANA-Relay ‘device control’ IE 802.15.4e MAC Frame Downlink messaging Uplink messaging PANA-Relay (PRY) Message 64-bit Prefix 64-bit Interface Identifier 16-bit Port Number Frame Control (1 octet) + PANA PDU fragment (variable) IPv6 Address PaC-Information AVP Relayed-Message AVP Yoshihiro Ohba, Toshiba

PANA Session Management for 802.15.9 March 2012 PANA Session Management for 802.15.9 Single-hop case In both PaC and PAA, PANA session is associated with MAC addresses of PaC and PAA Multi-hop case In PaC, PANA session is associated with MAC addresses of PaC and PRE In PAA, PANA session is associated with IP addresses and port numbers of PaC, PAA and PRE (same as RFC 6345) Yoshihiro Ohba, Toshiba

Link Establishment KMP doc.: IEEE 802.15-15-12-0109-00-0009 March 2012 Link Establishment KMP If a child node already has valid LLCs, it can skip Bootstrapping KMP and do Link Establishment KMP only Link Establishment KMP depends on type of LLCs For PSK-based LLCs, use SAE, etc For pubkey-based LLCs, use HIP, etc Yoshihiro Ohba, Toshiba