RFC 4241 on A Model of IPv6/IPv4 Dual Stack Internet Access Service
rfc-editor@rfc-editor.org Wed, 14 December 2005 01:22 UTC
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EmLLy-0008KI-9B; Tue, 13 Dec 2005 20:22:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EmLLw-0008IS-5c for ietf-announce@megatron.ietf.org; Tue, 13 Dec 2005 20:22:44 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA04009 for <ietf-announce@ietf.org>; Tue, 13 Dec 2005 20:21:47 -0500 (EST)
Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EmLN1-00053z-L0 for ietf-announce@ietf.org; Tue, 13 Dec 2005 20:23:52 -0500
Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.8/8.12.8) with ESMTP id jBE1MfZF008653; Tue, 13 Dec 2005 17:22:41 -0800
Received: (from apache@localhost) by nit.isi.edu (8.12.8/8.12.8/Submit) id jBE1MfOQ008652; Tue, 13 Dec 2005 17:22:41 -0800
Date: Tue, 13 Dec 2005 17:22:41 -0800
Message-Id: <200512140122.jBE1MfOQ008652@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="4c80133743882326268c58a2c66ea035"
X-Spam-Score: -14.7 (--------------)
X-Scan-Signature: 2beba50d0fcdeee5f091c59f204d4365
Cc: rfc-editor@rfc-editor.org
Subject: RFC 4241 on A Model of IPv6/IPv4 Dual Stack Internet Access Service
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
A new Request for Comments is now available in online RFC libraries.
RFC 4241
Title: A Model of IPv6/IPv4 Dual Stack Internet Access
Service
Author(s): Y. Shirasaki, S. Miyakawa, T. Yamasaki,
A. Takenouchi
Status: Informational
Date: December 2005
Mailbox: yasuhiro@nttv6.jp, miyakawa@nttv6.jp,
t.yamasaki@ntt.com, takenouchi.ayako@lab.ntt.co.jp
Pages: 10
Characters: 20580
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-shirasaki-dualstack-service-04.txt
URL: http://www.rfc-editor.org/rfc/4241.txt
This memo is a digest of the user network interface specification of NTT Communications\' dual stack ADSL access service, which provide a IPv6/IPv4 dual stack services to home users. In order to simplify user setup, these services have a mechanism to configure IPv6 specific parameters automatically. The memo focuses on two basic parameters: the prefix assigned to the user and the addresses of IPv6 DNS servers, and it specifies a way to deliver these parameters to Customer Premises Equipment (CPE) automatically. This memo provides information for the Internet community.
INFORMATIONAL: 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-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce