Pending issues?

Carlos Garcia Braschi <cgbraschi@gmail.com> Thu, 21 April 2005 13:36 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DObqy-00037D-7T; Thu, 21 Apr 2005 09:36:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DObqw-00036V-Hx for rtg-bfd@megatron.ietf.org; Thu, 21 Apr 2005 09:36:22 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29576 for <rtg-bfd@ietf.org>; Thu, 21 Apr 2005 09:36:21 -0400 (EDT)
Received: from rproxy.gmail.com ([64.233.170.199]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOc2M-0007eT-Lu for rtg-bfd@ietf.org; Thu, 21 Apr 2005 09:48:11 -0400
Received: by rproxy.gmail.com with SMTP id z35so427632rne for <rtg-bfd@ietf.org>; Thu, 21 Apr 2005 06:36:11 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=OL1tbDCNgn9wHr3OytSK6nys5AIeS4Xsu2ygl/N7QhrIIPCKRtySF7YX6h1flujG1v4h50Zk3iY6KilN+oRyk3z8BXbIoLGxIDRpmagKgpw7XU4zf0stQwwLcl2wMgj+D56k2YHHG/kP9RDJNgXmVOwDn4ablVrWI1Y0kqDwHnI=
Received: by 10.38.78.59 with SMTP id a59mr2212957rnb; Thu, 21 Apr 2005 06:36:11 -0700 (PDT)
Received: by 10.38.75.43 with HTTP; Thu, 21 Apr 2005 06:36:11 -0700 (PDT)
Message-ID: <9e31186f050421063668a536eb@mail.gmail.com>
Date: Thu, 21 Apr 2005 15:36:11 +0200
From: Carlos Garcia Braschi <cgbraschi@gmail.com>
To: rtg-bfd@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: quoted-printable
Subject: Pending issues?
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Carlos Garcia Braschi <cgbraschi@gmail.com>
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
Sender: rtg-bfd-bounces@ietf.org
Errors-To: rtg-bfd-bounces@ietf.org

Hi,

After a little action after the IETF meeting, traffic about new
questions regarding the protocol has been dwindling. There seems to be
no pending issues with the current drafts, and little wording to be
added to the drafts (Admin Down issue, AFAIK).
Is there something keeping the drafts from moving forward? (apart from
the workload on the authors, of course :-).

On the other hand, I still do not have a clear understanding on how
the issue of application to static routes, BGP (and I would like also
to add RIP) could be progressed. Last time we wrote about a separate
draft, would it be done in this WG? Or should it go to the home WG of
the routing protocols? (actually it seems only BGP has a WG now...).

For RIP and static routes there does not seem to me to be a need for
changes to be made to the protocols on the wire. I do not know for BGP
(haven't been able to find the details of the proposal), but does not
seem to be needed, either, so this WG could be the place...

Regards,
Carlos.