IETF Logo Mail Archive

Re: [Idr] 2 week WG adoption call for draft (5/31 to 6/14)

"Susan Hares" <shares@ndzh.com> Mon, 01 June 2015 21:37 UTC

Return-Path: <shares@ndzh.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 99DA61A0068 for <idr@ietfa.amsl.com>; Mon, 1 Jun 2015 14:37:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.156
X-Spam-Level:
X-Spam-Status: No, score=-97.156 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DOS_OUTLOOK_TO_MX=2.845, USER_IN_WHITELIST=-100] 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 2StaipP8-P1Q for <idr@ietfa.amsl.com>; Mon, 1 Jun 2015 14:37:48 -0700 (PDT)
Received: from hickoryhill-consulting.com (hhc-web3.hickoryhill-consulting.com [64.9.205.143]) by ietfa.amsl.com (Postfix) with ESMTP id C66DE1A005C for <idr@ietf.org>; Mon, 1 Jun 2015 14:37:47 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=184.157.80.157;
From: Susan Hares <shares@ndzh.com>
To: 'Nick Hilliard' <nick@foobar.org>, 'IETF IDR Working Group' <idr@ietf.org>
References: <006801d09c15$ba8bba30$2fa32e90$@ndzh.com> <556CCBCA.6070308@foobar.org>
In-Reply-To: <556CCBCA.6070308@foobar.org>
Date: Mon, 01 Jun 2015 17:37:42 -0400
Message-ID: <023501d09cb3$313ee970$93bcbc50$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJg7LE/xZJIxYjXt4BODNqSVdP/UAHvrmx0nGgPFBA=
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/Dohdt2eXK2tHaVfP-Ed__IVc4qk>
Cc: draft-raszuk-wide-bgp-communities@tools.ietf.org
Subject: Re: [Idr] 2 week WG adoption call for draft (5/31 to 6/14)
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, 01 Jun 2015 21:37:48 -0000

Nick:

<WG chair hat off > I can understand how the draft will be complex to
implement along with other communities.  Can you describe how you think the
draft will be complicated to operate?   
Sue Hares

-----Original Message-----
From: Nick Hilliard [mailto:nick@foobar.org] 
Sent: Monday, June 01, 2015 5:17 PM
To: Susan Hares; IETF IDR Working Group
Cc: draft-raszuk-wide-bgp-communities@tools.ietf.org
Subject: Re: [Idr] 2 week WG adoption call for draft (5/31 to 6/14)

On 01/06/2015 03:50, Susan Hares wrote:
> Please discuss
> 
> a)       If these drafts should be adopted in addition to
> draft-ietf-idr-as4octet-extcomm-generic-subtype-07,

yes, draft-ietf-idr-as4octet-extcomm-generic-subtype is still restricted to
48 bits of community space, which is insufficient for flexible management of
asn32 based networks.

> b)       whether the new flexible format is useful for BGP deployments,
and

yes, asn32s have serious deployment problems due to poor bgp community
support.  This draft - if implemented by vendors - will provide a long term
fix for that problem.

> c)       Any technical issues on the draft.

I am concerned that the draft will be complicated both to implement and to
operate.  However, it provides the sort of hooks that advanced operators
would dearly like to have.

> As always, indicate "support" or "no support" within the comment. 

fully support.

Nick

v2.23.0 | Report a Bug | By Email