[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

I-D ACTION:draft-kato-bgp-ipv6-link-local-00.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.

	Title		: BGP4+ Peering Using IPv6 Link-local Address
	Author(s)	: A. Kato, B. Manning
	Filename	: draft-kato-bgp-ipv6-link-local-00.txt
	Pages		: 7
	Date		: 24-Sep-01
In IPv6 it is possible to use link-local addresses to specify a E-BGP
connection.  In this case, no global address space is necessary on a
link between two Autonomous systems or on an Internet Exchange point.
This memo proposes changes of the protocol defined in RFC2545, and some
guidelines of implementation and operation to enable E-BGP sessions
using IPv6 link-local addresses.

A URL for this Internet-Draft is:

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-kato-bgp-ipv6-link-local-00.txt".

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

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

Send a message to:
In the body type:
	"FILE /internet-drafts/draft-kato-bgp-ipv6-link-local-00.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
Content-type: text/plain