Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] Fwd: [babel] RFC 8966 on The Babel Routing Protocol
Date: Mon, 11 Jan 2021 13:05:58 -0800	[thread overview]
Message-ID: <CAA93jw4J4TPtk5Z813fAHhuS3cD40ZsJmUECD1oTdYk07gJx3g@mail.gmail.com> (raw)
In-Reply-To: <20210111203843.09F45F40765@rfc-editor.org>

I thought it would never happen.

---------- Forwarded message ---------
From: <rfc-editor@rfc-editor.org>
Date: Mon, Jan 11, 2021 at 12:40 PM
Subject: [babel] RFC 8966 on The Babel Routing Protocol
To: <ietf-announce@ietf.org>, <rfc-dist@rfc-editor.org>
Cc: <drafts-update-ref@iana.org>, <babel@ietf.org>, <rfc-editor@rfc-editor.org>


A new Request for Comments is now available in online RFC libraries.


        RFC 8966

        Title:      The Babel Routing Protocol
        Author:     J. Chroboczek,
                    D. Schinazi
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2021
        Mailbox:    jch@irif.fr,
                    dschinazi.ietf@gmail.com
        Pages:      54
        Obsoletes:  RFC 6126, RFC 7557

        I-D Tag:    draft-ietf-babel-rfc6126bis-20.txt

        URL:        https://www.rfc-editor.org/info/rfc8966

        DOI:        10.17487/RFC8966

Babel is a loop-avoiding, distance-vector routing protocol that is
robust and efficient both in ordinary wired networks and in wireless
mesh networks.  This document describes the Babel routing protocol
and obsoletes RFC 6126 and RFC 7557.

This document is a product of the Babel routing protocol Working Group
of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
babel mailing list
babel@ietf.org
https://www.ietf.org/mailman/listinfo/babel


-- 
"For a successful technology, reality must take precedence over public
relations, for Mother Nature cannot be fooled" - Richard Feynman

dave@taht.net <Dave Täht> CTO, TekLibre, LLC Tel: 1-831-435-0729

       reply	other threads:[~2021-01-11 21:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210111203843.09F45F40765@rfc-editor.org>
2021-01-11 21:05 ` Dave Taht [this message]
2021-01-11 21:14   ` Dave Taht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAA93jw4J4TPtk5Z813fAHhuS3cD40ZsJmUECD1oTdYk07gJx3g@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox