1 / 8

SMIv2 Translation to YANG

SMIv2 Translation to YANG. draft-schoenw-netmod-smi-yang-02. Jürgen Schönwälder Jacobs University. Changes since draft-schoenw-netmod-smi-yang-01. Inlined examples again (avoids page flipping) Preserving the SMIv2 nesting instead of flattening things (see discussion in Beijing)

irene-manning
Télécharger la présentation

SMIv2 Translation to YANG

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. SMIv2 Translation to YANG draft-schoenw-netmod-smi-yang-02 Jürgen Schönwälder Jacobs University IETF 80 - NETMOD WG MEETING

  2. Changes since draft-schoenw-netmod-smi-yang-01 • Inlined examples again (avoids page flipping) • Preserving the SMIv2 nesting instead of flattening things (see discussion in Beijing) • Wrote some security considerations text • Clarifications and editorial improvements IETF 80 - NETMOD WG MEETING

  3. Issue #1: DISPLAY-HINTs • […] the DISPLAY-HINT value MAY be used to generate a regular expression for the YANG pattern statement within the type statement. • Options: • Declare this text to be sufficient • Elaborate how certain simple DISPLAY-HINTs can be translated, leaving the translation of more complex ones an implementation choice • Define a complete translation algorithm (hard, output usually not readable) • Declare that DISPLAY-HINTs are not translated at all IETF 80 - NETMOD WG MEETING

  4. Issue #2: Name Ambiguities • Options: • First definition encountered in a translation unit wins and declare certain valid SMIv2 updates to be avoided • Drop the idea to generate a hierarchy of nested containers (again) and instead merge all scalars into one container (name from MODULE-IDENTITY) followed by the tables • ? foo OBJECT IDENTIFIER ::= { baz 1 } bar OBJECT IDENTIFIER ::= { baz 1 } IETF 80 - NETMOD WG MEETING

  5. Issue #3: Enum/Bits Ambiguities • SMIv2 allows the descriptors of enumerated integers and named bits to change during revisions • YANG does not allow enums to be changed • Options: • declare certain valid SMIv2 updates to be avoided • ?? IETF 80 - NETMOD WG MEETING

  6. Issue #4: OBJECT-IDENTITY • Options: • Translate OBJECT-IDENTITIES into YANG containers? • Translate OBJECT-IDENTITIES into YANG identities? • Do both or do nothing? container usmNoAuthProtocol { description "No Authentication Protocol."; } identity usmNoAuthProtocol { base "smiv2:object-identity”; description “No Authentication Protocol."; } IETF 80 - NETMOD WG MEETING

  7. Issue #5: string vs binary • Presence of a DISPLAY-HINT is used to decide whether an OCTET STRING translates to a string or binary type • SMIv2 allows to add DISPLAY-HINTs during revisions, hence this is not safe • Options: • Use a union type to always allow textual strings and binary values; requires to “quote” string values in some way to avoid ambiguities • Always use the binary type (encoded in base64) • declare certain valid SMIv2 updates to be avoided • ?? IETF 80 - NETMOD WG MEETING

  8. Issue #6: smiv2 yang extensions • YANG extension statements (smiv2:oid, smiv2:display-hint, smiv2:max-access, smiv2:defval) are defined to keep SMIv2 information not directly translatable in a machine readable format • Options: • Implementations MUST generate these statements • Implementations SHOULD generate these statements IETF 80 - NETMOD WG MEETING

More Related