Subject: Non-member submission from ["Cheenu Srinivasan" <[email-masked]>]

From: "Ted Brunner 503.627.1317" <[email-masked]>
Date: Mon, 15 Jun 1998 00:27:26 -0700

------- Forwarded Message

From: "Cheenu Srinivasan" <[email-masked]>
To: <[email-masked]>, <[email-masked]>
Subject: Re: Reasons why we need better control over IANAifType...
Date: Fri, 12 Jun 1998 18:18:59 -0400
Message-ID: <[email-masked]>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.71.1712.3
X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3

If you look carefully at this assignment it will refer to RFC 2325.
This RFC was issued on April 1, 1998. Does that ring a bell?

Cheenu

- -----Original Message-----
From: sdurham <[email-masked]>
To: [email-masked] <[email-masked]>
Date: Friday, June 12, 1998 5:25 PM
Subject: Reasons why we need better control over IANAifType...

>coffee (132),       -- coffee pot
>
>do we really need a coffee pot sublayer in the interfaces mib?
>
>I think it was perkins who brought up an old issue - how we have really
>not a clue what some of these ifTypes refer to. Is there any way we can
>limit requests to IANA for ifType assigments so that they only come from
>the IFMIB working group chair, or some duly appointed stuckees? That way
>we can mandate that a descriptor document go along with all ifTypes so
>we at least have a reference to whether or not said coffee pot must
>support only IfGeneralInformationGroup...
>
>...and now we have not only the problem of determining duplex speeds
>from some other mibs, we have to figure out  caf/decaf from someplace
>outside the ifmib too...
>
>sandra
>ps  digitalPowerline (138), -- IP over Power Lines ??
>

------- End of Forwarded Message