1. YANG Key-Chain Model IETF 97, Seoul
Acee Lindem, Cisco
Ying-Zhen Qu, Cisco
Derek Yeung, Arrcus
Ing-Wher Chen, Kuatrotech
Jeffrey Zhang, Juniper
Yi Yang, Individual

2. Recent Developments Working Group Last Call in RTG WG
Changed structure based on prevailing Ops-state models
Need RTGWG Review and Second WG Last Call

3. Model Structural Change
Split into separate Config and State trees consistent with ietf-routing and unicast routing yang models
Model did not support retrieval of applied configuration without additional data stores.

4. New Tree Diagram (1/2) +--rw key-chain o
| +--rw key-chain-list* [name]
| | +--rw name string
| | +--rw description? string
| | +--rw accept-tolerance {accept-tolerance}?
| | | +--rw duration? uint32
| | +--rw key-chain-entries* [key-id]
| | rw key-id uint64 o

5. New Tree Diagram (2/2) +--ro key-chain-state
+--ro key-chain-list* [name]
| +--ro name string
| +--ro description? string
| +--ro accept-tolerance {accept-tolerance}?
| | +--ro duration? Uint32
| +--ro last-modified-timestamp? yang:date-and-time
| +--ro key-chain-entries* [key-id]
| ro key-id uint64
| ro lifetime o

6. Changes other than Config and State trees
For each key-chain – Last modified date and time
For each key-chain entry
accept-lifetime-valid - boolean indicates whether key is currently accepted
send-lifetime-valid - boolean indicates whether key can currently be sent
Key strings are not returned in operational state – similar to MIB.

7. Next Steps Social Changes with WG Group at IETF 97 WG Discussion
Second WG last call