RFC 8278 on Mobile Access Gateway (MAG) Multipath Options
rfc-editor@rfc-editor.org Wed, 24 January 2018 16:00 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A5711242F7; Wed, 24 Jan 2018 08:00:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lIG62_IP_mQ0; Wed, 24 Jan 2018 08:00:15 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D83612DA73; Wed, 24 Jan 2018 08:00:15 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 8D9F3B80CED; Wed, 24 Jan 2018 08:00:00 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8278 on Mobile Access Gateway (MAG) Multipath Options
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, dmm@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180124160000.8D9F3B80CED@rfc-editor.org>
Date: Wed, 24 Jan 2018 08:00:00 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/UoZ2GLvNaj91dteglTuKqSGwJz8>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
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>
X-List-Received-Date: Wed, 24 Jan 2018 16:00:18 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8278
Title: Mobile Access Gateway (MAG)
Multipath Options
Author: P. Seite,
A. Yegin,
S. Gundavelli
Status: Standards Track
Stream: IETF
Date: January 2018
Mailbox: pierrick.seite@orange.com,
alper.yegin@actility.com,
sgundave@cisco.com
Pages: 15
Characters: 32313
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-dmm-mag-multihoming-07.txt
URL: https://www.rfc-editor.org/info/rfc8278
DOI: 10.17487/RFC8278
This specification defines extensions to the Proxy Mobile IPv6
(PMIPv6) protocol that allow a mobile access gateway (MAG) to
register more than one proxy care-of address (pCoA) with the local
mobility anchor (LMA) and to simultaneously establish multiple IP
tunnels with the LMA. This capability allows the MAG to utilize all
the available access networks to route the mobile node's IP traffic.
This document defines the following two new mobility header options:
the MAG Multipath Binding option and the MAG Identifier option.
This document is a product of the Distributed Mobility Management Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
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