IETF Logo Mail Archive

Re: [Idr] draft-xie-idr-bgpls-sr-vtn-mt-03.txt - Call for WG adoption: 12/18/2021 to 1/7/2022

Stefano Previdi <stefano@previdi.net> Fri, 07 January 2022 09:32 UTC

Return-Path: <stefano@previdi.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 10EC53A17DB for <idr@ietfa.amsl.com>; Fri, 7 Jan 2022 01:32:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=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=previdi-net.20210112.gappssmtp.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 t8fv7euoiRFn for <idr@ietfa.amsl.com>; Fri, 7 Jan 2022 01:32:48 -0800 (PST)
Received: from mail-ed1-x534.google.com (mail-ed1-x534.google.com [IPv6:2a00:1450:4864:20::534]) (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 483AF3A17DA for <idr@ietf.org>; Fri, 7 Jan 2022 01:32:48 -0800 (PST)
Received: by mail-ed1-x534.google.com with SMTP id k15so19691357edk.13 for <idr@ietf.org>; Fri, 07 Jan 2022 01:32:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=previdi-net.20210112.gappssmtp.com; s=20210112; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=0xWETDXw/h9Wp+u8m9rIvQpLZuOjT2bUsp3G0zZ0sbY=; b=2tO5CC+dUEPS5lRxJGPyXcEEbOWMlguiPW18Wu2EaPzpLeJnTBjDqYc3ttiJqkMOAl g6o01GaicXqjJ0OyzLXJgh04VQ82fn9M1Ye3x3oPv4r+hs+pSPEuFRA4XuL+107Xgn4Y XVHBMqMEi7tzvCPlS1hITN3gt+zwaUolWTVbqFISvSnRokBjsJUQ3T1f9UPwulKUZ/If all7AdVHx8mY3FMbmJcI7Nh79F+Eh2iQtJQXBm3LV0eghL1+au214gHeTKLX+nG7A0Ku kYmO/xGhz32zl05X+gAlPl1GhvCCvsksVyfUv9E5dg0uySqjc45zT0c6+rguMxPVLfKW hdPQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=0xWETDXw/h9Wp+u8m9rIvQpLZuOjT2bUsp3G0zZ0sbY=; b=1kYf6sBOTkqmnyWwhdOtYBv8c/lqmB6I1i/GTou2ZR2DL9UWSsIJU9uqZdN6G74KNr DV/BcYVoj5N9J4656jQ8aDCp/zlV+c84a+AmiJlVu7FKNBG+7x6vFVpQrUYcNhrpK/YK i3O5gu2Ze7/mR3nRjCIEe9kmCipWPnOOT6fVtDHjxECjlBzeioPjI8kTpcecdLJL7KgY P4ln6JejG6Z/yUx0zfXEn9hq9V70HJkHiwXpLjsqhteRlzUq/chx5+YD42QimUamj4/G m5kqSmHT7ZpGpzUeDaqkZYs0l2Qa+K+yiNLNV6ph5dHOtgrHkIwVUd4cgkMAInMBvMLo NORw==
X-Gm-Message-State: AOAM533FoOVeXf+nAv/Tue5XpcLuoc2+fLpJouVjGyvUMVrrZbJhg5Mv mFdF7Tv5ZLOwM+b+rlFSScz9+qCSXbhi3A==
X-Google-Smtp-Source: ABdhPJwqr8S7Ucct7gRNm6VPqQDqeOFxGYxFg0M6Wc16eN6CYgqRbrkQrK2vtPz9GB+megLeZaaq8g==
X-Received: by 2002:a17:907:c14:: with SMTP id ga20mr7917137ejc.521.1641547964675; Fri, 07 Jan 2022 01:32:44 -0800 (PST)
Received: from pc.home (host-87-6-178-211.retail.telecomitalia.it. [87.6.178.211]) by smtp.gmail.com with ESMTPSA id 18sm1231526ejw.187.2022.01.07.01.32.44 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 07 Jan 2022 01:32:44 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.6\))
From: Stefano Previdi <stefano@previdi.net>
In-Reply-To: <009501d7f42c$e1bcbca0$a53635e0$@ndzh.com>
Date: Fri, 07 Jan 2022 10:32:42 +0100
Cc: idr wg <idr@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <37760B32-CBDA-422B-B941-EB9748552EDF@previdi.net>
References: <009501d7f42c$e1bcbca0$a53635e0$@ndzh.com>
To: Susan Hares <shares@ndzh.com>
X-Mailer: Apple Mail (2.3608.120.23.2.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/YtQlscXWNUER7usTIN0G7G6hRyA>
Subject: Re: [Idr] draft-xie-idr-bgpls-sr-vtn-mt-03.txt - Call for WG adoption: 12/18/2021 to 1/7/2022
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 07 Jan 2022 09:32:53 -0000

Hi,

I’ve read the draft. The proposal to use existing BGP-LS (igp-derived) TLVs in order to advertise information related to the VTN and its resources makes sense to me.

I support the adoption of the document. 

Thanks.
s.


> On Dec 18, 2021, at 5:32 PM, Susan Hares <shares@ndzh.com> wrote:
> 
> This begins a WG Adoption call for draft-xie-idr-bgpls-sr-vtn-mt-03.txt from 12/18 2021 to 1/7/2022.  The longer period is due to the Holiday/New Year time period. 
>  
> The draft can be found at: 
> https://datatracker.ietf.org/doc/draft-xie-idr-bgpls-sr-vtn-mt/
>  
> While reviewing the document consider the following questions: 
>  
> 1)  Does this informational draft aid operation of 5G networks for new applications? 
>  
> New 5G services require stringent  performance requirements for applications.  This information draft describes how to use existing segment routing (SR) 
> mechanisms to allow a centralized control to allocate a set of  virtual transport networks (VTNs) which are resource aware.  Isolation between resources for multi-AS transport may be necessary to protect the application. 
>  
> Intra-domain:  
> a) Uses MT-ID which identifies 1 or more ISIS/OSPF topologies.
> [drafts referenced:  draft-ietf-idr-rfc7752bis, draft-ietf-idr-bgp-ls-segment-routing-ext,  draft-ietf-idr-bgpls-srv6-ext] 
> b) New VTN-ID which specifies resources associated with each VTN
> [draft referenced: draft-ietf-lsr-isis-sr-vtn-mt] 
>  
> Inter-Domain mechanisms used include: 
> a) Isolation of certain VTNs to specific inter-domain links or BGP peers,  
> b) consistent use of MT-ID across multiple domains or use of VTN-ID TLV 
>  
> VTN-ID TLV is a bgp-ls TLV that specifies unique set of resources per VTN.  
>  
> [existing WG drafts referenced: draft-ietf-idr-bgpls-segment-routing-epe, draft-ietf-idr-bgpls-srv6-ext, draft-ietf-idr-rfc7752bis] 
> New drafts referenced: draft-dong-idr-bgpls-sr-enhanced-vpn-03.txt] 
>  
> 2) Should IDR recommend the global VTN-ID? 
>  
> The MT-ID is not an IANA registered named space.  VTN-ID is proposed as a global name space, but does not have any proposed IANA registry text.  Should VTN-ID become a register global name space that identifies a set of MT-IDs and other resources?  
>  
> Cheers, Sue 
>  
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr

v2.23.0 | Report a Bug | By Email