Re:IETF 108 candidate minutes

xiao.min2@zte.com.cn Fri, 31 July 2020 09:12 UTC

Return-Path: <xiao.min2@zte.com.cn>
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 BAEF53A114E for <rtg-bfd@ietfa.amsl.com>; Fri, 31 Jul 2020 02:12:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.917
X-Spam-Level:
X-Spam-Status: No, score=-1.917 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 yl8CkYWTuiMD for <rtg-bfd@ietfa.amsl.com>; Fri, 31 Jul 2020 02:12:32 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.217.80.70]) (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 53B743A1148 for <rtg-bfd@ietf.org>; Fri, 31 Jul 2020 02:12:31 -0700 (PDT)
Received: from mse-fl1.zte.com.cn (unknown [10.30.14.238]) by Forcepoint Email with ESMTPS id BD58F1E54EE5F59EAEC0; Fri, 31 Jul 2020 17:12:29 +0800 (CST)
Received: from njxapp05.zte.com.cn ([10.41.132.204]) by mse-fl1.zte.com.cn with SMTP id 06V9Bq1A070746; Fri, 31 Jul 2020 17:11:53 +0800 (GMT-8) (envelope-from xiao.min2@zte.com.cn)
Received: from mapi (njxapp03[null]) by mapi (Zmail) with MAPI id mid201; Fri, 31 Jul 2020 17:11:52 +0800 (CST)
Date: Fri, 31 Jul 2020 17:11:52 +0800 (CST)
X-Zmail-TransId: 2afb5f23e05859240e94
X-Mailer: Zmail v1.0
Message-ID: <202007311711528567034@zte.com.cn>
In-Reply-To: <2DFF0B9F-7D70-4239-B79A-2B91C3E69896@pfrc.org>
References: 2DFF0B9F-7D70-4239-B79A-2B91C3E69896@pfrc.org
Mime-Version: 1.0
From: <xiao.min2@zte.com.cn>
To: <jhaas@pfrc.org>
Cc: <rtg-bfd@ietf.org>
Subject: =?UTF-8?B?UmU6SUVURiAxMDggY2FuZGlkYXRlIG1pbnV0ZXM=?=
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl1.zte.com.cn 06V9Bq1A070746
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/fe02fy5nYyTobuN8Nh2o98AXboE>
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: Fri, 31 Jul 2020 09:12:36 -0000

Hi Jeff,






I think the candidate minutes reflect the discussion during the BFD session very well, and I have no suggestion for revision on it.


Just a comment w.r.t BFD for Geneve to test non-management VNI, we have been attempting to address the issues found by IESG discussion on BFD for VXLAN.


The latest draft can be found with below link.


https://tools.ietf.org/html/draft-xiao-nvo3-bfd-geneve-03 


Let's discuss it in more detail on NVO3 mailing list :-)






Best Regards,


Xiao Min



原始邮件



发件人:JeffreyHaas <jhaas@pfrc.org>
收件人:rtg-bfd@ietf.org <rtg-bfd@ietf.org>rg>;
日 期 :2020年07月31日 00:12
主 题 :IETF 108 candidate minutes


https://datatracker.ietf.org/doc/minutes-108-bfd/
The following are the candidate minutes for the IETF 108 BFD session.  Please provide feedback to the mailing list.

-- Jeff and Reshad


# BFD IETF 108 - July 30, 2020 - 13:00-13:50 UTC

Chairs: Jeffrey Haas, Reshad Rahman

# Agenda:

## Chairs update:

  10 mins - Jeff Haas & Reshad Rahman

**Greg Mirsky** asks about bfd 2.0.

**Jeff Haas** answers we're likely rechartering to tighten our charter to the core continuity check (CC) case.  We're likely to try to spin off the other inter-system protocol machinery for other state to another WG or BoF depending on interest.  IESG was luke-warm about this option, at best.  WG would happily help in such a spin-off.

----

## BFD for VxLAN:

  5 minutes - Greg Mirsky
  
**Matthew Bocci** asks about BFD in Geneve.  Question about testing to individual VNIs.  Also questions about issues related to ECMP.

**Greg Mirsky** notes that we're focusing on management VNI case.

**Reshad Rahman** asks about MAC assignments for non-management cases.

**Jeff Haas** WG had discussed the more general case for testing to VNI.  Decided to leave it out of scope based on IESG discussions on security issues.  However, the packet format is likely general enough for the test to the VNI case, but is out of scope for our document. These issues also applies to BFD for Geneve

Greg and Xiao are working on Geneve, so the Geneve document will pick up the relevant changes from WGLC discussion for vxlan document.

----

## BFD padding alteration (draft-xiao-bfd-padding-alteration):

  10 minutes - Xiao Min

**Santosh Pallagati**: How does poll and final interact with timers.  How long do we do poll/final sequence?

**Xiao Min**: Should be very quick.

**Santosh Pallagati**: This is just for negotiating large packets on.

**Reshad Rahman**: Followup - scheduled packet, large packet sent in next interval, verify that you get f-bit back.  Some implementations have policers; 1 packet ever X ms, we may see more.  We may see drops of BFD packets?  Having reviewed BFD instability draft, this may show up as instability.

**Xiao Min**: Extra padding poll can be sent more than once.

**Jeff Haas**: Poll continues until the the poller decides it is done. 

**Greg Mirsky**: Poll is one packet per second?

**Jeff Haas**: Poll actually for the rate that the session is currently running. pps is limiting factor for most bfd implementations.  bfd large changes bps as well.  That may interact poorly with policers?

**Reshad Rahman**: Have you considered instead of on top of small packet doing poll on just large packet?

**Xiao Min**: Intent is to keep bfd running when trying to toggle mode.

**Reshad Rahman**: You could replace a regular packet with a padded packet. Concern that it could cause a BFD session to fail?

**Jeff Haas** (speaking as BFD large packet author): Would you (Xiao) consider merging into bfd large? 

**Xiao Min**: Yes.

**Jeff Haas**: Need to discuss requirements for operators that need the large packet feature always on vs. negotiated.

----

## BFD unaffiliated echo (draft-cw-bfd-unaffiliated-echo):

  10 minutes  - Weiqiang Cheng

**Weiqiang Cheng**: Procedural text in BBF document is unclear.

**Rakesh Gandhi**: We are doing similar things with TWAMP for responder/reflector.  Does this means we'll update 5880?

**Weiqiang Cheng**: Is aware of TWAMP.  Don't have to change BFD solution. Don't need to change remote implementation.  It's just configuration.

**Jeff Haas**: This is different from BBF in that we're talking about a BFD implementation on the receiver. This would update 5880 if so.

**Greg Mirsky**: Clarify on multiplexing on sessions for sender/receiver. System assigns discriminator to the session - and it goes into the packet.

**Jaganbabu Rajamanickam** (Cisco): Is this same as S-BFD?

**Greg Mirsky**: Reflector (learned via IGP, etc.) has an active role in BFD.  This proposal uses transport layer looping.

**Jaganbabu Rajamanickam**: Could be loopback in data path. 

**Greg Mirsky**: And therefore it's echo mode.

**Xiao Min**: The BFD echo is actually a control packet.

**Greg Mirsky**: If you're running multiple sessions, you'll want to demux them.  The contents of the packet matters then.

**Jeff Haas**: Hum for adoption. Hum was panissimo - will take this further to the mailing list.

-----

## Actions for after IETF:

- Submit BFD for vxlan to IESG

- Submit BFD Unsolicited to IESG

- Try to get last updates on BFD Authentication documents to respond to shepherd reviews.  Submit to IESG.

- Update BFD Large Packets per WG discussion. Discuss whether we're submitting or holding back for further work.

- Update working group about chartering discussion for bfd v2/extended.

- Start adoption conversation for BFD unaffiliated.