Re: Type Codes for IANA
Paul Traina <pst@cisco.com> Wed, 19 July 1995 10:29 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa07986;
19 Jul 95 6:29 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa07982;
19 Jul 95 6:29 EDT
Received: from interlock.ans.net by CNRI.Reston.VA.US id aa05787;
19 Jul 95 6:28 EDT
Received: by interlock.ans.net id AA51170
(InterLock SMTP Gateway 3.0 for iwg-out@ans.net);
Wed, 19 Jul 1995 05:49:36 -0400
Message-Id: <199507190949.AA51170@interlock.ans.net>
Received: by interlock.ans.net (Protected-side Proxy Mail Agent-2);
Wed, 19 Jul 1995 05:49:36 -0400
Received: by interlock.ans.net (Protected-side Proxy Mail Agent-1);
Wed, 19 Jul 1995 05:49:36 -0400
To: jkrawczy@baynetworks.com
Cc: Bill Manning <bmanning@isi.edu>, bgp@ans.net, rchandra@cisco.com,
haskin@baynetworks.com
Subject: Re: Type Codes for IANA
In-Reply-To: Your message of "Tue, 18 Jul 1995 11:21:19 EDT."
<199507181521.AA12182@interlock.ans.net>
Date: Wed, 19 Jul 1995 02:49:30 -0700
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Paul Traina <pst@cisco.com>
I believe Dimitry's advertiser attribute and Ravi's originator attribute are the exact same bit of information and are compatible. Ravi? Dimitry? Paul From: jkrawczy@BayNetworks.com (John Krawczyk) Subject: Re: Type Codes for IANA Here's what Dimitry used in the RS draft; Hopefully, he'll correct anything I screw up here... This reminds me - we need to do the same administrivia with OPEN options and new messages (both of which are defined in the RS draft). As I said in the meeting, Dimitry grabbed numbers from the high end of the scale (255). Just pick n+1 from the other list for the assigned number. ADVERTISER path attribute CLUSTER ID open parameter LIST message I think that's it. -jj
- Type Codes for IANA Bill Manning
- Re: Type Codes for IANA Tony Bates
- Re: Type Codes for IANA John Krawczyk
- Re: Type Codes for IANA Paul Traina
- Re: Type Codes for IANA bmanning
- Re: Type Codes for IANA Dimitry Haskin