Re: WGLC for BFD over Link Aggregate Group Interfaces - ends November 8
Mahesh Jethanandani <mjethanandani@gmail.com> Fri, 01 November 2013 02:10 UTC
Return-Path: <mjethanandani@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 DD84411E8294 for <rtg-bfd@ietfa.amsl.com>; Thu, 31 Oct 2013 19:10:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qJLSz0aeNKZV for <rtg-bfd@ietfa.amsl.com>; Thu, 31 Oct 2013 19:10:50 -0700 (PDT)
Received: from mail-vb0-x234.google.com (mail-vb0-x234.google.com [IPv6:2607:f8b0:400c:c02::234]) by ietfa.amsl.com (Postfix) with ESMTP id 2C97A11E8291 for <rtg-bfd@ietf.org>; Thu, 31 Oct 2013 19:10:49 -0700 (PDT)
Received: by mail-vb0-f52.google.com with SMTP id f13so2854725vbg.11 for <rtg-bfd@ietf.org>; Thu, 31 Oct 2013 19:10:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=NXHj417bbAtmuGpz3L4lQyk9z7NFogIXFJWBFD8k+ZI=; b=zhub4e2f32XLTNJKjxeTbQ3rz2kBZwqlgrnIEnI9w3/n7K2Prev9lTA6Y4/I0weMU3 CFofn9J7Aw1avHQGCTwnlLj+ywhwy9ZNBJDp4xrU5NC4pS0dBPYY/qpyP8Iamj6RuLaF VcBUcvKPZuIcClWX5iwC4bwm4t0+jQMZUszqpPPWyKDyGcwdgd2ll/emhJ4qEMXapflV R3b/T3CRG1Mctgs7aiZIM7HxXD0elWPfg0ESG9aVbmrtU2zq1cMlQrMDgfil/YUvdoxI azeXMzCDkqrM/T+eP2NGM9VDvjtuN3qARWJunfGNSHwaiyYvgy6RS5VxqmCZvhKSR72Q Kt3w==
MIME-Version: 1.0
X-Received: by 10.220.250.4 with SMTP id mm4mr350722vcb.47.1383271848502; Thu, 31 Oct 2013 19:10:48 -0700 (PDT)
Received: by 10.53.13.133 with HTTP; Thu, 31 Oct 2013 19:10:48 -0700 (PDT)
In-Reply-To: <20131031222017.GA4446@pfrc>
References: <20131024191431.GO17538@pfrc> <315041E4211CB84E86EF7C25A2AB583D337EBFB3@xmb-rcd-x15.cisco.com> <425296D4-F96F-49FF-86D2-40737B64E117@gmail.com> <20211F91F544D247976D84C5D778A4C32E4EEE0D@SG70YWXCHMBA05.zap.alcatel-lucent.com> <CAAchPMsYyDTiONE1v=vKsebF8JPnnHiOFWEE_b0uR6zh8W+E=g@mail.gmail.com> <20211F91F544D247976D84C5D778A4C32E4F2A93@SG70YWXCHMBA05.zap.alcatel-lucent.com> <20131031222017.GA4446@pfrc>
Date: Thu, 31 Oct 2013 19:10:48 -0700
Message-ID: <CAAchPMve+_95T-b52=Qdkx8s+yRpQtOhrpRvFi23HJNJ0nBbDA@mail.gmail.com>
Subject: Re: WGLC for BFD over Link Aggregate Group Interfaces - ends November 8
From: Mahesh Jethanandani <mjethanandani@gmail.com>
To: Jeffrey Haas <jhaas@pfrc.org>
Content-Type: multipart/alternative; boundary="089e0160c2dc286a5604ea141383"
Cc: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 01 Nov 2013 02:10:51 -0000
Jeff, My e-mail editor behaves funny so look for comment starting with [mj] On Thu, Oct 31, 2013 at 3:20 PM, Jeffrey Haas <jhaas@pfrc.org> wrote: > For Mahesh, > > On Wed, Oct 30, 2013 at 04:10:51AM +0000, Bhatia, Manav (Manav) wrote: > > > have stood the test of time, like TCP, do not look beyond their own > layers in the frame > > > for validation of a frame. Even if we have breached the OSI layer, at > least we have > > > restricted ourselves to looking at what is in the frame. > > > > This happens all the time. Multicast often takes hints from the data > plane before triggering events in the control plane (pruning the RPT, > sending Register Stop messages, sending ASSERTs, etc). > > I want to strongly support this point since it seems to be the big item of > contention here. IP implementations have been able to tell what interface > datagram protocols come in for a rather long time. > > If you were to base your argument largely upon this point, you'll have to > throw out a large chunk of deployed multicast protocols. :-) > > FYI: > http://linux.die.net/man/7/ip - see IP_PKTINFO > > > The other would be use the individual link MAC address as a way to > co-relate a BFD packet to > > > a particular link both to set up a BFD session (when the discriminator > is zero) and for future validation > > > > This is precisely what I had meant by this being an implementation > specific issue. Your implementation can always look at the dest MAC to > figure out the link that the packet arrived on. It doesn't make sense to > explicitly state this in the draft since this is an implementation specific > issue. There are several devices that may use a chassis MAC address and MAY > not allocate a unique MAC per link. > > The draft effectively says "figure out what interface it came in on". If a > given implementation of an IP stack has deficiencies compared to others, > there are options. The real question is whether the text is clear enough > about this point. > [mj] My last e-mail effectively suggests just that. If the draft says, figure out for yourself which member link a particular BFD frame came on, it would be fine. It is the implication (and where the text could be more clear), that it is the ifIndex that the system MUST match against, is where I had a problem. How systems map the frame to a member link is an implementation level detail which is outside the scope of this draft. I suggested some text, but it is just that. > -- Jeff > -- Mahesh Jethanandani mjethanandani@gmail.com
- WGLC for BFD over Link Aggregate Group Interfaces… Jeffrey Haas
- Re: WGLC for BFD over Link Aggregate Group Interf… Henderickx, Wim (Wim)
- Re: WGLC for BFD over Link Aggregate Group Interf… Jeff Tantsura
- RE: WGLC for BFD over Link Aggregate Group Interf… Bhatia, Manav (Manav)
- Re: WGLC for BFD over Link Aggregate Group Interf… Srihari Raghavan (srihari)
- Re: WGLC for BFD over Link Aggregate Group Interf… Marc Binderberger
- Re: WGLC for BFD over Link Aggregate Group Interf… Shishio Tsuchiya
- RE: WGLC for BFD over Link Aggregate Group Interf… Vengada Prasad Govindan (venggovi)
- Re: WGLC for BFD over Link Aggregate Group Interf… Mahesh Jethanandani
- RE: WGLC for BFD over Link Aggregate Group Interf… Bhatia, Manav (Manav)
- Re: WGLC for BFD over Link Aggregate Group Interf… Carlos Pignataro (cpignata)
- Re: WGLC for BFD over Link Aggregate Group Interf… Mahesh Jethanandani
- RE: WGLC for BFD over Link Aggregate Group Interf… Bhatia, Manav (Manav)
- Re: WGLC for BFD over Link Aggregate Group Interf… Marc Binderberger
- RE: WGLC for BFD over Link Aggregate Group Interf… Marc Binderberger
- Re: WGLC for BFD over Link Aggregate Group Interf… Mahesh Jethanandani
- Re: WGLC for BFD over Link Aggregate Group Interf… Jeffrey Haas
- Re: WGLC for BFD over Link Aggregate Group Interf… Mahesh Jethanandani
- Re: WGLC for BFD over Link Aggregate Group Interf… Marc Binderberger
- Re: WGLC for BFD over Link Aggregate Group Interf… Mahesh Jethanandani
- Re: WGLC for BFD over Link Aggregate Group Interf… Marc Binderberger
- RE: WGLC for BFD over Link Aggregate Group Interf… Bhatia, Manav (Manav)
- WGLC for BFD over Link Aggregate Group Interfaces… Ashesh Mishra
- Re: WGLC for BFD over Link Aggregate Group Interf… Marc Binderberger
- RE: WGLC for BFD over Link Aggregate Group Interf… Ashesh Mishra
- Re: WGLC for BFD over Link Aggregate Group Interf… Glen Kent
- Re: WGLC for BFD over Link Aggregate Group Interf… Carlos Pignataro (cpignata)
- RE: WGLC for BFD over Link Aggregate Group Interf… Nobo Akiya (nobo)