Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id OAA20111 for <idr-archive@nic.merit.edu>; Wed, 20 Dec 2000 14:41:10 -0500 (EST)
Received: by segue.merit.edu (Postfix) id C91F45DE01; Wed, 20 Dec 2000 14:40:41 -0500 (EST)
Delivered-To: idr-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56) id B8EA15DDBB; Wed, 20 Dec 2000 14:40:41 -0500 (EST)
Received: from presque.djinesys.com (unknown [198.108.6.10]) by segue.merit.edu (Postfix) with ESMTP id 3A01F5DDA0 for <idr@merit.edu>; Wed, 20 Dec 2000 14:40:40 -0500 (EST)
Received: from jhaas.nexthop.com ([141.211.130.148]) by presque.djinesys.com (8.9.3/8.9.3) with ESMTP id OAA50604 for <idr@merit.edu>; Wed, 20 Dec 2000 14:33:11 -0500 (EST) (envelope-from jhaas@nexthop.com)
Received: (from jhaas@localhost) by jhaas.nexthop.com (8.11.0/8.11.0) id eBKJedj12356; Wed, 20 Dec 2000 14:40:39 -0500 (EST)
Date: Wed, 20 Dec 2000 14:40:39 -0500
From: Jeffrey Haas <jhaas@nexthop.com>
To: Srinivasa Chaganti <chaganti@pluris.com>
Cc: "'idr@merit.edu'" <idr@merit.edu>
Subject: Re: AS_PATH
Message-ID: <20001220144039.A12214@jhaas.nexthop.com>
References: <E097FDA4F2FED311994000104B31A86101025AF8@MONTEREY>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <E097FDA4F2FED311994000104B31A86101025AF8@MONTEREY>; from chaganti@pluris.com on Sun, Dec 17, 2000 at 10:15:41AM -0800
Sender: owner-idr@merit.edu
Precedence: bulk

On Sun, Dec 17, 2000 at 10:15:41AM -0800, Srinivasa Chaganti wrote:
> many implementations do check whether remote AS number is the first AS
> number from left in each update message received from remote AS. If first AS
> number is incorrect, then a malformed-aspath notification message is sent to
> the peer.

The route servers that run at the exchange points are often configured
to work transparently.  It may be advisable to make sending a NOTIFY
when the adjacent AS is not detected in the ASPATH a configurable
option.

> -Chaganti S.

-- 
Jeff Haas 
NextHop Technologies



Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id NAA19062 for <idr-archive@nic.merit.edu>; Sun, 17 Dec 2000 13:18:33 -0500 (EST)
Received: by segue.merit.edu (Postfix) id C99725DD9C; Sun, 17 Dec 2000 13:15:46 -0500 (EST)
Delivered-To: idr-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56) id B4AB35DDE5; Sun, 17 Dec 2000 13:15:46 -0500 (EST)
Received: from yarilo.pluris.com (pluris.com [208.227.9.12]) by segue.merit.edu (Postfix) with ESMTP id ACEFB5DD9C for <idr@merit.edu>; Sun, 17 Dec 2000 13:15:44 -0500 (EST)
Received: from monterey.pluris.com (monterey.pluris.com [172.16.50.17]) by yarilo.pluris.com (8.9.2/8.9.1) with ESMTP id KAA18005; Sun, 17 Dec 2000 10:15:43 -0800 (PST)
Received: by MONTEREY with Internet Mail Service (5.5.2650.21) id <YXJQQSSQ>; Sun, 17 Dec 2000 10:15:43 -0800
Message-ID: <E097FDA4F2FED311994000104B31A86101025AF8@MONTEREY>
From: Srinivasa Chaganti <chaganti@pluris.com>
To: "'Anoop Ghanwani '" <anoop@cosinecom.com>, "'idr@merit.edu'" <idr@merit.edu>
Subject: RE: AS_PATH 
Date: Sun, 17 Dec 2000 10:15:41 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain; charset="iso-8859-1"
Sender: owner-idr@merit.edu
Precedence: bulk

many implementations do check whether remote AS number is the first AS
number from left in each update message received from remote AS. If first AS
number is incorrect, then a malformed-aspath notification message is sent to
the peer.

-Chaganti S.



-----Original Message-----
From: Anoop Ghanwani
To: 'idr@merit.edu'
Sent: 12/16/00 6:26 PM
Subject: AS_PATH 

When BGP receives an Update message from a peer 
which it knows to be in a remote AS, say X, should it check 
that X has been prepended to the AS_PATH?  

If the answer to the above is "yes" and if the correct AS number 
has not been prepended to the AS_PATH, should it send a NOTIFY 
message and close the session? 

Thanks, -Anoop 




Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id VAA09998 for <idr-archive@nic.merit.edu>; Sat, 16 Dec 2000 21:29:21 -0500 (EST)
Received: by segue.merit.edu (Postfix) id 91D0D5DDAF; Sat, 16 Dec 2000 21:28:52 -0500 (EST)
Delivered-To: idr-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56) id 79C9E5DDEB; Sat, 16 Dec 2000 21:28:52 -0500 (EST)
Received: from exchsrv1.cosinecom.com (mail.cosinecom.com [63.88.104.16]) by segue.merit.edu (Postfix) with ESMTP id 18BE85DDAF for <idr@merit.edu>; Sat, 16 Dec 2000 21:28:51 -0500 (EST)
Received: by exchsrv1.cosinecom.com with Internet Mail Service (5.5.2650.21) id <Y4YLX16H>; Sat, 16 Dec 2000 18:26:59 -0800
Message-ID: <7EB7C6B62C4FD41196A80090279A2911011821E9@exchsrv1.cosinecom.com>
From: Anoop Ghanwani <anoop@cosinecom.com>
To: "'idr@merit.edu'" <idr@merit.edu>
Subject: AS_PATH 
Date: Sat, 16 Dec 2000 18:26:57 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C067D0.D4059CD0"
Sender: owner-idr@merit.edu
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C067D0.D4059CD0
Content-Type: text/plain

When BGP receives an Update message from a peer 
which it knows to be in a remote AS, say X, should it check 
that X has been prepended to the AS_PATH?  

If the answer to the above is "yes" and if the correct AS number
has not been prepended to the AS_PATH, should it send a NOTIFY 
message and close the session?

Thanks, -Anoop 

------_=_NextPart_001_01C067D0.D4059CD0
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=US-ASCII">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2652.35">
<TITLE>AS_PATH </TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>When BGP receives an Update message from a peer </FONT>
<BR><FONT SIZE=2>which it knows to be in a remote AS, say X, should it check </FONT>
<BR><FONT SIZE=2>that X has been prepended to the AS_PATH?&nbsp; </FONT>
</P>

<P><FONT SIZE=2>If the answer to the above is &quot;yes&quot; and if the correct AS number</FONT>
<BR><FONT SIZE=2>has not been prepended to the AS_PATH, should it send a NOTIFY </FONT>
<BR><FONT SIZE=2>message and close the session?</FONT>
</P>

<P><FONT SIZE=2>Thanks, -Anoop </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C067D0.D4059CD0--



Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id LAA25968 for <idr-archive@nic.merit.edu>; Tue, 12 Dec 2000 11:33:59 -0500 (EST)
Received: by segue.merit.edu (Postfix) id 0A93F5DDEC; Tue, 12 Dec 2000 11:31:26 -0500 (EST)
Delivered-To: idr-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56) id ED25C5DDE5; Tue, 12 Dec 2000 11:31:25 -0500 (EST)
Received: from presque.djinesys.com (unknown [198.108.6.10]) by segue.merit.edu (Postfix) with ESMTP id 777385DDCE for <idr@merit.edu>; Tue, 12 Dec 2000 11:31:24 -0500 (EST)
Received: from jhaas.nexthop.com ([141.211.130.148]) by presque.djinesys.com (8.9.3/8.9.3) with ESMTP id LAA52015 for <idr@merit.edu>; Tue, 12 Dec 2000 11:24:13 -0500 (EST) (envelope-from jhaas@nexthop.com)
Received: (from jhaas@localhost) by jhaas.nexthop.com (8.11.0/8.11.0) id eBCGVOt02347 for idr@merit.edu; Tue, 12 Dec 2000 11:31:24 -0500 (EST)
Date: Tue, 12 Dec 2000 11:31:23 -0500
From: Jeffrey Haas <jhaas@nexthop.com>
To: idr@merit.edu
Subject: Re: Private ASNs - which RFC
Message-ID: <20001212113123.A2340@jhaas.nexthop.com>
References: <4.3.2.7.2.20001212115928.00aa7b60@max.ibm.net.il> <Pine.GSO.3.96LJ1.1b7.1001212192417.26739P-100000@imap.interq.or.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <Pine.GSO.3.96LJ1.1b7.1001212192417.26739P-100000@imap.interq.or.jp>; from peter@interq.or.jp on Tue, Dec 12, 2000 at 07:24:34PM +0900
Sender: owner-idr@merit.edu
Precedence: bulk

