Re: WG Adoption request for draft-mirsky-bfd-mpls-demand

"Carlos Pignataro (cpignata)" <cpignata@cisco.com> Fri, 26 October 2018 04:04 UTC

Return-Path: <cpignata@cisco.com>
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 7880012F1A6 for <rtg-bfd@ietfa.amsl.com>; Thu, 25 Oct 2018 21:04:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.97
X-Spam-Level:
X-Spam-Status: No, score=-14.97 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 7PMN47GBpUX0 for <rtg-bfd@ietfa.amsl.com>; Thu, 25 Oct 2018 21:04:21 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 849BE12DD85 for <rtg-bfd@ietf.org>; Thu, 25 Oct 2018 21:04:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11632; q=dns/txt; s=iport; t=1540526661; x=1541736261; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=XQdhLDqwI1HGERk4aduEtIxRkFGXOpTKNS+JOwmwDPk=; b=hN4psybCVPws903X9mQtI53Jr+p1ZOn1Q9ki9JHpZpF7KmYd1pDBwikm ZJvBer3bkFxUUa7PIc7H2QeLVW6fws8Gtf3WG0z3npR68kfJuehpRxqeP rHGevrRg4N6gRi3jcGT820MzdqdJfgijVgzzJbSI3kdwxf064ohuiLBQO Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ANAAAdkdJb/5pdJa1jGwEBAQEDAQEBBwMBAQGBUQYBAQELAYENd2Z/KAqDa4gYjBeBaJF3hUqBegsBASOESQIXgnohNA0NAQMBAQIBAQJtHAELhTsGI0sLEAIBBgI/AwICAjAUEQIEDgWDIQGBHWQPi3CbTYEuhCwBEUA9hFwFi2cXgUE/gTgME4JMgSgZAYFZAQECAQGBXIMFMYImAo5GkDUJAoZnihYYgVKEd4l7jGuHKoJUAhEUgSYdOIFVcBU7KgGCQT6BdIhnhT5vAYwJgR8BAQ
X-IronPort-AV: E=Sophos;i="5.54,426,1534809600"; d="scan'208,217";a="192054560"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Oct 2018 04:04:20 +0000
Received: from XCH-RTP-017.cisco.com (xch-rtp-017.cisco.com [64.101.220.157]) by rcdn-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id w9Q44K5D009738 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 26 Oct 2018 04:04:20 GMT
Received: from xch-rtp-020.cisco.com (64.101.220.160) by XCH-RTP-017.cisco.com (64.101.220.157) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Fri, 26 Oct 2018 00:04:19 -0400
Received: from xch-rtp-020.cisco.com ([64.101.220.160]) by XCH-RTP-020.cisco.com ([64.101.220.160]) with mapi id 15.00.1395.000; Fri, 26 Oct 2018 00:04:19 -0400
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: "xiao.min2@zte.com.cn" <xiao.min2@zte.com.cn>
CC: Jeff Haas <jhaas@pfrc.org>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
Subject: Re: WG Adoption request for draft-mirsky-bfd-mpls-demand
Thread-Topic: WG Adoption request for draft-mirsky-bfd-mpls-demand
Thread-Index: AQHUZmhJiwqFodrsXU2xirocEt1c36Unp1uAgAmQ0oA=
Date: Fri, 26 Oct 2018 04:04:18 +0000
Message-ID: <75D9EDEC-68A6-4053-8931-39CFE3CCEA29@cisco.com>
References: <20181017222431.GK17157@pfrc.org> <201810200959390293198@zte.com.cn>
In-Reply-To: <201810200959390293198@zte.com.cn>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-mailer: Apple Mail (2.3445.100.39)
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.118.116.132]
Content-Type: multipart/alternative; boundary="_000_75D9EDEC68A64053893139CFE3CCEA29ciscocom_"
MIME-Version: 1.0
X-Outbound-SMTP-Client: 64.101.220.157, xch-rtp-017.cisco.com
X-Outbound-Node: rcdn-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/luXkh_walm1lqYbZlWy5R2tsNCg>
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, 26 Oct 2018 04:04:24 -0000

Xiao,

Scanning through the draft, two questions:

1. What is the underlying mechanism to check liveness such that Demand can be used?

https://tools.ietf.org/html/rfc5880#section-6.6

   Demand mode requires that some other mechanism is used to imply
   continuing connectivity between the two systems.  The mechanism used


2. Is this draft testing liveness of a path or a node?

https://tools.ietf.org/html/draft-mirsky-bfd-mpls-demand-03#section-3

   In this state BFD peers MAY remain as long as the egress LER is in Up
   state.  The ingress LER MAY check liveness of the egress LER by
   setting the Poll flag.  The egress LER will respond by transmitting


Thanks,

— Carlos Pignataro

On Oct 19, 2018, at 9:59 PM, xiao.min2@zte.com.cn<mailto:xiao.min2@zte.com.cn> wrote:


I support WG adoption of this draft. Use of the demand mode for p2p LSP monitoring is feasible and required.


Best Regards,

Xiao Min

原始邮件
发件人:JeffreyHaas <jhaas@pfrc.org<mailto:jhaas@pfrc.org>>
收件人:rtg-bfd@ietf.org<mailto:rtg-bfd@ietf.org> <rtg-bfd@ietf.org<mailto:rtg-bfd@ietf.org>>;
日 期 :2018年10月18日 06:24
主 题 :WG Adoption request for draft-mirsky-bfd-mpls-demand
Working Group,

The BFD chairs have received an adoption request for
"BFD in Demand Mode over Point-to-Point MPLS LSP"
(draft-mirsky-bfd-mpls-demand).

https://datatracker.ietf.org/doc/draft-mirsky-bfd-mpls-demand/

The adoption call will end on the Friday after IETF 103, November 9.

Note that there is are existing IPR statements on this draft:
https://datatracker.ietf.org/ipr/3301/
https://datatracker.ietf.org/ipr/3104/

Please indicate to the mailing list whether you support adoption of this
draft.

-- Jeff & Reshad