IETF Logo Mail Archive

Re: [babel] info-model: message log

Juliusz Chroboczek <jch@irif.fr> Thu, 03 January 2019 16:46 UTC

Return-Path: <jch@irif.fr>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40F9C131169 for <babel@ietfa.amsl.com>; Thu, 3 Jan 2019 08:46:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 KTiFQiZIgmgo for <babel@ietfa.amsl.com>; Thu, 3 Jan 2019 08:46:29 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2441C131159 for <babel@ietf.org>; Thu, 3 Jan 2019 08:46:28 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/82085) with ESMTP id x03GkI8C004106; Thu, 3 Jan 2019 17:46:18 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id D8B6D3E429; Thu, 3 Jan 2019 17:46:23 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id jNDj-IbbU67O; Thu, 3 Jan 2019 17:46:22 +0100 (CET)
Received: from pirx.irif.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 7E4F23E427; Thu, 3 Jan 2019 17:46:20 +0100 (CET)
Date: Thu, 03 Jan 2019 17:46:20 +0100
Message-ID: <87va35lmeb.wl-jch@irif.fr>
From: Juliusz Chroboczek <jch@irif.fr>
To: Mahesh Jethanandani <mjethanandani@gmail.com>
Cc: "STARK, BARBARA H" <bs7652@att.com>, Babel at IETF <babel@ietf.org>
In-Reply-To: <A52325B6-59E8-433A-8670-DA943B5DAD90@gmail.com>
References: <2D09D61DDFA73D4C884805CC7865E6114DF65C81@GAALPA1MSGUSRBF.ITServices.sbc.com> <87efa9legt.wl-jch@irif.fr> <A52325B6-59E8-433A-8670-DA943B5DAD90@gmail.com>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Thu, 03 Jan 2019 17:46:18 +0100 (CET)
X-Miltered: at korolev with ID 5C2E3C5A.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 5C2E3C5A.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@irif.fr>
X-j-chkmail-Score: MSGID : 5C2E3C5A.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/eeyV4gGXJdHkKfwyZUuhpEC_HEE>
Subject: Re: [babel] info-model: message log
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2019 16:46:31 -0000

> I will not be surprised if Wireshark does not understand Babel protocol,

Both tcpdump and Wireshark understand Babel.  That was one of the first
things we did after we got our first working prototype.

> particularly if no one has defined it in libpcap.

That has nothing to do with libpcap -- libpcap handles Babel packets as it
would any other IPv6 packets, interpreting the application-layer protocol
happens in the application (Wireshark or tcpdump).

-- Juliusz

v2.23.0 | Report a Bug | By Email