IETF Logo Mail Archive

Re: [Idr] Fwd: I-DACTION:draft-pmohapat-idr-acceptown-community-01.txt

"Pradosh Mohapatra (pmohapat)" <pmohapat@cisco.com> Mon, 28 July 2008 13:33 UTC

Return-Path: <idr-bounces@ietf.org>
X-Original-To: idr-archive@megatron.ietf.org
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C92D13A6A8D; Mon, 28 Jul 2008 06:33:50 -0700 (PDT)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E00E13A6A5F; Mon, 28 Jul 2008 06:33:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level:
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6hqSrVqKew53; Mon, 28 Jul 2008 06:33:45 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 2299C3A6813; Mon, 28 Jul 2008 06:33:45 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.31,265,1215388800"; d="scan'208";a="69599742"
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-2.cisco.com with ESMTP; 28 Jul 2008 13:33:55 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m6SDXtnD005174; Mon, 28 Jul 2008 06:33:55 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m6SDXsjG021079; Mon, 28 Jul 2008 13:33:54 GMT
Received: from xmb-sjc-215.amer.cisco.com ([171.70.151.169]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 28 Jul 2008 06:33:54 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 28 Jul 2008 06:33:52 -0700
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D54078032B9@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <1318F740-31EB-4D36-B487-EB647301F680@cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Idr] Fwd: I-DACTION:draft-pmohapat-idr-acceptown-community-01.txt
thread-index: AcjwsNz1RZzP0XSOQzqNVOf5BLlM9gAAJtnA
References: <20080425213001.4EB133A69E7@core3.amsl.com><64E4CA6A-B8E4-4390-BDA6-39EF28E95AEA@tcb.net> <1318F740-31EB-4D36-B487-EB647301F680@cisco.com>
From: "Pradosh Mohapatra (pmohapat)" <pmohapat@cisco.com>
To: David Ward <dward@cisco.com>, Danny McPherson <danny@tcb.net>, Robert Raszuk <raszuk@juniper.net>, Marshall Eubanks <tme@multicasttech.com>
X-OriginalArrivalTime: 28 Jul 2008 13:33:54.0649 (UTC) FILETIME=[94849490:01C8F0B6]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1413; t=1217252035; x=1218116035; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=pmohapat@cisco.com; z=From:=20=22Pradosh=20Mohapatra=20(pmohapat)=22=20<pmohapat @cisco.com> |Subject:=20RE=3A=20[Idr]=20Fwd=3A=20I-DACTION=3Adraft-pmoh apat-idr-acceptown-community-01.txt |Sender:=20; bh=ARO/FFGVkMoigeMm1Sn4NGQn/NjCEFJybVc0JU3wOcc=; b=ZMFa1QPtZaRSNtBTCz+ewO/N7XiSGouE1xh7k/sUGMkZb/UefWGv3GMDSn oG5OphqmqzqcI2LXc0rE/EW2JsmXdnaV4FtjcZv5sHGHGQBmioiRc594ddWk xX8Q+nv58k;
Authentication-Results: sj-dkim-4; header.From=pmohapat@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; );
Cc: idr <idr@ietf.org>, l3vpn@ietf.org
Subject: Re: [Idr] Fwd: I-DACTION:draft-pmohapat-idr-acceptown-community-01.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

| Robert -
| 
| In the L3VPN WG I asked a question on your use of well-known 
| BGP communities in this draft (as it is related to the IANA 
| BGP Well- Known Communities reservation procedures discussed 
| in IDR).  The question was "how do you know when the 
| community is well-known throughout the internet or service 
| provider network?" You answer was "it is off by default and 
| you have to configure it to be on, therefore the operator 
| knows what they are doing." That is a fine answer but, you 
| are using this as a reserved codepoint vs the semantics of 
| well-known communities (in which if a router receives the 
| well-known community whether configured or not, action is taken).  
| Does anyone care about the change of semantics and a router 
| will not pay attention to the community without configuration?

Going by the rule that well-known communities have global
significance & should be implemented by any community-attribute-
aware BGP speaker, I would agree to your earlier proposal that
split the reserved space and have some set of communities that
are either IANA allocated or FCFS allocated... and just call
the new ones reserved communities (*not* well-known). That also 
aligns with the fact that all BGP attributes defined later 
(than 1771) become optional by definition ;-)

- Pradosh

| 
| Thanks
| 
| -DWard
_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr

v2.23.0 | Report a Bug | By Email