RFC 5181 on IPv6 Deployment Scenarios in 802.16 Networks

rfc-editor@rfc-editor.org Fri, 09 May 2008 21:59 UTC

Return-Path: <ietf-announce-bounces@ietf.org>
X-Original-To: ietf-announce-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-announce-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B17E43A67D0; Fri, 9 May 2008 14:59:14 -0700 (PDT)
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 751723A67D0 for <ietf-announce@core3.amsl.com>; Fri, 9 May 2008 14:59:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.49
X-Spam-Level:
X-Spam-Status: No, score=-17.49 tagged_above=-999 required=5 tests=[AWL=0.109, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S9DeH0c9jp8T for <ietf-announce@core3.amsl.com>; Fri, 9 May 2008 14:59:11 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 685E33A67A8 for <ietf-announce@ietf.org>; Fri, 9 May 2008 14:59:11 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id 045FA129C23; Fri, 9 May 2008 14:28:29 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5181 on IPv6 Deployment Scenarios in 802.16 Networks
From: rfc-editor@rfc-editor.org
Message-Id: <20080509212829.045FA129C23@bosco.isi.edu>
Date: Fri, 09 May 2008 14:28:29 -0700
Cc: v6ops@ops.ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Announcements <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.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://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
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 5181

        Title:      IPv6 Deployment Scenarios in 802.16 
                    Networks 
        Author:     M-K. Shin, Ed., Y-H. Han, S-E. Kim,
                    D. Premec
        Status:     Informational
        Date:       May 2008
        Mailbox:    myungki.shin@gmail.com, yhhan@kut.ac.kr, 
                    sekim@kt.co.kr, domagoj.premec@siemens.com
        Pages:      16
        Characters: 36671
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-v6ops-802-16-deployment-scenarios-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5181.txt

This document provides a detailed description of IPv6 deployment and
integration methods and scenarios in wireless broadband access
networks in coexistence with deployed IPv4 services.  In this
document, we will discuss the main components of IPv6 IEEE 802.16
access networks and their differences from IPv4 IEEE 802.16 networks
and how IPv6 is deployed and integrated in each of the IEEE 802.16
technologies.  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://www.ietf.org/mailman/listinfo/ietf-announce