Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Applicability Statement for Reclassification of RFC 1643 to Historic Status (RFC3638)

IP.com Disclosure Number: IPCOM000019819D
Original Publication Date: 2003-Sep-01
Included in the Prior Art Database: 2003-Sep-30
Document File: 6 page(s) / 9K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Flick: AUTHOR [+2]

Abstract

This memo recommends that RFC 1643 be reclassified as an Historic document and provides the supporting motivation for that recommendation.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 41% of the total text.

Network Working Group J. Flick

Request for Comments: 3638 Hewlett-Packard Company

Obsoletes: 1643 C. Heard

Category: Informational Consultant

September 2003

Applicability Statement for Reclassification of

RFC 1643 to Historic Status

Status of this Memo

This memo provides information for the Internet community. It does

not specify an Internet standard of any kind. Distribution of this

memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (2003). All Rights Reserved.

Abstract

This memo recommends that RFC 1643 be reclassified as an Historic

document and provides the supporting motivation for that

recommendation.

1. Details

STD 50, RFC 1643 [RFC1643], "Definitions of Managed Objects for the

Ethernet-like Interface Types", and its SMIv2 equivalent, RFC 1650

[RFC1650], are applicable to half-duplex 10 Mb/s Ethernet interfaces

only. Subsequent to the 1994 publication of these documents, 100

Mb/s, 1000 Mb/s, and 10 Gb/s Ethernet interface types have been

developed, and full-duplex operation at 10 Mb/s has been

standardized. Updates to RFC 1650 have been produced to accommodate

these new technologies [RFC2358] [RFC2665] [RFC2666] [RFC3635].

These updates define new MIB objects to supplement those defined in

RFC 1643 and RFC 1650 and in addition deprecate some of the objects

in RFC 1643 and RFC 1650 that are no longer considered useful. They

also levy a requirement for implementations of the EtherLike-MIB to

support the MAU-MIB [RFC2239] [RFC2668] [RFC3636] as well.

Flick & Heard Informational [Page 1]

RFC 3638 RFC 1643 to Historic Status September 2003

RFC 1643 is an obsolete specification, overtaken by events. Its

SMIv2 equivalent, RFC 1650, was officially retired in 1998. New

implementations -- even those that support only half-duplex 10 Mb/s

interfaces -- should comply with in the latest version of the

specification, currently RFC 3635 [RFC3635] and RFC 2666 [RFC2666],

instead of RFC 1643. It is therefore recommended that RFC 1643 be

reclassified as an Historic document.

2. Effect on Other Standards Track Documents

Reclassification of RFC 1643 will have no impact on the status of any

standards track RFC because no standards track RFC cites it as a

normative reference. An RFC content search made with the tools

available at http://www.rfc-editor.org reveals the following

standards track documents that cite RFC 1643:

Document Title

-------- -----

RFC 2020 IEEE 802.12 Interface MIB

RFC 2358 Definitions of Managed Objects for the

Ethernet-like Interface Types

RFC 2665 Definitions of Managed Objects for the

Ethernet-like Interface Types

RFC 2720 Traffic Flow Measurement: Meter MIB

RFC 3635 Definitions of Managed Objects for the

Ethernet-like Interface Types

RFC 2020 [RFC2020] contains DOT12-IF-MIB, which is the MIB module for

managing IEEE 802.12 100VG-AnyLAN interfaces. It refers to RFC 1643

in the context of an admonition not to implement the EtherLike-MIB

for any interface where the DOT12-IF-MIB is implemented.

RFC 2358 [RFC2358], RF...