RFC 4779 on ISP IPv6 Deployment Scenarios in Broadband Access Networks
rfc-editor@rfc-editor.org Tue, 23 January 2007 02:01 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H9Aya-0004lx-Vo; Mon, 22 Jan 2007 21:01:32 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H9AyZ-0004jU-DW for ietf-announce@ietf.org; Mon, 22 Jan 2007 21:01:31 -0500
Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H9AyY-0000Mm-0i for ietf-announce@ietf.org; Mon, 22 Jan 2007 21:01:31 -0500
Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id l0N21RKW006493; Mon, 22 Jan 2007 18:01:27 -0800
Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id l0N21N2N006492; Mon, 22 Jan 2007 18:01:23 -0800
Date: Mon, 22 Jan 2007 18:01:23 -0800
Message-Id: <200701230201.l0N21N2N006492@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
X-Spam-Score: -14.8 (--------------)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Cc: v6ops@ops.ietf.org, rfc-editor@rfc-editor.org
Subject: RFC 4779 on ISP IPv6 Deployment Scenarios in Broadband Access Networks
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>
Errors-To: ietf-announce-bounces@ietf.org
A new Request for Comments is now available in online RFC libraries.
RFC 4779
Title: ISP IPv6 Deployment Scenarios in
Broadband Access Networks
Author: S. Asadullah, A. Ahmed,
C. Popoviciu, P. Savola,
J. Palet
Status: Informational
Date: January 2007
Mailbox: sasad@cisco.com,
adahmed@cisco.com,
cpopovic@cisco.com, psavola@funet.fi,
jordi.palet@consulintel.es
Pages: 81
Characters: 188511
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-v6ops-bb-deployment-scenarios-05.txt
URL: http://www.rfc-editor.org/rfc/rfc4779.txt
This document provides a detailed description of IPv6 deployment and
integration methods and scenarios in today's Service Provider (SP)
Broadband (BB) networks in coexistence with deployed IPv4 services.
Cable/HFC, BB Ethernet, xDSL, and WLAN are the main BB technologies
that are currently deployed, and discussed in this document. The
emerging Broadband Power Line Communications (PLC/BPL) access
technology is also discussed for completeness. In this document we
will discuss main components of IPv6 BB networks, their differences
from IPv4 BB networks, and how IPv6 is deployed and integrated in
each of these networks using tunneling mechanisms and native IPv6. This
memo provides information for the Internet community.
This document is a product of the IPv6 Operations
Working Group of the IETF.
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.
The RFC Editor Team
USC/Information Sciences Institute
...
_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce