Re: [OPSAWG] draft-ietf-opsawg-l3sm-l3nm
Qin Wu <bill.wu@huawei.com> Thu, 07 November 2019 13:40 UTC
Return-Path: <bill.wu@huawei.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 0538012084A for <opsawg@ietfa.amsl.com>; Thu, 7 Nov 2019 05:40:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 bBAYqRn6mn1i for <opsawg@ietfa.amsl.com>; Thu, 7 Nov 2019 05:40:54 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 81BB612083F for <opsawg@ietf.org>; Thu, 7 Nov 2019 05:40:54 -0800 (PST)
Received: from lhreml702-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 625808B1B5C3EDDBEB7A; Thu, 7 Nov 2019 13:40:52 +0000 (GMT)
Received: from DGGEML422-HUB.china.huawei.com (10.1.199.39) by lhreml702-cah.china.huawei.com (10.201.108.43) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 7 Nov 2019 13:40:51 +0000
Received: from DGGEML531-MBS.china.huawei.com ([169.254.5.209]) by dggeml422-hub.china.huawei.com ([10.1.199.39]) with mapi id 14.03.0439.000; Thu, 7 Nov 2019 21:40:49 +0800
From: Qin Wu <bill.wu@huawei.com>
To: SAMIER BARGUIL GIRALDO <samier.barguilgiraldo.ext@telefonica.com>, Erez Segev <Erez.Segev@ecitele.com>, "slitkows.ietf@gmail.com" <slitkows.ietf@gmail.com>, "alejandro.aguado_martin@nokia.com" <alejandro.aguado_martin@nokia.com>, Oscar González de Dios <oscar.gonzalezdedios@telefonica.com>, Victor Lopez <victor.lopezalvarez@telefonica.com>, "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: [OPSAWG] draft-ietf-opsawg-l3sm-l3nm
Thread-Index: AdWVcNw4FPF/WG8ZT+u2J35tUTLfnA==
Date: Thu, 07 Nov 2019 13:40:48 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABAA93EE405@dggeml531-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.134.31.203]
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABAA93EE405dggeml531mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/fH0UqrFYcS4TYdGSfsbxDH5BMDo>
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, 07 Nov 2019 13:40:57 -0000
2.Allow several BGP sessions under the same Network Access. To support several Routing Protocols sessions under the same Network Access we have changed the Key to have an ID to allow several protocols under the same Network Access: | | +--rw routing-protocol* [id] | | +--rw id string | | +--rw type? identityref | | +--rw routing-profiles* [id] | | | +--rw id -> /l3vpn-ntw/vpn-profiles/valid-provider-identifiers/routing-profile-identifier/id | | | +--rw type? ie-type | | +--rw ospf {rtg-ospf}? | | | +--rw address-family* address-family | | | +--rw area-address yang:dotted-quad | | | +--rw metric? uint16 | | | +--rw mtu? uint16 | | | +--rw security | | | | +--rw auth-key? string | | | +--rw sham-links {rtg-ospf-sham-link}? | | | +--rw sham-link* [target-site] | | | +--rw target-site svc-id | | | +--rw metric? uint16 | | +--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 | | +--rw static | | | +--rw cascaded-lan-prefixes | | | +--rw ipv4-lan-prefixes* [lan next-hop] {ipv4}? | | | | +--rw lan inet:ipv4-prefix | | | | +--rw lan-tag? string | | | | +--rw next-hop inet:ipv4-address | | | +--rw ipv6-lan-prefixes* [lan next-hop] {ipv6}? | | | +--rw lan inet:ipv6-prefix | | | +--rw lan-tag? string | | | +--rw next-hop inet:ipv6-address | | +--rw rip {rtg-rip}? | | | +--rw address-family* address-family | | +--rw vrrp {rtg-vrrp}? | | +--rw address-family* address-family [Qin]: I think type under routing-protocol should add a new identity for routing-profiles category identity routing-profile { base routing-protocol-type; description "Identity for routing profile type."; }
- [OPSAWG] draft-ietf-opsawg-l3sm-l3nm Erez Segev
- Re: [OPSAWG] draft-ietf-opsawg-l3sm-l3nm SAMIER BARGUIL GIRALDO
- Re: [OPSAWG] draft-ietf-opsawg-l3sm-l3nm Erez Segev
- Re: [OPSAWG] draft-ietf-opsawg-l3sm-l3nm Erez Segev
- Re: [OPSAWG] draft-ietf-opsawg-l3sm-l3nm SAMIER BARGUIL GIRALDO
- Re: [OPSAWG] draft-ietf-opsawg-l3sm-l3nm slitkows.ietf
- Re: [OPSAWG] draft-ietf-opsawg-l3sm-l3nm Erez Segev
- Re: [OPSAWG] draft-ietf-opsawg-l3sm-l3nm SAMIER BARGUIL GIRALDO
- Re: [OPSAWG] draft-ietf-opsawg-l3sm-l3nm Erez Segev
- Re: [OPSAWG] draft-ietf-opsawg-l3sm-l3nm SAMIER BARGUIL GIRALDO
- Re: [OPSAWG] draft-ietf-opsawg-l3sm-l3nm Qin Wu
- Re: [OPSAWG] draft-ietf-opsawg-l3sm-l3nm Qin Wu
- Re: [OPSAWG] draft-ietf-opsawg-l3sm-l3nm SAMIER BARGUIL GIRALDO
- Re: [OPSAWG] draft-ietf-opsawg-l3sm-l3nm Qin Wu