Re: Type Codes for IANA

John Krawczyk <jkrawczy@baynetworks.com> Tue, 18 July 1995 15:33 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa10546; 18 Jul 95 11:33 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa10542; 18 Jul 95 11:33 EDT
Received: from interlock.ans.net by CNRI.Reston.VA.US id aa10992; 18 Jul 95 11:33 EDT
Received: by interlock.ans.net id AA12182 (InterLock SMTP Gateway 3.0 for iwg-out@ans.net); Tue, 18 Jul 1995 11:21:25 -0400
Message-Id: <199507181521.AA12182@interlock.ans.net>
Received: by interlock.ans.net (Protected-side Proxy Mail Agent-4); Tue, 18 Jul 1995 11:21:25 -0400
Received: by interlock.ans.net (Protected-side Proxy Mail Agent-3); Tue, 18 Jul 1995 11:21:25 -0400
Received: by interlock.ans.net (Protected-side Proxy Mail Agent-2); Tue, 18 Jul 1995 11:21:25 -0400
Date: Tue, 18 Jul 95 11:21:19 EDT
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: John Krawczyk <jkrawczy@baynetworks.com>
Received: by interlock.ans.net (Protected-side Proxy Mail Agent-1); Tue, 18 Jul 1995 11:21:25 -0400
To: Bill Manning <bmanning@isi.edu>
Cc: bgp@ans.net
Subject: Re: Type Codes for IANA
In-Reply-To: <199507180837.AA21138@interlock.ans.net>
References: <199507180837.AA21138@interlock.ans.net>
Reply-To: jkrawczy@baynetworks.com

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