50 likes | 167 Vues
This document discusses the need to rename "TLV" (Type-Length-Value) in the context of FILS (Fast Initial Link Setup) due to a pre-existing definition in the TGaf draft. Key proposals include the adoption of new terminology such as FSCTLV (FILS Secure Container TLV) and the potential renaming of related elements for clarity. Feedback from a straw poll on preferred names will help determine the final decision. The goal is to ensure that the terminology aligns with established standards and avoids confusion.
E N D
Renaming TLV Authors: Date: 2013-11-07 Hitoshi Morioka, Allied Telesis R&D Center
Abstract This document explains TLV renaming. Hitoshi Morioka, Allied Telesis R&D Center
Comment • SantoshPandey 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. • 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 Hitoshi Morioka, Allied Telesis R&D Center
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 SubElement) • 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… Hitoshi Morioka, Allied Telesis R&D Center
Strawpoll • Which name do you prefer? • Result • FSCTLV: • FSCO: • FSCSE: • FCTLV: • FCO: • FCSE: • No need to change (TLV): Hitoshi Morioka, Allied Telesis R&D Center