Re: [netmod] 'uses' as a sub-statement to 'choice' statement?

2016-02-02 Thread Kent Watsen

>This has already been discussed, see
>
>https://mailarchive.ietf.org/arch/search/?email_list=netmod=1=uF7kbBPMxIBAMUm03D3AqxaJvK4


Okay, good answer.  Never mind.

Thanks,
Kent

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod


Re: [netmod] 'uses' as a sub-statement to 'choice' statement?

2016-02-02 Thread Andy Bierman
Hi,

I do not think this is a bug.
The uses-stmt has no node name, just a grouping name,
which may have a prefix.

In the example above 'ethernet' and 'optical' are forced to
be local names and be unique local names.


Andy


On Tue, Feb 2, 2016 at 9:39 AM, Kent Watsen  wrote:

>
> In a model where the choice shorthand notation is being used, it is
> necessary to use longhand notation if wanting a case statement to be
> defined by the ‘uses’ statement.   That is, 6020bis allows ‘uses’ as a
> sub-statement to the ‘case’ statement, but not to the ‘choice’ statement.
> As an example, this choice statement:
>
>  choice interface-type {
>case ethernet {
>  uses ethernet;
>}
>case optical {
>  uses optical;
>}
>  }
>
> Cannot use shorthand notation:
>
>  choice interface-type {
>uses ethernet;
>uses optical;
>  }
>
>
> This seems like a bug to me.   Is it too late to fix in 6020bis as an
> issue raised by WGLC?
>
> Kent  // as a contributor
>
>
>
> ___
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
>
>
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod


[netmod] 'uses' as a sub-statement to 'choice' statement?

2016-02-02 Thread Kent Watsen

In a model where the choice shorthand notation is being used, it is necessary 
to use longhand notation if wanting a case statement to be defined by the 
‘uses’ statement.   That is, 6020bis allows ‘uses’ as a sub-statement to the 
‘case’ statement, but not to the ‘choice’ statement.  As an example, this 
choice statement:

 choice interface-type {
   case ethernet {
 uses ethernet;
   }
   case optical {
 uses optical;
   }
 }

Cannot use shorthand notation:

 choice interface-type {
   uses ethernet;
   uses optical;
 }


This seems like a bug to me.   Is it too late to fix in 6020bis as an issue 
raised by WGLC?

Kent  // as a contributor


___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod