IPv4-Embedded IPv6 Multicast Address draft-ietf-mboned-64-multicast-address-format IETF 84 Vancouver 1.

Slides:



Advertisements
Similar presentations
1 IPv6 and IPv4 Interoperation and Transition Tony Hain co-chair IETF ngtrans WG
Advertisements

1 Internet Protocol Version 6 (IPv6) What the caterpillar calls the end of the world, nature calls a butterfly. - Anonymous.
Possible approaches to signal IPv4 embedded IPv6 Multicast Address.
Transition Mechanisms for Ipv6 Hosts and Routers RFC2893 By Michael Pfeiffer.
1IETF59 DNSOP WG IPv6 DNS Discovery Issues Jaehoon Paul Jeong ETRI 1st March th IETF – Seoul,
IPv6 Multicast Δημήτριος Α Αδάμος ΑΠΘ - ΕΔΕΤ 107 NW’
MIF API draft-ietf-mif-api-extension-05 Dapeng Liu.
IP/ICMP Translation Algorithm (IIT) Xing Li, Congxiao Bao, Fred Baker
CS 6401 IPv6 Outline Background Structure Deployment.
CSE 8343 Group 3 Advanced OS Inter Operability Between IPv4 and IPv6 Team Members Aman Preet Singh Rohit Singh Nipun Aggarwal Chirag Shah Eugene Novak.
© Janice Regan, CMPT 128, CMPT 371 Data Communications and Networking Multicast routing.
IPv6 Multicast 6DEPLOY. IPv6 Deployment and Support.
IPv6 Home Networking Architecture - update IETF homenet WG Interim meeting Philadelphia, 6 th Oct 2011 draft-chown-homenet-arch-00.
Dean Cheng Jouni Korhonen Mehamed Boucadair
Basic Transition Mechanisms for IPv6 Hosts and Routers -RFC 4213 Kai-Po Yang
IPv6 and IPv4 Coexistence Wednesday, October 07, 2015 IPv6 and IPv4 Coexistence Motorola’s Views for Migration and Co-existence of 3GPP2 Networks to Support.
CSC 600 Internetworking with TCP/IP Unit 8: IP Multicasting (Ch. 17) Dr. Cheer-Sun Yang Spring 2001.
1 IPv6 multicast Stig Venaas 2 Overview IPv6 multicast addresses and scopes IPv6 multicast protocols Interdomain IPv6 multicast Current.
1 CMPT 471 Networking II IGMP (IPv4) and MLD (IPv6) © Janice Regan,
ISIS Auto-Configuration (draft-liu-isis-auto-conf-01) Bing Liu Bruno Decraene
Draft-vandevelde-v6ops-addcon-00.txt IPv6 Unicast Address Assignment Considerations Gunter Van de Velde (editor) Tim Chown Ciprian Popoviciu IETF 65, March.
© J. Liebeherr, All rights reserved 1 Multicast Routing.
Interdomain multicast routing with IPv6 Stig Venaas University of Southampton Jerome Durand RENATER Mickael Hoerdt University Louis Pasteur - LSIIT.
Interdomain IPv6 multicast Stig Venaas UNINETT. PIM-SM and Rendezvous Points Interdomain multicast routing is usually done with a protocol called PIM-SM.
IPv6/IPv4 XLATE Trial Service for sharing IPv4 address Japan Internet Exchange Co., Ltd. Masataka MAWATARI.
ICMP
Multicast addresses for documentation purposes draft-venaas-mboned-mcaddrdoc-03.
Chapter 9 Hardware Addressing and Frame Type Identification 1.Delivering and sending packets 2.Hardware addressing: specifying a destination 3. Broadcasting.
Managing the Use of Privacy Extensions for SLAAC in IPv6 (draft-gont-6man-managing-privacy- extensions-01.txt) Fernando Gont (UTN/FRH) Ron Broersma (DREN)
Multrans Path Optimization draft-zhou-mboned-multrans-path-optimization-02 Cathy ZHOU Qiong SUN IETF 84, Vancouver.
An end-to-end usage of the IPv6 flow label
Draft-ietf-fecframe-config-signaling-02 1 FEC framework Configuration Signaling draft-ietf-fecframe-config-signaling-02.txt IETF 76 Rajiv Asati.
SAVI Analysis for PANA with SLACC Yilan Ding IETF 79 draft-ding-savi-pana-with-slacc-00.
W&L Page 1 CCNA CCNA Training 3.4 Describe the technological requirements for running IPv6 in conjunction with IPv4 Jose Luis Flores /
1 ipv6-node-02.PPT/ 18 November 2002 / John Loughney IETF 55 IPv6 Working Group IPv6 Node Requirements draft-ietf-ipv6-node-requirements-02.txt John Loughney.
IETF 81 th Multicast Extensions to DS-Lite Technique in Broadband Deployments draft-qin-softwire-dslite-multicast-04 Wang, Q., Qin, J., Boucadair, M.,
IP Multicast Receiver Access Control draft-atwood-mboned-mrac-req draft-atwood-mboned-mrac-arch.
Dean Cheng 81 st IETF Quebec City RADIUS Extensions for CGN Configurations draft-cheng-behave-cgn-cfg-radius-ext
1 ipv6-node-02.PPT/ 18 November 2002 / John Loughney IETF 55 IPv6 Working Group IPv6 Node Requirements draft-ietf-ipv6-node-requirements-02.txt John Loughney.
Issues In Multicast Transition For presentation to the Multrans BOF Tom Taylor Cathy Zhou.
1 3gpp_trans/ / IPv6 Transition Solutions for 3GPP Networks draft-wiljakka-3gpp-ipv6-transition-00.txt Juha Wiljakka,
464XLAT : Combination of Stateful and Stateless Translation draft-mawatari-softwire-464xlat IETF Taipei 2011 / 11 / 15 Japan Internet.
Extension of the MLD proxy functionality to support multiple upstream interfaces 1 Luis M. Contreras Telefónica I+D Carlos J. Bernardos Universidad Carlos.
IETF-53-IPv6 WG- Cellular host draft 1 Minimum IPv6 Functionality for a Cellular Host Jari Arkko Peter Hedman Gerben Kuijpers Hesham Soliman John Loughney.
6to4
Extensions to PCEP for Hierarchical Path Computation Elements PCE draft-zhang-pcep-hierarchy-extensions-00 Fatai Zhang Quintin Zhao.
6DEPLOY. IPv6 Deployment and Support
MBONED Agenda IETF 83 Paris. Agenda Review/status of work items5 min Charter Update5 min draft-chown-mboned-multicast-filtering-02 Tim C.10 min draft-tissa-pim-mcast-oam-00Tissa.
IPFIX Requirements: Document Changes and New Issues Raised Jürgen Quittek, NEC Benoit Claise, Cisco Tanja Zseby, Sebstian Zander, FhG FOKUS.
Multicasting EECS June Multicast One-to-many, many-to-many communications Applications: – Teleconferencing – Database – Distributed computing.
1 Framework for IPv4/IPv6 Multicast Translation draft-venaas-behave-v4v6mc- framework-03.txt.
Source-Specific Multicast (RFC4607) Author: H. Holbrook, Arastra, Inc. B. Cain, Acopia Networks Speaker: Wu Zhi Yu.
1 Link Scoped IPv6 Multicast Addresses Jung-Soo Park, Myung-Ki Shin ETRI 54th IETF – Yokohama, Japan draft-ietf-ipv6-link-scoped-mcast-01.txt.
PMIPv6 multicast handover optimization by the Subscription Information Acquisition through the LMA (SIAL) Luis M. Contreras Telefónica I+D Carlos J. Bernardos.
Extension of the MLD proxy functionality to support multiple upstream interfaces 1 Luis M. Contreras Telefónica I+D Carlos J. Bernardos Universidad Carlos.
Deploying Dual-Stack Lite in IPv6 Network draft-boucadair-dslite-interco-v4v6-04 Mohamed Boucadair
1 CMPT 471 Networking II Multicasting © Janice Regan,
Booting up on the Home Link
IETF 55 IPv6 Working Group IPv6 Node Requirements
V4-over-v6 MVPNs.
Dedicated Multicast-LMA (M-LMA)
Link Model Analysis for based Networks
IPv6 Router Alert Option for MPLS OAM
IPv6 VPN Based Address Format draft-lee-l3vpn-ipv6-vpn-00.txt
Percy S. Tarapore, AT&T Robert Sayko, AT&T
RFC4601 Implementation & Deployment Survey
PIM Assert Message Packing
Editors: Bala’zs Varga, Jouni Korhonen
DetNet Data Plane Solutions draft-ietf-detnet-dp-sol-ip-02  draft-ietf-detnet-dp-sol-mpls-02  Bala’zs Varga, Jouni Korhonen, Janos Farkas, Lou Berger,
draft-ietf-pim-igmp-mld-yang-06
Presentation transcript:

IPv4-Embedded IPv6 Multicast Address draft-ietf-mboned-64-multicast-address-format IETF 84 Vancouver 1

History December 2010: draft-boucadair-64-multicast-address-format-00 uses the last flag for embedding an IPv4 address. February 2011: draft-boucadair-behave-64-multicast-address- format-01 abandoned the use of the last flag. The reasons for that choice are listed in the document. February 2012: draft-ietf-mboned-64-multicast-address-format adopted in mboned WG. February 2012:mboned WG LC passed April 2012:IETF LC April 2012: B. Haberman suggested to use the remaining flag April 2012:Since that option has been abandoned, a mail has been sent to 6man ML to seek for feedback. May 2012:An updated version taking into account the comments received during IETF LC was submitted. May 2012:6man chairs asked the draft should be developed in 6man. We are here to present

Dependency

Motivations This address format is used for v4-v6 multicast transition. Specifies how to build an IPv4-embedded multicast IPv6 address Specifies how to extract an IPv4 address from an IPv4- embedded multicast IPv6 address Typical scenarios are –A IPv4 receiver wants to join a multicast group in IPv4 domain via an IPv6-only network (4-6-4). –An IPv6-only receiver wants to receive multicast content from an IPv4- only source (6-4) 4

Rationale Be compatible with embedded-RP [RFC3956] and unicast-based prefix [RFC3306] for ASMRFC3956RFC3306 Require minimal changes to existing RFCs Privilege stateless address translation and no coordination between involved functional elements Embed the multicast IPv4 address in the last 32 of the IPv4-embedded IPv6 multicast address Use a dedicated flag to uniquely identify an IPv4- embedded multicast address. 5

On IPv4-Embedded IPv6 Multicast Addresses Embeds a multicast IPv4 address in an IPv6 Multicast one; both ASM and SSM Modes are covered …0 ASM Flg Scop 64IX …0 SSM Scop 64IX …0 16 Flags: 4 flags 0RPT R (RP-embedded address), P (Unicast-based prefix), T (permanent assignment or not) Scope: Allowed values are “8” for Organization-Local scope or “E” for Global scope. 64IX field (IPv4-IPv6 interconnection scheme bits): The first bit is the M-bit. When is set to 1, it indicates that an multicast IPv4 address is embedded in the last 32 bits of the multicast IPv6 address. All the remaining bits are reserved and MUST be set to 0. 6 This means: reserve ffxx:8000/17 ASM block and ff3x:0:8000/33 SSM block to embed an IPv4 multicast address in the last 32 bits

PIM IPv4 PIM IPv6 IPv4-IPv6 Interconnection Function UE S Source Stateless IGMP- MLD interworking function R CPE IPv6 Receiver IPv4 Receiver On IPv4-Embedded IPv6 Multicast Addresses IGMP MLD PIM Stateless IPv4-IPv6 PIM interworking function Stateless (local) synthesis of IPv6 address when IPv4 multicast address are embedded in application payload (e.g., SDP) Stateless IPv4-IPv6 header translation of multicast flows No coordination is required between IPv4-IPv6 PIM interworking function, IGMP-MLD interworking function, IPv4-IPv6 Interconnection Function and any ALG in the path Minimal operational constraints on the multicast address management: IPv6 multicast addresses can be constructed using what has been deployed for IPv4 delivery mode S  S6; G  G6 Advertises in the IPv6 realm the IPv4- converted IPv6 address of S For SPT mode in ASM, requests will be received by this function For SSM, requests will be received by this node (ASM/SSM)

Why Need this Bit? This bit is used to signal the border multicast router who is in the edge of IPv4-IPv6 domain to perform necessary procedure to translate the address. An application (app in receiver or ALG north of receiver) may prefer a native multicast address rather than an IPv4 embedded address to avoid unnecessary translation. Without explicit bit in the address this is not possible. 8

Why not define a Well-Known Prefix? This implies the RP network prefix must be the same when Embedded RP is used. This adds unnecessary constraint to network design. This also requires the PIM JOIN using the IPv4- embedded IPv6 address must reach the translator (i.e., RP must be the translator). 9

Why not each domain uses its own prefix? This will require each domain to configure the prefix so that the routers knows address using the preconfigured prefix will have an IPv4 address embedded to it. When we want to use this across domains, this will require coordination between domains to exchange their preconfigured prefixes which may impose operation overhead to manage the network. 10

Alternative An alternative method is to include the bit not in the address but in the PIM JOIN and MLDv2 Report Message It does not help an application to signal an address is native or an IPv4 Embedded IPv6 Address Details specification is described in draft-kumar-mboned- 64mcast-embedded-address-00.txt 11

Why Not Used the Last Flag Bit? This is the last bit. If we use it, nothing left. There are implementations hardcoded FF3X::/32 for SSM and FF7x::/12 for Embedded-RP. RFC3306 Section 6 says: These settings create an SSM range of FF3x::/32 (where 'x' is any valid scope value). –Implementation(s) may ignore FFBx::/32 as a valid SSM address. RFC3956 Section 3 says: Without further IETF specification, implementation SHOULD NOT treat FFF0:/12 range as Embedded-RP. –This prohibits to use Embedded RP for v4 address in the “group ID” for translation. 12