Re: [nvo3] BFD over VXLAN: Trapping BFD Control packet at VTEP

Selvakumar Sivaraj <ssivaraj@juniper.net> Thu, 31 October 2019 02:34 UTC

Return-Path: <ssivaraj@juniper.net>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A78D31200F3; Wed, 30 Oct 2019 19:34:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.736
X-Spam-Level:
X-Spam-Status: No, score=0.736 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, 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_LOW=-0.7, RCVD_IN_SBL_CSS=3.335, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 mfLzqfN4r42S; Wed, 30 Oct 2019 19:34:34 -0700 (PDT)
Received: from mx0a-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (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 62CD61200DF; Wed, 30 Oct 2019 19:34:34 -0700 (PDT)
Received: from pps.filterd (m0108156.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id x9V2WVaK003962; Wed, 30 Oct 2019 19:34:27 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=PPS1017; bh=0ZE9Y4Wiv6+1lJrdtDIWNk2Z4qiSDli4vkoxcefPT4Q=; b=Uz2DfUPkcmy8WqigpyUKw1IdvprYjqElRwVfHNMW+Bf9oG2ZEexDsEk+grmlGNNIaqlR agL0h8sseGCHnnQjy1CjzwB2J14jqlijVdmOTWI7MHrRUct3KnnGgUA0y87rqD84iEuZ zGLByVi+RqyeLzNbNI/IA1O0SYpCpsPyyEnkOlFcYPItfe4pg3ahwEVP0UVkKiPd6N5R mSuYqejNgpO/r9svmjEu0R4R97Vvjo7QSrYFepqjaD4D/ghLLBlJa7sB+JZpbsg6wE5l DUoZ25qROws7mLZzVLm5ZgLuR9RDv/ZjkJOa+WPie51tc2MNsKUqy0OaVQ5kntYlFo8b IA==
Received: from nam03-co1-obe.outbound.protection.outlook.com (mail-co1nam03lp2051.outbound.protection.outlook.com [104.47.40.51]) by mx0a-00273201.pphosted.com with ESMTP id 2vxwfh2dj9-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 30 Oct 2019 19:34:26 -0700
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=g6U+QaFucJRZlcB1xkX/xMaeklZE9jY2TlZ+MKvWhhWXbsuN9LkZtoT8cip8EHuqpD8HhtlKFjhGKLbYnhQwBXoTNd/2jv5fjL3nUhIhnceWOwLjPKb0yP7iuJWFrZyUtA7+HPbWk/uMs/fBpp1IUsEdO5ZPQaGYfeZ/x5G/msWCWnei2LuJMZLdImXduLqUISS/gAhbbxPiFSffcfHaWE/lxILflvH2FI1++7lf42D/EOW99PgTum46FT/64iYXy4mhn6WWQqOhljI/8NnFjMRvaclV2OEApYsBS+eXbbs2ulE/yMBSaZf5rFgxTDeAGxjcxqPwLyFor9hgZf/olQ==
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=0ZE9Y4Wiv6+1lJrdtDIWNk2Z4qiSDli4vkoxcefPT4Q=; b=Z7aZ2gSpJR7GHNmDw5BnTD3FMq9oHSM0zmgNIj+Y1B0haUZ4T7C5t0arZ+8CSy0HaISyrkVRs7RYmd84e9zu5A7OjhvBNKnPtMq1+iEFVOMlL702/IRKr1778nUzp/TcQ/RECg1EQomvc5CbQOmzYe95APVnlo5QxEvtFvhoLecby5wPhkwBeVIK3sp26tjTMy7k6t2HqotBfwIw/HI2e1gUOxUOJOqg3Z0Wu5S8rlK+9ky+CFB92lFUYrweaVLtKBjutRHxPqXgj/zF9X8NC42G6S+6L6OsQVuBvZgZm9/xMNSkiLhJGtaEbKp/+7dCITSkcvGTky2ijLTZDv9mBA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=juniper.net; dmarc=pass action=none header.from=juniper.net; dkim=pass header.d=juniper.net; arc=none
Received: from BYAPR05MB5224.namprd05.prod.outlook.com (20.177.230.77) by BYAPR05MB4133.namprd05.prod.outlook.com (52.135.193.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2387.13; Thu, 31 Oct 2019 02:34:21 +0000
Received: from BYAPR05MB5224.namprd05.prod.outlook.com ([fe80::34b3:586b:67bd:e0f9]) by BYAPR05MB5224.namprd05.prod.outlook.com ([fe80::34b3:586b:67bd:e0f9%7]) with mapi id 15.20.2408.016; Thu, 31 Oct 2019 02:34:21 +0000
From: Selvakumar Sivaraj <ssivaraj@juniper.net>
To: Greg Mirsky <gregimirsky@gmail.com>
CC: Dinesh Dutt <didutt@gmail.com>, NVO3 <nvo3@ietf.org>, "draft-ietf-bfd-vxlan@ietf.org" <draft-ietf-bfd-vxlan@ietf.org>, Anoop Ghanwani <anoop@alumni.duke.edu>, Santosh P K <santosh.pallagatti@gmail.com>, Jeffrey Haas <jhaas@pfrc.org>, rtg-bfd WG <rtg-bfd@ietf.org>, "Joel M. Halpern" <jmh@joelhalpern.com>, "T. Sridhar" <tsridhar@vmware.com>, "xiao.min2@zte.com.cn" <xiao.min2@zte.com.cn>
Subject: Re: [nvo3] BFD over VXLAN: Trapping BFD Control packet at VTEP
Thread-Topic: [nvo3] BFD over VXLAN: Trapping BFD Control packet at VTEP
Thread-Index: AQHVefXTkwgUH6XWXUSpCrzkCHgBh6dls0cAgAELsQCAAFSxgIAAAloAgABQeQCAADkgWIAABPuAgADJCgCAAAU+gIAH16L3gAAZgwCAABCFgIAAAtMAgAAD6ICAAANigIAAAoUAgAAGUwCAABfdgIABQq+AgAAJ2ICAAN0Tb4AAFK9agABdngCAAIvTgP//kw8AgAB41QD//+sngA==
Date: Thu, 31 Oct 2019 02:34:21 +0000
Message-ID: <4200BA8D-0984-4D66-AA3F-974E28BFC5CD@juniper.net>
References: <CACi9rdu8PKsLW_Pq4ww5DEwLL8Bs6Hq1Je_jmAjES4LKBuE8MQ@mail.gmail.com> <CA+RyBmXkyQMumeCDxM6OSzdn=DCL=aeyQ+tJmUiyEg0VZuUpRg@mail.gmail.com> <1571798869.2855.1@smtp.gmail.com> <CACi9rduyvhweJd_aNx6miiUGyu-nCeqnNHGbPjyCfswHx1RD5A@mail.gmail.com> <CA+RyBmXLBLARxhA4MUvD6DE8vvY1oDP0opkxDqiPA4zYw9Jpug@mail.gmail.com> <1571860470.2855.11@smtp.gmail.com> <CACi9rdtwiuH2VjuUkzeg3+PhwcFMSqFepbcM0tgmRxSbcR3AQQ@mail.gmail.com> <CA+-tSzyi=uDdqSDq4u7kytAucX136mO2XtPtR=DG+KKAC5PjCQ@mail.gmail.com> <88a1320e-093a-a101-d8a6-6ae6d7648466@joelhalpern.com> <CA+-tSzxCpLOmhpBXP1k5vLY20qA5db9nbq4qEiH00jo=EH+w8g@mail.gmail.com> <d7b25f3a-5f1e-30da-8a41-0d11e3c2d04c@joelhalpern.com> <CA+-tSzzBfp9Wy8KO6MbxFNXZBhC3bL7u92VwqJTA82WrwGUAgg@mail.gmail.com> <c773cd4f-320c-fb15-3b7b-d0016b7d5978@joelhalpern.com> <CA+-tSzxUs9PGv+y1PBquaAhuq4wK_=TkR+b_ET6j7OBHf4Mq7Q@mail.gmail.com> <97bdb8b4-b334-53fb-05a6-2d1fc8684ad3@joelhalpern.com> <CA+-tSzw76E0AM2AJR=2GQsXJ3MtFUtsug7KoGQzAP-=Ds8u7Fg@mail.gmail.com> <aa853b8e-7ff4-a2d9-9b66-f9c22823ac9d@joelhalpern.com> <1572400778.28051.7@smtp.gmail.com> <CA+-tSzyNu8XVqL7=cGVaT7Mbg5yO6d3ohgv2qPTrMHRV1vw0rg@mail.gmail.com> <1a38424c-6bc1-4414-a7fd-c1e2105b581a@Spark> <CA+-tSzzSNnR=fKRU+mEX=d+tL5B0u8eNUAoGcPvfrna_qHL7Hg@mail.gmail.com> <1572435956.28051.12@smtp.gmail.com> <CA+RyBmWgvjDLdxEz7oZEfYjtJT=7CZbiV5bRkx=gf3hQHHokOw@mail.gmail.com> <73C65A84-D59F-42AA-A2BA-5DE6946DC6D8@juniper.net> <CA+RyBmXdjstOd6kR2t6okHGTEy+Sif=XDnrZV-2WNsijWd+=VA@mail.gmail.com>
In-Reply-To: <CA+RyBmXdjstOd6kR2t6okHGTEy+Sif=XDnrZV-2WNsijWd+=VA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.20.0.191028
x-originating-ip: [66.129.242.14]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 1bf6202a-4437-4fae-90dd-08d75daad632
x-ms-traffictypediagnostic: BYAPR05MB4133:
x-ms-exchange-purlcount: 7
x-microsoft-antispam-prvs: <BYAPR05MB41330EC94EF95F1930403BD9D3630@BYAPR05MB4133.namprd05.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:7691;
x-forefront-prvs: 02070414A1
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(376002)(366004)(39860400002)(396003)(136003)(199004)(189003)(966005)(478600001)(30864003)(1411001)(81166006)(8676002)(5070765005)(6246003)(6506007)(81156014)(58126008)(102836004)(53546011)(8936002)(71190400001)(517774005)(21615005)(606006)(71200400001)(99286004)(54906003)(440504004)(2906002)(76176011)(36756003)(33656002)(14444005)(5024004)(14454004)(316002)(66574012)(256004)(26005)(66946007)(446003)(6486002)(7736002)(7416002)(229853002)(6306002)(66446008)(64756008)(86362001)(5660300002)(25786009)(66476007)(66556008)(54896002)(486006)(476003)(186003)(76116006)(4326008)(6916009)(6436002)(66066001)(6512007)(11346002)(3846002)(6116002)(91956017)(236005)(2616005)(12620500001)(579004)(559001)(569006); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR05MB4133; H:BYAPR05MB5224.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-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: Gr3E8Pls2HOzSDr4xJhZFcnv9LtpHOLAy4V1mOjYWSsxqwR7kRvUBWqUXEqS1y+X/FHLvUl5bC9az0qwfDPkMn7wKKa0D3TAGNR180ZMuQrgWW0uZY+ifCO8TOS5Xrc7jjq6DkjFeiDqCQRpJbRg2H7nKJurITztocmomtGuhzXByy2zxK0OqwZZF65dXbB7L1uNymXwHqK6npO5W3hp9t1w+cfkdj52Yj+LWPkdtmgbHXLpRww9Z1tAad0P8/HyjS6lVmoQPM1gOtuq1lVMIVuKQdHyyuTRGUD9QzHdfz9wCYh7mEtHcRIoYu1uRJ2x/VA6u3UHMoOjsfK9yqEn5oKXDltaFC3Q1oBZlbX+0u4MQNfoD33y0W9X9bJFOk/XuGonEs3i04T48T5YecJgHw1OdDpf4tXeN6vhb8DRO47Cwi0z1kTr6GOs1vJurUy4/WbbmO4R+PFN3IlVF37FdUtQzbzKQLtbropgt2zXvHY=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_4200BA8D09844D66AA3F974E28BFC5CDjunipernet_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 1bf6202a-4437-4fae-90dd-08d75daad632
X-MS-Exchange-CrossTenant-originalarrivaltime: 31 Oct 2019 02:34:21.3047 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: /9Wbz/hg/FdiFDarva6rV3qMGdA8dQVuuIsLRJLZKjUWPzY+yre52tcQIsc8O/mgE4djGiyLEhHDHM1Ehpwv0g==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR05MB4133
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.95,1.0.8 definitions=2019-10-30_10:2019-10-30,2019-10-30 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 suspectscore=0 bulkscore=0 mlxlogscore=999 mlxscore=0 phishscore=0 impostorscore=0 adultscore=0 lowpriorityscore=0 clxscore=1015 malwarescore=0 spamscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1908290000 definitions=main-1910310024
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/-2H9IOapqJ6Om10fTbC4FF1k_W8>
X-Mailman-Approved-At: Wed, 30 Oct 2019 20:00:13 -0700
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-bfd/>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Oct 2019 02:34:41 -0000

Greg,

Here the assumption is that the VTEP incorrectly received a BFD packet and it needs to be dropped. What if there is an end to end BFD and VTEP is only transporting those packets? If the tenant needs the BFD packet then this requirement to drop is making it mutually exclusive with VTEP BFD capability.

Thanks,
Selvakumar

From: Greg Mirsky <gregimirsky@gmail.com>
Date: Wednesday, October 30, 2019 at 1:49 PM
To: Selvakumar Sivaraj <ssivaraj@juniper.net>
Cc: Dinesh Dutt <didutt@gmail.com>om>, NVO3 <nvo3@ietf.org>rg>, "draft-ietf-bfd-vxlan@ietf.org" <draft-ietf-bfd-vxlan@ietf.org>rg>, Anoop Ghanwani <anoop@alumni.duke.edu>du>, Santosh P K <santosh.pallagatti@gmail.com>om>, Jeffrey Haas <jhaas@pfrc.org>rg>, rtg-bfd WG <rtg-bfd@ietf.org>rg>, "Joel M. Halpern" <jmh@joelhalpern.com>om>, "T. Sridhar" <tsridhar@vmware.com>om>, "xiao.min2@zte.com.cn" <xiao.min2@zte.com.cn>
Subject: Re: [nvo3] BFD over VXLAN: Trapping BFD Control packet at VTEP

Hi Selvakumar,
a packet can be identified as a BFD Control message by the value of the destination UDP port field. The intention of the text you've quoted is to suggest that if the received by VTEP packet has been identified as a BFD control packet it SHOULD NOT be forwarded to a tenant. What to do with such packet? I believe it must be silently dropped.
Does it make sense?

Regards,
Greg

On Wed, Oct 30, 2019 at 1:36 PM Selvakumar Sivaraj <ssivaraj@juniper.net<mailto:ssivaraj@juniper.net>> wrote:
Greg,

>Section 5.
>If the Destination MAC of the inner Ethernet frame doesn't
>   match any of VTEP's MAC addresses, then the processing of the
>   received VXLAN packet MUST follow the procedures described in
>   Section 4.1 [RFC7348].
>BFD Control packets with unknown MAC address MUST NOT be
> forwarded to VMs.

If the packet doesn’t match VTEP mac address, the packet is forwarded based on  Section 4.1 [RFC7348]. What is the assumption behind this statement “BFD Control packets with unknown MAC address MUST NOT be forwarded to VMs”?

Thanks,
Selvakumar


From: nvo3 <nvo3-bounces@ietf.org<mailto:nvo3-bounces@ietf.org>> on behalf of Greg Mirsky <gregimirsky@gmail.com<mailto:gregimirsky@gmail.com>>
Date: Wednesday, October 30, 2019 at 1:08 PM
To: Dinesh Dutt <didutt@gmail.com<mailto:didutt@gmail.com>>
Cc: NVO3 <nvo3@ietf.org<mailto:nvo3@ietf.org>>, "draft-ietf-bfd-vxlan@ietf.org<mailto:draft-ietf-bfd-vxlan@ietf.org>" <draft-ietf-bfd-vxlan@ietf.org<mailto:draft-ietf-bfd-vxlan@ietf.org>>, Anoop Ghanwani <anoop@alumni.duke.edu<mailto:anoop@alumni.duke.edu>>, Santosh P K <santosh.pallagatti@gmail.com<mailto:santosh.pallagatti@gmail.com>>, Jeffrey Haas <jhaas@pfrc.org<mailto:jhaas@pfrc.org>>, rtg-bfd WG <rtg-bfd@ietf.org<mailto:rtg-bfd@ietf.org>>, "Joel M. Halpern" <jmh@joelhalpern.com<mailto:jmh@joelhalpern.com>>, "T. Sridhar" <tsridhar@vmware.com<mailto:tsridhar@vmware.com>>, "xiao.min2@zte.com.cn<mailto:xiao.min2@zte.com.cn>" <xiao.min2@zte.com.cn<mailto:xiao.min2@zte.com.cn>>
Subject: Re: [nvo3] BFD over VXLAN: Trapping BFD Control packet at VTEP

Dear All,
thank you for your comments, suggestions that have made the discussion the most helpful to the Editors. I've tried to reflect your comments in the updates listed below:

  *   on the inner destination IP address:
OLD TEXT:
         Destination IP: IP address MUST NOT be of one of tenant's IP
         addresses.  IP address MAY be selected from the range 127/8 for
         IPv4, for IPv6 - from the range 0:0:0:0:0:FFFF:7F00:0/104.
NEW TEXT:
         Destination IP: IP address MUST NOT be of one of tenant's IP
         addresses.  The IP address SHOULD be selected from the range 127/8
         for IPv4, for IPv6 - from the range 0:0:0:0:0:FFFF:7F00:0/104.
         Alternatively, the destination IP address MAY be set to VTEP's
         IP address.

  *   firewall. Appended Section 3 Deployment with the following paragraph:
   As per Section 4, the inner destination IP address SHOULD be set to
   one of the loopback addresses (127/8 range for IPv4 and
   0:0:0:0:0:FFFF:7F00:0/104 range for IPv6).  There could be a firewall
   configured on VTEP to block loopback addresses if set as the
   destination IP in the inner IP header.  It is RECOMMENDED to allow
   addresses from the loopback range through a firewall only if it is
   used as the destination IP address in the inner IP header, and the
   destination UDP port is set to 3784 [RFC5881].

Regarding the use of VNI 0 as the Management VNI. In Section 6 has been noted:
   An implementation MAY support the use of the Management
   VNI as control and management channel between VTEPs.  The selection
   of the VNI number of the Management VNI MUST be controlled through
   management plane.  An implementation MAY use VNI number 1 as the
   default value for the Management VNI.

Attached, please find the updated working version and the diff to -07.
Editors much appreciate your comments, suggestions, abd help to have the new version uploaded before the cut-off deadline.

Regards,
Greg

On Wed, Oct 30, 2019 at 4:46 AM Dinesh Dutt <didutt@gmail.com<mailto:didutt@gmail.com>> wrote:


On Wed, Oct 30, 2019 at 11:40 AM, Anoop Ghanwani <anoop@alumni.duke.edu<mailto:anoop@alumni.duke.edu>> wrote:
Hi Dinesh,

Your earlier comment was about silicon, that's why I discussed only the trapping issue.  As far as software goes, IP stacks would typically discard packets received from a non-loopback interface if the packet's address is in 127/8.  I am not sure a traditional IP stack can play here because even on Tx, we have the same MAC for reaching all remote VTEPs.  It seems to me the BFD module would have to be working directly with L2 frames coming off the tunnel.  Kind of like if we were running LLDP between the VTEPs.

Hi Anoop,

My earlier comment was indeed about silicon, but the packet has to go through the software stack as well once it gets to the CPU. Linux-based solutions such as Linux servers or Cumulus Linux or maybe even SONIC will need to have a valid IP address to process the packet. Given that 127/8 is already mandated by MPLS BFD, sticking with that is better than ignoring the IP address. This is why I agreed with Jeffrey Haas' comment about SHOULD be set.

Dinesh

Thanks,
Anoop

On Tue, Oct 29, 2019 at 10:02 PM Dinesh Dutt <didutt@gmail.com<mailto:didutt@gmail.com>> wrote:
Trapping to the CPU would be fine based on MAC DA. But once there, a self-respecting network stack would look at the IP header to decide what to do. Ignoring it on receive may not be an option,

Dinesh
On Oct 30, 2019, 10:26 AM +0530, Anoop Ghanwani <anoop@alumni.duke.edu<mailto:anoop@alumni.duke.edu>>, wrote:
Hi Dinesh,

What would break?  If messages are trapped to CPU based on the MAC DA, what is the problem?

On the flip side, there are implementations running BFD today which use different addresses as specified here:
http://www.openvswitch.org/support/dist-docs/vtep.5.html<https://urldefense.com/v3/__http:/www.openvswitch.org/support/dist-docs/vtep.5.html__;!8WoA6RjC81c!XSnPbDk99ntaSkrho1h-7Nk38vE1gJ9GQ7udWfbGLtCOiKt6Yz9oRI70D8TPFzme$>
>>>

       bfd_config_local : bfd_dst_ip: optional string

              Set to an IPv4 address to set the IP address that is expected as

              destination   for   received   BFD   packets.   The  default  is

              169.254.1.0.
>>>

Thanks,
Anoop

On Tue, Oct 29, 2019 at 7:01 PM Dinesh Dutt <didutt@gmail.com<mailto:didutt@gmail.com>> wrote:
I suspect silicon implementations will have a problem with saying that they can be set to anything and MUST be ignored on reception. Your logic is sound, it's just that I fear you'll break many existing implementations. I recommend sticking with the 127/8 address for this case.

Dinesh

On Tue, Oct 29, 2019 at 9:15 PM, Joel M. Halpern <jmh@joelhalpern.com<mailto:jmh@joelhalpern.com>> wrote:
In all the discussion about what VNI to use and multiple VNI support, I lsot track. Sorry. Still, the earlier documents did not specify the IP to use. That does NOT mean that we are required in later revisions of the document to allow anything the client wants. Having said that, we could add text saying that since the IP address in the BFD request in VNI 0 is effectively meaningless, it can be set to any value on transmission and must be ignored on reception. As far as I can tell, it is definitional that the VtEP does not have any assigned IP address for VNI 0, so we can't expect that address. Yours, Joel On 10/29/2019 11:10 AM, Anoop Ghanwani wrote:
Hi Joel, Yes, existing implementations use VNI 0 for BFD over VXLAN.  Here are a couple of references: https://www.juniper.net/documentation/en_US/junos/topics/concept/sdn-ovsdb-bfd-nsx.html https://www.cisco.com/c/en/us/products/collateral/switches/nexus-9000-series-switches/white-paper-c11-740091.html#_Toc18013665<https://urldefense.com/v3/__https:/www.cisco.com/c/en/us/products/collateral/switches/nexus-9000-series-switches/white-paper-c11-740091.html*_Toc18013665__;Iw!8WoA6RjC81c!XSnPbDk99ntaSkrho1h-7Nk38vE1gJ9GQ7udWfbGLtCOiKt6Yz9oRI70D-WWtRSX$> I guess this document has been evolving and I have not kept up with it. The version I had reviewed and commented on originally allowed for VNI 0.  The -04 version of the draft has this: https://tools.ietf.org/html/draft-ietf-bfd-vxlan-04#section-7<https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-ietf-bfd-vxlan-04*section-7__;Iw!8WoA6RjC81c!XSnPbDk99ntaSkrho1h-7Nk38vE1gJ9GQ7udWfbGLtCOiKt6Yz9oRI70D1ZHtv2T$> What version are you referring to? Thanks, Anoop On Mon, Oct 28, 2019 at 12:55 PM Joel M. Halpern <jmh@joelhalpern.com<mailto:jmh@joelhalpern.com> <mailto:jmh@joelhalpern.com>> wrote: You are saying that there are existing implementations using VNI 0 for this?  Given that previous versions of the spec explicitly disallowed VNI 0, I am having trouble with your objecting that a spec for how to run over VNI 0 breask existing implementations. Note that when there is a good technical reason, the IETF does change Internet Drafts in ways that break early implementations.  That is the price of standardization. Yours, Joel On 10/28/2019 2:30 PM, Anoop Ghanwani wrote: > Hi Joel, > > Writing the spec in that way would make the current, inter-operable > implementation of multiple vendors non-compliant with the spec. > > Thanks, > Anoop > > On Mon, Oct 28, 2019 at 11:07 AM Joel M. Halpern <jmh@joelhalpern.com<mailto:jmh@joelhalpern.com> <mailto:jmh@joelhalpern.com> > <mailto:jmh@joelhalpern.com <mailto:jmh@joelhalpern.com>>> wrote: > >     I assumed this was only for the case where a tenant VNI was being used. > >     For the 0 VNI (which is what I prefer), always (MUST) use the loopback >     address.  There are no addresses assigned to the VTEP in that space. >     There is no IRB in that space. > >     Yours, >     Joel > >     On 10/28/2019 1:58 PM, Anoop Ghanwani wrote: >      > Joel, >      > >      > Are we going to qualify this by VNI?  There's a bunch of >     implementations >      > out there that don't use a tenant IP or a loopback with VNI 0--they >      > simply repeat the underlay IP in the inner IPDA. >      > >      > Thanks, >      > Anoop >      > >      > On Mon, Oct 28, 2019 at 10:46 AM Joel M. Halpern >     <jmh@joelhalpern.com<mailto:jmh@joelhalpern.com> <mailto:jmh@joelhalpern.com> <mailto:jmh@joelhalpern.com <mailto:jmh@joelhalpern.com>> >      > <mailto:jmh@joelhalpern.com <mailto:jmh@joelhalpern.com> <mailto:jmh@joelhalpern.com <mailto:jmh@joelhalpern.com>>>> wrote: >      > >      >     I can live with saying that you SHOULD use loopback, and MAY >     instead >      >     use >      >     an IP address in the customer space known to be owned by the VTEP >      >     device >      >     when such exists. >      > >      >     Yours, >      >     Joel >      > >      >     On 10/28/2019 1:32 PM, Anoop Ghanwani wrote: >      >      > Hi Joel, >      >      > >      >      > Perhaps we need to say use of an address owned by the device >      >     containing >      >      > the VTEP. >      >      > >      >      > Or are you suggesting that the use of the loopback address >     space >      >     is a MUST? >      >      > >      >      > Anoop >      >      > >      >      > On Mon, Oct 28, 2019 at 10:22 AM Joel M. Halpern >      >     <jmh@joelhalpern.com<mailto:jmh@joelhalpern.com> <mailto:jmh@joelhalpern.com> <mailto:jmh@joelhalpern.com <mailto:jmh@joelhalpern.com>> >     <mailto:jmh@joelhalpern.com <mailto:jmh@joelhalpern.com> <mailto:jmh@joelhalpern.com <mailto:jmh@joelhalpern.com>>> >      >      > <mailto:jmh@joelhalpern.com <mailto:jmh@joelhalpern.com> <mailto:jmh@joelhalpern.com <mailto:jmh@joelhalpern.com>> >     <mailto:jmh@joelhalpern.com <mailto:jmh@joelhalpern.com> <mailto:jmh@joelhalpern.com <mailto:jmh@joelhalpern.com>>>>> wrote: >      >      > >      >      >     There is something I am missing in your assumption >     about IRB. >      >      > >      >      >     As I understand VxLAN, the VTEP is under the control >     of the >      >     operator. >      >      >     As such, it is a pure bridge.  If you run IRB behind >     it, that >      >     is fine. >      >      >     Yes, an operator may offer IRB.  But as I understand it, >      >     conceptually, >      >      >     in terms of the VxLAN architecture the IRB is an entity >      >     behind the >      >      >     VTEP, >      >      >     not part of the VTEP. >      >      > >      >      >     Yours, >      >      >     Joel >      >      > >      >      >     On 10/28/2019 12:23 PM, Anoop Ghanwani wrote: >      >      >      > Santosh, >      >      >      > >      >      >      > Does it have to be a MUST?  What if I am running >     IRB and there >      >      >     are IP >      >      >      > addresses per VNI assigned to the VTEPs? Why can the >      >     operator not >      >      >      > choose to use those? >      >      >      > >      >      >      > Anoop >      >      >      > >      >      >      > On Mon, Oct 28, 2019 at 7:51 AM Santosh P K >      >      >      > <santosh.pallagatti@gmail.com<mailto:santosh.pallagatti@gmail.com> <mailto:santosh.pallagatti@gmail.com> >     <mailto:santosh.pallagatti@gmail.com <mailto:santosh.pallagatti@gmail.com>> >      >     <mailto:santosh.pallagatti@gmail.com <mailto:santosh.pallagatti@gmail.com> >     <mailto:santosh.pallagatti@gmail.com <mailto:santosh.pallagatti@gmail.com>>> >      >      >     <mailto:santosh.pallagatti@gmail.com <mailto:santosh.pallagatti@gmail.com> >     <mailto:santosh.pallagatti@gmail.com <mailto:santosh.pallagatti@gmail.com>> >      >     <mailto:santosh.pallagatti@gmail.com <mailto:santosh.pallagatti@gmail.com> >     <mailto:santosh.pallagatti@gmail.com <mailto:santosh.pallagatti@gmail.com>>>> >      >      >     <mailto:santosh.pallagatti@gmail.com <mailto:santosh.pallagatti@gmail.com> >     <mailto:santosh.pallagatti@gmail.com <mailto:santosh.pallagatti@gmail.com>> >      >     <mailto:santosh.pallagatti@gmail.com <mailto:santosh.pallagatti@gmail.com> >     <mailto:santosh.pallagatti@gmail.com <mailto:santosh.pallagatti@gmail.com>>> >      >      >     <mailto:santosh.pallagatti@gmail.com <mailto:santosh.pallagatti@gmail.com> >     <mailto:santosh.pallagatti@gmail.com <mailto:santosh.pallagatti@gmail.com>> >      >     <mailto:santosh.pallagatti@gmail.com <mailto:santosh.pallagatti@gmail.com> >     <mailto:santosh.pallagatti@gmail.com <mailto:santosh.pallagatti@gmail.com>>>>>> wrote: >      >      >      > >      >      >      >     Dinesh, Anoop et all, >      >      >      >           Lets us know if this text works for 127/8 >      >     address range? >      >      >      > >      >      >      >     [proposed text for firewall] >      >      >      > >      >      >      >     "As per section 4 inner destination IP address >     MUST be >      >     set to >      >      >     127/8 >      >      >      >     address. There may be firewall configured on >     VTEP to >      >     block 127/8 >      >      >      >     address range if set as destination IP in inner IP >      >     header. It is >      >      >      >     recommended to allow 127/8 range address through >      >     firewall only if >      >      >      >     127/8 IP address is set as destination address >     in inner IP >      >      >     header." >      >      >      > >      >      >      > >      >      >      >     In section 4 we are talking about using 127/8 >     and not >      >     really >      >      >     giving >      >      >      >     reason why. I think we should have text as RFC 5884 >      >     has mentioned >      >      >      >     with below text. >      >      >      > >      >      >      >     [From RFC 5884] >      >      >      >     "The motivation for using the address range >     127/8 is >      >     the same as >      >      >      >     specified in Section 2.1 of [RFC4379] >      >      >      >  <https://tools.ietf.org/html/rfc4379#section-2.1<https://urldefense.com/v3/__https:/tools.ietf.org/html/rfc4379*section-2.1__;Iw!8WoA6RjC81c!XSnPbDk99ntaSkrho1h-7Nk38vE1gJ9GQ7udWfbGLtCOiKt6Yz9oRI70D1QXo1ID$>>. >      >     This is an >      >      >      >     exception to the behavior defined in [RFC1122 >      >      >      >     <https://tools.ietf.org/html/rfc1122<https://urldefense.com/v3/__https:/tools.ietf.org/html/rfc1122__;!8WoA6RjC81c!XSnPbDk99ntaSkrho1h-7Nk38vE1gJ9GQ7udWfbGLtCOiKt6Yz9oRI70D7jd9cRn$>>]." >      >      >      > >      >      >      > >      >      >      > >      >      >      >     Thanks >      >      >      >     Santosh P K >      >      >      > >      >      >      > >      >      >      > >      >      >      >     On Thu, Oct 24, 2019 at 1:24 AM Dinesh Dutt >      >     <didutt@gmail.com<mailto:didutt@gmail.com> <mailto:didutt@gmail.com> <mailto:didutt@gmail.com <mailto:didutt@gmail.com>> >     <mailto:didutt@gmail.com <mailto:didutt@gmail.com> <mailto:didutt@gmail.com <mailto:didutt@gmail.com>>> >      >      >     <mailto:didutt@gmail.com <mailto:didutt@gmail.com> <mailto:didutt@gmail.com <mailto:didutt@gmail.com>> >     <mailto:didutt@gmail.com <mailto:didutt@gmail.com> <mailto:didutt@gmail.com <mailto:didutt@gmail.com>>>> >      >      >      >     <mailto:didutt@gmail.com <mailto:didutt@gmail.com> >     <mailto:didutt@gmail.com <mailto:didutt@gmail.com>> <mailto:didutt@gmail.com <mailto:didutt@gmail.com> >     <mailto:didutt@gmail.com <mailto:didutt@gmail.com>>> >      >     <mailto:didutt@gmail.com <mailto:didutt@gmail.com> <mailto:didutt@gmail.com <mailto:didutt@gmail.com>> >     <mailto:didutt@gmail.com <mailto:didutt@gmail.com> <mailto:didutt@gmail.com <mailto:didutt@gmail.com>>>>>> wrote: >      >      >      > >      >      >      >         Looks good to me Greg. I see that the text >     around >      >     the use >      >      >     of the >      >      >      >         inner IP address as also quite acceptable. Will >      >     you add any >      >      >      >         words about the firewall? >      >      >      > >      >      >      >         Dinesh >      >      >      > >      >      >      >         On Wed, Oct 23, 2019 at 8:36 PM, Greg Mirsky >      >      >      >         <gregimirsky@gmail.com<mailto:gregimirsky@gmail.com> <mailto:gregimirsky@gmail.com> >     <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com>> >      >     <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com> <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com>>> >     <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com> <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com>> >      >     <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com> <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com>>>> >      >      >     <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com> >     <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com>> <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com> >     <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com>>> >      >     <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com> <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com>> >     <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com> <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com>>>>>> wrote: >      >      >      >>         Hi Dinesh, et al., >      >      >      >>         please check the updated version that >     removed the >      >      >     reference to >      >      >      >>         Hypervisor in the text and Figure 1. >      >      >      >> >      >      >      >>         Regards, >      >      >      >>         Greg >      >      >      >> >      >      >      >>         On Wed, Oct 23, 2019 at 10:47 AM Santosh P K >      >      >      >>         <santosh.pallagatti@gmail.com<mailto:santosh.pallagatti@gmail.com> <mailto:santosh.pallagatti@gmail.com> >     <mailto:santosh.pallagatti@gmail.com <mailto:santosh.pallagatti@gmail.com>> >      >     <mailto:santosh.pallagatti@gmail.com <mailto:santosh.pallagatti@gmail.com> >     <mailto:santosh.pallagatti@gmail.com <mailto:santosh.pallagatti@gmail.com>>> >      >      >     <mailto:santosh.pallagatti@gmail.com <mailto:santosh.pallagatti@gmail.com> >     <mailto:santosh.pallagatti@gmail.com <mailto:santosh.pallagatti@gmail.com>> >      >     <mailto:santosh.pallagatti@gmail.com <mailto:santosh.pallagatti@gmail.com> >     <mailto:santosh.pallagatti@gmail.com <mailto:santosh.pallagatti@gmail.com>>>> >      >      >      >>  <mailto:santosh.pallagatti@gmail.com <mailto:santosh.pallagatti@gmail.com> >     <mailto:santosh.pallagatti@gmail.com <mailto:santosh.pallagatti@gmail.com>> >      >     <mailto:santosh.pallagatti@gmail.com <mailto:santosh.pallagatti@gmail.com> >     <mailto:santosh.pallagatti@gmail.com <mailto:santosh.pallagatti@gmail.com>>> >      >      >     <mailto:santosh.pallagatti@gmail.com <mailto:santosh.pallagatti@gmail.com> >     <mailto:santosh.pallagatti@gmail.com <mailto:santosh.pallagatti@gmail.com>> >      >     <mailto:santosh.pallagatti@gmail.com <mailto:santosh.pallagatti@gmail.com> >     <mailto:santosh.pallagatti@gmail.com <mailto:santosh.pallagatti@gmail.com>>>>>> wrote: >      >      >      >> >      >      >      >>             Dinesh, >      >      >      >>                  Please see my inline comments [SPK] >      >      >      >> >      >      >      >> >      >      >      >>                 - In section 3, there's a sentence >     that >      >     is: "BFD >      >      >      >>                 packets intended for a Hypervisor >     VTEP MUST >      >      >     NOT..". I >      >      >      >>                 recommend getting rid of the word >      >     "Hypervisor" ashe >      >      >      >>                 logic applies to any VTEP. >      >      >      >> >      >      >      >>             [SPK] Thanks for comments. We will >     change this. >      >      >      >> >      >      >      >>                 - You already explained the >     precedence of >      >     the use of >      >      >      >>                 127/8 address in the inner header in >      >     MPLS. I have no >      >      >      >>                 specific comments in that area. I have >      >     only two >      >      >      >>                 questions: >      >      >      >>                    - Has anybody verified that the >     use of >      >     127/8 >      >      >      >>                 address (and the right MAC) works with >      >     existing >      >      >      >>                 implementations, including the silicon >      >     ones? If this >      >      >      >>                 doesn't work there, is it worth >     adding the >      >      >     possibilit >      >      >      >>                 y of another address, one that is >     owned >      >     by the >      >      >     VTEP node? >      >      >      >> >      >      >      >>                    - Do we know if Firewalls stop >     such VXLAN >      >      >     packets? >      >      >      >>                 I ask this because VXLAN has an IP >     header >      >     and I >      >      >     don't >      >      >      >>                 know if firewalls stop packets >     with 127/8 >      >     in the >      >      >     inner >      >      >      >>                 header. If not, is it worth adding a >      >     sentence to say >      >      >      >>                 that firewalls  allow such >     packets? The >      >     use of a >      >      >      >>                 non-127/8 address may alleviate >     this case >      >     as well. >      >      >      >> >      >      >      >>             [SPK] I think we may need to add the text >      >     about firewall >      >      >      >>             as some checks in firewall will be >     there if >      >     they are not >      >      >      >>             already using MPLS OAM which has inner IP >      >     header with >      >      >      >>             127/8 address range. >      >      >      >> >      >      >      >> >      >      >      >>                 The rest of the draft looks good >     to me, >      >      >      >> >      >      >      >>                 Dinesh >      >      >      >> >      >      >      >>                 On Wed, Oct 23, 2019 at 7:58 AM, >     Greg Mirsky >      >      >      >>                 <gregimirsky@gmail.com<mailto:gregimirsky@gmail.com> <mailto:gregimirsky@gmail.com> >     <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com>> >      >     <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com> <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com>>> >      >      >     <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com> >     <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com>> <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com> >     <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com>>>> >      >     <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com> <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com>> >     <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com> <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com>>> >      >      >     <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com> >     <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com>> <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com> >     <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com>>>>>> >      >      >      >>                 wrote: >      >      >      >>>                 Hi Dinesh, >      >      >      >>>                 I greatly appreciate your comments. >      >     Please heave a >      >      >      >>>                 look at the attached copy of the >     working >      >      >     version and >      >      >      >>>                 its diff to -07 (latest in the >     datatracker). >      >      >      >>> >      >      >      >>>                 Regards, >      >      >      >>>                 Greg >      >      >      >>> >      >      >      >>>                 On Tue, Oct 22, 2019 at 9:52 PM >     Dinesh Dutt >      >      >      >>>                 <didutt@gmail.com<mailto:didutt@gmail.com> <mailto:didutt@gmail.com> >     <mailto:didutt@gmail.com <mailto:didutt@gmail.com>> >      >     <mailto:didutt@gmail.com <mailto:didutt@gmail.com> <mailto:didutt@gmail.com <mailto:didutt@gmail.com>>> >     <mailto:didutt@gmail.com <mailto:didutt@gmail.com> <mailto:didutt@gmail.com <mailto:didutt@gmail.com>> >      >     <mailto:didutt@gmail.com <mailto:didutt@gmail.com> <mailto:didutt@gmail.com <mailto:didutt@gmail.com>>>> >      >      >     <mailto:didutt@gmail.com <mailto:didutt@gmail.com> <mailto:didutt@gmail.com <mailto:didutt@gmail.com>> >     <mailto:didutt@gmail.com <mailto:didutt@gmail.com> <mailto:didutt@gmail.com <mailto:didutt@gmail.com>>> >      >     <mailto:didutt@gmail.com <mailto:didutt@gmail.com> <mailto:didutt@gmail.com <mailto:didutt@gmail.com>> >     <mailto:didutt@gmail.com <mailto:didutt@gmail.com> <mailto:didutt@gmail.com <mailto:didutt@gmail.com>>>>>> wrote: >      >      >      >>> >      >      >      >>>                     I have the same feeling as Anoop. >      >     Greg, can you >      >      >      >>>                     please point me to the latest >     draft >      >     so that >      >      >     I can >      >      >      >>>                     quickly glance through it to be >      >     doubly sure, >      >      >      >>> >      >      >      >>>                     Dinesh >      >      >      >>> >      >      >      >>>                     On Wed, Oct 23, 2019 at 4:35 AM, >      >     Anoop Ghanwani >      >      >      >>>                     <anoop@alumni.duke.edu<mailto:anoop@alumni.duke.edu> <mailto:anoop@alumni.duke.edu> >     <mailto:anoop@alumni.duke.edu <mailto:anoop@alumni.duke.edu>> >      >     <mailto:anoop@alumni.duke.edu <mailto:anoop@alumni.duke.edu> <mailto:anoop@alumni.duke.edu <mailto:anoop@alumni.duke.edu>>> >      >      >     <mailto:anoop@alumni.duke.edu <mailto:anoop@alumni.duke.edu> >     <mailto:anoop@alumni.duke.edu <mailto:anoop@alumni.duke.edu>> <mailto:anoop@alumni.duke.edu <mailto:anoop@alumni.duke.edu> >     <mailto:anoop@alumni.duke.edu <mailto:anoop@alumni.duke.edu>>>> >      >      >      >>>  <mailto:anoop@alumni.duke.edu <mailto:anoop@alumni.duke.edu> >     <mailto:anoop@alumni.duke.edu <mailto:anoop@alumni.duke.edu>> >      >     <mailto:anoop@alumni.duke.edu <mailto:anoop@alumni.duke.edu> <mailto:anoop@alumni.duke.edu <mailto:anoop@alumni.duke.edu>>> >      >      >     <mailto:anoop@alumni.duke.edu <mailto:anoop@alumni.duke.edu> >     <mailto:anoop@alumni.duke.edu <mailto:anoop@alumni.duke.edu>> >      >     <mailto:anoop@alumni.duke.edu <mailto:anoop@alumni.duke.edu> >     <mailto:anoop@alumni.duke.edu <mailto:anoop@alumni.duke.edu>>>>>> wrote: >      >      >      >>>>                     Greg, >      >      >      >>>> >      >      >      >>>>                     I think the draft is fine as is. >      >      >      >>>> >      >      >      >>>>                     I discussion with Xiao Min was >      >     about #3 and I >      >      >      >>>>                     see that as unnecessary until we >      >     have a draft >      >      >      >>>>                     that explains why that is >     needed in the >      >      >     context >      >      >      >>>>                     of the NVO3 architecture. >      >      >      >>>> >      >      >      >>>>                     Anoop >      >      >      >>>> >      >      >      >>>>                     On Tue, Oct 22, 2019 at 11:17 AM >      >     Greg Mirsky >      >      >      >>>>  <gregimirsky@gmail.com<mailto:gregimirsky@gmail.com> <mailto:gregimirsky@gmail.com> >     <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com>> >      >     <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com> <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com>>> >      >      >     <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com> >     <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com>> <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com> >     <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com>>>> >      >      >      >>>> >       <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com> <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com>> >      >     <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com> <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com>>> >      >      >     <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com> >     <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com>> >      >     <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com> >     <mailto:gregimirsky@gmail.com <mailto:gregimirsky@gmail.com>>>>>> wrote: >      >      >      >>>> >      >      >      >>>>                         Hi Anoop, et al., >      >      >      >>>>                         I agree with your >     understanding >      >     of what is >      >      >      >>>>                         being defined in the current >      >     version >      >      >     of the >      >      >      >>>>                         BFD over VxLAN >     specification. >      >     But, as I >      >      >      >>>>                         understand, the WG is >      >     discussing the scope >      >      >      >>>>                         before the WGLC is closed. I >      >     believe there >      >      >      >>>>                         are three options: >      >      >      >>>> >      >      >      >>>>                          1. single BFD session >     between >      >     two VTEPs >      >      >      >>>>                          2. single BFD session >     per VNI >      >     between >      >      >     two VTEPs >      >      >      >>>>                          3. multiple BFD >     sessions per >      >     VNI between >      >      >      >>>>                             two VTEPs >      >      >      >>>> >      >      >      >>>>                         The current text >     reflects #2. Is WG >      >      >     accepts >      >      >      >>>>                         this scope? If not, which >      >     option WG would >      >      >      >>>>                         accept? >      >      >      >>>> >      >      >      >>>>                         Regards, >      >      >      >>>>                         Greg >      >      >      >>>> >      >      >      >>>>                         On Tue, Oct 22, 2019 at >     2:09 PM >      >     Anoop >      >      >      >>>>                         Ghanwani >     <anoop@alumni.duke.edu<mailto:anoop@alumni.duke.edu> <mailto:anoop@alumni.duke.edu> <mailto:anoop@alumni.duke.edu <mailto:anoop@alumni.duke.edu>> >      >     <mailto:anoop@alumni.duke.edu <mailto:anoop@alumni.duke.edu> <mailto:anoop@alumni.duke.edu <mailto:anoop@alumni.duke.edu>>> >      >      >     <mailto:anoop@alumni.duke.edu <mailto:anoop@alumni.duke.edu> >     <mailto:anoop@alumni.duke.edu <mailto:anoop@alumni.duke.edu>> <mailto:anoop@alumni.duke.edu <mailto:anoop@alumni.duke.edu> >     <mailto:anoop@alumni.duke.edu <mailto:anoop@alumni.duke.edu>>>> >      >      >      >>>> >       <mailto:anoop@alumni.duke.edu <mailto:anoop@alumni.duke.edu> <mailto:anoop@alumni.duke.edu <mailto:anoop@alumni.duke.edu>> >      >     <mailto:anoop@alumni.duke.edu <mailto:anoop@alumni.duke.edu> <mailto:anoop@alumni.duke.edu <mailto:anoop@alumni.duke.edu>>> >      >      >     <mailto:anoop@alumni.duke.edu <mailto:anoop@alumni.duke.edu> >     <mailto:anoop@alumni.duke.edu <mailto:anoop@alumni.duke.edu>> >      >     <mailto:anoop@alumni.duke.edu <mailto:anoop@alumni.duke.edu> >     <mailto:anoop@alumni.duke.edu <mailto:anoop@alumni.duke.edu>>>>>> wrote: >      >      >      >>>> >      >      >      >>>>                             I concur with Joel's >     assessment >      >      >     with the >      >      >      >>>>                             following >     clarifications. >      >      >      >>>> >      >      >      >>>>                             The current document >     is already >      >      >     capable >      >      >      >>>>                             of monitoring >     multiple VNIs >      >      >     between VTEPs. >      >      >      >>>> >      >      >      >>>>                             The issue under >     discussion >      >     was how >      >      >     do we >      >      >      >>>>                             use BFD to monitor >     multiple >      >     VAPs that >      >      >      >>>>                             use the same VNI >     between a >      >     pair of >      >      >      >>>>                             VTEPs.  The use case for >      >     this is not >      >      >      >>>>                             clear to me, as from my >      >     understanding, >      >      >      >>>>                             we cannot have a >     situation with >      >      >     multiple >      >      >      >>>>                             VAPs using the same >      >     VNI--there is 1:1 >      >      >      >>>>                             mapping between VAP >     and VNI. >      >      >      >>>> >      >      >      >>>>                             Anoop >      >      >      >>>> >      >      >      >>>>                             On Tue, Oct 22, 2019 >     at 6:06 AM >      >      >     Joel M. >      >      >      >>>>                             Halpern >      >     <jmh@joelhalpern.com<mailto:jmh@joelhalpern.com> <mailto:jmh@joelhalpern.com> <mailto:jmh@joelhalpern.com <mailto:jmh@joelhalpern.com>> >     <mailto:jmh@joelhalpern.com <mailto:jmh@joelhalpern.com> <mailto:jmh@joelhalpern.com <mailto:jmh@joelhalpern.com>>> >      >      >     <mailto:jmh@joelhalpern.com <mailto:jmh@joelhalpern.com> >     <mailto:jmh@joelhalpern.com <mailto:jmh@joelhalpern.com>> <mailto:jmh@joelhalpern.com <mailto:jmh@joelhalpern.com> >     <mailto:jmh@joelhalpern.com <mailto:jmh@joelhalpern.com>>>> >      >      >      >>>> >       <mailto:jmh@joelhalpern.com <mailto:jmh@joelhalpern.com> <mailto:jmh@joelhalpern.com <mailto:jmh@joelhalpern.com>> >      >     <mailto:jmh@joelhalpern.com <mailto:jmh@joelhalpern.com> <mailto:jmh@joelhalpern.com <mailto:jmh@joelhalpern.com>>> >      >      >     <mailto:jmh@joelhalpern.com <mailto:jmh@joelhalpern.com> >     <mailto:jmh@joelhalpern.com <mailto:jmh@joelhalpern.com>> <mailto:jmh@joelhalpern.com <mailto:jmh@joelhalpern.com> >     <mailto:jmh@joelhalpern.com <mailto:jmh@joelhalpern.com>>>>>> >      >     wrote: >      >      >      >>>> >      >      >      >>>>                                  From what I can >     tell, >      >     there >      >      >     are two >      >      >      >>>>                                 separate problems. >      >      >      >>>>                                 The document we >     have is a >      >      >     VTEP-VTEP >      >      >      >>>>                                 monitoring >     document. >      >     There is no >      >      >      >>>>                                 need for that >     document to >      >      >     handle the >      >      >      >>>>                                 multiple VNI case. >      >      >      >>>>                                 If folks want a >      >     protocol for doing >      >      >      >>>>                                 BFD monitoring >     of things >      >      >     behind the >      >      >      >>>>                                 VTEPs (multiple >     VNIs), >      >     then do >      >      >     that >      >      >      >>>>                                 as a separate >      >     document.   The >      >      >      >>>>                                 encoding will be >     a tenant >      >      >     encoding, >      >      >      >>>>                                 and thus >     sesparate from >      >     what is >      >      >      >>>>                                 defined in this >     document. >      >      >      >>>> >      >      >      >>>>                                 Yours, >      >      >      >>>>                                 Joel >      >      >      >>>> >      >      >      >>>>                                 On 10/21/2019 >     5:07 PM, >      >     Jeffrey >      >      >     Haas >      >      >      >>>>                                 wrote: >      >      >      >>>>                                 > Santosh and >     others, >      >      >      >>>>                                 > >      >      >      >>>>                                 > On Thu, Oct >     03, 2019 at >      >      >     07:50:20PM >      >      >      >>>>                                 +0530, Santosh P >     K wrote: >      >      >      >>>>                                 >>     Thanks >     for your >      >      >     explanation. >      >      >      >>>>                                 This helps a lot. I >      >     would wait >      >      >     for more >      >      >      >>>>                                 >> comments from >     others >      >     to see if >      >      >      >>>>                                 this what we >     need in this >      >      >     draft to be >      >      >      >>>>                                 >> supported >     based on >      >     that we can >      >      >      >>>>                                 provide appropriate >      >     sections >      >      >     in the >      >      >      >>>>                                 draft. >      >      >      >>>>                                 > >      >      >      >>>>                                 > The threads on the >      >     list have >      >      >      >>>>                                 spidered to the >     point >      >     where it is >      >      >      >>>>                                 challenging >      >      >      >>>>                                 > to follow what the >      >     current >      >      >     status >      >      >      >>>>                                 of the draft is, >     or should >      >      >     be.  :-) >      >      >      >>>>                                 > >      >      >      >>>>                                 > However, if I've >      >     followed things >      >      >      >>>>                                 properly, the >     question >      >     below is >      >      >      >>>>                                 really the >      >      >      >>>>                                 > hinge point on >     what our >      >      >      >>>>                                 encapsulation >     for BFD >      >     over vxlan >      >      >      >>>>                                 should look like. >      >      >      >>>>                                 > Correct? >      >      >      >>>>                                 > >      >      >      >>>>                                 > Essentially, >     do we or >      >     do we not >      >      >      >>>>                                 require the >     ability to >      >     permit >      >      >      >>>>                                 multiple BFD >      >      >      >>>>                                 > sessions between >      >     distinct VAPs? >      >      >      >>>>                                 > >      >      >      >>>>                                 > If this is so, >     do we >      >     have a >      >      >     sense >      >      >      >>>>                                 as to how we should >      >     proceed? >      >      >      >>>>                                 > >      >      >      >>>>                                 > -- Jeff >      >      >      >>>>                                 > >      >      >      >>>>                                 > [context preserved >      >     below...] >      >      >      >>>>                                 > >      >      >      >>>>                                 >> Santosh P K >      >      >      >>>>                                 >> >      >      >      >>>>                                 >> On Wed, Sep >     25, 2019 >      >     at 8:10 AM >      >      >      >>>> >       <xiao.min2@zte.com.cn<mailto:xiao.min2@zte.com.cn> <mailto:xiao.min2@zte.com.cn> <mailto:xiao.min2@zte.com.cn <mailto:xiao.min2@zte.com.cn>> >      >     <mailto:xiao.min2@zte.com.cn <mailto:xiao.min2@zte.com.cn> <mailto:xiao.min2@zte.com.cn <mailto:xiao.min2@zte.com.cn>>> >      >      >     <mailto:xiao.min2@zte.com.cn <mailto:xiao.min2@zte.com.cn> >     <mailto:xiao.min2@zte.com.cn <mailto:xiao.min2@zte.com.cn>> <mailto:xiao.min2@zte.com.cn <mailto:xiao.min2@zte.com.cn> >     <mailto:xiao.min2@zte.com.cn <mailto:xiao.min2@zte.com.cn>>>> >      >      >      >>>> >      >       <mailto:xiao.min2@zte.com.cn <mailto:xiao.min2@zte.com.cn> <mailto:xiao.min2@zte.com.cn <mailto:xiao.min2@zte.com.cn>> >     <mailto:xiao.min2@zte.com.cn <mailto:xiao.min2@zte.com.cn> <mailto:xiao.min2@zte.com.cn <mailto:xiao.min2@zte.com.cn>>> >      >      >     <mailto:xiao.min2@zte.com.cn <mailto:xiao.min2@zte.com.cn> >     <mailto:xiao.min2@zte.com.cn <mailto:xiao.min2@zte.com.cn>> <mailto:xiao.min2@zte.com.cn <mailto:xiao.min2@zte.com.cn> >     <mailto:xiao.min2@zte.com.cn <mailto:xiao.min2@zte.com.cn>>>>>> >      >     wrote: >      >      >      >>>>                                 >> >      >      >      >>>>                                 >>> Hi Santosh, >      >      >      >>>>                                 >>> >      >      >      >>>>                                 >>> >      >      >      >>>>                                 >>> With regard >     to the >      >     question >      >      >      >>>>                                 whether we >     should allow >      >      >     multiple BFD >      >      >      >>>>                                 sessions >      >      >      >>>>                                 >>> for the same >     VNI or >      >     not, >      >      >     IMHO we >      >      >      >>>>                                 should allow it, >     more >      >      >     explanation as >      >      >      >>>>                                 >>> follows. >      >      >      >>>>                                 >>> >      >      >      >>>>                                 >>> Below is a >     figure >      >     derived from >      >      >      >>>>                                 figure 2 of >     RFC8014 (An >      >      >     Architecture for >      >      >      >>>>                                 >>> Data-Center >     Network >      >      >      >>>>  Virtualization >     over Layer 3 >      >      >     (NVO3)). >      >      >      >>>>                                 >>> >      >      >      >>>>                                 >>> >              | >      >      >      >>>>                                  Data Center Network >      >     (IP)        | >      >      >      >>>>                                 >>> >              | >      >      >      >>>> >      >             | >      >      >      >>>>                                 >>> >      >      >      >>>> >      >      >       +-----------------------------------------+ >      >      >      >>>>                                 >>> >      >             | >      >      >      >>>> >           | >      >      >      >>>>                                 >>> >      >             | >      >      >      >>>>                                  Tunnel Overlay >          | >      >      >      >>>>                                 >>> >      >      >      >>>> >       +------------+---------+ >      >      >      >>>> >        +---------+------------+ >      >      >      >>>>                                 >>>         | >      >      >      >>>> >       +----------+-------+ | >      >           | >      >      >      >>>> >       +-------+----------+ | >      >      >      >>>>                                 >>> >     | | >      >     Overlay >      >      >      >>>>                                 Module  | | >       | | >      >     Overlay >      >      >      >>>>                                 Module  | | >      >      >      >>>>                                 >>>         | >      >      >      >>>> >       +---------+--------+ | >      >           | >      >      >      >>>> >       +---------+--------+ | >      >      >      >>>>                                 >>>         | >      >           | >      >      >      >>>>                                     |    | >             | >      >      >          | >      >      >      >>>>                                 >>>  NVE1   | >      >           | >      >      >      >>>>                                     |    | >             | >      >      >          | >      >      >      >>>>                                 NVE2 >      >      >      >>>>                                 >>>         | >      >      >      >>>> >       +--------+-------+  | >      >           | >      >      >      >>>> >       +--------+-------+  | >      >      >      >>>>                                 >>> >     |  |VNI1 >      >      >     VNI2  VNI1 >      >      >      >>>>                                 |  |  |  | VNI1 >      >     VNI2 VNI1 >      >      >     |  | >      >      >      >>>>                                 >>>         | >      >      >      >>>> >       +-+-----+----+---+  | >      >           | >      >      >      >>>> >       +-+-----+-----+--+  | >      >      >      >>>>                                 >>> >     |VAP1| >      >     VAP2|    | >      >      >      >>>>                                 VAP3 | >       |VAP1| VAP2| >      >      >       | VAP3| >      >      >      >>>>                                 >>> >      >      >      >>>> >       +----+-----+----+------+ >      >      >      >>>> >        +----+-----+-----+-----+ >      >      >      >>>>                                 >>> >      >       |     | >      >      >        | >      >      >      >>>>        | >      >       |     | >      >      >      >>>>                                 >>> >      >       |     | >      >      >        | >      >      >      >>>>        | >      >       |     | >      >      >      >>>>                                 >>> >      >       |     | >      >      >        | >      >      >      >>>>        | >      >       |     | >      >      >      >>>>                                 >>> >      >      >      >>>> >      >      > >       -------+-----+----+-------------------+-----+-----+------- >      >      >      >>>>                                 >>> >      >       |     | >      >      >        | >      >      >      >>>>  Tenant        | >      >       |     | >      >      >      >>>>                                 >>> >     TSI1 | >      >     TSI2|    | >      >      >      >>>>                                 TSI3 >     TSI1| TSI2| >      >      >       |TSI3 >      >      >      >>>>                                 >>> >      >     +---+ +---+ >      >      >      >>>>                                 +---+ >       +---+ >      >     +---+ >      >      >       +---+ >      >      >      >>>>                                 >>> >      >     |TS1| |TS2| >      >      >      >>>>                                 |TS3| >       |TS4| >      >     |TS5| >      >      >       |TS6| >      >      >      >>>>                                 >>> >      >     +---+ +---+ >      >      >      >>>>                                 +---+ >       +---+ >      >     +---+ >      >      >       +---+ >      >      >      >>>>                                 >>> >      >      >      >>>>                                 >>> To my >      >     understanding, the BFD >      >      >      >>>>                                 sessions between >     NVE1 >      >     and NVE2 are >      >      >      >>>>                                 actually >      >      >      >>>>                                 >>> initiated and >      >     terminated >      >      >     at VAP >      >      >      >>>>                                 of NVE. >      >      >      >>>>                                 >>> >      >      >      >>>>                                 >>> If the >     network operator >      >      >     want to >      >      >      >>>>                                 set up one BFD >     session >      >     between >      >      >     VAP1 of >      >      >      >>>>                                 >>> NVE1 and VAP1of >      >     NVE2, at the >      >      >      >>>>                                 same time >     another BFD >      >     session >      >      >      >>>>                                 between VAP3 of >      >      >      >>>>                                 >>> NVE1 and >     VAP3 of NVE2, >      >      >     although >      >      >      >>>>                                 the two BFD sessions >      >     are for >      >      >     the same >      >      >      >>>>                                 >>> VNI1, I >     believe it's >      >      >     reasonable, >      >      >      >>>>                                 so that's why I >     think we >      >      >     should allow it >      >      >      >>>> >      >      >      >>>> >      >      >       _______________________________________________ >      >      >      >>>>                                 nvo3 mailing list >      >      >      >>>> nvo3@ietf.org<mailto:nvo3@ietf.org> <mailto:nvo3@ietf.org> <mailto:nvo3@ietf.org <mailto:nvo3@ietf.org>> >     <mailto:nvo3@ietf.org <mailto:nvo3@ietf.org> <mailto:nvo3@ietf.org <mailto:nvo3@ietf.org>>> >      >     <mailto:nvo3@ietf.org <mailto:nvo3@ietf.org> <mailto:nvo3@ietf.org <mailto:nvo3@ietf.org>> >     <mailto:nvo3@ietf.org <mailto:nvo3@ietf.org> <mailto:nvo3@ietf.org <mailto:nvo3@ietf.org>>>> <mailto:nvo3@ietf.org <mailto:nvo3@ietf.org> >     <mailto:nvo3@ietf.org <mailto:nvo3@ietf.org>> >      >     <mailto:nvo3@ietf.org <mailto:nvo3@ietf.org> <mailto:nvo3@ietf.org <mailto:nvo3@ietf.org>>> >      >      >     <mailto:nvo3@ietf.org <mailto:nvo3@ietf.org> <mailto:nvo3@ietf.org <mailto:nvo3@ietf.org>> >     <mailto:nvo3@ietf.org <mailto:nvo3@ietf.org> <mailto:nvo3@ietf.org <mailto:nvo3@ietf.org>>>>> >      >      >      >>>> https://www.ietf.org/mailman/listinfo/nvo3<https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/nvo3__;!8WoA6RjC81c!XSnPbDk99ntaSkrho1h-7Nk38vE1gJ9GQ7udWfbGLtCOiKt6Yz9oRI70Dwxv3b_a$> >      >      >      >>>> >      >      > >      > >