Re: [CCAMP] AD review of draft-ietf-ccamp-swcaps-update

[t.petch <[e-mail]>]

----- Original Message -----
From: "Lou Berger" <[e-mail]>
To: <[e-mail]>
Cc: "'t.petch'" <[e-mail]>;
<[e-mail]>; <[e-mail]>
Sent: Friday, August 23, 2013 4:21 PM

> On 08/23/2013 10:16 AM, Adrian Farrel wrote:
> > Really good catch, Tom.
> >
> > What Lou suggests looks the best way to handle it.
> >
>
> Great.  Look for the publication announcement in a few minutes.

Yes.

I would prefer that the Switching Types portion of the GMPLS Signaling
Parameters was handled in a comparable manner, as for example
http://www.iana.org/assignments/icmp-parameters/icmp-parameters.xhtml#ic
mp-parameters-types
does so that PSC-2 PSC-3 PSC-4 still appeared in the registry but with
'deprecated' alongside each of them.  Given the updated reference to
whatever RFC this I-D becomes, then it will be relatively easy to follow
that link and see what these deprecated entries once were so it is a
minor consideration.

Tom Petch

> Lou
>
> > A
> >
> >> -----Original Message-----
> >> From: Lou Berger [mailto:[e-mail]]
> >> Sent: 23 August 2013 14:38
> >> To: t.petch; [e-mail]
> >> Cc: [e-mail];
[e-mail]
> >> Subject: Re: [CCAMP] AD review of draft-ietf-ccamp-swcaps-update
> >>
> >> Tom,
> >> See below.
> >>
> >> ...
> >>
> >>>> On 8/21/2013 6:55 AM, Adrian Farrel wrote:
> >> ...
> >>
> >>>>>
> >>>>> Please add a note to the IANA considerations section to request
an
> >>>>> update to
> >>>>>
> >>>
https://www.iana.org/assignments/ianagmplstc-mib/ianagmplstc-mib.xhtml
> >>>>>
> >>>>> Possibly you should refer to it as IANA-GMPLS-TC-MIB rather than
> >>> through
> >>>>> the URL.
> >>>> The proposed text to be added to the end of the section is:
> >>>>
> >>>>    A parallel change to IANA-GMPLS-TC-MIB is also required. In
> >>>>    particular, under IANAGmplsSwitchingTypeTC a reference to this
> >>>>    document should be added as item 3. Also the following changes
> >>> should
> >>>>    be made to the related values:
> >>>>
> >>>>           deprecated(2),      -- Deprecated
> >>>>           deprecated(3),      -- Deprecated
> >>>>           deprecated(4),      -- Deprecated
> >>>
> >>> Mmmmm RFC4181 says
> >>>
> >>> "Therefore, labels of named numbers and named
> >>>   bits MUST NOT be changed when revising IETF MIB modules (except
to
> >>>   correct typographical errors), and they SHOULD NOT be changed
when
> >>>   revising enterprise MIB modules.
> >>> "
> >>>
> >>> so I do not think that you can do that.  Change of STATUS (which
applies
> >>> to the whole TC) yes, label no. (Don't you love SNMP?)
> >>>
> >>> Tom Petch
> >>>
> >>
> >> Looks like you're right.
> >>
> >> Perhaps the following is the "right" middle ground:
> >> Existing:
> >>                   psc2(2),      -- Packet-Switch-Capable 2
> >>                   psc3(3),      -- Packet-Switch-Capable 3
> >>                   psc4(4),      -- Packet-Switch-Capable 4
> >> Revised:
> >>                   psc2(2),      -- Deprecated [This.document]
> >>                   psc3(3),      -- Deprecated [This.document]
> >>                   psc4(4),      -- Deprecated [This.document]
> >>
> >> Adrian,
> >>
> >> Do you agree with the above?  This is a bit different than your
request.
> >>
> >> Much thanks,
> >> Lou
> >
> >
>
>