IETF Logo Mail Archive

[Fwd: RFC 4048 on RFC 1888 Is Obsolete]

Brian E Carpenter <brc@zurich.ibm.com> Sun, 17 April 2005 07:04 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DN3pH-0007pk-BS; Sun, 17 Apr 2005 03:04:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DN3pE-0007oi-1Z for ipv6@megatron.ietf.org; Sun, 17 Apr 2005 03:04:12 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA28435 for <ipv6@ietf.org>; Sun, 17 Apr 2005 03:04:09 -0400 (EDT)
Received: from mtagate2.uk.ibm.com ([195.212.29.135]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DN3zk-0003Fq-9k for ipv6@ietf.org; Sun, 17 Apr 2005 03:15:05 -0400
Received: from d06nrmr1507.portsmouth.uk.ibm.com (d06nrmr1507.portsmouth.uk.ibm.com [9.149.38.233]) by mtagate2.uk.ibm.com (8.12.10/8.12.10) with ESMTP id j3H73xpW316536 for <ipv6@ietf.org>; Sun, 17 Apr 2005 07:03:59 GMT
Received: from d06av01.portsmouth.uk.ibm.com (d06av01.portsmouth.uk.ibm.com [9.149.37.212]) by d06nrmr1507.portsmouth.uk.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id j3H73xwa046250 for <ipv6@ietf.org>; Sun, 17 Apr 2005 08:03:59 +0100
Received: from d06av01.portsmouth.uk.ibm.com (loopback [127.0.0.1]) by d06av01.portsmouth.uk.ibm.com (8.12.11/8.12.11) with ESMTP id j3H73wf4018158 for <ipv6@ietf.org>; Sun, 17 Apr 2005 08:03:58 +0100
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232]) by d06av01.portsmouth.uk.ibm.com (8.12.11/8.12.11) with ESMTP id j3H73wOP018155 for <ipv6@ietf.org>; Sun, 17 Apr 2005 08:03:58 +0100
Received: from zurich.ibm.com (sig-9-145-132-253.de.ibm.com [9.145.132.253]) by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id JAA57410 for <ipv6@ietf.org>; Sun, 17 Apr 2005 09:03:57 +0200
Message-ID: <42620A5D.4070700@zurich.ibm.com>
Date: Sun, 17 Apr 2005 09:03:57 +0200
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en, fr, de
MIME-Version: 1.0
To: IPv6 <ipv6@ietf.org>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Content-Transfer-Encoding: 7bit
Subject: [Fwd: RFC 4048 on RFC 1888 Is Obsolete]
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org

-------- Original Message --------
Subject: RFC 4048 on RFC 1888 Is Obsolete
Date: Fri, 15 Apr 2005 12:20:00 -0700
From: rfc-editor@rfc-editor.org
To: ietf-announce@ietf.org
CC: rfc-editor@rfc-editor.org


A new Request for Comments is now available in online RFC libraries.


         RFC 4048

         Title:      RFC 1888 Is Obsolete
         Authors:    B. Carpenter
         Status:     Informational
         Date:       April 2005
         Mailbox:    brc@zurich.ibm.com
         Pages:      4
         Characters: 7394
         Updates/Obsoletes/SeeAlso:    None

         I-D Tag:    draft-carpenter-obsolete-1888-01.txt

         URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4048.txt


This document recommends that RFC 1888, on Open Systems
Interconnection (OSI) Network Service Access Points (NSAPs) and IPv6,
be reclassified as Historic, as most of it has no further value,
apart from one section, which is faulty.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs.  For example:

         To: rfc-info@RFC-EDITOR.ORG
         Subject: getting rfcs

         help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute




--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

v2.23.0 | Report a Bug | By Email