Re: [rbridge] draft-tissa-trill-oam-03 : ICMP vs RFC 4379 message channel
Jon Hudson <jon.hudson@gmail.com> Sat, 31 March 2012 10:30 UTC
Return-Path: <rbridge-bounces@postel.org>
X-Original-To: ietfarch-trill-archive-Osh9cae4@ietfa.amsl.com
Delivered-To: ietfarch-trill-archive-Osh9cae4@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D35F21F870F for <ietfarch-trill-archive-Osh9cae4@ietfa.amsl.com>; Sat, 31 Mar 2012 03:30:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.682
X-Spam-Level:
X-Spam-Status: No, score=-5.682 tagged_above=-999 required=5 tests=[AWL=0.916, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 CaDYIDXfb5XK for <ietfarch-trill-archive-Osh9cae4@ietfa.amsl.com>; Sat, 31 Mar 2012 03:30:49 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id C090D21F86F2 for <trill-archive-Osh9cae4@lists.ietf.org>; Sat, 31 Mar 2012 03:30:48 -0700 (PDT)
Received: from boreas.isi.edu (localhost [127.0.0.1]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id q2VA6IMH001232; Sat, 31 Mar 2012 03:06:20 -0700 (PDT)
Received: from mail-lpp01m010-f52.google.com (mail-lpp01m010-f52.google.com [209.85.215.52]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id q2VA5kN9001182 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <rbridge@postel.org>; Sat, 31 Mar 2012 03:05:56 -0700 (PDT)
Received: by lahi5 with SMTP id i5so2865995lah.39 for <rbridge@postel.org>; Sat, 31 Mar 2012 03:05:45 -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=HMoJOki4NxBYfMrvB6MetgmGjCNbtwOdNjqX8cdFyOw=; b=vyN5HZK+yikokrUN0fWX2aqwo5TGA9In03knWdHYcHeS4n0tKf7bGAd0V3TJ9EFkR1 +kjTvLlmj9gq/7pYYZIBNGzgvQ+JniPG6UwnGKA1NjAtJDrhJ7/473uYvAkXleLWhaIe Df2NCGXIP7xfY36/X4MRsHy8alyydvQiKu+ICJnF7Ajmvczrh4tMoq904ar1/xoVT3Tu 1f/x4BlfLtYSRPGzra1xuvijtwyqc5DWUAcNiNz29U2GYLJ6LD44L0uYcXWUA+XVZy4Y 3gYkCb65Bp/degC/6wxCvtrkakPlWonITfJMpxYk6wL0JsH/6ZfoHWuHNLdkAL1nEn2m 9BfA==
MIME-Version: 1.0
Received: by 10.152.147.100 with SMTP id tj4mr656538lab.39.1333188345228; Sat, 31 Mar 2012 03:05:45 -0700 (PDT)
Received: by 10.112.130.197 with HTTP; Sat, 31 Mar 2012 03:05:45 -0700 (PDT)
In-Reply-To: <7A958C02-3E5F-4F18-8BCB-3A63F76D8E18@gmail.com>
References: <344037D7CFEFE84E97E9CC1F56C5F4A5AD91C2@xmb-sjc-214.amer.cisco.com> <CAOyVPHRxasYYWxQP3uKLYRVV4vyr6GBRjiJLfni_4jc9jfhvdw@mail.gmail.com> <7A958C02-3E5F-4F18-8BCB-3A63F76D8E18@gmail.com>
Date: Sat, 31 Mar 2012 03:05:45 -0700
Message-ID: <CANbjNQFXXuQ1g2hTqgjmwN9RpnC+vCna5rc-OV8zCFrj3s8RBA@mail.gmail.com>
From: Jon Hudson <jon.hudson@gmail.com>
To: Sam Aldrin <aldrin.ietf@gmail.com>, "Tissa Senevirathne (tsenevir)" <tsenevir@cisco.com>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: jon.hudson@gmail.com
Cc: Vishwas Manral <vishwas.ietf@gmail.com>, "rbridge@postel.org" <rbridge@postel.org>
Subject: Re: [rbridge] draft-tissa-trill-oam-03 : ICMP vs RFC 4379 message channel
X-BeenThere: rbridge@postel.org
X-Mailman-Version: 2.1.6
Precedence: list
List-Id: "Developing a hybrid router/bridge." <rbridge.postel.org>
List-Unsubscribe: <http://mailman.postel.org/mailman/listinfo/rbridge>, <mailto:rbridge-request@postel.org?subject=unsubscribe>
List-Archive: <http://mailman.postel.org/pipermail/rbridge>
List-Post: <mailto:rbridge@postel.org>
List-Help: <mailto:rbridge-request@postel.org?subject=help>
List-Subscribe: <http://mailman.postel.org/mailman/listinfo/rbridge>, <mailto:rbridge-request@postel.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2039775657=="
Sender: rbridge-bounces@postel.org
Errors-To: rbridge-bounces@postel.org
The number one concern I hear from Users about anything UDP is that it can be dropped and is stateless. (big issue with VXLAN) As this is the same for ICMP I see no practical difference to the User which one is used. On Fri, Mar 2, 2012 at 10:47 AM, Sam Aldrin <aldrin.ietf@gmail.com> wrote: > Do not have much preference of reusing the same port or not. With a > programmer hat on, who developed rfc4379 and it's implementation, it will > be klugy, and have issues when process is/was implemented in h.w. For ex: > had issue with vccv when used by lsp ping and bfd, due to incompatible > hardware in the network. > Having said that, idea is to use similar message or tlv formats, will help > immensely in adopting the standard. > > Cheers > Sam > > Sent from my iPad > > On Mar 2, 2012, at 10:11 AM, Vishwas Manral <vishwas.ietf@gmail.com> > wrote: > > Hi Tissa, > > I am not sure we would want to use the same port for de-multiplexing MPLS > OAM and UDP based TRILL OAM packets. > > On another note, I do know that folks use different channels for testing > real application behavior in current networks. So yes UDP based channels > should be good too. > > My biggest concern is that we should not have different message formats > when the application works over different layers. It is for that reason > that BFD has been so successful (the same message format/ state machine) > irrespective of the lower layer protocol. > > Thanks, > Vishwas > > On Fri, Mar 2, 2012 at 8:08 AM, Tissa Senevirathne (tsenevir) < > tsenevir@cisco.com> wrote: > >> Dear All**** >> >> ** ** >> >> Current draft-tissa-till-oam utilize ICMP extensions defined in RFC 4884. >> I have also heard preference of using UDP based messaging channel defined >> in RFC 4379.**** >> >> ** ** >> >> Advantage of using RFC 4379 methods is we can utilize the same framework >> and OAM challenges in TRILL and MPLS world are similar. However, we need to >> define new TLV series and message types. Question arise whether we should >> use the same wellknown UDP port used in MPLS OAM or a use a different UDP >> port.**** >> >> ** ** >> >> Advantage of ICMP method is we are utilizing the ICMP infrastructure that >> is commonly utilized in IP world. However, we need to define RFC 4884 >> extensions and it also heavily depends on acceptance of individual >> submission draft-shen-traceroute-ping-ext-04.**** >> >> ** ** >> >> Would like to see the preference from the WG on specific method over the >> other ?**** >> >> ** ** >> >> Thanks**** >> >> Tissa**** >> >> > _______________________________________________ > rbridge mailing list > rbridge@postel.org > http://mailman.postel.org/mailman/listinfo/rbridge > > > _______________________________________________ > rbridge mailing list > rbridge@postel.org > http://mailman.postel.org/mailman/listinfo/rbridge > > -- "Do not lie. And do not do what you hate."
_______________________________________________ rbridge mailing list rbridge@postel.org http://mailman.postel.org/mailman/listinfo/rbridge
- [rbridge] draft-tissa-trill-oam-03 : ICMP vs RFC … Tissa Senevirathne (tsenevir)
- Re: [rbridge] draft-tissa-trill-oam-03 : ICMP vs … Sam Aldrin
- Re: [rbridge] draft-tissa-trill-oam-03 : ICMP vs … Vishwas Manral
- Re: [rbridge] draft-tissa-trill-oam-03 : ICMP vs … Sam Aldrin
- Re: [rbridge] draft-tissa-trill-oam-03 : ICMP vs … Jon Hudson