RFC 8059 on PIM Join Attributes for Locator/ID Separation Protocol (LISP) Environments
rfc-editor@rfc-editor.org Fri, 20 January 2017 16:17 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 D15E1129C18; Fri, 20 Jan 2017 08:17:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.401
X-Spam-Level:
X-Spam-Status: No, score=-7.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, 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 ePgBxNshPapm; Fri, 20 Jan 2017 08:17:56 -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 1D278129C17; Fri, 20 Jan 2017 08:17:50 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id E1653B81279; Fri, 20 Jan 2017 08:17:49 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8059 on PIM Join Attributes for Locator/ID Separation Protocol (LISP) Environments
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170120161749.E1653B81279@rfc-editor.org>
Date: Fri, 20 Jan 2017 08:17:49 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/L08eHwbA3vF9kfDWFZDieCm5igY>
Cc: drafts-update-ref@iana.org, pim@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
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: Fri, 20 Jan 2017 16:17:58 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8059
Title: PIM Join Attributes for Locator/ID
Separation Protocol (LISP) Environments
Author: J. Arango, S. Venaas,
I. Kouvelas, D. Farinacci
Status: Experimental
Stream: IETF
Date: January 2017
Mailbox: jearango@cisco.com,
stig@cisco.com,
kouvelas@arista.com,
farinacci@gmail.com
Pages: 9
Characters: 19562
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-pim-join-attributes-for-lisp-06.txt
URL: https://www.rfc-editor.org/info/rfc8059
DOI: 10.17487/RFC8059
This document defines two PIM Join/Prune attributes that support the
construction of multicast distribution trees where the root and
receivers are located in different Locator/ID Separation Protocol
(LISP) sites. These attributes allow the receiver site to select
between unicast and multicast underlying transport and to convey the
RLOC (Routing Locator) address of the receiver ETR (Egress Tunnel
Router) to the control plane of the root ITR (Ingress Tunnel Router).
This document is a product of the Protocols for IP Multicast 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
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