%% You should probably cite draft-sweet-uri-zoneid-01 instead of this revision.
@techreport{sweet-uri-zoneid-00,
	number =	{draft-sweet-uri-zoneid-00},
	type =		{Internet-Draft},
	institution =	{Internet Engineering Task Force},
	publisher =	{Internet Engineering Task Force},
	note =		{Work in Progress},
	url =		{https://datatracker.ietf.org/doc/html/draft-sweet-uri-zoneid-00},
        author =	{Michael Sweet and Brian E. Carpenter and Stuart Cheshire and Bob Hinden},
	title =		{{Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers}},
	pagetotal =	11,
	year =		,
	month =		,
	day =		,
	abstract =	{This document describes how the zone identifier of an IPv6 scoped address, defined as \textless{}zone\_id\textgreater{} in the IPv6 Scoped Address Architecture (RFC 4007), can be represented in a literal IPv6 address and in a Uniform Resource Identifier that includes such a literal address. It updates the URI Generic Syntax specification (RFC 3986) accordingly. {[} Editor's note: This draft adds the IPvFuture format used by CUPS since 2005, addresses some misconceptions of how zoneid's are not useful to HTTP servers, and is intended to replace RFC 6874. {]}},
}