Re: [Idr] RFC 4684 pedantry - routes with no Route Target

Robert Raszuk <robert@raszuk.net> Mon, 16 June 2014 08:28 UTC

Return-Path: <rraszuk@gmail.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9772D1B2B95 for <idr@ietfa.amsl.com>; Mon, 16 Jun 2014 01:28:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level:
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 Tlt5ZuPLf5K9 for <idr@ietfa.amsl.com>; Mon, 16 Jun 2014 01:28:29 -0700 (PDT)
Received: from mail-ie0-x22f.google.com (mail-ie0-x22f.google.com [IPv6:2607:f8b0:4001:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A0E81B2B9D for <idr@ietf.org>; Mon, 16 Jun 2014 01:28:29 -0700 (PDT)
Received: by mail-ie0-f175.google.com with SMTP id tp5so4733359ieb.34 for <idr@ietf.org>; Mon, 16 Jun 2014 01:28:28 -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:message-id:subject :from:to:cc:content-type; bh=eLRYWGc3BdzuUJbr4FYcIXSTyYeC8wBG/u6YshHRoZM=; b=LOYLFgQn4V4LI1jHwGjAD2NDyi7aG+wBW9sipAOQblPlU7QkpXGsrdKwTzcatIHjhT IEONfJmxAfZ3rerpQEzHAZng/rDS3naESybHnoP7ZCBr6whGHhR58+YAcjJ1HxCKuR1i Brr4zG70t0mgYfAg0tOgzzAV0kwnRonUsxCskviQ7URVbzCYa+tiiWTLLpq22eO7ESpZ /dOHVjhYP9vKH77paZBGDdLIx5zYqSPehnEujIx5kxFsqglLeQv3L+A9JKGZUOAgQChF Qapuj/Qrx0DMMnAc/f8gS3jgA8bv9fFn64VliP2UC17kbUw3TATtFUp1/WwMa4nT4tlm 9gmg==
MIME-Version: 1.0
X-Received: by 10.50.114.194 with SMTP id ji2mr23847410igb.21.1402907308487; Mon, 16 Jun 2014 01:28:28 -0700 (PDT)
Sender: rraszuk@gmail.com
Received: by 10.64.242.198 with HTTP; Mon, 16 Jun 2014 01:28:28 -0700 (PDT)
In-Reply-To: <76CD132C3ADEF848BD84D028D243C9273367B9D0@nkgeml512-mbx.china.huawei.com>
References: <25B13537-15F0-4994-8504-C04FF94C72C3@juniper.net> <13330.1401455098@erosen-lnx> <76CD132C3ADEF848BD84D028D243C9273367B9D0@nkgeml512-mbx.china.huawei.com>
Date: Mon, 16 Jun 2014 10:28:28 +0200
X-Google-Sender-Auth: k7VH6CTB5n3e2UCfNiaJkpIK88c
Message-ID: <CA+b+ERkJKvYJvoCM4p-uAUL+QXqDwGAjDjsxqQmi9U7iOq5kxg@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
To: "Dongjie (Jimmy)" <jie.dong@huawei.com>
Content-Type: multipart/alternative; boundary="089e013a0c68c67a3604fbefcf06"
Archived-At: http://mailarchive.ietf.org/arch/msg/idr/MEb1Cw0ad09v1aeI1hxsdsGtzio
Cc: "erosen@cisco.com" <erosen@cisco.com>, "idr@ietf.org" <idr@ietf.org>
Subject: Re: [Idr] RFC 4684 pedantry - routes with no Route Target
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 16 Jun 2014 08:28:33 -0000

Jie,

In my understanding, this implies two things:
>
>  1) RTC could be enabled on a particular AFI/SAFI;
>

​Yes.​


>  2) RTC processing for different AFI/SAFIs could be different;
>

​No.​



> While currently RTC is a global capability, which cannot be enabled on a
> particular AFI/SAFI only,



​Of course we can - why not ? To send RTs and to process them requires a
command on a per AF basis. ​



> either cannot behave differently for different AFI/SAFIs.


​That was never subject of this discussion. It's completely separate change
which does require changes to base spec.​


So can I infer that you prefer to make RTC a AFI/SAFI specific capability?
>

​That was also never part of this topic.

I would recommend to separate the discussion into specifying ​the default
behavior for routes with no RTs while separately discuss changes to base
RFC to make it per AFI/SAFI (provided there is community support for such
major rewrite).

Best,
R.