Re: [Idr] Questions to draft-hujun-idr-bgp-ipsec-01
Linda Dunbar <linda.dunbar@futurewei.com> Mon, 18 November 2019 01:13 UTC
Return-Path: <linda.dunbar@futurewei.com>
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 4EC061207FD for <idr@ietfa.amsl.com>; Sun, 17 Nov 2019 17:13:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.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 Tr-DesBCLqMq for <idr@ietfa.amsl.com>; Sun, 17 Nov 2019 17:13:28 -0800 (PST)
Received: from NAM03-DM3-obe.outbound.protection.outlook.com (mail-eopbgr800121.outbound.protection.outlook.com [40.107.80.121]) (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 2ECCA120831 for <idr@ietf.org>; Sun, 17 Nov 2019 17:13:28 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Sr2BHrI4Td8959ctwEKhSuGgXQl0RzQRdoZ30iHjFs5004YNtNWxbi8g0RuFVYU1kcag0PLRfQbl76outur78Ux9MgNXWOiO/9lLI9mYRxrM2K4OjEwKfVOr3jj8Rpl0YejanhJ1LkEM7QtoSRxUWqVlxfwBOyRHvwjQgfdRXkOwIOs2G9LHnco4/Fl9pbKpOwRJ/8sstDV/1DtNZ+5svyvp9p1NDRW+v4Uxb4JLu739GqVFUz7OY8GSNVbdoHr6dodTanrvnPNTKDube76Sihk4/tecUENX5K7UcJkLrzriey4M0Xmw2NiEJPSNi1iYh4L9KoSMiMMBqFWFHbe4PA==
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=WqYAsGLDAhWk19hgG6HNlj3lltrRLvqHGR/JNjmli6E=; b=JyjcAOoue9f60t/Mo4S+xpUEVJqRe9I3H38ekbbddP9fuyM1mCfl5FB4hRskv4uAjeaaSQ940qwb5KxCfn/H/5kt/hpqowgjiHzAAlI3Q2EhbnaULYZkSUPgRvGPo44O/mf9H2uq1sGGJLMvjv3xpnx4blnBBsHDdMyKE2cKvPzYnUqlaY9jT7A/nO3ZCLhN6ybluw+nUV0iAU+AIZKbRcJcA6cARxW5/qE7kKEkAgp6w1kjr1AFNbP2vz0k5UnJePr4OP3GWwbG8vgKY/4Cu8s2lq/l4GIwOjy8wUYQt2eOuBZL4qKdyjwCBL9bNg9ZVNYTa3xgExQhVmZcA8R1uQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=futurewei.com; dmarc=pass action=none header.from=futurewei.com; dkim=pass header.d=futurewei.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=WqYAsGLDAhWk19hgG6HNlj3lltrRLvqHGR/JNjmli6E=; b=ivhCZFd6mBKXpz/+S6lt/97F+ZgaTmXr4jCg3v+e5WWQnLV1HAvEpVewfdr1f3H+t2hwKfG+nsx0mmhN1/n4AVcnJAq7TqH/0WHYK1j5JrPyiw4OW27439o42zDjFIjYEBmDcUS5/CBIjuqG2Zk1w1hXPZg2lrwVdUKC9umqh/4=
Received: from BN8PR13MB2628.namprd13.prod.outlook.com (20.178.219.10) by BN8PR13MB2660.namprd13.prod.outlook.com (20.178.219.91) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2474.10; Mon, 18 Nov 2019 01:13:24 +0000
Received: from BN8PR13MB2628.namprd13.prod.outlook.com ([fe80::a89e:acd9:3ed9:998d]) by BN8PR13MB2628.namprd13.prod.outlook.com ([fe80::a89e:acd9:3ed9:998d%6]) with mapi id 15.20.2474.012; Mon, 18 Nov 2019 01:13:23 +0000
From: Linda Dunbar <linda.dunbar@futurewei.com>
To: "Hu, Jun (Nokia - US/Mountain View)" <jun.hu@nokia.com>, "idr@ietf.org" <idr@ietf.org>
CC: 'Paul Wouters' <paul@nohats.ca>, 'Benjamin Kaduk' <kaduk@mit.edu>, Susan Hares <shares@ndzh.com>
Thread-Topic: [Idr] Questions to draft-hujun-idr-bgp-ipsec-01
Thread-Index: AdWdq4agBSHNADxdRYaohM9zMtNHXQ==
Date: Mon, 18 Nov 2019 01:13:23 +0000
Message-ID: <BN8PR13MB2628920F76CEC28231169333854D0@BN8PR13MB2628.namprd13.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=linda.dunbar@futurewei.com;
x-originating-ip: [31.133.157.149]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 8d8433ba-878f-4ccc-a3c6-08d76bc48225
x-ms-traffictypediagnostic: BN8PR13MB2660:
x-microsoft-antispam-prvs: <BN8PR13MB266018FF61BC3F170A36334F854D0@BN8PR13MB2660.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0225B0D5BC
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(396003)(346002)(376002)(366004)(39840400004)(136003)(189003)(199004)(13464003)(606006)(52536014)(66946007)(33656002)(8676002)(25786009)(66066001)(45080400002)(64756008)(66556008)(66476007)(66446008)(2906002)(81156014)(81166006)(229853002)(8936002)(71190400001)(71200400001)(236005)(9686003)(54896002)(6306002)(55016002)(66574012)(6246003)(44832011)(6436002)(476003)(486006)(7696005)(6506007)(186003)(3846002)(6116002)(5660300002)(790700001)(966005)(53546011)(26005)(102836004)(478600001)(256004)(5024004)(14444005)(74316002)(4326008)(7736002)(14454004)(4001150100001)(296002)(76116006)(86362001)(316002)(54906003)(110136005)(99286004)(2501003); DIR:OUT; SFP:1102; SCL:1; SRVR:BN8PR13MB2660; H:BN8PR13MB2628.namprd13.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: futurewei.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 0d33gt0ZZzn5gfZYSdICSmaBSF4AT45UWvu5pvMuG7sWsZAgPTzcLuVHi39tR/hSuxpXX5t/z/7JZ2ewUHHHVK2YsDrBdO7HlaTk9pHr6velxCHnLRk0SNnFu7G8rJlHiG9SkaNKevVsP6YqcCBrcsWjiXSGBzNuIQEAdvAuwBTWUPkHm0zOSPuAfEX4E/FEtp+tr3i4zYn9g+88XQm7SvrMLlnibzucrUCb0WVbUCEcdbJaRoOTXoxolPJUCHzH/B39ISh0GbH8buLsWYySO1gJQSh330aCqFzHe2v5tUil8f1RD1B5/PozEnbeNYOEEK2DezY2CxfiRmb5sugx/LSJw9EmcKQjvhrnofKFXVZhquBEkxlzbuBPv0VhIlynnUikdxf908MRLk60t3jxFurCYkRQ+u9EzM8QE2yObhjomp6w9gTlDg4ya6+jxGlG
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_BN8PR13MB2628920F76CEC28231169333854D0BN8PR13MB2628namp_"
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 8d8433ba-878f-4ccc-a3c6-08d76bc48225
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Nov 2019 01:13:23.2774 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: QtByUn8ixFckc0+522ylcH8+ohe7bxBEtGF73IFimAIkb/wUX22t1jUGHq8YgV9J67Ue7BpCsokKiY9i0/WxSw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN8PR13MB2660
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/FJChwqSmu5bHUtFGCmbTFf2xJ_0>
Subject: Re: [Idr] Questions to draft-hujun-idr-bgp-ipsec-01
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: Mon, 18 Nov 2019 01:13:32 -0000
Jun, Thank you very much for the answers. Yes, the questions are to draft-hujun-idr-bgp-ipsec-01. Here are more questions: * If I want to find the least set of information for a node to propagate for IPsec tunnels to a set of nodes, can I use "Next Hop" field in the MP-NLRI for the Local Tunnel Endpoint? So the Tunnel-Encap Path Attribute doesn't have to include the "Local Tunnel Endpoint Address" subTLV * What is the difference between "Private Routing Instance" and "Child SA Traffic" selection? Can they be the same? * Can the "Private Routing Instance" be listed as Routes in the MP-NLRI Path Attribute? * Under what circumstance that you will need "Public routing instance"? especially, for a network with set of CPEs in one customer AS running as Overlay and the routing instance is locally significant to the Customer domain. Thank you. Linda From: Hu, Jun (Nokia - US/Mountain View) <jun.hu@nokia.com> Sent: Monday, November 18, 2019 8:13 AM To: Linda Dunbar <linda.dunbar@futurewei.com>; idr@ietf.org Cc: 'Paul Wouters' <paul@nohats.ca>; 'Benjamin Kaduk' <kaduk@mit.edu>; Susan Hares <shares@ndzh.com> Subject: RE: [Idr] Questions to draft-hujun-idr-bgp-ipsec-transport-mode-00.txt Hi Linda, I assume your questions are really about draft-hujun-idr-bgp-ipsec-01? since draft-hujun-idr-bgp-ipsec-transport-mode-00 doesn't have figure 4; "Figure 4: does R1 use Subnet A in NLRI? And have Tunnel-Encap with more detailed description on SubnetA<->SubnetB & SubnetA<->Subnet C? " Yes, R1 will advertise subnet-A in NLRI; not sure I understand your 2nd part of the question, but section 2.1 of draft-hujun-idr-bgp-ipsec-01 defines local/remote prefix sub-TLV (NLRI could be used for local prefix) "How does R1 need to know that Subnet A and Subnet B needs to communicate ahead of time? " This depends on use case, in this example, both R1 and R2 belong to same admin domain, so this kind of thing could be planned ahead; in other use case, if the remote prefix is not known or user want same Ipsec config for all remote prefix, then an all-zero prefix could be used in remote prefix sub-TLV "In addition, if the network has 4 routers, R1, R2, R3 and R4. Does the Update from R1 include all the <Local- Remote> pairs in each single UPDATE? i.e. when R1 sends out the UPDATE for the Subnet A attached to R1, the UPDATE from R1 has to include Local subnet A <-> remote subnet B on R2 Local subnet A <-> remote subnet D on R3 Local subnet A <-> remote subnet F on R4 Is it correct? If there are 100 nodes in the network, the UPDATE message has to include 100 pairs? " As explained above, it could be done this way, but not necessary; it really depends on granularity user case needs From: Linda Dunbar <linda.dunbar@futurewei.com<mailto:linda.dunbar@futurewei.com>> Sent: Sunday, November 17, 2019 8:52 PM To: Linda Dunbar <linda.dunbar@futurewei.com<mailto:linda.dunbar@futurewei.com>>; Hu, Jun (Nokia - US/Mountain View) <jun.hu@nokia.com<mailto:jun.hu@nokia.com>>; idr@ietf.org<mailto:idr@ietf.org> Cc: 'Paul Wouters' <paul@nohats.ca<mailto:paul@nohats.ca>>; 'Benjamin Kaduk' <kaduk@mit.edu<mailto:kaduk@mit.edu>>; Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>> Subject: RE: [Idr] Questions to draft-hujun-idr-bgp-ipsec-transport-mode-00.txt Jun, In addition, if the network has 4 routers, R1, R2, R3 and R4. Does the Update from R1 include all the <Local- Remote> pairs in each single UPDATE? i.e. when R1 sends out the UPDATE for the Subnet A attached to R1, the UPDATE from R1 has to include Local subnet A <-> remote subnet B on R2 Local subnet A <-> remote subnet D on R3 Local subnet A <-> remote subnet F on R4 Is it correct? If there are 100 nodes in the network, the UPDATE message has to include 100 pairs? Linda -----Original Message----- From: Idr <idr-bounces@ietf.org<mailto:idr-bounces@ietf.org>> On Behalf Of Linda Dunbar Sent: Sunday, November 17, 2019 8:32 PM To: Hu, Jun (Nokia - US/Mountain View) <jun.hu@nokia.com<mailto:jun.hu@nokia.com>>; idr@ietf.org<mailto:idr@ietf.org> Cc: 'Paul Wouters' <paul@nohats.ca<mailto:paul@nohats.ca>>; 'Benjamin Kaduk' <kaduk@mit.edu<mailto:kaduk@mit.edu>>; Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>> Subject: [Idr] Questions to draft-hujun-idr-bgp-ipsec-transport-mode-00.txt Jun, I have some questions on your draft: Figure 4: does R1 use Subnet A in NLRI? And have Tunnel-Encap with more detailed description on SubnetA<->SubnetB & SubnetA<->Subnet C? How does R1 need to know that Subnet A and Subnet B needs to communicate ahead of time? Linda -----Original Message----- From: Idr <idr-bounces@ietf.org<mailto:idr-bounces@ietf.org>> On Behalf Of Hu, Jun (Nokia - US/Mountain View) Sent: Friday, October 11, 2019 6:46 AM To: idr@ietf.org<mailto:idr@ietf.org> Cc: 'Paul Wouters' <paul@nohats.ca<mailto:paul@nohats.ca>>; 'Benjamin Kaduk' <kaduk@mit.edu<mailto:kaduk@mit.edu>>; Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>> Subject: [Idr] FW: New Version Notification for draft-hujun-idr-bgp-ipsec-transport-mode-00.txt Hi, Here is a new draft for using BGP to provision IPsec transport mode protected tunnel config; this draft is in companion with draft-hujun-idr-bgp-ipsec-01 (Ipsec tunnel mode) to provide a complete solution of using BGP provision IPsec config. Review and comment will be appreciated. -----Original Message----- From: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>> Sent: Thursday, October 10, 2019 3:41 PM To: Hu, Jun (Nokia - US/Mountain View) <jun.hu@nokia.com<mailto:jun.hu@nokia.com>>; Hu, Jun (Nokia - US/Mountain View) <jun.hu@nokia.com<mailto:jun.hu@nokia.com>> Subject: New Version Notification for draft-hujun-idr-bgp-ipsec-transport-mode-00.txt A new version of I-D, draft-hujun-idr-bgp-ipsec-transport-mode-00.txt has been successfully submitted by Hu Jun and posted to the IETF repository. Name: draft-hujun-idr-bgp-ipsec-transport-mode Revision: 00 Title: BGP Provisioned IPsec Transport Mode Protected Tunnel Configuration Document date: 2019-10-10 Group: Individual Submission Pages: 7 URL: https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Finternet-drafts%2Fdraft-hujun-idr-bgp-ipsec-transport-mode-00.txt&data=02%7C01%7Clinda.dunbar%40futurewei.com%7Cdb93469d32784754e52008d76b5a3300%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637095907488703369&sdata=L%2Bq8Gmm6svj7vUgwQqWCHqx6ex2MefKRN1U58vFwJ%2Fg%3D&reserved=0<https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Finternet-drafts%2Fdraft-hujun-idr-bgp-ipsec-transport-mode-00.txt&data=02%7C01%7Clinda.dunbar%40futurewei.com%7C4bd1f219e66a4162ea8108d76bbc11c9%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637096327822610357&sdata=eOAU9X%2FzfcMoahs%2FotSsufznlK5uN%2FfnurGcGc7aVcg%3D&reserved=0> Status: https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-hujun-idr-bgp-ipsec-transport-mode%2F&data=02%7C01%7Clinda.dunbar%40futurewei.com%7Cdb93469d32784754e52008d76b5a3300%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637095907488703369&sdata=fdGi7esvdmdejiZQ6s1ZjAauLjdtzETi4BXAC8664Ss%3D&reserved=0<https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-hujun-idr-bgp-ipsec-transport-mode%2F&data=02%7C01%7Clinda.dunbar%40futurewei.com%7C4bd1f219e66a4162ea8108d76bbc11c9%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637096327822610357&sdata=Q%2B7xt%2B2fKBKCUEogNk4FRCprASbiasTwo8UPoJaE6%2FA%3D&reserved=0> Htmlized: https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-hujun-idr-bgp-ipsec-transport-mode-00&data=02%7C01%7Clinda.dunbar%40futurewei.com%7Cdb93469d32784754e52008d76b5a3300%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637095907488703369&sdata=5GCI9uiTuLRbdNSvjT48mpbe1IxTWT8sXPm6qzkRaIE%3D&reserved=0<https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-hujun-idr-bgp-ipsec-transport-mode-00&data=02%7C01%7Clinda.dunbar%40futurewei.com%7C4bd1f219e66a4162ea8108d76bbc11c9%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637096327822620352&sdata=9jeVZbLjEcC1gVDv5yxTAd9Ygi4ao9hi5GT2zeaAqco%3D&reserved=0> Htmlized: https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-hujun-idr-bgp-ipsec-transport-mode&data=02%7C01%7Clinda.dunbar%40futurewei.com%7Cdb93469d32784754e52008d76b5a3300%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637095907488713364&sdata=G3azT0TBfD9NmSvJ%2B%2BBaNCA70SFMM%2BEqrvX2IjTIef8%3D&reserved=0<https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-hujun-idr-bgp-ipsec-transport-mode&data=02%7C01%7Clinda.dunbar%40futurewei.com%7C4bd1f219e66a4162ea8108d76bbc11c9%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637096327822620352&sdata=Ngxrm2VPjxe%2FuFVjOmmfyb%2BO1m6wfrAktnXqZE8vtp8%3D&reserved=0> Abstract: This document defines a method of using BGP to advertise IPsec transport mode protected tunnel (like GRE tunnel with IPsec transport mode protection) configuration along with NLRI, based on [I-D.ietf-idr-tunnel-encaps] and [I-D.hujun-idr-bgp-ipsec]. 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. The IETF Secretariat _______________________________________________ Idr mailing list Idr@ietf.org<mailto:Idr@ietf.org> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fidr&data=02%7C01%7Clinda.dunbar%40futurewei.com%7Cdb93469d32784754e52008d76b5a3300%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637095907488713364&sdata=5lz3DyKGqJb2asfcfarFXUtZptUy1XpsnAMsv6Rycic%3D&reserved=0<https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fidr&data=02%7C01%7Clinda.dunbar%40futurewei.com%7C4bd1f219e66a4162ea8108d76bbc11c9%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637096327822630345&sdata=15nN9cU3KVLHUlU1OtYTBuiowhTuAIDyrohCrCQJgRs%3D&reserved=0> _______________________________________________ Idr mailing list Idr@ietf.org<mailto:Idr@ietf.org> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fidr&data=02%7C01%7Clinda.dunbar%40futurewei.com%7Cdb93469d32784754e52008d76b5a3300%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637095907488713364&sdata=5lz3DyKGqJb2asfcfarFXUtZptUy1XpsnAMsv6Rycic%3D&reserved=0<https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fidr&data=02%7C01%7Clinda.dunbar%40futurewei.com%7C4bd1f219e66a4162ea8108d76bbc11c9%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637096327822630345&sdata=15nN9cU3KVLHUlU1OtYTBuiowhTuAIDyrohCrCQJgRs%3D&reserved=0>
- Re: [Idr] Questions to draft-hujun-idr-bgp-ipsec-… Linda Dunbar
- Re: [Idr] Questions to draft-hujun-idr-bgp-ipsec-… Hu, Jun (Nokia - US/Mountain View)