Browse Prior Art Database

Format for Literal IPv6 Addresses in URL's (RFC2732)

IP.com Disclosure Number: IPCOM000003328D
Original Publication Date: 1999-Dec-01
Included in the Prior Art Database: 2019-Feb-10
Document File: 5 page(s) / 6K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

R. Hinden: AUTHOR [+2]

Related Documents

10.17487/RFC2732: DOI

Abstract

This document defines the format for literal IPv6 Addresses in URL's for implementation in World Wide Web browsers. [STANDARDS-TRACK]

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 46% of the total text.

Network Working Group R. Hinden Request for Comments: 2732 Nokia Category: Standards Track B. Carpenter IBM L. Masinter AT&T December 1999

Format for Literal IPv6 Addresses in URL’s

Status of this Memo

This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (1999). All Rights Reserved.

Abstract

This document defines the format for literal IPv6 Addresses in URL’s for implementation in World Wide Web browsers. This format has been implemented in the IPv6 versions of several widely deployed browsers including Microsoft Internet Explorer, Mozilla, and Lynx. It is also intended to be used in the IPv6 version of the service location protocol.

This document incudes an update to the generic syntax for Uniform Resource Identifiers defined in RFC 2396 [URL]. It defines a syntax for IPv6 addresses and allows the use of "[" and "]" within a URI explicitly for this reserved purpose.

1. Introduction

The textual representation defined for literal IPv6 addresses in [ARCH] is not directly compatible with URL’s. Both use ":" and "." characters as delimiters. This document defines the format for literal IPv6 Addresses in URL’s for implementation in World Wide Web browsers. The goal is to have a format that allows easy "cut" and "paste" operations with a minimum of editing of the literal address.

Hinden, et al. Standards Track [Page 1]

RFC 2732 IPv6 Literal Addresses in URL’s December 1999

The format defined in this document has been implemented in the IPv6 versions of several widely deployed browsers including Microsoft Internet Explorer, Mozilla, and Lynx. It is also intended to be used in the IPv6 version of the service location protocol.

1.1 Requirements

The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, if and where they appear in this document, are to be interpreted as described in [KEYWORDS].

World Wide Web browsers SHOULD implement the format of IPv6 literals in URL’s defined in this document. Other types of applications and protocols that use URL’s MAY use this format.

2. Literal IPv6 Address Format in URL’s Syntax

To use a literal IPv6 address in a URL, the literal address should be enclosed in "[" and "]" characters. For example the following literal IPv6 addresses:

FEDC:BA98:7654:3210:FEDC:BA98:7654:3210 1080:0:0:0:8:800:200C:4171 3ffe:2a00:100:7031::1 1080::8:800:200C:417A ::192.9.5.5 ::FFFF:129.144.52.38 2010:836B:4179::836B:4179

would be represented as in the following example URLs:

http://[FEDC:BA98:7654:3210:FEDC:BA98:7654:3210]:80/index.html http://[1080:0:0:0:8:800:200C:417A]/index.html http://[3ffe:2a00:100:7031::1] http://[1080::8:800:200C:417A]/foo http://[:...

Processing...
Loading...