On Tue, Dec 12, 2000 at 07:24:34PM +0900, Peter Chow wrote:
> RFC1930
> 
> ASN 64512 through 65535

In addition, IANA lists 65535 as "reserved". :-)

http://www.isi.edu/in-notes/iana/assignments/as-numbers

> On Tue, 12 Dec 2000, Hank Nussbacher wrote:
> > I know I have seen it but I can't remember which RFC documents private ASN 
> > numbers.  Just send me the RFC #.

-- 
Jeff Haas 
NextHop Technologies



Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id FAA21757 for <idr-archive@nic.merit.edu>; Tue, 12 Dec 2000 05:25:38 -0500 (EST)
Received: by segue.merit.edu (Postfix) id 971375DDBC; Tue, 12 Dec 2000 05:25:08 -0500 (EST)
Delivered-To: idr-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56) id 889CF5DDB9; Tue, 12 Dec 2000 05:25:08 -0500 (EST)
Received: from tom.interq.or.jp (tom.interq.or.jp [210.172.128.229]) by segue.merit.edu (Postfix) with ESMTP id 67AFB5DDAA for <idr@merit.edu>; Tue, 12 Dec 2000 05:25:02 -0500 (EST)
Received: from imap.interq.or.jp (imap.interq [210.157.0.31]) by tom.interq.or.jp (8.9.3/8.9.0/8.9.0/199808251233) with SMTP id TAA07199; Tue, 12 Dec 2000 19:23:26 +0900 (JST)
Date: Tue, 12 Dec 2000 19:24:34 +0900 (JST)
From: Peter Chow <peter@interq.or.jp>
To: Hank Nussbacher <hank@att.net.il>
Cc: idr@merit.edu
Subject: Re: Private ASNs - which RFC
In-Reply-To: <4.3.2.7.2.20001212115928.00aa7b60@max.ibm.net.il>
Message-ID: <Pine.GSO.3.96LJ1.1b7.1001212192417.26739P-100000@imap.interq.or.jp>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idr@merit.edu
Precedence: bulk

RFC1930

ASN 64512 through 65535

On Tue, 12 Dec 2000, Hank Nussbacher wrote:

> I know I have seen it but I can't remember which RFC documents private ASN 
> numbers.  Just send me the RFC #.

--------------------------------------------------------------------
_/_/_/ Peter Chow		Chief Technical Advisor
_/_/_/ peter@interq.ad.jp	interQ Inc. - System Division
_/_/_/ ICQ: 41931890		Shibuya Infoss Tower 10F
_/_/_/ (tel)+81-3-5456-2555	20-1 Sakuragaoka, Shibuya-ku
_/_/_/ (fax)+81-3-5456-2556	Tokyo, Japan
_/_/_/ http://www.interq.ad.jp/	150-0031
--------------------------------------------------------------------




Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id FAA21314 for <idr-archive@nic.merit.edu>; Tue, 12 Dec 2000 05:03:15 -0500 (EST)
Received: by segue.merit.edu (Postfix) id 17D7C5DD9F; Tue, 12 Dec 2000 05:00:54 -0500 (EST)
Delivered-To: idr-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56) id E88E45DDAA; Tue, 12 Dec 2000 05:00:53 -0500 (EST)
Received: from biff.att.net.il (biff.att.net.il [192.115.72.164]) by segue.merit.edu (Postfix) with ESMTP id 21C565DD9F for <idr@merit.edu>; Tue, 12 Dec 2000 05:00:52 -0500 (EST)
Received: from docking.att.net.il (hank.tlv.att.net.il [192.115.72.7]) by biff.att.net.il (Postfix) with ESMTP id 4CAB611C0 for <idr@merit.edu>; Tue, 12 Dec 2000 11:29:12 +0200 (IST)
Message-Id: <4.3.2.7.2.20001212115928.00aa7b60@max.ibm.net.il>
X-Sender: hank@max.ibm.net.il
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 12 Dec 2000 12:00:20 +0200
To: idr@merit.edu
From: Hank Nussbacher <hank@att.net.il>
Subject: Private ASNs - which RFC
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idr@merit.edu
Precedence: bulk

I know I have seen it but I can't remember which RFC documents private ASN 
numbers.  Just send me the RFC #.

