[Idr] Multicast Geo-distribution features for BGP

Jeffrey Haas <jhaas@pfrc.org> Tue, 16 July 2013 15:20 UTC

Return-Path: <jhaas@slice.pfrc.org>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2ADA821F9B2A for <idr@ietfa.amsl.com>; Tue, 16 Jul 2013 08:20:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level:
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zG034OiRrKhT for <idr@ietfa.amsl.com>; Tue, 16 Jul 2013 08:20:22 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 0E2B221F9AF5 for <idr@ietf.org>; Tue, 16 Jul 2013 08:20:22 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 9B193C256; Tue, 16 Jul 2013 11:20:21 -0400 (EDT)
Date: Tue, 16 Jul 2013 11:20:21 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: idr@ietf.org
Message-ID: <20130716152021.GA23506@pfrc>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: zzhang@juniper.net, yakov@juniper.net, hj2387@att.com
Subject: [Idr] Multicast Geo-distribution features for BGP
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jul 2013 15:20:27 -0000

IDR,

The authors of Multicast Geo-Distribution Control would like to draw your
attention to the following drafts.  The base geo distribution draft was
presented a few IETFs ago in GROW and MBONED.

In very brief summary, for multicast capable networks, there is need to be
able to determine if subscribers are capable of receiving content via
multicast.  When they are capable of receiving it via multicast, there are
situations where subscribers may subvert access control mechanisms for
content.

The geo-distribution draft covers the operational scenario.  The BGP
signaling components of this draft have been separately split into two
drafts to cover their functionality: Multicast Distribution Reachability
Signaling to determine if a subscriber can receive content via multicast,
and Multicast Distribution Control Signaling to provide filtering mechanisms
for multicast signaling protocols.

While these mechanisms can be run in a network along with traditional BGP
forwarding applications (Internet, VPN, etc.), this application may also run
in a separate multicast network-specific context potentially on different peering
sessions.  Hopefully this alleviates the usual concern about "overloading
the BGP control plane".  

One thing these drafts also do that requires no changes to specification but
is a somewhat unusual application is making use of Constrained Route-target
distribution (RT-C) for non-VPN NLRI.  This is already permitted by the RFC,
but as far as I'm aware is not deployed.

http://tools.ietf.org/html/draft-rekhter-geo-distribution-control-03
http://tools.ietf.org/html/draft-rekhter-mdrs-00
http://tools.ietf.org/html/draft-rekhter-mdcs-00

We would like to request a brief (15 minute maximum) timeslot in IDR to
cover the BGP specific changes.  Our goal is to request adoption of MDRS and
MDCS in IDR.  We will likely request adoption of geo-distribution in MBONED.
This is consistent with the funtionality split that was suggested as part of
our feedback in GROW and MBONED.

-- Jeff