From routing-discussion-bounces@ietf.org  Tue Feb  1 09:21:02 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07604
	for <routing-discussion-archive@lists.ietf.org>; Tue, 1 Feb 2005 09:21:02 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CvylI-0007sZ-RQ; Tue, 01 Feb 2005 09:12:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cvyhm-0006zW-3x
	for routing-discussion@megatron.ietf.org;
	Tue, 01 Feb 2005 09:08:35 -0500
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 JAA04742
	for <routing-discussion@ietf.org>; Tue, 1 Feb 2005 09:08:31 -0500 (EST)
Received: from dns.nexthop.com ([65.247.36.216] helo=aa-mx1.nexthop.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cvyzv-0002e6-96
	for routing-discussion@ietf.org; Tue, 01 Feb 2005 09:27:20 -0500
Received: from localhost (localhost [127.0.0.1])
	by aa-mx1.nexthop.com (Postfix) with ESMTP
	id 5184F2D4AF1; Tue,  1 Feb 2005 09:08:01 -0500 (EST)
Received: from aa-mx1.nexthop.com ([127.0.0.1])
	by localhost (aa-mx1.nexthop.com [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id 42456-01-44; Tue,  1 Feb 2005 09:08:00 -0500 (EST)
Received: from jhaas.nexthop.com (jhaas.nexthop.com [65.247.36.31])
	by aa-mx1.nexthop.com (Postfix) with ESMTP
	id 269792D4AAD; Tue,  1 Feb 2005 09:08:00 -0500 (EST)
Received: (from jhaas@localhost)
	by jhaas.nexthop.com (8.11.6/8.11.6) id j11E7xX08822;
	Tue, 1 Feb 2005 09:07:59 -0500 (EST)
Date: Tue, 1 Feb 2005 09:07:59 -0500
From: Jeffrey Haas <jhaas@nexthop.com>
To: Curtis Villamizar <curtis@faster-light.net>
Message-ID: <20050201140759.GZ3965@nexthop.com>
References: <B53A8EFF919E0A4BA9EC42775D99C47002EDE969@EXCH-CLUSTER-01.force10networks.com>
	<200501230040.j0N0eEFV001169@workhorse.faster-light.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200501230040.j0N0eEFV001169@workhorse.faster-light.net>
User-Agent: Mutt/1.4.2.1i
X-Virus-Scanned: by amavisd-new at nexthop.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: routing-discussion@ietf.org, Jason Chen <jason@force10networks.com>
Subject: Re: question on RFC1771 9.1.3
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org

I could swear that I answered this recently, but it may have been off-list.

Draft-06 of MSDP at one point required BGP to reflect it's route back,
much like DVMRP, to signal that the route is the route being used for
RPF.  This was used by the peer-flooding mechanism of MSDP.

Later versions of the draft, and also the current updated MSDP draft
do not seem to require this, although those drafts will still use the
contents of the AS_PATH database.

On Sat, Jan 22, 2005 at 07:40:14PM -0500, Curtis Villamizar wrote:
> In message <B53A8EFF919E0A4BA9EC42775D99C47002EDE969@EXCH-CLUSTER-01.force10networks.com>
> "Jason Chen" writes:
> >  
> >  
> > Hi,
> >  
> > Can someone enlighten me on one paragraph on BGP RFC 1771 ?
> >  
> >    For the benefit of future support of inter-AS multicast capabilities,
> >    a BGP speaker that participates in inter-AS multicast routing shall
> >    advertise a route it receives from one of its external peers and if
> >    it installs it in its Loc-RIB, it shall advertise it back to the peer
> >    from which the route was received. For a BGP speaker that does not
> >    participate in inter-AS multicast routing such an advertisement is
> >    optional."
> >  
> > I cannot figure out where it applied to and how it works? Is this
> > mandatory requirement for supporting MSDP?
> >  
> > Appreciate for the help.
> >  
> > Jason
> 
> 
> 
> Jason,
> 
> At the risk of being proven wrong ...
> 
> I think that is left over from the days of Multicast BGP and MOSPF.
> I'm not sure if it is still needed.  In any case it doesn't hurt.  If
> you don't use Multicast BGP, and no one does, then don't bother with
> this advertisement.
> 
> Does anyone think this is needed?

-- 
Jeff Haas 
NextHop Technologies

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Wed Feb  2 18:37:44 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26995
	for <routing-discussion-archive@lists.ietf.org>; Wed, 2 Feb 2005 18:37:44 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CwTw6-0001PE-LX; Wed, 02 Feb 2005 18:29:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CwToH-0006fr-Lb
	for routing-discussion@megatron.ietf.org;
	Wed, 02 Feb 2005 18:21:21 -0500
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 SAA25664
	for <routing-discussion@ietf.org>; Wed, 2 Feb 2005 18:21:16 -0500 (EST)
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwU6i-0006Mi-P4
	for routing-discussion@ietf.org; Wed, 02 Feb 2005 18:40:26 -0500
Received: from psg.com ([147.28.0.62] helo=[127.0.0.1])
	by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CwToF-000KJ5-4o
	for routing-discussion@ietf.org; Wed, 02 Feb 2005 23:21:19 +0000
Date: Wed, 2 Feb 2005 15:21:18 -0800
From: Alex Zinin <zinin@psg.com>
X-Priority: 3 (Normal)
Message-ID: <634566195.20050202152118@psg.com>
To: routing-discussion@ietf.org
In-Reply-To: <200502022131.QAA08064@ietf.org>
References: <200502022131.QAA08064@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.8 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: 7bit
Subject: Fwd: Closing of SUB-IP Area
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Alex Zinin <zinin@psg.com>
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
Content-Transfer-Encoding: 7bit

FYI
-- 
Alex
http://www.psg.com/~zinin

This is a forwarded message
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce@ietf.org
Cc: 
Date: Wednesday, February 2, 2005, 1:31:37 PM
Subject: Closing of SUB-IP Area

===8<==============Original message text===============
The final documents of the TEWG working group have recently been approved by the
IESG. As a result, the TEWG has also been closed down.

That means we have no work left in the SUB-IP Area. Therefore we are now closing
it down. The area-level mailing lists for this area will also be closed. Please
note that some WGs that previously were part of the SUB-IP area were moved to
other areas earlier (e.g., L2VPN, L3VPN, MPLS, CCAMP WGs).

We would like to thank you all for your efforts. We would like to thank Scott
Bradner, who's been instrumental in creating the area and managing it during his
IESG term, as well as Harald Alvestrand for being the IETF chair during almost
exactly the same period that the SUB-IP Area existed.

Bert and Alex.







_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce

===8<===========End of original message text===========


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Fri Feb 18 18:50:08 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24571
	for <routing-discussion-archive@lists.ietf.org>; Fri, 18 Feb 2005 18:50:08 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D2HI8-0000KF-0o; Fri, 18 Feb 2005 18:12:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D2G5L-0000XF-N8
	for routing-discussion@megatron.ietf.org;
	Fri, 18 Feb 2005 16:54:51 -0500
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 QAA00564
	for <routing-discussion@ietf.org>; Fri, 18 Feb 2005 16:54:49 -0500 (EST)
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D2GR4-0008C5-Kv
	for routing-discussion@ietf.org; Fri, 18 Feb 2005 17:17:19 -0500
Received: from psg.com ([147.28.0.62] helo=[127.0.0.1])
	by psg.com with esmtp (Exim 4.44 (FreeBSD)) id 1D2G5I-000NQv-Pj
	for routing-discussion@ietf.org; Fri, 18 Feb 2005 21:54:48 +0000
Date: Fri, 18 Feb 2005 13:54:48 -0800
From: Alex Zinin <zinin@psg.com>
X-Priority: 3 (Normal)
Message-ID: <1031697513.20050218135448@psg.com>
To: routing-discussion@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.8 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Content-Transfer-Encoding: 7bit
Subject: IETF-62 RTGAREA meeting
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Alex Zinin <zinin@psg.com>
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Folks-

 If you'd like to request an agenda time slot for the meeting in Minneapolis,
 please send an e-mail to Bill and me.

 Thanks.
 
-- 
Alex
http://www.psg.com/~zinin


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Thu Feb 24 22:51:54 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA29188
	for <routing-discussion-archive@lists.ietf.org>; Thu, 24 Feb 2005 22:51:54 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D4VUM-0007n1-7P; Thu, 24 Feb 2005 21:45:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D4VUK-0007lW-EJ
	for routing-discussion@megatron.ietf.org;
	Thu, 24 Feb 2005 21:45:56 -0500
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 VAA23606
	for <routing-discussion@ietf.org>; Thu, 24 Feb 2005 21:45:54 -0500 (EST)
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4VUM-0003fg-6F
	for routing-discussion@ietf.org; Thu, 24 Feb 2005 21:45:59 -0500
Received: from psg.com ([147.28.0.62] helo=[127.0.0.1])
	by psg.com with esmtp (Exim 4.44 (FreeBSD)) id 1D4VUI-000AKe-7F
	for routing-discussion@ietf.org; Fri, 25 Feb 2005 02:45:54 +0000
Date: Thu, 24 Feb 2005 18:45:49 -0800
From: Alex Zinin <zinin@psg.com>
X-Priority: 3 (Normal)
Message-ID: <819517615.20050224184549@psg.com>
To: routing-discussion@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: 7bit
Subject: IETF-62 RTGAREA Agenda
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Alex Zinin <zinin@psg.com>
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Folks-

We'll have our usual open Routing Area meeting on Monday, while everyone is
still fresh and pumped up:

> MONDAY, March 7, 2005
> 1930-2200 Evening Sessions
> RTG  rtgarea    Routing Area Meeting

Our agenda at the moment:

   1. Agenda bashing, aministrivia (ADs)           [5m]    00:05

   2. Announcements, status, etc. (ADs)            [10m]   00:15

   3. WG reports (ADs/chairs)                      [15m]   00:30

   4. (G)MPLS change process discussion            [20m]   00:50
      RM: draft-andersson-rtg-gmpls-change-01.txt

   5. The Big Picture discussion                   [1h30]  02:20
      - where we are
      - what we're doing
      - what we're NOT doing
      - what we SHOULD be doing

See you all there!

-- 
Alex
P.S. If I forgot to put someone on the agenda--please send me a message


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Fri Feb 25 01:41:22 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA16089
	for <routing-discussion-archive@lists.ietf.org>; Fri, 25 Feb 2005 01:41:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D4YD3-0005ri-Fh; Fri, 25 Feb 2005 00:40:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D4YCj-0005pr-QF; Fri, 25 Feb 2005 00:39:58 -0500
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 AAA09756;
	Fri, 25 Feb 2005 00:39:54 -0500 (EST)
Received: from mail-red.research.att.com ([192.20.225.110]
	helo=mail-white.research.att.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D4YCm-0007Wv-Oz; Fri, 25 Feb 2005 00:40:02 -0500
Received: from bright.research.att.com (bright.research.att.com
	[135.207.20.189])
	by mail-blue.research.att.com (Postfix) with ESMTP id B68B31974E0;
	Fri, 25 Feb 2005 00:22:18 -0500 (EST)
Received: (from fenner@localhost)
	by bright.research.att.com (8.12.11/8.12.10/Submit) id j1P5dliu018627; 
	Thu, 24 Feb 2005 21:39:47 -0800
Message-Id: <200502250539.j1P5dliu018627@bright.research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
To: routing-discussion@ietf.org, mpls@ietf.org, ccamp@ops.ietf.org
Date: Thu, 24 Feb 2005 21:39:47 -0800
From: Bill Fenner <fenner@research.att.com>
Versions: dmail (linux) 2.6d/makemail 2.10
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Subject: MPLS/GMPLS Change Process
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: routing-discussion@ietf.org
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org


We expect to talk about the MPLS/GMPLS Change Process at the
Routing Area meeting in Minneapolis.  The main changes from the
-00 version are the addition of the preliminary process which
doesn't require an I-D and additional mentions of where liaisons
fit in the process.

Let's please discuss this on the routing-discussion list, instead
of trying to use both ccamp and mpls lists.

  Bill


----- Begin forwarded message:

From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-andersson-rtg-gmpls-change-01.txt
Date: Tue, 22 Feb 2005 15:50:01 -0500
To: i-d-announce@ietf.org
Reply-to: internet-drafts@ietf.org


	Title		: MPLS and GMPLS Change Process
	Author(s)	: L. Andersson, et al.
	Filename	: draft-andersson-rtg-gmpls-change-01.txt
	Pages		: 23
	Date		: 2005-2-22
	
The MPLS and GMPLS protocol suites have become quite popular for a
   growing number of applications and deployment scenarios.  One result
   of this popularity is a large number of suggestions for modifications
   and extensions.

   The IETF needs to be flexible and responsive in how it handles these
   suggestions, and has a responsiblity to supervise the growth and
   evolution of MPLS and GMPLS protocols.

   This memo describes the process through which individuals, working
   groups and external standards bodies can influence the development of
   the MPLS and GMPLS standards.  This process means that extensions and
   changes to protocols specified by these working groups can only be
   made through the IETF, the body that created the (G)MPLS
   ((Generalized) Multiprotocol Label Switching) technologies.  When
   possible, existing liaison relationships are used.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-andersson-rtg-gmpls-change-01.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the
message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-andersson-rtg-gmpls-change-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-andersson-rtg-gmpls-change-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

[Don't know how to fetch mail-server a3]
_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/i-d-announce


----- End forwarded message:

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Sat Feb 26 23:52:39 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA27138
	for <routing-discussion-archive@lists.ietf.org>; Sat, 26 Feb 2005 23:52:39 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D5GMk-0001TF-AZ; Sat, 26 Feb 2005 23:49:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D51RL-0004EV-H3
	for routing-discussion@megatron.ietf.org;
	Sat, 26 Feb 2005 07:52:59 -0500
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 HAA26422
	for <routing-discussion@ietf.org>; Sat, 26 Feb 2005 07:52:58 -0500 (EST)
Received: from vreme.yubc.net ([212.124.160.13])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D51Rf-0002Z5-8P
	for routing-discussion@ietf.org; Sat, 26 Feb 2005 07:53:20 -0500
Received: from vreme.yubc.net (localhost.localdomain [127.0.0.1])
	by vreme.yubc.net (8.12.11/8.12.11) with ESMTP id j1QCqmt3004661
	for <routing-discussion@ietf.org>; Sat, 26 Feb 2005 13:52:48 +0100
Received: (from root@localhost)
	by vreme.yubc.net (8.12.11/8.12.11/Submit) id j1QCqmMc004659
	for routing-discussion@ietf.org; Sat, 26 Feb 2005 13:52:48 +0100
Date: Sat, 26 Feb 2005 13:52:48 +0100
From: IPSI Transactions Special Issues <ipsitrans@vreme.yubc.net>
Message-Id: <200502261252.j1QCqmMc004659@vreme.yubc.net>
To: routing-discussion@ietf.org
X-Spam-Score: 2.2 (++)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
X-Mailman-Approved-At: Sat, 26 Feb 2005 23:49:12 -0500
Subject: Call for IPSI Transactions Special Issues in 2005/6; c/ba
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org

Dear potential Speaker:

We are pleased to inform you that both IPSI Transactions journals are planing some special issues in late 2005 and early 2006, and you are welcome to submit your paper(s), until the deadlines listed below!

IPSI Transactions on Internet Research:

March 31, 2005 -
Special Issue on E-Education: Concepts and Infrastructure

June 30, 2005 -
Special Issue on E-Business: Concepts and Infrastructure


IPSI Transactions on Advanced Research:

March 31, 2005 -
Special Issue on the Research with Multidisciplinary Elements

June 30, 2005 -
Special Issue on the Research with Interdisciplinary Elements

Each submitted paper first undergoes the editor review, and those who pass this first stage are sent to 12 external experts for a rigorous review; decisions are made after at least 6 external reviewers respond! The review is free of charge, but the authors of the accepted papers ar expected to pay the publication fee of E400 per paper (if 4 or 5 or 6 pages of the TIR/TAR format), and the additional fee of E100 per page, for each extra page, till the maximum of 10 pages.

Rigorous reviewing is the major strength of IPSI journals, which is the major contributor to their high quality! Soft copies of the existing issues of TIR and TAR can be seen at the web, and hard copies can be obtained on a special request by email, as indicated on the web, where can find all information!

Sincerely yours,

Prof. Dr. Veljko Milutinovic, Editor-in-Chief

P.S. If you need aditional information, please reply to this e-mail.

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Sun Feb 27 21:36:17 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28175
	for <routing-discussion-archive@lists.ietf.org>; Sun, 27 Feb 2005 21:36:17 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D5ain-00023t-1m; Sun, 27 Feb 2005 21:33:21 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D5ail-00023a-Vm
	for routing-discussion@megatron.ietf.org;
	Sun, 27 Feb 2005 21:33:20 -0500
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 VAA28004
	for <routing-discussion@ietf.org>; Sun, 27 Feb 2005 21:33:18 -0500 (EST)
Received: from relay03.pair.com ([209.68.5.17])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1D5ajQ-0002o8-NM
	for routing-discussion@ietf.org; Sun, 27 Feb 2005 21:34:01 -0500
Received: (qmail 39110 invoked from network); 28 Feb 2005 02:33:12 -0000
Received: from unknown (HELO workhorse.faster-light.net) (unknown)
	by unknown with SMTP; 28 Feb 2005 02:33:12 -0000
X-pair-Authenticated: 69.37.59.162
Received: from workhorse.faster-light.net (localhost.faster-light.net
	[127.0.0.1])
	by workhorse.faster-light.net (8.12.11/8.12.11) with ESMTP id
	j1S2X7oj002075; Sun, 27 Feb 2005 21:33:08 -0500 (EST)
	(envelope-from curtis@workhorse.faster-light.net)
Message-Id: <200502280233.j1S2X7oj002075@workhorse.faster-light.net>
To: routing-discussion@ietf.org
In-reply-to: Your message of "Thu, 24 Feb 2005 21:39:47 PST."
	<200502250539.j1P5dliu018627@bright.research.att.com> 
Date: Sun, 27 Feb 2005 21:33:07 -0500
From: Curtis Villamizar <curtis@faster-light.net>
X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED autolearn=failed 
	version=3.0.1
X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on 
	workhorse.faster-light.net
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: ccamp@ops.ietf.org, mpls@ietf.org
Subject: Re: MPLS/GMPLS Change Process 
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: curtis@faster-light.net
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org


In message <200502250539.j1P5dliu018627@bright.research.att.com>
Bill Fenner writes:
>  
>  
> We expect to talk about the MPLS/GMPLS Change Process at the
> Routing Area meeting in Minneapolis.  The main changes from the
> -00 version are the addition of the preliminary process which
> doesn't require an I-D and additional mentions of where liaisons
> fit in the process.
>  
> Let's please discuss this on the routing-discussion list, instead
> of trying to use both ccamp and mpls lists.
>  
>   Bill



Bill,

Excellent job on the liason section.  Exactly as it should be.

Curtis

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