Thanks,
Hank




Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id DAA00394 for <idr-archive@nic.merit.edu>; Mon, 11 Dec 2000 03:29:11 -0500 (EST)
Received: by segue.merit.edu (Postfix) id ACDF45DDB7; Mon, 11 Dec 2000 03:28:39 -0500 (EST)
Delivered-To: idr-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56) id 73E935DDDE; Mon, 11 Dec 2000 03:28:39 -0500 (EST)
Received: from smtp2.cluster.oleane.net (smtp2.cluster.oleane.net [195.25.12.17]) by segue.merit.edu (Postfix) with ESMTP id A08835DDB7 for <idr@merit.edu>; Mon, 11 Dec 2000 03:28:37 -0500 (EST)
Received: from oleane (dyn-1-1-004.Vin.dialup.oleane.fr [195.25.4.4]) by smtp2.cluster.oleane.net with SMTP id eBB8SYc99310 for <idr@merit.edu>; Mon, 11 Dec 2000 09:28:34 +0100 (CET)
Message-ID: <017601c0634c$a7b81fa0$8001a8c0@oleane.com>
From: "Peter Lewis" <peter.lewis@upperside.fr>
To: <idr@merit.edu>
Subject: "Betond Sonet/SDH"  Call for paper 
Date: Mon, 11 Dec 2000 09:30:41 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0173_01C06355.077D5C40"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-idr@merit.edu
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_0173_01C06355.077D5C40
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Gigabit Ethernet
Digital Wrapper Issues
Implementation of newly defined functionalities: STM-64, STM-256 =
(positioning beside N x 2.5 G or P x 10 G)=20
Tandem connection monitoring FEC WDM DWDM issues:=20
- Transitional step between SDH and OTN=20
- Terabit networks
- WDM for metro networks=20

The call for paper for the "Betond Sonet/SDH" conference has been =
extended to January 20.

Please take a look on:
http://www.upperside.fr/babeyondsdh.htm

------=_NextPart_000_0173_01C06355.077D5C40
Content-Type: text/html;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dwindows-1252" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>
<DIV><FONT face=3DArial size=3D2>
<DIV>Gigabit Ethernet</DIV>
<DIV>Digital Wrapper Issues</DIV>
<DIV>Implementation of newly defined functionalities: STM-64, STM-256=20
(positioning beside N x 2.5 G or P x 10 G) <BR>Tandem connection =
monitoring FEC=20
WDM DWDM issues: <BR>- Transitional step between SDH and OTN <BR>- =
Terabit=20
networks<BR>- WDM for metro networks </DIV>
<DIV>&nbsp;</DIV>
<DIV>The call for paper for the "Betond Sonet/SDH" conference has been =
extended=20
to January 20.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Please take a look on:</DIV>
<DIV><A=20
href=3D"http://www.upperside.fr/babeyondsdh.htm">http://www.upperside.fr/=
babeyondsdh.htm</A></DIV></FONT></DIV></FONT></DIV></BODY></HTML>

------=_NextPart_000_0173_01C06355.077D5C40--




Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id XAA28191 for <idr-archive@nic.merit.edu>; Fri, 8 Dec 2000 23:04:15 -0500 (EST)
Received: by segue.merit.edu (Postfix) id 0298B5DE47; Fri,  8 Dec 2000 23:01:41 -0500 (EST)
Delivered-To: idr-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56) id DFD375DE62; Fri,  8 Dec 2000 23:01:40 -0500 (EST)
Received: from workhorse.fictitious.org (workhorse.fictitious.org [209.66.129.230]) by segue.merit.edu (Postfix) with ESMTP id 175FC5DE47 for <idr@merit.edu>; Fri,  8 Dec 2000 23:01:37 -0500 (EST)
Received: from workhorse.fictitious.org (localhost.fictitious.org [127.0.0.1]) by workhorse.fictitious.org (8.9.3/8.9.3) with ESMTP id WAA57500; Fri, 8 Dec 2000 22:58:42 -0500 (EST) (envelope-from curtis@workhorse.fictitious.org)
Message-Id: <200012090358.WAA57500@workhorse.fictitious.org>
To: Geoffrey CRISTALLO <geoffrey.cristallo@alcatel.be>
Cc: idr@merit.edu
Reply-To: curtis@avici.com
Subject: Re: IDRP for IPv6 
In-reply-to: Your message of "Fri, 01 Dec 2000 15:21:27 +0100." <3A27B3E7.4FA7461A@alcatel.be> 
Date: Fri, 08 Dec 2000 22:58:42 -0500
From: Curtis Villamizar <curtis@workhorse.fictitious.org>
Sender: owner-idr@merit.edu
Precedence: bulk

