Re: [OPSAWG] draft-ietf-opsawg-l3sm-l3nm

<slitkows.ietf@gmail.com> Thu, 31 October 2019 15:21 UTC

Return-Path: <slitkows.ietf@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E0E812081D for <opsawg@ietfa.amsl.com>; Thu, 31 Oct 2019 08:21:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 9DTxuzNvi9Ag for <opsawg@ietfa.amsl.com>; Thu, 31 Oct 2019 08:21:40 -0700 (PDT)
Received: from mail-wm1-x334.google.com (mail-wm1-x334.google.com [IPv6:2a00:1450:4864:20::334]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F53D120077 for <opsawg@ietf.org>; Thu, 31 Oct 2019 08:21:39 -0700 (PDT)
Received: by mail-wm1-x334.google.com with SMTP id c12so1798432wml.4 for <opsawg@ietf.org>; Thu, 31 Oct 2019 08:21:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :thread-index:content-language; bh=Lzanka2CtJaoH5Z/YuNnVKIACTJEiCXJxZw6hJyOmBA=; b=cQe0i+XpuZOk4Kb2LoiGLavyyTHBUQjXyIjW6bHT2PMaqI+8XtFSqLw2dT7VqgMGfk gM3JcYN61qFpWXBVd2ECqcUQHZABlr+QKk2m7nLTM607o5ChIRD4LBxuqA/TtTt3/NUd mZ1x1RpSa88qPEjHDmCAlTIw02BjxsqrWvwOkKFVyePKfa0wSogXbBU6AE5QZknoaOCl KgYJWuWZ50CwFdzNCVpVUrYj/4CJcmQvRAJ0s8R68x+Ui+9ZcRHIqEpWdqD/knMYcacY Y8LZwzQBGpeEFOx7jBxKwITgV4jNFj+5aEx/Z+nEXZFu6RE3bTs7omqCrEG+mtVFlvMK b6eA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:references:in-reply-to:subject:date :message-id:mime-version:thread-index:content-language; bh=Lzanka2CtJaoH5Z/YuNnVKIACTJEiCXJxZw6hJyOmBA=; b=qh6DsKiNUvPBwBXldEdY8tNMfmtQM+qIolCJJp9w4+AqX1GaW1/+i7k5aE3pcrk/xA LJ53rHVpnq7O8SAjNhu9y7nNnWanaI9GuXEfHFosAXcxPScMlOIMtickbWBAy6gDStJh mfh3LxrKXlgI1/b362mLSPuyEtyYc3KTdKkHIKCvhllr8i44iM7w6OzOLaOm2zFK59DZ VQZ72RpoEFjA7kQ+xTKzcLSCft7IIB75ZUV2lq1d9JjxjgJTGYc1rP73D2BkM/wR0ahx 4Rn5wLsTzS0j4EiBj7a5KXQkgmsa+OzAArwp475B4U67tB3AK8nsBJq6QQnwtXTJXhVj dZOg==
X-Gm-Message-State: APjAAAXeupZo5W+ALYfYmP9UQWmeHc6aENYmFsN2XwpRofB0rHKa9w7E +lCnqmMnP2GnKwF2gu1VAg==
X-Google-Smtp-Source: APXvYqyfCxGbosumficWGUWZHII/d8eZiDiWfTcvGxDW09wOOPfCuE4KY2YYVA1BQZ6pB3dmT5es1w==
X-Received: by 2002:a1c:5415:: with SMTP id i21mr5899208wmb.120.1572535297793; Thu, 31 Oct 2019 08:21:37 -0700 (PDT)
Received: from SLITKOWS3YYU6 ([2001:420:c0c0:1008::f1]) by smtp.gmail.com with ESMTPSA id l22sm6990155wrb.45.2019.10.31.08.21.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 31 Oct 2019 08:21:36 -0700 (PDT)
From: slitkows.ietf@gmail.com
To: 'SAMIER BARGUIL GIRALDO' <samier.barguilgiraldo.ext@telefonica.com>, 'Erez Segev' <Erez.Segev@ecitele.com>, alejandro.aguado_martin@nokia.com, 'Oscar González de Dios' <oscar.gonzalezdedios@telefonica.com>, 'Victor Lopez' <victor.lopezalvarez@telefonica.com>, opsawg@ietf.org
References: <AM0PR03MB5124297C01A7CECB4CFD9EA086630@AM0PR03MB5124.eurprd03.prod.outlook.com> <VI1PR06MB59525445FEA09FA223441704D5630@VI1PR06MB5952.eurprd06.prod.outlook.com>, <AM0PR03MB5124A38A7CFE66A7BCB57D7F86630@AM0PR03MB5124.eurprd03.prod.outlook.com> <VI1PR06MB5952B586622799E0F4A1D5F6D5630@VI1PR06MB5952.eurprd06.prod.outlook.com>
In-Reply-To: <VI1PR06MB5952B586622799E0F4A1D5F6D5630@VI1PR06MB5952.eurprd06.prod.outlook.com>
Date: Thu, 31 Oct 2019 16:21:33 +0100
Message-ID: <008901d58ffe$e1b75010$a525f030$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/related; boundary="----=_NextPart_000_008A_01D59007.4380C120"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQJ6y5H75UBx8Nn78KF9Mlt2kxOOLgLfZz89AiBg3hUCdq3LEKXusfvg
Content-Language: fr
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/1t5mC2wqhqqB_KmeJUo5mrvydgU>
Subject: Re: [OPSAWG] draft-ietf-opsawg-l3sm-l3nm
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Oct 2019 15:21:45 -0000

Hi Erez,

 

What is the exact setup that you want to achieve ?

Currently the BGP is linked to the site-network-access. If a site has multiple site-network-access on the same PE, there is no issue to get multiple BGP sessions with the current model.

What is your use case for having multiple BGP sessions on the same access ? There are two that I could think of but I prefer to hear from you first, so you are not influenced 😉


regarding the AS, why do you need the SP AS in the model (I guess you mean the ASN of the PE) ? SP knows which ASN the PE is belonging to.

 

Brgds,

 

Stephane

 

 

From: OPSAWG <opsawg-bounces@ietf.org> On Behalf Of SAMIER BARGUIL GIRALDO
Sent: jeudi 31 octobre 2019 15:23
To: Erez Segev <Erez.Segev@ecitele.com>; alejandro.aguado_martin@nokia.com; Oscar González de Dios <oscar.gonzalezdedios@telefonica.com>; Victor Lopez <victor.lopezalvarez@telefonica.com>; opsawg@ietf.org
Subject: Re: [OPSAWG] draft-ietf-opsawg-l3sm-l3nm

 

Hi Erez, 

 

After checking the model, you are right this key does not allow the configuration of several BGP sessions on the Same VPN. 

 

Regarding the AS; We have already discussed and the idea is to include it in the New Version. Thanks for your feedback. 

 

Regards,

 

Samier Barguil
Transport & IP Networks | GCTIO - Technology | CIT Centro Integrado de Transporte |

Móvil +57 311 2402952

Móvil +34 665416074

E-mail samier.barguilgiraldo.ext@telefonica.com <mailto:samier.barguilgiraldo.ext@telefonica.com> 

E-mail samier.barguil@wipro.com <mailto:samier.barguil@wipro.com> 

 

  _____  

De: Erez Segev <Erez.Segev@ecitele.com <mailto:Erez.Segev@ecitele.com> >
Enviado: jueves, 31 de octubre de 2019 8:34
Para: SAMIER BARGUIL GIRALDO <samier.barguilgiraldo.ext@telefonica.com <mailto:samier.barguilgiraldo.ext@telefonica.com> >; alejandro.aguado_martin@nokia.com <mailto:alejandro.aguado_martin@nokia.com>  <alejandro.aguado_martin@nokia.com <mailto:alejandro.aguado_martin@nokia.com> >; Oscar González de Dios <oscar.gonzalezdedios@telefonica.com <mailto:oscar.gonzalezdedios@telefonica.com> >; Victor Lopez <victor.lopezalvarez@telefonica.com <mailto:victor.lopezalvarez@telefonica.com> >; opsawg@ietf.org <mailto:opsawg@ietf.org>  <opsawg@ietf.org <mailto:opsawg@ietf.org> >
Asunto: RE: draft-ietf-opsawg-l3sm-l3nm 

 

Hi Samier,

 

In addition to my previous mail, is there’s an ability to determine the provider’s autonomous-system, in order to initiate eBPG from the customer premises to the L2VPN , I believe ths attribute should be added to vpn-node container.

 

Thanks,

Erez

 

 

From: SAMIER BARGUIL GIRALDO [mailto:samier.barguilgiraldo.ext@telefonica.com] 
Sent: Thursday, October 31, 2019 1:00 PM
To: Erez Segev <Erez.Segev@ecitele.com <mailto:Erez.Segev@ecitele.com> >; alejandro.aguado_martin@nokia.com <mailto:alejandro.aguado_martin@nokia.com> ; Oscar González de Dios <oscar.gonzalezdedios@telefonica.com <mailto:oscar.gonzalezdedios@telefonica.com> >; Victor Lopez <victor.lopezalvarez@telefonica.com <mailto:victor.lopezalvarez@telefonica.com> >; opsawg@ietf.org <mailto:opsawg@ietf.org> 
Subject: RE: draft-ietf-opsawg-l3sm-l3nm

 

Hi Erez, 

 

We have defined the routing protocols inside the Network Access as a List. So you can have several routing protocols enabled at the same time, including two or more eBGP sesions or BGP+ OSPF or OSPF+ Static Route. 

 



 

In fact we have added the multihop count to be able to support BGP connections with not directly connected peers. So in this case an static route + BGP connection is enabled. 

 

Reagards

 

Samier Barguil
Transport & IP Networks | GCTIO - Technology | CIT Centro Integrado de Transporte |

Móvil +57 311 2402952

Móvil +34 665416074

E-mail samier.barguilgiraldo.ext@telefonica.com <mailto:samier.barguilgiraldo.ext@telefonica.com> 

E-mail samier.barguil@wipro.com <mailto:samier.barguil@wipro.com> 

 

  _____  

De: OPSAWG <opsawg-bounces@ietf.org <mailto:opsawg-bounces@ietf.org> > en nombre de Erez Segev <Erez.Segev@ecitele.com <mailto:Erez.Segev@ecitele.com> >
Enviado: jueves, 31 de octubre de 2019 4:59
Para: alejandro..aguado_martin@nokia.com <mailto:alejandro.aguado_martin@nokia.com>  <alejandro.aguado_martin@nokia.com <mailto:alejandro.aguado_martin@nokia.com> >; Oscar González de Dios <oscar.gonzalezdedios@telefonica.com <mailto:oscar.gonzalezdedios@telefonica.com> >; Victor Lopez <victor.lopezalvarez@telefonica.com <mailto:victor.lopezalvarez@telefonica.com> >; opsawg@ietf.org <mailto:opsawg@ietf.org>  <opsawg@ietf.org <mailto:opsawg@ietf.org> >
Asunto: [OPSAWG] draft-ietf-opsawg-l3sm-l3nm 

 

Dear Authors of draft-ietf-opsawg-l3sm-l3nm

 

 

Question regarding eBGP , 

what if I’d like several eBGP sessions to 

-          Multiple destinations 

-          Different AS  . 

 

How do I set several eBGP sessions per site?

Where does the AS of the other side defined?

 

 

 

 

                     |     +--rw bgp {rtg-bgp}?

                     |     |  +--rw autonomous-system    uint32

                     |     |  +--rw address-family*      address-family

                     |     |  +--rw neighbor?            inet:ip-address

                     |     |  +--rw multihop?            uint8

                     |     |  +--rw security

                     |     |     +--rw auth-key?   string

 

 

 

 

 

Thanks,

Erez

 

 

 


Erez Segev


NFV&SDN System Engineer

 


T:

+972.3.9287393


M:

+972.50.7057393


E:

 <mailto:erez.segev@ecitele.com> erez.segev@ecitele.com


 

 <http://www.ecitele.com/> www.ecitele.com




 

 


___________________________________________________________________________

This e-mail message is intended for the recipient only and contains information which is 
CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have received this 
transmission in error, please inform us by e-mail, phone or fax, and then delete the original 
and all copies thereof.
___________________________________________________________________________

 

  _____  


Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição


___________________________________________________________________________

This e-mail message is intended for the recipient only and contains information which is 
CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have received this 
transmission in error, please inform us by e-mail, phone or fax, and then delete the original 
and all copies thereof.
___________________________________________________________________________

 

  _____  


Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição