On Wed, Nov 06, 2019 at 06:15:25PM +, Vladimir Vassilev wrote:
>
> There is no technical reason at all to have MAC addresses represented as
> pattern constrained strings and not "binary" of length 6 (as it was in
> SMIv2 MIBs) either. There is no technical reason for ethertype to be
>
On 06/11/2019 15.10, Schönwälder, Jürgen wrote:
> On Wed, Nov 06, 2019 at 01:29:41PM +, Vladimir Vassilev wrote:
>> [2] Some of the types are based on strings with complex lexical
>> representation with canonical form specified in description statement
>> which is neither scalable nor
The licensing information for IEEE YANG models can be found here...
https://github.com/YangModels/yang (YANG Catalog's github repository)
If you scroll down there is the text of the README.md file, there you will
find...
In the Models Directory Structure section:
yang/standard/ieee: standard
On Wed, Nov 06, 2019 at 01:29:41PM +, Vladimir Vassilev wrote:
>
> [2] Some of the types are based on strings with complex lexical
> representation with canonical form specified in description statement
> which is neither scalable nor automation friendly. For example the
> "ethertype-type"
Moving a netmod relevant topic from a thread on the bmwg mailing list
https://mailarchive.ietf.org/arch/msg/bmwg/GwkVykKmOX7DFokCFynJVy_ZwZ8
On 29/10/2019 13.32, tom petch wrote:
> Picking up the point below about vlan, this is where the IETF is not
> doing the job it might. 'vlan' appears in