In message <3A27B3E7.4FA7461A@alcatel.be>, Geoffrey CRISTALLO writes:
> hi
> 
> here is a reference to draft "IDRP for IPv6" (draft-ietf-idr-idrp-v6-01)
> in RFC 1863.
> 
> does somebody know what is the status of the work on IDRP for IPv6 ? the
> draft is expired (novembre 1994), but are there newer versions of the
> draft ? has is been merged with other contributions ????
> 
> Any comment welcome


It would appear to me that IDRP for anything is pretty well dead.

Curtis



Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id JAA28206 for <idr-archive@nic.merit.edu>; Thu, 7 Dec 2000 09:44:08 -0500 (EST)
Received: by segue.merit.edu (Postfix) id C94D15DDA2; Thu,  7 Dec 2000 09:43:39 -0500 (EST)
Delivered-To: idr-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56) id AE4535DDA4; Thu,  7 Dec 2000 09:43:39 -0500 (EST)
Received: from redbaron.nexabit.com (d28.nexabit.com [209.6.34.253]) by segue.merit.edu (Postfix) with ESMTP id 92F525DDA2 for <idr@merit.edu>; Thu,  7 Dec 2000 09:43:37 -0500 (EST)
Received: from bandito.nexabit.com (bandito.nexabit.com [135.17.240.4]) by redbaron.nexabit.com (8.9.3/8.9.3) with ESMTP id KAA11976 for <idr@merit.edu>; Thu, 7 Dec 2000 10:07:31 -0500
Received: by bandito.nexabit.com with Internet Mail Service (5.5.2650.21) id <TL79FAK0>; Thu, 7 Dec 2000 09:43:32 -0500
Message-ID: <BAC9CCF04FEED311BD1D00062950ABB1C6C3B2@bandito.nexabit.com>
From: Barry Hass <BHass@nexabit.com>
To: idr@merit.edu
Subject: Agenda for San Diego
Date: Thu, 7 Dec 2000 09:43:31 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain; charset="iso-8859-1"
Sender: owner-idr@merit.edu
Precedence: bulk

Has the IDR WG published an agenda for San Diego yet?

Thanks,
Barry



Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id JAA02064 for <idr-archive@nic.merit.edu>; Fri, 1 Dec 2000 09:23:44 -0500 (EST)
Received: by segue.merit.edu (Postfix) id 95F1B5DDAF; Fri,  1 Dec 2000 09:23:16 -0500 (EST)
Delivered-To: idr-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56) id 7A6E05DDB8; Fri,  1 Dec 2000 09:23:16 -0500 (EST)
Received: from relay2.alcatel.be (alc239.alcatel.be [195.207.101.239]) by segue.merit.edu (Postfix) with ESMTP id 6E00E5DDAF for <idr@merit.edu>; Fri,  1 Dec 2000 09:23:14 -0500 (EST)
Received: from bemail04.net.alcatel.be (localhost [127.0.0.1]) by relay2.alcatel.be (8.10.1/8.10.1) with SMTP id eB1EKTt17039 for <idr@merit.edu>; Fri, 1 Dec 2000 15:20:29 +0100 (MET)
Received: from alcatel.be ([138.203.66.5]) by bemail04.net.alcatel.be (Lotus SMTP MTA v4.6.7  (934.1 12-30-1999)) with SMTP id C12569A8.004EFF7C; Fri, 1 Dec 2000 15:22:52 +0100
Message-ID: <3A27B3E7.4FA7461A@alcatel.be>
Date: Fri, 01 Dec 2000 15:21:27 +0100
From: Geoffrey CRISTALLO <geoffrey.cristallo@alcatel.be>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: idr@merit.edu
Subject: IDRP for IPv6
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idr@merit.edu
Precedence: bulk

hi

here is a reference to draft "IDRP for IPv6" (draft-ietf-idr-idrp-v6-01)
in RFC 1863.

does somebody know what is the status of the work on IDRP for IPv6 ? the
draft is expired (novembre 1994), but are there newer versions of the
draft ? has is been merged with other contributions ????

Any comment welcome


-- 
Geoffrey CRISTALLO         
Alcatel Telecom
Francis Wellesplein, 1, 2018 Antwerp, Belgium
Phone: +32 3 240 82 97
mailto:geoffrey.cristallo@alcatel.be