[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Obsoleting RFC 1818 and RFC 1871

To: RFC Editor <rfc-editor at rfc-editor.org>
Subject: Obsoleting RFC 1818 and RFC 1871
From: IESG Secretary <iesg-secretary-reply at ietf.org>
Date: Fri, 09 Sep 2005 13:59:11 -0400
Cc: iab at iab.org, ietf-announce at ietf.org
List-help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-id: ietf-announce.ietf.org
List-post: <mailto:ietf-announce@ietf.org>
List-subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
List-unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
Sender: ietf-announce-bounces at ietf.org

In its meeting of September 1, 2005, the IESG noted that
the contents of RFC 1818 and RFC 1871 were superseded by
sections 5 and 9 of RFC 2026 respectively.

RFC 1818 (BCP 1) and RFC 1871 (BCP 2) are therefore deemed
to be obsoleted by RFC 2026 (BCP 9) and are reclassified as
Historic.

_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce

Follow-Ups:
- Re: Obsoleting RFC 1818 and RFC 1871
  - From: RFC Editor

Prev by Date: Protocol Action: 'Mobile Node Identifier Option for MIPv6' to Proposed Standard
Next by Date: Document Action: 'Identity selection hints for Extensible Authentication Protocol (EAP)' to Informational RFC
Previous by thread: Protocol Action: 'Mobile Node Identifier Option for MIPv6' to Proposed Standard
Next by thread: Re: Obsoleting RFC 1818 and RFC 1871
Index(es):
- Date
- Thread