[multimob] RFC 7028 on Multicast Mobility Routing Optimizations for Proxy Mobile IPv6

rfc-editor@rfc-editor.org Fri, 20 September 2013 19:56 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: multimob@ietfa.amsl.com
Delivered-To: multimob@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8109D21F9E0B; Fri, 20 Sep 2013 12:56:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.286
X-Spam-Level:
X-Spam-Status: No, score=-102.286 tagged_above=-999 required=5 tests=[AWL=0.314, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TVkqNZmeGui9; Fri, 20 Sep 2013 12:56:15 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id D781621F9E02; Fri, 20 Sep 2013 12:56:14 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 2964BB1E011; Fri, 20 Sep 2013 12:49:39 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20130920194939.2964BB1E011@rfc-editor.org>
Date: Fri, 20 Sep 2013 12:49:39 -0700
Cc: drafts-update-ref@iana.org, multimob@ietf.org, rfc-editor@rfc-editor.org
Subject: [multimob] RFC 7028 on Multicast Mobility Routing Optimizations for Proxy Mobile IPv6
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multimob>, <mailto:multimob-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multimob>
List-Post: <mailto:multimob@ietf.org>
List-Help: <mailto:multimob-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Sep 2013 19:56:15 -0000

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

        
        RFC 7028

        Title:      Multicast Mobility Routing Optimizations for 
                    Proxy Mobile IPv6 
        Author:     JC. Zuniga, LM. Contreras,
                    CJ. Bernardos, S. Jeon,
                    Y. Kim
        Status:     Experimental
        Stream:     IETF
        Date:       September 2013
        Mailbox:    JuanCarlos.Zuniga@InterDigital.com,
                    lmcm@tid.es,
                    cjbc@it.uc3m.es,
                    seiljeon@av.it.pt,
                    yhkim@dcn.ssu.ac.kr
        Pages:      29
        Characters: 63110
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-multimob-pmipv6-ropt-08.txt

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

This document proposes some experimental enhancements to the base
solution to support IP multicasting in a Proxy Mobile IPv6 (PMIPv6)
domain.  These enhancements include the use of a multicast tree
mobility anchor as the topological anchor point for multicast
traffic, as well as a direct routing option where the Mobile Access
Gateway can provide access to multicast content in the local network.
The goal of these enhancements is to provide benefits such as
reducing multicast traffic replication and supporting different
PMIPv6 deployment scenarios.

This document is a product of the Multicast Mobility Working Group of the IETF.


EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/search/rfc_search.php
For downloading RFCs, see http://www.rfc-editor.org/rfc.html

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


The RFC Editor Team
Association Management Solutions, LLC