1 / 7

IANA Registry for ESC Bytes in 6loWPAN

This draft defines the usage and assignment of ESC bytes in 6loWPAN to accommodate new requirements and deployments. It addresses concerns over ITU-T usage of IETF code-space and proposes a new approach for ESC bytes.

ljune
Download Presentation

IANA Registry for ESC Bytes in 6loWPAN

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. draft-chairs-6lo-dispatch-iana-registry-00 Authors: Samita Chakrabarti, Gabriel Montenegro, Ralph Droms, James Woodyatt IETF 93, July 20, 2015

  2. Background • RFC 4944 and RFC 6282 do not define ESC Dispatch extension bytes and their usage clearly • Roll RPL likes to re-use some of the dispatch header space • draft-thubert-6lo-routing-dispatch-05 • Possibly reclaim some of the dispatch bytes from mesh header • ITU-T G3-PLC reported their use of ESC bytes dispatch header space along with Mesh Header • Deployment of their use of ESC bytes • ESC byte Dispatch values 1-31 for command frames [ No IANA assignments ] • Thierry Lys – April, 2015

  3. Purpose of this document • Define ESC bytes for 6loWPAN • We have more experience now on possible deployments • 6LoWPAN has progressed and adopted at many SDOs and forums • Communicate to other SDO about ESC bytes usage and IANA assignment policies • Consider other IETF requirements for Dispatch header use • Record IANA assignments for ESC dispatch values

  4. Usage of ESC bytes • EXT Type => New dispatch extension types • ESC dispatch type values are orthogonal to other dispatch values • Extended payloads must be predefined 0 1 2 3 …… 01 000000 EXT Type Extended Dispatch Payload

  5. WG Comments • Several comments from WG members • Johnathan Hui, Robert Cragie, Thierry Lys, Carsten Bormann, Pascal Thubert, Patricia Brett, Paul Daffy • Concern over ITUT-T usage of IETF code-space without IANA notification • How to resolve issues with legacy 6lowpan nodes? • How to define node behavior when unknown EXT-type is received? • Can’t skip unknown dispatch types • How many sequence of ESC and dispatch bytes to allow? • Feeling of not being able to design the ESC bytes according to IETF requirements [ Ex: 6loRH and other future enhancements]

  6. New proposal [ To be updated] • Use the existing ESC byte [01 000000] as defined in draft-chairs-6lo-dispatch-iana-00 draft • Accommodate with ITU-T needs • Assign new ESC bytes [ from unused code spaces] • WG will define new ESC bytes with Compressed TLV bytes[ ex:1 byte for T+L] • New ESC bytes type values may provide • Link specific behavior capabilities • Other IETF WG Requirements [ ex: RPL compression]

  7. Next Step • Update the draft with new proposal • Send LS to ITU-T and other SDO • Target WG approval of this draft by IETF94

More Related