November 2013 doc IEEE 802 11 131341 r

November 2013 doc. : IEEE 802. 11 -13/1341 r 0 Renaming TLV Date: 2013 -11 -07 Authors: Name Affiliations Address Phone email Hitoshi MORIOKA Allied Telesis R&D Center 2 -14 -38 Tenjin, Chuo-ku, Fukuoka 810 -0001 JAPAN +81 -92 -771 -7630 hmorioka@root-hq. com Submission Slide 1 Hitoshi Morioka, Allied Telesis R&D Center

November 2013 doc. : IEEE 802. 11 -13/1341 r 0 Abstract This document explains TLV renaming. Submission Slide 2 Hitoshi Morioka, Allied Telesis R&D Center

November 2013 doc. : IEEE 802. 11 -13/1341 r 0 Comment • Santosh Pandey pointed out that the name “TLV” was already defined in TGaf draft. – New clause 8. 2. 6 defines TLV. – This TLV definition cannot be used for our TLV. • So we should change the name “TLV” in 8. 4. 2. 186. – – – Submission FILS HLP Wrapped Data TLV FILS IP Address Request TLV FILS IP Address Assignment TLV FILS DNS Information TLV Key RSC TLV KDE Container TLV Slide 3 Hitoshi Morioka, Allied Telesis R&D Center

November 2013 doc. : IEEE 802. 11 -13/1341 r 0 Proposal • Our TLVs are used in FILS Secure Container element. • Candidate – FSCTLV (FILS Secure Container TLV) • little bit long… – FSCO (FILS Secure Container Object) • Is object good? – FSCSE (FILS Secure Container Sub. Element) • Is subelement confusing? – Any other? • How about rename “FILS Secure Container element” to “FILS Container element”? – Not secured by this element. Secured by AEAD scheme. – Abbriviation can be shorten as “FC”. • FCTLV, FCO, FCSE… Submission Slide 4 Hitoshi Morioka, Allied Telesis R&D Center

November 2013 doc. : IEEE 802. 11 -13/1341 r 0 Strawpoll • Which name do you prefer? • Result – – – – Submission FSCTLV: FSCO: FSCSE: FCTLV: FCO: FCSE: No need to change (TLV): Slide 5 Hitoshi Morioka, Allied Telesis R&D Center