The IPv6 Link-Local Address Type Field
draft-templin-6man-lla-type-00
The information below is for an old version of the document |
Document |
Type |
|
Active Internet-Draft (individual)
|
|
Author |
|
Fred Templin
|
|
Last updated |
|
2020-11-17
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
pdf
htmlized (tools)
htmlized
bibtex
|
Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group F. Templin, Ed.
Internet-Draft The Boeing Company
Intended status: Standards Track November 17, 2020
Expires: May 21, 2021
The IPv6 Link-Local Address Type Field
draft-templin-6man-lla-type-00
Abstract
IPv6 link-local addresses are formed from the prefix fe80::/10 which
is followed by 54 "zero" bits, then followed by a 64-bit Interface
Identifier. There are multiple methods for generating link-local
addresses, and multiple may be in use by nodes on the same link (and
sometimes even the same interface) at the same time. This document
defines an IPv6 link-local address "Type" field that identifies the
type of link-local address being used.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 21, 2021.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
Templin Expires May 21, 2021 [Page 1]
Internet-Draft IPv6 Link-Local Address Type Field November 2020
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. The IPv6 Link-Local Address Type Field . . . . . . . . . . . 3
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
7.1. Normative References . . . . . . . . . . . . . . . . . . 5
7.2. Informative References . . . . . . . . . . . . . . . . . 6
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction
The IPv6 link-local address prefix is defined in [RFC4291] as the
prefix fe80::/10 followed by 54 "zero" bits, then followed by a
64-bit interface identifier. There are multiple methods for
generating link-local addresses, and multiple may be in use on the
same link (and sometimes even the same interface) at the same time.
For example, [I-D.ietf-6man-rfc4941bis], [RFC7217], [RFC4291],
[RFC3972], [I-D.templin-6man-omni-interface] and possibly others
define diverse methods for generating interface idenfiers for
constructing link-local addresses on a given interface.
Administrative configuration (e.g., manually setting the interface
ID) is also an option available to all interfaces.
IPv6 multi-addressing allows each interface to assign multiple IPv6
addresses, and even multiple IPv6 link-local addresses. On some
interfaces, it may even be the case that multiple link-local
addresses of different types would be configured at the same time.
But, since the diverse methods for generating interface identifiers
are not coordinated with one another, some interfaces may need a way
to differentiate the types of link-local addresses as well as to
avoid collisions and duplication. This document defines a Type field
in the link-local address prefix for differentiating link-local
address construction types.
This document updates [RFC4291].
Templin Expires May 21, 2021 [Page 2]
Internet-Draft IPv6 Link-Local Address Type Field November 2020
2. Terminology
The terminology in the normative references applies.
3. The IPv6 Link-Local Address Type Field
[RFC4291] defines the IPv6 link-local address format as the prefix
fe80::/10, followed by 54 zero bits, then followed by a 64-bit
Interface Identifier as shown in Figure 1:
Show full document text