Re: [Bier] draft-ietf-bier-path-mtu-discovery
Greg Mirsky <gregimirsky@gmail.com> Fri, 22 May 2020 15:22 UTC
Return-Path: <gregimirsky@gmail.com>
X-Original-To: bier@ietfa.amsl.com
Delivered-To: bier@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 728C03A0CE0; Fri, 22 May 2020 08:22:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, 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 cfcsisBFWVVL; Fri, 22 May 2020 08:22:08 -0700 (PDT)
Received: from mail-lj1-x22e.google.com (mail-lj1-x22e.google.com [IPv6:2a00:1450:4864:20::22e]) (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 DDE653A0C97; Fri, 22 May 2020 08:21:53 -0700 (PDT)
Received: by mail-lj1-x22e.google.com with SMTP id o14so13137850ljp.4; Fri, 22 May 2020 08:21:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=iyNnfsgB3pjM9sjyi47QjcXpHGv3PEizrj5GsgszwRc=; b=VBLU4ktStNREV4OsMtFyqsJOVYbrEI+Vs762UUt2rx5aO1bpT0dkhFbhbJSReBJjC8 rcDc4U3ioRxvXxsmX0R6iTPZJEbNyZJ7NlPyBklWT5lQo6J59e1jltTNmE9Gb2s1eHCb aXTl14AJZKWRbK4Q4IhVH+cPkzoIB+Tap2JGoms9/E19Wq2iRkDJjpNCkis7APUvu8wm oBEME7fVXAZqZYw9yNovcCh2bkJadEW6SPSWlsH8JWGrGyaKrK3QHqFp+8TiybIqzmOx 40+cxZ4F46jsm3kPe8pGymaJ8nd/PU+yC5Sd0P62Urr2L2Pn0edhh+XrIL3uE3GVfHSm 7+3g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=iyNnfsgB3pjM9sjyi47QjcXpHGv3PEizrj5GsgszwRc=; b=rLkNXIrr9wNCgDqble4ta+IgawtAgg/UZklpUBxl9lLwOBm2exTpt0EOtwGU1NvKs+ qrjq0gHnwvHWsJXkk4YmOS6Ww9LxVDjbU7kwKAeiNAGlrEAhMhSjZpqcqVw/Yqwzz9A8 UoK+ElL75ThmhBMhO7FBr/UyV/nev/gE18sis8aIAh/gjLxy6OgjXP046zpG2vcZI+l2 Ot+vr3iJYKSaTzLRcL3nL91ndhoojyoPf7mT5MKRO7SBNdBKzUsfVMLjP8JtD+5lMmGZ 3XLR4jgBzIy40o+j+7RYFBeFmO0f0h3ghiCg8te0yIIFqfU7PWpdopvbpOnsfrePDQcp 0k4Q==
X-Gm-Message-State: AOAM533mhB51QwPGn++2+Y5l1f6HG2Mb7AnJOgeZFngBOkxFZy//9jKy wXLQAbJVvH4Wr0DWYJokohFQuwuT87NRZxfBphwsJqZ0
X-Google-Smtp-Source: ABdhPJzwsKUd50qLFnYNn2PN/QPYw46+lLyqUDrm99IW6c8rzpMkDqXAVSrg/W6BnD7FTDZbljRZk8m4TM5mCB0uFHY=
X-Received: by 2002:a2e:6c0c:: with SMTP id h12mr7636431ljc.266.1590160911644; Fri, 22 May 2020 08:21:51 -0700 (PDT)
MIME-Version: 1.0
References: <3EFC461E-D68C-4FBC-9147-B7E493BFC314@cisco.com>
In-Reply-To: <3EFC461E-D68C-4FBC-9147-B7E493BFC314@cisco.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Fri, 22 May 2020 08:21:40 -0700
Message-ID: <CA+RyBmVbDSOoMxaP=yF7UwHNKNfCtPNFp1FF-qSpdSbNNBkB=g@mail.gmail.com>
To: "Mankamana Mishra (mankamis)" <mankamis@cisco.com>, BIER WG <bier@ietf.org>
Cc: "draft-ietf-bier-path-mtu-discovery@ietf.org" <draft-ietf-bier-path-mtu-discovery@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000046405605a63e302f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/B11wUnyTaAp-gVkPvxONH3KMR5A>
Subject: Re: [Bier] draft-ietf-bier-path-mtu-discovery
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "\"Bit Indexed Explicit Replication discussion list\"" <bier.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bier>, <mailto:bier-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bier/>
List-Post: <mailto:bier@ietf.org>
List-Help: <mailto:bier-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bier>, <mailto:bier-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 May 2020 15:22:17 -0000
Hi Mankamana, hope this note finds you well. Many thanks for your question. I'd like to have the WG think of it and participate in the discussion. I agree with you that a tracing mechanism, using BIER ping/traceroute Downstream TLV, might be used to execute path MTU discovery. I think I see several challenges to such an approach. Consider that BIER is an overlay and adjacent BFRs might be connected not by a link but a tunnel. Thus, as I think of it, a BFR would be required to discover MTU of all of its interfaces and monitor them at some rate. That might create quite a computational load at the bootup and need to be controlled to avoid synchronization of these PMTUD measurements. Doable but seems quite complicated. What do you think? What do others think? Regards, Greg On Thu, May 21, 2020 at 8:01 PM Mankamana Mishra (mankamis) < mankamis@cisco.com> wrote: > Folks, > May be too late to game. But wondering if BIER ping already provides trace > route functionality which suppose to reply with MTU, what extra this draft > is bringing ? > > Mankamana
- Re: [Bier] draft-ietf-bier-path-mtu-discovery Greg Mirsky