[irs-discuss] Fwd: I-D Action: draft-keyupate-bgp-services-01.txt

Robert Raszuk <robert@raszuk.net> Mon, 22 October 2012 22:02 UTC

Return-Path: <rraszuk@gmail.com>
X-Original-To: irs-discuss@ietfa.amsl.com
Delivered-To: irs-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BA7F11E80E1; Mon, 22 Oct 2012 15:02:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.886
X-Spam-Level:
X-Spam-Status: No, score=-2.886 tagged_above=-999 required=5 tests=[AWL=0.091, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5x8eFoWE9142; Mon, 22 Oct 2012 15:02:52 -0700 (PDT)
Received: from mail-ia0-f172.google.com (mail-ia0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7CB7D21F84B2; Mon, 22 Oct 2012 15:02:52 -0700 (PDT)
Received: by mail-ia0-f172.google.com with SMTP id o25so2904596iad.31 for <multiple recipients>; Mon, 22 Oct 2012 15:02:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=fxgkgk/jXsvC5FWi0Xv/GZqXprgcbo33eWkZPNtOUxM=; b=VNbdfSq4YRM3JH9wMfPF6IlK8KcRuD3qVY6aaGXAuX0Y8xMjieQQXaQrC953lkmzaE MXG8InMjf/Mh0cEu1KNR/muMAv8xnGcy31cvS7UD5VloKWpnTa+4r9yVxQKuQ8KID5jg eT2JURyaO7eVijXSgS86+g7vgQuJXpjp8TtijopA6ehzWNzWMyU1VvzELDvAsYGcr41Z yhSvBjea5c+t73HtZ526JTTIyxKQtzmZKeW5OnoQgQWd+2HMRSYoDp46MfhGmfx4yt76 cDq21G6VxGREoH4VH7rWnncvUFRGd6KmtWog7CPzGiwEuIBM4lQJOa5HJuenSq8mPQ/9 7Pdg==
MIME-Version: 1.0
Received: by 10.50.208.71 with SMTP id mc7mr18036576igc.47.1350943371835; Mon, 22 Oct 2012 15:02:51 -0700 (PDT)
Sender: rraszuk@gmail.com
Received: by 10.42.68.133 with HTTP; Mon, 22 Oct 2012 15:02:51 -0700 (PDT)
In-Reply-To: <20121022211358.25006.8180.idtracker@ietfa.amsl.com>
References: <20121022211358.25006.8180.idtracker@ietfa.amsl.com>
Date: Tue, 23 Oct 2012 00:02:51 +0200
X-Google-Sender-Auth: 35S2ueIcE8DBTtXWbA8gQJT6qU8
Message-ID: <CA+b+ERkSX0B1LRSuccGMjMAfEaoLV8f=N3PsEP_wjzo+047E+A@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
To: idr wg <idr@ietf.org>, irs-discuss@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: Pedro Marques <pedro.r.marques@gmail.com>, rjs@rob.sh, Kireeti Kompella <kireeti.kompella@gmail.com>
Subject: [irs-discuss] Fwd: I-D Action: draft-keyupate-bgp-services-01.txt
X-BeenThere: irs-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <irs-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/irs-discuss>, <mailto:irs-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/irs-discuss>
List-Post: <mailto:irs-discuss@ietf.org>
List-Help: <mailto:irs-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/irs-discuss>, <mailto:irs-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 22:02:53 -0000

Dear authors,

After reading this document I would like to observe that BGP seems to
not fit to the proposed application. Not that it is BGP fault, but the
service model required for service dissemination and discovery is much
better to be based on publish, subscribe, search primitives rather
then p2mp data base distribution propagation which is the BGP model.

Putting gateways between service providers and service consumers is a
nice try to address the end point BGP protocol language barrier, but
it does not address the discovery model.

While one could argue that services could have attached RTs and
RT-Constrain could be used to push filter to only receive what is
necessary however current industry have already solved this problem in
a much more elegant way by using MAP servers and IF-MAP protocol
between producers and consumers. The database behind the MAP server
can be build in a very robust way (as compared to today's BGP state of
the art).

I would recommend for the authors to consider such alternatives and
possibly rewrite the proposal to make it fit the needs of this very
important class of application which is service discovery.

Best regards,
R.

---------- Forwarded message ----------
From:  <internet-drafts@ietf.org>
Date: Mon, Oct 22, 2012 at 11:13 PM
Subject: I-D Action: draft-keyupate-bgp-services-01.txt
To: i-d-announce@ietf.org



A New Internet-Draft is available from the on-line Internet-Drafts directories.


        Title           : Service Advertisement using BGP
        Author(s)       : Keyur Patel
                          Jan Medved
                          Rex Fernando
                          Burjiz Pithawala
        Filename        : draft-keyupate-bgp-services-01.txt
        Pages           : 12
        Date            : 2012-10-22

Abstract:
   A variety of services, such as NATs, firewalls, or caches, can be
   embedded in a service provider network or instantiated in data
   centers attached to the network.  This document proposes extensions
   to BGP that facilitate discovery of such service instances by
   interested clients and allows dissemination of service information,
   such as services capabilities or capacities, throughout the network
   domain.  The proposed extensions allow for optimal routing of
   requests to service instances that can optimally serve them.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-keyupate-bgp-services

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-keyupate-bgp-services-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-keyupate-bgp-services-01


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt