• Aucun résultat trouvé

This document clarifies that a mapping of an IPv6 packet with a multicast destination address may in some circumstances map to an Ethernet link-layer unicast address

N/A
N/A
Info
Télécharger
Protected

Academic year: 2022

Partager "This document clarifies that a mapping of an IPv6 packet with a multicast destination address may in some circumstances map to an Ethernet link-layer unicast address"

Copied!
3
0
0

Chargement.... (Voir le texte intégral maintenant)

Texte intégral

(1)

Internet Engineering Task Force (IETF) S. Gundavelli Request for Comments: 6085 M. Townsley Updates: 2464 O. Troan Category: Standards Track W. Dec ISSN: 2070-1721 Cisco January 2011

Address Mapping of IPv6 Multicast Packets on Ethernet Abstract

When transmitting an IPv6 packet with a multicast destination

address, the IPv6 destination address is mapped to an Ethernet link- layer multicast address. This document clarifies that a mapping of an IPv6 packet with a multicast destination address may in some circumstances map to an Ethernet link-layer unicast address.

Status of This Memo

This is an Internet Standards Track document.

This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.

Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at

http://www.rfc-editor.org/info/rfc6085.

Copyright Notice

Copyright (c) 2011 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

(http://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 the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

Gundavelli, et al. Standards Track [Page 1]

(2)

RFC 6085 Unicast Transmission on Link Layer January 2011

1. Introduction

"Transmission of IPv6 Packets over Ethernet Networks" ([RFC2464], Section 7) specifies how an IPv6 packet with a multicast destination address is mapped into an Ethernet link-layer address. This document extends this mapping to explicitly allow for a mapping of an IPv6 packet with a multicast destination address into an Ethernet link- layer unicast address, when it is clear that only one address is relevant.

This mapping does not replace the mapping described in [RFC2464], Section 7. The determination of the unicast Ethernet link-layer address and the construction of the outgoing IPv6 packet are out of scope for this document.

2. Conventions

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].

3. Receiving IPv6 Multicast Packets

An IPv6 node receiving an IPv6 packet with a multicast destination address and an Ethernet link-layer unicast address MUST NOT drop the packet as a result of the use of this form of address mapping.

4. Security Considerations

This document does not introduce any new security vulnerabilities.

5. Acknowledgements

The authors would like to acknowledge Bernard Aboba, Fred Baker, Wes Beebee, Ron Bonica, Olaf Bonness, Jean-Michel Combes, Ralph Droms, Alain Durand, Suresh Krishnan, Eric Levy-Abegnoli, Phil Roberts, Behcet Sarikaya, Hemant Singh, Mark Smith, Dave Thaler, Pascal Thubert, Stig Venaas, and Eric Voit for their contributions and discussions on this topic.

6. Normative References

[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.

[RFC2464] Crawford, M., "Transmission of IPv6 Packets over Ethernet Networks", RFC 2464, December 1998.

Gundavelli, et al. Standards Track [Page 2]

(3)

RFC 6085 Unicast Transmission on Link Layer January 2011

Authors’ Addresses Sri Gundavelli Cisco

170 West Tasman Drive San Jose, CA 95134 USA

EMail: sgundave@cisco.com

Mark Townsley Cisco

L’Atlantis, 11, Rue Camille Desmoulins ISSY LES MOULINEAUX, ILE DE FRANCE 92782 France

EMail: townsley@cisco.com

Ole Troan Cisco Oslo, Norway

EMail: ot@cisco.com

Wojciech Dec Cisco

Haarlerbergweg 13-19

Amsterdam, Noord-Holland 1101 CH Netherlands

EMail: wdec@cisco.com

Gundavelli, et al. Standards Track [Page 3]

Références

Télécharger maintenant ( PDF - 3 Page - 6.04 KB )

Documents relatifs

To support the storage of IPv6 addresses we define the following extensions: o A new resource record type is defined to map a domain name to an IPv6 address

changes include a new resource record type to store an IPv6 address, a new domain to support lookups based on an IPv6 address, and updated definitions of existing query types

Abstract This document seeks to document all usage of IPv4 addresses in currently deployed IETF Internet Area documented standards

RFC 2464 Transmission of IPv6 Packets over Ethernet Networks This specification documents a method for transmitting IPv6 packets over Ethernet and is not considered in

Abstract This memo defines an address allocation policy in which the address of the Rendezvous Point (RP) is encoded in an IPv6 multicast group address

This memo describes a multicast address allocation policy in which the address of the RP is encoded in the IPv6 multicast group address, and specifies a PIM-SM group-to-RP

For IP version 6 (IPv6), the address prefix FF3x::/32 is reserved for source-specific multicast use

When the first socket on host H subscribes to a channel (S,G) on interface I, the host IP module on H sends a request on interface I to indicate to neighboring routers that

Abstract This memo provides an analysis of the Host Density metric as it is currently used to guide registry allocations of IPv6 unicast address blocks

The fixed efficiency model, as used in the IPv4 address allocation policy, uses the assumption that as the allocation block becomes larger, the network structure remains at

IANA IPv6 Special Purpose Address Block [RFC2928] specified the assignment of the IPv6 address prefix to IANA

IANA may undertake IPv6 address designations in support of special purposes as requested in "IANA Considerations" sections in IESG- reviewed RFCs, where an address

Abstract This document specifies requirements for a for a Network Address Translator (NAT) and a Network Address Port Translator (NAPT) that support Any Source IP Multicast or Source-Specific IP Multicast

The NAT device will subsequently receive an IP multicast data packet on the ’outside’ interface and forward the IP multicast packet to the ’inside’ interface(s) based on

However, RFC 2544 does not address some of the specificities of IPv6

This document provides benchmarking methodology recommendations that address IPv6-specific aspects, such as evaluating the forwarding performance of traffic containing