IETF Logo Mail Archive

Re: [bess] draft-zzhang-bess-mvpn-msdp-sa-interoperation-01

"Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net> Mon, 26 March 2018 18:36 UTC

Return-Path: <zzhang@juniper.net>
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 D0D001250B8 for <bess@ietfa.amsl.com>; Mon, 26 Mar 2018 11:36:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 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, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 GG3sUzih4WfG for <bess@ietfa.amsl.com>; Mon, 26 Mar 2018 11:36:54 -0700 (PDT)
Received: from mx0b-00273201.pphosted.com (mx0b-00273201.pphosted.com [67.231.152.164]) (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 7E69F126CE8 for <bess@ietf.org>; Mon, 26 Mar 2018 11:36:54 -0700 (PDT)
Received: from pps.filterd (m0108160.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w2QIUCZr006638; Mon, 26 Mar 2018 11:36:52 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : subject : date : message-id : content-type : mime-version; s=PPS1017; bh=QhfkfvwX61KeQ33EQ4/Mr5dkKq684pvZAX3WVSbrDdY=; b=SOghoo2GpKhTrMRYLS5TanNLlk88eELgMMoRmV3B1F20CJ5dD8VLBJlfmouOLBEe96QO /8wa9dV8pTIphrABSlv4kGr0+hYVPXDW5ufnAQxzUIPpBdsTIt+/mM/pS1YZcuj43F5l 16tA0MNlkFkFdEJeKGBDU494R5k8DiB2kmHphC7+Rwv5BVUzANUl0Ik0Wb8ZwYU7fJwY z/nvZfD7iCM0WiSPo3elWaB5VEGa0Nt2mvecVC7Ey/6co5vwpf+zk09oHsIpUCoNQo3z CRWrk8cEAqUObazgCVDaVZkR+nGeZFov6sR944q1asRS/CWJqbBVdbmKolupeWFQINRn 8g==
Received: from nam02-sn1-obe.outbound.protection.outlook.com (mail-sn1nam02lp0019.outbound.protection.outlook.com [216.32.180.19]) by mx0b-00273201.pphosted.com with ESMTP id 2gy2xq8d23-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 26 Mar 2018 11:36:52 -0700
Received: from BN3PR0501MB1331.namprd05.prod.outlook.com (10.160.183.20) by BN3PR0501MB1428.namprd05.prod.outlook.com (10.160.117.15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.631.5; Mon, 26 Mar 2018 18:36:50 +0000
Received: from BN3PR0501MB1331.namprd05.prod.outlook.com ([fe80::a80d:e4cf:b8b9:c67]) by BN3PR0501MB1331.namprd05.prod.outlook.com ([fe80::a80d:e4cf:b8b9:c67%9]) with mapi id 15.20.0631.009; Mon, 26 Mar 2018 18:36:50 +0000
From: "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>
To: "A, Keshava" <keshava.a@hpe.com>, "bess@ietf.org" <bess@ietf.org>
Thread-Topic: draft-zzhang-bess-mvpn-msdp-sa-interoperation-01
Thread-Index: AdPFEAgUPUVAZhwFRO2VY6xEWc/YKg==
Date: Mon, 26 Mar 2018 18:36:50 +0000
Message-ID: <BN3PR0501MB1331624574C4557E56B2F6BED4AD0@BN3PR0501MB1331.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [66.129.241.14]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN3PR0501MB1428; 7:8DeU9tSZtOZu4eBPseMxHz+2bKFiyHxugA+qokHN1i2aeMOGrZDS2PjRRFKjJy5d0pnfoUjq6Dh0OeHDO0Qcu8vMIZoDEYzB/+DQcgr9YJ6agc2gmanpQ+BYHZBuVA2Woai1R/jEX8pg1K6q95wN9SOaH41uwfehHptRAek+8bM8YIewv/tXlu0OusN93SVprPgcCsH9E/EaUuvHM7Dmi8DmR13+FyxXBqtNBP3Sjcz2ZY06xPyOWpla+muJJxtq
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: a1f284ad-8c30-4add-d6ee-08d5934889ef
x-microsoft-antispam: UriScan:(222181515654134); BCL:0; PCL:0; RULEID:(7020095)(4652020)(48565401081)(5600026)(4604075)(3008032)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:BN3PR0501MB1428;
x-ms-traffictypediagnostic: BN3PR0501MB1428:
x-microsoft-antispam-prvs: <BN3PR0501MB14289246D1C50E22EBAB495BD4AD0@BN3PR0501MB1428.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(227479698468861)(21748063052155)(222181515654134);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(3002001)(93006095)(93001095)(10201501046)(3231221)(944501327)(52105095)(6055026)(6041310)(20161123558120)(20161123562045)(20161123564045)(20161123560045)(201703131423095)(201703031522075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6072148)(201708071742011); SRVR:BN3PR0501MB1428; BCL:0; PCL:0; RULEID:; SRVR:BN3PR0501MB1428;
x-forefront-prvs: 06237E4555
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(396003)(39860400002)(376002)(39380400002)(366004)(199004)(189003)(68736007)(9326002)(186003)(99286004)(26005)(7736002)(7696005)(8936002)(102836004)(2906002)(53546011)(296002)(229853002)(106356001)(478600001)(8676002)(81166006)(81156014)(6506007)(5660300001)(316002)(3280700002)(6116002)(606006)(74316002)(97736004)(86362001)(790700001)(3846002)(2900100001)(236005)(6306002)(53946003)(25786009)(9686003)(66066001)(6246003)(33656002)(3660700001)(54896002)(55016002)(53936002)(6346003)(110136005)(14454004)(105586002)(6436002)(2501003)(476003)(5250100002)(486005)(486005)(579004); DIR:OUT; SFP:1102; SCL:1; SRVR:BN3PR0501MB1428; H:BN3PR0501MB1331.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-microsoft-antispam-message-info: dfNCvH7Zj+Gy14dmMqnJHGREQa/5KmIu4AKiVz0I31uy9tKJdjh5bqb1teAExTa/u0AzR6UqF9uR9wMXsn0d5MSwdJHqgaA65e2zT7iaHj2E7ZGsbb2z5qhHItUYN0In9ZumiapkyefykFYHw/bAz6hnpe/on2JEA5gYg9SorZtOio4no6NiO2HglvapbTN4OxkpJ8petB0vJX9tedCaTqUS8yp10GjSE+EVgDoekTpNRinecU8S6vYjLUy5nVTelaHTpuqsLfg/SkjDkMU3819eQ4ZPiuIzOA6JVe1JpNIl+qr2g905pIOAy1aAg+xfq2fhnL7o02qAXEsA8z34DA==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_BN3PR0501MB1331624574C4557E56B2F6BED4AD0BN3PR0501MB1331_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: a1f284ad-8c30-4add-d6ee-08d5934889ef
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Mar 2018 18:36:50.2587 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR0501MB1428
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-03-26_08:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1803260189
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/YI1ifOyYRQk-6a7ytbL9GnpLgns>
Subject: Re: [bess] draft-zzhang-bess-mvpn-msdp-sa-interoperation-01
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 26 Mar 2018 18:36:58 -0000

Hi Keshava,

Thanks for your support on the problem (and the solution I assume).
I want to follow up on your comment on "Treating one protocol (MVPN SA)  output as an input trigger to another protocol (MSDP)".

The context text is the following:

   In addition to procedures in [RFC6514<https://tools.ietf.org/html/rfc6514>], an MVPN PE may be provisioned
   to generate MSDP SA messages from received MVPN SA routes, with or
   without fine policy control.  If a received MVPN SA route is to
   trigger MSDP SA message, it is treated as if a corresponding MSDP SA
   message was received from within the PE mesh group and normal MSDP
   procedure is followed (e.g. an MSDP SA message is advertised to other
   MSDP peers outside the PE mesh group).

Instead of specifying MSDP advertisement procedures upon the receipt of MVPN SA route, I thought the above best describes the expected result from protocol point of view (and one way of implementing the interop procedures), though local implementation could be different.

I hope that is acceptable?

Thanks.
Jeffrey
From: BESS <bess-bounces@ietf.org> On Behalf Of A, Keshava
Sent: Monday, March 12, 2018 4:10 AM
To: Susan Hares <shares@ndzh.com>; bess@ietf.org
Cc: A, Keshava <keshava.a@hpe.com>
Subject: Re: [bess] Call for adoption: draft-zzhang-bess-mvpn-msdp-sa-interoperation-01

Support.

Problem statement is valid.
Treating one protocol (MVPN SA)  output as an input trigger to another protocol (MSDP)  needs to be discussed more..


/keshava

v2.23.0 | Report a Bug | By Email