Re: Last Call: draft-ietf-rtgwg-ipfrr-spec-base (Basic Specification for IP ...
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Last Call: draft-ietf-rtgwg-ipfrr-spec-base (Basic Specification for IP ...
Beginning
Stewart
HeinerHummel at aol.com wrote:
> Question: Is the accomplishment of this document considered to be the
> end or rather the beginning of activities on the rerouting topic ?
>
> Heiner
>
> In einer eMail vom 29.04.2008 22:35:53 Westeuropäische Normalzeit
> schreibt iesg-secretary at ietf.org:
>
> The IESG has received a request from the Routing Area Working
> Group WG
> (rtgwg) to consider the following document:
>
> - 'Basic Specification for IP Fast-Reroute: Loop-free Alternates '
> <draft-ietf-rtgwg-ipfrr-spec-base-12.txt> as a Proposed SFrom rtgwg-bounces at ietf.org Wed Apr 30 05:40:53 2008
Return-Path: <rtgwg-bounces at ietf.org>
X-Original-To: rtgwg-archive at optimus.ietf.org
Delivered-To: ietfarch-rtgwg-archive at core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 624D83A6E2E;
Wed, 30 Apr 2008 05:40:53 -0700 (PDT)
X-Original-To: rtgwg at core3.amsl.com
Delivered-To: rtgwg at core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id BCFA23A6917;
Wed, 30 Apr 2008 05:40:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id qe2O+l1TMahf; Wed, 30 Apr 2008 05:40:47 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
by core3.amsl.com (Postfix) with ESMTP id E6DC73A6B72;
Wed, 30 Apr 2008 05:40:46 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.25,728,1199660400";
d="scan'208";a="7722871"
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
by ams-iport-1.cisco.com with ESMTP; 30 Apr 2008 14:40:48 +0200
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m3UCemkN028558;
Wed, 30 Apr 2008 14:40:48 +0200
Received: from dhcp-gpk02-vlan300-64-103-65-18.cisco.com
(dhcp-gpk02-vlan300-64-103-65-18.cisco.com [64.103.65.18])
by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m3UCemPx012293;
Wed, 30 Apr 2008 12:40:48 GMT
Message-ID: <481868CF.3010407 at cisco.com>
Date: Wed, 30 Apr 2008 13:40:47 +0100
From: Stewart Bryant <stbryant at cisco.com>
User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213)
MIME-Version: 1.0
To: HeinerHummel at aol.com
Subject: Re: Last Call: draft-ietf-rtgwg-ipfrr-spec-base (Basic Specification
for IP ...
References: <c23.36a7df5f.35499fb2 at aol.com>
In-Reply-To: <c23.36a7df5f.35499fb2 at aol.com>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l55; t09559248;
x10423248; c=relaxed/simple; s=amsdkim2001;
h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
d=cisco.com; i=stbryant at cisco.com;
z=From: Stewart Bryant <stbryant at cisco.com>
|Subject: Re: Last Call: draft-ietf-rtgwg-ipfrr
-spec-base (Basic Specification
for IP ...
|Sender: ; bh=iYFLOd3/d7L3bAAOsr2L7jjefP9ehNuIBOz597Vo8cw=;
b=Z5mN1q24ssK2eWiDHjFIDIU/+jwbv0X4UHwONm/y6gYl7fanrFWo/nUHlH
KHNCdhMJTUPh/Uj2n4tk33Emr/yX5PSDQhtJekyuyAFlEVuWRYqR5WcfwXXK
wVKVokauYm;
Authentication-Results: ams-dkim-2; header.From=stbryant at cisco.com; dkim=pass (
sig from cisco.com/amsdkim2001 verified; );
Cc: ietf at ietf.org, ietf-announce at ietf.org, rtgwg at ietf.org
X-BeenThere: rtgwg at ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: stbryant at cisco.com
List-Id: <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>,
<mailto:rtgwg-request at ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg at ietf.org>
List-Help: <mailto:rtgwg-request at ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>,
<mailto:rtgwg-request at ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: rtgwg-bounces at ietf.org
Errors-To: rtgwg-bounces at ietf.org
Beginning
Stewart
HeinerHummel at aol.com wrote:
> Question: Is the accomplishment of this document considered to be the
> end or rather the beginning of activities on the rerouting topic ?
>
> Heiner
>
> In einer eMail vom 29.04.2008 22:35:53 Westeuropäische Normalzeit
> schreibt iesg-secretary at ietf.org:
>
> The IESG has received a request from the Routing Area Working
> Group WG
> (rtgwg) to consider the following document:
>
> - 'Basic Specification for IP Fast-Reroute: Loop-free Alternates '
> <draft-ietf-rtgwg-ipfrr-spec-base-12.txt> as a Proposed Standard
tandard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments
> to the
> ietf at ietf.org mailing lists by 2008-05-13. Exceptionally,
> comments may be sent to iesg at ietf.org instead. In either case, please
> retain the beginning of the Subject line to allow automated sorting.
>
> The file can be obtained via
> http://www.ietf.org/internet-drafts/draft-ietf-rtgwg-ipfrr-spec-base-12.txt
>
>
> IESG discussion can be tracked via
> https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=12272&rfc_flag=0
>
> _______________________________________________
> rtgwg mailing list
> rtgwg at ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> rtgwg mailing list
> rtgwg at ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>
_______________________________________________
rtgwg mailing list
rtgwg at ietf.org
https://www.ietf.org/mailman/listinfo/rtgwg
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments
> to the
> ietf at ietf.org mailing lists by 2008-05-13. Exceptionally,
> comments may be sent to iesg at ietf.org instead. In either case, please
> retain the beginning of the Subject line to allow automated sorting.
>
> The file can be obtained via
> http://www.ietf.org/internet-drafts/draft-ietf-rtgwg-ipfrr-spec-base-12.txt
>
>
> IESG discussion can be tracked via
> https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=12272&rfc_flag=0
>
> _______________________________________________
> rtgwg mailing list
> rtgwg at ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> rtgwg mailing list
> rtgwg at ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>
_______________________________________________
rtgwg mailing list
rtgwg at ietf.org
https://www.ietf.org/mailman/listinfo/rtgwg
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.