Re: [Idr] I-D Action: draft-ietf-idr-as-migration-04.txt

Juan Alcaide <jalcaide@cisco.com> Mon, 20 April 2015 20:21 UTC

Return-Path: <jalcaide@cisco.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 B14AA1B3079 for <idr@ietfa.amsl.com>; Mon, 20 Apr 2015 13:21:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 9QZzvKmRlrlH for <idr@ietfa.amsl.com>; Mon, 20 Apr 2015 13:21:47 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE1E51B3070 for <idr@ietf.org>; Mon, 20 Apr 2015 13:21:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4077; q=dns/txt; s=iport; t=1429561301; x=1430770901; h=date:from:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=xrPAXk+SAuX9CJ5b/4WmvimLmIEJOuJ7y+ID293OCbM=; b=LlZ5yq1p72+OJZBTBcUeGFTyoP1ASrcoUWMt7F8t8kOyvRSf6OZTIhfD orUqidPH2+tZETJnpUYNW94Cd2R7kA/nG91oxgShsMC5zpjFkd6oPo+mb BXSSZiGR62ADQjWu0BBYgVN2cB6yEDEPGVM5ou7XUp7Z9WgUyPXSGlHJP 0=;
X-IronPort-AV: E=Sophos;i="5.11,610,1422921600"; d="scan'208";a="413421478"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by rcdn-iport-4.cisco.com with ESMTP; 20 Apr 2015 20:21:40 +0000
Received: from clubhouse-1.cisco.com (clubhouse-1.cisco.com [64.100.21.13]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id t3KKLdxn005011 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 20 Apr 2015 20:21:40 GMT
Date: Mon, 20 Apr 2015 16:21:38 -0400 (EDT)
From: Juan Alcaide <jalcaide@cisco.com>
To: "UTTARO, JAMES" <ju1738@att.com>
In-Reply-To: <B17A6910EEDD1F45980687268941550F0CB90981@MISOUT7MSGUSRCD.ITServices.sbc.com>
Message-ID: <alpine.GSO.2.00.1504201548460.29478@clubhouse-1.cisco.com>
References: <20150409140218.22830.31521.idtracker@ietfa.amsl.com> <D14BFEEA.4CC52%wesley.george@twcable.com> <02e401d072e4$4f5a1cc0$ee0e5640$@ndzh.com> <D14C3347.A438A%aretana@cisco.com> <alpine.GSO.2.00.1504161723090.17655@clubhouse-1.cisco.com> <001f01d07b3f$13ee12f0$3bca38d0$@ndzh.com> <B17A6910EEDD1F45980687268941550F0CB90981@MISOUT7MSGUSRCD.ITServices.sbc.com>
User-Agent: Alpine 2.00 (GSO 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-1691952160-1429561299=:29478"
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/lkt5cGaLWazpyuJX8A4s0DcAuSM>
Cc: "'jgralak@juniper.net'" <jgralak@juniper.net>, 'Susan Hares' <shares@ndzh.com>, "'idr@ietf.org'" <idr@ietf.org>
Subject: Re: [Idr] I-D Action: draft-ietf-idr-as-migration-04.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: Mon, 20 Apr 2015 20:21:48 -0000

Hi,

(on PTO with limitted internet access)

Possible updates:

- As we discussed, for ebgp incomming updates for local-as it makes more 
sense to prepend AS on incomming updates. I think we shoudl describe this 
option as the default one and any other one as a variation.

- Cisco plans to implement the internal BGP alias as ibgp local-as 
dual-as. So perhaps we can choose an agnostic name and explain both 
Juniper and Cisco names.

- About "the speaker SHOULD send BGP OPEN using the globally configured 
ASN first". I think we should emphasize how the FSM gets modified. It may 
be implicit, but it may save us from some interoperabilities problems. My 
ideas:

  1) In any case, my-AS and your-AS MUST be equal on any case.
  2) Define what to do if you send global-AS but you receive local-AS. 
Probably respond wiht "Bad Peer AS". But I'd like to understand what 
Juniper is doing as well.
  3) Note that without an agreement of the AS that is used first (both 
peers could decide to use first the local-as if they are both configured as 
such). This would happen in 2)

-Juan

On Mon, 20 Apr 2015, UTTARO, JAMES wrote:

> What would be great is that the features that are being used are standardized across vendors. The current approach where each implementation varies in behavior will make life difficult.
>
> Jim Uttaro
>
> -----Original Message-----
> From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares
> Sent: Monday, April 20, 2015 3:53 AM
> To: 'Juan Alcaide'; 'Alvaro Retana (aretana)'
> Cc: idr@ietf.org; jgralak@juniper.net
> Subject: Re: [Idr] I-D Action: draft-ietf-idr-as-migration-04.txt
>
> Juan:
>
> Do you think something needs to change in this draft?  This is the last day
> of the WG adoiption call.
>
> Sue
>
> -----Original Message-----
> From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Juan Alcaide
> Sent: Thursday, April 16, 2015 5:27 PM
> To: Alvaro Retana (aretana)
> Cc: idr@ietf.org; jgralak@juniper.net; Susan Hares
> Subject: Re: [Idr] I-D Action: draft-ietf-idr-as-migration-04.txt
>
> Hi,
>
> Let me chip using a previous discussion inputs.
>
> When using local-as, Cisco prepends AS on inbound updates from eBGP peers.
> I understand Juniper prepends AS on outbounds updates towards eBGP peers.
> In most cases, Cisco approach is better.
>
>>>>> Consider
>>>>>
>>>>> R1 (AS1) ----(local-as 2) R2(AS3)--- R3(AS3) --- R4 (AS4)
>>>>>          ebgp                    iBGP
>>>>>
>>>>> Cisco:
>>>>>
>>>>> R1: X
>>>>> R2: 2 X
>>>>> R3: 2 X
>>>>> R4: 3 2 X
>>>>>
>>>>> Juniper
>>>>>
>>>>> R1: X
>>>>> R2: X
>>>>> R3: 2 X
>>>>> R4: 3 2 X
>>>>>
>>>>> I think it's prefereable that R2 and R3 have the same AS-PATH.
> Otherwise
>>>>> you can have inconsistent best-path decission inside AS3
>
>
>
> -Juan
>
> On Thu, 9 Apr 2015, Alvaro Retana (aretana) wrote:
>
>> On 4/9/15, 12:43 PM, "Susan Hares" <shares@ndzh.com> wrote:
>>
>>> Let me review the document and query Alvaro to make sure it addresses
>>> his concerns.
>>>
>>> On re-doing WG LC, we can do this in parallel with the other reviews
>>> I'll need to redo (security directorate, routing directorate,
>>> ops-directorate and gen-art). I'll start both sequences at the same
>>> time once I've heard from Alvaro.
>>
>> I¹ll go read it, but my gut reaction is that we should go back through
>> (WGLC, etc.).
>>
>> Thanks!
>>
>> Alvaro.
>>
>> _______________________________________________
>> Idr mailing list
>> Idr@ietf.org
>> https://www.ietf.org/mailman/listinfo/idr
>>
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>