draftietf6 tisch 6 topinterface02 Qin Wang Ed Xavier
![Remarks [1/2] • We need reviewers to verify this interface is complete – “can](https://slidetodoc.com/presentation_image/1ee4b9ab8b873e29e55451cd9467bda0/image-6.jpg "Remarks [1/2] • We need reviewers to verify this interface is complete – “can")
![Remarks [2/2] • No security-related elements for the moment – Waiting for security DT](https://slidetodoc.com/presentation_image/1ee4b9ab8b873e29e55451cd9467bda0/image-7.jpg "Remarks [2/2] • No security-related elements for the moment – Waiting for security DT")
![Questions [1/3] • Should we expose PIB attributes through YANG interface? – 52 MAC](https://slidetodoc.com/presentation_image/1ee4b9ab8b873e29e55451cd9467bda0/image-8.jpg "Questions [1/3] • Should we expose PIB attributes through YANG interface? – 52 MAC")
![Questions [2/3] • Currently, YANG mode describes all components of 6 top: – –](https://slidetodoc.com/presentation_image/1ee4b9ab8b873e29e55451cd9467bda0/image-9.jpg "Questions [2/3] • Currently, YANG mode describes all components of 6 top: – –")
![Questions [3/3] • Protocol to interact with YANG data model? • Options – Remotely](https://slidetodoc.com/presentation_image/1ee4b9ab8b873e29e55451cd9467bda0/image-10.jpg "Questions [3/3] • Protocol to interact with YANG data model? • Options – Remotely")
- Slides: 10
draft-ietf-6 tisch 6 top-interface-02 Qin Wang (Ed. ) Xavier Vilajosana Thomas Watteyne 6 Ti. SCH@IETF 91 1
Apps 6 top Co. AP Scope UDP RPL 6 Lo. WPAN 6 top sublayer draft-ietf-6 tisch-6 top-interface draft-wang-6 tisch-6 top-sublayer IEEE 802. 15. 4 e TSCH IEEE 802. 15. 4 (PHY) Platforms Application 6 Ti. SCH@IETF 91 Contents: • some “tweaks” to IEEE 802. 15. 4 e-2012: • hard/soft cells • queuing • conceptual interface (function upper layer can call) • generic YANG data model draft-ietf-6 tisch-6 top-interface-02 2
Status • Status: – Adopted at IETF 89 London – Latest version (draft-ietf-6 tisch-6 top-interface-02) published on October 27, 2014 https: //datatracker. ietf. org/doc/draft-ietf-6 tisch-6 topinterface/ • Changes since IETF 90 – Minor fixes with respect to 15. 4 e variable types – Added monitoring to MAC counters – YANG model validation (YANG doctor) 6 Ti. SCH@IETF 91 draft-ietf-6 tisch-6 top-interface-02 3
Changes since IETF 90 • YANG model validation (YANG doctor) see next slide • Minor fixes with respect to 15. 4 e variable types – e. g. channel. Offset is “type uint 16”, not “type uint 8” • Added monitoring to MAC counters – – – – – mac. Counter. Octets mac. Retry. Count mac. Multiple. Retry. Count mac. TXFail. Count mac. TXSuccess. Count mac. FCSError. Count mac. Security. Failure mac. Duplicate. Frame. Count mac. RXSuccess. Count mac. NACKcount 6 Ti. SCH@IETF 91 draft-ietf-6 tisch-6 top-interface-02 4
YANG Model Validation 1. use min-elements constraint 2. use type leafref { path “ ” } 3. use mandatory true 4. use range “ 1. . max” 5. use default 6. use must 7. use unique 8. define type nodeaddresstype next revision “very soon” 6 Ti. SCH@IETF 91 draft-ietf-6 tisch-6 top-interface-02 5
Remarks [1/2] • We need reviewers to verify this interface is complete – “can I manage a IEEE 802. 15. 4 e TSCH network with this interface? ” 6 Ti. SCH@IETF 91 draft-ietf-6 tisch-6 top-interface-02 6
Remarks [2/2] • No security-related elements for the moment – Waiting for security DT to add a list of elements – Probably not blindly exposing the IEEE 802. 15. 4 -2011 security related • FYI, 11 Security-related MAC PIB attributes defined in Table 60: – mac. Key. Table, mac. Device. Table, mac. Security. Level. Table, mac. Frame. Counter, mac. Auto. Request. Security. Level, mac. Auto. Request. Key. Id. Mode, mac. Auto. Request. Key. Source, mac. Auto. Request. Key. Index, mac. Default. Key. Source, mac. PANCoord. Extended. Address, mac. PANCoord. Short. Address 6 Ti. SCH@IETF 91 draft-ietf-6 tisch-6 top-interface-02 7
Questions [1/3] • Should we expose PIB attributes through YANG interface? – 52 MAC PIB attributes defined in 6. 4. 2 of IEEE 802. 15. 4 -2011 – a. Base. Slot. Duration, a. Base. Superframe. Duration, a. GTSDesc. Persistence. Time, a. Max. Beacon. Overhead, a. Max. Beacon. Payload. Length, a. Max. Lost. Beacons, a. Max. MACSafe. Payload. Size, a. Max. MACPayload. Size, a. Max. MPDUUnsecured. Overhead, a. Max. SIFSFrame. Size, a. Min. CAPLength, a. Min. MPDUOverhead, a. Num. Superframe. Slots, a. Unit. Backoff. Period, mac. Extended. Address, mac. Ack. Wait. Duration, mac. Associated. PANCoord, mac. Auto. Request, mac. Batt. Life. Ext. Periods, mac. Beacon. Payload. Length, mac. Beacon. Order, mac. Beacon. Tx. Time, mac. BSN, mac. Coord. Extended. Address, mac. Coord. Short. Address, mac. DSN, mac. GTSPermit, mac. Max. BE, mac. Max. CSMABackoffs, mac. Max. Frame. Total. Wait. Time, mac. Max. Frame. Retries, mac. Min. BE, mac. LIFSPeriod, mac. SIFSPeriod, mac. PANId, mac. Promiscuous. Mode, mac. Ranging. Supported, mac. Response. Wait. Time, mac. Rx. On. When. Idle, mac. Security. Enabled, mac. Short. Address, mac. Superframe. Order, mac. Sync. Symbol. Offset, mac. Timestamp. Supported, mac. Transaction. Persistence. Time, mac. Tx. Control. Active. Duration, mac. Tx. Control. Pause. Duration, mac. Tx. Total. Duration, – Options: none, all, selection 6 Ti. SCH@IETF 91 draft-ietf-6 tisch-6 top-interface-02 8
Questions [2/3] • Currently, YANG mode describes all components of 6 top: – – Soft cells Chunks Tracks Label switching unlikely that all nodes will require all options all the time • Allow for nodes to implement only a subset of the features? – Use YANG feature – Add discovery mechanism 6 Ti. SCH@IETF 91 draft-ietf-6 tisch-6 top-interface-02 9
Questions [3/3] • Protocol to interact with YANG data model? • Options – Remotely ( “centralized management” PCE) • draft-ietf-6 tisch-coap • draft-vanderstok-core-comi – neighbor-to-neighbor (“distributed management”) • draft-wang-6 tisch-6 top-coapie • outcome discussion on Wednesday 11/12 6 Ti. SCH@IETF 91 draft-ietf-6 tisch-6 top-interface-02 10
