Subject: RE: Question/Comments: ietf-mpls-te-mib, ietf-mpls-ldp-mib,andiet f-mpls-te-mib

From: "Wijnen, Bert (Bert)" <[email-masked]>
Date: Fri, 19 Sep 2003 23:24:22 +0200

Inline

> -----Original Message-----
> From: Michelle S. Cotton [mailto:[email-masked]]
> Sent: vrijdag 19 september 2003 22:09
> To: Wijnen, Bert (Bert); [email-masked]
> Cc: [email-masked]; [email-masked]
> Subject: RE: Question/Comments: ietf-mpls-te-mib,
> ietf-mpls-ldp-mib,andietf-mpls-te-mib
> 
> 
> Alex/Bert See my comments below.
> 
> Thanks,
> 
> Michelle
> 
> 
> -----Original Message-----
> From: [email-masked] [mailto:[email-masked]]On Behalf Of
> Wijnen, Bert (Bert)
> Sent: Thursday, September 18, 2003 2:47 PM
> To: 'Michelle S. Cotton'; [email-masked]
> Cc: [email-masked]; [email-masked]
> Subject: RE: Question/Comments: ietf-mpls-te-mib,
> ietf-mpls-ldp-mib,andietf-mpls-te-mib
> 
> 
> Inline
> 
> > -----Original Message-----
> > From: Michelle S. Cotton [mailto:[email-masked]]
> > Sent: donderdag 18 september 2003 17:18
> > To: [email-masked]
> > Cc: [email-masked]; [email-masked]
> > Subject: Question/Comments: ietf-mpls-te-mib,
> > ietf-mpls-ldp-mib,andietf-mpls-te-mib
> > 
> > 
> > Alex,
> > 
> > Please confirm I understand the IANA actions for the
> > following documents:
> > 
> > draft-ietf-mpls-ldp-mib-13.txt
> > 
> > There are 4 assignments to be made in the above
> > document where do these need to go?
> > 
> This is correct. And the document suggests good values for you
> to assign. They go under the mplsStdMIB branch, which you
> also need to assign, as per document 
>    draft-ietf-mpls-tc-mib-09.txt
> That one asks you to assign transmission 166 to mplsStdMIB
> 
> [MSC] Is it OK to skip all the other numbers in the transmission 
> number registry?  Next in line would be 135.
> 
I think that is OK. The 166 is requested, because that is the ifType
for MPLS (in ianaiftype.mib) and most of the time we do assign
such specific MIB modules undertransmission with the arc that
equals th ifType.

So the values between 135 and 165 (inclusive) stay available for now.

> 
> > draft-ietf-mpls-ftn-mib-08.txt
> > 
> > No IANA actions
> > 
> Mmm... should have caught that myself. They do:
> 
> 
>        "Initial version issued as part of RFC XXXX."
>     ::= { mplsStdMIB 8 }
> 
> And in fact they should have asked you to make and 
> register that assignment.
> 
> [MSC] Can the authors be notified they need an IANA Considerations
> section?
> 
They should have done something aka:

      ::= { mplsStdMIB xxx } -- IANA assigns xxx
      -- IANA pls assign value 8.

by cc:ing mpls list I am asking authors to do so.

> > draft-ietf-mpls-te-mib-12.txt
> > 
> > The IANA Considerations section says there are 4 assignments
> > for this document, but then only 1 is described in section 18.1 
> > and that is the end of the document. Was this cut-off in the
> > online version by mistake.  If so, where should these assignments
> > go?
> > 
> It looks like this doc got indeed cut off.
> They have )page 13/14):
>    DESCRIPTION
>         "Initial draft version issued as part of RFC XXXX."
>    ::= { mplsStdMIB 3 }
> 
> And they should have asked you to make and register the assignment.
> So again this goes under mplsStdMIB. Seems like they have made a
> few copy and paste errors.
> 
Same here

Bert
> > Thanks in advance.  Sorry for not sending this earlier.
> > 
> 
> Since these docs all depend on the 
>    draft-ietf-mpls-tc-mib-09.txt
> document, it is clear that you might not easily have seen this
> cause it was not included in the package. It did have IETF Last Call
> though. This doc has a section 7 that explains that IANA is requested
> to setup a new registry for assignments under mplsStdMIB.
> 
> Bert
> 
> > Michelle
> > IANA
> > 
> > 
>