[Softwires] RFC 8389 on Definitions of Managed Objects for Mapping of Address and Port with Encapsulation (MAP-E)
rfc-editor@rfc-editor.org Wed, 19 December 2018 05:17 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 709B812F1A5; Tue, 18 Dec 2018 21:17:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] 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 A2RGytQfpk0I; Tue, 18 Dec 2018 21:17:39 -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 B64F2130FDA; Tue, 18 Dec 2018 21:17:34 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id ED931B80D4D; Tue, 18 Dec 2018 21:17:11 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
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, softwires@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20181219051711.ED931B80D4D@rfc-editor.org>
Date: Tue, 18 Dec 2018 21:17:11 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/softwires/jMZr1NiMOilrqejsRPpkS8N2qJk>
Subject: [Softwires] RFC 8389 on Definitions of Managed Objects for Mapping of Address and Port with Encapsulation (MAP-E)
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Dec 2018 05:17:43 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8389
Title: Definitions of Managed Objects for
Mapping of Address and Port with
Encapsulation (MAP-E)
Author: Y. Fu,
S. Jiang,
B. Liu,
J. Dong,
Y. Chen
Status: Standards Track
Stream: IETF
Date: December 2018
Mailbox: eleven711711@foxmail.com,
jiangsheng@huawei.com,
leo.liubing@huawei.com,
knight.dongjiang@gmail.com,
flashfoxmx@gmail.com
Pages: 16
Characters: 30534
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-softwire-map-mib-13.txt
URL: https://www.rfc-editor.org/info/rfc8389
DOI: 10.17487/RFC8389
This memo defines a portion of the Management Information Base (MIB)
for Mapping of Address and Port with Encapsulation (MAP-E) for use
with network management protocols.
This document is a product of the Softwires 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