Re: [bess] I-D Action: draft-ietf-bess-srv6-services-00.txt
li zhenqiang <li_zhenqiang@hotmail.com> Thu, 24 October 2019 09:54 UTC
Return-Path: <li_zhenqiang@hotmail.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F18F12007A; Thu, 24 Oct 2019 02:54:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.114
X-Spam-Level:
X-Spam-Status: No, score=-1.114 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FORGED_HOTMAIL_RCVD2=0.874, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hotmail.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 YQ8hB-akWLX9; Thu, 24 Oct 2019 02:54:41 -0700 (PDT)
Received: from APC01-HK2-obe.outbound.protection.outlook.com (mail-oln040092255086.outbound.protection.outlook.com [40.92.255.86]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69340120024; Thu, 24 Oct 2019 02:54:37 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=g51+i8TZEUt+bONwqlPPNdQVjuyK4Y+2NgQdqVPpxOcffiO4tjf33jKMNqaoX777k2cpqROjt7k/u/XhNsGUddI7NSfvYtrnVeZ067EXleIqEf2WkBovxtwJCrP3lACbzLhxIcSoeRQylRxLcURHgV1BdtLh7wRBh2j9Ij6WZYGVALlhzBw/IPGj7WxrjTXmn/eIdvfgUyPH9ygk4a0CBMkO68/GjzMSYOeCLyXDshab+dGpIW44eXl5+8b6KeG7ED2UljUjUPU0iOQyP4CrbYRyaNjsgc7KhOAc29Wf1Y5PVjgE7yQiIv+AOC7z1yAhb9OQ27llSqqSVankLQgX+g==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=sbzMwLaqhH+gcSK0v3lAIw/QbksWgg9HO58/8kqrX1k=; b=lzSvDprO5SGY/2IzK5L8VGIG5UmMDionsV/V2XFeIRZhOnHjHPeRKXRsIP0fP+xlg8CJ23VgvjlytUhnjmsMU80w1S7uJRgF8jwilwiH6769kvVMrgVmZYRKAogdaUnwVJ1ci4XDApT5ibq63B9KLix8fbs1Q23YXkoTdoMTk89iUwfTzaZC6MqAqd3k9Wk7d0Tmg4Rj+M3Hdqw4cruEWqUleT3m4TC761HOtcF2/T+Fm9DkkD9FICyXkWC9oMrt9b3c6i+pgo+rVuqC2JDGschZS9KdSZRekvGWhUr42f+Wpnr14HyPdMt/pRqSbvapLd47X4zdNdoYjD5HEU3rvQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=sbzMwLaqhH+gcSK0v3lAIw/QbksWgg9HO58/8kqrX1k=; b=ZiTowi/FOXAcZrb4lBDLw7ikokpwyc4/+HNzpVCN9FpHgaR29RZVIEicehYwJR3R03cjyAXpR+1tgoEiXotjHI4mg8szTPgic8hgpwDELv0u/qK0ZSBULuVgGxfzV1pWiupOs3WlhPxqmL3BQX5twWpPDF6IjM2JhQY5ViRl0BKhpxLielAuZYpTSbpIa1Ve4KgQi1xWr4uthWoeBkKbhhhpzJl1scU2i1nd5TSMk+qX6nMcBSywDsvwPtgruvrpoT6NEsYlLMYM/y7w2RX/nfqSbYO0ChUWMWpNui6JRidwIU09hesH2+u+t6KCIMa8zQTbx9rvVai72KJDLyDHZQ==
Received: from SG2APC01FT017.eop-APC01.prod.protection.outlook.com (10.152.250.56) by SG2APC01HT106.eop-APC01.prod.protection.outlook.com (10.152.251.110) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.2387.20; Thu, 24 Oct 2019 09:54:33 +0000
Received: from HK0PR03MB4066.apcprd03.prod.outlook.com (10.152.250.55) by SG2APC01FT017.mail.protection.outlook.com (10.152.250.203) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.2387.20 via Frontend Transport; Thu, 24 Oct 2019 09:54:33 +0000
Received: from HK0PR03MB4066.apcprd03.prod.outlook.com ([fe80::7dba:f7ea:56a0:2b70]) by HK0PR03MB4066.apcprd03.prod.outlook.com ([fe80::7dba:f7ea:56a0:2b70%3]) with mapi id 15.20.2387.021; Thu, 24 Oct 2019 09:54:33 +0000
From: li zhenqiang <li_zhenqiang@hotmail.com>
To: bess <bess@ietf.org>, draft-ietf-bess-srv6-services <draft-ietf-bess-srv6-services@ietf.org>
Thread-Topic: [bess] I-D Action: draft-ietf-bess-srv6-services-00.txt
Thread-Index: AQHVhA7A0mHICmIwhUe5w7AdpwrJhQ==
Date: Thu, 24 Oct 2019 09:54:33 +0000
Message-ID: <HK0PR03MB4066252E40175EF6AFBD5C6DFC6A0@HK0PR03MB4066.apcprd03.prod.outlook.com>
References: <157122268028.7898.5086338719399491703@ietfa.amsl.com>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: HK0PR04CA0019.apcprd04.prod.outlook.com (2603:1096:203:36::31) To HK0PR03MB4066.apcprd03.prod.outlook.com (2603:1096:203:9d::21)
x-incomingtopheadermarker: OriginalChecksum:66AEE268F4A436D44581B5B759FD6216BCBF32DA72AF768BB8F75DB39E89E927; UpperCasedChecksum:295FB1AAB3C61B2F4474FBC803875656F5F516178D5969A134128B6F38AC7E15; SizeAsReceived:7209; Count:49
x-ms-exchange-messagesentrepresentingtype: 1
x-has-attach: no
x-mailer: Foxmail 7.2.9.156[cn]
x-tmn: [Ap78eWMLzhfFvpS6iM0al+YmfGcc7bUe]
x-microsoft-original-message-id: <2019102417543624524047@hotmail.com>
x-ms-publictraffictype: Email
x-incomingheadercount: 49
x-eopattributedmessage: 0
x-ms-traffictypediagnostic: SG2APC01HT106:
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: W5rWkiQsPr5hRB8oN0Ke5UJ3JQl1a2dgjelRZV6fNQzSL37QjRoU9wMtsBkbjf8/iygCIAKrUigG01lfraRE/zUGnYoYIq/NBk774Qjo5kFG+AjZ3VJfqv6DRJwLXwcU7njtWeZ2DdqT+q+bhhS/2M2G5vKjFN13kPI8mPqafQR8/+TmiOCuCyusBBpv5hvR
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_HK0PR03MB4066252E40175EF6AFBD5C6DFC6A0HK0PR03MB4066apcp_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-Network-Message-Id: 7ca26023-fdf8-4be7-ce44-08d758682bcd
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Oct 2019 09:54:33.6852 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SG2APC01HT106
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/rrc2uvpaBs-M9cNQxbbOQ0MJpZQ>
Subject: Re: [bess] I-D Action: draft-ietf-bess-srv6-services-00.txt
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Oct 2019 09:54:43 -0000
Dear authors and all, I've read the draft with the following comments that need your clarificaton or consideration. 1. For Network Address of Next Hop in MP_REACH_NLRI, the doc says this field is IPv6 address of the egress PE, or 8 octets of RD set to 0 followed by IPv6 address of the egress PE. I want to know the IPv6 address of the egress PE can only be the IPv6 address which the egress PE uses to establish the BGP session, or it can also be the END SID of the egress PE. Would you please add a couple of sentences in the doc according to your answer to clarify this explicitly? 2. For the BGP session used to delivery the SRv6 services defined in this doc, is it only a IPv6 TCP connection, or a IPv4 TCP connection in the dual stack core network is also ok? If IPv4 BGP session is also ok, in my understanding the services carried in the BGP do not depend on the BGP session, i.e. the BGP session can be IPv4 or IPv6, so could you please find an apropriate place to state this in the doc? In this scenario, how to fill Network Address of Next Hop in MP_REACH_NLRI also needs to be specified. 3. Should we add a paragraph to specify the behavior of the ingress PE when it receives BGP update message? I think at least the following information should be included. Does the engress PE need to check the reachability of the locator since it will be used to encapsulate the traffic and it is distributed in IGP? Does BGP need to synchronize with IGP? We have to handle the situation that locator is not distributed in IGP by mistake or something. Best Regards, Zhenqiang Li ________________________________ li_zhenqiang@hotmail.com From: internet-drafts<mailto:internet-drafts@ietf.org> Date: 2019-10-16 18:44 To: i-d-announce@ietf.org<mailto:i-d-announce@ietf.org> CC: bess<mailto:bess@ietf.org> Subject: [bess] I-D Action: draft-ietf-bess-srv6-services-00.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the BGP Enabled ServiceS WG of the IETF. Title : SRv6 BGP based Overlay services Authors : Gaurav Dawra Clarence Filsfils Patrice Brissette Swadesh Agrawal Jonn Leddy Daniel Voyer Daniel Bernier Dirk Steinberg Robert Raszuk Bruno Decraene Satoru Matsushima Shunwan Zhuang Jorge Rabadan Filename : draft-ietf-bess-srv6-services-00.txt Pages : 28 Date : 2019-10-15 Abstract: This draft defines procedures and messages for SRv6-based BGP services including L3VPN, EVPN and Internet services. It builds on RFC4364 "BGP/MPLS IP Virtual Private Networks (VPNs)" and RFC7432 "BGP MPLS-Based Ethernet VPN". The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-bess-srv6-services-00 https://datatracker.ietf.org/doc/html/draft-ietf-bess-srv6-services-00 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
- [bess] I-D Action: draft-ietf-bess-srv6-services-… internet-drafts
- Re: [bess] I-D Action: draft-ietf-bess-srv6-servi… li zhenqiang