IETF Logo Mail Archive

Re: A question about RFC5884

Santosh P K <santosh.pallagatti@gmail.com> Mon, 17 July 2017 08:58 UTC

Return-Path: <santosh.pallagatti@gmail.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 7BE2C12EC36 for <rtg-bfd@ietfa.amsl.com>; Mon, 17 Jul 2017 01:58:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 aKsjjsigVesi for <rtg-bfd@ietfa.amsl.com>; Mon, 17 Jul 2017 01:58:12 -0700 (PDT)
Received: from mail-ua0-x230.google.com (mail-ua0-x230.google.com [IPv6:2607:f8b0:400c:c08::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E280B12EA7C for <rtg-bfd@ietf.org>; Mon, 17 Jul 2017 01:58:11 -0700 (PDT)
Received: by mail-ua0-x230.google.com with SMTP id 35so40329440uax.3 for <rtg-bfd@ietf.org>; Mon, 17 Jul 2017 01:58:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=xyHHFzmmvk/skmhdUMfo3lWHuuq38vMeF031advGgWs=; b=YxpTAey0nFA14kjE2h946GN0BWfZTL8FgM3h86sW4wJY4Lj3tPokgPKapeS6h5/BT9 dXiAQB//9VNZCXxFBlui8RutA7+mzm3RC3PMDgvboBU+rO7jA+UvruQdwj0QRJpkiAMk GNnZY/r7/njhwMXJLoJZrSexhL7YF0jvrta3MACuWxfPN65HZP7xNznxVuBpWWutBwEN BJn5gTOufpiyRAMlcynKF6/V+5zjJ8WLQqkyNXxaNuWcqcev1cLTl6I/WXOBIPvmhZB/ NXhQ2D8DPGjKBfv3jez4yxcU3JBm1RMAzlqjB6QtWCLbNTDWbW41y0meQv92+d4gDh4N 7taQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=xyHHFzmmvk/skmhdUMfo3lWHuuq38vMeF031advGgWs=; b=AP2ZM0YCY1+8Mip/GJXN1s3YQ9EFoxCXvtQuSqffu8/6twtrS5FCo7hoz70mGi0KII gPV5NuYJ4JQPDl3hAreAEUyV0fn2XkEr0EySkmIHj5fwizU08numbbRXFPm7TDPHtUbe TYPaq2T21HFxGHn65lG9hh/jkYQynBndJs8MHh0xwssifWcez/Zq9pIziG4GOS/0CUw2 mMJ31t5odxTQww2pVOb2yInoglwGcimk7XjbHdq3yholzClJhsEsXSmPvgR2G2MZ/fYm GCI1XlqORS2LAlJ7t1PfQrzZe6mj+4Mn139TR8VME9B81TtzoMPyhs/smvFB1TUCl+Kc 6blQ==
X-Gm-Message-State: AIVw110VLITpNM3TFiFPgx+/9tUx7NHwj3HiCMJ/Q+RmIbG3BsRv0D34 YkgBdwomuaJ8tGYqeO3Tpcc6Vk4Yfg==
X-Received: by 10.31.16.22 with SMTP id g22mr12174797vki.46.1500281890992; Mon, 17 Jul 2017 01:58:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.103.148.27 with HTTP; Mon, 17 Jul 2017 01:58:10 -0700 (PDT)
In-Reply-To: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE291842ADE@dggeml508-mbx.china.huawei.com>
References: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE291842ADE@dggeml508-mbx.china.huawei.com>
From: Santosh P K <santosh.pallagatti@gmail.com>
Date: Mon, 17 Jul 2017 14:28:10 +0530
Message-ID: <CACi9rdvUZKWgghHUvnzR_kijzs_3kdRb3C3OG2upBjpd-C23qA@mail.gmail.com>
Subject: Re: A question about RFC5884
To: Mach Chen <mach.chen@huawei.com>
Cc: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
Content-Type: multipart/alternative; boundary="001a114362182cf67405547f9922"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/dCm8hyX6h6-BqiCjQkLJ2JVjI6g>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 17 Jul 2017 08:58:13 -0000

I read it as Local discriminator assigned for a BDS session is optional in
echo reply that is being sent in response to LSP ping echo. I don't think
RFC 5884 is not talking about echo reply being optional.

Thanks
Santosh P K

On Sun, Jul 16, 2017 at 7:28 PM, Mach Chen <mach.chen@huawei.com> wrote:

> Hi BFDers,
>
> We met a multi-vendor interoperate issue recently, it's about whether an
> Echo reply is necessary.
>
> In Section 6 of RFC5884, 2nd paragraph
>
> "... The egress LSR MAY respond with an LSP Ping Echo
>    reply message that carries the local discriminator assigned by it for
>    the BFD session."
>
> >From the above text, my understanding is that an Echo reply is optional,
> the egress LSR can freely to return or not return an Echo reply, and the
> Ingress LSR should not expect there MUST be an Echo reply, but if there is
> one, it should handle it properly.
>
> Is my understanding correct?
>
> Thanks,
> Mach
>
>

v2.23.0 | Report a Bug | By Email