Re: [core] Zaheduzzaman Sarker's Discuss on draft-ietf-core-sid-16: (with DISCUSS and COMMENT)

[Zaheduzzaman Sarker <[e-mail]>]

On 2021-07-15, 23:52, "Michael Richardson" <[e-mail]> wrote:

    Zaheduzzaman Sarker via Datatracker <[e-mail]> wrote:
        > *Section 3 : says -

        > "The creation of this new version of the ".sid" file
        > SHOULD be performed using an automated tool"

        > If this is supposed to be the automation process written in appendix B then
        > putting a reference here makes sense. If not, then as this is very important
        > tool, more information need to be added here in this specification (like,
        > where to find it, who create and maintains it, any reference to such an
        > existing tools). Also I am missing what consequences one need to consider if
        > the process is not automated. If this is same as written in the
        > introduction -

    it's in pyang 2.1 since late 2019.
    I don't know what the current practice towards referencing pyang.

I think a short description of the tool  (may be should go in as an appendix in the doc ) and a url reference to pyang2.1 will do the job here.

        > "Assignment of SIDs to YANG items can be automated.  For more details
        > how this can be achieved, please consult Appendix B."

        > Then we have two kind of instructions for the same thing - "can be" and a
        > normative "SHOULD". Hence it need to be clarified which one should prevail.

    Good point.

        >> maximum SID range size is 1000.  A larger size may be requested by
        >> the authors if this recommendation is considered insufficient.  It is
        >> important to note that an additional SID range can be allocated to an
        >> existing YANG module if the initial range is exhausted."

        > I have hard time understanding the mentioning of the maximum SID range here.
        > does this mean this document sets the maximum range to 1000 but others can
        > have more? please clarify.

    Each of my ANIMA modules uses around 15 SID values from a range of 50.
    (that's draft-ietf-anima-constrained-voucher, which is among the first users)

    I think that if you write a module that requires more than 1000 SID values
    that you might be doing something wrong, and so more consultation is
    warranted.

Well I don't get the warranted in the document as clear as you wrote here.  Would be good to make it clear in the document.

BR

Zahed