[Idr] WG Last Call: draft-ietf-idr-vpn-prefix-orf-21 (Ends 2025-09-24)

Keyur Patel via Datatracker <noreply@ietf.org> Wed, 10 September 2025 19:27 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: idr@ietf.org
Delivered-To: idr@mail2.ietf.org
Received: from [10.244.8.59] (unknown [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 0D3B1609D717; Wed, 10 Sep 2025 12:27:28 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Keyur Patel via Datatracker <noreply@ietf.org>
To: draft-ietf-idr-vpn-prefix-orf@ietf.org, idr-chairs@ietf.org, idr@ietf.org, keyur@arrcus.com
X-Test-IDTracker: no
X-IETF-IDTracker: 12.49.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <175753244798.27047.17514132167863887857@dt-datatracker-f7c8fdcb7-pjx77>
Date: Wed, 10 Sep 2025 12:27:28 -0700
Message-ID-Hash: V7NRZAYQYXQXGU32OLPSDEDFPORXPFY6
X-Message-ID-Hash: V7NRZAYQYXQXGU32OLPSDEDFPORXPFY6
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-idr.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Reply-To: Keyur Patel <keyur@arrcus.com>
Subject: [Idr] WG Last Call: draft-ietf-idr-vpn-prefix-orf-21 (Ends 2025-09-24)
List-Id: Inter-Domain Routing <idr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/e10qGdjqpY0WAhJNPJ6YLO_QOzE>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Owner: <mailto:idr-owner@ietf.org>
List-Post: <mailto:idr@ietf.org>
List-Subscribe: <mailto:idr-join@ietf.org>
List-Unsubscribe: <mailto:idr-leave@ietf.org>

Subject: WG Last Call: draft-ietf-idr-vpn-prefix-orf-21 (Ends 2025-09-24)

This message starts a 2-week WG Last Call for this document.

Abstract:
   This draft defines a new type of Outbound Route Filter (ORF), known
   as the Virtual Private Network (VPN) Prefix ORF.  The VPN Prefix ORF
   mechanism is applicable when VPN routes from different Virtual
   Routing and Forwardings (VRFs) are exchanged through a single shared
   Border Gateway Protocol (BGP) session.

File can be retrieved from:
https://datatracker.ietf.org/doc/draft-ietf-idr-vpn-prefix-orf/

Please review and indicate your support or objection to proceed with the
publication of this document by replying to this email keeping idr@ietf.org
in copy. Objections should be motivated and suggestions to resolve them are
highly appreciated.

Authors, and WG participants in general, are reminded again of the
Intellectual Property Rights (IPR) disclosure obligations described in BCP 79
[1]. Appropriate IPR disclosures required for full conformance with the
provisions of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of
any. Sanctions available for application to violators of IETF IPR Policy can
be found at [3].

Thank you.

[1] https://datatracker.ietf.org/doc/bcp78/
[2] https://datatracker.ietf.org/doc/bcp79/
[3] https://datatracker.ietf.org/doc/rfc6701/