Re: [Idr] Accept draft-wkumari-idr-as0-01.txt ?

Arturo Servin <aservin@lacnic.net> Mon, 14 November 2011 01:48 UTC

Return-Path: <aservin@lacnic.net>
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 B75101F0C5A for <idr@ietfa.amsl.com>; Sun, 13 Nov 2011 17:48:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.204
X-Spam-Level:
X-Spam-Status: No, score=-1.204 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, NO_RELAYS=-0.001]
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 IVmABG-xeZU5 for <idr@ietfa.amsl.com>; Sun, 13 Nov 2011 17:48:09 -0800 (PST)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id D761E1F0C45 for <idr@ietf.org>; Sun, 13 Nov 2011 17:48:08 -0800 (PST)
Received: from [IPv6:2001:df8::16:7077:f636:130d:66d4] (unknown [IPv6:2001:df8:0:16:7077:f636:130d:66d4]) by mail.lacnic.net.uy (Postfix) with ESMTP id DB6A6308427; Sun, 13 Nov 2011 23:48:05 -0200 (UYST)
References: <7E27D7DD-8A61-43E8-904E-DEDB3B2D2C92@kumari.net>
In-Reply-To: <7E27D7DD-8A61-43E8-904E-DEDB3B2D2C92@kumari.net>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="us-ascii"
Message-Id: <BC8B0F1C-F8DD-4134-980E-93E552688766@lacnic.net>
X-Mailer: iPad Mail (9A334)
From: Arturo Servin <aservin@lacnic.net>
Date: Sun, 13 Nov 2011 23:48:46 -0200
To: Warren Kumari <warren@kumari.net>
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck:
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
Cc: "idr@ietf.org" <idr@ietf.org>
Subject: Re: [Idr] Accept draft-wkumari-idr-as0-01.txt ?
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: Mon, 14 Nov 2011 01:48:09 -0000

Warren,

Wouldn't this be a DoS attack vector if the attacker originates a valid prefix with ASN0?

It wouldn't be a global attack, but it may generate some local black holes for the victim, is it?

Regards,
-as




On 27 Oct 2011, at 11:29, Warren Kumari <warren@kumari.net> wrote:

> Hello IDRites,
> 
> I would like to draw your attention to draft-wkumari-idr-as0-01.txt  ( http://tools.ietf.org/html/draft-wkumari-idr-as0-01 ) - I am asking that this draft be considered for WG adoption.
> 
> 
> I have already received some feedback, mainly suggesting:
> 
> - Add a text for AS number 0 as a reserved in Aggregator and AS4
> Aggregator attribute
> 
> - Add text for AS number 0 as a reserved value in communities and
> extended communities. (RFC 1997 and Four-octet AS Specific Extended
> Communities)
> 
> Also suggested was providing a little more information on what to do it you do receive a route containing AS0  (more descriptive than just "MUST NOT accept" (for example, stating that it should be "excluded from the Phase 2 decision function")).
> 
> Anyway, I would value your feedback and input.
> 
> W
> 
> 
> 
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr