Re: [Tools-discuss] Tool request: datatracker link(s) to RFC-extracted YANG module(s)

[Benoit Claise <[e-mail]>]

Thanks Dale,

The more I think about this issue, the more I believe that we should 
implement the only viable solution: dissociate the YANG module, MIB 
module, code, etc. from the draft text.

Regards, Benoit
> Benoit Claise <[e-mail]> writes:
>> If you are familiar with github, all YANG modules are at
>> https://github.com/YangModels/yang/tree/master/standard/ietf/RFC
>>       See the latest pull request so that it's up to date:
>> https://github.com/YangModels/yang/pull/121
>>
>> In the end, we should observe that a YANG module (or a MIB module, or
>> code ...) embedded in a RFC is not easily accessible to the wider audience.
>> Sure there is CODE BEGINS/CODE ENDS as delimiters. Even those is a pain:
>> I spent one hour this morning sending email to authors, explaining how
>> to use them correctly.
> Perhaps better would be an IANA registry mapping
>
>      RFC-number
>      module-name
>      module-description
>      pointer-to-clean-copy
>
> each RFC could mention it in "IANA Considerations", and if the clean
> copies have to be moved, the registry could be bulk-updated by AD
> request or something simple.
>
> Dale
>
> .
>