Re: IANAifType at IANA web site

[James Watt <[e-mail]>]

Dave Fowler writes:
+--------
|> 1) Wrt to  'g703-2mb(67)', I have a couple of problems:
|> 
|> a) this should be a new value for dsx1LineCode, not a new ifType given that
|>    we have already said we wanted to deprecate the use of the ifType value
|>    of 'e1(19)' and use appropriate values of dsx1LineType
|
|I agree here and would be happy to add g703at64k and g703at2mb as line types.
|One question though:  Is it sufficient to add only a line type of g703
|and let the ifSpeed determine the speed of the g703 interface?
+------------
Interesting concept.  I had only thought about doing the 2Mbit/s case as I
hadn't figured out what it would mean to do the co-directonal case.  But
perhaps we should do that.  In both cases we need text to say which other
objects do or don't apply.

+--------
|> 2) Which reminds me, where do we note that the value of 'e1(19)' is deprecated
|> and one should instead use an ifType of 'ds1(18) and an appropriate
|> dsx1LineType value.  Is a simple comment of 'obsolete, see TRUNK-MIB' in
|> the IANAifType-MIB and an explanation in the TRUNK-MIB good enough ?
|
|If we're keen to put rfc references in this list, then we should be more
|complete.  We can add rfc1604 for frameRelayService, rfc1595 for sonet,
|rfc1407 for ds3, etc.
+---------
The RFC numbers were deliberately left out so that Joyce and John don't
have to update the ifType list every time we advance a MIB module.
This is why MIB modules no longer have the RFC # in their "name".

Regards,
-james

____________________________________________________________________________
James W. Watt,     [e-mail]                   Ph: [phone]
Newbridge Networks 600 March Rd Kanata ON Canada K2K 2E6 FAX:[phone]