Re: [core] SID files and IANA

[Michael Richardson <[e-mail]>]

As discussed in person, if SID files should be included in documents
in the way that YANG files are (wrapped in CODE BEGINS= pseudo wrapper),
then we need to say that in the document, and we probably need to
say tha the file extension should be .sid, and the filename probably
should match the yang module filename.

ivaylo petrov <[e-mail]> wrote:
    > About your point 2), there is no way to change existing SIDs that has
    > already been published. Now for the file, as it points to a yang
    > module, if there is a new version of the yang file, which is already
    > guarded, I don't see any problem for anyone to request updating of the
    > SID file. This will not change any existing SIDs, just possibly add new
    > ones. For that reason I am not sure locking is needed. Please let me
    > know if you know of a specific case where that might be.

While existing SID values are not changed, new ones may be allocated, and
it is up to the pyang --sid-* to do this against the .sid file, and so the
file needs to be available.

What is more than one entity does this to a particular module?
The locking can occur at the WG level for IETF streams, but there is a goal
to support processes in industry that are using SID not directly in IETF
protocols.

    > Then about your point 4), IANA is not going to do the generation. This is
    > something the authors will have to do I am afraid. The experts will
    > have to 
    > verify that this generation is acceptable.

Fair enough.

    > Given that draft-ietf-anima-constrained-voucher is past WGLC, I

draft-ietf-anima-bootstrapping-keyinfra is past WGLC, and at the IESG.
(That's non-constrained BRSKI)

draft-ietf-anima-constrained-voucher is not yet in WGLC, sadly.

    > don't see any problem to add it to the initial SID range allocations (sec
    > 6.3.3) with a new range (as IANA is not responsible for the mega range
    > that you have mentioned). That being said, I want to be sure that the
    > SID draft will not be delayed in case that draft is delayed for any
    > reason, so maybe we will need to discuss.

I would like to ask for a new range in the IANA range, in this document then.
I need two 50 unit ranges, or a single larger block if you like.

-- 
]               Never tell me the odds!                 | ipv6 mesh networks [ 
]   Michael Richardson, Sandelman Software Works        | network architect  [ 
]     [e-mail]  http://www.sandelman.ca/        |   ruby on rails    [