Re: [Idr] draft-ietf-idr-aigp-11.txt

Thomas Mangin <thomas.mangin@exa-networks.co.uk> Thu, 21 November 2013 15:48 UTC

Return-Path: <thomas.mangin@exa-networks.co.uk>
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 64C381ADFFD; Thu, 21 Nov 2013 07:48:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 oTVFuk1X53u8; Thu, 21 Nov 2013 07:48:52 -0800 (PST)
Received: from out-9.mail.exa.net.uk (out-7.mail.exa.net.uk [82.219.4.135]) by ietfa.amsl.com (Postfix) with ESMTP id E97F21ADFF6; Thu, 21 Nov 2013 07:48:51 -0800 (PST)
Received: from smtp-3.mail.exa.net.uk (smtp-1.mail.exa.net.uk [82.219.5.1]) by out-9.mail.exa.net.uk (ExaSMTPD) with ESMTP id 5D3DBA01CA; Thu, 21 Nov 2013 15:48:44 +0000 (GMT)
Received: from [10.0.1.3] (office.exa-networks.co.uk [82.219.212.253]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp-3.mail.exa.net.uk (ExaSMTPD) with ESMTPS id 2F0D422115D; Thu, 21 Nov 2013 15:48:44 +0000 (GMT)
Content-Type: multipart/signed; boundary="Apple-Mail=_CC2A6BAE-2D48-471C-AC97-2938F900834C"; protocol="application/pgp-signature"; micalg="pgp-sha1"
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Thomas Mangin <thomas.mangin@exa-networks.co.uk>
In-Reply-To: <6307.1385048646@erosen-linux>
Date: Thu, 21 Nov 2013 15:48:43 +0000
Message-Id: <71DB2D92-4631-484E-BFBF-5E938D1D746C@exa-networks.co.uk>
References: <6307.1385048646@erosen-linux>
To: idr-bounces@ietf.org, erosen@cisco.com
X-Mailer: Apple Mail (2.1822)
X-Virus-Scanned: clamav-milter 0.97.8 at out-2-2.mail.exa.net.uk
X-Virus-Status: Clean
Cc: "idr@ietf.org wg" <idr@ietf.org>
Subject: Re: [Idr] draft-ietf-idr-aigp-11.txt
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: Thu, 21 Nov 2013 15:48:54 -0000

Hello Eric,

Following your changes, I have no more feedback (at least atm - never say never :p) on this draft.
Good luck with its progression.

Thomas

On 21 Nov 2013, at 15:44, Eric Rosen <erosen@cisco.com> wrote:

> I have revised this draft per the WG Last Call comments:
> 
> - Error handling for a malformed AIGP attribute is "discard attribute".
> 
> - An AIGP attribute with the transitive bit set is regarded to be malformed,
>  and is to be discarded.
> 
> - Stated explicitly that the AIGP value used in bestpath computations is the
>  value of the first AIGP TLV in the attribute.
> 
> - The requirement to default "AIGP_SESSION" to "enabled" on IBGP sessions
>  has been demoted from "MUST" to "SHOULD".  This reflect the fact that
>  there is some controversy about it, but no real consensus to default it to
>  "disabled".
> 
> - Stated that the AIGP value is capped at its maximum (unsigned) value,
>  i.e., it should not wrap around due to addition.
> 
>  Also stated that if an AIGP attribute is received and its value is already
>  the maximum, the attribute should be treated as malformed.  (It's not
>  really useful if you can't add to it.)
> 
> I would like to thank those of you who commented during the last call, and
> would welcome comments on the changes.
> 
> 
> 
> 
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>