idnits 2.17.1 draft-wbl-rtgwg-baseline-switch-model-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 142 has weird spacing: '...-length uin...' == Line 178 has weird spacing: '...-length uin...' == Line 231 has weird spacing: '...address ine...' == Line 247 has weird spacing: '...rw name str...' == Line 251 has weird spacing: '...address ine...' == (1 more instance...) -- The document date (March 9, 2017) is 2604 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Looks like a reference, but probably isn't: '1' on line 357 -- Looks like a reference, but probably isn't: '2' on line 359 -- Looks like a reference, but probably isn't: '3' on line 361 == Unused Reference: 'RFC2119' is defined on line 352, but no explicit reference was found in the text Summary: 2 errors (**), 0 flaws (~~), 8 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. White 3 Internet-Draft D. Black 4 Intended status: Informational Dell EMC 5 Expires: September 9, 2017 J. Leung 6 Intel Corporation 7 March 9, 2017 9 YANG Data Center Baseline Switch Profile 10 draft-wbl-rtgwg-baseline-switch-model-01 12 Abstract 14 [ Insert abstract here ] 16 Status of This Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at http://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 This Internet-Draft will expire on September 9, 2017. 33 Copyright Notice 35 Copyright (c) 2017 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents 40 (http://trustee.ietf.org/license-info) in effect on the date of 41 publication of this document. Please review these documents 42 carefully, as they describe your rights and restrictions with respect 43 to this document. Code Components extracted from this document must 44 include Simplified BSD License text as described in Section 4.e of 45 the Trust Legal Provisions and are provided without warranty as 46 described in the Simplified BSD License. 48 1. Introduction 50 *Disclaimer* - this is a -00 draft. 52 This is a normative profile for Baseline Switch Profile (send into 53 IETF RTG) intended to be published as RFC on completion of DMTF spec 54 to wrap Baseline Switch Profile. 56 2. What is a Redfish Baseline Switch? 58 The baseline switch profile contains basic system, interface, L2, and 59 L3 configuration elements sufficient to set up the device for use in 60 a controller based converged infrastructure environment. 62 The following list of IETF drafts, RFCs, and Redfish models will 63 constitute the management interface to the baseline switch. 65 3. Core YANG RFCs 67 RFC6020 [1] provides the YANG modeling language definition. 69 RFC6991 [2] provides the Common YANG Data Types used by many other 70 IETF YANG modules. 72 Interface management requires at set of RFCs to provide all relevant 73 capabilities: 75 https://tools.ietf.org/html/rfc7223 76 https://tools.ietf.org/html/rfc7277 77 https://tools.ietf.org/html/rfc7224 78 https://tools.ietf.org/html/rfc7317 80 3.1. RFC7223 provides: 82 +--rw interfaces 83 | +--rw interface* [name] 84 | +--rw name string 85 | +--rw description? string 86 | +--rw type identityref 87 | +--rw enabled? boolean 88 | +--rw link-up-down-trap-enable? enumeration 89 +--ro interfaces-state 90 +--ro interface* [name] 91 +--ro name string 92 +--ro type identityref 93 +--ro admin-status enumeration 94 +--ro oper-status enumeration 95 +--ro last-change? YANG:date-and-time 96 +--ro if-index int32 97 +--ro phys-address? YANG:phys-address 98 +--ro higher-layer-if* interface-state-ref 99 +--ro lower-layer-if* interface-state-ref 100 +--ro speed? YANG:gauge64 101 +--ro statistics 102 +--ro discontinuity-time YANG:date-and-time 103 +--ro in-octets? YANG:counter64 104 +--ro in-unicast-pkts? YANG:counter64 105 +--ro in-broadcast-pkts? YANG:counter64 106 +--ro in-multicast-pkts? YANG:counter64 107 +--ro in-discards? YANG:counter32 108 +--ro in-errors? YANG:counter32 109 +--ro in-unknown-protos? YANG:counter32 110 +--ro out-octets? YANG:counter64 111 +--ro out-unicast-pkts? YANG:counter64 112 +--ro out-broadcast-pkts? YANG:counter64 113 +--ro out-multicast-pkts? YANG:counter64 114 +--ro out-discards? YANG:counter32 115 +--ro out-errors? YANG:counter32 117 3.2. RFC7277 adds: 119 +--rw if:interfaces 120 +--rw if:interface* [name] 121 ... 122 +--rw ipv4! 123 | +--rw enabled? boolean 124 | +--rw forwarding? boolean 125 | +--rw mtu? uint16 126 | +--rw address* [ip] 127 | | +--rw ip inet:ipv4-address-no-zone 128 | | +--rw (subnet) 129 | | +--:(prefix-length) 130 | | | +--rw ip:prefix-length? uint8 131 | | +--:(netmask) 132 | | +--rw ip:netmask? YANG:dotted-quad 133 | +--rw neighbor* [ip] 134 | +--rw ip inet:ipv4-address-no-zone 135 | +--rw link-layer-address YANG:phys-address 136 +--rw ipv6! 137 +--rw enabled? boolean 138 +--rw forwarding? boolean 139 +--rw mtu? uint32 140 +--rw address* [ip] 141 | +--rw ip inet:ipv6-address-no-zone 142 | +--rw prefix-length uint8 143 +--rw neighbor* [ip] 144 | +--rw ip inet:ipv6-address-no-zone 145 | +--rw link-layer-address YANG:phys-address 146 +--rw dup-addr-detect-transmits? uint32 147 +--rw autoconf 148 +--rw create-global-addresses? boolean 149 +--rw create-temporary-addresses? boolean 150 +--rw temporary-valid-lifetime? uint32 151 +--rw temporary-preferred-lifetime? uint32 153 AND 155 +--ro if:interfaces-state 156 +--ro if:interface* [name] 157 ... 158 +--ro ipv4! 159 | +--ro forwarding? boolean 160 | +--ro mtu? uint16 161 | +--ro address* [ip] 162 | | +--ro ip inet:ipv4-address-no-zone 163 | | +--ro (subnet)? 164 | | | +--:(prefix-length) 165 | | | | +--ro prefix-length? uint8 166 | | | +--:(netmask) 167 | | | +--ro netmask? YANG:dotted-quad 168 | | +--ro origin? ip-address-origin 169 | +--ro neighbor* [ip] 170 | +--ro ip inet:ipv4-address-no-zone 171 | +--ro link-layer-address? YANG:phys-address 172 | +--ro origin? neighbor-origin 173 +--ro ipv6! 174 +--ro forwarding? boolean 175 +--ro mtu? uint32 176 +--ro address* [ip] 177 | +--ro ip inet:ipv6-address-no-zone 178 | +--ro prefix-length uint8 179 | +--ro origin? ip-address-origin 180 | +--ro status? enumeration 181 +--ro neighbor* [ip] 182 +--ro ip inet:ipv6-address-no-zone 183 +--ro link-layer-address? YANG:phys-address 184 +--ro origin? neighbor-origin 185 +--ro is-router? empty 186 +--ro state? enumeration 188 3.3. RFC7224 provides: 190 The set of YANG identity statement for the IANA defined interface 191 types. 193 3.4. RFC7317 provides: 195 o System Identification 197 o System Time Date 199 o NTP 201 o DNS Client 203 System Identification 205 +--rw system 206 | +--rw contact? string 207 | +--rw hostname? inet:domain-name 208 | +--rw location? string 209 +--ro system-state 210 +--ro platform 211 +--ro os-name? string 212 +--ro os-release? string 213 +--ro os-version? string 214 +--ro machine? string 216 System Time 217 +--rw system 218 | +--rw clock 219 | | +--rw (timezone)? 220 | | +--:(timezone-name) 221 | | | +--rw timezone-name? timezone-name 222 | | +--:(timezone-utc-offset) 223 | | +--rw timezone-utc-offset? int16 224 | +--rw ntp! 225 | +--rw enabled? boolean 226 | +--rw server* [name] 227 | +--rw name string 228 | +--rw (transport) 229 | | +--:(udp) 230 | | +--rw udp 231 | | +--rw address inet:host 232 | | +--rw port? inet:port-number 233 | +--rw association-type? enumeration 234 | +--rw iburst? boolean 235 | +--rw prefer? boolean 236 +--ro system-state 237 +--ro clock 238 +--ro current-datetime? YANG:date-and-time 239 +--ro boot-datetime? YANG:date-and-time 241 DNS Client 243 +--rw system 244 +--rw dns-resolver 245 +--rw search* inet:domain-name 246 +--rw server* [name] 247 | +--rw name string 248 | +--rw (transport) 249 | +--:(udp-and-tcp) 250 | +--udp-and-tcp 251 | +--rw address inet:ip-address 252 | +--rw port? inet:port-number 253 +--rw options 254 +--rw timeout? uint8 255 +--rw attempts? uint8 257 User Authentication 258 +--rw system 259 +--rw authentication 260 +--rw user-authentication-order* identityref 261 +--rw user* [name] 262 +--rw name string 263 +--rw password? ianach:crypt-hash 264 +--rw authorized-key* [name] 265 +--rw name string 266 +--rw algorithm string 267 +--rw key-data binary 269 4. Additional YANG models 271 In addition to the above RFCs, the baseline switch models needs to 272 cover: 274 o VLANs 276 o ACLs 278 o Syslog 280 The following lists of IETF drafts sets our recommendation to cover 281 the above three areas. 283 4.1. VLAN and interface extensions: 285 To handle VLANs and with related interface configuration the 286 following YANG models are under evaluation. 288 o https://tools.ietf.org/html/draft-ietf-netmod-intf-ext-yang-03 290 o https://tools.ietf.org/html/draft-wilton-intf-vlan-yang-00.txt ## 291 ACL To handle ACL configuration the following YANG model is under 292 consideration. 294 o https://tools.ietf.org/html/draft-ietf-netmod-acl-model-09 296 4.2. Syslog 298 To handle configuration and access to syslog the following YANG model 299 is under consideration. 301 o https://tools.ietf.org/html/draft-ietf-netmod-syslog-model-11 303 5. Applicable Redfish system management models 305 The following standard Redfish systems management models apply to the 306 baseline network switch profile. Reference: Redfish schema index 307 [3]. The use of these Redfish management models allows a converged 308 infrastructure manager to have a consistent view of server, storage 309 and network systems. 311 o Chassis 313 o ComputerSystem 315 o Manager 317 o ManagerAccount 319 o Power 321 o Thermal 323 o SoftwareInventory plus UpdateService 325 o Event configuration using Event, EventDestination, and Event 326 Service 328 o Access to logs using LogEntry, and LogService 330 o Management interface configuration using EthernetInterface and 331 related 333 o Console configuration using SerialInterface 335 o PrivilegeRegistery and Privileges 337 Where YANG and Redfish overlap, the commonality of YANG vs Redfish is 338 TBD. 340 6. Overall Baseline Switch Profile Structure 342 ./redfish/v1/Systems 343 ./redfish/v1/Chassis 344 ./redfish/v1/NetworkDevices/BaselineSwitch/... 345 ... other redfish resource blocks... 346 (resource from RFCs and Redfish bullet list, above) 348 7. References 350 7.1. Normative References 352 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 353 Requirement Levels", BCP 14, RFC 2119, March 1997. 355 7.2. URIs 357 [1] https://tools.ietf.org/html/rfc6020 359 [2] https://tools.ietf.org/html/rfc6991 361 [3] http://redfish.dmtf.org/redfish/schema_index 363 Authors' Addresses 365 Joseph White 366 Dell EMC 368 Email: joseph.l.white@dell.com 370 David Black 371 Dell EMC 373 Email: david.black@dell.com 375 John Leung 376 Intel Corporation 378 Email: john.leung@intel.com