RE: Last Call: 'Early IANA Allocation of Standards Track Codepoints' to BCP (fwd)

["Romascanu, Dan (Dan)" <dromasca@avaya.com>]

I believe that this proposal is useful, but we need to be careful in picking the right timing for an early allocation of the OIDs for MIB modules. The key issue is the backwards compatibility. As long as there are fair chances for the MIB module to go through changes that would impact backwards compatibility, the WG chair or the shepherding AD should not publish values for pre-allocated OIDs. I would say that this moment is not sooner than the IESG approval of the document that includes the MIB module. This would still shorten the process and make the OID values available a few months before publication and lower the chances of later interoperability problems.

Obviously. I would like a consistent policy to be implemented by all WGs in the IETF that do MIB modules. 

Regards,

Dan



> -----Original Message-----
> From: owner-mreview@ops.ietf.org 
> [mailto:owner-mreview@ops.ietf.org]On Behalf Of C. M. Heard
> Sent: 06 August, 2004 6:40 PM
> To: Mreview (E-mail)
> Subject: Last Call: 'Early IANA Allocation of Standards Track 
> Codepoints' to BCP (fwd)
> 
> 
> Greetings,
> 
> I would like to suggest that all MIB Doctors have a look at
> 
> http://www.ietf.org/internet-drafts/draft-kompella-zinin-early
> -allocation-02.txt
> 
> which (as noted in the attached e-mail message) is now in last call.
> 
> I guess the questions that I have are whether or not it would be a
> good idea to adopt an Early Allocation policy for top-level OIDs of
> new MIB modules, and if such a policy was adopted, at what point
> such an allocation would make sense to allow such an allocation.
> 
> Thanks,
> 
> Mike Heard
> 
>