[pcp] RFC 7843 on Port Control Protocol (PCP) Third-Party ID Option
rfc-editor@rfc-editor.org Tue, 10 May 2016 22:53 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50D9A12D7E5; Tue, 10 May 2016 15:53:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.898
X-Spam-Level:
X-Spam-Status: No, score=-107.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.996, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 IH1_zcaxh-_Y; Tue, 10 May 2016 15:53:10 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3453612D770; Tue, 10 May 2016 15:53:08 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 2BAB618000F; Tue, 10 May 2016 15:52:14 -0700 (PDT)
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
Message-Id: <20160510225214.2BAB618000F@rfc-editor.org>
Date: Tue, 10 May 2016 15:52:14 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/pcp/busRY-ox2j3ScUGRLVZtbcfXKDw>
Cc: drafts-update-ref@iana.org, pcp@ietf.org, rfc-editor@rfc-editor.org
Subject: [pcp] RFC 7843 on Port Control Protocol (PCP) Third-Party ID Option
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pcp/>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 May 2016 22:53:19 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7843
Title: Port Control Protocol (PCP) Third-Party
ID Option
Author: A. Ripke, R. Winter,
T. Dietz, J. Quittek, R. da Silva
Status: Standards Track
Stream: IETF
Date: May 2016
Mailbox: ripke@neclab.eu,
winter@neclab.eu,
dietz@neclab.eu,
quittek@neclab.eu,
rafaelalejandro.lopezdasilva@telefonica.com
Pages: 14
Characters: 30488
Updates: RFC 6887
I-D Tag: draft-ietf-pcp-third-party-id-option-08.txt
URL: https://www.rfc-editor.org/info/rfc7843
DOI: http://dx.doi.org/10.17487/RFC7843
This document describes a new Port Control Protocol (PCP) option
called the THIRD_PARTY_ID option. It is designed to be used together
with the THIRD_PARTY option specified in RFC 6887.
The THIRD_PARTY_ID option serves to identify a third party in
situations where a third party's IP address contained in the
THIRD_PARTY option does not provide sufficient information to create
requested mappings in a PCP-controlled device.
This document is a product of the Port Control Protocol 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